Tdoc List

2020-02-28 16:27

Agenda Topic TDoc Title Source Type For Avail Treated Decision Wdrn Replaced-by Replaces
1 Opening of the meeting C3‑201529 Exception Sheet for Ecapif Samsung WI exception request Agreement No
No
 		reserved No    
    C3‑201530 Exception Sheet for eNS ZTE WI exception request Agreement No
No
 		reserved No    
    C3‑201531 Exception Sheet for 5G_CIoT Qualcomm WI exception request Agreement No
No
 		reserved No    
    C3‑201532 Exception Sheet for 5G_WWC Huawei WI exception request Agreement No
No
 		reserved No    
    C3‑201533 Exception Sheet for RACS Qualcomm WI exception request Agreement No
No
 		reserved No    
    C3‑201534 Exception Sheet for eV2XARC Huawei WI exception request Agreement No
No
 		reserved No    
    C3‑201535 Exception Sheet for SEAL Samsung WI exception request Agreement No
No
 		reserved No    
2 Agenda/Schedule C3‑201042 Way of Working for CT3#108-e Electronic Meeting CT3 chairman agenda Information Yes
YesCT3 Chair represented the working procedures for CT3 e-meeting. For the deadline of email discussion, CT3 chair suggest to avoid the last time comments. It proposed that the final comments shall be sent out in 27th Feb.
 		noted No    
2.1 Approval of the agenda C3‑201000 Draft Agenda for the CT3#108 e-Meeting CT3 chairman agenda Information Yes
Yes
 		noted No    
2.2 Proposed Schedule C3‑201001 INFO Proposed Schedule for CT3#108 CT3 chairman other Information Yes
Yes
 		noted No    
3 Registration of documents C3‑201002 Allocation of documents to agenda items (at Deadline) CT3 chairman other Information Yes
Yes
 		noted No    
    C3‑201003 Allocation of documents to agenda items (Start of Day 1) CT3 chairman other Information Yes
Yes
 		noted No    
    C3‑201004 Allocation of documents to agenda items (Start of Day 2) CT3 chairman other Information Yes
Yes
 		noted No    
    C3‑201005 Allocation of documents to agenda items (Start of Day 3) CT3 chairman other Information Yes
Yes
 		noted No    
    C3‑201006 Allocation of documents to agenda items (Start of Day 4) CT3 chairman other Information Yes
Yes
 		noted No    
    C3‑201007 Allocation of documents to agenda items (Start of Day 5) CT3 chairman other Information Yes
Yes
 		noted No    
    C3‑201008 Allocation of documents to agenda items (Start of Day 6) CT3 chairman other Information Yes
Yes
 		noted No    
    C3‑201009 Allocation of documents to agenda items (Start of Day 7) CT3 chairman other Information Yes
Yes
 		noted No    
    C3‑201010 Allocation of documents to agenda items (Start of Day 8) CT3 chairman other Information Yes
Yes
 		noted No    
    C3‑201011 Allocation of documents to agenda items (End of Day 8) CT3 chairman other Information No
No
 		reserved No    
4 Reports                      
4.1 Report from previous CT3 meeting C3‑201014 Minutes of CT3#107 MCC report Approval Yes
Yes
 		approved No    
4.2 Report from previous CT plenary C3‑201013 Summary of CT#86 related to CT3 CT3 chairman report Approval Yes
Yes
 		noted No    
4.3 Reports from other groups                      
5 Items for immediate consideration                      
5.1 IPR disclosures                      
5.2 Antitrust declarations                      
5.3 Statement Regarding Engagement with Companies Added to the U.S. Export Administration Regulations (EAR) Entity List in 3GPP Activities                      
5.4 Other items for immediate consideration                      
6 Received Liaison Statements C3‑201017 Reply LS on NID structure and length RAN2 LS in Discussion Yes
Yes
 		noted No    
    C3‑201018 Reply LS on "SMF Event Exposure enhancement for service experience" SA2 LS in Discussion Yes
Yes
 		noted No    
    C3‑201019 Reply LS on N6 routing information in AF acknowledgement SA2 LS in Discussion Yes
YesCT3 agreed to be aligned with SA2.
 		noted No    
    C3‑201020 Reply LS on Nsmf_EventExposure and Nnef_EventExposure service handling of the "Downlink data delivery status" and "Availability after DDN Failure" events. SA2 LS in Discussion Yes
Yes
 		noted No    
    C3‑201021 Reply LS on supporting simultaneous online and offline reporting level access SA2 LS in Discussion Yes
Yes
 		postponed No    
    C3‑201022 Reply LS on interface selection of GERAN, UTRAN and EUTRAN access SA2 LS in Discussion Yes
YesCMCC(zhenning): SA2 decided to postpone this functionality to R-17
 		noted No    
    C3‑201023 Reply LS to CT3 on the PCR triggers for wireline access and inputs for IPTV service SA2 LS in Discussion Yes
Yes
 		noted No    
    C3‑201024 LS on Reply to LS on background data transfer policy re-negotiation SA2 LS in Discussion Yes
Yes
 		noted No    
    C3‑201025 LS Response on Binding indication for subscribe/notify SA2 LS in Discussion Yes
YesHuawei: this LS does not impact on CT3 specifications.
 		noted No    
    C3‑201026 LS reply on Support of Network Address Translation in the User Plane function SA2 LS in Discussion Yes
Yes
 		noted No    
    C3‑201027 Reply LS on Policy control for ATSSS SA2 LS in Discussion Yes
Yes
 		noted No    
    C3‑201028 Reply LS on Enhanced coverage restriction SA2 LS in Discussion Yes
Yes
 		noted No    
    C3‑201029 Reply LS on Service on I-NEF Event Exposure SA2 LS in Discussion Yes
Yes
 		replied to No    
    C3‑201487 Reply LS on Service on I-NEF Event Exposure Huawei LS out approval Yes
Yes
 		revised No C3‑201494  
    C3‑201494 Reply LS on Service on I-NEF Event Exposure Huawei LS out approval Yes
Yes
 		approved No   C3‑201487
    C3‑201030 Reply to LS on separating scenarios for EPS Fallback SA2 LS in Discussion Yes
Yes
 		noted No    
    C3‑201031 LS on Group Message Delivery SA4 LS in Discussion Yes
Yes
 		postponed No    
    C3‑201032 LS on updates to CHEM feature and use of Application Layer Redundancy SA4 LS in Discussion Yes
Yes
 		postponed No    
    C3‑201033 LS on QoS mapping procedure SA4 LS in Discussion Yes
Yes
 		noted No    
    C3‑201034 LS on HLS and Hybrid DASH/HLS Service in MBMS SA4 LS in Discussion Yes
Yes
 		postponed No    
    C3‑201035 LS to SA2 Introduction of CHF Address from PCF SA5 LS in Discussion Yes
Yes
 		postponed No    
    C3‑201036 LS Reply to LS Reply to LS to SA2 Introduction of CHF Address from PCF SA5 LS in Discussion Yes
Yes
 		postponed No    
    C3‑201037 LS on Addition of AVP code definitions SA5 LS in Discussion Yes
Yes
 		noted No    
    C3‑201038 Reply LS on clarifications regarding V2XAPP services SA6 LS in Discussion Yes
Yes
 		noted No    
    C3‑201039 LS on API additions to SEAL and V2XAPP SA6 LS in Discussion Yes
Yes
 		noted No    
    C3‑201040 LIAISE-364_Broadband-Forum-adopts-open-structure_FINAL Broadband Forum LS in Discussion Yes
Yes
 		noted No    
    C3‑201329 Broadband Forum LIAISE-376 General status of WWC work Broadband Forum LS in Discussion Yes
Yes
 		noted No    
    C3‑201439 BBF LIAISE-382-03 Clarification on encryption requirements for AGF interfaces (N1, N2, N3) [WWC] Broadband Forum LS in Discussion Yes
YesChari suggested to forward to SA3.
 		noted No    
16.1 Rel-16 Work Items                      
16.1.1 New or revised Work Items C3‑201071 Revised WID on CT aspects of optimisations on UE radio capability signalling Qualcomm Incorporated WID revised Endorsement Yes
YesCT3 agreed to endorse the WID.
 		endorsed No    
    C3‑201072 Revised WID on CT aspects of Cellular IoT support and evolution for the 5G System Qualcomm Incorporated WID revised Endorsement Yes
YesCT3 agreed to endorse the WID.
 		endorsed No    
    C3‑201232 Revised WID on Multi-device and multi-identity Ericsson WID revised Endorsement Yes
YesCT3 agreed to endorse the WID.
 		endorsed No    
    C3‑201334 New WID on Service Based Interface Protocol Improvements Release 17 China Mobile International Ltd WID new Endorsement Yes
Yes
 		postponed No    
16.1.2 Contributions on Work Items                      
16.2 Multi-device and multi-identity [MuD]                      
16.3 IMS Stage-3 IETF Protocol Alignment [IMSProtoc16]                      
16.4 Enhancement of 5G PCC related services [en5GPccSer] C3‑201077 Update of the same PCF selection Huawei CR Agreement Yes
YesEricsson commented that clarify the PCF receives the "403 Forbidden" status code with "cause" attribute of the ProblemDetails data structure set to "EXISTING_BINDING_INFO_FOUND" and indicate the attribute in the BindingResp data structure where the FQDN is encoded and the attribute in the BindingResp data structure where the IP endpoints are encoded.
 		revised No C3‑201421  
    C3‑201421 Update of the same PCF selection Huawei CR Agreement Yes
Yes
 		agreed No   C3‑201077
    C3‑201078 Update of same PCF selectin Huawei CR Agreement Yes
Yes
 		revised No C3‑201422  
    C3‑201422 Update of same PCF selectin Huawei CR Agreement Yes
Yes
 		agreed No   C3‑201078
    C3‑201079 PCF selection performed by the AMF Huawei CR Agreement Yes
YesC3-201079 and C3-201182 merged into C3-201423
 		merged No    
    C3‑201080 DNN Clarification Huawei CR Agreement Yes
YesEricsson commented that it is not required a clarification of the DNN information in PCC APIs. DNN for PCC interfaces is defined with both alternative formats, so the clarification does not add information to the current definition of DNN in 29.571, where APN Operator Identifier is optional (see 23.003). i.e., no further clarification is needed. Ericsson accepts the CR although does not agree with this practice.
 		agreed No    
    C3‑201081 DNN Clarification Huawei CR Agreement Yes
YesEricsson: same comments as C3-201080
 		agreed No    
    C3‑201082 DNN Clarification Huawei CR Agreement Yes
YesEricsson: same comments as C3-201080
 		agreed No    
    C3‑201083 DNN Clarification Huawei CR Agreement Yes
YesEricsson: same comments as C3-201080
 		agreed No    
    C3‑201084 DNN Clarification Huawei CR Agreement Yes
YesEricsson: same comments as C3-201080
 		agreed No    
    C3‑201085 DNN Clarification Huawei CR Agreement Yes
YesEricsson: same comments as C3-201080
 		agreed No    
    C3‑201086 Cell change trigger Huawei CR Agreement Yes
YesEricsson commented whether a feature to support the trigger is needed. Huawei accepted to remove the feature.
 		revised No C3‑201424  
    C3‑201424 Cell change trigger Huawei CR Agreement Yes
Yes
 		agreed No   C3‑201086
    C3‑201087 Correction on UE Policy Association Establishment Huawei CR Agreement Yes
Yes
 		agreed No    
    C3‑201088 Correction to the policy decision data and condition data Huawei CR Agreement Yes
Yes
 		revised No C3‑201425  
    C3‑201425 Correction to the policy decision data and condition data Huawei CR Agreement Yes
Yes
 		agreed No   C3‑201088
    C3‑201089 Reallocation of credit Huawei CR Agreement Yes
YesEricsson commented a feature to support the trigger is not required. If the PCF does not support the trigger, the PCF will never provision it. If the SMF does not support the trigger, when the PCF provisions it the SMF will ignore it. Huawei accepted to remove the feature.
 		revised No C3‑201426  
    C3‑201426 Reallocation of credit Huawei CR Agreement Yes
Yes
 		agreed No   C3‑201089
    C3‑201090 UE initiated resource modification correction Huawei CR Agreement Yes
