Tdoc List

2025-04-11 15:54

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‑251200 Agenda WG Chair agenda Approval Yes
Yes
 		approved No    
3 IPR and legal declaration S5‑251201 IPR and legal declaration WG Chair other Information Yes
Yes1.Call for IPR (Meetings) "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 " 2. Antitrust policy Reminder "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‑251202 Report from last SA5 meeting MCC report Approval Yes
Yes
 		approved No    
4.2 Inter-organizational reports                      
5 SA5 level issues                      
5.1 Administrative issues at SA5 level S5‑251203 Time Plan for SA5 Plenary and OAM sessions WG Chair agenda Information Yes
YesSamsung recommended to move some parallel sessions
 		noted No    
    S5‑251204 agenda_with_Tdocs_sequence_Plenary&OAM WG Chair agenda Information Yes
Yes
 		noted No    
    S5‑251205 SA5 working procedures WG Chair other Information Yes
Yesstage 2 / stage 3 alignment needed. Check with MCC developer. Nokia offered training.
 		revised No S5‑252112  
    S5‑252112 SA5 working procedures WG Chair other Information No
Yes
 		endorsed No   S5‑251205
    S5‑251206 SA5 Meeting facility requirements WG Chair other Information Yes
Yes
 		noted No    
    S5‑251208 Post meeting email approval status WG Vice Chair (Ericsson) other Information No
Yespost-meeting doc
 		noted No    
    S5‑251211 Plenary and OAM Chair notes and conclusions WG Chair report Information No
Yeskeep open, conclude in closing rapp. call 17.4. is cancelled. 15.5. is kept
 		noted No    
    S5‑251214 Rel-19 SA5 work plan TU table WG Chair other Information Yes
Yeskeep open rapporteurs pls. check TU table
 		revised No S5‑252122  
    S5‑252122 Rel-19 SA5 work plan TU table WG Chair other Information No
Yes
 		noted No   S5‑251214
    S5‑251218 Latest SA5 Rel-19 WIs-SIs WG Chair other Information Yes
Yes
 		noted No    
    S5‑251219 Rel-19 SA5 work planning WG Chair other Information Yes
Yes
 		revised No S5‑251766  
    S5‑251766 Rel-19 SA5 work planning WG Chair other Information Yes
Yes
 		endorsed No   S5‑251219
    S5‑251220 Rel-20 SA5 work planning WG Chair other Information Yes
Yes
 		revised No S5‑251767  
    S5‑251767 Rel-20 SA5 work planning WG Chair other Information No
Yesd3
 		endorsed No   S5‑251220
    S5‑251413 Maintenance of TSs in SA5 Ericsson discussion Endorsement Yes
Yes
 		revised No S5‑251769  
    S5‑251769 Maintenance of TSs in SA5 Ericsson discussion Endorsement Yes
YesConclusion: alternative 1 was accepted. LS S5-251768 will be sent to TSG SA.
 		noted No   S5‑251413
    S5‑251758 Selecting the Release for the SA5 OAM and Charging aspects SA5 leadership & MCC other Agreement Yes
Yes
 		revised No S5‑251770  
    S5‑251770 Selecting the Release for the SA5 OAM and Charging aspects SA5 leadership & MCC other Information Yes
Yesjust for review. target to agree next meeting; then brought to SA.
 		noted No   S5‑251758
5.2 Technical issues at SA5 level                      
5.3 Liaison statements at SA5 level S5‑251328 LS on Ambient IoT progress of RAN3 RAN3 LS in Information Yes
Yes
 		noted No    
    S5‑251771 LS response on Ambient IoT progress of RAN3 SA5 LS out Approval Yes
Yes
 		approved No    
    S5‑251330 Publication of ETSI NFV group report on architectural support for NFV evolution ETSI ISG NFV LS in Information Yes
Yesplanning a joint workshop during NFV meeting not yet sure keep open
 		withdrawn Yes    
    S5‑252049 LS reply to ETSI NFV for the publication of NFV-IFA054 SA5 LS out Approval No
Yesd2 not available next meeting
 		withdrawn Yes    
    S5‑251409 Reply LS on per-UE UE performance metrics SA5 LS out Approval Yes
Yes
 		revised No S5‑252056  
    S5‑252056 Reply LS on per-UE UE performance metrics SA5 LS out Approval Yes
Yes
 		approved No   S5‑251409
    S5‑251768 LS to SA for guidance of maintenance of specifications SA5 LS out Approval Yes
Yes
 		revised No S5‑252123  
    S5‑252123 LS to SA for guidance of maintenance of specifications SA5 LS out Approval No
Yesfor email approval
 		for email approval No   S5‑251768
5.4 SA5 meeting calendar S5‑251207 SA5 meeting calendar WG Chair other Information Yes
Yesnoted in closing plenary
 		noted No    
5.5 Rel-20 topic preparation S5‑251316 New Study on AI/ML management enhancements NEC, Intel SID new Agreement Yes
YesSA5 Chair: we are not agreeing here. Will try in May. We just technically agree the objectives. Yellow more discussion, gree: agree Huawei: WT-1,2,3 needs rewording; clarify 5 Nokia: how is AIML integrated? Deutsche Telekom: alignment with other groups is important
 		revised No S5‑251772  
    S5‑251772 New Study on AI/ML management enhancements NEC, Intel SID new Agreement Yes
Yesd4
 		noted No   S5‑251316
    S5‑251366 New WID on OAM for XR and media services (XRM) ZTE Corporation WID new Agreement Yes
Yes
 		revised No S5‑251773  
    S5‑251773 New WID on OAM for XR and media services (XRM) ZTE Corporation WID new Agreement Yes
Yes
 		noted No   S5‑251366
    S5‑251387 New SID on energy efficiency and energy saving aspects of 5G Advanced Huawei SID new Agreement Yes
YesDeutsche Telekom: pl.s consider energy reduction in AIML, as this neds lots of energy. Fibercop: pls. extend to CCL. Nokia: unclear with MADCOL.
 		revised No S5‑251774  
    S5‑251774 New SID on energy efficiency and energy saving aspects of 5G Advanced Huawei SID new Agreement Yes
Yesd3
 		noted No   S5‑251387
    S5‑251453 SA5 Rel-20 5GA 25Q1 moderated discussion – ISAC management ZTE Corporation other Approval Yes
Yeswait for SA2 inputs keep open
 		noted No    
    S5‑251489 New SID on SBMA enhancement phase 4 Moderator (Huawei) SID new Agreement Yes
Yes
 		revised No S5‑251775  
    S5‑251775 New SID on SBMA enhancement phase 4 Moderator (Huawei) SID new Agreement Yes
Yesd3
 		noted No   S5‑251489
    S5‑251498 New SID on Management aspect of Network Digital Twins phase 2 China Mobile SID new Agreement Yes
YesEricsson: needs more clarification & motivation Samsung agrees with NTT DOCOMO on 2.1 & 3. Deutsche Telekom: the data synch is not clear. Ericsson: don't agree with external TR
 		revised No S5‑251776  
    S5‑251776 New SID on Management aspect of Network Digital Twins phase 2 China Mobile SID new Agreement Yes
Yesd3
 		noted No   S5‑251498
    S5‑251558 New SID Study on intent driven management services for mobile network phase 4 Moderator (Huawei, Ericsson) SID new Agreement Yes
Yes
 		revised No S5‑251777  
    S5‑251777 New SID Study on intent driven management services for mobile network phase 4 Moderator (Huawei, Ericsson) SID new Agreement Yes
Yesd5
 		noted No   S5‑251558
    S5‑251593 WID on Study on Management Data Analytics (MDA) – Phase 4 Huawei Tech. Japan, K.K. SID new Agreement Yes
YesSamsung: does not reflect NWM comments. Nokia, Ericsson: is too generic.
 		revised No S5‑251778  
    S5‑251778 WID on Study on Management Data Analytics (MDA) – Phase 4 Huawei Tech. Japan, K.K. SID new Agreement Yes
Yes
 		noted No   S5‑251593
    S5‑251634 New SID on cloud aspects of management and orchestration phase 2 China Mobile SID new Agreement Yes
YesHuawei: continue Rel-19 first.
 		revised No S5‑251779  
    S5‑251779 New SID on cloud aspects of management and orchestration phase 2 China Mobile SID new Agreement Yes
Yes
 		noted No   S5‑251634
    S5‑251652 New SID on Semantic-based Network Management Moderator(China Unicom, Samsung) SID new Agreement Yes
YesNokia: it's too late for 5G. Is more for 6G. Ericssson, NTT DOCOMO, NEC, DT agreed. keep open Samsung: have inputs. Chair: but will be for 6G.
 		revised No S5‑251780  
    S5‑251780 New SID on Semantic-based Network Management Moderator(China Unicom, Samsung) SID new Agreement Yes
Yes
 		noted No   S5‑251652
    S5‑251740 New SID on Study for Data management phase 3 Nokia SID new Agreement Yes
YesEricsson: needs more concretization.
 		revised No S5‑251781  
    S5‑251781 New SID on Study for Data management phase 3 Nokia, Verizon SID new Agreement Yes
Yes
 		revised No S5‑252124 S5‑251740
    S5‑252124 New SID on Study for Data management phase 3 Nokia, Verizon SID new Agreement No
Yes
 		noted No   S5‑251781
6 OAM&P                      
6.1 OAM&P Plenary S5‑251209 OAM action list WG Vice Chair (Nokia) other Information No
Yes
 		noted No    
    S5‑251210 OAM Exec Report WG Vice Chair (Nokia) report Information No
Yes
 		noted No    
    S5‑251212 Collection of useful endorsed documents in OAM WG Vice Chair (Nokia) discussion Discussion No
Yes
 		noted No    
    S5‑251213 Collection of external communication documents in OAM WG Vice Chair (Nokia) discussion Discussion No
Yes
 		noted No    
    S5‑251221 OAM breakout notes WG Chair report Discussion No
Yes
 		noted No    
    S5‑251222 Support Continuous MDT on reply to RAN3 incoming LS (R3-250788) Ericsson, AT&T, CMCC, Deutsche Telekom discussion Endorsement Yes
Yes
 		revised No S5‑252050  
    S5‑252050 Support Continuous MDT on reply to RAN3 incoming LS (R3-250788) Ericsson, AT&T, CMCC, Deutsche Telekom, ZTE discussion Endorsement Yes
Yesadd ZTE
 		not pursued No   S5‑251222
    S5‑251223 Reply LS to LS on Continuous MDT SA5 LS out Approval Yes
Yes
 		revised No S5‑252051  
    S5‑252051 Reply LS to LS on Continuous MDT SA5 LS out Approval No
Yes
 		withdrawn Yes   S5‑251223
    S5‑251226 LS on the new NGMN Publication: ‘MLOps for Highly Autonomous Network’ NGMN Alliance LS in Information Yes
Yes
 		noted No    
    S5‑251314 Reply LS to ITU-T SG2 on methodology coordination SA5 LS out Approval Yes
