Description
Within the 3GPP standardization ecosystem, a Solution Proponent (SP) is a crucial entity, typically a company, group of companies, or a regional standards organization, that takes the initiative to propose a new technical feature or system enhancement. The SP role is formal and procedural. The proponent is responsible for creating and submitting a detailed work item description (WID) or study item description (SID) proposal to the relevant 3GPP Technical Specification Group (TSG) or Working Group (WG). This proposal must comprehensively outline the objectives, scope, technical feasibility, and anticipated impact of the proposed work.
The proposal undergoes a rigorous evaluation process within the responsible group. The SP must present the justification for the new work, addressing aspects like market needs, technical benefits, backward compatibility, and complexity. They must also identify which existing specifications would be affected and propose a plan for the necessary changes. If the proposal is accepted as a Study Item, the SP often leads or heavily contributes to the study phase, producing a Technical Report (TR) that explores solutions. For a Work Item, the SP drives the development of the normative technical specifications, submitting numerous detailed technical contributions (CRs - Change Requests) to implement the feature across the relevant protocol and architecture specs.
The role of the SP extends beyond the initial proposal. They are expected to champion the feature throughout its lifecycle in 3GPP, coordinating with other members, resolving technical conflicts, and ensuring the work progresses to completion. The success of a feature often hinges on the commitment and technical resources of its SP. The list of specifications associated with an SP term like 'SP' in a glossary context often refers to the vast array of 3GPP specs that define the processes for work item handling, project management, and terminology, such as the 21-series, 22-series, 23-series, and 30-series documents, which govern how SPs operate within the system.
Purpose & Motivation
The Solution Proponent concept exists to provide a structured and accountable mechanism for introducing new ideas into the 3GPP standardization process. 3GPP is a consensus-driven organization involving hundreds of members; without a formal proponent system, it would be chaotic to manage the influx of proposals and ensure each has sufficient backing and technical merit. The SP serves as the responsible owner who shepherds the proposal, provides the necessary technical details, and rallies support, ensuring that valuable resources (meeting time, editor effort) are invested in well-justified projects.
This process addresses the limitations of an ad-hoc approach by ensuring that any new work item has a clear champion who is committed to seeing it through. It filters out vague or poorly supported ideas early. Historically, as mobile systems grew more complex, the need for this formal gatekeeping became evident to maintain the quality and coherence of the standards. The SP model balances openness (any member can propose) with responsibility (the proponent must do the work). It is fundamental to 3GPP's ability to evolve technologies like GSM, UMTS, LTE, and 5G NR in a managed way, driven by identified market requirements and technological innovations from its member companies.
Evolution Across Releases
The concept of a Solution Proponent was established as part of 3GPP's foundational project management and procedures. Initial processes defined in specifications like TS 21.900 (Project management) and TS 21.905 (Vocabulary) formalized the role of an entity proposing and driving new work items, setting the governance model for how 3GPP standards evolve from proposal to specification.
Explore further
Broader topics and technologies where SP plays a role.
Defining Specifications
3GPP specifications that define or reference SP, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj00 | 3GPP Technical Terms and Definitions | Rel-19 |
| TS 22.022 vj00 | ME Personalisation Features for GSM/3G | Rel-19 |
| TS 22.057 vj00 | Mobile Execution Environment (MExE) Stage 1 | Rel-19 |
| TS 22.801 vc00 | Study on Non-MTC Mobile Data Application Impacts | Rel-12 |
| TR 22.907 v1312 | UMTS IC Card and Terminal Concepts | Rel-4 |
| TS 23.171 v1300 | LCS Stage 2 Specification for UMTS | Rel-4 |
| TS 23.271 vj00 | LCS Stage 2 Specification | Rel-19 |
| TS 25.222 vj00 | UTRA TDD Multiplexing & Channel Coding | Rel-19 |
| TR 26.930 vj00 | WebRTC Enhancements for Immersive RTC over 5G | Rel-19 |
| TR 26.996 vj00 | ISAR Split Rendering Audio Characterization | Rel-19 |
| TS 28.390 vj00 | Solution Profiles for Interface IRPs | Rel-19 |
| TS 28.667 vj00 | RPTA IRP Requirements | Rel-19 |
| TS 28.668 vj00 | RPTA Integration Reference Point Requirements | Rel-19 |
| TS 28.735 vj00 | STN Interface NRM IRP Information Service | Rel-19 |
| TS 32.101 vj00 | Management principles and high-level requirements | Rel-19 |
| TS 32.140 vj00 | Subscription Management (SuM) requirements | Rel-19 |
| TS 32.141 vj00 | Subscription Management (SuM) Architecture | Rel-19 |
| TS 32.742 vb00 | STN NRM for Configuration Management | Rel-11 |
| TS 33.108 vj00 | LI Handover Interface Specification | Rel-19 |
| TS 33.246 vj00 | MBMS Security Specification | Rel-19 |
| TR 33.924 vj00 | GBA-OpenID Interworking Specification | Rel-19 |
| TR 33.980 vj00 | GAA & Liberty Alliance Interworking Guidelines | Rel-19 |
| TS 37.890 vj10 | Feasibility Study on 6 GHz for LTE/NR | Rel-19 |