Chairman's notes

 

IPR call reminder:

“I draw your attention to your obligations under the 3GPP Partner Organizations’ IPR policies. Every Individual Member organization is obliged to declare to the Partner Organization or Organizations of which it is a member any IPR owned by the Individual Member or any other organization which is or is likely to become essential to the work of 3GPP.

Delegates are asked to take note that they are thereby invited:

  • to investigate whether their organization or any other organization owns IPRs which are, or are likely to become Essential in respect of the work of 3GPP.
  • to notify their respective Organizational Partners of all potential IPRs, e.g., for ETSI, by means of the IPR Information Statement and the Licensing declaration forms"

 

Antitrust policy Reminder:

“I also draw your attention to the fact that 3GPP activities are subject to all applicable antitrust and competition laws and that compliance with said laws is therefore required of any participant of this TSG/WG meeting including the Chairman and Vice Chairman. In case of question I recommend that you contact your legal counsel.

The leadership shall conduct the present meeting with impartiality and in the interests of 3GPP.

Furthermore, I would like to remind you that timely submission of work items in advance of TSG/WG meetings is important to allow for full and fair consideration of such matters.”

 

 

List for Meeting: All Sessions
Temporary Documents List - Ordered by Agenda Item
AI TD# Type Doc For Subject Source Rel Comments e-mail_Discussion Result
0 - - - All Agenda Items - - Docs:=0 -
0.1 - - - Executive Summary - - Docs:=0 -
1 - - - Opening of the Meeting by e-mail - - Docs:=0 -
1.1 - - - Welcome Speech - - Docs:=0 -
1.2 - - - Introduction - - Docs:=0 -
1.3 - - - IPR & Antitrust reminders - - Docs:=0 -
1.4 - - - Approval of Agenda - - Docs:=2 -
1.4 SP-200891 AGENDA Approval Agenda & Procedures & Time Schedule for TSG SA#90-e TSG SA Chair The meeting agenda was approved. Approved
1.4 SP-201118 AGENDA Approval TSG SA#90-e GoToMeeting Sessions Agenda & Details TSG SA Chair May be updated throughout the meeting OPEN
1.5 - - - Report from previous SA meetings - - Docs:=1 -
1.5 SP-200892 REPORT Approval Draft report of TSG SA meeting #89E TSG SA Secretary The meeting report was approved. Approved
1.6 - - - Reports from TSG SA ad-hoc meetings and workshops - - Docs:=0 -
2 - - - Liaisons Statements - - Docs:=0 -
2.1 - - - Incoming LSs - proposed to note - - Docs:=19 -
2.1 - - - Block Approval Block 1 (Tue 15:00UTC) - - Docs:=19 -
2.1 SP-200895 LS In Information LS from ITU-R WP 5D: Invitation to IEGs to re-engage in Step 4 evaluation of the 'ETSI (TC DECT) and DECT Forum Proponent' and of the 'Nufront Proponent' candidate technology submissions for IMT-2020 under the ‘Way Forward’ Option 2 exceptional basis IMT- ITU-R WP 5D (5D_TD_201r1) CC#1: Block Noted Noted
2.1 SP-200896 LS In Information LS from ITU-R WP 5D: Development of a draft new Report ITU-R M.[IMT.C-V2X] - The use of the terrestrial component of IMT systems for Cellular-Vehicle-to-Everything ITU-R WP 5D (5D_TD_0206r2) CC#1: Block Noted Noted
2.1 SP-200897 LS In Information LS from ITU-R WP 5D: Future Technology Trends for the evolution of IMT towards 2030 and beyond ITU-R WP 5D (5D_TD_0219r2) CC#1: Block Noted Noted
2.1 SP-200898 LS In Information LS from GSMA 5GJA: LS response to TCCA on Public Safety GSMA 5GJA (5GJA14_121r1) CC#1: Block Noted Noted
2.1 SP-200899 LS In Information LS from NGMN Alliance Project P1: NGMN 5G End-to-End Architecture Framework (Phase-3) NGMN Alliance Project P1 (201117 NGMN_liaison) CC#1: Block Noted Noted
2.1 SP-200901 LS In Information LS from ETSI TC ITS: Open contribution or Review of initial Multi-Channel Operations study results, Mature Draft ETSI TR 103 439 from ETSI TC ITS - 'Intelligent Transport Systems (ITS); Multi-Channel Operation Study; Release 2' ETSI TC ITS (ITS(20)040040) CC#1: Block Noted Noted
2.1 SP-200900 LS In Information LS from ETSI JTC Broadcast: On ETSI TS 103 720 (5G Broadcast System for linear TV and radio services; LTE-based 5G terrestrial broadcast system) ETSI JTC Broadcast (BROADCAST(20)000075r3) CC#1: Block Noted Noted
2.1 SP-200908 LS In Information LS from SA WG4: LS reply on QoE Measurement Collection SA WG4 (S4-201600) CC#1: Block Noted Noted
2.1 SP-200909 LS In Information LS from SA WG4: Reply LS On ETSI TS 103 720 (5G Broadcast System for linear TV and radio services; LTE-based 5G terrestrial broadcast system) SA WG4 (S4-201606) CC#1: Block Noted Noted
2.1 SP-200905 LS In Information LS from RAN WG3: Reply LS on energy efficiency RAN WG3 (R3-205657) Rel-16 CC#1: Block Noted Noted
2.1 SP-200906 LS In Information LS from Ericsson: Reply LS on on energy efficiency RAN WG3 (R3-207014) Rel-17 CC#1: Block Noted Noted
2.1 SP-200912 LS In Information LS from SA WG5: Reply LS on energy efficiency SA WG5 (S5-205357) Rel-16 CC#1: Block Noted Noted
2.1 SP-200907 LS In Information LS from RAN WG3: LS Reply on HO to congested cells RAN WG3 (R3-207182) Rel-17 CC#1: Block Noted Noted
2.1 SP-200910 LS In Information LS from SA WG5: LS on QoE Measurement Collection SA WG5 (S5-205347) CC#1: Block Noted Noted
2.1 SP-200911 LS In Information LS from SA WG5: Reply LS on TM Forum implementation experiences 3GPP NRM Models SA WG5 (S5-205348) Rel-17 CC#1: Block Noted Noted
2.1 SP-200913 LS In Information LS from SA WG2: Reply LS on AUSF/UDM discovery based on SUCI information SA WG2 (S2-2009207) Rel-17 CC#1: Block Noted Noted
2.1 SP-200914 LS In Information LS from SA WG2: LS on ATSSS Phase 2 conclusions SA WG2 (S2-2009400) Rel-17 CC#1: Block Noted Noted
2.1 SP-200915 LS In Information LS from SA WG5: LS on Network Slice EE KPIs SA WG5 (S5-206446) Rel-17 CC#1: Block Noted Noted
2.1 SP-200916 LS In Information LS from SA WG5: LS on Network Slice EE KPIs SA WG5 (S5-206447) Rel-17 CC#1: Block Noted Noted
2.2 - - - Incoming LSs which need an outgoing LS - - Docs:=5 -
2.2 SP-200894 LS In Action LS from ITU-R WP 5D: LIAISON STATEMENT TO GCS PROPONENT AND TRANSPOSING ORGANIZATIONS OF LTE-ADVANCED ON THE REVISION OF IMT-ADV/31 (SCHEDULE FOR REVISION 5 OF RECOMMENDATION ITU R M.2012) ITU-R WP 5D (5D_TD_0184) CC#1: This LS was removed from block approval. CC#2: Noted Noted
2.2 SP-200902 LS In Information LS from ITU-R WP 4B: LIAISON STATEMENT TO 3GPP TSG SA AND TSG RAN ON THE INTEGRATION OF SATELLITE SOLUTIONS INTO 5G NETWORKS ITU-R WP 4B (R19-WP4B-201026-TD-0008) CC#1: Moved to 2.2 and removed from block approval. CC#2: Noted. Noted
2.2 SP-200903 LS In Action LS from CT WG1: LS on stage 3 aspects for Reliable Data Service Serialization Indication CT WG1 (C1-207769) Rel-17 CC#1: Removed from block approval. CC#2: Noted Noted
2.2 - - - Block Approval Block 2 (Wed 16:00UTC) - - Docs:=2 -
2.2 SP-200893 LS In Action LS from TSG RAN: LS on Relaxation of mini-WID requirement for Cat.B/C TEI CRs TSG RAN (RP-202001) Rel-16 Postponed SP-200868 from SA#89E. CC#1: This LS was noted. Noted
2.2 SP-200904 LS In Action Reply LS on RAN impact of FS_5MBS Study RAN WG2 (R2-2011271) Rel-17 CC#1: This LS was noted. Noted
3 - - - Items for discussion and early consideration - - Docs:=0 -
3.1 - - - Challenges to working agreements (Must have been previously requested) - - Docs:=0 -
3.2 - - - Issues highlighted for early treatment (Please contact the chair in advance) - - Docs:=0 -
3.3 - - - Discussion papers on work in Rel-15 and earlier - - Docs:=0 -
3.4 - - - Discussion papers on work in Rel-16 - - Docs:=0 -
3.5 - - - Discussion papers on work in Rel-17 - - Docs:=1 -
3.5 SP-201098 DISCUSSION Endorsement Discussion on documenting Edge Computing in SA WG2 AT&T, Broadcom, CATT, Charter Communications, Cisco, China Telecom, China Unicom, DT, Ericsson, Futurewei, Huawei, Intel, Interdigital, KDDI, KPN, Telecom Italia, Telefonica, Telia, Tencent, Verizon, Vodafone, ZTE Rel-17 CC#1: This should be discussed over e-mail. If there is no agreement, aa show of hands can be held at another CC. CC#4: This was noted. Susana (Vodafone) adds comments that could not be given in CC#1.
Dolby supports the comments made by Vodafone and the proposal in SP-201098.
Sherry (Xiaomi) asks if TS 23.501/5.13 can be updated to capture general description of the new R17 EC features (i.e. discovery, exposure and relocation mechanisms for Edge AS) with the detail described in 23.501, 23.502 and 23.503. In the meantime a new TR is created to capture other aspects that are mentioned in SP-201098.
Yusuke (KDDI) supports Vodafone's comments.
Nokia supports creating a TR to provide references to Edge Computing enablers and to describe deployment options, with normative specification in existing TS 23.50x.
Biao (China Telecom) fully supports Vodafone's comments.
Haris (Qualcomm) proposes the potential new TS to only
Deutsche Telekom (Johannes) supports the comments made by Vodafone and the proposal in SP-201098. Especially as SA#90 has a long discussion on tracking of features and requirements, this would especially help for feature tracking
Susana (Vodafone) can agree with the proposal from Qualcomm on a new TS with Rel 17 functionalities, contextualized with reference to support specified in Rel 15/16.
Also TIM can agree with the proposal from Qualcomm.
Deutsche Telekom (Johannes) also agrees with the proposal from Qualcomm.
Saso (Intel) supports the new TS. Also one comment to QC.
Huawei (Patrice) provides rev1 accordingly.
Sherry (Xiaomi) requests to add Xiaomi as supporting company to eEDGE_5GC.
Nokia requests clarification on latest proposal and on details provided in SP-201098.
Biao (China Telecom) also agrees with the proposal from Qualcomm and is OK with rev1 provided by Huawei.
Susana (Vodafone) clarifies that the rev1 provided by Huawei is for the updated WID in SP-201107 and not for the discussion paper in SP-201098.		 Noted
3.6 - - - Discussion papers on work in Rel-18 and later - - Docs:=0 -
4 - - - Reporting from SA Working Groups, other TSGs, and Others - - Docs:=0 -
4.1 - - - SA WG1 reporting - - Docs:=2 -
4.1 SP-201023 TOR Approval Proposed revision of the SA WG1 ToR SA WG1 CC#2: This was postponed. Samsung offers SP-201023_rev1 , reverting the ToR to S1-204461 as agreed by SA1 except for the terminology fixes pointed out by the CT chairman. SA needs to decide how to treat the SA1 ToR. Postponed
4.1 SP-201022 REPORT Information SA WG1 Report to TSG SA#90e SA WG1 Chair CC#2: Noted Noted
4.1 - - - Block Approval Block 3 (Wed 16:00UTC) - - Docs:=0 -
4.2 - - - SA WG2 reporting - - Docs:=1 -
4.2 SP-200944 REPORT Information SA WG2 Chair's status report to TSG SA#90E SA WG2 Chair CC#2: Noted Noted
4.2 - - - Block Approval Block 3 (Wed 16:00UTC) - - Docs:=0 -
4.3 - - - SA WG3 reporting - - Docs:=3 -
4.3 SP-201003 REPORT Information SA WG3 Status report SA WG3 Chair CC#2: Noted Noted
4.3 SP-201085 TOR Approval Terms of Reference (ToR) for SA WG3 (SA WG3) SA WG3 Chair CC#2: Removed from Block approval. CC#3: This TOR was approved Chris (Vodafone) asks whether security when using non-3GPP accesses needs to be reflected in the ToR?
SA3 chair provides clarifications on the use of the term 3GPP System in the SA3 ToR.
Chris (Vodafone) says that it is OK to consider any further details in SA3.		 Approved
4.3 SP-201086 OTHER Information CVD process update SA WG3 Chair, MCC CC#2: Noted Noted
4.3 - - - Block Approval Block 3 (Wed 16:00UTC) - - Docs:=0 -
4.4 - - - SA WG4 reporting - - Docs:=2 -
4.4 SP-200928 REPORT Information SA WG4 report to SA Plenary SA WG4 Chair CC#2: Noted Noted
4.4 SP-200929 TOR Approval Updated SA WG4 Terms of Reference (ToR) SA WG4 Chair CC#3: This TOR was approved Approved
4.4 - - - Block Approval Block 3 (Wed 16:00UTC) - - Docs:=0 -
4.5 - - - SA WG5 reporting - - Docs:=2 -
4.5 SP-201084 TOR Approval Proposed revision of SA WG5 ToR SA WG5 CC#3: This ToR was approved. Approved
4.5 SP-201087 REPORT Information SA WG5 Status report Ericsson LM CC#2: Noted Noted
4.5 - - - Block Approval Block 3 (Wed 16:00UTC) - - Docs:=0 -
4.6 - - - SA WG6 reporting - - Docs:=2 -
4.6 SP-200927 TOR Approval Terms of Reference (ToR) for SA WG6 (SA WG6) SA WG6 Chair CC#2: Removed from Block approval. CC#3: This was postponed. Postponed
4.6 SP-200982 REPORT Information SA WG6 status report to TSG SA#90 SA WG6 Chair CC#2: Noted Noted
4.6 - - - Block Approval Block 3 (Wed 16:00UTC) - - Docs:=0 -
4.7 - - - TSG RAN reporting and RAN ITU-R Ad Hoc Matters (will be handled on Monday 14 December in separate call) - - Docs:=3 -
4.7 SP-200917 LS In Action DRAFT Letter to ITU on the completion of the submission of LTE-Advanced toward Revision 5 of Rec. ITU-R M.2012, 'Detailed specifications of the terrestrial radio interfaces of International Mobile Telecommunications Advanced (IMT-Advanced)' TSG RAN (RP-202861) For 3GPP review: in: TSG SA feedback LS before: December 11, 2020 to: PCG. CC#4: Endorsed and will be forwarded to the PCG Endorsed
4.7 SP-200918 LS In Information LS from TSG RAN: Reply LS to ITU-R WP4B on the integration of satellite solutions into 5G networks TSG RAN (RP-202862) CC#4: This LS was noted. Noted
4.7 SP-201126 REPORT Presentation Status Report of TSG RAN#90-e TSG RAN Chair OPEN
4.8 - - - TSG CT reporting (will be handled on Monday 14 December in separate call) - - Docs:=3 -
4.8 SP-201125 REPORT Presentation Status report of TSG CT#90-e TSG CT Chair OPEN
4.8 SP-201124 REPORT Information Draft report of TSG CT#90-e TSG CT Secretary (MCC) OPEN
4.8 SP-201123 REPORT Presentation IETF Status report TSG CT Chair OPEN
4.9 - - - Reports from external bodies (provided by Liaison persons) - - Docs:=0 -
4.10 - - - Other reports - - Docs:=0 -
5 - - - Cross TSG Coordination - - Docs:=0 -
5.1 - - - General Cross TSG Coordination - - Docs:=1 -
5.1 SP-201042 DISCUSSION Approval Inclusive Language in 3GPP Specifications TSG SA Chair, TSG RAN Chair, TSG CT Chair, SA WG1 Chair, SA WG2 Chair, SA WG3 Chair, SA WG4 Chair, SA WG5 Chair, SA WG6 Chair, RAN WG1 Chair, RAN WG2 Chair, RAN WG3 Chair, RAN WG4 Chair, RAN WG5 Chair, CT WG1 Chair, CT WG3 Chair, CT WG4 Chair, CT WG6 Chair Rel-17 CC#1: Endorsed Endorsed
5.2 - - - Rel-16 Focus Areas Status Reports & Issues - - Docs:=0 -
5.3 - - - Rel-17 Focus Areas Status Reports & Issues - - Docs:=0 -
5.4 - - - Input to Joint RAN/SA meeting - - Docs:=0 -
6 - - - Work Item Descriptions, Study Item Descriptions, Specifications - - Docs:=0 -
6.1 - - - New Release 16 and earlier Study Item Descriptions and Work Item Descriptions - - Docs:=3 -
6.1 SP-201019 WID NEW Approval New WID on Removal of AKMA from Rel-16 SA WG3 CC#2: This was left for further off-line discussion. CC#3: _Rev2 Approved. Revised to SP-201128. Revision request
SA3 chair provides a revision based on feedback from work plan coordinator
Revision request
SA3 chair provides an editorial revision		 Revised
6.1 SP-201128 WID NEW Approval New WID on Removal of AKMA from Rel-16 SA WG3 Revision of SP-201019_Rev2. This WID NEW was approved Approved
6.1 SP-201007 CR PACK Approval Rel-16 CRs on Removal of AKMA from Rel-16 SA WG3 Removed from Block approval. CC#4: This CR PACK was approved Approved
6.1 - - - Block Approval Block 4 (Thu 15:00 UTC) - - Docs:=0 -
6.2 - - - Revised Release 16 and earlier Study Item Descriptions and Work Item Descriptions - - Docs:=0 -
6.3 - - - New Release 17 Study Item Descriptions - - Docs:=8 -
6.3 SP-201021 SID NEW Approval Study on enhanced Security Aspects of the 5G Service Based Architecture SA WG3 Agreed in SA WG3 with an objections from Ericsson. CC#2: _Rev1 was approved. Revised to SP-201129. Revision request
SA3 chair provides a revision based on feedback from work plan coordinator		 Revised
6.3 SP-201129 SID NEW Approval Study on enhanced Security Aspects of the 5G Service Based Architecture SA WG3 Revision of SP-201021_Rev1. This SID NEW was approved Approved
6.3 SP-200937 SID NEW Approval 5G media streaming extensions SA WG4 Removed from Block approval. CC#3: Left for further discussion. CC#4: _Rev2 approved. Revised to SP-201130. Revised
6.3 SP-201130 SID NEW Approval 5G media streaming extensions SA WG4 Revision of SP-200937_Rev2. This SID NEW was approved Approved
6.3 SP-201018 SID NEW Approval Study on the security of the system enablers for devices having multiple Universal Subscriber Identity Modules (USIM) SA WG3 CC#2: This was left for further off-line discussion. CC#3: _Rev6 was approved. Revised to SP-201131. Revision request
SA3 chair provides a revision based on feedback from work plan coordinator
Saso (Intel) seeks clarification on the correct Unique ID.
Chris (Vodafone) seeks clarification on the SID's timeline and when SA2 feedback will be available.
Revision request
SA3 chair proposes to correct the stage 1 WI reference and the time scale.
Saso (Intel) comments on the 'For approval' date.
Chris (Vodafone) comments that the 'For approval' date for the SA3 SID may need to be March if SA2 is to complete their specs in June.
Revision request
SA3 chair reverts the change to the approval date (back to Mar 2021).
Saso (Intel) is OK with rev4.
Revision request
SA3 chair provides an editorial revision		 Revised
6.3 SP-201131 SID NEW Approval Study on the security of the system enablers for devices having multiple Universal Subscriber Identity Modules (USIM) SA WG3 Revision of SP-201018_Rev6. This SID NEW was approved Approved
6.3 - - - Block Approval Block 4 (Thu 15:00 UTC) - - Docs:=2 -
6.3 SP-201081 SID NEW Approval New SID on Charging Aspect of 5G LAN-type Services SA WG5 CC#3: Block approved Approved
6.3 SP-201082 SID NEW Approval New Study on Charging Aspects for Network Slicing Phase 2 SA WG5 CC#3: Block approved Approved
6.4 - - - New Release 17 Work Item Descriptions - - Docs:=24 -
6.4 SP-200972 WID NEW Approval New WID on System enhancement for Proximity based Services in 5GS. SA WG2 Proposed company revision in SP-201096. CC#4: This was considered as revised in SP-201096. Siemens seeks clarification on the missing rapporteur in this work item proposal. Revised
6.4 SP-201096 WID NEW Approval New WID on System enhancement for Proximity based Services in 5GS CATT, OPPO Proposed revision of SP-200972. CC#4: SP-201096_Rev4 approved. Revised to SP-201132. Ming(CATT) provides rev1 to address the comments from CC#2..
Hucheng(CATT) provides rev2 to address the comment during the CC#3.
LaeYoung (LGE) provides comments on rev2.
Jianhua replies to LaeYoung.
LaeYoung (LGE) replies to Jianhua (OPPO).
Jianhua(OPPO) provides rev3 to remove duplicated item 830033 in 2.3.
Nokia requests to add Nokia and Nokia Shanghai Bell as supporting companies for SA2 work item on Proximity based Services in 5GS.
Jianhua (OPPO) provide rev4 to add Nokia and Nokia Shanghai Bell as supporting companies.		 Revised
6.4 SP-201132 WID NEW Approval New WID on System enhancement for Proximity based Services in 5GS CATT, OPPO Revision of SP-201096_Rev4. This WID NEW was approved Approved
6.4 SP-201106 WID NEW Approval New WID: Architectural enhancements for 5G multicast-broadcast services Huawei, CBN Rel-17 Company revision of SA WG2 agreed WID in SP-200974. CC#2: This new WID was approved. Approved
6.4 SP-200974 WID NEW Approval New WID on Architectural enhancements for 5G multicast-broadcast services (5MBS). SA WG2 Proposed company revision in SP-201106. CC#2: This was considered as revised in SP-201106. Revised
6.4 SP-200975 WID NEW Approval Proposed New WID on Enablers for Network Automation for 5G - phase 2. SA WG2 Proposed company revision in SP-201099. CC#4: Considered revised in SP-201099. Revised
6.4 SP-201099 WID NEW Approval New WID on Enablers for Network Automation for 5G - phase 2 China Mobile Rel-17 Company revision of SA WG2 agreed WID in SP-200975. CC#2: This was left for further off-line discussion. CC#4: SP-201099_Rev3 approved. Revised to SP-201133. Tao (CMCC) provides rev1 to address the comments from CC#2..
LaeYoung (LGE) comments on rev1.
Tao(CMCC) thanks LaeYoung quick review and comments and provides rev2.		 Revised
6.4 SP-201133 WID NEW Approval New WID on Enablers for Network Automation for 5G - phase 2 China Mobile Rel-17 Revision of SP-201099_Rev3. This WID NEW was approved Approved
6.4 SP-200981 WID NEW Approval New WID on enhancement of support for Edge Computing in 5G Core network. SA WG2 Proposed company revision in SP-201107. CC#4: This was replaced by the company revision and was noted. Noted
6.4 SP-201107 WID NEW Approval New WID on enhancement of support for Edge Computing in 5G Core network. Huawei, AT&T, CATT, Charter Communications, China Telecom, China Unicom, Deutsche Telekom, Ericsson, Futurewei, Intel, Interdigital, KDDI, KPN, Telecom Italia, Telefonica, Telia Company, Tencent, Verizon, Vodafone, ZTE Rel-17 Revision of SP-200981. CC#2: This was left for further off-line discussion. CC#4: _Rev5 approved. Revised to SP-201134. Sherry (Xiaomi) requests to add Xiaomi as supporting company to eEDGE_5GC.
Susana (Vodafone) clarifies there is a rev1 provided by Huawei and further revisions of SP-201107 belong to this thread.
Huawei (Patrice) provided the rev 1 in the link indicated below.
Huawei (Patrice) clarifies to SA6 chair.
Huawei (Patrice) provides rev2 adding Xiaomi as supporting company.
Haris (Qualcomm) objects to rev.1 and rev2
Toyota (Lei) would like to be the supporting company for eEDGE_5GC.
LGE (Hyunsook) asks for clarification.
Nokia comments on rev2.		 Revised
6.4 SP-201134 WID NEW Approval New WID on enhancement of support for Edge Computing in 5G Core network. Huawei, AT&T, CATT, Charter Communications, China Telecom, China Unicom, Deutsche Telekom, Ericsson, Futurewei, Intel, Interdigital, KDDI, KPN, Qualcomm, Telecom Italia, Telefonica, Telia Company, Tencent, Toyota, Verizon, Vodafone, ZTE, Xiaomi Rel-17 Revision of SP-201107_Rev5. This WID NEW was approved Approved
6.4 SP-201020 WID NEW Approval New WID on Adapting BEST for use in 5G networks SA WG3 CC#2: This was left for further off-line discussion. CC#4: _Rev2 approved. Revised to SP-201135. Revision request
SA3 chair provides a revision based on feedback from work plan coordinator
Revision request
SA3 chair provides an editorial revision		 Revised
6.4 SP-201135 WID NEW Approval New WID on Adapting BEST for use in 5G networks SA WG3 Revision of SP-201020_Rev2. This WID NEW was approved Approved
6.4 SP-200973 WID NEW Approval New WID on Enhanced support of Industrial IoT. SA WG2 CC#3: This was removed from Block approval. CC#4: _Rev2 approved. Revised to SP-201136. Siemens asks for adding missing unique identifiers in clause 2.3 and suggests the inclusion of 840050 (eCAV) in the same clause.
Siemens asks for the revision of SP-200972_rev1 in order to reflect the changes proposed by Siemens on 2020-12-08 (missing unique identifiers and inclusion of 840050 [eCAV]).
Rainer (Nokia) provides rev2.
Siemens thanks Nokia for sharing rev2 of SP-200973. Siemens votes for the approval of this new WID.		 Revised
6.4 SP-201136 WID NEW Approval New WID on Enhanced support of Industrial IoT. SA WG2 Revision of SP-200973_Rev2. This WID NEW was approved Approved
6.4 - - - Block Approval Block 4 (Thu 15:00 UTC) - - Docs:=9 -
6.4 SP-200976 WID NEW Approval New WID: Enhancement of Network Slicing Phase 2. SA WG2 CC#3: Block Approved Approved
6.4 SP-200977 WID NEW Approval New WID on Access Traffic Steering, Switch and Splitting support in the 5G system architecture; Phase 2 . SA WG2 CC#3: Block Approved Approved
6.4 SP-200978 WID NEW Approval New WID on system enablers for Multi-USIM devices. SA WG2 CC#3: Block Approved Approved
6.4 SP-200979 WID NEW Approval New WID on Support of Aerial Systems Connectivity, Identification, and Tracking . SA WG2 CC#3: Block Approved Approved
6.4 SP-200980 WID NEW Approval New WID on enhanced support of Non-Public Networks. SA WG2 CC#3: Block Approved Approved
6.4 SP-200987 WID NEW Approval New WID Enhanced Service Enabler Architecture Layer for Verticals SA WG6 CC#3: Block Approved Approved
6.4 SP-200988 WID NEW Approval New WID application layer support for Unmanned Aerial System (UAS) SA WG6 CC#3: Block Approved Approved
6.4 SP-201017 WID REVISED Approval Authentication and key management for applications based on 3GPP credential in 5G SA WG3 Rel-17 CC#3: Block Approved Approved
6.4 SP-201080 WID NEW Approval New WID on Management Aspects of 5G Network Sharing SA WG5 CC#3: Block Approved Approved
6.5 - - - Revised Release 17 Study Item and Work Item Descriptions - - Docs:=9 -
6.5 SP-201032 WID REVISED Approval Revised WID: TEI17_DCAMP - Dynamically Changing AM Policies in the 5GC SA WG2 Removed from Block approval. CC#3: _Rev1 was approved. Revised to SP-201137. Biao(China Telecom) provides rev1 to capture the changes made by SP-200580 which had been approved at the TSG SA#88E meeting. Revised
6.5 SP-201137 WID REVISED Approval Revised WID: TEI17_DCAMP - Dynamically Changing AM Policies in the 5GC SA WG2 Revision of SP-201032_Rev1. This WID REVISED was approved Approved
6.5 SP-201015 SID REVISED Approval Study on security for enhanced support of Industrial IoT SA WG3 Rel-17 CC#3: This was removed from Block approval. CC#4: _Rev1 approved. Revised to SP-201138. Chris (Vodafone) comments that there are '?' in the supporting company list, leaving only 2 supporting companies. Also the TR dates seem wrong as no TR is presented here for approval.
SA3 chair provides clarifications and a way forward..
Chris (Vodafone) says thanks - revising like that would be OK.
Nokia provides rev1 modifying completion date to March 2021 and removing question marks for supporting companies.		 Revised
6.5 SP-201138 SID REVISED Approval Study on security for enhanced support of Industrial IoT SA WG3 Rel-17 Revision of SP-201015_Rev1. This SID REVISED was approved Approved
6.5 - - - Block Approval Block 4 (Thu 15:00 UTC) - - Docs:=5 -
6.5 SP-201030 SID REVISED Approval Revised SID: Feasibility Study on Enhancement of Network Slicing Phase 2. SA WG2 CC#3: Block Approved Approved
6.5 SP-201031 SID REVISED Approval Revised SID: Study on Access Traffic Steering, Switch and Splitting support in the 5G system architecture Phase 2. SA WG2 CC#3: Block Approved Approved
6.5 SP-201016 SID REVISED Approval Study on Security for NR Integrated Access and Backhaul SA WG3 Rel-16 CC#3: Block Approved Approved
6.5 SP-201079 SID REVISED Approval Revised Study on charging aspects of Proximity-based Services in 5GS SA WG5 Rel-17 CC#3: Block Approved Approved
6.5 SP-200986 SID REVISED Approval Revised SID Study on application layer support for UAS service SA WG6 Rel-17 CC#3: Block Approved Approved
6.6 - - - New Release 18 Study Item Descriptions - - Docs:=2 -
6.6 - - - Block Approval Block 4 (Thu 15:00 UTC) - - Docs:=2 -
6.6 SP-201038 SID NEW Approval New WID on Study on FRMCS Evolution (FS_eFRMCS) SA WG1 Rel-18 CC#3: Block Approved Approved
6.6 SP-201039 SID NEW Approval New SID on Study on supporting tactile and multi-modality communication services in 5GS (FS_TMMin5GS) SA WG1 Rel-18 CC#3: Block Approved Approved
6.7 - - - New Release 18 Work Item Descriptions - - Docs:=6 -
6.7 SP-201040 WID NEW Approval New (mini) WID on Support for Service Function Chaining in 5G Network (SFCin5G) SA WG1 Rel-18 Proposed company revision in SP-201109. CC#4: Considered revised in SP-201109. Revised
6.7 SP-201109 WID NEW Approval New (mini) WID on Support for Service Function Chaining in 5G Network (SFCin5G) Nokia, Nokia Shanghai Bell Rel-18 Proposed revision of SP-201040. CC#2: This was left for further off-line discussion. CC#3: This was left for further off-line discussion until CC#4. CC#4: _Rev6 approved. Revised to SP-201139. Alessio(Nokia) provides rev1 based on offline discussions.
Saso (Intel) comments on rev1.
Saso (Intel) provides a revision in DRAFTS.
Alessio(nokia) provides rev 2
Saso (Intel) comments on rev 2
Alessio(nokia) provides rev3
Saso (Intel) notes that Alessio(nokia) has disregarded Intel's comment
Alessio(nokia) provides rev 4
Saso (Intel) can live with rev4.
Alessio(nokia) provides rev 5 adding the Service Hosting Environment to clause 1 'Impacts'		 Revised
6.7 SP-201139 WID NEW Approval New (mini) WID on Support for Service Function Chaining in 5G Network (SFCin5G) Nokia, Nokia Shanghai Bell Rel-18 Revision of SP-201109_Rev6. This WID NEW was approved Approved
6.7 SP-201090 CR Approval 22.261 CR0478R2 (Rel-18, 'B'): Service requirements for enhancing service function chaining support by 5G network Nokia, Nokia Shanghai Bell Rel-18 Revision of 22.261 CR0478R1 in CR Pack SP-201041. CC#2: This was left for further off-line discussion. CC#4: _Rev12 approved. Revised to SP-201140. Alessio(Nokia) provides rev1 based on offline discussions.
Saso (Intel) comments on rev1.
Saso (Intel) provides a draft revision in the DRAFTS folder.
Saad (Interdigital) provides a comment.
Deutsche Telekom (Johannes) also supports the revision proposed by Intel. The editorials from TIM and Interdigital are also fine.
Saso (Intel) uploads draft revision v2 in the DRAFTS folder.
Orange (Xiaobao) asks to clarify the differences between 5G system and 5G network because both are used in the proposed texts. Orange (Xiaobao) suggests that 5G network should be replaced by 5G system in the proposed changes to avoid confusions.
Alessio (Nokia) comments that only Nokia is authorized to revise its document in 1090 (source Nokia) so Saso's revisions stand dismissed.
Deutsche Telekom (Johannes) objects to the revision of the SA1 CR in SP-201090 and also to rev1.
Alessio(nokia) cannot accept the principles in the linked document by SASO (which should also be removed from the repository by Maurice as it is not a revision uploaded by the source company.
Alessio(nokia) provides comments in response to Johannes, confirming the SA1 agree CR text is not acceptable and now it seems also immature given the clearly fast pace of change introduced by the original supporting companies at SA#90. In particular unstable charging requirement have been detected.
Saso (Intel) comments.
Saso (Intel) replies to Xiaobao.
Alessio(nokia) comments.
Krister (Ericsson) responds to Saso with some concerns on how Intel may interpret the SA1 use of the undefined term '5G network' and explains that 5G network is a broad term in SA1 that also includes what SA2 specifies outside of 5G System e.g. a N6-LAN.
Saso (Intel) replies to Alessio.
Susana (Vodafone) proposes some wording for the requirements and prefers to keep the definition as it is.
Saso (Intel) actually confirms the same understanding as Krister (Ericsson) about '5G network' being a broad term in SA1 that also includes what SA2 specifies as being outside of the 5G System.
Saso (Intel supports the additional change from Susana (Vodafone).
Yusuke (KDDI) supports Krister's comment that SA1 CR could be approved in SA.
Alessio(Nokia) responds to Krister
Alessio(nokia) provides rev2 in line with Vodafone comments.
Alessio(nokia) provides rev3 in line with Vodafone comments but fixing two typos in rev2.
Deutsche Telekom (Johannes) provides some comments to rev3 and ask for one change in chapter x.2 General Requirements, bullet 3, to be considered.
Saso (Intel) provides comments on rev3
Alessio(nokia) asks a question for clareification
Gerald (Matrixx) suggest a further revision on clause 9.1 in rev3 to cover the requirement for charging management
Xiaobao (Orange) questions the ambiguity of some of the proposed texts with '5G network'.
Susana (Vodafone) comments on suggestion from Matrixx
Alessio(nokia) proposes rev4 as the way forward, where an active form of verb and a subject is clearly specified and avoids any sort of architectural or confusing debates that SA1 in the first place should stay away from.
Saso (Intel) comments on rev4 and provides an update in DRAFTS.
Deutsche Telekom (Johannes) proposes alignment of wording of 'service function chaining'.
Alessio(nokia) cannot accept the concept SA1 starts doing functional allocation of features.
Deutsche Telekom (Johannes) asks for clarification on changes in chapter 9 'Charging Aspects'.
Alessio(Nokia) provides rev5 aligning terminology as requested by DT
Alessio(Nokia) provides r6 to allay the concern by DT on charging aspect text.
Saso (Intel) reiterates that the change of the Service Hosting Environment (SHE) definition is not acceptable. The current SHE definition states that SHE resides inside the 5G network. The term '5G network' is used in 80+ occurrences in 22.261. Any change of SHE (if needed) shall be left to SA1.
Alessio(nokia) comments that we can discuss whether to add this change or not in the confcall. I assume the rest is acceptable.
Deutsche Telekom (Johannes) ask for revision of chapter 9 on charging and changes in the definition section.
Alessio (nokia) provides comment
Alessio(nokia) provides rev7
Deutsche Telekom (Johannes) supports the rev7 and proposes 3 minor editorial changes
Ericsson (Krister) supports the rev7 with some small update and including the editorials from Johannes. Update provided in Draft folder.
Saso (Intel) proposes two changes on top of Ericsson's (Krister) in the DRAFTS folder.
Alessio(Nokia) provides r8 incorporating DT and Ericsson proposed changes and adding these two companies to the list of supporting companies
Alessio(nokia) provides rev9
Deutsche Telekom (Johannes) supports rev9 and the changes herein, but asks for editorial on the cover page of the CR
Alessio(nokia) thanks Johannes and provides rev10
Saso (Intel) points to more editorials.
Alessio(nokia) thanks Saso and provides rev11
Ericsson (Krister) confirms support of rev11.
Susana (Vodafone) supports rev11.
Deutsche Telekom (Johannes) thanks the contributors for their efforts, spirit of compromise and concise review. DT is happy to support rev11 and be listed as co-signing company.
 Revised
6.7 SP-201140 CR Approval 22.261 CR0478R3 (Rel-18, 'B'): Service requirements for enhancing service function chaining support by 5G network Nokia, Nokia Shanghai Bell, Deutsche Telekom, Ericsson, Intel, Sandvine, InterDigital, Convida wireless, Verizon UK Ltd, Matrixx, KPN, Vodafone, TIM Rel-18 Revision of SP-201090_Rev12. This CR was approved Approved
6.7 SP-201041 CR PACK Approval Stage 1 CRs on SFC in 5G SA WG1 Rel-18 Proposed revision of 22.261 CR0478R1 in SP-201090. CC#4: 22.261 CR0478R1 was considered as revised in SP-201090. Other CRs were approved. This was partially approved. Partially approved
6.8 - - - Revised Release 18 Study Item Descriptions and Work Item Descriptions - - Docs:=1 -
6.8 - - - Block Approval Block 4 (Thu 15:00 UTC) - - Docs:=1 -
6.8 SP-201037 SID REVISED Approval Revised SID on Study on Supporting of Railway Smart Station Services (FS_RAILSS) SA WG1 Rel-18 CC#3: Block Approved Approved
6.9 - - - Specifications for Information - - Docs:=11 -
6.9 - - - Block Approval Block 4 (Thu 15:00 UTC) - - Docs:=11 -
6.9 SP-200961 DRAFT TR Information Presentation of TR 23.776: 'Study on architecture enhancements for 3GPP support of advanced Vehicle-to-Everything (V2X) services; Phase 2' to TSG SA for information SA WG2 Rel-17 CC#3: Block Noted Noted
6.9 SP-200962 DRAFT TR Information Presentation of TR 23.752: 'Study on system enhancement for Proximity based Services (ProSe) in the 5G System (5GS)' to TSG SA for information SA WG2 Rel-17 CC#3: Block Noted Noted
6.9 SP-200963 DRAFT TR Information Presentation of TR 23.700-20: 'Study on enhanced support of Industrial Internet of Things (IIoT) in the 5G System (5GS)' to TSG SA for information SA WG2 Rel-17 CC#3: Block Noted Noted
6.9 SP-200964 DRAFT TR Information Presentation of TR 23.757: 'Study on architectural enhancements for 5G multicast-broadcast services' to TSG SA for information SA WG2 Rel-17 CC#3: Block Noted Noted
6.9 SP-200965 DRAFT TR Information Presentation of TR 23.700-40: 'Study on enhancement of network slicing; Phase 2' to TSG SA for information SA WG2 Rel-17 CC#3: Block Noted Noted
6.9 SP-200966 DRAFT TR Information Presentation of TR 23.700-93: 'Study on access traffic steering, switch and splitting support in the 5G System (5GS) architecture; Phase 2' to TSG SA for information SA WG2 Rel-17 CC#3: Block Noted Noted
6.9 SP-200967 DRAFT TR Information Presentation of TR 23.700-07: 'Study on enhanced support of Non-Public Networks (NPN)' to TSG SA for information SA WG2 Rel-17 CC#3: Block Noted Noted
6.9 SP-200968 DRAFT TR Information Presentation of TR 23.761: 'Study on system enablers for devices having multiple Universal Subscriber Identity Modules (USIM)' to TSG SA for information SA WG2 Rel-17 CC#3: Block Noted Noted
6.9 SP-200984 DRAFT TR Information Presentation of TR 23.783 v1.0.0 for information SA WG6 Rel-17 CC#3: Block Noted Noted
6.9 SP-200985 DRAFT TR Information Presentation of TR 23.755 v1.0.0 for information SA WG6 Rel-16 CC#3: Block Noted Noted
6.9 SP-201078 DRAFT TR Information TR 28.808 Study on management and orchestration aspects of integrated satellite components in a 5G network SA WG5 Rel-17 CC#3: Block Noted Noted
6.10 - - - Specifications for Approval / for Information and Approval - - Docs:=4 -
6.10 - - - Block Approval Block 4 (Thu 15:00 UTC) - - Docs:=4 -
6.10 SP-200969 DRAFT TR Approval Presentation of TR 23.754: 'Study on supporting Unmanned Aerial Systems (UAS) connectivity, Identification and tracking' to TSG SA for approval SA WG2 Rel-17 CC#3: Block Approved Approved
6.10 SP-200970 DRAFT TR Approval Presentation of TR 23.748: 'Study on enhancement of support for Edge Computing in 5G Core network (5GC)' to TSG SA for approval SA WG2 Rel-17 CC#3: Block Approved vivo identifies that the coversheet SP-200970 has the wrong Work item on it. Not sure if a revision is needed as it's a minor typographic error. Approved
6.10 SP-200971 DRAFT TR Approval Presentation of TR 23.700-91: 'Study on enablers for network automation for the 5G System (5GS); Phase 2' to TSG SA for approval SA WG2 Rel-17 CC#3: Block Approved Approved
6.10 SP-201077 DRAFT TR Approval TR 28.807 Study on management aspects of non-public networks SA WG5 Rel-17 CC#3: Block Approved Approved
7 - - - Release Planning - - Docs:=0 -
7.1 - - - General Release Planning issues - - Docs:=0 -
7.2 - - - Issues related to Release 16 and earlier planning (nothing expected here) - - Docs:=0 -
7.3 - - - Release 17 Planning (schedule, prioritization, etc.) - - Docs:=2 -
7.3 SP-200923 DISCUSSION Approval Release 17 Timeline TSG SA Chair, TSG CT Chair, TSG RAN Chair Rel-17 CC#1: This was endorsed. Endorsed
7.3 SP-201094 DISCUSSION Presentation Support for Public Safety Needs in Release 17 FirstNet, AT&T ,NTIA , UK Home Office, MINISTERE DE L'INTERIEUR FRANÇAIS, SyncTechno Inc., Suomen Erillisverkot Oy, A.S.T.R.I.D. S.A., Norwegian Communications Authority, Softil. Rel-17 CC#1: Noted Note that the following companies expressed their support offline for this contribution: The Netherlands Police, BMWi, and Orange. Noted
7.4 - - - Release 18 Planning (schedule, prioritization, etc.) - - Docs:=2 -
7.4 SP-201024 DISCUSSION Information SA WG1 chair's view on Rel-18 Timeline and SIDs SA WG1 Chair CC#1: The '2nd scenario timeline on slide 5: Rel-17 + 6' was endorsed. Endorsed e-mail from the SA WG1 Chair on the handling of Rel 18/Rel 19 in SA WG1 from Q1/2021. This was then noted. With thanks to Jose (SA1 chairperson)for his effort, Ki-Dong (LG) provides two points for consideration in regard to 'closing Rel-18 stage-1 study' as per SA Chairperson's note for CC#1 but supports the idea proposed by Jose due to some practical reasons.
(1) 3GPP work is completely on a contribution basis
(2) It is not predictable whether all ongoing Study Items should/will/can be moved onto their normative phase, which means the workload in the respective following quarters is not predictable.
However, from the perspective of SA1 operation in reality, LG shares the view about the pain and implications that SA1 chairperson has shared, and agrees that it is important for SA1 to set up an easy and reasonable means to a manageable level of workload in Rel-18. LG supports the idea that SA1 should set up some mechanism (i.e., proposed in 1024) that can help healthy operations for both quality Rel-18 stage-1 progress and outcomes.		 Noted
7.4 SP-201097 WID NEW Discussion Inputs to the Release 18 Prioritization Reliance Jio Rel-18 CC#1: This was not available and was withdrawn Withdrawn
8 - - - Rel-8 CRs - - Docs:=0 -
9 - - - Rel-9 CRs - - Docs:=0 -
10 - - - Rel-10 CRs - - Docs:=0 -
11 - - - Rel-11 CRs - - Docs:=1 -
11 - - - Block Approval Block 5 (Thu 15:00 UTC) - - Docs:=1 -
11 SP-201048 CR PACK Approval Rel-11 CRs on TEI SA WG5 CC#3: Block Approved Approved
12 - - - Rel-12 CRs - - Docs:=0 -
13 - - - Rel-13 CRs - - Docs:=0 -
14 - - - Rel-14 CRs - - Docs:=0 -
15 - - - Rel-15 CRs - - Docs:=9 -
15 SP-201100 CR Approval 23.502 CR2439R2 (Rel-16, 'A'): Removal of SMSF registration notification flag NTT DOCOMO, Nokia, Nokia Shanghai Bell, Huawei Rel-16 Proposed revision of 23.502 CR2439R1 in CR Pack SP-200945. CC#1: This CR was approved. Approved
15 SP-200945 CR PACK Approval CRs to 23.501, 23.502 (5GS_Ph1, Rel-15, Rel-16) SA WG2 Proposed revision of 23.502 CR2439R1 in SP-201100. CC#1: 23.502 CR2439R1 was considered revised and the other CRs in this CR pack were approved. This CR Pack was partially approved. Partially approved
15 - - - Block Approval Block 5 (Thu 15:00 UTC) - - Docs:=7 -
15 SP-200939 CR PACK Approval Rel-15 CRs on Lawful Interception SA WG3-LI Rel-15 CC#3: Block Approved Approved
15 SP-201012 CR PACK Approval Rel-15 CRs on Security aspects of 5G System - Phase 1 SA WG3 CC#3: Block Approved Approved
15 SP-201049 CR PACK Approval Rel-15 CRs on TEI SA WG5 CC#3: Block Approved Approved
15 SP-201059 CR PACK Approval Rel-15 CRs on Performance Assurance for 5G networks including network slicing SA WG5 CC#3: Block Approved Approved
15 SP-201064 CR PACK Approval Rel-15 CRs on Network Resource Model (NRM) for 5G networks and network slicing SA WG5 CC#3: Block Approved Approved
15 SP-201071 CR PACK Approval Rel-15 CRs on Service Based Interface for 5G Charging SA WG5 CC#3: Block Approved Approved
15 SP-201072 CR PACK Approval Rel-15 CRs on SMS Charging in 5G System Architecture Phase 1 SA WG5 CC#3: Block Approved Approved
16 - - - Rel-16 CRs - - Docs:=0 -
16.1 - - - SA WG1 Rel-16 CRs - - Docs:=0 -
16.2 - - - SA WG2 Rel-16 CRs - - Docs:=20 -
16.2 SP-200960 CR PACK Approval CR to 23.502 (TEI16, Rel-16) SA WG2 Proposed replacement of 23.502 CR2453 in SP-201091. CC#3: This CR Pack was considered revised into the CR in SP-201091. Revised
16.2 SP-201091 CR Approval 23.502 CR2453R1 (Rel-16, 'F'): QoS parameter handling for PDU session transfer between 3GPP and non-3GPP access Nokia, Nokia Shanghai Bell, Apple, Huawei, HiSilicon, Rel-16 Proposed replacement of 23.502 CR2453 in SP-200960. CC#1: Left open for further checking (Ericsson). CC#2: _Rev1 was approved. Revised to SP-201141. Revised
16.2 SP-201141 CR Approval 23.502 CR2453R2 (Rel-16, 'F'): QoS parameter handling for PDU session transfer between 3GPP and non-3GPP access Nokia, Nokia Shanghai Bell, Apple, Huawei, HiSilicon, Broadcom, Ericsson Rel-16 Revision of SP-201091_Rev1. This CR was approved Approved
16.2 SP-201105 DISCUSSION Decision Discussion on URLLC QoS Monitoring Huawei, HiSilicon, China Mobile, China Unicom, China Telecom, Lenovo, Motorola Mobility Rel-16 Proposes returning a CR from SP-200952 to SA WG2. CC#1: Noted Noted
16.2 SP-200952 CR PACK Approval CR to 23.502 (5G_URLLC, Rel-16) SA WG2 SP-201105 proposes returning TS 23.502 CR2413R1 to SA WG2. CC#1: Removed from e-mail approval. CC#2: This was left for further off-line discussion. CC#2: CC#3: This was left for further off-line discussion. CC#4: Postponed Ericsson (Shabnam) provides r01 as per CC#2 discussion and aligned with RAN approved CR.
Wanqiang (Huawei) comments and the rev1 is not acceptable.
Biao (China Telecom) comments and support huawei's view.
Shabnam (Ericsson) asks how is it useful/make sense in a frozen release to keep text that is clearly not understood and is not taken on board in RAN? We believe at this point the best approach is to align the specs and any additional discussion to be handled separately.
Shabnam (Ericsson) provides rev2 following CC#3 discussion/proposal.
Wanqiang (Huawei) provides rev3.
Chi (China Unicom) comments on rev02.		 Postponed
16.2 SP-201108 DISCUSSION Decision Discussion on Redirection for EPS Fallback correction Huawei, HiSilicon Rel-16 Proposes returning a CR from SP-200946 to SA WG2. CC#1: This was left for off-line discussion. This contribution was then noted Noted
16.2 SP-200946 CR PACK Approval CRs, which received objections in SA WG2, to 23.501, 23.502 (eNS, TEI16, Rel-16) SA WG2 Objections were received at SA WG2 on the CRs in this CR Pack. CC#4: 23.502 CR2450R1 was considered revised and the remaining CRs in this CR Pack were approved. This CR Pack was partially approved. (23.502 CR2450R1 was revised in SP-201127) Fenqin (Huawei) provides rev1.
Rainer (Nokia) provides rev2.
LaeYoung (LGE) is fine with rev2 and asks whether ticking the RAN box is needed in the coversheet.
Fenqin (Huawei) agree that RAN box need be ticked.
Rainer (Nokia) provides rev3.		 Partially approved
16.2 SP-201127 CR Approval 23.502 CR2450R2 (Rel-16, 'F'): Fixing Redirection for EPS Fallback indication Nokia, Nokia Shanghai Bell, Verizon, Samsung, Ericsson, T-Mobile USA, AT&T Rel-16 Revision of 23.502 CR 2450R1 (S2-2007918) in CR Pack SP-200946 (SP-200946_Rev4). This CR was approved Approved
16.2 - - - Block Approval Block 5 (Thu 15:00 UTC) - - Docs:=12 -
16.2 SP-200947 CR PACK Approval CRs to 23.501, 23.502 (5G_CIoT, Rel-16) SA WG2 CC#3: Block Approved Approved
16.2 SP-200948 CR PACK Approval CRs to 23.273 (5G_eLCS, Rel-16) SA WG2 CC#3: Block Approved Approved
16.2 SP-200949 CR PACK Approval CRs to 23.501 (5G_eSBA, Rel-16) SA WG2 CC#3: Block Approved Approved
16.2 SP-200950 CR PACK Approval CRs to 23.287, 23.501, 23.503 (eV2XARC, Rel-16) SA WG2 CC#3: Block Approved Approved
16.2 SP-200951 CR PACK Approval CRs to 23.501, 23.502, 23.503 (5G_URLLC, Rel-16) SA WG2 CC#3: Block Approved Approved
16.2 SP-200953 CR PACK Approval CRs to 23.501, 23.502, 23.503 (Vertical_LAN, Rel-16) SA WG2 CC#3: Block Approved Approved
16.2 SP-200954 CR PACK Approval CRs to 23.306, 23.501, 23.502, 23.503 (5WWC, Rel-16) SA WG2 CC#3: Block Approved Approved
16.2 SP-200955 CR PACK Approval CR to 23.503 (ATSSS, Rel-16) SA WG2 CC#3: Block Approved Approved
16.2 SP-200956 CR PACK Approval CR to 23.228 (eIMS5G_SBA, Rel-16) SA WG2 CC#3: Block Approved Approved
16.2 SP-200957 CR PACK Approval CRs to 23.228, 23.502 (eNA, Rel-16) SA WG2 CC#3: Block Approved Approved
16.2 SP-200958 CR PACK Approval CRs to 23.501, 23.502 (eNS, Rel-16) SA WG2 CC#3: Block Approved Approved
16.2 SP-200959 CR PACK Approval CRs to 23.167, 23.228, 23.401, 23.501, 23.502, 23.503 (TEI16, Rel-16) SA WG2 CC#3: Block Approved Approved
16.3 - - - SA WG3 and SA WG3 LI Rel-16 CRs - - Docs:=11 -
16.3 SP-201093 CR Approval 33.501 CR0960R2 (Rel-16, 'F'): Error correction and clarification of Annex O CableLabs Rel-16 Revision of S3-203507 (not pursued at SA3#101-e). Confirm CR Revision - CR states 0! Revised to SP-201115. Revised
16.3 SP-201115 CR Approval 33.501 CR0960R3 (Rel-16, 'F'): Error correction and clarification of Annex O CableLabs Rel-16 Revision of SP-201093. CC#2: This was left for further off-line discussion. CC#3: This CR was approved Approved
16.3 - - - Block Approval Block 5 (Thu 15:00 UTC) - - Docs:=9 -
16.3 SP-200940 CR PACK Approval Rel-16 CRs on Lawful Interception SA WG3-LI Rel-16 CC#3: Block Approved Nokia requests clarification regarding which CR is withdrawn from CR Pack in SP-200940. Currently Chair's notes say it is CR0136R1, but CR Pack does not contain CR0136R1, it has CR0136R4.
SA3-LI Chair confirms that this is an admin error in the Agenda. The CR pack is actually correct and contains the correct approved CRs. The R1 CR referred to in the Agenda is one that was marked incorrectly as agreed by SA3-LI in 3GU. However, that version didn't go through the SA3 approval process (as it was replaced by R4) nor is it in the CR pack. So both the 136R4 and other CRs are correct. As such the CR pack should simply be left in the block approval, or manually approved as on the agenda, with the Agenda comment ignored.		 Approved
16.3 SP-201004 CR PACK Approval Rel-16 CRs on Security Assurance Specification for 5G SA WG3 CC#3: Block Approved Approved
16.3 SP-201005 CR PACK Approval Rel-16 CRs on Mission Critical Services Security Enhancements SA WG3 CC#3: Block Approved Approved
16.3 SP-201006 CR PACK Approval Rel-16 CRs on Authentication and key management for applications based on 3GPP credential in 5G SA WG3 CC#3: Block Approved Approved
16.3 SP-201009 CR PACK Approval Rel-16 CRs on TEI SA WG3 CC#3: Block Approved Approved
16.3 SP-201010 CR PACK Approval Rel-16 CRs on 3GPP profiles for cryptographic algorithms and security protocols SA WG3 CC#3: Block Approved Approved
16.3 SP-201011 CR PACK Approval Rel-16 CRs on Security for 5G_eSBA SA WG3 CC#3: Block Approved Approved
16.3 SP-201013 CR PACK Approval Rel-16 CRs on Security aspects of Enhanced Network Slicing SA WG3 CC#3: Block Approved Approved
16.3 SP-201014 CR PACK Approval Rel-16 CRs on Security Aspects of eV2XARC SA WG3 CC#3: Block Approved Approved
16.4 - - - SA WG4 Rel-16 CRs - - Docs:=7 -
16.4 - - - Block Approval Block 5 (Thu 15:00 UTC) - - Docs:=7 -
16.4 SP-200930 CR PACK Approval CR Pack for 26.501 SA WG4 CC#3: Block Approved Approved
16.4 SP-200931 CR PACK Approval CR Pack for 26.114 SA WG4 CC#3: Block Approved Approved
16.4 SP-200932 CR PACK Approval CR Pack for 26.118 SA WG4 CC#3: Block Approved Approved
16.4 SP-200933 CR PACK Approval CR Pack for 26.234 SA WG4 CC#3: Block Approved Approved
16.4 SP-200934 CR PACK Approval CR Pack for 26.346 SA WG4 CC#3: Block Approved Approved
16.4 SP-200935 CR PACK Approval CR Pack for 26.512 SA WG4 CC#3: Block Approved Approved
16.4 SP-200936 CR PACK Approval CR Pack for 26.928 SA WG4 CC#3: Block Approved Approved
16.5 - - - SA WG5 Rel-16 CRs - - Docs:=19 -
16.5 SP-201044 CR PACK Approval Rel-16 CRs on Network Slice Management Charging in 5G System SA WG5 CC#4: 32.291 CR0283R1 was postponed. The other CRs in this CR pack were approved Lionel (CT Chair) has raised an issue with S5-205449 in CR Pack SA-201044
Thomas (SA5 Chair) wishes to provide the following reply to the CT chair's comment on an issue with S5-205449 in CR Pack SA-201044:
For Charging, it was considered acceptable to live with this misalignment with 29.501 during a temporary period as long as specs validations can pass correctly, and further work on a more futureproof method for 32.291 OpenAPIs which cross-references CT datatypes and OAM datatypes is needed.
Gerald (Matrixx) wondering about the concern about the SA5 Forge initiate on the common data repository for Management, Orchestration and Charging architecture framework.		 Partially approved
16.5 SP-201056 CR PACK Approval Rel-16 CRs on Closed loop SLS Assurance SA WG5 CC#4: 28.536 CR0010R2 and 28.535 CR0013R1 were withdrawn. The other CRs in this CR pack were approved Samsung kindly requests that Cat-F CRs (corrections and clarifications only) discipline be observed in future for Closed loop SLS Assurance (COSLA) a Rel-16 work item.
Firstly, the SA5 chair thanks Samsung for the comment on some CRs in this CR pack. I will bring back this request to SA5 to carefully consider it for future CRs.
Secondly, I can report that issues have been found by MCC with two CRs in this CR pack SP-201056, being in conflict with two other CRs. 28.536 CR0010R2 and 28.535 CR0013R1 should therefore be withdrawn.		 Partially approved
16.5 - - - Block Approval Block 5 (Thu 15:00 UTC) - - Docs:=17 -
16.5 SP-201043 CR PACK Approval Rel-16 CRs on Network Slice Performance and Analytics Charging in 5G System SA WG5 CC#3: Block Approved Approved
16.5 SP-201045 CR PACK Approval Rel-16 CRs on Self-Organizing Networks (SON) for 5G networks SA WG5 CC#3: Block Approved Approved
16.5 SP-201047 CR PACK Approval Rel-16 CRs on Energy efficiency of 5G SA WG5 CC#3: Block Approved Approved
16.5 SP-201050 CR PACK Approval Rel-16 CRs on TEI Batch 1 SA WG5 CC#3: Block Approved Approved
16.5 SP-201051 CR PACK Approval Rel-16 CRs on TEI Batch 2 SA WG5 CC#3: Block Approved Approved
16.5 SP-201053 CR PACK Approval Rel-16 CRs on Management Aspects of 5G Service-Level Agreement SA WG5 CC#3: Block Approved Approved
16.5 SP-201054 CR PACK Approval Rel-16 CRs on Enhancement of performance assurance for 5G networks including network slicing SA WG5 CC#3: Block Approved Approved
16.5 SP-201055 CR PACK Approval Rel-16 CRs on Integration of ONAP and 3GPP 5G management framework SA WG5 CC#3: Block Approved Approved
16.5 SP-201057 CR PACK Approval Rel-16 CRs on NRM enhancements SA WG5 CC#3: Block Approved Approved
16.5 SP-201061 CR PACK Approval Rel-16 CRs on KPI reporting SA WG5 CC#3: Block Approved Approved
16.5 SP-201063 CR PACK Approval Rel-16 CRs on Management of MDT in 5G SA WG5 CC#3: Block Approved Approved
16.5 SP-201069 CR PACK Approval Rel-16 CRs on CHF-controlled quota management SA WG5 CC#3: Block Approved Approved
16.5 SP-201073 CR PACK Approval Rel-16 CRs on Charging Aspect for 5WWC SA WG5 CC#3: Block Approved Approved
16.5 SP-201074 CR PACK Approval Rel-16 CRs on Streaming trace reporting SA WG5 CC#3: Block Approved Approved
16.5 SP-201076 CR PACK Approval Rel-16 CRs on Charging aspects of ETSUN SA WG5 CC#3: Block Approved Approved
16.5 SP-201088 CR PACK Approval Rel-16 CRs on TEI Batch 3 SA WG5 CC#3: Block Approved Approved
16.5 SP-201089 CR PACK Approval Rel-16 CRs on NRM enhancements Batch 2 SA WG5 CC#3: Block Approved Approved
16.6 - - - SA WG6 Rel-16 CRs - - Docs:=4 -
16.6 - - - Block Approval Block 5 (Thu 15:00 UTC) - - Docs:=4 -
16.6 SP-200989 CR PACK Approval Rel-16 CRs to TS23282 for eMCData2 SA WG6 CC#3: Block Approved Approved
16.6 SP-200990 CR PACK Approval Rel-16 CRs to TS23281 for MONASTERY2 SA WG6 CC#3: Block Approved Approved
16.6 SP-200991 CR PACK Approval Rel-16 CRs to TS23434 for SEAL SA WG6 CC#3: Block Approved Approved
16.6 SP-200992 CR PACK Approval Rel-16 CRs to TS23286 for V2XAPP SA WG6 CC#3: Block Approved Approved
17 - - - Rel-17 CRs - - Docs:=0 -
17.1 - - - SA WG1 Rel-17 CRs - - Docs:=11 -
17.1 SP-200926 DISCUSSION Information Report from moderated e-mail discussion on (SA WG1) requirements enumeration TSG SA Chair CC#3: Noted Nokia requests clarification on the proposal to cross-reference enumerated SA1 requirements in the objectives of affected stage 2 WIDs.
Siemens corrects the subject line for this email thread and responds to four of Ericsson's statements.
Siemens addresses Nokia's question concerning the proposal to cross-reference enumerated SA1 requirements in the objectives of affected stage-2 WIDs.
Haris (Qualcomm) comments
Philips supports enumerating the requirements and provides additional feedback.
Siemens replies to Qualcomm
Gerald (Matrixx) with further comments and suggestion.
Huawei considers that this is a minor effort that could be helpful in bringing more relevant expertise to stage 2 and stage 3 groups, and is therefore worthwhile to invest in.
vivo considers that companies should be allowed to bring in tdocs to try and enumerate requirements in SA1.
Ericsson disagrees with point made by Huawei and objects to the proposal of introducing this new enumeration work process in 3GPP. As a consequence also objects starting to introduce and maintain requirement numbers in SA1 TSes up for approval in CRs in this meeting.
LG agrees with vivo's view in bullet points 'a' and 'b'.
LG disagrees the point that Huawei shared and provides reply comments. LG shares the view that it is for 'some' specifications that it would be helpful to have/keep requirement numbering but LG does not see any good justification because it has already been done on an as-needed basis so far. LG agrees that it is important to make a good interface with industry verticals but does not agree that those remedies that were put on table will become a helpful solution at all. LG would like to support some idea, in part, stated in SP-201101 ('Enumeration of TS 22.104 and TS 22.261: a bird's eye perspective'), specifically about the 'verticals' related specification. However, LG wants to clarify the view that SP-201102 (Rel-17 CR against 22.261) and SP-201103 (Rel-18 CR against 22.261) are attempting to claim something beyond what the authors of SP-201101 have tried to justify. This is because 22.261 is a comprehensive specification, not only covering verticals-related requirements but also covering a general set of requirements (refer to the WID of SMARTER, SID of FS_SMARTER and its four BBs). Therefore, although LG can agree to some change components made to vertical related clauses, LG disagrees to some of the change components that were proposed to (mostly/nearly) all clauses. Specifically for 22.261, instead, LG proposes that only those clauses related to verticals industry (e.g., directly affected by WI code of cyberCAV, eCAV, VIAPA, if necessary/agreeable) should be selectively taken care of by the CRs (R17, R18).
Peretz (Spirent) comments
Siemens replies to Spirent and Qualcomm
Siemens uploaded revisions to SP-201102, SP-201103, and SP-201104. These revisions correct slips identified in the chair's notes.
Siemens uploaded a revision of SP-201101.
Ericsson comments on 5G-ACIA activity on following up requirements from SA1 eCAV
Walter (Philips) provides additional reason for requirements enumeration
Deutsche Telekom (Johannes) comments on requirements enumeration
Siemens replies to Ericsson and agrees with Ericsson that requirements enumeration can be also useful for entities outside 3GPP. However, it was stated earlier on in the pertinent SA email discussion, that this has no impact on whether 3GPP should or should not endorse the enumeration proposals brought to SA#89-e. Furthermore, how enumerated requirements are used at 5G-ACIA differs fundamentally from the intended use at 3GPP.
Siemens replies to Spirent.
Futurewei (Tony) comments on requirements enumeration.
Siemens is okay with Futurewei's proposal and enquires if others also would like to see the proposed change.
Ericsson (Krister) comments on Futurewei suggestion.
Siemens uploaded rev2 of SP-201102, SP-201103, and SP-201104. These revisions implement Futurewei's proposed change to the 'Consequences if not approved' field.
Nokia requests further revision to remove reference to SP-201101 and SP-200926 from the CRs' coversheet.
Ericsson (Krister) comment that we should not introduce negative impacts to 3GPP way of working as proposed, but rather work with other ways to support smaller companies in interest organizations providing those smaller companies with what they need. 3GPP may also provide complements to existing search tools, work plan etc which is providing a support to allow smaller companies to follow where features and work progress.
Siemens agrees with Nokia that the indicated reference to SP-200926 needs to be deleted and has done so in the uploaded rev3 of SP-201102 and SP-201104. Since rev1 of SP-201101 does not contain any reference to down-stream groups anymore, the reference to this document does not need to be removed from the CR cover sheets.
Nokia asks again to remove reference to SP-201101 from the CRs' coversheet, or to put new number for the revision of SP-201101.
Gerald (Matrixx) will object except with a clear commitment to not require the implementation of the enumeration scheme in other WGs technical specifications.		 Noted
17.1 SP-201101 DISCUSSION Endorsement Enumeration of TS 22.104 and TS 22.261: a bird's eye perspective Siemens, Daimler, Volkswagen AG, Novamint, BMWi, Philips, Sennheiser, ETRI, EBU, Bosch Rel-17 CC#3: Endorsed. CC#4: Postponed Nokia requests clarification on the proposal to cross-reference enumerated SA1 requirements in the objectives of affected stage 2 WIDs.
Siemens corrects the subject line for this email thread and responds to four of Ericsson's statements.
Siemens addresses Nokia's question concerning the proposal to cross-reference enumerated SA1 requirements in the objectives of affected stage-2 WIDs.
Haris (Qualcomm) comments
Philips supports enumerating the requirements and provides additional feedback.
Siemens replies to Qualcomm
Gerald (Matrixx) with further comments and suggestion.
Huawei considers that this is a minor effort that could be helpful in bringing more relevant expertise to stage 2 and stage 3 groups, and is therefore worthwhile to invest in.
vivo considers that companies should be allowed to bring in tdocs to try and enumerate requirements in SA1.
Ericsson disagrees with point made by Huawei and objects to the proposal of introducing this new enumeration work process in 3GPP. As a consequence also objects starting to introduce and maintain requirement numbers in SA1 TSes up for approval in CRs in this meeting.
LG agrees with vivo's view in bullet points 'a' and 'b'.
LG disagrees the point that Huawei shared and provides reply comments. LG shares the view that it is for 'some' specifications that it would be helpful to have/keep requirement numbering but LG does not see any good justification because it has already been done on an as-needed basis so far. LG agrees that it is important to make a good interface with industry verticals but does not agree that those remedies that were put on table will become a helpful solution at all. LG would like to support some idea, in part, stated in SP-201101 ('Enumeration of TS 22.104 and TS 22.261: a bird's eye perspective'), specifically about the 'verticals' related specification. However, LG wants to clarify the view that SP-201102 (Rel-17 CR against 22.261) and SP-201103 (Rel-18 CR against 22.261) are attempting to claim something beyond what the authors of SP-201101 have tried to justify. This is because 22.261 is a comprehensive specification, not only covering verticals-related requirements but also covering a general set of requirements (refer to the WID of SMARTER, SID of FS_SMARTER and its four BBs). Therefore, although LG can agree to some change components made to vertical related clauses, LG disagrees to some of the change components that were proposed to (mostly/nearly) all clauses. Specifically for 22.261, instead, LG proposes that only those clauses related to verticals industry (e.g., directly affected by WI code of cyberCAV, eCAV, VIAPA, if necessary/agreeable) should be selectively taken care of by the CRs (R17, R18).
Peretz (Spirent) comments
Siemens replies to Spirent and Qualcomm
Siemens uploaded revisions to SP-201102, SP-201103, and SP-201104. These revisions correct slips identified in the chair's notes.
Siemens uploaded a revision of SP-201101.
Ericsson comments on 5G-ACIA activity on following up requirements from SA1 eCAV
Walter (Philips) provides additional reason for requirements enumeration
Deutsche Telekom (Johannes) comments on requirements enumeration
Siemens replies to Ericsson and agrees with Ericsson that requirements enumeration can be also useful for entities outside 3GPP. However, it was stated earlier on in the pertinent SA email discussion, that this has no impact on whether 3GPP should or should not endorse the enumeration proposals brought to SA#89-e. Furthermore, how enumerated requirements are used at 5G-ACIA differs fundamentally from the intended use at 3GPP.
Siemens replies to Spirent.
Futurewei (Tony) comments on requirements enumeration.
Siemens is okay with Futurewei's proposal and enquires if others also would like to see the proposed change.
Ericsson (Krister) comments on Futurewei suggestion.
Siemens uploaded rev2 of SP-201102, SP-201103, and SP-201104. These revisions implement Futurewei's proposed change to the 'Consequences if not approved' field.
Nokia requests further revision to remove reference to SP-201101 and SP-200926 from the CRs' coversheet.
Ericsson (Krister) comment that we should not introduce negative impacts to 3GPP way of working as proposed, but rather work with other ways to support smaller companies in interest organizations providing those smaller companies with what they need. 3GPP may also provide complements to existing search tools, work plan etc which is providing a support to allow smaller companies to follow where features and work progress.
Siemens agrees with Nokia that the indicated reference to SP-200926 needs to be deleted and has done so in the uploaded rev3 of SP-201102 and SP-201104. Since rev1 of SP-201101 does not contain any reference to down-stream groups anymore, the reference to this document does not need to be removed from the CR cover sheets.
Nokia asks again to remove reference to SP-201101 from the CRs' coversheet, or to put new number for the revision of SP-201101.
Siemens clarifies that the phrase 'supporting verticals' refers to the vertical 3GPP members that, besides Siemens, co-sourced SP-201101, SP-201102, SP-201103, and SP-201104, namely Bosch, Daimler, EBU, Novamint, Phillips, Sennheiser, and Volkswagen AG.
Gerald (Matrixx) will object except with a clear commitment to not require the implementation of the enumeration scheme in other WGs technical specifications.		 Postponed
17.1 SP-201102 CR Approval 22.261 CR0493 (Rel-17, 'D'): Quality improvement - enumeration of requirements in TS 22.261 (R17; this CR does not introduce any technical change) Siemens, Daimler, Volkswagen AG, Novamint, BMWi, Philips, Sennheiser, ETRI, EBU, Bosch Rel-17 Should have been reserved as a revision of 22.261 0465R1, not a new CR. CR states 'TS 22.261' instead of '22.261'. CC#4: Postponed Nokia requests clarification on the proposal to cross-reference enumerated SA1 requirements in the objectives of affected stage 2 WIDs.
Siemens corrects the subject line for this email thread and responds to four of Ericsson's statements.
Siemens addresses Nokia's question concerning the proposal to cross-reference enumerated SA1 requirements in the objectives of affected stage-2 WIDs.
Haris (Qualcomm) comments
Philips supports enumerating the requirements and provides additional feedback.
Siemens replies to Qualcomm
Gerald (Matrixx) with further comments and suggestion.
Huawei considers that this is a minor effort that could be helpful in bringing more relevant expertise to stage 2 and stage 3 groups, and is therefore worthwhile to invest in.
vivo considers that companies should be allowed to bring in tdocs to try and enumerate requirements in SA1.
Ericsson disagrees with point made by Huawei and objects to the proposal of introducing this new enumeration work process in 3GPP. As a consequence also objects starting to introduce and maintain requirement numbers in SA1 TSes up for approval in CRs in this meeting.
LG agrees with vivo's view in bullet points 'a' and 'b'.
LG disagrees the point that Huawei shared and provides reply comments. LG shares the view that it is for 'some' specifications that it would be helpful to have/keep requirement numbering but LG does not see any good justification because it has already been done on an as-needed basis so far. LG agrees that it is important to make a good interface with industry verticals but does not agree that those remedies that were put on table will become a helpful solution at all. LG would like to support some idea, in part, stated in SP-201101 ('Enumeration of TS 22.104 and TS 22.261: a bird's eye perspective'), specifically about the 'verticals' related specification. However, LG wants to clarify the view that SP-201102 (Rel-17 CR against 22.261) and SP-201103 (Rel-18 CR against 22.261) are attempting to claim something beyond what the authors of SP-201101 have tried to justify. This is because 22.261 is a comprehensive specification, not only covering verticals-related requirements but also covering a general set of requirements (refer to the WID of SMARTER, SID of FS_SMARTER and its four BBs). Therefore, although LG can agree to some change components made to vertical related clauses, LG disagrees to some of the change components that were proposed to (mostly/nearly) all clauses. Specifically for 22.261, instead, LG proposes that only those clauses related to verticals industry (e.g., directly affected by WI code of cyberCAV, eCAV, VIAPA, if necessary/agreeable) should be selectively taken care of by the CRs (R17, R18).
Peretz (Spirent) comments
Siemens replies to Spirent and Qualcomm
Siemens uploaded revisions to SP-201102, SP-201103, and SP-201104. These revisions correct slips identified in the chair's notes.
Siemens uploaded a revision of SP-201101.
Ericsson comments on 5G-ACIA activity on following up requirements from SA1 eCAV
Walter (Philips) provides additional reason for requirements enumeration
Deutsche Telekom (Johannes) comments on requirements enumeration
Siemens replies to Ericsson and agrees with Ericsson that requirements enumeration can be also useful for entities outside 3GPP. However, it was stated earlier on in the pertinent SA email discussion, that this has no impact on whether 3GPP should or should not endorse the enumeration proposals brought to SA#89-e. Furthermore, how enumerated requirements are used at 5G-ACIA differs fundamentally from the intended use at 3GPP.
Siemens replies to Spirent.
Futurewei (Tony) comments on requirements enumeration.
Siemens is okay with Futurewei's proposal and enquires if others also would like to see the proposed change.
Ericsson (Krister) comments on Futurewei suggestion.
Siemens uploaded rev2 of SP-201102, SP-201103, and SP-201104. These revisions implement Futurewei's proposed change to the 'Consequences if not approved' field.
Nokia requests further revision to remove reference to SP-201101 and SP-200926 from the CRs' coversheet.
Ericsson (Krister) comment that we should not introduce negative impacts to 3GPP way of working as proposed, but rather work with other ways to support smaller companies in interest organizations providing those smaller companies with what they need. 3GPP may also provide complements to existing search tools, work plan etc which is providing a support to allow smaller companies to follow where features and work progress.
Siemens agrees with Nokia that the indicated reference to SP-200926 needs to be deleted and has done so in the uploaded rev3 of SP-201102 and SP-201104. Since rev1 of SP-201101 does not contain any reference to down-stream groups anymore, the reference to this document does not need to be removed from the CR cover sheets.
Nokia asks again to remove reference to SP-201101 from the CRs' coversheet, or to put new number for the revision of SP-201101.
Siemens clarifies that the phrase 'supporting verticals' refers to the vertical 3GPP members that, besides Siemens, co-sourced SP-201101, SP-201102, SP-201103, and SP-201104, namely Bosch, Daimler, EBU, Novamint, Phillips, Sennheiser, and Volkswagen AG.
Gerald (Matrixx) will object except with a clear commitment to not require the implementation of the enumeration scheme in other WGs technical specifications.		 Postponed
17.1 SP-201103 CR Approval 22.261 CR0494 (Rel-18, 'D'): Quality improvement - enumeration of requirements in TS 22.261 (Rel-18; this CR does not introduce any technical change) Siemens, Daimler, Volkswagen AG, Novamint, BMWi, Philips, Sennheiser, ETRI, EBU, Bosch Rel-18 Should be Cat A CR - moved to AI 17.1. CR states 'TS 22.261' instead of '22.261'. CC#4: Postponed Nokia requests clarification on the proposal to cross-reference enumerated SA1 requirements in the objectives of affected stage 2 WIDs.
Siemens corrects the subject line for this email thread and responds to four of Ericsson's statements.
Siemens addresses Nokia's question concerning the proposal to cross-reference enumerated SA1 requirements in the objectives of affected stage-2 WIDs.
Haris (Qualcomm) comments
Philips supports enumerating the requirements and provides additional feedback.
Siemens replies to Qualcomm
Gerald (Matrixx) with further comments and suggestion.
Huawei considers that this is a minor effort that could be helpful in bringing more relevant expertise to stage 2 and stage 3 groups, and is therefore worthwhile to invest in.
vivo considers that companies should be allowed to bring in tdocs to try and enumerate requirements in SA1.
Ericsson disagrees with point made by Huawei and objects to the proposal of introducing this new enumeration work process in 3GPP. As a consequence also objects starting to introduce and maintain requirement numbers in SA1 TSes up for approval in CRs in this meeting.
LG agrees with vivo's view in bullet points 'a' and 'b'.
LG disagrees the point that Huawei shared and provides reply comments. LG shares the view that it is for 'some' specifications that it would be helpful to have/keep requirement numbering but LG does not see any good justification because it has already been done on an as-needed basis so far. LG agrees that it is important to make a good interface with industry verticals but does not agree that those remedies that were put on table will become a helpful solution at all. LG would like to support some idea, in part, stated in SP-201101 ('Enumeration of TS 22.104 and TS 22.261: a bird's eye perspective'), specifically about the 'verticals' related specification. However, LG wants to clarify the view that SP-201102 (Rel-17 CR against 22.261) and SP-201103 (Rel-18 CR against 22.261) are attempting to claim something beyond what the authors of SP-201101 have tried to justify. This is because 22.261 is a comprehensive specification, not only covering verticals-related requirements but also covering a general set of requirements (refer to the WID of SMARTER, SID of FS_SMARTER and its four BBs). Therefore, although LG can agree to some change components made to vertical related clauses, LG disagrees to some of the change components that were proposed to (mostly/nearly) all clauses. Specifically for 22.261, instead, LG proposes that only those clauses related to verticals industry (e.g., directly affected by WI code of cyberCAV, eCAV, VIAPA, if necessary/agreeable) should be selectively taken care of by the CRs (R17, R18).
Peretz (Spirent) comments
Siemens replies to Spirent and Qualcomm
Siemens uploaded revisions to SP-201102, SP-201103, and SP-201104. These revisions correct slips identified in the chair's notes.
Siemens uploaded a revision of SP-201101.
Ericsson comments on 5G-ACIA activity on following up requirements from SA1 eCAV
Walter (Philips) provides additional reason for requirements enumeration
Deutsche Telekom (Johannes) comments on requirements enumeration
Siemens replies to Ericsson and agrees with Ericsson that requirements enumeration can be also useful for entities outside 3GPP. However, it was stated earlier on in the pertinent SA email discussion, that this has no impact on whether 3GPP should or should not endorse the enumeration proposals brought to SA#89-e. Furthermore, how enumerated requirements are used at 5G-ACIA differs fundamentally from the intended use at 3GPP.
Siemens replies to Spirent.
Futurewei (Tony) comments on requirements enumeration.
Siemens is okay with Futurewei's proposal and enquires if others also would like to see the proposed change.
Ericsson (Krister) comments on Futurewei suggestion.
Siemens uploaded rev2 of SP-201102, SP-201103, and SP-201104. These revisions implement Futurewei's proposed change to the 'Consequences if not approved' field.
Nokia requests further revision to remove reference to SP-201101 and SP-200926 from the CRs' coversheet.
Ericsson (Krister) comment that we should not introduce negative impacts to 3GPP way of working as proposed, but rather work with other ways to support smaller companies in interest organizations providing those smaller companies with what they need. 3GPP may also provide complements to existing search tools, work plan etc which is providing a support to allow smaller companies to follow where features and work progress.
Siemens agrees with Nokia that the indicated reference to SP-200926 needs to be deleted and has done so in the uploaded rev3 of SP-201102 and SP-201104. Since rev1 of SP-201101 does not contain any reference to down-stream groups anymore, the reference to this document does not need to be removed from the CR cover sheets.
Nokia asks again to remove reference to SP-201101 from the CRs' coversheet, or to put new number for the revision of SP-201101.
Siemens clarifies that the phrase 'supporting verticals' refers to the vertical 3GPP members that, besides Siemens, co-sourced SP-201101, SP-201102, SP-201103, and SP-201104, namely Bosch, Daimler, EBU, Novamint, Phillips, Sennheiser, and Volkswagen AG.
Gerald (Matrixx) will object except with a clear commitment to not require the implementation of the enumeration scheme in other WGs technical specifications.		 Postponed
17.1 SP-201104 CR Approval 22.104 CR0061 (Rel-17, 'D'): Quality improvement - enumeration of requirements in TS 22.104 (R17; this CR does not introduce any technical change) Siemens, Daimler, Volkswagen AG, Novamint, BMWi, Philips, Sennheiser, ETRI, EBU, Bosch Rel-17 Should have been reserved as a revision of 22.104 CR0053R1, not a new CR. CR states 'TS 22.104' instead of '22.104'. CC#4: Postponed Nokia requests clarification on the proposal to cross-reference enumerated SA1 requirements in the objectives of affected stage 2 WIDs.
Siemens corrects the subject line for this email thread and responds to four of Ericsson's statements.
Siemens addresses Nokia's question concerning the proposal to cross-reference enumerated SA1 requirements in the objectives of affected stage-2 WIDs.
Haris (Qualcomm) comments
Philips supports enumerating the requirements and provides additional feedback.
Siemens replies to Qualcomm
Gerald (Matrixx) with further comments and suggestion.
Huawei considers that this is a minor effort that could be helpful in bringing more relevant expertise to stage 2 and stage 3 groups, and is therefore worthwhile to invest in.
vivo considers that companies should be allowed to bring in tdocs to try and enumerate requirements in SA1.
Ericsson disagrees with point made by Huawei and objects to the proposal of introducing this new enumeration work process in 3GPP. As a consequence also objects starting to introduce and maintain requirement numbers in SA1 TSes up for approval in CRs in this meeting.
LG agrees with vivo's view in bullet points 'a' and 'b'.
LG disagrees the point that Huawei shared and provides reply comments. LG shares the view that it is for 'some' specifications that it would be helpful to have/keep requirement numbering but LG does not see any good justification because it has already been done on an as-needed basis so far. LG agrees that it is important to make a good interface with industry verticals but does not agree that those remedies that were put on table will become a helpful solution at all. LG would like to support some idea, in part, stated in SP-201101 ('Enumeration of TS 22.104 and TS 22.261: a bird's eye perspective'), specifically about the 'verticals' related specification. However, LG wants to clarify the view that SP-201102 (Rel-17 CR against 22.261) and SP-201103 (Rel-18 CR against 22.261) are attempting to claim something beyond what the authors of SP-201101 have tried to justify. This is because 22.261 is a comprehensive specification, not only covering verticals-related requirements but also covering a general set of requirements (refer to the WID of SMARTER, SID of FS_SMARTER and its four BBs). Therefore, although LG can agree to some change components made to vertical related clauses, LG disagrees to some of the change components that were proposed to (mostly/nearly) all clauses. Specifically for 22.261, instead, LG proposes that only those clauses related to verticals industry (e.g., directly affected by WI code of cyberCAV, eCAV, VIAPA, if necessary/agreeable) should be selectively taken care of by the CRs (R17, R18).
Peretz (Spirent) comments
Siemens replies to Spirent and Qualcomm
Siemens uploaded revisions to SP-201102, SP-201103, and SP-201104. These revisions correct slips identified in the chair's notes.
Siemens uploaded a revision of SP-201101.
Ericsson comments on 5G-ACIA activity on following up requirements from SA1 eCAV
Walter (Philips) provides additional reason for requirements enumeration
Deutsche Telekom (Johannes) comments on requirements enumeration
Siemens replies to Ericsson and agrees with Ericsson that requirements enumeration can be also useful for entities outside 3GPP. However, it was stated earlier on in the pertinent SA email discussion, that this has no impact on whether 3GPP should or should not endorse the enumeration proposals brought to SA#89-e. Furthermore, how enumerated requirements are used at 5G-ACIA differs fundamentally from the intended use at 3GPP.
Siemens replies to Spirent.
Futurewei (Tony) comments on requirements enumeration.
Siemens is okay with Futurewei's proposal and enquires if others also would like to see the proposed change.
Ericsson (Krister) comments on Futurewei suggestion.
Siemens uploaded rev2 of SP-201102, SP-201103, and SP-201104. These revisions implement Futurewei's proposed change to the 'Consequences if not approved' field.
Nokia requests further revision to remove reference to SP-201101 and SP-200926 from the CRs' coversheet.
Ericsson (Krister) comment that we should not introduce negative impacts to 3GPP way of working as proposed, but rather work with other ways to support smaller companies in interest organizations providing those smaller companies with what they need. 3GPP may also provide complements to existing search tools, work plan etc which is providing a support to allow smaller companies to follow where features and work progress.
Siemens agrees with Nokia that the indicated reference to SP-200926 needs to be deleted and has done so in the uploaded rev3 of SP-201102 and SP-201104. Since rev1 of SP-201101 does not contain any reference to down-stream groups anymore, the reference to this document does not need to be removed from the CR cover sheets.
Nokia asks again to remove reference to SP-201101 from the CRs' coversheet, or to put new number for the revision of SP-201101.
Siemens clarifies that the phrase 'supporting verticals' refers to the vertical 3GPP members that, besides Siemens, co-sourced SP-201101, SP-201102, SP-201103, and SP-201104, namely Bosch, Daimler, EBU, Novamint, Phillips, Sennheiser, and Volkswagen AG.
Gerald (Matrixx) will object except with a clear commitment to not require the implementation of the enumeration scheme in other WGs technical specifications.		 Postponed
17.1 SP-201112 DISCUSSION Discussion On SA WG1 requirements enumeration Qualcomm CDMA Technologies CC#3: Noted Noted
17.1 - - - Block Approval Block 5 (Thu 15:00 UTC) - - Docs:=5 -
17.1 SP-201025 CR PACK Approval Stage 1 CRs on eCPSOR_CON SA WG1 Rel-17 CC#3: Block Approved Approved
17.1 SP-201026 CR PACK Approval Stage 1 CRs on MuDE SA WG1 Rel-17 CC#3: Block Approved Approved
17.1 SP-201027 CR PACK Approval Stage 1 CRs on MPS2 SA WG1 Rel-17 CC#3: Block Approved Approved
17.1 SP-201028 CR PACK Approval Stage 1 CRs on AVPROD SA WG1 Rel-17 CC#3: Block Approved Approved
17.1 SP-201029 CR PACK Approval Stage 1 CRs on TEI17 SA WG1 Rel-17 CC#3: Block Approved Approved
17.2 - - - SA WG2 Rel-17 CRs - - Docs:=0 -
17.3 - - - SA WG3 and SA WG3 LI Rel-17 CRs - - Docs:=1 -
17.3 - - - Block Approval Block 5 (Thu 15:00 UTC) - - Docs:=1 -
17.3 SP-201008 CR PACK Approval Rel-17 CRs on TEI SA WG3 CC#3: Block Approved Approved
17.4 - - - SA WG4 Rel-17 CRs - - Docs:=0 -
17.5 - - - SA WG5 Rel-17 CRs - - Docs:=10 -
17.5 - - - Block Approval Block 5 (Thu 15:00 UTC) - - Docs:=10 -
17.5 SP-201046 CR PACK Approval Rel-17 CRs on Management of the enhanced tenant concept SA WG5 CC#3: Block Approved Approved
17.5 SP-201052 CR PACK Approval Rel-17 CRs on TEI SA WG5 CC#3: Block Approved Approved
17.5 SP-201058 CR PACK Approval Rel-17 CRs on Enhancements of 5G performance measurements and KPIs SA WG5 CC#3: Block Approved Approved
17.5 SP-201062 CR PACK Approval Rel-17 CRs on Enhancements on EE for 5G networks SA WG5 CC#3: Block Approved Approved
17.5 SP-201065 CR PACK Approval Rel-17 CRs on Intent driven management service for mobile network SA WG5 CC#3: Block Approved Approved
17.5 SP-201066 CR PACK Approval Rel-17 CRs on Enhancements of Self-Organizing Networks (SON) for 5G networks SA WG5 CC#3: Block Approved Approved
17.5 SP-201067 CR PACK Approval Rel-17 CRs on Charging enhancement for URLLC SA WG5 CC#3: Block Approved Approved
17.5 SP-201068 CR PACK Approval Rel-17 CRs on IMS Charging in 5G System Architecture SA WG5 CC#3: Block Approved Approved
17.5 SP-201070 CR PACK Approval Rel-17 CRs on N40 Interface Enhancements to Support GERAN and UTRAN SA WG5 CC#3: Block Approved Approved
17.5 SP-201075 CR PACK Approval Rel-17 CRs on Closed loop SLS Assurance SA WG5 CC#3: Block Approved Approved
17.6 - - - SA WG6 Rel-17 CRs - - Docs:=8 -
17.6 - - - Block Approval Block 5 (Thu 15:00 UTC) - - Docs:=8 -
17.6 SP-200993 CR PACK Approval Rel-17 CR to TR23764 for FS_eV2XAPP SA WG6 CC#3: Block Approved Approved
17.6 SP-200994 CR PACK Approval Rel-17 CRs to TS23281 and TS23379 for eMONASTERY2 SA WG6 CC#3: Block Approved Approved
17.6 SP-200995 CR PACK Approval Rel-17 CRs to TS23280 and TS23379 for enh3MCPTT SA WG6 CC#3: Block Approved Approved
17.6 SP-200996 CR PACK Approval Rel-17 CRs to TS23282 for eMCData3 SA WG6 CC#3: Block Approved Approved
17.6 SP-200997 CR PACK Approval Rel-17 CRs to TS23222 for EDGEAPP SA WG6 CC#3: Block Approved Approved
17.6 SP-200998 CR PACK Approval Rel-17 CRs to TS23286 and TS23434 for eV2XAPP SA WG6 CC#3: Block Approved Approved
17.6 SP-200999 CR PACK Approval Rel-17 CRs to TS23434 for eSEAL SA WG6 CC#3: Block Approved Approved
17.6 SP-201000 CR PACK Approval Rel-17 CRs to TS23281 for TEI17 SA WG6 CC#3: Block Approved Approved
18 - - - Rel-18 CRs - - Docs:=0 -
18.1 - - - SA WG1 Rel-18 CRs - - Docs:=0 -
18.2 - - - SA WG2 Rel-18 CRs - - Docs:=0 -
18.3 - - - SA WG3 and SA WG3 LI Rel-18 CRs - - Docs:=0 -
18.4 - - - SA WG4 Rel-18 CRs - - Docs:=0 -
18.5 - - - SA WG5 Rel-18 CRs - - Docs:=0 -
18.6 - - - SA WG6 Rel-18 CRs - - Docs:=0 -
19 - - - CR’s related to Study Items - - Docs:=0 -
20 - - - Project Management & TSG SA owned specifications - - Docs:=0 -
20.1 - - - Review of the work plan - - Docs:=1 -
20.1 SP-201116 WORK PLAN Presentation Work Plan review at TSG#90E Work Plan Coordinator (MCC) OPEN
20.2 - - - Specification Status - - Docs:=0 -
20.3 - - - Work Item Summaries for TR 21.91x - - Docs:=10 -
20.3 - - - Block Approval Block 6 (Thu 15:00 UTC) - - Docs:=10 -
20.3 SP-200938 WI SUMMARY Endorsement Release 16 WI summary for V2XAPP Huawei Telecommunication India Rel-16 CC#3: Block Endorsed Endorsed
20.3 SP-200941 WI SUMMARY Endorsement Summary for work item 'Mobile Communication System for Railways 2 (MONASTERY2)' Nokia, Nokia Shanghai Bell Rel-16 CC#3: Block Endorsed Endorsed
20.3 SP-200943 WI SUMMARY Endorsement Summary for work item '5G positioning services (5G_HYPOS)' ESA Rel-16 CC#3: Block Endorsed Endorsed
20.3 SP-201001 WI SUMMARY Endorsement Release 16 summary for WI MBMSAPI_MCS CATT, TD-Tech Rel-16 CC#3: Block Endorsed Endorsed
20.3 SP-201083 WI SUMMARY Endorsement Release 16 WI summary for eMCData2 AT&T GNS Belgium SPRL Rel-16 CC#3: Block Endorsed Endorsed
20.3 SP-201111 WI SUMMARY Endorsement Release 16 WI summary for MCCI Sepura Ltd Rel-16 CC#3: Block Endorsed Endorsed
20.3 SP-201113 WI SUMMARY Endorsement Summary for work item 'Multi-device and multi-identity (MUD)' Ericsson Rel-16 CC#3: Block Endorsed Endorsed
20.3 SP-201114 WI SUMMARY Endorsement Summary of enh2MCPTT feature in Release 16 Motorola Solutions UK Ltd. Rel-16 CC#3: Block Endorsed Endorsed
20.3 SP-201117 WI SUMMARY Endorsement Summary for Work Item Network Resource Model (NRM) enhancements Nokia, Nokia Shanghai Bell Rel-16 CC#3: Block Endorsed Endorsed
20.3 SP-201119 DRAFT TR Information TR 21.916 v.1.0.0 on Rel-16 Description Summary MCC Work Plan Manager Rel-16 CC#3: Block Noted Noted
20.4 - - - Improvements to working methods & CRs against 3GPP TSG SA owned Specifications - - Docs:=6 -
20.4 SP-201002 CR Approval 21.801 CR0056 (Rel-17, 'B'): Use of inclusive terminology MCC Specifications manager Rel-17 CC#1: This was left for e-mail discussion and the MCC Specifications manager undertook to provide a revision of this over the e-mail list. CC#2: SP-201002_Rev4 was approved. Revised to SP-201142. BT comments that rev3 is fine for them.
Puneet (SA2 Chair) comments that rev3 is fine.		 Revised
20.4 SP-201142 CR Approval 21.801 CR0056R1 (Rel-17, 'B'): Use of inclusive terminology MCC Specifications manager Rel-17 Revision of SP-201002_Rev4. This CR was approved Approved
20.4 SP-201120 LS OUT Approval LS to 3GPP WGs on Use of inclusive terminology TSG SA Created at CC#1. CC#3: This was left for further off-line discussion until CC#4. CC#4: _Rev6 approved. Revised to SP-201143. Puneet (SA2 Chair) provides rev2.
Ki-Dong (LG) provides comments including suggested changes on rev2 (SP-201120_rev2.zip) that SA2 Chairperson has provided.
Shabnam (Ericsson) asks if March/2021 would give WGs sufficient time to apply these rules, including for cases like IEEE related references? And should we also provide reference to the LS to IEEE so WGs would avoid those changes until we receive feedback?
Deutsche Telekom (Johannes) proposes some editorials to the LS.
Sherry (Xiaomi) also feels more time may be needed to update the existing R17 TSs, and asks if it is possible to set the time for 4) to June 2021 TSGs meetings while keeping the time of March 2021 for Item 5).
Chris (Vodafone) asks if one of our LSs needs to inform GSMA (or whoever manages the information feeds for the EIR databases)?
Suresh (SA6 Chairs) questions whether we need to list down the detailed actions again since the endorsed SP-201042 is already referenced in the LS?
Puneet (SA2 Chair) provides rev3.
Thomas (SA5 Chair) provides an editorial comment.
Xiaobao (Orange) asks to consider sending an LS to inform all SDOs related to the 3GPP of the 3GPP's decisions.
Puneet (SA2 Chair) provides rev4.
LaeYoung (LGE) provides editorial comments on rev4. Same editorial changes are needed also in 1121.
With thanks to SA2 chair for the effort, Ki-Dong (LG) provides three suggested change points to rev4 (1120).
(1) [bullet point '3) c']: to set clear bound for these CRs so that nothing other than 'replacement' is combined in each CR (although the 'other thing' is purely editorial);
(2) [bullet point '3) d']: to editorially clarify the role to 'report to their WG's MCC' (this role doesn't seem to be chair's but that of rapporteurs and MCC);
(3) [bullet point '4)']: to move this under '3)' as this indicate the suggested due date on the respective WGs tasks entailed in bullet point '3)'; e.g., to make it '3) f'.
SA Chair requests to put all text that was indicated in 1042 to be sent in an LS out to be added to the LS.		 Revised
20.4 SP-201143 LS OUT Approval LS to 3GPP WGs on Use of inclusive terminology TSG SA Revision of SP-201120_Rev6. This LS OUT was approved Approved
20.4 SP-201121 LS OUT Approval LS to External Bodies on Use of inclusive terminology TSG SA Created at CC#1. CC#3: This was left for further off-line discussion until CC#4. CC#4: _Rev4 approved. Revised to SP-201144. Puneet (SA2 Chair) provides rev1.
Suresh (SA6 Chairs) questions whether we need to list down the detailed actions again since the endorsed SP-201042 is already referenced in the LS?
Puneet (SA2 Chair) provides rev2.
Suresh (SA6 Chair) provides comments on rev2 and seeks clarification on the general approach and alignment with the external organization, and provides some enhacements to the LS text.		 Revised
20.4 SP-201144 LS OUT Approval LS to External Bodies on Use of inclusive terminology TSG SA Revision of SP-201121_Rev4. This LS OUT was approved Approved
20.4 - - - Block Approval Block 6 (Thu 15:00 UTC) - - Docs:=0 -
20.5 - - - MCC Status Report (will be handled on Monday 14 December) - - Docs:=3 -
20.5 SP-201033 OTHER Approval 3GPP Voting Tool Testing during TSG#90e MCC Director Rel-17 CC#3: Noted Noted
20.5 SP-200942 REPORT Information MCC Support Team report MCC Director Revised to SP-201145. Revised
20.5 SP-201145 REPORT Information MCC Support Team report MCC Director Revision of SP-200942 OPEN
20.6 - - - Future Meeting schedule - - Docs:=2 -
20.6 - - - Block Approval Block 6 (Thu 15:00 UTC) - - Docs:=2 -
20.6 SP-200924 DISCUSSION Information TSGs calendar 2022 and 2023 TSG SA Chair, TSG RAN Chair, TSG CT Chair CC#3: Block Noted Noted
20.6 SP-200925 DISCUSSION Information Overview SA WG Meetings during H1/2021 TSG SA Chair CC#3: Block Noted Noted
21 - - - Any Other Business - - Docs:=1 -
21 SP-201110 DISCUSSION Endorsement EMeeting Operating procedure proposals vivo Mobile Com CC#2: This was not handled due to lack of time and may be handled in a later CC. OPEN
22 - - - Close of Meeting - - Docs:=0 -
99 - - - WITHDRAWN ITEMS - - Docs:=12 -
99 SP-201122 CR Approval 23.502 CR2413R2 (Rel-16, 'F'): Correcting configuration of QoS monitoring for URLLC MCC Rel-16 Created at CC#2: Revision of 23.502 CR2413R1 from CR pack SP-200946. WITHDRAWN Withdrawn
99 SP-200919 OTHER Information Reserved for incoming LS MCC WITHDRAWN Withdrawn
99 SP-200920 OTHER Information Reserved for incoming LS MCC WITHDRAWN Withdrawn
99 SP-200921 OTHER Information Reserved for incoming LS MCC WITHDRAWN Withdrawn
99 SP-200922 OTHER Information Reserved for incoming LS MCC WITHDRAWN Withdrawn
99 SP-201095 CR Approval 22.263 CR0013 (Rel-17, 'D'): Quality improvement - enumeration of requirements in TS 22.263 Sennheiser Electronic GmbH Rel-17 WITHDRAWN Withdrawn
99 SP-201060 CR PACK Approval Rel-17 CRs on Enhancements of 5G performance measurements and KPIs SA WG5 WITHDRAWN Withdrawn
99 SP-201092 CR Approval 33.501 CR1018 (Rel-16, 'F'): Error correction and clarification of Annex O in 33.501 CableLabs Rel-16 WITHDRAWN Withdrawn
99 SP-201034 DISCUSSION Approval Inclusive Language in 3GPP Specifications SA Chair, RAN Chair, CT Chair, SA WG1 Chair, SA WG2 Chair, SA WG3 Chair, SA WG4 Chair, SA WG5 Chair, SA WG6 Chair, RAN WG1 Chair, RAN WG2 Chair, RAN WG3 Chair, RAN WG4 Chair, RAN WG5 Chair, CT WG1 Chair, CT WG3 Chair, CT WG4 Chair, CT 6 Chair Rel-17 WITHDRAWN Withdrawn
99 SP-201035 DISCUSSION Approval Inclusive Language in 3GPP Specifications SA Chair, RAN Chair, CT Chair, SA WG1 Chair, SA WG2 Chair, SA WG3 Chair, SA WG4 Chair, SA WG5 Chair, SA WG6 Chair, RAN WG1 Chair, RAN WG2 Chair, RAN WG3 Chair, RAN WG4 Chair, RAN WG5 Chair, CT WG1 Chair, CT WG3 Chair, CT WG4 Chair, CT 6 Chair Rel-17 WITHDRAWN Withdrawn
99 SP-201036 DISCUSSION Approval Inclusive Language in 3GPP Specifications HUAWEI TECHNOLOGIES Co. Ltd. Rel-17 WITHDRAWN Withdrawn
99 SP-200983 TOR Approval SA WG6 ToR Update SA WG6 WITHDRAWN Withdrawn
Created:      END OF LIST
OPEN documents: 8
Parallel Agreed: 0
Approved/Endorsed: 143
Replied to LSs: 0
Noted: 55
Merged: 0
For e-mail approval: 0
Postponed: 7
Withdrawn: 13
Total documents: 255