Yes
 		revised No C3‑201427  
    C3‑201427 UE initiated resource modification correction Huawei CR Agreement Yes
Yes
 		agreed No   C3‑201090
    C3‑201091 Application data change notification Huawei CR Agreement Yes
YesEricsson commented that whether to have a new resource for data change subscription, for traffic influence data. At that point of time, Ericsson was not in favor of defining a second mechanism just because we didn’t strictly follow what is written in 29.504. ZTE agree with Ericsson's opinion. Huawei agreed to remove the supported feature definition.
 		revised No C3‑201419  
    C3‑201419 Application data change notification Huawei CR Agreement Yes
Yes
 		agreed No   C3‑201091
    C3‑201139 Corrections related to DNN replacement ZTE, Ericsson CR Agreement Yes
YesHuawei accepted two features.
 		agreed No    
    C3‑201140 Remove the possibility of SNSSAI change ZTE, Ericsson CR Agreement Yes
YesHuawei commented that it need to check how to control misalignments between values.
 		agreed No    
    C3‑201141 Mapping Of Allowed NSSAI ZTE, Ericsson CR Agreement Yes
Yes
 		agreed No    
    C3‑201142 DNN selection mode ZTE, Ericsson CR Agreement Yes
YesHuawei, ZTE and Ericsson agreed to add a feature.
 		revised No C3‑201485  
    C3‑201485 DNN selection mode ZTE, Ericsson CR Agreement Yes
Yes
 		agreed No   C3‑201142
    C3‑201143 Include influenceId into TrafficInfluData for Notification ZTE CR Agreement Yes
YesHuawei agreed to remove the text of C3-201091 that collides with C3-201143.
 		revised No C3‑201486  
    C3‑201486 Include influenceId into TrafficInfluData for Notification ZTE, Ericsson CR Agreement Yes
Yes
 		agreed No   C3‑201143
    C3‑201154 Adding EPS FB related trigger in N5 CT WG3 CR Agreement No
Yes
 		withdrawn Yes    
    C3‑201155 Adding EPS FB related trigger in N7 CT WG3 CR Agreement No
Yes
 		withdrawn Yes    
    C3‑201156 Reporting the EPS Fallback event CT WG3 CR Agreement No
Yes
 		withdrawn Yes    
    C3‑201160 Adding EPS FB related trigger in N5 China Telecom, Huawei CR Agreement Yes
YesC3-201167 and C3-201160 merged into C3-201495
 		merged No    
    C3‑201161 Adding EPS FB related trigger in N7 China Telecom, Huawei CR Agreement Yes
YesC3-201169 and C3-201161 merged into C3-201497
 		merged No    
    C3‑201162 Reporting the EPS Fallback event China Telecom, Huawei CR Agreement Yes
YesC3-201168 and C3-201162 merged into C3-201496
 		merged No    
    C3‑201166 Subscription and notification to data changes related to a subset of resource data, Policy Data set Ericsson CR Agreement Yes
Yes
 		revised No C3‑201428  
    C3‑201428 Subscription and notification to data changes related to a subset of resource data, Policy Data set Ericsson CR Agreement Yes
YesDependency with a CT4 CR
 		agreed No   C3‑201166
    C3‑201167 Report of EPS Fallback Ericsson CR Agreement Yes
YesC3-201167 and C3-201160 merged into C3-201495
 		revised No C3‑201495  
    C3‑201495 Report of EPS Fallback Ericsson, China Telecom, Huawei CR Agreement Yes
Yes
 		agreed No   C3‑201167
    C3‑201168 Report of EPS Fallback Ericsson CR Agreement Yes
YesC3-201168 and C3-201162 merged into C3-201496
 		revised No C3‑201496  
    C3‑201496 Report of EPS Fallback Ericsson, China Telecom, Huawei CR Agreement Yes
Yes
 		agreed No   C3‑201168
    C3‑201169 Report of EPS Fallback Ericsson CR Agreement Yes
YesC3-201169 and C3-201161 merged into C3-201497
 		revised No C3‑201497  
    C3‑201497 Report of EPS Fallback Ericsson, China Telecom, Huawei CR Agreement Yes
Yes
 		agreed No   C3‑201169
    C3‑201180 Completion of DNN replacement functionality Ericsson, ZTE CR Agreement Yes
Yes
 		agreed No    
    C3‑201181 Completing the description of triggers values applicability in PolicyAssociation and PolicyUpdate types Ericsson, ZTE CR Agreement Yes
Yes
 		revised No C3‑201429  
    C3‑201429 Completing the description of triggers values applicability in PolicyAssociation and PolicyUpdate types Ericsson, ZTE CR Agreement Yes
Yes
 		agreed No   C3‑201181
    C3‑201182 DNN Replacement as PCF discovery factor for the AMF Ericsson, ZTE CR Agreement Yes
YesC3-201079 and C3-201182 merged into C3-201423
 		revised No C3‑201423  
    C3‑201423 DNN Replacement as PCF discovery factor for the AMF Ericsson, ZTE, Huawei CR Agreement Yes
Yes
 		agreed No   C3‑201182
    C3‑201183 Completing the description of “PLMN_CH” and “CON_STATE_CH” triggers. Ericsson CR Agreement Yes
Yes
 		agreed No    
    C3‑201224 Resolve editor note for PATCH Ericsson CR Agreement Yes
Yes
 		agreed No    
    C3‑201236 Adding "ProblemDetails" data type in table 5.6.1-2 Ericsson CR Agreement Yes
Yes
 		agreed No    
    C3‑201237 Miscellaneous errors Ericsson CR Agreement Yes
Yes
 		revised No C3‑201430  
    C3‑201430 Miscellaneous errors Ericsson CR Agreement Yes
Yes
 		agreed No   C3‑201237
    C3‑201238 Support of the Update service operation Ericsson CR Agreement Yes
Yes
 		agreed No    
    C3‑201326 Definition of error “POLICY_ASSOCIATION_NOT_FOUND” Ericsson CR Agreement Yes
YesHuawei commented that this is a common issue both the API with callback URI. Need to defined a general solution rather than define an application error case by case.
 		postponed No    
    C3‑201327 Definition of error “POLICY_ASSOCIATION_NOT_FOUND” Ericsson CR Agreement Yes
Yes
 		postponed No    
    C3‑201328 Definition of error “POLICY_ASSOCIATION_NOT_FOUND” Ericsson CR Agreement Yes
Yes
 		postponed No    
16.5 CT aspects on Enablers for Network Automation for 5G [eNA] C3‑201043 Correction of PING_PONG UE Definition and Usage Spirent Communications CR Agreement Yes
YesC3-201043, C3-201332 and C3-201282 merged into C3-201378
 		merged No    
    C3‑201044 Definition of QosRequirement Huawei CR Agreement Yes
Yes
 		revised No C3‑201340  
    C3‑201340 Definition of QosRequirement Huawei CR Agreement Yes
Yes
 		agreed No   C3‑201044
    C3‑201045 Description of consumer functionalities Huawei CR Agreement Yes
YesC3-201045 and C3-201075 merged into C3-201379
 		revised No C3‑201379  
    C3‑201379 Description of consumer functionalities Huawei, Ericsson CR Agreement Yes
Yes
 		agreed No   C3‑201045
    C3‑201074 Update the types of analytics events Ericsson CR Agreement Yes
Yes
 		revised No C3‑201380  
    C3‑201380 Update the types of analytics events Ericsson CR Agreement Yes
Yes
 		agreed No   C3‑201074
    C3‑201075 Adding functionalities of NF Service Consumers Ericsson CR Agreement Yes
YesC3-201045 and C3-201075 merged into C3-201379
 		merged No    
    C3‑201076 Complete Feature negotiation description Ericsson CR Agreement Yes
YesHuawei commented the basic principle of feature negotiation has been described in TS 29.500 which is applicable to all CT3/CT4 SBIs. No need to repeat here. Other specifications also didn't clarify doubly, e.g. TS 29.512, TS 29.504. Nokia supported Huawei's opinion. CT3 should have a rule for all CT3's specificaiton. ZTE supported this CR.
 		postponed No    
    C3‑201137 Update Feature applicability for Rel-16 new data types Ericsson CR Agreement Yes
Yes
 		revised No C3‑201382  
    C3‑201382 Update Feature applicability for Rel-16 new data types Ericsson CR Agreement Yes
Yes
 		agreed No   C3‑201137
    C3‑201157 Adding NWDAF as Nbsf_management service consumer CT WG3 CR Agreement No
Yes
 		withdrawn Yes    
    C3‑201158 Corrections in TS29.520 CT WG3 CR Agreement No
Yes
 		withdrawn Yes    
    C3‑201159 Update the filters of UE related analytics CT WG3 CR Agreement No
Yes
 		withdrawn Yes    
    C3‑201163 Adding NWDAF as Nbsf_management service consumer China Telecom CR Agreement Yes
Yes
 		revised No C3‑201381  
    C3‑201381 Adding NWDAF as Nbsf_management service consumer China Telecom CR Agreement Yes
Yes
 		revised No C3‑201518 C3‑201163
    C3‑201518 Adding NWDAF as Nbsf_management service consumer China Telecom CR Agreement Yes
Yes
 		agreed No   C3‑201381
    C3‑201164 Corrections in TS29.520 China Telecom CR Agreement Yes
Yes
 		revised No C3‑201465  
    C3‑201465 Corrections in TS29.520 China Telecom CR Agreement Yes
Yes
 		revised No C3‑201519 C3‑201164
    C3‑201519 Corrections in TS29.520 China Telecom CR Agreement Yes
Yes
 		agreed No   C3‑201465
    C3‑201165 Update the filters of UE related analytics China Telecom CR Agreement Yes
YesC3-201165 and C3-201217 merged into C3-201383
 		merged No    
    C3‑201213 Clarify start time and end time Ericsson CR Agreement Yes
Yes
 		revised No C3‑201384  
    C3‑201384 Clarify start time and end time Ericsson CR Agreement Yes
Yes
 		agreed No   C3‑201213
    C3‑201214 Pseudo-CR on Clarify target UE identity Ericsson pCR Approval Yes
YesC3-201214 and C3-201299 merged into C3-201466
 		revised No C3‑201466  
    C3‑201466 Pseudo-CR on Clarify target UE identity Ericsson, Huawei pCR Approval Yes
Yes
 		agreed No   C3‑201214
    C3‑201215 Pseudo-CR on Correct HTTP and security text Ericsson pCR Approval Yes
Yes
 		revised No C3‑201385  
    C3‑201385 Pseudo-CR on Correct HTTP and security text Ericsson pCR Approval Yes
Yes
 		agreed No   C3‑201215
    C3‑201216 Correct QoS sustainability Ericsson CR Agreement Yes
YesC3-201216 and C3-201306 merged into C3-201386
 		revised No C3‑201386  
    C3‑201386 Correct QoS sustainability Ericsson, Huawei CR Agreement Yes
Yes
 		agreed No   C3‑201216
    C3‑201217 Correct UE mobility and communication Ericsson CR Agreement Yes
YesC3-201165 and C3-201217 merged into C3-201383 C3-201325 and C3-201217 merged into C3-201383
 		revised No C3‑201383  
    C3‑201383 Correct UE mobility and communication Ericsson, China Telecom, Huawei CR Agreement Yes
Yes
 		agreed No   C3‑201217
    C3‑201218 Correct UE mobility and communication Ericsson CR Agreement Yes
YesC3-201218 and C3-201293 merged into C3-201387
 		revised No C3‑201387  
    C3‑201387 Correct UE mobility and communication Ericsson, Huawei CR Agreement Yes
Yes
 		agreed No   C3‑201218
    C3‑201219 Support network performance analytics Ericsson CR Agreement Yes
YesC3-201219 and C3-201333 merged into C3-201388
 		revised No C3‑201388  
    C3‑201388 Support network performance analytics Ericsson, Orange CR Agreement Yes
Yes
 		agreed No   C3‑201219
    C3‑201220 Support network performance analytics Ericsson CR Agreement Yes
Yes
 		revised No C3‑201498  
    C3‑201498 Support network performance analytics Ericsson CR Agreement Yes
Yes
 		agreed No   C3‑201220
    C3‑201221 QFI allocation event Ericsson CR Agreement Yes
Yes
 		revised No C3‑201389  
    C3‑201389 QFI allocation event Ericsson CR Agreement Yes
