Tdoc List
2023-05-03 11:15
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‑233176 | Agenda | WG Chair | agenda | Yes |
Yes
| approved | No | |||
3 | IPR and legal declaration | S5‑233177 | IPR and legal declaration | WG Chair | other | Yes |
Yes
| noted | No | |||
4 | Meetings and activities reports |   | ||||||||||
4.1 | Last SA5 meeting report | S5‑233178 | 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‑233179 | Post e-meeting email approval status | WG Chair | other | Yes |
No
| available | No | |||
S5‑233187 | SA5 working procedures | WG Chair | other | Yes |
Yes
| approved | No | |||||
S5‑233190 | Process for management of draft TS-TRs | WG Chair | other | Yes |
Yes
| noted | No | |||||
S5‑233193 | SA5#148e E-Meeting Process | WG Chair | other | Yes |
Yes
| revised | No | S5‑233584 | ||||
S5‑233584 | SA5#148e E-Meeting Process | WG Chair | other | - | Yes |
Yes
| noted | No | S5‑233193 | |||
S5‑233406 | SA5 Working Procedures | Nokia, Nokia Shanghai Bell | other | Approval | Yes |
Yes
| revised | No | S5‑233552 | |||
S5‑233552 | SA5 Working Procedures | Nokia, Nokia Shanghai Bell | other | Approval | Yes |
Yes
| approved | No | S5‑233406 | |||
5.2 | Technical issues at SA5 level | S5‑233319 | SA5 Collection of Rel-19 potential topics for SA workshop preparation | SA5 Vice chair (Huawei) | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑233569 | S5‑232752 |
S5‑233569 | SA5 Collection of Rel-19 potential topics for SA workshop preparation | SA5 Vice chair (Huawei) | discussion | Endorsement | Yes |
Yes
| noted | No | S5‑233319 | |||
S5‑233320 | Service Management | Ericsson | other | Yes |
Yes
| endorsed | No | |||||
S5‑233365 | Discussion on Service Management | Nokia | discussion | Agreement | Yes |
Yes
| noted | No | ||||
5.3 | Liaison statements at SA5 level | S5‑233197 | LS on the new work item Y.Arch_NGNe_ncp ""Architectural evolution of NGN control plane by applying SDN technology"" | ITU-T SG13 | LS in | Yes |
Yes
| noted | No | |||
S5‑233201 | Reply LS ccSA5 on 5G capabilities exposure for factories of the future – identified gaps (5G-ACIA-LS-2022-005 / S2-2302175) | S2-2303304 | LS in | Yes |
Yes
| noted | No | |||||
S5‑233202 | LS reply to TSG SA ccSA5 on LS 5G-ACIA-LS-2022-005 on 5G capabilities exposure for factories of the future – identified gaps from 5G ACIA | S3-231387 | LS in | Yes |
Yes
| noted | No | |||||
S5‑233209 | An Invitation to the SA4 Gender Diversity Committee Meetings | S4-230431 | LS in | Yes |
Yes
| noted | No | |||||
S5‑233210 | Reply-LS ccSA5 on Research highlighting potential negated OAuth policy | C4-230487 | LS in | Yes |
Yes
| noted | No | |||||
S5‑233211 | Reply LS ccSA5 on Tracking IANA assignment requests | R3-230802 | LS in | Yes |
Yes
| noted | No | |||||
S5‑233213 | LS reply to TSG SA ccSA5 on LS 5G-ACIA-LS-2022-005 on 5G capabilities exposure for factories of the future – identified gaps from 5G ACIA | S6-231068 | LS in | Yes |
Yes
| noted | No | |||||
S5‑233328 | LS on publication of GSMA OPG and OPAG documents | GSMA | LS in | Yes |
Yes
| replied to | No | |||||
S5‑233543 | Reply to: LS on publication of GSMA OPG and OPAG documents | Huawei | LS out | approval | Yes |
Yes
| approved | No | ||||
S5‑233540 | LS on new Recommendation ITU-T Y.3160 (ex.Y.SLOA-arch) “Architectural framework of end-to-end service level objective guarantee for future networks including IMT-2020”. | ITU-T | LS in | Information | Yes |
Yes
| postponed | No | ||||
5.4 | SA5 meeting calendar | S5‑233191 | SA5 meeting calendar | WG Chair | other | Yes |
Yes
| revised | No | S5‑233553 | ||
S5‑233553 | SA5 meeting calendar | WG Chair | other | - | Yes |
Yes
| noted | No | S5‑233191 | |||
6 | OAM&P |   | ||||||||||
6.1 | OAM&P Plenary | S5‑233180 | OAM&P action list | WG Vice Chair (Huawei) | other | Yes |
Yes
| noted | No | |||
S5‑233181 | agenda_with_Tdocs_sequence_proposal_OAM | WG Vice Chair (Huawei) | agenda | Yes |
Yes
| noted | No | |||||
S5‑233182 | OAM Exec Report | WG Vice Chair (Huawei) | report | No |
No
| reserved | No | |||||
S5‑233183 | OAM Chair notes and conclusions | WG Chair | report | Yes |
No
| available | No | |||||
S5‑233188 | Collection of Rel-18 3GPP SA5 OAM WoP | WG Vice Chair (Huawei) | discussion | Yes |
Yes
| noted | No | |||||
S5‑233189 | Living document for stage 2-3 alignment | WG Chair | other | No |
Yes
| withdrawn | Yes | |||||
S5‑233192 | Time Plan for OAM&P sessions | WG Chair | other | No |
Yes
| withdrawn | Yes | |||||
S5‑233194 | TM Forum Liaison: Update on TM Forum Intent Management API and Ontologies – Connector model and 3GPP connector mode | TM Forum | LS in | Yes |
Yes
| replied to | No | |||||
S5‑233549 | Reply to: TM Forum Liaison: Update on TM Forum Intent Management API and Ontologies – Connector model and 3GPP connector mode | Huawei | LS out | approval | Yes |
Yes
| approved | No | ||||
S5‑233196 | Resubmitted LS on Performance measurement for AI/ML | S2-2211428 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑233550 | Reply to: Resubmitted LS on Performance measurement for AI/ML | Intel | LS out | approval | Yes |
Yes
| approved | No | ||||
S5‑233198 | LS on the consent of draft new Recommendation ITU-T Y.3183 (ex. ITU-T Y.ML-IMT2020-VNS): ""Framework for network slicing management assisted by machine learning leveraging QoE feedback from verticals"" | ITU-T SG13 | LS in | Yes |
Yes
| postponed | No | |||||
S5‑233199 | Resubmitted LS on secured and trusted access to the serving PLMN OAM server by a MBSR | S2-2301465 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑233546 | Reply to: Resubmitted LS on secured and trusted access to the serving PLMN OAM server by a MBSR | Huawei | LS out | approval | Yes |
Yes
| approved | No | ||||
S5‑233200 | Resubmitted LS on O-RAN - Applicability of TS 32.404 in NR | O-RAN | LS in | Yes |
Yes
| replied to | No | |||||
S5‑233551 | Reply to: Resubmitted LS on O-RAN - Applicability of TS 32.404 in NR | Samsung | LS out | approval | Yes |
Yes
| revised | No | S5‑233613 | |||
S5‑233613 | Reply to: Resubmitted LS on O-RAN - Applicability of TS 32.404 in NR | Samsung | LS out | approval | Yes |
Yes
| approved | No | S5‑233551 | |||
S5‑233203 | Reply LS ccSA5 on the user consent for trace reporting | S3-231398 | LS in | Yes |
Yes
| noted | No | |||||
S5‑233204 | Reply LS ccSA5 on user consent of Non-public Network | S3-231399 | LS in | Yes |
Yes
| noted | No | |||||
S5‑233205 | Reply LS ccSA5 on ID of MBS session in MBS QoE configuration | S4-230347 | LS in | Yes |
Yes
| noted | No | |||||
S5‑233206 | Reply LS ccSA5 on QoE measurements in RRC IDLE/INACTIVE states | S4-230369 | LS in | Yes |
Yes
| noted | No | |||||
S5‑233208 | Reply LS on secured and trusted access to the serving PLMN OAM server by a MBSR | S3-231400 | LS in | Yes |
Yes
| postponed | No | |||||
S5‑233212 | Reply LS on handover failures related to MRO for inter-system mobility | R3-230805 | LS in | Yes |
Yes
| noted | No | |||||
S5‑233214 | LS on requirement for network slice management service exposure interface and exposure entities | S6-230793 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑233215 | Resubmitted LS on NCR Solutions | R3-225253 | LS in | Yes |
Yes
| postponed | No | |||||
S5‑233216 | Resubmitted Reply LS to SA5 on TS 28.404/TS 28.405 Clarification | S4-221121 | LS in | Yes |
Yes
| noted | No | |||||
S5‑233217 | Resubmitted LS on RAN3 agreements for NR QoE | R3-222890 | LS in | Yes |
Yes
| noted | No | |||||
S5‑233218 | Resubmitted LS on O-RAN – Transport Network Slicing Enhancement IM/DM TS28.541 | O-RAN | LS in | Yes |
Yes
| postponed | No | |||||
S5‑233243 | LS on work progress of M.fidtom, “Framework of intent driven telecom operation and management” (reply to 3GPP TSG SA5-S5-225599). | ITU-T | LS in | Yes |
Yes
| replied to | No | |||||
S5‑233545 | Reply to: LS on work progress of M.fidtom, “Framework of intent driven telecom operation and management” (reply to 3GPP TSG SA5-S5-225599). | Huawei | LS out | approval | Yes |
Yes
| approved | No | ||||
S5‑233244 | LS on Consent of revised Recommendation ITU-T M.3020, “Management Interface Specification Methodology” (reply to 3GPP TSG SA5-S5-225615) | ITU-T | LS in | Yes |
Yes
| noted | No | |||||
S5‑233245 | LS on the Consent of draft Recommendations ITU-T M.3384 (ex. M.il-AITOM) and M.3385 (ex. M.ilef-AITOM) | ITU-T | LS in | Yes |
Yes
| replied to | No | |||||
S5‑233547 | Reply to: LS on the Consent of draft Recommendations ITU-T M.3384 (ex. M.il-AITOM) and M.3385 (ex. M.ilef-AITOM) | China Mobile | LS out | approval | Yes |
Yes
| revised | No | S5‑233711 | |||
S5‑233711 | Reply to: LS on the Consent of draft Recommendations ITU-T M.3384 (ex. M.il-AITOM) and M.3385 (ex. M.ilef-AITOM) | China Mobile | LS out | approval | Yes |
Yes
| approved | No | S5‑233547 | |||
S5‑233246 | LS on initiation of a new work item M.eiil-AITOM, “Effectiveness indicators of intelligence level for AI enhanced telecom operation and management” | ITU-T | LS in | Yes |
Yes
| replied to | No | |||||
S5‑233548 | Reply to: LS on initiation of a new work item M.eiil-AITOM, “Effectiveness indicators of intelligence level for AI enhanced telecom operation and management” | China Mobile | LS out | approval | Yes |
Yes
| revised | No | S5‑233712 | |||
S5‑233712 | Reply to: LS on initiation of a new work item M.eiil-AITOM, “Effectiveness indicators of intelligence level for AI enhanced telecom operation and management” | China Mobile | LS out | approval | Yes |
Yes
| approved | No | S5‑233548 | |||
S5‑233263 | Rel-18&Rel-19 time plan proposal for OAM | SA5 Vice chair (Huawei),SA5 Chair | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑233555 | S5‑232763 | ||
S5‑233555 | Rel-18&Rel-19 time plan proposal for OAM | SA5 Vice chair (Huawei),SA5 Chair | discussion | Endorsement | Yes |
Yes
| endorsed | No | S5‑233263 | |||
S5‑233322 | Reply LS on interface and exposure entities requirement for network slice management service | L.M. Ericsson Limited | LS out | Approval | Yes |
Yes
| revised | No | S5‑233554 | |||
S5‑233554 | Reply LS on interface and exposure entities requirement for network slice management service | L.M. Ericsson Limited | LS out | Approval | Yes |
Yes
| revised | No | S5‑233624 | S5‑233322 | ||
S5‑233624 | Reply LS on interface and exposure entities requirement for network slice management service | L.M. Ericsson Limited | LS out | Approval | Yes |
Yes
| approved | No | S5‑233554 | |||
S5‑233385 | LS to 5G-ACIA on Management of non-public networks | Huawei | LS out | Approval | Yes |
Yes
| approved | No | ||||
S5‑233391 | S5-23xxxx DP for Rel-19 topic | Samsung Electronics France SA | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑233556 | |||
S5‑233556 | S5-23xxxx DP for Rel-19 topic | Samsung Electronics France SA | discussion | Endorsement | Yes |
Yes
| endorsed | No | S5‑233391 | |||
S5‑233527 | Collection of useful endorsed document and external communication documents | WG Vice Chair (Huawei) | discussion | Yes |
Yes
| noted | No | S5‑232011 | ||||
S5‑233541 | LS to SA5 on E2E Network Slicing Requirements | GSMA | LS in | discussion | Yes |
Yes
| postponed | No | ||||
S5‑233544 | Reply LS on O-RAN – Transport Network Slicing Enhancement IM/DM TS28.541 | Ericsson | LS out | Approval | Yes |
Yes
| noted | No | ||||
6.2 | New OAM&P Work Item proposals |   | ||||||||||
6.2.1 | Intelligence and Automation | S5‑233408 | New WID on autonomous network levels phase 2 | China Mobile, Huawei, AsiaInfo, CATT, ZTE, China Unicom, Intel | WID new | Approval | Yes |
Yes
| noted | No | S5‑232769 | |
6.2.2 | Management Architecture and Mechanisms | S5‑233497 | Updade Release 18 SID on Management Aspects of URLLC | China Unicom | SID revised | Approval | Yes |
Yes
| agreed | No | ||
S5‑233506 | New Rel-18 WID on Management Aspects of URLLC | China Unicom | WID new | Approval | Yes |
Yes
| noted | No | ||||
S5‑233510 | New Rel-18 WID on Management Aspect of 5G Network Sharing Phase2 | China Unicom | WID new | Approval | Yes |
Yes
| noted | No | ||||
S5‑233524 | New WID on Management of cloud-native Virtualized Network Functions | China Mobile,Huawei,AsiaInfo | WID new | Approval | Yes |
Yes
| revised | No | S5‑233557 | |||
S5‑233557 | New WID on Management of cloud-native Virtualized Network Functions | China Mobile,Huawei,AsiaInfo | WID new | Approval | Yes |
Yes
| agreed | No | S5‑233524 | |||
6.2.3 | Support of New Services | S5‑233232 | New Work Item on Network and Service Operations for Energy Utilities | Samsung, EUTC, EDF, BMWK, Deutsche Telekom, Huawei, Ericsson, NOVAMINT | WID new | Agreement | Yes |
Yes
| noted | No | ||
S5‑233236 | FS_NSOEU and NSOEU WoP | Samsung (Rapporteur) | other | Information | Yes |
Yes
| noted | No | ||||
S5‑233237 | Skeleton of new TS 28.abc Network and Services Operations for Energy Utilities | Samsung (Rapporteur) | other | Information | Yes |
Yes
| noted | No | ||||
6.3 | OAM&P Maintenance and Rel-18 small Enhancements |   | ||||||||||
6.3.1 | Methodology |   | ||||||||||
6.3.2 | ANL |   | ||||||||||
6.3.3 | MDAS |   | ||||||||||
6.3.4 | AI/ML |   | ||||||||||
6.3.5 | Energy efficiency |   | ||||||||||
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 |   | ||||||||||
6.3.12 | PM/KPI |   | ||||||||||
6.3.13 | Trace/MDT |   | ||||||||||
6.3.14 | Other |   | ||||||||||
6.4 | Intelligence and Automation |   | ||||||||||
6.4.1 | Self-Configuration of RAN NEs |   | ||||||||||
6.4.1.1 | RANSC_WoP#1 |   | ||||||||||
6.4.1.2 | RANSC_WoP#2 |   | ||||||||||
6.4.1.3 | RANSC_WoP#3 |   | ||||||||||
6.4.1.4 | Draft TS 28.317 |   | ||||||||||
6.4.2 | Management Data Analytics phase 2 |   | ||||||||||
6.4.2.1 | eMDAS_Ph2_WoP#1 |   | ||||||||||
6.4.2.2 | eMDAS_Ph2_WoP#2 |   | ||||||||||
6.4.2.3 | eMDAS_Ph2_WoP#3 |   | ||||||||||
6.4.2.4 | eMDAS_Ph2_WoP#4 |   | ||||||||||
6.4.2.5 | eMDAS_Ph2_WoP#5 |   | ||||||||||
6.4.2.6 | eMDAS_Ph2_WoP#6 |   | ||||||||||
6.4.2.7 | eMDAS_Ph2_WoP#7 |   | ||||||||||
6.5 | Management Architecture and Mechanisms |   | ||||||||||
6.5.1 | Network slicing provisioning rules |   | ||||||||||
6.5.1.1 | NSRULE_WoP#1 |   | ||||||||||
6.5.1.2 | NSRULE_WoP#2 |   | ||||||||||
6.5.2 | Additional NRM features phase 2 |   | ||||||||||
6.5.2.1 | AdNRM_ph2_WoP#1 |   | ||||||||||
6.5.2.2 | AdNRM_ph2_WoP#2 |   | ||||||||||
6.5.2.3 | AdNRM_ph2_WoP#3 |   | ||||||||||
6.5.2.4 | AdNRM_ph2_WoP#4 |   | ||||||||||
6.5.3 | Enhanced Edge Computing Management |   | ||||||||||
6.5.3.1 | eECM_WoP#1 |   | ||||||||||
6.5.3.2 | eECM_WoP#2 |   | ||||||||||
6.5.3.3 | eECM_WoP#3 |   | ||||||||||
6.5.4 | Enhancement of QoE Measurement Collection |   | ||||||||||
6.5.4.1 | eQoE_WoP#1 |   | ||||||||||
6.5.4.2 | eQoE_WoP#2 |   | ||||||||||
6.5.5 | Access control for management service |   | ||||||||||
6.5.5.1 | MSAC_WoP#1 |   | ||||||||||
6.5.5.2 | MSAC_WoP#2 |   | ||||||||||
6.5.5.3 | MSAC_WoP#3 |   | ||||||||||
6.5.5.4 | MSAC_WoP#4 |   | ||||||||||
6.5.6 | 5G performance measurements and KPIs phase 3 |   | ||||||||||
6.5.6.1 | PM_KPI_5G_Ph3_WoP#1 |   | ||||||||||
6.5.6.2 | PM_KPI_5G_Ph3_WoP#2 |   | ||||||||||
6.5.6.3 | PM_KPI_5G_Ph3_WoP#3 |   | ||||||||||
6.5.7 | Methodology for deprecation |   | ||||||||||
6.5.7.1 | OAM_MetDep_ WoP#1 |   | ||||||||||
6.6 | Support of New Services |   | ||||||||||
6.6.1 | Enhancements of EE for 5G Phase 2 |   | ||||||||||
6.6.1.1 | EE5GPLUS_Ph2_WoP#1 |   | ||||||||||
6.6.1.2 | EE5GPLUS_Ph2_WoP#2 |   | ||||||||||
6.6.2 | Network slice provisioning enhancement |   | ||||||||||
6.6.2.1 | eNETSLICE_PRO_WoP#1 |   | ||||||||||
6.6.2.2 | eNETSLICE_PRO_WoP#2 |   | ||||||||||
6.7 | Intelligence and Automation |   | ||||||||||
6.7.1 | Study on enhancement of autonomous network levels |   | ||||||||||
6.7.1.1 | FS_eANL_WoP#1 | S5‑233409 | pCR TR 28.910 Add gap analysis and recommendation for key issue#5.1b RAN UE throughput optimization | China Mobile, Huawei, ZTE, AsiaInfo, China Unicom, CATT | pCR | Approval | Yes |
Yes
| noted | No | ||
S5‑233457 | pCR TR 28.910 Add key issue of attribution to individual MnS | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
6.7.1.2 | FS_eANL_WoP#2 |   | ||||||||||
6.7.1.3 | FS_eANL_WoP#3 | S5‑233346 | pCR TR 28.910 Add potential solution for 5GC NF deployment | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||
S5‑233410 | pCR TR 28.910 Add use cases and requirements for management of ANL | China Mobile, Huawei, Deutsche Telecom, AsiaInfo, CATT, China Unicom, ZTE | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑233459 | pCR TR 28.910 Add potential solution for management of ANL | Huawei, China Mobile,Deutsche Telekom | pCR | Approval | Yes |
Yes
| noted | No | ||||
6.7.1.4 | FS_eANL_WoP#4 | S5‑233458 | pCR TR 28.910 Add potential solutions for Key Issue #6-1: Autonomous network level for RAN energy saving use case | Huawei, Deutsche Telekom, China Mobile | pCR | Approval | Yes |
Yes
| noted | No | ||
6.7.1.5 | Draft TR 28.910 | S5‑233411 | pCR TR 28.910 Clean up some Editor's Notes and editorial issues | China Mobile | pCR | Approval | Yes |
Yes
| approved | No | ||
S5‑233663 | Draft TR 28.910 | China Mobile | draft TR | Approval | No |
Yes
| approved | No | ||||
6.7.2 | Study on evaluation of autonomous network levels |   | ||||||||||
6.7.2.1 | FS_ANLEVA_WoP#1 |   | ||||||||||
6.7.2.2 | FS_ANLEVA_WoP#2 |   | ||||||||||
6.7.2.3 | FS_ANLEVA_WoP#3 |   | ||||||||||
6.7.2.4 | FS_ANLEVA_WoP#4 |   | ||||||||||
6.7.2.5 | Draft TR 28.909 |   | ||||||||||
6.7.3 | Study on enhanced intent driven management services for mobile networks |   | ||||||||||
6.7.3.1 | FS_eIDMS_MN_WoP#1 |   | ||||||||||
6.7.3.2 | FS_eIDMS_MN_WoP#2 | S5‑233228 | pCR TR 28.912 enhance service support expectation | Nokia | pCR | Approval | Yes |
Yes
| not treated | No | ||
S5‑233229 | pCR TR 28.912 intents for slice-based cell configuration | Nokia | pCR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑233230 | pCR TR 28.912 Intent Fullfillment feedback | Nokia | pCR | Approval | No |
Yes
| revised | No | S5‑233231 | |||
S5‑233231 | pCR TR 28.912 Potential Solution on Intent-driven Closed Loop control | Nokia | pCR | Approval | Yes |
Yes
| revised | No | S5‑233558 | S5‑233230 | ||
S5‑233558 | pCR TR 28.912 Potential Solution on Intent-driven Closed Loop control | Nokia | pCR | Approval | Yes |
Yes
| approved | No | S5‑233231 | |||
S5‑233274 | pCR TR 28.912 Update the Issue#4.6 Intent-driven closed loop control | Huawei, Deutsche Telekom | pCR | Approval | Yes |
Yes
| revised | No | S5‑233559 | |||
S5‑233559 | pCR TR 28.912 Update the Issue#4.6 Intent-driven closed loop control | Huawei, Deutsche Telekom | pCR | Approval | Yes |
Yes
| approved | No | S5‑233274 | |||
S5‑233388 | pCR TR 28.912 Add intent fulfilment feasibility information into intent report | ZTE Corporation | pCR | Approval | Yes |
Yes
| revised | No | S5‑233560 | |||
S5‑233560 | pCR TR 28.912 Add intent fulfilment feasibility information into intent report | ZTE Corporation | pCR | Approval | Yes |
Yes
| approved | No | S5‑233388 | |||
S5‑233389 | pCR TR 28.912 Clarification on Issue 4.1 intent driven approach for RAN energy saving | ZTE Corporation | pCR | Approval | Yes |
Yes
| revised | No | S5‑233562 | |||
S5‑233562 | pCR TR 28.912 Clarification on Issue 4.1 intent driven approach for RAN energy saving | ZTE Corporation | pCR | Approval | Yes |
Yes
| approved | No | S5‑233389 | |||
S5‑233390 | pCR TR 28.912 Clarification on Issue 4.2 Intent conflicts | ZTE Corporation | pCR | Approval | Yes |
Yes
| revised | No | S5‑233563 | |||
S5‑233563 | pCR TR 28.912 Clarification on Issue 4.2 Intent conflicts | ZTE Corporation | pCR | Approval | Yes |
Yes
| approved | No | S5‑233390 | |||
S5‑233392 | pCR TR 28.912 Clarification on Issue 4.5 Intent report | ZTE Corporation | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑233394 | pCR TR 28.912 Clarification on Issue 4.7 Monitoring intent fulfilment information | ZTE Corporation | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑233473 | Intent fulfillment feasibility check and corresponding solutions | China Mobile Com. Corporation | pCR | Yes |
Yes
| revised | No | S5‑233561 | ||||
S5‑233561 | Intent fulfillment feasibility check and corresponding solutions | China Mobile Com. Corporation | pCR | - | Yes |
Yes
| approved | No | S5‑233473 | |||
S5‑233474 | Clarifying the use of ObjectContext and defining another value Property for configuration expectations | China Mobile Com. Corporation | pCR | Yes |
Yes
| revised | No | S5‑233565 | ||||
S5‑233565 | Clarifying the use of ObjectContext and defining another value Property for configuration expectations | China Mobile Com. Corporation | pCR | - | Yes |
Yes
| approved | No | S5‑233474 | |||
S5‑233475 | issue#4.11 Generic information model definition enhancement | China Mobile Com. Corporation | pCR | Yes |
Yes
| noted | No | |||||
S5‑233476 | issue#4.5.1 Intent report description enhancement | China Mobile Com. Corporation | pCR | Yes |
Yes
| revised | No | S5‑233564 | ||||
S5‑233564 | issue#4.5.1 Intent report description enhancement | China Mobile Com. Corporation | pCR | - | Yes |
Yes
| approved | No | S5‑233476 | |||
S5‑233477 | issue#4.5.1 Intent report potential solution#1 enhancement | China Mobile Com. Corporation | pCR | Yes |
Yes
| revised | No | S5‑233585 | ||||
S5‑233585 | issue#4.5.1 Intent report potential solution#1 enhancement | China Mobile Com. Corporation | pCR | - | Yes |
Yes
| approved | No | S5‑233477 | |||
S5‑233513 | pCR TR 28.912 Add solutions for monitoring intent fulfilment | China Mobile E-Commerce Co. | pCR | Approval | Yes |
Yes
| noted | No | ||||
6.7.3.3 | FS_eIDMS_MN_WoP#3 | S5‑233275 | pCR TR 28.912 Correct the wrong target and context definition in Issue#5.2 | Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||
6.7.3.4 | FS_eIDMS_MN_WoP#4 |   | ||||||||||
6.7.3.5 | FS_eIDMS_MN_WoP#5 | S5‑233272 | pCR TR 28.912 Rapporteur on clause 4 | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑233567 | |
S5‑233567 | pCR TR 28.912 Rapporteur on clause 4 | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑233272 | |||
S5‑233273 | pCR TR 28.912 Rapporteur clean up on clause 6 | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑233568 | |||
S5‑233568 | pCR TR 28.912 Rapporteur clean up on clause 6 | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑233273 | |||
S5‑233276 | LS on progress of 3GPP SA5 R18 work on intent driven management | Huawei | LS out | Approval | Yes |
Yes
| approved | No | ||||
S5‑233277 | LS on 3GPP SA5 work on intent interface collaboration | Huawei | LS out | Approval | Yes |
Yes
| approved | No | ||||
S5‑233345 | Presentation sheet of TR 28.912 for SA Approval | Huawei | TS or TR cover | Approval | Yes |
Yes
| approved | No | S5‑232444 | |||
S5‑233481 | pCR TR 28.912 Add conclusion and recommendation for enhancement for service support expectation | China Mobile E-Commerce Co. | pCR | Approval | Yes |
Yes
| revised | No | S5‑233566 | |||
S5‑233566 | pCR TR 28.912 Add conclusion and recommendation for enhancement for service support expectation | China Mobile E-Commerce Co.,Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑233481 | |||
6.7.3.6 | Draft TR 28.912 | S5‑233652 | Draft TR 28.912 | Huawei | draft TR | discussion | Yes |
Yes
| approved | No | ||
6.7.4 | Study on intent-driven management for network slicing |   | ||||||||||
6.7.4.1 | FS_NETSLICE_IDMS_WoP#1 | S5‑233280 | pCR TR28.836 Add solution for modelling ServiceProfile attributes as intent expectation for network slice service delivering and assurance | Huawei, Deutsche Telekom,China Mobile | pCR | Approval | Yes |
Yes
| noted | No | ||
S5‑233323 | Discussion paper on applicability of service profile parameters for intent | L.M. Ericsson Limited, Deutsche Telekom | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑233570 | |||
S5‑233570 | Discussion paper on applicability of service profile parameters for intent | L.M. Ericsson Limited, Deutsche Telekom | discussion | Endorsement | Yes |
Yes
| endorsed | No | S5‑233323 | |||
S5‑233324 | Discussion paper on ServAttrCom and Intent | L.M. Ericsson Limited, Deutsche Telekom | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑233571 | |||
S5‑233571 | Discussion paper on ServAttrCom and Intent | L.M. Ericsson Limited, Deutsche Telekom | discussion | Endorsement | Yes |
Yes
| endorsed | No | S5‑233324 | |||
S5‑233325 | pCR 28.836 Restructure solutions to allow multiple alternatives | L.M. Ericsson Limited, Deutsche Telekom | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑233326 | pCR 28.836 Add network slice expectation definition alternative | L.M. Ericsson Limited, Deutsche Telekom | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑233456 | pCR TR 28.836 Add description of network slice subnet instance in clause 4.2 | ZTE Corporation | pCR | Approval | Yes |
Yes
| revised | No | S5‑233572 | |||
S5‑233572 | pCR TR 28.836 Add description of network slice subnet instance in clause 4.2 | ZTE Corporation | pCR | Approval | Yes |
Yes
| approved | No | S5‑233456 | |||
S5‑233472 | pCR TR 28.836 Add Use case of Intent driven management to support the operation of network slice instance | ZTE Corporation | pCR | Approval | Yes |
Yes
| noted | No | ||||
6.7.4.2 | FS_NETSLICE_IDMS_WoP#2 | S5‑233327 | pCR 28.836 Use case for network slice intent | L.M. Ericsson Limited, Deutsche Telekom | pCR | Approval | Yes |
Yes
| noted | No | ||
6.7.4.3 | FS_NETSLICE_IDMS_WoP#3 | S5‑233278 | pCR TR 28.836 Add procedures for network slice (subnet) delivering and assurance | Huawei, Deutsche Telekom,China Mobile | pCR | Approval | Yes |
Yes
| revised | No | S5‑233586 | |
S5‑233586 | pCR TR 28.836 Add procedures for network slice (subnet) delivering and assurance | Huawei, Deutsche Telekom,China Mobile | pCR | Approval | Yes |
Yes
| approved | No | S5‑233278 | |||
S5‑233279 | pCR TR28.836 Add solution for intent expectation for RAN network slice subnet service delivering and assurance | Huawei, Deutsche Telekom,China Mobile | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑233347 | pCR 28.836 Add potential solution for IDM to express expectation of network slice service assurance | Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||||
6.7.4.4 | FS_NETSLICE_IDMS_WoP#4 | S5‑233529 | Add background information on the 5G features QoS and slicing | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑233573 | |
S5‑233573 | Add background information on the 5G features QoS and slicing | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑233529 | |||
S5‑233538 | Add use case of intent-based management of communication services | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
6.7.4.5 | FS_NETSLICE_IDMS_WoP#5 |   | ||||||||||
6.7.4.6 | Draft TR 28.836 | S5‑233710 | draft TR 28.836 | Ericsson | draft TR | Approval | Yes |
Yes
| approved | No | ||
6.7.5 | Study on AI/ ML management |   | ||||||||||
6.7.5.1 | FS_AIML_MGMT_WoP#1 | S5‑233321 | pCR TR 28.908 Correction of terminology | Ericsson India Private Limited | pCR | Agreement | Yes |
Yes
| noted | No | ||
S5‑233381 | pCR28.908 Rapporteur clean-up & clarifications | NEC, Intel | pCR | Approval | Yes |
Yes
| revised | No | S5‑233574 | |||
S5‑233574 | pCR28.908 Rapporteur clean-up & clarifications | NEC, Intel | pCR | Approval | Yes |
Yes
| approved | No | S5‑233381 | |||
6.7.5.2 | FS_AIML_MGMT_WoP#2 | S5‑233224 | pCR TR28.908 Description for AIML update control | Nokia | pCR | Approval | Yes |
Yes
| revised | No | S5‑233575 | |
S5‑233575 | pCR TR28.908 Description for AIML update control | Nokia | pCR | Approval | Yes |
Yes
| approved | No | S5‑233224 | |||
S5‑233271 | pCR 28.908 Replacing mandatory language from requirements | Ericsson Telecomunicazioni SpA | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑233282 | pCR 28.908 enhance ML retraining | Nokia | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑233338 | pCR 28.908 Add description for ML entity re-training | Intel, NEC | pCR | Approval | Yes |
Yes
| revised | No | S5‑233576 | |||
S5‑233576 | pCR 28.908 Add description for ML entity re-training | Intel, NEC | pCR | Approval | Yes |
Yes
| approved | No | S5‑233338 | |||
S5‑233339 | pCR 28.908 Add description for ML entity update | Intel, NEC | pCR | Approval | Yes |
Yes
| merged | No | S5‑233575 | |||
S5‑233340 | pCR 28.908 Add description for ML entity joint training | Intel, NEC | pCR | Approval | Yes |
Yes
| revised | No | S5‑233577 | |||
S5‑233577 | pCR 28.908 Add description for ML entity joint training | Intel, NEC | pCR | Approval | Yes |
Yes
| approved | No | S5‑233340 | |||
S5‑233382 | pCR28.908 clarifications to ML entity re-training use case | NEC, Intel | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑233384 | pCR28.908 clarifications to Training data effectiveness reporting and analytics use case | NEC, Intel | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑233399 | pCR TR 28.908 Add use case and solution for AI/ML management of RAN domain centrialized ES | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑233400 | pCR TR 28.908 Update the solution of AI/ML update control | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑233587 | |||
S5‑233587 | pCR TR 28.908 Update the solution of AI/ML update control | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑233400 | |||
S5‑233491 | pCR TR 28.909 Add description for ML entity joint training | China Mobile E-Commerce Co. | pCR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑233492 | pCR TR 28.909 Add description for ML entity re-training | China Mobile E-Commerce Co. | pCR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑233515 | pCR 28.908 Add use case and requirement on Model evaluation for ML testing | CATT | pCR | Approval | Yes |
Yes
| revised | No | S5‑233578 | |||
S5‑233578 | pCR 28.908 Add use case and requirement on Model evaluation for ML testing | CATT | pCR | Approval | Yes |
Yes
| approved | No | S5‑233515 | |||
S5‑233525 | pCR TR 28.908 Add description for ML entity joint training | China Mobile E-Commerce Co. | pCR | Approval | Yes |
Yes
| merged | No | S5‑233577 | |||
S5‑233526 | pCR TR 28.908 Add description for ML entity re-training | China Mobile E-Commerce Co. | pCR | Approval | Yes |
Yes
| merged | No | S5‑233576 | |||
S5‑233539 | pCR28.908 split of Trustworthy Machine Learning use cases into two parts for training/testing and inference phase | NEC, Intel | pCR | Approval | Yes |
Yes
| noted | No | ||||
6.7.5.3 | FS_AIML_MGMT_WoP#3 | S5‑233225 | pCR TR28.908 solution for AIML inference emulation | Nokia | pCR | Approval | Yes |
Yes
| revised | No | S5‑233590 | |
S5‑233590 | pCR TR28.908 solution for AIML inference emulation | Nokia | pCR | Approval | Yes |
Yes
| approved | No | S5‑233225 | |||
S5‑233226 | pCR TR28.908 solution for configuration of AIML inference | Nokia | pCR | Approval | Yes |
Yes
| revised | No | S5‑233580 | |||
S5‑233580 | pCR TR28.908 solution for configuration of AIML inference | Nokia | pCR | Approval | Yes |
Yes
| approved | No | S5‑233226 | |||
S5‑233227 | pCR TR28.908 Extend Coordination of AI/ML capabilities | Nokia | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑233269 | Rel 18 pCR TR 28.908 Enhancement to solutions on AIML trustworthiness | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑233588 | |||
S5‑233588 | Rel 18 pCR TR 28.908 Enhancement to solutions on AIML trustworthiness | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑233269 | |||
S5‑233270 | Rel 18 pCR TR 28.908 Evaluation for AI/ML trustworthiness | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑233589 | |||
S5‑233589 | Rel 18 pCR TR 28.908 Evaluation for AI/ML trustworthiness | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑233270 | |||
S5‑233341 | pCR 28.908 Add evaluation for trustworth Machine Learning | Intel, NEC | pCR | Approval | Yes |
Yes
| merged | No | S5‑233589 | |||
S5‑233342 | pCR 28.908 Add solution for management of ML entity emulation | Intel, NEC | pCR | Approval | Yes |
Yes
| merged | No | S5‑233590 | |||
S5‑233343 | pCR 28.908 Clarification on solution for AI-ML inference function configuration | Intel, NEC | pCR | Approval | Yes |
Yes
| merged | No | S5‑233580 | |||
S5‑233516 | pCR 28.908 Add potential solution on Model evaluation for ML testing | CATT | pCR | Approval | Yes |
Yes
| revised | No | S5‑233579 | |||
S5‑233579 | pCR 28.908 Add potential solution on Model evaluation for ML testing | CATT | pCR | Approval | Yes |
Yes
| approved | No | S5‑233516 | |||
6.7.5.4 | FS_AIML_MGMT_WoP#4 |   | ||||||||||
6.7.5.5 | FS_AIML_MGMT_WoP#5 |   | ||||||||||
6.7.5.6 | FS_AIML_MGMT_WoP#6 | S5‑233383 | pCR28.908 Further clarifications and corrections to deployment scenarios | NEC, Intel | pCR | Approval | Yes |
Yes
| approved | No | ||
6.7.5.7 | FS_AIML_MGMT_WoP#7 | S5‑233344 | Presentation of TR 28.908 for approval | Intel, NEC | pCR | Approval | Yes |
Yes
| approved | No | ||
6.7.5.8 | Draft TR 28.908 | S5‑233665 | Draft TR 28.908 | Intel | draft TR | Approval | Yes |
Yes
| approved | No | ||
6.7.6 | Study on Enhancement of the management aspects related to NWDAF |   | ||||||||||
6.7.6.1 | FS_MANWDAF_WoP#1 |   | ||||||||||
6.7.6.2 | FS_MANWDAF_WoP#2 | S5‑233464 | pCR 28.864 Update Evaluation and Conclusion for KI#3 | China Telecommunication | pCR | Approval | Yes |
Yes
| revised | No | S5‑233581 | |
S5‑233581 | pCR 28.864 Update Evaluation and Conclusion for KI#3 | China Telecommunication | pCR | Approval | Yes |
Yes
| approved | No | S5‑233464 | |||
S5‑233465 | Discussion paper on summarization of TR 28.864 and work plan for MANWDAF | China Telecommunication | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑233582 | |||
S5‑233582 | Discussion paper on summarization of TR 28.864 and work plan for MANWDAF | China Telecommunication | discussion | Endorsement | Yes |
Yes
| approved | No | S5‑233465 | |||
6.7.6.3 | Draft TR 28.864 | S5‑233679 | Draft TR 28.864 | China Telecom | draft TR | Approval | Yes |
Yes
| approved | No | ||
6.7.7 | Study on Fault Supervision Evolution |   | ||||||||||
6.7.7.1 | FS_FSEV_WoP#1 | S5‑233480 | Stateless Alert in Fault Supervision | Ericsson Hungary Ltd | discussion | Endorsement | Yes |
Yes
| noted | No | S5‑231106 | |
S5‑233537 | DP on FM restructuring TS 28-545 | Ericsson Hungary Ltd | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑233583 | S5‑232771 | ||
S5‑233583 | DP on FM restructuring TS 28-545 | Ericsson Hungary Ltd | discussion | Endorsement | Yes |
Yes
| approved | No | S5‑233537 | |||
6.7.7.2 | FS_FSEV_WoP#2 | S5‑233495 | pCR TR 28.830 Add description failure prediction enhancement | Huawei, China Mobile | pCR | Approval | Yes |
Yes
| noted | No | ||
S5‑233496 | pCR TR 28.830 Add description performance degradation analysis | Huawei, China Mobile | pCR | Approval | Yes |
Yes
| noted | No | ||||
6.7.7.3 | FS_FSEV_WoP#3 |   | ||||||||||
6.7.7.4 | Draft TR 28.830 |   | ||||||||||
6.8 | Management Architecture and Mechanisms |   | ||||||||||
6.8.1 | Study on Enhancement of service based management architecture |   | ||||||||||
6.8.1.1 | FS_eSBMA_WoP#1 | S5‑233467 | pCR TR 28.925 Add conclusion and recommendation for issue#9 Improvement on the management function description | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||
S5‑233468 | pCR TR 28.925 Update solution and add conclusion and recommendation for issue#12 illustration of using MnS in management reference model in TS 32.101 | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
6.8.1.2 | FS_eSBMA_WoP#2 |   | ||||||||||
6.8.1.3 | FS_eSBMA_WoP#3 | S5‑233329 | pCR 28.925 Issues in 28.621 | Ericsson | pCR | Yes |
Yes
| noted | No | |||
S5‑233330 | pCR 28.925 Proposal in 28.621 | Ericsson | pCR | Yes |
Yes
| noted | No | |||||
S5‑233331 | pCR 28.925 Issues in 28.622 | Ericsson | pCR | Yes |
Yes
| noted | No | |||||
S5‑233332 | pCR 28.925 Proposal in 28.622 | Ericsson | pCR | Yes |
Yes
| noted | No | |||||
S5‑233333 | pCR 28.925 Issues in 28.623 | Ericsson | pCR | Yes |
Yes
| noted | No | |||||
S5‑233334 | pCR 28.925 Proposal in 28.623 | Ericsson GmbH, Eurolab | pCR | Yes |
Yes
| noted | No | |||||
6.8.1.4 | FS_eSBMA_WoP#4 |   | ||||||||||
6.8.1.5 | FS_eSBMA_WoP#5 | S5‑233348 | pCR 28.925 Add an example for management function deployment scenario | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||
S5‑233461 | pCR TR 28.925 Add overview for management service features supported by CRUD operations in SBMA | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑233479 | pCR TR 28.925 update the example for management function deployment scenarios | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
6.8.1.6 | FS_eSBMA_WoP#6 | S5‑233466 | pCR TR 28.925 Add conclusion and recommendation for issue#6 software management feature in SBMA for 5G | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||
6.8.1.7 | Draft TR 28.925 |   | ||||||||||
6.8.2 | Study on Basic SBMA enabler enhancements |   | ||||||||||
6.8.2.1 | FS_eSBMAe_WoP#1 | S5‑233398 | pCR 28.831 Alarm Subscription and Notification Key Issue | Samsung Electronics France SA | pCR | Agreement | Yes |
Yes
| noted | No | ||
6.8.2.2 | FS_eSBMAe_WoP#2 | S5‑233284 | Rel-18 CR 28.831 Add conclusion for issue 3 Definition of createMOI | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||
6.8.2.3 | FS_eSBMAe_WoP#3 | S5‑233264 | Rel-18 pCR TR 28.831 Add a new key issue for Advertising NRM properties by MnS producer | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑233593 | |
S5‑233593 | Rel-18 pCR TR 28.831 Add a new key issue for Advertising NRM properties by MnS producer | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑233264 | |||
S5‑233265 | Rel-18 pCR TR 28.831 Add potential requirements for KI for Advertising NRM properties by MnS producer | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑233594 | |||
S5‑233594 | Rel-18 pCR TR 28.831 Add potential requirements for KI for Advertising NRM properties by MnS producer | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑233265 | |||
S5‑233266 | Rel-18 pCR TR 28.831 Add a potential solution for KI for Advertising NRM properties by MnS producer | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑233267 | Rel-18 pCR TR 28.831 Add a potential solution for the URI location for KI Advertising NRM properties by MnS producer | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑233268 | Rel-18 pCR TR 28.831 Add a new key issue for Advertising notifications supported by MnS producer | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑233285 | Rel-18 CR 28.831 Add definition of HTTP error codes (error response format) | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑233286 | Rel-18 CR 28.831 Improve description of error response body format (error response format) | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑233595 | |||
S5‑233595 | Rel-18 CR 28.831 Improve description of error response body format (error response format) | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑233286 | |||
S5‑233287 | Rel-18 CR 28.831 Clarify definition of the type property (error response format) | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑233596 | |||
S5‑233596 | Rel-18 CR 28.831 Clarify definition of the type property (error response format) | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑233287 | |||
S5‑233288 | Rel-18 CR 28.831 Clarify and restructure definition of the reason property for GET (error response format) | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑233597 | |||
S5‑233597 | Rel-18 CR 28.831 Clarify and restructure definition of the reason property for GET (error response format) | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑233288 | |||
S5‑233289 | mRel-18 CR 28.831 Clarify and restructure definition of the reason property for manipulating attributes (error response format) | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑233598 | |||
S5‑233598 | mRel-18 CR 28.831 Clarify and restructure definition of the reason property for manipulating attributes (error response format) | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑233289 | |||
S5‑233290 | Rel-18 CR 28.831 Clarify and restructure definition of the reason property for manipulating objects (error response format) | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑233599 | |||
S5‑233599 | Rel-18 CR 28.831 Clarify and restructure definition of the reason property for manipulating objects (error response format) | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑233290 | |||
S5‑233291 | Rel-18 CR 28.831 Add clause on Error reasons for application layer errors (error response format) | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑233600 | |||
S5‑233600 | Rel-18 CR 28.831 Add clause on Error reasons for application layer errors (error response format) | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑233291 | |||
S5‑233292 | Rel-18 CR 28.831 Add key issue on node selection | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑233601 | |||
S5‑233601 | Rel-18 CR 28.831 Add key issue on node selection | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑233292 | |||
6.8.2.4 | FS_eSBMAe_WoP#4 | S5‑233294 | Rel-18 CR 28.831 Add CR proposal for issue 2 Targeted notification subscriptions | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑233602 | |
S5‑233602 | Rel-18 CR 28.831 Add CR proposal for issue 2 Targeted notification subscriptions | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑233294 | |||
6.8.2.5 | FS_eSBMAe_WoP#5 | S5‑233293 | Rel-18 CR 28.831 Add key issue and solution on MnS versioning | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑233603 | |
S5‑233603 | Rel-18 CR 28.831 Add key issue and solution on MnS versioning | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑233293 | |||
6.8.2.6 | FS_eSBMAe_WoP#6 |   | ||||||||||
6.8.2.7 | FS_eSBMAe_WoP#7 | S5‑233393 | pCR 28.831 Logging Solution | Samsung Electronics France SA | pCR | Agreement | Yes |
Yes
| noted | No | ||
6.8.2.8 | FS_eSBMAe_WoP#8 |   | ||||||||||
6.8.2.9 | FS_eSBMAe_WoP#9 |   | ||||||||||
6.8.2.10 | FS_eSBMAe_WoP#10 |   | ||||||||||
6.8.2.11 | Draft TR 28.831 | S5‑233686 | Draft TR 28.831 | Nokia | draft TR | discussion | No |
Yes
| approved | No | ||
6.8.3 | Study on Management Aspects of URLLC |   | ||||||||||
6.8.3.1 | FS_URLLC_Mgt_WoP#1 | S5‑233349 | pCR 28.832 Correction of terminologies and missing references | Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||
6.8.3.2 | FS_URLLC_Mgt_WoP#2 | S5‑233501 | Add New Solution for configuration of latency for URLLC in RAN | China Unicom | pCR | Approval | Yes |
Yes
| revised | No | S5‑233604 | |
S5‑233604 | Add New Solution for configuration of latency for URLLC in RAN | China Unicom | pCR | Approval | Yes |
Yes
| approved | No | S5‑233501 | |||
S5‑233502 | Add Conclusion and recommendation for issue#4 | China Unicom | pCR | Approval | Yes |
Yes
| revised | No | S5‑233605 | |||
S5‑233605 | Add Conclusion and recommendation for issue#4 | China Unicom | pCR | Approval | Yes |
Yes
| approved | No | S5‑233502 | |||
6.8.3.3 | FS_URLLC_Mgt_WoP#3 | S5‑233499 | Add New Solution for URLLC performance management related to reliability | China Unicom | pCR | Approval | Yes |
Yes
| revised | No | S5‑233636 | |
S5‑233636 | Add New Solution for URLLC performance management related to reliability | China Unicom | pCR | Approval | Yes |
Yes
| approved | No | S5‑233499 | |||
S5‑233500 | Add New Solution for support for performance measurements related on URLLC resource load | China Unicom | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑233511 | Discussion on URLLC performance measurements related to resource load of URLLC services | China Unicom | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑233512 | Discussion on URLLC performance management related to reliability | China Unicom | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑233606 | |||
S5‑233606 | Discussion on URLLC performance management related to reliability | China Unicom | discussion | Endorsement | Yes |
Yes
| endorsed | No | S5‑233512 | |||
6.8.3.4 | FS_URLLC_Mgt_WoP#4 |   | ||||||||||
6.8.3.5 | Draft TR 28.832 | S5‑233700 | Draft TR 28.832 | China Unicom | draft TR | Approval | Yes |
Yes
| approved | No | ||
6.8.4 | Study on Management of Cloud Native Virtualized Network Functions |   | ||||||||||
6.8.4.1 | FS_MCVNF_WoP#1 |   | ||||||||||
6.8.4.2 | FS_MCVNF_WoP#2 |   | ||||||||||
6.8.4.3 | FS_MCVNF_WoP#3 | S5‑233350 | pCR 28.834 Editorial cleanup | Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||
S5‑233351 | pCR 28.834 Fix references | Huawei | pCR | Approval | Yes |
Yes
| merged | No | S5‑233607 | |||
S5‑233352 | pCR 28.834 Requirement cleanup | Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑233353 | pCR 28.834 Update recommendation for VNF package management | Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑233490 | pCR 28.834 Adding editorial changes | China Mobile Com. Corporation | pCR | Approval | Yes |
Yes
| revised | No | S5‑233607 | |||
S5‑233607 | pCR 28.834 Adding editorial changes | China Mobile Com. Corporation,Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑233490 | |||
6.8.4.5 | Draft TR 28.834 | S5‑233489 | Presentation sheet of TR 28.834 for SA Approval | China Mobile Com. Corporation | TS or TR cover | Approval | Yes |
Yes
| revised | No | S5‑233608 | |
S5‑233608 | Presentation sheet of TR 28.834 for SA Approval | China Mobile Com. Corporation | TS or TR cover | Approval | Yes |
Yes
| approved | No | S5‑233489 | |||
S5‑233685 | Draft TR 28.834 | China Mobile | draft TR | Approval | Yes |
Yes
| approved | No | ||||
6.8.5 | Study on Management Aspects of 5G MOCN Network Sharing Phase2 |   | ||||||||||
6.8.5.1 | FS_MANS_ph2_WoP#1 | S5‑233504 | Modify service-based management architecture for MOCN and add conclusion for issue #4 | China Unicom | pCR | Approval | Yes |
Yes
| noted | No | ||
S5‑233505 | Modify potential solution and add conclusion for issue #5 | China Unicom | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑233507 | Modify description, solution and add conclusion on issue #1 | China Unicom | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑233508 | Modify description, solution and add conclusion on issue #3 | China Unicom | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑233509 | Add conclusion and recommendation for issue #2 | China Unicom | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑233514 | Discussion on way forward of Management Aspects of 5G Network Sharing Phase2 | China Unicom | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
6.8.5.2 | FS_MANS_ph2_WoP#2 |   | ||||||||||
6.8.5.3 | FS_MANS_ph2_WoP#3 |   | ||||||||||
6.8.5.4 | Draft TR 28.834 |   | ||||||||||
6.8.6 | Study on Management of Trace/MDT phase 2 |   | ||||||||||
6.8.6.1 | FS_5GMDT_Ph2_WoP#1 |   | ||||||||||
6.8.6.2 | FS_5GMDT_Ph2_WoP#2 |   | ||||||||||
6.8.6.3 | FS_5GMDT_Ph2_WoP#3 |   | ||||||||||
6.8.6.4 | FS_5GMDT_Ph2_WoP#4 |   | ||||||||||
6.8.6.5 | FS_5GMDT_Ph2_WoP#5 |   | ||||||||||
6.8.6.6 | FS_5GMDT_Ph2_WoP#6 | S5‑233335 | Rel-18 pCR 28.837 Problem Statement and solution on Management of MDT of MRO for inter-system handover for voice fallback | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑233609 | |
S5‑233609 | Rel-18 pCR 28.837 Problem Statement and solution on Management of MDT of MRO for inter-system handover for voice fallback | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑233335 | |||
6.8.6.7 | FS_5GMDT_Ph2_WoP#7 |   | ||||||||||
6.8.6.8 | FS_5GMDT_Ph2_WoP#8 | S5‑233336 | Rel-18 pCR 28.837 Update on conclusions and recommendations | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||
6.8.6.9 | Draft TR 28.837 | S5‑233687 | Draft TR 28.837 | Nokia | draft TR | Approval | Yes |
Yes
| approved | No | ||
6.8.7 | Study on Management Aspects of IoT NTN Enhancements |   | ||||||||||
6.8.7.1 | FS_IOT_NTN_WoP#1 | S5‑233401 | pCR 28.841 add use case for monitoring of satellite components | China Unicom | pCR | Approval | Yes |
Yes
| noted | No | ||
S5‑233402 | pCR 28.841 add potential requirements and solutions for monitoring of satellite components | China Unicom | pCR | Approval | Yes |
Yes
| noted | No | ||||
6.8.7.2 | FS_IOT_NTN_WoP#2 |   | ||||||||||
6.8.7.3 | FS_IOT_NTN_WoP#3 | S5‑233403 | pCR 28.841 update conclusion and recommendations | China Unicom | pCR | Approval | Yes |
Yes
| noted | No | ||
S5‑233404 | pCR 28.841 Rapporteur clean up | China Unicom | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑233517 | pCR 28.841 Editorial clean-up | CATT | pCR | Approval | Yes |
Yes
| revised | No | S5‑233610 | |||
S5‑233610 | pCR 28.841 Editorial clean-up | CATT,Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑233517 | |||
6.8.7.4 | Draft TR 28.841 | S5‑233362 | pCR 28.841 Correction of reference number | Huawei | pCR | Approval | Yes |
Yes
| merged | No | S5‑233610 | |
S5‑233405 | Presentation sheet of TR 28.841 for Approval | China Unicom | TS or TR cover | Approval | Yes |
Yes
| noted | No | ||||
S5‑233676 | Draft TR 28.841 | China Unicom | draft TR | Approval | Yes |
Yes
| approved | No | ||||
6.8.8 | Study on Data management phase 2 |   | ||||||||||
6.8.8.1 | FS_MADCOL_ph2_WoP#1 | S5‑233528 | Add key issue on enhancing the description of management data | Nokia, Nokia Shanghai Bell, Microsift | pCR | Approval | Yes |
Yes
| revised | No | S5‑233611 | |
S5‑233611 | Add key issue on enhancing the description of management data | Nokia, Nokia Shanghai Bell, Microsift | pCR | Approval | Yes |
Yes
| approved | No | S5‑233528 | |||
S5‑233532 | pCR TR 28.842 Solution for discovery of stored management data | Microsoft Europe SARL | pCR | Approval | Yes |
Yes
| noted | No | ||||
6.8.8.2 | FS_MADCOL_ph2_WoP#2 | S5‑233337 | Rel-18 pCR 28.842 KI on discovery of data collection capabilities | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||
S5‑233518 | Rel-18 pCR TR 28.842 Add key issue for reporting of consolidated management data | Ericsson Inc. | pCR | Approval | Yes |
Yes
| revised | No | S5‑233612 | |||
S5‑233612 | Rel-18 pCR TR 28.842 Add key issue for reporting of consolidated management data | Ericsson Inc. | pCR | Approval | Yes |
Yes
| approved | No | S5‑233518 | |||
S5‑233531 | pCR 28.842 solution for retrieval of stored management data | Microsoft Europe SARL | pCR | Approval | Yes |
Yes
| noted | No | ||||
6.8.8.3 | FS_MADCOL_ph2_WoP#3 |   | ||||||||||
6.8.8.4 | FS_MADCOL_ph2_WoP#4 | S5‑233281 | pCR TR 28.842 add issue and potential solutions for external data management | Huawei, Deutsche Telekom | pCR | Approval | Yes |
Yes
| noted | No | ||
6.8.8.5 | Draft TR 28.842 | S5‑233535 | pCR TR 28.842 Correction -Adding missing reference | Microsoft Europe SARL | pCR | Approval | Yes |
Yes
| approved | No | ||
S5‑233688 | Draft TR 28.842 | Nokia | draft TR | Approval | Yes |
Yes
| approved | No | ||||
6.9 | Support of New Services |   | ||||||||||
6.9.1 | Study on new aspects of EE for 5G networks Phase 2 |   | ||||||||||
6.9.1.1 | FS_EE5G_Ph2_WoP#1 | S5‑233238 | pCR TR 28.913 KI#1 Consideration of four types of metrics to estimate VNF Energy Consumption | Huawei, Ericsson, AT&T, Deutsche Telekom | pCR | Approval | Yes |
Yes
| noted | No | ||
S5‑233239 | pCR 28.913 Conclusion for KI#2 Energy Consumption of containerized VNF/ VNFCs | Huawei, Deutsche Telekom | pCR | Approval | Yes |
Yes
| revised | No | S5‑233614 | |||
S5‑233614 | pCR 28.913 Conclusion for KI#2 Energy Consumption of containerized VNF/ VNFCs | Huawei, Deutsche Telekom | pCR | Approval | Yes |
Yes
| approved | No | S5‑233239 | |||
S5‑233240 | pCR 28.913 Conclusion for KI#3 Energy Consumption of RAN nodes | Huawei, Deutsche Telekom | pCR | Approval | Yes |
Yes
| revised | No | S5‑233615 | |||
S5‑233615 | pCR 28.913 Conclusion for KI#3 Energy Consumption of RAN nodes | Huawei, Deutsche Telekom | pCR | Approval | Yes |
Yes
| approved | No | S5‑233240 | |||
S5‑233241 | pCR 28.913 Conclusion for KI#4 EE KPI for V2X network slice | Huawei, Deutsche Telekom | pCR | Approval | Yes |
Yes
| revised | No | S5‑233616 | |||
S5‑233616 | pCR 28.913 Conclusion for KI#4 EE KPI for V2X network slice | Huawei, Deutsche Telekom | pCR | Approval | Yes |
Yes
| approved | No | S5‑233241 | |||
S5‑233247 | pCR 28.913 Conclusion for KI#6 EE KPI for URLLC network slice based on reliability | Huawei Technologies France | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑233248 | pCR 28.913 Conclusion for KI#7 Roles involved in EE KPI building | Huawei, Deutsche Telekom | pCR | Approval | Yes |
Yes
| revised | No | S5‑233617 | |||
S5‑233617 | pCR 28.913 Conclusion for KI#7 Roles involved in EE KPI building | Huawei, Deutsche Telekom | pCR | Approval | Yes |
Yes
| approved | No | S5‑233248 | |||
S5‑233498 | Add New Key issue and solution for Energy Efficiency of URLLC network slice- RAN based | China Unicom | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑233503 | Add potential solution for Energy Efficiency KPI of URLLC Network Slice based on both latency and reliability | China Unicom | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑233536 | Rel-18 pCR 28.913 Add Conclusion and Recommendation for Key Issue 6 | Samsung Electronics Nordic AB | pCR | Approval | Yes |
Yes
| noted | No | ||||
6.9.1.2 | FS_EE5G_Ph2_WoP#2 | S5‑233242 | pCR 28.913 Conclusion for KI#5 Customer acceptance for QoS degradation to save energy | Huawei, Deutsche Telekom | pCR | Approval | Yes |
Yes
| revised | No | S5‑233618 | |
S5‑233618 | pCR 28.913 Conclusion for KI#5 Customer acceptance for QoS degradation to save energy | Huawei, Deutsche Telekom | pCR | Approval | Yes |
Yes
| approved | No | S5‑233242 | |||
S5‑233249 | pCR 28.913 Conclusion for KI#9 RAN energy saving when using backup batteries | Huawei, Deutsche Telekom | pCR | Approval | Yes |
Yes
| revised | No | S5‑233619 | |||
S5‑233619 | pCR 28.913 Conclusion for KI#9 RAN energy saving when using backup batteries | Huawei, Deutsche Telekom | pCR | Approval | Yes |
Yes
| approved | No | S5‑233249 | |||
S5‑233250 | pCR 28.913 Solution and conclusion for KI#10 Digital sobriety | Huawei, Deutsche Telekom | pCR | Approval | Yes |
Yes
| revised | No | S5‑233620 | |||
S5‑233620 | pCR 28.913 Solution and conclusion for KI#10 Digital sobriety | Huawei, Deutsche Telekom | pCR | Approval | Yes |
Yes
| approved | No | S5‑233250 | |||
6.9.1.3 | Draft TR 28.913 | S5‑233651 | Draft TR 28.913 | Huawei | draft TR | Approval | Yes |
Yes
| approved | No | ||
6.9.2 | Study on Network and Service Operations for Energy Utilities |   | ||||||||||
6.9.2.1 | FS_NSOEU_WoP#1 | S5‑233366 | Discussion on Requirements in TR 28.829 | Nokia | discussion | Agreement | Yes |
Yes
| endorsed | No | ||
6.9.2.2 | FS_NSOEU_WoP#2 |   | ||||||||||
6.9.2.3 | FS_NSOEU_WoP#3 | S5‑233369 | Rel-18 pCR 28.829 – Update 6.4 | Nokia | pCR | Agreement | Yes |
Yes
| approved | No | ||
S5‑233370 | Rel-18 pCR 28.829 – Update 6.5 | Nokia | pCR | Agreement | Yes |
Yes
| approved | No | ||||
6.9.2.4 | FS_NSOEU_WoP#4 |   | ||||||||||
6.9.2.5 | FS_NSOEU_WoP#5 |   | ||||||||||
6.9.2.6 | FS_NSOEU_WoP#6 | S5‑233371 | Rel-18 pCR 28.829 – Update 6.6 | Nokia | pCR | Agreement | Yes |
Yes
| approved | No | ||
S5‑233372 | Rel-18 pCR 28.829 – Update 6.7 | Nokia | pCR | Agreement | Yes |
Yes
| approved | No | ||||
6.9.2.7 | FS_NSOEU_WoP#7 |   | ||||||||||
6.9.2.8 | FS_NSOEU_WoP#8 | S5‑233367 | Rel-18 pCR 28.829 – Update 6.8 | Nokia | pCR | Agreement | Yes |
Yes
| approved | No | ||
S5‑233368 | Rel-18 pCR 28.829 – Update 6.9 | Nokia | pCR | Agreement | Yes |
Yes
| approved | No | ||||
6.9.2.9 | FS_NSOEU_WoP#9 | S5‑233373 | Rel-18 pCR 28.829 – Update 6.8 | Nokia | pCR | Agreement | Yes |
Yes
| approved | No | ||
S5‑233374 | Rel-18 pCR 28.829 – Update 6.9 | Nokia | pCR | Agreement | Yes |
Yes
| approved | No | ||||
6.9.2.10 | FS_NSOEU_WoP#10 | S5‑233233 | Rel-18 pCR 28.829 – Potential Solution for Energy utility and telecommunication coordinated rapid recovery of energy service | Samsung, EUTC, EDF, Deutsche Telekom, BMWK, NOVAMINT | pCR | Approval | Yes |
Yes
| revised | No | S5‑233621 | |
S5‑233621 | Rel-18 pCR 28.829 – Potential Solution for Energy utility and telecommunication coordinated rapid recovery of energy service | Samsung, EUTC, EDF, Deutsche Telekom, BMWK, NOVAMINT | pCR | Approval | Yes |
Yes
| approved | No | S5‑233233 | |||
S5‑233375 | Rel-18 pCR 28.829 – authorization | Nokia | pCR | Agreement | Yes |
Yes
| revised | No | S5‑233622 | |||
S5‑233622 | Rel-18 pCR 28.829 – authorization | Nokia | pCR | Agreement | Yes |
Yes
| approved | No | S5‑233375 | |||
6.9.2.11 | FS_NSOEU_WoP#11 |   | ||||||||||
6.9.2.12 | FS_NSOEU_WoP#12 |   | ||||||||||
6.9.2.13 | FS_NSOEU_WoP#13 | S5‑233234 | Rel-18 pCR 28.829 – Clean up | Samsung, EUTC, EDF, Deutsche Telekom, BMWK, NOVAMINT | pCR | Approval | Yes |
Yes
| revised | No | S5‑233623 | |
S5‑233623 | Rel-18 pCR 28.829 – Clean up | Samsung, EUTC, EDF, Deutsche Telekom, BMWK, NOVAMINT | pCR | Approval | Yes |
Yes
| approved | No | S5‑233234 | |||
6.9.2.14 | Draft TR 28.829 | S5‑233235 | Presentation of Report to TSG: TR 28.829, Version 1.1.0 | Samsung (Rapporteur) | TS or TR cover | Approval | Yes |
Yes
| noted | No | ||
S5‑233705 | Draft TR 28.829 | Samsung | draft TR | Approval | Yes |
Yes
| approved | No | ||||
6.9.3 | Study on Key Quality Indicators (KQIs)for 5G service experience |   | ||||||||||
6.9.3.1 | FS_KQI_5G_WoP#1 | S5‑233469 | pCR TR 28.863 Issue1 definition of KQI | Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||
6.9.3.2 | FS_KQI_5G_WoP#2 |   | ||||||||||
6.9.3.3 | FS_KQI_5G_WoP#3 | S5‑233470 | pCR TR 28.863 Issue 3 Solution of KQIs for Video Uploading | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||
6.9.3.4 | FS_KQI_5G_WoP#4 | S5‑233471 | pCR TR 28.863 Issue4 definition of Remote controll | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||
6.9.3.5 | FS_KQI_5G_WoP#5 |   | ||||||||||
6.9.3.6 | Draft TR 28.863 | S5‑233664 | Draft TR 28.863 | Huawei | draft TR | Approval | Yes |
Yes
| approved | No | ||
6.9.4 | Study on Deterministic Communication Service Assurance |   | ||||||||||
6.9.4.1 | FS_DCSA_WoP#1 |   | ||||||||||
6.9.4.2 | FS_DCSA_WoP#2 | S5‑233493 | pCR TR 28.865 Report of reliability capability information | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||
S5‑233494 | pCR TR 28.865 Add description on reliability analysis | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
6.9.4.3 | FS_DCSA_WoP#3 |   | ||||||||||
6.9.4.4 | FS_DCSA_WoP#4 |   | ||||||||||
6.9.4.5 | FS_DCSA_WoP#5 |   | ||||||||||
6.9.4.6 | Draft TR 28.863 |   | ||||||||||
6.9.5 | Study on management aspects of network slice management capability exposure |   | ||||||||||
6.9.5.1 | FS_NSCE_WoP#1 | S5‑233386 | pCR TR 28.824 clean-up | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑233626 | |
S5‑233626 | pCR TR 28.824 clean-up | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑233386 | |||
S5‑233387 | pCR TR 28.824 Add conclusion and recommendation for network slice management capability exposure via CAPIF | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑233627 | |||
S5‑233627 | pCR TR 28.824 Add conclusion and recommendation for network slice management capability exposure via CAPIF | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑233387 | |||
6.9.5.2 | FS_NSCE_WoP#2 |   | ||||||||||
6.9.5.3 | FS_NSCE_WoP#3 |   | ||||||||||
6.9.5.4 | FS_NSCE_WoP#4 | S5‑233354 | pCR 28.824 Improve discovery solution | Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||
S5‑233355 | pCR 28.824 Improve description of exposure governance | Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑233478 | pCR TR 28.824 Add conclusion and recommendation for filtering | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑233628 | |||
S5‑233628 | pCR TR 28.824 Add conclusion and recommendation for filtering | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑233478 | |||
6.9.5.5 | Draft TR 28.824 | S5‑233356 | pCR 28.824 Correction of termiologies | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑233629 | |
S5‑233629 | pCR 28.824 Correction of termiologies | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑233356 | |||
S5‑233483 | pCR 28.824 Remove the EN about exposed management services | China Mobile E-Commerce Co. | pCR | Approval | Yes |
Yes
| revised | No | S5‑233630 | |||
S5‑233630 | pCR 28.824 Remove the EN about exposed management services | China Mobile E-Commerce Co. | pCR | Approval | Yes |
Yes
| approved | No | S5‑233483 | |||
S5‑233690 | Draft TR 28.824 | Alibaba | draft TR | Approval | Yes |
Yes
| approved | No | ||||
6.9.6 | Study on alignment with ETSI MEC for Edge computing management |   | ||||||||||
6.9.6.1 | FS_MEC_ECM_WoP#1 |   | ||||||||||
6.9.6.2 | FS_MEC_ECM_WoP#2 | S5‑233283 | pCR 28.903 Add KI and solution for dynamic EAS scaling | AsiaInfo,Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||
S5‑233357 | pCR 28.903 Add recommendation for resource reservation related issue | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑233631 | |||
S5‑233631 | pCR 28.903 Add recommendation for resource reservation related issue | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑233357 | |||
S5‑233358 | pCR 28.903 Add recommendation for SLA related issue | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑233632 | |||
S5‑233632 | pCR 28.903 Add recommendation for SLA related issue | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑233358 | |||
S5‑233359 | pCR 28.903 Add recommendation for management for alignement with ETSI MEC | Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑233360 | pCR 28.903 Add recommendation for application resource catalogue related issue | Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑233361 | pCR 28.903 Add solution for virtual resource related issue | Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑233395 | pCR 28.903 Federated EAS Management | Samsung Electronics France SA | pCR | Agreement | Yes |
Yes
| revised | No | S5‑233633 | |||
S5‑233633 | pCR 28.903 Federated EAS Management | Samsung Electronics France SA | pCR | Agreement | Yes |
Yes
| approved | No | S5‑233395 | |||
S5‑233396 | pCR 28.903 Federation Management | Samsung Electronics France SA | pCR | Agreement | Yes |
Yes
| revised | No | S5‑233634 | |||
S5‑233634 | pCR 28.903 Federation Management | Samsung Electronics France SA | pCR | Agreement | Yes |
Yes
| approved | No | S5‑233396 | |||
S5‑233397 | pCR 28.903 EAS Mobility | Samsung Electronics France SA | pCR | Agreement | Yes |
Yes
| revised | No | S5‑233635 | |||
S5‑233635 | pCR 28.903 EAS Mobility | Samsung Electronics France SA | pCR | Agreement | Yes |
Yes
| approved | No | S5‑233397 | |||
6.9.6.3 | Draft TR 28.903 | S5‑233667 | Draft TR 28.903 | Huawei | draft TR | Approval | Yes |
Yes
| approved | No | ||
7 | Charging |   | ||||||||||
7.1 | Charging Plenary | S5‑233184 | CH agenda and time plan | WG vice Chair (Matrixx Software) | agenda | Yes |
Yes
| revised | No | S5‑233643 | ||
S5‑233643 | CH agenda and time plan | WG vice Chair (Matrixx Software) | agenda | - | Yes |
Yes
| approved | No | S5‑233184 | |||
S5‑233185 | Collection of useful endorsed document and external communication documents | Huawei | discussion | Yes |
Yes
| noted | No | |||||
S5‑233186 | Charging exec report | WG vice Chair (Matrixx Software) | report | Yes |
Yes
| noted | No | |||||
S5‑233195 | Resubmitted LS out Rel17 Reply LS on Enhancement on Charging Identifier Uniqueness Mechanism | C4-225411 | LS in | Yes |
Yes
| postponed | No | |||||
S5‑233207 | LS on charging aspects for Ranging/Sidelink Positioning | S2-2303231 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑233655 | Reply to: LS on charging aspects for Ranging/Sidelink Positioning | current meeting | LS out | approval | Yes |
Yes
| approved | No | ||||
S5‑233542 | LS on Slice based (wholesale) differentiation and charging in roaming | GSMA | LS in | discussion | Yes |
Yes
| postponed | No | ||||
7.2 | New Charging Work Item proposals | S5‑233363 | Discussion paper on Charging Aspects of NG_RTC | China Mobile | discussion | Discussion | Yes |
Yes
| noted | No | ||
S5‑233364 | New WID on Charging Aspects of Next Generation Real time Communication services | China Mobile | WID new | Approval | Yes |
Yes
| revised | No | S5‑233661 | |||
S5‑233661 | New WID on Charging Aspects of IMS Data Channel | China Mobile | WID new | Approval | Yes |
Yes
| agreed | No | S5‑233364 | |||
S5‑233460 | New SID on Charging Aspects of Ranging and Sidelink Positioning | China Telecommunications | SID new | Approval | Yes |
Yes
| revised | No | S5‑233662 | |||
S5‑233662 | New SID on Charging Aspects of Ranging and Sidelink Positioning | China Telecommunications | SID new | Approval | Yes |
Yes
| agreed | No | S5‑233460 | |||
S5‑233462 | New WID on Charging Aspects for 5G Multicast-broadcast Services | China Mobile M2M Company Ltd. | WID new | Approval | Yes |
Yes
| revised | No | S5‑233671 | |||
S5‑233671 | New WID on Charging Aspects for 5G Multicast-broadcast Services | China Mobile M2M Company Ltd. | WID new | Approval | Yes |
Yes
| agreed | No | S5‑233462 | |||
S5‑233463 | Discussion paper on charging enhancements for 5MBS | China Mobile M2M Company Ltd. | discussion | Information | Yes |
Yes
| noted | No | ||||
7.3 | Charging Maintenance and Rel-18 small Enhancements | S5‑233251 | Rel-17 CR 32.257 Add LCM Event Type in EAS Deployment Charging Info | Amdocs Software Systems Ltd | CR | Approval | Yes |
Yes
| revised | No | S5‑233694 | |
S5‑233694 | Rel-17 CR 32.257 Add LCM Event Type in EAS Deployment Charging Info | Amdocs Software Systems Ltd | CR | Approval | Yes |
Yes
| agreed | No | S5‑233251 | |||
S5‑233252 | Rel-18 CR 32.257 Add LCM Event Type in EAS Deployment Charging Info | Amdocs Software Systems Ltd | CR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑233253 | Rel-17 CR 32.257 Add Usage Volume in EAS Infrastructure Usage Charging Info | Amdocs Software Systems Ltd | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑233254 | Rel-18 CR 32.257 Add Usage Volume in EAS Infrastructure Usage Charging Infon | Amdocs Software Systems Ltd | CR | Yes |
Yes
| withdrawn | Yes | |||||
S5‑233255 | Rel-17 CR 32.291 Add LCM Event Type in EAS Deployment Charging Info | Amdocs Software Systems Ltd | CR | Approval | Yes |
Yes
| revised | No | S5‑233695 | |||
S5‑233695 | Rel-17 CR 32.291 Add LCM Event Type in EAS Deployment Charging Info | Amdocs Software Systems Ltd | CR | Approval | Yes |
Yes
| agreed | No | S5‑233255 | |||
S5‑233256 | Rel-18 CR 32.291 Add LCM Event Type in EAS Deployment Charging Info | Amdocs Software Systems Ltd | CR | Approval | Yes |
Yes
| revised | No | S5‑233696 | |||
S5‑233696 | Rel-18 CR 32.291 Add LCM Event Type in EAS Deployment Charging Info | Amdocs Software Systems Ltd | CR | Approval | Yes |
Yes
| agreed | No | S5‑233256 | |||
S5‑233257 | Rel-17 CR 32.291 Update EAS Infrastructure Usage Charging Information | Amdocs Software Systems Ltd | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑233258 | Rel-18 CR 32.291 Update EAS Infrastructure Usage Charging Information | Amdocs Software Systems Ltd | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑233259 | Rel-17 32.298 Add LCM Event Type to EAS Deployment Charging Info | Amdocs Software Systems Ltd | CR | Approval | Yes |
Yes
| revised | No | S5‑233697 | |||
S5‑233697 | Rel-17 32.298 Add LCM Event Type to EAS Deployment Charging Info | Amdocs Software Systems Ltd | CR | Approval | Yes |
Yes
| agreed | No | S5‑233259 | |||
S5‑233260 | Rel-18 32.298 Add LCM Event Type to EAS Deployment Charging Info | Amdocs Software Systems Ltd | CR | Approval | Yes |
Yes
| revised | No | S5‑233698 | |||
S5‑233698 | Rel-18 32.298 Add LCM Event Type to EAS Deployment Charging Info | Amdocs Software Systems Ltd | CR | Approval | Yes |
Yes
| agreed | No | S5‑233260 | |||
S5‑233261 | Rel-17 CR 32.298 Update EAS Infrastructure Usage Charging Information | Amdocs Software Systems Ltd | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑233262 | Rel-18 CR 32.298 Update EAS Infrastructure Usage Charging Information | Amdocs Software Systems Ltd | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑233295 | Rel-17 CR 32.298 Correction of NetworkFunctionality civicLocation | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑233296 | Rel-18 CR 32.298 Correction of mMSChargingInformation NetworkFunctionality civicLocation | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑233297 | Rel-17 CR 32.291 Correction of requested units | Ericsson LM | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑233298 | Rel-18 CR 32.291 Correction of requested units | Ericsson LM | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑233299 | DP Use of QBC and FBC | Ericsson LM | discussion | Discussion | Yes |
Yes
| noted | No | ||||
S5‑233300 | DP Use of Charging Characteristics | Ericsson LM | discussion | Discussion | Yes |
Yes
| noted | No | ||||
S5‑233301 | DP Use of AMF charging profile | Ericsson LM | discussion | Discussion | Yes |
Yes
| noted | No | ||||
S5‑233448 | Correction the charging principle for alignment | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑233689 | |||
S5‑233689 | Correction the charging principle for alignment | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑233448 | |||
S5‑233449 | Add the converged charging mapping | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑233450 | Add the converged charging mapping | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑233451 | Addition of the Triggers in the CHF CDR | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑233452 | Addition of the Triggers in the CHF CDR | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑233519 | Rel-18 CR 32.260 IMS Charging Diagnostics | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑233682 | |||
S5‑233682 | Rel-18 CR 32.260 IMS Charging Diagnostics | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑233519 | |||
S5‑233520 | Rel-18 CR 32.291 IMS Charging Diagnostics | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑233683 | |||
S5‑233683 | Rel-18 CR 32.291 IMS Charging Diagnostics | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑233520 | |||
S5‑233521 | Rel-18 CR 32.298 IMS Charging Diagnostics | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑233684 | |||
S5‑233684 | Rel-18 CR 32.298 IMS Charging Diagnostics | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑233521 | |||
S5‑233654 | DP Use of QBC and FBC | Ericsson | discussion | discussion | Yes |
Yes
| noted | No | ||||
7.4 | Rel-18 Charging |   | ||||||||||
7.4.1 | Charging Aspects of Network Slicing Phase 2 | S5‑233376 | Rel-18 pCR 28.203 Introduce Architecture | MATRIXX Software | pCR | Approval | Yes |
Yes
| approved | No | ||
S5‑233377 | Rel-18 pCR 28.203 Introduce charging principles | MATRIXX Software | pCR | Approval | Yes |
Yes
| revised | No | S5‑233658 | |||
S5‑233658 | Rel-18 pCR 28.203 Introduce charging principles | MATRIXX Software | pCR | Approval | Yes |
Yes
| approved | No | S5‑233377 | |||
S5‑233378 | Rel-18 pCR 28.203 Introduce charging scenarios principles | MATRIXX Software | pCR | Approval | Yes |
Yes
| revised | No | S5‑233659 | |||
S5‑233659 | Rel-18 pCR 28.203 Introduce charging scenarios principles | MATRIXX Software | pCR | Approval | Yes |
Yes
| approved | No | S5‑233378 | |||
S5‑233379 | Rel-18 pCR 28.203 Introduce triggers | MATRIXX Software | pCR | Approval | Yes |
Yes
| revised | No | S5‑233660 | |||
S5‑233660 | Rel-18 pCR 28.203 Introduce triggers | MATRIXX Software | pCR | Approval | Yes |
Yes
| approved | No | S5‑233379 | |||
S5‑233380 | Rel-18 pCR 28.203 Introduce NSACF charging profile | MATRIXX Software | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑233407 | Rel-18 pCR 28.203 Introduce message flows | MATRIXX Software | pCR | Approval | Yes |
Yes
| revised | No | S5‑233657 | |||
S5‑233657 | Rel-18 pCR 28.203 Introduce message flows | MATRIXX Software | pCR | Approval | Yes |
Yes
| approved | No | S5‑233407 | |||
S5‑233644 | Draft TS 28.203 | MATRIXX Software | draft TS | Approval | Yes |
Yes
| approved | No | ||||
7.4.2 | Charging Aspects for NSSAA | S5‑233219 | Rel-18 TS 28.204 v0.0.0 Initial skeleton | MATRIXX Software | draft TS | Approval | Yes |
Yes
| approved | No | ||
S5‑233220 | Rel-18 pCR 28.204 Introduction of the Reference | MATRIXX Software | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑233221 | Rel-18 pCR 28.204 Introduction of the Scope | MATRIXX Software | pCR | Approval | Yes |
Yes
| revised | No | S5‑233656 | |||
S5‑233656 | Rel-18 pCR 28.204 Introduction of the Scope | MATRIXX Software | pCR | Approval | Yes |
Yes
| approved | No | S5‑233221 | |||
S5‑233222 | Rel-18 pCR 28.204 Introduction of the Terms | MATRIXX Software | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑233223 | Rel-18 pCR 28.203 Introduction of the Abbreviations | MATRIXX Software | pCR | Approval | Yes |
Yes
| approved | No | ||||
7.4.3 | Charging Aspects for Enhanced Support of Non-Public Networks |   | ||||||||||
7.4.4 | CHF Distributed Availability | S5‑233453 | DP on CHF Distributed Deployment Availability | Huawei | discussion | Discussion | Yes |
Yes
| noted | No | ||
S5‑233454 | An Architecture for CHF Distributed Availability in Migration Mode | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑233455 | An Architecture for CHF Distributed Availability in Multiple Backup Mode | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑233645 | Draft TS 28.204 | MATRIXX Software | draft TS | Approval | Yes |
Yes
| approved | No | ||||
7.5 | Charging studies |   | ||||||||||
7.5.1 | Study on Nchf charging services phase 2 | S5‑233302 | Rel-18 pCR 28.826 Adding service identifier based solution to clause 5.3 | Ericsson LM | pCR | Approval | Yes |
Yes
| noted | No | ||
S5‑233303 | Rel-18 pCR 28.826 Updating cancelling using charging session identifier clause 5.4 | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑233691 | |||
S5‑233691 | Rel-18 pCR 28.826 Updating cancelling using charging session identifier clause 5.4 | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑233303 | |||
S5‑233304 | Rel-18 pCR 28.826 Correcting use cases and key issues in clause 6.2 | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑233666 | |||
S5‑233666 | Rel-18 pCR 28.826 Correcting use cases and key issues in clause 6.2 | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑233304 | |||
S5‑233305 | Rel-18 pCR 28.826 New solutions for documenting binding in clause 6.3 | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑233681 | |||
S5‑233681 | Rel-18 pCR 28.826 New solutions for documenting binding in clause 6.3 | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑233305 | |||
S5‑233306 | Rel-18 pCR 28.826 New solutions for CDR handling in clause 6.3 | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑233715 | |||
S5‑233715 | Rel-18 pCR 28.826 New solutions for CDR handling in clause 6.3 | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑233306 | |||
S5‑233307 | Rel-18 pCR 28.826 New use case for containers exceeds message limit in clause 5.3 | Ericsson LM | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑233412 | Rel-18 pCR 28.826 Add the solution for reporting depending on the triggers | Huawei | pCR | Agreement | Yes |
Yes
| noted | No | ||||
S5‑233413 | Rel-18 pCR 28.826 Add the evaluation for charging reporting | Huawei | pCR | Agreement | Yes |
Yes
| noted | No | ||||
S5‑233414 | Rel-18 pCR 28.826 Add the solution for the undefined CDR | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑233701 | |||
S5‑233701 | Rel-18 pCR 28.826 Add the solution for the undefined CDR | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑233414 | |||
S5‑233415 | Rel-18 pCR 28.826 Update the evaluation for CHF rating | Huawei | pCR | Agreement | Yes |
Yes
| noted | No | ||||
S5‑233416 | Rel-18 pCR 28.826 Update the evaluation for non-blocking mode control | Huawei | pCR | Agreement | Yes |
Yes
| noted | No | ||||
S5‑233417 | Rel-18 pCR 28.826 Update the evaluation for the cancelling | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑233699 | |||
S5‑233699 | Rel-18 pCR 28.826 Update the evaluation for the cancelling | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑233417 | |||
S5‑233418 | Rel-18 pCR 28.826 Update the evaluation for the charging accuracy | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | ||||
S5‑233419 | Rel-18 pCR 28.826 Update the key issue, evaluation and conclusion in the clause 6 | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑233702 | |||
S5‑233702 | Rel-18 pCR 28.826 Update the key issue, evaluation and conclusion in the clause 6 | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑233419 | |||
S5‑233482 | Rel-18 pCR 28.826 Adding use case and key issue on handling of PEC and IEC triggers | Ericsson LM | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑233522 | Rel-18 pCR 28.826 Solution #1.15 Trigger | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑233646 | Draft TR 28.826 | Ericsson | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S5‑233653 | DP on Cancelling solutions | Huawei | discussion | discussion | Yes |
Yes
| noted | No | ||||
7.5.2 | Study on 5G roaming charging architecture for wholesale and retail scenarios | S5‑233308 | Rel-18 pCR 28.827 Correcting key issue for solution 1.4 | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑233716 | |
S5‑233716 | Rel-18 pCR 28.827 Correcting key issue for solution 1.4 | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑233308 | |||
S5‑233309 | Rel-18 pCR 28.827 Adding conclusion in clause 7.1 | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑233675 | |||
S5‑233675 | Rel-18 pCR 28.827 Adding conclusion in clause 7.1 | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑233309 | |||
S5‑233310 | Rel-18 pCR 28.827 New solution in clause 7.2 Roaming charging profile update CHF-to-CHF | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑233311 | Rel-18 pCR 28.827 Updating evaluation and conclusion in clause 7.2 | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑233674 | |||
S5‑233674 | Rel-18 pCR 28.827 Updating evaluation and conclusion in clause 7.2 | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑233311 | |||
S5‑233312 | Rel-18 pCR 28.827 Adding conclusion in clause 7.3 | Ericsson LM | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑233313 | Rel-18 pCR 28.827 New solution trigger of CHF-to-CHF interaction for clause 7.4 | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑233314 | Rel-18 pCR 28.827 Adding conclusion in clause 7.4 | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑233677 | |||
S5‑233677 | Rel-18 pCR 28.827 Adding conclusion in clause 7.4 | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑233314 | |||
S5‑233315 | Rel-18 pCR 28.827 Adding conclusion in clause 7.5 | Ericsson LM | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑233316 | Rel-18 pCR 28.827 Adding user reporting solution in clause 7.6 | Ericsson LM | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑233317 | Rel-18 pCR 28.827 Adding conclusion in clause 7.6 | Ericsson LM | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑233318 | Rel-18 pCR 28.827 Updating the conclusion | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑233680 | |||
S5‑233680 | Rel-18 pCR 28.827 Updating the conclusion | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑233318 | |||
S5‑233420 | Rel-18 pCR 28.827 Clarify Solution #2.10 for charging session between V-CHF and H-CHF per UE | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑233692 | |||
S5‑233692 | Rel-18 pCR 28.827 Clarify Solution #2.10 for charging session between V-CHF and H-CHF per UE | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑233420 | |||
S5‑233421 | Rel-18 pCR 28.827 Add Solution #2.x for charging session between V-CHF and H-CHF per PDU session | Huawei | pCR | Agreement | Yes |
Yes
| noted | No | ||||
S5‑233422 | Rel-18 pCR 28.827 Clarify Solution #2.11 for charging message exchange between V-CHF and H-CHF per charging data request | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑233693 | |||
S5‑233693 | Rel-18 pCR 28.827 Clarify Solution #2.11 for charging message exchange between V-CHF and H-CHF per charging data request | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑233422 | |||
S5‑233423 | Rel-18 pCR 28.827 Add Solution #2.y for charging message exchange between V-CHF and H-CHF based on quota management | Huawei | pCR | Agreement | Yes |
Yes
| noted | No | ||||
S5‑233424 | Rel-18 pCR 28.827 Update evaluation for key issue #2e in clause 7.2 | Huawei | pCR | Agreement | Yes |
Yes
| merged | No | S5‑233674 | |||
S5‑233425 | Rel-18 pCR 28.827 Add evaluation and conclusion for Solution #2.17 | Huawei | pCR | Agreement | Yes |
Yes
| noted | No | ||||
S5‑233426 | Rel-18 pCR 28.827 Update conclusion for clause 7.2 | Huawei | pCR | Agreement | Yes |
Yes
| merged | No | S5‑233674 | |||
S5‑233427 | Rel-18 pCR 28.827 Fix error in Solution #1.4 | Huawei | pCR | Agreement | Yes |
Yes
| merged | No | S5‑233716 | |||
S5‑233428 | Rel-18 pCR 28.827 Update evaluation for key issue #1e in clause 7.1 | Huawei | pCR | Agreement | Yes |
Yes
| merged | No | S5‑233675 | |||
S5‑233429 | Rel-18 pCR 28.827 Add conclusion for clause 7.1 | Huawei | pCR | Agreement | Yes |
Yes
| merged | No | S5‑233675 | |||
S5‑233647 | Draft TR 28.827 | Ericsson | draft TR | Approval | Yes |
Yes
| approved | No | ||||
7.5.3 | Study on Time Sensitive Networking charging | S5‑233430 | Rel18 pCR TR 28.839 Clarificatin on the solution the Network Exposure Charging | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | ||
S5‑233431 | Rel18 pCR TR 28.839 Addition of the solution for the 5GS bridge configuration | Huawei | pCR | Agreement | Yes |
Yes
| merged | No | S5‑233703 | |||
S5‑233432 | Rel18 pCR TR 28.839 Addition of the solution for the 5GS bridge management | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑233703 | |||
S5‑233703 | Rel18 pCR TR 28.839 Addition of the solution for the 5GS bridge management | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑233432 | |||
S5‑233433 | Rel18 pCR TR 28.839 Addition of the solution for the 5GS bridge management and configuration | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑233704 | |||
S5‑233704 | Rel18 pCR TR 28.839 Addition of the solution for the 5GS bridge management and configuration | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑233433 | |||
S5‑233434 | Rel18 pCR TR 28.839 Addition of the solution for the Enablers for TSC and TS Charging | Huawei | pCR | Agreement | Yes |
Yes
| noted | No | ||||
S5‑233435 | Rel18 pCR TR 28.839 Addition of the solution for the TSC from TSN station to TSN station | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑233706 | |||
S5‑233706 | Rel18 pCR TR 28.839 Addition of the solution for the TSC from TSN station to TSN station | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑233435 | |||
S5‑233436 | Rel18 pCR TR 28.839 Addition of the solution for the TSC from TSN station to TSN system | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑233707 | |||
S5‑233707 | Rel18 pCR TR 28.839 Addition of the solution for the TSC from TSN station to TSN system | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑233436 | |||
S5‑233648 | Draft TR 28.839 | Huawei | draft TR | Approval | Yes |
Yes
| approved | No | ||||
7.5.4 | Study on CHF Segmentation | S5‑233523 | Rel-18 pCR 28.840 Document Structure Update | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑233668 | |
S5‑233668 | Rel-18 pCR 28.840 Document Structure Update | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑233523 | |||
S5‑233530 | pCR TR 28.840 Abbreviations chapter Update | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑233678 | |||
S5‑233678 | pCR TR 28.840 Abbreviations chapter Update | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑233530 | |||
S5‑233533 | pCR TR 28.840 Symbols chapter Update | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑233534 | Draft TR 28.840 | Nokia, Nokia Shanghai Bell | draft TR | Approval | Yes |
Yes
| approved | No | ||||
7.5.5 | Study on Structure of Charging for Verticals | S5‑233437 | Rel18 pCR TR28.843 Addition of solution in the skeleton | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | ||
S5‑233438 | Rel18 pCR TR28.843 Addition of the Terms | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | ||||
S5‑233439 | Rel18 pCR TR28.843 Addition of the Key issues about architecture mapping | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑233708 | |||
S5‑233708 | Rel18 pCR TR28.843 Addition of the Key issues about architecture mapping | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑233439 | |||
S5‑233440 | Rel18 pCR TR28.843 Addition of the Key issues about charging principles clarification | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑233709 | |||
S5‑233709 | Rel18 pCR TR28.843 Addition of the Key issues about charging principles clarification | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑233440 | |||
S5‑233441 | Rel18 pCR TR28.843 Addition of the solution about Charging System selection | Huawei | pCR | Agreement | Yes |
Yes
| noted | No | ||||
S5‑233442 | Rel18 pCR TR28.843 Addition of the solution about CHFs Interaction | Huawei | pCR | Agreement | Yes |
Yes
| noted | No | ||||
S5‑233443 | Rel18 pCR TR28.843 Addition of the solution about Converged charging architecture | Huawei | pCR | Agreement | Yes |
Yes
| noted | No | ||||
S5‑233444 | Rel18 pCR TR28.843 Addition of the solution about Converged Vertical charging architecture | Huawei | pCR | Agreement | Yes |
Yes
| noted | No | ||||
S5‑233445 | Rel18 pCR TR28.843 Addition of the solution about Independent vertical charging architecture | Huawei | pCR | Agreement | Yes |
Yes
| noted | No | ||||
S5‑233446 | Rel18 pCR TR28.843 Addition of the solution about New TS for the charging architecture and Pinciples | Huawei | pCR | Agreement | Yes |
Yes
| noted | No | ||||
S5‑233447 | Rel18 pCR TR28.843 Addition of the solution about Restructure for the vertical charging | Huawei | pCR | Agreement | Yes |
Yes
| noted | No | ||||
S5‑233649 | Draft TR 28.843 | Huawei | draft TR | Approval | Yes |
Yes
| approved | No | ||||
7.5.6 | Study on charging aspects of Satellite in 5GS | S5‑233484 | Introduction of general background and satellite access architecture and functionality | CATT | pCR | Agreement | Yes |
Yes
| revised | No | S5‑233673 | |
S5‑233673 | Introduction of general background and satellite access architecture and functionality | CATT | pCR | Agreement | Yes |
Yes
| approved | No | S5‑233484 | |||
S5‑233485 | Introduction of satellite backhaul architecture and functionality | CATT | pCR | Agreement | Yes |
Yes
| approved | No | ||||
S5‑233486 | Introduction of charging modes | CATT | pCR | Agreement | Yes |
Yes
| revised | No | S5‑233669 | |||
S5‑233669 | Introduction of charging modes | CATT | pCR | Agreement | Yes |
Yes
| approved | No | S5‑233486 | |||
S5‑233487 | Add charging scenarios and key issues for Satellite access on converged charging for access connection | CATT | pCR | Agreement | Yes |
Yes
| revised | No | S5‑233672 | |||
S5‑233672 | Add charging scenarios and key issues for Satellite access on converged charging for access connection | CATT | pCR | Agreement | Yes |
Yes
| approved | No | S5‑233487 | |||
S5‑233488 | Add charging scenarios and key issues for Satellite backhaul on converged charging for data connection | CATT | pCR | Agreement | Yes |
Yes
| revised | No | S5‑233670 | |||
S5‑233670 | Add charging scenarios and key issues for Satellite backhaul on converged charging for data connection | CATT | pCR | Agreement | Yes |
Yes
| approved | No | S5‑233488 | |||
S5‑233650 | Draft TR 28.844 | CATT | draft TR | Approval | Yes |
Yes
| approved | No | ||||
8 | Any Other Business |   | ||||||||||
9 | Closing |   |