Tdoc List
2025-05-27 12:24
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‑252200 | Agenda | WG Chair | agenda | Yes |
Yes
| approved | No | |||
3 | IPR and legal declaration | S5‑252201 | IPR and legal declaration | WG Chair | other | Yes |
Yes
| noted | No | |||
4 | Meetings and activities reports |   | ||||||||||
4.1 | Last SA5 meeting report | S5‑252202 | 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‑252203 | Time Plan for SA5 Plenary and OAM sessions | WG Chair | agenda | Yes |
Yes
| noted | No | |||
S5‑252204 | agenda_with_Tdocs_sequence_Plenary&OAM | WG Chair | agenda | Yes |
Yes
| agreed | No | |||||
S5‑252205 | SA5 working procedures | WG Chair | other | Yes |
Yes
| revised | No | S5‑252817 | ||||
S5‑252817 | SA5 working procedures | WG Chair | other | - | Yes |
Yes
| endorsed | No | S5‑252205 | |||
S5‑252206 | SA5 Meeting facility requirements | WG Chair | other | Yes |
Yes
| noted | No | |||||
S5‑252208 | Post meeting email approval status | WG Vice Chair (Ericsson) | other | No |
Yes
| noted | No | |||||
S5‑252211 | Plenary and OAM Chair notes and conclusions | WG Chair | report | Yes |
Yes
| noted | No | |||||
S5‑252214 | Rel-19 SA5 work plan TU table | WG Chair | other | Yes |
Yes
| noted | No | |||||
S5‑252218 | Latest SA5 Rel-19 WIs-SIs | WG Chair | other | Yes |
Yes
| noted | No | |||||
S5‑252219 | Rel-19 SA5 work planning | WG Chair | other | Yes |
Yes
| endorsed | No | |||||
S5‑252220 | Rel-20 SA5 work planning | WG Chair | other | Yes |
Yes
| revised | No | S5‑253022 | ||||
S5‑253022 | Rel-20 SA5 work planning | WG Chair | other | - | Yes |
Yes
| endorsed | No | S5‑252220 | |||
S5‑252293 | Working Procedure | Nokia, Nokia Shanghai Bell | other | Approval | Yes |
YesTo add Balazs as code moderator of TS25.560 and TS28.310.
| merged | No | S5‑252817 | |||
S5‑252433 | Selecting the Release for the SA5 OAM and Charging aspects | SA5 leadership & MCC | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑252826 | |||
S5‑252826 | Selecting the Release for the SA5 OAM and Charging aspects | SA5 leadership & MCC | discussion | Endorsement | Yes |
Yes
| endorsed | No | S5‑252433 | |||
5.2 | Technical issues at SA5 level |   | ||||||||||
5.3 | Liaison statements at SA5 level | S5‑252346 | Publication of ETSI NFV group report on architectural support for NFV evolution (SA5#160) | ETSI ISG NFV | LS in | Information | Yes |
Yes
| replied to | No | ||
S5‑252348 | LS on draft-ietf-nmop-simap-concept, “SIMAP: Concept, Requirements, and Use Cases” | IETF Network Management Operations Working Group (NMOP) | LS in | Information | Yes |
Yes
| noted | No | ||||
S5‑252349 | LS on the creation of the Getting Ready for Energy-Efficient Networking Working Group in the IETF | IETF Getting Ready for Energy-Efficient Networking Working Group (GREEN) | LS in | Information | Yes |
Yes
| noted | No | ||||
S5‑252350 | LS on initiation of new work item ITU-T Y.JDEVOP-frame "Framework of joint development and operation for IMT-2020 networks and beyond" | ITU-T SG 13 | LS in | Information | Yes |
Yes
| noted | No | ||||
S5‑252352 | LS on initiation of new Supplement to ITU-T Y.3184 (Y.Sup-Mec-CONA) “Mechanism for customer-oriented intelligent awareness of network status” | ITU-T SG 13 | LS in | Information | Yes |
Yes
| noted | No | ||||
S5‑252617 | LS reply to ETSI NFV publication of NFV-IFA054 | NTT DOCOMO, China Mobile | LS out | Approval | Yes |
Yes
| approved | No | ||||
S5‑252737 | LS on call for contributions to the new Focus Group on Artificial Intelligence Native for Telecommunication Networks (FG-AINN) | ITU-T FG-AINN | LS in | Information | Yes |
Yes
| noted | No | ||||
5.4 | SA5 meeting calendar | S5‑252207 | SA5 meeting calendar | WG Chair | other | Yes |
Yes
| revised | No | S5‑252827 | ||
S5‑252827 | SA5 meeting calendar | WG Chair | other | - | Yes |
Yes
| noted | No | S5‑252207 | |||
5.5 | Rel-20 topic preparation | S5‑252306 | Rel-20 New SID on Charging Aspects of CAPIF Phase 3 | Nokia | SID new | Approval | Yes |
Yes
| revised | No | S5‑253082 | |
S5‑253082 | Rel-20 New SID on Charging Aspects of CAPIF Phase 3 | Nokia | SID new | Approval | Yes |
Yes
| revised | No | S5‑253099 | S5‑252306 | ||
S5‑253099 | Rel-20 New SID on Charging Aspects of CAPIF Phase 3 | Nokia | SID new | Approval | Yes |
Yes
| agreed | No | S5‑253082 | |||
S5‑252314 | New SID on energy efficiency and energy saving aspects of 5G Advanced | Nokia | SID new | Agreement | Yes |
Yes
| revised | No | S5‑253069 | |||
S5‑253069 | New SID on energy efficiency and energy saving aspects of 5G Advanced | Nokia | SID new | Agreement | Yes |
Yes
| agreed | No | S5‑252314 | |||
S5‑252331 | New WID on OAM for Extended Reality and Media service (XRM) Phase 2 | ZTE Corporation | WID new | Agreement | Yes |
Yes
| revised | No | S5‑253078 | |||
S5‑253078 | New WID on OAM for Extended Reality and Media service (XRM) Phase 2 | ZTE Corporation | WID new | Agreement | Yes |
Yes
| revised | No | S5‑253093 | S5‑252331 | ||
S5‑253093 | New WID on OAM for Extended Reality and Media service (XRM) Phase 2 | ZTE Corporation | WID new | Agreement | Yes |
Yes
| agreed | No | S5‑253078 | |||
S5‑252332 | New SID Study on intent driven management services for mobile network phase 4 | Moderator (Huawei, Ericsson) | SID new | Agreement | Yes |
Yes
| revised | No | S5‑253070 | S5‑251777 | ||
S5‑253070 | New SID Study on intent driven management services for mobile network phase 4 | Moderator (Huawei, Ericsson) | SID new | Agreement | Yes |
Yes
| agreed | No | S5‑252332 | |||
S5‑252376 | New SID on Enhancement of Management Aspects related to NWDAF Phase 3 | China Telecom Corporation Ltd. | SID new | Approval | Yes |
Yes
| revised | No | S5‑253079 | |||
S5‑253079 | New SID on Enhancement of Management Aspects related to NWDAF Phase 3 | China Telecom Corporation Ltd. | SID new | Approval | Yes |
Yes
| revised | No | S5‑253095 | S5‑252376 | ||
S5‑253095 | New WID on Enhancement of Management Aspects related to NWDAF Phase 3 | China Telecom Corporation Ltd. | WID new | Approval | Yes |
Yes
| agreed | No | S5‑253079 | |||
S5‑252414 | New WID on 5G performance measurements&KPIs and Trace&MDT&QoE | China Telecom Corporation Ltd. | WID new | Agreement | Yes |
Yes
| revised | No | S5‑253080 | |||
S5‑253080 | New WID on 5G performance measurements&KPIs and Trace&MDT&QoE | China Telecom Corporation Ltd. | WID new | Agreement | Yes |
Yes
| agreed | No | S5‑252414 | |||
S5‑252421 | New SID on Management aspect of Network Digital Twins phase 2 | Moderator (China Mobile) | SID new | Approval | Yes |
Yes
| revised | No | S5‑253071 | S5‑251776 | ||
S5‑253071 | New SID on Management aspect of Network Digital Twins phase 2 | Moderator (China Mobile) | SID new | Approval | Yes |
Yes
| revised | No | S5‑253094 | S5‑252421 | ||
S5‑253094 | New SID on Management aspect of Network Digital Twins phase 2 | Moderator (China Mobile) | SID new | Approval | Yes |
Yes
| agreed | No | S5‑253071 | |||
S5‑252442 | SA5_Rel-20_5GA_Topics_Consolidated_List | WG Chair | other | Information | Yes |
Yes
| noted | No | S5‑250168 | |||
S5‑252493 | Moderated R20 topic discussion on use cases for charging reliability enhancement | Huawei | discussion | Discussion | Yes |
Yes
| noted | No | ||||
S5‑252519 | New SID on Study on Management Data Analytics (MDA) – Phase 4 | Huawei Tech. Japan, K.K. | SID new | Approval | Yes |
Yes
| revised | No | S5‑253072 | |||
S5‑253072 | New SID on Study on Management Data Analytics (MDA) – Phase 4 | Huawei Tech. Japan, K.K. | SID new | Approval | Yes |
Yes
| agreed | No | S5‑252519 | |||
S5‑252520 | New SID on cloud aspects of management and orchestration phase 2 | Moderator (China Mobile) | SID new | Approval | Yes |
Yes
| revised | No | S5‑252944 | |||
S5‑252944 | New SID on cloud aspects of management and orchestration phase 2 | Moderator (China Mobile) | SID new | Approval | Yes |
Yes
| noted | No | S5‑252520 | |||
S5‑252558 | New Study on AI/ML management enhancements | NEC, Intel | SID new | Agreement | Yes |
Yes
| revised | No | S5‑253073 | |||
S5‑253073 | New Study on AI/ML management enhancements | NEC, Intel | SID new | Agreement | Yes |
Yes
| revised | No | S5‑253096 | S5‑252558 | ||
S5‑253096 | New Study on AI/ML management enhancements | NEC, Intel | SID new | Agreement | Yes |
Yes
| agreed | No | S5‑253073 | |||
S5‑252599 | New SID on SBMA enhancement phase 4 | Moderator (Huawei) | SID new | Agreement | Yes |
Yes
| revised | No | S5‑253074 | |||
S5‑253074 | New SID on SBMA enhancement phase 4 | Moderator (Huawei) | SID new | Agreement | Yes |
Yes
| agreed | No | S5‑252599 | |||
S5‑252609 | China Telecom’s View on 6G Charging | China Telecom Corporation Ltd. | discussion | Discussion | Yes |
Yes
| noted | No | ||||
S5‑252616 | New WID on 5G Advanced NRM features phase 4 | Nokia, Nokia Shanghai Bell | WID new | Agreement | Yes |
Yes
| revised | No | S5‑253081 | |||
S5‑253081 | New WID on 5G Advanced NRM features phase 4 | Nokia, Nokia Shanghai Bell | WID new | Agreement | Yes |
Yes
| revised | No | S5‑253097 | S5‑252616 | ||
S5‑253097 | New WID on 5G Advanced NRM features phase 4 | Nokia, Nokia Shanghai Bell | WID new | Agreement | Yes |
Yes
| agreed | No | S5‑253081 | |||
S5‑252654 | New SID on Enhanced exposure of management services | Nokia Belgium | SID new | Approval | Yes |
Yes
| revised | No | S5‑253075 | |||
S5‑253075 | New SID on Enhanced exposure of management services | Nokia Belgium | SID new | Approval | Yes |
Yes
| agreed | No | S5‑252654 | |||
S5‑252658 | New WID on AIML management phase 3 | Nokia Americas | WID new | Yes |
Yes
| noted | No | |||||
S5‑252669 | Rel-20 New SID on Semantic Network Management | Moderator(China Unicom, Samsung) | SID new | Approval | Yes |
Yes
| noted | No | ||||
S5‑252701 | New WID on Life Cycle Management (LCM) of NF Deployment | Ericsson Limited | WID new | Approval | Yes |
Yes
| revised | No | S5‑252945 | |||
S5‑252945 | New WID on Life Cycle Management (LCM) of NF Deployment | Ericsson Limited | WID new | Approval | No |
Yes
| noted | No | S5‑252701 | |||
S5‑252709 | New SID on Closed Control Loop Management -Ph2 | Samsung, Nokia | SID new | Agreement | Yes |
Yes
| revised | No | S5‑253076 | |||
S5‑253076 | New SID on Closed Control Loop Management -Ph2 | Samsung, Nokia | SID new | Agreement | Yes |
Yes
| revised | No | S5‑253098 | S5‑252709 | ||
S5‑253098 | New SID on Closed Control Loop Management -Ph2 | Samsung, Nokia | SID new | Agreement | Yes |
Yes
| agreed | No | S5‑253076 | |||
S5‑252729 | New SID on Study for Data management phase 3 | Nokia | SID new | Approval | Yes |
Yes
| revised | No | S5‑253077 | |||
S5‑253077 | New SID on Study for Data management phase 3 | Nokia | SID new | Approval | Yes |
Yes
| agreed | No | S5‑252729 | |||
6 | OAM&P |   | ||||||||||
6.1 | OAM&P Plenary | S5‑252209 | OAM action list | WG Vice Chair (Nokia) | other | No |
Yes
| noted | No | |||
S5‑252210 | OAM Exec Report | WG Vice Chair (Nokia) | report | No |
Yes
| noted | No | |||||
S5‑252212 | Collection of useful endorsed documents in OAM | WG Vice Chair (Nokia) | discussion | No |
Yes
| noted | No | |||||
S5‑252213 | Collection of external communication documents in OAM | WG Vice Chair (Nokia) | discussion | No |
Yes
| noted | No | |||||
S5‑252221 | OAM breakout notes | WG Chair | report | Yes |
Yes
| noted | No | |||||
S5‑252281 | LS on Updates to Umbrella Information Model | Ericsson Hungary Ltd | LS out | Approval | Yes |
Yes
| revised | No | S5‑252838 | |||
S5‑252838 | LS on Updates to Umbrella Information Model | Ericsson Hungary Ltd | LS out | Approval | Yes |
Yes
| revised | No | S5‑253086 | S5‑252281 | ||
S5‑253086 | LS on Updates to Umbrella Information Model | Ericsson Hungary Ltd | LS out | Approval | Yes |
Yes
| approved | No | S5‑252838 | |||
S5‑252284 | Reply LS clarification on UE performance measurement at PDCP level | NEC, Intel | LS out | Approval | Yes |
Yes
| revised | No | S5‑252839 | |||
S5‑252839 | Reply LS clarification on UE performance measurement at PDCP level | NEC, Intel | LS out | Approval | Yes |
Yes
| approved | No | S5‑252284 | |||
S5‑252295 | Reply to RAN2 LS on Number of UEs in RRC_INACTIVE state with data transmission | China Telecom Corporation Ltd. | LS out | Agreement | Yes |
Yes
| noted | No | ||||
S5‑252840 | Reply to RAN2 LS on Number of UEs in RRC_INACTIVE state with data transmission | China Telecom Corporation Ltd. | LS out | Agreement | No |
Yes
| withdrawn | Yes | ||||
S5‑252319 | Reply to LS on clarification on UE performance measurement at PDCP level | Ericsson Japan K.K. | LS out | Approval | Yes |
Yes
| merged | No | S5‑252839 | |||
S5‑252335 | Reply LS on SON for Network Slicing and Enhanced Area Scope | CT4 | LS in | Information | Yes |
Yes
| noted | No | ||||
S5‑252336 | LS on AI/ML UE sided data collection | RAN2 | LS in | Information | Yes |
Yes
| noted | No | ||||
S5‑252337 | Reply LS on signalling feasibility of dataset and parameter sharing | RAN2 | LS in | Information | Yes |
Yes
| postponed | No | ||||
S5‑252841 | Reply LS on signalling feasibility of dataset and parameter sharing | Nokia | LS out | approval | Yes |
Yes
| noted | No | ||||
S5‑252338 | LS on OAM-centric solution for NW-side data collection | RAN2 | LS in | Information | Yes |
Yes
| replied to | No | ||||
S5‑252339 | Reply LS on Number of UEs in RRC_INACTIVE state with data transmission | RAN2 | LS in | Information | Yes |
Yes
| postponed | No | ||||
S5‑252340 | LS on Ambient IoT further progress of RAN3 | RAN3 | LS in | Information | Yes |
Yes
| noted | No | ||||
S5‑252341 | LS on clarification on UE performance measurement at PDCP level | RAN3 | LS in | Information | Yes |
Yes
| replied to | No | ||||
S5‑252342 | Reply LS on ML Model provisioning by OAM to LMF for UE positioning | SA2 | LS in | Information | Yes |
Yes
| replied to | No | ||||
S5‑252343 | LS Reply on Ambient IoT progress of RAN3 | SA2 | LS in | Information | Yes |
Yes
| noted | No | ||||
S5‑252344 | Reply LS on MWAB-gNB Configurations | SA2 | LS in | Information | Yes |
Yes
| postponed | No | ||||
S5‑252345 | Reply LS on OAM requirements to support regenerative payload transport links (SA5#160) | RAN3 | LS in | Information | Yes |
Yes
| postponed | No | ||||
S5‑252347 | Liaison out to 3GPP SA5 on multi-dimensional network energy efficiency metrics | ETSI TC EE | LS in | Information | Yes |
Yes
| replied to | No | ||||
S5‑253014 | LS reply to TC EE on multi-dimensional network energy efficiency metrics | Huawei | LS out | approval | Yes |
Yes
| revised | No | S5‑253108 | |||
S5‑253108 | LS reply to TC EE on multi-dimensional network energy efficiency metrics | Huawei | LS out | approval | Yes |
Yes
| approved | No | S5‑253014 | |||
S5‑252351 | Liaison response to “Reply LS to ZSM Work on AI enablers and intent-driven autonomous networks" | ETSI ISG ZSM | LS in | Information | Yes |
Yes
| noted | No | ||||
S5‑252375 | Further reply LS on signalling feasibility of dataset and parameter sharing | Qualcomm Technologies | LS out | Approval | Yes |
Yes
| noted | No | ||||
S5‑252401 | Reply LS on signaling feasibility of dataset and parameter sharing | Samsung | LS out | Agreement | Yes |
Yes
| noted | No | ||||
S5‑252430 | Reply LS on ML Model provisioning by OAM to LMF for UE positioning | ZTE Corporation | LS out | Approval | Yes |
Yes
| revised | No | S5‑252843 | |||
S5‑252843 | Reply LS on ML Model provisioning by OAM to LMF for UE positioning | ZTE Corporation | LS out | Approval | Yes |
Yes
| revised | No | S5‑253091 | S5‑252430 | ||
S5‑253091 | Reply LS on ML Model provisioning by OAM to LMF for UE positioning | ZTE Corporation | LS out | Approval | Yes |
Yes
| approved | No | S5‑252843 | |||
S5‑252473 | DP Introduction of management and orchestration reference architecture in support of SBMA | NEC, Intel | discussion | Endorsement | No |
Yes
| withdrawn | Yes | ||||
S5‑252475 | Rel-19 CR TS 28.533 addition of management and orchestration reference architecture in support of SBMA | Intel, NEC | CR | Endorsement | Yes |
Yes
| not pursued | No | ||||
S5‑252483 | Reply LS to Reply LS on OAM requirements to support regenerative payload transport links | Huawei, CATT, China Unicom | LS out | Approval | Yes |
Yes
| noted | No | ||||
S5‑253024 | Reply LS on OAM requirements to support regenerative payload transport links | Huawei, CATT, China Unicom | LS out | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑252512 | Reply LS on clarification on UE performance measurement at PDCP level | ZTE Corporation | LS out | Approval | Yes |
Yes
| merged | No | S5‑252839 | |||
S5‑252570 | reply LS on OAM-centric solution for NW-side data collection | Huawei | LS out | Approval | Yes |
Yes
| revised | No | S5‑252842 | |||
S5‑252842 | Reply LS on OAM-centric solution for NW-side data collection | Huawei | LS out | Approval | Yes |
Yes
| approved | No | S5‑252570 | |||
S5‑252639 | Rel-19 CR TS 28.533 addition of management and orchestration reference architecture in support of SBMA | Intel, NEC | CR | Endorsement | Yes |
Yes
| withdrawn | Yes | ||||
S5‑252647 | Reply LS on signalling feasibility of dataset and parameter sharing | Ericsson Espańa S.A. | LS out | Approval | Yes |
Yes
| noted | No | ||||
S5‑252686 | Discussion Paper: Introduction of management and orchestration reference arc architecture in support of SBMA | NEC, Intel | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑253025 | |||
S5‑253025 | Discussion Paper: Introduction of management and orchestration reference arc architecture in support of SBMA | NEC, Intel, DTAG, NTT Docomo, China Unicom, Verizon, AT&T, ZTE, CATT, China Mobile, Rakuten Mobile, Huawei, China Telecom, ORANGE | discussion | Endorsement | Yes |
Yes
| noted | No | S5‑252686 | |||
S5‑252721 | Reply LS on signalling feasibility of dataset and parameter sharing | Nokia | LS out | Approval | Yes |
Yes
| noted | No | ||||
S5‑252722 | Discussion on AI-ML UE side data collection | Nokia | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑252723 | Reply LS on AI-ML UE side data collection | Nokia | LS out | Approval | Yes |
Yes
| noted | No | ||||
S5‑252724 | Reply LS on OAM-centric solution for NW-side data collection | Nokia | LS out | Approval | Yes |
Yes
| merged | No | S5‑252842 | |||
S5‑252725 | Reply LS on Number of UEs in RRC_INACTIVE state with data transmission | Nokia | LS out | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑252726 | Reply LS on clarification on UE performance measurement at PDCP level | Nokia | LS out | Approval | Yes |
Yes
| merged | No | S5‑252839 | |||
6.2 | New OAM&P Work Item proposals |   | ||||||||||
6.2.1 | Intelligence and Automation |   | ||||||||||
6.2.2 | Management Architecture and Mechanisms |   | ||||||||||
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‑252434 | Rel-17 CR TS 28.554 Clause 6.7.3.1 minor editorials | NTT DOCOMO | CR | Agreement | Yes |
Yes
| not pursued | No | ||
S5‑252435 | Rel-18 CR TS 28.554 Clause 6.7.3.1 minor editorials | NTT DOCOMO | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑252436 | Rel-19 CR TS 28.554 Clause 6.7.3.1 minor editorials | NTT DOCOMO | CR | Agreement | Yes |
Yes
| revised | No | S5‑252962 | |||
S5‑252962 | Rel-19 CR TS 28.554 Clause 6.7.3.1 minor editorials | NTT DOCOMO | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252436 | |||
S5‑252437 | Rel-18 CR TS 28.554 Clause 6.7.3.1 KPI name correction | NTT DOCOMO | CR | Agreement | Yes |
Yes
| revised | No | S5‑252963 | |||
S5‑252963 | Rel-18 CR TS 28.554 Clause 6.7.3.1 KPI name correction | NTT DOCOMO | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252437 | |||
S5‑252438 | Rel-19 CR TS 28.554 Clause 6.7.3.1 KPI name correction | NTT DOCOMO | CR | Agreement | Yes |
Yes
| revised | No | S5‑252964 | |||
S5‑252964 | Rel-19 CR TS 28.554 Clause 6.7.3.1 KPI name correction | NTT DOCOMO | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252438 | |||
S5‑252530 | Rel-17 CR TS 28.310 Clarify 6.2.1 overview | Ericsson, Deutsche Telekom | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑252531 | Rel-18 CR TS 28.310 Clarify 6.2.1 overview | Ericsson, Deutsche Telekom | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑252532 | Rel-19 CR TS 28.310 Clarify 6.2.1 overview | Ericsson, Deutsche Telekom | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑252715 | Incorporation of conclusions from TR 28.880 | Vodafone, Pairpoint | CR | Agreement | Yes |
Yes
| revised | No | S5‑253015 | |||
S5‑253015 | Incorporation of conclusions from TR 28.880 | Vodafone, Pairpoint | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252715 | |||
6.3.6 | Intent driven management |   | ||||||||||
6.3.7 | SON |   | ||||||||||
6.3.8 | QMC |   | ||||||||||
6.3.9 | Network slicing management |   | ||||||||||
6.3.10 | MEC management |   | ||||||||||
6.3.11 | General NRM | S5‑252684 | Rel-16 CR 28.662 Update sector equipment and antenna function definitions | Ericsson Canada Inc. | CR | Approval | Yes |
Yes
| revised | No | S5‑252903 | |
S5‑252903 | Rel-16 CR 28.662 Update sector equipment and antenna function definitions | Ericsson Canada Inc., Nokia, Nokia Shanghai Bell, Huawei, Samsung | CR | Approval | Yes |
Yes
| agreed | No | S5‑252684 | |||
S5‑252685 | Rel-17 CR 28.662 Update sector equipment and antenna function definitions | Ericsson Canada Inc. | CR | Approval | Yes |
Yes
| revised | No | S5‑252904 | |||
S5‑252904 | Rel-17 CR 28.662 Update sector equipment and antenna function definitions | Ericsson Canada Inc., Nokia, Nokia Shanghai Bell, Huawei, Samsung | CR | Approval | Yes |
Yes
| agreed | No | S5‑252685 | |||
S5‑252687 | Rel-18 CR 28.662 Update sector equipment and antenna function definitions | Ericsson Canada Inc. | CR | Approval | Yes |
Yes
| revised | No | S5‑252905 | |||
S5‑252905 | Rel-18 CR 28.662 Update sector equipment and antenna function definitions | Ericsson Canada Inc., Nokia, Nokia Shanghai Bell, Huawei, Samsung | CR | Approval | Yes |
Yes
| agreed | No | S5‑252687 | |||
S5‑252690 | Rel-16 CR 28.663 Update sector equipment and antenna function definitions | Ericsson Canada Inc. | CR | Approval | Yes |
Yes
| revised | No | S5‑252906 | |||
S5‑252906 | Rel-16 CR 28.663 Update sector equipment and antenna function definitions | Ericsson Canada Inc., Nokia, Nokia Shanghai Bell, Huawei, Samsung | CR | Approval | Yes |
Yes
| agreed | No | S5‑252690 | |||
S5‑252691 | Rel-17 CR 28.663 Update sector equipment and antenna function definitions | Ericsson Canada Inc. | CR | Approval | Yes |
Yes
| revised | No | S5‑252907 | |||
S5‑252907 | Rel-17 CR 28.663 Update sector equipment and antenna function definitions | Ericsson Canada Inc., Nokia, Nokia Shanghai Bell, Huawei, Samsung | CR | Approval | Yes |
Yes
| agreed | No | S5‑252691 | |||
S5‑252692 | Rel-18 CR 28.663 Update sector equipment and antenna function definitions | Ericsson Canada Inc. | CR | Approval | Yes |
Yes
| revised | No | S5‑252908 | |||
S5‑252908 | Rel-18 CR 28.663 Update sector equipment and antenna function definitions | Ericsson Canada Inc., Nokia, Nokia Shanghai Bell, Huawei, Samsung | CR | Approval | Yes |
Yes
| agreed | No | S5‑252692 | |||
S5‑252693 | Rel-19 CR 28.541 Update sector equipment and antenna function definitions | Ericsson Canada Inc. | CR | Approval | Yes |
Yes
| revised | No | S5‑252909 | |||
S5‑252909 | Rel-19 CR 28.541 Update sector equipment and antenna function definitions | Ericsson Canada Inc., Nokia, Nokia Shanghai Bell, Huawei, Samsung | CR | Approval | Yes |
Yes
| agreed | No | S5‑252693 | |||
S5‑252694 | Rel-16 CR 28.541 Update sector equipment and antenna function definitions | Ericsson Canada Inc. | CR | Approval | Yes |
Yes
| revised | No | S5‑252910 | |||
S5‑252910 | Rel-16 CR 28.541 Update sector equipment and antenna function definitions | Ericsson Canada Inc., Nokia, Nokia Shanghai Bell, Huawei, Samsung | CR | Approval | Yes |
Yes
| agreed | No | S5‑252694 | |||
S5‑252695 | Rel-17 CR 28.541 Update sector equipment and antenna function definitions | Ericsson Canada Inc. | CR | Approval | Yes |
Yes
| revised | No | S5‑252911 | |||
S5‑252911 | Rel-17 CR 28.541 Update sector equipment and antenna function definitions | Ericsson Canada Inc., Nokia, Nokia Shanghai Bell, Huawei, Samsung | CR | Approval | Yes |
Yes
| agreed | No | S5‑252695 | |||
S5‑252696 | Rel-18 CR 28.541 Update sector equipment and antenna function definitions | Ericsson Canada Inc. | CR | Approval | Yes |
Yes
| revised | No | S5‑252912 | |||
S5‑252912 | Rel-18 CR 28.541 Update sector equipment and antenna function definitions | Ericsson Canada Inc., Nokia, Nokia Shanghai Bell, Huawei, Samsung | CR | Approval | Yes |
Yes
| agreed | No | S5‑252696 | |||
S5‑252718 | Rel-16 CR 28.623 Update sector equipment and antenna function definitions (stage3, yang) | Ericsson Canada Inc. | CR | Approval | Yes |
Yes
| merged | No | S5‑252910 | |||
6.3.12 | PM/KPI | S5‑252574 | Rel-16 CR TS 28.554 Update the KPI definitions template | Huawei, Ericsson, China Telecom | CR | Agreement | Yes |
Yes
| revised | No | S5‑252965 | |
S5‑252965 | Rel-16 CR TS 28.554 Update the KPI definitions template | Huawei, Ericsson, China Telecom | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252574 | |||
S5‑252575 | Rel-17 CR TS 28.554 Update the KPI definitions template | Huawei, Ericsson, China Telecom | CR | Agreement | Yes |
Yes
| revised | No | S5‑252966 | |||
S5‑252966 | Rel-17 CR TS 28.554 Update the KPI definitions template | Huawei, Ericsson, China Telecom | CR | Agreement | Yes |
Yes
| revised | No | S5‑253087 | S5‑252575 | ||
S5‑253087 | Rel-17 CR TS 28.554 Update the KPI definitions template | Huawei, Ericsson, China Telecom | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252966 | |||
S5‑252576 | Rel-18 CR TS 28.554 Update the KPI definitions template | Huawei, Ericsson, China Telecom | CR | Agreement | Yes |
Yes
| revised | No | S5‑252967 | |||
S5‑252967 | Rel-18 CR TS 28.554 Update the KPI definitions template | Huawei, Ericsson, China Telecom | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252576 | |||
S5‑252577 | Rel-19 CR TS 28.554 Update the KPI definitions template | Huawei, Ericsson, China Telecom | CR | Agreement | Yes |
Yes
| revised | No | S5‑252968 | |||
S5‑252968 | Rel-19 CR TS 28.554 Update the KPI definitions template | Huawei, Ericsson, China Telecom | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252577 | |||
6.3.13 | Trace/MDT | S5‑252231 | Rel-16 CR TS 28.622 Corrections on MDT PLMN List | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑252969 | |
S5‑252969 | Rel-16 CR TS 28.622 Corrections on MDT PLMN List | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252231 | |||
S5‑252232 | Rel-17 CR TS 28.622 Corrections on MDT PLMN List | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑252970 | |||
S5‑252970 | Rel-17 CR TS 28.622 Corrections on MDT PLMN List | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252232 | |||
S5‑252233 | Rel-18 CR TS 28.622 Corrections on MDT PLMN List | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑252971 | |||
S5‑252971 | Rel-18 CR TS 28.622 Corrections on MDT PLMN List | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252233 | |||
S5‑252234 | Rel-19 CR TS 28.622 Corrections on MDT PLMN List | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑252972 | |||
S5‑252972 | Rel-19 CR TS 28.622 Corrections on MDT PLMN List | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252234 | |||
S5‑252235 | Rel-16 CR TS 28.623 Corrections on MDT PLMN List | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑252973 | |||
S5‑252973 | Rel-16 CR TS 28.623 Corrections on MDT PLMN List | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252235 | |||
S5‑252236 | Rel-17 CR TS 28.623 Corrections on MDT PLMN List | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑252974 | |||
S5‑252974 | Rel-17 CR TS 28.623 Corrections on MDT PLMN List | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252236 | |||
S5‑252237 | Rel-18 CR TS 28.623 Corrections on MDT PLMN List | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑252975 | |||
S5‑252975 | Rel-18 CR TS 28.623 Corrections on MDT PLMN List | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252237 | |||
S5‑252238 | Rel-19 CR TS 28.623 Corrections on MDT PLMN List | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑252976 | |||
S5‑252976 | Rel-19 CR TS 28.623 Corrections on MDT PLMN List | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252238 | |||
S5‑252239 | Rel-16 CR TS 32.422 Corrections on MDT PLMN List | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑252977 | |||
S5‑252977 | Rel-16 CR TS 32.422 Corrections on MDT PLMN List | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252239 | |||
S5‑252240 | Rel-17 CR TS 32.422 Corrections on MDT PLMN List | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑252978 | |||
S5‑252978 | Rel-17 CR TS 32.422 Corrections on MDT PLMN List | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252240 | |||
S5‑252241 | Rel-18 CR TS 32.422 Corrections on MDT PLMN List | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑252979 | |||
S5‑252979 | Rel-18 CR TS 32.422 Corrections on MDT PLMN List | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252241 | |||
S5‑252242 | Rel-19 CR TS 32.422 Corrections on MDT PLMN List | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑252980 | |||
S5‑252980 | Rel-19 CR TS 32.422 Corrections on MDT PLMN List | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252242 | |||
S5‑252243 | Rel-16 CR TS 28.622 Corrections on Triggering Event | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑252244 | Rel-17 CR TS 28.622 Corrections on Triggering Event | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑252245 | Rel-18 CR TS 28.622 Corrections on Triggering Event | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑252246 | Rel-19 CR TS 28.622 Corrections on Triggering Event | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑252247 | Rel-16 CR TS 32.423 Corrections on Trace Reference | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑252981 | |||
S5‑252981 | Rel-16 CR TS 32.423 Corrections on Trace Reference | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252247 | |||
S5‑252248 | Rel-17 CR TS 32.423 Corrections on Trace Reference | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑252982 | |||
S5‑252982 | Rel-17 CR TS 32.423 Corrections on Trace Reference | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252248 | |||
S5‑252249 | Rel-18 CR TS 32.423 Corrections on Trace Reference | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑252983 | |||
S5‑252983 | Rel-18 CR TS 32.423 Corrections on Trace Reference | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252249 | |||
S5‑252250 | Rel-19 CR TS 32.423 Corrections on Trace Reference | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑252984 | |||
S5‑252984 | Rel-19 CR TS 32.423 Corrections on Trace Reference | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252250 | |||
S5‑252251 | Rel-16 CR TS 28.622 Corrections on Trace Target | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑252252 | Rel-17 CR TS 28.622 Corrections on Trace Target | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑252253 | Rel-18 CR TS 28.622 Corrections on Trace Target | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑252254 | Rel-19 CR TS 28.622 Corrections on Trace Target | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑253060 | |||
S5‑253060 | Rel-19 CR TS 28.622 Corrections on Trace Target | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252254 | |||
S5‑252255 | Rel-16 CR TS 28.623 Corrections on Trace Target | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑252256 | Rel-17 CR TS 28.623 Corrections on Trace Target | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑252257 | Rel-18 CR TS 28.623 Corrections on Trace Target | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑252258 | Rel-19 CR TS 28.623 Corrections on Trace Target | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑253061 | |||
S5‑253061 | Rel-19 CR TS 28.623 Corrections on Trace Target | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252258 | |||
S5‑252605 | Rel-19 CR TS28.622 Corrections for MdtConfig | ZTE Corporation | CR | Agreement | Yes |
Yes
| withdrawn | Yes | ||||
S5‑252711 | Rel-16 CR TS32.422 Fix wrong IE in Initial Context Setup Request for MDT activation | ZTE Corporation | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑252712 | Rel-17 CR TS32.422 Fix wrong IE in Initial Context Setup Request for MDT activation | ZTE Corporation | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑252713 | Rel-18 CR TS32.422 Fix wrong IE in Initial Context Setup Request for MDT activation | ZTE Corporation | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑252714 | Rel-19 CR TS32.422 Fix wrong IE in Initial Context Setup Request for MDT activation | ZTE Corporation | CR | Agreement | Yes |
Yes
| revised | No | S5‑253062 | |||
S5‑253062 | Rel-19 CR TS32.422 Fix wrong IE in Initial Context Setup Request for MDT activation | ZTE Corporation | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252714 | |||
6.3.14 | Other |   | ||||||||||
6.4 | Rel-18 Maintenance and Rel-19 small Enhancements |   | ||||||||||
6.4.1 | Self-Configuration of RAN NEs |   | ||||||||||
6.4.2 | Management Data Analytics phase 2 |   | ||||||||||
6.4.3 | AI/ML management | S5‑252439 | Rel-18 CR TS 28.105 Correction on the isWritable propoerty of AIMLInferenceName in the MLTrainingRequest | ZTE Corporation, Intel, Huawei | CR | Agreement | Yes |
Yes
| withdrawn | Yes | ||
S5‑252440 | Rel-19 CR TS 28.105 Correction on the isWritable propoerty of AIMLInferenceName in the MLTrainingRequest | ZTE Corporation, Intel, Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑252443 | Rel-18 CR TS 28.105 Correction on the isWritable propoerty of AIMLInferenceName in the MLTrainingRequest | ZTE Corporation, Intel, Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
6.4.4 | Intent driven Management Service for mobile network phase 2 |   | ||||||||||
6.4.5 | Service based management architecture | S5‑252454 | Rel-18 CR 32.161 JEX EBNF corrections | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| revised | No | S5‑253027 | |
S5‑253027 | Rel-18 CR 32.161 JEX EBNF corrections | Ericsson Hungary Ltd, Nokia | CR | Approval | Yes |
Yes
| agreed | No | S5‑252454 | |||
S5‑252476 | Rel-18 CR TS 28.111 Stage 3 YAML for ThresholdCrossing dataType | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑253028 | |||
S5‑253028 | Rel-18 CR TS 28.111 Stage 3 YAML for ThresholdCrossing dataType | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252476 | |||
S5‑252477 | Rel-19 CR TS 28.111 Stage 3 YAML for ThresholdCrossing dataType | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑253029 | |||
S5‑253029 | Rel-19 CR TS 28.111 Stage 3 YAML for ThresholdCrossing dataType | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252477 | |||
S5‑252646 | Rel-19 CR 28.533 Clarify combination of MnS components | Nokia | CR | Agreement | Yes |
Yes
| revised | No | S5‑253030 | |||
S5‑253030 | Rel-19 CR 28.533 Clarify combination of MnS components | Nokia | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252646 | |||
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‑252267 | Rel-18 CR TS 28.552 corrections on filter value encoding | Ericsson, Rakuten Mobile, AT&T | CR | Agreement | Yes |
Yes
| not pursued | No | ||
S5‑252268 | Rel-19 CR TS 28.552 corrections on filter value encoding | Ericsson, Rakuten Mobile, AT&T | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑252474 | Rel-19 CR TS 28.558 Add the missing measured UE identifier for UE Data Volume | China Unicom | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑253031 | Rel-19 CR TS 28.558 Add the missing measured UE identifier for UE Data Volume | China Unicom | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
6.4.10 | Enhancement of QoE Measurement Collection |   | ||||||||||
6.4.11 | Additional NRM features phase 2 | S5‑252461 | Rel 18 CR TS 28.532 correct the format of input parameters define in stage 3 to align with stage 2 | Huawei | CR | Approval | No |
Yes
| withdrawn | Yes | ||
S5‑252533 | Rel-19 CR 28.541 Align predefinedPccRuleSet attributes with the definitions in TS 29.512 | Ericsson | CR | Approval | Yes |
Yes
| revised | No | S5‑253034 | S5‑252080 | ||
S5‑253034 | Rel-19 CR 28.541 Align predefinedPccRuleSet attributes with the definitions in TS 29.512 | Ericsson | CR | Approval | Yes |
Yes
| agreed | No | S5‑252533 | |||
S5‑252579 | Rel-18 CR TS 28.702 Correct the property of some attributes | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑252588 | Rel-18 CR TS28.541 Fix stage 3 related to DnnUpfInfoItem | ZTE Corporation | CR | Agreement | Yes |
Yes
| revised | No | S5‑253032 | |||
S5‑253032 | Rel-18 CR TS28.541 Fix stage 3 related to DnnUpfInfoItem | ZTE Corporation, Nokia | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252588 | |||
S5‑252589 | Rel-19 CR TS28.541 Fix stage 3 related to DnnUpfInfoItem | ZTE Corporation | CR | Agreement | Yes |
Yes
| revised | No | S5‑253033 | |||
S5‑253033 | Rel-19 CR TS28.541 Fix stage 3 related to DnnUpfInfoItem | ZTE Corporation, Nokia | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252589 | |||
6.4.12 | Management Aspects related to NWDAF |   | ||||||||||
6.4.13 | Enhanced Edge Computing Management |   | ||||||||||
6.4.14 | Management Aspect of 5GLAN |   | ||||||||||
6.4.15 | Management Aspects of NTN | S5‑252590 | Rel-18 CR TS28.541 Fix nTNGlobalRanNodeID for stage 3 OpenAPI | ZTE Corporation | CR | Agreement | No |
Yes
| withdrawn | Yes | ||
S5‑252591 | Rel-19 CR TS28.541 Fix nTNGlobalRanNodeID for stage 3 OpenAPI | ZTE Corporation | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
6.4.16 | methodology for deprecation |   | ||||||||||
6.4.17 | Management of cloud-native Virtualized Network Functions |   | ||||||||||
6.4.18 | Management Aspects of 5G Network Sharing Phase2 |   | ||||||||||
6.4.19 | Management Aspects of URLLC |   | ||||||||||
6.4.20 | Management aspects of 5G system supporting satellite backhaul |   | ||||||||||
6.4.21 | Access control for management service |   | ||||||||||
6.4.22 | Enhancements of EE for 5G Phase 2 |   | ||||||||||
6.4.23 | Management of non-public networks phase 2 |   | ||||||||||
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‑252222 | Rel-18 CR 28.623 YANG stage-3 corrections | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| revised | No | S5‑253035 | |
S5‑253035 | Rel-18 CR 28.623 YANG stage-3 corrections | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| agreed | No | S5‑252222 | |||
S5‑252223 | Rel-18 CR 28.541 YANG stage-3 corrections | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| revised | No | S5‑253036 | |||
S5‑253036 | Rel-18 CR 28.541 YANG stage-3 corrections | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| agreed | No | S5‑252223 | |||
S5‑252224 | Rel-19 CR 28.623 YANG stage-3 corrections | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| revised | No | S5‑253037 | |||
S5‑253037 | Rel-19 CR 28.623 YANG stage-3 corrections | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| agreed | No | S5‑252224 | |||
S5‑252225 | Rel-19 CR 28.541 YANG stage-3 corrections | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| revised | No | S5‑253038 | |||
S5‑253038 | Rel-19 CR 28.541 YANG stage-3 corrections | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| agreed | No | S5‑252225 | |||
S5‑252266 | Rel-18 CR TS 32.404 Corrections on measurement name size | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑253039 | S5‑251233 | ||
S5‑253039 | Rel-18 CR TS 32.404 Corrections on measurement name size | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252266 | |||
S5‑252276 | Rel-19 CR 32.156 Deprecate isNullable property | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑253042 | Rel-19 CR 32.156 Deprecate isNullable property | Ericsson Hungary Ltd | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑252277 | Rel-18 CR 28.111 Clarify alarmType | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| revised | No | S5‑253043 | |||
S5‑253043 | Rel-18 CR 28.111 Clarify alarmType | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| agreed | No | S5‑252277 | |||
S5‑252278 | Rel-19 CR 28.111 Clarify alarmType | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| revised | No | S5‑253044 | |||
S5‑253044 | Rel-19 CR 28.111 Clarify alarmType | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| agreed | No | S5‑252278 | |||
S5‑252282 | Rel-18 CR 32.156 Clarify usage of DN type | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| revised | No | S5‑253045 | |||
S5‑253045 | Rel-18 CR 32.156 Clarify usage of DN type | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| not pursued | No | S5‑252282 | |||
S5‑252283 | Rel-19 CR 32.156 Clarify usage of DN type | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| revised | No | S5‑253046 | |||
S5‑253046 | Rel-19 CR 32.156 Clarify usage of DN type | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| not pursued | No | S5‑252283 | |||
S5‑252286 | DP Deprecate isNullable property | Ericsson Hungary Ltd | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑253041 | |||
S5‑253041 | DP Deprecate isNullable property | Ericsson Hungary Ltd | discussion | Endorsement | Yes |
Yes
| noted | No | S5‑252286 | |||
S5‑252456 | Rel-18 CR TS 28.111 Correction on Alarm Definition | NTT DOCOMO, Huawei, Nokia, Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑252457 | Rel-19 CR TS 28.111 Correction on Alarm Definition | NTT DOCOMO, Huawei, Nokia, Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑252608 | Rel-18 CR 28.622 Fix missing and duplicate attributes from earlier CR | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
6.4.27 | OAM Rel-19 small enhancements | S5‑252265 | Rel-19 CR TS 28.560 Corrections on STM NRM | Ericsson, Vodafone | CR | Agreement | Yes |
YesIf this CR is agreed, S5-252085, S5-252087, S5-252089 from SA5#160 shall be not pursued.
| revised | No | S5‑253047 | |
S5‑253047 | Rel-19 CR TS 28.560 Corrections on STM NRM | Ericsson, Vodafone, Samsung | CR | Agreement | Yes |
YesIf this CR is agreed, S5-252085, S5-252087, S5-252089 from SA5#160 shall be not pursued.
| revised | No | S5‑253088 | S5‑252265 | ||
S5‑253088 | Rel-19 CR TS 28.560 Corrections on STM NRM | Ericsson, Vodafone, Samsung | CR | Agreement | Yes |
YesIf this CR is agreed, S5-252085, S5-252087, S5-252089 from SA5#160 shall be not pursued.
| agreed | No | S5‑253047 | |||
S5‑252271 | Rel-19 CR 28.560 Rename YANG module for stmfunction | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑252272 | Rel-19 CR 28.623 Rename YANG module for stmfunction | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑252300 | Rel-19 CR TS 28.622 Update Attribute definition for TimeWindow | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑253048 | S5‑252094 | ||
S5‑253048 | Rel-19 CR TS 28.622 Update Attribute definition for TimeWindow | Huawei, Nokia | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252300 | |||
S5‑252301 | Rel-19 CR TS 28.623 Update Attribute definition for TimeWindow | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑253049 | |||
S5‑253049 | Rel-19 CR TS 28.623 Update Attribute definition for TimeWindow | Huawei, Nokia | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252301 | |||
S5‑252305 | Rel-19 CR TS 28.537 Correct procedures for heartbeat | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑253050 | S5‑251391 | ||
S5‑253050 | Rel-19 CR TS 28.537 Correct procedures for heartbeat | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252305 | |||
S5‑252392 | Rel-19 CR TS 28.532 Implement HTTP POST method for createMOI operation | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑252631 | |||
S5‑252450 | Rel-19 CR TS 28.622 Miscellaneous Corrections | Nokia | CR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑252451 |
Rel-19 CR TS 28.622 Update TimeWindow < | Nokia | CR | Approval | Yes |
Yes
| merged | No | S5‑253048 | |||
S5‑252462 | Rel 19 CR TS 28.532 correct the format of input parameters define in stage 3 to align with stage 2 | Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑253052 | |||
S5‑253052 | Rel 19 CR TS 28.532 correct the format of input parameters define in stage 3 to align with stage 2 | Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑253089 | S5‑252462 | ||
S5‑253089 | Rel 19 CR TS 28.532 correct the format of input parameters define in stage 3 to align with stage 2 | Huawei | CR | Approval | Yes |
Yes
| agreed | No | S5‑253052 | |||
S5‑252492 | Rel-19 TS 28.312 Add qualifier description for coverageAreaTAContext | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑252555 | DP on new specification regarding resilient intent | NTT DOCOMO INC.. | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑253059 | |||
S5‑253059 | DP on the issue of updating Time-related Context for Intent Expectation | NTT DOCOMO INC.. | discussion | Endorsement | Yes |
Yes
| noted | No | S5‑252555 | |||
S5‑252595 | Rel-19 CR TS 28.111 Correction on reliability of alarm lists | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑253053 | |||
S5‑253053 | Rel-19 CR TS 28.111 Correction on reliability of alarm lists | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252595 | |||
S5‑252598 | Rel-19 CR TS 28.111 Add missing NRM info for the component | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑253054 | Rel-19 CR TS 28.111 Add missing NRM info for the component | Huawei | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
S5‑252631 | Rel-19 CR TS 28.532 Implement HTTP POST method for createMOI operation | Huawei,Deutsche Telekom | CR | Agreement | Yes |
Yes
| revised | No | S5‑253051 | S5‑252392 | ||
S5‑253051 | Rel-19 CR TS 28.532 Implement HTTP POST method for createMOI operation | Huawei, Deutsche Telekom, Nokia | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252631 | |||
S5‑252633 | Rel-19 TS 28.541 Correction on wrong attribute property definition | Ericsson LM | CR | Approval | Yes |
Yes
| revised | No | S5‑253055 | |||
S5‑253055 | Rel-19 TS 28.541 Correction on wrong attribute property definition | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | S5‑252633 | |||
S5‑252643 | Rel 19 CR TS 28.104 correct allowedValues for reportingMethod | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑253056 | |||
S5‑253056 | Rel 19 CR TS 28.104 correct allowedValues for reportingMethod | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252643 | |||
S5‑252644 | Rel 19 CR TS 28.319 Corrections to attribute properties table | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑253057 | |||
S5‑253057 | Rel 19 CR TS 28.319 Corrections to attribute properties table | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252644 | |||
S5‑252645 | Rel 19 CR TS 28.662 Remove Support Qualifier from attribute constraints | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑253058 | Rel 19 CR TS 28.662 Remove Support Qualifier from attribute constraints | Ericsson | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
S5‑252889 | Rel-19 CR TS 28.541 Correction on wrong attribute property definition | CATT | CR | Agreement | Yes |
Yes
| agreed | No | ||||
6.19 | OAM&P Rel-19 Study and Work Items |   | ||||||||||
6.19.1 | Study on AI/ML management - phase 2 (completed) |   | ||||||||||
6.19.1.1 | AI/ML management phase 2 | S5‑252355 | Input to draftCR TS28.105 AIML emulation environment | Nokia | other | Approval | Yes |
Yes
| revised | No | S5‑252994 | |
S5‑252994 | Input to draftCR TS28.105 AIML emulation environment | Nokia | other | Approval | Yes |
Yes
| noted | No | S5‑252355 | |||
S5‑252386 | Input to draftCR Rel19 TS 28.105 Use case on model confidence requirement | Nokia, Nokia Shanghai Bell | other | Approval | Yes |
Yes
| revised | No | S5‑252986 | |||
S5‑252986 | Input to draftCR Rel19 TS 28.105 Use case on model confidence requirement | Nokia, Nokia Shanghai Bell | other | Approval | Yes |
Yes
| noted | No | S5‑252386 | |||
S5‑252387 | Input to draftCR Rel19 TS 28.105 Solution on model confidence requirement | Nokia, Nokia Shanghai Bell | other | Approval | Yes |
Yes
| noted | No | ||||
S5‑252388 | Input to draftCR Rel19 TS 28.105 Use case and solution on sustainable AIML Inference | Nokia, Nokia Shanghai Bell | other | Approval | Yes |
Yes
| revised | No | S5‑252995 | |||
S5‑252995 | Input to draftCR Rel19 TS 28.105 Use case and solution on sustainable AIML Inference | Nokia, Nokia Shanghai Bell | other | Approval | Yes |
Yes
| noted | No | S5‑252388 | |||
S5‑252389 | Input to draftCR Rel19 TS 28.105 Use case and solution on sustainable AIML training | Nokia, Nokia Shanghai Bell | other | Approval | Yes |
Yes
| revised | No | S5‑252829 | |||
S5‑252829 | Input to draftCR Rel19 TS 28.105 Use case and solution on sustainable AIML training | Nokia, Nokia Shanghai Bell | other | Approval | Yes |
Yes
| noted | No | S5‑252389 | |||
S5‑252390 | Input to DraftCR Rel19 TS28.105 New use case on Coordination between the ML capabilities | Nokia, Nokia Shanghai Bell, China mobile, TELUS | other | Approval | Yes |
Yes
| revised | No | S5‑252999 | |||
S5‑252999 | Input to DraftCR Rel19 TS28.105 New use case on Coordination between the ML capabilities | Nokia, Nokia Shanghai Bell, China mobile, TELUS | other | Approval | Yes |
Yes
| noted | No | S5‑252390 | |||
S5‑252422 | Input to draftCR Rel-19 TS 28.105 add use case on AIML prediction latency in training | China Mobile, Nokia, Nokia Shanghai Bell | other | Approval | Yes |
Yes
| revised | No | S5‑252835 | |||
S5‑252835 | Input to draftCR Rel-19 TS 28.105 add use case on AIML prediction latency in training | China Mobile, Nokia, Nokia Shanghai Bell | other | Approval | Yes |
Yes
| noted | No | S5‑252422 | |||
S5‑252423 | Input to draftCR Rel-19 TS 28.105 add use case on AIML prediction latency in inference | China Mobile, Nokia, Nokia Shanghai Bell | other | Approval | Yes |
Yes
| not treated | No | ||||
S5‑252424 | Input to draftCR Rel-19 TS 28.105 add use case for Management of explanation in AIML training | China Mobile, Nokia, Nokia Shanghai Bell, Huawei | other | Approval | Yes |
Yes
| revised | No | S5‑252830 | |||
S5‑252830 | Input to draftCR Rel-19 TS 28.105 add use case for Management of explanation in AIML training | China Mobile, Nokia, Nokia Shanghai Bell, Huawei | other | Approval | Yes |
Yes
| noted | No | S5‑252424 | |||
S5‑252425 | Input to draftCR Rel-19 TS 28.105 add solution for Management of explanation in AIML training | China Mobile, Nokia, Nokia Shanghai Bell | other | Approval | Yes |
Yes
| revised | No | S5‑252831 | |||
S5‑252831 | Input to draftCR Rel-19 TS 28.105 add solution for Management of explanation in AIML training | China Mobile, Nokia, Nokia Shanghai Bell | other | Approval | Yes |
Yes
| noted | No | S5‑252425 | |||
S5‑252426 | Input to draftCR Rel-19 TS 28.105 add solution for AIML prediction latency in training | China Mobile, Nokia, Nokia Shanghai Bell | other | Approval | Yes |
Yes
| not treated | No | ||||
S5‑252427 | Input to draftCR Rel-19 TS 28.105 add solution for AIML prediction latency in inference | China Mobile, Nokia, Nokia Shanghai Bell | other | Approval | Yes |
Yes
| not treated | No | ||||
S5‑252431 | Input to DraftCR Rel-19 TS 28.105 Enhancement on AIMLSupportedFunction to support inference in LMF | ZTE Corporation | other | Agreement | Yes |
Yes
| revised | No | S5‑252988 | |||
S5‑252988 | Input to DraftCR Rel-19 TS 28.105 Enhancement on AIMLSupportedFunction to support inference in LMF | ZTE Corporation, Ericsson | other | Agreement | Yes |
Yes
| approved | No | S5‑252431 | |||
S5‑252432 | Rel-19 CR TS 28.541 Enhancement on LMF NRM to Support the Inference Functionality in LMF | ZTE Corporation | CR | Agreement | Yes |
Yes
| revised | No | S5‑252989 | |||
S5‑252989 | Rel-19 CR TS 28.541 Enhancement on LMF NRM to Support the Inference Functionality in LMF | ZTE Corporation, Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑253090 | S5‑252432 | ||
S5‑253090 | Rel-19 CR TS 28.541 Enhancement on LMF NRM to Support the Inference Functionality in LMF | ZTE Corporation | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252989 | |||
S5‑252441 | Input to DraftCR Rel-19 TS 28.105 Add Management Scenario for RL | ZTE Corporation | other | Agreement | Yes |
Yes
| not treated | No | ||||
S5‑252458 | Input to draftCR TS 28.105 Add NRMs on LCM for Federated Learning | Intel, NEC, ZTE, Samsung, Nokia | other | Approval | Yes |
Yes
| revised | No | S5‑252832 | |||
S5‑252832 | Input to draftCR TS 28.105 Add NRMs on LCM for Federated Learning | Intel, NEC, ZTE, Samsung, Nokia | other | Approval | Yes |
Yes
| noted | No | S5‑252458 | |||
S5‑252459 | Input to draftCR TS 28.105 Enhance UC for management of Reinforcement Learning | Intel, NEC | other | Approval | Yes |
Yes
| revised | No | S5‑252833 | |||
S5‑252833 | Input to draftCR TS 28.105 Enhance UC for management of Reinforcement Learning | Intel, NEC | other | Approval | Yes |
Yes
| revised | No | S5‑253092 | S5‑252459 | ||
S5‑253092 | Input to draftCR TS 28.105 Enhance UC for management of Reinforcement Learning | Intel, NEC | other | Approval | Yes |
Yes
| approved | No | S5‑252833 | |||
S5‑252460 | Input to draftCR TS 28.105 Add NRMs on LCM for Reinforcement Learning | Intel, ZTE, NEC | other | Approval | Yes |
Yes
| merged | No | S5‑252834 | |||
S5‑252463 | Rel-19 InputToDraftCR TS 28.105 add procedure of management of AIML capabilities for NG-RAN and MDA | Huawei | CR | Approval | Yes |
YesWrong type of Tdoc?
| revised | No | S5‑252523 | |||
S5‑252464 | Rel-19 InputToDraftCR TS 28.105 add solution for exploration in reinforcement learning | Huawei | CR | Approval | Yes |
YesWrong type of Tdoc?
| revised | No | S5‑252524 | |||
S5‑252465 | Rel-19 InputToDraftCR TS 28.105 add use case for Management of explanation in AIML inference | Huawei | CR | Approval | Yes |
YesWrong type of Tdoc?
| revised | No | S5‑252525 | |||
S5‑252466 | Rel-19 InputToDraftCR TS 28.105 add solution for Management of explanation in AIML inference | Huawei | CR | Approval | Yes |
YesWrong type of Tdoc?
| revised | No | S5‑252526 | |||
S5‑252467 | Rel-19 InputToDraftCR TS 28.105 enhance the description for managing AIML based capabilities | Huawei | CR | Approval | Yes |
YesWrong type of Tdoc?
| revised | No | S5‑252527 | |||
S5‑252468 | Rel-19 InputToDraftCR TS 28.105 update the ML model lifecycle management capabilities | Huawei | CR | Approval | Yes |
YesWrong type of Tdoc?
| revised | No | S5‑252528 | |||
S5‑252523 | Input to draftCR TS 28.105 for add procedure of management of AIML capabilities for NG-RAN and MDA | Huawei | other | Approval | Yes |
Yes
| not treated | No | S5‑252463 | |||
S5‑252524 | Input to draftCR TS 28.105 for add solution for exploration in reinforcement learning | Huawei, Samsung | other | Approval | Yes |
Yes
| revised | No | S5‑252834 | S5‑252464 | ||
S5‑252834 | Input to draftCR TS 28.105 for add solution for exploration in reinforcement learning | Huawei,Samsung,NEC,Nokia,ZTE | other | Approval | Yes |
Yes
| revised | No | S5‑253107 | S5‑252524 | ||
S5‑253107 | Input to draftCR TS 28.105 for add solution for exploration in reinforcement learning | Huawei,Samsung,NEC,Nokia,ZTE | other | Approval | Yes |
Yes
| approved | No | S5‑252834 | |||
S5‑252525 | Input to draftCR TS 28.105 for add use case for Management of explanation in AIML inference | Huawei, Orange, CMCC, Nokia, Verizon, NTT DOCOMO, Deutsche Telekom | other | Approval | Yes |
Yes
| revised | No | S5‑252996 | S5‑252465 | ||
S5‑252996 | Input to draftCR TS 28.105 for add use case for Management of explanation in AIML inference | HUAWEI, Orange, CMCC, Nokia, Verizon, NTT DOCOMO, Deutsche Telekom, Ericsson, NEC | other | Approval | Yes |
Yes
| approved | No | S5‑252525 | |||
S5‑252526 | Input to draftCR TS 28.105 for add solution for Management of explanation in AIML inference | Huawei, Orange, Deutsche Telekom | other | Approval | Yes |
Yes
| revised | No | S5‑252997 | S5‑252466 | ||
S5‑252997 | Input to draftCR TS 28.105 for add solution for Management of explanation in AIML inference | HUAWEI, Orange, Deutsche Telekom, Ericsson,Nokia,Nokia Shanghai Bell | other | Approval | Yes |
Yes
| approved | No | S5‑252526 | |||
S5‑252527 | Input to draftCR TS 28.105 for enhance the description for managing AIML based capabilities | Huawei | other | Approval | Yes |
Yes
| not treated | No | S5‑252467 | |||
S5‑252528 | Input to draftCR TS 28.105 for update the ML model lifecycle management capabilities | Huawei | other | Approval | Yes |
Yes
| not treated | No | S5‑252468 | |||
S5‑252556 | Input to draftCR TS 28.105 Pre-specialised training and Fine-tuning use cases | NEC, Intel, China Mobile, ZTE, Huawei | other | Approval | Yes |
Yes
| revised | No | S5‑252828 | |||
S5‑252828 | Input to draftCR TS 28.105 Pre-specialised training and Fine-tuning use cases | NEC, Intel, China Mobile, ZTE, Huawei | other | Approval | Yes |
Yes
| approved | No | S5‑252556 | |||
S5‑252557 | DraftCR Rel-19 TS 28.105 AIML management – phase 2 | NEC, Intel | draftCR | Information | Yes |
YesApproved as baseline for this meeting.
| approved | No | ||||
S5‑252559 | Input to DraftCR Rel-19 TS 28.105 Add Procedure for ML Model Training | ZTE Corporation | other | Agreement | Yes |
Yes
| noted | No | ||||
S5‑252560 | Input to DraftCR Rel-19 TS 28.105 Update on the use case of managing ML models in use in a live network | ZTE Corporation | other | Agreement | Yes |
Yes
| revised | No | S5‑252998 | |||
S5‑252998 | Input to DraftCR Rel-19 TS 28.105 Update on the use case of managing ML models in use in a live network | ZTE Corporation | other | Agreement | Yes |
Yes
| revised | No | S5‑253104 | S5‑252560 | ||
S5‑253104 | Input to DraftCR Rel-19 TS 28.105 Update on the use case of managing ML models in use in a live network | ZTE Corporation | other | Agreement | Yes |
Yes
| approved | No | S5‑252998 | |||
S5‑252561 | DP on the NRM Design for AIMLInferenceFunction | ZTE Corporation | discussion | Agreement | Yes |
Yes
| not treated | No | ||||
S5‑252562 | Input to DraftCR Rel-19 TS 28.105 Enhancement on AIMLInferenceFunction NRM | ZTE Corporation | other | Agreement | Yes |
Yes
| not treated | No | ||||
S5‑252563 | Input to DraftCR Rel-19 TS 28.105 Add Procedure Diagram for FL Server selection and determination | ZTE Corporation, NEC, Intel | other | Agreement | Yes |
Yes
| noted | No | ||||
S5‑252993 | Input to DraftCR Rel-19 TS 28.105 Add Procedure Diagram for FL Server selection and determination | ZTE Corporation, NEC, Intel | other | Agreement | No |
Yes
| withdrawn | Yes | ||||
S5‑252568 | Rel-19 Input to draftCR TS 28.105 Add addtional attributes on distributed training | CATT | other | Approval | Yes |
Yes
| revised | No | S5‑252836 | |||
S5‑252836 | Rel-19 Input to draftCR TS 28.105 Add addtional attributes on distributed training | CATT | other | Approval | Yes |
Yes
| approved | No | S5‑252568 | |||
S5‑252572 | Rel-19 Input to Draft CR TS 28.105 Pre-specialised training and Fine-tuning | China Mobile, ZTE | other | Approval | Yes |
Yes
| merged | No | S5‑252828 | |||
S5‑252573 | Rel-19 Input to draftCR TS 28.105 Pre-specialised training and Fine-tuning NRM | China Mobile, ZTE, NEC, Intel, Huawei | other | Approval | Yes |
Yes
| revised | No | S5‑253019 | |||
S5‑253019 | Rel-19 Input to draftCR TS 28.105 Pre-specialised training and Fine-tuning NRM | China Mobile, ZTE, NEC, Intel, Huawei, Rakuten, DTAG, China Unicom, Verizon | other | Approval | Yes |
Yes
| approved | No | S5‑252573 | |||
S5‑252648 | Input to DraftCR Rel-19 TS 28.105 Fix wrong reference and add RRC report | Ericsson Espańa S.A. | other | Approval | Yes |
Yes
| approved | No | ||||
S5‑252649 | DP on use cases of Pre-training and Fine tuning | Ericsson Espańa S.A. | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑252688 | Rel-19 Input to draftCR TS 28.105 add note for ML model lifecycle | China Mobile | other | Approval | Yes |
Yes
| revised | No | S5‑253000 | |||
S5‑253000 | Rel-19 Input to draftCR TS 28.105 add note for ML model lifecycle | China Mobile, ZTE | other | Approval | Yes |
Yes
| approved | No | S5‑252688 | |||
S5‑252689 | Rel-19 Input to draftCR TS 28.105 corrections of ML-Knowledge-based Transfer Learning | China Mobile | other | Approval | Yes |
Yes
| revised | No | S5‑252837 | |||
S5‑252837 | Rel-19 Input to draftCR TS 28.105 corrections of ML-Knowledge-based Transfer Learning | China Mobile | other | Approval | Yes |
Yes
| revised | No | S5‑253106 | S5‑252689 | ||
S5‑253106 | Rel-19 Input to draftCR TS 28.105 corrections of ML-Knowledge-based Transfer Learning | China Mobile | other | Approval | Yes |
Yes
| approved | No | S5‑252837 | |||
S5‑252733 | Rel-19 InputToDraftCR TS 28.105 Add solution for ML model training for multiple contexts | Samsung Electronics France SA | CR | Approval | Yes |
YesWrong Tdoc type
| not pursued | No | ||||
S5‑252987 | Rel-19 InputToDraftCR TS 28.105 Add solution for ML model training for multiple contexts | Samsung Electronics France SA | other | Approval | Yes |
Yes
| approved | No | ||||
S5‑252735 | Rel-19 InputToDraftCR TS 28.105 Add solution for management of Federated Learning | Samsung Electronics France SA | CR | Approval | Yes |
YesWrong type of Tdoc?
| merged | No | S5‑252832 | |||
S5‑252818 | DraftCR TS28.105 | NEC | draftCR | Approval | No |
Yes
| reserved | No | ||||
6.19.2 | Study on Management Data Analytics (MDA) – Phase 3 (completed) |   | ||||||||||
6.19.2.1 | Management Data Analytics phase 3 | S5‑252287 | Discussion on way forward for TS 28.104 clause 8 | Nokia, Nokia Shanghai Bell, Huawei | discussion | Endorsement | Yes |
Yes
| endorsed | No | ||
S5‑252288 | Rel19 CR TS28.104 enhancement to stage 2 and stage 3 for clause 8 | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑252868 | |||
S5‑252868 | Rel19 CR TS28.104 enhancement to stage 2 and stage 3 for clause 8 | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252288 | |||
S5‑252289 | Rel19 CR TS28.104 adding the new MDAType and correct the value format | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑252865 | |||
S5‑252865 | Rel19 CR TS28.104 adding the new MDAType and correct the value format | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252289 | |||
S5‑252290 | Rel19 CR TS28.104 adding stage 3 for Release 19 new use cases | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| merged | No | S5‑252869 | |||
S5‑252384 | Rel-19 CR TS 28.104 add stage3 solution for mobility performance analysis and coverage problem analysis | Huawei, Samsung | CR | Approval | Yes |
Yes
| revised | No | S5‑252869 | |||
S5‑252869 | Rel-19 CR TS 28.104 add stage3 solution for mobility performance analysis and coverage problem analysis | Huawei, Samsung | CR | Approval | Yes |
Yes
| agreed | No | S5‑252384 | |||
S5‑252385 | Rel-19 CR TS 28.104 enhance the discription of MDA request IOC to support UE throughput analysis | Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑252866 | |||
S5‑252866 | Rel-19 CR TS 28.104 enhance the discription of MDA request IOC to support UE throughput analysis | HUAWEI,Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑252385 | |||
S5‑252521 | Rel-19 CR TS 28.104 Fix errors in attribute definitions | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑252522 | Rel-19 CR TS 28.104 Fix editorial errors | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑252870 | |||
S5‑252870 | Rel-19 CR TS 28.104 Fix editorial errors | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252522 | |||
S5‑252578 | Rel-19 CR TS 28.104 Update the use case for failure prediction | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑252863 | |||
S5‑252863 | Rel-19 CR TS 28.104 Update the use case for failure prediction | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252578 | |||
S5‑252594 | Rel-19 CR TS 28.104 Enhancing service failure recovery | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑252864 | |||
S5‑252864 | Rel-19 CR TS 28.104 Enhancing service failure recovery | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252594 | |||
S5‑252634 | Rel-19 CR 28.104 clarification on resource management | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑252867 | |||
S5‑252867 | Rel-19 CR 28.104 clarification on resource management | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252634 | |||
S5‑252719 | Rel-19 CR TS 28.104 Multi Domain Resource Optimization | Nokia | CR | Approval | Yes |
Yes
| revised | No | S5‑252862 | |||
S5‑252862 | Rel-19 CR TS 28.104 Multi Domain Resource Optimization | Nokia | CR | Approval | Yes |
Yes
| not pursued | No | S5‑252719 | |||
6.19.3 | Study on intent driven management services for mobile network phase 3 (completed) |   | ||||||||||
6.19.3.1 | Intent driven management services for mobile network phase 3 | S5‑252226 | Rel-19 CR TS 28.312 Add stage3 openAPI definition for intent negotiation report | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑252872 | |
S5‑252872 | Rel-19 CR TS 28.312 Add stage3 openAPI definition for intent negotiation report | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252226 | |||
S5‑252227 | Rel-19 CR TS 28.312 Update procedure for intent feasibility check | Huawei, Deutsche Telekom | CR | Agreement | Yes |
Yes
| revised | No | S5‑252877 | |||
S5‑252877 | Rel-19 CR TS 28.312 Update procedure for intent feasibility check | Huawei, Deutsche Telekom, ZTE | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252227 | |||
S5‑252228 | Rel-19 CR TS 28.312 Add procedure for intent negotiation during fulfilment phase | Huawei, Deutsche Telekom | CR | Agreement | Yes |
Yes
| revised | No | S5‑252873 | |||
S5‑252873 | Rel-19 CR TS 28.312 Add procedure for intent negotiation during fulfilment phase | Huawei, Deutsche Telekom | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252228 | |||
S5‑252229 | Rel-19 CR TS 28.312 Address stage2 and stage3 misalignment issue for several attribute definition | Huawei, Deutsche Telekom | CR | Agreement | Yes |
Yes
| revised | No | S5‑252871 | |||
S5‑252871 | Rel-19 CR TS 28.312 Address stage2 and stage3 misalignment issue for several attribute definition | Huawei, Deutsche Telekom | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252229 | |||
S5‑252294 | Rel-19 CR Update UML diagram for Intent and IntentReport | Huawei, Ericsson, ZTE | CR | Agreement | Yes |
Yes
| revised | No | S5‑252880 | |||
S5‑252880 | Rel-19 CR Update UML diagram for Intent and IntentReport | Huawei, Ericsson, ZTE | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252294 | |||
S5‑252299 | Rel-19 CR TS 28.312 Update constraint description for IntentReport | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑252881 | |||
S5‑252881 | Rel-19 CR TS 28.312 Update constraint description for IntentReport | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252299 | |||
S5‑252353 | Correcting target achieved value | Nokia | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑252354 | Updating intent conflict reporting | Nokia | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑252377 | Rel-19 CR TS 28.312 correct TargetAchievedValue | Nokia | CR | Agreement | Yes |
Yes
| revised | No | S5‑252884 | |||
S5‑252884 | Rel-19 CR TS 28.312 correct TargetAchievedValue | Nokia | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252377 | |||
S5‑252378 | Rel-19 CR TS 28.312 correct TargetAchievedValue | Nokia | CR | Approval | Yes |
Yes
| revised | No | S5‑252885 | |||
S5‑252885 | Rel-19 CR TS 28.312 Update intent conflict reporting | Nokia | CR | Approval | Yes |
Yes
| agreed | No | S5‑252378 | |||
S5‑252402 | Rel-19 CR TS 28.312 Add procedure for intent exploration | ZTE Corporation | CR | Agreement | Yes |
Yes
| revised | No | S5‑252874 | S5‑251917 | ||
S5‑252874 | Rel-19 CR TS 28.312 Add procedure for intent exploration | Huawei, Deutsche Telekom, ZTE Corporation, Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252402 | |||
S5‑252403 | Rel-19 CR TS 28.312 Enhance the definition for intentMgmtPurpose | ZTE Corporation | CR | Agreement | Yes |
Yes
| revised | No | S5‑252875 | S5‑251918 | ||
S5‑252875 | Rel-19 CR TS 28.312 Enhance the definition for intentMgmtPurpose | Huawei, Deutsche Telekom, ZTE Corporation | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252403 | |||
S5‑252404 | Rel-19 CR TS 28.312 Clarification on Usage of Intent Utility Function | ZTE Corporation | CR | Agreement | Yes |
Yes
| revised | No | S5‑252878 | |||
S5‑252878 | Rel-19 CR TS 28.312 Clarification on Usage of Intent Utility Function | ZTE Corporation | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252404 | |||
S5‑252405 | Rel-19 CR TS 28.312 Clarify the usage of Intent NRM | ZTE Corporation | CR | Agreement | Yes |
Yes
| revised | No | S5‑252886 | |||
S5‑252886 | Rel-19 CR TS 28.312 Clarify the usage of Intent NRM | ZTE Corporation | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252405 | |||
S5‑252406 | Rel-19 CR TS 28.312 Update on the Intent Creation Procedure | ZTE Corporation | CR | Agreement | Yes |
Yes
| merged | No | S5‑252877 | |||
S5‑252407 | Rel-19 CR TS 28.312 Correct typo of Intent NRM | ZTE Corporation | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑252444 | Rel-19 CR TS 28.312 Add YAML document examples for Intent feasibility check and intent exploration | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑252876 | |||
S5‑252876 | Rel-19 CR TS 28.312 Add YAML document examples for Intent feasibility check and intent exploration | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252444 | |||
S5‑252445 | Rel-19 CR TS 28.312 Add YAML document examples for IntentHandlingCapability | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑252883 | |||
S5‑252883 | Rel-19 CR TS 28.312 Add YAML document examples for IntentHandlingCapability | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252445 | |||
S5‑252455 | Rel-19 CR TS 28.312 Enhance the solution for network maintenance expectation | NTT DOCOMO | CR | Agreement | Yes |
Yes
| revised | No | S5‑252882 | |||
S5‑252882 | Rel-19 CR TS 28.312 Enhance the solution for network maintenance expectation | NTT DOCOMO | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252455 | |||
S5‑252534 | Rel-19 CR TS 28.312 Update UML diagram for intent | Ericsson, ZTE | CR | Approval | Yes |
Yes
| not pursued | No | S5‑251661 | |||
S5‑252607 | Rel-19 CR TS 28.312 Add description of intent negotiation initiated by MnS producer | China Mobile Com. Corporation | CR | Approval | Yes |
Yes
| revised | No | S5‑252887 | |||
S5‑252887 | Rel-19 CR TS 28.312 Add description of intent negotiation initiated by MnS producer | China Mobile Com. Corporation | CR | Approval | Yes |
Yes
| agreed | No | S5‑252607 | |||
S5‑252612 | Rel-19 CR TS 28.312 Add description of implicitIntent | China Mobile Com. Corporation | CR | Approval | Yes |
Yes
| revised | No | S5‑252888 | |||
S5‑252888 | Rel-19 CR TS 28.312 Add description of implicitIntent | China Mobile Com. Corporation | CR | Approval | Yes |
Yes
| agreed | No | S5‑252612 | |||
S5‑252678 | Rel-19 CR TS 28.312 Update intent utility function report | Ericsson Canada Inc. | CR | Approval | Yes |
Yes
| revised | No | S5‑252879 | |||
S5‑252879 | Rel-19 CR TS 28.312 Update intent utility function report | Ericsson Canada Inc. | CR | Approval | Yes |
Yes
| agreed | No | S5‑252678 | |||
6.19.4 | Study on closed control loop management (completed) |   | ||||||||||
6.19.4.1 | Closed Control Loop Management | S5‑252356 | Definitions of CCL conflicts | Nokia | pCR | Approval | Yes |
Yes
| revised | No | S5‑252857 | |
S5‑252857 | Definitions of CCL conflicts | Nokia | pCR | Approval | Yes |
Yes
| approved | No | S5‑252356 | |||
S5‑252357 | Control of CCLs | Nokia | pCR | Approval | Yes |
Yes
| revised | No | S5‑253007 | |||
S5‑253007 | Control of CCLs | Nokia | pCR | Approval | Yes |
Yes
| approved | No | S5‑252357 | |||
S5‑252358 | Solution for Dynamic CCLs | Nokia | pCR | Approval | Yes |
Yes
| revised | No | S5‑252850 | |||
S5‑252850 | Solution for Dynamic CCLs | Nokia | pCR | Approval | Yes |
Yes
| approved | No | S5‑252358 | |||
S5‑252359 | CCL coordination NRM | Nokia | pCR | Approval | Yes |
Yes
| revised | No | S5‑252846 | |||
S5‑252846 | CCL coordination NRM | Nokia | pCR | Approval | Yes |
Yes
| approved | No | S5‑252359 | |||
S5‑252360 | CCL concurrent-actions conflicts | Nokia | pCR | Approval | Yes |
Yes
| revised | No | S5‑252848 | |||
S5‑252848 | CCL concurrent-actions conflicts | Nokia | pCR | Approval | Yes |
Yes
| approved | No | S5‑252360 | |||
S5‑252361 | CCL scope conflicts | Nokia | pCR | Approval | Yes |
Yes
| revised | No | S5‑252849 | |||
S5‑252849 | CCL scope conflicts | Nokia | pCR | Approval | Yes |
Yes
| approved | No | S5‑252361 | |||
S5‑252362 | CCL Goal NRM | Nokia | pCR | Approval | Yes |
Yes
| revised | No | S5‑252844 | |||
S5‑252844 | CCL Goal NRM | Nokia | pCR | Approval | Yes |
Yes
| noted | No | S5‑252362 | |||
S5‑252363 | DP on modelling CCL goals and targets | Nokia | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑252364 | CCL goal conflicts | Nokia | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑252365 | CCL-impact assessment and resolution | Nokia | pCR | Approval | Yes |
Yes
| revised | No | S5‑252854 | |||
S5‑252854 | CCL-impact assessment and resolution | Nokia | pCR | Approval | Yes |
Yes
| approved | No | S5‑252365 | |||
S5‑252366 | Procedure for CL decision escalation | Nokia | pCR | Approval | Yes |
Yes
| revised | No | S5‑252855 | |||
S5‑252855 | Procedure for CL decision escalation | Nokia | pCR | Approval | Yes |
Yes
| approved | No | S5‑252366 | |||
S5‑252367 | Procedure for CCL-impact assessment and resolution | Nokia | pCR | Approval | Yes |
Yes
| revised | No | S5‑252856 | |||
S5‑252856 | CCL-impact assessment, feedback and resolution | Nokia | pCR | Approval | Yes |
YesTitle of the Tdoc to be updated
| approved | No | S5‑252367 | |||
S5‑252368 | Example realizations of CCLs | Nokia | pCR | Approval | Yes |
Yes
| revised | No | S5‑253008 | |||
S5‑253008 | Example realizations of CCLs | Nokia | pCR | Approval | Yes |
Yes
| approved | No | S5‑252368 | |||
S5‑252369 | CCL DraftTS Rapporteur corrections | Nokia | pCR | Approval | Yes |
Yes
| revised | No | S5‑253009 | |||
S5‑253009 | CCL DraftTS Rapporteur corrections | Nokia | pCR | Approval | Yes |
Yes
| approved | No | S5‑252369 | |||
S5‑252394 | Rel-19 CR 28.535 use case for triggered CCL | Samsung | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑252847 | Rel-19 CR 28.535 use case for triggered CCL | Samsung | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
S5‑252395 | Rel-19 CR 28.536 solution for triggered CCL | Samsung | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑252396 | Rel-19 pCR 28.567 solution for triggered CCL | Samsung | pCR | Agreement | Yes |
Yes
| revised | No | S5‑253020 | |||
S5‑253020 | Rel-19 pCR 28.567 solution for triggered CCL | Samsung | pCR | Agreement | Yes |
Yes
| approved | No | S5‑252396 | |||
S5‑252397 | Rel-19 pCR 28.567 solution for conflict management | Samsung | pCR | Agreement | Yes |
Yes
| revised | No | S5‑252851 | |||
S5‑252851 | Rel-19 pCR 28.567 solution for conflict management | Samsung | pCR | Agreement | Yes |
Yes
| approved | No | S5‑252397 | |||
S5‑252491 | pCR TS 28.567 Correct information models for CCL management in clause 6.2.1 | Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑252845 | pCR TS 28.567 Correct information models for CCL management in clause 6.2.1 | Huawei | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑252529 | Pseudo-CR on Rel-19 TS 28.567 Add Definitions of terms and abbreviations for closed control loop | NTT DOCOMO | pCR | Approval | Yes |
Yes
| revised | No | S5‑253010 | |||
S5‑253010 | Pseudo-CR on Rel-19 TS 28.567 Add Definitions of terms and abbreviations for closed control loop | NTT DOCOMO | pCR | Approval | Yes |
Yes
| approved | No | S5‑252529 | |||
S5‑252554 | Pseudo-CR on Rel-19 TS 28.567 Add Stage-2 Solutions for Fault Management CCL | NTT DOCOMO | pCR | Approval | Yes |
Yes
| revised | No | S5‑252852 | |||
S5‑252852 | Pseudo-CR on Rel-19 TS 28.567 Add Stage-2 Solutions for Fault Management CCL | NTT DOCOMO | pCR | Approval | Yes |
Yes
| approved | No | S5‑252554 | |||
S5‑252734 | Rel-19 pCR TS 28.567 Metrics for CCL performance monitoring | Samsung Electronics France SA | pCR | Approval | Yes |
Yes
| revised | No | S5‑252853 | |||
S5‑252853 | Rel-19 pCR TS 28.567 Metrics for CCL performance monitoring | Samsung Electronics France SA | pCR | Approval | Yes |
Yes
| approved | No | S5‑252734 | |||
S5‑252822 | Draft TS28.567 | Nokia | draft TS | Agreement | No |
Yes
| reserved | No | ||||
6.19.5 | Study on management aspects of Network Digital Twin (completed) |   | ||||||||||
6.19.5.1 | Management aspects of Network Digital Twins | S5‑252370 | General NRM for NDTs | Nokia | pCR | Approval | Yes |
Yes
| revised | No | S5‑252861 | |
S5‑252861 | General NRM for NDTs | Nokia, Huawei, ZTE, NTT DOCOMO, Orange, SK Telecom, FiberCop, CMCC, Ericsson, Samsung | pCR | Approval | Yes |
Yes
| revised | No | S5‑253102 | S5‑252370 | ||
S5‑253102 | General NRM for NDTs | Nokia, Huawei, ZTE, NTT DOCOMO, Orange, SK Telecom, FiberCop, CMCC, Ericsson, Samsung | pCR | Approval | Yes |
Yes
| approved | No | S5‑252861 | |||
S5‑252371 | NRM for Automation & Verification NDTs | Nokia | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑253001 | NRM for Automation & Verification NDTs | Nokia | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑252372 | NRM for data generation | Nokia | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑253002 | NRM for data generation | Nokia | pCR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑252373 | NRM for Collaboration between NDTs | Nokia | pCR | Approval | Yes |
Yes
| revised | No | S5‑253068 | |||
S5‑253068 | NRM for Collaboration between NDTs | Nokia | pCR | Approval | Yes |
Yes
| approved | No | S5‑252373 | |||
S5‑252399 | Rel-19 pCR 28.561 solution for inducement | Samsung | pCR | Agreement | Yes |
Yes
| merged | No | S5‑253102 | |||
S5‑253003 | Rel-19 pCR 28.561 solution for inducement | Samsung | pCR | Agreement | No |
Yes
| withdrawn | Yes | ||||
S5‑252415 | Pseudo-CR on TS 28.561 NDT relation to automation | China Mobile, Nokia | pCR | Approval | Yes |
Yes
| revised | No | S5‑253064 | |||
S5‑253064 | Pseudo-CR on TS 28.561 NDT relation to automation | China Mobile, Nokia | pCR | Approval | Yes |
Yes
| noted | No | S5‑252415 | |||
S5‑252416 | Pseudo-CR on TS 28.561 Update use case of advanced NDT capabilities | China Mobile | pCR | Approval | Yes |
Yes
| merged | No | S5‑253006 | |||
S5‑252417 | Pseudo-CR on TS 28.561 Update the reference and abbreviations | China Mobile | pCR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑252418 | Pseudo-CR on TS 28.561 Rapporteur clean-up on abbreviations in clause 5 | China Mobile | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑252419 | Pseudo-CR on TS 28.561 NDT Procedure update | China Mobile | pCR | Approval | Yes |
Yes
| revised | No | S5‑253004 | |||
S5‑253004 | Pseudo-CR on TS 28.561 NDT Procedure update | China Mobile | pCR | Approval | Yes |
Yes
| approved | No | S5‑252419 | |||
S5‑252420 | Presentation sheet of TS 28.561 for SA Information | China Mobile | TS or TR cover | Information | Yes |
Yes
| revised | No | S5‑253066 | |||
S5‑253066 | Presentation sheet of TS 28.561 for SA Information | China Mobile | TS or TR cover | Information | Yes |
Yes
| approved | No | S5‑252420 | |||
S5‑252484 | Rel-19 pCR TS 28.561 Add attributes for NDT NRMs | Huawei | pCR | Approval | Yes |
Yes
| merged | No | S5‑253102 | |||
S5‑252485 | Rel-19 pCR TS 28.561 Deployment scenarios of NDT function | Huawei, China Mobile | pCR | Approval | Yes |
Yes
| revised | No | S5‑253065 | |||
S5‑253065 | Rel-19 pCR TS 28.561 Deployment scenarios of NDT function | Huawei, China Mobile | pCR | Approval | Yes |
Yes
| approved | No | S5‑252485 | |||
S5‑252515 | Pseudo-CR on TS 28.561 NDT Use case Update | ZTE Corporation | pCR | Agreement | Yes |
Yes
| revised | No | S5‑253063 | |||
S5‑253063 | Pseudo-CR on TS 28.561 NDT Use case Update | ZTE Corporation | pCR | Agreement | Yes |
Yes
| approved | No | S5‑252515 | |||
S5‑252516 | Pseudo-CR on TS 28.561 Add Attributes on NDT NRM | ZTE Corporation | pCR | Agreement | Yes |
Yes
| merged | No | S5‑253102 | |||
S5‑252517 | Pseudo-CR on TS 28.561 Update the procedure for consuming NDT management service | ZTE Corporation | pCR | Agreement | Yes |
Yes
| merged | No | S5‑253004 | |||
S5‑252518 | Pseudo-CR on TS 28.561 NDT LCM Overview | ZTE Corporation | pCR | Agreement | Yes |
Yes
| not treated | No | ||||
S5‑252580 | Rel-19 pCR TS 28.561 Update the use case for life cycle management of NDT instances | Huawei | pCR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑252581 | Rel-19 pCR TS 28.561 Update the overview of NDT | Huawei | pCR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑252582 | Rel-19 pCR TS 28.561 Add procedures for delete and query an NDT job | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑253005 | |||
S5‑253005 | Rel-19 pCR TS 28.561 Add procedures for delete and query an NDT job | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑252582 | |||
S5‑252583 | Rel-19 pCR TS 28.561 Add reference and abbreviations | Huawei | pCR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑252593 | Issue on supporting vendor specific value in NDT | NTT DOCOMO, Orange, SK Telecom, FiberCop, CMCC | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑252604 | Pseudo-CR on Add attribute of NDTFunction and NDTJob | NTT DOCOMO, Orange, SK Telecom, FiberCop, CMCC | pCR | Approval | Yes |
Yes
| merged | No | S5‑253102 | |||
S5‑252610 | Rel-19 pCR TS 28.561 Add authorization to all requirement | Ericsson France S.A.S | pCR | Agreement | Yes |
Yes
| approved | No | ||||
S5‑252614 | Rel-19 pCR TS 28.561 Clarify evaluation of high-risk operation | Ericsson France S.A.S | pCR | Agreement | Yes |
Yes
| not treated | No | ||||
S5‑252615 | Rel-19 pCR TS 28.561 Clarify NDT management service | Ericsson France S.A.S | pCR | Agreement | Yes |
Yes
| not treated | No | ||||
S5‑252635 | Rel-19 pCR TS 28.561 Update verification of network response to events | Huawei | pCR | Agreement | Yes |
Yes
| not treated | No | ||||
S5‑252636 | Rel-19 pCR TS 28.561 Clarify NDT definition and collaborative NDT use case | Ericsson France S.A.S | pCR | Agreement | Yes |
Yes
| revised | No | S5‑253006 | |||
S5‑253006 | Rel-19 pCR TS 28.561 Clarify NDT definition and collaborative NDT use case | Ericsson France S.A.S | pCR | Agreement | Yes |
Yes
| noted | No | S5‑252636 | |||
S5‑252637 | Rel-19 pCR TS 28.561 Clarify support for data generation | Ericsson France S.A.S | pCR | Agreement | Yes |
Yes
| not treated | No | ||||
S5‑252638 | DP on using terms simulation and emulation | Ericsson France S.A.S | discussion | Endorsement | Yes |
Yes
| not treated | No | ||||
S5‑252642 | Rel-19 pCR TS 28.561 Clarify the use of terms simulation and emulation | Ericsson France S.A.S | pCR | Agreement | Yes |
Yes
| not treated | No | ||||
S5‑252650 | Rel-19 pCR TS 28.561 Add attributes to NDTFunction and NDTJob and NDTReport | Ericsson France S.A.S | pCR | Agreement | Yes |
Yes
| merged | No | S5‑253102 | |||
S5‑252821 | Draft TS28.561 | CMCC | draft TS | Agreement | No |
Yes
| reserved | No | ||||
6.19.6 | Study on Cloud Aspects of Management and Orchestration | S5‑252321 | pCR TR 28.869 Add potential solution for VNF configuration management | Huawei, Deutsche Telekom, Ericsson, Nokia, Samsung | pCR | Approval | Yes |
Yes
| revised | No | S5‑252858 | S5‑251889 |
S5‑252858 | pCR TR 28.869 Add potential solution for VNF configuration management | Huawei, Deutsche Telekom, Ericsson, Nokia, Samsung, China Unicom, AT&T, Orange | pCR | Approval | Yes |
Yes
| approved | No | S5‑252321 | |||
S5‑252490 | pCR on TR 28.869 Add conclusion for management data streaming solution based on message bus | Huawei Device Co., Ltd | pCR | Yes |
Yes
| revised | No | S5‑252991 | S5‑252121 | |||
S5‑252991 | pCR on TR 28.869 Add conclusion for management data streaming solution based on message bus | Huawei, Nokia, Rakuten | pCR | - | Yes |
Yes
| approved | No | S5‑252490 | |||
S5‑252513 | Pseudo-CR on TR 28.869 clean up about editorial and small corrections | China Mobile Com. Corporation | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑252514 | Pseudo-CR on TR 28.869 add some recommendations | China Mobile Com. Corporation | pCR | Approval | Yes |
Yes
| revised | No | S5‑252992 | |||
S5‑252992 | Pseudo-CR on TR 28.869 add some recommendations | China Mobile Com. Corporation | pCR | Approval | Yes |
Yes
| noted | No | S5‑252514 | |||
S5‑252618 | Pseudo-CR on TR28.869 conclusions | NTT DOCOMO | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑252619 | Pseudo-CR on TR28.869 editorial cleanup removing ENs | NTT DOCOMO, China Mobile | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑252620 | Pseudo-CR on TR28.869 VNF configuration management evaluation | NTT DOCOMO | pCR | Approval | Yes |
Yes
| merged | No | S5‑252859 | |||
S5‑252622 | Pseudo-CR on TR28.869 VNF generic OAM functions and PaaS Services relationship | NTT DOCOMO, China Mobile | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑252623 | Pseudo-CR on TR28.869 VNF policy management evaluation | NTT DOCOMO, China Mobile | pCR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑252624 | Pseudo-CR on TR28.869 VNF traffic management evaluation | NTT DOCOMO | pCR | Approval | Yes |
Yes
| merged | No | S5‑252859 | |||
S5‑252626 | Pseudo-CR on TR28.869 VNF upgrade evaluation | NTT DOCOMO | pCR | Approval | Yes |
Yes
| merged | No | S5‑252859 | |||
S5‑252659 | pCR TR 28.869 LCM details for declarative descriptor | Rakuten Mobile, Inc | pCR | Approval | Yes |
Yes
| revised | No | S5‑252860 | |||
S5‑252860 | pCR TR 28.869 LCM details for declarative descriptor | Rakuten Mobile, Inc, Orange | pCR | Approval | Yes |
Yes
| noted | No | S5‑252659 | |||
S5‑252664 | Rel-19 pCR TR 28.869 Add Evaluation to the use of VNF generic OAM functions | Nokia Belgium, Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S5‑252859 | |||
S5‑252859 | Rel-19 pCR TR 28.869 Add Evaluation to the use of VNF generic OAM functions | Nokia Belgium, Ericsson, AT&T | pCR | Approval | Yes |
Yes
| noted | No | S5‑252664 | |||
S5‑252665 | Rel-19 pCR TR 28.869 Add conclusions and recommendations to the use of VNF generic OAM functions | Nokia Belgium, Ericsson | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑252666 | Rel-19 pCR TR 28.869 Add evaluation and conclusion for data streaming for cloud-native NF deployments | Nokia Belgium, Ericsson | pCR | Approval | Yes |
Yes
| merged | No | S5‑252991 | |||
S5‑252668 | pCR TR 28.869 Add evaluation and conclusion for management data streaming based on message bus | Rakuten Mobile, Inc | pCR | Approval | Yes |
Yes
| merged | No | S5‑252991 | |||
S5‑252672 | pCR TR 28.869 Evaluation and conclusions for LCM | Rakuten Mobile, Inc | pCR | Approval | Yes |
Yes
| merged | No | S5‑253023 | |||
S5‑252683 | DP cloud native NF data streaming based on message bus evaluation and recommendation | Rakuten Mobile, Inc | discussion | Endorsement | Yes |
Yes
| not treated | No | ||||
S5‑252698 | pCR TR 28.869 Detailed procedure flow for creation of NF Deployment instance | Ericsson Limited | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑252990 | pCR TR 28.869 Detailed procedure flow for creation of NF Deployment instance | Ericsson Limited | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑252699 | pCR TR 28.869 Recommendation for LCM of NF Deployment | Ericsson Limited | pCR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑252700 | pCR TR 28.869 Evaluations for LCM of NF Deployment use cases | Ericsson Limited | pCR | Approval | Yes |
Yes
| revised | No | S5‑253023 | |||
S5‑253023 | pCR TR 28.869 Evaluations for LCM of NF Deployment use cases | Ericsson Limited, Rakuten | pCR | Approval | Yes |
Yes
| noted | No | S5‑252700 | |||
S5‑252825 | Draft TS28.869 | CMCC | draft TS | Agreement | No |
Yes
| reserved | No | ||||
6.19.7 | Study on Enablers for Security Monitoring (completed) |   | ||||||||||
6.19.8 | Study on Service Based Management Architecture enhancement phase 3 (completed) |   | ||||||||||
6.19.8.1 | Service Based Management Architecture enhancement phase 3 | S5‑252279 | DP Allowedvalues and boolean literals | Ericsson Hungary Ltd | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑252890 | |
S5‑252890 | DP Allowedvalues and boolean literals | Ericsson Hungary Ltd | discussion | Endorsement | Yes |
Yes
| endorsed | No | S5‑252279 | |||
S5‑252280 | Rel-19 CR 32.156 Using allowedValues and boolean literals | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑252891 | Rel-19 CR 32.156 Using allowedValues and boolean literals | Ericsson Hungary Ltd | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑252320 | Rel-19 CR 28.532 Add new notifications for reliability | Ericsson India Private Limited, Nokia | CR | Approval | Yes |
Yes
| revised | No | S5‑252895 | S5‑251733 | ||
S5‑252895 | Rel-19 CR 28.532 Add new notifications for reliability | Ericsson India Private Limited, Nokia | CR | Approval | Yes |
Yes
| agreed | No | S5‑252320 | |||
S5‑252374 | Rel-19 CR 28.622 Reliable notification transfer | Ericsson Hungary Ltd, Nokia | CR | Approval | Yes |
Yes
| revised | No | S5‑252896 | S5‑251940 | ||
S5‑252896 | Rel-19 CR 28.622 Reliable notification transfer | Ericsson Hungary Ltd, Nokia | CR | Approval | Yes |
Yes
| agreed | No | S5‑252374 | |||
S5‑252535 | Rel-19 CR TS 28.533 Update Annex E | Ericsson, Huawei, AT&T, Verizon, China Unicom | CR | Approval | Yes |
Yes
| revised | No | S5‑253021 | S5‑251937 | ||
S5‑253021 | Rel-19 CR TS 28.533 Update Annex E | Ericsson, Huawei, AT&T, Verizon, China Unicom | CR | Approval | Yes |
Yes
| agreed | No | S5‑252535 | |||
S5‑252597 | Rel-19 CR TS 28.533 Management services exposure | Huawei, Nokia | CR | Agreement | Yes |
Yes
| revised | No | S5‑253067 | |||
S5‑253067 | Rel-19 CR TS 28.533 Management services exposure | Huawei, Nokia, AT&T, DTAG, China Mobile, China Unicom, Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑252597 | |||
S5‑252651 | Rel-19 CR TS 28.533 Update figure in Annex E | Ericsson Espańa S.A. | CR | Agreement | Yes |
Yes
| withdrawn | Yes | ||||
S5‑252657 | Rel-19 CR 32.158 Add MnS versioning concept | Nokia | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑252673 | DP Long Running Configuration Reads | Ericsson Hungary Ltd, Nokia | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑252985 | |||
S5‑252985 | DP Long Running Configuration Reads | Ericsson Hungary Ltd, Nokia | discussion | Endorsement | Yes |
Yes
| endorsed | No | S5‑252673 | |||
S5‑252676 | Rel-19 CR 32.158 Add details for MnS component versioning | Ericsson Canada Inc. | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑252893 | Rel-19 CR 32.158 Add details for MnS component versioning | Ericsson Canada Inc., Nokia | CR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑252677 | Rel-19 CR 28.537 Add details for MnS component versioning | Ericsson Canada Inc. | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑252894 | Rel-19 CR 28.537 Add details for MnS component versioning | Ericsson Canada Inc. | CR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑252706 | Rel-19 CR 28.623 Reliable notification transfer | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑252730 | Rel-19 CR TS 28.533 Update figure in Annex E | Ericsson Espańa S.A | CR | Agreement | Yes |
Yes
| revised | No | S5‑252892 | |||
S5‑252892 | Rel-19 CR TS 28.533 Update figure in Annex E | Ericsson Espańa S.A | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252730 | |||
6.19.9 | Study on Management of planned configurations (completed) |   | ||||||||||
6.19.9.1 | Management of planned configurations | S5‑252640 | Rel-19 pCR TS 28.572 Improve clause Information model | Nokia, Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S5‑252897 | |
S5‑252897 | Rel-19 pCR TS 28.572 Improve clause Information model | Nokia, Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S5‑252640 | |||
S5‑252708 | Rel-19 pCR TS 28.572 Plan Configuration Examples | Ericsson Hungary Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑252898 | |||
S5‑252898 | Rel-19 pCR TS 28.572 Plan Configuration Examples | Ericsson Hungary Ltd | pCR | Approval | Yes |
Yes
| approved | No | S5‑252708 | |||
S5‑253040 | Draft TS28.572 | Nokia | draft TS | Agreement | No |
Yes
| reserved | No | ||||
6.19.10 | Data management phase 2 | S5‑252274 | Draft CR for MADCOL_Ph2 – TS 28.537 | Nokia France | draftCR | Approval | Yes |
Yes
| approved | No | ||
S5‑252275 | Rel-19 CR TS28.622 | Nokia France | CR | Approval | No |
Yes
| reserved | No | ||||
S5‑252285 | Rel-19 CR TS28.623 | Nokia France | CR | Approval | Yes |
Yes
| revised | No | S5‑252915 | |||
S5‑252915 | Rel-19 CR TS28.623 | Nokia France | CR | Approval | No |
Yes
| reserved | No | S5‑252285 | |||
S5‑252322 | Input to draftCR TS 28.622 for MADCOL Update the MgmtDataInfo to align with MnSInfo | Huawei | other | Agreement | Yes |
Yes
| approved | No | ||||
S5‑252323 | Rel-19 CR TS 28.623 Add stage3 YAML definition for management data discovery | Huawei | CR | Agreement | Yes |
Yes
| merged | No | S5‑252915 | |||
S5‑252324 | Input to draftCR TS 28.537 for MADCOL Add solution reference management data registry and discovery | Huawei | other | Agreement | Yes |
Yes
| revised | No | S5‑252632 | |||
S5‑252325 | Input to draftCR TS 28.537 for MADCOL Update Usage of MnS Registry for different deployment scenarios to support MgmtDataInfo | Huawei | other | Agreement | Yes |
Yes
| approved | No | ||||
S5‑252446 | Rel-19 Input to DraftCR TS 28.537 Correction of requirement labels | Nokia | other | Approval | Yes |
Yes
| approved | No | ||||
S5‑252447 | Rel-19 Input to DraftCR TS 28.622 Miscellaneous Issues on Management Data Collection | Nokia | other | Approval | Yes |
Yes
| revised | No | S5‑253026 | |||
S5‑253026 | Rel-19 Input to DraftCR TS 28.622 Miscellaneous Issues on Management Data Collection | Nokia | other | Approval | Yes |
Yes
| approved | No | S5‑252447 | |||
S5‑252448 | Rel-19 Input to DraftCR TS 28.622 External Management Data | Nokia | other | Approval | Yes |
Yes
| revised | No | S5‑252914 | |||
S5‑252914 | Rel-19 Input to DraftCR TS 28.622 External Management Data | Nokia | other | Approval | Yes |
Yes
| approved | No | S5‑252448 | |||
S5‑252449 | Rel-19 Input to DraftCR TS 28.622 Reporting methods of external management data | Nokia | other | Approval | Yes |
Yes
| approved | No | ||||
S5‑252632 | Input to draftCR TS 28.537 for MADCOL Add solution reference management data registry and discovery | Huawei, Deutsche Telekom | other | Agreement | Yes |
Yes
| revised | No | S5‑252913 | S5‑252324 | ||
S5‑252913 | Input to draftCR TS 28.537 for MADCOL Add solution reference management data registry and discovery | Huawei, Deutsche Telekom | other | Agreement | Yes |
Yes
| approved | No | S5‑252632 | |||
S5‑252720 | Draft CR for MADCOL_Ph2 – TS 28.622 | Nokia | draftCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑252819 | DraftCR TS28.622 | Nokia | draftCR | Approval | No |
Yes
| reserved | No | ||||
S5‑252820 | DraftCR TS28.537 | Nokia | draftCR | Approval | Yes |
Yes
| reserved | No | ||||
S5‑252916 | Rel-19 CR TS28.537 | Nokia | CR | Approval | No |
Yes
| reserved | No | ||||
S5‑252823 | DraftCR TS28.537 | Nokia | draftCR | Approval | No |
Yes
| withdrawn | Yes | ||||
6.19.11 | Study on data management regarding subscriptions and reporting (completed) |   | ||||||||||
6.19.11.1 | Data management regarding subscriptions and reporting | S5‑252259 | Rel-19 CR TS 32.422 Trace Reference Uniqueness | Ericsson, CATT | CR | Agreement | Yes |
Yes
| revised | No | S5‑252899 | S5‑251959 |
S5‑252899 | Rel-19 CR TS 32.422 Trace Reference Uniqueness | Ericsson, CATT, Nokia | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252259 | |||
S5‑252260 | Rel-19 CR TS 28.405 QoE Reference Uniqueness | Ericsson, CATT | CR | Agreement | Yes |
Yes
| revised | No | S5‑252900 | S5‑251958 | ||
S5‑252900 | Rel-19 CR TS 28.405 QoE Reference Uniqueness | Ericsson, CATT, Nokia | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252260 | |||
S5‑252261 | Rel-19 CR TS 32.422 Trace Failure Notification | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑252901 | Rel-19 CR TS 32.422 Trace Failure Notification | Ericsson | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
S5‑252262 | Rel-19 CR TS 28.405 QoE Failure Notification | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑252902 | |||
S5‑252902 | Rel-19 CR TS 28.405 QoE Failure Notification | Ericsson, Nokia | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252262 | |||
S5‑252716 | Rel-19 CR TS 32.422 Trace Reference Uniqueness | Nokia | CR | Approval | Yes |
Yes
| merged | No | S5‑252899 | |||
S5‑252717 | Rel-19 CR TS 28.405 QoE Reference Uniqueness | Nokia | CR | Approval | Yes |
Yes
| merged | No | S5‑252900 | |||
6.19.12 | 5G performance measurements and KPIs phase 4 | S5‑252263 | Rel-19 CR TS 28.552 correction on paging record measurement | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||
S5‑252264 | Rel-19 CR TS 28.552 DRB measurement with filter | Ericsson Japan K.K. | CR | Agreement | Yes |
Yes
| revised | No | S5‑252702 | |||
S5‑252270 | Rel-19 CR TS 32.404 PM Counter Metadata | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑251963 | |||
S5‑252273 | Rel-19 CR TS 28.552 Performance Measurement Method | Ericsson Japan K.K. | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑252304 | Rel-19 CR TS 28.552 Update number of active UEs related measurements | China Telecom Corporation Ltd. | CR | Agreement | Yes |
Yes
| revised | No | S5‑252929 | |||
S5‑252929 | Rel-19 CR TS 28.552 Update number of active UEs related measurements | China Telecom Corporation Ltd. | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252304 | |||
S5‑252316 | Rel-19 CR TS 28.532 JobID delimiters | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑252930 | |||
S5‑252930 | Rel-19 CR TS 28.532 JobID delimiters | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252316 | |||
S5‑252318 | Rel-19 CR TS 28.552 Measurement Method | Ericsson Japan K.K. | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
S5‑252408 | Rel-19 CR TS 28.552 Add average DL PDU set delay for XR measurement | China Telecom Corporation Ltd. | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑252569 | Rel-19 CR TS 28.554 add coverage ratio KPI | CMCC, Huawei, ZTE, CATT | CR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑252571 | Rel-19 CR TS 28.554 add coverage ratio KPI | CMCC | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑252931 | Rel-19 CR TS 28.554 add coverage ratio KPI | CMCC | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑252606 | Rel-19 CR TS32.423 Enhance the Example of 5GC UE level measurements | ZTE Corporation | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑252702 | Rel-19 CR TS 28.552 DRB measurement with filter | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑252928 | S5‑252264 | ||
S5‑252928 | Rel-19 CR TS 28.552 DRB measurement with filter | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252702 | |||
S5‑252710 | Rel-19 CR TS28.558 Fix UE level measurements unit | ZTE Corporation | CR | Agreement | Yes |
Yes
| revised | No | S5‑252932 | |||
S5‑252932 | Rel-19 CR TS28.558 Fix UE level measurements unit | ZTE Corporation | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252710 | |||
S5‑252727 | Rel-19 CR TS 28.552 Measurements related to LTM cell-switch | Nokia | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑252728 | Measurements related to LTM cell-switch with almost invalid TA | Nokia | CR | Approval | Yes |
Yes
| not pursued | No | ||||
6.19.13 | 5G Advanced NRM features phase 3 | S5‑252291 | Rel19 CR TS 28.541 NRM enhancement cleanup | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | ||
S5‑252292 | Rel19 CR TS 28.541 Rapporteur clean up on editing and small corrections | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑252946 | |||
S5‑252946 | Rel19 CR TS 28.541 Rapporteur clean up on editing and small corrections | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252292 | |||
S5‑252326 | Rel-19 CR TS 28.541 Enhancements on NRFFunction to support hierarchical NRF scenario | ZTE Corporation, Orange | CR | Agreement | Yes |
Yes
| revised | No | S5‑252933 | |||
S5‑252933 | Rel-19 CR TS 28.541 Enhancements on NRFFunction to support hierarchical NRF scenario | ZTE Corporation, Orange | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252326 | |||
S5‑252327 | Rel-19 CR TS 28.541 Move cNSIIdList to ManagedNFProfile | ZTE Corporation, Orange, Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑252934 | |||
S5‑252934 | Rel-19 CR TS 28.541 Move cNSIIdList to ManagedNFProfile | ZTE Corporation, Orange, Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑252327 | |||
S5‑252328 | Rel19 CR TS 28.541 NRM enhancements on ManagedNFProfile | ZTE Corporation, Orange, Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑252935 | |||
S5‑252935 | Rel19 CR TS 28.541 NRM enhancements on ManagedNFProfile | ZTE Corporation, Orange, Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252328 | |||
S5‑252329 | Rel19 CR TS 28.541 NRM enhancements on NFService | ZTE Corporation, Orange, Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑252936 | |||
S5‑252936 | Rel19 CR TS 28.541 NRM enhancements on NFService | ZTE Corporation, Orange, Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252329 | |||
S5‑252330 | Rel19 CR TS 28.541 Correction on N3IWFFunction | ZTE Corporation | CR | Agreement | Yes |
Yes
| revised | No | S5‑252937 | |||
S5‑252937 | Rel19 CR TS 28.541 Correction on N3IWFFunction | ZTE Corporation | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252330 | |||
S5‑252333 | Rel-19 CR TS 28.541 Correct stage2 and stage3 definition for attribute allowedTime in MWAB | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑252400 | Rel-19 CR 28.541 NRM extensions for VMR Ph2 | Samsung | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑252938 | Rel-19 CR 28.541 NRM extensions for VMR Ph2 | Samsung | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
S5‑252469 | Rel-19 CR TS 28.541 Add UPF capabilities configuration | Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑252939 | |||
S5‑252939 | Rel-19 CR TS 28.541 Add UPF capabilities configuration | Huawei | CR | Approval | Yes |
Yes
| agreed | No | S5‑252469 | |||
S5‑252478 | Rel-19 CR TS 28.541 Enhance NR NRM for reader to support AIOT | Huawei, China Unicom | CR | Agreement | Yes |
Yes
| revised | No | S5‑252940 | |||
S5‑252940 | Rel-19 CR TS 28.541 Enhance NR NRM for reader to support AIOT | Huawei, China Unicom | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252478 | |||
S5‑252479 | Rel-19 CR TS 28.541 Add EP_AIOT NRMs to support AIOT | Huawei, China Unicom | CR | Agreement | Yes |
Yes
| revised | No | S5‑252941 | |||
S5‑252941 | Rel-19 CR TS 28.541 Add EP_AIOT NRMs to support AIOT | Huawei, China Unicom | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252479 | |||
S5‑252486 | Rel-19 CR TS 28.541 Add AIOTF and ADM IOC to support management of Ambient IoT | Huawei, China Unicom | CR | Agreement | Yes |
Yes
| revised | No | S5‑252942 | S5‑251971 | ||
S5‑252942 | Rel-19 CR TS 28.541 Add AIOTF and ADM IOC to support management of Ambient IoT | Huawei, China Unicom | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252486 | |||
S5‑252652 | Rel-19 CR TS 28.540 Enhance description of WAB-gNB management | Ericsson Espańa S.A. | CR | Agreement | Yes |
Yes
| revised | No | S5‑252943 | |||
S5‑252943 | Rel-19 CR TS 28.540 Enhance description of WAB-gNB management | Ericsson Espańa S.A. | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252652 | |||
S5‑252653 | Rel-19 CR TS 28.541 Enhancing slicing provisioning request | Ericsson Espańa S.A, AT&T | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑252679 | Rel-19 CR 28.540 Add NRM requirement for NF identities used in managment data | Ericsson Canada Inc. | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑252680 | Rel-19 CR 28.622 Add NF instance id to managed function (stage2) | Ericsson Canada Inc. | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑252681 | Rel-19 CR 28.623 Add NF instance id to managed function (stage3, yaml) | Ericsson Canada Inc. | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑252682 | Rel-19 CR 28.623 Add NF instance id to managed function (stage3, yang) | Ericsson Canada Inc. | CR | Approval | Yes |
Yes
| not pursued | No | ||||
6.19.14 | Subscriber and Equipment Trace and QoE collection management | S5‑252230 | Rel-19 CR TS 32.423 Corrections on Trace Record Format | Ericsson, AT&T | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑251984 | |
S5‑252269 | Rel-19 CR TS 32.423 Enhancement on Trace Record Header | Ericsson, AT&T | CR | Agreement | Yes |
Yes
| agreed | No | ||||
6.19.15 | Study on Management Aspects of NTN Phase 2 (completed) |   | ||||||||||
6.19.15.1 | Management Aspects of NTN Phase 2 | S5‑252391 | Rel-19 CR TS 28.708 Add attributes to support Store and Forward Satellite operation for EPC | Samsung | CR | Agreement | Yes |
Yes
| revised | No | S5‑252952 | S5‑252027 |
S5‑252952 | Rel-19 CR TS 28.708 Add attributes to support Store and Forward Satellite operation for EPC | Samsung | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252391 | |||
S5‑252393 | Rel-19 CR TS 28.709 Add attributes to support Store and Forward Satellite operation for EPC stage 3 | Samsung | CR | Agreement | Yes |
Yes
| revised | No | S5‑252953 | S5‑252028 | ||
S5‑252953 | Rel-19 CR TS 28.709 Add attributes to support Store and Forward Satellite operation for EPC stage 3 | Samsung | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252393 | |||
S5‑252482 | Rel-19 CR TS 28.541 NRM enhancement for configuring AMF with TAIs supported by NTN gNB | Huawei, CATT, China Unicom | CR | Agreement | Yes |
Yes
| revised | No | S5‑252954 | |||
S5‑252954 | Rel-19 CR TS 28.541 NRM enhancement for configuring AMF with TAIs supported by NTN gNB | Huawei, CATT, China Unicom | CR | Agreement | Yes |
Yes
| endorsed | No | S5‑252482 | |||
S5‑252488 | Rel-19 CR TS 28.540 Requirements for configuring AMF with TAIs supported by NTN gNB | Huawei, CATT, China Unicom, China Mobile | CR | Agreement | Yes |
Yes
| endorsed | No | S5‑250933 | |||
S5‑252564 | Rel-19 CR TS 28.540 Add new requirements to support broadcast multiple TACs for NTN | CATT | CR | Approval | Yes |
Yes
| revised | No | S5‑252955 | |||
S5‑252955 | Rel-19 CR TS 28.540 Add new requirements to support broadcast multiple TACs for NTN | CATT | CR | Approval | Yes |
Yes
| agreed | No | S5‑252564 | |||
S5‑252565 | Rel-19 CR TS 28.541 Add solution to support broadcast multiple TACs for NTN | CATT | CR | Approval | Yes |
Yes
| revised | No | S5‑252956 | |||
S5‑252956 | Rel-19 CR TS 28.541 Add solution to support broadcast multiple TACs for NTN | CATT | CR | Approval | Yes |
Yes
| agreed | No | S5‑252565 | |||
S5‑252566 | Rel-19 CR TS 28.658 Add solution for NTN TACList configuration | CATT | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑252567 | Rel-19 CR TS 28.659 Add attributes to support Store and Forward Satellite operation for eNB stage3 | CATT | CR | Approval | Yes |
Yes
| agreed | No | ||||
6.19.16 | Study on management of IAB nodes (completed) |   | ||||||||||
6.19.16.1 | Management of IAB nodes | S5‑252704 | Requirements for IAB-node configuration | Ericsson | CR | Approval | Yes |
Yes
| agreed | No | ||
S5‑252957 | Requirements for IAB-node configuration | Ericsson | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑252705 | Use case IAB-node configuration | Ericsson | CR | Approval | Yes |
Yes
| revised | No | S5‑252958 | |||
S5‑252958 | Use case IAB-node configuration | Ericsson | CR | Approval | Yes |
Yes
| revised | No | S5‑253103 | S5‑252705 | ||
S5‑253103 | Use case IAB-node configuration | Ericsson | CR | Approval | Yes |
Yes
| agreed | No | S5‑252958 | |||
6.19.17 | Study on management aspects of RedCap feature(completed) |   | ||||||||||
6.19.17.1 | Management Aspects of RedCap features | S5‑252470 | Rel-19 CR TS 28.552 Add new filter for PDCP PDU data volume measurements for RedCap service | China Unicom, ZTE | CR | Agreement | Yes |
Yes
| revised | No | S5‑252924 | |
S5‑252924 | Rel-19 CR TS 28.552 Add new filter for PDCP PDU data volume measurements for RedCap service | China Unicom, ZTE | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252470 | |||
S5‑252471 | Rel-19 CR TS 28.552 Add new filter for throughput measurements for RedCap service | China Unicom, ZTE | CR | Agreement | Yes |
Yes
| revised | No | S5‑252925 | |||
S5‑252925 | Rel-19 CR TS 28.552 Add new filter for throughput measurements for RedCap service | China Unicom, ZTE | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252471 | |||
S5‑252472 | Rel-19 CR TS 28.552 Add new filter for RRC connection number measurements for RedCap service | China Unicom, ZTE | CR | Agreement | Yes |
Yes
| revised | No | S5‑252926 | |||
S5‑252926 | Rel-19 CR TS 28.552 Add new filter for RRC connection number measurements for RedCap service | China Unicom, ZTE | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252472 | |||
S5‑252736 | Rel-19 CR TS 28.541 Enhancing NR NRM to control RedCap and e-RedCap UEs access | Samsung Electronics France SA | CR | Approval | Yes |
Yes
| revised | No | S5‑252927 | |||
S5‑252927 | Rel-19 CR TS 28.541 Enhancing NR NRM to control RedCap and e-RedCap UEs access | Samsung Electronics France SA | CR | Approval | Yes |
Yes
| revised | No | S5‑253105 | S5‑252736 | ||
S5‑253105 | Rel-19 CR TS 28.541 Enhancing NR NRM to control RedCap and e-RedCap UEs access | Samsung Electronics France SA | CR | Approval | Yes |
Yes
| agreed | No | S5‑252927 | |||
6.19.18 | Study on Enhancement of Management Aspects related to NWDAF Phase 2 (completed) |   | ||||||||||
6.19.18.1 | Enhancement of Management Aspects related to NWDAF Phase 2 | S5‑252641 | WI summary for Enhancement of Management Aspects Related of NWDAF Phase 2 | China Telecom Corporation Ltd. | discussion | Discussion | Yes |
Yes
| noted | No | ||
6.19.19 | Study on Management of Network Sharing Phase 3 (completed) |   | ||||||||||
6.19.19.1 | Management of Network Sharing Phase 3 | S5‑252296 | Rel-19 CR TS 28.552 Add PLMN granularity performance measurement of UDM in the Indirect Network Sharing Scenario | China Telecom, China Unicom | CR | Agreement | Yes |
Yes
| revised | No | S5‑252959 | |
S5‑252959 | Rel-19 CR TS 28.552 Add PLMN granularity performance measurement of UDM in the Indirect Network Sharing Scenario | China Telecom, China Unicom | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252296 | |||
S5‑252297 | Rel-19 CR TS 28.552 Add PLMN granularity performance measurement of PDU session for SMF | China Telecom, China Unicom | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑252298 | Rel-19 CR TS 28.552 Add PLMN granularity performance measurement of initial registration for AMF | China Telecom, China Unicom | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑252670 | Rel-19 CR TS 32.130 Add figures of Indirect Network Sharing | China Unicom | CR | Agreement | Yes |
Yes
| revised | No | S5‑252961 | |||
S5‑252961 | Rel-19 CR TS 32.130 Add figures of Indirect Network Sharing | China Unicom | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252670 | |||
S5‑252671 | Rel-19 CR TS 32.130 Correct editorial errors | China Unicom | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑252674 | Rel-19 CR TS 32.130 Add management workflows for requirements for management of INS | China Unicom | CR | Agreement | Yes |
Yes
| revised | No | S5‑252960 | |||
S5‑252960 | Rel-19 CR TS 32.130 Add management workflows for requirements for management of INS | China Unicom | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252674 | |||
S5‑252675 | Discussion paper on reorganizing TS 32.130 | China Unicom | discussion | Endorsement | No |
Yes
| withdrawn | Yes | ||||
6.19.20 | Study on energy efficiency and energy saving aspects of 5G networks and services (completed) |   | ||||||||||
6.19.20.1 | Energy efficiency and energy saving aspects of 5G networks and services | S5‑252310 | Rel-19 CR TS 28.310 Add use case and requirements for energy related information | Nokia, Huawei, Orange, AT&T, NTT DOCOMO | CR | Agreement | Yes |
Yes
| revised | No | S5‑252919 | |
S5‑252919 | Rel-19 CR TS 28.310 Add use case and requirements for energy related information | Nokia, Huawei, Orange, AT&T, NTT DOCOMO, Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252310 | |||
S5‑252311 | Rel-19 CR TS 28.310 Introduce energy related information NRM | Nokia, Huawei, Orange, AT&T, NTT DOCOMO | CR | Agreement | Yes |
Yes
| merged | No | S5‑252920 | |||
S5‑252312 | Rel-19 CR TS 28.623 Update stage 3 to support energy related information NRM | Nokia, Huawei, Orange, AT&T, NTT DOCOMO | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑252313 | Rel-19 CR TS 28.104 Enhance the MDA assisted Energy Saving use case for handling of power shortages | Nokia | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑253016 | Rel-19 CR TS 28.104 Enhance the MDA assisted Energy Saving use case for handling of power shortages | Nokia | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
S5‑252315 | Rel-19 CR TS 28.310 Add solution on Energy saving optimization for multi-carrier RAN scenarios | Nokia | CR | Agreement | Yes |
Yes
| revised | No | S5‑253017 | |||
S5‑253017 | Rel-19 CR TS 28.310 Add solution on Energy saving optimization for multi-carrier RAN scenarios | Nokia | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑252315 | |||
S5‑252317 | Rel-19 CR TS 28.541 Add NRM solution on Energy saving optimization for multi-carrier RAN scenarios | Nokia | CR | Agreement | Yes |
Yes
| revised | No | S5‑253018 | |||
S5‑253018 | Rel-19 CR TS 28.541 Add NRM solution on Energy saving optimization for multi-carrier RAN scenarios | Nokia | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑252317 | |||
S5‑252428 | Rel-19 CR TS 28.310 Updates to energy consumption VNF | NTT DOCOMO, Rakuten Mobile, ZTE Corporation | CR | Agreement | Yes |
Yes
| revised | No | S5‑252917 | |||
S5‑252917 | Rel-19 CR TS 28.310 Updates to energy consumption VNF | NTT DOCOMO, Rakuten Mobile, ZTE Corporation | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑252428 | |||
S5‑252429 | Rel-19 CR TS 28.554 Updates to NF energy consumption based on VNF | NTT DOCOMO, Rakuten Mobile, ZTE Corporation | CR | Agreement | Yes |
Yes
| revised | No | S5‑252918 | |||
S5‑252918 | Rel-19 CR TS 28.554 Updates to NF energy consumption based on VNF | NTT DOCOMO, Rakuten Mobile, ZTE Corporation | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑252429 | |||
S5‑252452 | Rel-19 CR TS 28.310 Add use case and requirements for energy information | Ericsson | CR | Yes |
Yes
| merged | No | S5‑252919 | ||||
S5‑252453 | Rel-19 CR TS 28.310 Add information model definitions for energy information | Ericsson | CR | Yes |
Yes
| revised | No | S5‑252920 | ||||
S5‑252920 | Rel-19 CR TS 28.310 Add information model definitions for energy information | Ericsson, Nokia, Huawei, Orange, AT&T, NTT DOCOMO | CR | - | Yes |
Yes
| agreed | No | S5‑252453 | |||
S5‑252480 | Rel-19 CR TS 28.310 Add use case and requirements for carbon emission measurement | Huawei, China Mobile | CR | Agreement | Yes |
Yes
| revised | No | S5‑252921 | |||
S5‑252921 | Rel-19 CR TS 28.310 Add use case and requirements for carbon emission measurement | Huawei, China Mobile | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑252480 | |||
S5‑252481 | Rel-19 CR TS 28.552 Add the measurement of carbon emission related KPIs for gNB | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑252922 | Rel-19 CR TS 28.554 Add the measurement of carbon emission related KPIs for gNB | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑252600 | Rel-19 CR TS 28.554 Add multi-dimensional energy efficiency use case | Huawei, China Unicom, China Mobile | CR | Agreement | Yes |
Yes
| revised | No | S5‑252923 | |||
S5‑252923 | Rel-19 CR TS 28.554 Add multi-dimensional energy efficiency use case | Huawei, China Unicom, China Mobile, China Telecom, Orange, Verizon, AT&T, Samsung | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252600 | |||
S5‑252601 | Rel-19 CR TS 28.554 Add EE KPIs evaluated from network availability performance dimension | Huawei, China Unicom | CR | Agreement | Yes |
Yes
| revised | No | S5‑253011 | |||
S5‑253011 | Rel-19 CR TS 28.554 Add EE KPIs evaluated from network availability performance dimension | Huawei, China Unicom, China Mobile, China Telecom, Orange, Verizon, AT&T, Samsung | CR | Agreement | Yes |
Yes
| revised | No | S5‑253084 | S5‑252601 | ||
S5‑253084 | Rel-19 CR TS 28.554 Add EE KPIs evaluated from network availability performance dimension | Huawei, China Unicom, China Mobile, China Telecom, Orange, Verizon, AT&T, Samsung | CR | Agreement | Yes |
Yes
| agreed | No | S5‑253011 | |||
S5‑252602 | Rel-19 CR TS 28.554 Add EE KPIs evaluated from network quality performance dimension | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑253012 | |||
S5‑253012 | Rel-19 CR TS 28.554 Add EE KPIs evaluated from network quality performance dimension | Huawei, China Mobile, China Telecom, Orange, Verizon, AT&T | CR | Agreement | Yes |
Yes
| revised | No | S5‑253085 | S5‑252602 | ||
S5‑253085 | Rel-19 CR TS 28.554 Add EE KPIs evaluated from network quality performance dimension | Huawei, China Mobile, China Telecom, Orange, Verizon, AT&T | CR | Agreement | Yes |
Yes
| agreed | No | S5‑253012 | |||
S5‑252603 | Rel-19 CR TS 28.310 Update EE KPIs overview | Huawei, China Unicom | CR | Agreement | Yes |
Yes
| revised | No | S5‑253013 | |||
S5‑253013 | Rel-19 CR TS 28.310 Update EE KPIs overview | Huawei, China Unicom, China Mobile, China Telecom, Orange, Verizon, AT&T, Samsung | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252603 | |||
6.19.21 | Study on Enhanced OAM for management exposure to external consumers (completed) |   | ||||||||||
6.19.21.1 | Enhanced OAM for management service exposure to external consumers through CAPIF | S5‑252398 | Rel-19 pCR 28.561 UC and solution for consumer getting authorization to access MnS | Samsung | pCR | Agreement | Yes |
Yes
| merged | No | S5‑252951 | |
S5‑252950 | Rel-19 pCR 28.561 UC and solution for consumer getting authorization to access MnS | Samsung | pCR | Agreement | No |
Yes
| withdrawn | Yes | ||||
S5‑252596 | pCR TS 28.579 Add introduction content | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑252947 | |||
S5‑252947 | pCR TS 28.579 Add introduction content | Huawei, Nokia, Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S5‑252596 | |||
S5‑252655 | Rel-19 pCR TS 28.579 Fix wrong reference | Ericsson Espańa S.A. | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑252656 | Presentation of TS 28.579 to SA for Information | Nokia Belgium | TS or TR cover | Approval | Yes |
Yes
| revised | No | S5‑253083 | |||
S5‑253083 | Presentation of TS 28.579 to SA for Information | Nokia Belgium | TS or TR cover | Approval | Yes |
Yes
| approved | No | S5‑252656 | |||
S5‑252660 | Discussion paper on CCF generating access token for external MnS consumers | Nokia Belgium | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑252661 | Rel-19 pCR TS 28.579 Add MSED deployment options | Nokia Belgium | pCR | Approval | Yes |
Yes
| revised | No | S5‑252948 | |||
S5‑252948 | Rel-19 pCR TS 28.579 Add MSED deployment options | Nokia, Huawei, Samsung, Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S5‑252661 | |||
S5‑252662 | Rel-19 pCR TS 28.579 Add use case and requirements for authorization of the external MnS consumers at the CCF | Nokia Belgium | pCR | Approval | Yes |
Yes
| revised | No | S5‑252949 | |||
S5‑252949 | Rel-19 pCR TS 28.579 Add use case and requirements for authorization of the external MnS consumers at the CCF | Nokia, Samsung | pCR | Approval | Yes |
Yes
| noted | No | S5‑252662 | |||
S5‑252663 | Rel-19 pCR TS 28.579 Add use case solution for authorization of the external MnS consumers at the CCF | Nokia Belgium | pCR | Approval | Yes |
Yes
| revised | No | S5‑252951 | |||
S5‑252951 | Rel-19 pCR TS 28.579 Add use case solution for authorization of the external MnS consumers at the CCF | Nokia, Samsung | pCR | Approval | Yes |
Yes
| noted | No | S5‑252663 | |||
S5‑252824 | Draft TS28.579 | Nokia | draft TS | Agreement | No |
Yes
| reserved | No | ||||
6.19.22 | Management for MonStra (completed) |   | ||||||||||
7 | Charging | S5‑252791 | (reserved) | CH | other | discussion | No |
Yes
| withdrawn | Yes | ||
S5‑252792 | (reserved) | CH | other | discussion | No |
Yes
| withdrawn | Yes | ||||
S5‑252793 | (reserved) | CH | other | discussion | No |
Yes
| withdrawn | Yes | ||||
S5‑252794 | (reserved) | CH | other | discussion | No |
Yes
| withdrawn | Yes | ||||
S5‑252795 | (reserved) | CH | other | discussion | No |
Yes
| withdrawn | Yes | ||||
S5‑252796 | (reserved) | CH | other | discussion | No |
Yes
| withdrawn | Yes | ||||
S5‑252797 | (reserved) | CH | other | discussion | No |
Yes
| withdrawn | Yes | ||||
S5‑252798 | (reserved) | CH | other | discussion | No |
Yes
| withdrawn | Yes | ||||
S5‑252799 | (reserved) | CH | other | discussion | No |
Yes
| withdrawn | Yes | ||||
S5‑252800 | (reserved) | CH | other | discussion | No |
Yes
| withdrawn | Yes | ||||
S5‑252801 | (reserved) | CH | other | discussion | No |
Yes
| withdrawn | Yes | ||||
S5‑252802 | (reserved) | CH | other | discussion | No |
Yes
| withdrawn | Yes | ||||
S5‑252803 | (reserved) | CH | other | discussion | No |
Yes
| withdrawn | Yes | ||||
S5‑252804 | (reserved) | CH | other | discussion | No |
Yes
| withdrawn | Yes | ||||
S5‑252805 | (reserved) | CH | other | discussion | No |
Yes
| withdrawn | Yes | ||||
S5‑252806 | (reserved) | CH | other | discussion | No |
Yes
| withdrawn | Yes | ||||
S5‑252807 | (reserved) | CH | other | discussion | No |
Yes
| withdrawn | Yes | ||||
S5‑252808 | (reserved) | CH | other | discussion | No |
Yes
| withdrawn | Yes | ||||
S5‑252809 | (reserved) | CH | other | discussion | No |
Yes
| withdrawn | Yes | ||||
S5‑252810 | (reserved) | CH | other | discussion | No |
Yes
| withdrawn | Yes | ||||
S5‑252811 | (reserved) | CH | other | discussion | No |
Yes
| withdrawn | Yes | ||||
S5‑252812 | (reserved) | CH | other | discussion | No |
Yes
| withdrawn | Yes | ||||
S5‑252813 | (reserved) | CH | other | discussion | No |
Yes
| withdrawn | Yes | ||||
S5‑252814 | (reserved) | CH | other | discussion | No |
Yes
| withdrawn | Yes | ||||
S5‑252815 | (reserved) | CH | other | discussion | No |
Yes
| withdrawn | Yes | ||||
S5‑252816 | (reserved) | CH | other | discussion | No |
Yes
| withdrawn | Yes | ||||
7.1 | Charging Plenary | S5‑252215 | agenda_with_Tdocs_sequence_CH | SWG CH Chair (MATRIXX Software) | agenda | Yes |
Yes
| revised | No | S5‑252738 | ||
S5‑252738 | agenda_with_Tdocs_sequence_CH | SWG CH Chair (MATRIXX Software) | agenda | - | Yes |
Yes
| noted | No | S5‑252215 | |||
S5‑252216 | Charging exec report | SWG CH Chair (MATRIXX Software) | report | Yes |
Yes
| noted | No | |||||
S5‑252217 | Collection of useful contributions and external communication documents in CH | SWG Vice Chair (Huawei Tech.(UK) Co.. Ltd) | other | Yes |
Yes
| noted | No | |||||
S5‑252334 | LS on Extending Charging Support in 5GC | CT3 | LS in | Information | Yes |
Yes
| replied to | No | ||||
7.2 | New Charging Study/Work Item proposals | S5‑252739 | New WID on Charging Aspects of CAPIF Phase 3 | Nokia | WID new | Agreement | Yes |
Yes
| revised | No | S5‑253100 | |
S5‑253100 | New WID on Converged Charging Aspects of CAPIF Phase 3 | Nokia | WID new | Agreement | Yes |
Yes
| agreed | No | S5‑252739 | |||
7.3 | Charging Maintenance and Rel-19 Charging small enhancements | S5‑252409 | Remove the editor note in clause 6.5.2.1 | China Telecom | CR | Yes |
Yes
| not pursued | No | |||
S5‑252410 | Remove the editor note in clause 6.5.2.1 | China Telecom | CR | Yes |
Yes
| not pursued | No | |||||
S5‑252411 | Remove the editor note in clause 6.5.2.1 | China Telecom | CR | Yes |
Yes
| revised | No | S5‑252782 | ||||
S5‑252782 | Rel-19 CR 32.277 Remove the editor note in clause 6.5.2.1 and correct the container format | China Telecom | CR | - | Yes |
Yes
| agreed | No | S5‑252411 | |||
S5‑252496 | Discussion on NSPA charging information correction | Huawei | discussion | Discussion | Yes |
Yes
| noted | No | ||||
S5‑252497 | Rel-18 CR 28.201 Correction on NSPA charging information | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑252778 | S5‑251302 | ||
S5‑252778 | Rel-18 CR 28.201 Correction on NSPA charging information | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252497 | |||
S5‑252498 | Rel-19 CR 28.201 Correction on NSPA charging information | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑251303 | |||
S5‑252779 | Rel-19 CR 28.201 Addition on NSPA charging information | Huawei | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
S5‑252499 | Rel-18 CR 32.291 Correction on NSPA charging information | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑251304 | |||
S5‑252500 | Rel-19 CR 32.291 Correction on NSPA charging information | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑251305 | |||
S5‑252780 | Rel-19 CR 32.291 Addition on NSPA charging information | Huawei | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
S5‑252501 | Rel-18 CR 32.298 Correction on NSPA charging information | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑251306 | |||
S5‑252502 | Rel-19 CR 32.298 Correction on NSPA charging information | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑251307 | |||
S5‑252781 | Rel-19 CR 32.298 Correction on NSPA charging information | Huawei | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
S5‑252536 | Rel-17 CR 32.298 Correction of externalIndividualIdList | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑252537 | Rel-18 CR 32.298 Correction of externalIndividualIdList | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑251853 | |||
S5‑252538 | Rel-19 CR 32.298 Correction of externalIndividualIdList | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑251854 | |||
S5‑252539 | Rel-18 CR 32.255 Correction of charging identifier handling by I-SMF | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑252789 | |||
S5‑252789 | Rel-18 CR 32.255 Correction of charging identifier handling by I-SMF | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252539 | |||
S5‑252540 | Rel-19 CR 32.255 Correction of charging identifier handling by I-SMF | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑252790 | |||
S5‑252790 | Rel-19 CR 32.255 Correction of charging identifier handling by I-SMF | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252540 | |||
S5‑252541 | Rel-18 CR 32.255 Correction of missing A-CHF definition | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑252784 | |||
S5‑252784 | Rel-18 CR 32.255 Correction of missing A-CHF definition | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252541 | |||
S5‑252542 | Rel-19 CR 32.255 Correction of missing A-CHF definition | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑252785 | |||
S5‑252785 | Rel-19 CR 32.255 Correction of missing A-CHF definition | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252542 | |||
S5‑252543 | Rel-18 CR 28.201 Correction of NSPA Container Information reference | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑252786 | |||
S5‑252786 | Rel-18 CR 28.201 Correction of NSPA Container Information reference | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252543 | |||
S5‑252544 | Rel-19 CR 28.201 Correction of NSPA Container Information reference | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑252787 | |||
S5‑252787 | Rel-19 CR 28.201 Correction of NSPA Container Information reference | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252544 | |||
S5‑252611 | IMS Call charging capability optimization | CSCN | discussion | Yes |
Yes
| noted | No | |||||
S5‑252613 | IMS Call charging capability optimization | CSCN | CR | Yes |
Yes
| not pursued | No | |||||
S5‑252783 | Rel-19 CR 28.201 Correction on NSPA charging information | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
7.4 | Rel-19 Work Items |   | ||||||||||
7.4.1 | CHF Segmentation | S5‑252504 | Rel-19 CR 32.255 Clarify the CHF selection method | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑252740 | |
S5‑252740 | Rel-19 CR 32.255 Clarify the CHF selection method | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252504 | |||
S5‑252505 | Rel-19 CR 32.256 Clarify the CHF selection method | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑252741 | |||
S5‑252741 | Rel-19 CR 32.256 Clarify the CHF selection method | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252505 | |||
S5‑252545 | LS_reply_Extending Charging support in 5GC | Ericsson | LS out | Approval | Yes |
Yes
| revised | No | S5‑252742 | |||
S5‑252742 | LS_reply_Extending Charging support in 5GC | Ericsson | LS out | Approval | Yes |
Yes
| revised | No | S5‑253101 | S5‑252545 | ||
S5‑253101 | LS_reply_Extending Charging support in 5GC | Ericsson | LS out | Approval | Yes |
Yes
| approved | No | S5‑252742 | |||
7.4.2 | Charging Aspects of Ranging and Sidelink Positioning (completed) |   | ||||||||||
7.4.3 | Charging aspects for energy efficiency of network slice (completed) |   | ||||||||||
7.4.4 | Charging for indirect network sharing (completed) |   | ||||||||||
7.4.5 | Charging Aspects for 5G ProSe Ph3 | S5‑252412 | Add information flows of layer-3 ProSe UE-to-UE relay communication | China Telecom | CR | Yes |
Yes
| revised | No | S5‑252743 | ||
S5‑252743 | Add information flows of layer-3 ProSe UE-to-UE relay communication | China Telecom | CR | - | Yes |
Yes
| agreed | No | S5‑252412 | |||
S5‑252413 | Add information elements to support Layer-3 ProSe UE-to-UE relay communication | China Telecom | CR | Yes |
Yes
| agreed | No | |||||
7.4.6 | Charging aspects of satellite access Phase 3 | S5‑252511 | Add charging information for store and forward satellite operation of SMS service | CATT | CR | Agreement | Yes |
Yes
| revised | No | S5‑252752 | |
S5‑252752 | Rel-19 CR 32.298 Add charging information for store and forward satellite operation of SMS service | CATT | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252511 | |||
S5‑252546 | Rel-19 CR 32.255 Addition of satellite backhaul category | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑252746 | |||
S5‑252746 | Rel-19 CR 32.255 Addition of satellite backhaul category | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252546 | |||
S5‑252621 | Add MVNO charging which provides satellite service | CSCN | CR | Agreement | Yes |
Yes
| revised | No | S5‑252747 | |||
S5‑252747 | Rel-19 CR 32.255 Add MVNO charging which provides satellite service | CSCN | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252621 | |||
S5‑252625 | Add MVNO charging which provides satellite access service | CSCN | CR | Agreement | Yes |
Yes
| revised | No | S5‑252748 | |||
S5‑252748 | Rel-19 CR 32.256 Add MVNO charging which provides satellite access service | CSCN | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252625 | |||
S5‑252627 | Add MVNO charging which provides satellite service | CSCN | CR | Agreement | Yes |
Yes
| revised | No | S5‑252749 | |||
S5‑252749 | Add MVNO charging which provides satellite service | CSCN | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252627 | |||
S5‑252628 | Add satellite resource usage charging between SSP and MNO for 5G satellite backhaul without UPF on-board | CSCN | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑252629 | Add satellite resource usage charging between SSP and MNO with UPF on board for edge computing | CSCN | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑252630 | Add satellite resource usage charging between SSP and MNO | CSCN | CR | Agreement | Yes |
Yes
| merged | No | S5‑252749 | |||
S5‑252667 | Add charging information for UE-satellite-UE charging to CHF CDR | CATT | CR | Approval | Yes |
Yes
| revised | No | S5‑252753 | |||
S5‑252753 | Rel-19 CR 32.298 Add charging information for UE-satellite-UE charging to CHF CDR | CATT | CR | Approval | Yes |
Yes
| agreed | No | S5‑252667 | |||
S5‑252697 | Add Open API for UE-satellite-UE charging | CATT | CR | Agreement | Yes |
Yes
| revised | No | S5‑252751 | |||
S5‑252751 | Rel-19 CR 32.291 Add Data Type and Open API for UE-satellite-UE charging | CATT | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252697 | |||
S5‑252703 | Add Data Type for UE-satellite-UE charging | CATT | CR | Agreement | Yes |
Yes
| merged | No | S5‑252751 | |||
S5‑252707 | Add charging principle for UE-satellite-UE communication | CATT | CR | Approval | Yes |
Yes
| revised | No | S5‑252750 | S5‑251812 | ||
S5‑252750 | Add charging principle for UE-satellite-UE communication | CATT | CR | Approval | Yes |
Yes
| agreed | No | S5‑252707 | |||
7.4.7 | Charging aspects of CAPIF | S5‑252307 | Rel-19 CR 32.291 CAPIF Attribute | Nokia | CR | Agreement | Yes |
Yes
| revised | No | S5‑252759 | |
S5‑252759 | Rel-19 CR 32.291 CAPIF Attribute | Nokia | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252307 | |||
S5‑252308 | Rel-19 CR 32.291 CAPIF EnumerationValue | Nokia | CR | Agreement | Yes |
Yes
| revised | No | S5‑252760 | |||
S5‑252760 | Rel-19 CR 32.291 CAPIF EnumerationValue | Nokia | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252308 | |||
S5‑252309 | Rel-19 CR 32.291 CAPIF Service | Nokia | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑252379 | Rel-19 CR 32.254 CAPIF API Invoker Charging Flow | Nokia | CR | Agreement | Yes |
Yes
| revised | No | S5‑252756 | |||
S5‑252756 | Rel-19 CR 32.254 CAPIF API Invoker Charging Flow | Nokia, Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252379 | |||
S5‑252380 | Rel-19 CR 32.254 CAPIF Triggers | Nokia | CR | Agreement | Yes |
Yes
| revised | No | S5‑252755 | |||
S5‑252755 | Rel-19 CR 32.254 CAPIF Triggers | Nokia | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252380 | |||
S5‑252381 | Rel-19 CR 32.254 CAPIF Service API Charging Flow | Nokia | CR | Agreement | Yes |
Yes
| merged | No | S5‑252756 | |||
S5‑252382 | Rel-19 CR 32.254 CAPIF API Invoker Charging Flow | Nokia | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
S5‑252383 | Rel-19 CR 32.254 CAPIF Message Flows Introduction | Nokia | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑252494 | Rel-19 CR 32.254 Addition of the CAPIF Charging Principle | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑252754 | |||
S5‑252754 | Rel-19 CR 32.254 Addition of the CAPIF Charging Principle | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252494 | |||
S5‑252495 | Rel-19 CR 32.254 Addition of the CAPIF Charging Procedure | Huawei | CR | Agreement | Yes |
Yes
| merged | No | S5‑252756 | |||
S5‑252547 | Rel-19 CR 32.254 Addition of CAPIF specific charging information | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑252757 | |||
S5‑252757 | Rel-19 CR 32.254 Addition of CAPIF specific charging information | Ericsson, Nokia | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252547 | |||
S5‑252731 | Rel-19 CR 32.254 CAPIF Exposure API Function | Nokia | CR | Agreement | Yes |
Yes
| merged | No | S5‑252757 | |||
S5‑252758 | Rel-19 CR 32.254 CAPIF Exposure API Function | Nokia | CR | Agreement | Yes |
Yes
| withdrawn | Yes | ||||
S5‑252732 | Rel-19 CR 32.254 CAPIF NEF API Charging Information | Nokia | CR | Agreement | Yes |
Yes
| merged | No | S5‑252757 | |||
7.4.8 | Charging aspects of next generation real time communication services phase 2 | S5‑252487 | Rel-19 CR 32.260 Charging principle for Avatar communication charging | China Mobile | CR | Approval | Yes |
Yes
| revised | No | S5‑252744 | |
S5‑252744 | Rel-19 CR 32.260 Charging principle for Avatar communication charging | China Mobile | CR | Approval | Yes |
Yes
| agreed | No | S5‑252487 | |||
S5‑252489 | Rel-19 CR 32.260 Charging information for Avatar communication charging | China Mobile | CR | Approval | Yes |
Yes
| revised | No | S5‑252745 | |||
S5‑252745 | Rel-19 CR 32.260 Charging information for Avatar communication charging | China Mobile | CR | Approval | Yes |
Yes
| agreed | No | S5‑252489 | |||
7.4.9 | Charging for Uncrewed Aerial Systems Phase 2 | S5‑252584 | Add UAS charging requirements | China Mobile Com. Corporation | CR | Agreement | Yes |
Yes
| revised | No | S5‑252761 | |
S5‑252761 | Add UAS charging requirements | China Mobile Com. Corporation | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252584 | |||
S5‑252585 | Add extended user information | China Mobile Com. Corporation | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑252762 | Add extended user information | China Mobile Com. Corporation | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
S5‑252586 | Add UAS charging requirements | China Mobile Com. Corporation | CR | Agreement | Yes |
Yes
| revised | No | S5‑252763 | |||
S5‑252763 | Add UAS charging requirements | China Mobile Com. Corporation | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252586 | |||
S5‑252587 | Add extended user information | China Mobile Com. Corporation | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑252764 | Add extended user information | China Mobile Com. Corporation | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
S5‑252592 | Add charging principles for UAS charging | China Mobile Com. Corporation | CR | Agreement | Yes |
Yes
| revised | No | S5‑252765 | |||
S5‑252765 | Add charging principles for UAS | China Mobile Com. Corporation | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252592 | |||
S5‑252788 | LS on UE type identification for UAS charging requirements | CMCC | LS out | Approval | No |
Yes
| reserved | No | ||||
7.4.10 | Charging Aspects of 5GC LoCation Services | S5‑252302 | Rel-19 CR TS 32.291 Introduce OpenAPI extension for 5GS LCS | China Telecom | CR | Approval | Yes |
Yes
| revised | No | S5‑252766 | |
S5‑252766 | Rel-19 CR TS 32.291 Introduce OpenAPI extension for 5GS LCS | China Telecom | CR | Approval | Yes |
Yes
| agreed | No | S5‑252302 | |||
S5‑252303 | Rel-19 CR TS 32.298 Add charging information to CDR for 5GS LCS | China Telecom | CR | Approval | Yes |
Yes
| revised | No | S5‑252767 | |||
S5‑252767 | Rel-19 CR TS 32.298 Add charging information to CDR for 5GS LCS | China Telecom | CR | Approval | Yes |
Yes
| agreed | No | S5‑252303 | |||
7.4.11 | Charging for Ambient power-enabled Internet of Things | S5‑252503 | Rel-19 CR 32.254 Add charging support to AIoT service | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑252768 | |
S5‑252768 | Rel-19 CR 32.254 Add charging support to AIoT service | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252503 | |||
7.4.12 | Charging aspects for Multi-Operator Core Network (MOCN) network sharing | S5‑252506 | Discussion on performance measurements for MOCN charging | Huawei | discussion | Discussion | Yes |
Yes
| noted | No | ||
S5‑252507 | Rel-19 CR 28.201 Add charging architecture for MOCN | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑252770 | |||
S5‑252770 | Rel-19 CR 28.201 Add charging architecture for MOCN | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252507 | |||
S5‑252508 | Rel-19 CR 32.255 Removal the addition of charging architecture for MOCN | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑252509 | Rel-19 CR 28.201 Add charging requirement for MOCN | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑252771 | |||
S5‑252771 | Rel-19 CR 28.201 Add charging requirement for MOCN | Huawei, Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252509 | |||
S5‑252510 | Rel-19 CR 32.255 Removal the addition of charging requirements for MOCN | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑252548 | Revised WID on Charging enhancement for MOCN network sharing | Ericsson | WID revised | Agreement | Yes |
Yes
| revised | No | S5‑252769 | |||
S5‑252769 | Revised WID on Charging enhancement for MOCN network sharing | Ericsson | WID revised | Agreement | Yes |
Yes
| agreed | No | S5‑252548 | |||
S5‑252549 | Rel-19 CR 32.255 Addition of charging principles for MOCN | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑252774 | |||
S5‑252774 | Rel-19 CR 32.255 Addition of charging principles for MOCN | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252549 | |||
S5‑252550 | Rel-19 CR 32.255 Addition of basic principles for MOCN | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑252775 | |||
S5‑252775 | Rel-19 CR 32.255 Addition of basic principles for MOCN | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑252550 | |||
S5‑252551 | Rel-19 CR 32.255 Addition of message flow for MOCN | Ericsson | CR | Agreement | Yes |
Yes
| merged | No | S5‑252776 | |||
S5‑252552 | Rel-19 CR 32.255 Addition of charging information for MOCN | Ericsson | CR | Agreement | Yes |
Yes
| merged | No | S5‑252777 | |||
S5‑252553 | Rel-19 CR 32.255 Addition of MOCN specific charging information | Ericsson | CR | Agreement | Yes |
Yes
| merged | No | S5‑252777 | |||
S5‑252772 | Rel-19 CR 32.255 Addition of charging architecture for MOCN | Ericsson, Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑252773 | Rel-19 CR 32.255 Addition of charging requirements for MOCN | Ericsson, Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑251845 | |||
S5‑252776 | Rel-19 CR 28.201 Addition of message flow for MOCN | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑252777 | Rel-19 CR 28.201 Addition of charging information for MOCN | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
7.5 | Charging Studies |   | ||||||||||
7.5.1 | Charging aspects of satellite access Phase 3 (completed) |   | ||||||||||
7.5.2 | Charging Aspects of CAPIF (completed) |   | ||||||||||
7.5.3 | Charging aspects of next generation real time communication services phase 2 (completed) |   | ||||||||||
7.5.4 | Charging aspects of Uncrewed Aerial Vehicle (completed) |   | ||||||||||
8 | Any Other Business |   | ||||||||||
9 | Closing of the meeting |   |