Yes
 		agreed No   C3‑201221
    C3‑201222 Support BDT policy candidates in notification Ericsson CR Agreement Yes
Yes
 		revised No C3‑201390  
    C3‑201390 Support BDT policy candidates in notification Ericsson CR Agreement Yes
Yes
 		agreed No   C3‑201222
    C3‑201223 Support BDT policy candidates in notification Ericsson CR Agreement Yes
Yes
 		revised No C3‑201391  
    C3‑201391 Support BDT policy candidates in notification Ericsson CR Agreement Yes
Yes
 		agreed No   C3‑201223
    C3‑201239 BDT renegotiation upon the network conditions change Ericsson CR Agreement Yes
Yes
 		revised No C3‑201392 C3‑195065
    C3‑201392 BDT renegotiation upon the network conditions change Ericsson CR Agreement Yes
Yes
 		agreed No   C3‑201239
    C3‑201240 BDT renegotiation upon the network conditions change Ericsson CR Agreement Yes
Yes
 		agreed No   C3‑195228
    C3‑201241 Correcting QoS sustainability information Ericsson CR Agreement Yes
Yes
 		revised No C3‑201393  
    C3‑201393 Correcting QoS sustainability information Ericsson CR Agreement Yes
Yes
 		agreed No   C3‑201241
    C3‑201277 Corrections on resouce name Huawei CR Agreement Yes
Yes
 		revised No C3‑201364  
    C3‑201364 Corrections on resouce name Huawei CR Agreement Yes
Yes
 		agreed No   C3‑201277
    C3‑201278 Data used for area of interest Huawei CR Agreement Yes
Yes
 		revised No C3‑201365  
    C3‑201365 Data used for area of interest Huawei CR Agreement Yes
Yes
 		agreed No   C3‑201278
    C3‑201279 Any UE possibility for UE mobility and UE communication Huawei CR Agreement Yes
Yes
 		revised No C3‑201366  
    C3‑201366 Any UE possibility for UE mobility and UE communication Huawei CR Agreement Yes
Yes
 		agreed No   C3‑201279
    C3‑201280 Nnwdaf_EventsSubscription API, Support of service experience Huawei CR Agreement Yes
YesC3-201280 and C3-201331 merged into C3-201394
 		revised No C3‑201394  
    C3‑201394 Nnwdaf_EventsSubscription API, Support of service experience Huawei, China Mobile Com. Corporation CR Agreement Yes
Yes
 		agreed No   C3‑201280
    C3‑201281 Nnwdaf_AnalyticsInfo API, Support of service experience Huawei CR Agreement Yes
YesC3-201281 and C3-201331 merged into C3-201395
 		revised No C3‑201395  
    C3‑201395 Nnwdaf_AnalyticsInfo API, Support of service experience Huawei, China Mobile Com. Corporation CR Agreement Yes
Yes
 		agreed No   C3‑201281
    C3‑201282 Nnwdaf_EventsSubscription API, Support of abnormal behaviour Huawei CR Agreement Yes
YesC3-201043, C3-201332 and C3-201282 merged into C3-201378
 		revised No C3‑201378  
    C3‑201378 Nnwdaf_EventsSubscription API, Support of abnormal behaviour Huawei, Spirent, Orange CR Agreement Yes
Yes
 		agreed No   C3‑201282
    C3‑201283 Nnwdaf_AnalyticsInfo API, Support of abnormal behaviour Huawei CR Agreement Yes
YesC3-201283 and C3-201332 merged into C3-201396
 		revised No C3‑201396  
    C3‑201396 Nnwdaf_AnalyticsInfo API, Support of abnormal behaviour Huawei, Orange CR Agreement Yes
Yes
 		agreed No   C3‑201283
    C3‑201288 Group Id in UeCommunicationInfo Huawei pCR Approval Yes
Yes
 		agreed No    
    C3‑201289 Support of Exception event Huawei pCR Approval Yes
Yes
 		revised No C3‑201367  
    C3‑201367 Support of Exception event Huawei pCR Approval Yes
Yes
 		agreed No   C3‑201289
    C3‑201290 Definition of ServiceExperienceInfo Huawei pCR Approval Yes
Yes
 		revised No C3‑201368  
    C3‑201368 Definition of ServiceExperienceInfo Huawei pCR Approval Yes
Yes
 		agreed No   C3‑201290
    C3‑201291 Definition of UeMobilityInfo Huawei pCR Approval Yes
Yes
 		revised No C3‑201413  
    C3‑201413 Definition of UeMobilityInfo Huawei pCR Approval Yes
Yes
 		agreed No   C3‑201291
    C3‑201292 OpenAPI file for Nnef_EventExposure API Huawei pCR Approval Yes
Yes
 		revised No C3‑201370  
    C3‑201370 OpenAPI file for Nnef_EventExposure API Huawei pCR Approval Yes
Yes
 		agreed No   C3‑201292
    C3‑201293 Correction on data type used for event reporting Huawei CR Agreement Yes
YesC3-201218 and C3-201293 merged into C3-201387
 		merged No    
    C3‑201294 AnalyticsExposure API, Analytics Event Filter associated with all events Huawei CR Agreement Yes
Yes
 		revised No C3‑201414  
    C3‑201414 AnalyticsExposure API, Analytics Event Filter associated with all events Huawei CR Agreement Yes
Yes
 		agreed No   C3‑201294
    C3‑201295 AnalyticsExposure API, support of abnormal behaviour Huawei CR Agreement Yes
Yes
 		revised No C3‑201397  
    C3‑201397 AnalyticsExposure API, support of abnormal behaviour Huawei CR Agreement Yes
Yes
 		agreed No   C3‑201295
    C3‑201296 AnalyticsExposure API, support of data congestion Huawei CR Agreement Yes
Yes
 		revised No C3‑201398  
    C3‑201398 AnalyticsExposure API, support of data congestion Huawei CR Agreement Yes
Yes
 		agreed No   C3‑201296
    C3‑201297 OpenAPI correction on anyUeInd within EventFilter Huawei pCR Approval Yes
Yes
 		agreed No    
    C3‑201298 Procedure extension and data correction Huawei pCR Approval Yes
Yes
 		revised No C3‑201399  
    C3‑201399 Procedure extension and data correction Huawei pCR Approval Yes
Yes
 		agreed No   C3‑201298
    C3‑201299 User Identification Huawei pCR Approval Yes
YesC3-201214 and C3-201299 merged into C3-201466
 		merged No    
    C3‑201300 Any application case for UE mobility and UE communication Huawei pCR Approval Yes
YesEricsson doesn't agree with the reason for change, Huawei will check with SA2.
 		postponed No    
    C3‑201301 Exception event supported by the AF Huawei pCR Approval Yes
Yes
 		revised No C3‑201440  
    C3‑201440 Exception event supported by the AF Huawei pCR Approval Yes
Yes
 		agreed No   C3‑201301
    C3‑201306 Shorten attribute names for QoS Sustainability Huawei CR Agreement Yes
YesC3-201216 and C3-201306 merged into C3-201386
 		merged No    
    C3‑201307 Group Id in UeCommunicationCollection Huawei pCR Approval Yes
Yes
 		revised No C3‑201369  
    C3‑201369 Group Id in UeCommunicationCollection Huawei pCR Approval Yes
Yes
 		agreed No   C3‑201307
    C3‑201325 Maximum number of results Huawei CR Agreement Yes
YesC3-201325 and C3-201217 merged into C3-201383
 		merged No    
    C3‑201330 Support of NF Load analytics Orange CR Agreement Yes
YesOrange will check the solution of threshold id from Ericsson will work. Orange agreed to have the info optional in the input, but for the output, need to check if it should be optional or mandatory.
 		revised No C3‑201400  
    C3‑201400 Support of NF Load analytics Orange CR Agreement Yes
Yes
 		agreed No   C3‑201330
    C3‑201331 Define the Date type of ServiceExperienceInfo China Mobile Com. Corporation CR Agreement Yes
YesC3-201280 and C3-201331 merged into C3-201394 C3-201281 and C3-201331 merged into C3-201395
 		merged No    
    C3‑201332 Support of abnormal analytics Orange CR Agreement Yes
YesC3-201043, C3-201332 and C3-201282 merged into C3-201378 C3-201283 and C3-201332 merged into C3-201396
 		merged No    
    C3‑201333 Definition of Network Performance Information Orange CR Agreement Yes
YesC3-201219 and C3-201333 merged into C3-201388
 		merged No    
    C3‑201477 Presentation sheet for TS 29.517 Huawei TS or TR cover Agreement No
No
 		reserved No    
    C3‑201482 TS 29.517 v1.1.0 Huawei draft TS Agreement No
No
 		reserved No    
    C3‑201488 LS on Nnef_NetworkStatus service Huawei LS out Approval Yes
Yes
 		revised No C3‑201499  
    C3‑201499 LS on Nnef_NetworkStatus service Huawei LS out Approval Yes
Yes
 		approved No   C3‑201488
16.6 CT aspects on eSBA [5G_eSBA] C3‑201092 PCF selection performed by the SMF Huawei CR Agreement Yes
Yes
 		revised No C3‑201431  
    C3‑201431 PCF selection performed by the SMF Huawei CR Agreement Yes
Yes
 		agreed No   C3‑201092
    C3‑201275 PCF set Id/PCF Id in Nbsf_Management_Register/Update Nokia, Nokia Shanghai Bell CR Agreement Yes
Yes
 		agreed No    
    C3‑201415 PCF set Id/PCF Id in Nbsf_Management_Register/Update Nokia, Nokia Shanghai Bell CR Agreement No
Yes
 		withdrawn Yes   C3‑201275
    C3‑201276 CHF set and instance Id in charging information Nokia, Nokia Shanghai Bell CR Agreement Yes
Yes
 		agreed No    
16.7 CT aspects of Access Traffic Steering, Switch and Splitting support in 5G system [ATSSS] C3‑201093 Complete the PCC procedure for ATSSS Huawei CR Agreement Yes
YesC3-201147 and C3-201093 merged into C3-201357
 		revised No C3‑201357  
    C3‑201357 Complete the PCC procedure for ATSSS Huawei, ZTE CR Agreement Yes
Yes
 		revised No C3‑201527 C3‑201093
    C3‑201527 Complete the PCC procedure for ATSSS Huawei, ZTE CR Agreement Yes
Yes
 		agreed No   C3‑201357
    C3‑201147 Removal of ENs for ATSSS ZTE CR Agreement Yes
YesC3-201147 and C3-201093 merged into C3-201357
 		merged No    
    C3‑201148 interwoking with EPS for ATSSS ZTE CR Agreement Yes
Yes
 		revised No C3‑201358  
    C3‑201358 interwoking with EPS for ATSSS ZTE CR Agreement Yes
Yes
 		revised No C3‑201489 C3‑201148
    C3‑201489 interwoking with EPS for ATSSS ZTE CR Agreement Yes
Yes
 		agreed No   C3‑201358
    C3‑201149 Additional Access Type for ATSSS ZTE CR Agreement Yes
Yes
 		revised No C3‑201359  
    C3‑201359 Additional Access Type for ATSSS ZTE CR Agreement Yes
Yes
 		agreed No   C3‑201149
16.8 CT aspects of 5GS enhanced support of vertical and LAN services [Vertical_LAN] C3‑201053 TSN bridge information in Npcf_SMPolicyControl_UpdateNotify Service Operation Nokia, Nokia Shanghai Bell CR Agreement Yes
YesC3-201053 and C3-201186 merged into C3-201432
 		merged No    
    C3‑201054 TSC assistance information transport to SMF Nokia, Nokia Shanghai Bell CR Agreement Yes
Yes
 		not pursued No    
    C3‑201055 Clarification of TsnBridgeInfo attributes Nokia, Nokia Shanghai Bell CR Agreement Yes
Yes
 		not pursued No    
    C3‑201056 TSN QoS Container as array Nokia, Nokia Shanghai Bell CR Agreement Yes
Yes
 		not pursued No    
    C3‑201057 Topology parameters in TSNBridgeInfo Nokia, Nokia Shanghai Bell CR Agreement Yes
YesC3-201057 and C3-201185 merged into C3-201434
 		merged No    
    C3‑201058 OpenAPI for TSN Nokia, Nokia Shanghai Bell CR Agreement Yes
