Connect
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: susanna.kooistra@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.
Concordia discors : adversus solem ne loquitor.
Status | Text | Date of | meeting at which created | supporting | challenge- | Challenge to be addressed at meeting | # |
|---|---|---|---|---|---|---|---|
51 | The TSG SA Chairman declared during TSG SA#96 meeting that CR Pack SP-220412 was approved as a working agreement. | 2022-06-17 | SA#96 | 2022-09-04 | SA#97-e | ||
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. | 2022-05-30 | SA3#107-e | 2022-08-08 | SA3#108-e | ||
49 | The SA3 Chair declared a working agreement approving S3-221072 on 5GFBS - Conclusion for solution#17. | 2022-05-30 | SA3#107-e | 2022-08-08 | SA3#108-e | ||
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 | 2022-05-23 | CT1#136-e | C1-223442 | 2022-08-11 | CT1#137-e | |
47 | The SA WG5 Chair declared during SA5#142e that the document S5-222633 “Management data collection” was approved as a working agreement. | 2022-04-14 | SA5#142-e | S5-222633 | 2022-05-17 | SA5#143e-Bis | 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. | 2022-04-14 | SA5#142-e | S5-222759 | 2022-05-17 | 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 | 2022-04-11 | CT3#121-e | 2022-05-17 | CT3 exceptional meeting (24th to 25th of May) | Unchallenged by date limit thus implicitly confirmed | |
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 | 2022-02-22 | RAN2#117-e | 2022-03-10 | RAN#95-e | Resolved via compromise (see RP-221003) | |
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. | 2022-02-18 | SA2#149-e | 2022-03-07 | SA#95-e | Challenge withdrawn | |
42 | The SA5 Chair declared during the SA5#139e meeting that the CR in S5-215534 was agreed as a Working Agreement. | 2021-10-19 | SA5#139-e | 2021-11-08 | SA5#140-e | Unchallenged by date limit thus implicitly confirmed | |
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. | 2021-10-04 | SA3#104eAd-Hoc | 2021-11-01 | SA3#105-e | Compromise solution achieved. See S3-214156 | |
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. | 2021-05-31 | SA2#145-e | S2-2105148, S2-2105149 | 2021-06-08 | SA#92-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. | 2021-03-11 | SA6#42-e | 2021-04-05 | Challenge withdrawn | ||
38 | The RAN4 Chairman declared during RAN4#97-e meeting that the content of R4-2016850 was approved as a working agreement. | 2020-11-12 | RAN4#97-e | 2020-11-30 | RAN#90-e | 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. | 2020-09-23 | SA#89-e | 2020-12-02 | SA#90-e | Unchallenged by date limit thus implicitly confirmed | |
36 | 2020-09-15 | 2020-10-05 | SA6#39 BIS-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. | 2020-08-27 | 2020-09-07 | Challenge withdrawn | |||
34 | 2020-07-06 | 2020-09-08 | 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. | 2019-11-15 | 2019-12-02 | 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. | 2019-06-28 | 2019-09-09 | Compromise solution achieved | |||
31 | The SA2 Chairman declared during the SA2#133 meeting that the Change Request in TD S2-1906569 was agreed as a working agreement. | 2019-05-21 | 2019-05-29 | Challenged and overturned by vote. | |||
30 | The SA6 Chairman declared during the SA6#30 meeting that the Change Request in TDoc S6-190869, was agreed as a working agreement. | 2019-04-17 | 2019-05-13 | 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. | 2019-03-25 | 2019-05-27 | Challenged and overturned by vote. | |||
28 | The CT1 Chairman declared in CT1#115 that the Change Request in Tdoc C1-191571 was agreed as a working agreement. | 2019-03-04 | - | 2019-04-01 | Unchallenged by date limit thus implicitly confirmed | ||
27 | The Chairman declared in CT1#113 that the Change Request in Tdoc C1-188578 was agreed as a working agreement. | 2018-12-03 | - | 2019-01-14 | Sustained objection withdrawn thus implicitly confirmed | ||
26 | The Chairman declared in CT1#113 that the Change Request in Tdoc C1-188888 was agreed as a working agreement. | 2018-12-03 | - | 2019-01-14 | 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. | 2018-11-20 | 2018-12-03 | Compromise solution achieved | |||
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. | 2018-08-27 | 2018-10-08 | Unchallenged by date limit thus implicitly confirmed | |||
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" | 2018-05-23 | 2018-06-06 | ||||
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.” | 2018-03-13 | 2018-03-14 | 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. | 2018-03-05 | 2018-04-09 | Challenged but confirmed by vote | |||
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. | 2018-03-05 | 2018-04-09 | Challenged but confirmed by vote | |||
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 . | 2017-07-11 | 2017-08-14 | Unchallenged by date limit thus implicitly confirmed | |||
18 | 2017-06-13 | 2017-09-06 | 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). | 2017-04-09 | 2017-05-08 | Unchallenged by date limit thus implicitly confirmed | |||
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. | 2016-04-13 | - | 2016-05-16 | Unchallenged by date limit thus implicitly confirmed | ||
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. | 2016-03-10 | S4-MCPTT codecs and media handling | S4-AHT011 | 2016-04-04 | S4-88 | Sustained objection withdrawn 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 | 2016-02-18 | S1-73 | S1-160529 | 2016-02-22 | SP-71 | 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: | 2015-10-19 | 2015-11-09 | 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 ?” | 2014-10-15 | 2014-11-10 | 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. | 2014-08-25 | 2014-09-02 | 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) | 2014-06-06 | 2014-08-19 | 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. | 2012-11-15 | 2012-12-03 | 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. | 2012-02-05 | 2012-05-07 | 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. | 2012-02-09 | 2012-02-21 | 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. | 2011-08-29 | 2011-09-06 | Unchallenged by date limit thus implicitly confirmed | |||
4 | 2010-09-06 | 2010-11-15 | Unchallenged by date limit thus implicitly confirmed | ||||
3 | At RAN #48, RAN4 CR0530r1 to TS 36.101 "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-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. | 2010-06-04 | 2010-09-07 | Unchallenged by date limit thus implicitly confirmed | |||
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. | 2009-08-24 | 2009-09-14 | 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 | 2008-10-17 | 2008-11-09 | 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.