Tdoc List
2022-07-08 11:29
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‑224000 | Agenda | WG Chair | agenda | Yes |
Yes
| approved | No | |||
3 | IPR and legal declaration |   | ||||||||||
4 | Meetings and activities reports |   | ||||||||||
4.1 | Last SA5 meeting report | S5‑224001 | Report from last SA5 meeting | MCC | report | Yes |
Yes
| approved | No | |||
4.2 | Last SA meeting report |   | ||||||||||
4.3 | Inter-organizational reports |   | ||||||||||
5 | Cross-SWG issues |   | ||||||||||
5.1 | Administrative issues at SA5 level | S5‑224002 | e-meeting process | WG Chair | discussion | Yes |
Yes
| noted | No | |||
S5‑224003 | Post e-meeting email approval status | WG Chair | other | No |
No
| reserved | No | |||||
S5‑224010 | SA5 working procedures | WG Chair | other | Yes |
Yes
| approved | No | |||||
S5‑224014 | Process for management of draft TS-TRs | WG Chair | other | Yes |
Yes
| revised | No | S5‑224344 | ||||
S5‑224344 | Process for management of draft TS-TRs | WG Chair | other | - | Yes |
Yes
| approved | No | S5‑224014 | |||
S5‑224028 | SA5 Working Procedures | Nokia Shanghai Bell | other | Approval | Yes |
Yes
| revised | No | S5‑224346 | |||
S5‑224346 | SA5 Working Procedures | Nokia Shanghai Bell | other | Approval | Yes |
Yes
| approved | No | S5‑224028 | |||
5.2 | Technical issues at SA5 level | S5‑224296 | SA5 work item and study items | Ericsson,Deutsche Telekom | other | Endorsement | Yes |
Yes
| revised | No | S5‑224380 | |
S5‑224380 | SA5 work item and study items | Ericsson | other | Endorsement | Yes |
Yes
| noted | No | S5‑224296 | |||
5.3 | Liaison statements at SA5 level | S5‑224316 | Reply LS ccSA5 on Logical relationship between query parameters | C1-223711 | LS in | Yes |
Yes
| noted | No | |||
S5‑224319 | Reply LS ccSA5 on Logical relationship between query parameters | C3-223457 | LS in | Yes |
Yes
| noted | No | |||||
S5‑224323 | RE: LS on Inclusive language updates related to BBF TR-196 | BBF | LS in | Yes |
Yes
| noted | No | |||||
S5‑224329 | Reply LSccSA5 on Issues Network Slice information delivery to a 3rd party | S1-221224 | LS in | Yes |
Yes
| noted | No | |||||
S5‑224332 | Reply LS ccSA5 on Logical relationship between query parameters | S4-220796 | LS in | Yes |
Yes
| noted | No | |||||
S5‑224334 | Reply LS to the clarification of Dynamic EAS instantiation triggering | S6-221486 | LS in | Yes |
Yes
| noted | No | |||||
S5‑224336 | LS ccSA5 on potential IPR issues | SP-220712 | LS in | Yes |
Yes
| noted | No | |||||
S5‑224337 | Publication of GS ZSM009-2 and information about related ETSI ISG ZSM work | ETSI ISG ZSM | LS in | Yes |
Yes
| postponed | No | |||||
5.4 | SA5 meeting calendar | S5‑224015 | SA5 meeting calendar | WG Chair | other | Yes |
Yes
| noted | No | |||
6 | OAM&P |   | ||||||||||
6.1 | OAM&P Plenary | S5‑224004 | OAM&P action list | WG Vice Chair (Huawei) | other | Yes |
Yes
| noted | No | |||
S5‑224005 | agenda_with_Tdocs_sequence_proposal_OAM | WG Vice Chair (Huawei) | agenda | Yes |
Yes
| noted | No | |||||
S5‑224006 | OAM Exec Report | WG Vice Chair (Huawei) | report | No |
Yes
| noted | No | |||||
S5‑224007 | OAM Chair notes and conclusions | WG Chair | report | Yes |
Yes
| noted | No | |||||
S5‑224011 | Collection of useful endorsed document and external communication documents | WG Vice Chair (Huawei) | discussion | Yes |
Yes
| noted | No | |||||
S5‑224012 | Collection of Rel-18 3GPP SA5 OAM WoP | WG Vice Chair (Huawei) | discussion | Yes |
Yes
| revised | No | S5‑224345 | ||||
S5‑224345 | Collection of Rel-18 3GPP SA5 OAM WoP | WG Vice Chair (Huawei) | discussion | - | No |
Yes
| email approval | No | S5‑224012 | |||
S5‑224013 | Living document for stage 2-3 alignment | WG Chair | other | No |
Yes
| withdrawn | Yes | |||||
S5‑224019 | DP on number of OAM Rel-18 work/study items | WG chair, Vice chair (Huawei) | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑224381 | |||
S5‑224381 | DP on number of OAM Rel-18 work/study items | WG chair, Vice chair (Huawei) | discussion | Endorsement | Yes |
Yes
| noted | No | S5‑224019 | |||
S5‑224056 | LS on 3GPP SA5 work on intent driven management | Huawei | LS out | Approval | Yes |
Yes
| revised | No | S5‑224343 | |||
S5‑224343 | LS on 3GPP SA5 work on intent driven management | Huawei | LS out | Approval | Yes |
Yes
| approved | No | S5‑224056 | |||
S5‑224063 | Discussion for LS of dynamic EAS VNF instantiation | Intel Korea, Ltd. | discussion | Approval | Yes |
Yes
| noted | No | ||||
S5‑224064 | Reply LS on FS_eEDGEAPP, Solution for Dynamic EAS instantiation | Intel Korea, Ltd. | LS out | Approval | Yes |
Yes
| revised | No | S5‑224387 | |||
S5‑224387 | Reply LS on FS_eEDGEAPP, Solution for Dynamic EAS instantiation | Intel Korea, Ltd. | LS out | Approval | Yes |
Yes
| approved | No | S5‑224064 | |||
S5‑224089 | DP on PM/KPI based analytics | Nokia, Nokia Shanghai Bell | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑224176 | Discussion on Date/Time Format Definition | Nokia, Nokia Shanghai Bell | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑224223 | Reply LS to SA6 on DN energy efficiency data analytics | Huawei Technologies France | LS out | Agreement | Yes |
Yes
| revised | No | S5‑224342 | |||
S5‑224342 | Reply LS to SA6 on DN energy efficiency data analytics | Huawei Technologies France | LS out | Agreement | Yes |
Yes
| approved | No | S5‑224223 | |||
S5‑224225 | Discussion of Open-Source-Defined 6G Core Network (CN) | Xidian University | discussion | Yes |
Yes
| noted | No | |||||
S5‑224259 | Discussion Paper Federated network modelling for EP_Transport | Nokia, Nokia Shanghai Bell | discussion | Approval | Yes |
Yes
| noted | No | ||||
S5‑224317 | Reply LS ccSA5 on NR QoE | C1-224182 | LS in | Yes |
Yes
| noted | No | |||||
S5‑224321 | Answer to liaison IN EEPS(22)061016 | ETSI TC EE | LS in | Yes |
Yes
| noted | No | |||||
S5‑224322 | Liaison Response to 3GPP TSG-SA5 for Network Slice Ordering, Provisioning & Assurance | MEF Forum | LS in | Yes |
Yes
| postponed | No | |||||
S5‑224324 | Resubmitted LS on RAN3 agreements for NR QoE | R3-222890 | LS in | Yes |
Yes
| postponed | No | |||||
S5‑224325 | Reply LS on User Consent Updating | R3-224076 | LS in | Yes |
Yes
| postponed | No | |||||
S5‑224326 | LS on M6 Delay Threshold | R3-224079 | LS in | Yes |
Yes
| postponed | No | |||||
S5‑224327 | Response LS on changes over E1AP due to RACH NSA Measurements | R3-224080 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑224341 | Reply to: Response LS on changes over E1AP due to RACH NSA Measurements | Nokia | LS out | approval | Yes |
Yes
| approved | No | ||||
S5‑224328 | Reply LS on Report Amount for M4, M5, M6 and M7 measurements | R3-224084 | LS in | Yes |
Yes
| postponed | No | |||||
S5‑224330 | LS on O-RAN – UML models and tools to be used by 3GPP SA5 | O-RAN | LS in | Yes |
Yes
| postponed | No | |||||
S5‑224331 | LS on O-RAN – Transport Network Slicing Enhancement IM/DM TS28.541 | O-RAN | LS in | Yes |
Yes
| postponed | No | |||||
S5‑224333 | LS on DN energy efficiency data analytics | S6-221347 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑224335 | LS/r on study on KQIs for 5G service experience (reply to 3GPP TSG SA5-LS35) | ITU-T SG12 | LS in | Yes |
Yes
| noted | No | |||||
S5‑224338 | Resubmitted LS on FS_eEDGEAPP, Solution for Dynamic EAS instantiation | S6-220848 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑224339 | LS/r on methodology harmonization update (reply to 3GPP TSG SA5-S5-222570) | ITU-T | LS in | discussion | Yes |
Yes
| postponed | No | ||||
S5‑224340 | Reply LS on methodology harmonization update (reply to S5-224339/SG2-LS26) | Ericsson | LS out | discussion | No |
Yes
| withdrawn | Yes | ||||
6.2 | New OAM&P Work Item proposals | S5‑224016 | Rel-18 New WID on enhancement of governance and monitoring of closed control loop | ZTE Corporation, China Telecom | WID new | Agreement | Yes |
Yes
| noted | No | ||
S5‑224190 | Study on Data Management | Nokia, Nokia Shanghai Bell | WID new | Approval | Yes |
Yes
| noted | No | ||||
S5‑224235 | New WID on operational testing support for 3GPP NFs | Lenovo | WID new | Yes |
Yes
| noted | No | |||||
S5‑224238 | New R18 SID on conflict management | Lenovo Future Communications | SID new | Approval | Yes |
Yes
| noted | No | ||||
S5‑224258 | New SID on management aspects of computing network convergence | China Mobile E-Commerce Co. | SID new | Approval | Yes |
Yes
| noted | No | ||||
S5‑224260 | New SID on management aspects of Digital Twin Network | China Mobile E-Commerce Co. | SID new | Approval | Yes |
Yes
| noted | No | ||||
S5‑224270 | New Rel-18 WID Enhancement of Management Data Analytics phase 2 | Intel, NEC | WID new | Agreement | Yes |
Yes
| revised | No | S5‑224384 | S5‑223486 | ||
S5‑224384 | New Rel-18 WID Enhancement of Management Data Analytics phase 2 | Intel, NEC | WID new | Agreement | Yes |
Yes
| agreed | No | S5‑224270 | |||
S5‑224295 | New WID on methodology for deprecation of IOCs, data types and attributes | Ericsson | WID new | Yes |
Yes
| noted | No | |||||
6.3 | OAM&P Maintenance and Rel-18 small Enhancements |   | ||||||||||
6.4 | Intelligence and Automation |   | ||||||||||
6.4.1 | Self-Configuration of RAN NEs |   | ||||||||||
6.4.1.1 | RANSC_WoP#1 | S5‑224095 | Concept Proposal for Draft TS 28.317 | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||
S5‑224097 | TS 28.317 Use cases and requirements for ARCF data handling | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224099 | TS 28.317 Use cases and requirements for Self-configuration Management | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
6.4.1.2 | RANSC_WoP#2 |   | ||||||||||
6.4.1.3 | RANSC_WoP#3 |   | ||||||||||
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 | S5‑224275 | Rel-18 CR TS 28.541 Add network slice isolation | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| withdrawn | Yes | ||
S5‑224282 | Specify network slicing provisioning rules requirements | Ericsson LM, Deutsche Telekom | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224284 | Add network slice rules to NRM | Ericsson LM, Deutsche Telekom | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224294 | Rel-18 CR TS 28.541 Add network slice isolation | Nokia, Nokia Shanghai Bell, Huawei | draftCR | Approval | Yes |
Yes
| noted | No | ||||
6.5.2 | Additional NRM features phase 2 |   | ||||||||||
6.5.2.1 | AdNRM_ph2_WoP#1 | S5‑224048 | DP on new specification for TS 28.622 in the context of SBMA with new structure proposal | Huawei | discussion | Approval | Yes |
Yes
| revised | No | S5‑224347 | |
S5‑224347 | DP on new specification for TS 28.622 in the context of SBMA with new structure proposal | Huawei | discussion | Approval | Yes |
Yes
| endorsed | No | S5‑224048 | |||
S5‑224075 | TS28.541 Rel-18 Enhance 5G Core managed NF Profile NRM fragment | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| revised | No | S5‑224348 | |||
S5‑224348 | TS28.541 Rel-18 Enhance 5G Core managed NF Profile NRM fragment | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| approved | No | S5‑224075 | |||
S5‑224076 | TS28.541 Rel-18 NRM enhancements for UPFFunction | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| revised | No | S5‑224349 | |||
S5‑224349 | TS28.541 Rel-18 NRM enhancements for UPFFunction | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| approved | No | S5‑224076 | |||
S5‑224169 | Rel-18 Input to draftCR 28.622 Add Scheduler IOC (stage 2) | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| revised | No | S5‑224350 | S5‑223180 | ||
S5‑224350 | Rel-18 Input to draftCR 28.622 Add Scheduler IOC (stage 2) | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| approved | No | S5‑224169 | |||
S5‑224170 | Rel-18 Input to draftCR 28.623 Add Scheduler IOC (stage 3) | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| approved | No | S5‑223181 | |||
S5‑224171 | Rel-18 Input to draftCR 28.622 Enhance PerfMetricJob by service execution condition (stage 2) | Nokia, Nokia Shanghai Bell | other | Approval | Yes |
Yes
| noted | No | ||||
S5‑224172 | Rel-18 Input to draftCR 28.623 Enhance PerfMetricJob by service execution condition (stage 3) | Nokia, Nokia Shanghai Bell | other | Approval | Yes |
Yes
| noted | No | ||||
S5‑224175 | Rel-18 Input to draftCR 28.622 Add missing definitions of common data types | Nokia, Nokia Shanghai Bell | other | Approval | Yes |
Yes
| noted | No | ||||
S5‑224300 | Discussion on Enhanced QoS model for RLC and PDCP | Ericsson Inc. | discussion | Approval | Yes |
Yes
| noted | No | ||||
S5‑224301 | Rel-18 28.541 Enhanced QoS model for RLC and PDCP (stage 2) | Ericsson Inc. | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224303 | Rel-18 28.541 Add BWP set support to NRM (stage 3, YANG) | Ericsson Inc. | draftCR | Approval | Yes |
Yes
| revised | No | S5‑224352 | |||
S5‑224352 | Rel-18 28.541 Add BWP set support to NRM (stage 3, YANG) | Ericsson Inc. | draftCR | Approval | Yes |
Yes
| approved | No | S5‑224303 | |||
S5‑224306 | Rel-18 28.541 Enhanced QoS model for RLC and PDCP (stage 3, YANG) | Ericsson Inc. | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224308 | Rel-18 28.541 Add BWP set support to NRM (stage 2) | Ericsson Inc. | draftCR | Approval | Yes |
Yes
| revised | No | S5‑224353 | |||
S5‑224353 | Rel-18 28.541 Add BWP set support to NRM (stage 2) | Ericsson Inc. | draftCR | Approval | Yes |
Yes
| approved | No | S5‑224308 | |||
S5‑224312 | Rel-18 28.541 Add Enhanced QoS support in NRM (stage 2) | Ericsson Inc. | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224314 | Rel-18 28.541 Add Enhanced QoS support in NRM (stage 3, YANG) | Ericsson Inc. | draftCR | Approval | Yes |
Yes
| noted | No | ||||
6.5.2.2 | AdNRM_ph2_WoP#2 | S5‑224159 | draftCR TS 28.541 Add missing pLMNInfoList attribute for OperatorDU and GNBDUFunction | China Unicom | draftCR | Approval | Yes |
Yes
| noted | No | ||
6.5.2.3 | AdNRM_ph2_WoP#3 |   | ||||||||||
6.5.3 | Enhanced Edge Computing Management |   | ||||||||||
6.5.3.1 | eECM_WoP#1 | S5‑224017 | Rel-18 InputTodraftCR 28.538 EASFunction IOC and EESFunction IOC | AsiaInfo Technologies Inc | other | Approval | Yes |
Yes
| revised | No | S5‑224354 | S5‑223564 |
S5‑224354 | Rel-18 InputTodraftCR 28.538 EASFunction IOC and EESFunction IOC | AsiaInfo Technologies Inc | other | Approval | Yes |
Yes
| approved | No | S5‑224017 | |||
S5‑224018 | Rel-18 InputToDraftCR 28.538 Add modification procedures and query procedures | AsiaInfo Technologies Inc | other | Approval | Yes |
Yes
| noted | No | ||||
S5‑224035 | Rel-18 CR 28.622 Add stage 2 solution for LcmJob IOC | Intel Korea, Ltd. | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑224036 | Rel-18 CR 28.623 Add stage 3 solution for LcmJob IOC | Intel Korea, Ltd. | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑224037 | Rel-18 CR 28.538 Revise EAS VNF instantiation procedure | Intel Korea, Ltd. | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑224038 | Rel-18 CR 28.538 Revise EAS VNF termination procedure | Intel Korea, Ltd. | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑224039 | Rel-18 CR 28.538 Revise EAS VNF update procedure | Intel Korea, Ltd. | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑224040 | Rel-18 InputTodraftCR 28.538 Add EASProfile configurations | AsiaInfo Technologies Inc | other | Approval | Yes |
Yes
| noted | No | ||||
S5‑224044 | InputToDraftCR 28.538 EAS Profile | Samsung R&D Institute India | other | Yes |
Yes
| noted | No | |||||
S5‑224058 | Rel-18 CR 28.622 Add stage 2 solution for LcmJob IOC | Intel Korea, Ltd. | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224059 | Rel-18 CR 28.623 Add stage 3 solution for LcmJob IOC | Intel Korea, Ltd. | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224060 | Rel-18 CR 28.538 Revise EAS VNF instantiation procedure | Intel Korea, Ltd. | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224061 | Rel-18 CR 28.538 Revise EAS VNF termination procedure | Intel Korea, Ltd. | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224062 | Rel-18 CR 28.538 Revise EAS VNF update procedure | Intel Korea, Ltd. | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224385 | DraftCR for eECM – TS 28.538 | Samsung | draftCR | Approval | Yes |
Yes
| approved | No | ||||
6.5.3.2 | eECM_WoP#2 |   | ||||||||||
6.5.3.3 | eECM_WoP#3 |   | ||||||||||
6.5.3.4 | eECM_WoP#4 | S5‑224045 | InputToDraftCR 28.538 Asynchronous support | Samsung R&D Institute India | other | Yes |
Yes
| noted | No | |||
6.5.3.5 | eECM_WoP#5 |   | ||||||||||
6.5.3.6 | eECM_WoP#6 |   | ||||||||||
6.5.3.7 | eECM_WoP#7 |   | ||||||||||
6.5.3.8 | eECM_WoP#8 |   | ||||||||||
6.5.4 | Enhancement of QoE Measurement Collection |   | ||||||||||
6.5.4.1 | eQoE_WoP#1 | S5‑224241 | Adding QMC job | Ericsson Limited | draftCR | Approval | Yes |
Yes
| noted | No | ||
S5‑224244 | Handling of QoE measurement collection at handover in NR | Ericsson Limited | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224246 | ding Signalling Based Activation for NR | Ericsson Limited | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224249 | Rel-18 draftCR Add QMC job (stage 3 YANG) | Ericsson Inc. | draftCR | Approval | Yes |
Yes
| noted | No | ||||
6.5.4.2 | eQoE_WoP#2 |   | ||||||||||
6.5.5 | Access control for management service |   | ||||||||||
6.5.5.1 | MSAC_WoP#1 | S5‑224071 | Rel-18 TS28.532 enhance OpenAPI to support access control | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| noted | No | ||
S5‑224074 | Rel-18 TS28.533 enhancement to support access control | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| noted | No | ||||
6.5.5.2 | MSAC_WoP#2 | S5‑224072 | Rel-18 TS28.622 enhance NRM to support access control | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| noted | No | ||
S5‑224073 | Rel-18 TS28.623 enhance NRM to support access control Stage 3 | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| noted | No | ||||
6.5.5.3 | MSAC_WoP#3 |   | ||||||||||
6.5.6 | 5G performance measurements and KPIs phase 3 |   | ||||||||||
6.5.6.1 | PM_KPI_5G_Ph3_WoP#1 | S5‑224033 | Rel-18 CR 28.552 Add the per SSB RSRQ and SINR measurements | Intel Korea, Ltd. | CR | Approval | No |
Yes
| withdrawn | Yes | ||
S5‑224057 | Rel-18 CR 28.552 Add the per SSB RSRQ and SINR measurements | Intel Korea, Ltd. | draftCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑224166 | Rel-18 draftCR 28.552 Add beam specific inter-system handover counters related to MRO | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑224167 | Rel-16 draftCR 28.313 Correction of intra-RAT and inter-RAT too early and too late handover failures description | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224168 | Rel-18 draftCR 28.313 Add beam specific inter-system handover counters related to MRO | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| approved | No | ||||
6.5.6.2 | PM_KPI_5G_Ph3_WoP#2 | S5‑224034 | R18 draftCR TS 28.552 Add remote interference related performance measurement | China Telecom Corporation Ltd., Huawei | draftCR | Approval | Yes |
Yes
| revised | No | S5‑224356 | |
S5‑224356 | R18 draftCR TS 28.552 Add remote interference related performance measurement | China Telecom Corporation Ltd., Huawei | draftCR | Approval | Yes |
Yes
| approved | No | S5‑224034 | |||
S5‑224087 | Rel-18 draftCR TS 28.552 Add measurements for UE throughput of Dedicated BWP | China Telecom Corporation Ltd., ZTE | draftCR | Approval | Yes |
Yes
| noted | No | ||||
6.5.6.3 | PM_KPI_5G_Ph3_WoP#3 |   | ||||||||||
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 | S5‑224242 | Discussion paper to Add StateManagementEntity support for 5G | Nokia, Nokia Shanghai Bell | discussion | Endorsement | Yes |
Yes
| withdrawn | Yes | ||
S5‑224248 | Rel-18 TS 28.531 Update operations of allocateNsi, allocateNssi, deallocateNsi, deallocateNssi | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224276 | Rel-18 CR TS 28.623 Add AvailabilityStatus and LifecycleState to comDefs | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224277 | Rel-18 CR TS 28.541 Add lifecycleState and availabilityStatus attributes to NetworkSlice and NetworkSliceSubnet | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224278 | Rel-18 CR TS 28.531 Update procedures for asynchronous mode of operations for Network Slice and Network Slice Subnet LCM | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224298 | Discussion to Add StateManagementEntity support for 5G | Nokia, Nokia Shanghai Bell | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
6.6.2.2 | eNETSLICE_PRO_WoP#2 | S5‑224273 | Add asynchronous network slicing provisioning procedures | Ericsson LM, Deutsche Telekom | draftCR | Approval | Yes |
Yes
| noted | No | ||
S5‑224279 | S5-224XX5 Rel-18 CR TS 28.531 Update procedures for modification of Network Slice and Network Slice Subnet MOIs | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑224281 | Add Job IOCs for asynchronous network slicing provisioning procedures | Ericsson LM, Deutsche Telekom | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224292 | Discussion to Correct inconsistencies in Network Slicing | Nokia, Nokia Shanghai Bell | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
6.7 | Intelligence and Automation |   | ||||||||||
6.7.1 | Study on enhancement of autonomous network levels |   | ||||||||||
6.7.1.1 | FS_eANL_WoP#1 | S5‑224049 | pCR TR 28.910 Add key issues for enhancement of network optimization | Huawei,China Mobile | pCR | Approval | Yes |
Yes
| noted | No | ||
S5‑224050 | pCR TR 28.910 Add key issues for enhancement of ANL for RAN NE deployment | Huawei,China Mobile | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224127 | pCR 28.910 Add introduction on relevant SI/WI in 3GPP | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| noted | No | S5‑223318 | |||
S5‑224128 | pCR TR 28.910 Add key issue for enhancement of ANL for fault management | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
6.7.1.2 | FS_eANL_WoP#2 |   | ||||||||||
6.7.1.3 | FS_eANL_WoP#3 | S5‑224041 | Add key issue for autonomous network level for network slice provisioning | AsiaInfo Technologies Inc,CMCC | pCR | Approval | Yes |
Yes
| noted | No | ||
S5‑224111 | pCR TR 28.910 Add key issue for autonomous network level for 5GC network disaster recovery | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224224 | pCR TR 28.910 Add autonomous network level for service experience optimization | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
6.7.1.4 | FS_eANL_WoP#4 |   | ||||||||||
6.7.2 | Study on evaluation of autonomous network levels |   | ||||||||||
6.7.2.1 | FS_ANLEVA_WoP#1 | S5‑224047 | pCR TR 28.909 Add general process of evaluating the autonomous network level | Huawei,China Mobile | pCR | Approval | Yes |
Yes
| noted | No | S5‑223325 | |
S5‑224098 | pCR 28.909 Add ANLS evaluation of autonomous network | ZTE Corporation,China Mobile | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224129 | pCR 28.909 Add key issue of dimensions for autonomous network levels | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| noted | No | S5‑223319 | |||
S5‑224130 | pCR TR 28.909 Add key issues of generic methodology for autonomous network levels evaluation | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| noted | No | S5‑223320 | |||
6.7.2.2 | FS_ANLEVA_WoP#2 | S5‑224046 | pCR TR 28.909 Add key issues for KEI of autonomous network levels evaluation for radio network optimization | Huawei,China Mobile | pCR | Approval | Yes |
Yes
| noted | No | S5‑223324 | |
6.7.2.3 | FS_ANLEVA_WoP#3 |   | ||||||||||
6.7.2.4 | FS_ANLEVA_WoP#4 |   | ||||||||||
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‑224051 | pCR TR 28.912 Add issue for intent Report | Huawei, Deutsche Telekom | pCR | Approval | Yes |
Yes
| revised | No | S5‑224358 | |
S5‑224358 | pCR TR 28.912 Add issue for intent Report | Huawei, Deutsche Telekom | pCR | Approval | Yes |
Yes
| approved | No | S5‑224051 | |||
S5‑224052 | pCR TR 28.912 Update issue for intent confliction | Huawei, Deutsche Telekom | pCR | Approval | Yes |
Yes
| revised | No | S5‑224263 | |||
S5‑224053 | pCR TR 28.912 Add conclusion and recommendation for existing issues | Huawei, Deutsche Telekom | pCR | Approval | Yes |
Yes
| revised | No | S5‑224362 | |||
S5‑224362 | pCR TR 28.912 Add conclusion and recommendation for existing issues | Huawei, Deutsche Telekom | pCR | Approval | Yes |
Yes
| approved | No | S5‑224053 | |||
S5‑224112 | pCR TR 28.912 add potential solution for 5GC intent expectation | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑224361 | |||
S5‑224361 | pCR TR 28.912 add potential solution for 5GC intent expectation | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑224112 | |||
S5‑224178 | pCR 28.912 Intent-driven Closed Loop Composition | Nokia Italy | pCR | Yes |
Yes
| revised | No | S5‑224359 | ||||
S5‑224359 | pCR 28.912 Intent-driven Closed Loop Composition | Nokia Italy | pCR | - | Yes |
Yes
| approved | No | S5‑224178 | |||
S5‑224263 | pCR TR 28.912 Update issue for intent confliction | Huawei, Deutsche Telekom,Nokia | pCR | Approval | Yes |
Yes
| revised | No | S5‑224360 | S5‑224052 | ||
S5‑224360 | pCR TR 28.912 Update issue for intent confliction | Huawei, Deutsche Telekom,Nokia | pCR | Approval | Yes |
Yes
| approved | No | S5‑224263 | |||
6.7.3.3 | FS_eIDMS_MN_WoP#3 |   | ||||||||||
6.7.3.4 | FS_eIDMS_MN_WoP#4 | S5‑224054 | pCR TR 28.912 Add issue for mapping intent operations between 3GPP and TM Forum | Huawei, Deutsche Telekom | pCR | Approval | Yes |
Yes
| revised | No | S5‑224363 | |
S5‑224363 | pCR TR 28.912 Add issue for mapping intent operations between 3GPP and TM Forum | Huawei, Deutsche Telekom | pCR | Approval | Yes |
Yes
| approved | No | S5‑224054 | |||
6.7.4 | Study on intent-driven management for network slicing |   | ||||||||||
6.7.4.1 | FS_NETSLICE_IDMS_WoP#1 | S5‑224069 | Add use case of Intent driven management for network slice feasibility check | AsiaInfo Technologies Inc | pCR | Approval | Yes |
Yes
| withdrawn | Yes | ||
S5‑224070 | DP on mapping of network slice operations and intent operations | AsiaInfo Technologies Inc | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑224077 | Add use case of Intent driven management for network slice management capability exposure | AsiaInfo Technologies Inc | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224104 | Add use case of Intent driven management for network slice feasibility check | AsiaInfo Technologies Inc | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224113 | pCR TR 28.836 add use case of slice modification | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224114 | pCR TR 28.836 add intent LCM | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224297 | Discussion paper on study intent driven management for network slicing | Ericsson LM | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
6.7.4.2 | FS_NETSLICE_IDMS_WoP#2 | S5‑224116 | pCR TR 28.836 add potential ExpectationTarget for intent MnS | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||
S5‑224313 | pCR 28.836 Add solution for use case 5.1.1 | Microsoft Europe SARL | pCR | Approval | Yes |
Yes
| noted | No | ||||
6.7.4.3 | FS_NETSLICE_IDMS_WoP#3 | S5‑224115 | pCR TR 28.836 add intent model IntentExpectation for network slicing instance | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||
6.7.4.4 | FS_NETSLICE_IDMS_WoP#4 |   | ||||||||||
6.7.4.5 | FS_NETSLICE_IDMS_WoP#5 |   | ||||||||||
6.7.5 | Study on AI/ ML management |   | ||||||||||
6.7.5.1 | FS_AIML_MGMT_WoP#1 | S5‑224020 | pCR 28.908 Requirements on AIML context | Nokia Italy | pCR | Yes |
Yes
| revised | No | S5‑224364 | ||
S5‑224364 | pCR 28.908 Requirements on AIML context | Nokia Italy | pCR | - | Yes |
Yes
| approved | No | S5‑224020 | |||
S5‑224088 | DP on Modelling AIML Entity | Nokia, Nokia Shanghai Bell | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑224101 | pCR TR 28.908 Add AIML capabilities deployment scenarios | Huawei, Nokia, Ericsson | pCR | Approval | Yes |
Yes
| merged | No | S5‑224365 | |||
S5‑224266 | pCR 28.908 Add AI-ML workflow for 5GS | Intel, NEC | pCR | Approval | Yes |
Yes
| revised | No | S5‑224365 | |||
S5‑224365 | pCR 28.908 Add AI-ML workflow for 5GS | Intel, NEC | pCR | Approval | Yes |
Yes
| approved | No | S5‑224266 | |||
S5‑224315 | pCR TR 28.908 Clarifications into the overview and terminologies updates | NEC, Intel | pCR | Approval | Yes |
Yes
| revised | No | S5‑224366 | |||
S5‑224366 | pCR TR 28.908 Clarifications into the overview and terminologies updates | NEC, Intel | pCR | Approval | Yes |
Yes
| approved | No | S5‑224315 | |||
6.7.5.2 | FS_AIML_MGMT_WoP#2 | S5‑224021 | pCR 28.908 Requirements on AIML Inference History | Nokia Italy | pCR | Yes |
Yes
| revised | No | S5‑224367 | ||
S5‑224367 | pCR 28.908 Requirements on AIML Inference History | Nokia Italy | pCR | - | Yes |
Yes
| approved | No | S5‑224021 | |||
S5‑224022 | pCR 28.908 Requirements on Coordinating AIML inference | Nokia Italy | pCR | Yes |
Yes
| noted | No | |||||
S5‑224267 | pCR 28.908 Add use case on AI-ML entity validation | Intel, NEC | pCR | Approval | Yes |
Yes
| revised | No | S5‑224368 | |||
S5‑224368 | pCR 28.908 Add use case on AI-ML entity validation | Intel, NEC | pCR | Approval | Yes |
Yes
| approved | No | S5‑224267 | |||
6.7.5.3 | FS_AIML_MGMT_WoP#3 | S5‑224023 | pCR 28.908 Requirements on AIML Testing | Nokia Italy | pCR | Yes |
Yes
| revised | No | S5‑224369 | ||
S5‑224369 | pCR 28.908 Requirements on AIML Testing | Nokia Italy | pCR | - | Yes |
Yes
| approved | No | S5‑224023 | |||
S5‑224268 | pCR 28.908 Add use case on AI-ML entity testing | Intel, NEC | pCR | Approval | Yes |
Yes
| merged | No | S5‑224369 | |||
6.7.5.4 | FS_AIML_MGMT_WoP#4 | S5‑224024 | pCR 28.908 Requirements on AIMLEntity Capability Discovery | Nokia Italy | pCR | Yes |
Yes
| revised | No | S5‑224386 | ||
S5‑224386 | pCR 28.908 Requirements on AIMLEntity Capability Discovery | Nokia Italy | pCR | - | Yes |
Yes
| approved | No | S5‑224024 | |||
S5‑224025 | 4. S5-xxxxxxx pCR 28.908 Requirements on Pre-processed event data for ML training | Nokia Italy | pCR | Yes |
Yes
| revised | No | S5‑224370 | ||||
S5‑224370 | pCR 28.908 Requirements on Pre-processed event data for ML training | Nokia Italy | pCR | - | Yes |
Yes
| approved | No | S5‑224025 | |||
S5‑224102 | pCR TR 28.908 Add use case on AI-ML model update | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑224371 | |||
S5‑224371 | pCR TR 28.908 Add use case on AI-ML model update | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑224102 | |||
S5‑224103 | pCR TR 28.908 Add use case on AI-ML model deployment | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224251 | pCR TR 28.908 Add use case on AI-ML model deployment | CATT | pCR | Yes |
Yes
| revised | No | S5‑224372 | ||||
S5‑224372 | pCR TR 28.908 Add use case on AI-ML model deployment | CATT | pCR | - | Yes |
Yes
| approved | No | S5‑224251 | |||
6.7.5.5 | FS_AIML_MGMT_WoP#5 |   | ||||||||||
6.7.5.6 | FS_AIML_MGMT_WoP#6 |   | ||||||||||
6.7.5.7 | FS_AIML_MGMT_WoP#7 |   | ||||||||||
6.7.5.8 | FS_AIML_MGMT_WoP#8 |   | ||||||||||
6.7.5.9 | FS_AIML_MGMT_WoP#9 |   | ||||||||||
6.7.5.10 | FS_AIML_MGMT_WoP#10 |   | ||||||||||
6.7.6 | Study on Enhancement of the management aspects related to NWDAF |   | ||||||||||
6.7.6.1 | FS_MANWDAF_WoP#1 | S5‑224239 | pCR 28864 KI1 KI2 update | China Telecommunications | pCR | Approval | Yes |
Yes
| revised | No | S5‑224373 | |
S5‑224373 | pCR 28864 KI1 KI2 update | China Telecommunications | pCR | Approval | Yes |
Yes
| approved | No | S5‑224239 | |||
S5‑224253 | pCR 28.864 Add potential solution for KI#1 | Chinatelecom Cloud | pCR | Yes |
Yes
| revised | No | S5‑224374 | ||||
S5‑224374 | pCR 28.864 Add potential solution for KI#1 | Chinatelecom Cloud | pCR | - | Yes |
Yes
| approved | No | S5‑224253 | |||
S5‑224254 | pCR 28.864 Add potential solution for KI#2 | Chinatelecom Cloud | pCR | Yes |
Yes
| revised | No | S5‑224375 | ||||
S5‑224375 | pCR 28.864 Add potential solution for KI#2 | Chinatelecom Cloud | pCR | - | Yes |
Yes
| approved | No | S5‑224254 | |||
S5‑224299 | pCR 28.864 Add KI for managing NWDAF output | Lenovo Future Communications | pCR | Yes |
Yes
| noted | No | |||||
6.7.6.2 | FS_MANWDAF_WoP#2 | S5‑224177 | pCR 28.864 Potential solution on service usage of NWDAF | Nokia Italy | pCR | No |
Yes
| withdrawn | Yes | |||
S5‑224240 | Discussion paper on relationship between the EE of NWDAF and the performance measurements of NWDAF | China Telecommunications | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑224382 | |||
S5‑224382 | Discussion paper on relationship between the EE of NWDAF and the performance measurements of NWDAF | China Telecommunications | discussion | Endorsement | Yes |
Yes
| endorsed | No | S5‑224240 | |||
S5‑224255 | pCR 28.864 Add potential solution for KI#5 | Chinatelecom Cloud | pCR | Yes |
Yes
| revised | No | S5‑224377 | ||||
S5‑224377 | pCR 28.864 Add potential solution for KI#5 | Chinatelecom Cloud | pCR | - | Yes |
Yes
| approved | No | S5‑224255 | |||
S5‑224262 | New key issue for the performance management of the NWDAF related on service output generation | Chinatelecom Cloud | pCR | Yes |
Yes
| noted | No | |||||
S5‑224265 | pCR 28.864 Add potential performance metrics related with UE groups for KI#3 | China Mobile E-Commerce Co. | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑224269 | pCR TR 28.864 Add potential solution related with number of notifications for data collection exposure capability | China Mobile E-Commerce Co. | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224271 | pCR TR 28.864 Add potential solution related with number of notifications for NWDAF Data Collection | China Mobile E-Commerce Co. | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224272 | pCR TR 28.864 Add potential solution related with number of subscriptions for data collection exposure capability | China Mobile E-Commerce Co. | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224274 | pCR TR 28.864 Add potential solution related with number of subscriptions for NWDAF Data Collection | China Mobile E-Commerce Co. | pCR | Approval | Yes |
Yes
| noted | No | ||||
6.7.7 | Study on Fault Supervision Evolution |   | ||||||||||
6.7.7.1 | FS_FSEV_WoP#1 |   | ||||||||||
6.7.7.2 | FS_FSEV_WoP#2 | S5‑224179 | pCR TR 28.830 Add background | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||
S5‑224180 | pCR TR 28.830 Add relation description with existing MnS | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224213 | pCR 28.830 Add clause Background | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224218 | pCR 28.830 Add key issue: Definition of terms | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑224383 | |||
S5‑224383 | pCR 28.830 Add key issue: Definition of terms | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑224218 | |||
S5‑224219 | pCR 28.830 Add framework of FSEV | Huawei, China Mobile | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224220 | pCR 28.830 Add interface description | Huawei, China Mobile | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224221 | pCR 28.830 Add description of issue E2E SLS degradation | Huawei, China Mobile | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224222 | pCR 28.830 Add solution of issue E2E SLS degradation | Huawei, China Mobile | pCR | Approval | Yes |
Yes
| noted | No | ||||
6.7.7.3 | FS_FSEV_WoP#3 | S5‑224181 | pCR TR 28.830 Add description of key issue service outage | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||
S5‑224182 | pCR TR 28.830 Add description of key issue performance degradation | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224183 | pCR TR 28.830 Add description of key issue 5GC service failure prediction | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224184 | pCR TR 28.830 Add solution of key issue service outage | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224185 | pCR TR 28.830 Add solution of key issue performance degradation | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224186 | pCR TR 28.830 Add solution of key issue 5GC service failure prediction | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
6.7.8 | Study on measurement data collection to support RAN intelligence |   | ||||||||||
6.7.8.1 | FS_MEDACO_RAN_WoP#1 | S5‑224029 | Rel-18 TR 28.838 v0.0.0 | Intel Korea, Ltd. | draft TR | Approval | Yes |
Yes
| approved | No | ||
S5‑224030 | pCR 28.838 skeleton | Intel Korea, Ltd. | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑224031 | pCR 28.838 scope | Intel Korea, Ltd. | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑224032 | pCR 28.838 overview | Intel Korea, Ltd. | pCR | Approval | Yes |
Yes
| revised | No | S5‑224379 | |||
S5‑224379 | pCR 28.838 overview | Intel Korea, Ltd. | pCR | Approval | Yes |
Yes
| approved | No | S5‑224032 | |||
6.7.8.2 | FS_MEDACO_RAN_WoP#2 |   | ||||||||||
6.7.8.3 | FS_MEDACO_RAN_WoP#3 |   | ||||||||||
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‑224302 | pCR TR 28.925 Add key issue on requirements and use cases supporting multiple MnS discovery service producers | China Unicom | pCR | Approval | Yes |
Yes
| noted | No | ||
6.8.1.2 | FS_eSBMA_WoP#2 |   | ||||||||||
6.8.1.3 | FS_eSBMA_WoP#3 |   | ||||||||||
6.8.1.4 | FS_eSBMA_WoP#4 |   | ||||||||||
6.8.1.5 | FS_eSBMA_WoP#5 | S5‑224160 | pCR TR28.925 Add conclusion for overview and usage guide for SBMA specifications | HuaWei Technologies Co., Ltd | pCR | Yes |
Yes
| approved | No | |||
S5‑224161 | pCR TR28.925 Add description on MnFs to be managed | HuaWei Technologies Co., Ltd | pCR | Yes |
Yes
| noted | No | |||||
6.8.1.6 | FS_eSBMA_WoP#6 |   | ||||||||||
6.8.2 | Study on Basic SBMA enabler enhancements |   | ||||||||||
6.8.2.1 | FS_eSBMAe_WoP#1 |   | ||||||||||
6.8.2.2 | FS_eSBMAe_WoP#2 |   | ||||||||||
6.8.2.3 | FS_eSBMAe_WoP#3 | S5‑224236 | pCR 28.831 Add key issue: Definition of createMOI | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||
S5‑224237 | pCR 28.831 Add key issue: Definition of getMOIAttributes | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224280 | Rel-18 pCR TR 28.831 Add a new key issue for Adding capabilities and procedures to advertise supported IOCs, attributes, conditions, and constraints by the MnS Producer | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
6.8.2.4 | FS_eSBMAe_WoP#4 | S5‑224250 | pCR 28.831 Add potential requirements for key issue Targeted notification subscription | Nokia, Nokia Shanhai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑224424 | |
S5‑224424 | pCR 28.831 Add potential requirements for key issue Targeted notification subscription | Nokia, Nokia Shanhai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑224250 | |||
S5‑224252 | pCR 28.831 Add potential solutions for key issue Targeted notification subscription | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑224425 | |||
S5‑224425 | pCR 28.831 Add potential solutions for key issue Targeted notification subscription | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑224252 | |||
S5‑224256 | pCR 28.831 Add analysis of XPath as potential solution | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224257 | pCR 28.831 Add analysis of JSONPointer as potential solution | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑224426 | |||
S5‑224426 | pCR 28.831 Add analysis of JSONPointer as potential solution | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑224257 | |||
S5‑224293 | pCR 28.831 Add analysis of JSONPath as potential solution | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑224427 | |||
S5‑224427 | pCR 28.831 Add analysis of JSONPath as potential solution | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑224293 | |||
6.8.2.5 | FS_eSBMAe_WoP#5 |   | ||||||||||
6.8.2.6 | FS_eSBMAe_WoP#6 |   | ||||||||||
6.8.2.7 | FS_eSBMAe_WoP#7 |   | ||||||||||
6.8.2.8 | FS_eSBMAe_WoP#8 |   | ||||||||||
6.8.2.9 | FS_eSBMAe_WoP#9 |   | ||||||||||
6.8.2.10 | FS_eSBMAe_WoP#10 | S5‑224247 | YANG Mapping Corrections | Ericsson Hungary Ltd | draftCR | Approval | Yes |
Yes
| approved | No | ||
6.8.3 | Study on Management Aspects of URLLC |   | ||||||||||
6.8.3.1 | FS_URLLC_Mgt_WoP#1 |   | ||||||||||
6.8.3.2 | FS_URLLC_Mgt_WoP#2 |   | ||||||||||
6.8.3.3 | FS_URLLC_Mgt_WoP#3 | S5‑224131 | Add sulotion for URLLC performance measurements related to latency | China Unicom, CATT | pCR | Approval | Yes |
Yes
| noted | No | ||
S5‑224132 | Discussion on URLLC performance measurements related to latency and reliability | China Unicom | discussion | Approval | Yes |
Yes
| noted | No | ||||
S5‑224133 | Discussion on URLLC performance measurements related to resource load of URLLC services | China Unicom | discussion | Approval | Yes |
Yes
| noted | No | ||||
S5‑224134 | Add Key Issue on URLLC Performance measurements | China Unicom | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224135 | Add solution for URLLC performance measurements related to DL resource load | China Unicom | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224136 | Add solution for URLLC performance measurements related to UL resource load with cancellation indication | China Unicom | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224137 | Add solution for URLLC performance measurements related to UL resource load with power boosting | China Unicom | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224158 | Add solution for URLLC performance measurements related to reliability | China Unicom | pCR | Approval | Yes |
Yes
| noted | No | ||||
6.8.3.4 | FS_URLLC_Mgt_WoP#4 |   | ||||||||||
6.8.4 | Study on Management Aspect of 5GLAN |   | ||||||||||
6.8.4.1 | FS_5GLAN_Mgt_WoP#1 |   | ||||||||||
6.8.4.2 | FS_5GLAN_Mgt_WoP#2 | S5‑224117 | pCR 28.833 add one key issue for PDU session management | Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||
S5‑224261 | pCR TR 28.833 Change TR structure | China Mobile E-Commerce Co. | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑224264 | pCR TR 28.833 Add key issue and potential solutions for 5G VN group data management of FS_5GLAN_Mgt | China Mobile E-Commerce Co. | pCR | Approval | Yes |
Yes
| approved | No | ||||
6.8.4.3 | FS_5GLAN_Mgt_WoP#3 | S5‑224118 | pCR 28.833 add one key issue for performance measurements per 5G VN group | China Southern Power Grid, Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||
6.8.4.4 | FS_5GLAN_Mgt_WoP#4 |   | ||||||||||
6.8.5 | Study on Management of Cloud Native Virtualized Network Functions |   | ||||||||||
6.8.5.1 | FS_MCVNF_WoP#1 | S5‑224105 | pCR 28.834 Add use case for VNFC failover | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑224428 | |
S5‑224428 | pCR 28.834 Add use case for VNFC failover | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑224105 | |||
S5‑224106 | pCR 28.834 Add background of supported LCM procedures | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224107 | pCR 28.834 Add concepts from ETSI NFV | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224108 | pCR 28.834 Add use case for NF creation as cloud native VNF | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224109 | pCR 28.834 Add use case for VNF instantiation | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224110 | pCR 28.834 Add use case for VNF scaling | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑224431 | |||
S5‑224431 | pCR 28.834 Add use case for VNF scaling | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑224110 | |||
S5‑224283 | pCR 28.834 Add Use Case on Configuration of the cloud-native VNF using generic OAM functions | China Mobile Com. Corporation | pCR | Approval | Yes |
Yes
| revised | No | S5‑224430 | |||
S5‑224430 | pCR 28.834 Add Use Case on Configuration of the cloud-native VNF using generic OAM functions | China Mobile Com. Corporation | pCR | Approval | Yes |
Yes
| approved | No | S5‑224283 | |||
S5‑224285 | pCR TR 28.834 Add Use Case on Traffic management of the cloud-native VNF using generic OAM functions | China Mobile Com. Corporation | pCR | Approval | Yes |
Yes
| revised | No | S5‑224429 | |||
S5‑224429 | pCR TR 28.834 Add Use Case on Traffic management of the cloud-native VNF using generic OAM functions | China Mobile Com. Corporation | pCR | Approval | Yes |
Yes
| approved | No | S5‑224285 | |||
S5‑224304 | pCR 28.834 Add concepts and background | Microsoft Europe SARL | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224305 | pCR 28.834 Add use case on LCM_query cloud-native VNF package | Microsoft Europe SARL | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224307 | pCR 28.834 Add use case on LCM_instantiation using de-facto standards | Microsoft Europe SARL | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224309 | pCR 28.834 Add use case on LCM_configuration using de-facto standards | Microsoft Europe SARL | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224310 | pCR 28.834 Add use case on LCM_modification using de-facto standards | Microsoft Europe SARL | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224311 | pCR 28.834 Add use case on LCM_deletion using de-facto standards | Microsoft Europe SARL | pCR | Approval | Yes |
Yes
| noted | No | ||||
6.8.5.2 | FS_MCVNF_WoP#2 |   | ||||||||||
6.8.5.3 | FS_MCVNF_WoP#3 |   | ||||||||||
6.8.6 | Study on Management Aspects of 5G MOCN Network Sharing Phase2 |   | ||||||||||
6.8.6.1 | FS_MANS_ph2_WoP#1 | S5‑224092 | pCR TR 28.835 Add potential solutions to address the no PLMN ID at NRcellCU issue | ZTE Corporation. | pCR | Approval | Yes |
Yes
| noted | No | ||
S5‑224094 | pCR TR 28.835 Add issue and potential solution for collection of operator specific performance measurements | ZTE Corporation. | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224162 | pCR TR 28.835 Add key issue remote access requirement of MOP-SR-DM for each POP | China Unicom | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑224163 | pCR TR 28.835 Add potential solution for management requirement between MOP-NM and MOP-SR-DM | China Unicom | pCR | Approval | Yes |
Yes
| revised | No | S5‑224432 | |||
S5‑224432 | pCR TR 28.835 Add potential solution for management requirement between MOP-NM and MOP-SR-DM | China Unicom | pCR | Approval | Yes |
Yes
| approved | No | S5‑224163 | |||
S5‑224165 | pCR TR 28.835 Add potential solution for remote access requirement of MOP-SR-DM for each POP | China Unicom | pCR | Approval | Yes |
Yes
| approved | No | ||||
6.8.6.2 | FS_MANS_ph2_WoP#2 | S5‑224164 | pCR TR 28.835 Add potential solution for performance measurements without PLMN ID at NRcellCU | China Unicom | pCR | Approval | Yes |
Yes
| noted | No | ||
6.8.6.3 | FS_MANS_ph2_WoP#3 |   | ||||||||||
6.8.7 | Study on Management of Trace/MDT phase 2 |   | ||||||||||
6.8.7.1 | FS_5GMDT_Ph2_WoP#1 | S5‑224174 | Rel-18 pCR 28.837 Reporting of Collected Management Data | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑223403 | |
6.8.7.2 | FS_5GMDT_Ph2_WoP#2 | S5‑224173 | Rel-18 pCR 28.837 Solution to Issue Gaps in Signalling Based Trace Activation | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||
6.8.7.3 | FS_5GMDT_Ph2_WoP#3 | S5‑224083 | Rel-18 pCR 28.837 Key Issue on alignment of “Report Amount” parameter for Immediate MDT measurements | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||
6.8.7.4 | FS_5GMDT_Ph2_WoP#4 |   | ||||||||||
6.8.7.5 | FS_5GMDT_Ph2_WoP#5 |   | ||||||||||
6.8.7.6 | FS_5GMDT_Ph2_WoP#6 |   | ||||||||||
6.8.7.7 | FS_5GMDT_Ph2_WoP#7 |   | ||||||||||
6.8.7.8 | FS_5GMDT_Ph2_WoP#8 |   | ||||||||||
6.8.8 | Study on YANG PUSH |   | ||||||||||
6.8.8.1 | FS_YANG_WoP#1 |   | ||||||||||
6.8.8.2 | FS_YANG_WoP#2 | S5‑224243 | Close down YANG-Push study | Ericsson Hungary Ltd | pCR | Approval | Yes |
Yes
| approved | No | ||
6.8.8.3 | FS_YANG_WoP#3 |   | ||||||||||
6.8.8.4 | FS_YANG_WoP#4 |   | ||||||||||
6.8.8.5 | FS_YANG_WoP#5 |   | ||||||||||
6.8.9 | Study on Management Aspects of IoT NTN Enhancements |   | ||||||||||
6.8.9.1 | FS_IOT_NTN_WoP#1 | S5‑224065 | TR 28.841-0.0.0 initial skeleton | China Unicom | draft TR | Approval | Yes |
Yes
| approved | No | ||
S5‑224066 | pCR 28.841 Add TR structure | China Unicom | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑224067 | pCR TR 28.841 Add Scope | China Unicom | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑224068 | pCR TR 28.841 Add Introduction | China Unicom | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑224084 | pCR 28.841 Add concepts and background | China Unicom | pCR | Approval | Yes |
Yes
| revised | No | S5‑224433 | |||
S5‑224433 | pCR 28.841 Add concepts and background | China Unicom | pCR | Approval | Yes |
Yes
| approved | No | S5‑224084 | |||
6.8.9.2 | FS_IOT_NTN_WoP#2 |   | ||||||||||
6.8.9.3 | FS_IOT_NTN_WoP#3 |   | ||||||||||
6.9 | Support of New Services |   | ||||||||||
6.9.1 | Study on enhancement of management of non-public networks |   | ||||||||||
6.9.1.1 | FS_OAM_eNPN_WoP#1 | S5‑224080 | pCR 28.907 Rapporteur proposal | Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||
6.9.1.2 | FS_OAM_eNPN_WoP#2 |   | ||||||||||
6.9.1.3 | FS_OAM_eNPN_WoP#3 | S5‑224078 | pCR 28.907 Update performance data collection procedure | Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||
S5‑224079 | pCR 28.907 Potential solution for SLA monitoring and evaluation | Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||||
6.9.1.4 | FS_OAM_eNPN_WoP#4 |   | ||||||||||
6.9.2 | Study on new aspects of EE for 5G networks Phase 2 |   | ||||||||||
6.9.2.1 | FS_EE5G_Ph2_WoP#1 | S5‑224090 | pCR 28.913 Add new Key Issue - EE KPI for V2X network slice | Huawei Technologies France | pCR | Agreement | Yes |
Yes
| approved | No | ||
S5‑224091 | pCR 28.913 Correcting vocabulary for CNF | Huawei Technologies France | pCR | Agreement | Yes |
Yes
| approved | No | ||||
S5‑224093 | pCR 28.913 Considering additional virtual resources usage to estimate VNF EC | Huawei Technologies France | pCR | Agreement | Yes |
Yes
| noted | No | ||||
S5‑224096 | pCR 28.913 Add new Key Issue - Customer accepts QoS degradation to save energy | Huawei Technologies France | pCR | Agreement | Yes |
Yes
| approved | No | ||||
S5‑224100 | LS to NGMN GFN and GSMA NG on Customer acceptation of QoS degradation to save energy | Huawei Technologies France | LS out | Approval | Yes |
Yes
| approved | No | ||||
6.9.2.2 | FS_EE5G_Ph2_WoP#2 |   | ||||||||||
6.9.3 | Study on Network and Service Operations for Energy Utilities |   | ||||||||||
6.9.3.1 | FS_NSOEU_WoP#1 |   | ||||||||||
6.9.3.2 | FS_NSOEU_WoP#2 |   | ||||||||||
6.9.3.3 | FS_NSOEU_WoP#3 | S5‑224026 | pCR TR 28.829 Business use case - MNO exposes Network Performance Monitoring | Vodafone GmbH | pCR | Approval | Yes |
Yes
| revised | No | S5‑224434 | |
S5‑224434 | pCR TR 28.829 Business use case - MNO exposes Network Performance Monitoring | Vodafone GmbH | pCR | Approval | Yes |
Yes
| approved | No | S5‑224026 | |||
S5‑224027 | pCR TR 28.829 Business use case - MNO exposes Network Service Alarm | Vodafone GmbH | pCR | Approval | Yes |
Yes
| revised | No | S5‑224435 | |||
S5‑224435 | pCR TR 28.829 Business use case - MNO exposes Network Service Alarm | Vodafone GmbH | pCR | Approval | Yes |
Yes
| approved | No | S5‑224027 | |||
6.9.3.4 | FS_NSOEU_WoP#4 |   | ||||||||||
6.9.3.5 | FS_NSOEU_WoP#5 |   | ||||||||||
6.9.3.6 | FS_NSOEU_WoP#6 |   | ||||||||||
6.9.3.7 | FS_NSOEU_WoP#7 |   | ||||||||||
6.9.3.8 | FS_NSOEU_WoP#8 |   | ||||||||||
6.9.3.9 | FS_NSOEU_WoP#9 |   | ||||||||||
6.9.3.10 | FS_NSOEU_WoP#10 |   | ||||||||||
6.9.3.11 | FS_NSOEU_WoP#11 |   | ||||||||||
6.9.3.12 | FS_NSOEU_WoP#12 |   | ||||||||||
6.9.3.13 | FS_NSOEU_WoP#13 |   | ||||||||||
6.9.4 | Study on Key Quality Indicators (KQIs)for 5G service experience |   | ||||||||||
6.9.4.1 | FS_KQI_5G_WoP#1 | S5‑224226 | DP on scenarios of 5G KQI for video uploading, remote controlling and cloud VR | Huawei | discussion | Endorsement | Yes |
Yes
| noted | No | ||
S5‑224227 | pCR TR 28.863 Issue#1 Difference of KPI, KQI and QoE | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224228 | pCR TR 28.863 Issue#3 Video uploading description | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224229 | pCR TR 28.863 Issue#4 Remote controlling description | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224230 | pCR TR 28.863 Issue#5 scenarios of cloud VR description | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224231 | pCR TR 28.863 Issue#3 requirements of KQIs for Video Uploading | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224232 | pCR TR 28.863 Issue#4 requirements of KQIs for remote controling | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224233 | pCR TR 28.863 Issue#5 requirements of KQIs for cloud VR | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
6.9.4.2 | FS_KQI_5G_WoP#2 | S5‑224234 | pCR TR 28.863 Key Issue#3 Solution of KQIs for Video Uploading | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||
6.9.4.3 | FS_KQI_5G_WoP#3 |   | ||||||||||
6.9.4.4 | FS_KQI_5G_WoP#4 |   | ||||||||||
6.9.4.5 | FS_KQI_5G_WoP#5 |   | ||||||||||
6.9.5 | Study on Deterministic Communication Service Assurance |   | ||||||||||
6.9.5.1 | FS_DCSA_WoP#1 |   | ||||||||||
6.9.5.2 | FS_DCSA_WoP#2 | S5‑224055 | pCR TR 28.865 Correct the inconsistence information in concept | Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||
S5‑224214 | pCR 28.865 Add solultion of service requirement modeling | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224215 | pCR 28.865 Add solultion of network preparation | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
6.9.5.3 | FS_DCSA_WoP#3 |   | ||||||||||
6.9.5.4 | FS_DCSA_WoP#4 | S5‑224216 | pCR 28.865 Update solution of service assurance for video monitoring | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||
S5‑224217 | pCR 28.865 Update solution of service assurance for PLC control | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
6.9.5.5 | FS_DCSA_WoP#5 |   | ||||||||||
6.9.6 | Study on management aspects of network slice management capability exposure |   | ||||||||||
6.9.6.1 | FS_NSCE_WoP#1 |   | ||||||||||
6.9.6.2 | FS_NSCE_WoP#2 |   | ||||||||||
6.9.6.3 | FS_NSCE_WoP#3 | S5‑224042 | pCR 28.824 Updating Solution for Network slice management capability exposure | Samsung R&D Institute India | pCR | Agreement | Yes |
Yes
| noted | No | ||
S5‑224043 | pCR 28.824 Updating use case for Network slice management capability exposure | Samsung R&D Institute India | pCR | Agreement | Yes |
Yes
| revised | No | S5‑224436 | |||
S5‑224436 | pCR 28.824 Updating use case for Network slice management capability exposure | Samsung R&D Institute India | pCR | Agreement | Yes |
Yes
| approved | No | S5‑224043 | |||
S5‑224081 | pCR 28.824 Add exposure governance for three CAPIF alternatives | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224082 | pCR 28.824 Possible solutions for CAPIF function entities implementation on management domain | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224085 | pCR 28.824 Update of solution 7.9 | Alibaba Group | pCR | Approval | Yes |
Yes
| revised | No | S5‑224443 | |||
S5‑224443 | pCR 28.824 Update of solution 7.9 | Alibaba Group | pCR | Approval | Yes |
Yes
| approved | No | S5‑224085 | |||
S5‑224086 | pCR 28.824 evaluation of solution 7.9 | Alibaba Group | pCR | Approval | Yes |
Yes
| revised | No | S5‑224442 | |||
S5‑224442 | pCR 28.824 evaluation of solution 7.9 | Alibaba Group | pCR | Approval | Yes |
Yes
| approved | No | S5‑224086 | |||
S5‑224119 | pCR 28.824 Requirements related to authorized external consumers | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑224437 | |||
S5‑224437 | pCR 28.824 Requirements related to authorized external consumers | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑224119 | |||
S5‑224120 | pCR 28.824 Editorial improvements | Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑224121 | pCR 28.824 Add solution based on CAPIF ServiceAPIDescription | Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑224286 | pCR TR 28.824 Divide clause 5.1.2 into issues and gaps | Ericsson LM, Deutsche Telekom | pCR | Approval | Yes |
Yes
| merged | No | S5‑224436 | |||
S5‑224287 | pCR TR 28.824 Potential solution for management capability exposure alternative 1 | Ericsson LM, Deutsche Telekom | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224288 | pCR TR 28.824 Rephrase or replace eMnS with exposed MnS | Ericsson LM, Deutsche Telekom | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑224289 | pCR TR 28.824 Update introduction to procedures 4.1.4.1 | Ericsson LM, Deutsche Telekom | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑224290 | pCR TR 28.824 Update procedure in clause 4.1.4.5 | Ericsson LM, Deutsche Telekom | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224291 | pCR TR 28.824 Update solution description for CAPIF alternative 2 and 3 | Ericsson LM, Deutsche Telekom | pCR | Approval | Yes |
Yes
| noted | No | ||||
6.9.6.4 | FS_NSCE_WoP#4 |   | ||||||||||
6.9.6.5 | FS_NSCE_WoP#5 |   | ||||||||||
6.9.7 | Study on alignment with ETSI MEC for Edge computing management |   | ||||||||||
6.9.7.1 | FS_MEC_ECM_WoP#1 | S5‑224122 | pCR 28.903 adding key issue for collocated management with MEC | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑224438 | |
S5‑224438 | pCR 28.903 adding key issue for collocated management with MEC | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑224122 | |||
S5‑224124 | pCR 28.903 adding key issue for application lifecycle management | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑224439 | |||
S5‑224439 | pCR 28.903 adding key issue for application lifecycle management | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑224124 | |||
6.9.7.2 | FS_MEC_ECM_WoP#2 | S5‑224123 | pCR 28.903 adding key issue for resource reservation | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑224440 | |
S5‑224440 | pCR 28.903 adding key issue for resource reservation | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑224123 | |||
S5‑224125 | pCR 28.903 adding key issue for deployment of application on containers | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224126 | pCR 28.903 adding background information for GSMA OPG | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑224441 | |||
S5‑224441 | pCR 28.903 adding background information for GSMA OPG | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑224126 | |||
6.10 | Latest draft TS/TR email approvals | S5‑224399 | Latest draft TS 28.317 | China Mobile | draft TS | Approval | No |
Yes
| withdrawn | Yes | ||
S5‑224400 | Latest draft TR 28.909 | China Mobile | draft TR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑224401 | Latest draft TR 28.910 | China Mobile | draft TR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑224402 | Latest draft TR 28.912 | Huawei | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S5‑224403 | Latest draft TR 28.836 | Ericsson | draft TR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑224404 | Latest draft TR 28.908 | Intel | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S5‑224405 | Latest draft TR 28.864 | China Telecom | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S5‑224406 | Latest draft TR 28.830 | China Mobile | draft TR | Approval | No |
Yes
| approved | No | ||||
S5‑224407 | Latest draft TR 28.838 | Intel | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S5‑224408 | Latest draft TR 28.925 | Huawei | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S5‑224409 | Latest draft TR 28.831 | Nokia | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S5‑224410 | Latest draft TR 28.832 | China Unicom | draft TR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑224411 | Latest draft TR 28.833 | China Mobile | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S5‑224412 | Latest draft TR 28.834 | China Mobile | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S5‑224413 | Latest draft TR 28.835 | China Unicom | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S5‑224414 | Latest draft TR 28.837 | Nokia | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S5‑224415 | Latest draft TR 28.818 | Ericsson | draft TR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑224416 | Latest draft TR 28.841 | China Unicom | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S5‑224417 | Latest draft TR 28.907 | Huawei | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S5‑224418 | Latest draft TR 28.913 | Huawei | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S5‑224419 | Latest draft TR 28.829 | Samsung | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S5‑224420 | Latest draft TR 28.863 | Huawei | draft TR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑224421 | Latest draft TR 28.865 | Huawei | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S5‑224422 | Latest draft TR 28.824 | Alibaba | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S5‑224423 | Latest draft TR 28.903 | Huawei | draft TR | Approval | Yes |
Yes
| approved | No | ||||
7 | Charging |   | ||||||||||
7.1 | Charging Plenary | S5‑224008 | CH agenda and time plan | WG vice Chair (Matrixx) | agenda | Yes |
Yes
| revised | No | S5‑224444 | ||
S5‑224444 | CH agenda and time plan | WG vice Chair (Matrixx) | agenda | - | Yes |
Yes
| noted | No | S5‑224008 | |||
S5‑224009 | Charging exec report | WG vice Chair (Matrixx) | report | Yes |
Yes
| noted | No | |||||
S5‑224245 | Reply LS on name of the interface for usage information collection | CATT | LS out | Approval | Yes |
Yes
| revised | No | S5‑224463 | |||
S5‑224318 | LS on name of the interface for usage information collection | C1-224296 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑224463 | Reply to: LS on name of the interface for usage information collection | CATT | LS out | approval | Yes |
Yes
| approved | No | S5‑224245 | |||
S5‑224320 | Reply LS on Enhancement on Charging Identifier Uniqueness Mechanism | C3-223669 | LS in | Yes |
Yes
| postponed | No | |||||
S5‑224462 | Draft CR Correction on the name of interface for usage information collection | CATT | draftCR | Approval | Yes |
Yes
| approved | No | ||||
7.2 | New Charging Work Item proposals | S5‑224157 | New SID on Time Sensitive Networking charging | Huawei | SID new | Agreement | Yes |
Yes
| revised | No | S5‑224479 | |
S5‑224479 | New SID on Time Sensitive Networking charging | Huawei | SID new | Agreement | Yes |
Yes
| agreed | No | S5‑224157 | |||
7.3 | Charging Maintenance and Rel-18 small Enhancements |   | ||||||||||
7.4 | Rel-18 Charging |   | ||||||||||
7.4.1 | Multimedia Messaging Service Charging using service-based interface |   | ||||||||||
7.5 | Charging studies |   | ||||||||||
7.5.1 | Study on charging aspects for enhancements of Network Slicing Phase 2 |   | ||||||||||
7.5.2 | Study on Nchf charging services phase 2 | S5‑224138 | Rel-18 pCR 28.826 Update the Reference | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | ||
S5‑224139 | Rel-18 pCR 28.826 Addition of Threshold based re-authorization triggers optimization | Huawei | pCR | Agreement | Yes |
Yes
| noted | No | ||||
S5‑224140 | Rel-18 pCR 28.826 Add the Solution for the clause 5.4 | Huawei | pCR | Agreement | Yes |
Yes
| noted | No | ||||
S5‑224141 | Rel-18 pCR 28.826 Add the QoS solution for CHF Rating | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑224464 | |||
S5‑224464 | Rel-18 pCR 28.826 Add the QoS solution for CHF Rating | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑224141 | |||
S5‑224142 | Rel-18 pCR 28.826 Add the General for NB mechanism enhancement | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑224465 | |||
S5‑224465 | Rel-18 pCR 28.826 Add the General for NB mechanism enhancement | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑224142 | |||
S5‑224143 | Rel-18 pCR 28.826 Add the Evaluation for clause 5.2 | Huawei | pCR | Agreement | Yes |
Yes
| noted | No | ||||
S5‑224144 | Rel-18 pCR 28.826 Add the Additional Information for CHF Rating | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑224466 | |||
S5‑224466 | Rel-18 pCR 28.826 Add the Additional Information for CHF Rating | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑224144 | |||
S5‑224191 | Rel-18 pCR 28.826 Adding solution in clause 5.1 using new trigger category | Ericsson LM | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224192 | Rel-18 pCR 28.826 Adding issue and solution to identifying non-blocking mode | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑224467 | |||
S5‑224467 | Rel-18 pCR 28.826 Adding issue and solution to identifying non-blocking mode | Ericsson LM | pCR | Approval | Yes |
Yes
| noted | No | S5‑224192 | |||
S5‑224193 | Rel-18 pCR 28.826 Adding solution for non-blocking mode change using PCF | Ericsson LM | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224194 | Rel-18 pCR 28.826 Correcting clause 5.5.5.2 | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑224195 | Rel-18 pCR 28.826 Correcting clause 5.2.5 | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑224481 | |||
S5‑224481 | Rel-18 pCR 28.826 Correcting clause 5.2.5 | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑224195 | |||
S5‑224196 | Rel-18 pCR 28.826 Adding use case and solution for cancel failed session charging | Ericsson LM | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224197 | Rel-18 pCR 28.826 Adding solution for cancel failed event | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑224468 | |||
S5‑224468 | Rel-18 pCR 28.826 Adding solution for cancel failed event | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑224197 | |||
S5‑224459 | Draft TR 28.826 | Ericsson | draft TR | Approval | Yes |
Yes
| approved | No | ||||
7.5.3 | Study on 5G roaming charging architecture for wholesale and retail scenarios | S5‑224145 | Rel-18 pCR 28.827 Correction on the clauses in the topic 7.1 and 7.2 | Huawei | pCR | Agreement | Yes |
Yes
| noted | No | ||
S5‑224146 | Rel-18 pCR 28.827 Clarification on the Roaming Charging Profile for HR | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑224469 | |||
S5‑224469 | Rel-18 pCR 28.827 Clarification on the Roaming Charging Profile for HR | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑224146 | |||
S5‑224147 | Rel-18 pCR 28.827 Add the solution of V-SMF connect to V-CHF with two charging sessions | Huawei | pCR | Agreement | Yes |
Yes
| noted | No | ||||
S5‑224148 | Rel-18 pCR 28.827 Add the solution of V-SMF connects to V-CHF with single charging session | Huawei | pCR | Agreement | Yes |
Yes
| noted | No | ||||
S5‑224149 | Rel-18 pCR 28.827 Add the solution for the roaming charging profile between V-CHF and H-CHF | Huawei | pCR | Agreement | Yes |
Yes
| noted | No | ||||
S5‑224150 | Rel-18 pCR 28.827 Add the solution for the charging session granularity | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑224470 | |||
S5‑224470 | Rel-18 pCR 28.827 Add the solution for the charging session granularity | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑224150 | |||
S5‑224151 | Rel-18 pCR 28.827 Add the solution for the charging information granularity | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑224471 | |||
S5‑224471 | Rel-18 pCR 28.827 Add the solution for the charging information granularity | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑224151 | |||
S5‑224152 | Rel-18 pCR 28.827 Add the new use case and solution for Roaming Charging Profile Update | Huawei | pCR | Agreement | Yes |
Yes
| noted | No | ||||
S5‑224153 | Rel-18 pCR 28.827 Add the key issues for the FBC negotiation | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑224472 | |||
S5‑224472 | Rel-18 pCR 28.827 Add the key issues for the FBC negotiation | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑224153 | |||
S5‑224154 | Rel-18 pCR 28.827 Add the key issue for QoS flow level of QBC triggers setting | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑224473 | |||
S5‑224473 | Rel-18 pCR 28.827 Add the key issue for QoS flow level of QBC triggers setting | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑224154 | |||
S5‑224155 | Rel-18 pCR 28.827 Add the key issue about the negotiation for FBC triggers and QBC triggers | Huawei | pCR | Agreement | Yes |
Yes
| merged | No | S5‑224473 | |||
S5‑224198 | Rel-18 pCR 28.827 Correcting message flows in clause 7.2.4 | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑224474 | |||
S5‑224474 | Rel-18 pCR 28.827 Correcting message flows in clause 7.2.4 | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑224198 | |||
S5‑224199 | Rel-18 pCR 28.827 Mapping requirement and issue mapping in clause 7.1 | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑224200 | Rel-18 pCR 28.827 Mapping requirement and issue mapping in clause 7.2 | Ericsson LM | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224201 | Rel-18 pCR 28.827 Mapping requirement and issue mapping in clause 7.3 | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑224202 | Rel-18 pCR 28.827 Mapping requirement and issue mapping in clause 7.4 | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑224203 | Rel-18 pCR 28.827 Mapping requirement and issue mapping in clause 7.5 | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑224204 | Rel-18 pCR 28.827 Mapping requirement and issue mapping in clause 7.6 | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑224205 | Rel-18 pCR 28.827 Adding solutions in clause 7.1 for VPLMN wholesale charging of HPLMN | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑224475 | |||
S5‑224475 | Rel-18 pCR 28.827 Adding solutions in clause 7.1 for VPLMN wholesale charging of HPLMN | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑224205 | |||
S5‑224206 | Rel-18 pCR 28.827 Adding solutions in clause 7.1 for roaming charging profile | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑224476 | |||
S5‑224476 | Rel-18 pCR 28.827 Adding solutions in clause 7.1 for roaming charging profile | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑224206 | |||
S5‑224207 | Rel-18 pCR 28.827 Adding solutions in clause 7.2 for trigger handling between vCHF and hCHF | Ericsson LM | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224208 | Rel-18 pCR 28.827 Adding solution in clause 7.2 using roaming charging profile for triggers | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑224477 | |||
S5‑224477 | Rel-18 pCR 28.827 Adding solution in clause 7.2 using roaming charging profile for triggers | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑224208 | |||
S5‑224209 | Rel-18 pCR 28.827 Adding use case in clause 7.4 where there is a reseller | Ericsson LM | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224210 | Rel-18 pCR 28.827 Adding use case in clause 7.5 for roaming where there is a reseller | Ericsson LM | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224211 | Rel-18 pCR 28.827 Adding solution in clause 7.6 for reconciliation | Ericsson LM | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑224212 | Rel-18 pCR 28.827 Adding solutions in clause 7.4 for CHF to CHF communication | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑224478 | |||
S5‑224478 | Rel-18 pCR 28.827 Adding solutions in clause 7.4 for CHF to CHF communication | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑224212 | |||
S5‑224460 | Draft TR 28.827 | Ericsson | draft TR | Approval | Yes |
Yes
| approved | No | ||||
7.5.4 | Study on Charging Aspects for Enhanced support of Non-Public Networks | S5‑224156 | Rel-18 pCR 28.828 The New Topic about access to PLMN services via SNPN | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑224480 | |
S5‑224480 | Rel-18 pCR 28.828 The New Topic about access to PLMN services via SNPN | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑224156 | |||
S5‑224187 | Rel-18 pCR 28.828 Addition of solution for end user charging for PNI-NPN network access and usage | China Mobile | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑224188 | Rel-18 pCR 28.828 Adding charging scenarios and key issues for PNI-NPN in topic 1 | China Mobile | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑224189 | Rel-18 pCR 28.828 Addition of solution for converged charging for number of UEs | China Mobile | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑224461 | Draft TR 28.828 | China Mobile | draft TR | Approval | Yes |
Yes
| approved | No | ||||
8 | Any Other Business |   | ||||||||||
9 | Closing of the meeting |   |