Yes
 		not pursued No    
    C3‑201059 Provisioning of TSC assistance information – Create Service Operation Nokia, Nokia Shanghai Bell CR Agreement Yes
Yes
 		not pursued No    
    C3‑201060 TsnBridgeInformation send from AF to SMF - Create Service Operation Nokia, Nokia Shanghai Bell CR Agreement Yes
Yes
 		not pursued No    
    C3‑201061 Provisioning of TSC assistance information – Update Service Operation Nokia, Nokia Shanghai Bell CR Agreement Yes
YesC3-201061, C3-201065, C3-201067 and C3-201191 merged into C3-201435
 		merged No    
    C3‑201062 TsnBridgeInformation send from AF to SMF - Update Service Operation Nokia, Nokia Shanghai Bell CR Agreement Yes
YesC3-201062 and C3-201187 merged into C3-201436
 		merged No    
    C3‑201063 Notification about TSN port detection – TSN_CONTAINER Nokia, Nokia Shanghai Bell CR Agreement Yes
YesC3-201063 and C3-201193 merged into C3-201437
 		merged No    
    C3‑201064 Notification about TSN port detection – No AF session Nokia, Nokia Shanghai Bell CR Agreement Yes
Yes
 		not pursued No    
    C3‑201065 SMF maps TSN Assistance information to 5GS clock Nokia, Nokia Shanghai Bell CR Agreement Yes
YesC3-201061, C3-201065, C3-201067 and C3-201191 merged into C3-201435
 		merged No    
    C3‑201066 TSNQoSContainer data types Nokia, Nokia Shanghai Bell CR Agreement Yes
Yes
 		not pursued No    
    C3‑201067 TSNQoSContainer delay requiements from UPF Nokia, Nokia Shanghai Bell CR Agreement Yes
YesC3-201061, C3-201065, C3-201067 and C3-201191 merged into C3-201435
 		merged No    
    C3‑201068 TSN acknowledgement with TSN attributes Nokia, Nokia Shanghai Bell CR Agreement Yes
Yes
 		not pursued No    
    C3‑201069 OpenAPI for TSN Nokia, Nokia Shanghai Bell CR Agreement Yes
Yes
 		not pursued No    
    C3‑201094 Clarify the support of QoS differention for NPN Huawei CR Agreement Yes
YesEricsson:SA2 does not specify any normative text about how to support QoS differentiation for NPN. Could we postpone this CR till there are specific SA2 requirments in te regard?
 		postponed No    
    C3‑201132 Indication of traffic correlation Huawei CR Agreement Yes
Yes
 		revised No C3‑201337  
    C3‑201337 Indication of traffic correlation Huawei CR Agreement Yes
Yes
 		agreed No   C3‑201132
    C3‑201133 Indication of traffic correlation Huawei CR Agreement Yes
Yes
 		revised No C3‑201338  
    C3‑201338 Indication of traffic correlation Huawei CR Agreement Yes
Yes
 		agreed No   C3‑201133
    C3‑201134 Indication of traffic correlation Huawei CR Agreement Yes
Yes
 		revised No C3‑201339  
    C3‑201339 Indication of traffic correlation Huawei CR Agreement Yes
Yes
 		agreed No   C3‑201134
    C3‑201185 Clarification of DS-TT and NW-TT ports identification Ericsson CR Agreement Yes
YesC3-201057 and C3-201185 merged into C3-201434
 		revised No C3‑201434  
    C3‑201434 Clarification of DS-TT and NW-TT ports identification Ericsson, Nokia, Nokia Shanghai Bell CR Agreement Yes
Yes
 		agreed No   C3‑201185
    C3‑201186 Clarification of DS-TT and NW-TT ports management information Ericsson CR Agreement Yes
YesC3-201053 and C3-201186 merged into C3-201432
 		revised No C3‑201432  
    C3‑201432 Clarification of DS-TT and NW-TT ports management information Ericsson, Nokia, Nokia Shanghai Bell CR Agreement Yes
Yes
 		agreed No   C3‑201186
    C3‑201187 Configuration of one or more NW-TT port management information containers Ericsson CR Agreement Yes
YesC3-201062 and C3-201187 merged into C3-201436
 		revised No C3‑201436  
    C3‑201436 Configuration of one or more NW-TT port management information containers Ericsson, Nokia, Nokia Shanghai Bell CR Agreement Yes
Yes
 		revised No C3‑201525 C3‑201187
    C3‑201525 Configuration of one or more NW-TT port management information containers Ericsson, Nokia, Nokia Shanghai Bell CR Agreement Yes
Yes
 		agreed No   C3‑201436
    C3‑201188 PCF provisioning of TSN related Policy Control Request triggers Ericsson CR Agreement Yes
Yes
 		agreed No    
    C3‑201189 AF session binding to PDU session for TSN networks Ericsson CR Agreement Yes
Yes
 		agreed No    
    C3‑201190 DS-TT port MAC address as UE MAC address Ericsson CR Agreement Yes
Yes
 		agreed No    
    C3‑201191 TSCAI input container and TSN QoS container Ericsson CR Agreement Yes
YesC3-201061, C3-201065, C3-201067 and C3-201191 merged into C3-201435
 		revised No C3‑201435  
    C3‑201435 TSCAI input container and TSN QoS container Ericsson, Nokia, Nokia Shanghai Bell CR Agreement Yes
Yes
 		revised No C3‑201524 C3‑201191
    C3‑201524 TSCAI input container and TSN QoS container Ericsson, Nokia, Nokia Shanghai Bell CR Agreement Yes
Yes
 		agreed No   C3‑201435
    C3‑201192 TSCAI input container and TSN QoS container Ericsson CR Agreement Yes
Yes
 		revised No C3‑201433  
    C3‑201433 TSCAI input container and TSN QoS container Ericsson, Nokia, Nokia Shanghai Bell CR Agreement Yes
Yes
 		agreed No   C3‑201192
    C3‑201193 Notification about TSN port detection and/or port management information, AF session exists Ericsson CR Agreement Yes
YesC3-201063 and C3-201193 merged into C3-201437
 		revised No C3‑201437  
    C3‑201437 Notification about TSN port detection and/or port management information, AF session exists Ericsson, Nokia, Nokia Shanghai Bell CR Agreement Yes
Yes
 		agreed No   C3‑201193
    C3‑201194 Notification about TSN port detection, no AF session exists Ericsson CR Agreement Yes
Yes
 		revised No C3‑201438  
    C3‑201438 Notification about TSN port detection, no AF session exists Ericsson, Nokia, Nokia Shanghai Bell CR Agreement Yes
Yes
 		agreed No   C3‑201194
    C3‑201242 Definition of 5GLanParametersProvision Ericsson CR Agreement Yes
Yes
 		agreed No    
16.9 CT aspects of Enhancing Topology of SMF and UPF in 5G Networks [ETSUN] C3‑201225 DDD status for I-SMF Ericsson CR Agreement Yes
Yes
 		agreed No    
    C3‑201226 IP address pool id encoding Ericsson CR Agreement Yes
Yes
 		agreed No    
16.10 CT aspects of System enhancements for Provision of Access to Restricted Local Operator Services by Unauthenticated Ues [PARLOS]                      
16.11 CT aspects on enhancement of network slicing [eNS] C3‑201144 Call flows of NSSAA procedures ZTE CR Agreement Yes
Yes
 		revised No C3‑201442  
    C3‑201442 Call flows of NSSAA procedures ZTE CR Agreement Yes
Yes
 		revised No C3‑201490 C3‑201144
    C3‑201490 Call flows of NSSAA procedures ZTE CR Agreement Yes
Yes
 		agreed No   C3‑201442
16.12 CT aspects of Enhancement to the 5GC LoCation Services [5G_eLCS] C3‑201259 Supporting the Location services in NEF CATT/Scott CR Agreement Yes
YesFrom Huawei: 1. TS 23.273 subclause 8.5. mentions that Location reporting is one of the monitoring events supported by Nnef_EventExposure service. It seems your proposal also go forward this proposal (as shown in subclause 5.3 and proposed by C3-191261) to reuse MonitoringEvent API. But why you define a new LocationService API and in parallel reusing the current MonitoringEvent API here? The solution need to be confirmed firstly then detailed comments can be given. 2. For subclause 4.1: there is no Nnef_Location service defined in TS 23.502 or TS 23.273. In TS 23.273, Nnef_ProvideLocation and Nnef_Location_LocationUpdateNotify are described in the procedure but no definition. And if you reuse the MonitoringEvent API, the new Nnef service should be added corresponds to the procedure of Monitoring. 3. For subclause 5.3, location_notification feature is applicable to R15 SCEF/NEF MonitoringEvent API, a new feature should be defined in TS 29.122 and listed here. 4. Since the AF access LCS services from an NEF not only use N33 but also can use CAPIF API. Whether you plan to enhance the CAPIF interface in next meeting? From Ericsson: *same concern.TS 23.273 has specified a “unified location service exposure” *support re-use Nnef_eventExposure and enhance it or eLCS need. *TS 29.122 will be enhanced with new information applicable for the eLCS service and TS 29.522 will describe the procedure difference and API difference. *In additional, for MO-LR location report, it can be a standalone NEF triggered notification included in a dedicated location API in TS 29.522 (refer to NiddConfigurationTrigger API). From Vodafone: *”in 5G” should be deleted in 4.4.z.1 *question for clarification on the text Upon receipt of the corresponding HTTP POST message, if the AF is authorized by the NEF to use location service... Will the AF know in advance of sending HTTP POST whether it is authorized for location services? AT&T: 1. Subclause 4.4.z.2.2 states: “… Otherwise, the AF shall handle the location estimate according to the Service Identity, and send a HTTP response including "200 OK" status code”. If this an Ack back to a Notification and there is nothing in the response body, HTTP status code of “204 No Content” should be used. If however, you intend to return some data please specify. 2. Table 5.x.2.3.1-2: could find NotifyReply data type definition. Is the Ack back to notification going to send some data (NotifyReply) back. Otherwise, HTTP “204 No Content” can be used. 3. Subclause 4.4.z.2.3 states: “… Upon receipt of the corresponding HTTP POST message, if the AF is authorized by the NEF to use location service” OpenAPI shows that, OAuth2.0 “Client Credentials” flow is intended to be used to determine if the AF is authorized to invoke the LocationService API. If this UE is related to an end-user (smartphone; not an CIoT), then the authorization of the end-user using OAuth 2.0 “Authorization Code” flow is required to ensure the subscriber has provided the necessary authorization to the LCS client (AF) to invoke the LocationService API onto the NEF. Question: is this LocationService API (provide-location custom operation) intended to be used to also retrieve UE’s (used by people) location? 4. Related to point #3 above: I see that CR C3-201260 is intended to update LPI in UDR. I also assume that the UDR record being updated (in the context of the CR C3-201260) can be an end-user’s (person) record which requires the end-user’s consent before the AF can invoke LocationService API. If so then again, the end-user’s authorization is required through the usage of OAuth 2.0 “Authorization Code” flow as ““Client Credentials” flow is not the appropriate OAuth flow for obtaining end-user’s authorization. I appreciate it if you can shed light as to the usage of the LocationService API in Rel 16.
 		revised No C3‑201500  
    C3‑201500 Supporting the Location services in NEF CATT/Scott CR Agreement Yes
Yes
 		revised No C3‑201521 C3‑201259
    C3‑201521 Supporting the Location services in NEF CATT/Scott CR Agreement Yes
Yes
 		postponed No   C3‑201500
    C3‑201260 UE Location Privacy Setting in NEF CATT/Scott CR Agreement Yes
