Tdoc List

2024-10-18 14:32

Agenda Topic TDoc Title Source Type For Avail Treated Decision Wdrn Replaced-by Replaces
1 Opening of the meeting                      
2 Approval of the agenda S5‑245200 Agenda WG Chair agenda   Yes
YesThe SA5 Chair opened the SA5#157 meeting. TATA welcomed the Delegates on behalf of the hosts.
 		approved No    
3 IPR and legal declaration S5‑245201 IPR and legal declaration WG Chair other   Yes
Yes"The attention of the delegates to the meeting of this Technical Specification Group was drawn to the fact that 3GPP Individual Members have the obligation under the IPR Policies of their respective Organizational Partners to inform their respective Organizational Partners of Essential IPRs they become aware of. The delegates were asked to take note that they were thereby invited: - to investigate whether their organization or any other organization owns IPRs which were, or were likely to become Essential in respect of the work of 3GPP. - to notify their respective Organizational Partners of all potential IPRs, e.g., for ETSI, by means of the IPR Information Statement and the Licensing declaration forms " "The attention of the delegates to the meeting was drawn to the fact that 3GPP activities were subject to all applicable antitrust and competition laws and that compliance with said laws was therefore required by any participant of the meeting, including the Chair and Vice-Chairs and were invited to seek any clarification needed with their legal counsel. The leadership would conduct the present meeting with impartiality and in the interests of 3GPP. Delegates were reminded that timely submission of work items in advance of TSG/WG/SWG meetings was important to allow for full and fair consideration of such matters."
 		noted No    
4 Meetings and activities reports                      
4.1 Last SA5 meeting report S5‑245202 Report from last SA5 meeting MCC report   Yes
Yes
 		approved No    
4.2 Inter-organizational reports                      
5 SA5 level issues                      
5.1 Administrative issues at SA5 level S5‑245203 Time Plan for SA5 Plenary and OAM sessions WG Chair agenda   No
Yeskept open
 		noted No    
    S5‑245204 agenda_with_Tdocs_sequence_Plenary&OAM WG Chair agenda   No
Yes
 		noted No    
    S5‑245205 SA5 working procedures WG Chair other   Yes
Yesdelegates need to request new tdocs numbers from MCC during the main track session to keep the Chair notes synchronized, i.e. no new tdoc numbers are allocated outside the main session. will be merged with S5-245228 Keep open
 		revised No S5‑245972  
    S5‑245972 SA5 working procedures WG Chair other - No
Yes
 		approved No   S5‑245205
    S5‑245206 SA5 Meeting facility requirements WG Chair other   Yes
Yesadd requirements for meeting room arrangements
 		revised No S5‑245973  
    S5‑245973 SA5 Meeting facility requirements WG Chair other - No
Yes
 		noted No   S5‑245206
    S5‑245208 Post meeting email approval status WG Vice Chair (Ericsson) other   No
Yes
 		noted No    
    S5‑245211 Plenary and OAM Chair notes and conclusions WG Chair report   No
Yes
 		noted No    
    S5‑245218 Latest SA5 Rel-19 WIs-SIs WG Chair other   Yes
Yes
 		noted No    
    S5‑245219 Rel-19 SA5 work planning WG Chair other   Yes
Yes
 		revised No S5‑245974  
    S5‑245974 Rel-19 SA5 work planning WG Chair other - No
Yes
 		noted No   S5‑245219
    S5‑245220 Rel-19 SA5 work plan TU table WG Chair other   Yes
Yesrev 1 was presented on Mon., based on the SA Chair's request. SA5 Chair: Can decide for the Origami resentation on Fri. xx: question about OAM starting at the same time as SA2 Agreement before next SA plenary keep open
 		revised No S5‑246294  
    S5‑246294 Rel-19 SA5 work plan TU table WG Chair other - No
Yes
 		noted No   S5‑245220
    S5‑245228 SA5 working procedures Nokia, Nokia Shanghai Bell other Approval Yes
YesNokia suggested to pilot this merged into 5978
 		merged No    
    S5‑245342 Revision of Terms of Reference (ToR) for 3GPP TSG SA WG5 (SA5) MATRIXX Software, Amdocs ToR Agreement Yes
Yesadded charging SWG info move the 'charging information'
 		revised No S5‑245975  
    S5‑245975 Revision of Terms of Reference (ToR) for 3GPP TSG SA WG5 (SA5) MATRIXX Software, Amdocs ToR Agreement No
Yeskeep open d1 Shall be submitted to next SA#106 meeting!!
 		agreed No   S5‑245342
    S5‑245494 Rel-20 SA5 work planning WG Chair Work Plan   No
Yeskeep open no update in this meeting noted in closing plenary? How to improve the relation with SA1 Planned Dec. 5. or 12. for the Origami presentation SA5.
 		noted No    
    S5‑245495 Rel-20 Consideration on capturing management requirements WG Chair Work Plan   No
Yeskeep open
 		noted No    
5.2 Technical issues at SA5 level S5‑245233 User Guide - Using Forge for SA5 Nokia, Nokia Shanghai Bell other Information Yes
Yesput link in the wiki! update 1-2x year; in guideline folder.
 		noted No    
5.3 Liaison statements at SA5 level S5‑245373 LS on AIML data collection RAN LS in Information Yes
Yespresented by usa lady? 2 different opinions from Huawei & ZTE. OEM & CH discussion. HW needs more time. DT prefers option 2. ZTE: RAN only asked to discuss opt. 3 SA5 Chair: reply is needed. -> replied in 6299
 		replied to No    
    S5‑245377 Reply LS on SA2 questions on the predictive slice modification in Inter-PLMN based slice service continuity SA6 LS in Information Yes
Yes
 		approved No    
    S5‑245378 LS on maintaining specification consistency between GSMA and 3GPP on 5G roaming over roaming intermediaries. SA LS in Information Yes
