TSG Working Agreements
"Working Agreements" are tentative decisions reached by 3GPP groups in order to make progress on matters where consensus [1] cannot be reached. See the 3GPP Working Procedures, article 25. See document PCG20_04 (slides 4 & 5) for further background information.
To propose additions to this page: elisabetta.comin@etsi.org.
Only working agreements explicitly documented in meeting reports will be included. Where appropriate, reference may be made to a meeting contribution (TDoc) supporting the working agreement, or giving further details.
To challenge a working agreement, contact the Chair of the meeting where the challenge would be resolved. The challenge will normally result in a formal vote at the earliest possible meeting. See the 3GPP Working Procedures, articles 25 & 26.
| # | Text | Date of inclusion | Challenge to be addressed at meeting | Supporting Tdoc | challenge-by date | meeting at which created | Status |
| 60 | The SA WG2 Chair declared during SA2#160 meeting that the CR on 'PDU Set based QoS Handling for uplink transmission' in S2-2313912 (23.501 CR4744R7) was agreed as a working agreement. | 22 November 2023 | SA#102 | S2-2313912 | 04 December 2023 | SA2#160 | Unchallenged by date limit thus implicitly confirmed |
| 59 | The SA5 Chair stated that the revised WID in tdoc S5-236538 was agreed. This was declared a working agreement | 13 October 2023 | SA5#152 | S5-236538 | 06 November 2023 | SA5#151 | Unchallenged by date limit thus implicitly confirmed |
| 58 | CT3 Chair concluded that a working agreement is declared for agreeing C3-234550 | 12 October 2023 | CT3#131 | C3-234550 | 06 November 2023 | CT3#130 | Challenged and overturned by vote |
| 57 | CT1 Chair concluded that a working agreement is declared for agreeing C1-235990 and C1-235994. | 25 August 2023 | CT1#143 | C1-235990 C1-235994 | 04 September 2023 | CT#101 | Challenged and overturned by vote |
| 56 | SA1 Chair concluded that a Working Agreement is declared for agreeing S1-232633 (pCR), S1-232595 (new version of the TR 22.841), S1-232289 (WID) and S1-232371 (CR). | 25 August 2023 | SA1#103 | S1-232633 S1-232595 S1-232289 S1-232371 | 04 September 2023 | SA#101 | Challenged and overturned by vote |
| 54 | The Chair declared as a working agreement the following: For ProSe TR33.740 key issue #1 on the protection of U2U discovery set and direct discovery set, two sets of key materials shall be used, and not one set. | 27 April 2023 | SA3-110-adhoc-e | No supporting tdoc | 15 May 2023 | SA3#111 | Unchallenged by date limit thus implicitly confirmed |
| 53 | The SA5 Chair declared the contents of tdoc S5-232888 was approved as a Working agreement. | 07 March 2023 | SA5#147 | S5-232888 | 15 March 2023 | SA#99 | Unchallenged by date limit thus implicitly confirmed |
| 55 | The Chair declared a working agreement on the content of tdoc S3-233047 | 30 May 2023 | SA3#111 | S3-233047 | 05 June 2023 | SA#100 | Unchallenged by date limit thus implicitly confirmed |
| 49 | The SA3 Chair declared a working agreement approving S3-221072 on 5GFBS - Conclusion for solution#17. | 30 May 2022 | SA3#107-e | S3-221072 | 08 August 2022 | SA3#108-e | Unchallenged by date limit thus implicitly confirmed |
| 52 | The SA5 Chair declared the contents of tdoc S5-232887 was approved as a Working agreement. | 07 March 2023 | SA5#147 | S5-232887 | 15 March 2023 | SA#99 | Unchallenged by date limit thus implicitly confirmed |
| 50 | The SA3 Chair declared a working agreement that ProSe key is generated by the AUSF (not in the PRoSE Anchor function PAnF). It is also agreed that the keys 5GPRUK and 5GPRUK ID are stored in PRoSE Anchor function PAnF and accessed via AUSF. There is no specific Tdoc related to this. | 30 May 2022 | SA3#107-e | 08 August 2022 | SA3#108-e | Unchallenged by date limit thus implicitly confirmed | |
| 51 | The TSG SA Chairman declared during TSG SA#96 meeting that CR Pack SP-220412 was approved as a working agreement. | 17 June 2022 | SA#96 | SP-220412 | 04 September 2022 | SA#97-e | Unchallenged by date limit thus implicitly confirmed |
| 46 | The SA WG5 Chair declared during SA5#142e that the document S5-222759 “Add requirements for data management” was approved as a working agreement. | 14 April 2022 | SA5#142-e | S5-222759 | 17 May 2022 | SA5#143e-Bis (24-25 May) | Unchallenged by date limit thus implicitly confirmed |
| 45 | CT3 Chair declared during CT3#121e that the pCR on EDGEAPP (unification of APIs) C3-222576 was agreed as a working agreement | 11 April 2022 | CT3#121-e | C3-222576 | 17 May 2022 | CT3 exceptional meeting (24th to 25th of May) | Unchallenged by date limit thus implicitly confirmed |
| 48 | The CT1 Chair declared during CT1#136-e that the CR in C1-223442 on “Addition of lower bound IEs for #78, alt 2” was agreed as a working agreement | 23 May 2022 | CT1#136-e | C1-223442 | 11 August 2022 | CT1#137-e | Unchallenged by date limit thus implicitly confirmed |
| 43 | The SA WG2 Chair declared during SA2#149-e meeting that the CR on 'SMF+PGW-C assigned PDU Session ID' in S2-2201675 (23.502) was approved as a working agreement. | 18 February 2022 | SA2#149-e | S2-2201675 | 07 March 2022 | SA#95-e | Challenge withdrawn |
| 44 | RAN2 Chair declared a working agreement regarding REL-17 WI NR_UE_pow_sav_enh-Core: - UE can start/stop RLM/BFD relaxation by itself if it meets/fails the relaxation criteria. - The feature is configured by RRC dedicated signalling, this is the only enable disable function that is supported | 22 February 2022 | RAN2#117-e | R2-2203992 | 10 March 2022 | RAN#95-e | Resolved via compromise (see RP-221003) |
| 41 | During the SA3#104eAd-Hoc meeting, the SA3 Chair declared that the content of the document S3-213611 is considered approved as a working agreement. | 04 October 2021 | SA3#104eAd-Hoc | S3-213611 | 01 November 2021 | SA3#105-e | Compromise solution achieved. See S3-214156 |
| 42 | The SA5 Chair declared during the SA5#139e meeting that the CR in S5-215534 was agreed as a Working Agreement. | 19 October 2021 | SA5#139-e | S5-215534 | 08 November 2021 | SA5#140-e | Unchallenged by date limit thus implicitly confirmed |
| 47 | The SA WG5 Chair declared during SA5#142e that the document S5-222633 “Management data collection” was approved as a working agreement. | 14 April 2022 | SA5#142-e | S5-222633 | 17 May 2022 | SA5#143e-Bis | Unchallenged by date limit thus implicitly confirmed |
| 37 | The TSG SA Chairman declared during TSG SA#89-e meeting that the content of SP-200870 was endorsed as a working agreement. | 23 September 2020 | SA#89-e | SP-200870 | 02 December 2020 | SA#90-e | Unchallenged by date limit thus implicitly confirmed |
| 38 | The RAN4 Chairman declared during RAN4#97-e meeting that the content of R4-2016850 was approved as a working agreement. | 12 November 2020 | RAN4#97-e | R4-2016850 | 30 November 2020 | RAN#90-e | Unchallenged by date limit thus implicitly confirmed |
| 35 | The CT1 Chairman declares during CT1#125e meeting that the Change Requests in C1-205249, C1-205183 and C1-205184 are agreed as a working agreement. | 27 August 2020 | CT1#125-e | C1-205249 C1-205183 C1-205184 | 07 September 2020 | CT#89-e | Challenge withdrawn |
| 36 | The SA6 Chair declared during SA#39-e meeting that the pCRs (related to Application Context Relocation Scenarios) in S6-201679, S6-201680, S6-201681, S6-201635, and S6-201682 were approved as a working agreement. | 15 September 2020 | SA6#39-e | S6-201679 S6-201680 S6-201681 S6-201635 S6-201682 | 05 October 2020 | SA6#39 BIS-e | Unchallenged by date limit thus implicitly confirmed |
| 39 | The SA6 Chairman declared during SA6#42-e meeting that the pCR S6-210730 (Service-based interfaces interaction within EDGEAPP) was approved as a working agreement. | 11 March 2021 | SA6#42-e | S6-210730 | 05 April 2021 | SA6#42BIS-e | Challenge withdrawn |
| 40 | The SA2 Chairman declared during SA2#145-e meeting that the CRs on ' Function Description for Multi-USIM devices' in S2-2105148 (23.401) and S2-2105149 (23.501) were approved as a working agreement. | 31 May 2021 | SA2#145-e | S2-2105148, S2-2105149 | 08 June 2021 | SA#92-e | Unchallenged by date limit thus implicitly confirmed |
| 29 | The following 3 CRs on "Capability for aperiodic CSI-RS triggering with different numerology between PDCCH and CSI-RS" were approved by RAN #83 with a working agreement: RP-190632 (38.214 REL-15), RP-190633 (38.331 REL-15), RP-190634 (38.306 for REL-15) due to sustained objection from 2 companies. | 25 March 2019 | RAN#83 | RP-190632 RP-190633 RP-190634 | 27 May 2019 | RAN#84 | Challenged and overturned by vote. |
| 34 | The TSG SA Chairman declared during TSG SA#88-e meeting that the Change Requests in SP-200549 and SP-200550 were approved as a working agreement. | 06 July 2020 | SA#88-e | SP-200549 SP-200550 | 08 September 2020 | SA#89-e | Unchallenged by date limit thus implicitly confirmed |
| 32 | The CT6 Chairman declared during the CT6#94 meeting that the Change Request in TD C6-190279 was agreed as a working agreement. | 28 June 2019 | CT6#94 | C6-190279 | 09 September 2019 | CT#85 | Compromise solution achieved |
| 30 | The SA6 Chairman declared during the SA6#30 meeting that the Change Request in TDoc S6-190869, was agreed as a working agreement. | 17 April 2019 | SA6#30 | S6-190869 | 13 May 2019 | SA6#31 | Unchallenged by date limit thus implicitly confirmed |
| 33 | The SA6 Chairman declared during the SA6#34 meeting that the Rel-16 Change Request in TDoc S6-192217 be agreed as a working agreement due to objections from only 2 companies while 12 companies were in favour of the CR. The CR removes the ‘temporary re-group procedures’ from Rel-16 due to no progress on corresponding security solution. As a compromise, the procedures have been included in Rel-17 to allow for potential resolution during Rel-17 timeframe. | 15 November 2019 | SA6#34 | S6-192217 | 02 December 2019 | SA#86 | Unchallenged by date limit thus implicitly confirmed |
| 31 | The SA2 Chairman declared during the SA2#133 meeting that the Change Request in TD S2-1906569 was agreed as a working agreement. | 21 May 2019 | SA2#133 | S2-1906569 | 29 May 2019 | SA#84 | Challenged and overturned by vote. |
| 23 | "The Chair has declared in SA3#91-Bis that the Change Request in the tdoc S3-182010 will be agreed as a working agreement" | 23 May 2018 | SA3#91-Bis | S3-182010 | 06 June 2018 | SA#80 | Compromise solution achieved See SP-180534. |
| 28 | The CT1 Chairman declared in CT1#115 that the Change Request in Tdoc C1-191571 was agreed as a working agreement. | 04 March 2019 | CT1#115 | - | 01 April 2019 | C1-116 | Unchallenged by date limit thus implicitly confirmed |
| 26 | The Chairman declared in CT1#113 that the Change Request in Tdoc C1-188888 was agreed as a working agreement. | 03 December 2018 | CT1#113 | - | 14 January 2019 | CT1#114 | Sustained objection withdrawn thus implicitly confirmed |
| 27 | The Chairman declared in CT1#113 that the Change Request in Tdoc C1-188578 was agreed as a working agreement. | 03 December 2018 | CT1#113 | - | 14 January 2019 | CT1#114 | Sustained objection withdrawn thus implicitly confirmed |
| 25 | The Chairman has declared in RAN3#102 that the draft Change Request in TDoc R3-187266 was agreed as a working agreement. It will be reviewed by RAN2 and will become a formal CR. | 20 November 2018 | RAN3#102 | R3-187266 | 03 December 2018 | RAN#82 | Compromise solution achieved |
| 19 | RAN4 way forward on NR BS EVM had sustained opposition by a small minority preventing consensus. The working agreement was made for the way forward in R4-1706969 . | 11 July 2017 | RAN4-NR#2 | R4-1706969 | 14 August 2017 | R4-84 | Unchallenged by date limit thus implicitly confirmed |
| 22 | At SA1#81, the following Working Agreement is made: “Subject to Home MNO policy as well as its service and operational needs, a legacy USIM instead of a 5G USIM may be used to authenticate a user in a 5G system to get services according to her/his subscription, without introducing undue security risks.” | 13 March 2018 | SA1#81 | S1-180610 | 14 March 2018 | SA#79 | Sustained objection withdrawn thus implicitly confirmed |
| 24 | The Chair has declared in CT1#112 that the Change Request in Tdoc C1-185794 (or a further revision) will be agreed as a working agreement. An LS will be sent to SA2 for information, and if concerns are raised, the agreed / approved change will be reverted. | 27 August 2018 | CT1#112 | C1-185794 | 08 October 2018 | CT1#112bis | Unchallenged by date limit thus implicitly confirmed |
| 18 | Approve TS 22.261 CR0031R1 in CR Pack SP-170443. Send guidance to SA WG3 to provide guidance on alignment with this CR in LS (SP-170581). | 13 June 2017 | SP-76 | SP-170582 SP-170443 SP-170581 | 06 September 2017 | SP#77 | Unchallenged by date limit thus implicitly confirmed |
| 17 | CT1 has agreed that UEs supporting enhanced coverage are mandated to support restriction on use of enhanced coverage, see CR #2860 to TS 24.301 (and its companion CR #3062 to TS 24.008). | 09 April 2017 | C1-103 | C1-171925 C1-171643 | 08 May 2017 | C1-104 | Unchallenged by date limit thus implicitly confirmed |
| 20 | RAN4 way forward on NR sync raster had a sustained opposition by a small minority preventing a consensus. The working agreement was made for the way forward in R4-1803438. | 05 March 2018 | RAN4#86 | R4-1803438 | 09 April 2018 | RAN4#86bis | Challenged but confirmed by vote |
| 14 | SA4 at its ad hoc teleconference 2016-03-10 agreed that draft TS 26.179 v0.2.0 (tdoc S4-AHT011, produced following the teleconference) was agreed to be converted to version 1.0.0 and sent to TSG SA#71 for information and approval. The agreement was supported by eighteen organizations. Two organizations sustained objection to the agreement. | 10 March 2016 | S4-MCPTT codecs and media handling | S4-AHT011 | 04 April 2016 | S4-88 | Sustained objection withdrawn thus implicitly confirmed |
| 21 | RAN4 way forward on NR sync raster had a sustained opposition by a small minority preventing a consensus. The working agreement was made for the way forward in R4-1803438. | 05 March 2018 | RAN4#86 | R4-1803438 | 09 April 2018 | RAN4#86bis | Challenged but confirmed by vote |
| 15 | CT1 has decided that an explicit indication in the SIB of support for "attach without PDN connectivity" by the network, will prevent the UE from having to discover availability of such a feature by using trial and error in Attach request and will facilitate handling when UE moves across tracking areas or changes PLMNs. | 13 April 2016 | C1-97 | - | 16 May 2016 | C1-98 | Unchallenged by date limit thus implicitly confirmed |
| 13 | The 3GPP System shall provide a secure mechanism via the 3GPP network to remotely provision an IOT-device, that has not been pre-provisioned, with its 3GPP subscription credentials | 18 February 2016 | S1-73 | S1-160529 | 22 February 2016 | SP-71 | Unchallenged by date limit thus implicitly confirmed |
| 11 | RAN4 way forward on Band 28 as global band had sustained opposition by a small minority preventing a consensus. The working agreement was made for the way forward in R4-146724. RAN4 received an LS from CEPT (R4-143812) requesting to harmonise the out of band requirements for 700 MHz mobile terminals between Europe and other regions. Agreement was to delete NS_24 from Rel-12 and add the -42dBm/8MHz associated to NS_01 for 10MHZ E-UTRA carrier within 703-733MHz, Otherwise -25 dBm/8MHz apply. -42dBm/8MHz will be specified in Rel-11 version of TS36.101. CRs for Rel-11 and Rel-12 will be approved in RAN4-73. This working agreement process will continue in RAN4-73. In case of challenge the questions to be vote for is: “Shall the UE out of band emission limit for Band 28 be specified as proposed in way forward on Band 28 as global band in R4-146724?” | 15 October 2014 | R4-72b | R4-146724 | 10 November 2014 | R4-73 | Unchallenged by date limit thus implicitly confirmed |
| 10 | RAN4 CR on Maximum allowed UL TX power for Band XXVI coexistence with Public Safety: CR 1041 (R4-144970) to TS 25.101 Rel-11, and CR 1042 (R4-144971) to 25.101 Rel-12, had sustained objection from Qualcomm. The topic had already been discussed at length in the previous RAN4 meetings, and the working assumption was made that these two CRs were agreed. The two CRs introduce UL power restrictions for single and dual carrier for certain uplink center frequencies for coexistence with Public Safety and Band 27 and they allow power averaging for the 6.25 kHz measurement bandwidth similar to requirements for protection of Public Safety in the 700 MHz band. | 25 August 2014 | R4-72 | R4-144970 R4-144971 | 02 September 2014 | RP-65 | Unchallenged by date limit thus implicitly confirmed |
| 12 | RAN4 way forward on LAA bands had sustained opposition by a small minority preventing a consensus. The working agreement was made for the way forward in R4-156785. The way forward is: 1) LAA operation is defined with a single operating band with the frequency range of 5150-5925MHz. 2) Sub-bands can be introduced in the BS specification in order to reflect specific regulatory requirements or restrictions. 3) The duplex method for 5GHz unlicensed band will be TDD subject to RAN1 design of new frame structure. – UL requirements are not defined in this version of specifications. | 19 October 2015 | R4-76b | R4-156785 | 09 November 2015 | R4-77 | Unchallenged by date limit thus implicitly confirmed |
| 9 | Proposal 3: Take the average of the average of all companies' proposed figures and the 2nd least stringent figure. (this is in fact the average of figures coming out of Proposal 1 and 2) | 06 June 2014 | G1-62 | GP-140331 | 19 August 2014 | G1-63 | Unchallenged by date limit thus implicitly confirmed |
| 8 | Exception sheet for work item "Enhancement to FEC for MBMS" (EMM-EFEC, uid 530148) was agreed, with a formal objection by Broadcom Corporation. | 15 November 2012 | S4-71 | S4-121562 | 03 December 2012 | SP-58 | Unchallenged by date limit thus implicitly confirmed |
| 7 | TR 45.860 CR0009r3 "Conclusion of SI Signal Precoding Enhancements for EGPRS2 DL (SPEED)" (Rel-11) was approved, with a formal objection by Nokia Siemens Networks. | 05 February 2012 | G1-53 | GP-120393 | 07 May 2012 | GP-54 | Unchallenged by date limit thus implicitly confirmed |
| 6 | "The emission requirement for Band 26 shall be -53 dBm / 6.25 kHz." The OOBE limit for co-existence with narrow band systems in the 851-859 MHz range is the only remaining issue blocking the approval of the WI e850_UB-Core. The topic has been discussed for a long time without reaching consensus. A substantial majority of individual members are in favour of -53 dBm / 6.25 kHz emission requirement for Band 26 but there is sustained opposition preventing consensus on this value. | 09 February 2012 | R4-62 | R4-121040 R4-121041 | 21 February 2012 | RP-55 | Confirmed by vote at RP-55 |
| 5 | Three RAN4 CRs for band 3.5GHz (WI code RInImp8-UMTSLTE3500): CR1140 (R4-114395) to TS 25.133, CR838r1 (R4-114755) to TS 25.101, and CR908r1 (R4-114762) to TS 36.101, had sustained objection from Qualcomm. The Topic had already been discussed at length in the previous RAN4 meetings, and the working assumption was made that these three CRs were agreed defining the requirement for tolerance for Maximum output power for LTE and for maximum output power and reference sensitivity for UTRA. | 29 August 2011 | R4-60 | R4-114395 R4-114755 R4-114762 | 06 September 2011 | RP-53 | Unchallenged by date limit thus implicitly confirmed |
| 4 | TDoc GP-101632 proposed working assumption on interference profiles for VAMOS uplink performance, from Nokia Siemens Networks, Telefon AB LM Ericsson, Vodafone Group, CMCC, was endorsed at the closing TSG GERAN#47 Plenary meeting. | 06 September 2010 | GP-47 | GP-101632 | 15 November 2010 | GP-48 | Unchallenged by date limit thus implicitly confirmed |
| 3 | At RAN #48, RAN4 CR0530r1 to "E-UTRA;User Equipment (UE) radio transmission and reception" v9.3.0 in RP-100683 had one sustained objection against the modification in table 7.3.1-2 for the case E-UTRA band 20 (see TS 36.101 table 5.5-1, WI RInImp9-UMTSLTE800EU) for the 10MHz channel bandwidth. The objecting company proposed RP-RP-100684 instead. The topic had already been discussed at length in the previous RAN4 meeting and there were strong market requirements in favour of a conclusion at RAN#48. As a working agreement the CR in RP-100683 was approved (to avoid delay in LTE UE implementation) for implementation after RAN#48. | 04 June 2010 | RP-48 | RP-100683 | 07 September 2010 | RP-49 | Unchallenged by date limit thus implicitly confirmed Note: R4-56 agreed an additional 36.101 CR0617r1 in R4-103463 which will be provided to RP-49 for approval. |
| 2 | CEN TC 278 WG 15 recommended to make the necessary changes to overcome the problem described in the LS from CEN to ETSI MSG forwarded to SA1 and SA4, i.e. to change the eCall initiation sequence, so that eCall equipped PSAPs only emit a SEND MSD message (in-band tone) in response to a valid incoming eCall INITIATION message from a vehicle eCall terminal (i.e. push mode) - the "In-Vehicle System" (IVS). Accordingly SA1 produced three CRs to TS 22.101 to be submitted to SA Plenary #45 for approval to clarify the service requirement, conditional on SA4 agreeing to include push mode operation. The CRs in question are: S1-093004 22.101 CR314 eCall mode of operation (Release 8), S1-093289 22.101 CR317 rev 1 Minimise delay to emergency voice calls (Release 8), and the "mirror CR" in S1-093290 22.101 CR315 rev 1 Minimise delay to emergency voice calls (Release 9). However concerns were raised at SA1 and later at SA4 about potential impacts of the changes proposed in S1-093289 and S1-093290. Those impacts are related to the situation where the push mode is facing some waiting / welcome messages on 112 lines. | 24 August 2009 | S4-55 | S4-090552 26.267 CR3r1 "Integration of IVS-initiated signalling option", S4-090473 26.268 CR7 "Integration of IVS-initiated signalling option | 14 September 2009 | SP-45 | Withdrawn Challenged 2009-09-11 in SP-090558 Following discussion at SP-45 and approval of liaison SP09-0666 urging WGs S1, C1 and C4 to develop an end-to-end eCall signal, the challenge was withdrawn. |
| 1 | REQ-ANR-CON-003 Operator shall be able to set the default values for the constraints for allowing and prohibiting HOs for NRs newly created by the ANR function. REQ-ANR-CON-004 Operator shall be able to set the default behaviour for allowing and prohibiting X2 connection setup to eNBs parenting newly detected cell by the ANR function | 17 October 2008 | S5-61 | S5-081945 | 09 November 2008 | S5-62 | Withdrawn Challenge in S5-081721. Proposed solution in S5-082442 Source: Vodafone. Discussion: The Vodafone proposal was approved by the group. The working agreement in S5-081945 was agreed to be withdrawn. |
Possible status values:
- Not yet challenged
- Challenged
- Challenged but confirmed by vote (or subsequent consensus)
- Challenged and overturned by vote (or subsequent consensus)
- Unchallenged by date limit thus implicitly confirmed
- Sustained objection withdrawn thus implicitly confirmed
- Commpromise solution achieved
Note: On April 19, 2016 the Working agreement Status (table above) the term “withdrawn” was clarified and now reads “Sustained objection withdrawn thus implicitly confirmed.”
1 Consensus is defined as the lack of sustained opposition. A working agreement representing the majority view is typically arrived at if only a very small number of individual members sustain opposing views.