YesHuawei: 1. Subclause 4.4.x: a) Lack of description about the NEF action (Create individual subscription resource, interact with southbound interface, send response to the AF) after receiving HTTP POST request from the AF; b) the resource for updating procedure is incorrect, and the individual resource name is inconsistence in some subclauses 2. Table 5.y.2.3.3-1: the afId is already indicated as part of the resource URI 3. Annex A.z: change the V16.2.0 to be V16.3.0 in the externalDocs filed since next TS version is not 16.2.0 anymore Ericsson: In addition to Huawei’s comments: 4. For 5.y.2.3.3: a. afTransId is not needed, since there is no notification for this API and the HTTP naturally supports the request and response correlation. b. NOTE should be marked in the description column, not in the attribute column, for gpsi and exterGroupId attributes 5. PATCH is not needed, since LPI (indication and validity period) doesn’t include a complex data structure that can utilize the PATCH advantage. 6. In openAPI, gpsi and exterGroupId should not be listed in “required” field. 7. And copyright in openAPI can be updated to 2020. AT&T: 1. Second Ericsson’s comment that “afTransId” is not needed (e.g. in table 5.y.2.3.3-1, it should be removed) 2. table 5.y.2.3.3-1 lists afId as a Mandatory parameter and yet the request resourceURI has the {afId} also present. Having afId duplicated in the POST request (for resource creation) is unnecessary and may lead to issues such as taking care of unnecessary new error scenarios like if the two values ({afId} in the request resourceURI and afId in the POST request body are different, what should the server do?) 3. In subclause 5.y.1.1: the resources names “subscriptions” and “subscriptionId” are too generic which doesn’t say what these resources do. Also normally the above two resources are used (in other REST APIs specs in CT/CT4) for creating event-subscriptions. I suggest using some other resource names which speak to what these resources are all about… subclause 4.4.x states that these resources are about provisioning Lpis hence, how about names like. “provisionedLpis” & “{provisionedLpiId}” or something along these? 4. Related to point #2 above: I see that CR C3-201260 is intended to update LPI in UDR. I also assume that the UDR record being updated (in the context of the CR C3-201260) can be an end-user’s (person) record which requires the end-user’s consent before the AF can invoke LocationService API. If so then again, the end-user’s authorization is required through the usage of OAuth 2.0 “Authorization Code” flow as ““Client Credentials” flow is not the appropriate OAuth flow for obtaining end-user’s authorization. I appreciate it if you can shed light as to the usage of the LocationService API in Rel 16.
 		revised No C3‑201502  
    C3‑201502 UE Location Privacy Setting in NEF CATT/Scott CR Agreement Yes
Yes
 		revised No C3‑201528 C3‑201260
    C3‑201528 UE Location Privacy Setting in NEF CATT/Scott CR Agreement No
No
 		reserved No   C3‑201502
    C3‑201261 Supporting the Location services in SCEF CATT/Scott CR Agreement Yes
YesHuawei: 1. Please change the SCEF to NEF in the CR title since T8 interface does not support this new 5G functionality 2. Since location_notification has already been defined for R15 SCEF/NEF MonitoringEvent API, please not use Location_notification as the new feature name and use a new one to more precise describe the new LCS functionality, and add the new feature description in subcaluse 5.3.4. Then change the feature name for all the related attributes 3. For Table 5.3.2.1.1-1: Some data types are listed more than once, e.g. AgeOfLocationEstimate, please remove the redundant one; LdrReference is described as notification correlation Id, which is incorrect 4. Some attributes in Tables 5.3.2.1.2-1 and 5.3.2.2.2 use Capital letter as the first one, should change to be lower letter. 5. Since the interface is external interface, what’s the scenario that the SUPI can be exposed? 6. For subclause 5.3.2.1.2: not use the latest version of the TS, please change; please use a parent data type to include all the new added attributes under the new LCS functionality. The new feature also applicable to accuracy IE 7. For subclause 5.3.2.2.2: the new LCS event reporting functionality should not be added within MonitoringNotfication data but the MonitoringEventReport data; the feature should be added in applicability part for the new added Ies; the ldrReference is not the notification correlation Id and will not expose to the AF; no need to use two Ies locationEstimate and civicAddress to indicate the location of the UE but one IE which uses LocationArea5G data type Ericsson: *General 1: I see some existing attributes are not re-used for the new Location_notification_5G (I assume it will be called this way). The style you see in event monitoring table (Table 5.3.2.1.2-1 ) is that one attribute may be marked to be used for different features, so I think we should continue to follow this style. *General 2: For attribute with array, cardinality 0..N shall be used, but in openAPI it should still be clear with minItems=1. This notation is different from other TS since we don’t have presence column. *Table 5.3.2.1.2-1 - I agree that supi is NOT allowed for exposure interface, if you still have doubt we can send LS to SA2 for clarification. - pseudonymOfUE, this is a new UE identity. Please update a table note 1 for the presence condition for the new Location_notification_5G feature. - periodicEventInfo, This is already supported by existing minimumReportInterval and maximumNumberOfReports. Therefore not needed. - areaEventInfo, This is partly supported by locationArea5G, minimumReportInterval, maximumNumberOfReports, and monitorExpireTime. So try to re-use existing attribute and add missing ones. - motionEventInfo, This is partly supported by minimumReportInterval, maximumNumberOfReports, and monitorExpireTime. So try to re-use existing attribute and add missing ones. O Why lcsServiceType is needed for NEF <- AF interaction, any reference in 23.273? - Table 5.3.2.2.2-1 o locationEstimate, civicAddress and ageOfLocationEstimate, if you check existing locationInfo attribute in the report, it has ageOfLocationEstimate and GeographicaArea. We probably only need to enhance the LocationInfo data type. O positioningDataList and gnssPositioningDataList, any reference in 23.273? O eventNotifyDataType, some enum values (from UE available to MOTION in 6.1.5.3.6 of 29.515) are already indicated during event subscription and existing cancelInd attribute can be used to indicate event cancellation. For ACTIVATION_OF_DEFERRED_LOCATION and "MAXIMUM_INTERVAL_EXPIRATION_EVENT", why AF needs to know? O Gpsi and supi can be removed Propose EN: The location monitoring details in eLCS about applicable data for event configuration and report is FFS
 		revised No C3‑201520  
    C3‑201520 Supporting the Location services in SCEF CATT/Scott CR Agreement Yes
Yes
 		postponed No   C3‑201261
16.13 CT Aspects of Media Handling for RAN Delay Budget Reporting in MTSI [E2E_DELAY]                      
16.14 Cellular IoT support and evolution for the 5G System [5G_CIoT] C3‑201073 5G CIoT work and contribution plan for CT3 Qualcomm Incorporated discussion Information Yes
Yes
 		noted No    
    C3‑201095 Update of the DDD status event and availability of DDN failure event Huawei CR Agreement Yes
Yes
 		revised No C3‑201402  
    C3‑201402 Update of the DDD status event and availability of DDN failure event Huawei CR Agreement Yes
Yes
 		agreed No   C3‑201095
    C3‑201096 Update of the Availability after DDN Failure event Huawei CR Agreement Yes
Yes
 		revised No C3‑201464  
    C3‑201464 Update of the Availability after DDN Failure event Huawei CR Agreement Yes
Yes
 		agreed No   C3‑201096
    C3‑201097 Update of the Availability after DDN Failure event Huawei CR Agreement Yes
YesC3-201097 and C3-201206 merged into C3-201404
 		revised No C3‑201404  
    C3‑201404 Update of the Availability after DDN Failure event Huawei, Ericsson CR Agreement Yes
Yes
 		agreed No   C3‑201097
    C3‑201098 Update of the DDD status event Huawei CR Agreement Yes
Yes
 		revised No C3‑201405  
    C3‑201405 Update of the DDD status event Huawei CR Agreement Yes
Yes
 		agreed No   C3‑201098
    C3‑201099 Update of the DDD status event Huawei CR Agreement Yes
YesC3-201099 and C3-201206 merged into C3-201406. Huawei considerred that there are no dependencies with SA2.
 		revised No C3‑201406  
    C3‑201406 Update of the DDD status event Huawei, Ericsson CR Agreement Yes
Yes
 		agreed No   C3‑201099
    C3‑201203 Clarify empty array for API capability change Ericsson CR Agreement Yes
Yes
 		agreed No    
    C3‑201204 Correct TS number for NEF southbound NIDD service Ericsson CR Agreement Yes
Yes
 		agreed No    
    C3‑201205 Support PDU session establishment event Ericsson CR Agreement Yes
Yes
 		agreed No    
    C3‑201206 Remove DDN failure event Ericsson CR Agreement Yes
YesC3-201097 and C3-201206 merged into C3-201404 C3-201099 and C3-201206 merged into C3-201406
 		merged No    
    C3‑201207 Resolve editor note for PLMN rate control Ericsson CR Agreement Yes
Yes
 		agreed No    
    C3‑201208 Support PDU session status Ericsson CR Agreement Yes
Yes
 		agreed No    
    C3‑201209 Support PDU session status Ericsson CR Agreement Yes
Yes
 		agreed No    
    C3‑201210 V-SMF applicable event Ericsson CR Agreement Yes
Yes
 		agreed No    
    C3‑201211 Additional PDU session status data Ericsson CR Agreement Yes
Yes
 		agreed No    
    C3‑201284 Reference point between NEF and I-NEF Huawei pCR Approval Yes
Yes
 		agreed No    
    C3‑201285 Events supported by I-NEF Event Exposure during notification procedure Huawei pCR Approval Yes
Yes
 		revised No C3‑201407  
    C3‑201407 Events supported by I-NEF Event Exposure during notification procedure Huawei pCR Approval Yes
Yes
 		agreed No   C3‑201285
    C3‑201286 NEF Event Filter associated with all events Huawei pCR Approval Yes
Yes
 		revised No C3‑201408  
    C3‑201408 NEF Event Filter associated with all events Huawei pCR Approval Yes
Yes
 		revised No C3‑201516 C3‑201286
    C3‑201516 NEF Event Filter associated with all events Huawei pCR Approval Yes
Yes
 		agreed No   C3‑201408
    C3‑201287 API enhancement to support I-NEF Event Exposure Huawei pCR Approval Yes
Yes
 		revised No C3‑201409  
    C3‑201409 API enhancement to support I-NEF Event Exposure Huawei pCR Approval Yes
Yes
 		agreed No   C3‑201287
    C3‑201476 Presentation sheet for TS 29.591 Huawei TS or TR cover Agreement No
No
 		reserved No    
    C3‑201481 TS 29.591 v0.4.0 Huawei draft TS Agreement No
No
 		reserved No    
16.15 CT aspects on wireless and wireline convergence for the 5G system architecture [5WWC] C3‑201100 Complete the IPTV support Huawei CR Agreement Yes
Yes
 		revised No C3‑201353  
    C3‑201353 Complete the IPTV support Huawei CR Agreement Yes
Yes
 		agreed No   C3‑201100
    C3‑201101 Policy Control Request Triggers for wireline access Huawei CR Agreement Yes
Yes
 		revised No C3‑201354  
    C3‑201354 Policy Control Request Triggers for wireline access Huawei CR Agreement Yes
Yes
 		agreed No   C3‑201101
    C3‑201102 The data type of GlobalLineId Huawei CR Agreement Yes
Yes
 		revised No C3‑201458  
    C3‑201458 The data type of GlobalLineId Huawei CR Agreement Yes
Yes
 		agreed No   C3‑201102
    C3‑201103 Policy Control Request Triggers for wireline access Huawei CR Agreement Yes
Yes
 		revised No C3‑201355  
    C3‑201355 Policy Control Request Triggers for wireline access Huawei CR Agreement Yes
Yes
 		agreed No   C3‑201103
    C3‑201104 The data type of GlobalLineId Huawei CR Agreement Yes
Yes
 		revised No C3‑201459  
    C3‑201459 The data type of GlobalLineId Huawei CR Agreement Yes
Yes
 		agreed No   C3‑201104
    C3‑201105 Complete the procedure for WWC Huawei CR Agreement No
Yes
 		withdrawn Yes    
    C3‑201106 Complete the IPTV configuration Huawei CR Agreement Yes
Yes
 		revised No C3‑201335  
    C3‑201335 Complete the IPTV configuration Huawei CR Agreement Yes
Yes
 		agreed No   C3‑201106
    C3‑201136 Clarification of IPTV configuration Huawei CR Agreement Yes
Yes
 		revised No C3‑201336  
    C3‑201336 Clarification of IPTV configuration Huawei CR Agreement Yes
Yes
 		agreed No   C3‑201136
    C3‑201138 Complete the procedure for WWC Huawei Technologies R&D UK CR Agreement Yes
Yes
 		revised No C3‑201356  
    C3‑201356 Complete the procedure for WWC Huawei Technologies R&D UK CR Agreement Yes
Yes
 		agreed No   C3‑201138
    C3‑201202 Correct content type in PATCHing IPTV application data Ericsson CR Agreement Yes
