3GPP TSG CT WG1 Meeting#127bis-e	C1-210004

Electronic meeting, 25-29 January 2021

Meeting documents by agenda item Meeting: Meeting #127bis-e Electronic meeting 25 - 29 January 2021 All indicated times are UTC (except timestamps for comments during the e-meeting, which are in CET)
Cyan background means allocated but not available.	Yellow background means available but not yet treated document.	Green background means this document was agreed at a revious meeting in this plenary cycle.	White background means that the document has been handled in the meeting and a decision has been made.
Additional Colour coding for Tdocs in the 1st row
Late Papers
Easy and uncontroversial papers – can be presented within 2 minutes
Papers for common sessions
Low Priority
Agenda item	Agenda item title	Tdoc	Title	Source	Spec	Result
Opening & welcome	Tdoc	Title	Source	Spec	Result
IPR Policy Reminder to Individual Members and the persons making the technical proposals about their obligations under their respective Organizational Partners IPR Policy: I draw your attention to your obligations under the 3GPP Partner Organizations' IPR policies. Every Individual Member organization is obliged to declare to the Partner Organization or Organizations of which it is a member any IPR owned by the Individual Member or any other organization which is or is likely to become essential to the work of 3GPP.
Antitrust & Competition I also draw your attention to the fact that 3GPP activities are subject to all applicable antitrust and competition laws and that compliance with said laws is therefore required of any participant of this TSG/WG meeting including the Chair 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.
Please remember: - to perform the electronic registration before end-of-meeting - to wear your badge
Agenda & Reports	Tdoc	Title	Source	Doctype	Result & comments
C1-210001	3GPP TSG CT1#127bis-e – agenda for Tdoc allocation	CT1 chair	agenda
C1-210002	3GPP TSG CT1#127bis-e – agenda after Tdoc allocation deadline	CT1 chair	agenda
C1-210003	3GPP TSG CT1#127bis-e – agenda with proposed LS-actions	CT1 chair	agenda
C1-210004	3GPP TSG CT1#127bis-e – agenda at start of meeting	CT1 chair	agenda
C1-210005	3GPP TSG CT1#127bis-e – agenda Thursday evening	CT1 chair	agenda
C1-210006	3GPP TSG CT1#127bis-e – agenda at end of meeting	CT1 chair	agenda
C1-210007	draft C1-127 meeting report	MCC	report
Highest number C1-210261
Agenda Tdoc reservation deadline: Monday 18th January 11:00 UTC Tdoc submission deadline: Monday 18th January 14:00 UTC Start of e-meeting: Monday 25th January 08:00 UTC Comment Free Time Thursday 28th January 11:00 - 15:00 UTC Last revision upload: Thursday 28th January 15:00 UTC Last comments: Friday 29th January 15:00 UTC 1 Opening 2 Agenda and Reports 3 work organization 4 incoming LS (22) Rel-14 and earlier: Not on agenda Rel-15: Not on agenda Rel-16: Agenda Items from 16.1 Not on agenda Agenda Items from 16.2 Not on agenda Agenda Items from 16.3 Not on agenda Rel-17: Agenda Items from 17.1 17.1.1 Work Item descriptions (11) 17.1.2 CRs and disc related to new/revised work items (4) 17.1.3 Status of other work items () 17.1.4 Rel-17 docs for information (1) Agenda Items from 17.2 17.2.1 not on agenda () 17.2.2 not on agenda () 17.2.3 eCPSOR_CON (20) 17.2.4 5GSAT_ARCH-CT (42) 17.2.5 SMS_SBI (0) 17.2.6 AKMA-CT (8) 17.2.7 PAP_CHAP (1) 17.2.8 RDSSI (0) 17.2.9 FS_MINT-CT (73) 17.2.10 EDGEAPP (7) 17.2.11 not on agenda () Agenda Items from 17.3 17.3.1 not on agenda () 17.3.2 not on agenda () 17.3.3 FS_eIMS5G2 (7) 17.3.4 MuDe (8) 17.3.5 MPS2 (1) 17.3.6 eMCData3 (3) 17.3.7 MCSMI_CT (0) 17.3.8 eMCCI_CT (0) 17.3.9 enh3MCPTT-CT (13) 17.3.10 eMONASTERY2 (7) 17.3.12 not on agenda () 18 outgoing LS (7)
Work organisation	Tdoc	Title	Source	To / CC	Result & comments
Meeting schedule
CT1 and CT plenary meeting dates.
Date	Meeting	Venue
25 – 29 January 2021	CT1#127bis-e	Electronic Meeting
01 – 05 March 2021	CT1#128	Cancelled
25 Feb - 05 March 2021	CT1#128-e	Electronic Meeting
22 – 24 March 2021	CT plenary#91e	Electronic Meeting
19 – 23 April 2021	CT1#129	Tbd
24 – 28 May 2021	CT1#130	Tbd
14 – 16 June 2021	CT plenary#92e	Electronic Meeting
Work Plan and other adm. issues	Tdoc	Title	Source	Spec / doctype	Result & comments
C1-210008	work plan	MCC	Work Plan
C1-210025	Decision making– Show of hands via email	CT1 Chair	other
C1-210026	CT1#127bis-e – Process and Scope	CT1 Chair	other
C1-210246	Usage of inclusive language	CT1 Chair	discussion
Input Liaison statements	Tdoc	Title	Source	To / CC	Result & comments
C1-210029	Reply LS on the re-keying procedure for NR SL (R2-2010963)	RAN2	To	Proposed Postponed Rel-16
C1-210030	Reply LS on NAS procedure guard timers for GEO satellite (R2-2011230)	RAN2	To	Proposed Noted Related pCRs in C1-210068 and C1-210121
C1-210031	Reply LS on Cell Configuration within TA/RA to Support Allowed NSSAI (R3-207147)	RAN3	Cc	Proposed Noted
C1-210036	LS on inconsistency in specifying handling of MCPTT SIP 183 (Session Progress) response in TS 24.379 (R5-206258)	RAN5	To	Proposed tbd (if meeting decides that this is a Rel-17 item, then it can be handled) Rel-14/Rel-15 Related CR C1-210255 and C1-210256. Related LS out in C1-210258
C1-210037	LS on failing initial registration without Retry-After header field (R5-206259)	RAN5	To	Proposed tbd Are there any contributions? We need a reply LS
C1-210038	LS on integrity and confidentiality protection of xcap-diff and pidf documents in MCPTT (TS 24.379) (R5- 206273)	RAN5	To	Proposed Postponed Rel-14, Rel-15
C1-210039	LS on SDP attribute a=key-mgmt:mikey (R5-206283)	RAN5	To	Proposed tbd Are there any contributions? We need a reply LS
C1-210040	Reply LS on high priority service exempt from release due to SOR (S1-204376)	SA1	To	Proposed Noted Related CR in C1-210114
C1-210041	LS on Satellite RATs for PLMN selection (S1-204379)	SA1	To	Proposed Noted Related pCR in C1-210032, C1-210067, C1-210092, C1-210137 Should be forwarded to CT6
C1-210042	Reply LS on MuDe functionality (S1-204380)	SA1	To	Proposed Noted Related Disc in in C1-210120
C1-210043	Reply LS on SNPN access mode when UE accesses SNPN services via a PLMN (S2-2009206)	SA2	To	Proposed Postponed Rel-16
C1-210044	Reply LS on Location Information for SMS over IMS (S2-2009332)	SA2	Cc	Proposed Postponed Rel-16
C1-210045	Reply LS on Additional Clarifications on LI requirements applicable to SNPNs (S2-2009335)	SA2	Cc	Proposed Postponed Rel-16
C1-210046	Reply LS on early UE capability retrieval for eMTC (S2-2009345)	SA2	Cc	Proposed Postponed Rel-16/Rel-17
C1-210047	LS on NR satellite access PLMN selection (S2-2009485)	SA2	To	Proposed tbd Related DISC in C1-210069, C1-210123, C1-210140 draft reply LS in C1-210070, C1-210124, C1-210141
C1-210048	Reply to LS C1-206576 on the re-keying procedure for NR SL (S3-203483)	SA3	To	Proposed Postponed Rel-16
C1-210049	Reply LS on Counter of UEs Registering Network Slice (S5-206346)	SA5	Cc	Proposed Postponed Rel-16
C1-210050	LS on APIs in EDGEAPP (S6-202009)	SA6	To	Proposed: tbd Draft reply LS in C1-210226, C1-210189
C1-210028	Reply to LS on APIs in EDGEAPP (C3-205439)	CT3	Cc	Proposed Noted CT3 answer to SA6 LS in C1-210050
C1-210051	LS on Use of Inclusive Language in 3GPP (SP-201143)	TSG SA	To	Proposed Noted See C1-210246 for info on specs that need a CR
C1-210052	LS on initiation of new work item Q.Sig_Req_ETS_IMS_roaming “Signalling requirements for emergency telecommunication service in IMS roaming environment” (SG11-LS165)	ITU-T Study group 11	To	Proposed Noted LS will be addressed by SA2, as discussed during the SA/CT/RAN coordination session, see also notes from SA plenary ftp://ftp.3gpp.org/tsg_sa/TSG_SA/TSGs_90E_Electronic/Report/SA%2390-e_Notes_of_CC%235_v1.zip.
C1-210261	LS on MINT requirements (S1-204329)	SA1	To	Proposed Noted Related discussion in C1-210126 Related pCR in C1-210220
void	Release 5 is closed
void	Release 6 is closed
void	Release 7 is closed
Release 8 work items	Tdoc	NOT IN SCOPE	Source	Tdoc info	Result & comments
Release 9 work items	Tdoc	NOT IN SCOPE	Source	Tdoc info	Result & comments
Release 10 work items	Tdoc	NOT IN SCOPE	Source	Tdoc info	Result & comments
Release 11 work items	Tdoc	NOT IN SCOPE	Source	Tdoc info	Result & comments
Release 12 work items	Tdoc	NOT IN SCOPE	Source	Tdoc info	Result & comments
Release 13 work items	Tdoc	NOT IN SCOPE	Source	Tdoc info	Result & comments
Release 14 work items	Tdoc	NOT IN SCOPE	Source	Tdoc info	Result & comments
Release 15 work items	Tdoc	NOT IN SCOPE	Source	Tdoc info	Result & comments
Release 16 work items	Tdoc	NOT IN SCOPE	Source	Tdoc info	Result & comments
Release 17 work items	Tdoc	Title	Source	Tdoc info	Result & comments
Tdocs on work items
Work Item Descriptions	Peter - Main	New and revised Work Item Descritpions
C1-210009	New WID on CT aspects of Enhanced support of Non-Public Networks	Ericsson / Ivo	WID new	CT1 lead
C1-210024	New WID on CT aspects for Support of Unmanned Aerial Systems Connectivity, Identification, and Tracking	Qualcomm Korea	WID new Rel-17	CT1 lead
C1-210027	New WID on CT aspects of Access Traffic Steering, Switch and Splitting support in the 5G system architecture; Phase 2	ZTE, China Telecom	WID new Rel-17	CT1 lead
C1-210054	New WID on CT aspects of enhanced support of industrial IoT	Nokia, Nokia Shanghai Bell	WID new Rel-17	CT1 lead
C1-210055	CT aspects of proximity based services in 5GS	CATT, OPPO	WID new Rel-17	CT1 lead
C1-210088	Enhancement of Network Slicing Phase 2	ZTE, China Telecom	WID new Rel-17	CT1 lead New revision number is C1-210269
C1-210206	New WID on CT Aspects of 5G eEDGE	Huawei, HiSlicon/Lin	WID new Rel-17	CT4 lead
C1-210273	New WID on Enabling Multi-USIM devices	Intel / Vivek	WID new Rel-17	Revision of C1-210198 _________________________________________ CT1 lead
C1-210058	Revised WID on Enhancement for the 5G Control Plane Steering of Roaming for UE in CONNECTED mode	CT1	WID revised Rel-17	Revision of CP-202186
C1-210135	Revised WID on CT aspects of 5GC architecture for satellite networks	Qualcomm Incorporated / Amer	WID revised Rel-17
C1-210219	Revised WID on CT aspects on PAP/CHAP protocols usage in 5GS	Ericsson	WID revised Rel-17	Revision of CP-202251
CRs and Discussion Documents related to new or revised Work Items	Peter - Main	CRs and Disc papers related to new Work Items
C1-210010	Discussion on CT aspects of Enhanced support of Non-Public Networks	Ericsson / Ivo	discussion Rel-17	Revision of C1-207073
C1-210056	Discussion on CT impacts of 5G_ProSe	OPPO, CATT	discussion Rel-17
C1-210087	Impacts of eNS_Ph2 to CT WGs	ZTE	discussion
C1-210199	Discussion on Enabling Multi-USIM devices	Intel / Vivek	discussion Rel-17
Status of other Work Items	Peter - Main	Status information on other relevant Rel-17 Work Items
Release 17 documents for information	Peter - Main	Miscellaneous documents provided for information
C1-210207	5G eEDGE CT work plan	Huawei, HiSlicon/Lin	discussion Rel-17
WIs for common and EPS/5GS	WIs mainly targeted for common sessions and EPS/5GS
SAES17 WIs	NOT IN SCOPE	Stage-3 SAE protocol development for Rel-17
SAES17	NOT IN SCOPE	General Stage-3 SAE protocol development
SAES17-CSFB	NOT IN SCOPE	Stage-3 SAE protocol development related to Circuit Switched Fall Back
SAES17-non3GPP	NOT IN SCOPE	Stage-3 SAE protocol development related to non-3GPP access
5GProtoc17 WIs	NOT IN SCOPE	Stage-3 5GS NAS protocol development for Rel-17
5GProtoc17	NOT IN SCOPE	General Stage-3 5GS NAS protocol development
5GProtoc17-non3GPP	NOT IN SCOPE	Stage-3 5GS NAS protocol development related to non-3GPP access
eCPSOR_CON	Peter –Main	Enhancement for the 5G Control Plane Steering of Roaming for UE in CONNECTED mode
C1-210059	Handling of multiple Tsor-cm timers and multiple PDU sessions	DOCOMO Communications Lab.	discussion Rel-17	Related CRs in C1-210060 and C1-210061
C1-210060	Handling and coordination of multiple Tsor-cm timers	DOCOMO Communications Lab.	CR 0644 23.122 Rel-17	0197 and 0060 are altenatives
C1-210061	Setting Tsor-cm timer for new or modified PDU sessions	DOCOMO Communications Lab.	CR 0645 23.122 Rel-17	0086 and 0061 are altenatives
C1-210062	Removing resolved Editor's Notes and general corrections	DOCOMO Communications Lab.	CR 0646 23.122 Rel-17	Overlaps with C1-210187
C1-210063	No de-registration when Tsor-cm stops due to going to idle mode	OPPO / Rae	CR 0647 23.122 Rel-17
C1-210085	UE behavior upon receiving higher priority PLMN ID in the SOR transparent container	SHARP	CR 0648 23.122 Rel-17	FF: not sure what’s wrong. Please revise the CR before final agreement with a fresh cover sheet.
C1-210086	UE behavior while timer Tsor-cm is running	SHARP	CR 0649 23.122 Rel-17	FF: not sure what’s wrong. Please revise the CR before final agreement with a fresh cover sheet 0086 and 0061 are altenatives
C1-210106	Preventing sending of SOR-CMCI when the UE does not support SOR-CMCI	Ericsson / Ivo	CR 0650 23.122 Rel-17
C1-210107	Configuring UE with SOR-CMCI	Ericsson / Ivo	CR 0651 23.122 Rel-17
C1-210114	Configuration of services exempted from release due to SOR at the UE	Qualcomm Incorporated / Lena	CR 0652 23.122 Rel-17
C1-210164	Analysis on the storage of SOR-CMCI in the UE	NTT DOCOMO INC.	discussion Rel-17	Related with Cr C1-210165
C1-210165	Storage of SOR-CMCI in the UE	NTT DOCOMO INC.	CR 0653 23.122 Rel-17
C1-210186	Definition of CP-SOR	vivo	CR 0654 23.122 Rel-17
C1-210187	UDM obtaining SOR-CMCI from the SOR-AF	vivo	CR 0655 23.122 Rel-17	Overlaps with C1-210062
C1-210188	UDM obtaining SOR-CMCI using the Nsoraf_SoR_Get service operation	vivo	CR 0656 23.122 Rel-17
C1-210195	UE behavior upon receiving new timer valuer for Tsor-cm timer	SHARP	CR 0657 23.122 Rel-17
C1-210196	Handling of timer Tsor-cm when changing the network selection mode to manual mode	SHARP	CR 0658 23.122 Rel-17
C1-210197	Handling of timer Tsor-cm when SOR-CMCI has more than one criterion applicable for multiple PDU sessions and services	SHARP	CR 0659 23.122 Rel-17	0197 and 0060 are altenatives
C1-210217	PLMN selection when the emergency PDU session is released	vivo	CR 0660 23.122 Rel-17
C1-210242	eCPSOR_CON work plan	DOCOMO Communications Lab.	other Rel-17
5GSAT_ARCH-CT	Peter –Main	CT aspects of 5GC architecture for satellite networks New TR 24.821 Is TR 24.821 ready to be sent for information?
C1-210032	Solution to KI#5-access technology	China Mobile	pCR 24.821 Rel-17	x032, x067, x137, x139 are related to KI#5
C1-210033	Solution to KI#6-About MCC limitation	China Mobile	pCR 24.821 Rel-17	x033, x034, x121 are related to KI#6
C1-210034	Solution to KI#6-About priority of PLMNs in satellite access	China Mobile	pCR 24.821 Rel-17	x033, x034, x121 are related to KI#6
C1-210035	Solution to KI#7-Emergency calls	China Mobile	pCR 24.821 Rel-17	x035, x134, x173 are related to KI#7
C1-210064	Clarifying between the definition of "same country" and "same MCC"	OPPO / Chen	pCR 24.821 Rel-17
C1-210065	PLMN's broadcast of countries it can be selected and LI requirements	OPPO / Chen	discussion Rel-17
C1-210066	KI#2, Update: Regulatory, security and LI requirements and PLMN selection	OPPO / Chen	pCR 24.821 Rel-17	x066, x089, x090, x091, x111, x136, x203, x205, x231 are related to KI#2
C1-210067	KI#5 Update: Removal of unnecessary RAT types for satellite access	OPPO / Chen	pCR 24.821 Rel-17	x032, x067, x137, x139 are related to KI#5
C1-210068	KI#6, Update to Solution8 to remove Editor's notes	OPPO / Chen	pCR 24.821 Rel-17
C1-210069	Discussion on SA2's questions on NR satellite access PLMN selection	OPPO / Chen	discussion Rel-17
C1-210089	Solution to Key Issue 2, 3 and 4: Determination of accessible PLMN/satellite NG-RAN combination	MediaTek Inc. / Carlson	pCR 24.821 Rel-17	x066, x089, x090, x091, x111, x136, x203, x205, x231 are related to KI#2 x089, x090, x091, x122 are related to KI#3 x089, x111, x204, x243 are related to KI#4
C1-210090	Solution to Key Issue 2 and 3: Detecting change of country and in/out of international areas Alternative 1	MediaTek Inc. / Carlson	pCR 24.821 Rel-17	x066, x089, x090, x091, x111, x136, x203, x205, x231 are related to KI#2 x089, x090, x091, x122 are related to KI#3
C1-210091	Solution to Key Issue 2 and 3: Detecting change of country and in/out of international areas Alternative 2	MediaTek Inc. / Carlson	pCR 24.821 Rel-17	x066, x089, x090, x091, x111, x136, x203, x205, x231 are related to KI#2 x089, x090, x091, x122 are related to KI#3
C1-210092	Solution to Key Issue 5: Handling of new satellite NG-RAN Access Technology Identifier	MediaTek Inc. / Carlson	pCR 24.821 Rel-17
C1-210093	Solution to Key Issue 1: UE is assumed with GNSS capabilities	MediaTek Inc. / Carlson	pCR 24.821 Rel-17	x093, x113, x138, x202 are related to KI#1
C1-210111	Correction for SOL#2 and SOL#4: document impact on SoR	BlackBerry UK Ltd.	pCR 24.821 Rel-17	x066, x089, x090, x091, x111, x136, x203, x205, x231 are related to KI#2 x089, x111, x204, x243 are related to KI#4
C1-210112	Optimization for SOL#4: deprioritize TN accesses	BlackBerry UK Ltd.	pCR 24.821 Rel-17
C1-210113	Correction for KI#1 and SOL#1: applicability of legacy procedures to determine the country serving the area	BlackBerry UK Ltd.	pCR 24.821 Rel-17	x093, x113, x138, x202 are related to KI#1
C1-210121	Solution to Key Issue #6	Apple	pCR 24.821 Rel-17	x033, x034, x121 are related to KI#6
C1-210122	Solution to Key Issue #3	Apple	pCR 24.821 Rel-17	x089, x090, x091, x122 are related to KI#3
C1-210123	Discussion on C1-210047 (NR satellite access PLMN selection)	Apple	discussion Rel-17
C1-210134	Correction in KI #7	Nokia, Nokia Shanghai Bell	pCR 24.821 Rel-17	x035, x134, x173 are related to KI#7
C1-210136	Updates to KI2	Qualcomm Incorporated / Amer	pCR 24.821 Rel-17	x066, x089, x090, x091, x111, x136, x203, x205, x231 are related to KI#2
C1-210137	Updates to KI5	Qualcomm Incorporated / Amer	pCR 24.821 Rel-17	x032, x067, x137, x139 are related to KI#5
C1-210138	Solution to KI1	Qualcomm Incorporated / Amer	pCR 24.821 Rel-17	x093, x113, x138, x202 are related to KI#1
C1-210139	Solution to KI5	Qualcomm Incorporated / Amer	pCR 24.821 Rel-17	x032, x067, x137, x139 are related to KI#5
C1-210140	Discussion on the reply LS to SA2 on NR satelltie access PLMN selection	Qualcomm Incorporated / Amer	discussion 24.821 Rel-17
C1-210170	Editor’s notes on selection of a PLMN not allowed from a UE’s location	Nokia, Nokia Shanghai Bell	pCR 24.821 Rel-17
C1-210171	LI requirement applicable to all UEs compliant to Rel-17 and beyond	Nokia, Nokia Shanghai Bell	pCR 24.821 Rel-17
C1-210172	Conclusions to KI #1	Nokia, Nokia Shanghai Bell	pCR 24.821 Rel-17
C1-210173	New solution to KI #7	Nokia, Nokia Shanghai Bell	pCR 24.821 Rel-17	x035, x134, x173 are related to KI#7
C1-210202	Clarification of Solution 1 for key issue 1	Ericsson, Nokia, Nokia Shanghai Bell, Oppo / Mikael	pCR 24.821 Rel-17	x093, x113, x138, x202 are related to KI#1
C1-210203	Clarification of Solution 2 for key issue 2	Ericsson, Oppo / Mikael	pCR 24.821 Rel-17	x066, x089, x090, x091, x111, x136, x203, x205, x231 are related to KI#2
C1-210204	Clarification of Solution 7 for key issue 4	Ericsson, Oppo / Mikael	pCR 24.821 Rel-17	x089, x111, x204, x243 are related to KI#4
C1-210205	New solution for key issue 2	Ericsson, Oppo / Mikael	pCR 24.821 Rel-17	x066, x089, x090, x091, x111, x136, x203, x205, x231 are related to KI#2
C1-210229	Discussion paper on country mapping limitations impacts on PLMN selection	THALES	discussion 24.821
C1-210231	Solution 2 description enhancement	THALES	pCR 24.821 Rel-17	x066, x089, x090, x091, x111, x136, x203, x205, x231 are related to KI#2
C1-210241	Discussion paper on PLMN selection on shared/global PLMN	LG Electronics Inc.	discussion
C1-210243	Solution to KI#2 on PLMN selection on shared/global PLMN	LG Electronics Inc.	pCR 24.821 Rel-17	x089, x111, x204, x243 are related to KI#4
C1-210244	Handling of emergency calls	Samsung / Kyungjoo Grace Suh	pCR 24.821 Rel-17
SMS_SBI (CT4 lead)	Peter –Main	Service-based support for SMS in 5GC
AKMA-CT (CT3 lead)	Peter –Main	Authentication and key management for applications based on 3GPP credential in 5G
C1-210022	Kausf change	Ericsson / Ivo	CR 2948 24.501 Rel-17
C1-210057	Clarification on AKMA	ZTE / Joy	CR 2949 24.501 Rel-17
C1-210200	Refreshing KAF after lifetime expiry	Samsung R&D Institute India	discussion 24.501 Rel-17
C1-210201	Refreshing KAF after lifetime expiry	Samsung R&D Institute India	CR 2951 24.501 Rel-17	FF: What is the current version? It reads 17.0.0 on the cover page but the Tdoc is reserved for version 17.1.0. What is the CR category? It reads F on the cover page but the Tdoc is reserved for category B. Tick any of the boxes as impacted.
C1-210213	Discussion on KAF desynchronization for AKMA	Huawei, HiSlicon/Lin	discussion Rel-17
C1-210214	Resolving KAF desynchronization for AKMA	Huawei, HiSlicon/Lin	CR 2952 24.501 Rel-17
C1-210215	Collision of AKMA and NAS AKA procedure handling	Huawei, HiSlicon/Lin	CR 2953 24.501 Rel-17
C1-210216	UE handling in case of no valid KAUSF for AKMA	Huawei, HiSlicon/Lin	CR 2954 24.501 Rel-17
PAP_CHAP (CT3 lead)	Peter –Main	CT aspects on PAP/CHAP protocols usage in 5GS
C1-210218	Adding the RFC reference of PAP/CHAP protocol identifier contents and related abbreviations	China Telecommunications,Huawei, HiSilicon	CR 3252 24.008 Rel-17	FF: Expected 3 work item code(s) but found 1. CR number missing on cover page
RDSSI	Peter –Main	Reliable Data Service Serialization Indication
FS_MINT-CT	Peter –Main	Study on the CT aspects of Support for Minimization of service Interruption
C1-210221	Work Plan for FS_MINT-CT	LG Electronics / SangMin	discussion Rel-17
C1-210126	Discussion on whether the main node in the Core Network should be considered in the Study on MINT	InterDigital	discussion 24.811 Rel-17	Related to incoming LS in C1-210261
C1-210220	Architectural Assumption on the CN failure scenario	LG Electronics / SangMin	pCR 24.811 Rel-17	Related to incoming LS in C1-210261 Architectural Assumptions
C1-210168	Updates to Architectural Assumptions	Samsung Guangzhou Mobile R&D	pCR 24.811 Rel-17	Architectural Assumptions
C1-210178	Architectural Assumptions	vivo	pCR 24.811 Rel-17	Architectural Assumptions
C1-210108	Resilience against fake broadcast	Ericsson / Ivo	pCR 24.811 Rel-17	Architectural Requirement
C1-210109	Applicability of MINT to roamers	Ericsson / Ivo	pCR 24.811 Rel-17	Architectural Requirement
C1-210179	Architectural Requirements	vivo	pCR 24.811 Rel-17	Architectural Requirement
C1-210240	MINT: Discussion on New Key Issue for Manual PLMN Selection	Huawei, HiSilicon / Vishnu	discussion 24.811 Rel-17	New Key Issue and its solution
C1-210156	FS_MINT: New Key Issue #Y: Manual PLMN Selection	Huawei, HiSilicon / Vishnu	pCR 24.811 Rel-17	New Key Issue and its solution
C1-210157	FS_MINT: Solution for New Key issue #Y: Manual PLMN Selection	Huawei, HiSilicon / Vishnu	pCR 24.811 Rel-17	New Key Issue and its solution
C1-210230	Updates to KI#1	LG Electronics / SangMin	pCR 24.811 Rel-17	KI update
C1-210180	Updates to KI#2	vivo	pCR 24.811 Rel-17	KI update
C1-210181	Updates to KI#4	vivo	pCR 24.811 Rel-17	KI update
C1-210174	Correction in Key Issue #5	Nokia, Nokia Shanghai Bell	pCR 24.811 Rel-17	Moved from AI 17.2.4 KI update
C1-210212	Correction on KI#6	Huawei, HiSlicon/Lin	pCR 24.811 Rel-17	KI update
C1-210167	Update to KI#7 – Prevention of congestion 5GSM level congestion	Samsung Guangzhou Mobile R&D	pCR 24.811 Rel-17	KI update
C1-210071	Outline of solutions in C1-210072 - C1-210079	Nokia, Nokia Shanghai Bell	discussion Rel-17	DP regarding solutions
C1-210208	Discussion on solutions for KI#2 and KI#6 for MINT	Huawei, HiSlicon/Lin	discussion Rel-17	DP regarding solutions
C1-210259	FS_MINT: Discussion on Solution for Key Issues #3,#4,#5,#7,#8	Huawei, HiSilicon / Vishnu	discussion 24.811 Rel-17	Revision of C1-210148 DP regarding solutions
C1-210011	MINT: solution for key issue #1	Ericsson / Ivo	pCR 24.811 Rel-17	Revision of C1-207323 New solution / KI#1
C1-210072	New solution on Key Issue #1	Nokia, Nokia Shanghai Bell	pCR 24.811 Rel-17	New solution / KI#1
C1-210084	MINT Solution for KI#1: Notification of Disaster Condition to the UE via Non-3GPP Acess	ZTE Corporation	pCR 24.811 Rel-17	New solution / KI#1
C1-210143	KI#1: Indication of CN Failure	Apple AB	pCR 24.811 Rel-17	New solution / KI#1
C1-210184	Disaster condition information delivered to UE via broadcast	vivo	pCR 24.811 Rel-17	New solution / KI#1
C1-210154	Solution to KI#1 & part of KI#7: Indicating, via non-3GPP access, the applicability of a disaster condition to the 3GPP access of the same PLMN	Samsung Guangzhou Mobile R&D	pCR 24.811 Rel-17	New solution / KI#1 and KI#7
C1-210012	MINT: alternative 1 for key issue #2	Ericsson / Ivo	pCR 24.811 Rel-17	Revision of C1-207324 New solution / KI#2
C1-210013	MINT: alternative 2 for key issue #2	Ericsson / Ivo	pCR 24.811 Rel-17	Revision of C1-207325 New solution / KI#2
C1-210073	New solution on Key Issue #2	Nokia, Nokia Shanghai Bell	pCR 24.811 Rel-17	New solution / KI#2
C1-210209	Solution for KI#2: O&M-based solution	Huawei, HiSlicon/Lin	pCR 24.811 Rel-17	New solution / KI#2
C1-210014	MINT: alternative 1 for key issue #3	Ericsson / Ivo	pCR 24.811 Rel-17	Revision of C1-207326 New solution / KI#3
C1-210015	MINT: alternative 2 for key issue #3	Ericsson / Ivo	pCR 24.811 Rel-17	Revision of C1-207327 New solution / KI#3
C1-210074	New solution on Key Issue #3	Nokia, Nokia Shanghai Bell	pCR 24.811 Rel-17	New solution / KI#3
C1-210144	KI#3: Broadcast of disaster roaming indication	Apple AB	pCR 24.811 Rel-17	New solution / KI#3
C1-210150	FS_MINT: Solution for Key issue #3	Huawei, HiSilicon / Vishnu	pCR 24.811 Rel-17	New solution / KI#3
C1-210182	DRS-supported PLMN list	vivo	pCR 24.811 Rel-17	New solution / KI#3
C1-210117	Solution to MINT Key Issue #3 (Indication of accessibility from other PLMNs without Disaster Condition to the UE), and Key Issue #7 (Prevention of signalling overload in PLMNs without Disaster Condition) - alternative 2, using Access Identities	Qualcomm Incorporated / Lena	pCR 24.811 Rel-17	New solution / KI#3 and KI#7
C1-210020	MINT: alternative 2 for key issue #4	Ericsson / Ivo	pCR 24.811 Rel-17	Revision of C1-207333 New solution / KI#4
C1-210075	New solution on Key Issue #4	Nokia, Nokia Shanghai Bell	pCR 24.811 Rel-17	New solution / KI#4
C1-210151	FS_MINT: Solution for Key issue #4	Huawei, HiSilicon / Vishnu	pCR 24.811 Rel-17	New solution / KI#4
C1-210163	Solution to KI#4: Confining a Disaster Inbound Roamer UE’s area of service to the area of the disaster condition	Samsung Guangzhou Mobile R&D	pCR 24.811 Rel-17	New solution / KI#4
C1-210016	MINT: solution for key issue #5	Ericsson / Ivo	pCR 24.811 Rel-17	Revision of C1-207328 New solution / KI#5
C1-210076	New solution on Key Issue #5	Nokia, Nokia Shanghai Bell	pCR 24.811 Rel-17	New solution / KI#5
C1-210115	Solution to MINT Key Issue #5 (PLMN selection when a "Disaster Condition" applies)	Qualcomm Incorporated / Lena	pCR 24.811 Rel-17	New solution / KI#5
C1-210145	KI#5: Considerations for PLMN selection in a "Disaster Condition"	Apple AB	pCR 24.811 Rel-17	New solution / KI#5
C1-210152	FS_MINT: Solution for Key issue #5	Huawei, HiSilicon / Vishnu	pCR 24.811 Rel-17	New solution / KI#5
C1-210185	PLMN selection base on DRS-Supported PLMN list	vivo	pCR 24.811 Rel-17	New solution / KI#5
C1-210222	New solution to KI#5: Handling of forbidden PLMN list	LG Electronics / SangMin	pCR 24.811 Rel-17	New solution / KI#5
C1-210017	MINT: solution for key issue #6	Ericsson / Ivo	pCR 24.811 Rel-17	Revision of C1-207329 New solution / KI#6
C1-210077	New solution on Key Issue #6	Nokia, Nokia Shanghai Bell	pCR 24.811 Rel-17	New solution / KI#6
C1-210119	Solution to MINT Key Issue #6 (Notification that Disaster Condition is no longer applicable to the UEs)	Qualcomm Incorporated / Lena	pCR 24.811 Rel-17	New solution / KI#6
C1-210177	The quick return to PLMN with Disaster Condition	vivo	pCR 24.811 Rel-17	New solution / KI#6
C1-210158	Solution to KI#6 and KI#8: Indicating, via non-3GPP access, the end of a disaster condition that was applicable to the 3GPP access of the same PLMN	Samsung Guangzhou Mobile R&D	pCR 24.811 Rel-17	New solution / KI#6 and KI#8
C1-210224	New solution to KI#6: NAS based notification	LG Electronics / SangMin	pCR 24.811 Rel-17	New solution / KI#6 and KI#8
C1-210270	Solution for KI#6: O&M-based solution	Huawei, HiSlicon/Lin	pCR 24.811 Rel-17	Revision of C1-210210 _________________________________________ New solution / KI#6 Corrupted styles
C1-210271	Solution for KI#6: UE-based solution	Huawei, HiSlicon/Lin	pCR 24.811 Rel-17	Revision of C1-210211 _________________________________________ New solution / KI#6 Corrupted styles
C1-210021	MINT: solution for key issue #7	Ericsson / Ivo	pCR 24.811 Rel-17	New solution / KI#7
C1-210078	New solution on Key Issue #7	Nokia, Nokia Shanghai Bell	pCR 24.811 Rel-17	New solution / KI#7
C1-210116	Solution to MINT Key Issue #7 (Prevention of signalling overload in PLMNs without Disaster Condition) – Alternative 1: providing disaster roaming assistance information to distribute roamers, and congestion mitigation	Qualcomm Incorporated / Lena	pCR 24.811 Rel-17	New solution / KI#7
C1-210127	Staggering the arrivals of UEs in the PLMN without Disaster Condition	InterDigital	pCR 24.811 Rel-17	New solution / KI#7
C1-210129	Enabling the PLMN without Disaster Condition to efficiently prevent Disaster Inbound Roamers from attempting registration	InterDigital	pCR 24.811 Rel-17	New solution / KI#7
C1-210146	KI#7: Introduction of a new access category	Apple AB	pCR 24.811 Rel-17	New solution / KI#7
C1-210147	KI#7: Enhancements to UAC barring information	Apple AB	pCR 24.811 Rel-17	New solution / KI#7
C1-210153	FS_MINT: Solution for Key issue #7	Huawei, HiSilicon / Vishnu	pCR 24.811 Rel-17	New solution / KI#7
C1-210166	Solution to KI#7: Preventing 5GSM-level congestion on a PLMN without a disaster condition	Samsung Guangzhou Mobile R&D	pCR 24.811 Rel-17	New solution / KI#7
C1-210183	Recommended PLMN without Disaster Condition	vivo	pCR 24.811 Rel-17	New solution / KI#7
C1-210225	New solution to KI#7: Congestion control for inbound disaster roamers	LG Electronics / SangMin	pCR 24.811 Rel-17	New solution / KI#7
C1-210018	MINT: solution for key issue #8	Ericsson / Ivo	pCR 24.811 Rel-17	Revision of C1-207331 New solution / KI#8
C1-210079	New solution on Key Issue #8	Nokia, Nokia Shanghai Bell	pCR 24.811 Rel-17	New solution / KI#8
C1-210118	Solution to MINT Key Issue #8 (Prevention of signalling overload by returning UEs in PLMN previously with Disaster Condition)	Qualcomm Incorporated / Lena	pCR 24.811 Rel-17	New solution / KI#8
C1-210128	Prevention of signaling overload by returning UEs in the PLMN previously with Disaster Condition	InterDigital	pCR 24.811 Rel-17	New solution / KI#8
C1-210149	KI#8: Network controlled return of UEs at the end of disaster condition	Apple AB	pCR 24.811 Rel-17	New solution / KI#8
C1-210155	FS_MINT: Solution for Key issue #8	Huawei, HiSilicon / Vishnu	pCR 24.811 Rel-17	New solution / KI#8
6
C1-210019	MINT: alternative 1 for key issue #4	Ericsson / Ivo	pCR 24.811 Rel-17	Withdrawn Revision of C1-207332
C1-210110	Significance of an available cell	Ericsson / Ivo	pCR 24.811 Rel-17	Withdrawn
2
EDGEAPP (CT3 lead)	Lena - Breakout	CT aspects for Enabling Edge Applications
C1-210023	Way forward for protocol selection on EDGE-1 and EDGE-4	Qualcomm Korea	discussion Rel-17
C1-210190	EDGEAPP Workplan	Samsung / Sapan	discussion
C1-210191	Selection Of API Wayforward	Samsung, AT&T, Convida Wireless, Deutsche Telekom, KDDI, Korea Telecom, SK Telecom, Softil, Ericsson, Intel, Qualcomm Incorporated	discussion Rel-17
C1-210192	Draft skeleton for ts 24.558	Samsung / Sapan	pCR 24.558 Rel-17
C1-210193	clause 1 Scope	Samsung / Sapan	pCR 24.558 Rel-17
C1-210194	clause 3.3 Abbreviations	Samsung / Sapan	pCR 24.558 Rel-17
C1-210223	Discussion on the EDGE-4 reference point using the NAS	Huawei, China Telecom, China Unicom, HiSilicon /Christian	discussion Rel-17
C1-210239	EDGEAPP protocol analysis	Nokia, Nokia Shanghai Bell	discussion Rel-17	Withdrawn
Other Rel-17 issues (TEI17)	NOT IN SCOPE	Other Rel-17 topics
WIs for IMS and MC	Jörgen – Breakout	Work items on IMS and Mission Critical
IMSProtoc17	NOT IN SCOPE	IMS Stage-3 IETF Protocol Alignment for Rel-17
MCProtoc17	NOT IN SCOPE	Protocol enhancements for Mission Critical Services for Rel-17
FS_eIMS5G2	Jörgen – Breakout	Study on enhanced IMS to 5GC Integration Phase 2
C1-210131	IMS retrieves session binding information by utilizing service provided by BSF	China Mobile	pCR 23.700-10 Rel-17	Postponed Jörgen Mon 1355: Shouldn't these be discussed in CT3? Xu Mon 1625: KI#4 is more for IMS. Sung Mon 1849: Objection. Agree with Jörgen, and functionality is specified in 23.502 5.2.13.1 and 23.503 6.1.1.2.2. Xu Tue 0329: Some comments to Sung and this pCR addresses questions ia)b) in KI#4. Jörgen Tue 1500: Maintains it seems to be CT3 procedures Xu Wed 1438: Will discuss with CT3 colleague.
C1-210175	IMS retrieve Location Information by utilizing service provided by AMF	China Mobile Com. Corporation	pCR 23.700-10 Rel-17	Postponed Sung Mon 1918: Objection. Location retrieval already supported, this is CT4 functionality. 3 technical questions. Jörgen Tue 1748: Agree this is not CT1. Xu Wed 1441: Will discuss with CT4 colleague.
C1-210176	P-CSCF retrieve PLMN ID by utilizing service provided by 5GC	China Mobile Com. Corporation	pCR 23.700-10 Rel-17	Postponed Sung Mon 1925: Objection. This is for CT4. No advantige with the proposal. Jörgen Tue 1748: Agree not CT1. Xu Wed 1444: Will discuss with CT4 colleague.
C1-210227	IMS traffic local routing by applying AF influence mechanism	Huawei, HiSilicon / Bill	pCR 23.700-10 Rel-17	Withdrawn
C1-210228	IMS signalling and media of an application through one 5GC slice	Huawei, HiSilicon / Bill	pCR 23.700-10 Rel-17	Withdrawn
C1-210280	Add one possibly scenario for Key issue 1	China Mobile Com. Corporation	pCR 23.700-10 Rel-17	Current status: Agreed Revision of C1-210169 _________________________________________ Jörgen Mon 1349: Asks for more description. Some text not updated to refer to three scenarios. Sung Mon 1844: Objection, proposal rejected in SA1 and SA2 in 2018, not slicing as only one slice is used. Jiang Yi: Needed for deployment. Already in the TR, fig 5.1.2. Xu: Draft revision in draftRev1. Jörgen Tue 1748: OK with draft as such. Some further questions. Xu Wed 0229: Responds to Jörgen. Sung Wed 0437: Requests change of figure. Xu Wed 1423: Modified figure according to Sung's comment. See draftRev1
C1-210400	Support of one slice connecting to multiple IMS network	China Mobile	pCR 23.700-10 Rel-17	Current status: Agreed Note that 0130 has been revised twice. C1-210358 has been withdrawn. Revision of C1-210130 _________________________________________ Jörgen Mon 1352: Are the SMF procedures for CT4? Sung Mon 1845: Objection, use case in 0169 is also objected. Xu Wed 1359: Revised, think CT1 is appropriate. Changed figure in 0169 as result of Sung's comment. See draftRev1 Sung Wed 2039: Objection, there should be no confustion® Xu Thu 0453: SMF needs info from UE to select correct network Sung Thu 0854: Isn't UE ID known by SMF? Xu Thu 0941: UE ID means SUPI? Does not believe SMF has UE IMS identities. Jörgen Thu 1012: Problem description could be better. Xu Thu 1108: Revision in draftRev2 Jörgen Thu 1126: Some editorial, and a question.
C1-210401	Solution to KI#1-Slice selection by IMS subscription	China Mobile	pCR 23.700-10 Rel-17	Current status: Agreed Revision of C1-210132 _________________________________________ Sung Mon 1855: Revision required, Alt #2 does not work, should be removed. Jörgen Tjue 17.44: Comment on URSP. Can't DNN be used? Xu Wed 1540: Responds to Sung. Proposes to add a NOTE. Sung Wed 2104: Clarify how IMPI is used in RSD. Xu Thu 0211: DNN included as possibility. Alt 2 removed, see draft in draftRev1 Sung Thu 0259: OK Jörgen Thu 1151: PCF is for CT3, not convinced about IMPI, may be for evaluation.
C1-210402	Suggestion to KI#1-About unappropriate slice	China Mobile	pCR 23.700-10 Rel-17	Current status: Agreed Revision of C1-210133 _________________________________________ Sung Mon 1909: Revision required: Remove two bullets instead of adding the new. Jörgen Tue 1745: What does indicate inappropriate mean? Xu: Thu 0929: Responds to Sung Xu Thu 1012: Responds to Jörgen Xu Thu 1131: See draftRev Jörgen Thu 1156: Minor comments.
MuDe	Jörgen – Breakout	Multi-device and multi-identity enhancements
C1-210053	Updating ability to activate and deactivate an identity	vivo Mobile Communication Co. LTD	CR 0016 24.174 Rel-17	Current status: Postponed Mariusz Mon 0956: Revision required. Some editorials. Jörgen Mon 1046: Premature, decide on function first. Some editorials. Upendra Mon 1203: activation is also needed in the CR text. Adrian Mon 1930: Taken Jörgen's and Upendra's comments into account in draftRev1. Question on which terms are best Roozbeh Mon 2026: Objection. b) not justified by the LS. WID is only how to allow/disallow routing of call. Bill Tue 0921: Have we decided? Jörgen Tue 1703: Answers Bill. Requests to postpone until we have a procedure. Adrian Tue 2014: responds to Roozbeh Roozbeh Wed 0618: Responds to Adrian Jörgen Wed 1038: Don't discuss GSMA here. External additional identities not in reg event. Roozbeh Wed 1558: Objection with long discussion. Mariusz Wed 2316: Asks if subscription is reg event package or something else?
C1-210120	Analysis of MuDe LS from SA1 in C1-210042	vivo Mobile Com. (Chongqing)	discussion Rel-17	Noted Mariusz Mon 0952: 3) is unclear. Should the call be terminated as in RfC in SA1. Jörgen Mon 1049: Comments on the questions. Assumes 3) means do nothing, not happy with response on question 4). Upendra Mon 1233: Do we need clarification for 3)? Authorized user needs to be defined in 24.174. Roozbeh (RA)and Adrian (AB) having a long discussion on terms and related things: AB: Mon 1826, 2114, 2122, Tue 0018, 0102. RA: Mon 2017, 2047, 2148, 2158, Tue 0650 0712. Jörgen Tue 1006: Comment related to activated in 24.623. Adrian Tue 1734: Agrees with Jörgen's summary of the thread. Mariusz Wed 2352: View on deactivation Roozbeh Thu 0055: SA1 and CT1 discrepancy on terms Mariusz: Responds on emergency use case. Adrian Thu 0216 comment on terms and use case Roozbeh Thu 0231, 0243: Responds on terms and use case.
C1-210159	Discussion on how to route an incoming call or message	Lenovo, Motorola Mobility	discussion	Noted Mariusz Mon 0958: Maybe reintroduce data modeling from early versions of 24.174. Disagree with observation 1. Several other comments. Jörgen Mon 1051: Disagree with observation 1. Some comments, and does not understand conclusion 4. Upendra Mon 1348: Virtual identities can be registerd. PAU not allwoed in REGUSTER. Two further comments on identity sharing and reg-event. Roozbeh Mon 1926: Responds to Mariusz. Some agreement. Roozbeh Mon 1936: Responds to Jörgen. Roozbeh Mon 1954: Responds to Upendra Jörgen Tue 1708: Reg event only within subscription. Not willing to change that. Roozbeh Tue 2333: Responds to Jörgen. Jörgen Wed 1048: Responds to Roozbeh. Mariusz Thu 0025: Responds to Roozbeh Roozbeh Thu 0304: Not convinced
C1-210160	Temporary activation and deactivation of identities	Lenovo, Motorola Mobility	CR 0017 24.174 Rel-17	Current status: Postponed Frederic, before meeting: Tdoc number on cover page incorrect (“0” is missing), work item incorrect on cover page wrong, needs to be MuDe Mariusz Mon 0957: Unclear if the ICSI refers to a particular identity and which one. Jörgen Mon 1103: Objection. PAU cannot be used in REGISTER. ICSI is conceptually wrong. Upendra Mon 1358: Not recommended to use registration for activation/deactivation. PAU only allowed in 2xx response to REGISTER. Roozbeh Mon 1813: Responds to Mariusz Roozbeh Mon 1826: Responds to Jörgen. PAU possible in REGISTER. Roozbeh Mon 1838: Responds to Upendra and asks question. Jörgen Tue 1035: Ack on PAU in REGISTER in RFC, not in 24.229. Asks a question, but still sceptical. Roozbeh Wed 0309: Register is better than Ut. Requirement to (de)activate any identity on any UE is very ambitious. Bill Wed 0812: Support Upendra, in particular for not using registration. Jörgen Wed 1109: Responding to Roozbeh.
C1-210161	Subscriptions to identities	Lenovo, Motorola Mobility	CR 0018 24.174 Rel-17	Current status: Postponed Frederic, before meeting: work item incorrect on cover page wrong, needs to be MuDe Mariusz Mon 0957: No conclusion to use registration for activating/deactivating identities. Some more comments on feasibility. Jörgen Mon 1106: Stage 1 text. More needed. Reg event not possible outside subscription. Upendra Mon 1400: Reg event not possible outside subscription. Roozbeh Mon 1754: Responds to Mariusz. Roozbeh Mon 1802: Responds to Jörgen. Thinks reg event can be made to work. Roozbeh Mon 1804: Why is reg event not possible. Jörgen Tue 1942: Different IMS registrations. Roozbeh Tue 2259: Let's use reg event when we can.
C1-210162	Corrected text for identities	Lenovo, Motorola Mobility	CR 0019 24.174 Rel-17	Postponed, out of scope for the meeting Frederic, before meeting: work item incorrect on cover page wrong, needs to MuDe Mariusz Mon 0958: Objection, existing text is correct. Explains why. Jörgen Mon 1109: Request to postpone, this is either IMSProtoc17 or MuD, not MuDe, so out of scope of the meeting. OK to postpone
C1-210245	Discussion activation identities	Ericsson /Jörgen	discussion	Noted Mariusz Mon0956: Support network based solution. Don't see need to specify user friendly name in 3GPP. Jörgen Tue 2207: Not only the user needs to identify the UEs, but also the UE itself. Bill Wed 0852: User friendly name is encouraged, list of IRS identities can be used, for change of UE correlation with IMSI is the choice.
C1-210260	MuDe Identity activation status indication	Orange / Mariusz	CR 0015 24.174 Rel-17	Current status: Postponed Revision of C1-206742 FF: Tdoc number on cover page incorrect, work item code on cover page incorrect, it needs to be MuDe Jörgen Mon 1115: Several comments on the schema. CR needs more description of new elements. Upendra Mon 1435: Questions, some seems related to existing text. Roozbeh Mon 1729: Ut not right for external alternative identity. Activation/deactivation should be temporary feature without requiren owner or operator authorization Jörgen Tue 1449: Describes current Ut handling of external alternative identities. Takayuki Wed 0713: How is a UE informed about change of status. Mariusz Wed 1456: Draft revision in draftRev1 Jörgen Wed 17.36: furthter comments. Roozbeh Wed 2023: Some questions. Jörgen Thu 1035: Response to Roozbeh.
MPS2 (CT3 lead)	Jörgen – Breakout	Stage 3 of Multimedia Priority Service (MPS) Phase 2
C1-210094	24.501 Redirection with MPS	Perspecta Labs, CISA ECD, Ericsson	CR 2950 24.501 Rel-17	Due to nature of the CR, TO BE DISCUSSED on the main email list
eMCData3	Jörgen – Breakout	CT aspects of Enhancements to Mission Critical Data
C1-210252	Incorrect subclause reference correction in subclause 10.2.5.2.3 and 10.2.5.2.4	Samsung	CR 0204 24.282 Rel-17	Postponed Jörgen Mon 1126: Seems an MCProtoc CR, and hence out of scope.
C1-210262	Emergency alert area notification functionalities handling for MCData	Samsung	CR 0202 24.282 Rel-17	Current status: Agreed Revision of C1-210247
C1-210321	Entry into or exit from a group geographic area functionality handling for MCData	Samsung	CR 0203 24.282 Rel-17	Current status: Agreed Revision of C1-210296 _________________________________________ Revision of C1-210288 _________________________________________ Mike OK Revision of C1-210264 _________________________________________ Revision of C1-210249 _________________________________________ FF: not sure what’s wrong. Please revise the CR before final agreement with a fresh cover sheet. Jörgen Mon 1126: xs:boolean need to be lower case. an <group a <group. Mike Mon1437: 2) a) also needs to reference 8.2.2 for affilitation. Wants to cosign. Will fix 24.379 next meeting.
MCSMI_CT	Jörgen – Breakout	Mission Critical system migration and interconnection Shifted from Rel-16
eMCCI_CT	Jörgen – Breakout	CT aspects of Enhanced Mission Critical Communication Interworking with Land Mobile Radio Systems
enh3MCPTT-CT	Jörgen – Breakout	CT aspects of Enhanced Mission Critical Push-to-talk architecture phase 3
C1-210083	enh3MCPTT Plan After CT1_127e	FirstNet / Mike	discussion Rel-17	Noted
C1-210251	Spelling correction of altitude element of the location	Samsung	CR 0108 24.281 Rel-17	Current status: Agreed
C1-210256	Appropriate handling of P-Answer-State in group call procedure	Samsung	CR 0672 24.379 Rel-17	Current status: Postponed Jörgen Mon 1209: Discussion on work item and some minor comments. Lazaros Mon 2323: Seems to imply non-essential CR. Jörgen Tue 1340: Questions to Lazaros. Lazaros Tue 1711: Private calls need some specification. Group calls can be clarified. Not FASMO. Kiran Tue 1915, Tue 1936, Wed 0719, Wed 1519, Mike Tue 2005 Lazaros Tue 2233, Wed 1024 Jörgen Wed 1624: Discussion on WI, essentiality and way forward.
C1-210263	Emergency alert area notification functionalities handling for MCVideo	Samsung	CR 0106 24.281 Rel-17	Current status: Agreed Revision of C1-210248
C1-210267	Appropriate handling of P-Answer-State in private and ambient call procedure	Samsung	CR 0671 24.379 Rel-17	Current status: Postponed Jörgen Mon 1321: Same question regarding WI as for 0256. A few editorial comments. Lazaros Tue 1453: Analysis of what is needed. Revision of C1-210255 _________________________________________ FF: What is the CR category? It reads C on the cover page but the Tdoc is reserved for category B.
C1-210276	Add Application metadata container - MCData	FirstNet / Mike	CR 0200 24.282 Rel-17	Postponed on request from the author Francois Wed 1104: Not comfortable, gives some alternatives for future handling Revision of C1-210080 _________________________________________ Shifted from 17.3.9 Francois Mon 1157: Stage 2 not fully stable. Should we wait? SDP has been discussed. Mike Mon 1424: States the mechanism is appropriate. Argues against SDP Francois Mon 1502: Agrees SDP might not be best, but SA6 work has not concluded. Requests to postpone. Mike Mon 1556: Let's see later in the week how SA6 evolves. If they change we can postpone.
C1-210278	Preconfigured Group Use Only - MCVideo	FirstNet / Mike	CR 0104 24.281 Rel-17	Current status: Agreed Revision of C1-210082 _________________________________________ Jörgen Mon 1149: Minor editorial Mike Mon 1541: Ack
C1-210290	Emergency alert area notification handling at client side for MCPTT	Samsung	CR 0670 24.379 Rel-17	Postponed Revision of C1-210266 _________________________________________ Revision of C1-210254 Jörgen Mon 1317: Questions the WI for the CR. A minor editorial. Mike Mon 1506: One further change in 12.1.1.6 is needed. Wants to cosign. Kiran Tue 1533: Proposes a gloval statement Mike Tue 1640: Agree global statement is better. Jörgen Tue 1958: Is this within this WI? Kiran Wed 0616: Responds. Jörgen Wed 1425: Alternatives for handling
C1-210297	Entry into or exit from a group geographic area functionality handling for MCVideo	Samsung	CR 0107 24.281 Rel-17	Current status: Agreed Revision of C1-210289 _________________________________________ Revision of C1-210265 _________________________________________ Revision of C1-210250 _________________________________________ FF: not sure what’s wrong. Please revise the CR before final agreement with a fresh cover sheet. Jörgen Mon 1313: xs.boolean issue Mike Mon 1437: Editorial, want to cosign
C1-210299	Corrections to protection attribute for altitude and loctimestamp elements	Samsung	CR 0669 24.379 Rel-17	Current status: Agreed Revision of C1-210253 _________________________________________ Jörgen Mon 1155: Some editorial comments. Kiran Mon 1347: Disagrees. Responds.
C1-210301	Preconfigured Group Use Only - MCData	FirstNet / Mike	CR 0201 24.282 Rel-17	Current status: Agreed Revision of C1-210277 _________________________________________ Revision of C1-210081 _________________________________________ Jörgen Mon 1129: Formatting issue. Gives alternatives. Kiran Mon 1257: Cover page, wording in warning text, some "and" changes. Mike Mon 1534: Acks comment by Jörgen Mike Mon 1550: Acks Kiran comments 1) and 3). For 2), prefers to have same text across MCX. UE can display what it wants.
C1-210322	Authorized user being notified about other users floor queue status	Samsung	CR 0295 24.380 Rel-17	Current status: Agreed Revision of C1-210298 _________________________________________ Jörgen Wed 2336some issues Revision of C1-210291 _________________________________________ Mike Wed 1633: Minor comment Kiran Wed 1649: Ack Revision of C1-210268 _________________________________________ Revision of C1-210257 _________________________________________ Revision of C1-207442 FF: What is the current version? It reads 17.0.0 on the cover page but the Tdoc is reserved for version 17.1.0. Jörgen Mon 1945: A number of comments Kiran Tue 1339: Responds. Agrees on some comments.
C1-210430	PDN connections in UE initial config	Ericsson /Jörgen	CR 0168 24.484 Rel-17	Current status: Agreed Revision of C1-210302 _________________________________________ Revision of C1-210142 _________________________________________ FF: cover says “enh3MCPTT” Kiran Mond 1026: Some comments, seems editorial in nature. Mike Mon 1437: Omitted word, some clarification of list semantics needed. xsd file missing.
eMONASTERY2	Jörgen – Breakout	Enhancements to Mobile Communication System for Railways Phase 2
C1-210232	Call control of FAs allowed in a first-to-answer call	Nokia, Nokia Shanghai Bell	CR 0668 24.379 Rel-17	Postponed Kiran Mon 1026: More changes required. Nevenka Mon 1808: Can warning code descriptions be improved? Some hard spaces. Lazaros Thu 1001: Responds to comment. Draft in draftRev Kiran Thu 1031: Some missing elements Lazaros Thu 1105: Ack, some response.
C1-210233	Update MCPTT user profile to support allowed Fas	Nokia, Nokia Shanghai Bell	CR 0169 24.484 Rel-17	Postponed Kiran Mon 1026: Proposes a flag instead of list. Jörgen Mon 1330: Small comments. Terminology in 24.483 and 24.484 should be consistent. Nevenka Mon 1917: Proposes name for the lists. Lazaros Thu 0014:Responds Nevenka Thu 0924: Fine with explanation. Kiran Thu 1012: Fine, no further comments
C1-210234	MO update to support allowed FAs	Nokia, Nokia Shanghai Bell	CR 0087 24.483 Rel-17	Postponed Nevenka Mon 1856: Comment on names of leaves, description should mention used FA, text could be clearer. Error using MCPTT user instead of FA. Lazaros Thu 0013: See draft in draftRev. Nevenka Thu 0908: I am fine with the updates
C1-210238	Work plan of Enhancements to Mobile Communication System for Railways Phase 2 (eMONASTERY2)	Nokia, Nokia Shanghai Bell	discussion Rel-17	Noted
C1-210410	Call control - Restricting MCVideo private communications	Nokia, Nokia Shanghai Bell	CR 0105 24.281 Rel-17	Current status: Agreed Revision of C1-210235 _________________________________________ Nevenka Mon 1746: Hard space. Lazaros Wed 1933: See draftRev
C1-210411	Update configuration to Restrict MCVideo private communications	Nokia, Nokia Shanghai Bell	CR 0170 24.484 Rel-17	Current status: Agreed Revision of C1-210236 _________________________________________ Jörgen Mon 1333: Small comment, namespace incorrect. Jörgen Wed 2309: Format issue. Lazaros Wed 2309: Ack
C1-210412	MOs to restrict MCVideo private communications	Nokia, Nokia Shanghai Bell	CR 0088 24.483 Rel-17	Current status: Agreed Revision of C1-210237 _________________________________________ Nevenka Mon 1738: Are the Required/Optional correct. One copy and paste error? A wording proposal. Lazaros Wed 1933: Responds Jörgen Thu 0750: Responds on Required/Optional. Lazaros Thu 1142, Jörgen Thu 1158: More responses. Confirmed understanding.
Stop24980	Jörgen – Breakout	Stop updating TR 24.980 No CRs needed, 100%
Other Rel-17 IMS & MC issues (TEI17)	NOT IN SCOPE	Other Rel-17 IMS and MC topics
Output Liaison Statements	Tdoc	Title	Prepared by	To/CC	Result & comment
C1-210070	Reply to LS on NR satellite access PLMN selection	OPPO / Chen	LS out Rel-17	C1-210070, C1-210124 and C1-210141 all related to LS in C1-210047
C1-210124	[draft] Reply to LS on NR satellite access PLMN selection	Apple	LS out Rel-17	C1-210070, C1-210124 and C1-210141 all related to LS in C1-210047
C1-210141	Draft reply LS to SA2 on NR satelltie access PLMN selection	Qualcomm Incorporated / Amer	LS out Rel-17	C1-210070, C1-210124 and C1-210141 all related to LS in C1-210047
C1-210125	LS on selecting a PLMN with an MCC not corresponding to the country of a UE’s location	Nokia, Nokia Shanghai Bell	LS out Rel-17
C1-210189	Reply_LS_On_APIs_In_EDGEAPP	Samsung / Sapan	LS out Rel-17
C1-210258	LS Response on inconsistency in specifying handling of MCPTT SIP 183 (Session Progress) response in TS 24.379	Samsung	LS out Rel-14	Revision of C1-207662
C1-210226	Reply LS to S6-202009/C1-210050 on APIs in EDGEAPP (to: SA6; cc: CT3; contact: Huawei)	Huawei, HiSilicon /Christian	LS out Rel-17	Shifted from 17.2.10
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-210095	void	void	pCR 24.811 Rel-17	Withdrawn Revision of C1-207323
C1-210096	void	void	pCR 24.811 Rel-17	Withdrawn Revision of C1-207324
C1-210097	void	void	pCR 24.811 Rel-17	Withdrawn Revision of C1-207325
C1-210098	void	void	pCR 24.811 Rel-17	Withdrawn Revision of C1-207326
C1-210099	void	void	pCR 24.811 Rel-17	Withdrawn Revision of C1-207327
C1-210100	void	void	pCR 24.811 Rel-17	Withdrawn Revision of C1-207328
C1-210101	void	void	pCR 24.811 Rel-17	Withdrawn Revision of C1-207329
C1-210102	void	void	pCR 24.811 Rel-17	Withdrawn Revision of C1-207331
C1-210103	void	void	pCR 24.811 Rel-17	Withdrawn Revision of C1-207332
C1-210104	void	void	pCR 24.811 Rel-17	Withdrawn Revision of C1-207333
C1-210105	void	void	pCR 24.811 Rel-17	Withdrawn
A.O.B.	Tdoc	Title	Source	Tdoc info	Result & comments
Closing Friday by 15:00 UTC 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 28 January 2021 15:00 UTC Last comments: Friday 29 January 2021 15:00 UTC