YesSamsung volunteered to draft reply.
 		noted No    
    S5‑245379 LS on API availability support (SA5#156) SA6 LS in Action Yes
Yes
 		noted No    
    S5‑245976 reply to LS on API availability support (SA5#156) SA5 LS out Approval No
YesEricsson is in favour of sending. Nokia needed more time. Next meeting. Samsung: was postponed already at the last meeting.
 		revised No S5‑246295  
    S5‑246295 reply to LS on API availability support (SA5#156) SA5 LS out Approval No
Yesfor email approval
 		for email approval No   S5‑245976
    S5‑245380 LS response to 3GPP_Reservation of Edge Resources and Correlation information for API volume-based charging (SA5#156) GSMA OPG Operator Platform API Group LS in Information Yes
YesSA5 Chair: need to reply. Involve the leaders.
 		revised No    
    S5‑245977 LS response to 3GPP_Reservation of Edge Resources and Correlation information for API volume-based charging (SA5#156) SA5 LS out Information No
YesMetrixx, Huawei d4 for email approval
 		for email approval No    
5.4 SA5 meeting calendar S5‑245207 SA5 meeting calendar WG Chair other   Yes
Yes
 		revised No S5‑245978  
    S5‑245978 SA5 meeting calendar WG Chair other - No
Yes
 		noted No   S5‑245207
6 OAM&P                      
6.1 OAM&P Plenary S5‑245209 OAM action list WG Vice Chair (Nokia) other   No
Yes
 		noted No    
    S5‑245210 OAM Exec Report WG Vice Chair (Nokia) report   No
Yes
 		noted No    
    S5‑245212 Collection of useful endorsed documents in OAM WG Vice Chair (Nokia) discussion   No
Yes
 		noted No    
    S5‑245213 Collection of external communication documents in OAM WG Vice Chair (Nokia) discussion   No
Yes
 		noted No    
    S5‑245214 Living document for stage 2-3 alignment WG Vice Chair (Ericsson) discussion   No
Yes
 		withdrawn Yes    
    S5‑245222 Reply LS on AIML data collection ZTE Corporation LS out Approval Yes
Yesdiscussions between Samsung, Ericsson, etc. about how to reply. Samsung: we should not teach RAN how this works. merged into S5-245979 Content will be included in 5980.
 		merged No    
    S5‑245370 Reply LS on the Realization of Network Slices for 5G Networks Using Current IP/MPLS Technologies RAN3 LS in Information Yes
Yes
 		noted No    
    S5‑245371 LS on MBS Communication Service Type RAN3 LS in Information Yes
Yes
 		noted No    
    S5‑245372 LS on SON for Network Slicing and enhanced area scope RAN3 LS in Information Yes
YesEricsson will reply at the next meeting This LS needs to be presented again at the next meeting!!
 		postponed No    
    S5‑245374 LS Reply on "A Realization of Network Slices for 5G Networks Using Current IP/MPLS Technologies" SA2 LS in Information Yes
Yes
 		noted No    
    S5‑245376 LS on Masking of cryptographic keys in UE trace file from 3GPP core network entities SA3 LS in Information Yes
Yesrelated CRs 5256-65 This LS has to be presented again at the next meeting!!
 		postponed No    
    S5‑245381 LS on Establishment of new Focus Group on Artificial Intelligence Native for Telecommunication Networks (FG-AINN) ITU-T SG13 LS in Information Yes
Yeskeep open (need Hassan) Has to be presented again at the next meeting!!
 		postponed No    
    S5‑245382 LS on consent of draft new Recommendation ITU-T Y.3144 (ex.Y.IMT2020-DCN) “Future networks including IMT-2020 – Requirements and functional architecture of distributed core network” ITU-T SG13 LS in Information Yes
Yes
 		noted No    
    S5‑245383 LS on consent of draft new Recommendation ITU-T Y.3187 (ex.Y.ML-IMT2020-MLFO) “Architectural framework for Machine Learning Function Orchestrator in future networks including IMT-2020” ITU-T SG13 LS in Information Yes
Yes
 		noted No    
    S5‑245384 LS on initiation of new work item ITU-T Y.NSF “Requirements and framework of network slicing federation in IMT-2020 networks and beyond” ITU-T SG13 LS in Information Yes
Yes
 		noted No    
    S5‑245385 LS on initiation of two new Recommendations ITU-T Y.NGNe-cp_mobility: “Mobility management and control framework in NGN evolution control plane” and ITU-T Y.NGNe-cp_na: “Network attachment control framework in NGN evolution control plane” ITU-T SG13 LS in Information Yes
Yes
 		noted No    
    S5‑245386 LS/r on ongoing work on Network Digital Twin (reply to ETSI ISG ZSM-(24)000087-LS10) ITU-T SG13 LS in Information Yes
Yes
 		noted No    
    S5‑245387 LS on the consent of draft new Recommendation ITU-T Y.3092 (ex.Y.DTNMO) “Digital twin for management and orchestration in IMT-2020 networks and beyond” ITU-T SG13 LS in Information Yes
Yes
 		noted No    
    S5‑245388 LS on consent of draft new Recommendation ITU-T Y.3163 (ex.Y.NAEC) “Network accelerating for edge computing in IMT-2020 networks and beyond” ITU-T SG13 LS in Information Yes
Yes
 		noted No    
    S5‑245424 LS to ETSI ATTM, ETSI OEU and ITU-T SG5 on carbon emission related KPIs Huawei LS out Approval Yes
Yes+SA1
 		revised No S5‑246215  
    S5‑246215 LS to ETSI ATTM, ETSI OEU and ITU-T SG5 on carbon emission related KPIs Huawei LS out Approval No
Yes
 		approved No   S5‑245424
    S5‑245527 Reply LS on AIML Data Collection SA5 LS out Approval Yes
YesSamsung: cannot say MDT is futureproof. Qualcomm: SA5 does not support any solution yet. Samsung will disagree to any discussion papers.
 		revised No S5‑245979  
    S5‑245979 Reply LS on AIML Data Collection SA5 LS out Approval No
Yesd7
 		revised No S5‑246299 S5‑245527
    S5‑246299 Reply LS on AIML Data Collection SA5 LS out Approval No
Yes
 		approved No   S5‑245979
    S5‑245772 DP on Recommendation for TS handling of IRP based solutions Ericsson India Private Limited discussion Endorsement Yes
Yes
 		revised No S5‑246216  
    S5‑246216 DP on Recommendation for TS handling of IRP based solutions Ericsson India Private Limited discussion Endorsement No
Yeswas not the right version
 		revised No S5‑246286 S5‑245772
    S5‑246286 DP on Recommendation for TS handling of IRP based solutions Ericsson India Private Limited discussion Endorsement No
Yes
 		endorsed No   S5‑246216
    S5‑245968 OAM breakout notes Chair report discussion No
Yespost meeting
 		noted No    
    S5‑245980 data collection options for UE-side model training. ZTE, Huawei, NEC discussion discussion No
Yesnew doc MCC: pls. produce a clean version
 		revised No S5‑246287  
    S5‑246287 data collection options for UE-side model training. ZTE, Huawei, NEC discussion discussion No
Yes
 		endorsed No   S5‑245980
    S5‑246296 LS to SA3 on SA5 MonStra work progress (VDF) SA5 LS out discussion No
No(Vaodafone) for email approval
 		for email approval No    
6.2 New OAM&P Work Item proposals                      
6.2.1 Intelligence and Automation S5‑245360 New WID on intent driven management services for mobile network phase 3 Huawei,Ericsson WID new Agreement Yes
Yes
 		revised No S5‑246125  
    S5‑246125 New WID on intent driven management services for mobile network phase 3 Huawei,Ericsson WID new Agreement No
Yes
 		agreed No   S5‑245360
    S5‑245367 WID Management Data Analytics (MDA) – Phase 3 Huawei WID new Agreement Yes
YesNEC, Samsung, Nokia, ZTE, DT asked to be added d2: added China Mobile, China Unicom, Verizon
 		revised No S5‑246126  
    S5‑246126 WID Management Data Analytics (MDA) – Phase 3 Huawei WID new Agreement No
Yes
 		agreed No   S5‑245367
    S5‑245396 New WID on management aspects of Network Digital Twin China Mobile WID new Agreement Yes
Yesreceived offline comments & prepared a rev.
 		revised No S5‑246127  
    S5‑246127 New WID on management aspects of Network Digital Twin China Mobile WID new Agreement No
YesNokia objected.
 		noted No   S5‑245396
    S5‑245714 New WID on Closed Control Loop management Samsung, Nokia WID new Agreement Yes
YesEricsson offline comments DT is supporting
 		revised No S5‑246128  
    S5‑246128 New WID on Closed Control Loop management Samsung, Nokia WID new Agreement No
YesEricsson : several comments not taken into account. Objected.
 		noted No   S5‑245714
    S5‑245854 Revised SID: Study on AIML management phase 2 NEC, Intel SID revised Agreement Yes
YesUnique identifier: 1020007
 		revised No S5‑246129  
    S5‑246129 Revised SID: Study on AIML management phase 2 NEC, Intel SID revised Agreement No
Yes
 		agreed No   S5‑245854
6.2.2 Management Architecture and Mechanisms S5‑245442 New WID on management of IAB nodes Ericsson Telecomunicazioni SpA WID new Agreement Yes
Yes
 		revised No S5‑246130  
    S5‑246130 New WID on management of IAB nodes Ericsson Telecomunicazioni SpA WID new Agreement No
Yes
 		agreed No   S5‑245442
    S5‑245544 New WID on Life Cycle Management (LCM) of NF Deployment Ericsson Telecomunicazioni SpA WID new Agreement Yes
Yes
 		noted No    
    S5‑245715 New WID on Management Aspects of NTN Phase 2 China Unicom,CATT WID new Agreement Yes
Yes
 		revised No S5‑246131  
    S5‑246131 New WID on Management Aspects of NTN Phase 2 China Unicom,CATT WID new Agreement No
Yes
 		revised No S5‑246288 S5‑245715
    S5‑246288 New WID on Management Aspects of NTN Phase 2 China Unicom,CATT WID new Agreement No
Yes
 		agreed No   S5‑246131
    S5‑245726 new WID on cloud aspects of management and orchestration China Mobile Com. Corporation WID new Agreement Yes
YesEricsson objected
 		noted No    
    S5‑245738 Revised SID Study on Service Based Management Architecture enhancement phase 3 Ericsson, Huawei SID revised Agreement Yes
Yes
 		agreed No    
    S5‑245768 pCR Add Evaluation of solutions for Cloud-native VNF policy management China Mobile,NTT DOCOMO pCR Approval No
Yes
 		withdrawn Yes    
    S5‑245775 Revised SID Study on Cloud Aspects of Management and Orchestration China Mobile SID revised Approval Yes
Yes
 		agreed No   SP‑231781
    S5‑245785 New WID on Management of Network Sharing Phase 3 China Unicom WID new Agreement Yes
YesNokia offline comments AN x Samsung: WT-1 needs to wait
 		revised No S5‑246132  
    S5‑246132 New WID on Management of Network Sharing Phase 3 China Unicom WID new Agreement No
Yes
 		revised No S5‑246289 S5‑245785
    S5‑246289 New WID on Management of Network Sharing Phase 3 China Unicom WID new Agreement No
Yes
 		agreed No   S5‑246132
    S5‑245793 Revised WID on 5G Advanced NRM features phase 3 Ericsson Inc. WID revised Agreement Yes
YesUnique identifier: 1020027
 		noted No    
6.2.3 Support of New Services S5‑245336 Initial skeleton of draft TS28.abc v0.0.0 signaling traffic monitoring management Ericsson, Vodafone other Approval Yes
Yes
 		revised No S5‑245983  
    S5‑245983 Initial skeleton of draft TS28.abc v0.0.0 signaling traffic monitoring management Ericsson, Vodafone other Approval No
Yespreliminary work before SA approval on the MonStra WID.
 		approved No   S5‑245336
    S5‑245337 pCR of draft TS28.abc Introduction Ericsson, Vodafone other Approval Yes
Yes
 		revised No S5‑245984  
    S5‑245984 pCR of draft TS28.abc Introduction Ericsson, Vodafone other Approval No
Yes
 		approved No   S5‑245337
    S5‑245338 pCR of draft TS28.abc Scope Ericsson, Vodafone other Approval Yes
Yes
 		revised No S5‑245985  
    S5‑245985 pCR of draft TS28.abc Scope Ericsson, Vodafone other Approval No
Yes
 		approved No   S5‑245338
    S5‑245339 pCR of draft TS28.abc Stage 1 skeleton Ericsson, Vodafone other Approval Yes
Yes
 		revised No S5‑245986  
    S5‑245986 pCR of draft TS28.abc Stage 1 skeleton Ericsson, Vodafone other Approval No
Yes
 		approved No   S5‑245339
    S5‑245340 pCR of draft TS28.abc Stage 2 skeleton Ericsson, Vodafone other Approval Yes
Yes
 		revised No S5‑245987  
    S5‑245987 pCR of draft TS28.abc Stage 2 skeleton Ericsson, Vodafone other Approval No
Yes
 		approved No   S5‑245340
    S5‑245341 pCR of draft TS28.abc Stage 3 skeleton Ericsson, Vodafone other Approval Yes
Yes
 		revised No S5‑245988  
    S5‑245988 pCR of draft TS28.abc Stage 3 skeleton Ericsson, Vodafone other Approval No
Yes
 		approved No   S5‑245341
    S5‑245615 Revised SID on Study on Enhanced OAM for management exposure to external consumers Nokia SID revised Agreement Yes
Yes
 		revised No S5‑246133  
    S5‑246133 Revised SID on Study on Enhanced OAM for management exposure to external consumers Nokia SID revised Agreement No
Yes
 		agreed No   S5‑245615
    S5‑245711 New WID on Management Aspects of RedCap features China Unicom WID new Agreement Yes
YesWT 1.2 shall be kept open
 		revised No S5‑246134  
    S5‑246134 New WID on Management Aspects of RedCap features China Unicom WID new Agreement No
YesSamsung needs more time for the discussions.
 		noted No   S5‑245711
    S5‑245722 New WID on Management for MonStra Vodafone, Ericsson, Nokia, Nokia Shanghai Bell, Verizon, Telecom Italia, Deutsche Telekom, NTT DOCOMO WID new Agreement Yes
Yes2 meetings to conclude. DT supports the WID.
 		revised No S5‑245981  
    S5‑245981 New WID on Management for MonStra Vodafone, Ericsson, Nokia, Nokia Shanghai Bell, Verizon, Telecom Italia, Deutsche Telekom, NTT DOCOMO WID new Agreement No
Yes
 		agreed No   S5‑245722
    S5‑245802 pCR of draft TS28.abc Stage 1 requirements Vodafone, Ericsson other Approval Yes
Yes
 		revised No S5‑245989  
    S5‑245989 pCR of draft TS28.abc Stage 1 requirements Vodafone, Ericsson other Approval No
Yeskeep open rev5
 		approved No   S5‑245802
    S5‑245806 DP on Signalling Traffic Monitoring Vodafone, Ericsson discussion Endorsement Yes
Yes
 		withdrawn Yes    
    S5‑245845 DP on Signalling Traffic Monitoring Vodafone Ireland Plc discussion Endorsement Yes
Yes
 		withdrawn Yes    
    S5‑245847 DP on Signalling Traffic Monitoring Vodafone, Ericsson discussion Endorsement Yes
Yessummarize proposals for endorsement.
 		revised No S5‑245982  
    S5‑245982 DP on Signalling Traffic Monitoring Vodafone, Ericsson discussion Endorsement No
Yesrev1
 		endorsed No   S5‑245847
6.3 Pre-Rel-18 Maintenance                      
6.3.1 Methodology                      
6.3.2 ANL                      
6.3.3 MDAS S5‑245523 Rel-17 CR TS 28.104 Fixing a non-existing datatype Nokia CR Approval Yes
YesEricsson needed more time
 		revised No S5‑246180  
    S5‑246180 Rel-17 CR TS 28.104 Fixing a non-existing datatype Nokia CR Approval No
Yesd1
 		agreed No   S5‑245523
    S5‑245524 Rel-18 CR TS 28.104 Fixing the non-existing datatype - "List" Nokia CR Approval Yes
Yessame as 5523
 		revised No S5‑246181  
    S5‑246181 Rel-18 CR TS 28.104 Fixing the non-existing datatype - "List" Nokia CR Approval No
Yes
 		agreed No   S5‑245524
    S5‑245525 Rel-17 CR TS 28.104 Aligning ENUM literals as per the guidelines Nokia CR Approval Yes
YesEricsson: overlap with 5748 (merge into) Use core as CN in a consistent way. merge 5609 into
 		revised No S5‑246182  
    S5‑246182 Rel-17 CR TS 28.104 Aligning ENUM literals as per the guidelines Nokia CR Approval No
Yes
 		agreed No   S5‑245525
    S5‑245526 Rel-18 CR TS 28.104 Aligning ENUM literals as per the guidelines Nokia CR Approval Yes
Yessame as 5525 E/// CR 5747.
 		revised No S5‑246183  
    S5‑246183 Rel-18 CR TS 28.104 Aligning ENUM literals as per the guidelines Nokia CR Approval No
Yes
 		agreed No   S5‑245526
    S5‑245609 Rel-17 CR TS 28.104 Correct the allowed value of issue type Huawei CR Agreement Yes
Yesmerged into 6182
 		merged No    
    S5‑245610 Rel-18 CR TS 28.104 Correct the allowed value of issue type Huawei CR Agreement Yes
Yesmerged into 6183
 		merged No    
    S5‑245744 Rel-17 CR TS 28.104 Clarify MDA in management loop Ericsson, Deutsche Telekom CR Approval Yes
Yes
 		agreed No   S5‑244275
    S5‑245745 CR TS 28.104 Clarify MDA in management loop Ericsson, Deutsche Telekom CR Approval Yes
Yes
 		agreed No   S5‑244276
    S5‑245746 Rel-17 CR TS 28.104 Clarify MDA report identifier Ericsson, Deutsche Telekom CR Approval Yes
YesHuawei: this attribute is introduced in Rel-17, how to deprecate it.
 		not pursued No   S5‑244268
    S5‑245747 Rel-18 CR TS 28.104 Clarify MDA report identifier Ericsson, Deutsche Telekom CR Approval Yes
Yessame as 5747
 		not pursued No   S5‑244269
    S5‑245748 Rel-17 CR TS 28.104 Clarify Recommended3GPPAction Ericsson, Deutsche Telekom CR Approval Yes
Yes
 		revised No S5‑246185 S5‑244277
    S5‑246185 Rel-17 CR TS 28.104 Clarify Recommended3GPPAction Ericsson, Deutsche Telekom CR Approval No
Yesd2
 		agreed No   S5‑245748
    S5‑245749 Rel-18 CR TS 28.104 Clarify Recommended3GPPAction Ericsson, Deutsche Telekom CR Approval Yes
Yes
 		revised No S5‑246186 S5‑244278
    S5‑246186 Rel-18 CR TS 28.104 Clarify Recommended3GPPAction Ericsson, Deutsche Telekom CR Approval No
Yes
 		agreed No   S5‑245749
    S5‑245750 Rel-17 CR TS 28.104 Correct error in attribute properties of analyticsScope Ericsson, Deutsche Telekom CR Approval Yes
Yes
 		agreed No   S5‑244266
    S5‑245751 Rel-18 CR TS 28.104 Correct error in attribute properties of analyticsScope Ericsson, Deutsche Telekom CR Approval No
Yes
 		withdrawn Yes   S5‑244266
    S5‑245752 Rel-17 CR 28.104 Clarify analytics identifier Ericsson, Deutsche Telekom CR Approval Yes
YesHuawei: changing a string to integer is not fully justified
 		revised No S5‑246275  
    S5‑246275 Rel-17 CR 28.104 Clarify analytics identifier Ericsson, Deutsche Telekom CR Approval No
Yesd1
 		withdrawn Yes   S5‑245752
    S5‑245753 Rel-18 CR 28.104 Clarify analytics identifier Ericsson, Deutsche Telekom CR Approval Yes
Yessame as 5752
 		revised No S5‑246276  
    S5‑246276 Rel-18 CR 28.104 Clarify analytics identifier Ericsson, Deutsche Telekom CR Approval No
Yesd1
 		withdrawn Yes   S5‑245753
    S5‑245779 Rel-18 CR TS 28.104 Correct error in attribute properties of analyticsScope Ericsson, Deutsche Telekom CR Approval Yes
Yes
 		agreed No   S5‑244267
6.3.4 AI/ML S5‑245730 Rel 17 CR TS 28.105 Make decisionConfidenceScore attr applicable for Training Ericsson CR Approval Yes
Yes
 		revised No S5‑246217  
    S5‑246217 Rel 17 CR TS 28.105 Make decisionConfidenceScore attr applicable for Training Ericsson CR Approval No
Yes
 		agreed No   S5‑245730
    S5‑245733 Rel 18 CR TS 28.105 Make decisionConfidenceScore attr applicable for Training Ericsson CR Approval Yes
Yes
 		revised No S5‑246218  
    S5‑246218 Rel 18 CR TS 28.105 Make decisionConfidenceScore attr applicable for Training Ericsson CR Approval No
Yesd1
 		agreed No   S5‑245733
    S5‑245735 Rel 19 CR TS 28.105 Make decisionConfidenceScore attr applicable for Training Ericsson CR Approval Yes
Yes
 		revised No S5‑246219  
    S5‑246219 Rel 19 CR TS 28.105 Make decisionConfidenceScore attr applicable for Training Ericsson CR Approval No
Yes
 		agreed No   S5‑245735
    S5‑245809 Rel-17 CR TS 28.105 Fix trainingRequestSource attribute Ericsson Limited CR   No
Yes
 		withdrawn Yes    
6.3.5 Energy efficiency                      
6.3.6 Intent driven management S5‑245438 Rel-17 CR TS 28.312 intent definition clarification Nokia CR Approval Yes
YesHuawei: coversheet needs to be aligned.
 		revised No S5‑246187  
    S5‑246187 Rel-17 CR TS 28.312 intent definition clarification Nokia CR Approval No
Yesd1
 		agreed No   S5‑245438
6.3.7 SON                      
6.3.8 QMC                      
6.3.9 Network slicing management S5‑245286 Rel-17 CR TS 28.541 Update configuration parameters for GST translation Huawei CR Agreement Yes
Yes
 		not pursued No    
    S5‑245287 Rel-18 CR TS 28.541 Update configuration parameters for GST translation Huawei CR Agreement Yes
Yes
 		not pursued No    
    S5‑245288 Rel-19 CR TS 28.541 Update configuration parameters for GST translation Huawei CR Agreement Yes
YesEricsson offline comments
 		not pursued No    
    S5‑245622 Rel-18 CR TS 28.541 Correction to sliceAvailability and sliceSubnetAvailability Nokia CR Approval Yes
Yes
 		agreed No    
    S5‑245623 Rel-19 CR TS 28.541 Correction to sliceAvailability and sliceSubnetAvailability Nokia CR Approval Yes
Yes
 		agreed No    
    S5‑245628 Rel-17 CR TS 28.541 Corrections to slice SLA attribute energyEfficiency Nokia CR Approval Yes
YesHuawei: wait for reply from GSMA
 		not pursued No   S5‑243599
    S5‑245629 Rel-18 CR TS 28.541 Corrections to slice SLA attribute energyEfficiency Nokia CR Approval Yes
Yes
 		not pursued No   S5‑243600
    S5‑245630 Rel-19 CR TS 28.541 Corrections to slice SLA attribute energyEfficiency Nokia CR Approval Yes
Yes
 		not pursued No   S5‑243601
6.3.10 MEC management S5‑245316 Rel-17 CR TS 28.538 Correct the desciption of attributes Huawei CR Agreement Yes
YesEricsson: check offline
 		revised No S5‑246189  
    S5‑246189 Rel-17 CR TS 28.538 Correct the desciption of attributes Huawei CR Agreement No
Yes
 		agreed No   S5‑245316
    S5‑245317 Rel-18 CR TS 28.538 Correct the desciption of attributes Huawei CR Agreement Yes
Yes
 		revised No S5‑246190  
    S5‑246190 Rel-18 CR TS 28.538 Correct the desciption of attributes Huawei CR Agreement No
Yes
 		agreed No   S5‑245317
    S5‑245318 Rel-19 CR TS 28.538 Correct the desciption of attributes Huawei CR Agreement Yes
Yes
 		revised No S5‑246191  
    S5‑246191 Rel-19 CR TS 28.538 Correct the desciption of attributes Huawei CR Agreement No
Yes
 		agreed No   S5‑245318
6.3.11 General NRM S5‑245229 Correction to misalignment of stage 2 and stage 3 for CellIndividualOffset and QOffsetRangeList Nokia, Nokia Shanghai Bell CR Approval Yes
YesEricsson offline comments
 		revised No S5‑246192 S5‑243653
    S5‑246192 Correction to misalignment of stage 2 and stage 3 for CellIndividualOffset and QOffsetRangeList Nokia, Nokia Shanghai Bell CR Approval No
Yes
 		agreed No   S5‑245229
    S5‑245230 Correction to misalignment of stage 2 and stage 3 for CellIndividualOffset and QOffsetRangeList Nokia, Nokia Shanghai Bell CR Approval Yes
Yes
 		revised No S5‑246193 S5‑243654
    S5‑246193 Correction to misalignment of stage 2 and stage 3 for CellIndividualOffset and QOffsetRangeList Nokia, Nokia Shanghai Bell CR Approval No
Yes
 		agreed No   S5‑245230
    S5‑245231 Correction to misalignment of stage 2 and stage 3 for CellIndividualOffset and QOffsetRangeList Nokia, Nokia Shanghai Bell CR Approval Yes
Yesfirst agreed, than revised on Thu
 		revised No S5‑246220 S5‑244052
    S5‑246220 Correction to misalignment of stage 2 and stage 3 for CellIndividualOffset and QOffsetRangeList Nokia, Nokia Shanghai Bell CR Approval No
Yes
 		agreed No   S5‑245231
    S5‑245232 Correction to misalignment of stage 2 and stage 3 for CellIndividualOffset and QOffsetRangeList Nokia, Nokia Shanghai Bell CR Approval Yes
Yes
 		agreed No   S5‑244053
    S5‑245239 Rel-17 CR TS 28.541 Correct both stage2 and stage3 for NRNetwork and EUtraNetwork NRM fragement Huawei CR Agreement No
Yes
 		withdrawn Yes    
    S5‑245242 Rel-17 CR TS 28.623 Correct the YAML definition for PerfMetricJob and ProcessMonitor to align with stage2 Huawei CR Agreement Yes
Yes
 		agreed No    
    S5‑245243 Rel-18 CR TS 28.623 Correct the YAML definition for PerfMetricJob and ProcessMonitor to align with stage2 Huawei CR Agreement Yes
Yes
 		agreed No    
    S5‑245244 Rel-19 CR TS 28.623 Correct the YAML definition for PerfMetricJob and ProcessMonitor to align with stage2 Huawei CR Agreement Yes
Yes
 		agreed No    
    S5‑245472 Correction to Jex for dataNodeSelector and notificationFilter in OpenAPI Nokia, Nokia Shanghai Bell CR Approval Yes
Yes
 		agreed No    
    S5‑245473 Correction to Jex for dataNodeSelector and notificationFilter in OpenAPI Nokia, Nokia Shanghai Bell CR Approval Yes
Yes
 		agreed No    
    S5‑245474 Correction to Jex for dataNodeSelector and Filter in OpenAPI Nokia, Nokia Shanghai Bell CR Approval Yes
Yes
 		agreed No    
    S5‑245475 Update Forge link and a few miscellaneous corrections Nokia, Nokia Shanghai Bell CR Approval Yes
Yes
 		revised No S5‑246194  
    S5‑246194 Update Forge link and a few miscellaneous corrections Nokia, Nokia Shanghai Bell CR Approval No
Yes
 		agreed No   S5‑245475
    S5‑245476 Update Forge link and a few miscellaneous corrections Nokia, Nokia Shanghai Bell CR Approval Yes
Yes
 		revised No S5‑246195  
    S5‑246195 Update Forge link and a few miscellaneous corrections Nokia, Nokia Shanghai Bell CR Approval No
Yes
 		agreed No   S5‑245476
    S5‑245477 Correction to class diagram Nokia, Nokia Shanghai Bell CR Approval Yes
Yes
 		agreed No    
    S5‑245478 Correction to class diagram Nokia, Nokia Shanghai Bell CR Approval Yes
Yes
 		agreed No    
    S5‑245535 Rel-17 CR 32.300 Clarification of allowed characters and escaping Ericsson Hungary Ltd CR Approval Yes
YesNokia: need time to check
 		agreed No    
    S5‑245536 Rel-18 CR 32.300 Clarification of allowed characters and escaping Ericsson Hungary Ltd CR Approval Yes
Yessame as 5535
 		agreed No    
    S5‑245611 Rel-17 CR TS 28.541 Correction on the property of attibutes Huawei CR Agreement Yes
Yes
 		agreed No    
    S5‑245612 Rel-18 CR TS 28.541 Correction on the property of attibutes Huawei CR Agreement Yes
Yes
 		agreed No    
    S5‑245613 Rel-19 CR TS 28.541 Correction on the property of attibutes Huawei CR Agreement Yes
Yes
 		agreed No    
    S5‑245781 Discussion paper on scope and cleanup of FNIM content Ericsson Inc. discussion Approval Yes
YesNokia: cannot agree. Prefer solution 3. Rapporteur's call.
 		noted No    
    S5‑245805 Rel-17 CR TS 28.622 Correction to AreaOfInterest Ericsson Limited CR   Yes
Yes
 		withdrawn Yes    
    S5‑245807 Rel-18 CR TS 28.622 Correction to AreaOfInterest Ericsson Limited CR   Yes
Yes
 		withdrawn Yes    
    S5‑245808 Rel-19 CR TS 28.622 Correction to AreaOfInterest Ericsson Limited CR   Yes
Yes
 		withdrawn Yes    
    S5‑245822 Rel15 CR TS 28.532 Correction on the supported URI query parameters by the HTTP DELETE method on the "…/{className}={id}" resource Nokia CR Approval Yes
Yes
 		agreed No    
    S5‑245823 Rel16 CR TS 28.532 Correction on the supported URI query parameters and response body of the HTTP DELETE method on the "…/{className}={id}" resource Nokia CR Approval Yes
Yes
 		agreed No    
    S5‑245824 Rel17 CR TS 28.532 Correction on the supported URI query parameters and response body of the HTTP DELETE method on the "…/{className}={id}" resource Nokia CR Approval Yes
Yes
 		agreed No    
    S5‑245825 Rel18 CR TS 28.532 Correction on the supported URI query parameters and response body of the HTTP DELETE method on the "…/{className}={id}" resource Nokia CR Approval Yes
Yes
 		agreed No    
    S5‑245826 Rel18 CR TS 28.532 Clarifying the description of the modifications list input parameter in the changeMOI operations Nokia CR Approval Yes
Yes
 		agreed No    
    S5‑245832 Rel-17 CR TS 28.531 Management Service for NF provisioning Ericsson Limited CR   Yes
Yes
 		agreed No    
    S5‑245833 Rel-18 CR TS 28.531 Management Service for NF provisioning Ericsson Limited CR   Yes
Yes
 		agreed No    
    S5‑245834 Rel-19 CR TS 28.531 Management Service for NF provisioning Ericsson Limited CR   Yes
Yes18.7.0->19.7.0
 		revised No S5‑246198  
    S5‑246198 Rel-19 CR TS 28.531 Management Service for NF provisioning Ericsson Limited CR - No
Yes
 		agreed No   S5‑245834
    S5‑245836 Rel-17 CR TS28.541 Fix Documentation column of NRCellDU.pLMNInfoList ZTE Corporation CR Approval Yes
Yes
 		agreed No    
    S5‑245837 Rel-18 CR TS28.541 Fix Documentation column of NRCellDU.pLMNInfoList ZTE Corporation CR Approval Yes
Yes
 		agreed No    
    S5‑245838 Rel-19 CR TS28.541 Fix Documentation column of NRCellDU.pLMNInfoList ZTE Corporation CR Approval Yes
Yes
 		agreed No    
    S5‑245865 Rel-18 CR 28.623 YANG Corrections SA5-157 Ericsson Hungary Ltd CR Approval Yes
Yesrev 1
 		revised No S5‑246199  
    S5‑246199 Rel-18 CR 28.623 YANG Corrections SA5-157 Ericsson Hungary Ltd CR Approval No
Yes
 		agreed No   S5‑245865
    S5‑245868 Rel-18 CR 28.541 YANG Corrections SA5-157 Ericsson Hungary Ltd CR Approval Yes
Yesrev 1
 		revised No S5‑246200  
    S5‑246200 Rel-18 CR 28.541 YANG Corrections SA5-157 Ericsson Hungary Ltd CR Approval No
Yes
 		agreed No   S5‑245868
6.3.12 PM/KPI S5‑245549 Clarification of Measured UE Identifier in the measurement template Intel, Ericsson, Nokia CR Agreement No
Yes
 		withdrawn Yes    
    S5‑245635 Rel-19 CR 28.552 Correction of performance monitoring for UDM Ericsson CR Agreement Yes
Yes
 		agreed No    
    S5‑245841 Rel-16 CR TS28.552 Fix message for Number of successful PDU session modifications ZTE Corporation CR Approval Yes
Yes
 		agreed No    
    S5‑245842 Rel-17 CR TS28.552 Fix message for Number of successful PDU session modifications ZTE Corporation CR Approval Yes
Yes
 		agreed No    
    S5‑245843 Rel-18 CR TS28.552 Fix message for Number of successful PDU session modifications ZTE Corporation CR Approval Yes
Yes
 		agreed No    
    S5‑245844 Rel-19 CR TS28.552 Fix message for Number of successful PDU session modifications ZTE Corporation CR Approval Yes
Yes
 		agreed No    
6.3.13 Trace/MDT S5‑245256 R15 CR 32.421 missing Sec requirements Ericsson CR Agreement Yes
YesNokia offline comments
 		revised No S5‑246201 S5‑242421
    S5‑246201 R15 CR 32.421 missing Sec requirements Ericsson CR Agreement No
Yes
 		agreed No   S5‑245256
    S5‑245257 R16 CR 32.421 missing Sec requirements Ericsson CR Agreement Yes
Yessame as 5256
 		revised No S5‑246202 S5‑242422
    S5‑246202 R16 CR 32.421 missing Sec requirements Ericsson CR Agreement No
Yes
 		agreed No   S5‑245257
    S5‑245258 R17 CR 32.421 missing Sec requirements Ericsson CR Agreement Yes
Yessame as above
 		revised No S5‑246203 S5‑242423
    S5‑246203 R17 CR 32.421 missing Sec requirements Ericsson CR Agreement No
Yes
 		agreed No   S5‑245258
    S5‑245259 R18 CR 32.421 missing Sec requirements Ericsson CR Agreement Yes
Yessame as above
 		revised No S5‑246204 S5‑242424
    S5‑246204 R18 CR 32.421 missing Sec requirements Ericsson CR Agreement No
Yes
 		agreed No   S5‑245259
    S5‑245260 R19 CR 32.421 missing Sec requirements Ericsson CR Agreement Yes
Yessame as above
 		revised No S5‑246205  
    S5‑246205 R19 CR 32.421 missing Sec requirements Ericsson CR Agreement No
Yes
 		agreed No   S5‑245260
    S5‑245261 R15 CR 32.423 missing Sec requirements Ericsson CR Agreement Yes
Yesoffline comments
 		revised No S5‑246206 S5‑242429
    S5‑246206 R15 CR 32.423 missing Sec requirements Ericsson CR Agreement No
Yes
 		agreed No   S5‑245261
    S5‑245262 R16 CR 32.423 missing Sec requirements Ericsson CR Agreement Yes
Yessame as above
 		revised No S5‑246207 S5‑242426
    S5‑246207 R16 CR 32.423 missing Sec requirements Ericsson CR Agreement No
Yes
 		agreed No   S5‑245262
    S5‑245263 R17 CR 32.423 missing Sec requirements Ericsson CR Agreement Yes
Yessame as above
 		revised No S5‑246208 S5‑242427
    S5‑246208 R17 CR 32.423 missing Sec requirements Ericsson CR Agreement No
Yes
 		agreed No   S5‑245263
    S5‑245264 R18 CR 32.423 missing Sec requirements Ericsson CR Agreement Yes
Yessame as above
 		revised No S5‑246209 S5‑242428
    S5‑246209 R18 CR 32.423 missing Sec requirements Ericsson CR Agreement No
Yes
 		agreed No   S5‑245264
    S5‑245265 R19 CR 32.423 missing Sec requirements Ericsson CR Agreement Yes
Yessame as above
 		revised No S5‑246210  
    S5‑246210 R19 CR 32.423 missing Sec requirements Ericsson CR Agreement No
Yes
 		agreed No   S5‑245265
    S5‑245266 Rel-16 CR TS 28.622 Correction on File ready notification Ericsson CR Agreement Yes
YesNokia would like to keep the 'no notification' Keep open
 		revised No S5‑246211 S5‑243615
    S5‑246211 Rel-16 CR TS 28.622 Correction on File ready notification Ericsson CR Agreement No
Yes
 		withdrawn Yes   S5‑245266
    S5‑245267 Rel-17 CR TS 28.622 Correction on File ready notification Ericsson CR Agreement Yes
Yes
 		revised No S5‑246212 S5‑243616
    S5‑246212 Rel-17 CR TS 28.622 Correction on File ready notification Ericsson CR Agreement No
Yes
 		withdrawn Yes   S5‑245267
    S5‑245268 Rel-18 CR TS 28.622 Correction on File ready notification Ericsson CR Agreement Yes
Yes
 		revised No S5‑246213 S5‑243617
    S5‑246213 Rel-18 CR TS 28.622 Correction on File ready notification Ericsson CR Agreement No
Yes
 		withdrawn Yes   S5‑245268
    S5‑245269 Rel-19 CR TS 28.622 Correction on File ready notification Ericsson CR Agreement Yes
Yes
 		revised No S5‑246214 S5‑243618
    S5‑246214 Rel-19 CR TS 28.622 Correction on File ready notification Ericsson CR Agreement No
Yes
 		withdrawn Yes   S5‑245269
    S5‑245270 Rel-16 CR TS 32.422 Update NG-RAN activation mechanisms for management based MDT CATT CR Approval Yes
YesNokia offline comments
 		revised No S5‑246221  
    S5‑246221 Rel-16 CR TS 32.422 Update NG-RAN activation mechanisms for management based MDT CATT CR Approval No
Yes
 		agreed No   S5‑245270
    S5‑245271 Rel-17 CR TS 32.422 Update NG-RAN activation mechanisms for management based MDT CATT CR Approval Yes
Yes
 		revised No S5‑246222  
    S5‑246222 Rel-17 CR TS 32.422 Update NG-RAN activation mechanisms for management based MDT CATT CR Approval No
Yes
 		agreed No   S5‑245271
    S5‑245272 Rel-18 CR TS 32.422 Update NG-RAN activation mechanisms for management based MDT CATT CR Approval Yes
Yes
 		revised No S5‑246223  
    S5‑246223 Rel-18 CR TS 32.422 Update NG-RAN activation mechanisms for management based MDT CATT CR Approval No
Yes
 		agreed No   S5‑245272
    S5‑245273 Rel-19 CR TS 32.422 Update NG-RAN activation mechanisms for management based MDT CATT CR Approval Yes
Yes
 		revised No S5‑246224  
    S5‑246224 Rel-19 CR TS 32.422 Update NG-RAN activation mechanisms for management based MDT CATT CR Approval No
Yes
 		agreed No   S5‑245273
    S5‑245390 Rel-18 CR 28.623 Correction for "NR Measurent Type" for TraceControlNrm Nokia Corporation CR Approval Yes
Yes
 		revised No S5‑246227  
    S5‑246227 Rel-18 CR 28.623 Correction for "NR Measurent Type" for TraceControlNrm Nokia Corporation CR Approval No
Yes
 		agreed No   S5‑245390
    S5‑245452 Rel-16 CR 32.422 update measurement period description Huawei CR Agreement Yes
Yes
 		agreed No    
    S5‑245453 Rel-17 CR 32.422 update measurement period description Huawei CR Agreement Yes
Yes
 		agreed No    
    S5‑245454 Rel-18 CR 32.422 update measurement period description Huawei CR Agreement Yes
Yes
 		agreed No    
    S5‑245455 Rel-19 CR 32.422 update measurement period description Huawei CR Agreement Yes
Yes
 		revised No S5‑246229  
    S5‑246229 Rel-19 CR 32.422 update measurement period description Huawei CR Agreement No
Yes
 		agreed No   S5‑245455
    S5‑245481 Rel-19 CR 28.623 Correction for "NR Measurent Type" for TraceControlNrm Nokia Corporation CR Approval Yes
Yes
 		revised No S5‑246228  
    S5‑246228 Rel-19 CR 28.623 Correction for "NR Measurent Type" for TraceControlNrm Nokia Corporation CR Approval No
Yes
 		agreed No   S5‑245481
    S5‑245486 Rel-16 CR 28.623 Correction for "NR Measurent Type" for "GenericNrm" Nokia Corporation CR Approval Yes
Yes
 		revised No S5‑246225  
    S5‑246225 Rel-16 CR 28.623 Correction for "NR Measurent Type" for "GenericNrm" Nokia Corporation CR Approval No
Yes
 		agreed No   S5‑245486
    S5‑245488 Rel-17 CR 28.623 Correction for "NR Measurent Type" for "GenericNrm" Nokia Corporation CR Approval Yes
Yes
 		revised No S5‑246226  
    S5‑246226 Rel-17 CR 28.623 Correction for "NR Measurent Type" for "GenericNrm" Nokia Corporation CR Approval No
Yes
 		agreed No   S5‑245488
    S5‑245506 Rel-16 CR 28.622 Correction of attribute "jobType" of TraceJob IOC Nokia CR Approval Yes
Yes
 		agreed No    
    S5‑245507 Rel-17 CR 28.622 Correction of attribute "jobType" of TraceJob IOC Nokia CR Approval Yes
Yes
 		agreed No    
    S5‑245508 Rel-18 CR 28.622 Correction of attribute "jobType" of TraceJob IOC Nokia CR Approval Yes
Yes
 		agreed No    
    S5‑245509 Rel-19 CR 28.622 Correction of attribute "jobType" of TraceJob IOC Nokia CR Approval Yes
Yes
 		agreed No    
    S5‑245513 Rel-17 CR 32.422 Cleanup regarding latest time to send Trace Records to TCE Nokia CR Approval Yes
Yes
 		agreed No    
    S5‑245514 Rel-18 CR 32.422 Cleanup regarding latest time to send Trace Records to TCE Nokia CR Approval Yes
Yes
 		agreed No    
    S5‑245515 Rel-19 CR 32.422 Cleanup regarding latest time to send Trace Records to TCE Nokia CR Approval Yes
Yes
 		agreed No    
    S5‑245516 Rel-16 CR 32.422 Cleanup of configuration parameters and conditions Nokia CR Approval Yes
Yes
 		revised No S5‑245728  
    S5‑245517 Rel-17 CR 32.422 Cleanup of configuration parameters and conditions Nokia CR Approval Yes
Yes
 		agreed No    
    S5‑245518 Rel-18 CR 32.422 Cleanup of configuration parameters and conditions Nokia CR Approval Yes
Yes
 		revised No S5‑245731  
    S5‑245519 Rel-19 CR 32.422 Cleanup of configuration parameters and conditions Nokia CR Approval Yes
Yes
 		revised No S5‑245734  
    S5‑245728 Rel-16 CR 32.422 Cleanup of configuration parameters and conditions Nokia CR Approval Yes
Yes
 		agreed No   S5‑245516
    S5‑245731 Rel-18 CR 32.422 Cleanup of configuration parameters and conditions Nokia CR Approval Yes
Yes
 		agreed No   S5‑245518
    S5‑245734 Rel-19 CR 32.422 Cleanup of configuration parameters and conditions Nokia CR Approval Yes
Yes
 		agreed No   S5‑245519
    S5‑245866 CR Rel-19 TS 32.422 Corrections for MDT NEC CR Agreement Yes
YesF->A
 		revised No S5‑246230  
    S5‑246230 CR Rel-19 TS 32.422 Corrections for MDT NEC CR Agreement No
Yes
 		agreed No   S5‑245866
    S5‑245867 CR Rel-18 TS 32.422 Corrections for MDT NEC CR Agreement Yes
YesF->A
 		revised No S5‑246231  
    S5‑246231 CR Rel-18 TS 32.422 Corrections for MDT NEC CR Agreement No
Yes
 		agreed No   S5‑245867
    S5‑245869 CR Rel-17 TS 32.422 Corrections for MDT NEC CR Agreement Yes
YesA->F
 		revised No S5‑246232  
    S5‑246232 CR Rel-17 TS 32.422 Corrections for MDT NEC CR Agreement No
Yes
 		agreed No   S5‑245869
6.3.14 Other S5‑245236 Discussion on improvements of creating class diagram Nokia, Nokia Shanghai Bell discussion Endorsement Yes
Yes
 		revised No S5‑246233  
    S5‑246233 Discussion on improvements of creating class diagram Nokia, Nokia Shanghai Bell discussion Endorsement No
Yes
 		endorsed No   S5‑245236
    S5‑245310 Rel-16 CR TS 28.541 Align allowed value for ueAccProbabilityDist Huawei CR Approval Yes
Yes
 		agreed No    
    S5‑245311 Rel-17 CR TS 28.541 Align allowed value for ueAccProbabilityDist Huawei CR Approval Yes
YesTEI16?
 		revised No S5‑246234  
    S5‑246234 Rel-17 CR TS 28.541 Align allowed value for ueAccProbabilityDist Huawei CR Approval No
Yes
 		agreed No   S5‑245311
    S5‑245312 Rel-18 CR TS 28.541 Align allowed value for ueAccProbabilityDist Huawei CR Approval Yes
Yes
 		agreed No    
    S5‑245313 Rel-19 CR TS 28.541 Align allowed value for ueAccProbabilityDist Huawei CR Approval Yes
Yes
 		agreed No    
    S5‑245502 Rel-17 CR 28.537 Clarification of external management data Nokia CR Approval Yes
Yes
 		not pursued No    
    S5‑245503 Rel-18 CR 28.537 Clarification of external management data Nokia CR Approval Yes
Yes
 		not pursued No    
    S5‑246235 Rel-19 CR 28.537 Clarification of external management data Nokia CR Approval No
Yes
 		agreed No    
    S5‑245504 Rel-17 CR 28.537 Correction of requirement labels Nokia CR Approval Yes
YesEricsson disagreed, it's not FASMO
 		not pursued No    
    S5‑245505 Rel-18 CR 28.537 Clarification of management data and subgroups of it Nokia CR Approval Yes
YesEricsson disagreed, it's not FASMO
 		not pursued No    
    S5‑245606 Rel-16 CR TS 28.536 Fix issues in SLS Assurance Procedure Huawei CR Agreement Yes
Yes
 		agreed No    
    S5‑245607 Rel-17 CR TS 28.536 Fix issues in SLS Assurance Procedure Huawei CR Agreement Yes
Yes
 		agreed No    
    S5‑245608 Rel-18 CR TS 28.536 Fix issues in SLS Assurance Procedure Huawei CR Agreement Yes
Yes
 		agreed No    
    S5‑245673 Rel-18 TS 28.623 Correction to AreaScope YANG Stage 3 only Ericsson-LG Co., LTD CR Approval Yes
Yes
 		withdrawn Yes    
    S5‑245680 Rel-17 TS 28.623 Correction to AreaScope YANG Stage 3 only Ericsson-LG Co., LTD CR Approval Yes
Yes
 		withdrawn Yes    
    S5‑245682 Rel-16 TS 28.623 Correction to AreaScope YANG Stage 3 only Ericsson-LG Co., LTD CR Approval No
Yes
 		withdrawn Yes    
    S5‑245683 Rel-19 TS 28.623 Correction to AreaScope YANG Stage 3 only Ericsson-LG Co., LTD CR Approval Yes
Yes
 		withdrawn Yes    
    S5‑245727 Rel-17 CR TS 28.622 Correction of undefined data types Ericsson India Private Limited CR Agreement Yes
Yes
 		revised No S5‑246236  
    S5‑246236 Rel-17 CR TS 28.622 Correction of undefined data types Ericsson India Private Limited CR Agreement No
Yes
 		agreed No   S5‑245727
    S5‑245729 Rel-18 CR TS 28.622 Correction of undefined data types Ericsson India Private Limited CR Agreement Yes
Yes
 		revised No S5‑246237  
    S5‑246237 Rel-18 CR TS 28.622 Correction of undefined data types Ericsson India Private Limited CR Agreement No
Yes
 		agreed No   S5‑245729
    S5‑245739 Discussion on simplification ACCL model Ericsson, Deutsche Telekom discussion Endorsement Yes
Yes
 		noted No    
    S5‑245740 Rel-17 CR TS 28.536 Correcting ACCL class diagram and AssuranceGoal description Ericsson, Deutsche Telekom CR Approval Yes
Yes
 		not pursued No    
    S5‑245741 Rel-18 CR TS 28.536 Correcting ACCL class diagram and AssuranceGoal description Ericsson, Deutsche Telekom CR Agreement Yes
Yes
 		not pursued No    
    S5‑245742 Rel-17 CR 28.536 Clarify ACCL and AssurancGoal constraints Ericsson, Deutsche Telekom CR Approval Yes
Yes
 		not pursued No    
    S5‑245743 Rel-18 CR 28.536 Clarify ACCL and AssurancGoal constraints Ericsson, Deutsche Telekom CR Agreement Yes
Yes
 		not pursued No    
    S5‑245798 Rel-17 CR TS 28.530 Fix network slice related aspects Ericsson Limited CR Agreement Yes
Yes
 		revised No S5‑246238  
    S5‑246238 Rel-17 CR TS 28.530 Fix network slice related aspects Ericsson Limited CR Agreement No
Yes
 		agreed No   S5‑245798
    S5‑245799 Rel-18 CR TS 28.530 Fix network slice related aspects Ericsson Limited CR Agreement Yes
Yes
 		revised No S5‑246239  
    S5‑246239 Rel-18 CR TS 28.530 Fix network slice related aspects Ericsson Limited CR Agreement No
Yes
 		agreed No   S5‑245799
    S5‑245800 Rel-17 CR TS 28.532 Clarify only-system-created behaviour for ProvMnS Ericsson Inc. CR Approval Yes
YesNokia disagreed
 		not pursued No    
    S5‑245801 Rel-18 CR TS 28.532 Clarify only-system-created behaviour for ProvMnS Ericsson Inc. CR Agreement Yes
Yes
 		agreed No    
6.4 Rel-18 Maintenance and Rel-19 small Enhancements                      
6.4.1 Self-Configuration of RAN NEs                      
6.4.2 Management Data Analytics phase 2                      
6.4.3 AI/ML management S5‑245225 Rel-18 CR TS 28.105 Clarify the Usage of mLModelRef and mLModelCoordinationGroupRef ZTE Corporation CR Agreement Yes
YesEricsson & Nokia offline comments Don't new attributes for the 2. & 3. change.
 		revised No S5‑246135  
    S5‑246135 Rel-18 CR TS 28.105 Clarify the Usage of mLModelRef and mLModelCoordinationGroupRef ZTE Corporation CR Agreement No
Yes
 		not pursued No   S5‑245225
    S5‑245226 Rel-18 CR TS 28.105 Clarify the Usage of mLModelRef and mLModelCoordinationGroupRef ZTE Corporation CR Agreement Yes
Yessame as 5225
 		revised No S5‑246136  
    S5‑246136 Rel-18 CR TS 28.105 Clarify the Usage of mLModelRef and mLModelCoordinationGroupRef ZTE Corporation CR Agreement No
Yes
 		not pursued No   S5‑245226
    S5‑245234 Rel-18 CR TS 28.105 AIML Terminology Alignment ZTE Corporation CR Agreement Yes
Yes
 		agreed No    
    S5‑245235 Rel-18 CR TS 28.105 AIML Terminology Alignment ZTE Corporation CR Agreement Yes
Yesreissued as S5-246137 because of wrong title
 		revised No    
    S5‑246137 Rel-19 CR TS 28.105 AIML Terminology Alignment ZTE Corporation CR Agreement No
Yes
 		agreed No    
    S5‑245314 Rel-18 CR TS 28.105 correct the areNewTrainingDataUsed attributes Huawei CR Agreement Yes
Yes
 		revised No S5‑246279  
    S5‑246279 Rel-18 CR TS 28.105 correct the areNewTrainingDataUsed attributes Huawei CR Agreement No
Yes
 		agreed No   S5‑245314
    S5‑245315 Rel-19 CR TS 28.105 correct the areNewTrainingDataUsed attributes Huawei CR Agreement Yes
Yes
 		revised No S5‑246138  
    S5‑246138 Rel-19 CR TS 28.105 correct the areNewTrainingDataUsed attributes Huawei CR Agreement No
Yes
 		agreed No   S5‑245315
    S5‑245690 Rel-19 TS 28.541Correct AIML associations Ericsson-LG Co., LTD CR Agreement Yes
Yes
 		agreed No   S5‑244882
    S5‑245720 Rel-18 CR TS 28.105 Corrections to AIML functionalities management scenarios Nokia CR Agreement Yes
Yes
 		not pursued No    
    S5‑245723 Rel-19 CR TS 28.105 Corrections to AIML functionalities management scenarios Nokia CR Agreement Yes
Yesoffline comments from Nokia
 		not pursued No    
    S5‑245737 Rel 18 CR TS 28.105 Fix modelPerformanceValidation attribute Ericsson CR Agreement Yes
Yes
 		revised No S5‑246139  
    S5‑246139 Rel 18 CR TS 28.105 Fix modelPerformanceValidation attribute Ericsson CR Agreement No
Yesoffline comments from Nokia
 		revised No S5‑246280 S5‑245737
    S5‑246280 Rel 18 CR TS 28.105 Fix modelPerformanceValidation attribute Ericsson CR Agreement No
Yes
 		agreed No   S5‑246139
    S5‑245761 Rel 19 CR TS 28.105 Fix modelPerformanceValidation attribute Ericsson CR Agreement Yes
Yes
 		revised No S5‑246140  
    S5‑246140 Rel 19 CR TS 28.105 Fix modelPerformanceValidation attribute Ericsson CR Agreement No
Yes
 		revised No S5‑246281 S5‑245761
    S5‑246281 Rel 19 CR TS 28.105 Fix modelPerformanceValidation attribute Ericsson CR Agreement No
Yes
 		agreed No   S5‑246140
    S5‑245863 CR Rel-19 TS 28.105 add missing terms NEC, Intel CR Agreement Yes
YesCat. F->A ! this is a mirror
 		revised No S5‑246141  
    S5‑246141 CR Rel-19 TS 28.105 add missing terms NEC, Intel CR Agreement No
Yesd1
 		revised No S5‑246290 S5‑245863
    S5‑246290 CR Rel-19 TS 28.105 add missing terms NEC, Intel CR Agreement No
Yes
 		agreed No   S5‑246141
    S5‑245864 CR Rel-18 TS 28.105 add missing terms NEC, Intel CR Agreement Yes
Yes
 		revised No S5‑246142  
    S5‑246142 CR Rel-18 TS 28.105 add missing terms NEC, Intel CR Agreement No
Yes
 		revised No S5‑246291 S5‑245864
    S5‑246291 CR Rel-18 TS 28.105 add missing terms NEC, Intel CR Agreement No
Yes
 		agreed No   S5‑246142
6.4.4 Intent driven Management Service for mobile network phase 2 S5‑245255 Rel-18 CR TS 28.312 Correct issues for targetAssuranceTimeContext and pLMNContext Huawei CR Agreement Yes
Yes
 		agreed No    
    S5‑245437 Rel-18 CR TS 28.312 intent definition clarification Nokia CR Approval Yes
Yes
 		revised No S5‑246188  
    S5‑246188 Rel-18 CR TS 28.312 intent definition clarification Nokia CR Approval No
Yesd1
 		agreed No   S5‑245437
    S5‑245441 Rel-18 CR TS 28.312 intent termination deadline Nokia, Nokia Shanghai Bell CR Approval Yes
YesB->C Rel-19 instead; come back at the next meeting Ericsson: questioned whether these additions are needed
 		not pursued No    
    S5‑245754 Rel-18 CR TS 28.312 Fix stage 2 type definition of infeasibilityReason Ericsson, Deutsche Telekom CR Approval Yes
Yes
 		revised No S5‑246144  
    S5‑246144 Rel-18 CR TS 28.312 Fix stage 2 type definition of infeasibilityReason Ericsson, Deutsche Telekom CR Approval No
Yes
 		agreed No   S5‑245754
    S5‑245764 Rel 19 CR TS 28.312 Remove Support Qualifier from attribute constraints Ericsson CR Approval Yes
Yes
 		agreed No    
6.4.5 Service based management architecture S5‑245399 Rel-18 CR 28.111 Add missing definition of Alarming Condition Ericsson Hungary Ltd CR Approval Yes
Yes
 		agreed No    
    S5‑245496 Rel-18 CR 28.111 Add numerical values for probable cause Ericsson Hungary Ltd, Deutsche Telekom, AT&T, Huawei, NTT DOCOMO, China Mobile, China Unicom, China Telecom, Vodafone, Verizon, KDDI CR Approval Yes
Yes+KDDI
 		revised No S5‑246145 S5‑244887
    S5‑246145 Rel-18 CR 28.111 Add numerical values for probable cause Ericsson Hungary Ltd, Deutsche Telekom, AT&T, Huawei, NTT DOCOMO, China Mobile, China Unicom, China Telecom, Vodafone, Verizon, KDDI CR Approval No
Yes
 		agreed No   S5‑245496
    S5‑245736 Rel-18 CR TS 28.622 Rapporteur cleanup Ericsson India Private Limited CR Agreement Yes
Yes[29]=[30] Ericsson: every new spec going forward should follow the current guideline Disussion about changing the reference version.
 		revised No S5‑246146  
    S5‑246146 Rel-18 CR TS 28.622 Rapporteur cleanup Ericsson India Private Limited CR Agreement No
Yes
 		agreed No   S5‑245736
    S5‑245762 Rel-19 CR TS 28.622 Rapporteur cleanup Ericsson India Private Limited CR Agreement Yes
Yes
 		revised No S5‑246147  
    S5‑246147 Rel-19 CR TS 28.622 Rapporteur cleanup Ericsson India Private Limited CR Agreement No
Yes
 		agreed No   S5‑245762
6.4.6 Network slicing provisioning rules                      
6.4.7 Network slice provisioning enhancement                      
6.4.8 Management of Trace/MDT phase 2 S5‑245510 Rel-18 CR 28.622 Corrections for 5GC UE level measurements in TraceJob IOC Nokia CR Approval Yes
Yes
 		revised No S5‑246148  
    S5‑246148 Rel-18 CR 28.622 Corrections for 5GC UE level measurements in TraceJob IOC Nokia CR Approval No
Yesd1
 		agreed No   S5‑245510
    S5‑245511 Rel-19 CR 28.622 Corrections for 5GC UE level measurements in TraceJob IOC Nokia CR Approval Yes
Yes4.4.1 should disappear
 		revised No S5‑246149  
    S5‑246149 Rel-19 CR 28.622 Corrections for 5GC UE level measurements in TraceJob IOC Nokia CR Approval No
Yesd1
 		agreed No   S5‑245511
6.4.9 5G performance measurements and KPIs phase 3 S5‑245551 Resubmitted clarification of Measured UE Identifier in the measurement template Intel, Ericsson, Nokia CR Agreement Yes
Yes
 		revised No S5‑245778  
    S5‑245636 Rel-19 CR 28.554 Energy consumption per node type for NwSlice Ericsson CR Agreement Yes
Yesoffline comments from Nokia. Huawei did not agree.
 		not pursued No    
    S5‑245637 Rel-19 CR 28.554 Energy efficiency per node type for NwSlice Ericsson CR Agreement Yes
Yessame as 5636
 		not pursued No    
    S5‑245638 Rel-19 CR 28.554 Energy consumption per SMSF for NwSlice Ericsson CR Agreement Yes
Yessame as 5636
 		not pursued No    
    S5‑245699 Rel-18 CR 28.622 resolving inconsistencies common-measurements Samsung R&D Institute India CR Agreement Yes
YesEricsson: work together to find a better solution. Will be presented again next time.
 		not pursued No    
    S5‑245700 Rel-19 CR 28.622 resolving inconsistencies common-measurements Samsung R&D Institute India CR Agreement Yes
YesWIC AdNRM_Ph3->AdNRM_ph2
 		not pursued No    
    S5‑245701 Rel-18 CR 28.623 resolving inconsistencies common-measurements Samsung R&D Institute India CR Agreement Yes
YesRAN x
 		not pursued No    
    S5‑245702 Rel-19 CR 28.623 resolving inconsistencies common-measurements Samsung R&D Institute India CR Agreement Yes
YesRAN x AdNRM_Ph3-> AdNRM_ph2
 		not pursued No    
    S5‑245778 Resubmitted clarification of Measured UE Identifier in the measurement template Intel, Ericsson, Nokia CR Agreement Yes
Yes
 		revised No S5‑246150 S5‑245551
    S5‑246150 Resubmitted clarification of Measured UE Identifier in the measurement template Intel, Ericsson, Nokia CR Agreement No
Yes
 		agreed No   S5‑245778
6.4.10 Enhancement of QoE Measurement Collection S5‑245223 Rel-18 CR TS 28.405 Correct the procedure description of management based activation in NR ZTE Corporation CR Approval Yes
YesEricsson: clause renumbering! MCC: not allowed
 		revised No S5‑246155  
    S5‑246155 Rel-18 CR TS 28.405 Correct the procedure description of management based activation in NR ZTE Corporation CR Approval No
Yesd1 Ericsson needed more time.
 		agreed No   S5‑245223
    S5‑245224 Rel-19 CR TS 28.405 Correct the procedure description of management based activation in NR ZTE Corporation CR Approval Yes
YesEricsson: clause renumbering! MCC: not allowed
 		revised No S5‑246156  
    S5‑246156 Rel-19 CR TS 28.405 Correct the procedure description of management based activation in NR ZTE Corporation CR Approval No
Yesd1 Ericsson needed more time.
 		agreed No   S5‑245224
6.4.11 Additional NRM features phase 2 S5‑245240 Rel-18 CR TS 28.541 Correct both stage2 and stage3 for NRNetwork and EUtraNetwork NRM fragement Huawei CR Agreement Yes
Yes
 		agreed No    
    S5‑245241 Rel-19 CR TS 28.541 Correct both stage2 and stage3 for NRNetwork and EUtraNetwork NRM fragement Huawei CR Agreement Yes
Yes
 		agreed No    
    S5‑245319 Rel-18 CR TS 28.541 Correct the reference of alarm notifications Huawei CR Agreement Yes
Yes
 		revised No S5‑246157  
    S5‑246157 Rel-18 CR TS 28.541 Correct the reference of alarm notifications Huawei CR Agreement No
Yesd1
 		agreed No   S5‑245319
    S5‑245320 Rel-19 CR TS 28.541 Correct the reference of alarm notifications Huawei CR Agreement Yes
Yes
 		revised No S5‑246158  
    S5‑246158 Rel-19 CR TS 28.541 Correct the reference of alarm notifications Huawei CR Agreement No
Yesd1
 		agreed No   S5‑245320
6.4.12 Management Aspects related to NWDAF                      
6.4.13 Enhanced Edge Computing Management S5‑245456 Rel-18 CR 28.538 CR implemention issue for reservationJobRef Huawei CR Agreement Yes
Yes
 		agreed No    
    S5‑245457 Rel-19 CR 28.538 CR implemention issue for reservationJobRef Huawei CR Agreement Yes
Yes
 		revised No S5‑246159  
    S5‑246159 Rel-19 CR 28.538 CR implemention issue for reservationJobRef Huawei CR Agreement No
Yesd1
 		agreed No   S5‑245457
6.4.14 Management Aspect of 5GLAN                      
6.4.15 Management Aspects of NTN S5‑245670 Correct NRM diagram and remove not used imported definitions Ericsson CR Approval Yes
Yes
 		not pursued No    
6.4.16 methodology for deprecation                      
6.4.17 Management of cloud-native Virtualized Network Functions                      
6.4.18 Management Aspects of 5G Network Sharing Phase2 S5‑245851 Rel-18 CR TS28.552 Recover bulk wrongly voided clauses for conflict CR0482 and 0497 in MANS_ph2 ZTE Corporation CR Approval Yes
Yes
 		revised No S5‑246161  
    S5‑246161 Rel-18 CR TS28.552 Recover bulk wrongly voided clauses for conflict CR0482 and 0497 in MANS_ph2 ZTE Corporation, China Unicom, Ericsson CR Approval No
Yes
 		agreed No   S5‑245851
    S5‑245852 Rel-19 CR TS28.552 Recover bulk wrongly voided clauses for conflict CR0482 and 0497 in MANS_ph2 ZTE Corporation CR Approval Yes
Yes
 		revised No S5‑246162  
    S5‑246162 Rel-19 CR TS28.552 Recover bulk wrongly voided clauses for conflict CR0482 and 0497 in MANS_ph2 ZTE Corporation, China Unicom, Ericsson CR Approval No
Yes
 		agreed No   S5‑245852
6.4.19 Management Aspects of URLLC                      
6.4.20 Management aspects of 5G system supporting satellite backhaul                      
6.4.21 Access control for management service                      
6.4.22 Enhancements of EE for 5G Phase 2                      
6.4.23 Management of non-public networks phase 2                      
6.4.24 Network and Service Operations for Energy Utilities S5‑245766 Rel 19 CR TS 28.318 implement readOnly attributes for openAPI Ericsson CR Approval Yes
Yesmerged into 6175
 		merged No    
6.4.25 Rel-18 CAT B/C alignment CR(s) due to the work led by other 3GPP Working Groups S5‑245278 Rel-18 CR to TS 28.623 Correct wrong CR number in managed element YANG file Ericsson (China) CR   Yes
Yeskeep open
 		agreed No    
    S5‑245279 Rel-19 CR to TS 28.623 Correct wrong CR number in managed element YANG file Ericsson (China) CR Agreement Yes
Yeskeep open
 		agreed No    
    S5‑245624 Rel-18 CR TS 28.541 OpenAPI SS Stage 3 for energy cost mapping rule Nokia CR Agreement Yes
YesF->B +Huawei
 		revised No S5‑246163  
    S5‑246163 Rel-18 CR TS 28.541 OpenAPI SS Stage 3 for energy cost mapping rule Nokia, Huawei CR Agreement No
Yes
 		agreed No   S5‑245624
    S5‑245625 Rel-19 CR TS 28.541 OpenAPI SS Stage 3 for energy cost mapping rule Nokia CR Agreement Yes
Yes+Huawei
 		revised No S5‑246164  
    S5‑246164 Rel-19 CR TS 28.541 OpenAPI SS Stage 3 for energy cost mapping rule Nokia, Huawei CR Agreement No
Yes
 		agreed No   S5‑245625
    S5‑245626 Rel-18 CR TS 28.541 Corrections to energy cost mapping rule description Nokia CR Agreement Yes
YesF->B Huawei: editorial enhancement Ericsson: concern on average window size +Huawei
 		revised No S5‑246165  
    S5‑246165 Rel-18 CR TS 28.541 Corrections to energy cost mapping rule description Nokia, Huawei, Ericsson CR Agreement No
Yesd1
 		agreed No   S5‑245626
    S5‑245627 Rel-19 CR TS 28.541 Corrections to energy cost mapping rule description Nokia CR Approval Yes
Yessame as 5626 +Huawei
 		revised No S5‑246166  
    S5‑246166 Rel-19 CR TS 28.541 Corrections to energy cost mapping rule description Nokia, Huawei, Ericsson CR Approval No
Yesd1
 		agreed No   S5‑245627
6.4.26 Rel-18 CAT B/C SA5 internal alignment and other CAT F CR(s)                      
6.4.27 OAM Rel-19 small enhancements S5‑245246 Rel-19 CR TS 28.105 Implement readonly attributes for openAPI SS Huawei CR Agreement Yes
Yes+Ericsson
 		revised No S5‑246167  
    S5‑246167 Rel-19 CR TS 28.105 Implement readonly attributes for openAPI SS Huawei, Ericsson CR Agreement No
Yes
 		agreed No   S5‑245246
    S5‑245247 Rel-19 CR TS 28.317 Implement readonly attributes for openAPI SS Huawei CR Agreement Yes
Yes+Ericsson
 		revised No S5‑246168  
    S5‑246168 Rel-19 CR TS 28.317 Implement readonly attributes for openAPI SS Huawei, Ericsson CR Agreement No
Yes
 		agreed No   S5‑245247
    S5‑245248 Rel-19 CR TS 28.312 Implement readonly attributes for openAPI SS Huawei CR Agreement Yes
Yes
 		revised No S5‑246169  
    S5‑246169 Rel-19 CR TS 28.312 Implement readonly attributes for openAPI SS Huawei, Ericsson CR Agreement No
Yes
 		agreed No   S5‑245248
    S5‑245249 Rel-19 CR TS 28.111 Implement readonly attributes for openAPI SS Huawei CR Agreement Yes
Yes+Ericsson
 		revised No S5‑246170  
    S5‑246170 Rel-19 CR TS 28.111 Implement readonly attributes for openAPI SS Huawei, Ericsson CR Agreement No
Yes
 		agreed No   S5‑245249
    S5‑245250 Rel-19 CR TS 28.623 Implement readonly attributes for openAPI SS Huawei CR Agreement Yes
Yes+Ericsson Nokia: need more time
 		revised No S5‑246171  
    S5‑246171 Rel-19 CR TS 28.623 Implement readonly attributes for openAPI SS Huawei, Ericsson CR Agreement No
Yes
 		agreed No   S5‑245250
    S5‑245251 Rel-19 CR TS 28.104 Implement readonly attributes for openAPI SS Huawei CR Agreement Yes
Yes+Ericsson
 		revised No S5‑246172  
    S5‑246172 Rel-19 CR TS 28.104 Implement readonly attributes for openAPI SS Huawei, Ericsson CR Agreement No
Yes
 		agreed No   S5‑245251
    S5‑245252 Rel-19 CR TS 28.538 Implement readonly attributes for openAPI SS Huawei CR Agreement Yes
Yes+Ericsson Huawei: keep duration
 		revised No S5‑246173  
    S5‑246173 Rel-19 CR TS 28.538 Implement readonly attributes for openAPI SS Huawei, Ericsson CR Agreement No
Yes
 		agreed No   S5‑245252
    S5‑245253 Rel-19 CR TS 28.536 Implement readonly attributes for openAPI SS Huawei, Ericsson CR Agreement Yes
Yes
 		revised No S5‑246174  
    S5‑246174 Rel-19 CR TS 28.536 Implement readonly attributes for openAPI SS Huawei, Ericsson CR Agreement No
Yes
 		agreed No   S5‑245253
    S5‑245254 Rel-19 CR TS 28.318 Implement readonly attributes for openAPI SS Huawei CR Agreement Yes
Yes5766 merge into here
 		revised No S5‑246175  
    S5‑246175 Rel-19 CR TS 28.318 Implement readonly attributes for openAPI SS Huawei, Ericsson CR Agreement No
Yes
 		agreed No   S5‑245254
    S5‑245321 Rel-19 CR TS 28.541 Add the inheritance information for NRECMappingRule IOC and Beam IOC. Huawei CR Agreement Yes
Yes
 		agreed No    
    S5‑245397 Rel-19 CR 32.156 Specify Escaping for DN type Ericsson Hungary Ltd CR Approval Yes
YesQuestion from Nokia about the reference to 32.300, still needs discussion. related to 5535-6 Delayed.
 		agreed No    
    S5‑245467 Enhance the isUnique property for stage 3 OpenAPI Nokia, Nokia Shanghai Bell CR Approval Yes
Yes
 		agreed No    
    S5‑245469 Clarify the Attribute property "multiplicity" for OpenAPI Nokia, Nokia Shanghai Bell CR Approval Yes
Yes
 		agreed No    
    S5‑245499 Rel-19 CR 32.158 Add design pattern for requests of data fractions Nokia CR Approval Yes
Yes
 		not pursued No    
    S5‑245500 Rel-19 CR 28.532 Add HTTP Range Request for file data reporting service Nokia CR Approval Yes
Yes
 		not pursued No    
    S5‑245533 Rel-19 CR 28.623 Clarify how to fetch YANG modules Ericsson Hungary Ltd CR Approval Yes
Yes
 		agreed No    
    S5‑245546 Rel-19 CR 28.622 Correct definition of choice Ericsson Hungary Ltd CR Approval Yes
Yes
 		agreed No    
    S5‑245547 Rel-19 CR 28.541 Correct definition of choice Ericsson Hungary Ltd CR Agreement Yes
Yes
 		agreed No    
    S5‑245631 Rel-19 CR 28.312 Enhance the isUnique property for stage 3 OpenAPI Nokia CR Agreement Yes
Yes
 		agreed No    
    S5‑245632 Rel-19 CR 28.317 Enhance the isUnique property for stage 3 OpenAPI Nokia CR Approval Yes
Yes
 		agreed No    
    S5‑245633 Rel-19 CR 28.104 Enhance the isUnique property for stage 3 OpenAPI Nokia CR Approval Yes
Yes
 		agreed No    
    S5‑245634 Rel-19 CR 28.536 Enhance the isUnique property for stage 3 OpenAPI Nokia CR Approval Yes
Yes
 		agreed No    
    S5‑245721 Rel-19 CR TS 28.623 Clarification on Real and Float data types Ericsson Hungary Ltd CR Agreement Yes
Yes
 		agreed No    
    S5‑245759 Rel-18 CR TS 28.533 Clarify phrasing in the diagram in clause 5.5 Ericsson, Deutsche Telekom CR Approval Yes
YesHuawei disagreed.
 		not pursued No    
    S5‑245763 Rel 19 CR TS 28.538 Remove Support Qualifier from attribute constraints Ericsson CR Approval Yes
Yes
 		agreed No    
    S5‑245765 Rel 19 CR TS 28.104 Remove Support Qualifier from attribute constraints Ericsson CR Agreement Yes
Yes
 		revised No S5‑246178  
    S5‑246178 Rel 19 CR TS 28.104 Remove Support Qualifier from attribute constraints Ericsson CR Agreement No
Yes
 		agreed No   S5‑245765
    S5‑245804 Rel-19 CR TS 28.541 Define new data types Ericsson Limited CR   Yes
YesNokia: stage 3 is missing.
 		not pursued No    
    S5‑245835 Rel-19 CR 32.160 Simplify YANG mapping of structured attributes Ericsson Hungary Ltd CR Approval Yes
Yesfirst agreed, then revised to change a colon.
 		revised No S5‑246184  
    S5‑246184 Rel-19 CR 32.160 Simplify YANG mapping of structured attributes Ericsson Hungary Ltd CR Approval No
Yes
 		agreed No   S5‑245835
6.19 OAM&P Rel-19 Study and Work Items                      
6.19.1 Study on AI/ML management - phase 2 S5‑245274 Rel-19 pCR TR 28.858 Add possible solutions on ML entity distributed training management CATT pCR Approval Yes
Yes
 		revised No S5‑246003 S5‑244256
    S5‑246003 Rel-19 pCR TR 28.858 Add possible solutions on ML entity distributed training management CATT pCR Approval No
Yes
 		approved No   S5‑245274
    S5‑245275 Rel-19 pCR TR 28.858 Update use case on ML entity distributed training CATT pCR Approval Yes
YesE///: who is responsible for the splitting?
 		revised No S5‑246002  
    S5‑246002 Rel-19 pCR TR 28.858 Update use case on ML entity distributed training CATT pCR Approval No
Yes
 		approved No   S5‑245275
    S5‑245299 Rel-19 pCR TR 28.858 add the use case of Managing NWDAF inference function Huawei pCR Approval Yes
Yesdiscussion involving Huawei, NEC, Nokia, Ericsson about removing federated learning
 		revised No S5‑245999  
    S5‑245999 Rel-19 pCR TR 28.858 add the use case of Managing NWDAF inference function Huawei pCR Approval No
YesNokia objects
 		noted No   S5‑245299
    S5‑245300 Rel-19 pCR TR 28.858 add use case of managing NG-RAN AIML-based Network Slicing Huawei pCR Approval Yes
Yescomments about RAN3 having already use cases.
 		revised No S5‑246000  
    S5‑246000 Rel-19 pCR TR 28.858 add use case of managing NG-RAN AIML-based Network Slicing Huawei pCR Approval No
YesNokia objected
 		noted No   S5‑245300
    S5‑245301 Rel-19 pCR TR 28.858 add use case of managing NG-RAN AIML-based Coverage and Capacity Optimization Huawei pCR Approval Yes
Yes
 		revised No S5‑246001  
    S5‑246001 Rel-19 pCR TR 28.858 add use case of managing NG-RAN AIML-based Coverage and Capacity Optimization Huawei pCR Approval No
YesNokia objects
 		noted No   S5‑245301
    S5‑245302 Rel-19 pCR TR 28.858 add the use case of Data collection for UE-side model training Huawei pCR Approval Yes
Yesdiscuss with S5-245980 merged into 6287
 		merged No    
    S5‑245303 Rel-19 pCR TR 28.858 Update the use case of ML training data statistics Huawei pCR Approval Yes
Yes
 		revised No S5‑245993  
    S5‑245993 Rel-19 pCR TR 28.858 Update the use case of ML training data statistics Huawei pCR Approval No
Yes
 		approved No   S5‑245303
    S5‑245304 Rel-19 pCR TR 28.858 Update the use case of ML model training for multiple contexts Huawei pCR Approval Yes
Yes
 		revised No S5‑246259  
    S5‑246259 Rel-19 pCR TR 28.858 Update the use case of ML model training for multiple contexts Huawei pCR Approval No
Yes
 		approved No   S5‑245304
    S5‑245305 Rel-19 pCR TR 28.858 Update the use case of Managing ML Model Transfer in RAN Huawei pCR Approval Yes
YesDT and Ericsson supported clarification from RAN. NEC will draft LS S5-5997 in the next meeting. merge into 5998.
 		merged No    
    S5‑245997 Clarification on model transfer from OEM Model transfer/delivery to UE SA5 LS out Approval No
Yeswrong doc
 		withdrawn Yes    
    S5‑246292 LS on AI/ML Model transfer/delivery to UE SA5 LS out Approval No
Yes
 		approved No    
    S5‑245306 Rel-19 pCR TR 28.858 add use cases, requirements for network performance management of reinforcement learning Huawei pCR Approval Yes
Yesmerged into 5461->6255
 		merged No    
    S5‑245307 Rel-19 pCR TR 28.858 add possible solutions and evaluations for reinforcement learning management Huawei pCR Approval Yes
Yesmerged into 6255
 		merged No    
    S5‑245308 Rel-19 pCR TR 28.858 add use cases, requirements for conflict management of reinforcement learning Huawei pCR Approval Yes
Yes
 		revised No S5‑246257  
    S5‑246257 Rel-19 pCR TR 28.858 add use cases, requirements for conflict management of reinforcement learning Huawei, Nokia, ZTE pCR Approval No
Yes
 		approved No   S5‑245308
    S5‑245309 Rel-19 pCR TR 28.858 add possible solutions for conflict management of reinforcement learning Huawei pCR Approval Yes
Yes
 		revised No S5‑246256  
    S5‑246256 Rel-19 pCR TR 28.858 add possible solutions for conflict management of reinforcement learning Huawei, Nokia pCR Approval No
Yes
 		approved No   S5‑245309
    S5‑245395 Rel-19 pCR TR 28.858 add solution for AI emulation China Mobile pCR Approval Yes
Yes
 		revised No S5‑245990  
    S5‑245990 Rel-19 pCR TR 28.858 add solution for AI emulation China Mobile, Nokia pCR Approval No
Yes
 		approved No   S5‑245395
    S5‑245416 Rel-19 pCR TR 28.858 improve ML-knowledge-based transfer learning use case Nokia pCR Approval Yes
Yes
 		revised No S5‑245994  
    S5‑245994 Rel-19 pCR TR 28.858 improve ML-knowledge-based transfer learning use case Nokia pCR Approval No
Yes
 		approved No   S5‑245416
    S5‑245460 Rel-19 pCR TR 28.858 Update the Description of Management of Reinforcement Learning Use Case ZTE Corporation pCR Approval Yes
Yes
 		revised No S5‑246254  
    S5‑246254 Rel-19 pCR TR 28.858 Update the Description of Management of Reinforcement Learning Use Case ZTE Corporation pCR Approval No
Yes
 		approved No   S5‑245460
    S5‑245461 Rel-19 pCR TR 28.858 Add New Requirements and Possible Solution to the Reinforcement Learning Use Case ZTE Corporation pCR Approval Yes
Yes
 		revised No S5‑246255  
    S5‑246255 Rel-19 pCR TR 28.858 Add New Requirements and Possible Solution to the Reinforcement Learning Use Case ZTE Corporation pCR Approval No
Yes
 		approved No   S5‑245461
    S5‑245462 Rel-19 pCR TR 28.858 Add Possible Solution, Evaluation and Conclusion for Managing ML Model Transfer in RAN ZTE Corporation pCR Approval Yes
Yeseditorial comments. E/// agreed with Huawei that the evaluation needs an update. Samsung: modal loading does not support OAM use case. merged into S5-245998
 		merged No    
    S5‑245463 Rel-19 pCR TR 28.858 Add Term and Concept for HFL and VFL ZTE Corporation pCR Approval Yes
Yesinto 6264
 		merged No    
    S5‑245464 Rel-19 pCR TR 28.858 Update Description and Add New Requirements to Management of Federated Learning Use Case ZTE Corporation pCR Approval Yes
YesDT: what is 'maintain the client'? Revise to add HFL.
 		revised No S5‑246004  
    S5‑246004 Rel-19 pCR TR 28.858 Update Description and Add New Requirements to Management of Federated Learning Use Case ZTE Corporation pCR Approval No
Yes
 		approved No   S5‑245464
    S5‑245465 Rel-19 pCR TR 28.858 Add Possible Solution for Management of Federated Learning ZTE Corporation pCR Approval Yes
Yesmerged into 6248
 		merged No    
    S5‑245479 pCR 28.858 Updates to Coordination between the ML capabilities Nokia, Nokia Shanghai Bell pCR Approval Yes
YesE/// supports NEC DT suggested a more sophisticated approach.
 		revised No S5‑245991  
    S5‑245991 pCR 28.858 Updates to Coordination between the ML capabilities Nokia, Nokia Shanghai Bell pCR Approval No
Yes
 		approved No   S5‑245479
    S5‑245480 Rel-19 pCR TR 28.858 Add evaluation for ML model confidence Nokia pCR Approval Yes
Yes
 		revised No S5‑246261  
    S5‑246261 Rel-19 pCR TR 28.858 Add evaluation for ML model confidence Nokia pCR Approval No
Yes
 		approved No   S5‑245480
    S5‑245482 Rel-19 pCR TR 28.858 Add solution for ML remedial action management Nokia pCR Approval Yes
Yes
 		revised No S5‑246262  
    S5‑246262 Rel-19 pCR TR 28.858 Add solution for ML remedial action management Nokia pCR Approval No
Yes
 		approved No   S5‑245482
    S5‑245483 Rel-19 pCR TR 28.858 Add solution for Management of Reinforcement Learning Nokia pCR Approval Yes
Yesinto 6355
 		merged No    
    S5‑245484 Rel-19 pCR TR 28.858 Add solution for ML training aspects of sustainable AIML Nokia pCR Approval Yes
Yes
 		revised No S5‑246265  
    S5‑246265 Rel-19 pCR TR 28.858 Add solution for ML training aspects of sustainable AIML Nokia pCR Approval No
Yesrevised further
 		revised No S5‑246285 S5‑245484
    S5‑246285 Rel-19 pCR TR 28.858 Add solution for ML training aspects of sustainable AIML Nokia, ZTE pCR Approval No
Yes
 		approved No   S5‑246265
    S5‑245485 Rel-19 pCR TR 28.858 Add solution for ML inference aspects of sustainable AIML Nokia pCR Approval Yes
Yes
 		revised No S5‑245992  
    S5‑245992 Rel-19 pCR TR 28.858 Add solution for ML inference aspects of sustainable AIML Nokia pCR Approval No
Yeslate comments
 		revised No S5‑246284 S5‑245485
    S5‑246284 Rel-19 pCR TR 28.858 Add solution for ML inference aspects of sustainable AIML Nokia, ZTE pCR Approval No
Yes
 		approved No   S5‑245992
    S5‑245487 Rel-19 pCR TR 28.858 Add use case to support efficient retraining Nokia pCR Approval Yes
Yes
 		revised No S5‑246278  
    S5‑246278 Rel-19 pCR TR 28.858 Add use case to support efficient retraining Nokia pCR Approval No
Yes
 		noted No   S5‑245487
    S5‑245489 Rel-19 pCR TR 28.858 AIML prediction latency Nokia pCR Approval Yes
Yes
 		revised No S5‑246263  
    S5‑246263 Rel-19 pCR TR 28.858 AIML prediction latency Nokia, ZTE pCR Approval No
Yes
 		approved No   S5‑245489
    S5‑245490 Discussion on ML explainability Nokia, Verizon discussion Discussion Yes
YesProposal 1 and 2
 		noted No    
    S5‑245491 Rel-19 pCR TR 28.858 ML explainability Nokia, Verizon pCR Approval Yes
Yes
 		revised No S5‑245719  
    S5‑245492 Rel-19 pCR TR 28.858 Add evaluation for ML model training for multiple contexts Nokia pCR Approval Yes
Yes
 		revised No S5‑246260  
    S5‑246260 Rel-19 pCR TR 28.858 Add evaluation for ML model training for multiple contexts Nokia pCR Approval No
Yes
 		approved No   S5‑245492
    S5‑245493 pCR 28.858 Add description for GenAI HUAWEI Technologies Japan K.K. pCR Approval Yes
Yes
 		noted No    
    S5‑245531 Rel-19 pCR TR 28.858 Add Evaluation and Conclusion for Pre-training China Mobile Com. Corporation, ZTE pCR Approval Yes
Yes
 		revised No S5‑246251  
    S5‑246251 Rel-19 pCR TR 28.858 Add Evaluation and Conclusion for Pre-training China Mobile Com. Corporation, ZTE pCR Approval No
Yes5686 merged into.
 		approved No   S5‑245531
    S5‑245532 Rel-19 pCR TR 28.858 Add Evaluation and Conclusion for Fine-tuning China Mobile Com. Corporation, ZTE pCR Approval Yes
Yesbreakout 2-Q4 merge with 5861? 6249?
 		noted No    
    S5‑245552 pCR TR 28.858 Add possible solution for management of Federated Learning Intel, ZTE, Nokia, China Mobile, NEC, HUAWEI pCR Approval Yes
Yes
 		revised No S5‑245780  
    S5‑245556 pCR 28.858 Correct use of specification HUAWEI Technologies Japan K.K. pCR Approval Yes
Yes
 		revised No S5‑246253  
    S5‑246253 pCR 28.858 Correct use of specification HUAWEI Technologies Japan K.K. pCR Approval No
Yes
 		approved No   S5‑245556
    S5‑245663 Rel-19 pCR 28.858 Solution for managing ML Model in live network Samsung, AT&T pCR Agreement Yes
Yes
 		revised No S5‑245996  
    S5‑245996 Rel-19 pCR 28.858 Solution for managing ML Model in live network Samsung, AT&T pCR Agreement No
Yes
 		approved No   S5‑245663
    S5‑245681 Rel-19 pCR 28.858 Generative AI Samsung R&D Institute India pCR Agreement Yes
Yes
 		noted No    
    S5‑245685 PCR TR 28.858 Add missing Terms and abbreviations Ericsson-LG Co., LTD pCR Approval Yes
Yesmerged into 6264
 		merged No    
    S5‑245686 PCR TR 28.858 Pre-training Potential Solution and Evaluation Ericsson-LG Co., LTD pCR Approval Yes
Yesmerge 6251
 		merged No    
    S5‑245687 PCR TR 28.858 Fine-Tunning Potential Solution and Evaluation Ericsson-LG Co., LTD pCR Approval Yes
Yes
 		noted No    
    S5‑245688 PCR TR 28.858 Adding ML Authentication UseCase Ericsson-LG Co., LTD pCR Approval Yes
Yes
 		revised No S5‑246258  
    S5‑246258 PCR TR 28.858 Adding ML Authentication UseCase Ericsson-LG Co., LTD pCR Approval No
Yes
 		approved No   S5‑245688
    S5‑245719 Rel-19 pCR TR 28.858 ML explainability Nokia, Verizon, NTT DOCOMO pCR Approval Yes
Yes
 		revised No S5‑245840 S5‑245491
    S5‑245780 pCR TR 28.858 Add possible solution for management of Federated Learning Intel, ZTE, Nokia, China Mobile, NEC, HUAWEI, Ericsson pCR Approval Yes
Yesmerge 4565 into
 		revised No S5‑246248 S5‑245552
    S5‑246248 pCR TR 28.858 Add possible solution for management of Federated Learning Intel, ZTE, Nokia, China Mobile, NEC, HUAWEI, Ericsson pCR Approval No
Yes
 		approved No   S5‑245780
    S5‑245840 Rel-19 pCR TR 28.858 ML explainability Nokia, Verizon, NTT DOCOMO, Deutsche Telekom pCR Approval Yes
Yes
 		revised No S5‑246266 S5‑245719
    S5‑246266 Rel-19 pCR TR 28.858 ML explainability Nokia, Verizon, NTT DOCOMO, Deutsche Telekom pCR Approval No
Yes
 		approved No   S5‑245840
    S5‑245853 WF: Study on AI/ML management – phase 2 NEC, Intel discussion Discussion Yes
Yesrapporteur to provide more inputs for guidance
 		noted No    
    S5‑245855 pCR TR 28.858 clarifications into ML model transfer use case NEC, Intel pCR Approval Yes
Yes
 		revised No S5‑245998  
    S5‑245998 pCR TR 28.858 clarifications into ML model transfer use case NEC, Intel, Huawei, ZTE, Deutsche Telekom pCR Approval No
YesS5-245462 merged into here
 		approved No   S5‑245855
    S5‑245856 pCR TR 28.858 clarifications and corrections into ML-Knowledge-based Transfer Learning NEC, Intel pCR Approval Yes
YesDT: specific-> -ied (criteria)
 		revised No S5‑245995  
    S5‑245995 pCR TR 28.858 clarifications and corrections into ML-Knowledge-based Transfer Learning NEC, Intel pCR Approval No
Yes
 		approved No   S5‑245856
    S5‑245857 pCR TR 28.858 clarifications and corrections into AI/ML inference emulation NEC, Intel pCR Approval Yes
Yes
 		approved No    
    S5‑245858 pCR TR 28.858 add terms and abbreviations NEC, Intel pCR Approval Yes
Yes
 		revised No S5‑246264  
    S5‑246264 pCR TR 28.858 add terms and abbreviations NEC, Intel pCR Approval No
Yes
 		approved No   S5‑245858
    S5‑245859 pCR TR 28.858 add reference to TS 28.105 for Rel-19 terms and definitions NEC, Intel pCR Approval Yes
Yes
 		approved No    
    S5‑245860 pCR TR 28.858 add clarifications on ML pre-training use case NEC, Intel pCR Approval Yes
Yes
 		revised No S5‑246252  
    S5‑246252 pCR TR 28.858 add clarifications on ML pre-training use case NEC, Intel pCR Approval No
YesZTE objected.
 		noted No   S5‑245860
    S5‑245861 pCR TR 28.858 add clarifications on ML fine-tuning use case NEC, Intel pCR Approval Yes
Yes
 		revised No S5‑246250  
    S5‑246250 pCR TR 28.858 add clarifications on ML fine-tuning use case NEC, Intel pCR Approval No
YesZTE objected.
 		noted No   S5‑245861
    S5‑245862 DP Rel-18 and Rel-19 AIML related terms and definitions NEC, Intel pCR Endorsement Yes
Yesie endorsed.
 		endorsed No    
    S5‑245950 Draft TR 28.858 NEC draft TR Approval No
Yes
 		email approval No    
6.19.2 Study on Management Data Analytics (MDA) – Phase 3 S5‑245221 Rel-19 pCR TR 28.866 Add solution evaluation and conclusion for Edge computing performance analytics UC AsiaInfo pCR Approval Yes
Yes
 		approved No    
    S5‑245362 Rel-19 pCR 28.866 Remove WT-5 Huawei pCR Approval Yes
Yes
 		approved No    
    S5‑245363 Rel-19 pCR 28.866 WT alignment for control plane congestion analytics Huawei pCR Approval Yes
Yes
 		approved No    
    S5‑245364 Rel-19 pCR 28.866 Improve wording of conclusions Huawei pCR Approval Yes
YesNokia got comments +Samsung
 		revised No S5‑246035  
    S5‑246035 Rel-19 pCR 28.866 Improve wording of conclusions Huawei, Samsung pCR Approval No
Yes
 		approved No   S5‑245364
    S5‑245365 Rel-19 pCR 28.866 Editorial improvements Huawei pCR Approval Yes
Yes
 		approved No    
    S5‑245366 Presentation of TR 28.866 to SA for Approval Huawei TS or TR cover Approval Yes
Yessuggest to do it at the next meeting, insert into 6035 keep it open Nokia asked for more time.
 		noted No    
    S5‑245520 Rel-19 pCR TR 28.866 New Usecase on Management data collection recommendation for predicted failure Nokia pCR Approval Yes
Yes
 		revised No S5‑246037  
    S5‑246037 Rel-19 pCR TR 28.866 New Usecase on Management data collection recommendation for predicted failure Nokia pCR Approval No
Yesd2 Huawei has concern. Objecting.
 		noted No   S5‑245520
    S5‑245679 Rel-19 pCR 28.866 EE Conclusions Samsung, Nokia pCR Agreement Yes
YesZTE: no ES state for beams.
 		revised No S5‑246036  
    S5‑246036 Rel-19 pCR 28.866 EE Conclusions Samsung, Nokia pCR Agreement No
Yesd2
 		approved No   S5‑245679
    S5‑245955 Draft TR 28.866 Huawei draft TR Approval No
Yes
 		email approval No    
6.19.3 Study on intent driven management services for mobile network phase 3 S5‑245343 pCR TR 28.914 Rapporteur clean up Huawei pCR Approval Yes
Yes
 		approved No    
    S5‑245344 pCR TR 28.914 Add conclusion for Use case #5 Improve intent lifecycle documentation Huawei, Deutsche Telekom pCR Approval Yes
Yes
 		approved No    
    S5‑245345 CR TR 28.914 Update Use case #6 Investigate potential impacts to support natural language intents translation Huawei, Deutsche Telekom pCR Approval Yes
YesNTT DOCOMO: not clear if natural language context cannot be translated directly. Ericsson: it may be outside of scope of SA5.
 		revised No S5‑246056  
    S5‑246056 CR TR 28.914 Update Use case #6 Investigate potential impacts to support natural language intents translation Huawei, Deutsche Telekom pCR Approval No
Yesd2
 		approved No   S5‑245345
    S5‑245401 Rel-19 pCR 28.914 Rel-19 pCR TR28.914 Conclusion on negotiation and utility functions Nokia pCR Approval Yes
Yes5776 is related. ZTE & NTT DOCOMO have offline comments. +Huawei
 		revised No S5‑246054  
    S5‑246054 Rel-19 pCR 28.914 Rel-19 pCR TR28.914 Conclusion on negotiation and utility functions Nokia, Huawei pCR Approval No
Yes
 		approved No   S5‑245401
    S5‑245440 Rel-19 pCR 28.914 editorial corrections Nokia pCR Approval Yes
Yes
 		approved No    
    S5‑245667 Rel-19 pCR TR 28.914 implicit intent report subscription update Nokia pCR Approval Yes
Yesmerged into 6054
 		merged No    
    S5‑245694 pCR TR 28.914 Add Evaluation and Conclusion for Use-Case #19 NTT DOCOMO INC. pCR Approval Yes
YesZTE: what is the relationship between the new template supported requirement context and existing object context?
 		revised No S5‑246055  
    S5‑246055 pCR TR 28.914 Add Evaluation and Conclusion for Use-Case #19 NTT DOCOMO INC. pCR Approval No
Yesd2
 		approved No   S5‑245694
    S5‑245776 pCR TR 28.914 Update UC#13 evaluation and recommendation Ericsson Inc. pCR Approval Yes
Yes
 		approved No    
    S5‑245783 Presentation of TR 28.914 to SA for information Ericsson Inc., Huawei TS or TR cover Approval Yes
YesSA5 Vice Chair: we need a summary to describe the changes since last time.
 		revised No S5‑246059  
    S5‑246059 Presentation of TR 28.914 to SA for information Ericsson Inc., Huawei TS or TR cover Approval No
Yesd1 meeting nr.!
 		approved No   S5‑245783
    S5‑245784 pCR TR 28.914 Rapporteur clean-up Ericsson Inc. pCR Approval Yes
Yes'shall' is allowed in potential requirements.
 		revised No S5‑246053  
    S5‑246053 pCR TR 28.914 Rapporteur clean-up Ericsson Inc. pCR Approval No
Yes
 		approved No   S5‑245784
    S5‑245788 pCR TR 28.914 Add description of intent negotiation initiated by MnS producer China Mobile, ZTE pCR Approval Yes
YesDT: not clear which negotiation is intended. Keep open.
 		revised No S5‑246058  
    S5‑246058 pCR TR 28.914 Add description of intent negotiation initiated by MnS producer China Mobile, ZTE pCR Approval No
Yesd2
 		approved No   S5‑245788
    S5‑245791 pCR TR 28.914 Add description of intent negotiation China Mobile, ZTE pCR Approval Yes
YesSamsung: what is implicit target is not clear. Nokia: this conclusion is not needed at all.
 		revised No S5‑246057  
    S5‑246057 pCR TR 28.914 Add description of intent negotiation China Mobile, ZTE pCR Approval No
Yesd2
 		approved No   S5‑245791
    S5‑245958 Draft TR 28.914 Ericsson draft TR Approval No
Yes
 		email approval No    
6.19.4 Study on closed control loop management S5‑245322 pCR TR 28.867 Update the description of the usage by ConditoinMonitor in UC2 Huawei pCR Approval Yes
Yes
 		approved No    
    S5‑245323 pCR TR 28.867 Update the description of the relationship between CCL and Intent Handling Huawei pCR Approval Yes
Yes
 		revised No S5‑246011  
    S5‑246011 pCR TR 28.867 Update the description of the relationship between CCL and Intent Handling Huawei pCR Approval No
Yesd1 E/// needed more time.
 		approved No   S5‑245323
    S5‑245346 pCR TR28.867 Add conclusion for Use case 4 closed control loop for problem recovery Huawei pCR Approval Yes
Yes
 		revised No S5‑246012  
    S5‑246012 pCR TR28.867 Add conclusion for Use case 4 closed control loop for problem recovery Huawei, Nokia pCR Approval No
Yesd2 E/// needed more time.
 		approved No   S5‑245346
    S5‑245402 Rel-19 pCR TR28.867 Rapporteur cleanup.docx" Nokia pCR Approval Yes
Yes
 		revised No S5‑246009  
    S5‑246009 Rel-19 pCR TR28.867 Rapporteur cleanup.docx" Nokia pCR Approval No
Yes
 		approved No   S5‑245402
    S5‑245403 Rel-19 pCR TR28.867 Revise terminology on CCL conflicts.docx" Nokia pCR Approval Yes
Yes
 		revised No S5‑246013  
    S5‑246013 Rel-19 pCR TR28.867 Revise terminology on CCL conflicts.docx" Nokia pCR Approval No
Yesd1
 		approved No   S5‑245403
    S5‑245404 Rel-19 pCR TR28.867 CCL conflicts with other management features.docx" Nokia pCR Approval Yes
Yes
 		revised No S5‑246023  
    S5‑246023 Rel-19 pCR TR28.867 CCL conflicts with other management features.docx" Nokia pCR Approval No
Yes
 		approved No   S5‑245404
    S5‑245405 Rel-19 pCR TR28.867 Add information on severity conflicts.docx" Nokia pCR Approval Yes
Yes
 		revised No S5‑246024  
    S5‑246024 Rel-19 pCR TR28.867 Add information on severity conflicts.docx" Nokia pCR Approval No
YesSamsung objected.
 		noted No   S5‑245405
    S5‑245406 Rel-19 pCR TR28.867 Avoidance of CCL action-execution-time conflicts.docx" Nokia pCR Approval Yes
Yes
 		revised No S5‑246015  
    S5‑246015 Rel-19 pCR TR28.867 Avoidance of CCL action-execution-time conflicts.docx" Nokia pCR Approval No
Yes
 		approved No   S5‑245406
    S5‑245407 Rel-19 pCR TR28.867 enhance solution on Dynamic CCL creation.docx" Nokia pCR Approval Yes
YesEricsson does not agree with this change. It was already not agreed at the last meeting.
 		revised No S5‑246019  
    S5‑246019 Rel-19 pCR TR28.867 enhance solution on Dynamic CCL creation.docx" Nokia pCR Approval No
Yes
 		approved No   S5‑245407
    S5‑245408 Rel-19 pCR TR28.867 enhance solution on triggered CCL.docx" Nokia pCR Approval Yes
YesEricsson wondered what the added information is.
 		noted No    
    S5‑245409 Rel-19 pCR TR28.867 enhance usecase on Historical CCL.docx" Nokia pCR Approval Yes
Yes
 		revised No S5‑246021  
    S5‑246021 Rel-19 pCR TR28.867 enhance usecase on Historical CCL.docx" Nokia pCR Approval No
Yes
 		approved No   S5‑245409
    S5‑245410 Rel-19 pCR TR28.867 Clarify Solution for CCL conflicts.docx" Nokia pCR Approval Yes
YesDT: needs to be revised
 		revised No S5‑246016  
    S5‑246016 Rel-19 pCR TR28.867 Clarify Solution for CCL conflicts.docx" Nokia pCR Approval No
Yes
 		approved No   S5‑245410
    S5‑245411 Rel-19 pCR TR28.867 Clarify Solution for CCL scope management.docx" Nokia pCR Approval Yes
Yes
 		revised No S5‑246017  
    S5‑246017 Rel-19 pCR TR28.867 Clarify Solution for CCL scope management.docx" Nokia pCR Approval No
Yes
 		approved No   S5‑245411
    S5‑245412 Rel-19 pCR TR28.867 Clarify Solution for CCL impact assessment.docx" Nokia pCR Approval Yes
Yes
 		revised No S5‑246018  
    S5‑246018 Rel-19 pCR TR28.867 Clarify Solution for CCL impact assessment.docx" Nokia pCR Approval No
Yes
 		approved No   S5‑245412
    S5‑245413 Rel-19 pCR TR28.867 Conclusions and Recommendations.docx" Nokia, Samsung pCR Approval Yes
Yesmerged into 6026
 		merged No    
    S5‑245665 Rel-19 pCR 28.867 Unifying Req with CCL MnS Producer Samsung R&D Institute India pCR Agreement Yes
Yes
 		revised No S5‑246010  
    S5‑246010 Rel-19 pCR 28.867 Unifying Req with CCL MnS Producer Samsung R&D Institute India pCR Agreement No
Yesd1
 		approved No   S5‑245665
    S5‑245666 Rel-19 pCR 28.867 Solution Evaluations Performance Samsung R&D Institute India pCR Agreement Yes
Yes
 		approved No    
    S5‑245668 Rel-19 pCR 28.867 Solution Evaluations Historical Samsung R&D Institute India pCR   Yes
Yeskeep open
 		approved No    
    S5‑245669 Rel-19 pCR 28.867 Solution Evaluations Dynamic and Triggered CCL Samsung R&D Institute India pCR Agreement Yes
YesNokia: these attributes are not reachable.
 		revised No S5‑246020  
    S5‑246020 Rel-19 pCR 28.867 Solution Evaluations Dynamic and Triggered CCL Samsung R&D Institute India pCR Agreement No
Yes
 		approved No   S5‑245669
    S5‑245675 Rel-19 pCR 28.867 Conclusions and Recommendations Samsung R&D Institute India pCR Agreement Yes
Yes
 		revised No S5‑246026  
    S5‑246026 Rel-19 pCR 28.867 Conclusions and Recommendations Samsung R&D Institute India pCR Agreement No
Yes
 		approved No   S5‑245675
    S5‑245697 Rel-19 pCR 28.867 Feedback Management solutions Samsung R&D Institute India pCR Agreement Yes
Yes
 		revised No S5‑246022  
    S5‑246022 Rel-19 pCR 28.867 Feedback Management solutions Samsung R&D Institute India pCR Agreement No
Yes
 		approved No   S5‑245697
    S5‑245756 pCR TR 28.871 Add alternative solution for discovery of management capabilities Ericsson, Deutsche Telekom pCR Approval Yes
YesHuawei: solution 2 is not needed. Keep open merge into 6065
 		merged No    
    S5‑245757 pCR TR 28.867 Fix alignment with ACCL model Ericsson, Deutsche Telekom pCR Approval Yes
Yes
 		approved No    
    S5‑245758 pCR TR 28.867 Add solution for CCL co-ordination and conflict handling Ericsson, Deutsche Telekom pCR Approval Yes
YesNTT DOCOMO: rename to child list
 		revised No S5‑246014  
    S5‑246014 pCR TR 28.867 Add solution for CCL co-ordination and conflict handling Ericsson, Deutsche Telekom pCR Approval No
Yes
 		approved No   S5‑245758
    S5‑245803 pCR TR 28.867 Add potential requirements and a potential solution for CCL for fault mgmt NTT DOCOMO pCR Approval Yes
Yes
 		revised No S5‑246025  
    S5‑246025 pCR TR 28.867 Add potential requirements and a potential solution for CCL for fault mgmt NTT DOCOMO, Deutsche Telekom pCR Approval No
Yes
 		approved No   S5‑245803
    S5‑245959 Draft TR 28.867 Nokia draft TR Approval No
Yes
 		email approval No    
6.19.5 Study on management aspects of Network Digital Twin S5‑245282 pCR TR 28.915 Evalutation of potential solution for UC11 Huawei Technologies R&D UK pCR   Yes
YesEricsson & Nokia: the solution is not complete
 		revised No S5‑246046  
    S5‑246046 pCR TR 28.915 Evalutation of potential solution for UC11 Huawei Technologies R&D UK pCR - No
Yes
 		approved No   S5‑245282
    S5‑245283 pCR TR 28.915 Update configuration verification Huawei Technologies R&D UK pCR   Yes
YesNTT: not clear why time synch is needed. Nokia: req. 3 is covered by req. 1 & 2
 		revised No S5‑246042  
    S5‑246042 pCR TR 28.915 Update configuration verification Huawei Technologies R&D UK pCR - No
Yes
 		approved No   S5‑245283
    S5‑245324 pCR TR 28.915 Add an example for nested NDTs Huawei pCR Approval Yes
YesLenovo & ZTE: offline comments DT: not so clear why we standardize Ericsson objected.
 		noted No    
    S5‑245325 pCR TR 28.915 Conclusion and recommendation for using NDT to generate ML training data Huawei pCR Approval Yes
YesEricsson: want a rephrasal
 		revised No S5‑246047  
    S5‑246047 pCR TR 28.915 Conclusion and recommendation for using NDT to generate ML training data Huawei pCR Approval No
Yes
 		approved No   S5‑245325
    S5‑245326 pCR TR 28.915 Update the relations between NDT and network automation functions Huawei pCR Approval Yes
Yes
 		revised No S5‑246267  
    S5‑246267 pCR TR 28.915 Update the relations between NDT and network automation functions Huawei pCR Approval No
Yes
 		approved No   S5‑245326
    S5‑245327 pCR TR 28.915 Clean up for wordings Huawei pCR Approval Yes
Yeskeep open
 		approved No    
    S5‑245368 Rel-19 pCR 28.915 Add evaluation of solution for emergency preparedness Huawei pCR Approval Yes
Yes+Nokia
 		revised No S5‑246048  
    S5‑246048 Rel-19 pCR 28.915 Add evaluation of solution for emergency preparedness Huawei, Nokia pCR Approval No
Yes
 		approved No   S5‑245368
    S5‑245393 Add the evaluation, conclusion and recommendation for TR 28.915 China Mobile pCR Approval Yes
Yesmerged into 6052
 		merged No    
    S5‑245394 Add the solution of 5G LAN topology visualization and user plane traffic analysis for TR28.915 China Mobile pCR Approval Yes
YesEricsson disagreed.
 		revised No S5‑246044  
    S5‑246044 Add the solution of 5G LAN topology visualization and user plane traffic analysis for TR28.915 China Mobile pCR Approval No
Yes
 		approved No   S5‑245394
    S5‑245398 Presentation sheet of TR 28.915 for SA Approval China Mobile TS or TR cover Approval Yes
Yes
 		noted No    
    S5‑245414 Rel-19 DP 28.915 DP on NDT Normative work scope Nokia discussion Endorsement Yes
YesEricsson: we should concsider it as a black box. Huawei supported Samsung's opinion. Merge 5393 and 5695
 		revised No S5‑246051  
    S5‑246051 Rel-19 DP 28.915 DP on NDT Normative work scope Nokia discussion Endorsement No
YesSamsung objected.
 		noted No   S5‑245414
    S5‑245415 Rel-19 pCR TR28.915 Conclusions and Recommendations Nokia pCR Approval Yes
Yes
 		revised No S5‑246052  
    S5‑246052 Rel-19 pCR TR28.915 Conclusions and Recommendations Nokia pCR Approval No
Yesneeds update Samsung & Ericsson disagreed to a further revision to reinstate parts of cl.6.
 		noted No   S5‑245415
    S5‑245439 Rel-19 pCR 28.915 basic concepts Nokia pCR Approval Yes
Yes
 		revised No S5‑246269  
    S5‑246269 Rel-19 pCR 28.915 basic concepts Nokia pCR Approval No
Yes
 		approved No   S5‑245439
    S5‑245458 pCR TR 28.915 Add evaluation for configuration verification Huawei pCR Approval Yes
Yes
 		approved No    
    S5‑245459 pCR TR 28.915 Add evaluation of signaling storm analysis Huawei, China Mobile pCR Approval Yes
Yes
 		revised No S5‑246049  
    S5‑246049 pCR TR 28.915 Add evaluation of signaling storm analysis Huawei, China Mobile pCR Approval No
Yes
 		approved No   S5‑245459
    S5‑245557 pCR 28.915 Add solution for NDT visualization HUAWEI, CMCC pCR Approval Yes
YesDT: it is unclear about the visualization
 		revised No S5‑246045  
    S5‑246045 pCR 28.915 Add solution for NDT visualization HUAWEI, CMCC pCR Approval No
Yes
 		approved No   S5‑245557
    S5‑245664 Rel-19 pCR TR 28.858 Update Solution for Nested NDT ZTE Corporation pCR Approval Yes
Yes
 		withdrawn Yes    
    S5‑245691 Rel-19 pCR 28.915 NDT Assisted Network Configuration Generation based on Performance Monitoring Samsung R&D Institute India, NTT DOCOMO pCR Agreement Yes
YesNTT DOCOMO was added as an author
 		revised No S5‑246270  
    S5‑246270 Rel-19 pCR 28.915 NDT Assisted Network Configuration Generation based on Performance Monitoring Samsung R&D Institute India, NTT DOCOMO pCR Agreement No
Yes
 		approved No   S5‑245691
    S5‑245693 Rel-19 pCR 28.915 Evaluation of Inducement Samsung R&D Institute India pCR Agreement Yes
Yes
 		revised No S5‑246050  
    S5‑246050 Rel-19 pCR 28.915 Evaluation of Inducement Samsung R&D Institute India pCR Agreement No
Yes
 		approved No   S5‑245693
    S5‑245695 Rel-19 pCR 28.915 Conclusions Samsung R&D Institute India pCR Agreement Yes
Yesmerged into 6052
 		merged No    
    S5‑245839 Rel-19 pCR TR 28.915 Update Solution for Nested NDT ZTE Corporation pCR Approval Yes
YesEricsson does not support. Not clear on basic NDT.
 		revised No S5‑246043  
    S5‑246043 Rel-19 pCR TR 28.915 Update Solution for Nested NDT ZTE Corporation pCR Approval No
YesHuawei objected
 		noted No   S5‑245839
    S5‑245960 Draft TR 28.915 CMCC draft TR Approval No
Yes
 		email approval No    
6.19.6 Study on Cloud Aspects of Management and Orchestration S5‑245347 DP on observations and issues for using of VNF generic OAM functions in SBMA Huawei, Nokia,Deutsche Telekom pCR Endorsement Yes
Yesseveral comments from E///. NTT DOCOMO commented that before the matter was clear and now it's again not clear. Discussion between Nokia, NTT DOCOMO, and x. SA5 Chair: we need to define the 2 options. E/// need to define virtualization dependent. Option 1: generic OAM to manage Param X+Y; Opt2, Opt.3.
 		noted No    
    S5‑245348 pCR TR 28.869 Add potential deployment scenario for using of VNF generic OAM functions in SBMA Huawei, Nokia, Deutsche Telekom pCR Approval Yes
Yes
 		revised No S5‑246240  
    S5‑246240 pCR TR 28.869 Add potential deployment scenario for using of VNF generic OAM functions in SBMA Huawei, Nokia, Deutsche Telekom, NTT DOCOMO pCR Approval No
Yes
 		approved No   S5‑245348
    S5‑245349 pCR TR 28.869 Update Use cases for use of VNF generic OAM functions Huawei, Nokia, Deutsche Telekom pCR Approval Yes
Yes
 		revised No S5‑246241  
    S5‑246241 pCR TR 28.869 Update Use cases for use of VNF generic OAM functions Huawei, Nokia, Deutsche Telekom pCR Approval No
Yes
 		approved No   S5‑245349
    S5‑245369 Rel-19 pCR 28.869 Add solution for specification of architecture Huawei pCR Approval Yes
Yes
 		noted No    
    S5‑245446 pCR TR 28.869 remove editor note and adopt to new concept in Annex D Ericsson Telecomunicazioni SpA pCR Approval Yes
Yesmerge with 5813 NTT DOCOMO: note is not needed remove Editor's notes
 		revised No S5‑246123  
    S5‑246123 pCR TR 28.869 remove editor note and adopt to new concept in Annex D Ericsson Telecomunicazioni SpA pCR Approval No
Yes
 		approved No   S5‑245446
    S5‑245447 pCR TR 28.869 remove editor note and adopt to new concept in Annex E Ericsson Telecomunicazioni SpA pCR Approval Yes
Yesoffline comments from Rakuten merge with 5814
 		merged No    
    S5‑245448 pCR TR 28.869 remove editor note and adopt to new concept in Annex F Ericsson Telecomunicazioni SpA pCR Approval Yes
Yesmerge with 6245
 		merged No    
    S5‑245449 pCR TR 28.869 remove editor note and adopt to new concept in use case 5.2.4 Ericsson Telecomunicazioni SpA pCR Approval Yes
Yes
 		revised No S5‑246007  
    S5‑246007 pCR TR 28.869 remove editor note and adopt to new concept in use case 5.2.4 Ericsson Telecomunicazioni SpA pCR Approval No
Yes
 		revised No S5‑246297 S5‑245449
    S5‑246297 pCR TR 28.869 remove editor note and adopt to new concept in use case 5.2.4 Ericsson Telecomunicazioni SpA pCR Approval No
Yes
 		approved No   S5‑246007
    S5‑245450 pCR TR 28.869 remove editor note and adopt to new concept in use case 5.2.5 Ericsson Telecomunicazioni SpA pCR Approval Yes
Yesovelaps with 5849 and 5555
 		revised No S5‑246121  
    S5‑246121 pCR TR 28.869 remove editor note and adopt to new concept in use case 5.2.5 Ericsson Telecomunicazioni SpA pCR Approval No
Yes5849 merged into here
 		approved No   S5‑245450
    S5‑245451 pCR TR 28.869 conclusion on management data streaming based on message bus Ericsson Telecomunicazioni SpA pCR Approval Yes
Yes
 		postponed No    
    S5‑245528 pCR TR 28.869 Add evaluation of solutions for LCM of NF Deployment use case Rakuten Mobile, Inc pCR Approval Yes
Yes
 		revised No S5‑246075  
    S5‑246075 pCR TR 28.869 Add evaluation of solutions for LCM of NF Deployment use case Rakuten Mobile, Inc pCR Approval No
YesNTT DOCOMO objcted.
 		noted No   S5‑245528
    S5‑245529 pCR TR 28.869 Add evaluation of solutions for data streaming for cloud native network function use case Rakuten Mobile, Inc pCR Approval Yes
Yesneeds more discussion.
 		revised No S5‑246076  
    S5‑246076 pCR TR 28.869 Add evaluation of solutions for data streaming for cloud native network function use case Rakuten Mobile, Inc pCR Approval No
YesEricsson objected
 		noted No   S5‑245529
    S5‑245530 pCR TR 28.869 Add conclusions and recommendations for WT-2 Rakuten Mobile, Inc pCR Approval Yes
Yes
 		postponed No    
    S5‑245545 pCR TR 28.869 conclusion on use of industry solutions for LCM of NF Deployment Ericsson Telecomunicazioni SpA pCR Approval Yes
Yes
 		postponed No    
    S5‑245553 pCR TR 28.869 Add evaluation of solution for creation of a NF deployment instance Rakuten Mobile, Inc pCR Approval Yes
Yes
 		revised No S5‑246243  
    S5‑246243 pCR TR 28.869 Add evaluation of solution for creation of a NF deployment instance Rakuten Mobile, Inc pCR Approval No
Yes
 		approved No   S5‑245553
    S5‑245554 pCR TR 28.869 Add evaluation of solutions for modification of CNF instance Rakuten Mobile, Inc pCR Approval Yes
Yes
 		revised No S5‑245850  
    S5‑245555 pCR TR 28.869 Add evaluation of solutions for termination of CNF instance Rakuten Mobile, Inc pCR Approval Yes
YesHuawei: conclusions and evaluations are postponed to the next meeting. Nokia, Ericsson and NTT DOCOMO offline comments
 		revised No S5‑246122  
    S5‑246122 pCR TR 28.869 Add evaluation of solutions for termination of CNF instance Rakuten Mobile, Inc pCR Approval No
Yes4. change of 5849 merged into here Ericsson objected
 		noted No   S5‑245555
    S5‑245671 pCR terminology related ENs NTT DOCOMO INC.. pCR Approval Yes
YesE///: no need for the change Nokia: 4.th change has to be done.
 		revised No S5‑246005  
    S5‑246005 pCR terminology related ENs NTT DOCOMO INC.. pCR Approval No
Yes
 		approved No   S5‑245671
    S5‑245674 pCR VNF Configuration management ENs NTT DOCOMO INC.. pCR Approval Yes
YesNokia offline comments. Should be postponed to the next meeting.
 		revised No S5‑246117  
    S5‑246117 pCR VNF Configuration management ENs NTT DOCOMO INC.. pCR Approval No
Yes
 		approved No   S5‑245674
    S5‑245676 pCR addressing Annexes_ENs NTT DOCOMO INC.. pCR Approval Yes
Yes
 		revised No S5‑246242  
    S5‑246242 pCR addressing Annexes_ENs NTT DOCOMO INC.. pCR Approval No
Yes
 		approved No   S5‑245676
    S5‑245677 pCR note for data streaming services NTT DOCOMO INC.. pCR Approval Yes
Yes
 		revised No S5‑246244  
    S5‑246244 pCR note for data streaming services NTT DOCOMO INC.. pCR Approval No
Yes
 		approved No   S5‑245677
    S5‑245678 pCR location information in NFV NTT DOCOMO INC.. pCR Approval Yes
Yes
 		revised No S5‑246246  
    S5‑246246 pCR location information in NFV NTT DOCOMO INC.. pCR Approval No
YesEricsson objected
 		noted No   S5‑245678
    S5‑245732 pCR 28.869 VNF traffic mgmt solution and evaluation NTT DOCOMO INC, China Mobile pCR Approval Yes
YesNTT DOCOMO: postpone to the next meeting. Huawei disagree with change #1.
 		revised No S5‑246118  
    S5‑246118 pCR 28.869 VNF traffic mgmt solution and evaluation NTT DOCOMO INC, China Mobile pCR Approval No
YesNokia objected
 		noted No   S5‑245732
    S5‑245770 pCR Add Evaluation of solutions for Cloud-native VNF policy management China Mobile,NTT DOCOMO pCR Approval Yes
YesNTT DOCOMO: postpone to the next meeting. Ericsson & Nokia offline comments
 		revised No S5‑246119  
    S5‑246119 pCR Add Evaluation of solutions for Cloud-native VNF policy management China Mobile,NTT DOCOMO pCR Approval No
YesNokia objected
 		postponed No   S5‑245770
    S5‑245771 pCR add a solution and evaluation of solutions for Cloud-native VNF traffic mgmt China Mobile,NTT DOCOMO pCR Approval No
Yes
 		withdrawn Yes    
    S5‑245773 pCR Add Potential solution for WT-3 Placement of cloud native NFs China Mobile pCR Approval Yes
Yeskeep open Ericsson objected
 		noted No    
    S5‑245774 pCR Add Conclusions and recommendations China Mobile,NTT DOCOMO pCR Approval Yes
Yes
 		postponed No    
    S5‑245810 Rel-19 pCR TR 28.869 Resolve editor's note on the impact of the cloud-native design principles on the 3GPP management system Nokia Hungary pCR Approval Yes
Yesmerged onto 6005
 		merged No    
    S5‑245811 Rel-19 pCR TR 28.869 Add conclusions and recommendations to the use of industry solutions for management of cloud-native network functions Nokia Hungary pCR Approval Yes
Yes
 		postponed No    
    S5‑245812 Rel-19 pCR TR 28.869 Removing unnecessary statement regarding VNF generic OAM functions consumers and correcting the sub-clause numbering Nokia Hungary pCR Approval Yes
YesNTT DOCOMO offline comments no need for revision
 		approved No    
    S5‑245813 Rel-19 pCR TR 28.869 Resolve editor's note in Annex D by updating the content and the related figure Nokia Hungary pCR Approval Yes
Yesmerged into 6123 NTT DOCOMO: NF deployment requests are not clear
 		merged No    
    S5‑245814 Rel-19 pCR TR 28.869 Resolve editor's note in Annex E by updating the content and the related figure Nokia Hungary pCR Approval Yes
Yes
 		revised No S5‑246124  
    S5‑246124 Rel-19 pCR TR 28.869 Resolve editor's note in Annex E by updating the content and the related figure Nokia Hungary pCR Approval No
Yes
 		approved No   S5‑245814
    S5‑245815 Rel-19 pCR TR 28.869 Resolve editor's note in Annex F by updating the content and the related figure Nokia Hungary pCR Approval Yes
Yes
 		revised No S5‑246245  
    S5‑246245 Rel-19 pCR TR 28.869 Resolve editor's note in Annex F by updating the content and the related figure Nokia Hungary pCR Approval No
YesRakuten objected
 		noted No   S5‑245815
    S5‑245848 pCR TR 28.869 Add details for modification of NF instance Rakuten Mobile, Inc pCR Approval Yes
Yesmerged into 6007(-8)
 		merged No    
    S5‑245849 pCR TR 28.869 Add details for termination of NF instance Rakuten Mobile, Inc pCR Approval Yes
Yesmerged into 6121
 		merged No    
    S5‑245850 pCR TR 28.869 Add evaluation of solutions for modification of CNF instance Rakuten Mobile, Inc pCR Approval Yes
Yes
 		revised No S5‑246008 S5‑245554
    S5‑246008 pCR TR 28.869 Add evaluation of solutions for modification of CNF instance Rakuten Mobile, Inc pCR Approval No
YesNokia objected
 		noted No   S5‑245850
    S5‑245961 Draft TR 28.869 CMCC draft TR Approval No
Yes
 		email approval No    
6.19.7 Study on Enablers for Security Monitoring                      
6.19.8 Study on Service Based Management Architecture enhancement phase 3 S5‑245294 pCR TR 28.871 Add SBMA concepts and background Huawei pCR Approval Yes
Yes
 		approved No    
    S5‑245295 pCR TR 28.871 Add evaluation and conclusion for Support IOCs in SBMA Huawei pCR Approval Yes
Yes
 		approved No    
    S5‑245350 pCR TR 28.871 Update solution for Discovery of management capabilities of MnS supported by a MnS Producer Huawei, Deutsche Telekom pCR Approval Yes
Yes
 		revised No S5‑246065  
    S5‑246065 pCR TR 28.871 Update solution for Discovery of management capabilities of MnS supported by a MnS Producer Huawei, Deutsche Telekom, Ericsson, Nokia pCR Approval No
Yesd3
 		approved No   S5‑245350
    S5‑245351 pCR TR 28.871 Add conclusion for schema reference enhancements Huawei pCR Approval Yes
Yes
 		approved No    
    S5‑245352 pCR TR 28.871 Add conclusion for Overview of management capabilities and corresponding Solution Sets Huawei pCR Approval Yes
Yes
 		revised No S5‑246060  
    S5‑246060 pCR TR 28.871 Add conclusion for Overview of management capabilities and corresponding Solution Sets Huawei pCR Approval No
Yesd1
 		approved No   S5‑245352
    S5‑245353 pCR TR 28.871 Usage of MnS Registry NRM fragment for MnS Registry and Discovery Huawei, Deutsche Telekom pCR Approval Yes
Yes
 		revised No S5‑246066  
    S5‑246066 pCR TR 28.871 Usage of MnS Registry NRM fragment for MnS Registry and Discovery Huawei, Deutsche Telekom pCR Approval No
Yesd2
 		approved No   S5‑245353
    S5‑245391 Rel-19 pCR TR 28.871 Reliable notification transfer Ericsson Hungary Ltd pCR Approval Yes
Yes
 		revised No S5‑246063  
    S5‑246063 Rel-19 pCR TR 28.871 Reliable notification transfer Ericsson Hungary Ltd pCR Approval No
Yesd1
 		approved No   S5‑245391
    S5‑245392 pCR TR 28.871 Alarm definition - filtering Ericsson Hungary Ltd pCR Approval Yes
Yes
 		revised No S5‑246064  
    S5‑246064 pCR TR 28.871 Alarm definition - filtering Ericsson Hungary Ltd pCR Approval No
Yes
 		approved No   S5‑245392
    S5‑245755 pCR TR 28.871 Rapporteur clean-up.docx Ericsson pCR Approval Yes
Yes
 		revised No S5‑246061  
    S5‑246061 pCR TR 28.871 Rapporteur clean-up.docx Ericsson pCR Approval No
Yesd2
 		approved No   S5‑245755
    S5‑245777 pCR TR 28.871 Add use case, reqs, potential solutions and evaluation (management model decoupling) Ericsson Inc. pCR Approval Yes
YesNokia: dealing with multiple object instance versions.
 		revised No S5‑246067 S5‑244335
    S5‑246067 pCR TR 28.871 Add use case, reqs, potential solutions and evaluation (management model decoupling) Ericsson Inc., Huawei, Deutsche Telekom, Nokia pCR Approval No
Yes
 		approved No   S5‑245777
    S5‑245782 pCR TR 28.871 Add evaluation of potential solutions (schema retrieval support) Ericsson Inc. pCR Approval Yes
Yes
 		revised No S5‑246062  
    S5‑246062 pCR TR 28.871 Add evaluation of potential solutions (schema retrieval support) Ericsson Inc. pCR Approval No
Yesd2
 		approved No   S5‑245782
    S5‑245962 Draft TR 28.871 Ericsson draft TR Approval No
Yes
 		email approval No    
6.19.9 Study on Management of planned configurations (completed)                      
6.19.9.1 Management of planned configurations S5‑245426 Input Draft TS 28.572 Management of planned configurations Nokia draft TS Approval Yes
YesEricsson: is not a skeleton. SA5 Vice Chair: management and orchestration to be added in the title.
 		revised No S5‑246079  
    S5‑246079 Input Draft TS 28.572 Management of planned configurations Nokia draft TS Approval No
Yes
 		approved No   S5‑245426
    S5‑245427 pCR 28.572 Add skeleton Nokia pCR Approval Yes
Yes
 		revised No S5‑246080  
    S5‑246080 pCR 28.572 Add skeleton Nokia pCR Approval No
Yesd1
 		approved No   S5‑245427
    S5‑245428 pCR 28.572 Add requirements for plans Nokia pCR Approval Yes
Yes
 		revised No S5‑246081  
    S5‑246081 pCR 28.572 Add requirements for plans Nokia pCR Approval No
Yesd1
 		approved No   S5‑245428
    S5‑245429 pCR 28.572 Add requirements for transactions Nokia pCR Approval Yes
Yes
 		revised No S5‑246082  
    S5‑246082 pCR 28.572 Add requirements for transactions Nokia pCR Approval No
Yes
 		approved No   S5‑245429
    S5‑245430 pCR 28.572 Add requirements for validation Nokia pCR Approval Yes
Yes
 		revised No S5‑246083  
    S5‑246083 pCR 28.572 Add requirements for validation Nokia pCR Approval No
Yesd1
 		approved No   S5‑245430
    S5‑245431 pCR 28.572 Add requirements for activation Nokia pCR Approval Yes
Yes
 		revised No S5‑246084  
    S5‑246084 pCR 28.572 Add requirements for activation Nokia pCR Approval No
Yesd1
 		approved No   S5‑245431
    S5‑245432 pCR 28.572 Add content for plans Nokia pCR Approval Yes
Yes
 		revised No S5‑246085  
    S5‑246085 pCR 28.572 Add content for plans Nokia pCR Approval No
Yesd1
 		approved No   S5‑245432
    S5‑245433 pCR 28.572 Add content for transactions Nokia pCR Approval Yes
YesOffline comments from Ericsson.
 		revised No S5‑246086  
    S5‑246086 pCR 28.572 Add content for transactions Nokia pCR Approval No
Yesd1
 		approved No   S5‑245433
    S5‑245434 pCR 28.572 Add content for validation Nokia pCR Approval Yes
Yes
 		revised No S5‑246087  
    S5‑246087 pCR 28.572 Add content for validation Nokia pCR Approval No
Yesd1
 		approved No   S5‑245434
    S5‑245435 pCR 28.572 Add content for activation Nokia pCR Approval Yes
YesEricsson offline comments Discussing fallback plan. Atomic behaviour for multiple plans needs to be clarified.
 		revised No S5‑246088  
    S5‑246088 pCR 28.572 Add content for activation Nokia pCR Approval No
Yesd1
 		approved No   S5‑245435
    S5‑245436 pCR 28.572 Add examples for the RESTful HTTP-based solution set Nokia pCR Approval Yes
YesEricsson suggested to note.
 		noted No    
    S5‑245830 DP management of planned configuration Ericsson Hungary Ltd discussion Endorsement Yes
Yesrev 1 Samsung: stage 2 is not decided? Remove the yaml file in 3.2
 		revised No S5‑246089  
    S5‑246089 DP management of planned configuration Ericsson Hungary Ltd discussion Endorsement No
Yesd1
 		endorsed No   S5‑245830
    S5‑245963 Draft TS 28.572 Nokia draft TS Approval No
Yes
 		email approval No    
6.19.10 Data management phase 2 S5‑245354 Rel-19 inputToDraftCR TS 28.622 Add solution for Managing external management data Huawei, Deutsche Telekom draftCR Approval Yes
Yes
 		revised No S5‑246090 S5‑244801
    S5‑246090 Rel-19 inputToDraftCR TS 28.622 Add solution for Managing external management data Huawei, Deutsche Telekom, Nokia draftCR Approval No
Yesd2
 		approved No   S5‑245354
    S5‑245355 Discussion on observations and potential enhancement for management data discovery capability Huawei, Deutsche Telekom discussion Endorsement Yes
YesNokia: should have a more general discussion on the matter, instead of going case by case. Ericsson: turn the WID into a SID? The TR was very clear. Several things have shifted. The discussion paper is reopening things which were agreed before.
 		noted No    
    S5‑245356 Rel-19 inputToDraftCR TS 28.622 Enhance the model for supported managgement data to support management data discovery Huawei, Deutsche Telekom draftCR Agreement Yes
Yesrelated to 5786 Ericsson: how to model the capabilities Potential rapporteur call->agreed
 		noted No    
    S5‑245357 Rel-19 inputToDraftCR TS 28.537 Update the description and requirements for clause 6.5 Discovery of management data Huawei, Deutsche Telekom draftCR Agreement Yes
YesProposal 1 Need more time. Proposals are approved.
 		approved No    
    S5‑245501 Discussion on external management data Nokia discussion Endorsement Yes
YesHuawei: capture supported external management data in subnetwork IOC Ericsson: many info associates with geogr. area need more discussion. Rapporteur call.
 		noted No    
    S5‑245786 Rel-19 inputToDraftCR TS 28.622 Add supported data reporting capability (stage 2) Ericsson Inc. draftCR Approval Yes
Yes
 		noted No    
    S5‑245787 Rel-19 inputToDraftCR TS 28.623 Add supported data reporting capability (stage 3, yang) Ericsson Inc. draftCR Approval Yes
Yesw/d on Wed at author's request. Based on offline discussions the stage2 requires further update first.
 		withdrawn Yes    
    S5‑245969 Rel-19 DraftCR TS 28.622 Nokia draftCR discussion No
Yes
 		email approval No    
    S5‑245970 Rel-19 DraftCR TS 28.537 Update the description and requirements for clause 6.5 Discovery of management data Nokia draftCR discussion No
Yesreissued
 		withdrawn Yes    
    S5‑246298 Rel-19 DraftCR TS 28.537 Nokia draftCR discussion No
Yes
 		for email approval No    
6.19.11 Study on data management regarding subscriptions and reporting (completed) S5‑245238 Rel-19 CR 28.873_1900 Remove normative text from the TR Ericsson CR   Yes
Yes
 		revised No S5‑246091  
    S5‑246091 Rel-19 CR 28.873_1900 Remove normative text from the TR Ericsson CR - No
Yes
 		agreed No   S5‑245238
6.19.11.1 Data management regarding subscriptions and reporting                      
6.19.12 5G performance measurements and KPIs phase 4 S5‑245281 Rel-19 CR TS 28.552 Add PMF measurement of network-initiated PLR for ATSSS China Telecom Corporation Ltd., ZTE CR Agreement Yes
Yes
 		agreed No    
    S5‑245521 Rel-19 CR TS 28.552 Sub optimal Handover Metrics Nokia CR Approval Yes
Yes
 		agreed No    
    S5‑245522 Rel-18 CR TS 28.552 XR PDU set packet delay measurement Nokia CR Approval Yes
Yes
 		not pursued No    
    S5‑245548 New performance measurements for Reduced Capability (RedCap) Device Early Identification Apple CR   Yes
Yesrev marks on cover template 12.3! Date; >Annex< A
 		revised No S5‑246068  
    S5‑246068 New performance measurements for Reduced Capability (RedCap) Device Early Identification Apple CR - No
Yesd1
 		agreed No   S5‑245548
    S5‑245689 New performance measurements for eDRX negotiation registration requests and accepts Apple CR   Yes
YesKorea! +Date. template 12.3! >Annex< A
 		revised No S5‑246069  
    S5‑246069 New performance measurements for eDRX negotiation registration requests and accepts Apple CR - No
Yes
 		agreed No   S5‑245689
    S5‑245692 New performance measurements for UE assistance information with RRM Measurement Relaxation feature usage Apple CR   Yes
Yes
 		revised No S5‑246070  
    S5‑246070 New performance measurements for UE assistance information with RRM Measurement Relaxation feature usage Apple, Deutsche Telekom CR - No
Yesd1
 		agreed No   S5‑245692
    S5‑245696 New KPIs for Connected Mode RRM Relaxation Usage rate Apple CR   Yes
Yessee CRs above. core X!
 		revised No S5‑246071  
    S5‑246071 New KPIs for Connected Mode RRM Relaxation Usage rate Apple, Deutsche Telekom CR - No
Yesd1
 		agreed No   S5‑245696
    S5‑245698 New KPIs for Extended DRX Negotiation Success Rate Apple CR   Yes
Yes
 		revised No S5‑246072  
    S5‑246072 New KPIs for Extended DRX Negotiation Success Rate Apple CR - No
Yes
 		agreed No   S5‑245698
    S5‑245703 Rel-19 CR 28.552 Correct LTM measurements Ericsson GmbH Eurolab CR Approval Yes
Yes
 		agreed No    
    S5‑245704 Rel-19 CR 28.554 Update mobility KPI for LTM Ericsson GmbH Eurolab CR Approval Yes
Yes
 		agreed No    
    S5‑245705 Rel-19 CR 28.552 Add LTM use case Ericsson GmbH Eurolab CR Approval Yes
Yes
 		revised No S5‑246073  
    S5‑246073 Rel-19 CR 28.552 Add LTM use case Ericsson GmbH Eurolab CR Approval No
Yes
 		agreed No   S5‑245705
6.19.13 5G Advanced NRM features phase 3 S5‑245277 Rel-19 CR TS 28.541 Update 5GC NRM and Network Slicing NRM yaml file to include the missing default values Huawei CR Agreement Yes
YesNokia: add action point for this WI at the end of Rel-19 for stage 3
 		agreed No    
    S5‑245297 Rel-19 CR TS 28.541 add max preamble to support msg1 repetition for RACH Huawei CR Approval Yes
Yes
 		noted No    
    S5‑245298 Rel-19 CR TS 28.541 add cell coverage configuration to support CCO in RAN3 Huawei CR Approval Yes
Yes
 		revised No S5‑246077  
    S5‑246077 Rel-19 CR TS 28.541 add cell coverage configuration to support CCO in RAN3 Huawei CR Approval No
Yesd1 remove RAN3 from title & cover Reissued as S5-246277 because of title change
 		withdrawn Yes   S5‑245298
    S5‑246277 Rel-19 CR TS 28.541 add cell coverage configuration to support CCO Huawei CR Approval No
Yes
 		agreed No    
    S5‑245466 Enhance the isUnique property for stage 3 OpenAPI Nokia, Nokia Shanghai Bell CR Approval Yes
Yes
 		agreed No    
    S5‑245468 TS28.541 Rel19 enhance property for stage 3 OpenAPI Nokia, Nokia Shanghai Bell CR Approval No
Yes
 		withdrawn Yes    
    S5‑245470 Alignment of IP Address modeling Nokia, Nokia Shanghai Bell CR Approval Yes
Yes
 		agreed No    
    S5‑245471 Alignment of attribute value list with TS29.510 for UPInterfaceType notificationType and supportedDataSets Nokia, Nokia Shanghai Bell CR Approval Yes
Yes
 		agreed No    
    S5‑245534 Rel-19 CR 28.623 Add missing DN type to the table of YANG common types Ericsson Hungary Ltd CR Approval Yes
Yes
 		revised No S5‑246078  
    S5‑246078 Rel-19 CR 28.623 Add missing DN type to the table of YANG common types Ericsson Hungary Ltd CR Approval No
Yes
 		agreed No   S5‑245534
    S5‑245560 Update the isReadOnly property for stage 3 OpenAPI Nokia, Nokia Shanghai Bell CR Approval Yes
Yes
 		agreed No    
    S5‑245684 Rel-19 CR 28.538 adding managed services to Edge entities Samsung R&D Institute India CR Agreement Yes
Yes
 		revised No S5‑246074  
    S5‑246074 Rel-19 CR 28.538 adding managed services to Edge entities Samsung R&D Institute India CR Agreement No
Yesd1
 		agreed No   S5‑245684
    S5‑245712 Rel-19 CR 28.541 NRM extensions for VMR Ph2 Samsung R&D Institute India CR Agreement Yes
YesEricsson: sent offline comments Huawei: pospone until RAN have some results
 		not pursued No    
    S5‑245797 Rel-19 CR TS 28.541 Add new OperatorCU and NRCellOperatorCU for MOCN China Unicom CR Agreement Yes
Yes
 		not pursued No    
6.19.14 Subscriber and Equipment Trace and QoE collection management S5‑245296 Rel-19 CR TS 32.422 updated procedure for Trace session activation for RRC reporting in NG-RAN Huawei CR Approval Yes
Yes
 		revised No S5‑246104  
    S5‑246104 Rel-19 CR TS 32.422 updated procedure for Trace session activation for RRC reporting in NG-RAN Huawei, Ericsson CR Approval No
Yes
 		agreed No   S5‑245296
    S5‑245512 Rel-19 CR 28.622 Corrections for tracing of RRC reports Nokia CR Approval Yes
Yes
 		agreed No    
    S5‑245706 Rel-19 CR 32.421 Corrections of RRC reporting Ericsson CR Approval Yes
Yes
 		agreed No    
    S5‑245707 Rel-19 CR 32.422 Corrections to RRC reporting Ericsson CR Approval Yes
Yes
 		agreed No    
    S5‑245708 Rel-19 CR 28.622 Corrections of RRC reporting Ericsson CR Approval Yes
Yes
 		agreed No    
    S5‑245709 Rel-19 CR 28.623 Corrections on RRC reporting Ericsson CR Approval Yes
Yes
 		agreed No    
6.19.15 Study on Management Aspects of NTN Phase 2 S5‑245276 Rel-19 pCR TR 28.874 Rapportuer cleanup CATT pCR Approval Yes
YesEricsson: potential requirements no need to change from shall to should.
 		revised No S5‑246092  
    S5‑246092 Rel-19 pCR TR 28.874 Rapportuer cleanup CATT pCR Approval No
Yes
 		approved No   S5‑245276
    S5‑245328 DP on using plan management to support time based configuration for NTN scenarios Huawei discussion Endorsement Yes
YesSamsung: do not like to use 'plan'
 		noted No    
    S5‑245329 pCR TR 28.874 Add plan management solution for NTN scenarios Huawei pCR Approval Yes
Yes
 		revised No S5‑246093  
    S5‑246093 pCR TR 28.874 Add plan management solution for NTN scenarios Huawei pCR Approval No
Yesd1 Samsung needed more time.
 		approved No   S5‑245329
    S5‑245330 pCR TR 28.874 Evaluation for NTN neighbour cell management Huawei pCR Approval Yes
Yes
 		revised No S5‑246094  
    S5‑246094 pCR TR 28.874 Evaluation for NTN neighbour cell management Huawei pCR Approval No
Yes
 		approved No   S5‑245330
    S5‑245331 pCR TR 28.874 Overview of management enhancement supporting new NTN features Huawei pCR Approval Yes
Yes
 		approved No    
    S5‑245361 pCR 28.874-101 Complement potential solutions for Management of connections and associations Ericsson LM pCR Approval Yes
YesSA5 Chair: update the note
 		revised No S5‑246095  
    S5‑246095 pCR 28.874-101 Complement potential solutions for Management of connections and associations Ericsson LM pCR Approval No
Yes
 		approved No   S5‑245361
    S5‑245389 pCR TR 28.874 Add potential solutions on configuration of the NFs supported S&F operation China Telecomunication Corp. pCR Approval Yes
Yes
 		revised No S5‑246096  
    S5‑246096 pCR TR 28.874 Add potential solutions on configuration of the NFs supported S&F operation China Telecomunication Corp. pCR Approval No
Yes
 		approved No   S5‑245389
    S5‑245425 pCR TR 28.874 Update the Use Case#1 of UE-Satellite-UE communication China Telecomunication Corp. pCR Approval Yes
Yes
 		approved No    
    S5‑245672 pCR 28.874-101 Update evaluations Ericsson LM pCR Approval Yes
Yes
 		revised No S5‑246097  
    S5‑246097 pCR 28.874-101 Update evaluations Ericsson LM pCR Approval No
Yesd1
 		approved No   S5‑245672
    S5‑245951 Draft TR 28.874 CATT draft TR Approval No
Yes
 		email approval No    
6.19.16 Study on management of IAB nodes S5‑245443 Presentation of TR 28.875 to SA for information Ericsson Telecomunicazioni SpA TS or TR cover Approval Yes
Yeskeep open
 		approved No    
    S5‑245444 pCR TR 28.875 conclusion for IAB node configuration Ericsson Telecomunicazioni SpA pCR   Yes
Yes
 		revised No S5‑246098  
    S5‑246098 pCR TR 28.875 conclusion for IAB node configuration Ericsson Telecomunicazioni SpA pCR - No
Yesd1
 		approved No   S5‑245444
    S5‑245445 pCR TR 28.875 conclusion for IAB node OAM connectivity Ericsson Telecomunicazioni SpA pCR Approval Yes
Yessame as 5444
 		revised No S5‑246099  
    S5‑246099 pCR TR 28.875 conclusion for IAB node OAM connectivity Ericsson Telecomunicazioni SpA pCR Approval No
Yesd2
 		approved No   S5‑245445
    S5‑245952 Draft TR 28.875 Ericsson draft TR Approval No
Yes
 		email approval No    
6.19.17 Study on management aspects of RedCap feature S5‑245227 pCR TR 28.876 update some unclear descriptions AsiaInfo pCR Approval Yes
Yes
 		approved No    
    S5‑245245 pCR TR 28.876 Add evaluation and conclusions for use case #5 AsiaInfo pCR Approval Yes
Yesstidy item maybe not allowed.
 		revised No S5‑246100  
    S5‑246100 pCR TR 28.876 Add evaluation and conclusions for use case #5 AsiaInfo pCR Approval No
Yes
 		approved No   S5‑245245
    S5‑245358 pCR TR 28.876 Update Use Case#1 NG-RAN configuration to support RedCap and Non-RedCap UEs co-existence scenario Huawei, China Unicom pCR Approval Yes
Yes
 		revised No S5‑246101  
    S5‑246101 pCR TR 28.876 Update Use Case#1 NG-RAN configuration to support RedCap and Non-RedCap UEs co-existence scenario Huawei, China Unicom pCR Approval No
Yes
 		approved No   S5‑245358
    S5‑245359 pCR TR 28.876 Add missing definitions and clarifications Huawei, China Unicom pCR Approval Yes
Yes
 		revised No S5‑246102  
    S5‑246102 pCR TR 28.876 Add missing definitions and clarifications Huawei, China Unicom pCR Approval No
Yes
 		approved No   S5‑245359
    S5‑245710 pCR TR 28.876 Add potential solution, evaluation and conclusion for EE KPI of RedCap China Unicom pCR Approval Yes
YesEricsson: this KPI can't achieve the requirements related to this use case.
 		revised No S5‑246103  
    S5‑246103 pCR TR 28.876 Add potential solution, evaluation and conclusion for EE KPI of RedCap China Unicom pCR Approval No
YesSamsung objected
 		noted No   S5‑245710
    S5‑245724 Rel-19 pCR TR28.876 Update requirement and add potential solution for Inactive RedCap UEs ZTE Corporation pCR Approval Yes
Yes
 		approved No    
    S5‑245725 Rel-19 pCR TR28.876 Add conclusion and recommendation for resource load of RedCap service ZTE Corporation pCR Approval Yes
Yes
 		approved No    
    S5‑245953 Draft TR 28.876 AsiaInfo draft TR Approval No
Yes
 		email approval No    
    S5‑246105 Presentation sheet for approval of 28.876 China Unicom other discussion No
YesSamsung objected
 		noted No    
6.19.18 Study on Enhancement of Management Aspects related to NWDAF Phase 2 (completed)                      
6.19.18.1 Enhancement of Management Aspects related to NWDAF Phase 2 S5‑245497 Rel-19 CR 28.552 Add measurements related to NWDAF roaming analytics Nokia CR Approval Yes
Yes3GPP styles to be applied cover ver 12.3!
 		revised No S5‑246106  
    S5‑246106 Rel-19 CR 28.552 Add measurements related to NWDAF roaming analytics Nokia CR Approval No
Yesd1
 		agreed No   S5‑245497
    S5‑245498 Rel-19 CR 28.552 Add use case on NWDAF roaming analytics Nokia CR Approval Yes
Yes3GPP styles to be applied cover ver 12.3!
 		revised No S5‑246107  
    S5‑246107 Rel-19 CR 28.552 Add use case on NWDAF roaming analytics Nokia CR Approval No
Yesd1
 		agreed No   S5‑245498
6.19.19 Study on Management of Network Sharing Phase 3 S5‑245789 pCR TR 28.878 Add evaluation, conclusion and recommendation for Use Case #1 China Unicom pCR Approval Yes
Yes
 		approved No    
    S5‑245790 pCR TR 28.878 Add evaluation, conclusion and recommendation for Use Case #2 China Unicom pCR Approval Yes
Yes
 		approved No    
    S5‑245792 pCR TR 28.878 Add evaluation, conclusion and recommendation for Use Case #3 China Unicom pCR Approval Yes
YesEricsson offline comments rev 1
 		revised No S5‑246108  
    S5‑246108 pCR TR 28.878 Add evaluation, conclusion and recommendation for Use Case #3 China Unicom pCR Approval No
Yesd1
 		agreed No   S5‑245792
    S5‑245794 pCR TR 28.878 Add evaluation, conclusion and recommendation for Use Case #4 China Unicom pCR Approval Yes
YesEricsson offline comments rev 1
 		revised No S5‑246109  
    S5‑246109 pCR TR 28.878 Add evaluation, conclusion and recommendation for Use Case #4 China Unicom pCR Approval No
Yesd1
 		approved No   S5‑245794
    S5‑245795 pCR TR 28.878 Add evaluation, conclusion and recommendation for Use Case #5 China Unicom pCR Approval Yes
YesEricsson offline comments rev 1
 		revised No S5‑246110  
    S5‑246110 pCR TR 28.878 Add evaluation, conclusion and recommendation for Use Case #5 China Unicom pCR Approval No
Yesd1
 		approved No   S5‑245795
    S5‑245796 pCR TR 28.878 Add evaluation, conclusion and recommendation for Use Case #6 China Unicom pCR Approval Yes
YesEricsson offline comments First it seemed rev 1, but then not needed.
 		approved No    
    S5‑245831 Rel-19 pCR TR28.878 Editorial corrections ZTE Corporation pCR Approval Yes
YesEricsson offline comments rev 1
 		revised No S5‑246112  
    S5‑246112 Rel-19 pCR TR28.878 Editorial corrections ZTE Corporation pCR Approval No
Yes
 		approved No   S5‑245831
    S5‑245954 Draft TR 28.878 China Unicom draft TR Approval No
Yes
 		email approval No    
6.19.20 Study on energy efficiency and energy saving aspects of 5G networks and services S5‑245289 pCR TR 28.880 Update potential solution of EE KPIs evaluated from network data traffic performance dimension Huawei pCR Approval Yes
Yes
 		approved No    
    S5‑245290 pCR TR 28.880 Potential solution of EE KPIs evaluated from network quality performance dimension Huawei pCR Approval Yes
Yes
 		revised No S5‑246113  
    S5‑246113 pCR TR 28.880 Potential solution of EE KPIs evaluated from network quality performance dimension Huawei pCR Approval No
Yesd1
 		approved No   S5‑245290
    S5‑245291 pCR TR 28.880 Update potential solution of EE KPIs evaluated from availability performance dimension Huawei pCR Approval Yes
Yes
 		revised No S5‑246114  
    S5‑246114 pCR TR 28.880 Update potential solution of EE KPIs evaluated from availability performance dimension Huawei pCR Approval No
YesSamsung objected
 		noted No   S5‑245291
    S5‑245292 pCR TR 28.880 Evaluation of potential solutions for multi-dimensional energy efficiency metrics Huawei pCR Approval Yes
Yes
 		revised No S5‑246115  
    S5‑246115 pCR TR 28.880 Evaluation of potential solutions for multi-dimensional energy efficiency metrics Huawei pCR Approval No
YesEricsson objected
 		noted No   S5‑245292
    S5‑245293 pCR TR 28.880 Conclusion and recommendation for multi-dimensional energy efficiency metrics Huawei pCR Approval Yes
Yesconclusion for the last 3 Docs.
 		revised No S5‑246116  
    S5‑246116 pCR TR 28.880 Conclusion and recommendation for multi-dimensional energy efficiency metrics Huawei pCR Approval No
YesEricsson objected
 		noted No   S5‑245293
    S5‑245332 pCR TR 28.880 Conclusion and recommendation for renewable energy based LBO Huawei pCR Approval Yes
YesNokia: it does not make sense to add this attribute here, if RAN doesn't use this. Would be good to send an LS: S5-246028
 		revised No S5‑246029  
    S5‑246028 LS on renewable energy based LBO SA3 LS out Approval No
Yes(Huawei)
 		approved No    
    S5‑246029 pCR TR 28.880 Conclusion and recommendation for renewable energy based LBO Huawei pCR Approval No
Yesd1 need more time
 		approved No   S5‑245332
    S5‑245400 pCR TR 28.880 New clause for conclusions and recommendations Huawei, Deutsche Telekom pCR Agreement Yes
Yes
 		revised No S5‑246027  
    S5‑246027 pCR TR 28.880 New clause for conclusions and recommendations Huawei, Deutsche Telekom pCR Agreement No
Yesd1
 		approved No   S5‑245400
    S5‑245417 pCR TR 28.880 Updates after the publication of ETSI GS NFV IFA 027 V5.2.1 Huawei pCR Agreement Yes
Yes
 		approved No    
    S5‑245418 pCR TR 28.880 Potential solution for use case 1 Huawei, Deutsche Telekom pCR Agreement Yes
YesNokia disagreed
 		noted No    
    S5‑245419 pCR TR 28.880 Potential solution for use case #3 - Carbon emission of non-split gNB Huawei pCR Agreement Yes
Yes
 		revised No S5‑246030  
    S5‑246030 pCR TR 28.880 Potential solution for use case #3 - Carbon emission of non-split gNB Huawei pCR Agreement No
Yesd2
 		approved No   S5‑245419
    S5‑245420 pCR TR 28.880 Potential solution for use case #3: Renewable Energy Factor of non-split gNB Huawei, Deutsche Telekom pCR Agreement Yes
Yes
 		revised No S5‑246031  
    S5‑246031 pCR TR 28.880 Potential solution for use case #3: Renewable Energy Factor of non-split gNB Huawei, Deutsche Telekom pCR Agreement No
Yesd1
 		approved No   S5‑245420
    S5‑245421 pCR TR 28.880 Potential solution for use case #3 - Non-split gNB carbon intensity Huawei pCR Agreement Yes
Yes
 		revised No S5‑246032  
    S5‑246032 pCR TR 28.880 Potential solution for use case #3 - Non-split gNB carbon intensity Huawei pCR Agreement No
Yesd1 Ericsson objected
 		noted No   S5‑245421
    S5‑245422 pCR TR 28.880 Closure of use case #4 Huawei, Deutsche Telekom pCR Agreement Yes
Yesbased on previous docs Getting back later. Nokia objected.
 		noted No    
    S5‑245423 pCR TR 28.880 Closure of use case 5 Huawei, Deutsche Telekom pCR Agreement Yes
Yes
 		revised No S5‑246033  
    S5‑246033 pCR TR 28.880 Closure of use case 5 Huawei, Deutsche Telekom pCR Agreement No
Yesd1
 		approved No   S5‑245423
    S5‑245618 Rel-19 pCR TR 28.880 Potential solution for use case Handling of power shortages Nokia pCR Approval Yes
Yesoverlap with 5619
 		revised No S5‑246034  
    S5‑246034 Rel-19 pCR TR 28.880 Potential solution for use case Handling of power shortages Nokia pCR Approval No
Yeskeep open Huawei objected
 		noted No   S5‑245618
    S5‑245619 Rel-19 pCR TR 28.880 Potential solution for use case Enabling renewable energy consumption and carbon emission information reporting Nokia pCR Approval Yes
Yes
 		revised No S5‑246271  
    S5‑246271 Rel-19 pCR TR 28.880 Potential solution for use case Enabling renewable energy consumption and carbon emission information reporting Nokia pCR Approval No
YesSamsung wanted a revision.
 		revised No S5‑246293 S5‑245619
    S5‑246293 Rel-19 pCR TR 28.880 Potential solution for use case Enabling renewable energy consumption and carbon emission information reporting Nokia pCR Approval No
Yes
 		approved No   S5‑246271
    S5‑245620 Rel-19 pCR TR 28.880 Add use case and potential requirements to Enable energy type aware energy consumption reporting Nokia pCR Approval Yes
Yes
 		revised No S5‑246272  
    S5‑246272 Rel-19 pCR TR 28.880 Add use case and potential requirements to Enable energy type aware energy consumption reporting Nokia pCR Approval No
Yesd2 reissued as S5-246282 because of title change
 		withdrawn Yes   S5‑245620
    S5‑246282 Rel-19 pCR TR 28.880 Add use case on cell proximity based energy saving Nokia pCR Approval No
YesHuawei objects, need more time.
 		noted No    
    S5‑245621 Discussion paper on renewable energy information Nokia discussion Endorsement Yes
YesHuawei objects
 		noted No    
    S5‑245713 pCR TR 28.880 Conclusion and recommendation for the use case #10 Vodafone Ireland Plc pCR Approval Yes
Yes
 		withdrawn Yes    
    S5‑245716 pCR TR 28.880 Correction to use case #10 Vodafone Ireland Plc pCR Approval Yes
Yes
 		revised No S5‑246273  
    S5‑246273 pCR TR 28.880 Correction to use case #10 Vodafone Ireland Plc pCR Approval No
Yes
 		approved No   S5‑245716
    S5‑245717 pCR TR 28.880 Conclusion and recommendation for the use case #10 Vodafone Ireland Plc pCR Approval Yes
Yes
 		revised No S5‑246274  
    S5‑246274 pCR TR 28.880 Conclusion and recommendation for the use case #10 Vodafone Ireland Plc pCR Approval No
Yes
 		approved No   S5‑245717
    S5‑245846 Rel-19 pCR 28.880 Solution for QoS update Samsung R&D Institute India pCR Agreement Yes
Yes
 		noted No    
    S5‑245956 Draft TR 28.880 Samsung draft TR Approval No
Yes
 		email approval No    
6.19.21 Study on Enhanced OAM for management exposure to external consumers S5‑245616 Rel-19 pCR TR 28.879 Update Introduction, add scope and remove clause 5.2 and 5.3 Nokia pCR Approval Yes
Yes
 		approved No    
    S5‑245617 Rel-19 pCR TR 28.879 Addressing editHelp comments and Rapporteur cleanup Nokia pCR Approval Yes
Yes
 		approved No    
    S5‑245816 Rel-19 pCR TR 28.879 Add conclusions and recommendations for exposing management services Nokia Hungary pCR Approval Yes
Yes
 		noted No    
    S5‑245817 Rel-19 pCR TR 28.879 Add use case, requirements, potential solution and evaluation for service API consumption by an external MnS consumer Nokia Hungary pCR Approval Yes
Yes
 		noted No    
    S5‑245818 Rel-19 pCR TR 28.879 Clean up to clarify the roles of the MnS producer vs the MnF and differentiates between discovery info configuration and authorization Nokia Hungary pCR Approval Yes
YesEricsson: wording is not appropriate Nokia: need to merge
 		revised No S5‑246038  
    S5‑246038 Rel-19 pCR TR 28.879 Clean up to clarify the roles of the MnS producer vs the MnF and differentiates between discovery info configuration and authorization Nokia Hungary pCR Approval No
Yes
 		approved No   S5‑245818
    S5‑245819 Rel-19 pCR TR 28.879 Enhance exposure concepts and background Nokia Hungary pCR Approval Yes
YesEricsson: is not needed.
 		noted No    
    S5‑245820 Rel-19 pCR TR 28.879 Enhancements to the evaluation of the potential solutions for configuring discovery information Nokia Hungary pCR Approval Yes
YesNokia: would need a LS to SA6
 		revised No S5‑246041  
    S5‑246041 Rel-19 pCR TR 28.879 Enhancements to the evaluation of the potential solutions for configuring discovery information Nokia Hungary pCR Approval No
YesEricsson objected
 		noted No   S5‑245820
    S5‑245821 Rel-19 pCR TR 28.879 Evaluation analysis for the publishing of management services use case Nokia Hungary pCR Approval Yes
Yesmerged into 6040
 		merged No    
    S5‑245827 pCR TR 28.879 Configuring permissions of an external MnS consumer Ericsson Limited pCR   Yes
Yesdiscussion ongoing. Will come back at next meeting
 		noted No    
    S5‑245828 pCR TR 28.879 Publishing UC - updates on description and requirements Ericsson Limited pCR   Yes
Yes
 		revised No S5‑246039  
    S5‑246039 pCR TR 28.879 Publishing UC - updates on description and requirements Ericsson Limited pCR - No
YesNokia objects
 		noted No   S5‑245828
    S5‑245829 pCR TR 28.879 pCR TR 28.879 Publishing UC – updates on solution and evaluation Ericsson Limited pCR   Yes
Yescomments from Nokia, didn't agree with the propsed solution
 		revised No S5‑246040  
    S5‑246040 pCR TR 28.879 pCR TR 28.879 Publishing UC – updates on solution and evaluation Ericsson Limited pCR - No
Yesto be revised further!
 		revised No S5‑246283 S5‑245829
    S5‑246283 pCR TR 28.879 pCR TR 28.879 Publishing UC – updates on solution and evaluation Ericsson Limited pCR - No
Yes
 		approved No   S5‑246040
    S5‑245957 Draft TR 28.879 Nokia draft TR Approval No
Yes
 		email approval No    
7 Charging                      
7.1 Charging Plenary S5‑245215 CH agenda and time plan SA5 SWG CH Chair (MATRIXX Software) agenda   No
No
 		reserved No    
    S5‑245216 Charging exec report SA5 SWG CH Chair (MATRIXX Software) report   No
Yeslist of agreed CRs!
 		noted No    
    S5‑245217 Collection of useful contributions and external communication documents in CH SWG Vice Chair (Huawei Tech.(UK) Co.. Ltd) other   No
No
 		reserved No    
    S5‑245375 LS on Ranging/Sidelink Positioning Charging SA2 LS in Information Yes
Yes
 		postponed No    
    S5‑245575 Discussion Paper on SA5 Charging Specifications Structure Huawei discussion Discussion Yes
Yes
 		revised No S5‑245872  
    S5‑245872 Discussion Paper on SA5 Charging Specifications Structure Huawei discussion Discussion No
Yes
 		noted No   S5‑245575
    S5‑245870 (reserved) CH other discussion No
No
 		reserved No    
    S5‑245871 (reserved) CH other discussion No
No
 		reserved No    
    S5‑245922 (reserved) CH other discussion No
No
 		reserved No    
    S5‑245923 (reserved) CH other discussion No
No
 		reserved No    
    S5‑245924 (reserved) CH other discussion No
No
 		reserved No    
    S5‑245925 (reserved) CH other discussion No
No
 		reserved No    
    S5‑245926 (reserved) CH other discussion No
No
 		reserved No    
    S5‑245927 (reserved) CH other discussion No
No
 		reserved No    
    S5‑245928 (reserved) CH other discussion No
No
 		reserved No    
    S5‑245929 (reserved) CH other discussion No
No
 		reserved No    
    S5‑245930 (reserved) CH other discussion No
No
 		reserved No    
    S5‑245931 (reserved) CH other discussion No
No
 		reserved No    
    S5‑245932 (reserved) CH other discussion No
No
 		reserved No    
    S5‑245933 (reserved) CH other discussion No
No
 		reserved No    
    S5‑245934 (reserved) CH other discussion No
No
 		reserved No    
    S5‑245935 (reserved) CH other discussion No
No
 		reserved No    
    S5‑245936 (reserved) CH other discussion No
No
 		reserved No    
    S5‑245937 (reserved) CH other discussion No
No
 		reserved No    
    S5‑245938 (reserved) CH other discussion No
No
 		reserved No    
    S5‑245939 (reserved) CH other discussion No
No
 		reserved No    
    S5‑245940 (reserved) CH other discussion No
No
 		reserved No    
    S5‑245941 (reserved) CH other discussion No
No
 		reserved No    
    S5‑245942 (reserved) CH other discussion No
No
 		reserved No    
    S5‑245943 (reserved) CH other discussion No
No
 		reserved No    
    S5‑245944 (reserved) CH other discussion No
No
 		reserved No    
    S5‑245945 (reserved) CH other discussion No
No
 		reserved No    
    S5‑245946 (reserved) CH other discussion No
No
 		reserved No    
    S5‑245947 (reserved) CH other discussion No
No
 		reserved No    
    S5‑245948 (reserved) CH other discussion No
No
 		reserved No    
    S5‑245949 (reserved) CH other discussion No
No
 		reserved No    
7.2 New Charging Study/Work Item proposals S5‑245542 Rel-19 DP Femto Support Nokia discussion Discussion Yes
Yes
 		revised No S5‑245873  
    S5‑245873 Rel-19 DP Femto Support Nokia discussion Discussion No
Yes
 		noted No   S5‑245542
    S5‑245543 Rel-19 New SID on Charging Aspects of EEES Nokia SID new Agreement Yes
Yes
 		not pursued No    
    S5‑245559 Rel-19 DP on charging for 5GS LCS China Telecom discussion Discussion Yes
Yes
 		withdrawn Yes    
    S5‑245576 Discussion Paper on business models for Ambient IoT Huawei discussion Discussion Yes
Yes
 		noted No    
    S5‑245577 New WID on Charging for Ambient power-enabled Internet of Things Huawei, China Unicom WID new Agreement Yes
Yes
 		not pursued No    
7.3 Charging Maintenance and Rel-19 Charging small enhancements S5‑245561 Rel-18 DP Reference Points N107 and N108 Amdocs Software Systems Ltd discussion Approval Yes
Yes
 		noted No    
    S5‑245562 Rel-18 CR 32.240 Update N107 and N108 Definitions Amdocs Software Systems Ltd CR Approval Yes
Yes
 		revised No S5‑245878  
    S5‑245878 Rel-18 CR 32.240 Update N107 and N108 Definitions Amdocs Software Systems Ltd CR Approval No
NoNew Tdoc title Rel-18 CR 32.240 Correction on N107 and N108 for MVNO Charging?
 		reserved No   S5‑245562
    S5‑245563 Rel-19 CR 32.240 Update N107 and N018 Definitions Amdocs Software Systems Ltd CR Approval Yes
Yes
 		revised No S5‑245879  
    S5‑245879 Rel-19 CR 32.240 Update N107 and N018 Definitions Amdocs Software Systems Ltd CR Approval No
NoNew Tdoc title Rel-19 CR 32.240 Correction on N107 and N108 for MVNO Charging?
 		reserved No   S5‑245563
    S5‑245564 Rel-18 CR 32.240 Add CHF-CHF Interface Amdocs Software Systems Ltd CR Approval Yes
Yes
 		revised No S5‑245896  
    S5‑245896 Rel-18 CR 32.240 Add CHF-CHF Interface Amdocs Software Systems Ltd CR Approval No
No
 		reserved No   S5‑245564
    S5‑245565 Rel-19 CR 32.240 Add CHF-CHF Interface Amdocs Software Systems Ltd CR Approval Yes
Yes
 		revised No S5‑245897  
    S5‑245897 Rel-19 CR 32.240 Add CHF-CHF Interface Amdocs Software Systems Ltd CR Approval No
No
 		reserved No   S5‑245565
    S5‑245566 Rel-18 CR 32.255 Add Charging Architecture for MVNO Charging Amdocs Software Systems Ltd CR Approval Yes
Yes
 		revised No S5‑245880  
    S5‑245880 Rel-18 CR 32.255 Add Charging Architecture for MVNO Charging Amdocs Software Systems Ltd CR Approval No
NoNew Tdoc title Rel-18 CR 32.255 Correction on N107 and N108 for MVNO Charging
 		reserved No   S5‑245566
    S5‑245567 Rel-19 CR 32.255 Add Charging Architecture for MVNO Charging Amdocs Software Systems Ltd CR Approval Yes
Yes
 		revised No S5‑245881  
    S5‑245881 Rel-19 CR 32.255 Add Charging Architecture for MVNO Charging Amdocs Software Systems Ltd CR Approval No
No
 		reserved No   S5‑245567
    S5‑245568 Rel-18 CR 32.255 CHF Selection for Inter-CHF in Non-Roaming Amdocs Software Systems Ltd CR Approval Yes
Yes
 		revised No S5‑245884  
    S5‑245884 Rel-18 CR 32.255 CHF Selection for Inter-CHF in Non-Roaming Amdocs Software Systems Ltd CR Approval No
No
 		reserved No   S5‑245568
    S5‑245569 Rel-19 CR 32.255 CHF Selection for Inter-CHF in Non-Roaming Amdocs CR Approval Yes
Yes
 		revised No S5‑245885  
    S5‑245570 Rel-18 CR 32.256 Correction of Reference Points Amdocs CR Approval Yes
Yes
 		revised No S5‑245882  
    S5‑245882 Rel-18 CR 32.256 Correction of Reference Points Amdocs CR Approval No
No
 		reserved No   S5‑245570
    S5‑245571 Rel-19 CR 32.256 Correction of Reference Points Amdocs CR Approval Yes
Yes
 		revised No S5‑245883  
    S5‑245883 Rel-19 CR 32.256 Correction of Reference Points Amdocs CR Approval No
No
 		reserved No   S5‑245571
    S5‑245572 Rel-18 CR 32.256 CHF Selection for Inter-CHF Amdocs CR Approval Yes
Yes
 		revised No S5‑245903  
    S5‑245903 Rel-18 CR 32.256 CHF Selection for Inter-CHF Amdocs CR Approval No
No
 		reserved No   S5‑245572
    S5‑245573 Rel-19 CR 32.256 CHF Selection for Inter-CHF Amdocs Software Systems Ltd CR Approval Yes
Yes
 		withdrawn Yes    
    S5‑245578 Discussion Paper for correction on the non-blocking mode Huawei discussion Discussion Yes
Yes
 		noted No    
    S5‑245579 Rel-18 CR 32.290 Correction on the non-blocking mode Huawei CR Agreement Yes
Yes
 		not pursued No   S5‑243993
    S5‑245580 Rel-19 CR 32.290 Correction on the non-blocking mode Huawei CR Agreement Yes
Yes
 		not pursued No   S5‑243994
    S5‑245581 Rel-18 CR 32.291 Correction on the non-blocking mode Huawei CR Agreement Yes
Yes
 		not pursued No   S5‑241615
    S5‑245582 Rel-19 CR 32.291 Correction on the non-blocking mode Huawei CR Agreement Yes
Yes
 		not pursued No    
    S5‑245583 Rel-18 CR 32.254 Correction on the unsuccessful event charging Huawei CR Agreement Yes
Yes
 		not pursued No   S5‑243998
    S5‑245584 Rel-18 CR 32.291 Correction on the unsuccessful event charging Huawei CR Agreement Yes
Yes
 		not pursued No   S5‑241609
    S5‑245585 Rel-19 CR 32.291 Correction on the unsuccessful event charging Huawei CR Agreement Yes
Yes
 		not pursued No    
    S5‑245586 Rel-18 CR 32.298 Correction on the unsuccessful event charging Huawei CR Agreement Yes
Yes
 		not pursued No    
    S5‑245587 Rel-18 32.240 Correction on CHF deployment models Huawei, Nokia CR Agreement Yes
Yes
 		revised No S5‑245916 S5‑244000
    S5‑245916 Rel-18 32.240 Correction on CHF deployment models Huawei, Nokia CR Agreement No
No
 		reserved No   S5‑245587
    S5‑245588 Rel-19 32.240 Correction on CHF deployment models Huawei, Nokia CR Agreement Yes
Yes
 		revised No S5‑245917 S5‑244001
    S5‑245917 Rel-19 32.240 Correction on CHF deployment models Huawei, Nokia CR Agreement No
No
 		reserved No   S5‑245588
    S5‑245589 Rel-18 CR 32.290 Correction on CHF as NF consumer detected failure Huawei CR Agreement Yes
Yes
 		not pursued No   S5‑244002
    S5‑245590 Rel-19 CR 32.290 Correction on CHF as NF consumer detected failure Huawei CR Agreement Yes
Yes
 		not pursued No   S5‑244003
    S5‑245614 Rel-18 CR 32.256 CHF Selection for Inter-CHF Amdocs CR Approval Yes
Yes
 		revised No S5‑245921  
    S5‑245921 Rel-18 CR 32.256 CHF Selection for Inter-CHF Amdocs CR Approval No
No
 		reserved No   S5‑245614
    S5‑245639 Rel-19 CR 32.255 Clarifying the support of N107 and PCF Ericsson CR Agreement Yes
Yes
 		revised No S5‑245920  
    S5‑245920 Rel-19 CR 32.255 Clarifying the support of N107 and PCF Ericsson CR Agreement No
No
 		reserved No   S5‑245639
    S5‑245640 Rel-18 CR 32.274 Correction of references for SMS information Ericsson CR Agreement Yes
Yes
 		agreed No    
    S5‑245641 Rel-17 CR 32.291 Correction of ProblemDetails to use allOf Ericsson CR Agreement Yes
Yes
 		not pursued No    
    S5‑245642 Rel-18 CR 32.291 Correction of ProblemDetails to use allOf Ericsson LM CR Agreement Yes
Yes
 		not pursued No    
    S5‑245643 Rel-19 CR 32.291 Correction of ProblemDetails to use allOf Ericsson CR Agreement Yes
Yes
 		not pursued No    
    S5‑245644 Rel-17 CR 32.298 Correction of versions or format faults in ASN references Ericsson CR Agreement Yes
Yes
 		withdrawn Yes    
    S5‑245645 Rel-18 CR 32.298 Correction of IMSTrigger and InterCHF ASN Ericsson CR Agreement Yes
Yes
 		withdrawn Yes    
    S5‑245646 Rel-19 CR 32.298 Correction of IMSTrigger and InterCHF ASN Ericsson CR Agreement Yes
Yes
 		withdrawn Yes    
    S5‑245647 Rel-17 CR 32.298 Moving ASN to 3GPP Forge Ericsson CR Agreement Yes
Yes
 		withdrawn Yes    
    S5‑245648 Rel-18 CR 32.298 Moving ASN to 3GPP Forge Ericsson CR Agreement Yes
Yes
 		withdrawn Yes    
    S5‑245649 Rel-19 CR 32.298 Moving ASN to 3GPP Forge Ericsson CR Agreement Yes
Yes
 		withdrawn Yes    
    S5‑245767 Rel-19 CR 32.290 Message Sequence Handling Nokia CR Agreement Yes
Yes
 		revised No S5‑245919  
    S5‑245919 Rel-19 CR 32.290 Message Sequence Handling Nokia CR Agreement No
No
 		reserved No   S5‑245767
    S5‑245769 Rel-18 CR 32.290 Message Sequence Handling Nokia CR Agreement Yes
Yes
 		revised No S5‑245918  
    S5‑245918 Rel-18 CR 32.290 Message Sequence Handling Nokia CR Agreement No
No
 		reserved No   S5‑245769
7.4 Rel-19 Work Items                      
7.4.1 WID on CHF Segmentation S5‑245574 Rel-19 32.291 Add Charging Domains in Supported Features Amdocs Software Systems Ltd CR Approval Yes
Yes
 		revised No S5‑245874  
    S5‑245874 Rel-19 32.291 Add Charging Domains in Supported Features Amdocs Software Systems Ltd CR Approval No
No
 		reserved No   S5‑245574
    S5‑245650 LS on Usage of Charging Characteristics and CHF Group ID Ericsson LS out Approval Yes
Yes
 		noted No    
    S5‑245651 Rel-19 CR 32.255 Adding use of charging characteristics for CHF Group Ericsson CR Agreement Yes
Yes
 		revised No S5‑245876  
    S5‑245876 Rel-19 CR 32.255 Adding use of charging characteristics for CHF Group Ericsson CR Agreement No
No
 		reserved No   S5‑245651
    S5‑245652 Rel-19 CR 32.256 Adding use of charging characteristics for CHF Group Ericsson CR Agreement Yes
Yes
 		revised No S5‑245877  
    S5‑245877 Rel-19 CR 32.256 Adding use of charging characteristics for CHF Group Ericsson CR Agreement No
No
 		reserved No   S5‑245652
7.4.2 WID on Charging Aspects of Ranging and Sidelink Positioning S5‑245558 Add charging support for Ranging and Sidelink Positioning service China Telecom CR Approval Yes
Yes
 		withdrawn Yes    
7.4.3 WID on charging aspects for energy efficiency of 5G                      
7.4.4 WID on charging for indirect network sharing S5‑245653 Rel-19 CR 32.240 Addition network sharing Ericsson CR Agreement Yes
Yes
 		revised No S5‑245875  
    S5‑245875 Rel-19 CR 32.240 Addition network sharing Ericsson CR Agreement No
No
 		reserved No   S5‑245653
7.4.5 New WID on Charging Aspects for 5G ProSe Ph3                      
7.5 Charging Studies                      
7.5.1 Study on charging aspects of satellite access Phase 3 S5‑245284 pCR TR28.846 update the business scenario for roaming from terrestrial operator network to satellite operator network CSCN pCR Approval Yes
Yesinto 5654
 		merged No    
    S5‑245285 pCR TR28.846 update the business scenario for VNO which provide satellite communication services CSCN pCR Approval Yes
Yesinto 5654
 		merged No    
    S5‑245333 Add store and forward satellite operation charging solutions for SMS CATT pCR Approval Yes
Yes
 		revised No S5‑245908  
    S5‑245908 Add store and forward satellite operation charging solutions for SMS CATT pCR Approval No
No
 		reserved No   S5‑245333
    S5‑245334 Add store and forward satellite operation charging solutions for Control Plane CIoT CATT pCR Approval Yes
Yes
 		revised No S5‑245909  
    S5‑245909 Add store and forward satellite operation charging solutions for Control Plane CIoT CATT pCR Approval No
No
 		reserved No   S5‑245334
    S5‑245335 Add evaluation for store and forward satellite operation charging CATT pCR Approval Yes
Yes
 		revised No S5‑245910  
    S5‑245910 Add evaluation for store and forward satellite operation charging CATT pCR Approval No
No
 		reserved No   S5‑245335
    S5‑245591 Rel-19 pCR 28.846 Update charging scenario for Satellite Roaming Charging Huawei pCR Approval Yes
Yes
 		revised No S5‑245911  
    S5‑245911 Rel-19 pCR 28.846 Update charging scenario for Satellite Roaming Charging Huawei pCR Approval No
No
 		reserved No   S5‑245591
    S5‑245592 Rel-19 pCR 28.846 Introduce the solution for Satellite Roaming Charging Huawei pCR Approval Yes
Yes
 		revised No S5‑245912  
    S5‑245912 Rel-19 pCR 28.846 Introduce the solution for Satellite Roaming Charging Huawei pCR Approval No
No
 		reserved No   S5‑245592
    S5‑245654 Rel-19 pCR 28.846 Update of business roles and scenarios Ericsson pCR Approval Yes
Yes
 		revised No S5‑245878  
    S5‑245655 Rel-19 pCR 28.846 Clarification of topic 1 use cases Ericsson pCR Approval Yes
Yes
 		revised No S5‑245913  
    S5‑245913 Rel-19 pCR 28.846 Clarification of topic 1 use cases Ericsson pCR Approval No
No
 		reserved No   S5‑245655
    S5‑245656 Rel-19 pCR 28.846 Clarification of topic 2 use cases Ericsson pCR Approval Yes
Yes
 		revised No S5‑245914  
    S5‑245914 Rel-19 pCR 28.846 Clarification of topic 2 use cases Ericsson pCR Approval No
No
 		reserved No   S5‑245656
    S5‑245657 Rel-19 pCR 28.846 Clarification of topic 3 use cases Ericsson pCR Approval Yes
Yes
 		revised No S5‑245915  
    S5‑245915 Rel-19 pCR 28.846 Clarification of topic 3 use cases Ericsson pCR Approval No
No
 		reserved No   S5‑245657
    S5‑245964 Draft TR 28.846 CICT draft TR Approval No
Yes
 		email approval No    
7.5.2 Study on Charging Aspects of CAPIF S5‑245537 Rel-19 pCR 28.849 API Service Management Solution Nokia pCR Approval Yes
Yes
 		revised No S5‑245885  
    S5‑245885 Rel-19 pCR 28.849 API Service Management Solution Nokia pCR Approval No
No
 		reserved No   S5‑245537
    S5‑245538 Rel-19 pCR 28.849 API Service Management Evaluation Nokia pCR Approval Yes
Yes
 		revised No S5‑245886  
    S5‑245886 Rel-19 pCR 28.849 API Service Management Evaluation Nokia pCR Approval No
No
 		reserved No   S5‑245538
    S5‑245539 Rel-19 pCR 28.849 Multiple API Providers Solution Nokia pCR Approval Yes
Yes
 		revised No S5‑245887  
    S5‑245887 Rel-19 pCR 28.849 Multiple API Providers Solution Nokia pCR Approval No
No
 		reserved No   S5‑245539
    S5‑245540 Rel-19 pCR 28.849 Multiple API Providers Evaluation Nokia pCR Approval Yes
Yes
 		revised No S5‑245888  
    S5‑245888 Rel-19 pCR 28.849 Multiple API Providers Evaluation Nokia pCR Approval No
No
 		reserved No   S5‑245540
    S5‑245541 Rel-19 pCR 28.849 Topic#4 CAPIF Charging Scenarios and KI Nokia pCR Approval No
Yes
 		withdrawn Yes    
    S5‑245593 Rel-19 pCR 28.849 Update charging solution for API invocation Huawei pCR Approval Yes
Yes
 		revised No S5‑245889  
    S5‑245889 Rel-19 pCR 28.849 Update charging solution for API invocation Huawei pCR Approval No
No
 		reserved No   S5‑245593
    S5‑245594 Rel-19 pCR 28.849 New charging scenario for API invoker operation Huawei pCR Approval Yes
Yes
 		revised No S5‑245890  
    S5‑245890 Rel-19 pCR 28.849 New charging scenario for API invoker operation Huawei pCR Approval No
No
 		reserved No   S5‑245594
    S5‑245595 Rel-19 pCR 28.849 New charging solution for API invoker operation Huawei pCR Approval Yes
Yes
 		revised No S5‑245891  
    S5‑245891 Rel-19 pCR 28.849 New charging solution for API invoker operation Huawei pCR Approval No
No
 		reserved No   S5‑245595
    S5‑245596 Rel-19 pCR 28.849 New charging solution for API invoker management Huawei pCR Approval Yes
Yes
 		revised No S5‑245892  
    S5‑245892 Rel-19 pCR 28.849 New charging solution for API invoker management Huawei pCR Approval No
No
 		reserved No   S5‑245596
    S5‑245597 Rel-19 pCR 28.849 New charging solution for service API management Huawei pCR Approval Yes
Yes
 		revised No S5‑245893  
    S5‑245893 Rel-19 pCR 28.849 New charging solution for service API management Huawei pCR Approval No
No
 		reserved No   S5‑245597
    S5‑245658 Rel-19 pCR 28.849 Update of relationships for RNAA Ericsson pCR Approval Yes
Yes
 		approved No    
    S5‑245659 Rel-19 pCR 28.849 Solution for topic 1 reusing NEF charging Ericsson pCR Approval Yes
Yes
 		revised No S5‑245894  
    S5‑245894 Rel-19 pCR 28.849 Solution for topic 1 reusing NEF charging Ericsson pCR Approval No
No
 		reserved No   S5‑245659
    S5‑245660 Rel-19 pCR 28.849 Solution for topic 1 using subscription Ericsson pCR Approval Yes
Yes
 		revised No S5‑245895  
    S5‑245895 Rel-19 pCR 28.849 Solution for topic 1 using subscription Ericsson pCR Approval No
No
 		reserved No   S5‑245660
    S5‑245661 Rel-19 pCR 28.849 Solution for topic 3 reusing NEF charging Ericsson pCR Approval Yes
Yes
 		revised No S5‑245898  
    S5‑245898 Rel-19 pCR 28.849 Solution for topic 3 reusing NEF charging Ericsson pCR Approval No
No
 		reserved No   S5‑245661
    S5‑245718 pCR TR 28.849 Topic#4 CAPIF Charging Scenarios and KI Nokia pCR Approval Yes
Yes
 		revised No S5‑245899  
    S5‑245899 pCR TR 28.849 Topic#4 CAPIF Charging Scenarios and KI Nokia pCR Approval No
No
 		reserved No   S5‑245718
    S5‑245760 Rel-19 pCR 28.849 Editorial Changes Nokia pCR Approval Yes
Yes
 		approved No    
    S5‑245965 Draft TR 28.849 Nokia draft TR Approval No
Yes
 		email approval No    
7.5.3 Study on Charging aspects of next generation real time communication services phase 2 S5‑245280 Rel-19 pCR 28.851 Adding solution on IMS converged charging for standalone IMS Data Channel China Mobile, Huawei pCR Approval Yes
Yes
 		revised No S5‑245900  
    S5‑245900 Rel-19 pCR 28.851 Adding solution on IMS converged charging for standalone IMS Data Channel China Mobile, Huawei pCR Approval No
No
 		reserved No   S5‑245280
    S5‑245598 Rel-19 pCR 28.851 New charging solution for IMS network capabilities exposure Huawei, China Mobile pCR Approval Yes
Yes
 		revised No S5‑245901  
    S5‑245901 Rel-19 pCR 28.851 New charging solution for IMS network capabilities exposure Huawei, China Mobile pCR Approval No
No
 		reserved No   S5‑245598
    S5‑245599 Rel-19 pCR 28.851 Update charging scenario for DC application usage Huawei pCR Approval Yes
Yes
 		revised No S5‑245902  
    S5‑245902 Rel-19 pCR 28.851 Update charging scenario for DC application usage Huawei pCR Approval No
No
 		reserved No   S5‑245599
    S5‑245600 Rel-19 pCR 28.851 New charging solution for DC application download Huawei pCR Approval Yes
Yes
 		revised No S5‑245903  
    S5‑245662 Rel-19 pCR 28.851 Solution for topic 3 reusing NEF charging Ericsson pCR Approval Yes
Yesinto 5598
 		merged No    
    S5‑245966 Draft TR 28.851 CMCC draft TR Approval No
Yes
 		email approval No    
7.5.4 Study on Charging aspects of Uncrewed Aerial Vehicle S5‑245237 Rel-19 pCR 28.853 Add solution for charging with UAV Identifier China Mobile E-Commerce Co. pCR Approval Yes
Yes
 		revised No S5‑245904  
    S5‑245904 Rel-19 pCR 28.853 Add solution for charging with UAV Identifier China Mobile E-Commerce Co. pCR Approval No
No
 		reserved No   S5‑245237
    S5‑245601 Rel-19 pCR 28.853 Introduce the Aircraft-to-Everything for UAS Charging Huawei pCR Approval Yes
Yes
 		revised No S5‑245905  
    S5‑245905 Rel-19 pCR 28.853 Introduce the Aircraft-to-Everything for UAS Charging Huawei pCR Approval No
No
 		reserved No   S5‑245601
    S5‑245602 Rel-19 pCR 28.853 New charging solution for provisioning for A2X communication Huawei pCR Approval Yes
Yes
 		approved No    
    S5‑245603 Rel-19 pCR 28.853 New charging solution for non-roaming A2X Communication Huawei pCR Approval Yes
Yes
 		revised No S5‑245906  
    S5‑245906 Rel-19 pCR 28.853 New charging solution for non-roaming A2X Communication Huawei pCR Approval No
No
 		reserved No   S5‑245603
    S5‑245604 Rel-19 pCR 28.853 New charging solution for roaming A2X Communication Huawei pCR Approval Yes
Yes
 		revised No S5‑245907  
    S5‑245907 Rel-19 pCR 28.853 New charging solution for roaming A2X Communication Huawei pCR Approval No
No
 		reserved No   S5‑245604
    S5‑245605 Rel-19 pCR 28.853 Update charging solution for UAS service invocation Huawei pCR Approval Yes
Yes
 		approved No    
    S5‑245967 Draft TR 28.853 CMCC draft TR Approval No
Yes
 		email approval No    
8 Any Other Business                      
9 Closing of the meeting