3GPP TSG CT WG1 Meeting#122	C1-200203

Electronic meeting, 20-28 February 2020

Meeting documents by agenda item Meeting: Meeting #122-e Electronic meeting 20 - 28 February 2020 All indicated times are CET
Cyan background means allocated but not available.	Yellow background means available but not yet treated document.	Green background means this document was agreed at a revious meeting in this plenary cycle.	White background means that the document has been handled in the meeting and a decision has been made.
Additional Colour coding for Tdocs in the 1st row
Late Papers
Easy and uncontroversial papers – can be presented within 2 minutes
Papers for common sessions
Low Priority
Agenda item	Agenda item title	Tdoc	Title	Source	Spec	Result
Opening & welcome	Tdoc	Title	Source	Spec	Result
IPR Policy Reminder to Individual Members and the persons making the technical proposals about their obligations under their respective Organizational Partners IPR Policy: 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.
Antitrust & Competition 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.
Usage if WiFi During 3GPP meetings, IT support staff have noticed an increasing amount of RF pollution from private, ad hoc, wireless networks (Wi-Fi Direct, hot-spots hosted on mobile phones, …), and this gives rise to reduced throughput capability of the 3GPP WLAN. I would like to remind delegates to disable all such non-3GPP Wi-Fi networks while they are in the meeting rooms or adjacent areas. This will allow the quality of connection to the 3GPP Wi-Fi network which delegates have a right to expect.
Statement Regarding Engagement with Companies Added to the U.S. Export Administration Regulations (EAR) Entity List in 3GPP Activities 1. Public Information is Not Subject to EAR 3GPP is an open platform where all contributions (including technology protected or not by patent) made by the different Individual Members under the membership of each respective Organizational Partner are publicly available. Indeed, contributions by all and any Individual Members are uploaded to a public file server when received and then the documents are effectively in the public domain. In addition, since membership of email distribution lists is open to all, documents and emails distributed by that means are considered to be publicly available. As a result, information contained in 3GPP contributions, documents, and emails distributed at 3GPP meetings or by 3GPP email distribution lists, because it is made available to the public without restrictions upon its further dissemination, is not subject to the export restrictions of the EAR. Meeting minutes are maintained for 3GPP meetings. Such meeting minutes for 3GPP meetings are made available to the public without restrictions upon its further dissemination. As a result, information, including information conveyed orally, contained in 3GPP meetings is not subject to the export restriction of the EAR; this would include information conveyed during side meetings that may occur during the main meetings, if these meetings are open to any participants and the results of all said meetings are publicly available without restrictions upon their further dissemination. 2. Non-Public Information Non-public information refers to the information not contained or not intended to be contained in 3GPP contributions, documents or emails. Such non-public information may be disclosed during informal meetings, exchanges, discussions or any form of other communication outside the 3GPP meetings and email distribution lists, and may be subject to the EAR. 3. Other Information Certain encryption software controlled under the International Traffic in Arms Regulations (ITAR), even if publicly available, may still be subject to US export controls other than the EAR. 4. Conduct of Meetings The situation should be considered as "business as usual" during all the meetings called by 3GPP. 5. Responsibility of Individual Members It should be remembered that contributions, meetings, exchanges, discussions or any form of other communication in or outside the 3GPP meetings are of the accountability, integrity and the responsibility of each Individual Member. In addition, Individual Members remain responsible for ensuring their compliance with all applicable export control regulations, including but not limited to EAR. Individual Members with questions regarding the impact of laws and regulations on their participation in 3GPP should contact their companies’ legal counsels.
Please remember: - to perform the electronic registration before end-of-meeting - to wear your badge
Agenda & Reports	Tdoc	Title	Source	Doctype	Result & comments
C1-200275	3GPP TSG CT1#122 – agenda after Tdoc allocation deadline	CT1 chairman	agenda	Revision of C1-200200
C1-200201	3GPP TSG CT1#122 – agenda after Tdoc allocation deadline	CT1 chairman	agenda
C1-200202	3GPP TSG CT1#122 – agenda with proposed LS-actions	CT1 chairman	agenda
C1-200203	3GPP TSG CT1#122 – agenda at start of meeting	CT1 chairman	agenda
C1-200204	3GPP TSG CT1#122 – agenda Thursday (27th Feb) evening	CT1 chairman	agenda
C1-200205	3GPP TSG CT1#122 – agenda at end of meeting	CT1 chairman	agenda
C1-200307	draft C1-121 meeting report	MCC	report
Highest number shown in the 0775
Agenda 1 Opening 2 Agenda and Reports 3 work organization 4 incoming LS Rel-16 Rel-16: 16.1.x Work items (4) 16.2.3 SAES16 (all aspects) (0) only revisions of CRs agreed in CT1#121bis-e and disc papers supporting LSs 16.2.4 5GProtoc16 (all aspects) (5) only revisions of CRs agreed in CT1#121bis-e and disc papers supporting LSs 16.2.21 Rel-16 non-IMS issues (0) only revisions of CRs agreed in CT1#121bis-e and disc papers supporting LSs Agenda Items from 16.2 16.2.2 SINE_5G (4) 16.2.5 ATSSS (28) 16.2.6 eNS (51) 16.2.7.x vertical-LAN (79) 16.2.8 5G_CIoT (44) 16.2.9 5WWC (25) 16.2.11 5G_eLCS (2) 16.2.14 RACS (16) 16.2.15 5G_SRVCC (2) 16.2.16 xBDT (0) 16.2.17 IAB-CT (0) 16.2.18 5GS_OTAF (0) 16.2.19 5G_URLLC (2) 16.2.20 SEAL (51) 16.2.1 ePWS (5) 16.2.10 PARLOS (7) 16.2.12 V2XAPP (13) 16.2.13 eV2XARC (35) Agenda Items from 16.3 16.3.1 MCCI_CT (7) 16.3.2 MCProtoc16 (5) 16.3.5 MCSMI_CT (0) 16.3.6 eMCDATA2 (19) 16.3.10 MONASTERY2 (8) 16.3.12 enh2MCPTT-CT (9) 16.3.3 MuD (15) 16.3.4 IMSProtoc16 (3) 16.3.7 E2E_DELAY (0) 16.3.8 VBCLTE (0) 16.3.11 eIMS5G_SBA (1) 16.3.13 eIMSVideo (8) 16.3.14 IMS/MC TEI16 (3) 18 outgoing LS Rel-16
Work organisation	Tdoc	Title	Source	To / CC	Result & comments
Meeting schedule
CT1 and CT plenary meeting dates.
Date	Meeting	Venue
13 – 17 January	CT1-Potential Ad-Hoc	cancelled
16 – 22 January	CT1#121bis-e	Electronic Meeting
24 – 28 February	CT1#122	cancelled
20 – 28 February	CT1#122-e	Electronic Meeting
16 – 17 March 2020	CT plenary #87	Jeju, Korea
20 – 24 April	CT1#123	Dubrovnik, Croatia
25 – 29 May	CT1#124	Dalian, China
15 – 16 June 2020	CT plenary #88	Malmö, Sweden
13 – 17 July	CT1-Potential Ad-Hoc	TBD
24 – 28 August	CT1#125	US
14 – 15 September 2020	CT plenary #89	Funchal, Madeira
12 – 16 October	CT1#126	India
16 – 20 November	CT1#127	US
7 – 8 December 2020	CT plenary #90	NAF
25 – 29 January 2021	CT1#127bis	tbd
01- 05 March 2021	CT1#128	tbd
22 – 23 March 2021	CT plenary #91	US
19 – 23 April 2021	CT1#129	tbd
24 – 28 May 2021	CT1#130	tbd
14 – 15 June 2021	CT plenary #91	Japan
Work Plan and other adm. issues	Tdoc	Title	Source	Spec / doctype	Result & comments
C1-200306	work plan	MCC	Work Plan
C1-200312	CT1#122-e Electronic Meeting – Process and Scope	CT1 chairman	other
Input Liaison statements	Tdoc	Title	Source	To / CC	Result & comments
C1-200206	LS on usage of IMSI during 3GPP based authentication (C4-195574)	CT4	Cc	Proposed Noted
C1-200207	LS on user identity when 5G-AKA or EAP AKA’ is used for SNPN (C6-190468)	CT6	To	Proposed Noted SA3 reply in C1-200255
C1-200208	LS on Proposal to transfer the study on service-based support for SMS in 5GC to CT WGs (CP-193301)	TSG CT	Cc	Postponed LS pertains to Rel-17
C1-200209	Reply LS to Transfer the study on service-based support for SMS in 5GC to CT WGs (SP-191362)	TSG SA	Cc	Postponed LS pertains to Rel-17
C1-200210	Response to 3GPP S2-1910806 and S2-1912767 on Line ID (LIAISE-353)	Broadband Forum	To	Proposed Noted SA2 has already handled the incoming LS
C1-200211	General Status of Work (LIAISE-363à	Broadband Forum	To	Proposed tbd Reply needed Proposed LS out in C1-200309
C1-200212	LS on Testing and Certification of 3GPP Mission Critical features A GCF-TCCA Joint Approach to Develop and Manage MC Certification (	TCCA	Cc	Proposed Noted
C1-200213	Reply LS on QoE Measurement Collection (R2-1916328)	RAN2	Cc	Proposed Noted
C1-200214	Reply LS on NID structure and length (R2-1916344)	RAN2	Cc	Proposed Noted Related CR in C1-200334
C1-200215	CMAS/ETWS and emergency services for SNPNs (R2-1916345)	RAN2	Cc	Proposed Noted
C1-200216	Reply LS on Sending CAG ID in NAS layer (R2-1916349)	RAN2	Cc	Proposed Noted Related DP in C1-200335 and CR in C1-200337
C1-200217	Reply LS on Mobile-terminated Early Data Transmission (R2-1916368)	RAN2	To	Proposed tbd Proposed LS out in C1-200707 CR in C1-200368
C1-200218	Reply LS on assistance indication for WUS (R2-1916440)	RAN2	To	Proposed Noted Seems no reply needed
C1-200219	Reply LS on PC5S and PC5 RRC unicast message protection (R2-1916461)	RAN2	Cc	Proposed Noted
C1-200220	LS on dependencies on AS design for mobility management aspects of NTN in 5GS (R2-1916470)	RAN2	Cc	Proposed Noted C1-200220 from RAN2 and C1-200269 from RAN3 are both replies to the same LS from SA2 (S2-1910786)
C1-200221	LS on RRC establishment cause value in EPS voice fallback from NR to E-UTRAN (R2-1916530)	RAN2	To	Proposed tbd TEI16, potentially changes to 24.301 needed Proposed LS out in C1-200710
C1-200222	LS on inter-RAT HO from SA to EN-DC (R2-1916600)	RAN2	Cc	Proposed Noted
C1-200223	LS on LS on system level design assumptions for satellite in 5GS (R2-1916620)	RAN2	Cc	Proposed Noted C1-200223 from RAN2 and C1-200269 from RAN3 are both replies to the same LS from SA2 (S2-1910787)
C1-200224	Reply LS on extended NAS timers for CE in 5GS (R2-1916623)	RAN2	To	Proposed tbd Proposed LS out in C1-200717 Related CRs in C1-200383 - C1-200384
C1-200225	Reply LS on Sending CAG ID in NAS layer (R3-197591)	RAN3	Cc	Proposed Noted Related DP in C1-200335 and CR in C1-200337
C1-200226	LS on Concurrent Broadcasting for CMAS (R3-197749)	RAN3	To	Postponed LS pertains to Rel-15 Proposed LS out in C1-200764
C1-200227	Reply LS on UAC for NB-IOT (S1-193592)	SA1	Cc	Proposed Noted Is related at least to CRs in C1-200397, C1-200421, C1-200677
C1-200228	Reply LS on enhanced access control for IMS signalling (S1-193595)	SA1	To	Proposed Noted No action in the LS
C1-200229	Reply LS on NSI requirements (S1-193596)	SA1	Cc	Proposed Noted
C1-200230	Reply LS on LS on PC5S and PC5 RRC unicast message protection (S2-1912002)	SA2	Cc	Proposed Noted Related CR in C1-200349
C1-200231	Reply LS on Enquiries on eV2XARC (S2-1912018)	SA2	To	Proposed Noted Related pCR in C1-200391 Related CR in C1-200349
C1-200232	Reply LS on SUCI computation from an NSI (S2-1912417)	SA2	To	Proposed Noted Are CRs available to this meeting?
C1-200233	LS on PLMN selection solutions for satellite access (S2-1912551)	SA2	To	Postponed LS pertains to Rel-17 (FS_5GSAT_ARCH) although header of the LS incorrectly indicates Rel-16
C1-200234	Reply LS on applicability of the notification procedure in SNPNs (S2-1912601)	SA2	To	Proposed tbd Proposed LS out in C1-200718 Related CRs in C1-200504, C1-200505, C1-200333
C1-200235	LS on support of Control Plane CIoT 5GS Optimisation (S2-1912609)	SA2	To	Proposed Noted Are CRs available to this meeting?
C1-200236	Reply LS on sending CAG ID during resume procedure (S2-1912731)	SA2	To	Proposed Noted No action for CT1
C1-200237	Reply LS on Rel-16 NB-IoT enhancements (S2-1912763)	SA2	To	Proposed tbd Reply Needed Proposed LS out in C1-200499 Proposed LS out in C1-200416 Discussion paper in C1-200498 DP in C1-200417
C1-200238	Reply LS on clarification on the requirement for steering of roaming (S2-1912764)	SA2	To	Proposed Postponed CRs in CT1 likely needed, agenda item not in scope of this meeting
C1-200239	LS on the support for ECN in 5GS (S2-1912765)	SA2	Cc	Proposed Noted
C1-200240	Reply LS on "set of configuration parameters" in the precedence of the V2X configuration parameters (S2-2000970)	SA2	To	Proposed Noted Related pCR in C1-200625
C1-200241	Reply LS on PC5 unicast and groupcast security protection (S2-2000971)	SA2	To	Proposed Noted Related CR in C1-200349
C1-200242	Reply LS on Response LS on SL RLM/RLF (S2-2000973)	SA2	To	Proposed Noted Related CR in C1-200350
C1-200243	Reply LS on configured NSSAI handling (S2-2001110)	SA2	To	Proposed tbd Proposed LS out in C1-200718 No action for CT1 identified
C1-200244	Reply LS on Dual-registration requirements for EHPLMNs (S2-2001130)	SA2	To	Proposed Postponed CT1 CRs seem needed, potentially a reply LS
C1-200245	LS on MA PDU establishment when the VPLMN does not support ATSSS (S2-2001148)	SA2	To	Proposed Noted Are CRs available to this meeting?
C1-200246	Reply LS on gPTP message delivery to DS-TT (S2-2001150)	SA2	To	Proposed Noted Related CR in C1-200339
C1-200247	Reply LS on 5G-S-TMSI Truncation Procedure (S2-2001248)	SA2	To	Proposed Noted C1-200500 (discussion paper) and C1-200501 (related CR)
C1-200248	Reply LS on congestion during RLOS access (S2-2001335)	SA2	To	Proposed Noted No action seems required
C1-200249	LS on Non-UE N2 Message Services Operations (S2-2001340)	SA2	To	Proposed tbd Proposed LS out in C1-200721
C1-200250	Reply LS on CMAS/ETWS and emergency services for SNPNs (S2-2001400)	SA2	Cc	Proposed Noted
C1-200251	Reply LS on assistance indication for WUS (S2-2001578)	SA2	To	Withdrawn
C1-200252	LS on Sending CAG ID (S2-2001616)	SA2	To	Proposed tbd Reply Needed Proposed LS out in C1-200310 Related CRs in C1-200311, C1-200467, C1-200337 (seem to contain the same solution) Related DP in C1-200335
C1-200253	LS on PC5S and PC5 RRC unicast message protection (S3-193802)	SA3	To	Proposed Noted Proposed LS out in C1-200545 Related CR in C1-200349
C1-200254	Reply LS to LS on usage of IMSI during 3GPP based authentication (S3-194454)	SA3	Cc	Proposed Noted Reply from SA3 to CT4 (C1-200206)
C1-200255	Reply LS on SUCI computation from an NSI (S3-194455)	SA3	To	Proposed tbd Reply Needed Proposed LS out in C1-200395
C1-200256	Reply LS to SA2 on 5G-S-TMSI Truncation Procedure (S3-194482)	SA3	Cc	Proposed Noted
C1-200257	Reply LS on SUCI computation from an NSI (S3-194548)	SA3	To	Proposed Noted Are CRs available to this meeting?
C1-200258	Reply LS on Sending CAG ID in NAS layer (S3-194559)	SA3	Cc	Proposed Noted
C1-200259	Reply LS on IANA assigned values for mission critical (S3-194603)	SA3	To	Proposed Postponed Reply LS is needed, not provided to the meeting, SA6 meets in May, i.e. after next CT1 meeting
C1-200260	LS to CT1 on 3rd ETSI MCX Remote Plugtest (S3-194611)	SA3	To	Proposed Noted
C1-200261	LS on Reply on QoE Measurement Collection (S5-197543)	SA5	Cc	Proposed Noted
C1-200262	Reply LS on how the IWF obtains key material for interworking group and private communications (S6-192194)	SA6	To	Proposed Noted Are CRs available to this meeting?
C1-200263	Reply LS (S6-192023) on clarifications regarding SEAL services (S6-192318)	SA6	Cc	Proposed Noted
C1-200264	Reply LS on Unicast resource management with SIP core (S6-200163)	SA6	To	Proposed Noted related CR iC1-200616
C1-200265	LS on API additions to SEAL and V2XAPP (S6-200270)	SA6	To	Proposed Noted No CT1 CRs seem available to this meeting, commented that none are needed
C1-200266	Reply LS on Enquiries for supporting vertical applications (S6-200337)	SA6	To	Proposed Noted Related CRs in C1-200562, C1-200563, C1-200554,C1-200552, C1-200553, C1-200608 and C1-200610
C1-200267	Reply LS on clarifications regarding V2XAPP services (S6-192385)	SA6	Cc	Proposed Noted
C1-200268	LS on missing cause code mapping (C3-195374)	CT3	Cc	Proposed Noted
C1-200269	Reply LS on LS on dependencies on AS design for mobility management aspects of NTN in 5GS / LS on system level design assumptions for satellite in 5GS (R3-197699)	RAN3	Cc	Proposed Noted C1-200220 from RAN2 and C1-200269 from RAN3 are both replies to the same LS from SA2 (S2-1910786) C1-200223 from RAN2 and C1-200269 from RAN3 are both replies to the same LS from SA2 (S2-1910787)
C1-200270	Reply on QoE Measurement Collection (S4-200241)	SA4	To	Proposed Postponed Reply LS is needed, not provided to the meeting
C1-200271	Reply LS on Support for ECN in 5GS (S4-200298)	SA4	Cc	Proposed Noted
C1-200272	LS on GSMA NG.116 Attribute Area of service and impact on PLMN selection (S2-2001726)	SA2	To	Postponed LS pertains to Rel-17 (FS_eNS_Ph2 )
C1-200273	Questions on onboarding requirements (S2-2001729)	SA2	Cc	Postponed LS pertains to Rel-17 (FS_eNPN)
C1-200274	Reply LS on assistance indication for WUS (S2-2001732)	SA2	To	Proposed Postponed SA2 asks CT WG1 group to take the above answers into account and update their specifications accordingly, if required. Any CRs for WUS in EPC were treated under SAES in previous meeting
C1-200319	Specification of NAS COUNT for 5G (FSAG Doc 78_002)	GSMA FSAG	To	Proposed Postponed CRs to 24.501 may be needed Reply LS may be needed
C1-200356	General status of WWC work (LIAISE-376)	Broadband Forum	LS in	Proposed Noted
void	Release 5 is closed
void	Release 6 is closed
void	Release 7 is closed
Release 8 work items	Tdoc	NOT PART OF THIS MEETING
Release 9 work items	Tdoc	NOT PART OF THIS MEETING
Release 10 work items	Tdoc	NOT PART OF THIS MEETING
Release 11 work items	Tdoc	NOT PART OF THIS MEETING
Release 12 work items	Tdoc	NOT PART OF THIS MEETING
Release 13 work items	Tdoc	NOT PART OF THIS MEETING
Release 14 work items	Tdoc	NOT PART OF THIS MEETING
Release 15 work items	Tdoc	NOT PART OF THIS MEETING
Release 16 work items	Tdoc	Title	Source	Tdoc info	Result & comments
Tdocs on Work Items	Papers related to Rel-16 Work Items
Work Item Descriptions	Peter - Main	New and revised Work Item Descritpions
C1-200296	Stage-3 5GS NAS protocol development	Ericsson / Ivo	WID revised Rel-16	Revision of CP-183087
C1-200348	Revised WID on CT aspects of optimisations on UE radio capability signalling	Qualcomm Incorporated / Lena	WID revised Rel-16
C1-200423	Revised WID on CT aspects of Cellular IoT support and evolution for the 5G System	Qualcomm Incorporated / Amer	WID revised Rel-16
C1-200472	Revised WID on Multi-device and multi-identity	Ericsson /Jörgen	WID revised Rel-16
CRs and Discussion Documents related to new or revised Work Items	Peter - Main	CRs and Disc papers related to new Work Items
Status of other Work Items	Peter - Main	Status information on other relevant Rel-16 Work Items
C1-200422	5G_CIoT WI workplan	Qualcomm Incorporated / Amer	Work Plan Rel-16
Release 16 documents for information	Peter - Main	Miscellaneous documents provided for information
WIs for common and SAE/5G	WIs mainly targeted for common sessions or the SAE/5G breakout
ePWS	Lena – Main	CT aspects of enhancements of Public Warning System TR 23.735 is sent to CT#85 for approval
C1-200442	CR 23.041#0208 Addition of message identifiers for UEs with no user interface	SyncTechno Inc.	CR 0208 23.041 Rel-16	Ivo, Thursday, 9:16 - ePWS WID (CP-191155) states "This work item will not introduce new functionality for US WEA and Japan ETWS." but this CR defines new message IDs for ETWS and CMAS and 23.041 states "CMAS (aka WEA)". Thus, the proposed new message IDs should be limited to KPAS and EU-Alert only. - furthermore, if CMAS and ETWS are anyway in scope, then to follow the existing 23.041 convention, there should be two sets of message ids - one set for ETWS (in the range 4357 - 4369) and one set for non-ETWS PWS (in the range proposed in the CR). Peter, Thursday, 11:00 1) I don't completely agree with Ivo's comment: Neither KPAS, nor EU-Alert have requirements for an ePWS service. The new message IDs should not apply to KPAS or EU-Alert. Simply removing the "CMAS/ETWS" will do (so this remains: "CBS Message Identifier for warning message dedicated to UEs with no user interface and with ePWS functionality regardless of the type of disasters and characteristics of a disaster.") 2) My remarks: - The RAN Node needs to make a choice between broadcasting as an ETWS-like service (SIB10 or SIB11 in E-UTRAN) or as a CMAS-like service (SIB12 in E-UTRAN). At this moment it is not specified which choice the RAN node should make and what this choice should be based on. Since the message contains no text, and the receiving device will use the message ID instead, I assume that it will be an ETWS-like service. - The text in red above says there is no user interface, but all entries for the new message IDs have a sentence "(Not) Settable by MMI". This is confusing; there is no MMI says the text in red. Since we are talking about devices, I would simply remove that sentence. Ivo, Thursday, 11:13: 1) Peter’s proposed wording ("CBS Message Identifier for warning message dedicated to UEs with no user interface and with ePWS functionality regardless of the type of disasters and characteristics of a disaster.") would still make the new message IDs applicable for ETWS and CMAS, which is against the scope of the WID. So, such wording is NOT OK. 2) I agree that RAN Node needs to make a choice between broadcasting as an ETWS-like service (SIB10 or SIB11 in E-UTRAN) or as a CMAS-like service (SIB12 in E-UTRAN). At this moment it is not specified which choice the RAN node should make and what this choice should be based on. However, specifying the message identifiers for ETWS is against the WID. Peter, Thursday, 11:57 To Ivo: I'm not sure there is a confusion. There are 65535 possible message IDs and only the range 4370-4399 applies to CMAS and 4351-4359 applies to ETWS. That leaves 65495 message IDs that don't belong to either. But, I don't have a strong objection against adding your words. We need to specify whether the CBC will populate the Warning Type IE (which will result in an ETWS-like broadcast) or not use this IE (which will result in CMAS-like broadcast). However, there are no Warning Type values allocated for ePWS.
C1-200443	CR 23.041#0209 Support of a stored language-independent content referenced by a warning message	SyncTechno Inc.	CR 0209 23.041 Rel-16	Ivo, Thursday, 10:22 1st sentence uses "mapping" while 2nd sentence uses "referencing". --------------------------- 2) UEs with user interface which support the ePWS language-independent content functionality and which are incapable of displaying text-based warning messages should be capable of mapping message identifiers of received warning messages to language-independent contents stored in those UEs. Such UEs should be capable of referencing a stored language-independent content to be displayed by those UEs when a warning message is received. --------------------------- Are those supposed to be the same functionality? If so, then the same term should be used. E.g. 2nd sentence can be changed as follows: "When a warning message is received, such a UE should be capable of displaying of a language-independent content stored in the UE mapped from message identifier of the received warning message." If those are not supposed to the same functionality, then the 2nd sentence was not concluded in 23.735 subclause 6.4.3. Peter, Thursday, 11:15 This is the new proposed text: "2) UEs with user interface which support the ePWS language-independent content functionality and which are incapable of displaying text-based warning messages should be capable of mapping message identifiers of received warning messages to language-independent contents stored in those UEs. Such UEs should be capable of referencing a stored language-independent content to be displayed by those UEs when a warning message is received." The words "with user interface" seem to be unnecessary. The device only needs to display language-independent content and that is mentioned in the second sentence. I think the words "with user interface" add a requirement that serves no purpose. I would remove those words.
C1-200444	CR 23.041#0210 Example of Unicode based symbols as the language independent contents mapping to disasters in NOTE	SyncTechno Inc.	CR 0210 23.041 Rel-16	Ivo, Thursday, 9:28 each unicode character required to be supported as a language-independent content needs to be listed in a normative text (not in a NOTE). Until this is done, editor's notes in 9.1.3.4.2 and 9.1.3.5.2 are valid and cannot be removed. I suggest to introduce a table with rows containing an event/disaster semantic and related unicode character code (if known, or TBD if not known) + an editor's note related to those TBDs.
C1-200446	Workplan for ePWS-CT aspects	SyncTechno Inc.	Work Plan Rel-16
C1-200765	handling of ePWS message	Samsung /Grace	CR 0211 23.041 Rel-16	The CR seems to be related to incoming LS in C1-200226. The incoming LS pertains to Rel-15, and is not part of work item ePWS.
C1-200769	discussion for concurrent broadcast for CMAS	Samsung R&D Institute UK	discussion 23.041 Rel-16	Withdrawn
C1-200770	discussion for concurrent broadcast for CMAS	Samsung R&D Institute UK	discussion 23.041 Rel-16	Withdrawn
C1-200771	discussion for concurrent broadcast for CMAS	Samsung /Grace	discussion 23.041 Rel-16	Postponed Document was LATE
SINE_5G	Peter – Main	Signalling Improvements for Network Efficiency in 5GS
C1-200513	Work plan for SINE_5G	Huawei, HiSilicon/Lin	discussion Rel-16	Revision of C1-198222
C1-200514	No retry in 4G for PDU session type related 5GSM causes	Huawei, HiSilicon/Lin	CR 1943 24.501 Rel-16
C1-200547	Correction on UE retry restriction on EPLMN	China Telecom, Huawei, HiSilicon	CR 1944 24.501 Rel-16
C1-200768	handling of PDU session authentication	Samsung/Grace	CR 2026 24.501 Rel-16
SAES16 WIs	Peter – Main	Stage-3 SAE protocol pevelopment for Rel-16
SAES16	Peter – Main	General Stage-3 SAE protocol development Only revision of agreed CRs from the ad-hoc meeting and DISC paper supporting LS possible
C1ah-200120	Correcting reference to 5GSM procedures	Ericsson / Mikael	CR 1858 24.501 Rel-16	Agreed
C1ah-200123	+CGEV amendment for indicating IP address/type change	MediaTek Inc. / JJ	CR 0681 27.007 Rel-16	Agreed Revision of C1ah-200091
SAES16-CSFB	Peter – Main	Stage-3 SAE protocol development related to Circuit Switched Fall Back
SAES16-non3GPP	Peter – Main	Stage-3 SAE protocol development related to non-3GPP access
5GProtoc16 WIs	Peter – Main	Stage-3 5GS NAS protocol development for Rel-16
5GProtoc16	General Stage-3 5GS NAS protocol development Only revision of agreed CRs from the ad-hoc meeting and DISC paper supporting LS possible
C1ah-200023	Correction for AUTHENTICATION REJECT handling	Ericsson / Ivo	CR 1785 24.501 Rel-16	Agreed
C1ah-200032	Correct “ANSDP”	Intel	CR 1793 24.501 Rel-16	Agreed
C1ah-200037	Correction to RAT's that can be scanned after E-UTRAN disable due to no voice service	Samsung/Anikethan	CR 0482 23.122 Rel-16	Agreed
C1ah-200043	Emergency service missing condition for performing registration update	Intel / Thomas	CR 0483 23.122 Rel-16	Agreed
C1ah-200044	Listing of 5GMM parameters for EMM cause #12 handling	HiSilicon, HiSilicon / Vishnu	CR 3315 24.301 Rel-16	Agreed
C1ah-200047	Declare syntactical error when both MFBR uplink and MFBR downlink equal zero	Qualcomm Incorporated	CR 1804 24.501 Rel-16	Agreed
C1ah-200059	Correction on NAS transparent container for 5G-4G interworking	Huawei, HiSilicon/Lin	CR 1811 24.501 Rel-16	Agreed
C1ah-200062	Trigger for stopping timer T3511	Huawei, HiSilicon/Lin	CR 1813 24.501 Rel-16	Agreed
C1ah-200063	Correction on T3502 for deactivated value	Huawei, HiSilicon/Lin	CR 1814 24.501 Rel-16	Agreed
C1ah-200066	EMM cause #22 for resetting registration attempt counter	Huawei, HiSilicon/Lin	CR 3322 24.301 Rel-16	Agreed
C1ah-200067	Consistent use of additional 5G security information IE	Huawei, HiSilicon/Lin	CR 1816 24.501 Rel-16	Agreed
C1ah-200069	Correction on N26 interface indicator	Huawei, HiSilicon/Lin	CR 3323 24.301 Rel-16	Agreed
C1ah-200070	Correction on reference of TS 36.304	Huawei, HiSilicon/Lin	CR 1818 24.501 Rel-16	Agreed
C1ah-200072	Inclusion of 5GSM cause in PDU session release request	Huawei, HiSilicon/Lin	CR 1820 24.501 Rel-16	Agreed
C1ah-200073	PDU session establishment reject with 5GSM #29	Huawei, HiSilicon/Lin	CR 1821 24.501 Rel-16	Agreed
C1ah-200079	Acknowledgement of UCU procedure	vivo / Yanchao	CR 1826 24.501 Rel-16	Agreed
C1ah-200100	Correction in handling of persistent PDU session during the mobility registration update	Nokia, Nokia Shanghai Bell	CR 1842 24.501 Rel-16	Agreed
C1ah-200099	Procedures for an ETWS/CMAS-capable UE in NG-RAN	Nokia, Nokia Shanghai Bell	CR 0205 23.041 Rel-16	Agreed
C1ah-200101	NAS signalling spelling correction	Ericsson / Mikael	CR 1843 24.501 Rel-16	Agreed
C1ah-200105	Correction to IEI values	Huawei, HiSilicon /Christian	CR 1846 24.501 Rel-16	Agreed
C1ah-200107	Correction to UCU procedure abnormal cases on NW side for a new TAI list	Ericsson /kaj	CR 1848 24.501 Rel-16	Agreed
C1ah-200113	Correction to the Mapped NSSAI IE	Huawei, HiSilicon /Christian	CR 1854 24.501 Rel-16	Agreed
C1ah-200118	Correction to AT+CLADN string type	MediaTek Inc. / Marko	CR 0682 27.007 Rel-16	Agreed
C1ah-200124	S-NSSAI value associated with the BO timer applied for all PLMNs	MediaTek Inc., Qualcomm Incorporated, Huawei, HiSilicon / JJ	CR 1839 24.501 Rel-16	Agreed Revision of C1ah-200096
C1ah-200127	Correcting styles	BlackBerry UK Ltd.	CR 3313 24.301 Rel-16	Agreed Revision of C1ah-200014 This is now a TEI16 change
C1ah-200129	Abnormal case for service request procedure	ZTE	CR 1797 24.501 Rel-16	Agreed Revision of C1ah-200038
C1ah-200131	S-NSSAI as a mandatory parameter for interworking with 5GS	MediaTek Inc. / JJ	CR 1836 24.501 Rel-16	Agreed Revision of C1ah-200093
C1ah-200137	Service Request for PS Data Off	ZTE	CR 1799 24.501 Rel-16	Agreed Revision of C1ah-200040
C1ah-200139	Usage of SoR-AF function	Nokia, Nokia Shanghai Bell /Jennifer	CR 0486 23.122 Rel-16	Agreed Revision of C1ah-200081
C1ah-200140	Update bullet index to include all NAS transport cases	Nokia, Nokia Shanghai Bell /Jennifer	CR 1827 24.501 Rel-16	Agreed Revision of C1ah-200082
C1ah-200141	Correction to 5GMM cause IE	Huawei, HiSilicon /Christian	CR 1847 24.501 Rel-16	Agreed Revision of C1ah-200106
C1ah-200145	Correction to the retransmission timer for the network slice-specific EAP message reliable transport procedure	Huawei, HiSilicon /Christian	CR 1852 24.501 Rel-16	Agreed Revision of C1ah-200111
C1ah-200147	Handling of unsupported SSC mode	Qualcomm Incorporated / Lena	CR 1794 24.501 Rel-16	Agreed Revision of C1ah-200033 Author indicated a revision for Sophia meeting to fix some unlcarity
C1ah-200148	Matching of SSC mode for association between an application and an existing PDU session	Qualcomm Incorporated / Lena	CR 0069 24.526 Rel-16	Agreed Revision of C1ah-200034
C1ah-200151	Clarification of forbidden PLMN list	vivo	CR 0484 23.122 Rel-16	Agreed Revision of C1ah-200053
C1ah-200154	Correction to sending of EPS NAS message container in Registration Request message	Samsung/Anikethan	CR 1789 24.501 Rel-16	Agreed Revision of C1ah-200028
C1ah-200155	Editorial correction of an input parameter for 5G NAS message integrity protection	Samsung/Anikethan	CR 1786 24.501 Rel-16	Agreed Revision of C1ah-200025
C1ah-200156	Inclusion of PDU session reactivation result error cause IE	Huawei, HiSilicon/Lin	CR 1810 24.501 Rel-16	Agreed Revision of C1ah-200056
C1ah-200157	Deletion of the rejected NSSAI for the current registration area	Huawei, HiSilicon/Lin	CR 1812 24.501 Rel-16	Agreed Revision of C1ah-200061
C1ah-200158	5GMM cause #22 for resetting registration attempt counter	Huawei, HiSilicon/Lin	CR 1815 24.501 Rel-16	Agreed Revision of C1ah-200065 Author indicated a revision for Sophia to fix a minor aspect
C1ah-200159	Inclusion of 5GSM cause in PDU session modification request	Huawei, HiSilicon/Lin	CR 1819 24.501 Rel-16	Agreed Revision of C1ah-200071
C1ah-200160	Correction on QoS rule/QoS flow synchronization	Huawei, HiSilicon/Lin	CR 1822 24.501 Rel-16	Agreed Revision of C1ah-20000074 MCC is asked to fix the missing semicolon between “session” and “and” as shown below the SMF decides to continue to use the previous configuration of the PDU session and
C1ah-200166	UE handling of invalid QoS flow description	MediaTek Inc. / JJ	CR 1835 24.501 Rel-16	Agreed Revision of C1ah-200092
C1ah-200167	UE handling of multiple QoS errors in EPS	MediaTek Inc., Qualcomm Incorporated, Ericsson / JJ	CR 1838 24.501 Rel-16	Agreed Revision of C1ah-200095
C1ah-200168	Optional IE description for release assistance indication IE	MediaTek Inc. / JJ	CR 1837 24.501 Rel-16	Agreed Revision of C1ah-200094
C1ah-200171	Correction on NAS COUNT handling for intra-N1 handover	Huawei, HiSilicon/Lin	CR 1824 24.501 Rel-16	Agreed Revision of C1ah-200077
C1ah-200172	Correction on Uplink data status IE coding	Huawei, HiSilicon/Lin	CR 1825 24.501 Rel-16	Agreed Revision of C1ah-200078 Lin, Monday, 16:01
C1ah-200175	Correction on payload container of type SMS	Nokia, Nokia Shanghai Bell	CR 1828 24.501 Rel-16	Agreed Revision of C1ah-200083
C1ah-200177	Correcting reference to NAS transparent container IE during S1 mode to N1 mode in 5GMM-CONNECTED mode	Qualcomm Incorporated	CR 1805 24.501 Rel-16	Agreed Revision of C1ah-200049
C1ah-200181	Corrections on 5GMM cause #91 "DNN not supported or not subscribed in the slice"	Nokia, Nokia Shanghai Bell	CR 1834 24.501 Rel-16	Agreed Revision of C1ah-200090
C1ah-200187	Handling multiple QoS errors during a PDU session establishment procedure	Qualcomm Incorporated, MediaTek Inc. / Amer	CR 1807 24.501 Rel-16	Agreed Revision of C1ah-200051
C1ah-200190	Correction on N26 interface indicator	Huawei, HiSilicon/Lin	CR 1817 24.501 Rel-16	Agreed Revision of C1ah-200068
C1ah-200191	Abnormal case for UL NAS TRANSPORT	ZTE	CR 1800 24.501 Rel-16	Agreed Revision of C1ah-200041
C1ah-200192	Mapped EPS bearer contexts deletion	ZTE	CR 1798 24.501 Rel-16	Agreed Revision of C1ah-200130 _________________________________________ Revision of C1ah-200039
C1ah-200196	Corrections on UE-initiated NAS transport procedure initiation	Nokia, Nokia Shanghai Bell	CR 1829 24.501 Rel-16	Agreed Revision of C1ah-200176 _________________________________________ Revision of C1ah-200084
C1ah-200201	Abnormal case handling for 5GMM cause value #90 along with a PDU SESSION MODIFICATION REQUEST message	Nokia, Nokia Shanghai Bell	CR 1840 24.501 Rel-16	Agreed Revision of C1ah-200097
C1ah-200203	Service area restrictons, condition for UE out of allowed tracking area list and RA is missing	Ericsson /kaj	CR 1853 24.501 Rel-16	Agreed There was a late request for a revision, some editorial Revision of C1ah-200170 _________________________________________ Revision of C1ah-200112
C1ah-200205	Reject non-emergency PDU session request attempt while registered for emergency services	Ericsson /kaj	CR 1845 24.501 Rel-16	Agreed Revision of C1ah-200104 There was a reservation to raise concerns to this CR in February i.e., to not sending it for CT plenary for approval. Potential issues: make the reason for change (scenario) clearer so implementers would understand the scenario when they need to implement this. to (re-)consider updating the proposal by using a reject cause different than #90 to the UE.
C1ah-200208	Correcting unimplementable condition regarding N26 interworking support detection	BlackBerry UK Ltd., Nokia, Nokia Shanghai Bell	CR 1781 24.501 Rel-16	Agreed Revision of C1ah-200183 _________________________________________ Revision of C1ah-200086
C1ah-200211	Maintain Selected EPS NAS security algorithms during N1 mode to N1 mode handover	Huawei, HiSilicon/Cristina	CR 1784 24.501 Rel-16	Agreed Revision of C1ah-200197 _________________________________________ Revision of C1ah-200019
C1ah-200212	Correction to handling of a PDU session for emergency service at SOR	MediaTek Inc. / Marko	CR 0488 23.122 Rel-16	Agreed Revision of C1ah-200204 _________________________________________ Revision of C1ah-200202 _________________________________________ Revision of C1ah-200169 _________________________________________ Revision of C1ah-200116
C1-200332	Handling of unsupported SSC mode	Qualcomm Incorporated / Lena	CR 1794 24.501 Rel-16	Revision of C1ah-200147
C1-200515	Deletion of the rejected NSSAI for the current registration area	Huawei, HiSilicon/Lin	CR 1812 24.501 Rel-16	Revision of C1ah-200157
C1-200620	Dual-registration requirements for EHPLMNs	Intel, Qualcomm Incorporated / Vivek	CR 1974 24.501 Rel-16	Postponed NEW CR for this WID, out of scope of the meeting
C1-200680	Reject non-emergency PDU session request attempt while registered for emergency services	Ericsson /kaj	CR 1845 24.501 Rel-16	Revision of C1ah-200205
C1-200719	Corrections in specifying reasons for errors	Nokia, Nokia Shanghai Bell	CR 1834 24.501 Rel-16	Revision of C1ah-200181
C1-200631	S-NSSAI as a mandatory parameter to support interworking with 5GS	MediaTek Inc., Ericsson / JJ	CR 1836 24.501 Rel-16	Revision of C1ah-200131
C1-200678	Service area restrictions, case missing for when UE is out of allowed tracking area list and RA	Ericsson /kaj	CR 1853 24.501 Rel-16	Revision of C1ah-200203 Moved from 16.2.8
5GProtoc16-non3GPP	Peter – Main	Stage-3 5GS NAS protocol development related to non-3GPP access
ATSSS	Peter – Main	CT aspects of Access Traffic Steering, Switch and Splitting support in 5G system Is TS 24.193 sufficiently stable to be sent to CT#87-e for approval?
C1-200286	ATSSS PCO parameters for 5G-RG	Ericsson / Ivo	CR 3211 24.008 Rel-16
C1-200287	Contents of ATSSS PCO parameters for 5G-RG	Ericsson / Ivo	pCR 24.193 Rel-16
C1-200288	Procedures for establishment of a PDN connection in EPS as a user-plane resource of a MA PDU session	Ericsson / Ivo	pCR 24.193 Rel-16
C1-200289	PDU session ID usage when the UE is a 5G-RG and requests establishment of a PDN connection in EPS as a user-plane resource of a MA PDU session	Ericsson / Ivo	CR 3326 24.301 Rel-16
C1-200299	5GSM capabilities for MA PDU session	Motorola Mobility, Lenovo	CR 1860 24.501 Rel-16	Revision of C1-200001 C1-200299 and C1-200565 are competing
C1-200301	MA PDU session is not supported	Motorola Mobility, Lenovo	CR 1862 24.501 Rel-16	Withdrawn Revision of C1-200004
C1-200303	MA PDU session is not supported	Motorola Mobility, Lenovo	CR 1862 24.501 Rel-16	Revision of C1-200004
C1-200313	Comparison of solutions for performance measurement function (PMF) protocol	Ericsson / Ivo	discussion Rel-16
C1-200314	Performance management function protocol	Ericsson / Ivo	pCR 24.193 Rel-16	Revision of C1-200110 Alternative to C1-200655
C1-200396	MA PDU session and one set of QoS parameters	Ericsson / Ivo	CR 1896 24.501 Rel-16
C1-200317	MA-PDU session activation in Restricted Service Area	InterDigital / Atle	pCR 24.193 Rel-16	Revision of C1-200112
C1-200404	Minor Correction to ATSSS container IE desciption	China Mobile	CR 1903 24.501 Rel-16
C1-200406	Minor Correction to Traffic descriptor component type identifier of ATSSS rules	China Mobile	pCR 24.193 Rel-16
C1-200413	Removing editor's note	Motorola Mobility, Lenovo	pCR 24.193 Rel-16	Partially overlapping with C1-200459
C1-200414	MA PDU session is not supported	Motorola Mobility France S.A.S	pCR 24.193 Rel-16
C1-200456	Discussion on handling of clause 5.2 of TS 24.193	ZTE / Joy	discussion Rel-16	Related to CRs in C1-200457, C1-200458 and C1-200459, describes two alternatives
C1-200457	Move the content of clause 5.2 out of TS 24.193	ZTE / Joy	pCR 24.193 Rel-16	Alternative 1 described in C1-200456
C1-200458	Introduction of multi-access PDU connectivity service	ZTE / Joy	CR 1920 24.501 Rel-16	Alternative 1 described in C1-200456
C1-200459	Remove editor's notes	ZTE / Joy	pCR 24.193 Rel-16	Alternative 2 described in C1-200456 Partially overlapping with C1-200413
C1-200460	Clarification on link-specific address/prefix	ZTE / Joy	pCR 24.193 Rel-16
C1-200461	Clarification on multi-homing and UL-CL funtionalities in MA PDU Session	ZTE / Joy	pCR 24.193 Rel-16
C1-200565	ATSSS Non-MPTCP traffic support	Apple	CR 1948 24.501 Rel-16	C1-200299 and C1-200565 are competing
C1-200567	ATSSS Non-MPTCP traffic support	Apple	pCR 24.193 Rel-16
C1-200627	Considering allowed NSSAI when establishing MA PDU session	MediaTek Inc., ZTE / JJ	CR 1976 24.501 Rel-16
C1-200628	UE Handling upon receipt of PDU session release command	MediaTek Inc. / JJ	CR 1977 24.501 Rel-16
C1-200629	Correction of release of user-plane resources	MediaTek Inc. / JJ	pCR 24.193 Rel-16
C1-200630	Correction of "a different PLMN"	MediaTek Inc. / JJ	pCR 24.193 Rel-16
C1-200655	ATSSS Performance Measurement Function Protocols and Procedures	Apple, Deutsche Telekom, Charter Communications	pCR 24.193 Rel-16	Revision of C1-199051 Alternative to C1-200314
C1-200747	service request for multiple access PDU session	Samsung /Grace	pCR 24.193 Rel-16
C1-200760	ATSSS 5GSM capability indication	Nokia, Nokia Shanghai Bell	CR 2024 24.501 Rel-16	Withdrawn LATE
eNS	Peter – Main	CT aspects on enhancement of network slicing
C1-200318	Cleanups of the Pending NSSAI	InterDigital / Atle	CR 1869 24.501 Rel-16	Revision of C1-200113
C1-200320	Alignment of error codes with 3GPP TS 24.501	InterDigital / Atle	CR 0683 27.007 Rel-16	Revision of C1-200315
C1-200352	Handling of S-NSSAIs in the pending NSSAI	LG Electronics / Sunhee	CR 1889 24.501 Rel-16	See also C1-200318 & 0405 & 0579 Covers the change in C1-200702. Covers the change in C1-200401. Covers the change in C1-200690
C1-200392	Clarification on HPLMN S-NSSAI	LG Electronics / Sunhee Kim	CR 1893 24.501 Rel-16	See also C1-200432. Different proposals.
C1-200393	Adding NSSAA result indication into Network slicing indication IE of the CONFIGURATION UPDATE COMMAND message	China Telecommunications	CR 1894 24.501 Rel-16
C1-200394	Adding NSSAA failed or revoked to 5GSM and 5GMM cause IE	China Telecommunications	CR 1895 24.501 Rel-16
C1-200399	Update to registration procedure due to eNS	vivo / Yanchao	CR 1899 24.501 Rel-16
C1-200401	Definition of Rejected NSSAI due to the failed and revorked NSSAA	vivo / Yanchao	CR 1901 24.501 Rel-16	Covered by C1-200352.
C1-200354	Correcting condition for Network Slice-Specific Authentication and Authorization	Samsung Electronics Polska / Ricky	CR 1890 24.501 Rel-16	Covered by C1-200697
C1-200405	Updating requirements and descriptions of NS for NSSAA	China Mobile	CR 1904 24.501 Rel-16	See also C1-200352
C1-200407	Clarification of T35xx timer during Network slice-specific authentication and authorization procedure	LG Electronics / Sunhee Kim	CR 1905 24.501 Rel-16	Covered by C1-200432
C1-200415	Network-requested PDU session release due no longer available S-NSSAI	Motorola Mobility, Lenovo, China Mobile	CR 1906 24.501 Rel-16	See also C1-200395, 0704, 0695 Three different proposals in C1-200704,0695 and C1-200415
C1-200428	Work Plan for eNS in CT1	ZTE	Work Plan Rel-16
C1-200429	Deleting Editors note regarding indefinite wait at the UE for NSSAA completion	ZTE	CR 1912 24.501 Rel-16	See also C1-200494. Different proposals. Related to the outgoing LS in C1-200434
C1-200430	UE behaviour for other causes in the rejected NSSAI during deregistration procedure	ZTE	CR 1913 24.501 Rel-16
C1-200431	Pending NSSAI update for the configured NSSAI in the CUC message	ZTE	CR 1914 24.501 Rel-16
C1-200432	Cleanup for NSSAA message and coding	ZTE	CR 1915 24.501 Rel-16	See also C1-200392. Also covers the changes in C1-200407
C1-200433	Rejected NSSAI during the initial registration procedure	ZTE	CR 1916 24.501 Rel-16
C1-200462	Name of the rejected NSSAI cause values	vivo	CR 1921 24.501 Rel-16
C1-200494	Prevention of indefinite wait for completion of the network slice-specific authentication and authorization procedure	InterDigital / Atle	CR 1929 24.501 Rel-16	See also C1-200429.
C1-200509	Requested NSSAI creation from configured NSSAI excluding pending NSSA	Huawei, HiSilicon/Lin	CR 1939 24.501 Rel-16	See also C1-200724
C1-200510	Remove mobility restriction after NSSAA	Huawei, HiSilicon/Lin	CR 1940 24.501 Rel-16	See also C1-200602
C1-200511	ENs resolution for revoked or failed NSSAA	Huawei, HiSilicon/Lin	CR 1941 24.501 Rel-16	See also C1-200683, C1-200694
C1-200512	Consistent name for NSSAA	Huawei, HiSilicon/Lin	CR 1942 24.501 Rel-16
C1-200572	EPS selection when the UE is deregistered due to NSSAA failure	Samsung/Kundan	CR 1950 24.501 Rel-16
C1-200574	Handling of NSSAA at non suppoting AMF	Samsung/Kundan	CR 1951 24.501 Rel-16
C1-200575	PDN connection establishment and NSSAA	Samsung/Kundan	CR 1952 24.501 Rel-16
C1-200576	NSSAA revocation function	Samsung/Kundan	CR 1953 24.501 Rel-16
C1-200577	Intersystem selection procedure when all allowed S-NSSAI are subject to NSSAA	Samsung/Kundan	CR 1954 24.501 Rel-16
C1-200579	Correction related the rejected NSSAI due to the failed or revoked NSSAA	SHARP	CR 1955 24.501 Rel-16	See also C1-200352.
C1-200582	Correction UE behaviour when the UE recives the pending NSSAI	SHARP	CR 1958 24.501 Rel-16
C1-200584	Correction related the rejected NSSAI	SHARP	CR 1960 24.501 Rel-16
C1-200601	Discussion on eNS	BEIJING SAMSUNG TELECOM R&D	discussion
C1-200602	Removal of the use of Service area list IE during NSSAA	BEIJING SAMSUNG TELECOM R&D	CR 1971 24.501 Rel-16	Related to DP C1-200601 See also C1-200510.
C1-200604	Re-initiation of NSSAA for a registered UE	BEIJING SAMSUNG TELECOM R&D	CR 1972 24.501 Rel-16
C1-200605	Additional triggers for deletion of pending S-NSSAI	Samsung/Anikethan	CR 1973 24.501 Rel-16
C1-200683	NW slice authentication and authorization failure and revocation	Ericsson /kaj	CR 1533 24.501 Rel-16	Revision of C1-198772 Partly overlaps with C1-200511
C1-200689	No default S-NSSAI	Nokia, Nokia Shanghai Bell	CR 1988 24.501 Rel-16
C1-200690	Missing NSSAI storage for rejected NSSAI due to the failed or revoked network slice-specific authentication and authorization	NEC	CR 1989 24.501 Rel-16	Covered by C1-200352
C1-200691	Updating NSSAI status in AMF	NEC	CR 1990 24.501 Rel-16
C1-200692	AMF updates the UE NSSAI storage after network slice-specific authentication and authorization is completed	NEC	CR 1991 24.501 Rel-16
C1-200693	NSSAI status in AMF	NEC	CR 1992 24.501 Rel-16
C1-200694	NSSAI storage at UE – pending NSSAI	NEC	CR 1993 24.501 Rel-16	See also 0511, 0683
C1-200695	Release of PDU sessions due to revocation from AAA server or re-auth failure	NEC	CR 1994 24.501 Rel-16	See also C1-200415 & 0704 Three different proposals in C1-200704,0695 and C1-200415
C1-200696	Clarification on the S-NSSAI not subject to NSSAA included in allowed NSSAI	Nokia, Nokia Shanghai Bell	CR 1995 24.501 Rel-16
C1-200697	Subscribed S-NSSAI marked as default and NSSAA	Nokia, Nokia Shanghai Bell	CR 1996 24.501 Rel-16	Covers the change in C1-200354
C1-200698	Additional conditions to the presence in the subscribed S-NSSAIs	Nokia, Nokia Shanghai Bell	CR 1997 24.501 Rel-16
C1-200702	Definition of pending NSSAI	Nokia, Nokia Shanghai Bell	CR 1999 24.501 Rel-16	Covered by C1-200352.
C1-200703	Emergency PDU session handling after NSSAA failure	Nokia, Nokia Shanghai Bell	CR 2000 24.501 Rel-16
C1-200704	Release of a PDU session due to failure/revocation in NSSAA	Nokia, Nokia Shanghai Bell	CR 2001 24.501 Rel-16	See also C1-200415 & 0695 Three different proposals in C1-200704,0695 and C1-200415
C1-200724	Request S-NSSAI pending the NW slice-specific authentication and authorization	Ericsson /kaj	CR 2004 24.501 Rel-16	See also C1-200509
Vertical_LAN	Peter – Main	CT aspects of 5GS enhanced support of vertical and LAN services TS 24.534 has been withdrawn Is TS 24.535 sufficiently stable to be sent to CT#87-e for approval Is TS 24.519 sufficiently stable to be sent to CT#87-e for approval?
Stand-alone NPN
C1-200762	Work plan for CT aspects of Vertical_LAN	Nokia, Nokia Shanghai Bell	discussion Rel-16
C1-200767	Work plan for CT aspects of Vertical_LAN	Nokia, Nokia Shanghai Bell	discussion Rel-16	Revision of C1-200762
C1-200466	Correction to Limited service state for SNPN	Huawei, HiSilicon / Vishnu	CR 0492 23.122 Rel-16
C1-200551	UE receives CAG information in SNPN access mode	Huawei, HiSilicon/Cristina	CR 1946 24.501 Rel-16
C1-200587	Correlation of SNPN entry stored in ME and USIM	Samsung/Kundan	CR 1963 24.501 Rel-16
C1-200591	Modification of the allowed CAG list	Samsung/Kundan	CR 1965 24.501 Rel-16	Postponed Document was LATE
C1-200599	Handlig of PLMN specific NID	Samsung/Kundan	CR 1969 24.501 Rel-16
C1-200333	Removal of Editor’s note on the use of the NOTIFICATION message in SNPNs	Qualcomm Incorporated / Lena	CR 1882 24.501 Rel-16
C1-200334	Updating length of NID	Qualcomm Incorporated, Ericsson, Nokia, Nokia Shanghai Bell / Lena	CR 0115 24.502 Rel-16
C1-200464	Clarification of forbidden TAI lists for SNPN	vivo	CR 1923 24.501 Rel-16
C1-200469	Clarify that access to RLOS is not supported in SNPN	Huawei, HiSilicon / Vishnu	CR 0494 23.122 Rel-16
C1-200470	Clarification of the rejected NSSAI cause value	vivo	CR 1926 24.501 Rel-16
C1-200504	Correction on 5GMM cause #74/#75 for no touching non-3GPP access	Huawei, HiSilicon/Lin	CR 1935 24.501 Rel-16
C1-200505	5GMM cause #72 not used in SNPN	Huawei, HiSilicon/Lin	CR 1936 24.501 Rel-16
C1-200506	Correction on term “non-3GPP access” used in SNPN	Huawei, HiSilicon/Lin	CR 1937 24.501 Rel-16
C1-200507	Correction on term “shared network” definition for SNPN	Huawei, HiSilicon/Lin	CR 0497 23.122 Rel-16
C1-200600	Handling of LADN infotmation when the UE operating in SNPN access mode	SHARP	CR 1970 24.501 Rel-16
C1-200681	Update SNPN key differences	Intel / Thomas	CR 1985 24.501 Rel-16
C1-200686	UE identifier for SNPN	Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Vodafone, Charter Communications, NTT DOCOMO, Ericsson	CR 0498 23.122 Rel-16
C1-200735	Correction in UE ehaviour upon receipt of 5GMM cause value #74 or #75 via a non-integrity protected NAS message	Nokia, Nokia Shanghai Bell	CR 2010 24.501 Rel-16
C1-200736	List of SNPNs for which the N1 mode capability was disabled	Nokia, Nokia Shanghai Bell	CR 0502 23.122 Rel-16
C1-200737	Introduction of SNPN-specific N1 mode attempt counters	Nokia, Nokia Shanghai Bell	CR 2011 24.501 Rel-16
C1-200738	N1 mode capability disabling and re-enabling for SNPN	Nokia, Nokia Shanghai Bell	CR 2012 24.501 Rel-16
C1-200739	#72 applicable and #31 not applicable in an SNPN	Nokia, Nokia Shanghai Bell	CR 2013 24.501 Rel-16
C1-200740	T3245 in an SNPN	Nokia, Nokia Shanghai Bell	CR 2014 24.501 Rel-16
C1-200741	Validity of the USIM for an SNPN and for a specific access type	Nokia, Nokia Shanghai Bell	CR 2015 24.501 Rel-16
C1-200742	Handling of 5GMM cause values #62 in an SNPN	Nokia, Nokia Shanghai Bell	CR 2016 24.501 Rel-16
C1-200743	No mandate to support default configured NSSAI or network slicing indication	Nokia, Nokia Shanghai Bell	CR 2017 24.501 Rel-16
C1-200744	SNN coding	Nokia, Nokia Shanghai Bell	CR 2018 24.501 Rel-16
C1-200745	5GMM cause value #74 in an SNPN with a globally-unique SNPN identity	Nokia, Nokia Shanghai Bell	CR 2019 24.501 Rel-16
C1-200746	Display of the human readable name of an SNPN	Nokia, Nokia Shanghai Bell	CR 0503 23.122 Rel-16
Public network integrated NPN
C1-200291	CAG information list storage	Ericsson / Ivo	CR 1879 24.501 Rel-16
C1-200311	CAG-ID not provided to lower layers during NAS signalling connection establishment	Ericsson / Ivo	CR 1880 24.501 Rel-16
C1-200316	CAG Information in Registration Reject	InterDigital / Atle	CR 1868 24.501 Rel-16	Revision of C1-200111
C1-200335	Signalling of CAG-ID	Qualcomm Incorporated / Lena	discussion Rel-16
C1-200336	Clarification to manual CAG selection	Qualcomm Incorporated / Lena	CR 0489 23.122 Rel-16
C1-200337	Removal of the requirement for NAS to pass the selected CAG-ID to the lower layers	Qualcomm Incorporated / Lena	CR 1883 24.501 Rel-16
C1-200398	“CAG information list” preventing selection of any available and allowable PLMN	Ericsson / Ivo	CR 1898 24.501 Rel-16
C1-200403	Clarification on CAG selection	Intel / Thomas	CR 0490 23.122 Rel-16
C1-200338	Including CAG information list in REGISTRATION ACCEPT message	Qualcomm Incorporated / Lena	CR 1884 24.501 Rel-16
C1-200451	Discussion on limited service on CAG cell	Huawei, HiSilicon/Vishnu	discussion 23.122 Rel-16
C1-200452	Limited service state on CAG cell	Huawei, HiSilicon / Vishnu	CR 0491 23.122 Rel-16
C1-200465	Deletion of all CAG IDs of a CAG cell for 5GMM cause #76	Huawei, HiSilicon / Vishnu	CR 1924 24.501 Rel-16
C1-200467	Removal of the indication of CAG-ID for N1 NAS signalling connection	Huawei, HiSilicon / Vishnu	CR 1925 24.501 Rel-16
C1-200468	Presentation of PLMN with non-CAG cells for manual selection	Huawei, HiSilicon / Vishnu	CR 0493 23.122 Rel-16
C1-200471	Removal of term CAG access control	Huawei, HiSilicon / Vishnu	CR 1927 24.501 Rel-16
C1-200508	Reset the registration attempt counter for #76 in service reject	Huawei, HiSilicon/Lin	CR 1938 24.501 Rel-16
C1-200516	Updates for Manual CAG selection	Huawei, HiSilicon / Vishnu	CR 1554 24.501 Rel-16	Revision of C1-198992 Seem to conflict with C1-200701
C1-200517	Configuration for the presentation of CAG cells for manual CAG selection	Huawei, HiSilicon / Vishnu	CR 0471 23.122 Rel-16	Revision of C1-199010
C1-200549	Clarification on Public Network Integrated NPN in TS 24.501	China Telecom	CR 1945 24.501 Rel-16
C1-200578	Discussion on requirement of sending CAG ID by UE	Samsung/Kundan	discussion 24.501 Rel-16
C1-200581	Handling of manual CAG selection procedure	Samsung/Kundan	CR 1957 24.501 Rel-16
C1-200586	CAG only UE and Manual PLMN selection	Samsung/Kundan	CR 1962 24.501 Rel-16
C1-200589	Handling of a CAG UE at non supporting AMF	Samsung/Kundan	CR 1964 24.501 Rel-16
C1-200688	CAG information towards the lower layers for paging	Nokia, Nokia Shanghai Bell	CR 1567 24.501 Rel-16	Revision of C1-196737
C1-200700	Manual CAG selection	Nokia, Nokia Shanghai Bell	CR 0499 23.122 Rel-16
C1-200701	Triggering mobility registration update due to manual CAG selection	Nokia, Nokia Shanghai Bell	CR 1998 24.501 Rel-16	Seem to conflict with C1-200516
C1-200728	Rejection of non-emergency PDU session establishment with 5GMM cause #76	Nokia, Nokia Shanghai Bell	CR 2007 24.501 Rel-16
C1-200729	Handling of a UE with an emergency PDU session in terms of CAG	Nokia, Nokia Shanghai Bell	CR 2008 24.501 Rel-16
C1-200730	Determination of CAG cell	Nokia, Nokia Shanghai Bell	CR 0500 23.122 Rel-16
C1-200731	Discussion to manual CAG selection	Ericsson / Ivo	discussion Rel-16
C1-200732	Manual CAG selection	Ericsson / Ivo	CR 0501 23.122 Rel-16
C1-200733	Manual CAG selection – providing HRNN	Ericsson / Ivo	CR 2009 24.501 Rel-16
Time sensitive communication
C1-200329	Support for per-stream filtering and policing	Intel / Thomas	other Rel-16
C1-200330	Support for traffic forwarding	Intel, Nokia, Nokia Shanghai Bell	other Rel-16
C1-200331	Additional LLDP parameters	Intel / Thomas	other Rel-16
C1-200339	Update of text on time synchronization	Qualcomm Incorporated / Lena	CR 1885 24.501 Rel-16
C1-200411	Port management corrections	Intel / Thomas	other Rel-16
C1-200493	Definition alignment for UE-DS-TT residence time	vivo	CR 1928 24.501 Rel-16
C1-200564	Establish PDU session to transfer port management information containers	Huawei, HiSilicon/Cristina	CR 1947 24.501 Rel-16	CRs in C1-200685, C1-200290, C1-200564 conflict
C1-200566	Correction on port management message direction	Huawei, HiSilicon/Cristina	pCR 24.519 Rel-16
C1-200570	Add PSFP parameters	Huawei, HiSilicon/Cristina	pCR 24.519 Rel-16
C1-200571	Correction for the wrongly implemented CR1963r1	Huawei, HiSilicon/Cristina	CR 1949 24.501 Rel-16
C1-200573	Exchange port management information container through N4 Session Level Reporting procedure	Huawei, HiSilicon/Cristina	pCR 24.519 Rel-16
C1-200687	Port management IE format and length updates	Intel / Thomas	other Rel-16
C1-200706	Resolving editor’s notes on reliable transmission	Nokia, Nokia Shanghai Bell	pCR 24.519 Rel-16
C1-200708	Duplicated Ethernet port parameters in case of validation and generation of LLDP frames processed centrally at NW-TT	Nokia, Nokia Shanghai Bell	pCR 24.519 Rel-16
C1-200734	Clarification on calculation of the residence time spent within the 5G system	Intel / Thomas	pCR 24.535 Rel-16
5G_CioT	Peter – Main	CT aspects of Cellular IoT support and evolution for the 5G System
C1-200298	Update of Reading coverage enhancement status +CRCES for Connection to 5G Core Network	BlackBerry UK Limited	CR 0684 27.007 Rel-16	Revision of C1-200116
C1-200328	Removal of EN and additional abnormal case for cause #31	Samsung/Anikethan	CR 1881 24.501 Rel-16
C1-200351	Removal of EN and additional abnormal case for cause #31	Samsung/Anikethan	CR 3330 24.301 Rel-16
C1-200368	Addition of MT-EDT support indication	Ericsson, Qualcomm Incorporated, OPPO / Mikael	CR 3332 24.301 Rel-16
C1-200383	Resolve Editor´s Notes on NB-N1 mode extended NAS timers for CE	Ericsson / Mikael	CR 1891 24.501 Rel-16
C1-200384	Resolve Editor´s Notes on WB-N1 mode extended NAS timers for CE	Ericsson / Mikael	CR 1892 24.501 Rel-16
C1-200397	“MO exception data” access category	Ericsson / Ivo	CR 1897 24.501 Rel-16	C1-200397, C1-200421 and C1-200677 overlap, all related to incoming LS in C1-200227
C1-200355	Applicability of UE specific DRX Parameter for NB-S1 mode Indicator	Vodafone GmbH	CR 3331 24.301 Rel-16	C1-200355, C1-200417, C1-200498 overlapping, All related to the incoming LS in C1-200237
C1-200400	Stop T3565 upon connection resumption	vivo / Yanchao	CR 1900 24.501 Rel-16	Corrected agenda
C1-200417	Support for UE specific DRX for NB-S1 mode	Qualcomm Incorporated, Ericsson / Amer	discussion Rel-16	C1-200355, C1-200417, C1-200498 overlapping, All related to the incoming LS in C1-200237
C1-200418	Support for the signalling of the capability for receiving WUS assistance information	Qualcomm Incorporated / Amer	CR 1907 24.501 Rel-16
C1-200419	Handling of user-plane resources for NB-IoT UEs having at least two PDU sessions	Qualcomm Incorporated, Ericsson / Amer	CR 1672 24.501 Rel-16	Revision of C1-198585 C1-200419 and C1-200497 overlap
C1-200420	5GSM congestion timers apply to data transfer over control plane	Qualcomm Incorporated / Amer	CR 1908 24.501 Rel-16
C1-200421	Definition of a new access category for MO exception data	Qualcomm Incorporated / Amer	CR 1909 24.501 Rel-16	C1-200397, C1-200421 and C1-200677 overlap, all related to incoming LS in C1-200227
C1-200424	Update of +CNMPSD for NR	BlackBerry UK Ltd.	CR 0685 27.007 Rel-16
C1-200435	UE behaviour when T3447 running	ZTE	CR 1917 24.501 Rel-16
C1-200495	Enhancement on CPSR for CIoT CP data transport	Huawei, HiSilicon, Vodafone, ZTE, China Mobile, China Telecom, CATT/Lin	CR 1701 24.501 Rel-16	Revision of C1-198581
C1-200496	Ciphering and deciphering handling of CPSR message	Huawei, HiSilicon/Lin	CR 1930 24.501 Rel-16
C1-200497	UE-requested user-plane resources release in NB-N1 mode	Huawei, HiSilicon/Lin	CR 1931 24.501 Rel-16	C1-200419 and C1-200497 overlap
C1-200498	NAS evaluation on options for UE specific DRX for NB-IoT	Huawei, HiSilicon/Lin	discussion Rel-16	C1-200355, C1-200417, C1-200498 overlapping, All related to the incoming LS in C1-200237
C1-200500	Discussion on truncated 5G-S-TMSI over NAS	Huawei, HiSilicon/Lin	discussion Rel-16
C1-200501	Truncated 5G-S-TMSI over NAS	Huawei, HiSilicon/Lin	CR 1932 24.501 Rel-16
C1-200502	AMF behavior on stop T3448	Huawei, HiSilicon/Lin	CR 1933 24.501 Rel-16
C1-200503	No SMS in payload container IE in CPSR message	Huawei, HiSilicon/Lin	CR 1934 24.501 Rel-16
C1-200580	Stopping of T3513 after connection resume for user plane CIoT 5GS optimization	Samsung/Mahmoud	CR 1956 24.501 Rel-16
C1-200583	5G-GUTI reallocation after resume from 5GMM-IDLE mode with suspend indication due to paging	Samsung/Mahmoud	CR 1959 24.501 Rel-16
C1-200585	Adding an editor’s note for suspend indication due to user plane CIoT 5GS optimization	Samsung/Mahmoud	CR 1961 24.501 Rel-16
C1-200588	Ambiguity in the suspend indication from lower layers to the NAS	Samsung/Mahmoud	discussion 24.501 Rel-16
C1-200592	Recovery from fallback for UEs using CP CIoT optimization	Samsung/Mahmoud	CR 1966 24.501 Rel-16
C1-200593	Service area restrictions for UEs using CIoT 5GS optimization	Samsung/Mahmoud	CR 1967 24.501 Rel-16
C1-200594	Adding reference to TS 24.501 for exception data reporting	Samsung/Mahmoud	CR 0047 24.368 Rel-16
C1-200618	Value range of UE specific DRX in NB-S1 mode	Vodafone GmbH	CR 3212 24.008 Rel-16
C1-200626	Indication of change in the use of enhanced coverage	BEIJING SAMSUNG TELECOM R&D	CR 1975 24.501 Rel-16
C1-200658	Correction to UL CIoT user data container not routable or not allowed to be routed	Ericsson /kaj	CR 1978 24.501 Rel-16
C1-200661	Single downlink data only indication and release of NAS signalling connection	Ericsson /kaj	CR 1979 24.501 Rel-16
C1-200663	PDU session status with control plane service request message	Ericsson /KAJ	CR 1980 24.501 Rel-16
C1-200666	Service gap control timer corrections	Ericsson /kaj	CR 3335 24.301 Rel-16
C1-200669	Service gap control, correction when to start service gap control timer in UE and NW	Ericsson /kaj	CR 1981 24.501 Rel-16
C1-200672	Clarification of control plane service request message options	Ericsson /kaj	CR 1982 24.501 Rel-16
C1-200675	CIoT user data container in CPSR message not forwarded	Ericsson /kaj	CR 1743 24.501 Rel-16	Revision of C1-198950
C1-200677	UAC updates for NB-IoT to include "MO exception data"	DOCOMO Communications Lab.	CR 1983 24.501 Rel-16	C1-200397, C1-200421 and C1-200677 overlap, all related to incoming LS in C1-200227
C1-200679	Clarification on the use of exception data reporting	DOCOMO Communications Lab.	CR 1984 24.501 Rel-16
C1-200682	MO exception data for NB-IoT in 5G	DOCOMO Communications Lab., Ericsson	CR 1986 24.501 Rel-16	Withdrawn CR was withdrawn as it used a CR number requested for 24.501 instead of 24.368
C1-200773	MO exception data for NB-IoT in 5G	DOCOMO Communications Lab., Ericsson	CR 0048 24.368 Rel-16	CR was originally provided as C1-200682, on time, new CR number was needed for 24.368
5WWC	Peter – Main	CT aspects on wireless and wireline convergence for the 5G system architecture
C1-200276	Secondary authentication and W-AGF acting on behalf of FN-RG	Ericsson / Ivo	CR 1689 24.501 Rel-16	Revision of C1-198161
C1-200277	EAP-5G handling and transport of NAS messages for wireline access	Ericsson / Ivo	CR 0110 24.502 Rel-16	Revision of C1-198159
C1-200278	SUCI used by W-AGF acting on behalf of FN-RG	Ericsson / Ivo	CR 1870 24.501 Rel-16	Conflict with C1-200754 in subclause 5.3.2
C1-200279	Resolving editor's note on W-AGF acting on behalf of FN-RG not using the "null integrity protection algorithm" 5G-IA0	Ericsson / Ivo	CR 1871 24.501 Rel-16
C1-200280	Resolving editor's note on service area restrictions in case of FN-BRG	Ericsson / Ivo	CR 1872 24.501 Rel-16
C1-200281	Resolving editor's note in forbidden wireline access area	Ericsson / Ivo	CR 1873 24.501 Rel-16
C1-200282	Wireline 5G access network and wireline 5G access	Ericsson / Ivo	CR 1874 24.501 Rel-16
C1-200283	PEI clean up	Ericsson / Ivo	CR 1875 24.501 Rel-16
C1-200284	Alignment for stop of enforcement of mobility restrictions in 5G-RG and W-AGF acting on behalf of FN-CRG	Ericsson / Ivo	CR 1876 24.501 Rel-16
C1-200285	Introduction of GCI and GLI	Ericsson / Ivo	CR 1877 24.501 Rel-16
C1-200297	Removal of editor notes	BlackBery UK Ltd. Motorola Mobility, Lenovo	CR 0114 24.502 Rel-16	Revision of C1-200114
C1-200300	Additional QoS Information in an untrusted non-3GPP network	Motorola Mobility, Lenovo	CR 0111 24.502 Rel-16	Revision of C1-200002
C1-200302	Removal of editor's notes for N5CW device	Motorola Mobility, Lenovo	CR 0112 24.502 Rel-16	Revision of C1-200005
C1-200304	Removal of an editor's note	Motorola Mobility, Lenovo, BlackBerry UK Ltd.	CR 0113 24.502 Rel-16	Revision of C1-200006
C1-200305	PDU session handling for N5CW device	Motorola Mobility, Lenovo	CR 1641 24.501 Rel-16	Revision of C1-200007
C1-200425	Correct reference	BlackBerry UK Ltd.	CR 6410 24.229 Rel-16
C1-200426	Enabling mobility with (emergency) sessions/connections between the (trusted) non-3GPP access network connected to the 5GCN and the E-UTRAN	BlackBerry UK Ltd.	CR 1910 24.501 Rel-16
C1-200454	ACS information via DHCP	ZTE / Joy	CR 1919 24.501 Rel-16
C1-200455	LADN service does not apply for RG connected to 5GC via wireline access	ZTE / Joy	CR 0070 24.526 Rel-16
C1-200518	Work plan for the CT1 part of 5WWC	Huawei, HiSilicon /Christian	discussion Rel-16
C1-200754	Registration of N5GC devices via wireline access	Nokia, Nokia Shanghai Bell,Charter Communications	CR 2020 24.501 Rel-16	Conflict with C1-200278 in subclause 5.3.2
C1-200755	Support of authentication and registration of N5GC devices via wireline access	Nokia, Nokia Shanghai Bell,Charter Communications	CR 0116 24.502 Rel-16
C1-200756	Corrections on EUI-64 as PEI	Nokia, Nokia Shanghai Bell	CR 2021 24.501 Rel-16
C1-200757	Corrections on N5CW support	Nokia, Nokia Shanghai Bell	CR 2022 24.501 Rel-16
C1-200758	Supporting IPTV NAS impacts	Nokia, Nokia Shanghai Bell	CR 2023 24.501 Rel-16	Withdrawn LATE
C1-200759	Supporting IPTV via wireline access	Nokia, Nokia Shanghai Bell	CR 0117 24.502 Rel-16	Withdrawn LATE
C1-200761	SUPI and SUCI for legacy wireline access	Nokia, Nokia Shanghai Bell	CR 0118 24.502 Rel-16
PARLOS	Lena – Breakout	CT aspects of System enhancements for Provision of Access to Restricted Local Operator Services by Unauthenticated UEs
C1-200322	Factoring in T3346 during access to RLOS	Samsung R&D Institute India	CR 3327 24.301 Rel-16
C1-200476	Support of restriction on access to RLOS	Nokia, Nokia Shanghai Bell /Jennifer	CR 3333 24.301 Rel-16	Lena, Thursday, 9:06 Editorial comments: the MCC of the serving PLMN network name” should be “the MCC of the serving PLMN” “For UE with USIM” should be “if the UE has a valid USIM” Ricky, Thursday, 12:48 “the UE shall verify that the MCC of the serving PLMN network name is present in the list of RLOS allowed MCCs configured in the UE” should be “the UE shall verify that the MCC of the serving PLMN network name is present in the list of RLOS allowed MCCs configured in the ME” given that the white list is maintained on the ME according to the SA3 requirement. Ivo, Thursday, 14:54 In "the MCC of the serving PLMN network name", what is "serving PLMN network name"? Is it the same as "the MCC of the PLMN ID of the serving PLMN"? If so, then I prefer the updated term.
C1-200477	Support of restriction on access to RLOS	Nokia, Nokia Shanghai Bell /Jennifer	CR 0495 23.122 Rel-16	Lena, Thursday, 9:07: the added text about requesting user’s consent is not needed. CT1 has agreed an AT command which allows to set/unset user consent (see TS 27.007 subclause 8.80), so user consent does not need to be requested every time a PLMN is selected. Ivo, Thursday, 14:59 Issue with the use of “allowable” in "If registration cannot be achieved because no PLMNs are available and allowable, and if no PLMN offering access to RLOS has been found, or none of the PLMNs offering access to RLOS is allowable according to RLOS allowed MCC list configured in the USIM (see 3GPP TS 31.102 [40]) or in the ME (see 3GPP TS 24.368 [50])” . The term "allowable PLMN" is defined in 23.122 as below and has nothing to do with the RLOS allowed MCC list.
C1-200478	NAS configuration on access to RLOS	Nokia, Nokia Shanghai Bell /Jennifer	CR 0046 24.368 Rel-16	Lena, Thursday, 9:07: The DDF needs to be updated. Ricky, Thursday, 12:34 1) “5.10zg /<X>/RLOSPreferredPLMNList/<X>” should be “5.10zg /<X>/RLOSAllowedMCCList/<X>” 2) The SA3 requirement talks only about preconfiguring the white list either at the time of ME manufacturing or hardcoding with {310, 311, 312, 313, 314, 315, 316}. So is there a need for an MO parameter, if this is purely pre-configuration? Ivo, Thursday, 15:02 - in 5.10zf last paragraph: it is not clear where is stage-1 or stage-2 requirement related to "the interior node <X> that holds the following MCC leaf values {310, 311, 312, 313, 314, 315, 316}. ". If there is such stage-1 or stage-2 requirement, then the requirement should be enforced in 23.122, without the need to configure the UE. - same comment applies to last paragraph of 5.10zh.
C1-200479	Authentication and security handling for RLOS	Nokia, Nokia Shanghai Bell /Jennifer	CR 3334 24.301 Rel-16	Ivo, Thursday, 15:05 In 5.4.3.3: the UE has to be attached for RLOS, in order to be able to establish an RLOS PDN connection. This is different from emergency PDN connection which can be established even when the UE is non-emergency non-RLOS registered. If change is needed, it would be better to add "or is attached for access to RLOS".
C1-200480	Manual network selection procedure for access to RLOS	Nokia, Nokia Shanghai Bell /Jennifer	CR 0496 23.122 Rel-16
C1-200748	Detach before RLOS and Emergency Attach	MediaTek / Marko	CR 3338 24.301 Rel-16	Ricky, Thursday, 13:01 1) TEI16 needs to be added as WIC on the coversheet as the “may detach locally and initiate attach for emergency bearer services” is not a change related to RLOS 2) OK to add the clarification, but surely it is obvious that the UE will perform a local detach, as it is unable to perform the detach procedure by explicit signalling since the UE in these states is unable to perform the detach procedure (as stated in the cover sheet)
C1-200763	De-registration before initial registration for RLOS and Emergency	MediaTek / Marko	CR 2025 24.501 Rel-16	Withdrawn
5G_eLCS (CT4)	Peter – Main	CT aspects of Enhancement to the 5GC LoCation Services Is TS 24.571 sufficiently stable to be sent to CT#87-e for approval
C1-200568	Adding UE initiated LCS service operations	CATT/Scott	pCR 24.571 Rel-16
C1-200569	LCS messages and coding	CATT/Scott	pCR 24.571 Rel-16
V2XAPP	Lena – Breakout	CT aspects of V2XAPP Is TS 24.486 sufficiently stable to be sent to CT#87-e for information and/or approval
C1-200519	Work plan for the CT1 part of V2XAPP	Huawei, HiSilicon /Christian	discussion Rel-16
C1-200522	Latest reference version of draft TS 24.486	Huawei, HiSilicon /Christian	draft TS 24.486 Rel-16
C1-200528	Application level location tracking procedure	Huawei, HiSilicon /Christian	pCR 24.486 Rel-16
C1-200529	V2X message delivery procedure	Huawei, HiSilicon /Christian	pCR 24.486 Rel-16
C1-200530	V2X service discovery procedure	Huawei, HiSilicon /Christian	pCR 24.486 Rel-16
C1-200532	V2X sevice continuity procedure	Huawei, HiSilicon /Christian	pCR 24.486 Rel-16
C1-200533	General on provisioning of parameters	Huawei, HiSilicon /Christian	pCR 24.486 Rel-16
C1-200534	V2X USD provisioning	Huawei, HiSilicon /Christian	pCR 24.486 Rel-16	Withdrawn
C1-200535	PC5 parameters provisioning	Huawei, HiSilicon /Christian	pCR 24.486 Rel-16	Withdrawn
C1-200619	Structure and data semantics for application level location tracking procedure	Huawei, HiSilicon /Christian	pCR 24.486 Rel-16
C1-200621	Structure and data semantics for V2X message delivery procedure	Huawei, HiSilicon /Christian	pCR 24.486 Rel-16
C1-200622	Structure and data semantics for V2X service discovery procedure	Huawei, HiSilicon /Christian	pCR 24.486 Rel-16
C1-200623	Structure and data semantics for V2X UE registration procedure	Huawei, HiSilicon /Christian	pCR 24.486 Rel-16
C1-200624	Structure and data semantics for V2X UE de-registration procedure	Huawei, HiSilicon /Christian	pCR 24.486 Rel-16
eV2XARC	Lena – Breakout	CT aspects of eV2XARC Is TS 24.587 sufficiently stable to be sent to CT#87-e for approval? Is TS 24.588 sufficiently stable to be sent to CT#87-e for approval?
C1-200292	UE policies for V2X communication over PC5	Ericsson / Ivo	pCR 24.588 Rel-16	CRs C1-200391, C1-200389, C1-200388, C1-200386 influence coding in CR C1-200292
C1-200293	Updates of configuration parameters for V2X communication over Uu	Ericsson / Ivo	pCR 24.587 Rel-16	Rae, Thursday, 10:18 There is no stage-2 requirement for the authorization policy for Uu interface. In EPS the authorization policy for Uu is related to MBMS, but for eV2XARC there is no MBMS so there is no need for special authorization policy for V2X Uu.
C1-200294	V2X communication over Uu	Ericsson / Ivo	pCR 24.587 Rel-16
C1-200295	UE policies for V2X communication over Uu	Ericsson / Ivo	pCR 24.588 Rel-16
C1-200321	Precedence order between V2X configuration parameters	LG Electronics	pCR 24.587 Rel-16	Withdrawn Revision of C1-198404
C1-200324	Direct link establishment procedure update based on SA3 LS	OPPO / Rae	pCR 24.587 Rel-16	Yanchao, Thursday, 12:46 In Table 7.3.2.1.1, the length of sequence number should be 1 octet Ivo, Thursday, 15:07 - "if the result of the above check is yes" -> "If the request is accepted" - it is not clear how the UE figures out whether "the security association with the initiating UE is successful". Maybe an editor's note is needed.
C1-200325	Remove the FFS on non-IP	OPPO / Rae	pCR 24.587 Rel-16
C1-200326	Decoding on V2X service ID and application ID	OPPO / Rae	pCR 24.587 Rel-16	Ivo, Thursday, 15:09 - V2X service identifier is PSID or ITS-AID, and the coding should point to ISO TS 17419 ITS-AID AssignedNumbers : http://standards.iso.org/iso/ts/17419/TS17419%20Assigned%20Numbers/TS17419_ITS-AID_AssignedNumbers.pdf similarly as done in V2X in EPS. - V2X service identifier cannot be out-of-scope since it is used to distinguish different formattings of V2X messages
C1-200327	Keep alive procedure	OPPO / Rae	pCR 24.587 Rel-16
C1-200349	Security establishment for PC5 unicast link	Qualcomm Incorporated / Lena	pCR 24.587 Rel-16	Rae, Thursday, 10:24 For the deletion of FFS on Non-IP, I think this part can be left to my C1-200325 since this CR covers security issues and has a lot of information already. For the security procedures, I cannot find SA3 V2X TS. I agree that the security procedures in principle may be the same with what defined in EPS. But is it better to wait for SA3 TS? Yanchao, Thursday, 13:09 1) The length of sequence number should be 1 octet. 2) Which UE can trigger the PC5 unicast link authentication procedure: the initiating UE, the target, or both? 3) Which UE can trigger the PC5 unicast link security mode control procedure: the initiating UE, the target, or both? Ivo, Thursday, 15:10 It is too early to bring security in CT1 specs - no version of 33.536 exists yet and there are no security details available in 23.287 either.
C1-200385	Adding abnormal case on the network side	Huawei, HiSilicon / Chen	pCR 24.587 Rel-16	Ivo, Thursday, 15:12 In case REJECT is not delivered, the PCF should wait for retransmission of REQUEST. If the procedure is aborted, the PCF will need to handle any retransmitted REQUEST again.
C1-200386	Correction for the list of the V2X services authorized for PPPR over V2X PC5 in E-UTRA	Huawei, HiSilicon / Chen	pCR 24.587 Rel-16	CRs C1-200391, C1-200389, C1-200388, C1-200386 influence coding in CR C1-200292
C1-200387	Correction for the list of V2X service identifier to PDU session parameters mapping rules over V2X Uu	Huawei, HiSilicon / Chen	pCR 24.587 Rel-16
C1-200388	Correction for the list of V2X service identifier to Tx profiles mapping rules over V2X PC5	Huawei, HiSilicon / Chen	pCR 24.587 Rel-16	CRs C1-200391, C1-200389, C1-200388, C1-200386 influence coding in CR C1-200292
C1-200389	Correction for the list of V2X service identifier to V2X E-UTRA frequency mapping rules over V2X PC5	Huawei, HiSilicon / Chen	pCR 24.587 Rel-16	CRs C1-200391, C1-200389, C1-200388, C1-200386 influence coding in CR C1-200292
C1-200390	Resolution of the editor's note on details about PC5 unicast link establishment procedure not accepted by the target UE	Huawei, HiSilicon / Chen	pCR 24.587 Rel-16	Ivo, Thursday, 15:14 Table 8.4.x.1 is not aligned with Figure 8.4.x.1 on fields in 2nd octet.
C1-200391	Resolution of the editor's note on validity timer	Huawei, HiSilicon / Chen	pCR 24.587 Rel-16	C1-200391, C1-200389, C1-200388, C1-200386 influence coding in CR C1-200292
C1-200350	PC5 unicast link keep-alive procedure	Qualcomm Incorporated / Lena	pCR 24.587 Rel-16	Yanchao, Thursday, 13:00 1) The length of sequence number IE should be 1 octet. 2) Can the keep-alive procedure be triggered by upper layers? 3) The stop of T5xxx in Figure 6.1.2.x.2 should be removed because the procedure can also be triggered when T5xxx expires
C1-200437	PC5 unicast link release procedure	vivo	pCR 24.587 Rel-16	Ivo, Thursday, 15:15 - unnecessary capitalization in “PC5 Signalling Protocol procedures" - in 6.1.2.X.3 + 6.1.2.X.4: why is the release of the PC5 unicast link after DIRECT LINK RELEASE ACCEPT optional?
C1-200438	Encoding of direct link release messages and parameters	vivo	pCR 24.587 Rel-16	Ivo, Thursday, 15:19 - remove unncessary capitalization in "Sequence Number" + "Release Reason" + "Release Reason Content" - incorrect styles in 7.3.X.1, message type - in Table 7.3.X.1.1, length of Release Reason should be 1 octet - in Table 7.3.X.1.1 + Table 7.3.y.1, length of sequence number should be 1 octet - Table 8.4.x.1 is inconsistent on length of Release Reason value - Figure 8.4.x.1 is not aligned with Table 8.4.x.1 on fields in 2nd octet
C1-200439	PC5 unicast link identifier update procedure	vivo	pCR 24.587 Rel-16	Ivo, Thursday, 15:22 - 6.1.2.x.2 bullet a) is not an English sentence - unnecessary capitalization in "the Security Information" - in 6.1.2.x.3, 2nd paragraph should be normative
C1-200440	Updates to the link modification procedure	vivo	pCR 24.587 Rel-16
C1-200441	Encoding of direct link modification messages and parameters	vivo	pCR 24.587 Rel-16	Ivo, Thursday, 15:25 V2X service identifier can be a type 3 IE, with a total length of 5 octets in TV formatting (rather than type 4 IE with total length of 6 octets in TLV formatting).
C1-200520	Work plan for the CT1 part of eV2XARC	Huawei, HiSilicon /Christian	discussion Rel-16
C1-200521	Latest reference version of draft TS 24.587	Huawei, HiSilicon /Christian	draft TS 24.587 Rel-16
C1-200525	Resolution of the editor's notes on precedence of V2X configuration parameters	Huawei, HiSilicon /Christian	pCR 24.587 Rel-16
C1-200536	Operations for broadcast mode and groupcast mode communication over PC5	Huawei, HiSilicon /Christian	pCR 24.587 Rel-16	Ivo, Thursday, 15:26 - broken styles of headlines - wrong style of A) bullet list - "Then, there can be two conditions:" seems strange - "according to the mapping rules specified in subclause 5.2.3" - which mapping rules? There are several. - what is meant by “build a new context for the destination layer-2 ID"? - "set up a new PC5 QoS rule, the PC5 QoS rule contains:" and "a set of packet filters" - which packet filters? - 6.1.3.2.4 - the bullet list starting with 3) should start with 1)
C1-200537	Data transmission over PC5 unicast link	Huawei, HiSilicon /Christian	pCR 24.587 Rel-16	Ivo, Thursday, 15:29 - "The pair of layer-2 IDs shall be associated with a PC5 unicast link context." - which pair? - 6.1.2.X - why is providing source layer-2 ID and destination layer-2 ID to lower layers optional? Shouldn't it be conditional or mandatory?
C1-200538	Introduction of “PC5 Unicast Link Identifier Update Procedure”	InterDigital Communications	pCR 24.587 Rel-16	Yanchao, Thursday, 13:49 According to S2-2000953, if the target UE has the privacy configuration, it will update its identifier after receiving the link id update request message In clause 6.1.2.4.3, bullet f), g) and h) are not the IEs included in the link update accept message. These are the UE’s behaviours. Same as the bullet e) and f) in subclause 6.1.2.4.4. The format of figure 6.1.2.4.2 is not right. The number of the timers are not defined yet.
C1-200595	Triggering service request procedure for V2X communication over PC5 interface	LG Electronics / SangMin	CR 1968 24.501 Rel-16
C1-200596	Discussion on multiple V2X services during the direct link establishment procedure	LG Electronics / SangMin	discussion Rel-16	Yanchao, Thursday, 13:42 Vivo does not agree with Proposal 1 for the following reasons: We see no strong reason from the real V2X services that have to support multiple V2X service during the PC5 link establishment procedure. The current link modification procedure can add new V2X service to the existing PC5 link. Inclusion of multiple V2X service identifier to the direct link establishment request will introduce lots complexity in the PC5 link establishment procedure: If multiple V2X service are included in one link establishment request message, it needs to convey the relationship between V2X service and the PQFIs; The link establishment accept message has to be extended to include the V2X service ID that target UE accepts; According to the descriptions in TS23.287, if the UE has the interest on the announcing V2X service, it responds with a accept message. (This mean only one V2X service). If multiple V2X service are include, there is no SA2 requirement that the target UE are interested on all the V2X service or some of the V2X servicess. If multiple V2X service are included in a establishment request message, the UE has to ensure that all the V2X service ID are linked to the same UE application layer ID.
C1-200597	Multiple V2X service identifiers in DIRECT LINK ESTABLISHMENT REQUEST message	LG Electronics / SangMin	pCR 24.587 Rel-16	Ivo, Thursday, 15:36 - 6.1.2.2.2 "V2X service identifier(s)" -> "one or more V2X service identifier(s)" - 6.1.2.2.3 "it is interested in the V2X service(s) identified by the V2X service identifiers IE" - can you please clarify whether the target UE has to be interested in *all of them* or *at least one of them*. If *at least one of them*, then DIRECT LINK ESTABLISHMENT ACCEPT should indicate which of the V2X service identifier(s) indicated in the DIRECT LINK ESTABLISHMENT REQUEST are interesting for the target UE.
C1-200598	Association between V2X service id and PC5 QoS flow description	LG Electronics / SangMin	pCR 24.587 Rel-16	Ivo, Thursday, 15:37 V2X services can be added to and removed from the PC5 unicast link. It is not clear how to identify the V2X service in such case, given that the coding refers solely to DIRECT LINK ESTABLISHMENT REQUEST.
C1-200603	Latest reference version of draft TS 24.588	LG Electronics / SangMin	draft TS 24.588 Rel-16
C1-200632	PC5 unicast link keep-alive procedure – additions to C1-200350	Apple	pCR 24.587 Rel-16
C1-200652	Clean-up for TS 24.588	LG Electronics / SangMin	pCR 24.588 Rel-16
RACS (CT4 lead)	Peter – Main	CT aspects of optimizations on UE radio capability signaling
C1-200340	RACS CT work plan	Qualcomm Incorporated / Lena	discussion Rel-16
C1-200341	Proposed way forward on remaining CT1 items for RACS	Qualcomm Incorporated / Lena	discussion Rel-16
C1-200342	UE radio capability ID assignment via GUTI reallocation procedure	Qualcomm Incorporated / Lena	CR 3328 24.301 Rel-16
C1-200343	Finalizing provisioning of manufacturer-assigned UE radio capability IDs at the UE	Qualcomm Incorporated / Lena	CR 0045 24.368 Rel-16
C1-200344	Removal of Editor’s note on applicability of RACS to SNPNs	Qualcomm Incorporated / Lena	CR 1886 24.501 Rel-16
C1-200345	Finalizing the encoding of the UE radio capability ID	Qualcomm Incorporated / Lena	CR 1887 24.501 Rel-16	Delete the same Editor’s note as C1-200723, plus contains more changes
C1-200346	UE radio capability ID deletion upon Version ID change	Qualcomm Incorporated / Lena	CR 1888 24.501 Rel-16
C1-200402	RACS not apply for non-3GPP access	vivo / Yanchao	CR 1902 24.501 Rel-16	Overlaps with C1-200725 which covers more changes.
C1-200347	UE radio capability ID deletion upon Version ID change	Qualcomm Incorporated / Lena	CR 3329 24.301 Rel-16
C1-200463	Clarification of the cause of start of T3550	vivo	CR 1922 24.501 Rel-16
C1-200720	UE behaviour upon receipt of a UE radio capability ID deletion indication	Nokia, Nokia Shanghai Bell	CR 2002 24.501 Rel-16
C1-200722	UE behaviour upon receipt of a UE radio capability ID deletion indication	Nokia, Nokia Shanghai Bell	CR 3336 24.301 Rel-16
C1-200723	Format of the UE radio capability ID	Nokia, Nokia Shanghai Bell	CR 2003 24.501 Rel-16	CR deletes an Editor’s note which is also deleted by C1-200345
C1-200725	RACS not applicable for non-3GPP access	Nokia, Nokia Shanghai Bell	CR 2005 24.501 Rel-16	Overlaps with C1-200402. Covers more required changes but missed the change to subclause 4.7.2 which is included in C1-200402.
C1-200726	UE radio capability information storage not needed for RACS	Nokia, Nokia Shanghai Bell	CR 2006 24.501 Rel-16
C1-200727	UE radio capability information storage not needed for RACS	Nokia, Nokia Shanghai Bell	CR 3337 24.301 Rel-16
5G_SRVCC (CT4 lead)	Peter – Main	CT aspects of single radio voice continuity from 5GS to 3G
C1-200427	Use registration message to inform the network when the SRVCC information changes	BlackBerry UK Ltd.	CR 1911 24.501 Rel-16
C1-200436	PDU session release at the UE side	ZTE, China Unicom, Ericsson	CR 1918 24.501 Rel-16
xBDT (CT3 lead)	Peter – Main	CT aspects on 5GS Transfer of Policies for Background Data 100%
IAB-CT (CT4 lead)	Peter – Main	CT aspects of support for integrated access and backhaul (IAB) CT1 no longer affected by this work item
5GS_OTAF (CT4 lead)	Peter – Main	5GS Enhanced support of OTA mechanism for UICC configuration parameter update
5G_URLLC (CT4 lead)	Peter – Main	CT aspects of CT Aspects of 5G URLLC
C1-200290	Always-On PDU session and URLLC	Ericsson / Ivo	CR 1878 24.501 Rel-16	CRs in C1-200685, C1-200290, C1-200564 conflict
C1-200685	Setting the Always-on PDU session indication IE in the PDU SESSION ESTABLISHMENT ACCEPT message	Nokia, Nokia Shanghai Bell	CR 1987 24.501 Rel-16	CRs in C1-200685, C1-200290, C1-200564 conflict
SEAL	Lena – Breakout	CT aspects of Service Enabler Architecture Layer for Verticals Is TS 24.544 sufficiently stable to be sent to CT#87-e for approval? Is TS 24.545 sufficiently stable to be sent to CT#87-e for information and/or approval? Is TS 24.546 sufficiently stable to be sent to CT#87-e for approval? Is TS 24.547 sufficiently stable to be sent to CT#87-e for approval? Is TS 24.548 sufficiently stable to be sent to CT#87-e for information and/or approval?
C1-200449	Obtain list of users based on location	Samsung / Sapan	pCR 24.545 Rel-16	Chen, Thursday, 14:19 In the client procedure, the identity of the querying client should be included; In the server procedure, the SLM-S should first check if the client is authorized to query; In order to query the list of users based on given geolocation area, the client shall send an HTTP POST request message
C1-200450	Annex to describes the functionality expected from the HTTP entities	Samsung, Intel / Sapan	pCR 24.547 Rel-16
C1-200523	Latest reference version of draft TS 24.545	Huawei, HiSilicon /Christian	draft TS 24.545 Rel-16	Sapan, Thursday, 13:55 In clause 7.6, the Editor’s note needs to be removed as the MIME type is already defined.
C1-200524	Latest reference version of draft TS 24.548	Huawei, HiSilicon /Christian	draft TS 24.548 Rel-16	Sapan, Thursday, 13:52 Editorial comments: 1) In clause 7.5.2: <request> is an optional element used to include the unicast resource management requested information. should be changed to The <request> element is an optional element used to include the unicast resource management requested information. 2) In clause 7.5.2: <response> is an optional element used to include the unicast resource management response information. should be changed to The <response> element is an optional element used to include the unicast resource management response information.
C1-200526	Off-network procedures for SEAL location management	Huawei, HiSilicon /Christian	pCR 24.545 Rel-16
C1-200527	Off-network procedures for SEAL network resource management	Huawei, HiSilicon /Christian	pCR 24.548 Rel-16
C1-200552	Fetching location reporting configuration	Huawei, HiSilicon / Chen	pCR 24.545 Rel-16	Merged into C1-20774
C1-200553	Structure and data semantics for fetching location reporting configuration	Huawei, HiSilicon / Chen	pCR 24.545 Rel-16	Merged into C1-20774
C1-200554	On-demand location reporting procedure	Huawei, HiSilicon / Chen	pCR 24.545 Rel-16
C1-200555	Structure and data semantics for on-demand location reporting procedure	Huawei, HiSilicon / Chen	pCR 24.545 Rel-16
C1-200556	Location reporting event-triggered configuration cancel procedure	Huawei, HiSilicon / Chen	pCR 24.545 Rel-16
C1-200557	Location information subscription procedure	Huawei, HiSilicon / Chen	pCR 24.545 Rel-16
C1-200558	Structure and data semantics for location information subscription procedure	Huawei, HiSilicon / Chen	pCR 24.545 Rel-16
C1-200559	Event-triggered location information notification procedure	Huawei, HiSilicon / Chen	pCR 24.545 Rel-16
C1-200560	Structure and data semantics for Event-triggered location information notification procedure	Huawei, HiSilicon / Chen	pCR 24.545 Rel-16
C1-200561	On-demand usage of location information procedure	Huawei, HiSilicon / Chen	pCR 24.545 Rel-16
C1-200562	MBMS bearer announcement over MBMS bearer procedure	Huawei, HiSilicon / Chen	pCR 24.548 Rel-16
C1-200563	MBMS bearer quality detection procedure	Huawei, HiSilicon / Chen	pCR 24.548 Rel-16
C1-200607	Latest draft version of TS 24.547 ver 1.0.0	Intel / Vivek	pCR 24.547 Rel-16
C1-200609	Updates to Client User Authentication Procedure	Intel / Vivek	pCR 24.547 Rel-16
C1-200611	Updates to Server User Authentication Procedure	Intel / Vivek	pCR 24.547 Rel-16
C1-200612	Updates to Client Token Exchange Procedure	Intel / Vivek	pCR 24.547 Rel-16
C1-200613	Updates to Server Token Exchange Procedure	Intel / Vivek	pCR 24.547 Rel-16
C1-200614	Off Network Procedures for Identity Management	Intel / Vivek	pCR 24.547 Rel-16
C1-200615	Resolution of editor's note under clause 6.2.2.2.1	Huawei, HiSilicon /Christian	pCR 24.548 Rel-16
C1-200616	Resolution of editor's note under 6.2.2.2.3	Huawei, HiSilicon /Christian	pCR 24.548 Rel-16
C1-200617	General on unicast resource management	Huawei, HiSilicon /Christian	pCR 24.548 Rel-16
C1-200633	Adding access token in proper header of HTTP request from client	Samsung / Sapan	pCR 24.544 Rel-16
C1-200634	XML schema for SEAL group document and update coding	Samsung / Sapan	pCR 24.544 Rel-16
C1-200635	Updating client side procedures based on XML schema	Samsung / Sapan	pCR 24.544 Rel-16
C1-200636	Location based group creation procedure	Samsung / Sapan	pCR 24.544 Rel-16	See also: C1-200449
C1-200637	Parameters for group event subscription and notification	Samsung / Sapan	pCR 24.544 Rel-16
C1-200638	Procedures for management of group events subscription	Samsung / Sapan	pCR 24.544 Rel-16	Related to C1-200637
C1-200639	Procedures to notify group events	Samsung / Sapan	pCR 24.544 Rel-16	Related to C1-200637
C1-200640	Removal of clause for security parameter	Samsung / Sapan	pCR 24.544 Rel-16
C1-200641	Group announcement and join procedure	Samsung / Sapan	pCR 24.544 Rel-16
C1-200642	Group member leave procedure	Samsung / Sapan	pCR 24.544 Rel-16
C1-200643	Removal of editor’s note for off-network	Samsung / Sapan	pCR 24.544 Rel-16
C1-200644	Update references	Samsung / Sapan	pCR 24.544 Rel-16
C1-200645	XML schema for VAL user profile document and update of coding	Samsung / Sapan	pCR 24.546 Rel-16
C1-200646	XML schema and coding for VAL UE configuration document	Samsung / Sapan	pCR 24.546 Rel-16
C1-200647	Management of configuration event subscription	Samsung / Sapan	pCR 24.546 Rel-16	Related to C1-200649
C1-200648	Procedure to notify configuration management event	Samsung / Sapan	pCR 24.546 Rel-16	Related to C1-200649
C1-200649	Parameters for configuration event subscription and notification	Samsung / Sapan	pCR 24.546 Rel-16
C1-200650	Corrections in procedures	Samsung / Sapan	pCR 24.546 Rel-16
C1-200651	Removal of editor’s note for off-network	Samsung / Sapan	pCR 24.546 Rel-16
C1-200660	Latest draft version of TS 24.544 ver 1.0.0	Samsung / Sapan	pCR 24.544 Rel-16
C1-200662	Latest draft version of TS 24.546 ver 1.0.0	Samsung / Sapan	pCR 24.546 Rel-16
C1-200676	Workplan for SEAL	Samsung / Sapan	Work Plan
C1-200774	Update to Event-triggered location reporting procedure	Huawei, HiSilicon /Christian	pCR 24.545 Rel-16	Revision of C1-200608 Sapan, Thursday, 14:45 1) In clause 6.2.2.1, step a), reference to clause 6.2.2.2 needs to be modified to clause 6.2.2.2.2. 2) In clause 6.2.2.2.1: b) shall set X-3GPP-Intended-Identity header to the VAL user identity requesting for location reporting configuration. Should be changed to b) shall include an Authorization header field with the "Bearer" authentication scheme set to an access token of the "bearer" token type as specified in IETF RFC 6750 [r6750]. 3) In clause 6.2.2.3.1, B) a <triggering-criteria> child element which indicate a specified location trigger criteria to send the location report; and should be changed to B) a <triggering-criteria> child element specifying the triggers for the SLM-C to request a location report as specified in clause 7; and 4) In clause 6.2.2.3.1, not able to understand below step - can you please reword it? 3) shall include the <trigger-id> attribute where defined for the sub-elements defining the trigger criterion; and
C1-200775	Update to structure and data semantics for event-triggered location reporting procedure	Huawei, HiSilicon /Christian	pCR 24.545 Rel-16	Revision of C1-200610 Sapan, Thursday, 15:36 The structure in clause 7.3 and the data semantics in clause 7.5 are not matching. the triggering criteria should be optional only. Can you please change clause 7.3 from “shall” to “may”? Same comment applies to the <triggering-criteria> element of <report> element also (which is already existing text).
Other Rel-16 non-IMS issues	Peter – Main	Other Rel-16 non-IMS topics Only revision of agreed CRs from the ad-hoc meeting and DISC paper supporting LS
C1ah-200024	Correction for misalignment of 23.041 with 23.007 and 23.527	Ericsson, one2many / Ivo	CR 0204 23.041 Rel-16	Agreed
C1ah-200064	Correction on T3402 for deactivated value	Huawei, HiSilicon/Lin	CR 3321 24.301 Rel-16	Agreed
C1ah-200186	Correcting reference	BlackBerry UK Ltd.	CR 0128 24.007 Rel-16	Agreed Revision of C1ah-200136 _________________________________________ Revision of C1ah-200134 _________________________________________ Revision of C1ah-200010
C1ah-200207	Correcting active flag and signalling active flag wording	BlackBerry UK Ltd.	CR 3314 24.301 Rel-16	Agreed Revision of C1ah-200193 _________________________________________ Revision of C1ah-200185 _________________________________________ Revision of C1ah-200128 _________________________________________ Revision of C1ah-200015
C1ah-200209	Correct UE behavior when maximum number of active EPS bearer contexts is reached and the upper layers request more DRBs	BlackBerry UK Limited	CR 3317 24.301 Rel-16	Agreed Revision of C1ah-200184 _________________________________________ Revision of C1ah-200125 _________________________________________ Revision of C1ah-200052
C1-200308	Removal of Duplicate Service Operation Details	Cisco Systems Belgium	CR 0207 23.041 Rel-16	Postponed New CR under TEI16, out of scope for this meeting
C1-200606	Considerations for AML over SMS in roaming scenarios	Apple	discussion Rel-16	Postponed New input DISC on TEI16, out of scope of this meeting
WIs for IMS	Joergen – Breakout
MCCI_CT	Mission Critical Communication Interworking with Land Mobile Radio Systems Is TS 29.582 sufficiently stable to be sent to CT#87-e for approval?
C1-200366	Non-3GPP Message for Data interworking	Sepura, Hytera Communications Corp.	pCR 29.582 Rel-16
C1-200367	SDS media plane message handling by IWF	Sepura, Hytera Communications Corp.	pCR 29.582 Rel-16
C1-200369	Remove editor's note – clause 4.1	FirstNet / Mike	pCR 29.582 Rel-16
C1-200370	Remove editor's note – clause 4.2.2	FirstNet / Mike	pCR 29.582 Rel-16
C1-200371	Remove editor's note – clause 6.3.2.1	FirstNet / Mike	pCR 29.582 Rel-16
C1-200372	Remove editor's note – clause 6.6.2	FirstNet / Mike	pCR 29.582 Rel-16
C1-200373	Remove editor's note – clause 8.3.2.8	FirstNet / Mike	pCR 29.582 Rel-16
MCProtoc16	Joergen – Breakout	Protocol enhancements for Mission Critical Services for Rel-16
C1-200357	Correcting SIP related terminology	Ericsson / Nevenka	CR 0543 24.379 Rel-16
C1-200358	Correcting SIP related terminology	Ericsson / Nevenka	CR 0089 24.281 Rel-16
C1-200359	Correcting SIP related terminology	Ericsson / Nevenka	CR 0099 24.282 Rel-16
C1-200709	FEC encoding by the BM-SC	ENENSYS	CR 0068 24.581 Rel-16
MuD	Joergen – Breakout	Multi-device and multi-identity Is TS 24.174 sufficiently stable to be sent to CT#87-e for approval? Is Ts 24.175 management object sufficiently stable to be sent to CT#87-e for approval?
C1-200360	Update of OMA references	Ericsson / Nevenka	pCR 24.174 Rel-16
C1-200361	Adding interactions with "Multi-Device" and "Multi-Identity" services	Ericsson / Nevenka	CR 0188 24.604 Rel-16
C1-200362	Adding interactions with "Multi-Device" and "Multi-Identity" services	Ericsson / Nevenka	CR 0028 24.605 Rel-16
C1-200363	Adding interactions with "Multi-Device" and "Multi-Identity" services	Ericsson / Nevenka	CR 0075 24.615 Rel-16
C1-200364	Adding interactions with "Multi-Device" and "Multi-Identity" services	Ericsson / Nevenka	CR 0039 24.629 Rel-16
C1-200653	Clarifications of identity definitions and activation procedures	Ericsson /Jörgen	pCR 24.174 Rel-16
C1-200654	Call log handling, Additional-Identity	Ericsson /Jörgen	pCR 24.174 Rel-16
C1-200656	Conf indication completion	Ericsson /Jörgen	pCR 24.174 Rel-16
C1-200657	Management object correction, MuD	Ericsson /Jörgen	pCR 24.175 Rel-16
C1-200664	MO for MuD and MiD correction	Orange / Mariusz	pCR 24.175 Rel-16
C1-200665	MuD MiD and CAT interactions	Orange / Mariusz	pCR 24.174 Rel-16
C1-200667	MuD MiD and CRS interactions	Orange / Mariusz	pCR 24.174 Rel-16
C1-200668	CAT interactsions with MuD and MiD	Orange / Mariusz	CR 0118 24.182 Rel-16
C1-200670	CRS interactsions with MuD and MiD	Orange / Mariusz	CR 0061 24.183 Rel-16
IMSProtoc16	Joergen – Breakout	IMS Stage-3 IETF Protocol Alignment for Rel-16
C1-200625	Location information; mid-call access change	Ericsson, Deutsche Telekom /Jörgen	CR 6411 24.229 Rel-16
C1-200659	Correction of P-Associated-URI handling	Ericsson /Jörgen	CR 6412 24.229 Rel-16
C1-200684	UAC for MO-IMS registration related signalling EN resolution	NTT DOCOMO INC.	CR 6413 24.229 Rel-16
MCSMI_CT	Joergen – Breakout	Mission Critical system migration and interconnection
eMCData2	Joergen – Breakout	CT aspects of Enhancements to Functional architecture and information flows for Mission Critical Data
C1-200447	Key download procedrue for MCData	Samsung / Sapan	CR 0102 24.282 Rel-16
C1-200475	Delete Stored Object(s) in MCData message store	AT&T, Samsung	CR 0106 24.282 Rel-16
C1-200531	Add Message Store Client subclause	AT&T, Samsung	CR 0107 24.282 Rel-16
C1-200539	Copy stored object(s) and-or folder(s)	AT&T, Samsung	CR 0108 24.282 Rel-16
C1-200540	Creating new folder	AT&T, Samsung	CR 0109 24.282 Rel-16
C1-200541	Delete folder	AT&T, Samsung	CR 0110 24.282 Rel-16
C1-200542	Move object(s) and folder(s)	AT&T, Samsung	CR 0111 24.282 Rel-16
C1-200543	Search for Folders in MCData message store	AT&T, Samsung	CR 0112 24.282 Rel-16
C1-200544	Retrieval of stored object	AT&T, Samsung	CR 0103 24.282 Rel-16	Revision of C1-200448
C1-200548	Search for Objects in MCData message store	AT&T, Samsung	CR 0104 24.282 Rel-16	Revision of C1-200473
C1-200550	Update Object(s) in MCData message store	AT&T, Samsung	CR 0105 24.282 Rel-16	Revision of C1-200474
C1-200705	Move the stored object to destination folder	Samsung Electronics Co., Ltd	CR 0113 24.282 Rel-16
C1-200711	Upload the objects to the MCData message store	Samsung, AT&T	CR 0114 24.282 Rel-16
C1-200712	Included absolute URI associated with the media storage function of MCData content server	Samsung	CR 0066 24.483 Rel-16
C1-200713	Included absolute URI associated with the media storage function of MCData content server	Samsung	CR 0135 24.484 Rel-16
C1-200714	Accessing the absolute URI associated with the media storage function	Samsung	CR 0115 24.282 Rel-16
C1-200715	Corrections to TDC2 and TDC3 timer handling	Samsung	CR 0116 24.282 Rel-16
C1-200716	The pre-establshed session modification for MCData	Samsung	CR 0117 24.282 Rel-16
C1-200766	File distribution over MBMS - signalling control	ENENSYS	CR 0093 24.282 Rel-16	Postponed Document was LATE Revision of C1-198542
E2E_DELAY (CT4)	Joergen – Breakout	CT Aspects of Media Handling for RAN Delay Budget Reporting in MTSI 100%
VBCLTE (CT3 lead)	Joergen – Breakout	Volume Based Charging Aspects for VoLTE CT
ISAT-MO-WITHDRAW	Joergen – Breakout	Withdrawal of TS 24.323 from Rel-11, Rel-12, Rel-13 No CRs needed, listed for the sake of completeness 100%
MONASTERY2	Joergen – Breakout	Mobile Communication System for Railways Phase 2
C1-200408	Automatic group affiliation and deaffiliation based on location or functional alias	Kontron Transportation, Nokia, Nokia Shanghai Bell	CR 0132 24.484 Rel-16	Revision of C1-198846
C1-200409	Automatic group affiliation and deaffiliation based on location or functional alias	Kontron Transportation, Nokia, Nokia Shanghai Bell	CR 0064 24.483 Rel-16	Revision of C1-198847
C1-200410	Automatic group affiliation and deaffiliation based on location or functional alias	Kontron TransportationS, Nokia, Nokia Shanghai Bell	CR 0541 24.379 Rel-16	Revision of C1-198803
C1-200412	IP Connectivity	Kontron Transportation	CR 0101 24.282 Rel-16
C1-200749	Work plan for the CT1 part of MONASTERY2	Nokia, Nokia Shanghai Bell	discussion Rel-16
C1-200750	Analysis of options for FA resolution	Nokia, Nokia Shanghai Bell	discussion Rel-16
C1-200751	Support of functional alias in first-to-answer calls	Nokia, Nokia Shanghai Bell	CR 0551 24.379 Rel-16
C1-200752	Update service configuration to support limiting the number of authorized clients per MCPTT user	Nokia, Nokia Shanghai Bell	CR 0136 24.484 Rel-16	Postponed Document was LATE
C1-200753	Update service authorization procedures to support limiting the number of authorized clients per MCPTT user	Nokia, Nokia Shanghai Bell	CR 0552 24.379 Rel-16
eIMS5G_SBA	Joergen – Breakout	CT aspects of SBA interactions between IMS and 5GC
C1-200353	No impact from SBA on main body	Nokia, Nokia Shanghai Bell, Ericsson	CR 6408 24.229 Rel-16
enh2MCPTT-CT	Joergen – Breakout	Enhancements for Mission Critical Push-to-Talk CT aspects
C1-200374	Affiliation in a regroup	FirstNet / Mike	CR 0544 24.379 Rel-16
C1-200375	Ambiguity of location information in 6.3.2.1.4	FirstNet / Mike	CR 0545 24.379 Rel-16
C1-200376	Calling party location	FirstNet / Mike	CR 0546 24.379 Rel-16
C1-200377	Check for controlling function identity in 10.1.1.3.1.1	FirstNet / Mike	CR 0547 24.379 Rel-16
C1-200378	Check for groups that are already regrouped	FirstNet / Mike	CR 0548 24.379 Rel-16
C1-200379	Correct clause reference in 11.1.1.3.1.2	FirstNet / Mike	CR 0549 24.379 Rel-16
C1-200380	Missing client procedures for preconfigured regroup	FirstNet / Mike	CR 0550 24.379 Rel-16
C1-200381	Correct reference in 8.3.2.6	FirstNet / Mike	CR 0100 24.282 Rel-16
C1-200382	Update on Plugtest Reported Issues	FirstNet / Mike	discussion Rel-16
eIMSVideo	Joergen – Breakout	Video enhancement of IMS CAT/CRS/announcement services
C1-200481	Work plan for eIMSVideo	Huawei,China Telecom,China Unicom,HiSilicon /Hongxia	discussion Rel-16
C1-200487	Work plan for eIMSVideo	Huawei,China Telecom,China Unicom,HiSilicon /Hongxia	discussion Rel-16	Withdrawn
C1-200482	Use precondition only for CAT when network disables precondition	Huawei,China Telecom,China Unicom,HiSilicon /Hongxia	CR 0114 24.182 Rel-16
C1-200483	Use precondition for CAT when originating UE and network both support precondtion	Huawei,China Telecom,China Unicom,HiSilicon /Hongxia	CR 0115 24.182 Rel-16
C1-200484	Use precondition for CRS when network disables precondition	Huawei,China Telecom,China Unicom,HiSilicon /Hongxia	CR 0057 24.183 Rel-16
C1-200485	Use precondition for CRS when terminating UE supports or requires precondition	Huawei,China Telecom,China Unicom,HiSilicon /Hongxia	CR 0058 24.183 Rel-16
C1-200486	Providing video announcement at the same time with audio conversation	Huawei,China Telecom,China Unicom,HiSilicon /Hongxia	CR 0072 24.628 Rel-16
C1-200488	Use precondition only for CAT when network disables precondition	Huawei,China Telecom,China Unicom,HiSilicon /Hongxia	CR 0116 24.182 Rel-16	Withdrawn
C1-200489	Use precondition for CAT when originating UE and network both support precondtion	Huawei,China Telecom,China Unicom,HiSilicon /Hongxia	CR 0117 24.182 Rel-16	Withdrawn
C1-200490	Use precondition for CRS when network disables precondition	Huawei,China Telecom,China Unicom,HiSilicon /Hongxia	CR 0059 24.183 Rel-16	Withdrawn
C1-200491	Use precondition for CRS when terminating UE supports or requires precondition	Huawei,China Telecom,China Unicom,HiSilicon /Hongxia	CR 0060 24.183 Rel-16	Withdrawn
C1-200492	Providing video announcement at the same time with audio conversation	Huawei,China Telecom,China Unicom,HiSilicon /Hongxia	CR 0073 24.628 Rel-16	Withdrawn
C1-200546	Condition of providing video announcement	China Telecom,Huawei, China Unicom, HiSilicon	CR 0074 24.628 Rel-16
Other Rel-16 IMS & MC issues	Joergen – Breakout	Other Rel-16 IMS topics
C1-200365	SDP profile update to support FLUS	Ericsson / Nevenka	CR 6409 24.229 Rel-16
C1-200673	Discussion on SRVCC from E-UTRAN to GERAN/UTRAN when IMS voice call is initiated in 5GS	Ericsson / Ivo	discussion Rel-16
C1-200674	SRVCC from E-UTRAN to GERAN/UTRAN when IMS voice call is initiated in 5GS	Ericsson / Ivo	CR 1298 24.237 Rel-16
C1-200772	Correction in IMS_Registration_handling policy about how UE should deregister	MediaTek Inc.	CR 6404 24.229 Rel-16	Postponed Document was late
Release 17 work items	Tdoc	NOT PART OF THIS MEETING
Output Liaison Statements	Tdoc	Title	Prepared by	To/CC	Result & comment
C1-200309	Reply LS on General Status of Work	Ericsson / Ivo	LS out Rel-16
C1-200310	Reply LS on sending CAG ID	Ericsson / Ivo	LS out Rel-16
C1-200395	Reply LS on SUCI computation from an NSI	Ericsson / Ivo	LS out Rel-16
C1-200434	LS on secure that a UE does not wait indefinitely for completion of NSSAA procedure	ZTE	LS out Rel-16
C1-200499	Reply LS on Rel-16 NB-IoT enhancements	Huawei, HiSilicon/Lin	LS out Rel-16	C1-200416 and C1-200499 compete
C1-200545	Reply LS on PC5S and PC5 RRC unicast message protection	OPPO / Rae	LS out Rel-16
C1-200590	LS on suspend indication to the NAS	Samsung/Mahmoud	LS out Rel-16
C1-200699	LS on manual CAG selection	Nokia, Nokia Shanghai Bell	LS out Rel-16
C1-200707	Reply LS on Mobile-terminated Early Data Transmission	Ericsson / Mikael	LS out Rel-16
C1-200710	Reply LS on RRC establishment cause value in EPS voice fallback from NR to E-UTRAN	Nokia, Nokia Shanghai Bell	LS out Rel-16
C1-200717	Reply LS on extended NAS timers for CE in 5GS	Ericsson / Mikael	LS out Rel-16
C1-200718	Reply LS on configured NSSAI handling	Nokia, Nokia Shanghai Bell	LS out Rel-16
C1-200721	Reply LS on Non-UE N2 Message Services Operations	Ericsson / Mikael	LS out Rel-16
C1-200764	reply LS for concurrent broadcast for CMAS	Samsung /Grace	LS out Rel-16	Proposed Postponed The related incoming LS in C1-200226 is Rel-15 and hence not in scope of this meeting. Consequently any Reply LS is not in scope of the meeting either (although header of this LS lists Rel-16)
C1-200323	Response to LS on Non-UE N2 Message Services Operations	Cisco Systems Belgium	LS out Rel-16	Withdrawn Moved from 16.2.21
C1-200416	LS on UE specific DRX for NB-S1 mode	Qualcomm Incorporated / Amer	LS out Rel-16	Moved from 16.2.8 C1-200416 and C1-200499 compete
C1-200445	[Draft] LS on Unicode symbol numbers representing disasters	SyncTechno Inc.	LS out Rel-16	Moved from 16.2.1
C1-200453	LS on limited service state for CAG cell	Huawei, HiSilicon / Vishnu	LS out Rel-16	Moved from 16.2.7.1
C1-200671	Response to LS on Sending CAG ID	Samsung/Kundan	LS out Rel-16	Moved from 16.7.1 LATE
Late and misplaced documents	Tdoc	Title Prioritization of documents within this category will be done during the meeting. Some tdocs are left in the main agenda item, although they are late (e.g. papers reporting IETF progress, which are usually more up to date the later they are submitted)	Source	Tdoc info	Result & comments Late documents and documents which were submitted with erroneous or incomplete information
A.O.B.	Tdoc	Title	Source	Tdoc info	Result & comments
Closing Friday by 16:00 at the latest	Did you mark your attendance to this meeting?	Any meeting document which is not mentioned in this report or with no recorded decision shall be interpreted as "reserved", i.e. not defined and shall be ignored if received
Last upload of revisions: Thursday 27th February 2020 16:00 CET Last comments: Friday 28th February 2020 16:00 CET Chairman Report of the meeting: Monday 2nd March 2020