Tdoc List
2025-02-17 19:05
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‑250000 | Agenda | WG Chair | agenda | Yes |
Yes
| approved | No | |||
3 | IPR and legal declaration | S5‑250001 | IPR and legal declaration | WG Chair | other | Yes |
Yes
| noted | No | |||
4 | Meetings and activities reports | |||||||||||
4.1 | Last SA5 meeting report | S5‑250002 | Report from last SA5 meeting | MCC | report | Yes |
Yes
| approved | No | |||
4.2 | Inter-organizational reports | |||||||||||
5 | SA5 level issues | |||||||||||
5.1 | Administrative issues at SA5 level | S5‑250003 | Time Plan for SA5 Plenary and OAM sessions | WG Chair | agenda | Yes |
No
| available | No | |||
S5‑250004 | agenda_with_Tdocs_sequence_Plenary&OAM | WG Chair | agenda | Yes |
Yes
| noted | No | |||||
S5‑250005 | SA5 working procedures | WG Chair | other | Yes |
Yes
| revised | No | S5‑250784 | ||||
S5‑250784 | SA5 working procedures | WG Chair | other | - | No |
No
| reserved | No | S5‑250005 | |||
S5‑250006 | SA5 Meeting facility requirements | WG Chair | other | Yes |
Yes
| noted | No | |||||
S5‑250008 | Post meeting email approval status | WG Vice Chair (Ericsson) | other | No |
Yes
| noted | No | |||||
S5‑250011 | Plenary and OAM Chair notes and conclusions | WG Chair | report | No |
Yes
| noted | No | |||||
S5‑250014 | Rel-19 SA5 work plan TU table | WG Chair | other | Yes |
Yes
| revised | No | S5‑250785 | ||||
S5‑250785 | Rel-19 SA5 work plan TU table | WG Chair | other | - | No |
No
| reserved | No | S5‑250014 | |||
S5‑250018 | Latest SA5 Rel-19 WIs-SIs | WG Chair | other | Yes |
Yes
| noted | No | |||||
S5‑250019 | Rel-19 SA5 work planning | WG Chair | other | Yes |
Yes
| revised | No | S5‑250786 | ||||
S5‑250786 | Rel-19 SA5 work planning | WG Chair | other | - | No |
No
| reserved | No | S5‑250019 | |||
S5‑250020 | Rel-20 SA5 work planning | WG Chair | other | Yes |
Yes
| revised | No | S5‑250787 | ||||
S5‑250787 | Rel-20 SA5 work planning | WG Chair | other | - | No |
No
| reserved | No | S5‑250020 | |||
S5‑250389 | SA5 Working Procedure update | Ericsson | other | Yes |
Yes
| merged | No | S5‑250784 | ||||
5.2 | Technical issues at SA5 level | |||||||||||
5.3 | Liaison statements at SA5 level | S5‑250279 | Reply to LS on establishment of new Focus Group on Artificial Intelligence Native for Telecommunication Networks (FG-AINN) | NEC, Intel, Matrixx | LS out | Approval | Yes |
Yes
| revised | No | S5‑250788 | |
S5‑250788 | Reply to LS on establishment of new Focus Group on Artificial Intelligence Native for Telecommunication Networks (FG-AINN) | NEC, Intel, Matrixx | LS out | Approval | No |
No
| reserved | No | S5‑250279 | |||
S5‑250293 | LS on A-IoT Conclusions in SA WG2 | SA2 | LS in | Information | Yes |
No
| available | No | ||||
S5‑250295 | Reply-LS on Internal 5G Core information expose to trusted AF | SA3 | LS in | Information | Yes |
Yes
| noted | No | ||||
S5‑250296 | LS Reply on MBS Communication Service Type | SA4 | LS in | Information | Yes |
No
| available | No | ||||
S5‑250298 | LS on call for contributions to new Focus Group on Artificial Intelligence Native for Telecommunication Networks (FG-AINN) | ITU-T FG-AINN | LS in | Information | Yes |
No
| available | No | ||||
S5‑250299 | LS on Internet-Draft: “Export of GTP-U Information in IP Flow Information Export (IPFIX)” | IETF OPSAWG | LS in | Information | Yes |
No
| available | No | ||||
S5‑250300 | LS on GSMA OPG PRDs publication and document restructuring (SA5#158) | GSMA OPG | LS in | Information | Yes |
Yes
| noted | No | ||||
S5‑250357 | LS on multi-dimensional network energy efficiency metrics | Huawei | LS out | Approval | Yes |
Yes
| revised | No | S5‑250789 | |||
S5‑250789 | LS on multi-dimensional network energy efficiency metrics | Huawei | LS out | Approval | No |
No
| reserved | No | S5‑250357 | |||
S5‑250617 | LS on the scope attribute of the access token standard claims | Nokia UK | LS out | Approval | Yes |
Yes
| revised | No | S5‑250790 | |||
S5‑250790 | LS on the scope attribute of the access token standard claims | Nokia UK | LS out | Approval | No |
No
| reserved | No | S5‑250617 | |||
S5‑250680 | Reply to LS on A-IoT Conclusions in SA WG2 | China Unicom | LS out | Approval | No |
No
| reserved | No | ||||
5.4 | SA5 meeting calendar | S5‑250007 | SA5 meeting calendar | WG Chair | other | Yes |
Yes
| revised | No | S5‑250791 | ||
S5‑250791 | SA5 meeting calendar | WG Chair | other | - | No |
No
| reserved | No | S5‑250007 | |||
5.5 | Input Documents to SA5 5GA Rel-20 workshop | S5‑250029 | Chair's Perspective on SA5 Rel-20 5G-Advanced Standardization | SA WG5 Chair | Work Plan | Yes |
No
| available | No | |||
S5‑250168 | SA5_Rel-20_5GA_Topics_Consolidated_List | WG Chair | other | Information | No |
No
| reserved | No | ||||
S5‑250273 | View on SA5 Rel-20 5G-Advanced Priorities | FiberCop, Telecom Italia | discussion | Information | Yes |
No
| available | No | ||||
S5‑250278 | Rel-20 5G Advanced workshop AIML Management | NEC, Intel | discussion | Discussion | Yes |
No
| available | No | ||||
S5‑250310 | Verizon’s view on SA5 Rel-20 5G-Advanced Priorities | Verizon Denmark | discussion | Information | Yes |
No
| available | No | ||||
S5‑250313 | ZTE‘s view on SA5 Rel-20 5G-Advanced Priorities | ZTE Corporation | discussion | Discussion | Yes |
No
| available | No | ||||
S5‑250350 | Huawei view on SA5 Rel-20 5G-Advanced Priorities | Huawei | discussion | Discussion | Yes |
No
| available | No | ||||
S5‑250381 | CATT view on SA5 Rel-20 5G-Advanced Priorities | CATT | other | Discussion | Yes |
No
| available | No | ||||
S5‑250420 | China Telecom’s view on SA5 Rel-20 5G-Advanced Priorities | China Telecom Corporation Ltd. | other | Discussion | Yes |
No
| available | No | ||||
S5‑250432 | China Unicom view on SA5 Rel-20 5G-Advanced Priorities | China Unicom | discussion | Discussion | Yes |
No
| available | No | ||||
S5‑250441 | China Mobile’s view on SA5 Rel-20 5G-Advanced Priorities | China Mobile Com. Corporation | discussion | Discussion | Yes |
No
| available | No | ||||
S5‑250446 | Future study on Semantics-Based Network Management | Samsung R&D Institute India, China Unicom | other | Discussion | Yes |
No
| available | No | ||||
S5‑250447 | NTT DOCOMO view on SA5 Rel-20 5G-Advanced Priorities | NTT DOCOMO INC.. | discussion | Discussion | Yes |
No
| available | No | ||||
S5‑250516 | New SID on Study for Data Management phase 3 | Nokia | SID new | Approval | Yes |
No
| available | No | ||||
S5‑250546 | Asiainfo's view on SA5 Rel-20 5G-Advanced Priorities | AsiaInfo | discussion | Discussion | Yes |
No
| available | No | ||||
S5‑250550 | New WID on 5G Advanced NRM features phase 4 | Nokia, Nokia Shanghai Bell | discussion | Discussion | Yes |
No
| available | No | ||||
S5‑250561 | Orange view on SA5 Rel-20 5G-Advanced Priorities | Orange | other | Yes |
No
| available | No | |||||
S5‑250639 | New SID on Study on Enhanced OAM for management service exposure to external consumers phase 2 | Nokia UK | SID new | Approval | Yes |
No
| available | No | ||||
S5‑250666 | Deutsche Telekom's view on SA5 Rel. 20 5G Advanced Priorities | Deutsche Telekom AG | other | Presentation | No |
No
| reserved | No | ||||
S5‑250799 | SA5 Rel-20 5GA topics | Chair | other | Endorsement | No |
No
| reserved | No | ||||
6 | OAM&P | |||||||||||
6.1 | OAM&P Plenary | S5‑250009 | OAM action list | WG Vice Chair (Nokia) | other | No |
No
| reserved | No | |||
S5‑250010 | OAM Exec Report | WG Vice Chair (Nokia) | report | No |
No
| reserved | No | |||||
S5‑250012 | Collection of useful endorsed documents in OAM | WG Vice Chair (Nokia) | discussion | No |
No
| reserved | No | |||||
S5‑250013 | Collection of external communication documents in OAM | WG Vice Chair (Nokia) | discussion | No |
No
| reserved | No | |||||
S5‑250021 | OAM breakout notes | WG Chair | report | No |
No
| reserved | No | |||||
S5‑250023 | LS to ITU-T SG2 on methodology coordination | SA5 Vice Chair (Ericsson) | LS out | Approval | Yes |
Yes
| revised | No | S5‑250825 | |||
S5‑250825 | LS to ITU-T SG2 on methodology coordination | SA5 Vice Chair (Ericsson) | LS out | Approval | No |
Yes
| approved | No | S5‑250023 | |||
S5‑250113 | Reply LS on ML Model provisioning by OAM to LMF for UE positioning | ZTE Corporation | LS out | Approval | Yes |
Yes
| revised | No | S5‑250826 | |||
S5‑250826 | Reply LS on ML Model provisioning by OAM to LMF for UE positioning | ZTE Corporation | LS out | Approval | No |
No
| reserved | No | S5‑250113 | |||
S5‑250209 | DP on TS 28.554 KPIs related to NetworkSlice and NetworkSliceSubnet KPI Object | Nokia | discussion | Yes |
Yes
| revised | No | S5‑250598 | ||||
S5‑250258 | LS reply on energy saving for split gNB | Ericsson (China) | LS out | Yes |
NoThere is some dependencies with CRs (S5-250028).
| available | No | |||||
S5‑250280 | LS on 5G Trace to support UE level measurement | CT4 | LS in | Information | Yes |
YesThis requires some changes to SA5 specs.
| postponed | No | ||||
S5‑250281 | LS on signalling feasibility of dataset and parameter sharing | RAN1 | LS in | Information | Yes |
Yes
| noted | No | ||||
S5‑250282 | Reply to SA5 LS on Number of UEs in RRC_INACTIVE state with data transmission (SA5#158) | RAN2 | LS in | Information | Yes |
Yes
| replied to | No | ||||
S5‑250283 | Reply LS to SA5 on AIML data collection | RAN2 | LS in | Information | Yes |
Yes
| noted | No | ||||
S5‑250284 | Reply LS to SA2 on AIML data collection | RAN2 | LS in | Information | No |
Yes
| withdrawn | Yes | ||||
S5‑250285 | Reply LS on renewable energy based LBO | RAN3 | LS in | Information | Yes |
Yes
| noted | No | ||||
S5‑250286 | LS on per-UE UE performance metrics | RAN3 | LS in | Information | Yes |
Yes
| replied to | No | ||||
S5‑250829 | LS reply on per-UE UE performance metrics | Samsung | LS out | approval | No |
No
| reserved | No | ||||
S5‑250287 | Reply LS on AIML data collection | RAN3 | LS in | Information | Yes |
Yes
| noted | No | ||||
S5‑250288 | LS on energy saving for split gNB | RAN3 | LS in | Information | Yes |
Yes
| replied to | No | ||||
S5‑250289 | LS on AI/ML UE sided data collection | RAN | LS in | Information | Yes |
Yes
| replied to | No | ||||
S5‑250828 | LS reply to RAN on AI/ML UE sided data collection | Intel | LS out | approval | No |
No
| reserved | No | ||||
S5‑250290 | Reply LS on AIML data collection | SA2 | LS in | Information | Yes |
Yes
| noted | No | ||||
S5‑250291 | LS on ML Model provisioning by OAM to LMF for UE positioning | SA2 | LS in | Information | Yes |
Yes
| replied to | No | ||||
S5‑250292 | LS on reply to LS on OAM requirements to support regenerative payload | SA2 | LS in | Information | Yes |
Yes
| replied to | No | ||||
S5‑250842 | LS reply to LS on OAM requirements to support regenerative payload | Huawei | LS out | approval | No |
No
| reserved | No | ||||
S5‑250294 | LS on energy information collection from OAM to EIF | SA2 | LS in | Information | Yes |
Yes
| replied to | No | ||||
S5‑250297 | LS to ETSI ATTM, ETSI OEU and ITU-T SG5 on carbon emissions related KPIs | ETSI TC ATTM | LS in | Information | Yes |
Yes
| noted | No | ||||
S5‑250301 | LS on information about the initiation of new draft Recommendation ITU-T Y.IoT-IPP “Requirements and framework of intent perception and processing in intelligent operations for IoT” | ITU-T SG20 | LS in | Information | Yes |
Yes
| replied to | No | ||||
S5‑250844 | Reply to: LS on information about the initiation of new draft Recommendation ITU-T Y.IoT-IPP “Requirements and framework of intent perception and processing in intelligent operations for IoT” | Huawei | LS out | approval | No |
No
| reserved | No | ||||
S5‑250302 | LS response to "Reply LS to ZSM Work on AI enablers and intent-driven autonomous networks" | ETSI ISG ZSM | LS in | Information | Yes |
Yes
| replied to | No | ||||
S5‑250845 | Reply to: LS response to "Reply LS to ZSM Work on AI enablers and intent-driven autonomous networks" | Chair | LS out | approval | No |
No
| reserved | No | ||||
S5‑250311 | LS reply to LS on energy information collection from OAM to EIF | Huawei, China Mobile | LS out | Approval | Yes |
Yes
| revised | No | S5‑250843 | |||
S5‑250843 | LS reply to LS on energy information collection from OAM to EIF | Huawei, China Mobile | LS out | Approval | No |
No
| reserved | No | S5‑250311 | |||
S5‑250319 | LS on Vendor Specific Trace Record | Ericsson Canada Inc. | LS out | Agreement | Yes |
No
| available | No | ||||
S5‑250343 | DP on number of UEs in RRC_INACTIVE state with data transmission | China Telecom, Huawei, China Unicom, CATT, Ericsson, ZTE, Intel | discussion | Endorsement | Yes |
Yes
| endorsed | No | ||||
S5‑250348 | Reply to RAN2 LS on Number of UEs in RRC_INACTIVE state with data transmission | China Telecom Corporation Ltd. | LS out | Approval | Yes |
YesThe attachment is missing.
| revised | No | S5‑250827 | |||
S5‑250827 | Reply to RAN2 LS on Number of UEs in RRC_INACTIVE state with data transmission | China Telecom Corporation Ltd. | LS out | Approval | No |
No
| reserved | No | S5‑250348 | |||
S5‑250598 | DP on TS 28.554 KPIs related to NetworkSlice and NetworkSliceSubnet KPI Object | Nokia | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑250846 | S5‑250209 | ||
S5‑250846 | DP on TS 28.554 KPIs related to NetworkSlice and NetworkSliceSubnet KPI Object | Nokia | discussion | Endorsement | No |
No
| reserved | No | S5‑250598 | |||
S5‑250667 | Reply to LS on ML Model provisioning by OAM to LMF for UE positioning | NEC, Intel | LS out | Approval | Yes |
Yes
| merged | No | S5‑250826 | |||
6.2 | New OAM&P Work Item proposals | |||||||||||
6.2.1 | Intelligence and Automation | |||||||||||
6.2.2 | Management Architecture and Mechanisms | S5‑250087 | Revised WID on Subscriber and Equipment Trace and QoE Collection | Ericsson Canada Inc. | WID revised | Agreement | Yes |
No
| available | No | ||
S5‑250210 | DP on TS 28.554 KPIs related to NF Energy Consumption | Nokia | discussion | Yes |
Yes
| revised | No | S5‑250599 | ||||
S5‑250424 | DP on OAM supporting Ambient IoT feature | Huawei, China Mobile, China Unicom, CATT | discussion | Endorsement | Yes |
No
| available | No | ||||
S5‑250425 | Revised WID on 5G Advanced NRM features phase 3 | Huawei, China Mobile, China Unicom, CATT | WID revised | Agreement | Yes |
No
| available | No | ||||
S5‑250517 | Revised WID on Data management phase 2 | Nokia | WID revised | Approval | Yes |
No
| available | No | ||||
S5‑250599 | DP on TS 28.554 KPIs related to NF Energy Consumption | Nokia | discussion | Endorsement | Yes |
Yes
| noted | No | S5‑250210 | |||
6.2.3 | Support of New Services | |||||||||||
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‑250354 | Rel-17 CR TS 28.310 Add missing solution description for 5GC EE | Huawei | CR | Agreement | Yes |
No
| available | No | ||
S5‑250355 | Rel-17 CR TS 28.310 Add missing solution description for 5GC EE | Huawei | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250356 | Rel-19 CR TS 28.310 Add missing solution description for 5GC EE | Huawei | CR | Agreement | Yes |
No
| available | No | ||||
6.3.6 | Intent driven management | |||||||||||
6.3.7 | SON | S5‑250456 | Rel-16 CR TS 28.541 Update stage3 for the allowed value for ueAccProbabilityDist | Huawei | CR | Approval | Yes |
No
| available | No | ||
S5‑250457 | Rel-17 CR TS 28.541 Update stage3 for the allowed value for ueAccProbabilityDist | Huawei | CR | Approval | Yes |
No
| available | No | ||||
S5‑250458 | Rel-18 CR TS 28.541 Update stage3 for the allowed value for ueAccProbabilityDist | Huawei | CR | Approval | Yes |
No
| available | No | ||||
S5‑250459 | Rel-19 CR TS 28.541 Update stage3 for the allowed value for ueAccProbabilityDist | Huawei | CR | Approval | Yes |
No
| available | No | ||||
6.3.8 | QMC | |||||||||||
6.3.9 | Network slicing management | |||||||||||
6.3.10 | MEC management | |||||||||||
6.3.11 | General NRM | S5‑250097 | Rel-18 CR 28.532 Correct path in notifyMOIChanges YANG mapping | Ericsson Hungary Ltd | CR | Approval | Yes |
No
| available | No | ||
S5‑250098 | R17 CR 28.620 Clarify attribute tables | Ericsson Hungary Ltd | CR | Approval | Yes |
No
| available | No | ||||
S5‑250099 | R18 CR 28.620 Clarify attribute tables | Ericsson Hungary Ltd | CR | Approval | Yes |
No
| available | No | ||||
S5‑250100 | R19 CR 28.620 Clarify attribute tables | Ericsson Hungary Ltd | CR | Approval | Yes |
No
| available | No | ||||
S5‑250101 | R17 CR 28.620 Change atribute properties | Ericsson Hungary Ltd | CR | Approval | Yes |
No
| available | No | ||||
S5‑250102 | R18 CR 28.620 Change atribute properties | Ericsson Hungary Ltd | CR | Approval | Yes |
No
| available | No | ||||
S5‑250103 | R19 CR 28.620 Change atribute properties | Ericsson Hungary Ltd | CR | Approval | Yes |
No
| available | No | ||||
S5‑250154 | Rel19 CR TS28.541 correction to inconsistency between stage 2 and stage 3 | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250162 | Rel-17 CR TS 28.541 Correct typos in 5GC NRM fragment | Ericsson España S.A. | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250163 | Rel-18 CR TS 28.541 Correct typos in 5GC NRM fragment | Ericsson España S.A. | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250164 | Rel-19 CR TS 28.541 Correct typos in 5GC NRM fragment | Ericsson España S.A. | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250181 | Rel18 CR TS28.541 correction to inconsistency between stage 2 and stage 3 | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250261 | Rel19 CR TS28.105 correction to data type definitions related to AIMLInferenceName | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250262 | Rel19 CR TS28.622 correction to definitions related to availableRANqoEMetrics | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250263 | Rel19 CR TS28.623 correction to definitions related to availableRANqoEMetrics for YANG and OpenAPI | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250610 | Rel16 CR TS 28.532 Correction of the event time format to follow the standardized date time format & correction of the “notificationType” for the “MoiChange” data type | Nokia UK | CR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑250611 | Rel17 CR TS 28.532 Correction of the event time format to follow the standardized date time format & correction of the “notificationType” for the “MoiChange” data type | Nokia UK | CR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑250612 | Rel18 CR TS 28.532 Correction of the event time format to follow the standardized date time format & correction of the “notificationType” for the “MoiChange” data type | Nokia UK | CR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑250619 | Rel-17 CR 28.536 Clarify the relationship between NetworkSlice and ACCL | Ericsson, Deutsche Telekom | CR | Approval | Yes |
No
| available | No | ||||
S5‑250620 | Rel-18 CR 28.536 Clarify the relationship between NetworkSlice and ACCL | Ericsson, Deutsche Telekom | CR | Approval | Yes |
No
| available | No | ||||
S5‑250621 | Rel-19 CR 28.536 Clarify the relationship between NetworkSlice and ACCL | Ericsson, Deutsche Telekom | CR | Approval | Yes |
No
| available | No | ||||
S5‑250622 | Rel-17 CR 28.536 Correct association between various classes and their datatypes | Ericsson, Deutsche Telekom | CR | Approval | Yes |
No
| available | No | ||||
S5‑250623 | Rel-18 CR 28.536 Correct association between various classes and their datatypes | Ericsson, Deutsche Telekom | CR | Approval | Yes |
No
| available | No | ||||
S5‑250624 | Rel-19 CR 28.536 Correct association between various classes and their datatypes | Ericsson, Deutsche Telekom | CR | Approval | Yes |
No
| available | No | ||||
S5‑250625 | Rel-17 CR 28.541 Correct association between networkslice classes and their profiles | Ericsson, Deutsche Telekom | CR | Approval | Yes |
No
| available | No | ||||
S5‑250626 | Rel-18 CR Correct association between networkslice classes and their profiles | Ericsson, Deutsche Telekom | CR | Approval | Yes |
No
| available | No | ||||
S5‑250627 | Rel-19 CR 28.541 Correct association between networkslice classes and their profiles | Ericsson, Deutsche Telekom | CR | Approval | Yes |
No
| available | No | ||||
S5‑250635 | Discussion paper on 5GS PCC rules | Ericsson, Deutsche Telekom | discussion | Endorsement | Yes |
No
| available | No | ||||
S5‑250644 | Rel16 CR TS 28.532 Correction of the event time format & correction of the “notificationType” for the “MoiChange” data type | Nokia | CR | Approval | Yes |
No
| available | No | ||||
S5‑250645 | Rel17 CR TS 28.532 Correction of the event time format & correction of the “notificationType” for the “MoiChange” data type | Nokia | CR | Approval | Yes |
No
| available | No | ||||
S5‑250646 | Rel18 CR TS 28.532 Correction of the event time format & correction of the “notificationType” for the “MoiChange” data type | Nokia | CR | Approval | Yes |
No
| available | No | ||||
6.3.12 | PM/KPI | S5‑250336 | Rel-16 CR TS28.552 Correct unit and description of some measurements | ZTE Corporation | CR | Approval | Yes |
No
| available | No | ||
S5‑250337 | Rel-17 CR TS28.552 Correct unit and description of some measurements | ZTE Corporation | CR | Approval | Yes |
No
| available | No | ||||
S5‑250338 | Rel-18 CR TS28.552 Correct unit and description of some measurements | ZTE Corporation | CR | Approval | Yes |
No
| available | No | ||||
S5‑250339 | Rel-19 CR TS28.552 Correct unit and description of some measurements | ZTE Corporation | CR | Approval | Yes |
No
| available | No | ||||
6.3.13 | Trace/MDT | S5‑250166 | Rel-16 CR TS 28.622 Correct descriptions for areascope attribute in TraceJob IOC | Ericsson España S.A. | CR | Agreement | Yes |
No
| available | No | ||
S5‑250234 | Rel-17 CR TS 28.622 Correct descriptions for areascope attribute in TraceJob IOC | Ericsson España S.A. | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250235 | Rel-18 CR TS 28.622 Correct descriptions for areascope attribute in TraceJob IOC | Ericsson España S.A. | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250236 | Rel-16 CR 28.622 Correct constraints of Trace-MDT attributes | Ericsson España S.A. | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250237 | Rel-17 CR 28.622 Correct constraints of Trace-MDT attributes | Ericsson España S.A. | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250238 | Rel-18 CR TS 28.622 Correct constraints of Trace-MDT attributes | Ericsson España S.A. | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250239 | Rel-19 CR TS 28.622 Correct constraints of Trace-MDT attributes | Ericsson España S.A. | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250240 | Rel-16 CR TS 28.623 Correct Trace-MDT (YANG) | Ericsson España S.A. | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250241 | Rel-17 CR TS 28.623 Correct Trace-MDT (YANG) | Ericsson España S.A. | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250242 | Rel-18 CR TS 28.623 Correct Trace-MDT (YANG) | Ericsson España S.A. | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250243 | Rel-19 CR TS 28.623 Correct Trace-MDT (YANG) | Ericsson España S.A. | CR | Agreement | Yes |
No
| available | No | ||||
6.3.14 | Other | S5‑250024 | Rel-19 CR 28.541 Editorial corrections | Ericsson | CR | Agreement | Yes |
No
| available | No | ||
S5‑250096 | Rel-17 CR 28.532 Correct path in notifyMOIChanges YANG mapping | Ericsson Hungary Ltd | CR | Approval | Yes |
No
| available | No | ||||
S5‑250582 | Rel18 CR 28.623 Correction of geographical area | Nokia | CR | Approval | Yes |
No
| available | No | ||||
S5‑250583 | Rel19 CR 28.623 Correction of geographical area | Nokia | CR | Approval | Yes |
No
| available | No | ||||
6.4 | Rel-18 Maintenance and Rel-19 small Enhancements | |||||||||||
6.4.1 | Self-Configuration of RAN NEs | |||||||||||
6.4.2 | Management Data Analytics phase 2 | S5‑250195 | Rel-18 CR TS 28.104 Correct the MDAType definition | Huawei | CR | Agreement | Yes |
No
| available | No | ||
S5‑250196 | Rel-19 CR TS 28.104 Correct the MDAType definition | Huawei | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250433 | Rel-19 CR TS 28.104 Fix corrupted descriptive text | Huawei | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250563 | Rel 18 CR TS 28.104 Correct recommendationFilter attr | Ericsson | CR | Approval | Yes |
No
| available | No | ||||
S5‑250564 | Rel 19 CR TS 28.104 Correct recommendationFilter attr | Ericsson | CR | Approval | Yes |
No
| available | No | ||||
6.4.3 | AI/ML management | S5‑250122 | Rel-18 CR TS 28.105 Correction of PlanUML code | ZTE Corporation | CR | Agreement | Yes |
No
| available | No | ||
S5‑250123 | Rel-19 CR TS 28.105 Correction of PlanUML code | ZTE Corporation | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250244 | Rel-18 CR TS 28.105 Fix trainingRequestSource attribute | Ericsson España S.A. | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250460 | Rel-18 CR TS 28.105 correct the components for ML model deployment and AI/ML inference | Huawei | CR | Approval | Yes |
No
| available | No | ||||
S5‑250461 | Rel-19 CR TS 28.105 correct the components for ML model deployment and AI/ML inference | Huawei | CR | Approval | Yes |
No
| available | No | ||||
S5‑250464 | Rel-18 CR TS 28.105 correct the the requirements for ML model training | Huawei | CR | Approval | Yes |
No
| available | No | ||||
S5‑250465 | Rel-19 CR TS 28.105 correct the the requirements for ML model training | Huawei | CR | Approval | Yes |
No
| available | No | ||||
S5‑250566 | Rel 18 CR TS 28.105 Correct MLTrainingFunction definition | Ericsson | CR | Approval | Yes |
No
| available | No | ||||
S5‑250567 | Rel 19 CR TS 28.105 Correct MLTrainingFunction definition | Ericsson | CR | Approval | Yes |
No
| available | No | ||||
S5‑250568 | Rel 18 CR TS 28.105 Various corrections for Clause 6 | Ericsson | CR | Approval | Yes |
No
| available | No | ||||
S5‑250570 | Rel 19 CR TS 28.105 Various corrections for Clause 6 | Ericsson | CR | Approval | Yes |
No
| available | No | ||||
S5‑250572 | Rel 18 CR TS 28.105 Correct isWritable property of requestStatus for MLLoadingRequest and MLUpdateRequest | Ericsson | CR | Approval | Yes |
No
| available | No | ||||
S5‑250574 | Rel 19 CR TS 28.105 Correct isWritable property of requestStatus for MLLoadingRequest and MLUpdateRequest | Ericsson | CR | Approval | Yes |
No
| available | No | ||||
S5‑250591 | Rel-18 CR TS 28.105 Correct MLContext attributes | Ericsson-LG Co., LTD | CR | Approval | Yes |
No
| available | No | ||||
S5‑250594 | Rel-19 CR TS 28.105 Correct MLContext attributes | Ericsson-LG Co., LTD | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250658 | Rel-18 CR TS 28.105 Correction of MLTestingRequest attributes | Ericsson AB. | CR | Agreement | Yes |
Yes
| withdrawn | Yes | ||||
S5‑250660 | Rel-18 CR TS 28.105 Correction of MLTestingRequest attributes | Ericsson AB | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250661 | Rel-19 CR TS 28.105 Correction of MLTestingRequest attributes | Ericsson AB | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250663 | Rel-18 CR TS 28.105 Correction of MLModel attribute properties | Ericsson AB | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250665 | Rel-19 CR TS 28.105 Correction of MLModel attribute properties | Ericsson AB | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250668 | Rel-18 CR TS 28.105 Correct MLTrainingProcess attributes | Ericsson-LG Co., LTD | CR | Approval | Yes |
No
| available | No | ||||
S5‑250669 | Rel-19 CR TS 28.105 Correct MLTrainingProcess attributes | Ericsson-LG Co., LTD | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑250670 | Rel-19 CR TS 28.105 Correct MLTrainingProcess attributes | Ericsson-LG Co., LTD | CR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑250671 | Rel-18 CR TS 28.105 Correct MLTrainingReport attributes | Ericsson-LG Co., LTD | CR | Approval | Yes |
No
| available | No | ||||
S5‑250672 | Rel-19 CR TS 28.105 Correct MLTrainingReport attributes | Ericsson-LG Co., LTD | CR | Approval | Yes |
No
| available | No | ||||
S5‑250673 | Rel-18 CR TS 28.105 Correct MLTrainingRequest attributes | Ericsson-LG Co., LTD | CR | Approval | Yes |
No
| available | No | ||||
S5‑250675 | Rel-19 CR TS 28.105 Correct MLTrainingRequest attributes | Ericsson-LG Co., LTD | CR | Approval | Yes |
No
| available | No | ||||
S5‑250678 | Rel-19 CR TS 28.105 Correct MLTrainingProcess attributes | Ericsson-LG Co., LTD | CR | Approval | Yes |
No
| available | No | ||||
6.4.4 | Intent driven Management Service for mobile network phase 2 | S5‑250200 | Rel-18 CR TS 28.312 Address the CR implmentation issue for infeasibilityReasons in CR252 | Huawei | CR | Agreement | Yes |
No
| available | No | ||
S5‑250201 | Rel-18 CR TS 28.312 Address the CR implmentation issue for infeasibilityReasons in CR252 | Huawei | CR | Agreement | Yes |
No
| available | No | ||||
6.4.5 | Service based management architecture | S5‑250104 | DP Clarify of usage of DnPrefix | Ericsson Hungary Ltd | discussion | Endorsement | Yes |
No
| available | No | ||
S5‑250105 | DP How to use notifyPotentialFaultyAlarmList | Ericsson Hungary Ltd | discussion | Endorsement | Yes |
No
| available | No | ||||
S5‑250110 | Rel-18 CR 28.111 Rapporteur cleanup | Ericsson Hungary Ltd | CR | Approval | Yes |
No
| available | No | ||||
S5‑250111 | Rel-19 CR 28.111 Rapporteur cleanup | Ericsson Hungary Ltd | CR | Approval | Yes |
No
| available | No | ||||
6.4.6 | Network slicing provisioning rules | |||||||||||
6.4.7 | Network slice provisioning enhancement | |||||||||||
6.4.8 | Management of Trace/MDT phase 2 | |||||||||||
6.4.9 | 5G performance measurements and KPIs phase 3 | S5‑250036 | DP Corrections of Subcounter and Filter Format | Ericsson Canada Inc. | discussion | Endorsement | Yes |
No
| available | No | S5‑246341 | |
S5‑250037 | Rel-18 CR TS 28.552 Corrections of subcounters and filters | Ericsson | CR | Agreement | Yes |
No
| available | No | S5‑246342 | |||
S5‑250038 | Rel-19 CR TS 28.552 Corrections of subcounters and filters | Ericsson | CR | Agreement | Yes |
No
| available | No | S5‑246343 | |||
S5‑250039 | Rel-18 CR TS 28.552 Corrections of measurement type | Ericsson | CR | Agreement | Yes |
No
| available | No | S5‑246344 | |||
S5‑250040 | Rel-19 CR TS 28.552 Corrections of measurement type | Ericsson | CR | Agreement | Yes |
No
| available | No | S5‑246345 | |||
S5‑250041 | Rel-18 CR TS 28.622 Corrections of measurement type | Ericsson | CR | Agreement | Yes |
No
| available | No | S5‑246348 | |||
S5‑250042 | Rel-19 CR TS 28.622 Corrections of measurement type | Ericsson | CR | Agreement | Yes |
No
| available | No | S5‑246349 | |||
S5‑250043 | Rel-18 CR TS 28.623 Corrections of measurement type | Ericsson | CR | Agreement | Yes |
No
| available | No | S5‑246350 | |||
S5‑250044 | Rel-19 CR TS 28.623 Corrections of measurement type | Ericsson | CR | Agreement | Yes |
No
| available | No | S5‑246351 | |||
S5‑250045 | Rel-18 CR TS 28.552 Corrections on Packet Delay measurements | Ericsson | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250046 | Rel-19 CR TS 28.552 Corrections on Packet Delay measurements | Ericsson | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250047 | Rel-18 CR TS 28.552 Corrections on Radio Resource Utlization measurements | Ericsson | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250048 | Rel-19 CR TS 28.552 Corrections on Radio Resource Utlization measurements | Ericsson | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250049 | Rel-18 CR TS 28.552 Corrections on UE throughput measurements | Ericsson | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250050 | Rel-19 CR TS 28.552 Corrections on UE throughput measurements | Ericsson | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250051 | Rel-18 CR TS 28.552 Corrections on RRC Connection Number measurements | Ericsson | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250052 | Rel-19 CR TS 28.552 Corrections on RRC Connection Number measurements | Ericsson | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250255 | Rel-19 CR TS 28.552 Distribution of UE throughput | Ericsson | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250320 | Rel-18 CR TS 28.552 Distribution of UE throughput | Ericsson | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250332 | Rel-18 CR TS28.558 update descriptions of some measurements and cleanup | ZTE Corporation | CR | Approval | Yes |
No
| available | No | ||||
S5‑250333 | Rel-19 CR TS28.558 update descriptions of some measurements and cleanup | ZTE Corporation | CR | Approval | Yes |
No
| available | No | ||||
S5‑250553 | Rel-18 CR 28.532 Correct definition of notifyFileReady | Ericsson Inc. | CR | Approval | Yes |
No
| available | No | ||||
S5‑250555 | Rel-18 CR 28.622 Clarify usage of notifyFileReady for PM | Ericsson Inc. | CR | Approval | Yes |
No
| available | No | ||||
S5‑250556 | Rel-19 CR 28.622 Clarify usage of notifyFileReady for PM | Ericsson Inc. | CR | Approval | Yes |
No
| available | No | ||||
S5‑250558 | Rel-18 CR 28.623 Clarify usage of notifyFileReady for PM (yang) | Ericsson Inc. | CR | Approval | Yes |
No
| available | No | ||||
S5‑250559 | Rel-19 CR 28.623 Clarify usage of notifyFileReady for PM (yang) | Ericsson Inc. | CR | Approval | Yes |
No
| available | No | ||||
S5‑250562 | Rel-19 CR 28.532 Enhance notifyFilePreparationError definition | Ericsson Inc. | CR | Approval | Yes |
No
| available | No | ||||
6.4.10 | Enhancement of QoE Measurement Collection | |||||||||||
6.4.11 | Additional NRM features phase 2 | S5‑250114 | Rel-18 CR TS 28.541 Clarify the relation between servedNfInfo and NfInfo | ZTE Corporation, Orange, Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
No
| available | No | ||
S5‑250115 | Rel-19 CR TS 28.541 Clarify the relation between servedNfInfo and NfInfo | ZTE Corporation, Orange, Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250248 | Rel-18 CR TS 28.622 Fix errors on selected attributes | Ericsson España S.A. | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250249 | Rel-19 CR TS 28.622 Fix errors on selected attributes | Ericsson España S.A. | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250250 | Rel-19 CR TS 28.623 Fix errors on selected attributes (YAML) | Ericsson España S.A. | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250251 | Rel-18 CR TS 28.622 Fix implementation errors of past CRs | Ericsson España S.A. | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250252 | Rel-19 CR TS 28.622 Fix implementation errors of past CRs | Ericsson España S.A. | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250368 | Rel-18 CR 28.541 correction on NwdafInfo | Huawei | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250369 | Rel-19 CR 28.541 correction on NwdafInfo | Huawei | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250462 | Rel-18 CR TS 28.541 corrections for 5QISetRef | Huawei | CR | Approval | Yes |
No
| available | No | ||||
S5‑250463 | Rel-19 CR TS 28.541 corrections for 5QISetRef | Huawei | CR | Approval | Yes |
No
| available | No | ||||
6.4.12 | Management Aspects related to NWDAF | |||||||||||
6.4.13 | Enhanced Edge Computing Management | S5‑250370 | Rel-18 CR 28.538 correction on PO and LO | Huawei | CR | Agreement | Yes |
No
| available | No | ||
S5‑250371 | Rel-19 CR 28.538 correction on PO and LO | Huawei | CR | Agreement | Yes |
No
| available | No | ||||
6.4.14 | Management Aspect of 5GLAN | |||||||||||
6.4.15 | Management Aspects of NTN | S5‑250193 | Rel-18 CR TS 28.541 Correct stage3 definition for NTNFunction | Huawei | CR | Agreement | Yes |
No
| available | No | ||
S5‑250194 | Rel-19 CR TS 28.541 Correct stage3 definition for NTNFunction | Huawei | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250334 | Rel-18 CR TS28.541 add missing satelliteCoverageInfoList for stage 3 OpenAPI | ZTE Corporation | CR | Approval | Yes |
No
| available | No | ||||
S5‑250335 | Rel-19 CR TS28.541 add missing satelliteCoverageInfoList for stage 3 OpenAPI | ZTE Corporation | CR | Approval | Yes |
No
| available | No | ||||
S5‑250383 | Rel-19 CR TR 28.874 Add missing reference for secure connection use case | CATT | CR | Approval | Yes |
No
| available | No | ||||
S5‑250384 | Rel-19 CR TR 28.874 Correction on the evaluation description of NTN secure connection | CATT | CR | Approval | Yes |
No
| available | 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 | S5‑250421 | Rel-18 CR TS 28.540 Remove requirements of MSAC | Huawei | CR | Agreement | Yes |
No
| available | No | ||
S5‑250560 | Rel-18 CR TS 28.319 Move MSAC requirements from TS 28.540 | Ericsson Inc., Huawei | CR | Approval | Yes |
No
| available | No | ||||
6.4.22 | Enhancements of EE for 5G Phase 2 | |||||||||||
6.4.23 | Management of non-public networks phase 2 | |||||||||||
6.4.24 | Network and Service Operations for Energy Utilities | |||||||||||
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‑250032 | Rel-18 CR TS 32.404 Corrections on measurement name size | Ericsson | CR | Agreement | Yes |
No
| available | No | ||
S5‑250213 | Rel-18 CR 28.532 Fix description of input parameteres of changeMOIs | Nokia | CR | Yes |
Yes
| revised | No | S5‑250603 | ||||
S5‑250274 | Rel-18 CR TS 28.541 Fix error in Transport view of AMF NRM diagram | Huawei | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250275 | Rel-19 CR TS 28.541 Fix error in Transport view of AMF NRM diagram | Huawei | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250603 | Rel-18 CR 28.532 Fix description of input parameteres of changeMOIs | Nokia | CR | Approval | Yes |
No
| available | No | S5‑250213 | |||
6.4.27 | OAM Rel-19 small enhancements | S5‑250076 | Rel-19 CR 28560-j00 Corrections according to Edit Helpdesk | Ericsson | CR | Yes |
Yes
| revised | No | S5‑250078 | ||
S5‑250078 | Rel-19 CR 28560-j00 Corrections according to Edit Helpdesk | Ericsson | CR | Yes |
No
| available | No | S5‑250076 | ||||
S5‑250084 | Rel-19 CR 28.541 YANG Corrections SA5-159 | Ericsson Hungary Ltd | CR | Approval | Yes |
No
| available | No | ||||
S5‑250085 | Rel-19 CR 28.623 YANG Corrections SA5-159 | Ericsson Hungary Ltd | CR | Approval | Yes |
No
| available | No | ||||
S5‑250155 | Rel19 CR TS28.532 OpenAPI correction related to format of URI query parameters | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250156 | Rel19 CR TS28.550 OpenAPI correction related to format of URI query parameters | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250191 | Rel-19 CR TS 28.550 Update Annex D to remove undefined updateStreamInfo operation | Huawei | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250192 | Rel-19 CR TS 28.537 Change MnS provider to MnS producer | Huawei | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250197 | Rel-19 CR TS 28.111 Correct Enum value for notificationType to align with stage 2 definition | Huawei | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250198 | Rel-19 CR TS 28.532 Correct Enum value for notificationType to align with stage 2 definition | Huawei | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250199 | Rel-19 CR TS 28.622 Correct attributes definition for HeartbeatControl | Huawei | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250211 | Rel-19 CR 28.104 Enhance stage 3 OpenAPI for isUnique property | Nokia | CR | Yes |
Yes
| revised | No | S5‑250600, S5‑250601 | ||||
S5‑250212 | Rel-19 CR 28.536 Enhance stage 3 OpenAPI for isUnique property | Nokia | CR | Yes |
Yes
| revised | No | S5‑250602 | ||||
S5‑250247 | Rel-19 CR TR 28.879 Fix inconsistencies | Ericsson España S.A. | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250256 | Rel-18 CR 28.622 Small corrections | Ericsson Hungary Ltd | CR | Approval | Yes |
No
| available | No | ||||
S5‑250257 | Rel-18 CR 28.623 YANG Corrections SA5-159 | Ericsson Hungary Ltd | CR | Approval | Yes |
No
| available | No | ||||
S5‑250305 | Rel-19 CR TS 28.620 Align IOC definitions with TS 32.160 template | Huawei | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250307 | Rel-19 CR TS 28.620 Update TMF and ITU-T references | Huawei | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250309 | Rel-19 CR 28.111 YANG Corrections SA5-159 | Ericsson Hungary Ltd | CR | Approval | Yes |
No
| available | No | ||||
S5‑250324 | Rel-19 CR 32.160 Add missing vendor extension guideline | Ericsson Hungary Ltd | CR | Approval | Yes |
No
| available | No | ||||
S5‑250330 | Rel-19 CR 32.156 Deprecate isNullable TRUE | Ericsson Hungary Ltd | CR | Approval | Yes |
No
| available | No | ||||
S5‑250422 | Rel-19 CR TS 28.111 Add ThresholdInfo dataType and related definition | Huawei | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250423 | Rel-19 CR TS 28.111 Add ThresholdInfo dataType and related definition | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑250677 | |||
S5‑250544 | DP PM for Inter-CU LTM and conditional LTM | Ericsson India Private Limited | discussion | Endorsement | Yes |
No
| available | No | ||||
S5‑250545 | Rel-19 CR 28.313 Use case and requirements for Inter-CU LTM and conditional LTM | Ericsson | CR | Approval | Yes |
No
| available | No | ||||
S5‑250548 | DP Modify YANG mapping of Subnetwork | Ericsson Hungary Ltd | discussion | Endorsement | Yes |
No
| available | No | ||||
S5‑250565 | Rel 19 CR TS 28.104 Add Priority Attribute | Ericsson | CR | Approval | Yes |
No
| available | No | ||||
S5‑250576 | Rel 19 CR TS 28.537 Remove editors notes | Ericsson | CR | Approval | Yes |
No
| available | No | ||||
S5‑250579 | Rel-19 CR 32.401 Introduce missing definition of terms “Key Performance Indicator (KPI)” and “performance metrics” | Nokia | CR | Approval | Yes |
No
| available | No | ||||
S5‑250580 | Rel-19 CR 28.552 Introduce missing definition of term “Key Performance Indicator (KPI)” | Nokia | CR | Approval | Yes |
No
| available | No | ||||
S5‑250581 | Rel-19 CR 28.622 Introduce missing definition of terms “Key Performance Indicator (KPI)” and “performance metric” | Nokia | CR | Approval | Yes |
No
| available | No | ||||
S5‑250584 | Rel 19 TS 28.538 Correct attributes | Ericsson | CR | Approval | Yes |
No
| available | No | ||||
S5‑250600 | Rel-19 CR 28.104 Enhance stage 3 OpenAPI for isUnique property | Nokia | CR | Approval | Yes |
No
| available | No | S5‑250211 | |||
S5‑250601 | Rel-19 CR 28.104 Enhance stage 3 OpenAPI for isUnique property | Nokia | CR | Approval | Yes |
No
| available | No | S5‑250211 | |||
S5‑250602 | Rel-19 CR 28.536 Enhance stage 3 OpenAPI for isUnique property | Nokia | CR | Approval | Yes |
No
| available | No | S5‑250212 | |||
S5‑250628 | Rel-19 CR TS 32.160 Clarify use of dataType in UML diagrams | Ericsson, Deutsche Telekom | CR | Approval | Yes |
No
| available | No | ||||
S5‑250629 | Rel-19 CR TS 28.541 Correct references | Ericsson | CR | Approval | Yes |
No
| available | No | ||||
S5‑250630 | Rel-18 CR TS 28.312 Add attribute names on association lines | Ericsson, Deutsche Telekom | CR | Approval | Yes |
No
| available | No | ||||
S5‑250631 | Rel-19 CR TS 28.312 Add attribute names on association lines | Ericsson, Deutsche Telekom | CR | Approval | Yes |
No
| available | No | ||||
S5‑250632 | Rel-18 CR TS 28.708 Update references to imported information entities for CN | Ericsson, Deutsche Telekom | CR | Approval | Yes |
No
| available | No | ||||
S5‑250633 | Rel-18 CR TS 28.541 Add transport view of MMEFunction NRM | Ericsson | CR | Approval | Yes |
No
| available | No | ||||
S5‑250634 | Rel-19 CR TS 28.541 Add transport view of MMEFunction NRM | Ericsson, Deutsche Telekom | CR | Approval | Yes |
No
| available | No | ||||
S5‑250677 | Rel-19 CR TS 28.111 Add a restriction in notifyChangedAlarmGeneral | Huawei | CR | Agreement | Yes |
No
| available | No | S5‑250423 | |||
6.19 | OAM&P Rel-19 Study and Work Items | |||||||||||
6.19.1 | Study on AI/ML management - phase 2 | |||||||||||
6.19.1.1 | AI/ML management phase 2 | S5‑250079 | CR TS 28.105 ML-Knowledge-based Transfer Learning | Nokia | CR | Approval | Yes |
No
| available | No | ||
S5‑250080 | CR TS 28.105 Enhance AIML inference emulation | Nokia | CR | Approval | Yes |
No
| available | No | ||||
S5‑250081 | CR TS 28.105 AIML inference emulation environment selection | Nokia | CR | Approval | Yes |
No
| available | No | ||||
S5‑250082 | CR TS 28.105 Coordination AIML inference capabilities | Nokia | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑250173 | Rel-19 CR TS 28.105 Enhancement on AIMLInferenceFunction NRM | ZTE Corporation, Nokia | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250174 | Rel-19 CR TS 28.105 Clarify the relation between ML model delivery in RAN and ML model loading in SA5 | ZTE Corporation | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250175 | Input to DraftCR Rel-19 TS 28.105 Add New Use Case and Requirements of Sustainable AIML for AIML Inference | ZTE Corporation | draftCR | Agreement | Yes |
No
| available | No | ||||
S5‑250176 | Input to DraftCR Rel-19 TS 28.105 Add New Use Case and Requirements of Sustainable AIML for ML training | ZTE Corporation | draftCR | Agreement | Yes |
No
| available | No | ||||
S5‑250177 | Input to DraftCR Rel-19 TS 28.105 Add New Use Case and Requirements of Management of Federated Learning | ZTE Corporation | draftCR | Agreement | Yes |
Yes
| merged | No | S5‑250803 | |||
S5‑250178 | Input to DraftCR Rel-19 TS 28.105 Add Solution of Management of Federated Learning | ZTE Corporation | draftCR | Agreement | Yes |
No
| available | No | ||||
S5‑250179 | Input to DraftCR Rel-19 TS 28.105 Add New Use Case and Requirements of Management of Reinforcement Learning | ZTE Corporation | draftCR | Agreement | Yes |
Yes
| merged | No | S5‑250805 | |||
S5‑250180 | Input to DraftCR Rel-19 TS 28.105 Add Solution of Management of Reinforcement Learning | ZTE Corporation | draftCR | Agreement | Yes |
Yes
| revised | No | S5‑250806 | |||
S5‑250806 | Input to DraftCR Rel-19 TS 28.105 Add Solution of Management of Reinforcement Learning | ZTE Corporation | draftCR | Agreement | No |
No
| reserved | No | S5‑250180 | |||
S5‑250188 | Input to DraftCR Rel19 TS28.105 New use case on Management of Federated Learning | China Mobile | draftCR | Agreement | Yes |
Yes
| merged | No | S5‑250803 | |||
S5‑250189 | Input to DraftCR Rel19 TS28.105 New use case on ML inference emulation environment selection | China Mobile | draftCR | Agreement | Yes |
No
| available | No | ||||
S5‑250190 | Input to DraftCR Rel19 TS28.105 Training Data Effectiveness clarification | China Mobile, Nokia, Nokia Shanghai Bell, Ericsson | draftCR | Agreement | Yes |
No
| available | No | ||||
S5‑250266 | Rel-19 CR TS 28.105 Add Pre-training Usecase | Ericsson-LG Co., LTD | CR | Approval | Yes |
Yes
| revised | No | S5‑250801 | |||
S5‑250801 | Rel-19 CR TS 28.105 Add Pre-training Usecase | Ericsson-LG Co., LTD | CR | Approval | No |
No
| reserved | No | S5‑250266 | |||
S5‑250267 | Rel-19 CR TS 28.105 Add Pre-training Solution | Ericsson-LG Co., LTD | CR | Approval | Yes |
Yes
| revised | No | S5‑250802 | |||
S5‑250802 | Rel-19 CR TS 28.105 Add Pre-training Solution | Ericsson-LG Co., LTD | CR | Approval | No |
No
| reserved | No | S5‑250267 | |||
S5‑250303 | Input to draft CR TS 28.105 add use cases and requirements for ML pre-training | NEC, Intel | draftCR | Agreement | Yes |
Yes
| merged | No | S5‑250801 | |||
S5‑250304 | Input to draft CR TS 28.105 add use cases and requirements for ML fine-tuning | NEC, Intel | draftCR | Agreement | Yes |
Yes
| merged | No | S5‑250801 | |||
S5‑250306 | Input to draft CR TS 28.105 add NRM for ML pre-training and fine-tuning | NEC, Intel | draftCR | Agreement | Yes |
Yes
| merged | No | S5‑250802 | |||
S5‑250308 | Work plan & guidelines AIML Management – Phase 2 | NEC, Intel | Work Plan | Information | Yes |
Yes
| revised | No | S5‑250800 | |||
S5‑250800 | Work plan & guidelines AIML Management – Phase 2 | NEC, Intel | Work Plan | Information | No |
No
| reserved | No | S5‑250308 | |||
S5‑250321 | Input to draftCR TS 28.105 Add use cases and requirements on LCM for Federated Learning | Intel, NEC | draftCR | Approval | Yes |
Yes
| merged | No | S5‑250803 | |||
S5‑250322 | Input to draftCR TS 28.105 Add NRMs on LCM for Federated Learning | Intel, NEC | draftCR | Approval | Yes |
Yes
| revised | No | S5‑250804 | |||
S5‑250804 | Input to draftCR TS 28.105 Add NRMs on LCM for Federated Learning | Intel, NEC | draftCR | Approval | No |
No
| reserved | No | S5‑250322 | |||
S5‑250323 | Input to draftCR TS 28.105 Add use cases and requirements on LCM for Reinforcement Learning | Intel, NEC | draftCR | Approval | Yes |
Yes
| revised | No | S5‑250805 | |||
S5‑250805 | Input to draftCR TS 28.105 Add use cases and requirements on LCM for Reinforcement Learning | Intel, NEC | draftCR | Approval | No |
No
| reserved | No | S5‑250323 | |||
S5‑250382 | Rel-19 CR TS 28.105 Add Usecase and Requirements for ML model distributed training | CATT | CR | Approval | Yes |
Yes
| merged | No | S5‑250809 | |||
S5‑250438 | Input to DraftCR 28.105 add solution to support ML incremental pre-training and ML fine-tuning | China Mobile, ZTE | draftCR | Agreement | Yes |
Yes
| merged | No | S5‑250802 | |||
S5‑250440 | Input to DraftCR 28.105 Add new use case and requirements of ML Incremental Pre-training and ML Fine-tuning | China Mobile, ZTE | draftCR | Agreement | Yes |
Yes
| merged | No | S5‑250801 | |||
S5‑250443 | Input to DraftCR 28.105 Add new symbols and abbreviations | China Mobile, ZTE | draftCR | Agreement | Yes |
No
| available | No | ||||
S5‑250452 | Rel-19 CR 28.105 Distributed Learning UC and Requirements | Samsung R&D Institute India | CR | Agreement | Yes |
Yes
| merged | No | S5‑250809 | |||
S5‑250454 | Rel-19 CR 28.105 Reinforcement Learning UC and Requirements | Samsung R&D Institute India | CR | Agreement | Yes |
Yes
| revised | No | S5‑250807 | |||
S5‑250807 | Rel-19 CR 28.105 Reinforcement Learning UC and Requirements | Samsung R&D Institute India | CR | Agreement | No |
No
| reserved | No | S5‑250454 | |||
S5‑250455 | Rel-19 CR 28.105 CR Reinforcement Learning UC and Requirements | Samsung R&D Institute India | CR | Agreement | Yes |
Yes
| merged | No | S5‑250805 | |||
S5‑250466 | Rel-19 CR TS 28.105 add overview of management of AI/ML capabilities for RAN 5GC and MDA | Huawei | CR | Approval | Yes |
No
| available | No | ||||
S5‑250467 | Rel-19 CR TS 28.105 enhance OpenAPI specification description | Huawei | CR | Approval | Yes |
No
| available | No | ||||
S5‑250468 | Rel-19 CR TS 28.105 Add use case, requirements and solutions of training conflict management for reinforcement learning | Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑250808 | |||
S5‑250808 | Rel-19 CR TS 28.105 Add use case, requirements and solutions of training conflict management for reinforcement learning | Huawei | CR | Approval | No |
No
| reserved | No | S5‑250468 | |||
S5‑250469 | Rel-19 CR TS 28.105 Add use case, requirements and solutions for exploration in reinforcement learning | Huawei | CR | Approval | Yes |
YesMerged into S5-250805 for UC and requirements.
| merged | No | S5‑250805 | |||
S5‑250470 | Rel-19 CR TS 28.105 update the requirement and solution to enhance the ML model loading use case | Huawei | CR | Approval | Yes |
No
| available | No | ||||
S5‑250471 | Discussion on the transfer of data over UP for option 3 | Huawei | discussion | Endorsement | Yes |
No
| available | No | ||||
S5‑250586 | Rel-19 CR TS28.105 Add Management of Federated Learning Usecase | Ericsson-LG Co., LTD | CR | Approval | Yes |
Yes
| merged | No | S5‑250803 | |||
S5‑250587 | Rel-19 CR TS 28.105 Add management of Distributed Training use case | Ericsson-LG Co., LTD | CR | Approval | Yes |
Yes
| revised | No | S5‑250809 | |||
S5‑250809 | Rel-19 CR TS 28.105 Add management of Distributed Training use case | Ericsson-LG Co., LTD | CR | Approval | No |
No
| reserved | No | S5‑250587 | |||
S5‑250590 | Rel-19 CR TS 28.105 Add Fine-Tuning Usecase | Ericsson-LG Co., LTD | CR | Approval | Yes |
Yes
| merged | No | S5‑250801 | |||
S5‑250640 | Input to draftCR Rel-19 TS 28.105 Use case on model confidence requirement | Nokia | draftCR | Approval | Yes |
No
| available | No | ||||
S5‑250641 | Input to draftCR Rel-19 TS 28.105 Solution on model confidence requirement | Nokia | draftCR | Approval | Yes |
No
| available | No | ||||
S5‑250642 | Input to draftCR Rel-19 TS 28.105 Use case on training data statistics | Nokia | draftCR | Approval | Yes |
No
| available | No | ||||
S5‑250643 | Input to draftCR Rel-19 TS 28.105 Solution on training data statistics | Nokia | draftCR | Approval | Yes |
No
| available | No | ||||
S5‑250648 | Rel-19 CR TS 28.105 Add authentication use case | Ericsson AB | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250649 | Rel-19 CR TS 28.105 Use Case and Requirements for Management of Federated Learning | Samsung Electronics France SA | CR | Approval | Yes |
Yes
| merged | No | S5‑250803 | |||
S5‑250650 | Input to draftCR Rel-19 TS 28.105 Use case on reinforcement learning | Nokia | draftCR | Approval | Yes |
Yes
| merged | No | S5‑250805 | |||
S5‑250651 | Rel-19 CR TS 28.105 Use Case and Requirements for ML model training for multiple contexts | Samsung Electronics France SA | CR | Approval | Yes |
No
| available | No | ||||
S5‑250653 | Input to draftCR Rel-19 TS 28.105 Solution on reinforcement learning | Nokia | draftCR | Approval | Yes |
Yes
| merged | No | S5‑250806 | |||
S5‑250655 | Rel-19 CR TS 28.105 Add use case for Management of Reinforcement Learning | Ericsson AB | CR | Agreement | Yes |
Yes
| merged | No | S5‑250805 | |||
S5‑250657 | Input to draftCR Rel-19 TS 28.105 Use case on sustainable AIML training | Nokia | draftCR | Approval | Yes |
No
| available | No | ||||
S5‑250659 | Input to draftCR Rel-19 TS 28.105 ML model training for multiple contexts | Nokia | draftCR | Approval | Yes |
No
| available | No | ||||
S5‑250662 | Input to draftCR Rel-19 TS 28.105 Use case on federated learning | Nokia | draftCR | Approval | Yes |
Yes
| revised | No | S5‑250803 | |||
S5‑250803 | Input to draftCR Rel-19 TS 28.105 Use case on federated learning | Nokia | draftCR | Approval | No |
No
| reserved | No | S5‑250662 | |||
S5‑250664 | Input to draftCR Rel-19 TS 28.105 Solution on sustainable AIML training | Nokia | draftCR | Approval | Yes |
No
| available | No | ||||
S5‑250780 | DraftCR Rel-19 TS 28.105 | Intel Intel Corporation (UK) Ltd | draftCR | Approval | No |
Yes
| email approval | No | ||||
6.19.2 | Study on Management Data Analytics (MDA) – Phase 3 | |||||||||||
6.19.2.1 | Management Data Analytics phase 3 | S5‑250025 | Add the use case and requirements for edge application deployment location analysis | AsiaInfo | CR | Agreement | Yes |
YesAuthor was not present at this meeting.
| not pursued | No | ||
S5‑250026 | Add the use case and requirements for edge computing performance analysis | AsiaInfo | CR | Agreement | Yes |
YesAuthor was not present at this meeting.
| not pursued | No | ||||
S5‑250027 | Add the use case and requirements for network congestion analytics based on UE throughput analysis | AsiaInfo | CR | Agreement | Yes |
YesAuthor was not present at this meeting.
| not pursued | No | ||||
S5‑250160 | Rel19 CR TS28.104 New use case and solution on management data correlation analytics | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑250161 | Rel19 CR TS28.104 add use case and requirement on management data correlation analytics for threshold assessment and adjustment | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑250811 | |||
S5‑250811 | Rel19 CR TS28.104 add use case and requirement on management data correlation analytics for threshold assessment and adjustment | Nokia, Nokia Shanghai Bell, Orange | CR | Agreement | No |
No
| reserved | No | S5‑250161 | |||
S5‑250264 | Rel19 CR TS28.104 add use case and requirement on correlation analytics for NF Scaling and dimensioning | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑250812 | |||
S5‑250812 | Rel19 CR TS28.104 add use case and requirement on correlation analytics for NF Scaling and dimensioning | Nokia, Nokia Shanghai Bell | CR | Agreement | No |
No
| reserved | No | S5‑250264 | |||
S5‑250265 | Rel19 CR TS28.104 add use case and requirement for predicted failures | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑250813 | |||
S5‑250813 | Rel19 CR TS28.104 add use case and requirement for predicted failures | Nokia, Nokia Shanghai Bell | CR | Agreement | No |
No
| reserved | No | S5‑250265 | |||
S5‑250373 | Rel-19 CR 28.104 adding threshold related requirements for Fault management | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑250374 | Rel-19 CR 28.104 adding threshold information in the MDARequest | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑250817 | |||
S5‑250817 | Rel-19 CR 28.104 adding threshold information in the MDARequest | Huawei | CR | Agreement | No |
No
| reserved | No | S5‑250374 | |||
S5‑250434 | Rel-19 CR TS 28.104 Improvements to failure prediction | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑250818 | |||
S5‑250818 | Rel-19 CR TS 28.104 Improvements to failure prediction | Huawei | CR | Agreement | No |
No
| reserved | No | S5‑250434 | |||
S5‑250448 | Rel-19 CR TS 28.104 Update MDA capability for control plane congestion analysis | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑250449 | Rel-19 CR TS 28.104 Update solution for control plane congestion analysis | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑250819 | |||
S5‑250819 | Rel-19 CR TS 28.104 Update solution for control plane congestion analysis | Huawei | CR | Agreement | No |
No
| reserved | No | S5‑250449 | |||
S5‑250472 | Rel-19 CR TS 28.104 add use case and requirements for RAN UE throughput analysis | Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑250820 | |||
S5‑250820 | Rel-19 CR TS 28.104 add use case and requirements for RAN UE throughput analysis | Huawei | CR | Approval | No |
No
| reserved | No | S5‑250472 | |||
S5‑250473 | Rel-19 CR TS 28.104 add solutions for RAN UE throughput analysis | Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑250821 | |||
S5‑250821 | Rel-19 CR TS 28.104 add solutions for RAN UE throughput analysis | Huawei | CR | Approval | No |
No
| reserved | No | S5‑250473 | |||
S5‑250474 | Rel-19 CR TS 28.104 add stage3 solution for mobility performance analysis | Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑250823 | |||
S5‑250823 | Rel-19 CR TS 28.104 add stage3 solution for mobility performance analysis | Huawei | CR | Approval | No |
No
| reserved | No | S5‑250474 | |||
S5‑250475 | Discussion on the add use case specific stage3 for MDA report | Huawei | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑250822 | |||
S5‑250822 | Discussion on the add use case specific stage3 for MDA report | Huawei | discussion | Endorsement | No |
No
| reserved | No | S5‑250475 | |||
S5‑250476 | Rel-19 CR TS 28.104 Add stage 3 definition for MDA Management | Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑250824 | |||
S5‑250824 | Rel-19 CR TS 28.104 Add stage 3 definition for MDA Management | Huawei | CR | Approval | No |
No
| reserved | No | S5‑250476 | |||
S5‑250491 | Rel-19 CR 28.104 UC and Requirements for Software Upgrade Validation | Samsung R&D Institute India | CR | Agreement | Yes |
Yes
| revised | No | S5‑250814 | |||
S5‑250814 | Rel-19 CR 28.104 UC and Requirements for Software Upgrade Validation | Samsung R&D Institute India | CR | Agreement | No |
No
| reserved | No | S5‑250491 | |||
S5‑250512 | Rel-19 CR TS 28.104 New use case and solution on traffic steering analytics | Nokia | CR | Approval | Yes |
YesEmpty Tdoc
| revised | No | S5‑250810 | |||
S5‑250810 | Rel-19 CR TS 28.104 New use case and solution on traffic steering analytics | Nokia | CR | Approval | No |
No
| reserved | No | S5‑250512 | |||
S5‑250513 | Rel-19 CR TS 28.104 Enhancing the failure prediction use case | Nokia | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑250514 | Rel-19 CR TS 28.104 New use case on Multi Domain Resource Optimization | Nokia | CR | Approval | Yes |
Yes
| revised | No | S5‑250815 | |||
S5‑250815 | Rel-19 CR TS 28.104 New use case on Multi Domain Resource Optimization | Nokia, Orange | CR | Approval | No |
No
| reserved | No | S5‑250514 | |||
S5‑250515 | Rel-19 CR TS 28.104 New use case on Handover and service data correlation analytics | Nokia | CR | Approval | Yes |
Yes
| revised | No | S5‑250816 | |||
S5‑250816 | Rel-19 CR TS 28.104 New use case on Handover and service data correlation analytics | Nokia | CR | Approval | No |
No
| reserved | No | S5‑250515 | |||
6.19.3 | Study on intent driven management services for mobile network phase 3 | |||||||||||
6.19.3.1 | Intent driven management services for mobile network phase 3 | S5‑250053 | Rel-19 pCR TS28.312 Negotiation on intent fulfillment | Nokia | pCR | Approval | Yes |
Yes
| noted | No | ||
S5‑250830 | Rel-19 CR TS28.312 Negotiation on intent fulfillment | Nokia | CR | Approval | No |
No
| reserved | No | S5‑250053 | |||
S5‑250054 | Rel-19 pCR TS28.312 extend Intent capability exposure | Nokia | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑250831 | Rel-19 CR TS28.312 extend Intent capability exposure | Nokia | CR | Approval | No |
No
| reserved | No | ||||
S5‑250119 | Rel-19 CR TS 28.312 Add New Use Case, Requirements, and Solution of Intent Degradation based on Expectation Preference | ZTE Corporation, Nokia, Deutsche Telekom | CR | Agreement | No |
Yes
| withdrawn | Yes | S5‑247180 | |||
S5‑250120 | Rel-19 CR TS 28.312 Update the Mapping of IntentReport model | ZTE Corporation | CR | Agreement | Yes |
Yes
| withdrawn | Yes | ||||
S5‑250121 | Rel-19 CR TS 28.312 Update the Relationship UML Diagram for Intent | ZTE Corporation | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250124 | Rel-19 CR TS 28.312 Enhance the use case and solution to support the scenario of delivering a radio service in a scheduled time | Huawei, Deutsche Telekom | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑250125 | Rel-19 CR TS 28.312 Enhance the use case and solution to support radio network traffic assurance for scheduled events scenario | Huawei, Deutsche Telekom | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑250126 | Rel-19 CR TS 28.312 Add New Use Case, Requirements, and Solution of Intent Degradation based on Expectation Preference | ZTE Corporation, Nokia, Deutsche Telekom | CR | Agreement | Yes |
Yes
| withdrawn | Yes | ||||
S5‑250127 | Rel-19 CR TS 28.312 Update the Mapping of IntentReport model | ZTE Corporation | CR | Agreement | Yes |
Yes
| revised | No | S5‑250839 | |||
S5‑250839 | Rel-19 CR TS 28.312 Update the Mapping of IntentReport model | ZTE Corporation | CR | Agreement | No |
No
| reserved | No | S5‑250127 | |||
S5‑250128 | Rel-19 CR TS 28.312 Enhance the use case and solution to support RAN energy saving scenario | Huawei, Deutsche Telekom | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑250129 | Rel-19 CR TS 28.312 Add concept for intent negotiations | Huawei, Deutsche Telekom | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑250130 | Rel-19 CR TS 28.312 Update use case, requirements and solution for intent feasibility check | Huawei, Deutsche Telekom | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑250131 | Rel-19 CR TS 28.312 Add use case and requirements for intent exploration | Huawei, Deutsche Telekom, Nokia, ZTE | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑250132 | Rel-19 CR TS 28.312 Enhance the intent report use case, reqs and solution to support implicit intent report subscription with customized requirements | Huawei, Deutsche Telekom, ZTE, NTT DOCOMO | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑250133 | Rel-19 CR TS 28.312 Add Use Case, Requirements, and Solution of Intent Degradation based on Expectation Preference | ZTE Corporation, Nokia, Deutsche Telekom | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑250134 | 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‑250833 | |||
S5‑250833 | 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 | No |
No
| reserved | No | S5‑250134 | |||
S5‑250135 | Rel-19 CR TS 28.312 Add use case and requirements for Enablers for Intent Fulfilment | Huawei, Deutsche Telekom | CR | Agreement | Yes |
YesZTE supports
| revised | No | S5‑250832 | |||
S5‑250832 | Rel-19 CR TS 28.312 Add use case and requirements for Enablers for Intent Fulfilment | Huawei, Deutsche Telekom | CR | Agreement | No |
No
| reserved | No | S5‑250135 | |||
S5‑250137 | Rel-19 CR TS 28.312 Add solution for intent exploration | Huawei,Deutsche Telekom | CR | Agreement | Yes |
Yes
| revised | No | S5‑250834 | |||
S5‑250834 | Rel-19 CR TS 28.312 Add solution for intent exploration | Huawei,Deutsche Telekom | CR | Agreement | No |
No
| reserved | No | S5‑250137 | |||
S5‑250138 | Rel-19 CR TS 28.312 Enhancement of Intent handling state management | Huawei, Deutsche Telekom | CR | Agreement | Yes |
Yes
| revised | No | S5‑250838 | |||
S5‑250838 | Rel-19 CR TS 28.312 Enhancement of Intent handling state management | Huawei, Deutsche Telekom | CR | Agreement | No |
No
| reserved | No | S5‑250138 | |||
S5‑250139 | Rel-19 CR TS 28.312 Add guidelines for using intent generic information model to support new scenario which is not standardized | Huawei, Deutsche Telekom | CR | Agreement | Yes |
Yes
| revised | No | S5‑250841 | |||
S5‑250841 | Rel-19 CR TS 28.312 Add guidelines for using intent generic information model to support new scenario which is not standardized | Huawei, Deutsche Telekom, Nokia | CR | Agreement | No |
Yes
| agreed | No | S5‑250139 | |||
S5‑250140 | Rel-19 CR TS 28.312 Intent lifecycle documentation improvement | Huawei, Deutsche Telekom | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑250141 | Rel-19 CR TS 28.312 Add procedure for intent feasibility check | Huawei, Deutsche Telekom | CR | Agreement | Yes |
Yes
| revised | No | S5‑250835 | |||
S5‑250835 | Rel-19 CR TS 28.312 Add procedure for intent feasibility check | Huawei, Deutsche Telekom | CR | Agreement | No |
No
| reserved | No | S5‑250141 | |||
S5‑250142 | Rel-19 CR TS 28.312 Add YAML definition for Intent capability exposure | Huawei, Nokia | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑250149 | Rel-19 CR TS 28.623 decouples the ProvMnS schema with supported feature schemas | Huawei,Ericsson | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250328 | Rel-19 CR 28.312 Add generic utility function support (stage 1) | Ericsson Inc., AT&T | CR | Agreement | Yes |
Yes
| revised | No | S5‑250836 | |||
S5‑250836 | Rel-19 CR 28.312 Add generic utility function support (stage 1) | Ericsson Inc., AT&T , Huawei, Orange, Nokia | CR | Agreement | No |
No
| reserved | No | S5‑250328 | |||
S5‑250439 | Rel-19 CR TS 28.312 Add use-case and requirements for intent driven management of network maintenance | NTT DOCOMO | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑250494 | Rel-19 CR TS 28.312 Add solution for intent driven management of network maintenance | NTT DOCOMO | CR | Agreement | Yes |
Yes
| revised | No | S5‑250840 | |||
S5‑250840 | Rel-19 CR TS 28.312 Add solution for intent driven management of network maintenance | NTT DOCOMO, Huawei | CR | Agreement | No |
No
| reserved | No | S5‑250494 | |||
S5‑250497 | Rel-19 CR TS 28.312 Add description of intent negotiation | China Mobile Com. Corporation | CR | Approval | Yes |
Yes
| revised | No | S5‑250837 | |||
S5‑250837 | Rel-19 CR TS 28.312 Add description of intent negotiation | China Mobile Com. Corporation | CR | Approval | No |
No
| reserved | No | S5‑250497 | |||
6.19.4 | Study on closed control loop management | |||||||||||
6.19.4.1 | Closed Control Loop Management | S5‑250055 | 28.567-000 | Nokia | other | Approval | Yes |
No
| available | No | ||
S5‑250056 | pCR TS28.567 TS clause structure | Nokia | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250057 | pCR TS28.567 Concepts and overview | Nokia | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250058 | pCR TS28.567 Dynamic composition of CCLs | Nokia | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250059 | pCR TS28.567 Conditional control of CCLs | Nokia | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250060 | pCR TS28.567 CCL Goal & targets conflicts management | Nokia | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250061 | pCR TS28.567 CCL scope conflicts management | Nokia | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250062 | pCR TS28.567 CCL Trigger-time & action-execution-time conflicts | Nokia | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250063 | pCR TS28.567 CCL Direct-Actions Conflicts management | Nokia | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250064 | pCR TS28.567 CCL Indirect target conflict management | Nokia | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250065 | pCR TS28.567 CCL-impact assessment and resolution | Nokia | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250066 | pCR TS28.567 CCL decision escalation | Nokia | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250067 | pCR TS28.567 Coordinating CCLs with other functions | Nokia | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250068 | pCR TS28.567 General CCL model | Nokia | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250069 | pCR TS28.567 Conflicts management solution description | Nokia | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250083 | CR TS28.536 Assurace CCL model | Nokia | CR | Approval | Yes |
No
| available | No | ||||
S5‑250112 | pCR TS28.567 CCL coordination basic NRM | Nokia Belgium | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250431 | Rel-19 pCR TS 28.567 Add use-case and Requirements for CCL for Fault Management | NTT DOCOMO, Nokia | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250492 | Rel-19 pCR 28.567 Triggered CCL UC and Requirements | Samsung R&D Institute India | pCR | Agreement | Yes |
No
| available | No | ||||
S5‑250493 | Rel-19 pCR 28.567 CCL creation based on historical data UC and Requirements | Samsung R&D Institute India | pCR | Agreement | Yes |
No
| available | No | ||||
S5‑250614 | Rel-19 pCR 28.567 Conflict Management UC and Requirements | Samsung R&D Institute India | pCR | No |
Yes
| withdrawn | Yes | |||||
S5‑250618 | Rel-19 pCR 28.567 Conflict Management UC and Requirements | Samsung Electronics GmbH | pCR | Agreement | Yes |
No
| available | No | ||||
S5‑250656 | Rel-19 pCR TS 28.567 Add use case and requirements for Performance monitoring of Closed control loop | Samsung Electronics France SA | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250783 | Draft TS 28.567 | Nokia | draft TS | Agreement | No |
Yes
| email approval | No | ||||
6.19.5 | Study on management aspects of Network Digital Twin | |||||||||||
6.19.5.1 | Management aspects of Network Digital Twins | S5‑250070 | pCR TS28.561 NDT concept and scope | Nokia | pCR | Approval | Yes |
No
| available | No | ||
S5‑250071 | pCR TS28.561 NDT LCM use case | Nokia | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250072 | pCR TS28.561 NDT support to Automation | Nokia | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250073 | pCR TS28.561 NDTs for verification | Nokia | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250074 | pCR TS28.561 NDTs for data generation | Nokia | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250169 | Rel-19 pCR TS 28.561 Add the Role of NDT in the Management Loop | ZTE Corporation | pCR | Agreement | Yes |
No
| available | No | ||||
S5‑250170 | Rel-19 pCR TS 28.561 Add New Use Case and Requirements on Life-cycle Management of NDT | ZTE Corporation | pCR | Agreement | Yes |
No
| available | No | ||||
S5‑250171 | Rel-19 pCR TS 28.561 Add Use Case and Requirements of Network Failure and Risk Prediction | ZTE Corporation | pCR | Agreement | Yes |
No
| available | No | ||||
S5‑250172 | Rel-19 pCR TS 28.561 Generic NDT NRM | ZTE Corporation | pCR | Agreement | Yes |
No
| available | No | ||||
S5‑250182 | pCR 28.561 Add skeleton | China Mobile, NTT DOCOMO | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250183 | pCR 28.561 Add scope | China Mobile | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250184 | pCR 28.561 Add the term and concepts of NDT | China Mobile | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250185 | pCR Add UC of using NDT to generate ML training data for TS 28.561 | China Mobile, Huawei | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250186 | pCR Add UC for using NDT support for network automation in TS 28.561 | China Mobile, Huawei | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250187 | pCR Add solution of Using NDT to generate ML training data for TS 28.561 | China Mobile | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250390 | Rel-19 pCR 28.561 NDT support for network automation | Samsung R&D Institute UK | pCR | Agreement | Yes |
No
| available | No | ||||
S5‑250419 | Rel-19 28.561 pCR Network Issue Inducement UC and Requirements | Samsung R&D Institute UK | pCR | Agreement | Yes |
No
| available | No | ||||
S5‑250442 | Rel-19 CR TS 28.561 Add concept of network topology data | NTT DOCOMO | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250444 | Rel-19 CR TS 28.561 Add use case and requirements on Network issue inducement | NTT DOCOMO | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250445 | Rel-19 CR TS 28.561 Add use case and requirements on synchronization with network | NTT DOCOMO | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250451 | NDT use cases and future development | FiberCop, Telecom Italia, Deutsche Telekom | discussion | Discussion | Yes |
No
| available | No | ||||
S5‑250484 | Rel-19 pCR TS 28.561 Concept and terms of NDT | Huawei | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250485 | Rel-19 pCR TS 28.561 Relations with existing network automation functions | Huawei | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250486 | Rel-19 pCR TS 28.561 NDT lifecycle management | Huawei | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250487 | Rel-19 pCR TS 28.561 Concepts of NDT services and reports | Huawei | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250488 | Rel-19 pCR TS 28.561 Use case of RAN energy saving policy verification | Huawei | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250489 | DP on the relation of general NDT framework and scenario specific attributes | Huawei | discussion | Endorsement | Yes |
No
| available | No | ||||
S5‑250490 | Rel-19 pCR TS 28.561 NDT NRMs | Huawei | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250782 | Draft TS 28.561 | CMCC | draft TS | Agreement | No |
Yes
| email approval | No | ||||
6.19.6 | Study on Cloud Aspects of Management and Orchestration | S5‑250229 | DP K8S CRD based orchestration | Rakuten Mobile, Inc | discussion | Endorsement | No |
Yes
| withdrawn | Yes | ||
S5‑250232 | pCR TR 28.869 Annex example for CRD based deployment | Rakuten Mobile, Inc | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250233 | pCR TR 28.869 LCM changes for declarative descriptor | Rakuten Mobile, Inc | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250325 | DP cloud native NF management data streaming solutions analysis | Rakuten Mobile, Inc | discussion | Presentation | Yes |
No
| available | No | ||||
S5‑250326 | S5-250326 pCR TR 28.869 enhance use case description for data streaming for cloud native network function | Rakuten Mobile, Inc | pCR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑250327 | pCR TR 28.869 enhance annex examples for data streaming for cloud native network function | Rakuten Mobile, Inc | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250329 | pCR TR 28.869 enhance use case description for data streaming for cloud native network function | Rakuten Mobile, Inc | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250331 | DP K8S CRD based orchestration | Rakuten Mobile, Inc | discussion | Presentation | Yes |
No
| available | No | ||||
S5‑250342 | pCR TR 28.869 Add use case and solution for 3GPP management architecture evolution based on PaaS | China Mobile,NTT DOCOMO | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250344 | DP on TR 28.869 solution for 3GPP management architecture evolution | China Mobile,NTT DOCOMO | discussion | Endorsement | Yes |
No
| available | No | ||||
S5‑250345 | pCR TR 28.869 Add Potential detailed solution for 3GPP management architecture | China Mobile,NTT DOCOMO | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250388 | R19 CR TR 28.869 add Observability for CNFs | Orange | draftCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑250437 | Rel-19 pCR 28.869 Add description of specification impacts | Huawei Technologies Japan K.K. | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250542 | pCR TR28.869 VNF configuration management | NTT DOCOMO, China Mobile | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250543 | pCR TR28.869 VNF configuration management flows | NTT DOCOMO, China Mobile | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250552 | R19 pCR TR 28.869 add Observability for CNFs | Orange | pCR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑250589 | R19 pCR TR 28.869 add Observability for CNFs | Orange, AT&T | pCR | Yes |
No
| available | No | |||||
S5‑250615 | pCR TR 28.869 Add clarification to terminology | Ericsson Telecomunicazioni SpA | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250616 | pCR TR 28.869 Update Annex D for example scenario of creation of NF Deployment instance | Ericsson Telecomunicazioni SpA | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250798 | Draft TR 28.869 | CMCC | draft TR | Agreement | No |
Yes
| 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 | |||||||||||
6.19.8.1 | Service Based Management Architecture enhancement phase 3 | S5‑250075 | Rel-19 CR 28.111 Add missing input parameters | Ericsson Hungary Ltd | CR | Approval | Yes |
No
| available | No | ||
S5‑250086 | Rel-19 CR 28.532 Define common notification header | Ericsson Hungary Ltd | CR | Approval | Yes |
No
| available | No | ||||
S5‑250106 | Rel-19 CR 28.111 Update notifications with common header | Ericsson Hungary Ltd | CR | Approval | Yes |
No
| available | No | ||||
S5‑250107 | Rel-19 CR 28.622 Reliable notification transfer | Ericsson Hungary Ltd | CR | Approval | Yes |
No
| available | No | ||||
S5‑250108 | Rel-19 CR 28.623 Reliable notification transfer | Ericsson Hungary Ltd | CR | Approval | Yes |
No
| available | No | ||||
S5‑250109 | Rel-19 CR 28.532 notifyNotificationError | Ericsson Hungary Ltd | CR | Approval | Yes |
No
| available | No | ||||
S5‑250143 | Rel-19 CR TS 28.537 Add reference for solution description (NRM fragment) for each management capability | Huawei | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
S5‑250144 | Rel-19 CR TS 28.537 Add reference for solution description (NRM fragment) for each management capability | Huawei, Deutsche Telekom | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250145 | 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 |
No
| available | No | ||||
S5‑250146 | Rel-19 CR TS 28.622 Enhance the MnSInfo to support discoverying management capabilities of MnS instances based on area of interest (Stage2) | Huawei, Deutsche Telekom | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250147 | Rel-19 CR TS 28.623 Enhance the MnSInfo to support discoverying management capabilities of MnS instances based on area of interest (Stage3) | Huawei | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250148 | Rel-19 CR TS 28.532 decouples the ProvMnS schema with supported feature schemas | Huawei,Ericsson | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250150 | Rel-19 CR TS 28.533 Overview of management capabilities and corresponding Solution Sets | Huawei, Deutsche Telekom | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250151 | Rel-19 TS 28.537 Usage of MnS Registry NRM fragment for MnS Registry and Discovery for different deployment scenarios | Huawei, Deutsche Telekom | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250152 | Rel-19 CR TS 28.622 Update MnSInfo IOC to support MnS Registry capability | Huawei, Deutsche Telekom | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250153 | Rel-19 CR TS 28.622 Update MnSInfo IOC to support MnS Registry capability | Huawei | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250364 |
Rel-19 CR TS 32.156 Clarify usage of < | Huawei | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250365 | Rel-19 CR TS 28.533 Enhance SBMA definitions | Huawei | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250366 | Rel-19 CR TS 28.533 Remove unused concept | Huawei | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250547 | Rel-19 CR 28.533 Add details for MnS versioning | Ericsson Inc. | CR | Approval | Yes |
No
| available | No | ||||
S5‑250636 | Rel-19 CR TS 28.533 Augment TS structure in Annex E | Ericsson, Deutsche Telekom | CR | Approval | Yes |
No
| available | No | ||||
S5‑250637 | Rel-19 CR TS 28.541 Add entry point information | Ericsson, Deutsche Telekom | CR | Approval | Yes |
No
| available | No | ||||
S5‑250638 | Rel-19 CR TS 28.622 Add entry point information | Ericsson, Deutsche Telekom | CR | Approval | Yes |
No
| available | No | ||||
6.19.9 | Study on Management of planned configurations | |||||||||||
6.19.9.1 | Management of planned configurations | S5‑250088 | Rel-19 pCR TS 28.572 Improve clause Planned configuration groups | Nokia | pCR | Approval | Yes |
No
| available | No | ||
S5‑250089 | Rel-19 pCR TS 28.572 Add clause Fallback configurations and Managing fallback configurations | Nokia | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250090 | Rel-19 pCR TS 28.572 Improve clause Trigger conditions | Nokia | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250091 | Rel-19 pCR TS 28.572 Improve clause Validation | Nokia | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250092 | Rel-19 pCR TS 28.572 Improve clause Activation | Nokia | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250093 | Rel-19 pCR TS 28.572 Add clause Asynchronous configuration updates | Nokia | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250094 | Rel-19 pCR TS 28.572 Improve clauses on Managing planned configurations | Nokia | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250095 | Rel-19 pCR TS 28.572 Add information model | Nokia | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250793 | Draft TS 28.572 | Nokia | draft TS | Agreement | No |
Yes
| email approval | No | ||||
6.19.10 | Data management phase 2 | S5‑250214 | Rel-19 CR TS 28.622 Add solution for model driven approach for management data reporting for area based KPI (Stage2) | Huawei, Deutsche Telekom | CR | Agreement | Yes |
No
| available | No | ||
S5‑250215 | Rel-19 CR TS 28.623 Add solution for model driven approach for management data reporting for area based KPI (Stage3) | Huawei | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250216 | Rel19 CR TS 28.623 Add stage3 YAML definition for external management data management | Huawei | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250217 | Rel19 CR TS 28.623 Add stage3 YAML defiintion for management data discovery | Huawei | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250518 | Rel19 CR TS 28.623 Stage 3 defintion for ManagementDataCollectionIoc | Nokia | CR | Approval | No |
No
| reserved | No | ||||
S5‑250519 | Rel19 CR TS 28.623 Stage 3 defintion for NodeFilter | Nokia | CR | Approval | No |
No
| reserved | No | ||||
S5‑250577 | Discussion on external management data | Nokia | discussion | Endorsement | Yes |
No
| available | No | ||||
S5‑250578 | Input to Draft CR 28.622 External Management Data | Nokia | draftCR | Approval | Yes |
No
| available | No | ||||
S5‑250781 | DraftCR Rel-19 TS 28.622 External Management Data | Ericsson Ericsson LM | draftCR | Approval | No |
Yes
| email approval | No | ||||
6.19.11 | Study on data management regarding subscriptions and reporting | |||||||||||
6.19.11.1 | Data management regarding subscriptions and reporting | S5‑250033 | Rel-19 CR TS 28.405 QoE Reference Uniqueness | Ericsson | CR | Agreement | Yes |
No
| available | No | ||
S5‑250034 | Rel-19 CR TS 32.422 Trace Reference Uniqueness | Ericsson | CR | Agreement | Yes |
No
| available | No | S5‑246353 | |||
6.19.12 | 5G performance measurements and KPIs phase 4 | S5‑250035 | Rel-19 CR TS 28.552 Corrections of Monitoring of NWDAF data collection Reference | Ericsson | CR | Agreement | Yes |
No
| available | No | ||
S5‑250253 | DP on PM Counter Metadata | Ericsson Canada Inc. | discussion | Endorsement | Yes |
No
| available | No | ||||
S5‑250254 | Rel-19 CR TS 28.552 Cell Unavailable Time performance measurement | Ericsson, AT&T | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250346 | Rel-19 CR TS 28.554 Add MA PDU session establishment time of network slice KPI for ATSSS | China Telecommunications Corp. | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250367 | Rel-19 CR TS 28.552 Correction of Mean time and max time of PDU session establishment | China Telecommunications Corp. | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250477 | Rel-19 CR TS 28.552 Enhanced the PRB usage with subcounter S-NSSAI | Huawei | CR | Approval | Yes |
No
| available | No | ||||
S5‑250478 | Rel-19 CR TS 28.552 Update the handover related measurements | Huawei | CR | Approval | Yes |
No
| available | No | ||||
S5‑250479 | Rel-19 CR TS 28.554 Update the reference for reliability related KPIs | Huawei | CR | Approval | Yes |
No
| available | No | ||||
S5‑250480 | Rel-19 CR TS 28.554 enhance the RAN UE throughput definition | Huawei | CR | Approval | Yes |
No
| available | No | ||||
S5‑250481 | Rel-19 CR TS 28.552 Enhanced DL UE throughput in gNB | Huawei | CR | Approval | Yes |
No
| available | No | ||||
6.19.13 | 5G Advanced NRM features phase 3 | S5‑250116 | Rel-19 CR TS 28.541 Add callbackUriPrefixList to NFService datatype | ZTE Corporation, Orange, Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
No
| available | No | ||
S5‑250117 | Rel-19 CR TS 28.541 Add supportedVendorSpecificFeatures to NFService datatype | ZTE Corporation, Orange, Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250118 | Rel-19 CR TS 28.541 Add ManagedNFProfile to NRFFunction | ZTE Corporation, Orange | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250136 | Rel-19 CR TS 28.541 Add attributes to support 5G Prose multi-hop relay services | CATT | CR | Approval | Yes |
No
| available | No | ||||
S5‑250157 | Rel19 CR TS28.541 NRM enhancements to NFProfile | Nokia, Nokia Shanghai Bell, ZTE Corporation, Orange | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250158 | Rel19 CR TS28.541 Enhance the OpenAPI related to multiplicity for 5GCNrm | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250159 | Rel19 CR TS28.541 Enhance the OpenAPI related to isUnique property for 5GCNrm | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250372 | Rel-19 CR 28.538 Update on ManagedEdgeNFService | Huawei | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250450 | Rel-19 CR 28.541 NRM extensions for VMR Ph2 | Samsung R&D Institute India | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250482 | Rel-19 CR TS 28.540 add usecase and requirements for WAB-gNB management | Huawei | CR | Approval | Yes |
No
| available | No | ||||
S5‑250483 | Rel-19 CR TS 28.540 corrections for MR-DC related description | Huawei | CR | Approval | Yes |
No
| available | No | ||||
6.19.14 | Subscriber and Equipment Trace and QoE collection management | S5‑250030 | Corrections of Trace Report Format | Ericsson, AT&T | discussion | Endorsement | Yes |
No
| available | No | ||
S5‑250031 | Rel-19 CR TS 32.423 Corrections on Trace Record Format | Ericsson, AT&T | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250077 | Rel-19 CR TS 32.422 Corrections on VS Trace Record | Ericsson, AT&T | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250245 | Rel-19 CR TS 28.622 Add RRC report in missing IOCs | Ericsson España S.A. | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250246 | Rel-19 CR TS 28.623 Add RRC report in missing IOCs (YANG) | Ericsson España S.A. | CR | Agreement | Yes |
No
| available | No | ||||
6.19.15 | Study on Management Aspects of NTN Phase 2 | |||||||||||
6.19.15.1 | Management Aspects of NTN Phase 2 | S5‑250314 | Rel-19 CR TS28.540 Add new requirements for NTN management | ZTE Corporation | CR | Approval | Yes |
No
| available | No | ||
S5‑250315 | Rel-19 CR TS28.541 Enhance the solution to support MEC deployed on the satellite scenario | ZTE Corporation | CR | Approval | Yes |
No
| available | No | ||||
S5‑250375 | Rel-19 CR TS 28.530 Update management capability support for NTN | China Unicom | CR | Agreement | Yes |
Yes
| withdrawn | Yes | ||||
S5‑250385 | Rel-19 CR TS 28.541 Add attributes to support 5GS functions on board the NTN | CATT | CR | Approval | Yes |
No
| available | No | ||||
S5‑250426 | Rel-19 CR TS 28.540 Requirements for NTN neighbour cell management | Huawei | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250427 | Rel-19 CR TS 28.540 Requirements for configuring AMF with TAIs supported by NTN gNB | Huawei | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250549 | Rel-19 CR 28.541 Add NTN time-based configuration support | Ericsson Inc. | CR | Approval | Yes |
No
| available | No | ||||
S5‑250588 | Rel-19 CR TS 28.530 Update management capability support for NTN | China Unicom | CR | Agreement | Yes |
No
| available | No | ||||
6.19.16 | Study on management of IAB nodes | |||||||||||
6.19.16.1 | Management of IAB nodes | S5‑250647 | Use case IAB-node connects to management system | Ericsson | CR | Approval | Yes |
No
| available | No | ||
6.19.17 | Study on management aspects of RedCap feature | |||||||||||
6.19.17.1 | Management Aspects of RedCap features | S5‑250259 | Rel-19 CR TS 28.540 Add requirements for management of RedCap feature | Huawei, China Unicom | CR | Agreement | Yes |
No
| available | No | ||
S5‑250260 | Rel-19 CR TS 28.541 Enhance NR NRM to support management of RedCap feature | Huawei, China Unicom | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250316 | Rel-19 CR TS28.552 Enhance RRC connection resuming related measurements for RedCap UEs | ZTE Corporation | CR | Approval | Yes |
No
| available | No | ||||
S5‑250317 | Rel-19 CR TS28.552 Enhance PRB Usage related measurements for RedCap UEs | ZTE Corporation | CR | Approval | Yes |
No
| available | No | ||||
S5‑250318 | Rel-19 CR TS28.552 Enhance Number of Active UEs related measurements for RedCap UEs | ZTE Corporation | CR | Approval | Yes |
No
| available | No | ||||
S5‑250380 | Rel-19 CR TS 28.541 Enhance NR NRM to support management of RedCap BWP feature | ChinaUnicom | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250386 | Rel-19 CR TS 28.552 Add new filter for throughput measurements for RedCap service | China Unicom | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250387 | Rel-19 CR TS 28.552 Add new filter for RRC connection number measurements for RedCap service | China Unicom | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250652 | Rel-19 CR TS 28.540 Adding requirements to control RedCap and e-RedCap UEs access | Samsung Electronics France SA | CR | Approval | Yes |
No
| available | No | ||||
S5‑250654 | Rel-19 CR TS 28.541 Enhancing NR NRM to control RedCap and e-RedCap UEs access | Samsung Electronics France SA | CR | Approval | Yes |
No
| available | No | ||||
6.19.18 | Study on Enhancement of Management Aspects related to NWDAF Phase 2 | |||||||||||
6.19.18.1 | Enhancement of Management Aspects related to NWDAF Phase 2 | S5‑250165 | Rel-19 CR 28.552 Add a new measurement related to number of failed NWDAF roaming analytics service subscriptions | China Telecom Corporation Ltd. | CR | Approval | Yes |
No
| available | No | ||
S5‑250167 | Rel-19 CR 28.552 Add new measurements related to failed rate of NWDAF roaming analytics service subscriptions | China Telecom | CR | Approval | Yes |
No
| available | No | ||||
6.19.19 | Study on Management of Network Sharing Phase 3 | |||||||||||
6.19.19.1 | Management of Network Sharing Phase 3 | S5‑250569 | Rel-19 CR TS 32.130 Enhance service-based management for MOCN | China Unicom, China Telecom | CR | Agreement | Yes |
No
| available | No | ||
S5‑250571 | Rel-19 CR TS 32.130 Add access requirements for management of shared NG-RAN | China Unicom, China Telecom | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250573 | Rel-19 CR TS 32.130 Add requirements for RAN and CN Management of Indirect of Network Sharing | China Unicom, China Telecom | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250575 | Rel-19 CR TS 32.130 Add concepts and background for Indirect Network Sharing | China Unicom | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250585 | Rel-19 CR TS 32.130 Add requirements for Management of Indirect of Network Sharing | China Unicom | CR | Agreement | Yes |
No
| available | No | ||||
6.19.20 | Study on energy efficiency and energy saving aspects of 5G networks and services | |||||||||||
6.19.20.1 | Energy efficiency and energy saving aspects of 5G networks and services | S5‑250028 | Rel-19 CR TS 28.541 Enhancements to energy cost mapping rule for split gNB support | Ericsson (China), Huawei, Nokia, Deutsche Telekom, AT&T | CR | Yes |
No
| available | No | |||
S5‑250202 | Rel-19 CR TS 28.622 Add GenericCollection to support grouping of objects - Stage 2 | Nokia | CR | Yes |
Yes
| revised | No | S5‑250595 | ||||
S5‑250203 | Rel-19 CR TS 28.623 Add GenericCollection to support grouping of objects - Stage 3 | Nokia | CR | Yes |
Yes
| revised | No | S5‑250596 | ||||
S5‑250204 | Rel-19 CR TS 28.310 cell proximity-based energy saving | Nokia | CR | Yes |
Yes
| revised | No | S5‑250597 | ||||
S5‑250205 | Rel-19 CR TS 28.104 Enhance the MDA assisted Energy Saving use case for handling of power shortages | Nokia | CR | No |
Yes
| withdrawn | Yes | |||||
S5‑250206 | Rel-19 CR TS 28.541 Enhance energy cost mapping rule to include renewable energy information to assist LBO | Nokia | CR | No |
Yes
| withdrawn | Yes | |||||
S5‑250207 | DP on enhancing energy cost mapping rule to include renewable energy information to assist LBO | Nokia | discussion | No |
Yes
| withdrawn | Yes | |||||
S5‑250208 | Discussion on deployment scenarios relevant for modelling of energy-related data | Nokia | discussion | Information | No |
No
| reserved | No | ||||
S5‑250276 | Rel-19 CR TS 28.541 Introducing EIFFunction IOC in 5GC NRM | Huawei, Deutsche Telekom | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250277 | Rel-19 CR TS 28.310 Add definitions and abbreviations | Huawei, Deutsche Telekom | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250312 | Rel-19 CR TS 28.310 Add informative annex on how EIF can collect energy information from OAM | Huawei, Deutsche Telekom | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250358 | Rel-19 CR TS 28.310 Update EE KPIs overview | Huawei | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250359 | Rel-19 CR TS 28.310 Add multi-dimensional energy efficiency use case and requirements | Huawei | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250360 | Rel-19 CR TS 28.310 Update some tags of EE requirements | Huawei | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250428 | Rel-19 CR TS 28.313 Use case and requirements for renewable energy based LBO | Huawei | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250429 | Rel-19 CR TS 28.313 Use case and requirements for renewable energy based LBO | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑250674 | |||
S5‑250430 | Rel-19 CR TS 28.313 Use case and requirements for renewable energy based LBO | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑250676 | |||
S5‑250435 | Rel-19 CR TS 28.532 Introduce energy supply, carbon emission and renewable energy information elements - stage 3 impacts | Nokia | CR | Yes |
Yes
| revised | No | S5‑250604 | ||||
S5‑250436 | Rel-19 CR TS 28.310 Introduce energy supply, carbon emission and renewable energy information elements | Nokia | CR | Yes |
Yes
| revised | No | S5‑250605 | ||||
S5‑250551 | Discussion Paper on modelling energy related information | Huawei | discussion | Discussion | Yes |
No
| available | No | ||||
S5‑250554 | Rel-19 CR TS 28.310 Add information model definitions for energy related information | Huawei | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250557 | Rel-19 CR TS 28.310 Add use case and requirements for collecting gNB and UPF Carbon Emission | Huawei | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250595 | Rel-19 CR TS 28.622 Add GenericCollection to support grouping of objects - Stage 2 | Nokia | CR | Approval | Yes |
No
| available | No | S5‑250202 | |||
S5‑250596 | Rel-19 CR TS 28.623 Add GenericCollection to support grouping of objects - Stage 3 | Nokia | CR | Approval | Yes |
No
| available | No | S5‑250203 | |||
S5‑250597 | Rel-19 CR TS 28.310 cell proximity-based energy saving | Nokia | CR | Approval | Yes |
No
| available | No | S5‑250204 | |||
S5‑250604 | Rel-19 CR TS 28.532 Introduce energy supply, carbon emission and renewable energy information elements - stage 3 impacts | Nokia | CR | Approval | Yes |
No
| available | No | S5‑250435 | |||
S5‑250605 | Rel-19 CR TS 28.310 Introduce energy supply, carbon emission and renewable energy information elements | Nokia | CR | Approval | Yes |
No
| available | No | S5‑250436 | |||
S5‑250674 | Rel-19 CR TS 28.313 Procedure for renewable energy based LBO | Huawei | CR | Agreement | Yes |
No
| available | No | S5‑250429 | |||
S5‑250676 | Rel-19 CR TS 28.541 NRM enhancement to capture renewable energy based LBO | Huawei | CR | Agreement | Yes |
No
| available | No | S5‑250430 | |||
S5‑250679 | Discussion paper on deployment scenarios relevant for modelling of energy-related data | Nokia Germany | discussion | Yes |
No
| available | No | |||||
6.19.21 | Study on Enhanced OAM for management exposure to external consumers | |||||||||||
6.19.21.1 | Enhanced OAM for management service exposure to external consumers through CAPIF | S5‑250361 | pCR TS 28.579 Add scope content | Huawei | pCR | Approval | Yes |
No
| available | No | ||
S5‑250362 | pCR TS 28.579 Add concepts content | Huawei | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250363 | pCR TS 28.579 Use case exposure of management services through the CAPIF | Huawei | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250606 | Rel-19 pCR TS 28.579 Add concepts and background | Nokia UK | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250607 | Rel-19 pCR TS 28.579 Add use case and requirements for API provider domain for management services | Nokia UK | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250608 | Rel-19 pCR TS 28.579 Add use case and requirements for logging the management service API invocations to the CCF | Nokia UK | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250609 | Rel-19 pCR TS 28.579 Add use case and requirements for publishing of management services to the CCF | Nokia UK | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250613 | TS Skeleton for TS 28.579 | Nokia UK | other | Approval | Yes |
No
| available | No | ||||
S5‑250792 | Draft TS 28.579 | Nokia | draft TS | Agreement | No |
Yes
| email approval | No | ||||
6.19.22 | Management for MonStra (completed) | |||||||||||
7 | Charging | S5‑250681 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||
S5‑250682 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250683 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250684 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250685 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250686 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250687 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250688 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250689 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250690 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250691 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250692 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250693 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250694 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250695 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250696 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250697 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250698 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250699 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250700 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250701 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250702 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250703 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250704 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250705 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250706 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250707 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250708 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250709 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250710 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250711 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250712 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250713 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250714 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250715 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250716 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250717 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250718 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250719 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250720 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250721 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250722 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250723 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250724 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250725 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250726 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250727 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250728 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250729 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250730 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250731 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250732 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250733 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250734 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250735 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250736 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250737 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250738 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250739 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250740 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250741 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250742 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250743 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250744 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250745 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250746 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250747 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250748 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250749 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250750 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250751 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250752 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250753 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250754 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250755 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250756 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250757 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250758 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250759 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250760 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250761 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250762 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250763 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250764 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250765 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250766 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250767 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250768 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250769 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250770 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250771 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250772 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250773 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250774 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250775 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250776 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250777 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250778 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
S5‑250779 | (reserved) | CH | other | discussion | No |
No
| reserved | No | ||||
7.1 | Charging Plenary | S5‑250015 | agenda_with_Tdocs_sequence_CH | SWG CH Chair (MATRIXX Software) | agenda | Yes |
No
| available | No | |||
S5‑250016 | Charging exec report | SWG CH Chair (MATRIXX Software) | report | No |
No
| reserved | No | |||||
S5‑250017 | Collection of useful contributions and external communication documents in CH | SWG Vice Chair (Huawei Tech.(UK) Co.. Ltd) | other | No |
No
| reserved | No | |||||
S5‑250022 | SA5 Charging workplan for Rel-19 – update | SWG CH Chair (MATRIXX Software) | other | No |
No
| reserved | No | |||||
7.2 | New Charging Study/Work Item proposals | S5‑250218 | Rel-19 New WID on Charging aspects of CAPIF | Nokia | WID new | Agreement | Yes |
No
| available | No | ||
S5‑250340 | Rel-19 DP on Charging Aspects of 5GC LoCation Services | China Telecommunications | discussion | Discussion | Yes |
No
| available | No | ||||
S5‑250341 | Rel-19 New WID on Charging Aspects of 5GC LoCation Services | China Telecommunications | WID new | Approval | Yes |
No
| available | No | ||||
S5‑250347 | New WID on Charging for Uncrewed Aerial Systems Phase 2 | China Mobile Com. Corporation | WID new | Agreement | Yes |
No
| available | No | ||||
S5‑250391 | Discussion on the way forward for A-IoT Charging | Huawei | discussion | Discussion | Yes |
No
| available | No | ||||
S5‑250392 | New WID on Charging for Ambient power-enabled Internet of Things | Huawei, China Unicom | WID new | Agreement | Yes |
No
| available | No | ||||
S5‑250408 | Rel-19 Revised WID on charging aspects for energy efficiency of 5G | Huawei | WID revised | Agreement | Yes |
No
| available | No | ||||
S5‑250495 | New WID on Charging aspects of next generation real time communication services phase 2 | China Mobile | WID new | Approval | Yes |
No
| available | No | ||||
S5‑250510 | New WID on charging aspects of satellite access Phase 3 | CATT, CSCN | WID new | Approval | Yes |
No
| available | No | ||||
S5‑250520 | New WID on charging information including device identities | Ericsson | WID new | Agreement | Yes |
No
| available | No | ||||
S5‑250521 | New WID on charging enhancement for MOCN network sharing | Ericsson | WID new | Agreement | Yes |
No
| available | No | ||||
7.3 | Charging Maintenance and Rel-19 Charging small enhancements | S5‑250409 | Discussion on inter-CHF failure handling | Huawei | discussion | Discussion | Yes |
No
| available | No | ||
S5‑250410 | Rel-18 CR 32.290 Correction on inter-CHF failure handling | Huawei | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250411 | Rel-19 CR 32.290 Correction on CHF as NF consumer detected failure | Huawei | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250412 | Rel-18 CR 32.291 Correction on inter-CHF failure handling | Huawei | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250413 | Rel-19 CR 32.291 Correction on inter-CHF failure handling | Huawei | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250414 | Discussion on Correction of Recipient Address in SMS Charging | Huawei | discussion | Discussion | Yes |
No
| available | No | ||||
S5‑250415 | Rel-18 CR 32.291 Correction of Recipient Address in SMS Charging | Huawei | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250416 | Rel-19 CR 32.291 Correction of Recipient Address in SMS Charging | Huawei | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250417 | Rel-18 CR 32.298 Correction on SMS charging CDR | Huawei | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250418 | Rel-19 CR 32.298 Correction on SMS Charging CDR | Huawei | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250522 | Rel-17 CR 32.255 Correction of missing pduType for PGW | Ericsson | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250523 | Rel-17 CR 32.255 Correction of missing pduType for PGW | Ericsson | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250524 | Rel-19 CR 32.255 Correction of missing pduType for PGW | Ericsson | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250525 | Rel-19 CR 32.291 Correction of missing pduType for PGW | Ericsson | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250526 | Rel-19 CR 32.291 Correction of missing pduType for PGW | Ericsson | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250527 | Rel-19 CR 32.291 Correction of missing pduType for PGW | Ericsson | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250592 | Rel-17 CR 32.298 Correction of GSNAddress import | Ericsson | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250593 | Rel-18 CR 32.298 Correction of GSNAddress import | Ericsson | CR | Agreement | Yes |
No
| available | No | ||||
7.4 | Rel-19 Work Items | |||||||||||
7.4.1 | WID on CHF Segmentation | S5‑250528 | Rel-19 DP Introduction of features for domains | Ericsson | discussion | Endorsement | Yes |
No
| available | No | ||
7.4.2 | WID on Charging Aspects of Ranging and Sidelink Positioning (completed) | |||||||||||
7.4.3 | WID on charging aspects for energy efficiency of 5G | S5‑250406 | Rel-19 CR 32.291 Add network slice energy information | Huawei | CR | Agreement | Yes |
No
| available | No | ||
S5‑250407 | Rel-19 CR 32.298 Add network slice energy information | Huawei | CR | Agreement | Yes |
No
| available | No | ||||
S5‑250529 | Rel-19 DP Use of energy efficiency and consumption information | Ericsson | discussion | Discussion | Yes |
No
| available | No | ||||
7.4.4 | WID on charging for indirect network sharing (completed) | |||||||||||
7.4.5 | Charging Aspects for 5G ProSe Ph3 | S5‑250376 | Add charging-related information in support of ProSe Multi-Hop UE-to-Network communication | China Telecom Corporation Ltd. | CR | Yes |
No
| available | No | |||
S5‑250377 | DP on charging aspects for 5G ProSe Communication via Multi-hop 5G ProSe Layer-3 UE-to-Network Relay | China Telecom Corporation Ltd. | discussion | Endorsement | Yes |
No
| available | No | ||||
S5‑250378 | Update Message flows for ProSe Direct Discovery over PC5 reference point | China Telecom Corporation Ltd. | CR | Yes |
No
| available | No | |||||
S5‑250379 | Update Message flows for ProSe UE-to-Network Direct Communication | China Telecom Corporation Ltd. | CR | Yes |
No
| available | No | |||||
7.5 | Charging Studies | |||||||||||
7.5.1 | Study on charging aspects of satellite access Phase 3 | S5‑250453 | pCR 28.846 Add References, Evaluation and Conclusion for satellite resource usage charging | CSCN | pCR | Approval | Yes |
No
| available | No | ||
S5‑250502 | TR 28.846 Add TDF based solution for S&F operation charging with User Plane CIoT | CATT | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250503 | TR 28.846 Update evaluation for store and forward satellite operation charging | CATT | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250504 | TR 28.846 Update conclusion for store and forward satellite operation charging | CATT | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250505 | TR 28.846 Add charging solutions for UE-SAT-UE communication | CATT | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250506 | TR 28.846 Add evaluation for UE-SAT-UE communication | CATT | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250507 | TR 28.846 Add conclusion for UE-SAT-UE communication | CATT | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250508 | Presentation of TR 28.846 for Approval | CATT | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250509 | Clean TR 28.846 based on edithelp | CATT | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250511 | 28.846 Add conclusions and recommendations | CATT | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250530 | Rel-19 pCR 28.846 Architecture updates | Ericsson | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250531 | Rel-19 pCR 28.846 Business scenario updates | Ericsson | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250532 | Rel-19 pCR 28.846 Correction and conclusion update for topic 1 | Ericsson | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250533 | Rel-19 pCR 28.846 New solution for topic 1 | Ericsson | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250534 | Rel-19 pCR 28.846 Solution update for topic 3 | Ericsson | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250535 | Rel-19 pCR 28.846 Solution for topic 4 | Ericsson | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250794 | Draft TR 28.846 | CICT | draft TR | Agreement | No |
Yes
| email approval | No | ||||
7.5.2 | Study on Charging Aspects of CAPIF | S5‑250219 | pCR 28.849 CAPIF Converged Charging using CEF | Nokia | pCR | Approval | Yes |
No
| available | No | ||
S5‑250220 | pCR TR 28.849 Conclusion for Topic#1 | Nokia | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250221 | pCR 28.849 Conclusion for Topic #2 | Nokia | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250222 | pCR 28.849 Conclusion for Topic #3 | Nokia | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250223 | Rel-19 pCR 28.849 Conclusion for Topic #4 | Nokia | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250224 | Rel-19 pCR 28.849 Conclusion | Nokia | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250225 | Rel-19 pCR 28.849 EditHelp Editorial Changes | Nokia | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250226 | Rel-19 pCR 28.849 Evaluation for Topic #2 | Nokia | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250227 | Rel-19 pCR 28.849 Evaluation for Topic #3 | Nokia | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250228 | Rel-19 pCR 28.849 Evaluation for Topic #4 | Nokia | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250230 | Rel-19 pCR 28.849 Solution for Topic #3 | Nokia | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250231 | Rel-19 pCR 28.849 Use Case for Topic #3 | Nokia | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250393 | Rel-19 pCR 28.849 New solution for NEF implementing API Provider in Topic 4 | Huawei | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250394 | Rel-19 pCR 28.849 New solution for distributed deployment of NEF in Topic 4 | Huawei | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250395 | Rel-19 pCR 28.849 Update evaluation and conclusion for Topic 4 | Huawei | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250396 | Rel-19 pCR 28.849 Update evaluation and conclusion for Topic 1 | Huawei | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250397 | Rel-19 pCR 28.849 Update evaluation and conclusion for Topic 3 | Huawei | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250536 | Rel-19 pCR 28.849 Evaluation and conclusion for topic 1 | Ericsson | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250537 | Rel-19 pCR 28.849 Update of solution 1.6 | Ericsson | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250538 | Rel-19 pCR 28.849 Evaluation and conclusion for topic 2 | Ericsson | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250539 | Rel-19 pCR 28.849 Evaluation and conclusion for topic 3 | Ericsson | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250540 | Rel-19 pCR 28.849 Evaluation and conclusion for topic 4 | Ericsson | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250541 | Rel-19 pCR 28.849 Evaluation and conclusion | Ericsson | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250795 | Draft TR 28.849 | Nokia | draft TR | Agreement | No |
Yes
| email approval | No | ||||
7.5.3 | Study on Charging aspects of next generation real time communication services phase 2 | S5‑250268 | pCR 28.851 DC Application Charging Requirements | Nokia | pCR | Approval | Yes |
No
| available | No | ||
S5‑250269 | DC Key Issues for Topic #3 | Nokia | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250270 | Rel-19 pCR 28.851 DC Solution for Topic #3 | Nokia | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250271 | Rel-19 pCR 28.851 DC Use Case | Nokia | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250272 | Rel-19 pCR 28.851 Topic #3 Evaluation | Nokia | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250398 | Rel-19 pCR 28.851 New charging solution for DC application usage by volume | Huawei | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250399 | Rel-19 pCR 28.851 New charging solution for DC application download by volume | Huawei | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250400 | Rel-19 pCR 28.851 Update evaluation for Topic 2 | Huawei | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250401 | Rel-19 pCR 28.851 Add conclusion for Topic 2 | Huawei | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250402 | Rel-19 pCR 28.851 Add conclusion for Topic 3 | Huawei | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250403 | Rel-19 pCR 28.851 Add conclusion for Topic 4 | Huawei | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250496 | Rel-19 pCR 28.851 New KI on Support of Avatar communication | China Mobile | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250498 | Rel-19 pCR 28.851 Adding solution on Support of Avatar communication | China Mobile | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250499 | Rel-19 pCR 28.851 Adding conclusion for topic 1 | China Mobile | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250500 | Rel-19 pCR 28.851 Conclusions and recommendations | China Mobile | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250501 | Presentation of TR 28.851 for Approval | China Mobile | TS or TR cover | Approval | Yes |
No
| available | No | ||||
S5‑250796 | Draft TR 28.851 | CMCC | draft TR | Agreement | No |
Yes
| email approval | No | ||||
7.5.4 | Study on Charging aspects of Uncrewed Aerial Vehicle | S5‑250349 | Rel-19 pCR 28.853 Add Evaluation and Conclusion for UAV Indication | China Mobile Com. Corporation | pCR | Approval | Yes |
No
| available | No | ||
S5‑250351 | Rel-19 pCR 28.853 Add Evaluation and Conclusion for C2 Communication charging | China Mobile Com. Corporation | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250352 | Rel-19 pCR 28.853 Update Conclusions and Recommendations | China Mobile Com. Corporation | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250353 | Presentation of TR 28.853 for Approval | China Mobile Com. Corporation | TS or TR cover | Approval | Yes |
No
| available | No | ||||
S5‑250404 | Rel-19 pCR 28.853 New solutions for UAV indication | Huawei, China Mobile | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250405 | Rel-19 pCR 28.853 Conclusion for A2X communication charging | Huawei | pCR | Approval | Yes |
No
| available | No | ||||
S5‑250797 | Draft TR 28.853 | CMCC | draft TR | Agreement | No |
Yes
| email approval | No | ||||
8 | Any Other Business | |||||||||||
9 | Closing of the meeting |