Yes
 		agreed No    
    C3‑201243 Definition of IptvConfigData Ericsson CR Agreement Yes
Yes
 		agreed No    
16.16 Volume Based Charging Aspects for VoLTE [VBCLTE]                      
16.17 CT aspects of optimisations on UE radio capability signalling [RACS] C3‑201070 RACS CT work plan Qualcomm Incorporated discussion Information Yes
Yes
 		noted No    
    C3‑201197 Pseudo-CR on resolving editor note for GET Ericsson pCR Approval Yes
Yes
 		revised No C3‑201420  
    C3‑201420 Pseudo-CR on resolving editor note for GET Ericsson pCR Approval Yes
Yes
 		agreed No   C3‑201197
    C3‑201479 Presentation sheet for TS 29.675 Ericsson TS or TR cover Agreement No
No
 		reserved No    
    C3‑201484 TS 29.675 v1.1.0 Ericsson draft TS Agreement No
No
 		reserved No    
16.18 Service Based Interface Protocol Enhancement [SBIProtoc16] C3‑201244 OpenAPI: usage of the "tags" keyword Ericsson CR Agreement Yes
Yes
 		agreed No    
    C3‑201245 OpenAPI: usage of the "tags" keyword Ericsson CR Agreement Yes
Yes
 		agreed No    
    C3‑201246 OpenAPI: usage of the "tags" keyword Ericsson CR Agreement Yes
Yes
 		agreed No    
    C3‑201247 Enumeration PreemptionControlInformationRm and "nullable" keyword Ericsson CR Agreement Yes
Yes
 		agreed No    
    C3‑201248 Enumerations and "nullable" keyword Ericsson CR Agreement Yes
Yes
 		agreed No    
16.19 CT aspects of eV2XARC [eV2XARC] C3‑201107 Binding mechanism update for V2X Huawei CR Agreement Yes
Yes
 		revised No C3‑201461  
    C3‑201461 Binding mechanism update for V2X Huawei CR Agreement Yes
Yes
 		agreed No   C3‑201107
    C3‑201108 Complete the PCC procedure for V2XARC Huawei CR Agreement Yes
YesC3-201108 and C3-201316 merged into C3-201374
 		revised No C3‑201374  
    C3‑201374 Complete the PCC procedure for V2XARC Huawei, Ericsson CR Agreement Yes
Yes
 		agreed No   C3‑201108
    C3‑201109 Complete the PCC procedure for V2XARC Huawei CR Agreement Yes
YesC3-201109 and C3-201317 merged into C3-201375.
 		merged No    
    C3‑201110 Nnef_AFsessionWithQoS service update to support V2X Huawei CR Agreement Yes
YesC3-201110 and C3-201228 merged into C3-201410
 		merged No    
    C3‑201111 Nnef_AFsessionWithQoS service update to support V2X Huawei CR Agreement Yes
YesC3-201111, C3-201274 and C3-201227 merged into C3-201411
 		merged No    
    C3‑201112 Procedure of Nnef_ServiceParameter service Huawei CR Agreement Yes
Yes
 		revised No C3‑201467  
    C3‑201467 Procedure of Nnef_ServiceParameter service Huawei CR Agreement Yes
Yes
 		agreed No   C3‑201112
    C3‑201113 Resources and data types of Nnef_ServiceParameter service Huawei CR Agreement Yes
Yes
 		revised No C3‑201468  
    C3‑201468 Resources and data types of Nnef_ServiceParameter service Huawei CR Agreement Yes
Yes
 		agreed No   C3‑201113
    C3‑201114 OpenAPI file of Nnef_ServiceParameter service Huawei CR Agreement Yes
Yes
 		revised No C3‑201469  
    C3‑201469 OpenAPI file of Nnef_ServiceParameter service Huawei CR Agreement Yes
Yes
 		revised No C3‑201526 C3‑201114
    C3‑201526 OpenAPI file of Nnef_ServiceParameter service Huawei CR Agreement Yes
Yes
 		agreed No   C3‑201469
    C3‑201115 Nudr_DataRepository API update for Service Parameter provisioning Huawei CR Agreement Yes
Yes
 		revised No C3‑201470  
    C3‑201470 Nudr_DataRepository API update for Service Parameter provisioning Huawei CR Agreement Yes
Yes
 		agreed No   C3‑201115
    C3‑201116 Network function enhancement for V2X communication Huawei CR Agreement Yes
YesHuawei: check the status in CT1 that UE policies for V2X communication over Uu are part of URSP.
 		revised No C3‑201462  
    C3‑201462 Network function enhancement for V2X communication Huawei CR Agreement Yes
Yes
 		agreed No   C3‑201116
    C3‑201117 UE Policy for V2XARC Huawei CR Agreement Yes
Yes
 		revised No C3‑201376  
    C3‑201376 UE Policy for V2XARC Huawei CR Agreement Yes
Yes
 		agreed No   C3‑201117
    C3‑201118 N2 PC5 Policy for V2XARC Huawei CR Agreement Yes
Yes
 		revised No C3‑201377  
    C3‑201377 N2 PC5 Policy for V2XARC Huawei CR Agreement Yes
Yes
 		agreed No   C3‑201118
    C3‑201151 QoS parameter mapping at PCF update for V2X Huawei Technologies R&D UK CR Agreement Yes
Yes
 		revised No C3‑201463  
    C3‑201463 QoS parameter mapping at PCF update for V2X Huawei Technologies R&D UK CR Agreement Yes
Yes
 		agreed No   C3‑201151
    C3‑201152 QoS parameter mapping at SMF update for V2X Huawei Technologies R&D UK CR Agreement Yes
Yes
 		revised No C3‑201412  
    C3‑201412 QoS parameter mapping at SMF update for V2X Huawei Technologies R&D UK CR Agreement Yes
Yes
 		agreed No   C3‑201152
    C3‑201227 Add alternative QoS requirements Ericsson CR Agreement Yes
YesC3-201111, C3-201274 and C3-201227 merged into C3-201411 part of C3-201122 will merged with C3-201227
 		revised No C3‑201411  
    C3‑201411 Add alternative QoS requirements Ericsson, Huawei, Samsung Electronics France SA CR Agreement Yes
Yes
 		agreed No   C3‑201227
    C3‑201228 Add alternative QoS requirements Ericsson CR Agreement Yes
YesC3-201110 and C3-201228 merged into C3-201410
 		revised No C3‑201410  
    C3‑201410 Add alternative QoS requirements Ericsson, Huawei CR Agreement Yes
Yes
 		agreed No   C3‑201228
    C3‑201229 Support QoS sustainability analytics Ericsson CR Agreement Yes
YesHuawei considers that this CR impacts eNA
 		revised No C3‑201471  
    C3‑201471 Support QoS sustainability analytics Ericsson CR Agreement Yes
Yes
 		agreed No   C3‑201229
    C3‑201233 Modification of Alternative Service Requirements Ericsson CR Agreement Yes
Yes
 		agreed No    
    C3‑201234 Service Procedures for AF session with required QoS functionality Ericsson CR Agreement Yes
Yes
 		agreed No    
    C3‑201274 V2X – AS Session with alternate service requirements Samsung Electronics France SA CR Agreement Yes
YesC3-201111, C3-201274 and C3-201227 merged into C3-201411
 		merged No    
    C3‑201316 Correction to QoS notification Control Ericsson CR Agreement Yes
YesC3-201108 and C3-201316 merged into C3-201374
 		merged No    
    C3‑201317 Correction to QoS notification Control Ericsson CR Agreement Yes
YesC3-201109 and C3-201317 merged into C3-201375
 		revised No C3‑201375  
    C3‑201375 Correction to QoS notification Control Ericsson, Huawei CR Agreement Yes
Yes
 		agreed No   C3‑201317
16.20 CT aspects of 5G URLLC [5G_URLLC] C3‑201119 Complete the QoS Monitoring Huawei CR Agreement Yes
Yes
 		revised No C3‑201372  
    C3‑201372 Complete the QoS Monitoring Huawei CR Agreement Yes
Yes
 		agreed No   C3‑201119
    C3‑201120 Complete the QoS Monitoring Huawei CR Agreement Yes
Yes
 		revised No C3‑201373  
    C3‑201373 Complete the QoS Monitoring Huawei CR Agreement Yes
Yes
 		revised No C3‑201522 C3‑201120
    C3‑201522 Complete the QoS Monitoring Huawei CR Agreement Yes
Yes
 		agreed No   C3‑201373
    C3‑201121 QoS Monitoring Report Huawei CR Agreement Yes
Yes
 		revised No C3‑201472  
    C3‑201472 QoS Monitoring Report Huawei CR Agreement Yes
Yes
 		agreed No   C3‑201121
    C3‑201122 QoS Monitoring Report Huawei CR Agreement Yes
Yes
 		revised No C3‑201473  
    C3‑201473 QoS Monitoring Report Huawei CR Agreement Yes
Yes
 		agreed No   C3‑201122
    C3‑201123 QoS Monitoring Report Huawei CR Agreement Yes
Yes
 		revised No C3‑201474  
    C3‑201474 QoS Monitoring Report Huawei CR Agreement Yes
Yes
 		agreed No   C3‑201123
    C3‑201249 Correcting 5G_URLLC errors in clause 5.6 Ericsson CR Agreement Yes
Yes
 		agreed No    
16.21 Enhancement of 3GPP Northbound APIs [eNAPIs] C3‑201304 Event of Usage Threshold Huawei CR Agreement Yes
Yes
 		postponed No    
    C3‑201318 Enumeration PdnEstablishmentOptionsRm and "nullable" keyword Ericsson CR Agreement Yes
Yes
 		agreed No    
16.22 CT Aspects of 5GS Transfer of Policies for Background Data [xBDT] C3‑201145 map ASPid to DNN and SNSSAI for xBDT ZTE CR Agreement Yes
Yes
 		revised No C3‑201417  
    C3‑201417 map ASPid to DNN and SNSSAI for xBDT ZTE CR Agreement Yes
Yes
 		revised No C3‑201491 C3‑201145
    C3‑201491 map ASPid to DNN and SNSSAI for xBDT ZTE CR Agreement Yes
Yes
 		agreed No   C3‑201417
    C3‑201146 Correct the mapping of ASPid for xBDT ZTE CR Agreement Yes
Yes
 		revised No C3‑201418  
    C3‑201418 Correct the mapping of ASPid for xBDT ZTE CR Agreement Yes
Yes
 		revised No C3‑201492 C3‑201146
    C3‑201492 Correct the mapping of ASPid for xBDT ZTE CR Agreement Yes
Yes
 		agreed No   C3‑201418
    C3‑201231 Correct content type in PATCHing BDT application data Ericsson CR Agreement Yes
Yes
 		agreed No    
    C3‑201250 Removal of the BDT policy from the "bdtRefIds" object Ericsson CR Agreement Yes
Yes
 		agreed No    
    C3‑201251 Adding data type for the BDT Reference ID with "nullable: true" property Ericsson CR Agreement Yes
Yes
 		revised No C3‑201517  
    C3‑201517 Adding data type for the BDT Reference ID with "nullable: true" property Ericsson CR Agreement Yes
Yes
 		agreed No   C3‑201251
    C3‑201252 Usage of the "bdtRefId" property Ericsson CR Agreement Yes
Yes
 		agreed No    
    C3‑201253 Applying UE Policy Association Modification to all affected Ues Ericsson CR Agreement Yes
Yes
 		agreed No    
16.23 Mobile Communication System for Railways (MONASTERY) [MONASTERY2]                      
16.24 CT aspects of SBA interactions between IMS and 5GC [eIMS5G_SBA] C3‑201153 Network provided location information at SIP session release Nokia, Nokia Shanghai Bell CR Agreement Yes
Yes
 		revised No C3‑201416  
    C3‑201416 Network provided location information at SIP session release Nokia, Nokia Shanghai Bell CR Agreement Yes
Yes
 		agreed No   C3‑201153
    C3‑201170 Annex B, IMS Session Establishment Ericsson CR Agreement Yes
YesC3-201170, C3-201308 and C3-201309 merged into C3-201443. Ericsson commented that check if EPS fallback is needed.
 		revised No C3‑201443  
    C3‑201443 Annex B, IMS Session Establishment Ericsson, Huawei CR Agreement Yes