Yes
 		approved No    
    S5‑251322 LS on 5G Trace to support UE level measurement (SA5#159) CT4 LS in Information Yes
Yes
 		replied to No    
    S5‑251323 LS reply to LS on energy information collection from OAM to EIF CT LS in Information Yes
Yes
 		noted No    
    S5‑251324 LS on per-UE UE performance metrics (SA5#159) RAN3 LS in Information Yes
Yes
 		replied to No    
    S5‑251325 Reply LS on MBS Communication Service Type RAN3 LS in Information Yes
Yes
 		noted No    
    S5‑251326 LS on Continuous MDT RAN3 LS in Information Yes
YesS5-252114
 		replied to No    
    S5‑252053 Reply LS to RAN3 LS on Continuous MDT SA5 LS out Approval Yes
Yestypo
 		revised No S5‑252114  
    S5‑252114 Reply LS to RAN3 LS on Continuous MDT SA5 LS out Approval Yes
Yes
 		approved No   S5‑252053
    S5‑251327 Reply LS on OAM requirements to support regenerative payload transport links RAN3 LS in Information Yes
YesHuawei suggested to postpone.
 		postponed No    
    S5‑251331 LS on the initiation of a new Technical Report ITU-T TR.M.rnscesnr “Requirements of network service consistency evaluation for shared network resources” ITU-T SG2 LS in Information Yes
Yes
 		noted No    
    S5‑251332 LS/r on methodology harmonization update (reply to 3GPP TSG SA5-244109 - LS57) ITU-T SG2 LS in Information Yes
YesS5-251314
 		replied to No    
    S5‑251372 LS on the consent of Recommendation ITU-T M. 3042(ex. M.fcnhe): "Framework of communication network health evaluation" ITU-T SG2 LS in Information Yes
YesNoted
 		noted No    
    S5‑251615 LS reply to LS on 5G Trace to support UE level measurement SA5 LS out Approval Yes
Yes
 		revised No S5‑252055  
    S5‑252055 LS reply to LS on 5G Trace to support UE level measurement SA5 LS out Approval Yes
Yeschange font
 		revised No S5‑252113 S5‑251615
    S5‑252113 LS reply to LS on 5G Trace to support UE level measurement SA5 LS out Approval Yes
Yes
 		approved No   S5‑252055
    S5‑251741 Continuous MDT Discussion Nokia discussion Endorsement Yes
Yes
 		revised No S5‑252052  
    S5‑252052 Continuous MDT Discussion Nokia discussion Endorsement No
YesNoted
 		noted No   S5‑251741
    S5‑251742 Reply LS on Continuous MDT SA5 LS out Approval Yes
Yes
 		merged No    
    S5‑251990 LS to SA3 on management of secure backhaul for NTN SA5 LS out Approval No
Yesd1 need to check CRs Samsung: we need this LS.
 		approved No    
6.2 New OAM&P Work Item proposals                      
6.2.1 Intelligence and Automation                      
6.2.2 Management Architecture and Mechanisms S5‑251230 Revised WID on 5G performance measurements and KPIs phase 4 Ericsson LM WID revised Agreement Yes
Yes
 		agreed No    
    S5‑251627 Rel-19 Revised WID on Management Aspects of NTN Phase 2 CATT, China Unicom WID revised Agreement Yes
Yesmerged with S5-251529
 		revised No S5‑252022  
    S5‑252022 Rel-19 Revised WID on Management Aspects of NTN Phase 2 CATT, China Unicom WID revised Agreement Yes
Yes
 		agreed No   S5‑251627
6.2.3 Support of New Services S5‑251529 Revised WID on Management Aspects of NTN Phase 2 Samsung R&D Institute UK WID revised Agreement Yes
YesHuawei: baseline is wrong merged into S5-252022
 		merged No S5‑252022  
6.3 Pre-Rel-18 Maintenance                      
6.3.1 Methodology                      
6.3.2 ANL                      
6.3.3 MDAS                      
6.3.4 AI/ML                      
6.3.5 Energy efficiency S5‑251664 Rel-17 CR TS 28.310 Clarify information of service Ericsson, Deutsche Telekom CR Agreement Yes
YesHuawei: like to keep tenant.
 		not pursued No    
    S5‑252102 Rel-17 CR TS 28.310 Clarify information of service Ericsson, Deutsche Telekom CR Agreement No
Yes
 		withdrawn Yes    
    S5‑251665 Rel-18 CR TS 28.310 Clarify information of service Ericsson, Deutsche Telekom CR Agreement Yes
Yeswrong WIC Huawei objected
 		not pursued No    
    S5‑251666 Rel-19 CR TS 28.310 Clarify information of service Ericsson, Deutsche Telekom CR Agreement Yes
Yes
 		not pursued No    
6.3.6 Intent driven management                      
6.3.7 SON S5‑251429 Rel-16 CR 28.541 Update for allowed value ueAccProbabilityDist (stage3, yang) Ericsson Canada Inc. CR Agreement Yes
Yes
 		agreed No    
    S5‑251430 Rel-17 CR 28.541 Update for allowed value ueAccProbabilityDist (stage3, yang) Ericsson Canada Inc. CR Approval Yes
YesRAN x
 		revised No S5‑252103  
    S5‑252103 Rel-17 CR 28.541 Update for allowed value ueAccProbabilityDist (stage3, yang) Ericsson Canada Inc. CR Agreement Yes
Yes
 		agreed No   S5‑251430
    S5‑251431 Rel-18 CR 28.541 Update for allowed value ueAccProbabilityDist (stage3, yang) Ericsson Canada Inc. CR Agreement Yes
Yes
 		agreed No    
    S5‑251432 Rel-19 CR 28.541 Update for allowed value ueAccProbabilityDist (stage3, yang) Ericsson Canada Inc. CR Agreement Yes
YesRAN x
 		revised No S5‑252104  
    S5‑252104 Rel-19 CR 28.541 Update for allowed value ueAccProbabilityDist (stage3, yang) Ericsson Canada Inc. CR Agreement Yes
Yes
 		agreed No   S5‑251432
6.3.8 QMC                      
6.3.9 Network slicing management S5‑251667 Rel-16 CR TS 28.530 Clarify tenant information concept Ericsson, Deutsche Telekom CR Agreement Yes
YesHuawei disagrees
 		not pursued No    
    S5‑251668 Rel-17 CR TS 28.530 Clarify tenant information concept Ericsson, Deutsche Telekom CR Agreement Yes
Yes
 		not pursued No    
    S5‑251669 Rel-18 CR TS 28.530 Clarify tenant information concept Ericsson, Deutsche Telekom CR Approval Yes
Yes
 		not pursued No    
    S5‑251670 Rel-19 CR TS 28.530 Clarify tenant information concept Ericsson, Deutsche Telekom CR Approval Yes
Yes
 		not pursued No    
6.3.10 MEC management                      
6.3.11 General NRM S5‑251295 Rel19 CR TS28.541 correction to inconsistency between stage 2 and stage 3 concerning SubNetwork and ManagedElement containment Nokia, Nokia Shanghai Bell CR Agreement Yes
YesTEI18->19
 		revised No S5‑252105  
    S5‑252105 Rel19 CR TS28.541 correction to inconsistency between stage 2 and stage 3 concerning SubNetwork and ManagedElement containment Nokia, Nokia Shanghai Bell CR Agreement Yes
Yes
 		agreed No   S5‑251295
    S5‑251296 Rel18 CR TS28.541 correction to inconsistency between stage 2 and stage 3 concerning SubNetwork and ManagedElement containment Nokia, Nokia Shanghai Bell CR Agreement Yes
Yeskeep open
 		agreed No    
    S5‑251297 Rel18 CR TS28.541 correction to stage 3 of SatelliteBackhaulInfo Nokia, Nokia Shanghai Bell CR Agreement Yes
Yes
 		agreed No    
    S5‑251298 Rel19 CR TS28.541 correction to stage 3 of SatelliteBackhaulInfo Nokia, Nokia Shanghai Bell CR Agreement Yes
Yes
 		revised No S5‑252106  
    S5‑252106 Rel19 CR TS28.541 correction to stage 3 of SatelliteBackhaulInfo Nokia, Nokia Shanghai Bell CR Agreement Yes
Yes
 		agreed No   S5‑251298
    S5‑251418 Rel-17 CR 28.622 Change dnPrefix properties Ericsson India Private Limited CR Agreement No
Yes
 		withdrawn Yes    
    S5‑251419 Rel-17 CR 28.622 Change dnPrefix properties Ericsson India Private Limited CR Agreement Yes
Yeskeep open
 		agreed No    
    S5‑251420 Rel-18 CR 28.622 Change dnPrefix properties Ericsson India Private Limited CR Agreement Yes
Yes
 		agreed No    
    S5‑251421 Rel-19 CR 28.622 Change dnPrefix properties Ericsson India Private Limited CR Agreement Yes
Yes
 		agreed No    
    S5‑251424 Rel-17 CR 28.623 Change dnPrefix properties Ericsson India Private Limited CR Agreement Yes
Yes
 		agreed No    
    S5‑251425 Rel-18 CR 28.623 Change dnPrefix properties Ericsson India Private Limited CR Agreement Yes
Yes
 		agreed No    
    S5‑251426 Rel-19 CR 28.623 Change dnPrefix properties Ericsson India Private Limited CR Agreement Yes
Yes
 		agreed No    
    S5‑251595 Rel-17 CR TS 28.541 Fix invalid reference Huawei CR Agreement Yes
Yestitle typo Rel-19
 		revised No S5‑252096  
    S5‑252096 Rel-19 CR TS 28.541 Fix invalid reference Huawei CR Agreement Yes
Yes
 		agreed No   S5‑251595
    S5‑251703 Rel15 CR TS 32.156 Enhancement of the description of the “isNotifyable” attribute property Nokia CR Agreement Yes
Yes
 		not pursued No    
    S5‑251704 Rel16 CR TS 32.156 Enhancement of the description of the “isNotifyable” attribute property and correction of the default value for the “isReadable” attribute property Nokia CR Approval Yes
Yes
 		not pursued No    
    S5‑251705 Rel17 CR TS 32.156 Enhancement of the description of the “isNotifyable” attribute property and correction of the default value for the “isReadable” attribute property Nokia CR Approval Yes
Yes
 		not pursued No    
    S5‑251706 Rel18 CR TS 32.156 Enhancement of the description of the “isNotifyable” attribute property and correction of the default value for the “isReadable” attribute property Nokia CR Approval Yes
Yes
 		not pursued No    
    S5‑251707 Rel19 CR TS 32.156 Enhancement of the description of the “isNotifyable” attribute property and correction of the default value for the “isReadable” attribute property Nokia CR Agreement Yes
YesCat.A->B
 		revised No S5‑252107  
    S5‑252107 Rel19 CR TS 32.156 Enhancement of the description of the “isNotifyable” attribute property and correction of the default value for the “isReadable” attribute property Nokia CR Agreement Yes
Yes
 		agreed No   S5‑251707
6.3.12 PM/KPI                      
6.3.13 Trace/MDT                      
6.3.14 Other S5‑251349 Rel19 CR TS28.104 correction to reference Nokia, Nokia Shanghai Bell CR Agreement Yes
Yesmerged into S5-251882
 		merged No S5‑251882  
6.4 Rel-18 Maintenance and Rel-19 small Enhancements                      
6.4.1 Self-Configuration of RAN NEs S5‑251673 Rel-18 CR TS 28.317 Correct import table Ericsson, Deutsche Telekom CR Agreement Yes
Yes
 		agreed No    
    S5‑251674 Rel-19 CR TS 28.317 Correct import table Ericsson, Deutsche Telekom CR Agreement Yes
Yes
 		agreed No    
6.4.2 Management Data Analytics phase 2 S5‑251624 Rel 18 CR TS 28.104 Correct References for MDA reporting Ericsson CR Agreement Yes
Yes
 		not pursued No    
    S5‑251625 Rel 19 CR TS 28.104 Correct References for MDA reporting Ericsson CR Agreement Yes
YesCat. A->F
 		revised No S5‑252057  
    S5‑252057 Rel 19 CR TS 28.104 Correct References for MDA reporting Ericsson CR Agreement Yes
Yes
 		agreed No   S5‑251625
6.4.3 AI/ML management S5‑251352 Rel-18 CR TS 28.105 Correction on the isWritable propoerty of AIMLInferenceName in the MLTrainingRequest ZTE Corporation, Intel, Huawei CR Agreement Yes
YesEricsson: should have been a draftCR, it's against the rules to present a CR.
 		not pursued No    
    S5‑251353 Rel-19 CR TS 28.105 Correction on the isWritable propoerty of AIMLInferenceName in the MLTrainingRequest ZTE Corporation, Intel, Huawei CR Agreement Yes
Yes
 		not pursued No    
6.4.4 Intent driven Management Service for mobile network phase 2 S5‑251671 Rel-18 CR TS 28.312 Correct import table Ericsson, Deutsche Telekom CR Agreement Yes
Yes
 		revised No S5‑252058  
    S5‑252058 Rel-18 CR TS 28.312 Correct import table Ericsson, Deutsche Telekom CR Agreement Yes
Yes
 		agreed No   S5‑251671
    S5‑251672 Rel-19 CR TS 28.312 Correct import table Ericsson, Deutsche Telekom CR Agreement Yes
Yescoverpage ver!
 		revised No S5‑252059  
    S5‑252059 Rel-19 CR TS 28.312 Correct import table Ericsson, Deutsche Telekom CR Agreement Yes
Yes
 		agreed No   S5‑251672
6.4.5 Service based management architecture S5‑251416 Rel-18 CR 28.111 How to use notifyPotentialFaultyAlarmList Ericsson India Private Limited CR Agreement Yes
Yes
 		revised No S5‑252060  
    S5‑252060 Rel-18 CR 28.111 How to use notifyPotentialFaultyAlarmList Ericsson India Private Limited CR Agreement Yes
Yes
 		agreed No   S5‑251416
    S5‑251417 Rel-19 CR 28.111 How to use notifyPotentialFaultyAlarmList Ericsson India Private Limited CR Agreement Yes
Yes
 		revised No S5‑252061  
    S5‑252061 Rel-19 CR 28.111 How to use notifyPotentialFaultyAlarmList Ericsson India Private Limited CR Agreement Yes
Yes
 		agreed No   S5‑251417
    S5‑251438 Rel-19 CR 28.622 Remove deprecated notification Ericsson India Private Limited CR Agreement Yes
Yes
 		revised No S5‑252062  
    S5‑252062 Rel-19 CR 28.622 Remove deprecated notification Ericsson India Private Limited CR Agreement Yes
Yes
 		agreed No   S5‑251438
    S5‑251439 Rel-19 CR 28.541 Remove deprecated notification Ericsson India Private Limited CR Agreement Yes
Yes
 		revised No S5‑252063  
    S5‑252063 Rel-19 CR 28.541 Remove deprecated notification Ericsson India Private Limited CR Agreement Yes
Yes
 		agreed No   S5‑251439
    S5‑251451 Rel-18 CR 28.623 Modify YANG mapping of Subnetwork Ericsson India Private Limited CR Agreement Yes
Yes
 		agreed No    
    S5‑251452 Rel-19 CR 28.623 Modify YANG mapping of Subnetwork Ericsson India Private Limited CR Agreement Yes
Yes
 		agreed No    
    S5‑251459 Rel-18 CR 28.541 Modify YANG mapping of Subnetwork Ericsson India Private Limited CR Agreement No
Yes
 		withdrawn Yes    
    S5‑251461 Rel-19 CR 28.541 Modify YANG mapping of Subnetwork Ericsson India Private Limited CR Approval No
Yes
 		withdrawn Yes    
    S5‑251479 Rel-18 CR TS 28.111 Add missing solution components Huawei CR Agreement Yes
Yespls. come back at the next meeting
 		not pursued No    
    S5‑251480 Rel-19 CR TS 28.111 Add missing solution components Huawei CR Agreement Yes
Yespls. come back at the next meeting
 		not pursued No    
    S5‑251481 Rel-18 CR TS 28.111 Correction on reliability of alarm lists Huawei CR Agreement Yes
Yesbasic object must be clarified
 		not pursued No    
    S5‑252064 Rel-18 CR TS 28.111 Correction on reliability of alarm lists Huawei CR Agreement No
Yes
 		withdrawn Yes    
    S5‑251482 Rel-19 CR TS 28.111 Correction on reliability of alarm lists Huawei CR Agreement Yes
Yes
 		not pursued No    
    S5‑252065 Rel-19 CR TS 28.111 Correction on reliability of alarm lists Huawei CR Agreement No
Yes
 		withdrawn Yes    
    S5‑251543 Rel 18 CR TS 28.532 correct the format of scope parameter to align with stage3 HUAWEI CR Agreement Yes
YesEricsson: Reason for change is inverted
 		revised No S5‑252066  
    S5‑252066 Rel 18 CR TS 28.532 correct the format of scope parameter to align with stage3 HUAWEI CR Agreement Yes
YesNokia objected
 		not pursued No   S5‑251543
    S5‑251544 Rel 19 CR TS 28.532 correct the scope operation parameter in stage 3 Huawei CR Approval Yes
Yes
 		revised No S5‑252067  
    S5‑252067 Rel 19 CR TS 28.532 correct the scope operation parameter in stage 3 Huawei CR Approval Yes
Yesformat!
 		not pursued No   S5‑251544
    S5‑251562 Rel-18 CR TS 28.111 Clarify notifyChangedAlarmGeneral Huawei, Ericsson CR Agreement Yes
Yes
 		agreed No    
    S5‑251563 Rel-19 CR TS 28.111 Clarify notifyChangedAlarmGeneral Huawei, Ericsson CR Agreement Yes
Yes
 		agreed No    
    S5‑251564 Rel-18 CR TS 28.111 Add missing ThresholdInfo dataType and related definition Huawei CR Agreement Yes
Yesco-signed with Nokia, Ericsson
 		revised No S5‑252068  
    S5‑252068 Rel-18 CR TS 28.111 Add missing ThresholdInfo dataType and related definition Huawei, Nokia, Ericsson CR Agreement Yes
Yes
 		agreed No   S5‑251564
    S5‑251565 Rel-19 CR TS 28.111 Add missing ThresholdInfo dataType and related definition Huawei CR Agreement Yes
Yes
 		revised No S5‑252069  
    S5‑252069 Rel-19 CR TS 28.111 Add missing ThresholdInfo dataType and related definition Huawei, Nokia CR Agreement Yes
Yes
 		agreed No   S5‑251565
    S5‑251730 Rel-19 CR 28.622 Add new generic type KeyValueList Ericsson India Private Limited CR Approval Yes
Yes
 		revised No S5‑251938  
    S5‑251938 Rel-19 CR 28.622 Add new generic type KeyValueList Ericsson India Private Limited CR Approval No
Yesno chance of a successful update. The number was and will not be used.
 		withdrawn Yes   S5‑251730
6.4.6 Network slicing provisioning rules                      
6.4.7 Network slice provisioning enhancement                      
6.4.8 Management of Trace/MDT phase 2 S5‑251616 Rel-18 CR 32.422 Clarification on SMF obtaining Trace control and measurement parameters from UDM Huawei CR Agreement Yes
YesEricsson co-sign
 		revised No S5‑252070  
    S5‑252070 Rel-19 CR 32.422 Clarification on SMF obtaining Trace control and measurement parameters from UDM Huawei, Ericsson CR Agreement Yes
Yes
 		agreed No   S5‑251616
    S5‑251617 Rel-18 CR 32.422 Clarification on SMF obtaining trace control and configuration parameters from UDM Huawei CR Agreement Yes
Yeswrong title!
 		revised No S5‑252071  
    S5‑252071 Rel-19 CR 32.422 Clarification on SMF obtaining trace control and configuration parameters from UDM Huawei, Ericsson CR Agreement Yes
Yes
 		agreed No   S5‑251617
6.4.9 5G performance measurements and KPIs phase 3 S5‑251234 Rel-18 CR TS 28.552 Corrections of subcounters and filters Ericsson, Rakuten Mobile, Samsung CR Agreement Yes
YesNokia co-sign
 		revised No S5‑252072  
    S5‑252072 Rel-18 CR TS 28.552 Corrections of subcounters and filters Ericsson, Rakuten Mobile, Samsung, Nokia CR Agreement Yes
Yes
 		agreed No   S5‑251234
    S5‑251235 Rel-19 CR TS 28.552 Corrections of subcounters and filters Ericsson, Rakuten Mobile, Samsung CR Agreement Yes
YesNokia co-signed
 		revised No S5‑252073  
    S5‑252073 Rel-19 CR TS 28.552 Corrections of subcounters and filters Ericsson, Rakuten Mobile, Samsung, Nokia CR Agreement Yes
Yes
 		agreed No   S5‑251235
    S5‑251236 Rel-18 CR TS 28.552 Distribution of UE throughput Ericsson CR Agreement Yes
Yes
 		agreed No    
    S5‑251237 Rel-19 CR TS 28.552 Distribution of UE throughput Ericsson CR Agreement Yes
Yes
 		agreed No    
    S5‑251587 Rel-19 CR 28.532 Enhance notifyFilePreparationError definition Ericsson Canada Inc. CR Agreement Yes
YesNokia: fileCreationErrorInfoList?
 		revised No S5‑252074  
    S5‑252074 Rel-19 CR 28.532 Enhance notifyFilePreparationError definition Ericsson Canada Inc. CR Agreement Yes
Yes
 		agreed No   S5‑251587
    S5‑251597 Rel-18 CR TS 28.552 PLMN name inconsistency Ericsson CR Agreement Yes
Yes
 		revised No S5‑252075  
    S5‑252075 Rel-18 CR TS 28.552 PLMN name inconsistency Ericsson CR Agreement Yes
Yes
 		agreed No   S5‑251597
    S5‑251598 Rel-19 CR TS 28.552 PLMN name inconsistency Ericsson CR Agreement Yes
Yesoverlap with ZTE CR S5-251996.
 		revised No S5‑252076  
    S5‑252076 Rel-19 CR TS 28.552 PLMN name inconsistency Ericsson CR Agreement Yes
Yes
 		agreed No   S5‑251598
    S5‑251692 Rel-18 CR TS28.552 Add missing EP_N9 for GTP capacity related measurements ZTE Corporation CR Approval Yes
Yes
 		agreed No    
    S5‑251693 Rel-19 CR TS28.552 Add missing EP_N9 for GTP capacity related measurements ZTE Corporation CR Approval Yes
Yes
 		agreed No    
    S5‑251737 Rel-19 CR TS 28.558 Correction on the UE identifer Nokia CR Agreement Yes
Yesneed feedback from Intel (not present) The date should be up to date.
 		revised No S5‑252077  
    S5‑252077 Rel-19 CR TS 28.558 Correction on the UE identifer Nokia, Ericsson CR Agreement Yes
Yesd1
 		agreed No   S5‑251737
    S5‑251738 Rel-19 CR TS 28.552 Corrections on Filter Definition Nokia CR Agreement Yes
Yesfirst merged into S5-252072 Later Samsung objected, as the CR is conflicting with Ericsson's S5-251234. Not pursued.
 		not pursued No    
    S5‑251739 Rel-19 CR TS 28.552 Corrections on Filter Definition Nokia CR Agreement Yes
Yes
 		not pursued No    
6.4.10 Enhancement of QoE Measurement Collection                      
6.4.11 Additional NRM features phase 2 S5‑251350 Rel-18 CR TS 28.541 Typo corrections and missing definitions ZTE Corporation, Orange CR Agreement Yes
YesNokia co-signed
 		revised No S5‑252078  
    S5‑252078 Rel-18 CR TS 28.541 Typo corrections and missing definitions ZTE Corporation, Orange, Nokia CR Agreement Yes
Yes
 		agreed No   S5‑251350
    S5‑251351 Rel-19 CR TS 28.541 Typo corrections and missing definitions ZTE Corporation, Orange CR Agreement Yes
YesNokia co-signed
 		revised No S5‑252079  
    S5‑252079 Rel-19 CR TS 28.541 Typo corrections and missing definitions ZTE Corporation, Orange, Nokia CR Agreement Yes
Yes
 		agreed No   S5‑251351
    S5‑251659 Rel-19 CR 28.541 Align predefinedPccRuleSet attributes with the definitions in TS 29.512 Ericsson, Deutsche Telekom CR Agreement Yes
Yes
 		revised No S5‑252080  
    S5‑252080 Rel-19 CR 28.541 Align predefinedPccRuleSet attributes with the definitions in TS 29.512 Ericsson, Deutsche Telekom CR Agreement Yes
Yes
 		agreed No   S5‑251659
    S5‑251689 Rel-19 CR TS28.541 Fix isOrdered and isUnique Attribute properties ZTE Corporation CR Agreement Yes
YesNokia co-signed conflict with S5-251351. merged into S5-252079
 		merged No S5‑252079  
6.4.12 Management Aspects related to NWDAF                      
6.4.13 Enhanced Edge Computing Management                      
6.4.14 Management Aspect of 5GLAN                      
6.4.15 Management Aspects of NTN S5‑251591 Rel-18 CR 28541 Correct support qualifier condition for ephemerisInfoSetRef Ericsson CR Agreement Yes
Yes
 		agreed No    
    S5‑251690 Rel-18 CR TS28.541 Fix nTNTAClist for stage 3 OpenAPI ZTE Corporation CR Agreement Yes
Yes
 		agreed No    
    S5‑251691 Rel-19 CR TS28.541 Fix nTNTAClist for stage 3 OpenAPI ZTE Corporation CR Agreement Yes
Yes
 		agreed 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                      
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 S5‑251561 Rel-18 CR TS 28.557 Update procedure of management of tenant to align with access control solution Huawei CR Agreement Yes
YesEricsson: Diagram is wrong. 2. Difference between technical concept and business concept.
 		revised No S5‑252081  
    S5‑252081 Rel-18 CR TS 28.557 Update procedure of management of tenant to align with access control solution Huawei, Ericsson CR Agreement Yes
Yes
 		agreed No   S5‑251561
    S5‑251729 Rel-18 CR TS 28.557 Fix wrong references and correct solution for NPN-SC mgmt Ericsson GmbH, Eurolab CR Agreement Yes
Yes
 		revised No S5‑252082  
    S5‑252082 Rel-18 CR TS 28.557 Fix wrong references and correct solution for NPN-SC mgmt Ericsson GmbH, Eurolab CR Agreement Yes
Yes
 		agreed No   S5‑251729
6.4.24 Network and Service Operations for Energy Utilities S5‑251716 Rel-18 CR TS 28.318 Fix affectedArea attribute for DSO service outage use case Ericsson GmbH, Eurolab CR Agreement Yes
Yes
 		agreed No    
    S5‑251717 Rel-19 CR TS 28.318 Fix affectedArea attribute for DSO service outage use case Ericsson GmbH, Eurolab CR Agreement Yes
Yes
 		agreed No    
6.4.25 Rel-18 CAT B/C alignment CR(s) due to the work led by other 3GPP Working Groups                      
6.4.26 Rel-18 CAT B/C SA5 internal alignment and other CAT F CR(s) S5‑251233 Rel-18 CR TS 32.404 Corrections on measurement name size Ericsson CR Agreement Yes
YesSamsung objected, as it will affect existing implementations Rel-15 to -18. discusison about 32/64 bit length. Keep open Samsung objected.
 		not pursued No    
    S5‑251282 Rel-18 CR 28.111 YANG stage-3 corrections Ericsson India Private Limited CR Agreement Yes
YesEricsson wanted to include changes from S5-251564.
 		revised No S5‑252083  
    S5‑252083 Rel-18 CR 28.111 YANG stage-3 corrections Ericsson India Private Limited CR Agreement Yes
Yes
 		agreed No   S5‑251282
    S5‑251283 Rel-19 CR 28.111 YANG stage-3 corrections Ericsson India Private Limited CR Agreement Yes
Yes
 		revised No S5‑252084  
    S5‑252084 Rel-19 CR 28.111 YANG stage-3 corrections Ericsson India Private Limited CR Agreement Yes
Yes
 		agreed No   S5‑251283
    S5‑251284 Rel-18 CR 28.623 YANG stage-3 corrections Ericsson India Private Limited CR Agreement No
Yes
 		withdrawn Yes    
    S5‑251285 Rel-19 CR 28.623 YANG stage-3 corrections Ericsson India Private Limited CR Agreement Yes
Yes
 		agreed No    
    S5‑251286 Rel-18 CR 28.623 YANG stage-3 corrections Ericsson India Private Limited CR Agreement Yes
Yes
 		agreed No    
    S5‑251289 Rel-18 CR 28.541 YANG stage-3 corrections Ericsson India Private Limited CR Agreement Yes
Yes
 		agreed No    
    S5‑251290 Rel-19 CR 28.541 YANG stage-3 corrections Ericsson India Private Limited CR Agreement Yes
Yes
 		agreed No    
    S5‑251406 Rel-18 CR TS 28.111 Correction on Alarm Definition NTT DOCOMO, Ericsson CR Agreement Yes
Yesdate keep open Nokla: defer to next meeting. Alarm needs operator attention. But why not a fault?
 		not pursued No    
    S5‑251407 Rel-19 CR TS 28.111 Correction on Alarm Definition NTT DOCOMO, Ericsson CR Agreement Yes
Yes
 		not pursued No    
6.4.27 OAM Rel-19 small enhancements S5‑251239 Rel-19 CR TS 28.560 Corrections on networkInterfaceTypeList Ericsson, Vodafone CR Agreement Yes
Yescoversheet version
 		revised No S5‑252085  
    S5‑252085 Rel-19 CR TS 28.560 Corrections on networkInterfaceTypeList Ericsson, Vodafone CR Agreement Yes
Yes
 		agreed No   S5‑251239
    S5‑251240 Rel-19 CR TS 28.560 Corrections on PCAPNG header Ericsson, Vodafone CR Agreement Yes
Yescoversheet version
 		revised No S5‑252086  
    S5‑252086 Rel-19 CR TS 28.560 Corrections on PCAPNG header Ericsson, Vodafone CR Agreement Yes
Yes
 		agreed No   S5‑251240
    S5‑251287 Addressing ENs in TS 28.560 Vodafone, Ericsson CR Agreement Yes
Yesno source to TSG; also for following Nokia, Deutsche Telekom co-sign
 		revised No S5‑252087  
    S5‑252087 Addressing ENs in TS 28.560 Vodafone, Ericsson, Nokia, Deutsche Telekom CR Agreement Yes
Yes
 		agreed No   S5‑251287
    S5‑251288 Removal of already addressed Editor's Note Vodafone CR Agreement Yes
Yesco sign Nokia, Ericsson, Deutsche Telekom
 		revised No S5‑252088  
    S5‑252088 Removal of already addressed Editor's Note Vodafone, Nokia, Ericsson, Deutsche Telekom CR Agreement Yes
Yes
 		agreed No   S5‑251288
    S5‑251380 Rel-19 CR TS 28.622 Correct misalignment issue for notificationTypes in stage2 and stage3 Huawei CR Agreement Yes
Yeskeep open
 		agreed No    
    S5‑251382 Rel-19 CR TS 28.623 Update the YANG definition for notificationTypes to align with stage 2 definition Huawei CR Agreement Yes
Yesoffline comments from Ericsson
 		revised No S5‑252092  
    S5‑252092 Rel-19 CR TS 28.623 Update the YANG definition for notificationTypes to align with stage 2 definition Huawei CR Agreement Yes
Yeskeep open
 		revised No S5‑252115 S5‑251382
    S5‑252115 Rel-19 CR TS 28.623 Update the YANG definition for notificationTypes to align with stage 2 definition Huawei CR Agreement Yes
YesEricsson supports
 		agreed No   S5‑252092
    S5‑251383 Rel-19 CR TS 28.533 Correct wrong references Huawei CR Agreement Yes
Yesmerged into S5-252093
 		merged No S5‑252093  
    S5‑252093 Rel-19 CR TS 28.533 Corrections Huawei CR Agreement Yes
Yes
 		agreed No    
    S5‑251384 Rel-19 CR TS 28.533 Fix errors in clause 4.5 Huawei CR Agreement Yes
YesS5-252093
 		merged No S5‑252093  
    S5‑251385 Rel-19 CR TS 28.533 Correct note in clause 3.1 Huawei CR Agreement Yes
YesS5-252093
 		merged No S5‑252093  
    S5‑251389 Rel-19 CR TS 28.623 Implement the writeOnly property for triggerHeartbeatNtf Huawei CR Agreement Yes
Yes
 		agreed No    
    S5‑251390 Rel-19 CR TS 28.622 Update Attribute constraints for TimeWindow Huawei CR Agreement Yes
YesNokia & Ericssson offline comments
 		revised No S5‑252094  
    S5‑252094 Rel-19 CR TS 28.622 Update Attribute constraints for TimeWindow Huawei CR Agreement Yes
YesNokia objected
 		not pursued No   S5‑251390
    S5‑251391 Rel-19 CR TS 28.537 Correct procedures for heartbeat Huawei CR Agreement Yes
Yes
 		not pursued No    
    S5‑251414 Addressing EN for supporting type of signalling Vodafone, Samsung CR Agreement Yes
Yesco-sign Ericsson
 		revised No S5‑252089  
    S5‑252089 Addressing EN for supporting type of signalling Vodafone, Samsung, Ericsson CR Agreement Yes
Yes
 		agreed No   S5‑251414
    S5‑251415 Removal of Editor's Note on encoding Vodafone CR Agreement Yes
Yesno source to TSG
 		revised No S5‑252090  
    S5‑252090 Removal of Editor's Note on encoding Vodafone CR Agreement Yes
Yes
 		agreed No   S5‑251415
    S5‑251500 Rel-19 CR TS 28.622 Corrections of Trace Reference Notifications Nokia CR Agreement Yes
Yes
 		agreed No    
    S5‑251557 Rel-19 CR 28.541 Add control attribute for LTM cell switch Ericsson CR Agreement Yes
YesNokia offline comments
 		revised No S5‑252095  
    S5‑252095 Rel-19 CR 28.541 Add control attribute for LTM cell switch Ericsson CR Agreement Yes
Yes
 		agreed No   S5‑251557
    S5‑251621 Rel 19 CR TS 28.541 Remove support qualifier from attribute constraints for NR NRM Ericsson CR Agreement Yes
Yesdate, +'TS'
 		revised No S5‑252097  
    S5‑252097 Rel 19 CR TS 28.541 Remove support qualifier from attribute constraints for NR NRM Ericsson CR Agreement Yes
Yes
 		agreed No   S5‑251621
    S5‑251622 Rel 19 CR TS 28.541 Remove support qualifier from attribute constraints for Network Slice NRM Ericsson CR Agreement Yes
Yesdate, +'TS'
 		revised No S5‑252098  
    S5‑252098 Rel 19 CR TS 28.541 Remove support qualifier from attribute constraints for Network Slice NRM Ericsson CR Agreement Yes
Yes
 		agreed No   S5‑251622
    S5‑251623 Rel 19 CR TS 28.541 Remove support qualifier from attribute constraints for 5GC NRM Ericsson CR Agreement Yes
Yesdate, +'TS'
 		revised No S5‑252099  
    S5‑252099 Rel 19 CR TS 28.541 Remove support qualifier from attribute constraints for 5GC NRM Ericsson CR Agreement Yes
Yes
 		agreed No   S5‑251623
    S5‑251628 Rel-19 CR TS 28.541 Correction on wrong attribute property definition.docx CATT CR Agreement Yes
Yes
 		revised No S5‑252100 S5‑250932
    S5‑252100 Rel-19 CR TS 28.541 Correction on wrong attribute property definition.docx CATT CR Agreement Yes
Yes
 		agreed No   S5‑251628
    S5‑251649 Correct the description of maximum number of PDU sessions of network slice Huawei CR Agreement Yes
Yesdate
 		revised No S5‑252101  
    S5‑252101 Correct the description of maximum number of PDU sessions of network slice Huawei CR Agreement Yes
Yes
 		agreed No   S5‑251649
    S5‑251726 Rel-19 CR TS 28.622 Correction of Area Scope Parameter Nokia CR Agreement Yes
Yes
 		agreed No    
    S5‑251727 Rel-19 CR TS 32.422 Correction of Area Scope Parameter Nokia CR Agreement Yes
Yes
 		agreed No    
6.19 OAM&P Rel-19 Study and Work Items                      
6.19.1 Study on AI/ML management - phase 2 (completed)                      
6.19.1.1 AI/ML management phase 2 S5‑251258 Input to draftCR TS28.105 Coordination AIML inference Nokia other Approval Yes
Yes
 		not treated No    
    S5‑251259 Input to draftCR TS28.105 Enhance AIML inference emulation Nokia other Approval Yes
Yes
 		not treated No    
    S5‑251260 Input to draftCR TS28.105 NRM for AIML emulation environment Nokia other Approval Yes
Yes
 		not treated No    
    S5‑251261 Input to draftCR TS28.105 NRM for ML-Knowledge-based TL Nokia other Approval Yes
Yes
 		revised No S5‑252041  
    S5‑252041 Input to draftCR TS28.105 NRM for ML-Knowledge-based TL Nokia other Approval Yes
Yes+'input' to draftCR
 		revised No S5‑252133 S5‑251261
    S5‑252133 Input to draftCR TS28.105 NRM for ML-Knowledge-based TL Nokia other Approval No
Yes
 		approved No   S5‑252041
    S5‑251354 Input to DraftCR Rel-19 TS 28.105 Add Management Scenario for RL ZTE Corporation, NEC, Intel other Agreement Yes
Yes
 		not treated No    
    S5‑251355 Input to DraftCR Rel-19 TS 28.105 Add Procedure Diagram for FL Server selection and determination ZTE Corporation,NEC, Intel other Agreement Yes
Yes
 		revised No S5‑251785  
    S5‑251785 Input to DraftCR Rel-19 TS 28.105 Add Procedure Diagram for FL Server selection and determination ZTE Corporation,NEC, Intel other Agreement Yes
YesEricsson objected
 		noted No   S5‑251355
    S5‑251356 Input to DraftCR Rel-19 TS 28.105 Add Procedure Diagram for FL Client selection ZTE Corporation,NEC, Intel other Agreement Yes
Yessame comments as S5-251355 merged into S5-251785
 		merged No S5‑251785  
    S5‑251357 Input to DraftCR Rel-19 TS 28.105 Update the UC and Req of Reinforcement Learning ZTE Corporation other Approval Yes
Yes
 		revised No S5‑251788  
    S5‑251788 Input to DraftCR Rel-19 TS 28.105 Update the UC and Req of Reinforcement Learning ZTE Corporation, Ericsson other Approval Yes
Yeskeep open
 		approved No   S5‑251357
    S5‑251358 Input to DraftCR Rel-19 TS 28.105 Add New Use Case and Requirements of Sustainable AIML for ML training ZTE Corporation other Approval Yes
Yes
 		revised No S5‑252044  
    S5‑252044 Input to DraftCR Rel-19 TS 28.105 Add New Use Case and Requirements of Sustainable AIML for ML training ZTE Corporation other Agreement Yes
YesEricsson objected
 		noted No   S5‑251358
    S5‑251359 Input to DraftCR Rel-19 TS 28.105 Add Solution for Sustainable AIML for ML training ZTE Corporation other Agreement Yes
Yesmerge into S5-251611
 		merged No    
    S5‑251360 Input to DraftCR Rel-19 TS 28.105 Enhancement on AIMLSupportedFunction to support inference in LMF ZTE Corporation other Agreement Yes
Yes
 		not treated No    
    S5‑251361 Rel-19 CR TS 28.541 Enhancement on LMF NRM to Support the Inference Functionality in LMF ZTE Corporation CR Agreement Yes
Yes
 		not treated No    
    S5‑251362 Input to DraftCR Rel-19 TS 28.105 Add New AI/ML functionalities management scenario for LMF ZTE Corporation other Agreement Yes
Yes
 		revised No S5‑252048  
    S5‑252048 Input to DraftCR Rel-19 TS 28.105 Add New AI/ML functionalities management scenario for LMF ZTE Corporation, Ericsson other Agreement Yes
Yesd1
 		approved No   S5‑251362
    S5‑251363 Input to DraftCR Rel-19 TS 28.105 Add Solution for Distributed Learning ZTE Corporation other Approval Yes
Yesmerged into S5-251633.
 		merged No S5‑251633  
    S5‑251364 DP on the NRM Design for AIMLInferenceFunction ZTE Corporation discussion Approval Yes
Yes
 		not treated No    
    S5‑251365 Input to DraftCR Rel-19 CR TS 28.105 Enhancement on AIMLInferenceFunction NRM ZTE Corporation other Agreement Yes
Yes
 		not treated No    
    S5‑251410 Input to draftCR TS 28.105 Add NRMs on LCM for Federated Learning Intel, NEC, ZTE, Samsung, Nokia other Approval Yes
Yeswrong CR coversheet Samsung agreed with Huawei, requirements need to come from consumer.
 		revised No S5‑251784  
    S5‑251784 Input to draftCR TS 28.105 Add NRMs on LCM for Federated Learning Intel, NEC, ZTE, Samsung, Nokia other Approval Yes
YesEricsson objected
 		noted No   S5‑251410
    S5‑251411 Input to draftCR TS 28.105 Add NRMs on LCM for Reinforcement Learning Intel, ZTE, NEC other Approval Yes
Yesmerged into S5-252040
 		merged No S5‑252040  
    S5‑251412 Input to draftCR TS 28.105 Enhance UC for management of Reinforcement Learning Intel, NEC other Approval Yes
Yes
 		not treated No    
    S5‑251444 Rel19 input to DraftCR TS28.105 New use case on Coordination between the ML capabilities Nokia, Nokia Shanghai Bell, China mobile, TELUS other Approval Yes
Yes
 		not treated No    
    S5‑251496 Input to DraftCR Rel-19 TS 28.105 Add UC for prediction latency China Mobile other Approval Yes
YesS5-252045
 		merged No S5‑252045  
    S5‑251497 Input to DraftCR Rel-19 TS 28.105 Add UC for AIML explainability China Mobile other Approval Yes
YesS5-252047
 		merged No S5‑252047  
    S5‑251506 Input to draftCR TS 28.105 Pre-specialized training and Fine-tuning China Mobile, ZTE other Approval Yes
YesNTT DOCOMO: want to uinderstand the difference between pretraining and pre-specialized tr. merged into S5-251782.
 		merged No S5‑251782  
    S5‑251507 Input to Draft CR Rel-19 CR TS 28.105 Add solution for Pre-specialized training and fine-tuning China Mobile, ZTE other Approval Yes
Yesmerged into S5-251783
 		merged No S5‑251783  
    S5‑251530 Rel-19 InputToDraftCR 28.105 solution for Impact management Samsung R&D Institute UK other Approval Yes
Yes
 		revised No S5‑252108  
    S5‑252108 Rel-19 InputToDraftCR 28.105 solution for Impact management Samsung R&D Institute UK, ZTE, Ericsson other Approval Yes
Yes
 		approved No   S5‑251530
    S5‑251541 Rel-19 InputToDraftCR 28.105 RL UC and Requirements Samsung R&D Institute UK other Approval Yes
YesETSI MCC: title should be aligned to 3GU, otherwise doc type in unknown Nokia: shall->should Samsung: agree
 		revised No S5‑251787  
    S5‑251787 Rel-19 InputToDraftCR 28.105 RL UC and Requirements Samsung R&D Institute UK, Ericsson other Approval Yes
Yeskeep open
 		approved No   S5‑251541
    S5‑251545 Rel-19 InputToDraftCR TS 28.105 enhance the description for managing AIML based capabilities Huawei other Approval Yes
Yes
 		not treated No    
    S5‑251546 Rel-19 InputToDraftCR TS 28.105 add procedure of management of AIML capabilities for NG-RAN and MDA Huawei other Approval Yes
Yes
 		not treated No    
    S5‑251547 Rel-19 InputToDraftCR TS 28.105 Update the description for managing ML models in use in a live network Huawei other Approval Yes
Yes
 		revised No S5‑252046  
    S5‑252046 Rel-19 InputToDraftCR TS 28.105 Update the description for managing ML models in use in a live network Huawei, NEC, Ericsson other Approval Yes
Yes
 		approved No   S5‑251547
    S5‑251548 Rel-19 InputToDraftCR TS 28.105 add solution for exploration in reinforcement learning Huawei other Approval Yes
Yeswrong CR coversheet
 		revised No S5‑252040  
    S5‑252040 Rel-19 InputToDraftCR TS 28.105 add solution for exploration in reinforcement learning Huawei, Samsung, Nokia, Intel, NEC, ZTE other Approval Yes
YesNokia objected
 		noted No   S5‑251548
    S5‑251549 Rel-19 InputToDraftCR TS 28.105 Add use case and requirements for reinforcement learning conflict management Huawei other Approval Yes
YesETSI MCC: wrong CR coversheet SA5 Chair: offline RL is within Rel-19 scope. Samsung: onine+offline has been agreed in the last meeting. Ericsson: online+offline is a training technique, RLFL is learning technique. Plus the environment. Suggested to discuss separately.
 		revised No S5‑251786  
    S5‑251786 Rel-19 InputToDraftCR TS 28.105 Add use case and requirements for reinforcement learning conflict management Huawei other Approval Yes
YesEricsson objected
 		noted No   S5‑251549
    S5‑251550 Rel-19 InputToDraftCR TS 28.105 Add solutions of training conflict management for reinforcement learning Huawei other Approval Yes
Yes
 		not treated No    
    S5‑251551 Rel-19 InputToDraftCR TS 28.105 add use case for Management of Local explanation in AIML inference Huawei other Agreement Yes
Yes
 		revised No S5‑252047  
    S5‑252047 Rel-19 InputToDraftCR TS 28.105 add use case for Management of Local explanation in AIML inference HUAWEI, Orange, CMCC, Nokia, Verizon,NTT DOCOMO other Agreement Yes
Yes+NTT DOCOMO Ericsson objected
 		noted No   S5‑251551
    S5‑251552 Rel-19 InputToDraftCR TS 28.105 add solution for Management of Local explanation in AIML inference Huawei other Approval Yes
Yes
 		not treated No    
    S5‑251553 Rel-19 InputToDraftCR TS 28.105 update the ML model lifecycle management capabilities Huawei other Approval Yes
Yes
 		not treated No    
    S5‑251606 Input to draftCR Rel-19 TS 28.105 Use case on AIML prediction latency in inference Nokia, Nokia Shanghai Bell other Approval Yes
Yes
 		withdrawn Yes    
    S5‑251607 Input to draftCR Rel-19 TS 28.105 Use case on AIML prediction latency in training Nokia, Nokia Shanghai Bell other Approval Yes
Yes
 		noted No    
    S5‑252045 Input to draftCR Rel-19 TS 28.105 Use case on AIML prediction latency in training Nokia, Nokia Shanghai Bell other Approval No
Yes
 		withdrawn Yes    
    S5‑251608 Input to draftCR Rel-19 TS 28.105 Use case on ML explainability for inference Nokia, Nokia Shanghai Bell other Approval Yes
YesS5-252047
 		merged No S5‑252047  
    S5‑251609 Input to draftCR Rel-19 TS 28.105 Use case on ML explainability for training Nokia, Nokia Shanghai Bell other Approval Yes
Yesmerged into S5-252040
 		merged No S5‑252040  
    S5‑251610 Input to draftCR Rel-19 TS 28.105 Solution on model confidence requirement Nokia, Nokia Shanghai Bell other Approval Yes
Yes
 		withdrawn Yes    
    S5‑251611 Input to draftCR Rel-19 TS 28.105 Solution on sustainable AIML training Nokia, Nokia Shanghai Bell other Approval Yes
Yes
 		noted No    
    S5‑252043 Input to draftCR Rel-19 TS 28.105 Solution on sustainable AIML training Nokia, Nokia Shanghai Bell other Approval No
Yes
 		withdrawn Yes    
    S5‑251612 Input to draftCR Rel-19 TS 28.105 Use case on model confidence requirement Nokia, Nokia Shanghai Bell other Approval Yes
Yes
 		revised No S5‑252042  
    S5‑252042 Input to draftCR Rel-19 TS 28.105 Use case on model confidence requirement Nokia, Nokia Shanghai Bell other Approval Yes
YesEricsson objected
 		noted No   S5‑251612
    S5‑251613 Input to draftCR Rel-19 TS 28.105 Use case on sustainable AIML training Nokia, Nokia Shanghai Bell other Approval Yes
YesR5-252044
 		merged No R5‑252044  
    S5‑251614 Input to draftCR Rel-19 TS 28.105 Add RL NRMs Nokia, Nokia Shanghai Bell other Approval Yes
Yesmerged into S5-252040
 		merged No S5‑252040  
    S5‑251633 Rel-19 Input to draftCR TS 28.105 Add NRMs on distributed training CATT other Approval Yes
Yeswrong CR doc type!
 		revised No S5‑251789  
    S5‑251789 Rel-19 Input to draftCR TS 28.105 Add NRMs on distributed training CATT, ZTE, Samsung, Ericsson other Approval Yes
Yes
 		approved No   S5‑251633
    S5‑251713 Input to DraftCR Rel-19 TS 28.105 Fix wrong reference and add RRC report Ericsson GmbH, Eurolab other Agreement Yes
Yes
 		not treated No    
    S5‑251755 pCR DraftCR Rel-19 TS 28.105 Editorials corrections to the requirements of Managing ML models in use in a live network NEC Europe Ltd other Approval Yes
YesS5-252046
 		merged No S5‑252046  
    S5‑251756 Input to Draft CR Rel-19 CR TS 28.105 Pre-specialized training and Fine-tuning NEC, Intel other Approval Yes
Yes
 		revised No S5‑251782  
    S5‑251782 Input to Draft CR Rel-19 CR TS 28.105 Pre-specialized training and Fine-tuning NEC, Intel, China Mobile, ZTE other Approval Yes
Yesd3
 		noted No   S5‑251756
    S5‑251757 Input to draft CR TS 28.105 add NRM for ML pre-training and fine-tuning NEC, Intel other Approval Yes
YesETSI MCC: wrong CR type coversheet
 		revised No S5‑251783  
    S5‑251783 Input to draft CR TS 28.105 add NRM for ML pre-training and fine-tuning NEC, Intel, China Mobile, ZTE, Huawei other Approval Yes
Yes
 		noted No   S5‑251757
    S5‑251764 Rel-19 draftCR TS28.105 NEC draftCR discussion No
No
 		email approval No    
6.19.2 Study on Management Data Analytics (MDA) – Phase 3 (completed)                      
6.19.2.1 Management Data Analytics phase 3 S5‑251317 Add the use case and requirements for edge application deployment location analysis AsiaInfo, ZTE CR Agreement Yes
Yes
 		revised No S5‑251790  
    S5‑251790 Add the use case and requirements for edge application deployment location analysis AsiaInfo, ZTE CR Agreement Yes
Yesd2
 		agreed No   S5‑251317
    S5‑251318 Add the use case and requirements for edge computing performance analysis AsiaInfo, ZTE CR Agreement Yes
Yes
 		revised No S5‑251792  
    S5‑251792 Add the use case and requirements for edge computing performance analysis AsiaInfo, ZTE CR Agreement Yes
Yesd1
 		agreed No   S5‑251318
    S5‑251319 Add the use case and requirements for traffic congestion prediction analytics based on UE throughput AsiaInfo, ZTE CR Agreement Yes
Yes
 		revised No S5‑251798  
    S5‑251798 Add the use case and requirements for traffic congestion prediction analytics based on UE throughput AsiaInfo, ZTE, Orange CR Agreement Yes
Yesd1
 		agreed No   S5‑251319
    S5‑251320 Rel-19 CR TS 28.104 Add solution for edge application deployment location analysis AsiaInfo, ZTE CR Approval Yes
Yes
 		revised No S5‑251791  
    S5‑251791 Rel-19 CR TS 28.104 Add solution for edge application deployment location analysis AsiaInfo, ZTE CR Approval Yes
Yes
 		agreed No   S5‑251320
    S5‑251321 Rel-19 CR TS 28.104 add solutions for edge computing performance analysis AsiaInfo, ZTE CR Approval Yes
Yesproblem with the use of underscore was detected.
 		revised No S5‑251793  
    S5‑251793 Rel-19 CR TS 28.104 add solutions for edge computing performance analysis AsiaInfo, ZTE CR Approval Yes
Yesd1
 		agreed No   S5‑251321
    S5‑251440 Rel19 CR TS28.104 add solution on management data correlation analytics Nokia, Nokia Shanghai Bell CR Agreement Yes
Yes
 		revised No S5‑251795  
    S5‑251795 Rel19 CR TS28.104 add solution on management data correlation analytics Nokia, Nokia Shanghai Bell, Orange CR Agreement Yes
Yes
 		agreed No   S5‑251440
    S5‑251441 Rel19 CR TS28.104 add solution on correlation analytics for NF Scaling and dimensioning Nokia, Nokia Shanghai Bell CR Agreement Yes
YesSamsung: is doing more than the requirements are asking for.
 		revised No S5‑251796  
    S5‑251796 Rel19 CR TS28.104 add solution on correlation analytics for NF Scaling and dimensioning Nokia, Nokia Shanghai Bell, Orange CR Agreement Yes
Yesd3
 		agreed No   S5‑251441
    S5‑251442 Rel19 CR TS28.104 add solution on management data correlation analytics for threshold assessment and adjustment Nokia, Nokia Shanghai Bell CR Agreement Yes
YesSamsung: which use case is this?
 		revised No S5‑251797  
    S5‑251797 Rel19 CR TS28.104 add solution on management data correlation analytics for threshold assessment and adjustment Nokia, Nokia Shanghai Bell CR Agreement Yes
Yesd3
 		agreed No   S5‑251442
    S5‑251443 Rel19 CR TS28.104 add solution on management data collection recommendation for predicted failures Nokia, Nokia Shanghai Bell CR Agreement Yes
Yesshall->should Orange is supporting these requirements Huawei: managementDataCollectionIndication is not needed.
 		revised No S5‑251881  
    S5‑251881 Rel19 CR TS28.104 add solution on management data collection recommendation for predicted failures Nokia, Nokia Shanghai Bell, Orange CR Agreement Yes
Yesd2
 		agreed No   S5‑251443
    S5‑251462 Rel-19 CR TS 28.104 Add solutions for traffic congestion prediction analysis based on UE throughput AsiaInfo, ZTE CR Approval Yes
Yes
 		revised No S5‑251799  
    S5‑251799 Rel-19 CR TS 28.104 Add solutions for traffic congestion prediction analysis based on UE throughput AsiaInfo, ZTE CR Approval Yes
Yesd1
 		agreed No   S5‑251462
    S5‑251539 Rel-19 CR 28.104 software upgrade validation Samsung R&D Institute UK CR Agreement Yes
YesOrange is supporting Huawei: requirement should not recommend. clauses affected is missing
 		revised No S5‑251885  
    S5‑251885 Rel-19 CR 28.104 software upgrade validation Samsung R&D Institute UK, Orange CR Agreement Yes
Yesd2->d3?
 		revised No S5‑252116 S5‑251539
    S5‑252116 Rel-19 CR 28.104 software upgrade validation Samsung R&D Institute UK, Orange CR Agreement Yes
Yes
 		agreed No   S5‑251885
    S5‑251554 Rel-19 CR TS 28.104 update MDA type for UE throughput anlaysis Huawei CR Approval Yes
Yes
 		revised No S5‑251880  
    S5‑251880 Rel-19 CR TS 28.104 update MDA type for UE throughput anlaysis Huawei CR Approval Yes
Yesd1
 		agreed No   S5‑251554
    S5‑251555 Rel-19 CR TS 28.104 add stage3 solution for mobility performance analysis Huawei, Samsung CR Approval Yes
YesNokia will provide a discussion paper at the next meeting SA5#161.
 		not pursued No    
    S5‑251596 Rel-19 CR TS 28.104 Improvements to failure prediction Huawei CR Agreement Yes
Yesoverlap with Ericsson's S5-251715 and Nokia's S5-251349
 		agreed No    
    S5‑251618 Rel-19 CR 28.104 adding statics information in failure prediction output Huawei CR Agreement Yes
Yesoffline discussion needed
 		revised No S5‑251883  
    S5‑251883 Rel-19 CR 28.104 adding statics information in failure prediction output Huawei CR Agreement Yes
Yesd2
 		agreed No   S5‑251618
    S5‑251619 Rel-19 CR 28.104 clarification on resource management Huawei CR Agreement Yes
YesEricsson is objecting to the whole document more offline discussions keep open
 		not pursued No    
    S5‑251620 Rel-19 CR 28.104 topology information as enabling data is missing Huawei CR Agreement Yes
YesETSI MCC: cl. aff missing
 		revised No S5‑251884  
    S5‑251884 Rel-19 CR 28.104 topology information as enabling data is missing Huawei CR Agreement Yes
Yesd1
 		agreed No   S5‑251620
    S5‑251626 Rel 19 CR TS 28.104 Clarify definition of confidenceDegree attribute Ericsson CR Agreement Yes
YesETSI MCC: date!
 		revised No S5‑251886  
    S5‑251886 Rel 19 CR TS 28.104 Clarify definition of confidenceDegree attribute Ericsson CR Agreement Yes
Yes
 		agreed No   S5‑251626
    S5‑251715 Rel-19 CR TS 28.104 Fix wrong reference and add RRC report Ericsson GmbH, Eurolab CR Agreement Yes
Yes
 		revised No S5‑251882  
    S5‑251882 Rel-19 CR TS 28.104 Fix wrong reference and add RRC report Ericsson GmbH, Eurolab, Nokia, Nokia Shanghai Bell CR Agreement Yes
Yesd1
 		agreed No   S5‑251715
    S5‑251736 Rel-19 CR TS 28.104 Multi Domain Resource Optimization Nokia CR Approval Yes
YesHuawei: MARO not needed
 		revised No S5‑251794  
    S5‑251794 Rel-19 CR TS 28.104 Multi Domain Resource Optimization Nokia CR Approval Yes
YesHuawei objected
 		not pursued No   S5‑251736
6.19.3 Study on intent driven management services for mobile network phase 3 (completed)                      
6.19.3.1 Intent driven management services for mobile network phase 3 S5‑251241 Enhancing Enablers for Intent Fulfilment Nokia, Samsung pCR Approval Yes
Yeswrong coversheet! wrong TS, WIC, etc. discussion about CCL.
 		withdrawn Yes    
    S5‑251272 Rel-19 CR TS 28.312 Update the solution for Intent capability exposure Huawei, Deutsche Telekom, Nokia CR Agreement Yes
YesNokia co-signs
 		revised No S5‑251924  
    S5‑251924 Rel-19 CR TS 28.312 Update the solution for Intent capability exposure Huawei, Deutsche Telekom, Nokia CR Agreement Yes
Yesd1
 		agreed No   S5‑251272
    S5‑251273 Rel-19 CR TS 28.312 Update the solution for intent negotiation report Huawei CR Agreement Yes
Yesexpected outcome of the breakout session
 		revised No S5‑251916  
    S5‑251916 Rel-19 CR TS 28.312 Update the solution for intent negotiation report Huawei, China Mobile, ZTE CR Agreement Yes
Yesd2
 		agreed No   S5‑251273
    S5‑251274 Rel-19 CR TS 28.312 Enhance the use case and solution to support radio network support for UAV pre-flight preparation Huawei, Deutsche Telekom CR Agreement Yes
Yes
 		revised No S5‑251913 S5‑250833
    S5‑251913 Rel-19 CR TS 28.312 Enhance the use case and solution to support radio network support for UAV pre-flight preparation Huawei, Deutsche Telekom CR Agreement Yes
Yesd2
 		agreed No   S5‑251274
    S5‑251275 Rel-19 CR TS 28.312 Add procedure for intent exploration Huawei, Deutsche Telekom CR Agreement Yes
Yes
 		revised No S5‑251917  
    S5‑251917 Rel-19 CR TS 28.312 Add procedure for intent exploration Huawei, Deutsche Telekom, ZTE CR Agreement Yes
Yesd2
 		agreed No   S5‑251275
    S5‑251276 Rel-19 CR TS 28.312 Update procedures for intent report management to support implicit intent report subscription Huawei CR Agreement Yes
YesZTE, DT co-signed
 		revised No S5‑251922  
    S5‑251922 Rel-19 CR TS 28.312 Update procedures for intent report management to support implicit intent report subscription Huawei, ZTE, Deutsche Telekom CR Agreement Yes
Yes
 		agreed No   S5‑251276
    S5‑251277 Rel-19 CR TS 28.312 Update 5.3.1 Intent handling capability obtaining Huawei CR Agreement Yes
Yes
 		revised No S5‑251925  
    S5‑251925 Rel-19 CR TS 28.312 Update 5.3.1 Intent handling capability obtaining Huawei CR Agreement Yes
Yesd2
 		agreed No   S5‑251277
    S5‑251278 Rel-19 CR TS 28.312 Add missing abbreviation and definition Huawei, Deutsche Telekom CR Agreement Yes
Yes
 		revised No S5‑251926  
    S5‑251926 Rel-19 CR TS 28.312 Add missing abbreviation and definition Huawei, Deutsche Telekom CR Agreement Yes
Yes
 		agreed No   S5‑251278
    S5‑251279 Rel-19 CR TS 28.312 Enhance the definition for intentMgmtPurpose Huawei, Deutsche Telekom CR Agreement Yes
Yes
 		revised No S5‑251918  
    S5‑251918 Rel-19 CR TS 28.312 Enhance the definition for intentMgmtPurpose Huawei, Deutsche Telekom, ZTE CR Agreement Yes
Yesd2
 		agreed No   S5‑251279
    S5‑251280 Rel-19 CR TS 28.312 Enhance the solution for RadioServiceExpectation Huawei, Deutsche Telekom CR Agreement Yes
Yes
 		agreed No    
    S5‑251281 Rel-19 Address the implementation issue for CR 0277 and CR 0304 Huawei CR Agreement No
Yes
 		withdrawn Yes    
    S5‑251367 Rel-19 CR TS 28.312 Enhance the use case and solution to support MOCN undifferentiated radio service in a specified area China Unicom CR Agreement Yes
YesHuawei sent offline comments Nokia: added text is not necessary.
 		revised No S5‑251914  
    S5‑251914 Rel-19 CR TS 28.312 Enhance the use case and solution to support MOCN undifferentiated radio service in a specified area China Unicom CR Agreement Yes
Yesd1
 		agreed No   S5‑251367
    S5‑251392 Rel-19 CR TS 28.312 Update clause 6.1 and 7.1 to support intent negotiation Huawei, Deutsche Telekom CR Agreement Yes
Yes
 		revised No S5‑251919  
    S5‑251919 Rel-19 CR TS 28.312 Update clause 6.1 and 7.1 to support intent negotiation Huawei, Deutsche Telekom, ZTE CR Agreement Yes
Yesd1
 		agreed No   S5‑251392
    S5‑251408 Rel-19 CR TS 28.312 Add Stage-3 Solution for intent driven management of network maintenance NTT DOCOMO CR Agreement Yes
Yes
 		agreed No    
    S5‑251422 Rel-19 CR 28.312 Add generic utility function support (stage 2) Ericsson Inc. CR Approval Yes
Yes
 		withdrawn Yes    
    S5‑251445 Rel-19 CR TS 28.312 Add requirements and solutions for refusing to intent negotiation China Mobile Com. Corporation CR   Yes
Yes
 		withdrawn Yes    
    S5‑251446 Rel-19 CR TS 28.312 Add description of excavating of implicit intent China Mobile Com. Corporation CR   Yes
Yes
 		withdrawn Yes    
    S5‑251449 Rel-19 CR TS 28.312 Update on Intent Negotiation Use Case ZTE Corporation CR Agreement Yes
Yesmerge with S5-251603. Ericsson proposed a breakout session to cover this and negotiation related issues. 1273, 1450, 1495.
 		merged No S5‑251603  
    S5‑251450 Rel-19 CR TS 28.312 Update on Intent Negotiation NRM ZTE Corporation CR Agreement Yes
YesS5-251916
 		merged No S5‑251916  
    S5‑251458 Rel-19 CR TS 28.312 Add requirements and solutions for triggering intent negotiation China Mobile Com. Corporation CR Agreement Yes
Yesmerged into S5-251915
 		merged No S5‑251915  
    S5‑251460 Rel-19 CR TS 28.312 Add description of excavating of implicit intent China Mobile Com. Corporation CR Agreement Yes
Yes
 		revised No S5‑252054  
    S5‑252054 Rel-19 CR TS 28.312 Add description of excavating of implicit intent China Mobile Com. Corporation CR Agreement Yes
Yesd1
 		not pursued No   S5‑251460
    S5‑251494 Rel-19 CR TS 28.312 Modify the Generic Information model definition China Mobile, Huawei CR Agreement Yes
Yes
 		agreed No    
    S5‑251495 Rel-19 CR TS 28.312 Update solution for intent exploration China Mobile, Huawei CR Agreement Yes
Yesmerged into S5-251916
 		merged No S5‑251916  
    S5‑251532 Rel-19 CR TS 28.312 Add use case and requirement for intent related intents NTT DOCOMO CR Agreement Yes
Yes
 		not pursued No    
    S5‑251534 Rel-19 CR TS 28.312 Add an example to support intent report based on condition Huawei CR Agreement Yes
Yes
 		revised No S5‑251923  
    S5‑251923 Rel-19 CR TS 28.312 Add an example to support intent report based on condition Huawei CR Agreement Yes
Yesd1
 		agreed No   S5‑251534
    S5‑251559 Rel-19 CR TS 28.312 Correction on introduction in clause 5.1.9.1 NTT DOCOMO CR Agreement Yes
Yes
 		agreed No    
    S5‑251577 Rel-19 CR TS 28.312 Correction on introduction for intent fulfilment feasibility check NTT DOCOMO CR Agreement Yes
Yes
 		revised No S5‑251920  
    S5‑251920 Rel-19 CR TS 28.312 Correction on introduction for intent fulfilment feasibility check NTT DOCOMO CR Agreement Yes
Yesd1
 		agreed No   S5‑251577
    S5‑251603 Rel-19 CR 28.312 Clarifications on negotiation of intent fulfillment Ericsson Canada Inc. CR Agreement Yes
Yes
 		revised No S5‑251915  
    S5‑251915 Rel-19 CR 28.312 Clarifications on negotiation of intent fulfillment Ericsson Canada Inc., ZTE CR Agreement Yes
Yesd3
 		agreed No   S5‑251603
    S5‑251660 Rel-19 CR TS 28.312 Introduce mapping table Ericsson, Deutsche Telekom CR Agreement Yes
YesTable C.2
 		revised No S5‑251927  
    S5‑251927 Rel-19 CR TS 28.312 Introduce mapping table Ericsson, Deutsche Telekom CR Agreement Yes
Yesd1 ver 19.0.0?
 		revised No S5‑252117 S5‑251660
    S5‑252117 Rel-19 CR TS 28.312 Introduce mapping table Ericsson, Deutsche Telekom CR Agreement Yes
Yes
 		agreed No   S5‑251927
    S5‑251661 Rel-19 CR TS 28.312 Update UML diagram for intent Ericsson, ZTE CR Agreement Yes
Yesis not sent to plenary. Will be resubmitted to SA5#161.
 		endorsed No    
    S5‑251750 Rel-19 CR 28.312 Add generic utility function support (stage 2) Ericsson Canada Inc. CR Agreement Yes
Yes
 		revised No S5‑251921  
    S5‑251921 Rel-19 CR 28.312 Add generic utility function support (stage 2) Ericsson Canada Inc. CR Agreement Yes
Yesd9
 		agreed No   S5‑251750
6.19.4 Study on closed control loop management (completed) S5‑251334 TS28.536 CR update Assurace CCL model Nokia Americas CR Agreement Yes
Yes
 		not treated No    
6.19.4.1 Closed Control Loop Management S5‑251242 CCL Goal-targets and actions conflicts Nokia, Samsung pCR Approval Yes
YesNTT DOCOMO: offline comments
 		revised No S5‑251906  
    S5‑251906 CCL Goal-targets and actions conflicts Nokia, Samsung pCR Approval Yes
Yes
 		approved No   S5‑251242
    S5‑251243 CCL network & time scope conflicts Nokia pCR Approval Yes
Yes
 		revised No S5‑251908  
    S5‑251908 CCL network & time scope conflicts Nokia pCR Approval Yes
YesEricsson objected
 		noted No   S5‑251243
    S5‑251244 CCL Trigger conflicts Nokia, Samsung pCR Approval Yes
YesEricsson: resolution of trigger conflicts safe to ignore. Needs to be clarified. Huawei: needs overview to all these conflicts.
 		revised No S5‑251905  
    S5‑251905 CCL Trigger conflicts Nokia, Samsung pCR Approval Yes
Yes
 		approved No   S5‑251244
    S5‑251245 CCL Indirect target conflicts Nokia pCR Approval Yes
YesEricsson offline comments
 		revised No S5‑251907  
    S5‑251907 CCL Indirect target conflicts Nokia pCR Approval Yes
Yes
 		approved No   S5‑251245
    S5‑251246 CCL-impact assessment and resolution Nokia, Samsung pCR Approval Yes
Yes
 		revised No S5‑251910  
    S5‑251910 CCL-impact assessment and resolution Nokia, Samsung pCR Approval Yes
YesEricsson objected
 		noted No   S5‑251246
    S5‑251247 CCL decision escalation Nokia pCR Approval Yes
YesEricsson: examples of decision escalation?
 		revised No S5‑251911  
    S5‑251911 CCL decision escalation Nokia pCR Approval Yes
Yes
 		approved No   S5‑251247
    S5‑251248 Coordinating CCLs with other functions Nokia pCR Approval Yes
Yes
 		revised No S5‑252034  
    S5‑252034 Coordinating CCLs with other functions Nokia pCR Approval Yes
Yes
 		approved No   S5‑251248
    S5‑251249 CCL General NRM Nokia pCR Approval Yes
Yes
 		revised No S5‑252030  
    S5‑252030 CCL General NRM Nokia, Samsung pCR Approval Yes
Yesd2
 		approved No   S5‑251249
    S5‑251250 DP on CCL and ACCL modelling relationship Nokia discussion Endorsement Yes
Yes
 		revised No S5‑252029  
    S5‑252029 DP on CCL and ACCL modelling relationship Nokia, Samsung discussion Endorsement Yes
Yesd2
 		endorsed No   S5‑251250
    S5‑251251 CCL coordination NRM Nokia pCR Approval Yes
Yes
 		revised No S5‑252035  
    S5‑252035 CCL coordination NRM Nokia pCR Approval Yes
Yeskeep open Ericsson objected
 		noted No   S5‑251251
    S5‑251252 Informative Annex on conflict handling approach Nokia pCR Approval Yes
Yes
 		revised No S5‑251909  
    S5‑251909 Informative Annex on conflict handling approach Nokia pCR Approval Yes
Yes
 		approved No   S5‑251252
    S5‑251527 Rel-19 pCR 28.567 Triggered CCL UC and Requirements Samsung R&D Institute UK pCR Agreement Yes
YesNokia & DT would like to co-sign.
 		revised No S5‑251904  
    S5‑251904 Rel-19 pCR 28.567 Triggered CCL UC and Requirements Samsung R&D Institute UK, Nokia, Deutsche Telekom, China Unicom pCR Agreement Yes
Yes
 		approved No   S5‑251527
    S5‑251536 pCR TS 28.567 Add use case and requirements for network performance problem recovery Huawei, Deutsche Telekom pCR Approval Yes
YesNokia: diff between domain management functions & cross management domain functions. Nokia co-signed
 		revised No S5‑251912  
    S5‑251912 pCR TS 28.567 Add use case and requirements for network performance problem recovery Huawei, Deutsche Telekom, Nokia pCR Approval Yes
Yes
 		approved No   S5‑251536
    S5‑251662 Rel-19 CR TS 28.536 Clarify generic use of closed control loop Ericsson, Deutsche Telekom CR Approval Yes
Yes
 		not pursued No    
    S5‑252031 Rel-19 CR TS 28.536 Clarify generic use of closed control loop Ericsson, Deutsche Telekom CR Approval No
Yesnot available
 		withdrawn Yes    
    S5‑251663 pCR on TS 28.567 introduce imported information elements Ericsson, Deutsche Telekom pCR Approval Yes
Yes
 		not pursued No    
    S5‑252032 pCR on TS 28.567 introduce imported information elements Ericsson, Deutsche Telekom pCR Approval No
Yesnot available
 		withdrawn Yes    
    S5‑251749 Rel-19 pCR TS 28.567 Procedure and metrics for CCL performance monitoring Samsung Electronics GmbH pCR Approval Yes
Yes
 		revised No S5‑252033  
    S5‑252033 Rel-19 pCR TS 28.567 Procedure and metrics for CCL performance monitoring Samsung Electronics GmbH pCR Approval Yes
Yeschanges over changes
 		approved No   S5‑251749
    S5‑251760 Draft TS28.567 Nokia draft TS discussion No
No
 		email approval No    
6.19.5 Study on management aspects of Network Digital Twin (completed)                      
6.19.5.1 Management aspects of Network Digital Twins S5‑251253 NDT concept and scope Nokia, Ericsson pCR Approval Yes
YesETSI MCC: would be appropriate to use the same naming convention. Nokia: we're following the template(which removes data). Huawei: data is useful in the template. SA5 Chair: only modify 4.2.
 		revised No S5‑251896  
    S5‑251896 NDT concept and scope Nokia, Ericsson pCR Approval Yes
Yesobjected by Samsung
 		noted No   S5‑251253
    S5‑251254 NDT relation to automation Nokia, Ericsson pCR Approval Yes
YesOrange, Huawei support.
 		revised No S5‑251898  
    S5‑251898 NDT relation to automation Nokia, Ericsson pCR Approval Yes
Yesobjected by Samsung
 		noted No   S5‑251254
    S5‑251255 NDTs for verification Nokia, Ericsson pCR Approval Yes
YesHuawei: what is the difference between network config and automation config? NTT DOCOMO: 5.3.Y.1 duplication. Samsung & Deutsche Telekom agree with Huawei & NTT DOCOMO. DT: example in req.4 should be avoided.
 		revised No S5‑251901  
    S5‑251901 NDTs for verification Nokia, Ericsson, Huawei pCR Approval Yes
Yes
 		approved No   S5‑251255
    S5‑251256 NDT support to Automation Nokia, Ericsson pCR Approval Yes
YesOrange supports Overlaps with 1599 keep open ZTE: do not agree remove the policy related text Nokia: will split later the pCRs merged into S5-251898
 		merged No S5‑251898  
    S5‑251900 NDT support to Automation Nokia, Ericsson pCR Approval No
Yes
 		withdrawn Yes    
    S5‑251257 NDT NRM Nokia pCR Approval Yes
Yesmerged into S5-252020
 		merged No S5‑252020  
    S5‑251423 Discussion Paper Justification for the Inclusion of Nested NDT Definition in the TS 28.561 FiberCop, Deutsche Telekom, Telecom Italia discussion Endorsement Yes
Yes
 		revised No S5‑252018  
    S5‑252018 Discussion Paper Justification for the Inclusion of Nested NDT Definition in the TS 28.561 FiberCop, Deutsche Telekom, Telecom Italia discussion Endorsement Yes
Yes
 		noted No   S5‑251423
    S5‑251427 Pseudo-CR on TS 28.561 Nested NDT Definition FiberCop, Deutsche Telekom, Telecom Italia pCR Approval Yes
Yes
 		revised No S5‑251657  
    S5‑251447 Rel-19 pCR TS 28.561 Generic NDT NRM ZTE Corporation pCR Agreement Yes
YesS5-252020
 		merged No S5‑252020  
    S5‑251448 Rel-19 pCR TS 28.561 Add Requirements for Network failure and risk prediction ZTE Corporation pCR Agreement Yes
YesNokia: these reuirements have to be checked against the other requirements merged into S5-251899
 		merged No S5‑251899  
    S5‑251490 TS28.561 Add the NDT concept and scope China Mobile pCR Approval Yes
Yes
 		withdrawn Yes    
    S5‑251491 TS28.561 NDT support for network automation China Mobile, Huawei pCR Approval Yes
Yes
 		withdrawn Yes    
    S5‑251492 pCR Add UC and requirements of using NDT to generate customer experience data for TS 28.561 China Mobile, Huawei pCR Approval Yes
YesETSI MCC: table should hae a title SA5 Vice Chair: is against 32.160? Huawei: merge into S5-251569! DT: req. 1 and 2.
 		merged No S5‑251569  
    S5‑251493 pCR Add solution of Using NDT to generate ML training data for TS 28.561 China Mobile pCR Approval Yes
YesS5-252020
 		merged No S5‑252020  
    S5‑251538 Rel-19 pCR 28.561 adding requirement of network issue inducement capability NTT DOCOMO, SK Telecom pCR Approval Yes
YesHuawei: requirement 3 should be removed. merged into S5-251899 DT: remove the examples, make sure what the network issue is.
 		merged No S5‑251899  
    S5‑251540 Rel-19 pCR 28.561 NDT overview NTT DOCOMO, SK Telecom pCR Approval Yes
Yesmerged into S5-251897
 		merged No S5‑251897  
    S5‑251542 Rel-19 CR 28.561 NDT Inducement Requirements Samsung R&D Institute UK pCR Approval Yes
Yesmerged into S5-251899
 		merged No S5‑251899  
    S5‑251566 Pseudo-CR on TS 28.561 Use case of RAN energy saving policy verification Huawei pCR Approval Yes
Yesmerged into S5-251901
 		merged No S5‑251901  
    S5‑251902 Pseudo-CR on TS 28.561 Use case of RAN energy saving policy verification Huawei pCR Approval No
Yes
 		withdrawn Yes    
    S5‑251567 Pseudo-CR on TS 28.561 NDT NRMs Huawei pCR Approval Yes
Yes
 		revised No S5‑252020  
    S5‑252020 Pseudo-CR on TS 28.561 NDT NRMs Huawei pCR Approval Yes
Yesreceived more comments
 		revised No S5‑252118 S5‑251567
    S5‑252118 Pseudo-CR on TS 28.561 NDT NRMs Huawei, Nokia, CMCC, ZTE, Orange, Ericsson pCR Approval Yes
Yes
 		approved No   S5‑252020
    S5‑251568 Pseudo-CR on TS 28.561 Remove abbreviations in clause 5.1 Huawei pCR Approval Yes
Yes
 		noted No    
    S5‑251569 Pseudo-CR on TS 28.561 Add requirements for NDT supporting data generation Huawei pCR Approval Yes
YesSamsung: req. 1 is not needed Nokia co-signs
 		revised No S5‑251903  
    S5‑251903 Pseudo-CR on TS 28.561 Add requirements for NDT supporting data generation Huawei, Nokia, Ericsson, China Mobile pCR Approval Yes
Yeskeep open
 		approved No   S5‑251569
    S5‑251570 Pseudo-CR on TS 28.561 Procedure for consuming NDT capability Huawei pCR Approval Yes
Yes
 		revised No S5‑252021  
    S5‑252021 Pseudo-CR on TS 28.561 Procedure for consuming NDT capability Huawei pCR Approval Yes
YesETSI MCC: fix formats
 		revised No S5‑252119 S5‑251570
    S5‑252119 Pseudo-CR on TS 28.561 Procedure for consuming NDT capability Huawei pCR Approval Yes
Yes
 		approved No   S5‑252021
    S5‑251599 Rel-19 pCR TS 28.561 General improvements to use cases and requirements Huawei Tech. Japan, K.K. pCR Approval Yes
Yes
 		revised No S5‑252019  
    S5‑252019 Rel-19 pCR TS 28.561 General improvements to use cases and requirements Huawei Tech. Japan, K.K., Ericsson pCR Approval Yes
Yes
 		approved No   S5‑251599
    S5‑251601 TS28.561 Add the NDT concept and scope China Mobile, FiberCop pCR Approval Yes
YesOrange supports. Samsung sent offline comments. SA5 Chair: This doc will be a basis. NTT DOCOMO: suggest to merge with next contribution. Samsung needed more time.
 		revised No S5‑251897  
    S5‑251897 TS28.561 Add the NDT concept and scope China Mobile, FiberCop, Orange, Nokia, Huawei, NTT DOCOMO, SK Telecom, Ericsson pCR Approval Yes
Yes
 		approved No   S5‑251601
    S5‑251602 TS28.561 NDT support for network automation China Mobile, Huawei, FiberCop pCR Approval Yes
YesCMCC: this can be baseline Nokia: some requirements are overlapping Ericsson: same
 		revised No S5‑251899  
    S5‑251899 TS28.561 NDT support for network automation China Mobile, Huawei, FiberCop, Nokia, Ericsson, ZTE, Huawei, NTT DOCOMO, SK Telecom, Samsung pCR Approval Yes
Yes
 		approved No   S5‑251602
    S5‑251648 Pseudo-CR on TS 28.561 Update use case for NDT support analysis of failure events including signaling storm Huawei pCR Approval Yes
YesETSI MCC: pls. format according to the 3GPP styles merged into S5-251899
 		merged No S5‑251899  
    S5‑251657 Pseudo-CR on TS 28.561 Nested NDT Definition FiberCop, Deutsche Telekom, Telecom Italia, Orange pCR Approval Yes
Yes
 		revised No S5‑252017 S5‑251427
    S5‑252017 Pseudo-CR on TS 28.561 Nested NDT Definition FiberCop, Deutsche Telekom, Telecom Italia, Orange, NTT Docomo , Nokia , China Mobile, Ericsson pCR Approval Yes
Yes
 		revised No S5‑252120 S5‑251657
    S5‑252120 Pseudo-CR on TS 28.561 Nested NDT Definition FiberCop, Deutsche Telekom, Telecom Italia, Orange, NTT Docomo , Nokia , China Mobile, Ericsson pCR Approval Yes
Yes
 		approved No   S5‑252017
    S5‑251759 Draft TS28.561 China Mobile draft TS discussion No
No
 		email approval No    
6.19.6 Study on Cloud Aspects of Management and Orchestration S5‑251262 pCR TR 28.869 Annex example for CRD based deployment Rakuten Mobile, Inc pCR Approval Yes
YesOrange supports
 		revised No S5‑251893  
    S5‑251893 pCR TR 28.869 Annex example for CRD based deployment Rakuten Mobile, Inc, Orange pCR Approval Yes
Yes
 		approved No   S5‑251262
    S5‑251263 pCR TR 28.869 LCM changes for declarative descriptor Rakuten Mobile, Inc pCR Approval Yes
YesHuawei, Ericsson, Nokia, Orange supported. ETSI MCC: pls. format according to 3GPP styles. CNF resource requirements are out of scope.
 		revised No S5‑251887  
    S5‑251887 pCR TR 28.869 LCM changes for declarative descriptor Rakuten Mobile, Inc, Orange pCR Approval Yes
Yes
 		noted No   S5‑251263
    S5‑251537 pCR TR 28.869 Add potential solution for VNF configuration management Huawei, Deutsche Telekom, Ericsson, Nokia pCR Approval Yes
Yes
 		revised No S5‑251889  
    S5‑251889 pCR TR 28.869 Add potential solution for VNF configuration management Huawei, Deutsche Telekom, Ericsson, Nokia, Samsung pCR Approval Yes
YesNTT DOCOMO objected
 		noted No   S5‑251537
    S5‑251560 R19 pCR TR 28.869 enhance observability requirements (Use case 7) Orange, AT&T pCR Approval Yes
YesEricsson: do not see the relation 8/9/10
 		revised No S5‑251891  
    S5‑251891 R19 pCR TR 28.869 enhance observability requirements (Use case 7) Orange, AT&T pCR Approval Yes
Yes
 		approved No   S5‑251560
    S5‑251571 Pseudo-CR on TR 28.869 Add an example in Annex B Huawei pCR Approval Yes
Yes
 		revised No S5‑252010  
    S5‑252010 Pseudo-CR on TR 28.869 Add an example in Annex B Huawei, Rakuten Mobile, Inc. pCR Approval Yes
Yes
 		approved No   S5‑251571
    S5‑251572 Pseudo-CR on TR 28.869 Add conclusion for management data streaming solution based on message bus Huawei pCR Approval Yes
Yes
 		revised No S5‑252013  
    S5‑252013 Pseudo-CR on TR 28.869 Add conclusion for management data streaming solution based on message bus Huawei pCR Approval Yes
Yes-Rakuten
 		revised No S5‑252121 S5‑251572
    S5‑252121 Pseudo-CR on TR 28.869 Add conclusion for management data streaming solution based on message bus Huawei pCR Approval Yes
Yes
 		noted No   S5‑252013
    S5‑251578 pCR Add evaluation for solutions in clause 5.2.1.3 China Mobile,NTT DOCOMO pCR Approval Yes
YesETSI MCC: pls. respect title convention, delete non-modified clauses, renumber new table with real number
 		revised No S5‑251892  
    S5‑251892 pCR Add evaluation for solutions in clause 5.2.1.3 China Mobile,NTT DOCOMO pCR Approval Yes
Yes
 		approved No   S5‑251578
    S5‑251579 pCR Add solution and evaluation statement for usecase Placement of cloud native NFs China Mobile pCR Approval Yes
Yes
 		approved No    
    S5‑251583 pCR TR 28.869 Cloud-native VNF policy management evaluation NTT DOCOMO pCR Approval Yes
YesNokia: no need to have separate VNF solution NTT DOCOMO: is executed outside MNC producer.
 		revised No S5‑251890  
    S5‑251890 pCR TR 28.869 Cloud-native VNF policy management evaluation NTT DOCOMO pCR Approval Yes
YesNokia objects
 		noted No   S5‑251583
    S5‑251584 pCR TR 28.869 3GPP management architecture evolution based on PaaS NTT DOCOMO, China Mobile pCR Approval Yes
YesETSI MCC: pls. show rather the context with clauses nearby.
 		revised No S5‑251895  
    S5‑251895 pCR TR 28.869 3GPP management architecture evolution based on PaaS NTT DOCOMO, China Mobile pCR Approval Yes
Yesgot more comments Nokia objected
 		noted No   S5‑251584
    S5‑251594 pCR Add evaluation for some LCM solutions and update the clause 5.2.6 China Mobile pCR Approval Yes
Yes
 		revised No S5‑252011  
    S5‑252011 pCR Add evaluation for some LCM solutions and update the clause 5.2.6 China Mobile pCR Approval Yes
Yes
 		noted No   S5‑251594
    S5‑251600 pCR Add general conclusion and some recommendations China Mobile pCR Approval Yes
Yes
 		revised No S5‑252014  
    S5‑252014 pCR Add general conclusion and some recommendations China Mobile pCR Approval Yes
Yes
 		approved No   S5‑251600
    S5‑251639 pCR Add terminology China Mobile pCR Approval Yes
Yes
 		revised No S5‑252015  
    S5‑252015 pCR Add terminology China Mobile pCR Approval Yes
YesEricsson objected
 		noted No   S5‑251639
    S5‑251718 pCR TR 28.869 Adopt NF Deployment terminology in scaling use case Ericsson Telecomunicazioni SpA pCR Approval Yes
Yes
 		revised No S5‑252012  
    S5‑252012 pCR TR 28.869 Adopt NF Deployment terminology in scaling use case Ericsson Telecomunicazioni SpA pCR Approval Yes
Yes
 		approved No   S5‑251718
    S5‑251719 pCR TR 28.869 Detail procedure flow for creation of NF Deployment Ericsson Telecomunicazioni SpA pCR Approval Yes
Yes2 potential alternative solutions are not solid. fu
 		revised No S5‑251888  
    S5‑251888 pCR TR 28.869 Detail procedure flow for creation of NF Deployment Ericsson Telecomunicazioni SpA pCR Approval Yes
YesNTT DOCOMO objected
 		noted No   S5‑251719
    S5‑251722 pCR TR 28.869 Specification structure for LCM of NF Deployment Ericsson Telecomunicazioni SpA pCR Approval Yes
Yes
 		revised No S5‑252016  
    S5‑252016 pCR TR 28.869 Specification structure for LCM of NF Deployment Ericsson Telecomunicazioni SpA pCR Approval Yes
YesChina Mobile objected
 		noted No   S5‑251722
    S5‑251725 pCR TR 28.869 Update Annex D for example scenario for creation of NF Deployment instance Ericsson Telecomunicazioni SpA pCR Approval Yes
Yes
 		revised No S5‑251894  
    S5‑251894 pCR TR 28.869 Update Annex D for example scenario for creation of NF Deployment instance Ericsson Telecomunicazioni SpA pCR Approval Yes
YesChina Mobile objected
 		noted No   S5‑251725
    S5‑251744 DP cloud native NF data streaming - connection based vs pub-sub based Rakuten Mobile, Inc discussion Endorsement Yes
Yes
 		revised No S5‑252009  
    S5‑252009 DP cloud native NF data streaming - connection based vs pub-sub based Rakuten Mobile, Inc, AT&T, Orange, NTT DOCOMO, China Mobile, China Unicom, FiberCop discussion Endorsement Yes
Yes+AT&T, Orange, NTT DOCOMO, China Mobile, China Unicom, FiberCop Nokia objected.
 		noted No   S5‑251744
    S5‑251746 Pseudo-CR on enhance annex examples for data streaming for cloud native network function Rakuten Mobile, Inc pCR Approval Yes
Yesmerged into S5-252010?
 		merged No S5‑252010  
    S5‑251747 Pseudo-CR on Add evaluation and conclusion for management data streaming based on message bus Rakuten Mobile, Inc pCR Approval Yes
Yes
 		noted No    
    S5‑251763 Draft TR28.869 China Mobile draft TR discussion No
No
 		email approval No    
6.19.7 Study on Enablers for Security Monitoring (completed)                      
6.19.8 Study on Service Based Management Architecture enhancement phase 3 (completed)                      
6.19.8.1 Service Based Management Architecture enhancement phase 3 S5‑251333 Rel-19 CR 28.532 Add new notifications for reliability Ericsson India Private Limited CR Approval No
Yes
 		withdrawn Yes    
    S5‑251393 Rel-19 CR TS 28537 Add requirements for discovering management capabilities of MnS instances based on area of interest Huawei, Deutsche Telekom CR Agreement Yes
YesEricsson: suggests rewording of requirements
 		revised No S5‑251928 S5‑250881
    S5‑251928 Rel-19 CR TS 28537 Add requirements for discovering management capabilities of MnS instances based on area of interest Huawei, Deutsche Telekom CR Agreement Yes
Yesd2 Nokia has more comments
 		agreed No   S5‑251393
    S5‑251394 Rel-19 CR TS 28.622 Extend the MnsScope to support area of interest (Stage2) Huawei, Deutsche Telekom CR Agreement Yes
Yes
 		revised No S5‑251929 S5‑250882
    S5‑251929 Rel-19 CR TS 28.622 Extend the MnsScope to support area of interest (Stage2) Huawei, Deutsche Telekom CR Agreement Yes
Yesd2
 		agreed No   S5‑251394
    S5‑251395 Rel-19 CR TS 28.623 Extend the MnsScope to support area of interest (Stage3) Huawei, Deutsche Telekom CR Agreement Yes
Yes
 		revised No S5‑251930 S5‑250883
    S5‑251930 Rel-19 CR TS 28.623 Extend the MnsScope to support area of interest (Stage3) Huawei, Deutsche Telekom CR Agreement Yes
Yesd2
 		agreed No   S5‑251395
    S5‑251396 Rel-19 CR TS 28.622 Enhance the MnSInfo to support discovery of management capabilities of MnS supported by a MnS Producer (Stage2) Huawei, Deutsche Telekom CR Agreement Yes
Yes
 		revised No S5‑251931  
    S5‑251931 Rel-19 CR TS 28.622 Enhance the MnSInfo to support discovery of management capabilities of MnS supported by a MnS Producer (Stage2) Huawei, Deutsche Telekom, Nokia CR Agreement Yes
Yesd3
 		agreed No   S5‑251396
    S5‑251397 Rel-19 CR TS 28.623 Enhance the MnSInfo to support discovery of management capabilities of MnS supported by a MnS Producer (Stage3) Huawei, Deutsche Telekom CR Agreement Yes
Yes
 		revised No S5‑251932  
    S5‑251932 Rel-19 CR TS 28.623 Enhance the MnSInfo to support discovery of management capabilities of MnS supported by a MnS Producer (Stage3) Huawei, Deutsche Telekom, Nokia CR Agreement Yes
Yesd4
 		agreed No   S5‑251397
    S5‑251486 Rel-19 CR TS 28.111 Update terms and concepts overview Huawei CR Agreement Yes
YesNokia & Ericsson: change is not needed.
 		revised No S5‑251933  
    S5‑251933 Rel-19 CR TS 28.111 Update terms and concepts overview Huawei CR Agreement Yes
Yesd2 Nokia objected
 		not pursued No   S5‑251486
    S5‑251487 Rel-19 CR TS 28.111 Update references and abbreviations Huawei CR Agreement Yes
Yes
 		agreed No    
    S5‑251488 Rel-19 CR TS 28.111 Update scope Huawei CR Agreement Yes
Yes
 		agreed No    
    S5‑251581 Rel-19 CR 32.158 Add details for MnS API versioning Ericsson Canada Inc. CR Approval Yes
YesNokia: not every yaml file needs a server. There are 5 files with different versions. Opt. 1: comp. A+version Opt. 2: comp. A+B
 		not pursued No    
    S5‑251934 Rel-19 CR 32.158 Add details for MnS API versioning Ericsson Canada Inc. CR Approval No
Yesnext meeting
 		withdrawn Yes    
    S5‑251582 Rel-19 CR 28.537 Add details for MnS API versioning Ericsson Canada Inc. CR Approval Yes
Yes
 		not pursued No    
    S5‑251935 Rel-19 CR 28.537 Add details for MnS API versioning Ericsson Canada Inc. CR Approval No
Yes
 		withdrawn Yes    
    S5‑251936 Rel-19 CR 28.537 Add details for MnS API versioning Ericsson Canada Inc. CR Agreement No
Yesnew Tdoc during the meeting
 		withdrawn Yes    
    S5‑251675 Discussion paper on adding information in entry point specifications Ericsson, Huawei, Deutsche Telekom discussion Information Yes
Yes
 		noted No    
    S5‑251676 Rel-19 CR TS 28.310 Add entry point information Ericsson, Huawei, Deutsche Telekom CR Agreement Yes
YesNokia: not sure why this is needed. The title explains already. SA5 Chair: needs more offline discussion. Nokia objected.
 		not pursued No    
    S5‑251677 Rel-19 CR TS 28.313 Add entry point information Ericsson, Huawei, Deutsche Telekom CR Agreement Yes
Yes
 		not pursued No    
    S5‑251678 Rel-19 CR TS 28.314 Add entry point information Ericsson, Huawei, Deutsche Telekom CR Agreement Yes
Yes
 		not pursued No    
    S5‑251679 Rel-19 CR TS 28.404 Add entry point information Ericsson, Huawei, Deutsche Telekom CR Agreement Yes
Yes
 		not pursued No    
    S5‑251680 Rel-19 CR TS 28.531 Add entry point information Ericsson, Huawei, Deutsche Telekom CR Agreement Yes
Yes
 		not pursued No    
    S5‑251681 Rel-19 CR TS 28.532 Add entry point information Ericsson, Huawei, Deutsche Telekom CR Agreement Yes
Yes
 		not pursued No    
    S5‑251682 Rel-19 CR TS 28.535 Add entry point information Ericsson, Huawei, Deutsche Telekom CR Agreement Yes
Yes
 		not pursued No    
    S5‑251683 Rel-19 CR TS 28.537 Add entry point information Ericsson, Huawei, Deutsche Telekom CR Agreement Yes
Yes
 		not pursued No    
    S5‑251684 Rel-19 CR TS 28.540 Add entry point information Ericsson, Huawei, Deutsche Telekom CR Agreement Yes
Yes
 		not pursued No    
    S5‑251685 Rel-19 CR TS 28.555 Add entry point information Ericsson, Huawei, Deutsche Telekom CR Agreement Yes
Yes
 		not pursued No    
    S5‑251686 Rel-19 CR TS 28.622 Add entry point information Ericsson, Huawei, Deutsche Telekom CR Agreement Yes
Yes
 		not pursued No    
    S5‑251687 Rel-19 CR TS 28.130 Add entry point information Ericsson, Huawei, Deutsche Telekom CR Agreement Yes
Yes
 		not pursued No    
    S5‑251688 Rel-19 CR TS 32.421 Add entry point information Ericsson, Huawei, Deutsche Telekom CR Agreement Yes
Yes
 		not pursued No    
    S5‑251724 Rel-19 CR TS 28.533 Update Annex E Ericsson GmbH, Eurolab CR Agreement Yes
Yesco-sign Deutsche Telekom
 		revised No S5‑251937  
    S5‑251937 Rel-19 CR TS 28.533 Update Annex E Ericsson GmbH, Eurolab, Deutsche Telekom, Huawei, Orange CR Agreement Yes
Yesd1
 		agreed No   S5‑251724
    S5‑251733 Rel-19 CR 28.532 Add new notifications for reliability Ericsson India Private Limited CR Agreement Yes
Yes
 		revised No S5‑251939  
    S5‑251939 Rel-19 CR 28.532 Add new notifications for reliability Ericsson India Private Limited CR Agreement Yes
Yesd1 Nokia objected, wants to sort it out until the next meeting
 		not pursued No   S5‑251733
    S5‑251743 Rel-19 CR 28.532 Update notifications with common header Ericsson India Private Limited CR Agreement Yes
Yes
 		agreed No    
    S5‑251752 Rel-19 CR 28.622 Reliable notification transfer Ericsson Hungary Ltd CR Agreement Yes
Yes
 		revised No S5‑251940 S5‑250888
    S5‑251940 Rel-19 CR 28.622 Reliable notification transfer Ericsson Hungary Ltd CR Agreement Yes
Yeslike S5-251939
 		not pursued No   S5‑251752
6.19.9 Study on Management of planned configurations (completed)                      
6.19.9.1 Management of planned configurations S5‑251635 Rel-19 pCR TS 28.572 Improve clauses on Planned configuration concepts Nokia pCR Approval Yes
YesEricsson offline comments.
 		revised No S5‑251950  
    S5‑251950 Rel-19 pCR TS 28.572 Improve clauses on Planned configuration concepts Nokia pCR Approval Yes
Yesd1
 		approved No   S5‑251635
    S5‑251636 Rel-19 pCR TS 28.572 Improve clauses on Managing planned configurations Nokia pCR Approval Yes
Yes
 		revised No S5‑251951  
    S5‑251951 Rel-19 pCR TS 28.572 Improve clauses on Managing planned configurations Nokia pCR Approval Yes
Yes
 		approved No   S5‑251636
    S5‑251637 Rel-19 pCR TS 28.572 Improve clause Information model Nokia pCR Approval Yes
Yes
 		revised No S5‑251952  
    S5‑251952 Rel-19 pCR TS 28.572 Improve clause Information model Nokia pCR Approval Yes
Yesd1
 		approved No   S5‑251637
    S5‑251638 Rel-19 pCR TS 28.572 Improve clause RESTful HTTP-based solution set Nokia pCR Approval Yes
Yes
 		revised No S5‑251953  
    S5‑251953 Rel-19 pCR TS 28.572 Improve clause RESTful HTTP-based solution set Nokia pCR Approval Yes
Yesd1
 		approved No   S5‑251638
    S5‑251694 Rel-19 pCR TS 28.572 Allow recursive Planned configuration groups Ericsson India Private Limited pCR Approval Yes
Yes
 		revised No S5‑251954  
    S5‑251954 Rel-19 pCR TS 28.572 Allow recursive Planned configuration groups Ericsson India Private Limited pCR Approval Yes
Yesd1
 		approved No   S5‑251694
    S5‑251751 Rel-19 pCR TS 28.572 Plan Configuration Examples Ericsson India Private Limited pCR Approval Yes
Yes
 		withdrawn Yes    
    S5‑251753 Rel-19 pCR TS 28.572 Plan Activation Results Ericsson India Private Limited pCR Approval Yes
Yes
 		withdrawn Yes    
    S5‑251754 Discussion paper on: Long Running Configuration Reads Ericsson India Private Limited discussion Endorsement Yes
Yes
 		withdrawn Yes    
    S5‑251761 Draft TS28.572 Nokia draft TS discussion No
No
 		email approval No    
6.19.10 Data management phase 2 S5‑251499 Input to Draft CR 28.622 External Management Data Nokia other Agreement Yes
Yesis 19.1.0! SA5 Chair: pls. use 19.3.0 as baseline. Latest draftCR R5-247045. DT co-signs
 		revised No S5‑251955  
    S5‑251955 Input to Draft CR 28.622 External Management Data Nokia, Deutsche Telekom, Ericsson, Huawei other Agreement Yes
Yesd3
 		approved No   S5‑251499
    S5‑251956 Draft CR MADCOL TS 28.622 Nokia draftCR Approval Yes
Yesd1 ETSI MCC: c. aff., bullets & B1!
 		revised No S5‑252125  
    S5‑251957 Draft CR MADCOL TS 28.622 Nokia draftCR Approval No
Yesfor email approval use S5-251765
 		withdrawn Yes    
    S5‑252125 Draft CR MADCOL TS 28.622 Nokia draftCR Approval No
Yes
 		approved No   S5‑251956
    S5‑251765 Rel-19 draftCR TS28.622 Nokia draftCR discussion No
Yesfor email approval
 		for email approval No    
6.19.11 Study on data management regarding subscriptions and reporting (completed)                      
6.19.11.1 Data management regarding subscriptions and reporting S5‑251231 Rel-19 CR TS 28.405 QoE Reference Uniqueness Ericsson CR Agreement Yes
Yes
 		revised No S5‑251958  
    S5‑251958 Rel-19 CR TS 28.405 QoE Reference Uniqueness Ericsson, CATT CR Agreement Yes
Yesd1 Nokia objected. Nokia will provide concrete solution at the next meeting. A decision will be made then.
 		not pursued No   S5‑251231
    S5‑251232 Rel-19 CR TS 32.422 Trace Reference Uniqueness Ericsson, CATT CR Agreement Yes
Yesoffline comments from CATT
 		revised No S5‑251959  
    S5‑251959 Rel-19 CR TS 32.422 Trace Reference Uniqueness Ericsson, CATT CR Agreement Yes
Yessame like S5-251958
 		not pursued No   S5‑251232
    S5‑251401 Rel-19 CR TS 32.422 Introduction of new Trace Depth “Micro” for Optimised Tracing Jio Platforms Ltd (JPL) CR Decision Yes
Yes
 		withdrawn Yes    
    S5‑251501 Rel-19 CR TS 32.421 Enhancement to Trace Reference Nokia CR Approval Yes
YesEricsson objected keep open
 		not pursued No    
    S5‑251502 Rel-19 CR TS 32.422 Enhancement to Trace Reference Nokia CR Approval Yes
YesEricsson objected keep open
 		not pursued No    
    S5‑251503 Rel-19 CR TS 32.423 Enhancement to Trace Reference Nokia CR Approval Yes
YesEricsson objected keep open
 		not pursued No    
    S5‑251504 Rel-19 CR TS 28.622 Enhancement to Trace Reference Nokia CR Approval Yes
YesEricsson objected keep open
 		not pursued No    
    S5‑251505 Rel-19 CR TS 28.623 Enhancement to Trace Reference Nokia CR Approval Yes
YesEricsson objected keep open
 		not pursued No    
    S5‑251524 Rel-19 CR TS 32.422 Introduction of new Trace Depth “Micro” for Optimised Tracing Jio Platforms Ltd (JPL) CR Approval Yes
Yesno delegate present
 		not pursued No    
6.19.12 5G performance measurements and KPIs phase 4 S5‑251224 Rel-19 CR TS 28.532 PM File extension Ericsson LM CR Agreement Yes
Yes
 		withdrawn Yes    
    S5‑251225 Rel-19 CR 28.558 misaligned 5GC UE level measurement procedure Ericsson CR Agreement Yes
Yes
 		revised No S5‑251960  
    S5‑251960 Rel-19 CR 28.558 misaligned 5GC UE level measurement procedure Ericsson CR Agreement Yes
Yes
 		agreed No   S5‑251225
    S5‑251227 Rel-19 CR TS 28.552 Cell Unavailable Time performance measurement Ericsson, AT&T, Samsung CR Agreement Yes
Yes
 		revised No S5‑251961  
    S5‑251961 Rel-19 CR TS 28.552 Cell Unavailable Time performance measurement Ericsson, AT&T, Samsung CR Agreement Yes
Yes
 		agreed No   S5‑251227
    S5‑251228 Rel-19 CR TS 32.401 PM Counter Metadata Ericsson CR Agreement Yes
Yes
 		revised No S5‑251962  
    S5‑251962 Rel-19 CR TS 32.401 PM Counter Metadata Ericsson CR Agreement Yes
YesSamsung objected
 		not pursued No   S5‑251228
    S5‑251229 Rel-19 CR TS 32.404 PM Counter Metadata Ericsson CR Agreement Yes
Yes
 		revised No S5‑251963  
    S5‑251963 Rel-19 CR TS 32.404 PM Counter Metadata Ericsson CR Agreement Yes
YesSamsung objected
 		not pursued No   S5‑251229
    S5‑251653 Rel-19 CR TS 28.552 Correction of Distribution of time interval Esurfing IoT CR Agreement Yes
Yes
 		revised No S5‑251964  
    S5‑251964 Rel-19 CR TS 28.552 Correction of Distribution of time interval Esurfing IoT CR Agreement Yes
Yes
 		agreed No   S5‑251653
    S5‑251654 Rel-19 CR TS 28.552 Add Multicast Group Paging records for MBS measurement Esurfing IoT CR Agreement Yes
Yes
 		revised No S5‑251965  
    S5‑251965 Rel-19 CR TS 28.552 Add Multicast Group Paging records for MBS measurement Esurfing IoT CR Agreement Yes
Yes
 		agreed No   S5‑251654
    S5‑251658 Rel-19 CR TS 28.552 add measurement of coverage satisfaction ratio CMCC, Huawei, ZTE, CATT CR Approval Yes
Yes
 		withdrawn Yes    
    S5‑251709 Rel-19 CR TS 28.554 add measurement of coverage satisfaction ratio CMCC, Huawei, ZTE, CATT CR Agreement No
Yes
 		withdrawn Yes    
    S5‑251710 Rel-19 CR TS 28.552 add measurement of coverage satisfaction ratio CMCC, Huawei, ZTE, CATT CR Agreement No
Yes
 		withdrawn Yes    
    S5‑251712 Rel-19 CR TS 28.552 add measurement of coverage ratio CMCC, Huawei, ZTE, CATT CR Agreement Yes
Yesno cl. aff.
 		not pursued No    
    S5‑251966 Rel-19 CR TS 28.552 add measurement of coverage ratio CMCC, Huawei, ZTE, CATT CR Agreement No
Yes
 		withdrawn Yes    
    S5‑251714 Rel-19 CR TS 28.554 add measurement of coverage ratio CMCC, Huawei, ZTE, CATT CR Approval Yes
Yes
 		not pursued No    
    S5‑251735 Rel-19 CR TS 28.532 PM File extension Ericsson LM CR Agreement Yes
Yes
 		revised No S5‑252023  
    S5‑252023 Rel-19 CR TS 28.532 PM File extension Ericsson LM CR Agreement Yes
Yes
 		agreed No   S5‑251735
6.19.13 5G Advanced NRM features phase 3 S5‑251292 Rel19 CR TS28.541 NRM enhancements to ManagedNFProfile Nokia, Nokia Shanghai Bell, ZTE Corporation, Orange CR Agreement Yes
Yes
 		revised No S5‑251967  
    S5‑251967 Rel19 CR TS28.541 NRM enhancements to ManagedNFProfile Nokia, Nokia Shanghai Bell, ZTE Corporation, Orange CR Agreement Yes
Yes
 		agreed No   S5‑251292
    S5‑251293 Rel19 CR TS28.541 change the dataType concerning HostAddr Nokia, Nokia Shanghai Bell CR Agreement Yes
YesEricsson offline comments Rel-19 on cover!
 		revised No S5‑251978  
    S5‑251978 Rel19 CR TS28.541 change the dataType concerning HostAddr Nokia, Nokia Shanghai Bell CR Agreement Yes
Yes
 		agreed No   S5‑251293
    S5‑251294 Rel19 CR TS28.538 change the dataType concerning HostAddr Nokia, Nokia Shanghai Bell CR Agreement Yes
YesNokia offline comments Rel-19 on cover!
 		revised No S5‑251979  
    S5‑251979 Rel19 CR TS28.538 change the dataType concerning HostAddr Nokia, Nokia Shanghai Bell CR Agreement Yes
Yes
 		agreed No   S5‑251294
    S5‑251398 Rel-19 CR TS 28.541 update the naming convention in TS28541_NrNrm.yaml to align with stage 2 definition Huawei CR Agreement Yes
Yes
 		revised No S5‑251972  
    S5‑251972 Rel-19 CR TS 28.541 update the naming convention in TS28541_NrNrm.yaml to align with stage 2 definition Huawei, Nokia CR Agreement Yes
Yes
 		agreed No   S5‑251398
    S5‑251399 Rel-19 CR TS 28.622 Address the misalignment issues for vnfParametersList and peeParametersList (stage2) Huawei CR Agreement Yes
YesEricsson and Nokia offline comments. Nokia: Cat. C?
 		revised No S5‑251976  
    S5‑251976 Rel-19 CR TS 28.622 Address the misalignment issues for vnfParametersList and peeParametersList (stage2) Huawei CR Agreement Yes
Yes
 		agreed No   S5‑251399
    S5‑251400 Rel-19 CR TS 28.623 Address the misalignment issues for vnfParametersList and peeParametersList (stage3) Huawei CR Agreement Yes
Yes
 		revised No S5‑251977  
    S5‑251977 Rel-19 CR TS 28.623 Address the misalignment issues for vnfParametersList and peeParametersList (stage3) Huawei CR Agreement Yes
Yes
 		agreed No   S5‑251400
    S5‑251402 Rel-19 CR TS 28.622 Enhance the definition for schedulerStatus and conditionStatus with default values (stage2) Huawei CR Agreement Yes
YesNokia: straight quotation marks Ericsson offline comments
 		revised No S5‑251974  
    S5‑251974 Rel-19 CR TS 28.622 Enhance the definition for schedulerStatus and conditionStatus with default values (stage2) Huawei CR Agreement Yes
Yeslate comment: Nokia: what is the default value?
 		not pursued No   S5‑251402
    S5‑251403 Rel-19 CR TS 28.623 Enhance the definition for schedulerStatus and conditionStatus with default values (stage3) Huawei CR Agreement Yes
YesEricsson offline coment
 		revised No S5‑251975  
    S5‑251975 Rel-19 CR TS 28.623 Enhance the definition for schedulerStatus and conditionStatus with default values (stage3) Huawei CR Agreement Yes
Yes
 		not pursued No   S5‑251403
    S5‑251404 Rel-19 CR TS 28.540 Enhance the requirement description Huawei CR Agreement Yes
Yes
 		revised No S5‑251969  
    S5‑251969 Rel-19 CR TS 28.540 Enhance the requirement description Huawei CR Agreement Yes
Yes
 		agreed No   S5‑251404
    S5‑251573 Rel-19 CR TS 28.540 Add requirements for management of Ambient IoT Huawei CR Agreement Yes
Yes
 		revised No S5‑251970  
    S5‑251970 Rel-19 CR TS 28.540 Add requirements for management of Ambient IoT Huawei, China Unicom CR Agreement Yes
Yes
 		agreed No   S5‑251573
    S5‑251574 Rel-19 CR TS 28.541 Add AIOTF and ADM IOC to support management of Ambient IoT Huawei, China Unicom CR Agreement Yes
Yes
 		revised No S5‑251971  
    S5‑251971 Rel-19 CR TS 28.541 Add AIOTF and ADM IOC to support management of Ambient IoT Huawei, China Unicom CR Agreement Yes
Yes
 		agreed No   S5‑251574
    S5‑251575 Rel-19 CR TS 28.538 Update the procedure 5GC NF Provisioning Huawei CR Agreement Yes
Yes
 		revised No S5‑251968  
    S5‑251968 Rel-19 CR TS 28.538 Update the procedure 5GC NF Provisioning Huawei CR Agreement Yes
Yes
 		agreed No   S5‑251575
    S5‑251589 Rel-19 CR 28.662 Update sector equipment and antenna function definitions Ericsson Canada Inc. CR Agreement Yes
YesNokia does not support the change to cl.1 & 2.
 		revised No S5‑251980  
    S5‑251980 Rel-19 CR 28.662 Update sector equipment and antenna function definitions Ericsson Canada Inc. CR Agreement No
Yesremove the first change Nokia disagreed. different understanding of the discussion paper.
 		not pursued No   S5‑251589
    S5‑251590 Rel-19 CR 28.541 Update sector equipment and antenna function definitions Ericsson Canada Inc. CR Agreement Yes
Yes
 		revised No S5‑251981  
    S5‑251981 Rel-19 CR 28.541 Update sector equipment and antenna function definitions Ericsson Canada Inc. CR Agreement No
Yes
 		not pursued No   S5‑251590
    S5‑251711 Rel-19 CR 28.623 Update sector equipment and antenna function definitions Ericsson Canada Inc. CR Agreement Yes
Yesoffline
 		revised No S5‑251982  
    S5‑251982 Rel-19 CR 28.623 Update sector equipment and antenna function definitions Ericsson Canada Inc. CR Agreement No
Yes
 		not pursued No   S5‑251711
    S5‑251720 DP on Solution-agnostic request for service provisioning Ericsson GmbH, Eurolab discussion Endorsement Yes
YesNokia does not agree, doc is out of scope
 		noted No    
    S5‑251721 Rel-19 CR TS 28.541 Enhance network slicing model to support solution-agnostic service provisioning request. Ericsson GmbH, Eurolab CR Agreement Yes
YesRakuten, Nokia objected.
 		not pursued No    
    S5‑251723 Rel-19 CR TS 28.531 Add requirements to support solution-agnostic request for service provisioning Ericsson GmbH, Eurolab CR Agreement Yes
YesRakuten, Nokia objected.
 		not pursued No    
    S5‑251728 Rel-19 CR TS 28.622 Remove stage-3 clarifications for Float datatype Ericsson GmbH, Eurolab CR Agreement Yes
YesNokia co-signed
 		revised No S5‑251973  
    S5‑251973 Rel-19 CR TS 28.622 Remove stage-3 clarifications for Float datatype Ericsson GmbH, Eurolab, Nokia CR Agreement Yes
Yes
 		agreed No   S5‑251728
    S5‑251731 Rel-19 CR 28.663 Update sector equipment and antenna function definitions Ericsson Canada Inc. CR Agreement Yes
Yeswrong WIC
 		revised No S5‑251983  
    S5‑251983 Rel-19 CR 28.663 Update sector equipment and antenna function definitions Ericsson Canada Inc. CR Agreement No
Yes
 		not pursued No   S5‑251731
6.19.14 Subscriber and Equipment Trace and QoE collection management S5‑251238 Rel-19 CR TS 32.423 Corrections on Trace Record Format Ericsson, AT&T CR Agreement Yes
Yes
 		revised No S5‑251984  
    S5‑251984 Rel-19 CR TS 32.423 Corrections on Trace Record Format Ericsson, AT&T CR Agreement Yes
YesNokia objected. Nokia does not support either formats. Ericsson: no technical comment. Nokia disagreed.
 		not pursued No   S5‑251238
    S5‑251375 Introduction of Sequence Number in Trace Record Header Jio Platforms Ltd (JPL) CR Agreement Yes
Yes
 		withdrawn Yes    
    S5‑251378 Rel-19 CR TS 32.423 Introduction of Sequence Number in Trace Record Header Jio Platforms Ltd (JPL) CR Agreement Yes
YesEricsson doesn't agree
 		not pursued No    
    S5‑251388 Additional NFs added in Trace Record contents Jio Platforms Ltd(JPL) CR Agreement Yes
Yes
 		not pursued No    
    S5‑251405 Introduction of Summary Code in Trace Record Header for Optimised Tracing Jio Platforms Ltd (JPL) CR Agreement Yes
Yes
 		withdrawn Yes    
    S5‑251525 Rel-19 CR TS 32.423 Introduction of Summary Code in Trace Record Header for Optimised Tracing Jio Platforms Ltd (JPL) CR Agreement Yes
Yesrelated to 1524 no delegate present
 		not pursued No    
6.19.15 Study on Management Aspects of NTN Phase 2 (completed)                      
6.19.15.1 Management Aspects of NTN Phase 2 S5‑251454 Rel-19 CR TS 28.541 Add attributes to support MEC deployment on board the NTN ZTE Corporation CR Agreement Yes
YesHuawei & Samsung offline comments
 		revised No S5‑251985  
    S5‑251985 Rel-19 CR TS 28.541 Add attributes to support MEC deployment on board the NTN ZTE Corporation CR Agreement Yes
Yes
 		agreed No   S5‑251454
    S5‑251528 CR 28.657 Add requirements for SnF support Samsung R&D Institute UK CR Agreement Yes
Yes
 		revised No S5‑251986  
    S5‑251986 CR 28.657 Add requirements for SnF support Samsung R&D Institute UK CR Agreement Yes
Yes
 		agreed No   S5‑251528
    S5‑251556 Rel-19 CR TS 28.540 Add new requirements for management of NTN China Unicom CR Agreement Yes
Yesdoc not needed
 		not pursued No    
    S5‑251576 Rel-19 CR TS 28.541 add YAML stage 3 for NTN time based solution Huawei CR Agreement Yes
YesNokia: keep open
 		revised No S5‑252110  
    S5‑252110 Rel-19 CR TS 28.541 add YAML stage 3 for NTN time based solution Huawei CR Agreement Yes
Yes
 		agreed No   S5‑251576
    S5‑251585 Rel-19 CR 28.540 Add secure backhaul requirements for NTN Ericsson Canada Inc. CR Agreement Yes
Yesmove content into 314
 		revised No S5‑251987  
    S5‑251987 Rel-19 CR 28.540 Add secure backhaul requirements for NTN Ericsson Canada Inc. CR Agreement Yes
Yes
 		revised No   S5‑251585
    S5‑251988 Rel-19 CR 28.314 Add secure backhaul requirements for NTN Ericsson Canada Inc. CR Agreement Yes
Yesnow Tdoc during the meeting
 		revised No    
    S5‑251989 Rel-19 CR 28.315 Add secure backhaul requirements for NTN Ericsson Canada Inc. CR Agreement Yes
Yesnow Tdoc during the meeting
 		agreed No    
    S5‑251586 Rel-19 CR 28.541 Add solution for NTN time-based IP configuration Ericsson Canada Inc. CR Agreement Yes
Yes
 		revised No S5‑251991  
    S5‑251991 Rel-19 CR 28.541 Add solution for NTN time-based IP configuration Ericsson Canada Inc. CR Agreement Yes
Yes
 		agreed No   S5‑251586
    S5‑251588 Rel-19 CR 28.540 Add NTN regenerative concepts and requirements Ericsson CR Agreement Yes
Yes
 		revised No S5‑252024  
    S5‑252024 Rel-19 CR 28.540 Add NTN regenerative concepts and requirements Ericsson CR Agreement Yes
Yes
 		agreed No   S5‑251588
    S5‑251629 Rel-19 CR TS 28.658 Add attributes to support Store and Forward Satellite operation for eNB CATT CR Agreement Yes
YesSamsung supports this. Offline suggestions.
 		revised No S5‑252027  
    S5‑252025 Rel-19 CR TS 28.658 Add attributes to support Store and Forward Satellite operation for eNB CATT, Samsung CR Agreement Yes
Yes
 		agreed No   S5‑251629
    S5‑251630 Rel-19 CR TS 28.658 Add attributes to support Store and Forward Satellite operation for eNB stage3 CATT, Samsung CR Agreement Yes
Yes
 		agreed No    
    S5‑252026 Rel-19 CR TS 28.659 Add attributes to support Store and Forward Satellite operation for eNB stage3 CATT, Samsung CR Agreement Yes
Yeswill trigger a Rel-19 upgrade
 		agreed No    
    S5‑251631 Rel-19 CR TS 28.708 Add attributes to support Store and Forward Satellite operation for EPC CATT CR Agreement Yes
YesSamsung supports, offline suggestions.
 		revised No S5‑252027  
    S5‑252027 Rel-19 CR TS 28.708 Add attributes to support Store and Forward Satellite operation for EPC CATT, Samsung CR Agreement Yes
Yes
 		agreed No   S5‑251631
    S5‑251632 Rel-19 CR TS 28.709 Add attributes to support Store and Forward Satellite operation for EPC stage3 CATT CR Agreement Yes
Yes
 		revised No S5‑252028  
    S5‑252028 Rel-19 CR TS 28.709 Add attributes to support Store and Forward Satellite operation for EPC stage3 CATT, Samsung CR Agreement Yes
Yes
 		agreed No   S5‑251632
6.19.16 Study on management of IAB nodes (completed)                      
6.19.16.1 Management of IAB nodes S5‑251656 Requirements for IAB-node connects to management system Ericsson CR Agreement Yes
Yes
 		revised No S5‑251992  
    S5‑251992 Requirements for IAB-node connects to management system Ericsson CR Agreement Yes
Yes
 		agreed No   S5‑251656
    S5‑251695 Use case IAB-node connects to management system Ericsson CR Agreement Yes
Yes
 		agreed No    
    S5‑251708 Procedure IAB-node connects to management system Ericsson CR Agreement Yes
Yes
 		revised No S5‑251993  
    S5‑251993 Procedure IAB-node connects to management system Ericsson CR Agreement Yes
Yes
 		agreed No   S5‑251708
6.19.17 Study on management aspects of RedCap feature(completed)                      
6.19.17.1 Management Aspects of RedCap features S5‑251455 Rel-19 CR TS28.552 Enhance RRC connection resuming related measurements for RedCap UEs ZTE Corporation CR Agreement Yes
YesChina Unicom offline comments Samsung suggests rewording
 		revised No S5‑251994  
    S5‑251994 Rel-19 CR TS28.552 Enhance RRC connection resuming related measurements for RedCap UEs ZTE Corporation, China Unicom, Ericsson CR Agreement Yes
Yes
 		agreed No   S5‑251455
    S5‑251456 Rel-19 CR TS28.552 Enhance PRB Usage related measurements for RedCap UEs ZTE Corporation CR Agreement Yes
YesEricsson: UE type
 		revised No S5‑251995  
    S5‑251995 Rel-19 CR TS28.552 Enhance PRB Usage related measurements for RedCap UEs ZTE Corporation, China Unicom, Ericsson CR Agreement Yes
Yes
 		agreed No   S5‑251456
    S5‑251457 Rel-19 CR TS28.552 Enhance Number of Active UEs related measurements for RedCap UEs ZTE Corporation CR Agreement Yes
Yes
 		revised No S5‑251996  
    S5‑251996 Rel-19 CR TS28.552 Enhance Number of Active UEs related measurements for RedCap UEs ZTE Corporation, China Unicom, Ericsson CR Agreement Yes
Yes
 		agreed No   S5‑251457
    S5‑251745 Rel-19 CR TS 28.540 Adding requirement to control RedCap and e-RedCap UEs access based on network conditions Samsung Electronics GmbH CR Agreement Yes
Yes
 		revised No S5‑251997  
    S5‑251997 Rel-19 CR TS 28.540 Adding requirement to control RedCap and e-RedCap UEs access based on network conditions Samsung Electronics GmbH CR Agreement Yes
YesEricsson objected
 		not pursued No   S5‑251745
    S5‑251748 Rel-19 CR TS 28.541 Enhancing NR NRM to control RedCap and e-RedCap UEs access Samsung Electronics GmbH CR Agreement Yes
Yes
 		revised No S5‑252111  
    S5‑252111 Rel-19 CR TS 28.541 Enhancing NR NRM to control RedCap and e-RedCap UEs access Samsung Electronics GmbH CR Agreement Yes
YesEricsson objected
 		not pursued No   S5‑251748
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‑251336 Rel-19 CR 28.552 Add a new measurement related to efficiency of data collection from NFs performed by NWDAF China Telecom CR Agreement Yes
Yes
 		revised No S5‑251998  
    S5‑251998 Rel-19 CR 28.552 Add a new measurement related to efficiency of data collection from NFs performed by NWDAF China Telecom, Ericsson CR Agreement Yes
Yes
 		agreed No   S5‑251336
    S5‑251337 Rel-19 CR 28.552 Add a new measurement related to efficiency of data collection from DCCF or NWDAF hosting DCCF performed by NWDAF China Telecom CR Agreement Yes
Yes
 		revised No S5‑251999  
    S5‑251999 Rel-19 CR 28.552 Add a new measurement related to efficiency of data collection from DCCF or NWDAF hosting DCCF performed by NWDAF China Telecom CR Agreement Yes
Yesmerged into S5-251998
 		merged No S5‑251998 S5‑251337
    S5‑251338 Rel-19 CR 28.552 Add a new measurement related to transmission rate related to the data collection from NFs performed by NWDAF China Telecom CR Agreement Yes
Yes
 		revised No S5‑252000  
    S5‑252000 Rel-19 CR 28.552 Add a new measurement related to transmission rate related to the data collection from NFs performed by NWDAF China Telecom, Ericsson CR Agreement Yes
Yes
 		agreed No   S5‑251338
    S5‑251339 Rel-19 CR 28.552 Add a new measurement related to transmission rate related to the data collection from DCCF or NWDAF hosting DCCF performed by NWDAF China Telecom CR Agreement Yes
Yes
 		revised No S5‑252001  
    S5‑252001 Rel-19 CR 28.552 Add a new measurement related to transmission rate related to the data collection from DCCF or NWDAF hosting DCCF performed by NWDAF China Telecom CR Agreement Yes
Yesmerged into S5-252000
 		merged No S5‑252000 S5‑251339
    S5‑251340 Rel-19 CR 28.552 Add use case descriptions on monitoring of NWDAF data collection China Telecom CR Agreement Yes
Yes
 		revised No S5‑252002  
    S5‑252002 Rel-19 CR 28.552 Add use case descriptions on monitoring of NWDAF data collection China Telecom, Ericsson CR Agreement Yes
Yes
 		agreed No   S5‑251340
6.19.19 Study on Management of Network Sharing Phase 3 (completed)                      
6.19.19.1 Management of Network Sharing Phase 3 S5‑251374 Rel-19 CR TS 32.130 Enhance the service-based management architecture for MOCN Huawei, China Unicom CR Agreement Yes
Yes
 		revised No S5‑252003  
    S5‑252003 Rel-19 CR TS 32.130 Enhance the service-based management architecture for MOCN Huawei, China Unicom CR Agreement Yes
Yes
 		agreed No   S5‑251374
    S5‑251376 Rel-19 CR TS 32.130 Enhance Indirect Network Sharing scenario description Huawei, China Unicom CR Agreement Yes
YesCat. F->D
 		revised No S5‑252004  
    S5‑252004 Rel-19 CR TS 32.130 Enhance Indirect Network Sharing scenario description Huawei, China Unicom CR Agreement Yes
Yes
 		agreed No   S5‑251376
    S5‑251377 Rel-19 CR TS 32.130 Clarify MOCN and GWCN scenarios description Huawei, China Unicom CR Agreement Yes
Yes
 		revised No S5‑252005  
    S5‑252005 Rel-19 CR TS 32.130 Clarify MOCN and GWCN scenarios description Huawei, China Unicom CR Agreement Yes
Yes
 		agreed No   S5‑251377
    S5‑251379 Rel-19 CR TS 32.130 Categorize requirements for the management support for Indirect Network Sharing scenario Huawei, China Unicom CR Agreement Yes
Yes
 		revised No S5‑252006  
    S5‑252006 Rel-19 CR TS 32.130 Categorize requirements for the management support for Indirect Network Sharing scenario Huawei, China Unicom CR Agreement Yes
Yes
 		agreed No   S5‑251379
    S5‑251381 Rel-19 CR TS 32.130 Separate business-level requirements from specification-level requirements Huawei, China Unicom CR Agreement Yes
Yes
 		agreed No    
    S5‑251650 Rel-19 CR TS 28.541 Add support of RAN configurations for Indirect Network Sharing China Unicom CR Agreement No
Yes
 		withdrawn Yes    
    S5‑251651 Rel-19 CR TS 32.130 Update abbreviations for Indirect Network Sharing China Unicom, China Telecom CR Agreement Yes
YesCat. B->F
 		revised No S5‑252007  
    S5‑252007 Rel-19 CR TS 32.130 Update abbreviations for Indirect Network Sharing China Unicom, China Telecom CR Agreement Yes
Yes
 		agreed No   S5‑251651
    S5‑251655 Rel-19 CR TS 28.541 Add solution to support RAN configurations for Indirect Network Sharing China Unicom, China Telecom CR Agreement Yes
Yes
 		agreed No    
    S5‑251732 Rel-19 CR TS 32.130 Add PLMN granularity performance measurement requirements for Indirect Network Sharing Esurfing IoT, China Unicom CR Agreement Yes
YesHuawei & Deutsche Telekom asked to revise 'some'. Ericsson: we already have the requirements. Check offline.
 		revised No S5‑252008  
    S5‑252008 Rel-19 CR TS 32.130 Add PLMN granularity performance measurement requirements for Indirect Network Sharing Esurfing IoT, China Unicom CR Agreement Yes
Yes
 		agreed No   S5‑251732
6.19.20 Study on energy efficiency and energy saving aspects of 5G networks and services (completed)                      
6.19.20.1 Energy efficiency and energy saving aspects of 5G networks and services S5‑251264 Rel-19 CR TS 28.310 Introduce energy supply, carbon emission and renewable energy information elements Nokia CR Agreement Yes
YesNTT DOCOMO: offline comments add Huawei, Orange and AT&T
 		revised No S5‑251941  
    S5‑251941 Rel-19 CR TS 28.310 Introduce energy supply, carbon emission and renewable energy information elements Nokia, Huawei, Orange, AT&T CR Agreement Yes
YesEricsson objected SA% doesn't need to satisfy solutions for SA1 requirements.
 		not pursued No   S5‑251264
    S5‑251265 Rel-19 CR TS 28.622 Add GenericCollection to support grouping of objects for energy related information - Stage 2 Nokia CR Agreement Yes
Yespostponed
 		not pursued No    
    S5‑251266 Rel-19 CR TS 28.623 Add GenericCollection to support grouping of objects for energy related information - Stage 3 Nokia CR Agreement Yes
Yespostponed
 		revised No S5‑251942  
    S5‑251942 Rel-19 CR TS 28.623 Add GenericCollection to support grouping of objects for energy related information - Stage 3 Nokia CR Agreement Yes
Yesreissued as S5-252109 because of title and contents change add Huawei, Orange and AT&T
 		revised No   S5‑251266
    S5‑252109 Rel-19 CR TS 28.623 Update stage 3 to support energy information NRM Nokia, Huawei, Orange, AT&T CR Agreement Yes
Yes
 		not pursued No    
    S5‑251267 Rel-19 CR TS 28.532 Introduce energy supply, carbon emission and renewable energy information elements - stage 3 impacts Nokia CR Agreement No
Yes
 		withdrawn Yes    
    S5‑251268 Rel-19 CR TS 28.310 Multi-carrier RAN energy saving optimization Nokia CR Agreement Yes
YesHuawei: remove NOTE 1.
 		revised No S5‑251945  
    S5‑251945 Rel-19 CR TS 28.310 Multi-carrier RAN energy saving optimization Nokia CR Agreement Yes
Yes
 		agreed No   S5‑251268
    S5‑251269 Rel-19 CR TS 28.104 Enhance the MDA assisted Energy Saving use case for handling of power shortages Nokia CR Agreement Yes
YesNTT DOCOMO offline comments.
 		revised No S5‑251944  
    S5‑251944 Rel-19 CR TS 28.104 Enhance the MDA assisted Energy Saving use case for handling of power shortages Nokia CR Agreement Yes
Yes
 		not pursued No   S5‑251269
    S5‑251270 Discussion on modelling of energy-related information Nokia discussion Information Yes
Yes
 		noted No    
    S5‑251271 DP on TS 28.554 KPIs related to NF Energy Consumption Nokia discussion Endorsement No
Yes
 		withdrawn Yes    
    S5‑251335 Incorporation of conclusions from TR 28.880 Vodafone CR Agreement Yes
Yesdiscussion with Nokia about the GSMA attribute Nokia objected
 		not pursued No    
    S5‑251943 Incorporation of conclusions from TR 28.880 Vodafone CR Agreement No
Yesnot available
 		withdrawn Yes    
    S5‑251386 Rel-19 CR TS 28.310 Add information model definitions for energy related information Huawei CR Agreement Yes
Yesmerged into S5-251941
 		merged No S5‑251941  
6.19.21 Study on Enhanced OAM for management exposure to external consumers (completed)                      
6.19.21.1 Enhanced OAM for management service exposure to external consumers through CAPIF S5‑251373 Rel-19 pCR TS 28.579 Introduce definition of External MnS consumer Huawei pCR Approval Yes
Yes
 		revised No S5‑251946  
    S5‑251946 Rel-19 pCR TS 28.579 Introduce definition of External MnS consumer Huawei pCR Approval Yes
Yes
 		revised No S5‑252126 S5‑251373
    S5‑252126 Rel-19 pCR TS 28.579 Introduce definition of External MnS consumer Huawei, Ericsson, Nokia, Deutsche Telekom pCR Approval No
Yes
 		approved No   S5‑251946
    S5‑251483 pCR TS 28.579 Add concepts content Huawei, Nokia, Samsung pCR Approval Yes
YesEricsson: discussion on internal/external.
 		revised No S5‑251947  
    S5‑251947 pCR TS 28.579 Add concepts content Huawei, Nokia, Samsung, AT&T, Ericsson pCR Approval Yes
Yes
 		approved No   S5‑251483
    S5‑251484 DP on management services exposure Huawei discussion Endorsement Yes
YesEricsson: prefer to wait for the normative work before endorsing. Samsung only endorses the 2. proposal. Agreed WID restrict to CAPIF. merged into S5-251948
 		merged No S5‑251948  
    S5‑251485 pCR TS 28.579 Introduce MSEDF Huawei pCR Approval Yes
Yes
 		not pursued No    
    S5‑251696 Discussion paper on MSED components, requirements and naming Nokia Hungary discussion Endorsement Yes
Yes
 		revised No S5‑251948  
    S5‑251948 Discussion paper on MSED components, requirements and naming Nokia, Huawei, AT&T, Ericsson discussion Endorsement Yes
Yes
 		endorsed No   S5‑251696
    S5‑251697 Rel-19 pCR TS 28.579 Add use case and requirements for registration of the MSED into the CCF Nokia Hungary pCR Approval Yes
Yes
 		revised No S5‑251949  
    S5‑251949 Rel-19 pCR TS 28.579 Add use case and requirements for registration of the MSED into the CCF Nokia Hungary pCR Approval Yes
Yes+ AT&T
 		revised No S5‑252127 S5‑251697
    S5‑252127 Rel-19 pCR TS 28.579 Add use case and requirements for registration of the MSED into the CCF Nokia Hungary, AT&T pCR Approval No
Yes
 		approved No   S5‑251949
    S5‑251698 Rel-19 pCR TS 28.579 Add use case solution for registration of the MSED into the CCF Nokia Hungary pCR Approval Yes
Yes
 		revised No S5‑252036  
    S5‑252036 Rel-19 pCR TS 28.579 Add use case solution for registration of the MSED into the CCF Nokia Hungary pCR Approval Yes
Yes+AT&T
 		revised No S5‑252128 S5‑251698
    S5‑252128 Rel-19 pCR TS 28.579 Add use case solution for registration of the MSED into the CCF Nokia Hungary, AT&T pCR Approval No
Yes
 		approved No   S5‑252036
    S5‑251699 Rel-19 pCR TS 28.579 Add use case requirements for publishing of management services to the CCF Nokia Hungary pCR Approval Yes
Yes
 		revised No S5‑252037  
    S5‑252037 Rel-19 pCR TS 28.579 Add use case requirements for publishing of management services to the CCF Nokia Hungary pCR Approval Yes
Yes+AT&T
 		revised No S5‑252129 S5‑251699
    S5‑252129 Rel-19 pCR TS 28.579 Add use case requirements for publishing of management services to the CCF Nokia Hungary, AT&T pCR Approval No
Yes
 		approved No   S5‑252037
    S5‑251700 Rel-19 pCR TS 28.579 Add use case solution to enable the publishing management services to the CCF Nokia Hungary pCR Approval Yes
Yes
 		revised No S5‑252038  
    S5‑252038 Rel-19 pCR TS 28.579 Add use case solution to enable the publishing management services to the CCF Nokia Hungary pCR Approval Yes
Yes+AT&T
 		revised No S5‑252130 S5‑251700
    S5‑252130 Rel-19 pCR TS 28.579 Add use case solution to enable the publishing management services to the CCF Nokia Hungary, AT&T pCR Approval No
Yes
 		approved No   S5‑252038
    S5‑251701 Rel-19 pCR TS 28.579 Add use case requirements for logging of management service APIs invocations to the CCF Nokia Hungary pCR Approval Yes
Yes
 		revised No S5‑252039  
    S5‑252039 Rel-19 pCR TS 28.579 Add use case requirements for logging of management service APIs invocations to the CCF Nokia Hungary pCR Approval Yes
Yes+AT&T
 		revised No S5‑252131 S5‑251701
    S5‑252131 Rel-19 pCR TS 28.579 Add use case requirements for logging of management service APIs invocations to the CCF Nokia Hungary, AT&T pCR Approval No
Yes
 		approved No   S5‑252039
    S5‑251702 Rel-19 pCR TS 28.579 Add use case solution for logging the management service API invocations to the CCF Nokia Hungary pCR Approval Yes
Yes+AT&T
 		revised No S5‑252132  
    S5‑252132 Rel-19 pCR TS 28.579 Add use case solution for logging the management service API invocations to the CCF Nokia Hungary, AT&T pCR Approval No
Yes
 		approved No   S5‑251702
    S5‑251762 Draft TS28.579 Nokia draft TS discussion No
No
 		email approval No    
6.19.22 Management for MonStra (completed) S5‑251734 Correction of the description of the attribute stmTargetUri Nokia Germany CR Agreement Yes
YesCR in the CR field! co-sign Ericsson
 		revised No S5‑252091  
    S5‑252091 Correction of the description of the attribute stmTargetUri Nokia Germany, Ericsson CR Agreement Yes
Yesd1
 		agreed No   S5‑251734
7 Charging                      
7.1 Charging Plenary S5‑251215 agenda_with_Tdocs_sequence_CH SWG CH Chair (MATRIXX Software) agenda Information Yes
Yes
 		revised No S5‑251800  
    S5‑251800 agenda_with_Tdocs_sequence_CH SWG CH Chair (MATRIXX Software) agenda Information No
Yes
 		noted No   S5‑251215
    S5‑251216 Charging exec report SWG CH Chair (MATRIXX Software) report Information No
Yes
 		noted No    
    S5‑251217 Collection of useful contributions and external communication documents in CH SWG Vice Chair (Huawei Tech.(UK) Co.. Ltd) other Information Yes
Yes
 		noted No    
    S5‑251329 Reply LS on Usage of Charging Characteristics and CHF Group ID SA2 LS in Information Yes
Yes
 		noted No    
7.2 New Charging Study/Work Item proposals S5‑251368 Revised WID on on Charging aspects of next generation real time communication services phase 2 China Mobile WID revised Approval Yes
Yes
 		revised No S5‑251857  
    S5‑251857 Revised WID on on Charging aspects of next generation real time communication services phase 2 China Mobile WID revised Approval Yes
Yes
 		agreed No   S5‑251368
    S5‑251433 Rel-20 DP Moderator update on Charging Aspects of CAPIF Nokia discussion Discussion Yes
Yes
 		noted No    
    S5‑251463 Moderated R20 topic discussion on use cases for charging reliability enhancement Huawei discussion Discussion Yes
Yes
 		withdrawn Yes    
    S5‑251533 Revised WID on Charging for Uncrewed Aerial Systems Phase 3 China Mobile Com. Corporation WID revised Agreement Yes
Yes
 		revised No S5‑251801  
    S5‑251801 Revised WID on Charging for Uncrewed Aerial Systems Phase 3 China Mobile Com. Corporation WID revised Agreement Yes
Yes
 		agreed No   S5‑251533
    S5‑251535 Discussion paper on objective for UAS_Ph3-CH China Mobile Com. Corporation discussion Discussion Yes
Yes
 		noted No    
7.3 Charging Maintenance and Rel-19 Charging small enhancements S5‑251291 Correct bindings information for 5G ProSe Charging China Telecom CR Agreement Yes
Yes
 		revised No S5‑251847  
    S5‑251847 Correct bindings information for 5G ProSe Charging China Telecom CR Agreement Yes
Yes
 		agreed No   S5‑251291
    S5‑251301 Discussion on NSPA charging information correction Huawei discussion Discussion Yes
Yes
 		withdrawn Yes    
    S5‑251302 Rel-18 CR 28.201 Correction on NSPA charging information Huawei CR Agreement Yes
Yes
 		withdrawn Yes    
    S5‑251303 Rel-19 CR 28.201 Correction on NSPA charging information Huawei CR Agreement Yes
Yes
 		withdrawn Yes    
    S5‑251304 Rel-18 CR 28.201 Correction on NSPA charging information Huawei CR Agreement Yes
Yes
 		withdrawn Yes    
    S5‑251305 Rel-19 CR 28.201 Correction on NSPA charging information Huawei CR Agreement Yes
Yes
 		withdrawn Yes    
    S5‑251306 Rel-18 CR 32.298 Correction on NSPA charging information Huawei CR Agreement Yes
Yes
 		withdrawn Yes    
    S5‑251307 Rel-19 CR 32.298 Correction on NSPA charging information Huawei CR Agreement Yes
Yes
 		withdrawn Yes    
    S5‑251371 Rel-19 CR 28.851 Cleanup China Mobile CR Approval Yes
Yes
 		withdrawn Yes    
    S5‑251434 Rel-19 CR 28.849 EditHelp Editorial Changes Nokia CR Approval Yes
Yes
 		revised No S5‑251850  
    S5‑251850 Rel-19 CR 28.849 EditHelp Editorial Changes Nokia CR Approval Yes
Yes
 		agreed No   S5‑251434
    S5‑251508 Rel-19 DP Handling of un-reported usage information after failure Ericsson discussion Agreement Yes
Yes
 		noted No    
    S5‑251526 Rel-19 CR 28.851 Addressing editHelp comments China Mobile CR Approval Yes
Yes
 		revised No S5‑251851  
    S5‑251851 Rel-19 CR 28.851 Addressing editHelp comments China Mobile CR Approval Yes
Yes
 		agreed No   S5‑251526
    S5‑251531 Correction of reference China Mobile Com. Corporation CR Agreement Yes
Yes
 		revised No S5‑251852  
    S5‑251852 Correction of reference China Mobile Com. Corporation CR Agreement Yes
Yes
 		agreed No   S5‑251531
    S5‑251604 Rel-18 CR 32.298 Correction of API Information Amdocs CR Approval Yes
Yes
 		revised No S5‑251853  
    S5‑251853 Rel-18 CR 32.298 Correction of API Information Amdocs CR Approval Yes
Yesd2
 		agreed No   S5‑251604
    S5‑251605 Rel-19 CR 32.298 Correction of API Information Amdocs Software Systems Ltd CR Approval Yes
Yes
 		revised No S5‑251854  
    S5‑251854 Rel-19 CR 32.298 Correction of API Information Amdocs Software Systems Ltd CR Approval Yes
Yesd2
 		agreed No   S5‑251605
7.4 Rel-19 Work Items                      
7.4.1 CHF Segmentation S5‑251464 Discussion on the charging domain for NRF registration and discovery Huawei discussion Discussion Yes
Yes
 		noted No    
    S5‑251465 Rel-19 CR 32.291 Add charging domain for NRF registration and discovery Huawei CR Agreement Yes
Yesmerged into S5-251509
 		merged No S5‑251509  
    S5‑251509 Rel-19 CR 32.291 Addition of domain features Ericsson CR Agreement Yes
Yes
 		revised No S5‑251802  
    S5‑251802 Rel-19 CR 32.291 Addition of domain features Ericsson CR Agreement Yes
Yesr3
 		agreed No   S5‑251509
    S5‑251510 Rel-19 CR 32.274 Addition of charging characteristics Ericsson CR Agreement Yes
Yes
 		revised No S5‑251803  
    S5‑251803 Rel-19 CR 32.274 Addition of charging characteristics Ericsson CR Agreement Yes
Yes
 		agreed No   S5‑251510
7.4.2 Charging Aspects of Ranging and Sidelink Positioning (completed)                      
7.4.3 Charging aspects for energy efficiency of network slice (completed)                      
7.4.4 Charging for indirect network sharing (completed)                      
7.4.5 Charging Aspects for 5G ProSe Ph3 S5‑251299 Correct bindings information for 5G ProSe Charging China Telecom CR Agreement Yes
Yes
 		revised No S5‑251848  
    S5‑251848 Correct bindings information for 5G ProSe Charging China Telecom CR Agreement Yes
Yesr2
 		agreed No   S5‑251299
    S5‑251300 Correct bindings information for 5G ProSe Charging China Telecom CR Agreement Yes
Yes
 		revised No S5‑251849  
    S5‑251849 Correct bindings information for 5G ProSe Charging China Telecom CR Agreement Yes
Yes
 		agreed No   S5‑251300
    S5‑251312 Add layer 3 multi-hop ProSe UE-to-Network relay communication related attributes China Telecom CR Agreement Yes
Yes
 		revised No S5‑251856  
    S5‑251856 Add layer 3 multi-hop ProSe UE-to-Network relay communication related attributes China Telecom CR Agreement Yes
Yes
 		agreed No   S5‑251312
    S5‑251313 Add layer 3 multi-hop ProSe UE-to-Network relay communication related CDR parameters China Telecom CR Agreement Yes
Yes
 		revised No S5‑251804  
    S5‑251804 Add layer 3 multi-hop ProSe UE-to-Network relay communication related CDR parameters China Telecom CR Agreement Yes
Yes
 		agreed No   S5‑251313
    S5‑251315 Add information flows of Layer-3 ProSe UE-to-UE direct communication China Telecom Corporation Ltd. CR Agreement No
Yes
 		withdrawn Yes    
7.4.6 Charging aspects of satellite access Phase 3 S5‑251466 Rel-19 CR 32.255 Addition of the Satellite Roaming Charging Principle Huawei CR Agreement Yes
Yes
 		revised No S5‑251807  
    S5‑251807 Rel-19 CR 32.255 Addition of the Satellite Roaming Charging Principle Huawei CR Agreement Yes
Yes
 		agreed No   S5‑251466
    S5‑251580 Update Business roles for Support of Satellite charging CSCN, CATT CR Agreement Yes
Yes
 		agreed No    
    S5‑251592 Update Charging principles and architecture references for MVNOs charging CSCN CR Agreement Yes
Yes
 		revised No S5‑251805  
    S5‑251805 Update Charging principles and architecture references for MVNOs charging CSCN CR Agreement Yes
Yes
 		agreed No   S5‑251592
    S5‑251640 Introduce the support of store and forward satellite operation and UE-satellite-UE communication CATT CR Approval Yes
Yes
 		revised No S5‑251806  
    S5‑251806 Introduce the support of store and forward satellite operation and UE-satellite-UE communication CATT CR Approval Yes
Yes
 		agreed No   S5‑251640
    S5‑251641 Add charging principle for store and forward satellite operation CATT CR Approval Yes
Yes
 		revised No S5‑251808  
    S5‑251808 Add charging principle for store and forward satellite operation CATT CR Approval Yes
Yes
 		agreed No   S5‑251641
    S5‑251642 Add charging information for store and forward satellite operation of SMS service CATT CR Approval Yes
Yes
 		revised No S5‑251809  
    S5‑251809 Add charging information for store and forward satellite operation of SMS service CATT CR Approval Yes
Yes
 		agreed No   S5‑251642
    S5‑251643 Add charging trigger for store and forward satellite operation with UP CIoT CATT CR Approval Yes
Yes
 		revised No S5‑251810  
    S5‑251810 Add charging trigger for store and forward satellite operation with UP CIoT CATT CR Approval Yes
Yes
 		agreed No   S5‑251643
    S5‑251644 Add charging information for store and forward satellite operation with UP CIoT CATT CR Approval Yes
Yes
 		revised No S5‑251811  
    S5‑251811 Add charging information for store and forward satellite operation with UP CIoT CATT CR Approval Yes
Yes
 		agreed No   S5‑251644
    S5‑251645 Add charging principle for UE-satellite-UE communication CATT CR Approval Yes
Yes
 		revised No S5‑251812  
    S5‑251812 Add charging principle for UE-satellite-UE communication CATT CR Approval Yes
Yes
 		agreed No   S5‑251645
    S5‑251646 Add charging trigger and charging information for UE-satellite-UE communication CATT CR Approval Yes
Yes
 		revised No S5‑251813  
    S5‑251813 Add charging trigger and charging information for UE-satellite-UE communication CATT CR Approval Yes
Yes
 		agreed No   S5‑251646
    S5‑251647 Update reference for the TR CATT CR Approval Yes
Yes
 		revised No S5‑251855  
    S5‑251855 Update reference for the TR CATT CR Approval Yes
Yes
 		agreed No   S5‑251647
7.4.7 Charging aspects of CAPIF S5‑251428 CR 32.254 CAPIF Converged charging Architecture Nokia CR Agreement Yes
Yesmerged into S5-251512
 		merged No S5‑251512  
    S5‑251435 Rel-19 CR 32.240 CAPIF Logical Charging Architecture Nokia CR Agreement Yes
Yes
 		revised No S5‑251814  
    S5‑251814 Rel-19 CR 32.240 CAPIF Logical Charging Architecture Nokia CR Agreement Yes
Yes
 		agreed No   S5‑251435
    S5‑251436 Rel-19 CR 32.240 CAPIF Service Charging Nokia CR Agreement Yes
Yes
 		revised No S5‑251815  
    S5‑251815 Rel-19 CR 32.240 CAPIF Service Charging Nokia CR Agreement Yes
Yes
 		agreed No   S5‑251436
    S5‑251437 Rel-19 CR 32.240 CAPIF Reference Point Nokia CR Agreement Yes
Yesmerged into S5-251435
 		merged No S5‑251435  
    S5‑251467 Rel-19 CR 32.254 Addition of the CAPIF Charging Architecture Huawei CR Agreement Yes
Yesmerged into S5-251512
 		merged No S5‑251512  
    S5‑251468 Rel-19 CR 32.254 Addition of the CAPIF Charging Principle and Scenarios Huawei CR Agreement Yes
Yesmerged into S5-251513
 		merged No S5‑251513  
    S5‑251469 Rel-19 CR 32.254 Addition of CAPIF charging support Huawei CR Agreement Yes
Yes
 		revised No S5‑251818  
    S5‑251818 Rel-19 CR 32.254 Addition of CAPIF charging support Huawei CR Agreement Yes
Yesr2
 		agreed No   S5‑251469
    S5‑251511 Rel-19 DP Charging architecture considerations for CAPIF Ericsson discussion Agreement Yes
Yes
 		noted No    
    S5‑251512 Rel-19 CR 32.254 Addition of charging architecture for CAPIF Ericsson CR Agreement Yes
Yes
 		revised No S5‑251816  
    S5‑251816 Rel-19 CR 32.254 Addition of charging architecture for CAPIF Ericsson CR Agreement Yes
Yesr1
 		agreed No   S5‑251512
    S5‑251513 Rel-19 CR 32.254 Addition of charging principles for CAPIF Ericsson CR Agreement Yes
Yes
 		revised No S5‑251817  
    S5‑251817 Rel-19 CR 32.254 Addition of charging principles for CAPIF Ericsson CR Agreement Yes
Yesr2
 		agreed No   S5‑251513
7.4.8 Charging aspects of next generation real time communication services phase 2 S5‑251369 Rel-19 CR 32.255 Support volume-based charging for standalone IMS data channel China Mobile CR Approval Yes
Yes
 		revised No S5‑251819  
    S5‑251819 Rel-19 CR 32.255 Support volume-based charging for standalone IMS data channel China Mobile CR Approval Yes
Yesr1
 		agreed No   S5‑251369
    S5‑251370 Rel-19 CR 32.260 Support duration-based charging for standalone IMS data channel China Mobile CR Agreement Yes
Yesno revision marks!!
 		revised No S5‑251822  
    S5‑251822 Rel-19 CR 32.260 Support duration-based charging for standalone IMS data channel China Mobile CR Agreement Yes
Yesr1
 		agreed No   S5‑251370
    S5‑251470 Rel-19 CR 32.260 Charging architecture for IMS DC application download charging charging Huawei CR Agreement Yes
Yes
 		revised No S5‑251823  
    S5‑251823 Rel-19 CR 32.260 Charging architecture for IMS DC application download charging charging Huawei CR Agreement Yes
Yesr1
 		agreed No   S5‑251470
    S5‑251471 Rel-19 CR 32.260 Charging principle for IMS DC application download charging Huawei CR Agreement Yes
Yes
 		revised No S5‑251824  
    S5‑251824 Rel-19 CR 32.260 Charging principle for IMS DC application download charging Huawei CR Agreement Yes
Yesr3
 		agreed No   S5‑251471
    S5‑251472 Rel-19 CR 32.260 Charging information for IMS DC application download charging Huawei CR Agreement Yes
Yes
 		revised No S5‑251825  
    S5‑251825 Rel-19 CR 32.260 Charging information for IMS DC application download charging Huawei CR Agreement Yes
Yesr2
 		agreed No   S5‑251472
    S5‑251473 Rel-19 CR 32.291 Charging information for IMS DC application download charging Huawei CR Agreement Yes
Yes
 		revised No S5‑251826  
    S5‑251826 Rel-19 CR 32.291 Charging information for IMS DC application download charging Huawei CR Agreement Yes
Yesr1
 		agreed No   S5‑251473
    S5‑251474 Rel-19 CR 32.298 Charging information for IMS DC application download charging Huawei CR Agreement Yes
Yes
 		revised No S5‑251827  
    S5‑251827 Rel-19 CR 32.298 Charging information for IMS DC application download charging Huawei CR Agreement Yes
Yesr2
 		agreed No   S5‑251474
    S5‑251475 Rel-19 CR 32.260 Add duration based charging principle for DC application usage Huawei CR Agreement Yes
Yesmerged into S5-251370
 		merged No S5‑251370  
    S5‑251476 Rel-19 CR 32.255 Add volume based charging principle for DC application download and usage Huawei CR Agreement Yes
Yes
 		revised No S5‑251820  
    S5‑251820 Rel-19 CR 32.255 Add volume based charging principle for DC application download and usage Huawei CR Agreement Yes
Yesr2
 		agreed No   S5‑251476
    S5‑251477 Rel-19 CR 32.255 Add volume based charging principle to support IMS DC as a PS Data Off Exempt Service Huawei CR Agreement Yes
Yes
 		revised No S5‑251821  
    S5‑251821 Rel-19 CR 32.255 Add volume based charging principle to support IMS DC as a PS Data Off Exempt Service Huawei CR Agreement Yes
Yesr3
 		agreed No   S5‑251477
    S5‑251478 Rel-19 CR 32.254 Add charging principle for IMS network capabilities exposure Huawei CR Agreement Yes
Yes
 		revised No S5‑251828  
    S5‑251828 Rel-19 CR 32.254 Add charging principle for IMS network capabilities exposure Huawei CR Agreement Yes
Yesr3
 		agreed No   S5‑251478
7.4.9 Charging for Uncrewed Aerial Systems Phase 2 S5‑251514 Rel-19 DP Format of user identity Ericsson discussion Agreement Yes
Yes
 		noted No    
    S5‑251515 Rel-19 CR 32.255 Addition of user identifiers Ericsson CR Agreement Yes
Yes
 		not pursued No    
7.4.10 Charging Aspects of 5GC LoCation Services S5‑251341 Extend the scope and charging architecture to support 5G LCS converged charging China Telecom CR Agreement Yes
Yes
 		revised No S5‑251829  
    S5‑251829 Extend the scope and charging architecture to support 5G LCS converged charging China Telecom CR Agreement Yes
Yesr1
 		agreed No   S5‑251341
    S5‑251342 Extend basic priciples, CDR generation and handling for 5G LCS converged charging China Telecom CR Agreement Yes
Yes
 		revised No S5‑251830  
    S5‑251830 Extend basic priciples, CDR generation and handling for 5G LCS converged charging China Telecom CR Agreement Yes
Yesr1
 		agreed No   S5‑251342
    S5‑251343 Add message flow of converged charging for 5GC-MT-LR China Telecom CR Agreement Yes
Yes
 		revised No S5‑251832  
    S5‑251832 Add message flow of converged charging for 5GC-MT-LR China Telecom CR Approval Yes
Yes
 		agreed No   S5‑251343
    S5‑251344 Add message flow of converged charging for 5GC-MO-LR China Telecom CR Approval Yes
Yes
 		revised No S5‑251833  
    S5‑251833 Add message flow of converged charging for 5GC-MO-LR China Telecom CR Approval Yes
Yes
 		agreed No   S5‑251344
    S5‑251345 Extend data description for 5G LCS converged charging China Telecom CR Approval Yes
Yes
 		revised No S5‑251834  
    S5‑251834 Extend data description for 5G LCS converged charging China Telecom CR Agreement Yes
Yesr1
 		agreed No   S5‑251345
    S5‑251346 Extend charging information and bindings for 5G LCS converged charging China Telecom CR Agreement Yes
Yes
 		revised No S5‑251835  
    S5‑251835 Extend charging information and bindings for 5G LCS converged charging China Telecom CR Agreement Yes
Yesr2
 		agreed No   S5‑251346
    S5‑251347 Extend Data Type for 5G LCS converged charging China Telecom CR Agreement Yes
Yes
 		revised No S5‑251836  
    S5‑251836 Extend Data Type for 5G LCS converged charging China Telecom CR Agreement Yes
Yesr1
 		agreed No   S5‑251347
    S5‑251348 Extend CHF-CDR for 5G LCS converged charging China Telecom CR Agreement Yes
Yes
 		revised No S5‑251837  
    S5‑251837 Extend CHF-CDR for 5G LCS converged charging China Telecom CR Agreement Yes
Yesr1
 		agreed No   S5‑251348
    S5‑251516 Rel-19 CR 32.271 Addition of LCS architecture Ericsson CR Agreement Yes
Yes
 		revised No S5‑251831  
    S5‑251831 Rel-19 CR 32.271 Addition of LCS architecture Ericsson CR Agreement Yes
Yes
 		agreed No   S5‑251516
    S5‑251517 Rel-19 CR 32.271 Addition of charging architecture for LCS Ericsson CR Agreement Yes
YesMerged into S5-251341
 		merged No S5‑251341  
    S5‑251518 Rel-19 CR 32.271 Addition of charging principles for LCS Ericsson CR Agreement Yes
YesMerged into S5-251342
 		merged No S5‑251342  
7.4.11 Charging for Ambient power-enabled Internet of Things S5‑251308 Rel-19 CR 32.240 Add charging support for AIoT service Huawei CR Agreement Yes
Yes
 		revised No S5‑251838  
    S5‑251838 Rel-19 CR 32.240 Add charging support for AIoT service Huawei CR Agreement Yes
Yesr2
 		agreed No   S5‑251308
    S5‑251309 Rel-19 CR 32.254 Add charging support for AIoT service Huawei CR Agreement Yes
Yes
 		revised No S5‑251839  
    S5‑251839 Rel-19 CR 32.254 Add charging support for AIoT service Huawei CR Agreement No
Yesr3
 		not pursued No   S5‑251309
    S5‑251310 Rel-19 CR 32.291 Add charging support for AIoT service Huawei CR Agreement Yes
Yes
 		revised No S5‑251840  
    S5‑251840 Rel-19 CR 32.291 Add charging support for AIoT service Huawei CR Agreement Yes
Yesr2
 		agreed No   S5‑251310
    S5‑251311 Rel-19 CR 32.298 Add charging support for AIoT service Huawei CR Agreement Yes
Yes
 		revised No S5‑251841  
    S5‑251841 Rel-19 CR 32.298 Add charging support for AIoT service Huawei CR Agreement Yes
Yesr2
 		agreed No   S5‑251311
7.4.12 Charging aspects for Multi-Operator Core Network (MOCN) network sharing S5‑251519 Rel-19 CR 32.240 Addition of MOCN network sharing Ericsson CR Agreement Yes
Yes
 		revised No S5‑251842  
    S5‑251842 Rel-19 CR 32.240 Addition of MOCN network sharing Ericsson CR Agreement Yes
Yesr2
 		agreed No   S5‑251519
    S5‑251520 Rel-19 CR 32.255 Addition of architecture for MOCN Ericsson CR Agreement Yes
Yes
 		revised No S5‑251843  
    S5‑251843 Rel-19 CR 32.255 Addition of architecture for MOCN Ericsson CR Agreement Yes
Yesr1
 		agreed No   S5‑251520
    S5‑251521 Rel-19 CR 32.256 Addition of architecture for network sharing Ericsson CR Agreement Yes
Yes
 		revised No S5‑251846  
    S5‑251846 Rel-19 CR 32.256 Addition of architecture for network sharing Ericsson CR Agreement Yes
Yesr2
 		agreed No   S5‑251521
    S5‑251522 Rel-19 CR 32.255 Addition of charging architecture for MOCN Ericsson CR Agreement Yes
Yes
 		revised No S5‑251844  
    S5‑251844 Rel-19 CR 32.255 Addition of charging architecture for MOCN Ericsson CR Agreement Yes
Yesr1
 		agreed No   S5‑251522
    S5‑251523 Rel-19 CR 32.255 Addition of charging requirements for MOCN Ericsson CR Agreement Yes
Yes
 		revised No S5‑251845  
    S5‑251845 Rel-19 CR 32.255 Addition of charging requirements for MOCN Ericsson CR Agreement Yes
Yesr1
 		agreed No   S5‑251523
7.5 Charging Studies                      
7.5.1 Charging aspects of satellite access Phase 3 (completed)                      
7.5.2 Charging Aspects of CAPIF (completed)                      
7.5.3 Charging aspects of next generation real time communication services phase 2 (completed)                      
7.5.4 Charging aspects of Uncrewed Aerial Vehicle (completed)                      
8 Any Other Business                      
9 Closing of the meeting