3GPP TSG CT WG1 Meeting#123-e	C1-202003

Electronic meeting, 16-24 April 2020

Meeting documents by agenda item Meeting: Meeting #123-e Electronic meeting 16 - 24 April 2020 All indicated times are CEST
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 acti ities 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-202048	3GPP TSG CT1#123-e – agenda for Tdoc allocation	CT1 chairman	agenda	Revision of C1-202000
C1-202001	3GPP TSG CT1#123-e – agenda after Tdoc allocation deadline	CT1 chairman	agenda
C1-202002	3GPP TSG CT1#123-e – agenda with proposed LS-actions	CT1 chairman	agenda
C1-202003	3GPP TSG CT1#123-e – agenda at start of meeting	CT1 chairman	agenda
C1-202004	3GPP TSG CT1#123-e – agenda Thursday (23rd April) evening	CT1 chairman	agenda
C1-202005	3GPP TSG CT1#123-e – agenda at end of meeting	CT1 chairman	agenda
C1-202006	draft C1-122e report	MCC	report
Hightest number 2598
Agenda Start of e-meeting: Thursday 16th April 09:00 CEST Comment Free Time Thursday 23rd April 12:00-16:00 CEST Last revision upload: Thursday 23th April 16:00 CEST Last comments: Friday 24th April 16:00 CEST Chairman’s report of the meeting: Monday 27th April 12:00 CEST 1 Opening 2 Agenda and Reports 3 work organization 4 incoming LS Rel-15: 15.1.1 all work items () 15.1.2 all work items (2) 15.1.3 all work items (11+3) Rel-16: Agenda Items from 16.2 16.2.2 SINE_5G (1) 16.2.3 SAES16 (all aspects) (5) 16.2.4 5GProtoc16 (all aspects) (104) 16.2.5 ATSSS (19) 16.2.6 eNS (44) 16.2.7.x vertical-LAN (74) 16.2.8 5G_CIoT (41) 16.2.9 5WWC (12) 16.2.11 5G_eLCS (2) 16.2.14 RACS (1) 16.2.15 5G_SRVCC (3) 16.2.16 xBDT (0) 16.2.17 IAB-CT (0) 16.2.18 5GS_OTAF (0) 16.2.19 5G_URLLC (0) 16.2.21 Rel-16 non-IMS issues (27) 16.2.1 ePWS (1) 16.2.10 PARLOS (3) 16.2.12 V2XAPP (18) 16.2.13 eV2XARC (50) 16.2.20 SEAL (44) Agenda Items from 16.3 16.3.1 MCCI_CT (1) 16.3.2 MCProtoc16 (14) 16.3.5 MCSMI_CT (0) 16.3.6 eMCDATA2 (16) 16.3.10 MONASTERY2 (8) 16.3.12 enh2MCPTT-CT (0) 16.3.3 MuD (2) 16.3.4 IMSProtoc16 (1) 16.3.7 E2E_DELAY (0) 16.3.8 VBCLTE (0) 16.3.11 eIMS5G_SBA (2) 16.3.13 eIMSVideo (3) 16.3.14 IMS/MC TEI16 (8) 18 outgoing LS
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	Electronic Meeting
20 – 24 April	CT1#123	Cancelled
16 – 24 April	CT1#123-e	Electronic Meeting
25 – 29 May	CT1#124	F2fF cancelled
29 June – 1 July. 2020	CT plenary #88-e	Electronic Meeting
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 #92	Japan
Work Plan and other adm. issues	Tdoc	Title	Source	Spec / doctype	Result & comments
C1-202007	CT1#123-e Electronic Meeting – Process and Scope	CT1 chairman	other
C1-202051	work plan	MCC	Work Plan
C1-202055	Decision making during CT1#123e – electronic show of hands	CT1 chairman	other
Input Liaison statements	Tdoc	Title	Source	To / CC	Result & comments
C1-202033	Specification of NAS COUNT for 5G (FSAG Doc 78_002)	GSMA FSAG	To	Proposed Noted Related CR in C1-202089
C1-202034	Mandatory User Plane Integrity for 5G (FSAG Doc 79_002)	GSMA FSAG	To	Proposed Noted Wait for SA to conclude
C1-202035	LS Reply on QoS mapping procedure for FLUS (C3-201460)	CT3	Cc	Proposed Noted
C1-202036	LS on Proposal to transfer the study on service-based support for SMS in 5GC to CT WGs (CP-193301)	TSG CT	Cc	Proposed Postponed Rel-17
C1-202037	LS on MO exception data (C4-201003)	CT4	Cc	Proposed Noted
C1-202038	SMS and UDM (C4-201045)	CT4	To	Proposed Noted Wait on next steps from SA2 on 23.501
C1-202039	LS on the Usage of Version ID (C4-2011218)	CT4	Cc	Proposed Noted
C1-202040	Reply LS on Further clarifications on GLI/GCI and Line ID/ HFC_Identifier (C4-201220)	CT4	Cc	Proposed Noted
C1-202041	LS on subscribe/notify for 5G Steering of Roaming (C4-201221)	CT4	To	Proposed tbd Reply LS in C1-202067 and C1-202151 Related CRs in C1-202068, C1-202069, C1-202152
C1-202042	Clarification on encryption requirements for AGF interfaces (N1, N2, N3) [WWC] (LIAISE-382)	Broadband Forum	To	Proposed Noted No action required from CT1
C1-202043	LS on RRC establishment cause value in EPS voice fallback from NR to E-UTRAN (R2-1916530)	RAN2	To	Proposed Noted Related CR C1-202269
C1-202044	Reply LS on Rel-16 NB-IoT enhancements (R2-2001815)	RAN2	To	Proposed Noted CT1 questions on values for UE specific DRX cycle in NB-IoT in C1-201024 are not answered, no consensus in RAN2 Related with incoming LS in C1-202049 Related CRs in C1-202084 and C1-202384
C1-202045	LS on Manual CAG ID selection and granularity of UAC parameters for PNI-NPNs (R2-2002417)	RAN2	To	Proposed tbd Reply LS in C1-202012, C1-202103, C1-202180, C1-202240, C1-202359 Disc paper C1-202102, C1-202239, C1-202493, C1-202499, Related CR C1-202397, C1-202015
C1-202047	Reply LS on assistance indication for WUS (R3-201397)	RAN3	Cc	Proposed Noted Related with incoming LS in C1-202058
C1-202049	Reply LS on Rel-16 NB-IoT enhancements (R3-201417)	RAN3	To	Proposed Noted Related with incoming LS in C1-202044 Related CRs in C1-202084 and C1-202384
C1-202050	LS on Questions on onboarding requirements (S1-201087)	SA1	Cc	Proposed Postponed Rel-17
C1-202052	LS on PLMN selection solutions for satellite access (S2-1912551)	SA2	To	Proposed Postponed Rel-17
C1-202053	Reply LS on clarification on the requirement for steering of roaming (S2-1912764)	SA2	To	Proposed Noted Are CRs available to the meeting?
C1-202054	Reply LS on Dual-registration requirements for EHPLMNs (S2-2001130)	SA2	To	Proposed tbd related CR in C1-202136 Is a reply LS available?
C1-202056	LS on GSMA NG.116 Attribute Area of service and impact on PLMN selection (S2-2001726)	SA2	To	Proposed Postponed Rel-17 Related with incoming LS in C1-202065
C1-202057	Questions on onboarding requirements (S2-2001729)	SA2	Cc	Proposed Postponed Rel-17
C1-202058	Reply LS on assistance indication for WUS (S2-2001732)	SA2	To	Proposed Noted Related with incoming LS in C1-202047 Are CRs available to the meeting?
C1-202059	Reply LS on IANA assigned values for mission critical (S3-194603)	SA3	To	Proposed Postponed Reply LS needed, seems not available
C1-202060	Reply LS to LS on native 5G NAS security context activation (S3-200529)	SA3	To	Proposed Noted Are CRs available?
C1-202061	Reply on QoE Measurement Collection (S4-200241)	SA4	To	Proposed Postponed Are CRs available? Reply LS needed, seems not availalble
C1-202062	LS on RTP/RTCP Verification (S4-200340)	SA4	To	Proposed Postponed Reply LS needed, seems not available
C1-202063	Reply LS to Transfer the study on service-based support for SMS in 5GC to CT WGs (SP-191362)	TSG SA	To	Proposed Postponed Rel-17
C1-202064	Reply LS on support for eCall over NR (SP-200287)	TSG SA	To	Proposed Noted CRs available in C1-202081 and C1-202358
C1-202065	LS reply to SA2 on PLMN Selection (5GJA12_115r3)	GSMA 5G Joint-Activity (5GJA)	To	Proposed Postponed Rel-17 Related with Incoming LS in C1-202056 No action from CT1 required
C1-202591	Reply LS on QoS mapping procedure (S4-200690)	SA4	Proposed Noted Wait for CT3 to clarify "a=3gpp-qos-hint" usage Do we have CRs or DISC paper to the meeting?
C1-202597	LS on Concurrent Broadcasting for CMAS (R3-197749)	RAN3	To	Proposed tbd Reply LS in C1-202232 and C1-202564 Disc paper in C1-202231 and C1-202565 Related CR in C1-202263 Revision of C1-202046 _________________________________________ 2046 had incomplete tdoc number on the cover sheet
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	Title	Source	Tdoc info	Result & comments
Rel-15 Mission Critical work items and issues: eMCVideo-CT eMCDATA-CT enhMCPTT-CT MCProtoc15 MONASTERY MBMS_MCservices	Jörgen	All work items complete Enhancements to Mission Critical Video – CT aspects Enhancements for Mission Critical Data – CT aspects Enhancements for Mission Critical Push-to-Talk – CT aspects Protocol enhancements for Mission Critical Services sion Critical Push-to-Talk – CT aspects Mobile Communication System for Railways MBMS usage for mission critical communication services
Rel-15 IMS work items and issues 5GS_Ph1-IMSo5G eCNAM-CT FS_PC_VBC (CT3) IMSProtoc9 bSRVCC_MT eSPECTRE PC_VBC (CT3) TEI15 (IMS)	Jörgen	All work items complete IMS impact due to 5GS IP-CAN CT aspects of Enhanced Calling Name Service Study on Policy and Charging for Volume Based Charging IMS Stage-3 IETF Protocol Alignment for Rel-15 SRVCC for terminating call in pre-alerting phase Enhancements to Call spoofing functionality Policy and Charging for Volume Based Charging
C1-202584	Reference update for PASSporT Extension for Diverted Calls	Orange / Mariusz	CR 6416 24.229 Rel-15
C1-202585	Reference update for PASSporT Extension for Diverted Calls	Orange / Mariusz	CR 6417 24.229 Rel-16
Rel-15 non-IMS/non-MC work items and issues 5GS_Ph1-CT EDCE5-CT ProSe_WLAN_DD_Stage3 VoWLAN-CT PS_DATA_OFF2-CT LTE_LIGHT_CON-CT AT_CIoT-Ext SAES6 INOBEAR-CT TEI15	Peter	All work items complete CT aspects on 5G System - Phase 1 EPC enhancements to support 5G New Radio via Dual Connectivity Inclusion of WLAN direct discovery technologies as an alternative for ProSe direct discovery Complementary Features for Voice services over WLAN PS Data Off Phase 2 CT aspects of signalling reduction to enable light connection for LTE AT Commands for CIoT-Ext Stage-3 SAE Protocol Development for Rel-15 Increasing the number of EPS bearers Other Rel-15 non-IMS topics
C1-202032	Remove the duplicated cause value for announce request procedure not accepted by the ProSe Function	CATT	CR 0328 24.334 Rel-15
C1-202092	Correct N3AN node selection due to LI	BlackBerry Uk Ltd.	CR 0119 24.502 Rel-15
C1-202093	Correct N3AN node selection due to LI	BlackBerry Uk Ltd.	CR 0120 24.502 Rel-16
C1-202096	Correct EPS SRVCC support indication when registering with 5GS	BlackBerry Uk Ltd.	CR 1642 24.501 Rel-15	Revision of C1-198013 Alternative to C1-202133 (is Rel-16 only)
C1-202097	Correct EPS SRVCC support indication when registering with 5GS	BlackBerry Uk Ltd.	CR 1643 24.501 Rel-16	Revision of C1-198014 Alternative to C1-202133 (is Rel-16 only)
C1-202227	Adding Unstructured type(non-IP) to encoding of UE policy part type URSP(R15)	China Telecom Corporation Ltd.	CR 0074 24.526 Rel-15
C1-202231	CWMI use in PWS	Ericsson / Mikael	discussion Rel-15
C1-202291	Remove USE_TRANSPORT_MODE in response	ZTE / Joy	CR 0124 24.502 Rel-15
C1-202292	Remove USE_TRANSPORT_MODE in response	ZTE / Joy	CR 0125 24.502 Rel-16
C1-202360	Remove SUPI in the form of NSI from stage 2(in R15)	China Telecom / Michelle	CR 2127 24.501 Rel-15
C1-202361	Remove SUPI in the form of NSI from stage 2(in R15)	China Telecommunications	CR 0127 24.502 Rel-15
C1-202507	Registration at PLMN change at PLMN-SEARCH substate	MediaTek Inc.	CR 2189 24.501 Rel-15
C1-202561	handling of ePWS message	Samsung/ Kyungjoo Grace Suh	CR 0216 23.041 Rel-15
C1-202565	Discussion for concurrent broadcast for CMAS	Samsung/ Kyungjoo Grace Suh	discussion 23.041 Rel-15
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-202166	Revised WID on CT aspects of eV2XARC	Huawei, HiSilicon /Christian	WID revised Rel-16	Revision of CP-200291
C1-202570	Updated WID MONASTERY2	Nokia, Nokia Shanghai Bell	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-202424	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
C1-202563	handling of ePWS message	Samsung/ Kyungjoo Grace Suh	CR 0217 23.041 Rel-16
SINE_5G	Peter – Main	Signalling Improvements for Network Efficiency in 5GS 100%
C1-202581	Handling of PDU session authentication	Samsung / Kyungjoo Grace Suh	CR 2210 24.501 Rel-16
SAES16 WIs	Peter – Main	Stage-3 SAE protocol pevelopment for Rel-16 100%
SAES16	Peter – Main	General Stage-3 SAE protocol development
C1-202515	Correction of EMM initiated TAU procedure in EMM-REGISTERED.ATTEMPTING-TO-UPDATE-MM	MediaTek Inc.	CR 3366 24.301 Rel-16
C1-202516	Correction to Handling of MO CSFB Emergency call in EMM-REGISTERED.ATTEMPTING-TO-UPDATE-MM	MediaTek Inc.	CR 3367 24.301 Rel-16
C1-202517	Correction to Handling of #31	MediaTek Inc.	CR 3368 24.301 Rel-16
C1-202519	Correction to Handling of #35	MediaTek Inc.	CR 3369 24.301 Rel-16
C1-202542	Error handling of precedence value conflict	MediaTek Inc. / JJ	CR 3372 24.301 Rel-16
C1-202127	Consistent usage of "tracking area updating procedure"	Samsung Electronics Polska	CR 3341 24.301 Rel-16	Shifted from 16.2.21
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
C1-202144	Clarification on URSP in EPS	ZTE / Joy	CR 0073 24.526 Rel-16
C1-202524	Handling of allowed NSSAI when the RA includes the TAI belonging to EPLMN	SHARP	CR 2198 24.501 Rel-16
C1-202527	UE initiating service request over non-3GPP access after stopping T3346	SHARP	CR 2201 24.501 Rel-16
C1-202530	Discussion on S-NSSAI based congestion control	MediaTek Inc., Qualcomm Incoporated. / JJ	discussion Rel-16
C1-202534	Discussion on support of QoS rules/QoS flow descriptions with the length of two octets	MediaTek Inc. / JJ	discussion Rel-16
C1-202535	Indicate support of ePCO length of two octets parameter when establishing the PDU session – Alt#2	MediaTek Inc. / JJ	CR 2204 24.501 Rel-16
C1-202536	Indicate support of ePCO length of two octets parameter in the bearer resource modification procedure – Alt#3	MediaTek Inc. / JJ	CR 3371 24.301 Rel-16
C1-202537	Unsupported 5QI values	MediaTek Inc. / JJ	CR 0686 27.007 Rel-16
C1-202538	Addition of 5GSM cause #59	MediaTek Inc. / JJ	CR 2205 24.501 Rel-16
C1-202541	Correction to the URSP coding	MediaTek Inc., ZTE / JJ	CR 0068 24.526 Rel-16	Revision of C1-198970
C1-202175	No allowed NSSAI associated with a registration area	vivo	CR 2061 24.501 Rel-16
C1-202016	Manual CAG selection	Ericsson / Ivo	CR 0501 23.122 Rel-16	Withdrawn Not available on time Revision of C1-200732
C1-202017	Correction for SoR-AF	Ericsson / Ivo	CR 0481 23.122 Rel-16	Revision of C1-200064
C1-202068	SoR in HPLMN after registration	Orange, Ericsson / Mariusz	CR 0508 23.122 Rel-16	Releated CR in C1-202152
C1-202069	Modification of exchanges between SOR-AF and UDM	Orange, Ericsson / Mariusz	CR 0509 23.122 Rel-16	Releated CR in C1-202152
C1-202152	Correcting the parameter "RAT type" for SOR-AF	DOCOMO Communications Lab.	CR 0515 23.122 Rel-16	Releated CRs in C1-202068, C1-202069
C1-202070	OTAF renamed to SP-AF	Orange / Mariusz	CR 0510 23.122 Rel-16
C1-202071	Reference correction in URSP encoding	Orange / Mariusz	CR 0071 24.526 Rel-16
C1-202073	Removal of Duplicate Service Operation Details	one2many	CR 0207 23.041 Rel-16	Revision of C1-200308
C1-202074	Correction to figure	one2many B.V.	CR 0212 23.041 Rel-16
C1-202075	Corrections to references	one2many B.V.	CR 0213 23.041 Rel-16
C1-202076	Subscription management in PWS-IWF	one2many B.V.	CR 0214 23.041 Rel-16
C1-202089	Clarification of NAS COUNT handling in 5G	Vodafone GmbH	CR 2036 24.501 Rel-16
C1-202098	Correcting order in which connections/sessions are transferred if there is an emergency call	BlackBerry Uk Ltd.	CR 1782 24.501 Rel-16	Revision of C1-200115
C1-202100	Clarification on use of operator-defined access categories	Qualcomm Incorporated, Ericsson, Nokia, Nokia Shanghai Bell / Lena	CR 1795 24.501 Rel-16	Revision of C1ah-200149
C1-202101	Clarification on DL only match-all packet filter	Qualcomm Incorporated / Lena	CR 2037 24.501 Rel-16
C1-202110	Adding Unstructured type(non-IP) to encoding of UE policy part type URSP	China Telecom Corporation Ltd.	CR 0072 24.526 Rel-16
C1-202128	Correction of the handling of timer TG	Apple, Qualcomm Incorporated, T-Mobile USA	CR 0513 23.122 Rel-16
C1-202129	Correction of the handling of 5GMM cause #27	Apple, Qualcomm Incorporated, T-Mobile USA	CR 2047 24.501 Rel-16
C1-202136	Dual-registration requirements for EHPLMNs	Intel, Qualcomm Incorporated / Vivek	CR 1974 24.501 Rel-16	Revision of C1-200620
C1-202141	Additional condition to start T3540	Samsung/Anikethan	CR 2050 24.501 Rel-16
C1-202145	Specify UE behaviour for NOTIFICATION message for additional state/sub-states	Samsung/Anikethan	CR 2051 24.501 Rel-16
C1-202146	Additional abnormal case handling for NOTIFICATION message	Samsung/Anikethan	CR 1791 24.501 Rel-16	Revision of C1ah-200199
C1-202149	Restricting handling of cause #9 to the access on which it was received	Samsung/Anikethan	CR 1792 24.501 Rel-16	Revision of C1ah-200031
C1-202153	Correcting the case when the AMF does not need to provide SOR-info to the UE	DOCOMO Communications Lab.	CR 0516 23.122 Rel-16
C1-202158	Adding new IMSDoPS indication bits in “EPS network feature support” IE for network to indicate support for “IMS Data over PS” services	MediaTek Inc., Apple	CR 2054 24.501 Rel-16
C1-202200	storage of counters for UE in PLMN	vivo	CR 2071 24.501 Rel-16
C1-202201	Clarification of the figure of registration procedure	vivo	CR 2072 24.501 Rel-16
C1-202203	Addition of Test Flag	one2many B.V.	CR 0215 23.041 Rel-16
C1-202218	Editorial corrections	Ericsson / Mikael	CR 2074 24.501 Rel-16
C1-202219	UAC for MO-IMS registration related signalling EN resolution	NTT DOCOMO INC.	CR 6413 24.229 Rel-16	Revision of C1-200684
C1-202228	Possible KSI types in EPS	Ericsson / Mikael	CR 2076 24.501 Rel-16	Withdrawn
C1-202229	Possible KSI types in EPS	Ericsson / Mikael	CR 3346 24.301 Rel-16
C1-202244	Notification over non-3GPP access when UE is deregistered over 3GPP access	Ericsson /kaj	CR 2082 24.501 Rel-16
C1-202254	No available S-NSSAIs at handover with emergency PDU session established	Ericsson /kaj	discussion Rel-16
C1-202255	No available S-NSSAIs and emergency PDU session at handover	Ericsson /kaj	CR 2088 24.501 Rel-16
C1-202268	Add handling for parameter set to “value is not used” in 5GS	Qualcomm Incorporated	CR 2093 24.501 Rel-16
C1-202272	Correct parameters included by AMF during inter-system change from S1 mode to N1 mode in 5GMM-CONNECTED mode	Qualcomm Incorporated	CR 2095 24.501 Rel-16
C1-202275	Remove invalid cases in error handling for QoS rule operation and TFT operation	Qualcomm Incorporated	CR 2096 24.501 Rel-16
C1-202276	Clarify PAP/CHAP usage in PCO for 5GS	Qualcomm Incorporated	CR 3215 24.008 Rel-16
C1-202277	Add handling for UE configured to use timer T3245 in 5GS via 3GPP access	Qualcomm Incorporated	CR 2097 24.501 Rel-16	Withdrawn
C1-202278	Add handling for UE configured to use timer T3245 in 5GS via 3GPP access	Qualcomm Incorporated	CR 1803 24.501 Rel-16	Revision of C1ah-200178
C1-202280	Applicable URSP is not optional for a UE	Motorola Mobility, Lenovo	CR 2098 24.501 Rel-16
C1-202285	Additional QoS error handling related to mapped EBI	Qualcomm Incorporated / Lena	CR 2101 24.501 Rel-16
C1-202289	PS Data Off status report for non-3GPP access	LG Electronics, Ericsson / SangMin	CR 2102 24.501 Rel-16	Partially overlaps with C1-202120
C1-202295	Unify terms network-initiated and network-requested	Huawei, HiSilicon / Cristina	CR 2103 24.501 Rel-16
C1-202324	NW triggered SR over N3GPP under MM congestion control	OPPO / Rae	CR 2104 24.501 Rel-16
C1-202325	Initiate 3GPP access associated notification procedure over non-3GPP access	Huawei, HiSilicon / Cristina	CR 2105 24.501 Rel-16
C1-202331	Consider PDU session type IE set by UE in IP address allocation	Huawei, HiSilicon / Cristina	CR 2110 24.501 Rel-16
C1-202339	Add MFBR as mandatory parameter in GBR QoS flow	Huawei, HiSilicon / Cristina	CR 2116 24.501 Rel-16	Withdrawn
C1-202341	Add MFBR as mandatory parameter in GBR QoS flow	Huawei, HiSilicon / Cristina	CR 2117 24.501 Rel-16	Withdrawn
C1-202342	Fixing a reference in the service request procedure	BEIJING SAMSUNG TELECOM R&D	CR 2118 24.501 Rel-16
C1-202343	Add MFBR as mandatory parameter in GBR QoS flow	Huawei, HiSilicon / Cristina	CR 2119 24.501 Rel-16	Withdrawn
C1-202344	Add MFBR as mandatory parameter in GBR QoS flow	Huawei, HiSilicon / Cristina	CR 2120 24.501 Rel-16
C1-202347	Correcting length of extended emergency number list IE	Huawei, HiSilicon / Cristina	CR 3352 24.301 Rel-16
C1-202348	Initial registration for initiating emergency PDU session	Huawei, HiSilicon / Cristina	CR 2121 24.501 Rel-16
C1-202349	Missing QoS flow description parameters for GBR QoS flows in 5GSM and ESM coordination	Huawei, HiSilicon / Cristina	CR 2122 24.501 Rel-16
C1-202358	Support for eCall over IMS over NR	Huawei, HiSilicon / Cristina	CR 0521 23.122 Rel-16
C1-202375	Initial NAS message protection on inter-system change from EPS to 5GS	Samsung/Kundan	CR 2136 24.501 Rel-16
C1-202376	Handling of MCS data in various 5GMM states	Samsung	CR 1415 24.501 Rel-16	Revision of C1-194530
C1-202377	No messages without integrity protection processed after security activation	Nokia, Nokia Shanghai Bell	CR 2137 24.501 Rel-16
C1-202378	Clarification on the AMF behaviour after security activation in case of integrity check failure	Nokia, Nokia Shanghai Bell	CR 2138 24.501 Rel-16
C1-202379	Discarding a SECURITY MODE COMMAND message which fails integrity check	Nokia, Nokia Shanghai Bell	CR 2139 24.501 Rel-16
C1-202380	Initiation of ESFB by a UE in the state 5GMM-REGISTERED.ATTEMPTING-REGISTRATION-UPDATE	Nokia, Nokia Shanghai Bell	CR 2140 24.501 Rel-16
C1-202381	No emergency session transfer after ESFB	Nokia, Nokia Shanghai Bell	CR 2141 24.501 Rel-16
C1-202382	Indication that the emergency services fallback attempt failed	Nokia, Nokia Shanghai Bell	CR 2142 24.501 Rel-16
C1-202390	Inclusion of ATTACH REQUEST message in REGISTRATION REQUEST message during initial registration when 5G-GUTI mapped from 4G-GUTI is used	Nokia, Nokia Shanghai Bell, Ericsson, Qualcomm Incorporated	CR 0793 24.501 Rel-16	Revision of C1ah-200179
C1-202391	Attach request message for N1 mode	Nokia, Nokia Shanghai Bell, Ericsson	CR 3150 24.301 Rel-16	Revision of C1ah-200180
C1-202392	Paging with two valid 5G-GUTIs	Nokia, Nokia Shanghai Bell	CR 1841 24.501 Rel-16	Revision of C1ah-200213
C1-202394	PDU session release for an inactive UE with RAN paging failure	Nokia, Nokia Shanghai Bell	CR 1833 24.501 Rel-16	Revision of C1ah-200089
C1-202417	Handling of correction to UE configuration update procedure conditions for re-registration	LG Electronics France	CR 2160 24.501 Rel-16	Withdrawn Not available on time
C1-202418	Correction to conditions for including the S-NSSAI(s) from default NSSAI in the requested NSSAI	Qualcomm Incorporated / Amer	CR 2161 24.501 Rel-16
C1-202420	Definition of current PLMN and serving PLMN	Qualcomm Incorporated / Amer	CR 2163 24.501 Rel-16
C1-202436	Discussion on the selected EPS NAS security algorithms	BEIJING SAMSUNG TELECOM R&D	discussion
C1-202437	Condition for setting the Selected EPS NAS algorithm IE to NULL	BEIJING SAMSUNG TELECOM R&D	CR 2171 24.501 Rel-16
C1-202476	Corrections on the abnormal cases of registration procedure for initial registration	Huawei, HiSilicon/Lin	CR 1379 24.501 Rel-16	Revision of C1-199032
C1-202477	Correction on UE behaviour for service area restriction	Huawei, HiSilicon/Lin	CR 1823 24.501 Rel-16	Revision of C1ah-200161
C1-202478	Single-registration mode without N26	Huawei, HiSilicon/Lin	CR 2182 24.501 Rel-16
C1-202479	Single-registration mode without N26	Huawei, HiSilicon/Lin	CR 3358 24.301 Rel-16
C1-202480	Service reject for emergency EPS fallback	Huawei, HiSilicon/Lin	CR 3359 24.301 Rel-16	Withdrawn Used CR number against 24.301 although targeted for 24.501
C1-202592	Service reject for emergency EPS fallback	Huawei, HiSilicon/Lin	CR 2213 24.501 Rel-16
C1-202481	Handling of mapped EPS bearer contexts	Huawei, HiSilicon/Lin	CR 3360 24.301 Rel-16	Withdrawn Used CR number against 24.301 although targeted for 24.501
C1-202593	Handling of mapped EPS bearer contexts	Huawei, HiSilicon/Lin	CR 2214 24.501 Rel-16
C1-202482	Integrity check interworking in 5GMM-CONNECTED mode	Huawei, HiSilicon/Lin	CR 3361 24.301 Rel-16	Withdrawn Used CR number against 24.301 although targeted for 24.501
C1-202594	Integrity check interworking in 5GMM-CONNECTED mode	Huawei, HiSilicon/Lin	CR 2215 24.501 Rel-16
C1-202483	Correction on LADN DNN based congestion control	Huawei, HiSilicon/Lin	CR 3362 24.301 Rel-16	Withdrawn Used CR number against 24.301 although targeted for 24.501
C1-202595	Correction on LADN DNN based congestion control	Huawei, HiSilicon/Lin	CR 2216 24.501 Rel-16
C1-202491	Allowed SSC mode for association between an application and a PDU session	OPPO / Rae	CR 0075 24.526 Rel-16
C1-202492	Handling of unallowed SSC mode	OPPO / Rae	CR 2183 24.501 Rel-16
C1-202501	UAC exception for emergency	MediaTek Inc.	CR 2184 24.501 Rel-16
C1-202503	MRU after SR for ESFB aborted	MediaTek Inc.	CR 2185 24.501 Rel-16
C1-202504	MRU failed due to RRC signalling connection release in restricted service area	MediaTek Inc.	CR 2186 24.501 Rel-16
C1-202505	Correction to criteria to enter 5GMM-REGISTERED.UPDATE-NEEDED substate after resumption failure	MediaTek Inc.	CR 2187 24.501 Rel-16
C1-202508	T3346 handling when the UE is registered to different PLMNs over 3GPP and non-3GPP	MediaTek Inc.	CR 2190 24.501 Rel-16
C1-202509	Correction to 5G-GUTI handling when received at REGISTRATION ACCEPT	MediaTek Inc.	CR 2191 24.501 Rel-16
C1-202510	Correcting that 5G NAS integrity key is one of the input parameters for integrity protection algorithm	MediaTek Inc.	CR 2192 24.501 Rel-16
C1-202514	Correction to Handling of T3521 timer	MediaTek Inc.	CR 2193 24.501 Rel-16
C1-202518	Correction to Handling of #31	MediaTek Inc.	CR 2194 24.501 Rel-16
C1-202523	De-registration before initial registration for Emergency Services	MediaTek Inc.	CR 2197 24.501 Rel-16
C1-202525	Handling of rejected NSSAI for the current RA when the RA includes the TAI belonging to EPLMN	SHARP	CR 2199 24.501 Rel-16
C1-202526	Correction to deletion of Allowed NSSAI	Huawei, HiSilicon / Vishnu	CR 2200 24.501 Rel-16
C1-202528	UE behaviour when the UE receives the rejected NSSAI for the current RA in the registration reject message and the RA is not stored	SHARP	CR 2202 24.501 Rel-16
C1-202583	Security handling	Samsung/ Kyungjo Grace Suh	CR 2211 24.501 Rel-16	Withdrawn
5GProtoc16-non3GPP	Peter – Main	Stage-3 5GS NAS protocol development related to non-3GPP access
C1-202279	Add handling for UE configured to use timer T3245 in 5GS for non-3GPP access	Qualcomm Incorporated	CR 0121 24.502 Rel-16
C1-202578	Extending congestion notification to capture ePDG overload	Nokia, Nokia Shanghai Bell, Charter Communications	CR 0718 24.302 Rel-16
C1-202579	Extending congestion notification to capture N3IWF or TNGF overload	Nokia, Nokia Shanghai Bell, Charter Communications	CR 0130 24.502 Rel-16
C1-202580	Enable N3IWF to initiate TCP connection establishment upon failure	Nokia, Nokia Shanghai Bell	CR 0131 24.502 Rel-16
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#88 for approval?
C1-202009	EPS interworking of MA PDU session of 5G-RG when N26 is not supported	Ericsson / Ivo	CR 2027 24.501 Rel-16
C1-202019	Performance management function protocol	Ericsson / Ivo	pCR 24.193 Rel-16	Revision of C1-200314
C1-202021	Comparison of solutions for performance measurement function (PMF) protocol	Ericsson / Ivo	discussion Rel-16	Revision of C1-200313
C1-202031	EPS interworking of MA PDU session of 5G-RG when N26 is supported	Ericsson / Ivo	CR 2029 24.501 Rel-16
C1-202120	Applicability of PS data off to MA PDU	OPPO / Rae	CR 2042 24.501 Rel-16	Partially overlaps with C1-202289
C1-202142	Correction on network steering functionalities information	ZTE / Joy	pCR 24.193 Rel-16
C1-202143	Correction on EPS interworking	ZTE / Joy	pCR 24.193 Rel-16
C1-202266	ATSSS Performance Measurement Function Protocols and Procedures	Apple, Deutsche Telekom, Charter Communications, Ruckus, Commscope	pCR 24.193 Rel-16	Revision of C1-200655
C1-202294	Discussion on handling of clause 5.2 in TS 24.193	ZTE / Joy	discussion Rel-16
C1-202371	Clarification of UE behavior on receiving ATSSS support indicator	SHARP	CR 2133 24.501 Rel-16
C1-202372	Clarification of SMF and UE behavior in 5GS to EPS mobility without N26 interface	SHARP	pCR 24.193 Rel-16
C1-202431	Editorial fix in 9.11.4	Apple	CR 2169 24.501 Rel-16
C1-202531	Handlings of MA PDU session when deregistration from an access	MediaTek Inc. / JJ	CR 2203 24.501 Rel-16
C1-202532	Considering allowed NSSAI when requesting MA PDU session upgrade	MediaTek Inc. / JJ	pCR 24.193 Rel-16
C1-202533	Correction to the steering modes	MediaTek Inc. / JJ	pCR 24.193 Rel-16
C1-202575	PMF protocol alternatives analysis	Nokia, Nokia Shanghai Bell	discussion Rel-16
C1-202576	Minor clarification for ATSSS-LL support	Nokia, Nokia Shanghai Bell	CR 2209 24.501 Rel-16	Withdrawn
C1-202577	Clarification on MAI	Nokia, Nokia Shanghai Bell	pCR 24.193 Rel-16	Withdrawn
C1-202582	Service Request for Multiple access PDU session	Samsung / Kyungjoo Grace Suh	pCR 24.193 Rel-16
eNS	Peter – Main	CT aspects on enhancement of network slicing
C1-202111	Clarification S-NSSAI status in AMF for NSSAA	China Telecom Corporation Ltd.	CR 2038 24.501 Rel-16	Overlaps with C1-202454
C1-202112	Update description on whether UE indicate supporting NSSAA	China Telecom Corporation Ltd.	CR 2039 24.501 Rel-16
C1-202113	Pending NSSAI update for the configured NSSAI in the CUC message	China Telecom Corporation Ltd.	CR 2040 24.501 Rel-16
C1-202114	Adding the referenced subclause 4.6.2.2 for the UE stored Pending NSSAI.	China Telecom Corporation Ltd.	CR 2041 24.501 Rel-16
C1-202121	Missing condition for inclusion of “NSSAA to be performed” indicator	Samsung Electronics Polska	CR 2043 24.501 Rel-16
C1-202122	AMF triggers PDU session release	Samsung Electronics Polska	CR 2044 24.501 Rel-16
C1-202123	Allowed NSSAI was formed from contents of the requested NSSAI and all default S-NSSAI(s) require network slice-specific authentication and authorisation	Samsung Electronics Polska	discussion	EN#11 & Task #4 See also C1-202123, 2124,2243, 2252
C1-202124	All default S-NSSAI(s) require network slice-specific authentication and authorisation (solution 1)	Samsung Electronics Polska	CR 2045 24.501 Rel-16	EN#11 & Task #4 See also C1-202123, 2124,2243, 2252
C1-202134	Stopping of T3346 after receiving the NSSA Command message	BEIJING SAMSUNG TELECOM R&D	CR 2049 24.501 Rel-16
C1-202150	Inclusion of Rejected NSSAI in Registration reject with cause #62	Samsung/Anikethan	CR 2052 24.501 Rel-16
C1-202157	Clarification on the rejected S-NSSAI included in requested NSSAI in registration procedure.	China Telecom Corporation Ltd.	CR 2053 24.501 Rel-16
C1-202170	The handling of N1 SM information during re-authentication and re-authorization for an S-NSSAI	China Mobile	CR 2057 24.501 Rel-16	EN#10 & Task#1 See also C1-202170, 2345, 2351, 2352.
C1-202171	Updating descriptions of NS for NSSAA	China Mobile	CR 2058 24.501 Rel-16
C1-202172	Discussion paper on the impact of non-standard S-NSSAI mapping to NSSAA and NSSAI storage	China Mobile	discussion 24.501 Rel-16
C1-202173	Updating requirements of NSSAA for roaming scenerios	China Mobile	CR 2059 24.501 Rel-16
C1-202224	T3540 is not started if the Registration Accept includes a pending NSSAI	BEIJING SAMSUNG TELECOM R&D	CR 2075 24.501 Rel-16
C1-202234	Clarify that NSSAA can occur during periodic registration or mobility updating for NB-N1 mode UEs	BEIJING SAMSUNG TELECOM R&D	CR 2079 24.501 Rel-16
C1-202241	Fixing typo related to eNS	BEIJING SAMSUNG TELECOM R&D	CR 2080 24.501 Rel-16
C1-202243	All default S-NSSAI(s) require network slice-specific authentication and authorisation (solution 2B)	Samsung Electronics Polska	CR 2081 24.501 Rel-16	EN#11 & Task #4 See also C1-202123, 2124,2243, 2252
C1-202246	S-NSSAI in rejected NSSAI for the failed or revoked NSSAA not to be requested	Ericsson /kaj	CR 2083 24.501 Rel-16	Withdrawn
C1-202247	S-NSSAI in rejected NSSAI for the failed or revoked NSSAA not to be requested	Ericsson /kaj	CR 1734 24.501 Rel-16	Revision of C1-198417
C1-202248	Alignment of UE actions of rejected NSSAI for the failed or revoked NSSAA	Ericsson /kaj	CR 2084 24.501 Rel-16
C1-202250	Request S-NSSAI pending the NW slice-specific authentication and authorization	Ericsson /kaj	CR 2004 24.501 Rel-16	Revision of C1-200724 Task#3, See also C1-202250, 2472, 2473
C1-202252	S-NSSAIs always selected from allowed NSSAI by AMF	Ericsson /kaj	CR 2086 24.501 Rel-16	EN#11 & Task #4 See also C1-202123, 2124,2243, 2252
C1-202257	Exception to initiate the service request procedure during NSSAA when there is no allowed NSSAI	BEIJING SAMSUNG TELECOM R&D	CR 2089 24.501 Rel-16
C1-202259	NSSAA for UEs that roam across 5GS VPLMNs	BEIJING SAMSUNG TELECOM R&D	CR 2090 24.501 Rel-16
C1-202261	Missing condition at registration reject due to no available slices	Ericsson /kaj	CR 2091 24.501 Rel-16
C1-202282	Network-requested PDU session release due to failed or revoked NSSAA	Motorola Mobility, Lenovo	CR 2099 24.501 Rel-16
C1-202329	Updating Rejeted NSSAI IE for failed NSSAA case in roaming scenerios	China Mobile	CR 2108 24.501 Rel-16
C1-202330	Abnormal case about missing EAP result for NSSAA	China Mobile	CR 2109 24.501 Rel-16	Withdrawn Not available on time
C1-202332	Work Plan for eNS in CT1	ZTE	Work Plan Rel-16
C1-202340	Deleting Editors note regarding indefinite wait at the UE for NSSAA completion	ZTE	CR 1912 24.501 Rel-16	Revision of C1-201051 EN#1 & Task #2
C1-202345	Discussion on re-initiation of NSSAA	BEIJING SAMSUNG TELECOM R&D	discussion	EN#10 & Task#1 See also C1-202170, 2345, 2351, 2352
C1-202346	EPS selection when the UE is deregistered due to NSSAA failure	Samsung/Kundan	CR 1950 24.501 Rel-16	Revision of C1-200572
C1-202351	Re-initiation of NSSAA (solution #1)	BEIJING SAMSUNG TELECOM R&D	CR 2124 24.501 Rel-16	EN#10 & Task#1 See also C1-202170, 2345, 2351, 2352.
C1-202352	Re-initiation of NSSAA (solution #2)	BEIJING SAMSUNG TELECOM R&D	CR 2125 24.501 Rel-16	EN#10 & Task#1 See also C1-202170, 2345, 2351, 2352
C1-202374	NSSAA in an SNPN	Nokia, Nokia Shanghai Bell	CR 2135 24.501 Rel-16
C1-202383	Clarification to NSSAA procedure	Samsung/Kundan	CR 2143 24.501 Rel-16
C1-202385	Handling of Pending S-NSSAI	Samsung/Kundan	CR 2144 24.501 Rel-16
C1-202430	Release PDU sessions due to revocation from AAA server , re-auth failure	LG Electronics France	CR 2168 24.501 Rel-16
C1-202454	Updating NSSAI status in AMF	NEC	CR 1990 24.501 Rel-16	Revision of C1-200691 Overlaps with C1-202111
C1-202472	Discussion on including pending S-NSSAI(s) in the requested NSSAI	Huawei, HiSilicon/Lin	discussion Rel-16	Task#3 See also C1-202250, 2472, 2473
C1-202473	Inclusion of pending S-NSSAI(s) in the requested NSSAI	Huawei, HiSilicon, China Telecom/Lin	CR 2180 24.501 Rel-16	Task#3, See also C1-202250, 2472, 2473
C1-202475	Term on rejected NSSAI for the failed or revoked NSSAA	Huawei, HiSilicon/Lin	CR 2181 24.501 Rel-16
C1-202543	Clarification to NW slice-specific re-authentication and re-authorization	Ericsson /kaj	CR 2206 24.501 Rel-16
C1-202587	Update Handing EAP Result for NSSAA	China Mobile	CR 2212 24.501 Rel-16	Withdrawn Not available on time
C1-202589	eNS – way forward for indefinite wait for NSSAA	InterDigital / Atle	Discussion	EN#1 & Task #2
Vertical_LAN	Peter – Main	CT aspects of 5GS enhanced support of vertical and LAN services
Stand-alone NPN
C1-202350	TSN working domain terminology	Huawei, HiSilicon / Cristina	CR 2123 24.501 Rel-16
C1-202353	TSN working domain terminology	Huawei, HiSilicon / Cristina	CR 0001 24.535 Rel-16
C1-202354	Trigger for Initial Registration procedure	Samsung/Kundan	CR 2126 24.501 Rel-16
C1-202365	DISC Configuring UE to enable manual CAG selection procedure	Samsung	discussion Rel-16	Withdrawn Not available on time
C1-202395	Work plan for Vertical_LAN	Nokia, Nokia Shanghai Bell	discussion Rel-16
C1-202399	non-3GPP access not supported in SNPN	Intel /Thomas	CR 2148 24.501 Rel-16
C1-202013	Configured HRNN for SNPN selection	Ericsson / Ivo	CR 0505 23.122 Rel-16
C1-202020	Configured N3IWF identity for SNPN access via PLMN	Ericsson / Ivo	CR 0507 23.122 Rel-16	Withdrawn Not available on time
C1-202086	Management of forbidden SNPNs list upon receipt of a non-integrity protected reject message	Nokia, Nokia Shanghai Bell	CR 0511 23.122 Rel-16
C1-202087	Correction in UE behavior 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	Revision of C1-200970
C1-202130	Correction of the handling of timer TG for SNPNs	Apple	CR 0514 23.122 Rel-16
C1-202131	Correction of the UE requirements for expiry of T3247	Apple	CR 2048 24.501 Rel-16
C1-202174	Definition of registered SNPN	Intel /Thomas	CR 2060 24.501 Rel-16
C1-202193	update of the counter for SNPN	vivo	CR 2064 24.501 Rel-16
C1-202194	temporarily and permanently forbidden SNPNs lists per access type	vivo	CR 2065 24.501 Rel-16
C1-202195	storage of counters for UE in SNPN	vivo	CR 2066 24.501 Rel-16
C1-202196	5G GUTI of SNPN	vivo	CR 2067 24.501 Rel-16
C1-202197	5GMM cause value #74 in an SNPN with a globally-unique SNPN identity	vivo	CR 2068 24.501 Rel-16
C1-202198	5GMM cause value #13 not supporting roaming for SNPN	vivo	CR 2069 24.501 Rel-16
C1-202366	Condition for access to SNPN	SHARP	CR 2129 24.501 Rel-16
C1-202389	Clarification to SNPN to SNPN selection procedure	Samsung/Kundan	CR 2146 24.501 Rel-16	Withdrawn Not available on time
C1-202393	figures 1, 2a, 2b, 3 and table 2 not applicable in SNPN	Intel /Thomas	CR 0524 23.122 Rel-16
C1-202396	Subscription update in case of SNPN	Intel /Thomas	CR 2147 24.501 Rel-16
C1-202401	NB-IoT not applicable for SNPN	Nokia, Nokia Shanghai Bell	CR 2149 24.501 Rel-16
C1-202402	Introduction of SNPN-specific N1 mode attempt counters	Nokia, Nokia Shanghai Bell	CR 2011 24.501 Rel-16	Revision of C1-201032
C1-202406	Handling of a UE not allowed to access SNPN services via a PLMN by subscription with 5GMM cause value #72	Nokia, Nokia Shanghai Bell	CR 2151 24.501 Rel-16
C1-202407	Human readable network name for SNPN	Nokia, Nokia Shanghai Bell	CR 0527 23.122 Rel-16
C1-202408	Miscellaneous clean-up for SNPN	Nokia, Nokia Shanghai Bell	CR 2152 24.501 Rel-16
C1-202409	Service area restrictions in an SNPN	Nokia, Nokia Shanghai Bell	CR 2153 24.501 Rel-16
C1-202410	MICO in an SNPN	Nokia, Nokia Shanghai Bell	CR 2154 24.501 Rel-16
C1-202411	5GMM CC in an SNPN	Nokia, Nokia Shanghai Bell	CR 2155 24.501 Rel-16
C1-202412	5GSM back-off mechanisms in an SNPN	Nokia, Nokia Shanghai Bell	CR 2156 24.501 Rel-16
C1-202413	UE in the 5GMM-REGISTERED.ATTEMPTING-REGISTRATION-UPDATE substate operating in SNPN access mode	Nokia, Nokia Shanghai Bell	CR 2157 24.501 Rel-16
C1-202414	Routing indicator update in an SNPN	Nokia, Nokia Shanghai Bell	CR 2158 24.501 Rel-16
C1-202415	3GPP PS data off in an SNPN	Nokia, Nokia Shanghai Bell	CR 2159 24.501 Rel-16
C1-202428	correction to network selection in case of multiple subscribed SNPNs	Intel /Thomas	CR 2167 24.501 Rel-16	Withdrawn
C1-202432	correction to network selection in case of multiple subscribed SNPNs	Intel /Thomas	CR 0528 23.122 Rel-16
C1-202469	Non-3GPP access for PLMN and SNPN	Huawei, HiSilicon/Lin	CR 2177 24.501 Rel-16
C1-202506	5GS forbidden tracking areas for roaming for SNPN	MediaTek Inc.	CR 2188 24.501 Rel-16
C1-202522	Correct "theregistration"	MediaTek Inc.	CR 2196 24.501 Rel-16
Public network integrated NPN
C1-202008	CAG-ID not provided to lower layers during NAS signalling connection establishment	Ericsson / Ivo	CR 1880 24.501 Rel-16	Revision of C1-200937
C1-202014	Configured HRNN for CAG selection	Ericsson / Ivo	CR 0506 23.122 Rel-16
C1-202015	Providing configured HRNN for CAG selection	Ericsson / Ivo	CR 2009 24.501 Rel-16	Revision of C1-200733
C1-202091	CAG information list provided to lower layers after manual CAG selection	Ericsson / Ivo	CR 0512 23.122 Rel-16
C1-202102	Discussion on RAN2’s questions on CAG in LS R2-2002417	Qualcomm Incorporated / Lena	discussion Rel-16
C1-202179	Correction on no suitable cell	Vivo	CR 0517 23.122 Rel-16
C1-202199	Clarification of the cause of start of T3550	Vivo	CR 2070 24.501 Rel-16
C1-202239	Discussion on reply LS to RAN2 manual CAG selection	Huawei, HiSilicon/Vishnu	discussion 23.122 Rel-16
C1-202242	Discussion on protecting CAG list against man in middle attack	Huawei, HiSilicon/ Vishnu	discussion 24.501 Rel-16
C1-202249	Protection of Allowed CAG list against man in middle attack	Huawei, HiSilicon / Vishnu	CR 2085 24.501 Rel-16
C1-202251	Discussion on including CAG Information list in reject messages	Huawei, HiSilicon / Vishnu	discussion 24.501 Rel-16
C1-202253	Provision of CAG information list in reject messages	Huawei, HiSilicon/ Vishnu	CR 2087 24.501 Rel-16
C1-202256	Handling of HRNN information in a CAG cell	Huawei, HiSilicon / Vishnu	CR 0518 23.122 Rel-16
C1-202258	Indication to user about allowed CAG IDs for manual CAG selection	Huawei, HiSilicon / Vishnu	CR 0519 23.122 Rel-16
C1-202397	Selected CAG-ID from the NAS layer to the AS layer	Nokia, Nokia Shanghai Bell, vivo, Qualcomm Incorporated, Samsung, Huawei, HiSilicon	CR 0525 23.122 Rel-16
C1-202398	Manual CAG selection	Nokia, Nokia Shanghai Bel	CR 0499 23.122 Rel-16	Revision of C1-201052
C1-202405	CAG selection is optional in the manual network selection mode	Nokia, Nokia Shanghai Bell	CR 0526 23.122 Rel-16
C1-202470	No CAG in non-3GPP access	Huawei, HiSilicon/Lin	CR 2178 24.501 Rel-16
C1-202471	Correction on 5GMM #27 for CAG	Huawei, HiSilicon/Lin	CR 2179 24.501 Rel-16
C1-202493	Discussion to RAN2 LS R2-2002417	Ericsson / Ivo	discussion Rel-16
C1-202499	Discussion paper – Considerations for CAG ID in Unified Access Control	Chengdu OPPO Mobile Com. corp.	discussion Rel-16
C1-202588	CAG Information in Registration Reject	InterDigital, Samsung / Atle	CR 1886 24.501 Rel-16
C1-202355	Clarification to Manual CAG selection procedure	Samsung/Kundan	CR 0520 23.122 Rel-16
C1-202357	Discussion paper on RAN2 LS regarding Manual CAG and URC for PNI-NPN	Samsung	discussion Rel-16
C1-202362	Sending CAG information list	Samsung/Kundan	CR 2128 24.501 Rel-16
C1-202363	Sending CAG information list	Samsun/Kundan	CR 0522 23.122 Rel-16
C1-202364	Handling of a CAG UE at non supporting AMF	Samsung/Kundan	CR 1964 24.501 Rel-16	Revision of C1-200589
C1-202368	Configuring UE to enable manual CAG selection procedure (24.501)	Samsung/Kundan	CR 2131 24.501 Rel-16
C1-202370	Configuring UE to enable manual CAG selection procedure (23.122)	Samsung/Kundan	CR 0523 23.122 Rel-16
C1-202495	Correction to Manual CAG selection procedure	Samsung/Kundan	CR 0529 23.122 Rel-16
Time sensitive communication
C1-202191	Correction of the abnormal case in NW-TT-initiated Ethernet port management procedure	vivo	CR 0001 24.519 Rel-16
C1-202192	Abbreviation correction	vivo	CR 0002 24.519 Rel-16
C1-202429	IEEE Std 802.1Qbv-2016 rolled into IEEE Std 802.1Q-2018	Nokia, Nokia Shanghai Bell	CR 0003 24.519 Rel-16
C1-202433	TSN working domain	Nokia, Nokia Shanghai Bell	CR 0002 24.535 Rel-16
C1-202435	TSN working domain	Nokia, Nokia Shanghai Bell	CR 2170 24.501 Rel-16
C1-202350	TSN working domain terminology	Huawei, HiSilicon / Cristina	CR 2123 24.501 Rel-16
C1-202353	TSN working domain terminology	Huawei, HiSilicon / Cristina	CR 0001 24.535 Rel-16
5G_CIoT	Peter – Main	CT aspects of Cellular IoT support and evolution for the 5G System
C1-202077	Indication of change in the use of enhanced coverage	Samsung, InterDigital, Huawei, HiSilicon	CR 2030 24.501 Rel-16	Overlaps with C1-202230
C1-202078	Discussion on the mandatory Integrity protection maximum data rate field for UEs that support control plane only	Samsung	discussion Rel-16
C1-202079	Integrity protection data rate for UEs that don’t support N3 data transfer	Samsung	CR 2031 24.501 Rel-16
C1-202082	Addition of Control Plane Service Request in the abnormal cases for service request procedure	InterDigital Communications	CR 2032 24.501 Rel-16
C1-202084	DRX parameters for NB-IoT	InterDigital Communications	CR 2034 24.501 Rel-16
C1-202085	Correcting a wrong reference	InterDigital Communications	CR 2035 24.501 Rel-16
C1-202169	Adding new abnormal cases on the network side for CPSR	China Mobile, InterDigital	CR 2056 24.501 Rel-16	Overlaps with C1-202245, C1-202337, C1-202461
C1-202176	Correction of SGC	vivo	CR 2062 24.501 Rel-16
C1-202177	Emergency PDU sesseion established after WUS negotiation	vivo	CR 2063 24.501 Rel-16
C1-202202	subclause of Negotiated WUS assistance information	vivo	CR 2073 24.501 Rel-16
C1-202230	Generic UE configuration update trigger for registration and EC Restriction change	Ericsson / Mikael	CR 2077 24.501 Rel-16	Overlaps with C1-202077
C1-202245	CIoT user data container in CPSR message not forwarded	Ericsson /kaj	CR 1743 24.501 Rel-16	Revision of C1-200675 C1-202169, C1-202337, C1-202461
C1-202270	Correct handling of receiving EMM cause #31 in EPS	Qualcomm Incorporated	CR 3349 24.301 Rel-16
C1-202271	Correct UE behavior for receiving 5GMM cause #31 in 5GS	Qualcomm Incorporated	CR 2094 24.501 Rel-16
C1-202326	Avoid repeated redirection for NB-IoT	OPPO / Rae	CR 2106 24.501 Rel-16
C1-202328	PDU session release due to CP only revocation	OPPO / Rae	CR 2107 24.501 Rel-16
C1-202335	Clarification on the UE behaviour when receiving T3448	ZTE	CR 2112 24.501 Rel-16
C1-202336	Connection Resumption for Notification	ZTE, vivo	CR 2113 24.501 Rel-16
C1-202337	CIoT user or small data container in CPSR message not forwarded	ZTE	CR 2114 24.501 Rel-16	C1-202169, C1-202245, C1-202461
C1-202367	Correction on terminology for the Control plane CIoT 5GS optimization	SHARP	CR 2130 24.501 Rel-16
C1-202369	Handling of PDU session and PDN connection associated with Control plane only indication in case of N26 based interworking procedures	SHARP	CR 2132 24.501 Rel-16
C1-202373	Non-integrity protected REGISTRATION REJECT message including 5GMM cause #31 or #76	Nokia, Nokia Shanghai Bell	CR 2134 24.501 Rel-16
C1-202384	UE specific DRX for NB-S1 mode	Vodafone GmbH	CR 3353 24.301 Rel-16
C1-202387	Discussion on errors on QoS parameter operations in NB-IoT	BEIJING SAMSUNG TELECOM R&D	discussion
C1-202388	QoS error checks for UEs in NB-N1 mode	BEIJING SAMSUNG TELECOM R&D	CR 2145 24.501 Rel-16
C1-202403	Discussion on integrity check failure on the Control Plane Service Request message for WB-N1 mode UEs	BEIJING SAMSUNG TELECOM R&D	discussion
C1-202404	Retransmission of a CPSR message after integrity check failure at the AMF	BEIJING SAMSUNG TELECOM R&D	CR 2150 24.501 Rel-16
C1-202419	Corrections to CR#1907	Qualcomm Incorporated / Amer	CR 2162 24.501 Rel-16	Overalaps with C1-202465
C1-202422	Initial APN rate control parameters	Qualcomm Incorporated / Amer	CR 3216 24.008 Rel-16
C1-202423	Signalling of EPS APN rate control parameters during PDU session establishment	Qualcomm Incorporated / Amer	CR 2164 24.501 Rel-16
C1-202425	Ethernet header compression for CP CIoT – 5GMM aspects	Qualcomm Incorporated / Amer	CR 2165 24.501 Rel-16
C1-202426	Ethernet header compression for CP CIoT – 5GSM aspects	Qualcomm Incorporated / Amer	CR 2166 24.501 Rel-16
C1-202459	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-200893
C1-202460	Discussion on routing failure of CPSR	Huawei, HiSilicon, China Mobile/Lin	discussion Rel-16
C1-202461	Routing failure handling of CPSR	Huawei, HiSilicon, China Mobile/Lin	CR 2172 24.501 Rel-16	C1-202169, C1-202245, C1-202337
C1-202462	Acknowledgement of truncated 5G-S-TMSI configuration	Huawei, HiSilicon/Lin	CR 2173 24.501 Rel-16
C1-202463	NAS-MAC calculation for RRC connection reestablishment for NB-IoT CP optimisation	Huawei, HiSilicon/Lin	CR 2174 24.501 Rel-16
C1-202464	Removal of Editor’s Note for CP congestion control	Huawei, HiSilicon/Lin	CR 2175 24.501 Rel-16
C1-202465	Correction on WUS assistance	Huawei, HiSilicon/Lin	CR 2176 24.501 Rel-16	Overlaps with C1-202419
C1-202521	Correction to handling of T3447 timer	MediaTek Inc.	CR 2195 24.501 Rel-16
5WWC	Peter – Main	CT aspects on wireless and wireline convergence for the 5G system architecture
C1-202018	Secondary authentication and W-AGF acting on behalf of N5GC	Ericsson / Ivo	CR 2028 24.501 Rel-16
C1-202168	ANDSP is not supported by 5G-RG and W-AGF	ZTE / Joy	CR 2055 24.501 Rel-16
C1-202207	Work plan for the CT1 part of 5WWC	Huswei, HiSilicon /Christian	discussion Rel-16
C1-202283	Inclusion of NSSAI in AN Parameters for non-3GPP access	Motorola Mobility, Lenovo	CR 2100 24.501 Rel-16
C1-202284	Inclusion of requested NSSAI in AN parameters	Motorola Mobility, Lenovo	CR 0122 24.502 Rel-16
C1-202290	Removal of editor’s notes	Motorola Mobility, Lenovo	CR 0123 24.502 Rel-16
C1-202293	Error type on failure of reserving QoS resources over non-3GPP access	ZTE / Joy	CR 0126 24.502 Rel-16
C1-202486	Discussion on 3GPP based access authentication for untrusted non-3GPP access to 5GCN	Ericsson, BlackBerry UK Ltd., Motorola Mobility, Lenovo / Ivo	discussion Rel-16
C1-202571	EAP details for N5GC	Nokia, Nokia Shanghai Bell	CR 2207 24.501 Rel-16	Withdrawn
C1-202572	Corrections on N5GC SUPI SUCI	Nokia, Nokia Shanghai Bell	CR 0128 24.502 Rel-16	Withdrawn
C1-202573	NAS impacts supporting IPTV	Nokia, Nokia Shanghai Bell	CR 2208 24.501 Rel-16	Withdrawn
C1-202574	Support IPTV via wireline access	Nokia, Nokia Shanghai Bell	CR 0129 24.502 Rel-16	Withdrawn
PARLOS	Lena – Breakout	CT aspects of System enhancements for Provision of Access to Restricted Local Operator Services by Unauthenticated UEs 100%
C1-202125	Miscellaneous editorial corrections	Samsung Electronics Polska	CR 2046 24.501 Rel-16	Withdrawn
C1-202126	Miscellaneous editorial corrections	Samsung Electronics Polska	CR 3340 24.301 Rel-16
C1-202147	Clarify UE behaviour for reject cause #9 and #10 received when attached for RLOS	Samsung/Anikethan	CR 3342 24.301 Rel-16
C1-202154	Condition to ensure that UE does not keep reattempting RLOS attach on a PLMN which has rejected the request	Samsung/Anikethan	CR 3343 24.301 Rel-16
5G_eLCS (CT4)	Peter – Main	CT aspects of Enhancement to the 5GC LoCation Services
C1-202548	Adding Location Privacy Setting operation	CATT	CR 0001 24.571 Rel-16
C1-202549	Addition of new AT command for 5G Location Services testing	CATT	CR 0689 27.007 Rel-16
C1-202562	Supplementary LCS Service Operations	CATT	draftCR 24.080 Rel-16	Withdrawn 24.080 is a CT4 spec
V2XAPP	Lena – Breakout	CT aspects of V2XAPP Is TS 24.486 sufficiently stable to be sent to CT#88 for approval
C1-202206	Work plan for the CT1 part of V2XAPP	Huawei, HiSilicon /Christian	discussion Rel-16
C1-202208	Latest reference version of draft TS 24.486	Huawei, HiSilicon /Christian	draft TS 24.486 Rel-16
C1-202212	Miscellaneous corrections	Huawei, HiSilicon /Christian	pCR 24.486 Rel-16
C1-202213	V2X USD provisioning	Huawei, HiSilicon /Christian	pCR 24.486 Rel-16
C1-202214	PC5 parameters provisioning	Huawei, HiSilicon /Christian	pCR 24.486 Rel-16
C1-202215	Structure and data semantics for V2X USD provisioning	Huawei, HiSilicon /Christian	pCR 24.486 Rel-16
C1-202216	Structure and data semantics for PC5 parameters provisioning	Huawei, HiSilicon /Christian	pCR 24.486 Rel-16
C1-202235	V2X UE registration procedure corrections	Ericsson / Mikael	pCR 24.486 Rel-16
C1-202236	V2X UE de-registration procedure corrections	Ericsson / Mikael	pCR 24.486 Rel-16
C1-202237	V2X service discovery procedure corrections	Ericsson / Mikael	pCR 24.486 Rel-16
C1-202238	V2X service continuity procedure corrections	Ericsson / Mikael	pCR 24.486 Rel-16
C1-202458	Application unique IDs for the VAE layer	Huawei , HiSilicon /Christian	pCR 24.486 Rel-16
C1-202489	Network monitoring by the V2X UE procedure	Huawei, HiSilicon /Christian	pCR 24.486 Rel-16	Withdrawn
C1-202490	MIME types	Huawei, HiSilicon /Christian	pCR 24.486 Rel-16
C1-202544	XML scheme declaration for V2XAPP	Huawei, HiSilicon / Chen	pCR 24.486 Rel-16
C1-202545	V2X application resource management procedure	Huawei, HiSilicon / Chen	pCR 24.486 Rel-16
C1-202546	Structure and data semantics for V2X application resource management procedure	Huawei, HiSilicon / Chen	pCR 24.486 Rel-16
eV2XARC	Lena – Breakout	CT aspects of eV2XARC
C1-202010	Additional transport over Uu for V2X messages of V2X services identified by V2X service identifiers	Ericsson / Ivo	CR 0023 24.386 Rel-16
C1-202011	Configuration parameters for additional transport over Uu for V2X messages of V2X services identified by V2X service identifiers	Ericsson / Ivo	CR 0020 24.385 Rel-16
C1-202022	Incorrect reference	Ericsson / Ivo	CR 0001 24.587 Rel-16
C1-202104	PC5 unicast link security establishment	Qualcomm Incorporated / Lena	CR 0002 24.587 Rel-16
C1-202105	NR PC5 unicast security policy provisioning	Qualcomm Incorporated / Lena	CR 0003 24.587 Rel-16
C1-202106	NR PC5 unicast security policy provisioning	Qualcomm Incorporated / Lena	CR 0001 24.588 Rel-16
C1-202107	PC5 unicast link re-keying procedure	Qualcomm Incorporated / Lena	CR 0004 24.587 Rel-16
C1-202108	Adding general subclause on security of PC5 signalling messages	Qualcomm Incorporated / Lena	CR 0005 24.587 Rel-16
C1-202109	Introducing new messages for the Link Identifier Update procedure	InterDigital Communications	CR 0006 24.587 Rel-16	Tdoc was not available on time
C1-202115	Add the missing figure for UE-requested V2X policy provisioning procedure	OPPO / Rae	CR 0007 24.587 Rel-16
C1-202116	L2 ID of target UE used in the direct link establishment request	OPPO / Rae	CR 0008 24.587 Rel-16
C1-202117	Non-standadized QoS characteristics over PC5-S	OPPO / Rae	CR 0009 24.587 Rel-16
C1-202118	Remove FFS on GFBR and MFBR for UL and DL	OPPO / Rae	CR 0010 24.587 Rel-16
C1-202119	Group size and menber ID from application layer for groupcast	OPPO / Rae	CR 0011 24.587 Rel-16
C1-202159	Introducing NR PC5 functionality for EPC	LG Electronics / SangMin	discussion Rel-16
C1-202160	Introducing V2X communications over NR PC5 in EPC	LG Electronics / SangMin	CR 0024 24.386 Rel-16
C1-202161	V2X MO update for V2X over NR PC5	LG Electronics / SangMin	CR 0021 24.385 Rel-16
C1-202162	Indicating support of V2X over NR-PC5	LG Electronics / SangMin	CR 3344 24.301 Rel-16
C1-202163	Clarifications on configuration parameters for the PC5 QoS profile	LG Electronics / SangMin	CR 0012 24.587 Rel-16
C1-202164	Clarifications on the V2X policies regarding QoS	LG Electronics / SangMin	CR 0002 24.588 Rel-16
C1-202165	Update to the V2X policies regarding RAN parameters	LG Electronics / SangMin	CR 0003 24.588 Rel-16
C1-202181	Handling of link establishment accept	vivo	CR 0013 24.587 Rel-16
C1-202182	Handling of link modification accept	vivo	CR 0014 24.587 Rel-16
C1-202183	ENs resolving in modification pocedure	vivo	CR 0015 24.587 Rel-16
C1-202184	Updates to link release procedure	vivo	CR 0016 24.587 Rel-16
C1-202185	Correction of the timers of link identifier update procedure	vivo	CR 0017 24.587 Rel-16
C1-202186	Encoding of link identifier update messages and parameters	vivo	CR 0018 24.587 Rel-16
C1-202187	Handling of link identifier update not accept	vivo	CR 0019 24.587 Rel-16
C1-202188	Handling of PC5 unicast QoS flow match and establishment	vivo	CR 0020 24.587 Rel-16
C1-202189	Handling of PC5 broadcast QoS flow match and establishment	vivo	CR 0021 24.587 Rel-16
C1-202190	Requirements for groupcast over PC5	vivo	CR 0022 24.587 Rel-16
C1-202205	Work plan for the CT1 part of eV2XARC	Huawei, HiSilicon /Christian	discussion Rel-16
C1-202226	Correction to the privacy timer	Huawei, HiSilicon /Christian	CR 0024 24.587 Rel-16
C1-202316	Corection for the target user info in the DIRECT LINK ESTABLISHMENT REQUEST message	Huawei, HiSilicon / Chen	CR 0025 24.587 Rel-16
C1-202317	Correction for the IP address configuration IE in the DIRECT LINK ESTABLISHMENT ACCEPT message	Huawei, HiSilicon / Chen	CR 0026 24.587 Rel-16
C1-202318	Correction for the link local IPv6 address IE in the DIRECT LINK ESTABLISHMENT ACCEPT message	Huawei, HiSilicon / Chen	CR 0027 24.587 Rel-16
C1-202333	T3540 for service request for V2X communications	ZTE	CR 2111 24.501 Rel-16
C1-202416	Discussion on maximum nbr of PC5 unicast links	Huawei, HiSilicon / Vishnu	discussion 24.587 Rel-16
C1-202427	Maximum number of NR PC5 unicast links for a UE	Huawei, HiSilicon / Vishnu	CR 0029 24.587 Rel-16
C1-202434	PC5 QoS flow establishment during the PC5 unicast link establishment procedure	Huawei, HiSIlicon / Vishnu	CR 0030 24.587 Rel-16
C1-202438	Resolution of editor's note under 5.2.3	Huawei, HiSilicon /Christian	CR 0031 24.587 Rel-16
C1-202439	Resolution of editor's note under 6.1.2.5.2	Huawei, HiSilicon /Christian	CR 0032 24.587 Rel-16
C1-202453	Miscellaneous corrections	Huawei, HiSilicon /Christian	CR 0033 24.587 Rel-16
C1-202455	Resolution of editor's note under 6.1.2.3.6	Huawei, HiSilicon /Christian	CR 0034 24.587 Rel-16
C1-202456	Resolution of the editor's note under 6.1.2.5.7.2	Huawei, HiSilicon /Christian	CR 0035 24.587 Rel-16
C1-202457	Correction on conditions to initiate a PC5 unciast link establishment procedure	Huawei, HiSilicon / Vishnu	CR 0036 24.587 Rel-16
C1-202485	Packet filter for PC5 QoS flows	Huawei, HiSilicon / Vishnu	CR 0037 24.587 Rel-16
C1-202547	Direct link identifier update procedure messages definition and IEs coding	CATT	CR 0038 24.587 Rel-16
C1-202596	Defining new parameters needed for the Link Identifier Update procedure	InterDigital Communications	CR 0028 24.587 Rel-16	Revision of C1-202327
C1-202598	Timer values for timers of PC5 unicast link management procedures	Huawei, HiSilicon /Christian	CR 0023 24.587 Rel-16	Revision of C1-202225
RACS (CT4 lead)	Peter – Main	CT aspects of optimizations on UE radio capability signalling 100%
C1-202233	RACS parameters in generic UE configuration procedure	Ericsson / Mikael	CR 2078 24.501 Rel-16
5G_SRVCC (CT4 lead)	Peter – Main	CT aspects of single radio voice continuity from 5GS to 3G 100%
C1-202094	Introduce support for 5G SRVCC support indication when registering with EPS	BlackBerry Uk Ltd.	CR 3213 24.008 Rel-16	Alternative to C1-202133
C1-202095	Introduce support for 5G SRVCC support indication when registering with EPS	BlackBerry Uk Ltd.	CR 3290 24.301 Rel-16	Revision of C1-198012 Alternative to C1-202133
C1-202529	Initial Registration after 5G-SRVCC	ZTE, China Unicom	CR 2115 24.501 Rel-16	Revision of C1-202338
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
SEAL	Lena – Breakout	CT aspects of Service Enabler Architecture Layer for Verticals Is TS 24.548 sufficiently stable to be sent to CT#88 for approval?
C1-202137	Updates to User Authentication Client (SIM-C) procedure	Intel / Vivek	CR 0001 24.547 Rel-16
C1-202138	Updates to User Authentication Server (SIM-S) procedure	Intel / Vivek	CR 0002 24.547 Rel-16
C1-202139	Updates to Token Exchange Client (SIM-C) procedure	Intel / Vivek	CR 0003 24.547 Rel-16
C1-202140	Updates to Token Exchange Server (SIM-S) procedure	Intel / Vivek	CR 0004 24.547 Rel-16
C1-202209	Latest reference version of draft TS 24.548	Huawei, HiSilicon /Christian	draft TS 24.548 Rel-16
C1-202210	Wrong implementation of agreed p-CR C1-200881	Huawei, HiSilicon /Christian	pCR 24.548 Rel-16
C1-202211	Wrong implementation of agreed p-CR C1-200882	Huawei, HiSilicon /Christian	pCR 24.548 Rel-16
C1-202296	Updates to request for unicast resource at VAL service communication establishment procedure	Huawei, HiSilicon / Chen	pCR 24.548 Rel-16
C1-202297	Updates to structure and data semantics for request for unicast resource at VAL service communication establishment procedure	Huawei, HiSilicon / Chen	pCR 24.548 Rel-16
C1-202298	Request for modification of unicast resources procedure	Huawei, HiSilicon / Chen	pCR 24.548 Rel-16
C1-202299	Structure and data semantics for request for modification of unicast resources procedure	Huawei, HiSilicon / Chen	pCR 24.548 Rel-16
C1-202300	Network resource adaptation procedure	Huawei, HiSilicon / Chen	pCR 24.548 Rel-16
C1-202301	Structure and data semantics for network resource adaptation procedure	Huawei, HiSilicon / Chen	pCR 24.548 Rel-16
C1-202302	Structure and data semantics for MBMS bearer announcement over MBMS bearer procedure	Huawei, HiSilicon / Chen	pCR 24.548 Rel-16
C1-202303	Updates to MBMS bearer quality detection procedure	Huawei, HiSilicon / Chen	pCR 24.548 Rel-16
C1-202304	Structure and data semantics for MBMS bearer quality detection procedure	Huawei, HiSilicon / Chen	pCR 24.548 Rel-16
C1-202305	Use of pre-established MBMS bearers procedure	Huawei, HiSilicon / Chen	pCR 24.548 Rel-16
C1-202306	Structure and data semantics for use of pre-established MBMS bearers procedure	Huawei, HiSilicon / Chen	pCR 24.548 Rel-16
C1-202307	Use of dynamic MBMS bearers procedure	Huawei, HiSilicon / Chen	pCR 24.548 Rel-16
C1-202308	Service continuity in MBMS scenarios procedure	Huawei, HiSilicon / Chen	pCR 24.548 Rel-16
C1-202309	Structure and data semantics for service continuity in MBMS scenarios procedure	Huawei, HiSilicon / Chen	pCR 24.548 Rel-16
C1-202310	MBMS suspension notification procedure	Huawei, HiSilicon / Chen	pCR 24.548 Rel-16
C1-202311	Structure and data semantics for MBMS suspension notification procedure	Huawei, HiSilicon / Chen	pCR 24.548 Rel-16
C1-202312	MBMS bearer event notification procedure	Huawei, HiSilicon / Chen	pCR 24.548 Rel-16
C1-202313	Switching between MBMS bearer bearer and unicast bearer procedure	Huawei, HiSilicon / Chen	pCR 24.548 Rel-16
C1-202314	Resolution of editor's note on application unique ID	Huawei, HiSilicon / Chen	pCR 24.548 Rel-16
C1-202315	XML scheme declaration for SEAL network resource management	Huawei, HiSilicon / Chen	pCR 24.548 Rel-16
C1-202319	IANA registration template of SEAL location management	Huawei, HiSilicon / Chen	CR 0001 24.545 Rel-16
C1-202320	Removal of editor’s note on MIME types	Huawei, HiSilicon / Chen	CR 0002 24.545 Rel-16
C1-202321	Resolution of editor's note on application unique ID	Huawei, HiSilicon / Chen	CR 0003 24.545 Rel-16
C1-202322	Structure and data semantics for query list of users based on location procedure	Huawei, HiSilicon / Chen	CR 0004 24.545 Rel-16
C1-202323	XML scheme declaration for SEAL location management	Huawei, HiSilicon / Chen	CR 0005 24.545 Rel-16
C1-202440	Create SIP based subscription for SLM	Samsung, Huawei, HiSilicon / Sapan	CR 0006 24.545 Rel-16
C1-202441	Modify SIP based subscription for SLM	Samsung / Sapan	CR 0007 24.545 Rel-16
C1-202442	Delete SIP based subscription for SLM	Samsung / Sapan	CR 0008 24.545 Rel-16
C1-202443	Handling of abnormal cases for SIP based subscription in SLM	Samsung / Sapan	CR 0009 24.545 Rel-16
C1-202444	Message Formats for location management subscription	Samsung / Sapan	CR 0010 24.545 Rel-16
C1-202445	Timers used in location management	Samsung / Sapan	CR 0011 24.545 Rel-16
C1-202446	Annex for registering ICSI and MIME for SLM	Samsung / Sapan	CR 0012 24.545 Rel-16
C1-202447	SIP based subscribe/notify procedures for SEAL group management	Samsung / Sapan	CR 0001 24.544 Rel-16
C1-202448	Removal of Editor’s notes	Samsung / Sapan	CR 0002 24.544 Rel-16
C1-202449	Indication from SGM-S to SGM-C about group join required	Samsung / Sapan	CR 0003 24.544 Rel-16
C1-202450	SIP based subscribe/notify procedures for configuration management	Samsung / Sapan	CR 0001 24.546 Rel-16
C1-202451	Removal of Editor’s notes.	Samsung / Sapan	CR 0002 24.546 Rel-16
Other Rel-16 non-IMS issues	Peter – Main	Other Rel-16 non-IMS topics
C1-202083	Correction of certain erroneous Information Element Identifiers	InterDigital Communications	CR 2033 24.501 Rel-16
C1-202088	Clarification for the use of enhanced coverage in EPS	Samsung, Huawei, HiSilicon, InterDigital	CR 3339 24.301 Rel-16
C1-202148	SMS timer extension for the MS using CP CIoT 5GS optimization	NTT DOCOMO	CR 0066 24.011 Rel-16
C1-202178	Emergency PDN connection established after WUS negotiation	vivo	CR 3345 24.301 Rel-16
C1-202217	RPDU transfer for 5GS using Control Plane CIoT Optimization	NTT DOCOMO INC.	CR 0067 24.011 Rel-16
C1-202263	TA change during Authentication procedure in EMM-CONNECTED mode	Apple	CR 3347 24.301 Rel-16
C1-202264	TA change during Authentication procedure in 5GMM-CONNECTED mode	Apple	CR 2092 24.501 Rel-16
C1-202265	Considerations for AML over SMS in roaming scenarios	Apple	discussion Rel-16	Revision of C1-200606
C1-202267	Add handling for parameter set to “value is not used” in EPS	Qualcomm Incorporated	CR 3348 24.301 Rel-16
C1-202269	Allow lower layer to change RRC establishment cause during voice EPS fallback	Qualcomm Incorporated, Ericsson	CR 3316 24.301 Rel-16	Revision of C1ah-200048
C1-202273	Remove invalid cases in error handling for TFT operation	Qualcomm Incorporated	CR 3214 24.008 Rel-16
C1-202274	Remove invalid cases in error handling for TFT operation in EPS	Qualcomm Incorporated	CR 3350 24.301 Rel-16
C1-202334	Clarification on the UE behaviour when receiving T3448	ZTE	CR 3351 24.301 Rel-16
C1-202421	Definition of current PLMN and serving PLMN	Qualcomm Incorporated / Amer	CR 3354 24.301 Rel-16
C1-202466	WUS assistance for emergency	Huawei, HiSilicon/Lin	CR 3355 24.301 Rel-16
C1-202467	WUS assistance for TAU	Huawei, HiSilicon/Lin	CR 3356 24.301 Rel-16
C1-202468	Retry restriction for NB-IoT UEs due to out of tariff package	Huawei, HiSilicon/Lin	CR 3357 24.301 Rel-16
C1-202484	Correction on retry restriction for ESM#66	Huawei, HiSilicon/Lin	CR 3363 24.301 Rel-16
C1-202539	New AT command for linking packet filters +CGLNKPF	MediaTek Inc. / JJ	CR 0687 27.007 Rel-16
C1-202540	New AT command for deleting packet filters +CGDELPF	MediaTek Inc. / JJ	CR 0688 27.007 Rel-16
C1-202502	NAS Message Container 2 for LPP/LCS messages	MediaTek Inc., Qualcomm Incorporated	CR 3308 24.301 Rel-16	Revision of C1-198902
C1-202511	Reset of PLMN-specific attempt counter	MediaTek Inc.	CR 3364 24.301 Rel-16
C1-202512	Correction to Handling of T3321 timer	MediaTek Inc.	CR 3217 24.008 Rel-16
C1-202513	Correction to Handling of T3421 timer	MediaTek Inc.	CR 3365 24.301 Rel-16
C1-202520	Correction to handling of T3447 timer	MediaTek Inc.	CR 3370 24.301 Rel-16
WIs for IMS	Jörgen – Breakout
MCCI_CT	Mission Critical Communication Interworking with Land Mobile Radio Systems 100%
C1-202610	Editorial corrections	Sepura Ltd, Hytera Communications Corp	CR 0001 29.582 Rel-16	Revision of C1-202286 _________________________________________ Jörgen (Thu 19:48): Tick the CN box. Kit (Tue 16:54), Jörgen (Tue 17:11) Done, no further comments
MCProtoc16	Jörgen – Breakout	Protocol enhancements for Mission Critical Services for Rel-16 100%
C1-202223	Floor Request to Regrouped Group	FirstNet / Mike	CR 0229 24.380 Rel-16	Withdrawn Jörgen (Thu 21:02): Why define procedures for a state machine that is deleted at the same time? Mike (Thu 21:19, Fri 15:59), Francois (Fri 12:10, Fri 17:11): Discussion of the use case and how to best solve it. Mike (Fri 18:29): State machine needed, should go to Start-Stop. Jörgen (Sun 11:43): R: Merge takes the state machine to Start-Stop, so maybe it is already there? Kiran: (Mon 15:53): Should reason for ending the call go to all participants. Keep a note on urgency of the ongoing calls before ending.
C1-202555	Corrections to step reference in terminating controlling function	Samsung	CR 0560 24.379 Rel-16	Mike (Fri 22:44): OK
C1-202556	Corrections to step reference in create a group regroup using preconfigured group	Samsung	CR 0561 24.379 Rel-16	Mike (Fri 22:44): OK
C1-202557	Corrected the client origination procedure subclause text of 11.1.6.2.1.1	Samsung	CR 0562 24.379 Rel-16	Mike (Fri 22:44): OK
C1-202558	Allow an emergency and immenit peril calls during max simultaneous sessions	Samsung	CR 0563 24.379 Rel-16
C1-202630	Check regroup ID	FirstNet / Mike	CR 0553 24.379 Rel-16	Revision of C1-202220
C1-202631	Clarification of 11.1.6.2.1.2	FirstNet / Mike	CR 0554 24.379 Rel-16	Revision of C1-202221
C1-202632	Update affiliation definition to support preconfigured regroups	FirstNet / Mike	CR 0555 24.379 Rel-16	Revision of C1-202222 _________________________________________ Jörgen (Thu 21:03): Unclear definition. Mike (Thu 23:12), Francois (Fri 12:00), Mike (Fri 15:54), Francois (Fri 17:10), Kiran (Fri (17:40): Discussion on affiliation definition. Mike (Fri 19:08) Jörgen (Sat 18:44) Conclusion seems to be that simplified definition is to be provided by Mike. Francois (Tue 12:16): Fine with the revision
C1-202656	Check for MCPTT ID bindng and validity period of existing binding	Samsung	CR 0557 24.379 Rel-16	Revision of C1-202552 _________________________________________ Francois (Fri 12:44): Some missing steps Kiran (Fri 13:47): Acknowledges. Kiran (Tue 09:23), Francois (Tue 12:22): revision in drafts folder, Francois agree.
C1-202657	Corrections to location sharing during call setup	Samsung	CR 0558 24.379 Rel-16	Revision of C1-202553 _________________________________________ Jörgen (Thu 21:12): Some editorials and styles guidelines. Kiran (Fri 10:55): Checking understanding. Jörgen (Sun 15:43), Kiran (Mon 11:15), Mike (Mon: 15:07), Kiran (Mon 15:18), Jörgen (Mon 17:10): Seems to have converged on the wording. Kiran (Tue 09:23): revision in drafts folder
C1-202658	Corrections to current talker location in ambient call	Samsung	CR 0559 24.379 Rel-16	Revision of C1-202554 _________________________________________ Jörgen (Thu 21:16): Is note same as bullet b). Some editorial. Kiran (Fri 11:23): Checking understanding Mike (Fri 16:28): Further comment. Jörgen (Mon 15:03), Kiran (Mon 15:03): Seems converging on the wording. Further comments awaited. Kiran (Tue 09:25): revision in drafts folder
C1-202659	Authentication of the MIKEY-SAKKE I_Message validation in pre-established session	Samsung	CR 0230 24.380 Rel-16	Postponed Revision of C1-202559 _________________________________________ Jörgen (Thu 21:19): Should Reason Code field be updated instead? Kiran (Fri 11:41): Prefer Warning text. Jörgen (Sun 16:11): Not convinced, not clear which text to insert. Kiran (Mon 13:21): Text messages and the mechanism exist. Mike (Mon 15:37): Text is likely of minor value, but should continue to use it unless good reason. Kiran (Tue 09:35): revision in drafts folder. Jörgen (Tue 17:04), Still not convinced, should be Cat B, which code to provide is no specific enough. Francois (Tue 17:24): Agree to not use text from 24.379. Prefer reason code. Why warning added to Disconnect message, it is not used.
C1-202660	Talker location sharing in remote ambient call	Samsung	CR 0231 24.380 Rel-16	Revision of C1-202560 _________________________________________ Jörgen (Thu 21:21): Some clarifications needed. Kiran (Fri 12:36): Checking understanding. Jörgen (Sun 16:37), Kiran (Mon 13:53): Seems converging, await further comments before revising. Kiran (Tue 09:40): revision in drafts folder. Jörgen (Tue 18:15), remaining editorial Kiran (Wed 09:30) Ack, will be fixed. Seems to have converged.
C1-202834	Authorisation validation for first-to-answer call origination requesting user using pre-established session	Samsung	CR 0556 24.379 Rel-16	Revision of C1-202655 _________________________________________ Revision of C1-202551 _________________________________________ Francois (Fri 12:29, 17:15), Kiran (Fri 13:14): Discussion if this should be done in other places. Jörgen (Thu 21:10): Validation misplaced Kiran (Fri 08:39): Ack, and proposes alternatives Mike (Fri 16:23): States a preference Jörgen (Sun 17:44), Mike (Mon 05:49), Kiran Mon (08:42): Different text proposals. Seems to have converged. Kiran (Tue 09:10), Francois (Tue 12:19), Jörgen (Tue 13:11): revision in drafts folder. Francois and Jörgen are fine. Mike Tue and Kiran Wed agree on a further editorial
MuD	Jörgen – Breakout	Multi-device and multi-identity 100%
C1-202494	Text for empty headings	Ericsson /Jörgen	CR 0001 24.174 Rel-16
C1-202586	Reference update for PASSporT Extension for Diverted Calls	Orange / Mariusz	CR 0002 24.174 Rel-16
IMSProtoc16	Jörgen – Breakout	IMS Stage-3 IETF Protocol Alignment for Rel-16 100%
C1-202167	Adding the definition and criteria for availability of IMS Data Services	MediaTek Inc., Apple	CR 6415 24.229 Rel-16	Frederic (Thursday 13:13): Styles corrupted, mark which clauses are new, remove and in bullet 1) and 2) of B.3.1.2B and U.3.1.2B. Simon (Thu 18:03): Not needed. References previous discussions. See the mail. Jörgen (Thu 21:33): Indicate dependency to NAS contribution. Data off might need stage 1, some other details. Rohit (Fri 06:17, 07:38): Useful for RCS, data should be separated from voice. Will indicate dependency and fix issues in update. Can stage 1 be added later? Takayuki (Fri 09:22): Is IMS data services defined somewhere? Bill (Sat 8:53): See no need. Rohit (Mon 03:12): Further motivations why this is necessary. Simon (Mon 19:00), Rohit (Tue 11:30): Further discussion and no conclusion yet. Simon (Wed 05:40), Rohit (Wed 11:33), Yoshihiro (Wed 12:49): No convergence between Simon and Rohit. Yoshir asking about stage1/stage2 requirements.
MCSMI_CT	Jörgen – Breakout	Mission Critical system migration and interconnection
eMCData2	Jörgen – Breakout	CT aspects of Enhancements to Functional architecture and information flows for Mission Critical Data
C1-202637	Deposit an object	AT&T	CR 0118 24.282 Rel-16	Revision of C1-202023 _________________________________________ Frederic (Thu 14:23): Cover sheet issues: - Wrong rev counter: should have been ‘-‘. This also applies to several CRs of this set: C1-202024, 2026, 2027, 2028, 2029, 2030 Jörgen (Fri 15:43): Some editorials, question on configuration. Shahram (Fri 16:48, Fri 17:34): Responses Shahram (Sat 05:35): Typo in previous mail Jörgen (Sun 16:53): Any MO in 24.483? Shahram (Mon 09:22): This is the server that is configured. Should MO clauses reference RCC.14? Jörgen (Mon 19:01): Clarification of previous comments. Shahram (Tue 09:26): [draft] C1-202637 was C1-202023.docx is now available in inbox/drafts.
C1-202640	Create a subscription to notifications	AT&T	CR 0119 24.282 Rel-16	Revision of C1-202024 _________________________________________ Jörgen (Mon 11:43): Bullets 1) and 2 should be merged. Shahram (Tue 09:27): [draft] C1-202640 was C1-202024.docx is now available in inbox/drafts.
C1-202641	Delete a subscription to notifications	AT&T	CR 0120 24.282 Rel-16	Revision of C1-202025 _________________________________________ Shahram (Tue 09:28): [draft] C1-202641 was C1-202025.docx is now available in inbox/drafts.
C1-202643	Update a subscription to notifications	AT&T	CR 0121 24.282 Rel-16	Revision of C1-202026 _________________________________________ Jörgen (Mon 11:45): and/or in first bullet to be avoided. Shahram (Mon 12:35): Text proposed. Shahram (Tue 09:28): [draft] C1-202643 was C1-202026.docx is now available in inbox/drafts.
C1-202646	Synchronization notification	AT&T	CR 0122 24.282 Rel-16	Revision of C1-202027 _________________________________________ Frederic (Thu 14:26): Some comments: - As already indicated, wrong rev counter on cover sheet - Discrepancy between clauses affected, which specify 21.2.16 and the actual changes, which use .X - No need to number the new note Shahram (Fri 19:26), Jörgen (Sun 17:13), Shahram (Mon 10:15), Jörgen (11:15): Some further discussion of style in text. Shahram (Tue 09:29): [draft] C1-202646 was C1-202027.docx is now available in inbox/drafts.
C1-202647	Search-based Synchronization	AT&T	CR 0123 24.282 Rel-16	Revision of C1-202028 Jörgen (Mon 12:58): Two minor editorials: There are curly quotes and recepectivelyrespectively. Shahram (Tue 09:29): [draft] C1-202647 was C1-202028.docx is now available in inbox/drafts.
C1-202649	List folder	AT&T	CR 0124 24.282 Rel-16	Revision of C1-202029 _________________________________________ Shahram (Tue 09:30): [draft] C1-202649 was C1-202029.docx is now available in inbox/drafts.
C1-202677	Typo fixes	AT&T	CR 0125 24.282 Rel-16	Revision of C1-202030 _________________________________________ Frederic (Thu 14:17): Cover sheet issues: - Wrong rev counter: should have been ‘-‘ - Source to TSG should be C1.
C1-202750	Configuration of resource priority for MCData emergency	AT&T / Val	CR 0137 24.484 Rel-16	Revision of C1-202386 _________________________________________ Kiran (Thu 12:25): 1) New elements shall be added to AddExt elements. 2) The schema shouldn't be changed in my understanding. 3) Update the MCPTT reference with MCData as it is for MCData service. Val (Sun 04:21, Sun 20:59): draft rev1 C1-202386 available in drafts folder. Mike (Mon 18:20), Kiran (Tue 16:42): Fine with the revision.
C1-202751	Auxiliary procedures in support of Emergency Alerts for MCData	AT&T / Val	CR 0130 24.282 Rel-16	Revision of C1-202288 _________________________________________ Kiran (Thu 12:25): The subclause 6.3.7.1.1 shall be added once we include the emergency flows for the MCData sub functionalities such as SDS and FD. As both the sub-services has session and non-session based flows and requires careful considerations. Val (Sun 06:36, Mon 08:42): Editor's note added, draft_rev1_C1-202288_24282CR130_AuxProcEmrgAlrt_MCData.doc in draft folder. Kiran (Tue 15:33): Fine with revision.
C1-202754	Handling of MCData Emergency Alerts at the MCData controlling server	AT&T / Val	CR 0129 24.282 Rel-16	Revision of C1-202287 Kiran (Thu 12:45): The 'emergency-ind' handling procedures may be added later once we bring the communication related procedures. - In subclause 16.2.3.2, Which covers the indication 'emergency-ind' shall be removed. We should cover only for the emergency alert functionalities as per the CR. Val (Sun 06:25, Mon 07:55): Prefer keeping the functions, will add editor's notes, uploaded draft_rev1_C1-202287_24282CR129_EmrgAlrt_MCData_cntrlingSrvr.doc to drafts folder. Kiran (Tue 15:42): Fine with revision.
C1-202755	Handling of MCData Emergency Alerts at the MCData participating servers	AT&T / Val	CR 0128 24.282 Rel-16	Revision of C1-202281 _________________________________________ Kiran (Thu 12:45): The 'emergency-ind' handling procedures may be added later once we bring the communication related procedures. In subclause 16.2.2.2, The step 1) which covers the indication 'emergency-ind' shall be removed. We should cover only for the emergency alert functionalities as per the CR. Francois (Fri 15:04, 17:21), Mike (16:15): Further discussion on applicability of the note. Val (Sun 02:38, Sun 06:20, Mon 06:46): Some responses, and draft_rev1_C1-202281_24282CR128_EmrgAlrt_MCData_participSrvr.doc uploaded in the drafts folder. Francois Tue (12:24), Kiran (14:08, 15:45): Fine with the revision
C1-202761	Emergency Alerts for MCData – client procedures	AT&T / Val	CR 0127 24.282 Rel-16	Revision of C1-202262 _________________________________________ Kiran (Thu 12:44): 1) The 'emergency-ind' and 'MCData emergency group communication state' handling procedures may be added later once we bring the communication related procedures. 2) The steps 2) c), 3) and 4) in subclause 16.2.1.3, shall not be included as there are no relevant procedures are available. As per the CR, we should cover only for the emergency alert functionalities. 3) In subclause 6.2.1.1, the indication 'emergency-ind' shall be removed from the description. Val (Sun 04:40, Mon (06:12): Response to Kiran's points. Will use editor's notes. Uploaded draft_rev1_C1-202262_24282CR127_EmrgAlrt_MCData_client.doc in the drafts folder Val (Tue 09:33), Kiran (Tue 14:07, Tue 15:32): Rev 2 of draft, Kiran OK with way forward and rev 2. Draft: draft_rev2_Obsoletes_rev1_C1-202262_24282CR127_EmrgAlrt_MCData_client.doc
C1-202771	Support for MCData emergency alert and communications	AT&T / Val	CR 0126 24.282 Rel-16	Revision of C1-202260 _________________________________________ Kiran (Thu 12:27): Some thoughts on this CR, and mostly apply to similar CRs: We should cover for the emergency alert functionalities as of today as we have other supporting CRs for the emergency alert functionalities. The subclause related to communication shall be added once we include the emergency flows for the MCData sub functionalities such as SDS and FD. As both the sub-services has session and non-session based flows and requires careful considerations. Val (Sun 04:28, Sun 22:15): Response to Kirans comment, draft uploaded in drafts folder. Jörgen (Mon 13:24): Align affiliation with Mike's 2222, schema not BW compatible. Mike (Mon 18:28), Val (Tue 09:10), KiranTue (13:58, 15:32): Common understanding of definition and adding Editor's Notes. Abhishek (Tue 18:58): Define MCData emergency alert and MCData emergency communication.
C1-202794	Fix minor issues in MCData pre-etsblished session	Samsung / Sapan	CR 0131 24.282 Rel-16	Revision of C1-202452 Sapan (Mon 20:44): Offline comments to improve cover sheet. Draft revision in: https://www.3gpp.org/ftp/tsg_ct/WG1_mm-cc-sm_ex-CN1/TSGC1_123e/inbox/drafts/C1-202452_eMCData2_Minor_Fixes_in_Pre-established_session_draft_rev_v1.zip
C1-202835	Corrections to file upload-download procedure as per stage 2 architecture changes	Samsung	CR 0133 24.282 Rel-16	Revision of C1-202654 _________________________________________ Revision of C1-202550 _________________________________________ Kiran (Tue 09:51): draft available with CR# in EN. Jörgen (Tue 11:25), Kit (Tue 11:42): Is the granularity of MCData client structure needed? Kiran (Tue 17:18): It is more exact and is used in other places. Prefer to agree and come back with new CR if needed. Mike (Wed 17:02), Kiran (Wed 17:48): Further discussion on client terminology.
E2E_DELAY (CT4)	Jörgen – Breakout	CT Aspects of Media Handling for RAN Delay Budget Reporting in MTSI 100%
VBCLTE (CT3 lead)	Jörgen – Breakout	Volume Based Charging Aspects for VoLTE CT
ISAT-MO-WITHDRAW	Jörgen – Breakout	Withdrawal of TS 24.323 from Rel-11, Rel-12, Rel-13 No CRs needed, listed for the sake of completeness 100%
MONASTERY2	Jörgen – Breakout	Mobile Communication System for Railways Phase 2
C1-202566	Work plan for the CT1 part of MONASTERY2	Nokia, Nokia Shanghai Bell	discussion Rel-16	Noted
C1-202567	Sub/Notify FA resolution analysis	Nokia, Nokia Shanghai Bell	discussion Rel-16	Noted Francois (Fri 16:40): Disagrees with comments on cons with SUBSCRIBE/NOTIFY.
C1-202569	Update service configuration to support limiting the number of authorized clients per MCPTT user	Nokia, Nokia Shanghai Bell	CR 0139 24.484 Rel-16	Postponed Kirin (Thursday 11:09): Harmonize the wordings from stage 2 to avoid the confusion. For e.g 'if the number of simultaneous service authorizations for that MCPTT user " Francois (Fri 17:00): Should be user profile? Lazaros (Tue 13:22), Francois (13:50), Kiran (16:27), Lazaros (17:26), Francois (17:54): Kiran fine with handling of his comments. Francois wants LS to SA1 (ccSA6) to ask if a parameter is in service configuration or user profile. LS proposed to be sent to SA1, cc SA6.
C1-202883	IPConnectivity extension to include IP Information	Kontron Transportation France	CR 0067 24.483 Rel-16	Revision of C1-202496 _________________________________________ Jörgen (Fri 18:38): Nodenode in the table cells. Leaf nodes should have a format other than "node" Peter B (Tue 09:56): uploaded revision, also off-line comments: https://www.3gpp.org/ftp/tsg_ct/WG1_mm-cc-sm_ex-CN1/TSGC1_123e/inbox/drafts/C1-202496-24483-CR0067%20IP%20Connectivity%20Extension%20to%20include%20IP%20Information-rev1.docx Jörgen (17:15): Minor editorial Nodenode in the table cells.
C1-202884	IPConnectivity extension to include IP Information	Kontron Transportation France	CR 0138 24.484 Rel-16	Revision of C1-202497 _________________________________________ Kiran (Thursday 11:30): -The section 10.3.2.3, the type="IPInformationListEntryType" should be appended with 'mcdataup:' Result: type="mcdataup:IPInformationListEntryType" -The structure in 10.3.2.1 should expand the IPInformation element with all the sub-elements. Pedro (Thu 18:51) Francois (Friday 15:57) Jörgen (Fri 16:33): Further comments, see the mails. Pedro will help Peter in revising. Peter (Tue 10:01): draft uploaded Francois (Tue 12:02): Minor typo Kiran (Tue 16:21): Seems fine, MinOccurs and MaxOccurs can be harmonized Jörgen (Tue 17:27): Minor editorial, or can be comma.
C1-202885	IPConnectivity extension to include IP Information	Kontron Transportation France	CR 0132 24.282 Rel-16	Revision of C1-202498 _________________________________________ Kiran (Thursday 11:31): 1) Cover page: Reason for change: Needs re-wording as it doesn't provide the information of using pre-defined IP information of the user from user profile configuration can be used for IP connectivity. 2) The proposed text can be re-worded by removing 'Depending on implementation' from the beginning of text and retaining the remaining portion of the text. 3) It's not clear whether the IP information is used in the INVITE request while setting up or determine the MC ID based on the IP information present in the user configuration by comparing with IP connectivity resolved to target. Jörgen (Fri 16:42): Some further questions Peter (Tue 10:01): draft uploaded Kiran (Tue 16:05): Change back to 24.484 Peter (Tue 17:23), Jörgen (Tue 17:47): OK to change back. Peter (Tue 20:49) will use 24.484.
C1-202905	Resolution of called functional alias in first-to-answer calls	Nokia, Nokia Shanghai Bell	CR 0564 24.379 Rel-16	Revision of C1-202568 _________________________________________ Kiran (Thursday 11:09): - In subclause 11.1.1.4.2, step 12) a) can be reworded from "by generating a SIP INVITE request as specified in subclause 9A.2.2.2.x;" to "by performing actions as specified in subclause 9A.2.2.2.x;". - In subclause 9A.2.2.2.x, There is no end quote for 'Upon receipt of a "'. - In subclause 9A.2.2.2.x, the heading can be reworded from "Functional alias resolution from MCPTT server owning functional alias procedure" to either "Sending functional alias resolution request towards MCPTT server owning the functional alias procedure" or "Receiving functional alias resolution request from MCPTT client procedure". - In subclause 9A.2.2.3.x, the heading can be reworded from "Functional alias resolution procedure" to "Receiving functional alias resolution request procedure". - In subclause 9A.2.2.2.x, the new INVITE request has been generated and sent to the MCPTT server owning the Functional alias, on receiving the response there is no procedure defined to respond back to the request which is received. - In subclause 11.1.1.4.2, step 12) b) can be reworded based on above point and shouldn't refer to 9A.2.2.3.x. Shall refer to same entity handling request and response - In subclause 9A.2.2.3.x, step 2) a) and b) of the response will have duplicate copy of data. We need to somehow manage to have one copy of data. Francois (Fri 16:53): Security issues with MCPTT ID, <mcptt-request-uri> element does not support a list.
eIMS5G_SBA	Jörgen – Breakout	CT aspects of SBA interactions between IMS and 5GC
C1-202066	No impact from SBA on main body	Nokia, Nokia Shanghai Bell, Ericsson	CR 6408 24.229 Rel-16	Revision of C1-200353
C1-202675	Support scenario where the SCC AS sends a request to the HSS to retrieve the SRVCC data for the UE	BlackBerry UK Ltd.	CR 1299 24.237 Rel-16	Merged into C1-202837 and its revisions Revision of C1-202099 _________________________________________ Ivo (Thursday 13:47):- the 5G SRVCC should be indicated using "ue5GSrvccCapability". - UDM is unaware of UE's capability for SRVCC from E-UTRAN to GERAN/UTRAN as the UE only indicates this capability in EPS. John-Luc (Thursday 17:45): Whether or not the UDM knows this capability is not relevant in this CR. Please note that Nhss_imsSubscriberDataManagement Service API is between the SCC AS and HSS, per subclause 4.1 of 29.562. TS 29.526 actually specifies an attribute by the name “ueSrvccCapabilities”, which is an array of capabilities Ivo (Friday 14:44): the comments still stand: - UDM is unaware of UE's capability for SRVCC from E-UTRAN to GERAN/UTRAN as the UE only indicates this capability in EPS. John-Luc (Friday 14:47): How does the comment apply to the CR? The behavior specified in the CR is based on informati0on received from the HSS, not from the UDM. Ivo (Tue 01:10, 11:15), John-Luc (Tue 02:03, 16:16): Continued discussion. After todays conf call now discussion on merging.
enh2MCPTT-CT	Jörgen – Breakout	Enhancements for Mission Critical Push-to-Talk CT aspects 100%
eIMSVideo	Jörgen – Breakout	Video enhancement of IMS CAT/CRS/announcement services
C1-202817	Restrictions of providing video announcement	China Telecom,Huawei,China Unicom,HiSilicon / Michelle	CR 0076 24.628 Rel-16	Revision of C1-202356 _________________________________________ Yoshihiro (Mon 16:17): This is too restrictive. Proposes a Note. Jörgen (Mon 22:59): Is this a real or theoretical problem? Michelle (Tue 08:10), Jörgen (Tue 14:00), Helen (14:34), Jörgen (16:15), Michelle (Tue 16:15): Some further discussion. Note proposal by Jörgen Yoshihiro (Tue 16:29): Fine with Jörgen's text.
C1-202863	Use preconditions for CRS when terminating UE supports precondition	Huawei,China Telecom,China Unicom,HiSilicon /Hongxia	CR 0063 24.183 Rel-16	Revision of C1-202605 _________________________________________ Revision of C1-202156 _________________________________________ Simon (Thu 18:32): Statement that UE indicates Support for precondition in 18x without receiving support indication in INVITE breaks 24.229. Jörgen (Thu 21:56): Agree on the 18x issue, somewhat problematic to offer new media in UPDATE as the user cannot indicate consent and resources most likely not available. Helen (Fri 11:51): Don't want to add precondition in INVITE. Can AS use precondition anyway based on local policy? Simon (Sat 00:36) Not possible according to 24.229. Helen (Sat 11:38), Jörgen (Sun 23:05), Simon (Mon 05:13), Helen (Mon 05:17): Some further description on principles. Seems to start converging. Simon (Mon 20:17), Jörgen (Mon23:13), Helen (Tue 04:25): Some comments on precondition to term side, new draft uploaded: draft 2605 Jörgen (Tue 15:04): Answers to questions
C1-202891	Use preconditions for CAT when originating UE supports precondition	Huawei,China Telecom,China Unicom,HiSilicon /Hongxia	CR 0119 24.182 Rel-16	Revision of C1-202604 _________________________________________ Revision of C1-202155 _________________________________________ Jörgen (Thu 21:46) NOTE: No Tdocnumber in Subject line: Text needs more work, some wording proposals. Helen (Fri 10:54): Agree to some comments, som responses on others. Yoshihiro (Fri 16:47): The change from "the originating UE requires" to "if the AS sends an 18x…" seems to change the meaning Helen (Sat 04:18), Yoshihiro (Mon 16:02): Continued discussion. One of the issues is how optional use of preconditions is for CAT media if preconditions is negotiated end to end. Jörgen (Mon 23:48): Issues with current text. Hiroshi: (Tue 04:10): issuse with can or may, partly cover sheet. Helen: Tue 11:29): checking wording of one paragraph.
Other Rel-16 IMS & MC issues	Jörgen – Breakout	Other Rel-16 IMS topics
C1-202072	Correction in CRS interactions with CDIV	Orange / Mariusz	CR 0062 24.183 Rel-16
C1-202080	UE must not render local tones in case of call is being forwarded or call is queued	Qualcomm Incorporated	CR 0075 24.628 Rel-16
C1-202081	NG eCall support over NR connected to the 5GC	Qualcomm Incorporated	CR 6414 24.229 Rel-16
C1-202132	Discussion on SRVCC from E-UTRAN to GERAN/UTRAN when IMS voice call is initiated in 5GS	Ericsson / Ivo	discussion Rel-16	Noted Revision of C1-200940
C1-202759	Correction in IMS_Registration_handling policy about how UE should deregister	MediaTek Inc.	CR 6404 24.229 Rel-16	C1-202090 was proived on time and has been reviewed. C1-202590 was revised before submission and not provided. This document is considered a revision of C1-202090. Revision of C1-202590 _________________________________________ Not provided on time Revision of C1-202090 Revision of C1-199028
C1-202837	SRVCC from E-UTRAN to GERAN/UTRAN when IMS voice call is initiated in 5GS	Ericsson / Ivo	CR 1298 24.237 Rel-16	Revision of C1-202133 _________________________________________ Revision of C1-200941 Alternative to C1-202094 – C1-202097 John-Luc (Thu 19:32): Overlap with C1-202099, may need changes. Several comments, see the mail: -misuse of g.3gpp.accesstype -no rel-15 support -diverges from Rel-10 principles -missing use case at SCC AS -a condition in D.3.3 is included but not defined. Ivo (Fri 14:39): General disagreement with John-Luc. The reader is referred to the mail, this margin is too small. John-Luc (Fri 22:50), Ivo (Mon 10:14), John-Luc (Mon 15:06). Further comments on the conditions, still clash with C1-202099. Latest draft revision in https://www.3gpp.org/ftp/tsg_ct/WG1_mm-cc-sm_ex-CN1/TSGC1_123e/inbox/drafts/C1-20iaea-was-C1-202133-was-C1-200941-was-C1-200674-v01.zip
C1-202887	Correction on rendering local tones	Ericsson /Jörgen	CR 0077 24.628 Rel-16	Postponed Revision of C1-202500
C1-202917	Editorial clean-up	Ericsson /Jörgen	CR 0064 24.183 Rel-16	Revision of C1-202785 _________________________________________ Revision of C1-202488 _________________________________________ Helen (Thu 13:54): Why not use GW model for CRS? "The media types can be…": With this change, it seems not cover audio CRS in video call. 4.3.1.2 and 4.3.1.3: The network needs to support AS actions, so different requirements. maybe there is a typo in the change of 4.3.1.3, “originating” should be ” terminating” Mariusz (Thu 14:27): 4.5.5.3.6: Remove comment, insert space in are-INVITE. Jörgen (Thu 22:15): Agree with Mariusz. Response to Helen. Helen (Fri 22:15) Jörgen (FriI (17:29): Ongoing discussion, mainly of the applicability of gateway model towards terminating user. Helen (Sat 11:56), Jörgen (Sun 23:16), Helen (Mon 05:07), Rohit (Mon 05:27): Further discussion on terminology, clarifying viewpoints.
Release 17 work items	Tdoc	NOT PART OF THIS MEETING
Output Liaison Statements	Tdoc	Title	Prepared by	To/CC	Result & comment
C1-202012	Reply LS on Manual CAG ID selection and granularity of UAC parameters for PNI-NPNs	Ericsson / Ivo	LS out Rel-16	Reply to incoming LS in C1-202045
C1-202067	Reply LS on 5G Steering of Roaming	Orange / Mariusz	LS out Rel-16	Reply to incoming LS in C1-202041
C1-202103	Reply LS on Manual CAG ID selection and granularity of UAC parameters for PNI-NPNs	Qualcomm Incorporated / Lena	LS out Rel-16	Reply to incoming LS in C1-202045
C1-202151	LS on subscribe/notify for 5G Steering of Roaming	DOCOMO Communications Lab.	LS out Rel-16	Reply to incoming LS in C1-202041
C1-202180	[draft] Reply LS on Manual CAG ID selection and granularity of UAC parameters for PNI-NPNs	vivo	LS out Rel-16	Reply to incoming LS in C1-202045
C1-202204	LS on PWS Test Flag	one2many B.V.	LS out Rel-16
C1-202232	LS on Concurrent Broadcasting for CMAS	Ericsson / Mikael	LS out Rel-15	Reply to incoming LS in C1-202046/C1-202597
C1-202400	LS on manual CAG selection	Nokia, Nokia Shanghai Bell	LS out Rel-16	Revision of C1-201053
C1-202474	LS on handling pending NSSAI during ongoing NSSAA	Huawei, HiSilicon/Lin	LS out Rel-16
C1-202487	LS on 3GPP based access authentication for untrusted non-3GPP access to 5GCN	Ericsson / Ivo	LS out Rel-16
C1-202564	Reply LS on concurrent Broadcasting for CMAS	Samsung/ Kyungjoo Grace Suh	LS out Rel-15	Reply to incoming LS in C1-202046/C1-202597
C1-202240	Reply LS to RAN2 on Manual CAG selection	Huawei, HiSilicon / Vishnu	LS out Rel-16	Shifted from 16.2.7.2 Reply to incoming LS in C1-202045
C1-202359	LS response on Manual CAG ID selection and granularity of UAC parameters for PNI-NPNs	Samsung/Kundan	LS out Rel-16	Shifted from 16.2.7.1 Reply to incoming LS in C1-202045
C1-202819	LS on limit the number of simultaneous log ins of an MCX	Nokia /Lazaros	LS out Rel-16	Endorsed by IMS BO
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
C1-202135	Discussion on SRVCC and 5G-SRVCC NAS capabilities vs. IMS based solution	BlackBerry UK Limited	discussion Rel-15	Withdrawn Not available on time
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 23rd April 2020 16:00 CEST Last comments: Friday 24th April 2020 16:00 CEST Chairman Report of the meeting: Monday 27th April 2020