Yes
 		agreed No   C3‑201170
    C3‑201171 Annex B, IMS Session Modification, provisioning of service information Ericsson CR Agreement Yes
Yes
 		revised No C3‑201444  
    C3‑201444 Annex B, IMS Session Modification, provisioning of service information Ericsson CR Agreement Yes
Yes
 		agreed No   C3‑201171
    C3‑201172 Annex B, IMS Session Modification, gate control Ericsson CR Agreement Yes
Yes
 		revised No C3‑201445  
    C3‑201445 Annex B, IMS Session Modification, gate control Ericsson CR Agreement Yes
Yes
 		agreed No   C3‑201172
    C3‑201173 Annex B, IMS Session Modification, media component removal Ericsson CR Agreement Yes
Yes
 		revised No C3‑201446  
    C3‑201446 Annex B, IMS Session Modification, media component removal Ericsson CR Agreement Yes
Yes
 		agreed No   C3‑201173
    C3‑201174 Annex B, IMS Session Termination Ericsson CR Agreement Yes
YesC3-201174, C3-201310 and C3-201311 merged into C3-201447
 		revised No C3‑201447  
    C3‑201447 Annex B, IMS Session Termination Ericsson, Huawei CR Agreement Yes
Yes
 		agreed No   C3‑201174
    C3‑201175 Annex B, Provisioning of SIP signalling flow information at IMS Registration Ericsson CR Agreement Yes
YesC3-201175 and C3-201313 merged into C3-201448
 		revised No C3‑201448  
    C3‑201448 Annex B, Provisioning of SIP signalling flow information at IMS Registration Ericsson, Huawei CR Agreement Yes
Yes
 		agreed No   C3‑201175
    C3‑201176 Annex B, Subscription to Notification of Change of Access Type Ericsson CR Agreement Yes
YesC3-201176 and C3-201314 merged into C3-201449
 		revised No C3‑201449  
    C3‑201449 Annex B, Subscription to Notification of Change of Access Type Ericsson, Huawei CR Agreement Yes
Yes
 		agreed No   C3‑201176
    C3‑201177 Annex B, Subscription to Notification of Change of PLMN Identifier Ericsson CR Agreement Yes
YesC3-201177 and C3-201315 merged into C3-201451
 		merged No    
    C3‑201178 Annex B, Subscription to notification of signalling path status at IMS Registration Ericsson CR Agreement Yes
YesC3-201178 and C3-201312 merged into C3-201450
 		merged No    
    C3‑201179 Annex B, P-CSCF Restoration Ericsson CR Agreement Yes
Yes
 		agreed No    
    C3‑201254 OpenAPI: property containing the pre-emption control information Ericsson CR Agreement Yes
Yes
 		agreed No    
    C3‑201255 Correcting eIMS5G_SBA errors in clause 5.6 Ericsson CR Agreement Yes
Yes
 		agreed No    
    C3‑201308 Provisioning of service information at Originating P-CSCF and PCF Huawei CR Agreement Yes
YesC3-201170, C3-201308 and C3-201309 merged into C3-201443
 		merged No    
    C3‑201309 Provisioning of service information at terminating P-CSCF and PCF Huawei CR Agreement Yes
YesC3-201170, C3-201308 and C3-201309 merged into C3-201443
 		merged No    
    C3‑201310 Mobile initiated session release / Network initiated session release Huawei CR Agreement Yes
YesC3-201174, C3-201310 and C3-201311 merged into C3-201447
 		merged No    
    C3‑201311 QoS Flow Release/Loss Huawei CR Agreement Yes
YesC3-201174, C3-201310 and C3-201311 merged into C3-201447
 		merged No    
    C3‑201312 Subscription to Notification of Signalling Path Status at IMS Registration Huawei CR Agreement Yes
YesC3-201178 and C3-201312 merged into C3-201450
 		revised No C3‑201450  
    C3‑201450 Subscription to Notification of Signalling Path Status at IMS Registration Huawei, Ericsson CR Agreement Yes
Yes
 		agreed No   C3‑201312
    C3‑201313 Provisioning of SIP signalling flow information at IMS Registration Huawei CR Agreement Yes
YesC3-201175 and C3-201313 merged into C3-201448
 		merged No    
    C3‑201314 Subscription to Notification of Change of Access Type at IMS Registration Huawei CR Agreement Yes
YesC3-201176 and C3-201314 merged into C3-201449
 		merged No    
    C3‑201315 Subscription to Notification of Change of PLMN Identifier at IMS Registration Huawei CR Agreement Yes
YesC3-201177 and C3-201315 merged into C3-201451
 		revised No C3‑201451  
    C3‑201451 Subscription to Notification of Change of PLMN Identifier at IMS Registration Huawei, Ericsson CR Agreement Yes
Yes
 		agreed No   C3‑201315
    C3‑201319 Report of EPS Fallback Ericsson CR Agreement No
Yes
 		withdrawn Yes    
    C3‑201320 Report of EPS Fallback Ericsson CR Agreement No
Yes
 		withdrawn Yes    
    C3‑201321 Report of EPS Fallback Ericsson CR Agreement No
Yes
 		withdrawn Yes    
    C3‑201322 Annex B, IMS Session Establishment Ericsson CR Agreement No
Yes
 		withdrawn Yes    
    C3‑201323 Annex B, IMS Session Modification, provisioning of service information Ericsson CR Agreement No
Yes
 		withdrawn Yes    
    C3‑201324 Annex B, IMS Restricted Local Operator Services Ericsson CR Agreement Yes
Yes
 		agreed No    
16.25 CT aspects of application layer support for V2X services[V2XAPP] C3‑201124 Complete the VAE_MessageDelivery API Huawei pCR Approval Yes
Yes
 		revised No C3‑201341  
    C3‑201341 Complete the VAE_MessageDelivery API Huawei pCR Approval Yes
Yes
 		agreed No   C3‑201124
    C3‑201125 Complete the VAE_FileDistribution API Huawei pCR Approval Yes
Yes
 		revised No C3‑201342  
    C3‑201342 Complete the VAE_FileDistribution API Huawei pCR Approval Yes
Yes
 		agreed No   C3‑201125
    C3‑201126 Complete the VAE_ApplicationRequirement API API Huawei pCR Approval Yes
Yes
 		revised No C3‑201343  
    C3‑201343 Complete the VAE_ApplicationRequirement API API Huawei pCR Approval Yes
Yes
 		agreed No   C3‑201126
    C3‑201127 VAE_DynamicGroup service Huawei pCR Approval Yes
Yes
 		revised No C3‑201344  
    C3‑201344 VAE_DynamicGroup service Huawei pCR Approval Yes
Yes
 		agreed No   C3‑201127
    C3‑201128 VAE_DynamicGroup OpenAPI Huawei pCR Approval Yes
Yes
 		revised No C3‑201345  
    C3‑201345 VAE_DynamicGroup OpenAPI Huawei pCR Approval Yes
Yes
 		agreed No   C3‑201128
    C3‑201129 Cleanup of 29.486 Huawei pCR Approval Yes
Yes
 		revised No C3‑201453  
    C3‑201453 Cleanup of 29.486 Huawei pCR Approval Yes
Yes
 		agreed No   C3‑201129
    C3‑201200 Pseudo-CR on Add security text Ericsson pCR Approval Yes
Yes
 		revised No C3‑201454  
    C3‑201454 Pseudo-CR on Add security text Ericsson pCR Approval Yes
Yes
 		agreed No   C3‑201200
    C3‑201201 Pseudo-CR on Add VAE service continuity API Ericsson pCR Approval Yes
Yes
 		revised No C3‑201455  
    C3‑201455 Pseudo-CR on Add VAE service continuity API Ericsson pCR Approval Yes
Yes
 		agreed No   C3‑201201
    C3‑201475 Presentation sheet for TS 29.486 Huawei TS or TR cover Agreement No
No
 		reserved No    
    C3‑201480 TS 29.486 v0.4.0 Huawei draft TS Agreement No
No
 		reserved No    
16.26 xMB extension for mission critical services [MC_XMB-CT] C3‑201230 Correct opeAPI error in Mission critical extension section Ericsson CR Agreement Yes
Yes
 		revised No C3‑201441  
    C3‑201441 Correct opeAPI error in Mission critical extension section Ericsson CR Agreement Yes
Yes
 		agreed No   C3‑201230
16.27 CT aspects of enhancements for Common API Framework for 3GPP Northbound APIs [eCAPIF] C3‑201212 Published API path Ericsson CR Agreement Yes
Yes
 		revised No C3‑201401  
    C3‑201401 Published API path Ericsson CR Agreement Yes
Yes
 		agreed No   C3‑201212
    C3‑201272 API Invoker Udpate – Event Updates Samsung Electronics France SA CR Agreement Yes
Yes
 		agreed No    
    C3‑201273 API Provider Management – Open API Samsung Electronics France SA CR Agreement Yes
Yes
 		revised No C3‑201403  
    C3‑201403 API Provider Management – Open API Samsung Electronics France SA CR Agreement Yes
Yes
 		revised No C3‑201523 C3‑201273
    C3‑201523 API Provider Management – Open API Samsung Electronics France SA CR Agreement Yes
Yes
 		agreed No   C3‑201403
16.28 CT aspects of Service Enabler Architecture Layer for Verticals [SEAL] C3‑201198 Pseudo-CR on multicast NRM support Ericsson pCR Approval Yes
Yes
 		revised No C3‑201346  
    C3‑201346 Pseudo-CR on multicast NRM support Ericsson pCR Approval Yes
Yes
 		agreed No   C3‑201198
    C3‑201262 Pseudo-CR on SEAL – Configuration Management API Samsung Electronics France SA pCR Approval Yes
Yes
 		revised No C3‑201347  
    C3‑201347 Pseudo-CR on SEAL – Configuration Management API Samsung Electronics France SA pCR Approval Yes
Yes
 		agreed No   C3‑201262
    C3‑201263 Pseudo-CR on SEAL - Configuration Management Event Samsung Electronics France SA pCR Approval Yes
Yes
 		revised No C3‑201348  
    C3‑201348 Pseudo-CR on SEAL - Configuration Management Event Samsung Electronics France SA pCR Approval Yes
Yes
 		agreed No   C3‑201263
    C3‑201264 Pseudo-CR on SEAL - Configuration Management Editor’s Note Samsung Electronics France SA pCR Approval Yes
YesEriccson commented that no claear stage 2 requirments, check what to use as resource id.
 		postponed No    
    C3‑201265 Pseudo-CR on SEAL - Group Management Delete Samsung Electronics France SA pCR Approval Yes
Yes
 		revised No C3‑201349  
    C3‑201349 Pseudo-CR on SEAL - Group Management Delete Samsung Electronics France SA pCR Approval Yes
Yes
 		agreed No   C3‑201265
    C3‑201266 Pseudo-CR on SEAL - Group Management Event Samsung Electronics France SA pCR Approval Yes
Yes
 		revised No C3‑201350  
    C3‑201350 Pseudo-CR on SEAL - Group Management Event Samsung Electronics France SA pCR Approval Yes
Yes
 		agreed No   C3‑201266
    C3‑201267 Pseudo-CR on SEAL - Group Management API Samsung Electronics France SA pCR Approval Yes
Yes
 		revised No C3‑201456  
    C3‑201456 Pseudo-CR on SEAL - Group Management API Samsung Electronics France SA pCR Approval Yes
Yes
 		agreed No   C3‑201267
    C3‑201268 Pseudo-CR on SEAL - Group Management Editor Notes Samsung Electronics France SA pCR Approval Yes
Yes
 		revised No C3‑201457  
    C3‑201457 Pseudo-CR on SEAL - Group Management Editor Notes Samsung Electronics France SA pCR Approval Yes
YesSamsung considerred that need a new LS to SA6 related with this CR.
 		agreed No   C3‑201268
    C3‑201269 Pseudo-CR on SEAL Events API Definition Samsung Electronics France SA pCR Approval Yes
Yes
 		revised No C3‑201351  
    C3‑201351 Pseudo-CR on SEAL Events API Definition Samsung Electronics France SA pCR Approval Yes
Yes
 		agreed No   C3‑201269
    C3‑201270 Pseudo-CR on SEAL Events Service Definition Samsung Electronics France SA pCR Approval Yes
Yes
 		revised No C3‑201352  
    C3‑201352 Pseudo-CR on SEAL Events Service Definition Samsung Electronics France SA pCR Approval Yes
Yes
 		agreed No   C3‑201270
    C3‑201271 Pseudo-CR on SEAL – Common Design Aspects Samsung Electronics France SA pCR Approval Yes
Yes
 		agreed No    
    C3‑201478 Presentation sheet for TS 29.549 Samsung TS or TR cover Agreement No
Yes
 		withdrawn Yes    
    C3‑201483 TS 29.549 v1.1.0 Samsung draft TS Agreement No
Yes
 		withdrawn Yes    
16.29 Load and Overload Control of 5GC Service Based Interfaces [LOCL]                      
16.30 CT aspect of single radio voice continuity from 5GS to 3G [5G_SRVCC] C3‑201184 Update of the indication of PS to CS Handover Ericsson CR Agreement Yes
YesHuawei considers this new requirement and prefer to define a separate indication of PS to CS indication and together with ALL_SDF_DEACTIVATION or PDU_SESSION_TERMINATION termination cause.
 		revised No C3‑201360  
    C3‑201360 Update of the indication of PS to CS Handover Ericsson CR Agreement Yes
Yes
 		agreed No   C3‑201184
    C3‑201195 5GSRVCC impacts on Rx ZTE, China Unicom CR Agreement Yes
Yes
 		revised No C3‑201361  
    C3‑201361 5GSRVCC impacts on Rx ZTE, China Unicom CR Agreement Yes
Yes
 		revised No C3‑201493 C3‑201195
    C3‑201493 5GSRVCC impacts on Rx ZTE, China Unicom CR Agreement Yes
Yes
 		agreed No   C3‑201361
    C3‑201196 SRVCC impacts on QoS mapping ZTE, China Unicom CR Agreement Yes
Yes
 		agreed No    
16.31 Technical Enhancements and Improvements [TEI16] C3‑201041 Incorrect figure 5.2.3.1-1: SMF-initiated SM Policy Association Termination procedure Cisco Systems Belgium CR Agreement Yes
Yes
 		revised No C3‑201363  
    C3‑201363 Incorrect figure 5.2.3.1-1: SMF-initiated SM Policy Association Termination procedure Cisco Systems Belgium, Ericsson CR Agreement Yes
Yes
 		agreed No   C3‑201041
16.31.1 TEI16 for IMS/CS C3‑201305 Clarification of the scope NTT corporation CR Agreement Yes
YesVodafone: The new text below could be understood to suggest that an IBCF fault management capability exists (and maybe other capabilities where the IBCF initiates requests) but, as the cover sheet says, such a feature is not currently defined in 24.229. I don't think we should list things that entities don't do without a good justification. Standalone SIP requests initiated from IBCF (e.g. fault management OPTIONS request) is not considered in the present release of this specification. Also a wording comment. 24.229 uses "SIP standalone transactions", which seems more accurate to me since the SIP signalling has a request and response(s) even if it does not set up a dialog, and it is defined in TS 23.218: Standalone Transaction: a SIP transaction that is not part of an existing dialog and does not initiate the creation of a new dialog. NTT: Current IBCF implementations possibly send SIP requests for stand-alone transaction (like OPTIONS pinging) to a neighbor entity. However, 3GPP IMS specifications (TS 22.173, TS 23.228 and TS 24.229) do not specify the behavior that IBCF generates the request for stand-alone transaction. Of course, there are no signaling requirement for such requests. Then, we propose to clarify that "Stand-alone transaction between the two IBCFs over the II-NNI (e.g. fault management OPTIONS request) is not within the scope of TS 29.165". We agree with your proposal to clarify the wording. We'll provide the revision of C3-201305 before teleconference tomorrow. Ericsson: support of standalone SIP requests e.g. OPTIONS is covered by TS 24.229 (see 5.10.1, annex A e.g. for OPTIONS) and by TS 29.165 (see table C.3.3.8, clauses 8.1, 18.3.1, annex B tables e.g. for MESSAGE, OPTIONS, PUBLISH, REFER, REGISTER methods), so we have problem with the added text. Further it is not clear: Who sends standalone SIP requests? Who is the recipient of the standalone SIP requests? How does the receiving IBCF know that the standalone SIP request e.g. OPTIONS was generated by the sending IBCF (if that is the case)? You modified clause 5.1, but CR cover page indicates clause 1. NTT: our intention is to clarify that such a stand-alone request generated/populated by IBCF is not covered in TS 29.165. Because the behavior is not specified in the IMS service requirements and procedures. Answers to Ericsson questions are: 1. We intended the case that an "IBCF" generating stand-alone request like OPTIONS request. 2. An IBCF acting as the entry point of the network. (The R-URI is FQDN/IP address of the IBCF)) 3. If the IBCF generates a stand-alone request, the IBCF can't include a P-Asserted-Identity header field, because there is no procedures to generate a stand-alone request. When the UE generates OPTIONS request, the OPTIONS request must include a P-Asserted-Identity header field. Vodafone: Where is the fault management OPTIONS feature is defined? Could not find it in 24.229, as the cover sheet also seems to indicate. We need to understand the consequence "inter operability problem caused by misunderstanding of the specification can be occurred between operators" before we add text to 29.165. NTT: TS 29.165 is specified based on the IMS specifications (TS 22.173, TS 23.228 and TS 24.229), so the fault management OPTIONS request is outside of the scope in TS 29.165. so that would like to clarify the scope not to misunderstand that such the fault management OPTIONS is compliant to TS 29.165 Vodafone proposes a text as starting point. NTT made a revision available: - Modified the cover page based on Peter's comments. - Added definition and reference for "standalone transaction". - Modified the negative wording (is not) to positive wording (is). We are proposing normative text now, however I think the text could be NOTE. If we should, we also add the note into the option item table for OPTIONS method in Annex C. Vodafone: The proposed change seems to guard against only one specific interoperability issue (standalone OPTIONS), what if someone comes next meeting proposing to add text that he IBCF does not originate SUBSCRIBE requests? NTT modifies the description in a NOTE. Vodafone changes the wording of the proposed NOTE. NTT accepts the comments.
 		revised No C3‑201452  
    C3‑201452 Clarification of the scope NTT corporation CR Agreement Yes
Yes
 		revised No C3‑201501 C3‑201305
    C3‑201501 Clarification of the scope NTT corporation CR Agreement Yes
Yes
 		agreed No   C3‑201452
16.31.2 TEI16 for Packet Core C3‑201046 Support of QCI values for Framework for Live Uplink Streaming (FLUS) Ericsson CR Agreement Yes
Yes
 		agreed No    
    C3‑201047 Support of Framework for Live Uplink Streaming (FLUS) in Rx interface Ericsson CR Agreement Yes
Yes
 		revised No C3‑201362  
    C3‑201362 Support of Framework for Live Uplink Streaming (FLUS) in Rx interface Ericsson CR Agreement Yes
Yes
 		agreed No   C3‑201047
    C3‑201048 Impacts on QoS mapping to support FLUS functionality Ericsson CR Agreement Yes
Yes
 		agreed No    
    C3‑201049 Support of Framework for Live Uplink Streaming (FLUS) in Npcf_PolicyAuthorization service Ericsson CR Agreement Yes
Yes
 		agreed No    
    C3‑201050 Impacts on QoS mapping to support FLUS functionality Ericsson CR Agreement Yes
Yes
 		agreed No    
    C3‑201051 LS Reply on QoS mapping procedure for FLUS Ericsson LS out Approval Yes
Yes
 		revised No C3‑201460  
    C3‑201460 LS Reply on QoS mapping procedure for FLUS Ericsson LS out Approval Yes
Yes
 		approved No   C3‑201051
    C3‑201052 LS on new AVPs in TS 29.214 Ericsson LS out Approval Yes
YesCT3 agreed that this LS will be sent to CT4 on Monday 24th Feb. if no comments.
 		approved No    
    C3‑201199 Correct xMB adaptation for CAPIF Ericsson CR Agreement Yes
Yes
 		agreed No    
    C3‑201256 Referencing enumerations in clause 5.6.1 Ericsson CR Agreement Yes
Yes
 		agreed No    
    C3‑201257 Adding info about removable attributes "maxPacketLossRateDl" and "maxPacketLossRateUl" Ericsson CR Agreement Yes
Yes
 		agreed No    
    C3‑201258 Miscellaneous errors Ericsson CR Agreement Yes
Yes
 		agreed No    
    C3‑201302 Correction on PcfBinding Huawei CR Agreement Yes
Yes
 		withdrawn Yes    
    C3‑201303 Reference of error code Huawei CR Agreement Yes
Yes
 		agreed No    
    C3‑201371 Correction on PcfBinding Huawei CR Agreement Yes
Yes
 		agreed No    
16.32 OpenAPI version updates C3‑201503 29.521 Rel-16 Update of OpenAPI version and TS version in externalDocs field China Mobile Communications Group Co.,Ltd CR Agreement No
No
 		reserved No    
    C3‑201504 29.512 Rel-16 Update of OpenAPI version and TS version in externalDocs field Huawei CR Agreement No
No
 		reserved No    
    C3‑201505 29.507 Rel-16 Update of OpenAPI version and TS version in externalDocs field Nokia, Nokia Shanghai Bell CR Agreement No
No
 		reserved No    
    C3‑201506 29.514 Rel-16 Update of OpenAPI version and TS version in externalDocs field Ericsson CR Agreement No
No
 		reserved No    
    C3‑201507 29.520 Rel-16 Update of OpenAPI version and TS version in externalDocs field China Mobile Communications Group Co.,Ltd. CR Agreement No
No
 		reserved No    
    C3‑201508 29.522 Rel-16 Update of OpenAPI version and TS version in externalDocs field Huawei CR Agreement No
No
 		reserved No    
    C3‑201509 29.508 Rel-16 Update of OpenAPI version and TS version in externalDocs field Nokia, Nokia Shanghai Bell CR Agreement No
No
 		reserved No    
    C3‑201510 29.122 Rel-16 Update of OpenAPI version and TS version in externalDocs field Huawei CR Agreement No
No
 		reserved No    
    C3‑201511 29.554 Rel-16 Update of OpenAPI version and TS version in externalDocs field Ericsson CR Agreement Yes
Yes
 		agreed No    
    C3‑201512 29.525 Rel-16 Update of OpenAPI version and TS version in externalDocs field Nokia, Nokia Shanghai Bell CR Agreement No
No
 		reserved No    
    C3‑201513 29.222 Rel-16 Update of OpenAPI version and TS version in externalDocs field Samsung CR Agreement No
No
 		reserved No    
    C3‑201514 29.551 Rel-16 Update of OpenAPI version and TS version in externalDocs field ZTE CR Agreement No
No
 		reserved No    
    C3‑201515 Rel-16 OpenAPI version update of Rel-16 Nudr_DataRepository API Huawei discussion discussion No
No
 		reserved No    
17.1 Work Plan Review C3‑201012 Status of CT3 Work Items CT3 chairman Work Plan Information Yes
Yes
 		revised No C3‑201536  
    C3‑201536 Status of CT3 Work Items CT3 chairman Work Plan Information No
No
 		reserved No   C3‑201012
    C3‑201015 WI status report from MCC MCC Work Plan Information Yes
Yes
 		noted No    
17.2 Specification Review                      
17.3 Next meetings, allocation of hosts                      
17.4 Calendar C3‑201016 Meeting Calendar MCC other Information Yes
Yes
 		noted No    
18 Joint Sessions C3‑201130 29.571 CR Downlink data delivery status Huawei discussion Agreement Yes
YesHuawei: new name for the data type impacts the CT3 CR.
 		noted No    
    C3‑201131 29.571 CR User Location Huawei discussion Agreement Yes
Yes
 		noted No    
    C3‑201135 Support of traffic correlation Huawei discussion Discussion Yes
Yes
 		noted No    
    C3‑201150 29.571 CR V2X parameters Huawei Technologies R&D UK discussion Discussion Yes
Yes
 		noted No    
    C3‑201235 Enumerations and "nullable" keyword Ericsson discussion Discussion Yes
YesCheck if the OpenAPI specification needs to change the version.
 		noted No    
19 Summary of results                      
20 Any other business                      
21 Closing of the meeting