Tdoc List
2019-10-21 11:16
| TDoc | Title | Source | Type | For | Agenda | Avail | Treated | Decision | Wdrn | Replaced-by | Replaces |
|---|---|---|---|---|---|---|---|---|---|---|---|
| S5‑196000 | Agenda | WG Chairman | agenda |
2Approval of the agenda
| Yes |
Yes
| approved | No | |||
| S5‑196001 | IPR and legal declaration | WG Chairman | other |
3IPR and legal declaration
| Yes |
Yes
| revised | No | S5‑196541 | ||
| S5‑196002 | Report from last SA5 meeting | MCC | report |
4.1Last SA5 meeting report
| Yes |
Yes
| approved | No | |||
| S5‑196003 | Leaders meeting agenda | WG Chairman | agenda |
5.1Administrative issues at SA5 level
| Yes |
YesThe Chair announced that one of the changes in the structure would be the removal of the OAM SWG.
| noted | No | |||
| S5‑196004 | Leaders meeting minutes | WG Chairman | report |
5.1Administrative issues at SA5 level
| Yes |
Yes
| noted | No | |||
| S5‑196005 | SA5 Working Procedures | WG Chair | other |
5.1Administrative issues at SA5 level
| Yes |
YesIt introduces many changes. It was intended to be presented for information and to be approved in the following meeting.
| noted | No | |||
| S5‑196006 | SA5 Meeting Facility Requirements | WG Vice Chair (Nokia) | other |
5.1Administrative issues at SA5 level
| No |
Yes
| withdrawn | Yes | |||
| S5‑196007 | Process for management of draft TSs/TRs | WG Chairman | other |
5.1Administrative issues at SA5 level
| Yes |
Yes
| noted | No | |||
| S5‑196008 | CR Quality Check | MCC | other |
5.1Administrative issues at SA5 level
| Yes |
Yes
| noted | No | |||
| S5‑196009 | Status of email approvals | WG Chairman | other |
5.1Administrative issues at SA5 level
| No |
No
| reserved | No | |||
| S5‑196010 | SA5 Meeting Calendar | WG Chairman | other |
5.4SA5 meeting calendar
| Yes |
YesIt introduces the dates for 2021. The Chair asked for hosts for that year if the dates were agreed. He added that Taipei was a potential candidate, China and also Japan were other possibilities.
| noted | No | |||
| S5‑196011 | 3GPP SA5 Work Plan | MCC | other |
5.5Review of the Work Plan
| Yes |
Yes
| noted | No | |||
| S5‑196012 | Time Plan for OAM&P | WG Chair | other |
6.1OAM&P Plenary
| Yes |
Yes
| noted | No | |||
| S5‑196013 | OAM Executive Report | WG Vice Chair (Huawei) | report |
6.1OAM&P Plenary
| No |
Yes
| left for email approval | No | |||
| S5‑196014 | OAM&P action list | WG Vice Chair (Huawei) | other |
6.1OAM&P Plenary
| Yes |
Yes
| noted | No | |||
| S5‑196015 | SA5 status report at last SA meeting | WG Chairman | report |
4.2Last SA meeting report
| Yes |
Yes
| noted | No | |||
| S5‑196016 | SA5 results at last SA meeting | WG Chairman | report |
4.2Last SA meeting report
| Yes |
YesThe Chair pointed out that having more than one Rapporteur in a SID/WID should be deprecated, and that he had had discussions about this during SA ending in the agreement that in very rare cases there could be more than a Rapporteur. This would have to be followed from now on in SA5.
| noted | No | |||
| S5‑196017 | Minutes of OAM&P opening session | MCC | report |
6.1OAM&P Plenary
| No |
Yes
| withdrawn | Yes | |||
| S5‑196018 | Minutes of New Work Item proposals - OAM&P | MCC | report |
6.2New OAM&P Work Item proposals
| No |
Yes
| withdrawn | Yes | |||
| S5‑196019 | Minutes of OAM&P Maintenance and Rel-16 small Enhancements | MCC | report |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| No |
Yes
| withdrawn | Yes | |||
| S5‑196020 | Minutes of Management of QoE measurement collection | Rapporteur (Ericsson) | report |
6.4.1Management of QoE measurement collection
| Yes |
Yes
| noted | No | |||
| S5‑196021 | Minutes of Energy effciency of 5G | Rapporteur (ORANGE) | report |
6.4.2Energy Efficiency of 5G
| Yes |
Yes
| noted | No | |||
| S5‑196022 | Minutes of Network policy management for mobile networks based on NFV scenarios | Rapporteur (China Mobile) | report |
6.4.3Network policy management for mobile networks based on NFV scenarios
| Yes |
Yes
| noted | No | |||
| S5‑196023 | Minutes of Intent driven management service for mobile networks | Rapporteur (Huawei) | report |
6.4.4Intent driven management service for mobile networks
| Yes |
Yes
| noted | No | |||
| S5‑196024 | Minutes of Enhancement of performance assurance for 5G networks including network slicing | Rapporteur (Intel) | report |
6.4.5Enhancement of performance assurance for 5G networks including network slicing
| Yes |
Yes
| noted | No | |||
| S5‑196025 | Minutes of Discovery of management services in 5G | Rapporteur (Huawei) | report |
6.4.6Discovery of management services in 5G
| Yes |
Yes
| noted | No | |||
| S5‑196026 | Minutes of NRM enhancements | Rapporteur (Nokia) | report |
6.4.7NRM enhancements
| Yes |
Yes
| noted | No | |||
| S5‑196027 | Minutes of Trace Management in the context of Services Based Management Architecture | Rapporteur (Nokia) | report |
6.4.8Trace Management in the context of Services Based Management Architecture
| No |
Yes
| withdrawn | Yes | |||
| S5‑196028 | Minutes of Integration of ONAP and 3GPP 5G management framework | Rapporteur (AT&T)) | report |
6.4.9Integration of ONAP and 3GPP 5G management framework
| Yes |
Yes
| noted | No | |||
| S5‑196029 | Minutes of Closed loop SLS Assurance | Rapporteur (Ericsson) | report |
6.4.10Closed loop SLS Assurance
| Yes |
Yes
| revised | No | S5‑196844 | ||
| S5‑196030 | Minutes of Streaming trace reporting | Rapporteur (Nokia) | report |
6.4.11Streaming trace reporting
| Yes |
Yes
| noted | No | |||
| S5‑196031 | Minutes of KPI reporting | Rapporteur (ZTE) | report |
6.4.12KPI reporting
| Yes |
Yes
| noted | No | |||
| S5‑196032 | Minutes of Self-Organizing Networks (SON) for 5G networks | Rapporteur (Intel) | report |
6.4.13Self-Organizing Networks (SON) for 5G networks
| Yes |
Yes
| noted | No | |||
| S5‑196033 | Minutes of Enhancement of 3GPP management system for multiple tenant environment support | Rapporteur (Huawei) | report |
6.4.14Enhancement of 3GPP management system for multiple tenant environment support
| Yes |
Yes
| noted | No | |||
| S5‑196034 | Minutes of Management Aspects of 5G Service-Level Agreement | Rapporteur (China Mobile) | report |
6.4.15Management Aspects of 5G Service-Level Agreement
| No |
Yes
| withdrawn | Yes | |||
| S5‑196035 | Minutes of Study on protocol enhancement for real time communication | Rapporteur(Nokia) | report |
6.5.1Study on protocol enhancement for real time communication
| No |
Yes
| withdrawn | Yes | |||
| S5‑196036 | Minutes of Study on Self-Organizing Networks (SON) for 5G | Rapporteur (Intel) | report |
6.5.2Study on Self-Organizing Networks (SON) for 5G
| Yes |
Yes
| noted | No | |||
| S5‑196037 | Minutes of Study on non-public networks management | Rapporteur (Huawei) | report |
6.5.3Study on non-public networks management
| Yes |
Yes
| noted | No | |||
| S5‑196038 | Minutes of Study on management and orchestration aspects with integrated satellite components in a 5G network | Rapporteur (Thales) | report |
6.5.4Study on management and orchestration aspects with integrated satellite components in a 5G network
| Yes |
Yes
| noted | No | |||
| S5‑196039 | Minutes of Study on enhancement of Management Data Analytics Service | Rapporteur (Intel) | report |
6.5.5Study on enhancement of Management Data Analytics Service
| No |
Yes
| withdrawn | Yes | |||
| S5‑196040 | Minutes of Study on autonomous network levels | Rapporteur (China Mobile) | report |
6.5.6Study on autonomous network levels
| Yes |
Yes
| noted | No | |||
| S5‑196041 | CH Agenda and Time Plan | CH SWG Chair | agenda |
7.1Charging Plenary
| Yes |
Yes
| approved | No | |||
| S5‑196042 | CH Executive Report | CH SWG Chair | report |
7.1Charging Plenary
| Yes |
Yes
| noted | No | |||
| S5‑196043 | Double S1/NG discussion in relation to retainability | Nokia Solutions & Networks (I) | discussion | Endorsement |
6.4.5Enhancement of performance assurance for 5G networks including network slicing
| Yes |
Yes
| revised | No | S5‑196605 | |
| S5‑196044 | Add new Use case related to extended 5QI 1 QoS Flow establishment via Initial Context Setup into A30 | Nokia Solutions & Networks (I) | CR | Agreement |
6.4.5Enhancement of performance assurance for 5G networks including network slicing
| Yes |
Yes
| revised | No | S5‑196606 | |
| S5‑196045 | Add new measurements related to QoS Flow Setup via Initial Context Setup | Nokia Solutions & Networks (I) | CR | Agreement |
6.4.5Enhancement of performance assurance for 5G networks including network slicing
| Yes |
Yes
| revised | No | S5‑196607 | |
| S5‑196046 | Add new Use case related to QCI1 E-RAB establishment via Initial Context Setup into A2 | Nokia Solutions & Networks (I) | CR | Agreement |
6.4.5Enhancement of performance assurance for 5G networks including network slicing
| Yes |
Yes
| revised | No | S5‑196608 | |
| S5‑196047 | Add new Use case related to extended 5QI 1 QoS Flow Retainability monitoring into A30 | Nokia Solutions & Networks (I) | CR | Agreement |
6.4.5Enhancement of performance assurance for 5G networks including network slicing
| Yes |
Yes
| revised | No | S5‑196609 | |
| S5‑196048 | Rel-16 CR 28.532 RESTful CM notifications for integration with ONAP VES | AT&T, Deutsche Telekom, Orange | CR | Approval |
6.4.9Integration of ONAP and 3GPP 5G management framework
| Yes |
Yes
| revised | No | S5‑196822 | |
| S5‑196049 | Rel-16 CR 28.532 RESTful PM file-based notifications for integration with ONAP VES | AT&T, Deutsche Telekom, Orange | CR | Approval |
6.4.9Integration of ONAP and 3GPP 5G management framework
| Yes |
YesEricsson: "perf3GPP" has been used by ONAP for another purpose.
Orange: the perf3GPP domain does not exist in ONAP.
It was proposed to ask ONAP before agreeing on this CR.
| not pursued | No | ||
| S5‑196050 | Shadow TS for Heartbeat Stage 1 | AT&T, Deutsche Telekom, Orange | other | Agreement |
6.4.9Integration of ONAP and 3GPP 5G management framework
| Yes |
Yes
| revised | No | S5‑196706 | |
| S5‑196051 | Rel-16 CR 28.532 Heartbeat MnS | AT&T, Deutsche Telekom, Orange | CR | Approval |
6.4.9Integration of ONAP and 3GPP 5G management framework
| Yes |
YesHuawei: 12.x.1.1 is not configurable instead of not mapped.
Nokia had a similar contribution, tdoc 426 but for another specification (28.622).
Ericsson: why to define a new operation?
| merged | No | S5‑196789 | |
| S5‑196052 | Rel-16 CR 28.622 Configurable Heartbeat NRM fragment | AT&T, Deutsche Telekom, Orange | CR | Approval |
6.4.9Integration of ONAP and 3GPP 5G management framework
| Yes |
Yes
| merged | No | S5‑196789 | |
| S5‑196053 | pCR TS 28.310 Edithelp comments | Orange | pCR | Agreement |
6.4.2Energy Efficiency of 5G
| Yes |
Yes
| approved | No | ||
| S5‑196054 | LS to RAN3 on energy efficiency of 5G | Orange | LS out | Approval |
6.4.2Energy Efficiency of 5G
| Yes |
Yes
| revised | No | S5‑196771 | |
| S5‑196055 | Management and orchestration; Management Services for Communication Service Assurance; Requirements | Ericsson India Private Limited | draft TS |
6.4.10Closed loop SLS Assurance
| Yes |
Yes
| approved | No | |||
| S5‑196056 | Management and orchestration; Management Services for Communication Service Assurance; Stage 2 and stage 3 | Ericsson India Private Limited | draft TS |
6.4.10Closed loop SLS Assurance
| Yes |
Yes
| approved | No | |||
| S5‑196057 | New WID Charging Access Traffic Steering, Switching and Splitting in 5G system architecture | Nokia, Nokia Shanghai Bell | WID new |
7.2New Charging Work Item proposals
| Yes |
Yes
| revised | No | S5‑196542 | ||
| S5‑196058 | Rel-15 CR 32.255 Add the Service Specification information | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | ||
| S5‑196059 | Rel-15 CR 32.291 Add the Service Specification information | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196565 | |
| S5‑196060 | Rel-15 CR 32.298 Add the Service Specification information | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196567 | |
| S5‑196061 | Discussion paper on 5G QoS support | Huawei | discussion | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| noted | No | ||
| S5‑196062 | Rel-15 CR 32.255 Add the QoS Characteristics | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| not pursued | No | ||
| S5‑196063 | Rel-15 CR 32.291 Add the QoS Characteristics | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| not pursued | No | ||
| S5‑196064 | Rel-15 CR 32.255 Add the QNC support | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196569 | |
| S5‑196065 | Rel-15 CR 32.291 Add the QNC support | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196571 | |
| S5‑196066 | Rel-15 CR 32.291 Clarify the QoS change trigger | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196622 | |
| S5‑196067 | Rel-15 CR 32.298 Add the selection model in PDU session information | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| No |
Yes
| withdrawn | Yes | ||
| S5‑196068 | Rel-15 CR 32.255 correction of PCC rules description | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196624 | |
| S5‑196069 | Rel-15 CR 32.255 Correction of UPF ID in CHF CDR data | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | ||
| S5‑196070 | Rel-15 CR 32.290 Correction of notify response | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196626 | |
| S5‑196071 | Rel-15 CR 32.291 Correction of notify response | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196628 | |
| S5‑196072 | Rel-15 CR 32.291 Correction of ChargingDataResponse description | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196630 | |
| S5‑196073 | Rel-15 CR 32.291 Correction of Nchf_ConvergedCharging_Release operation | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196634 | |
| S5‑196074 | Rel-15 CR 32.255 Correction of reportTime | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196636 | |
| S5‑196075 | Rel-15 CR 32.298 Correct inconsistent CHF CDR parameter | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196637 | |
| S5‑196076 | Rel-15 CR 32.298 Add rating indicator and rating failure reason in CHF-CDR | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| not pursued | No | ||
| S5‑196077 | Rel-15 CR 32.255 Add the sponsor based charging | Huawei | CR | Discussion |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196639 | |
| S5‑196078 | Rel-15 32.255 Correction of Unit Count Inactivity Timer | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196676 | |
| S5‑196079 | Rel-15 32.298 Correction of ASN.1 NetworkFunctionName | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | ||
| S5‑196080 | Rel-15 CR 32.255 Add the Service Specification information | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| No |
Yes
| withdrawn | Yes | ||
| S5‑196081 | Rel-15 CR 32.291 Add the Service Specification information | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| No |
Yes
| withdrawn | Yes | ||
| S5‑196082 | Rel-15 CR 32.298 Add the Service Specification information | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| No |
Yes
| withdrawn | Yes | ||
| S5‑196083 | Discussion paper on 5G QoS support | Huawei | discussion | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| No |
Yes
| withdrawn | Yes | ||
| S5‑196084 | Rel-15 CR 32.255 Add the QoS Characteristics | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| No |
Yes
| withdrawn | Yes | ||
| S5‑196085 | Rel-15 CR 32.291 Add the QoS Characteristics | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| No |
Yes
| withdrawn | Yes | ||
| S5‑196086 | Rel-15 CR 32.255 Add the QNC support | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| No |
Yes
| withdrawn | Yes | ||
| S5‑196087 | Rel-15 CR 32.291 Add the QNC support | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| No |
Yes
| withdrawn | Yes | ||
| S5‑196088 | Rel-15 CR 32.291 Clarify the QoS change trigger | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| No |
Yes
| withdrawn | Yes | ||
| S5‑196089 | Rel-15 CR 32.298 Add the selection model in PDU session information | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| No |
Yes
| withdrawn | Yes | ||
| S5‑196090 | Rel-15 CR 32.255 correction of PCC rules description | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| No |
Yes
| withdrawn | Yes | ||
| S5‑196091 | Rel-15 CR 32.255 Correction of UPF ID in CHF CDR data | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| No |
Yes
| withdrawn | Yes | ||
| S5‑196092 | Rel-15 CR 32.290 Correction of notify response | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| No |
Yes
| withdrawn | Yes | ||
| S5‑196093 | Rel-15 CR 32.291 Correction of notify response | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| No |
Yes
| withdrawn | Yes | ||
| S5‑196094 | Rel-15 CR 32.291 Correction of ChargingDataResponse description | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| No |
Yes
| withdrawn | Yes | ||
| S5‑196095 | Rel-15 CR 32.291 Correction of Nchf_ConvergedCharging_Release operation | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| No |
Yes
| withdrawn | Yes | ||
| S5‑196096 | Rel-15 CR 32.255 Correction of reportTime | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| No |
Yes
| withdrawn | Yes | ||
| S5‑196097 | Rel-15 CR 32.298 Correct inconsistent CHF CDR parameter | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| No |
Yes
| withdrawn | Yes | ||
| S5‑196098 | Rel-15 CR 32.298 Add rating indicator and rating failure reason in CHF-CDR | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| No |
Yes
| withdrawn | Yes | ||
| S5‑196099 | Rel-15 CR 32.255 Add the sponsor based charging | Huawei | CR | Discussion |
7.3Charging Maintenance and Rel-16 small Enhancements
| No |
Yes
| withdrawn | Yes | ||
| S5‑196100 | Rel-15 32.255 Correction of Unit Count Inactivity Timer | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| No |
Yes
| withdrawn | Yes | ||
| S5‑196101 | Rel-15 32.298 Correction of ASN.1 NetworkFunctionName | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| No |
Yes
| withdrawn | Yes | ||
| S5‑196102 | Rel-15 32.298 Correction of ASN.1 AMFID | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196680 | |
| S5‑196103 | Rel-15 32.298 Correction of ASN.1 userLocationInformation | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196732 | |
| S5‑196104 | Rel-15 CR 32.291 Correction of subscriberIdentifier | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | ||
| S5‑196105 | Rel-15 CR 32.291 Correction on OpenAPI for usedunitcontainer | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| No |
Yes
| withdrawn | Yes | ||
| S5‑196106 | Rel-16 CR 32.255 Add the Service Specification information | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | ||
| S5‑196107 | Rel-16 CR 32.291 Add the Service Specification information | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196566 | |
| S5‑196108 | Rel-16 CR 32.298 Add the Service Specification information | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196568 | |
| S5‑196109 | Rel-16 CR 32.255 Add the QoS Characteristics | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196730 | |
| S5‑196110 | Rel-16 CR 32.291 Add the QoS Characteristics | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196731 | |
| S5‑196111 | Rel-16 CR 32.255 Add the QNC support | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196570 | |
| S5‑196112 | Rel-15 CR 32.291 Add the QNC support | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196621 | |
| S5‑196113 | Rel-15 CR 32.291 Clarify the QoS change trigger | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196623 | |
| S5‑196114 | Rel-16 CR 32.298 Add the selection model in PDU session information | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| No |
Yes
| withdrawn | Yes | ||
| S5‑196115 | Rel-16 CR 32.255 correction of PCC rules description | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196625 | |
| S5‑196116 | Rel-16 CR 32.255 Correction of UPF ID in CHF CDR data | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | ||
| S5‑196117 | Rel-16 CR 32.290 Correction of notify response | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196627 | |
| S5‑196118 | Rel-16 CR 32.291 Correction of notify response | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196629 | |
| S5‑196119 | Rel-16 CR 32.291 Correction of ChargingDataResponse description | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196631 | |
| S5‑196120 | Rel-16 CR 32.291 Correction of Nchf_ConvergedCharging_Release operation | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196635 | |
| S5‑196121 | Rel-16 CR 32.255 Correction of reportTime | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| not pursued | No | ||
| S5‑196122 | Rel-16 CR 32.298 Correct inconsistent CHF CDR parameter | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196638 | |
| S5‑196123 | Rel-16 CR 32.298 Add rating indicator and rating failure reason in CHF-CDR | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| not pursued | No | ||
| S5‑196124 | Rel-16 CR 32.255 Add the sponsor based charging | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196640 | |
| S5‑196125 | Rel-16 32.255 Correction of Unit Count Inactivity Timer | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196677 | |
| S5‑196126 | Rel-16 32.298 Correction of ASN.1 NetworkFunctionName | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | ||
| S5‑196127 | Rel-16 32.298 Correction of ASN.1 AMFID | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | ||
| S5‑196128 | Rel-16 32.298 Correction of ASN.1 userLocationInformation | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196733 | |
| S5‑196129 | Rel-16 CR 32.291 Correction of subscriberIdentifier | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | ||
| S5‑196130 | Rel-16 CR 32.291 Correction on OpenAPI for usedunitcontainer | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196689 | |
| S5‑196131 | Rel-16 pCR TR 32.845 Conclusion on Business to Consumer | Huawei | pCR | Agreement |
7.5.1Study on Charging Aspects of Network Slicing
| Yes |
Yes
| revised | No | S5‑196549 | |
| S5‑196132 | Rel-16 pCR TR 32.845 Conclusion on event based charging | Huawei | pCR | Agreement |
7.5.1Study on Charging Aspects of Network Slicing
| Yes |
Yes
| revised | No | S5‑196550 | |
| S5‑196133 | Rel-16 pCR TR 32.845 Conclusion on solution 1.6 | Huawei | pCR | Agreement |
7.5.1Study on Charging Aspects of Network Slicing
| Yes |
Yes
| revised | No | S5‑196551 | |
| S5‑196134 | Rel-16 pCR TR 32.845 Relocate the conclusion of topic 1 | Huawei | pCR | Agreement |
7.5.1Study on Charging Aspects of Network Slicing
| Yes |
Yes
| revised | No | S5‑196552 | |
| S5‑196135 | Rel-16 pCR TS 28.201 Update of the Skeleton | Huawei | pCR | Agreement |
7.4.6Network Slice Performance and Analytics Charging in 5G System
| Yes |
Yes
| revised | No | S5‑196554 | |
| S5‑196136 | Rel-16 pCR TS 28.201 Scope | Huawei | pCR | Agreement |
7.4.6Network Slice Performance and Analytics Charging in 5G System
| Yes |
Yes
| revised | No | S5‑196555 | |
| S5‑196137 | Rel-16 pCR TS 28.201 Add the terms | Huawei | pCR | Agreement |
7.4.6Network Slice Performance and Analytics Charging in 5G System
| Yes |
Yes
| approved | No | ||
| S5‑196138 | Rel-16 CR 32.260 IMS Charging architecture introduction | Huawei | CR | Agreement |
7.4.4IMS Charging in 5G System Architecture
| Yes |
Yes
| revised | No | S5‑196546 | |
| S5‑196139 | Rel-16 CR 32.255 Add charging requirement for I-SMF | Huawei | CR | Agreement |
7.4.5Charging aspects of Enhancing Topology of SMF and UPF in 5G Networks
| Yes |
Yes
| revised | No | S5‑196724 | |
| S5‑196140 | Rel-16 CR 32.255 Add charging principle for I-SMF | Huawei | CR | Agreement |
7.4.5Charging aspects of Enhancing Topology of SMF and UPF in 5G Networks
| Yes |
Yes
| revised | No | S5‑196725 | |
| S5‑196141 | Rel-16 CR 32.255 Add charging trigger conditions for I-SMF | Huawei | CR | Agreement |
7.4.5Charging aspects of Enhancing Topology of SMF and UPF in 5G Networks
| Yes |
Yes
| revised | No | S5‑196726 | |
| S5‑196142 | Rel-16 CR 32.255 Add I-SMF PDU session charging information | Huawei | CR | Agreement |
7.4.5Charging aspects of Enhancing Topology of SMF and UPF in 5G Networks
| Yes |
Yes
| revised | No | S5‑196727 | |
| S5‑196143 | Rel-16 pCR TR 32.845 Add content analysis on network slice charging | Huawei | pCR | Approval |
7.5.1Study on Charging Aspects of Network Slicing
| Yes |
Yes
| noted | No | ||
| S5‑196144 | Rel-16 CR 32.255 Add clarifications to lifetime of offline only charging | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| not pursued | No | ||
| S5‑196145 | Discussion paper on charging aspect related to network slice management | Huawei | discussion | Endorsement |
7.4.7Network Slice Management Charging in 5G System
| Yes |
Yes
| noted | No | ||
| S5‑196146 | Discussion on offline only charging service for event based charging | Huawei | discussion | Endorsement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| noted | No | ||
| S5‑196147 | Rel-16 CR 32.290 Add event based charging for offline only charging service | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| not pursued | No | ||
| S5‑196148 | Rel-16 CR 32.255 Correction of Interworking flow | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196690 | |
| S5‑196149 | Rel-16 CR 32.290 Add clarifications to failure handling | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196682 | |
| S5‑196150 | Rel-15 CR 32.290 Add clarifications to failure handling | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196681 | |
| S5‑196151 | Rel-15 CR TS 28.552 Correction of Registered subscribers measurement for AMF | China Mobile Com. Corporation | CR | Approval |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | ||
| S5‑196152 | Rel-16 CR TS 28.552 Correction of Registered subscribers measurement for AMF | China Mobile Com. Corporation | CR | Approval |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | ||
| S5‑196153 | Add missing (E-UTRAN) cell and freq relation | Ericsson Inc.,Huawei | CR | Approval |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
YesIt was clarified that it was not a removal of 4.1 but a replacement of the table. Revised to adress other comments from Intel and MCC.
| revised | No | S5‑196587 | S5‑193420 |
| S5‑196154 | Correct Import table | Ericsson Inc. | CR | Approval |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
YesHuawei: UPFFunction and ExternalUPFFunction are not correct. Nokia asked to remove three lines
Ericsson commented that this was contradicting agreements from previous meetings and that going back and forth should be avoided. It was agreed to include in the minutes: the imported information table will not include IOC that is in the same specification.
| revised | No | S5‑196602 | S5‑195543 |
| S5‑196155 | Correct NR TAC attribute property | Ericsson LM | CR | Approval |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| not treated | No | ||
| S5‑196156 | Add missing stage 3 CORBA/IDL solution | Ericsson LM | CR | Approval |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
YesHuawei asked about the replacement of the whole clause A.2.2. Nokia agreed that it was misleading since it seemed that it was removing all the clauses. Ericsson replied that it was just a change of format. This was not accepted since the CR showed a total removal and a replacement, technical changes were not visible.
| revised | No | S5‑196588 | |
| S5‑196157 | Correct conditional mandatory qualifications for SectorEquipmentFunction | Ericsson Inc. | CR | Approval |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
YesHuawei saw a misalignment between the change and the reason for change stated in the cover. 4.3.1.3 didn’t seem to be a misimplementation, it was a new change for them.
Ericsson clarified that the changes were missing in CR implementation, so these were agreed changes.
It was taken offline to verify that the changes were misimplementation. Nokia verified that the comment on the CR cover was not correct, so they couldn’t find the referred CR.
| not pursued | No | S5‑195545 | |
| S5‑196158 | Correct use of ProxyCellList | Ericsson LM | CR | Approval |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| No |
Yes
| withdrawn | Yes | ||
| S5‑196159 | Correct use of ProxyCellList | Ericsson LM | CR | Approval |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
YesIntel: ProxyCell is not for 5G?why?
Ericsson replied that this was coming from an old specification.
Nokia: changes in the first line of attribute constrainst is addressed in 157 and not in here. Why is the change split in this way? Ericsson replied that the difference was a misimplementation in one CR and new content in the other. It was pointed out that there was a clash with the other CR, since it was fixing a text that was removed in another CR.
| revised | No | S5‑196596 | |
| S5‑196160 | Correct Import table | Ericsson Inc. | CR | Approval |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196603 | S5‑195544 |
| S5‑196161 | Rel-16 pCR TR 32.845 Correction on the editorial Comments | Huawei | pCR |
7.5.1Study on Charging Aspects of Network Slicing
| Yes |
Yes
| revised | No | S5‑196553 | ||
| S5‑196162 | Rel-15 CR TS 28.552 Add Registered subscribers related measurements for AMF | China Mobile Com. Corporation | CR | Approval |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
YesEricsson: there is no use case for this document.
Nokia: registered subscribers should not be measured in AMF. This is also an issue for the case when we have several AMFs.
MCC commented that it was not possible to add features/cat-B in release 15 anymore. The following document would be the correct way to add the measurements in release 16.
| not pursued | No | ||
| S5‑196163 | Rel-16 CR TS 28.552 Add Registered subscribers related measurements for AMF | China Mobile Com. Corporation | CR | Approval |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196585 | |
| S5‑196164 | Rel-15 CR TS 28.552 Add Unregistered subscribers measurements for UDM | China Mobile Com. Corporation | CR | Approval |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
YesSame as above, not valid for Release 15.
| not pursued | No | ||
| S5‑196165 | Rel-16 CR TS 28.552 Add Unregistered subscribers measurements for UDM | China Mobile Com. Corporation | CR | Approval |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
YesIntel suggested to restructure the clauses.
Nokia: what is the value for the operator for having both min and max numbers of unregistered subscribers?
MCC also commented that the WID code should be for Release 16. Nokia added that these should be intended for another agenda item.
| revised | No | S5‑196586 | |
| S5‑196166 | Discussion paper on charging aspect for network slicing | Huawei Telecommunication India | discussion | Endorsement |
7.4.6Network Slice Performance and Analytics Charging in 5G System
| Yes |
Yes
| noted | No | ||
| S5‑196167 | NWI on Charging for 5WWC | Huawei Telecommunication India | WID new | Agreement |
7.2New Charging Work Item proposals
| Yes |
Yes
| revised | No | S5‑196543 | |
| S5‑196168 | SA5 Summary of OAM WIs/SIs and Work Plan | WG Vice Chair (Huawei) | other | Information |
6.1OAM&P Plenary
| Yes |
YesThe Chair asked the group to endorse slide 3 and the last slide in order to align with the SA time plan and influence other groups like SA2.
Robert (Ericsson) found this useful and agreed with it. He asked for clickable references for the SP documents.
ORANGE: Enhanced IMS for 5GC integration, which is under CT responsibility, could be related to SA5 work. Zou Lan replied that the list wasn't exhaustive and it needed to be completed.
| revised | No | S5‑196579 | |
| S5‑196169 | Rel-16 CR TS 28.554 Update the template of KPI definition for TS 28.554 | Huawei | CR | Approval |
6.4.12KPI reporting
| Yes |
Yes
| revised | No | S5‑196793 | |
| S5‑196170 | pCR TS 28.406 Add introduction | Nanjing Ericsson Panda Com Ltd | pCR | Approval |
6.4.1Management of QoE measurement collection
| Yes |
Yes
| approved | No | ||
| S5‑196171 | pCR TS 28.406 Add scope and reference | Nanjing Ericsson Panda Com Ltd | pCR | Approval |
6.4.1Management of QoE measurement collection
| Yes |
Yes
| approved | No | ||
| S5‑196172 | Overview of the 5G specification structure | HUAWEI TECHNOLOGIES Co. Ltd. | discussion |
6.1OAM&P Plenary
| Yes |
YesSamsung supported this document and found it very useful to have.
Robert (Ericsson): what do we include in 5G? Connections in E-UTRAN should be added as well? There are also missing documents (e.g. Trace) but it’s a good start.
Edwin (Ericsson) had issues with having the three stages together. The positioning of some boxes could be tricky (positioning of new MnS where to?).
Zou Lan asked everybody to contribute in order to bring an updated version for the next meeting.
| noted | No | |||
| S5‑196173 | Draft LS reply from 3GPP SA5 to NGMN on 5G End-to-End Architecture Framework | HUAWEI TECHNOLOGIES Co. Ltd. | LS out |
5.3Liaison statements at SA5 level
| Yes |
YesThe Chair pointed out that the coordination with NGMN was more company-based than official. Robert (Ericsson) commented that there was no coordination and that the mapping had not been discussed or agreed in SA5.
Zou Lan (Huawei) agreed with Robert.
Anatoly (Nokia) also supported Ericsson and commented that the language in the LS of NGMN was not 3GPP SA5 language, so this would have be discussed before sending the LS reply.
Intel: don’t refer to the release as we are between releases now.
| revised | No | S5‑196572 | ||
| S5‑196174 | TS 28.312_000 | HUAWEI TECHNOLOGIES Co. Ltd. | draft TS |
6.4.4Intent driven management service for mobile networks
| Yes |
Yes
| approved | No | |||
| S5‑196175 | pCR 28.861 remove duplicated clause in Multi-aspect / multi-domain resource optimization use case | Nokia | pCR | Approval |
6.5.2Study on Self-Organizing Networks (SON) for 5G
| Yes |
Yes
| not treated | No | ||
| S5‑196176 | Allow for service-centric load redistribution to concurrently optimize load distribution and service performance | Nokia | pCR | Approval |
6.5.2Study on Self-Organizing Networks (SON) for 5G
| Yes |
Yes
| revised | No | S5‑196818 | |
| S5‑196177 | Extend the usecase to allow for PCI optimization in multi-layer scenarios | Nokia | pCR | Approval |
6.5.2Study on Self-Organizing Networks (SON) for 5G
| Yes |
Yes
| revised | No | S5‑196820 | |
| S5‑196178 | Update cell neighbour relationship indication | Nokia | pCR | Approval |
6.5.2Study on Self-Organizing Networks (SON) for 5G
| Yes |
Yes
| not treated | No | ||
| S5‑196179 | Update use case on Automatic Cell Clustering for Energy Management | Nokia | pCR | Approval |
6.5.2Study on Self-Organizing Networks (SON) for 5G
| Yes |
Yes
| withdrawn | Yes | ||
| S5‑196180 | Update ANR optimization use case to allow for use of deployment data | Nokia | pCR | Approval |
6.5.2Study on Self-Organizing Networks (SON) for 5G
| Yes |
Yes
| not treated | No | ||
| S5‑196181 | Update SON coordination use case | Nokia | pCR | Approval |
6.5.2Study on Self-Organizing Networks (SON) for 5G
| Yes |
Yes
| not treated | No | ||
| S5‑196182 | Add requirement for NR indication to ANR optimization usecase | Nokia | pCR | Approval |
6.5.2Study on Self-Organizing Networks (SON) for 5G
| Yes |
Yes
| not treated | No | ||
| S5‑196183 | Add requirements for supporting Multi-layer deployment scenarios to PCI Configuration use case | Nokia | pCR | Approval |
6.5.2Study on Self-Organizing Networks (SON) for 5G
| Yes |
Yes
| not treated | No | ||
| S5‑196184 | Update requirements for Load Balancing Optimization to allow for service centric resource optimization | Nokia | pCR | Approval |
6.5.2Study on Self-Organizing Networks (SON) for 5G
| Yes |
Yes
| revised | No | S5‑196846 | |
| S5‑196185 | Update Intra-RAT energy saving scenario with distributed decision-making | Nokia | pCR | Approval |
6.4.2Energy Efficiency of 5G
| Yes |
Yes
| revised | No | S5‑196646 | |
| S5‑196186 | Add Rollback operation to intent Lifecycle management | Nokia | pCR | Approval |
6.4.4Intent driven management service for mobile networks
| Yes |
Yes
| revised | No | S5‑196650 | |
| S5‑196187 | Extensions to PCF and UPF IOCs for support of TSC (Time Sensitive Communication) | Nokia | CR | Approval |
6.4.7NRM enhancements
| Yes |
Yes
| revised | No | S5‑196699 | |
| S5‑196188 | Rel-15 CR TS 28.531 fix inconsistencies in feasibility check use cases and requirements | Nokia | CR | Approval |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
YesNokia clarified that the feasibility check was different from instantation. The use case is an instantiation instead of feasibility.
Samsung: feasibility check is for now, not for the future as it appears here.
Comments from Huawei and Ericsson had to be taken offline.
| revised | No | S5‑196787 | |
| S5‑196189 | Rel-16 CR TS 28.531 fix inconsistencies in feasibility check use cases and requirements | Nokia | CR | Approval |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196788 | |
| S5‑196190 | pCR 28.861 cleanup | Intel Corporation (UK) Ltd | pCR | Approval |
6.5.2Study on Self-Organizing Networks (SON) for 5G
| Yes |
Yes
| not treated | No | ||
| S5‑196191 | pCR 28.310 solution for energy saving | Intel Corporation (UK) Ltd | pCR | Approval |
6.4.2Energy Efficiency of 5G
| Yes |
Yes
| revised | No | S5‑196769 | |
| S5‑196192 | draft TS 28313-000 | Intel Corporation (UK) Ltd | draft TS | Approval |
6.4.13Self-Organizing Networks (SON) for 5G networks
| Yes |
Yes
| revised | No | S5‑196671 | |
| S5‑196193 | dtaft TS 28544-000 | Intel Corporation (UK) Ltd | draft TS | Approval |
6.4.13Self-Organizing Networks (SON) for 5G networks
| Yes |
Yes
| noted | No | ||
| S5‑196194 | pCR 28.313 skeleton | Intel Corporation (UK) Ltd | pCR | Approval |
6.4.13Self-Organizing Networks (SON) for 5G networks
| Yes |
Yes
| revised | No | S5‑196672 | |
| S5‑196195 | pCR 28.544 skeleton | Intel Corporation (UK) Ltd | pCR | Approval |
6.4.13Self-Organizing Networks (SON) for 5G networks
| Yes |
Yes
| noted | No | ||
| S5‑196196 | pCR 28.313 introduction and scope | Intel Corporation (UK) Ltd | pCR | Approval |
6.4.13Self-Organizing Networks (SON) for 5G networks
| Yes |
Yes
| revised | No | S5‑196674 | |
| S5‑196197 | pCR 28.544 introduction and scope | Intel Corporation (UK) Ltd | pCR |
6.4.13Self-Organizing Networks (SON) for 5G networks
| Yes |
Yes
| noted | No | |||
| S5‑196198 | pCR 28.313 concepts | Intel Corporation (UK) Ltd | pCR | Approval |
6.4.13Self-Organizing Networks (SON) for 5G networks
| Yes |
Yes
| revised | No | S5‑196675 | |
| S5‑196199 | pCR 28.313 RACH optimization use case | Intel Corporation (UK) Ltd | pCR | Approval |
6.4.13Self-Organizing Networks (SON) for 5G networks
| Yes |
Yes
| revised | No | S5‑196696 | |
| S5‑196200 | pCR 28.313 RACH optimization use case | Intel Corporation (UK) Ltd | pCR | Approval |
6.4.13Self-Organizing Networks (SON) for 5G networks
| No |
Yes
| withdrawn | Yes | ||
| S5‑196201 | pCR 28.313 RACH optimization procedure | Intel Corporation (UK) Ltd | pCR | Approval |
6.4.13Self-Organizing Networks (SON) for 5G networks
| Yes |
Yes
| revised | No | S5‑196697 | |
| S5‑196202 | pCR 28.313 RACH optimization information | Intel Corporation (UK) Ltd | pCR | Approval |
6.4.13Self-Organizing Networks (SON) for 5G networks
| Yes |
Yes
| revised | No | S5‑196698 | |
| S5‑196203 | pCR 28.313 MRO use case | Intel Corporation (UK) Ltd | pCR | Approval |
6.4.13Self-Organizing Networks (SON) for 5G networks
| Yes |
Yes
| revised | No | S5‑196746 | |
| S5‑196204 | pCR 28.313 MRO procedure | Intel Corporation (UK) Ltd | pCR | Approval |
6.4.13Self-Organizing Networks (SON) for 5G networks
| Yes |
Yes
| revised | No | S5‑196747 | |
| S5‑196205 | pCR 28.313 MRO information | Intel Corporation (UK) Ltd | pCR | Approval |
6.4.13Self-Organizing Networks (SON) for 5G networks
| Yes |
Yes
| revised | No | S5‑196749 | |
| S5‑196206 | pCR 28.812 Add intent driven coverage optimization scenario | Huawei | pCR | Approval |
6.4.4Intent driven management service for mobile networks
| Yes |
Yes
| revised | No | S5‑196651 | |
| S5‑196207 | pCR 28.812 Update Figures | Huawei | pCR | Approval |
6.4.4Intent driven management service for mobile networks
| Yes |
Yes
| approved | No | ||
| S5‑196208 | pCR 28.812 Add solution for Intent driven NSI performance assurance scenario | Huawei | pCR | Approval |
6.4.4Intent driven management service for mobile networks
| Yes |
Yes
| revised | No | S5‑196670 | |
| S5‑196209 | pCR 28.812 Add potential stage 3 solution for intent driven MnS | Huawei | pCR | Approval |
6.4.4Intent driven management service for mobile networks
| Yes |
Yes
| noted | No | ||
| S5‑196210 | pCR 28.812 Add the description of MnS component type C in the concept | Huawei | pCR | Approval |
6.4.4Intent driven management service for mobile networks
| Yes |
Yes
| revised | No | S5‑196653 | |
| S5‑196211 | pCR 28.812 Add the relation between IDMS and SON | Huawei | pCR | Approval |
6.4.4Intent driven management service for mobile networks
| Yes |
Yes
| revised | No | S5‑196654 | |
| S5‑196212 | pCR 28.812 Update Intent Driven Object | Huawei | pCR | Approval |
6.4.4Intent driven management service for mobile networks
| Yes |
Yes
| revised | No | S5‑196666 | |
| S5‑196213 | pCR 28.312 Add skeleton | Huawei | pCR | Approval |
6.4.4Intent driven management service for mobile networks
| Yes |
Yes
| noted | No | ||
| S5‑196214 | pCR 28.312 Add Scope | Huawei | pCR | Approval |
6.4.4Intent driven management service for mobile networks
| Yes |
Yes
| noted | No | ||
| S5‑196215 | pCR 28.312 Add definition and concept of intent | Huawei | pCR | Approval |
6.4.4Intent driven management service for mobile networks
| Yes |
Yes
| noted | No | ||
| S5‑196216 | pCR 28.312 Add concept of intent-driven MnS | Huawei | pCR | Approval |
6.4.4Intent driven management service for mobile networks
| Yes |
Yes
| noted | No | ||
| S5‑196217 | pCR 28.312 Add concept of intent-driven closed-loop | Huawei | pCR | Approval |
6.4.4Intent driven management service for mobile networks
| Yes |
Yes
| noted | No | ||
| S5‑196218 | Rel-16 CR TS 28.530 Clean up for incosistence | Huawei | CR | Agreement |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196781 | |
| S5‑196219 | Rel-16 CR TS 28.531 Clean up for incosistence | Huawei | CR | Agreement |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
YesEricsson didn’t understand the change. Huawei replied that this was coming from another TS. Ericsson commented that there were other general descriptions in this TS and it wasn’t OK to have just another one. Nokia also had some issues and this had to be taken offline.
| revised | No | S5‑196782 | |
| S5‑196220 | Rel-15 CR TS 28.541 Correct the parameter sNSSAIList | Huawei | CR | Agreement |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
YesNokia didn't understand the removal of NSSAI list and they objected to the changes, combining two lists into one.
Ericsson and Deutsche Telekom didn't support this either.
This had to be taken offline.
| revised | No | S5‑196597 | |
| S5‑196221 | Rel-16 CR TS 28.541 Correct the parameter sNSSAIList | Huawei | CR | Agreement |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
YesKept it open depending on the discussions on the previous CR.
| not pursued | No | ||
| S5‑196222 | Rel-15 CR TS 28.541 Update on RRMPolicy | Huawei | CR | Agreement |
6.4.7NRM enhancements
| Yes |
Yes
| not pursued | No | ||
| S5‑196223 | Rel-16 CR TS 28.541 Update on RRMPolicy | Huawei | CR | Agreement |
6.4.7NRM enhancements
| Yes |
Yes
| not pursued | No | ||
| S5‑196224 | Rel-15 CR TS 28.659 Update XML solution set to support EUTRAN frequency relation | Huawei | CR | Agreement |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
YesNokia: 153 changes stage 2. Is this aligning with that? What is the relation with 156? Huawei replied that 156 + 224 are two parts of stage 3.
Kept open until stage 2 (tdco 587) was agreed.
| agreed | No | ||
| S5‑196225 | Rel-16 CR TS 28.659 Update XML solution set to support EUTRAN frequency relation | Huawei | CR | Agreement |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
YesKept open until stage 2 was agreed.
| agreed | No | ||
| S5‑196226 | Rel-15 CR TS 28.623 Correct XML Solution Set for generic NRM | Huawei | CR | Agreement |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
YesIntel: this CR depends on other contributions. If those are agreed this CR would need to be changed.
It was commented that stage 2 CRs without a stage 3 could not be agreed due to their dependency. MCC clarified that the stage 2 CRs without a stage 3 equivalent could be just postponed for the next meeting when the stage 3 CRs were available. The "conditionally agreed" status could also be used for the stage 2 CRs as well.
| agreed | No | ||
| S5‑196227 | Rel-15 CR TS 28.532 Correct provisioning management service | Huawei | CR | Agreement |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
YesOverlapping with 316.
Concerns of Nokia about the table
| revised | No | S5‑196758 | |
| S5‑196228 | Rel-16 CR TS 28.532 Correct provisioning management service | Huawei | CR | Agreement |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196759 | |
| S5‑196229 | Rel-15 CR TS 28.532 Correct fault supervision management service | Huawei | CR | Agreement |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
YesOrange: nothing on the stage 3 changes in the cover page.
Ericsson and Nokia suggested some other editorial changes.
| revised | No | S5‑196760 | |
| S5‑196230 | Rel-16 CR TS 28.532 Correct fault supervision management service | Huawei | CR | Agreement |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196761 | |
| S5‑196231 | Rel-15 CR TS 28.533 Update of Management service description and diagram | Huawei | CR | Agreement |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
YesNokia: the note contradicts the existing annexes. Don’t change the figure title. This was taken offline.
| revised | No | S5‑196762 | |
| S5‑196232 | Rel-16 CR TS 28.533 Update of Management service description and diagram | Huawei | CR | Agreement |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196763 | |
| S5‑196233 | Rel-15 CR TS 28.533 Add deployment scenario | Huawei | CR | Agreement |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
YesNokia: we don’t need normative deployment scenarios in this specification. This was rejected to be part of an informative annex before.
Ericsson supported to have examples in the annex, but not like in this document.
| not pursued | No | ||
| S5‑196234 | Rel-16 CR TS 28.533 Add deployment scenario | Huawei | CR | Agreement |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| not pursued | No | ||
| S5‑196235 | Rel-16 CR TS 28.541 Correct XML Solution Set for NR | Huawei | CR | Agreement |
6.4.7NRM enhancements
| Yes |
Yes
| revised | No | S5‑196847 | |
| S5‑196236 | Rel-16 CR TS 28.541 Correct Network slice NRM | Huawei,Ericsson | CR | Agreement |
6.4.7NRM enhancements
| Yes |
Yes
| revised | No | S5‑196849 | |
| S5‑196237 | Rel-16 CR TS 28.623 Correct XML Solution Set for generic NRM | Huawei | CR | Agreement |
6.4.7NRM enhancements
| Yes |
Yes
| revised | No | S5‑196848 | |
| S5‑196238 | Rel-16 CR TS 28.532 Add RESTful HTTP-based solution set of file-based performance assurance for integration with ONAP VES | Huawei | CR | Agreement |
6.4.9Integration of ONAP and 3GPP 5G management framework
| Yes |
Yes
| withdrawn | Yes | ||
| S5‑196239 | Rel-16 CR TS 28.532 Add Netconf-based solution set of provisioning MnS | Huawei | CR | Agreement |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
YesOrange: not relevant to ONAP only, move it to 6.3.
| merged | No | S5‑196791 | |
| S5‑196240 | Rel-16 CR TS 28.533 Update Clause A.7 Utilization of management data analystic services | Huawei | CR | Agreement |
6.4.10Closed loop SLS Assurance
| Yes |
Yes
| merged | No | S5‑196850 | |
| S5‑196241 | Correct NR TAC attribute property | Ericsson LM | CR | Approval |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| not treated | No | ||
| S5‑196242 | To sync up with Rel-15 stage 2 (on NR NRM) | Ericsson LM | CR | Approval |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| No |
Yes
| withdrawn | Yes | ||
| S5‑196243 | To syn up with v1540 stage 2 | Ericsson Inc. | CR | Approval |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
YesEricsson clarified that the corrections for Release 15 had been approved in the previous meeting already and that this correction was missing.
Huawei: clause 4.4.1 is not aligned with release 15. There was no change like this in there.
Intel: there seems to be some overlap with 153. Ericsson: it's a dependency, not an overlap. Intel added that this dependency should have been stated in the cover. This was agreed.
| revised | No | S5‑196591 | S5‑195412 |
| S5‑196244 | Rel-16 pCR TS 28.535 Add the description of data analytics utilization in closed loop SLA assurance | HUAWEI TECHNOLOGIES Co. Ltd. | pCR | Approval |
6.4.10Closed loop SLS Assurance
| Yes |
Yes
| noted | No | ||
| S5‑196245 | pCR TR 28.807 Roles related to NPN management | TELEFONICA S.A. | pCR | Approval |
6.5.3Study on non-public networks management
| Yes |
Yes
| revised | No | S5‑196713 | |
| S5‑196246 | Rel-16 pCR 32.256 Update triggers description | Nokia, Nokia Shanghai Bell | pCR | Approval |
7.4.3Charging AMF in 5G System Architecture Phase 1
| Yes |
Yes
| revised | No | S5‑196557 | |
| S5‑196247 | Rel-16 pCR 32.256 Solve Editor's Note for UE Presence in Presence Reporting Area (PRA) | Nokia, Nokia Shanghai Bell | pCR | Approval |
7.4.3Charging AMF in 5G System Architecture Phase 1
| Yes |
Yes
| revised | No | S5‑196558 | |
| S5‑196248 | Rel-16 pCR 32.256 Introduce CDRs generation for ECUR | Nokia, Nokia Shanghai Bell | pCR | Approval |
7.4.3Charging AMF in 5G System Architecture Phase 1
| Yes |
Yes
| approved | No | ||
| S5‑196249 | Rel-16 pCR 32.256 Introduce Roaming | Nokia, Nokia Shanghai Bell | pCR | Approval |
7.4.3Charging AMF in 5G System Architecture Phase 1
| Yes |
Yes
| revised | No | S5‑196559 | |
| S5‑196250 | Rel-16 pCR 32.256 Update message content | Nokia, Nokia Shanghai Bell | pCR | Approval |
7.4.3Charging AMF in 5G System Architecture Phase 1
| Yes |
Yes
| revised | No | S5‑196560 | |
| S5‑196251 | Rel-16 pCR 32.256 Add Detailed message format | Nokia, Nokia Shanghai Bell | pCR | Approval |
7.4.3Charging AMF in 5G System Architecture Phase 1
| Yes |
Yes
| revised | No | S5‑196561 | |
| S5‑196252 | Rel-16 pCR 32.256 Introduce CHF CDR description for AMF | Nokia, Nokia Shanghai Bell | pCR | Approval |
7.4.3Charging AMF in 5G System Architecture Phase 1
| Yes |
Yes
| revised | No | S5‑196562 | |
| S5‑196253 | Rel-16 CR 32.291 Introduce AMF in Nchf Converged Charging | Nokia, Nokia Shanghai Bell | CR | Agreement |
7.4.3Charging AMF in 5G System Architecture Phase 1
| Yes |
Yes
| postponed | No | ||
| S5‑196254 | Rel-15 CR 32.274 Addition of Post Event Charging flows | Nokia, Nokia Shanghai Bell | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196683 | |
| S5‑196255 | Rel-15 CR 32.274 Correction of message content for Post Event Charging | Nokia, Nokia Shanghai Bell | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | ||
| S5‑196256 | Rel-15 CR 32.274 Correction of Service Specification Information | Nokia, Nokia Shanghai Bell | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | ||
| S5‑196257 | Rel-16 CR 32.291 Add Retransmission IE for alignment with TS 32.290 | Nokia, Nokia Shanghai Bell | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196691 | |
| S5‑196258 | Rel-15 CR 32.274 Clarify CHF selection via NRF and roaming | Nokia, Nokia Shanghai Bell | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196684 | |
| S5‑196259 | Rel-15 CR 32.274 Correction of Multiple Unit Information | Nokia, Nokia Shanghai Bell | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196685 | |
| S5‑196260 | Rel-15 CR 32.291 Correction InvocationResult description and binding | Nokia, Nokia Shanghai Bell | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196686 | |
| S5‑196261 | Rel-16 CR 32.291 Correction InvocationResult description and binding | Nokia, Nokia Shanghai Bell | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196687 | |
| S5‑196262 | Rel-16 CR 28.623 Introduce Stage 3 for configurable heartbeat | AT&T, Deutsche Telekom, Orange | CR | Approval |
6.4.9Integration of ONAP and 3GPP 5G management framework
| Yes |
Yes
| not pursued | No | ||
| S5‑196263 | Rel-16 CR TS 28.541 Correction of the duplicated IOC NSSFFunction in daigram | CATT | CR | Approval |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | ||
| S5‑196264 | Rel-15 CR TS 28.541 Correction of the duplicated IOC NSSFFunction in daigram | CATT | CR | Approval |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | ||
| S5‑196265 | Rel-16 CR TS 28.541 Correction of the duplicated IOC NSSFFunction in daigram | CATT | CR | Approval |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
YesCATT clarified that this was a mirror although the title of the CR is different from the
| agreed | No | ||
| S5‑196266 | Rel-15 CR TS 28.541 Correction of the wrong IOC names in transport view of NWDAF and NSSF NRM | CATT | CR | Approval |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | ||
| S5‑196267 | pCR 28.535 Add analytics scenario introduction | HUAWEI TECHNOLOGIES Co. Ltd. | pCR |
6.5.5Study on enhancement of Management Data Analytics Service
| Yes |
Yes
| not treated | No | |||
| S5‑196268 | pCR 28.535 on MDAS assisted slice resource allocation | HUAWEI TECHNOLOGIES Co. Ltd. | pCR |
6.5.5Study on enhancement of Management Data Analytics Service
| Yes |
Yes
| not treated | No | |||
| S5‑196269 | pCR 28.535 on MDAS assisted E2E latency assurance | HUAWEI TECHNOLOGIES Co. Ltd. | pCR |
6.5.5Study on enhancement of Management Data Analytics Service
| Yes |
Yes
| not treated | No | |||
| S5‑196270 | pCR 28.535 on MDAS assisted SLS translation | HUAWEI TECHNOLOGIES Co. Ltd. | pCR |
6.5.5Study on enhancement of Management Data Analytics Service
| Yes |
Yes
| not treated | No | |||
| S5‑196271 | pCR 28.535 on MDAS assisted coverage performance assuranace | HUAWEI TECHNOLOGIES Co. Ltd. | pCR |
6.5.5Study on enhancement of Management Data Analytics Service
| Yes |
Yes
| revised | No | S5‑196815 | ||
| S5‑196272 | New WID network policy management for 5G mobile networks based on NFV scenarios | China Mobile Com. Corporation | WID new | Approval |
6.2New OAM&P Work Item proposals
| Yes |
YesCMCC clarified that this was intended for approval in December 2020.
Nokia had problems with the objectives and the alignment with ETSI MANO. This would imply changing all work done in release 15 and 16.
Edwin (Ericsson): virtualised resources in ETSI MANO are too narrow, as policies affect both virtualised and non-virtualised resources.
ORANGE: remove NFV scenarios from the spec and WID title, these are not necessary. This also assumes that normative work in 5G policy management is concluded, which is not true.
The Chair commented that in his view the current workload was very high and new WIDs should not be brought in until current working items are finished first.
Intel: this implies that service-based policy management in Release 16 would not be supported. Nokia: are there any policies in 5G management in Release 16? This would have to be analised.
| revised | No | S5‑196582 | |
| S5‑196273 | Revised WID network policy management for mobile networks based on NFV scenarios | China Mobile Com. Corporation | WID revised | Approval |
6.4.3Network policy management for mobile networks based on NFV scenarios
| Yes |
Yes
| revised | No | S5‑196655 | |
| S5‑196274 | pCR 28.311 Add Information Object Classes | China Mobile Com. Corporation | pCR | Approval |
6.4.3Network policy management for mobile networks based on NFV scenarios
| Yes |
Yes
| revised | No | S5‑196656 | |
| S5‑196275 | Add reference | China Mobile Com. Corporation | pCR | Approval |
6.4.3Network policy management for mobile networks based on NFV scenarios
| Yes |
Yes
| merged | No | S5‑196656 | |
| S5‑196276 | pCR 28.311 Add Solution Set(SS)definitions | China Mobile Com. Corporation | pCR | Approval |
6.4.3Network policy management for mobile networks based on NFV scenarios
| Yes |
Yes
| revised | No | S5‑196658 | |
| S5‑196277 | pCR 28.311 Add XML definition | China Mobile Com. Corporation | pCR | Approval |
6.4.3Network policy management for mobile networks based on NFV scenarios
| Yes |
Yes
| revised | No | S5‑196659 | |
| S5‑196278 | pCR 28.311 Add SOAP Solution Set | China Mobile Com. Corporation | pCR | Approval |
6.4.3Network policy management for mobile networks based on NFV scenarios
| Yes |
Yes
| revised | No | S5‑196660 | |
| S5‑196279 | Discussion on choices for 28.311 Solution Set | China Mobile Com. Corporation | discussion | Discussion |
6.4.3Network policy management for mobile networks based on NFV scenarios
| No |
Yes
| withdrawn | Yes | ||
| S5‑196280 | Discussion on choices for 28.311 Solution Set | China Mobile Com. Corporation | discussion | Discussion |
6.4.3Network policy management for mobile networks based on NFV scenarios
| No |
Yes
| withdrawn | Yes | ||
| S5‑196281 | Discussion on choices for 28.311 Solution Set | China Mobile Com. Corporation | discussion | Discussion |
6.4.3Network policy management for mobile networks based on NFV scenarios
| No |
Yes
| withdrawn | Yes | ||
| S5‑196282 | Discussion on choices for 28.311 Solution Set | China Mobile Com. Corporation | discussion | Discussion |
6.4.3Network policy management for mobile networks based on NFV scenarios
| No |
Yes
| withdrawn | Yes | ||
| S5‑196283 | Discussion on choices for 28.311 Solution Set | China Mobile Com. Corporation | discussion | Discussion |
6.4.3Network policy management for mobile networks based on NFV scenarios
| Yes |
Yes
| withdrawn | Yes | ||
| S5‑196284 | Discussion on URI dynamic discovery | Huawei | discussion | Endorsement |
6.4.6Discovery of management services in 5G
| Yes |
Yes
| revised | No | S5‑196777 | |
| S5‑196285 | Rel-16 CR TS 28.533 Obtaining URI of MnS instance | Huawei | CR | Agreement |
6.4.6Discovery of management services in 5G
| Yes |
Yes
| revised | No | S5‑196778 | |
| S5‑196286 | Rel-16 CR TS 28.532 MnS instance URI discovery | Huawei | CR | Agreement |
6.4.6Discovery of management services in 5G
| Yes |
Yes
| revised | No | S5‑196779 | |
| S5‑196287 | Discussion paper about exposure governance | Huawei | discussion | Endorsement |
6.4.6Discovery of management services in 5G
| Yes |
Yes
| revised | No | S5‑196667 | |
| S5‑196288 | Rel-16 CR TS 28.532 Add stage 2 and stage 3 definition for MnS capability query | Huawei | CR | Agreement |
6.4.6Discovery of management services in 5G
| Yes |
Yes
| not pursued | No | ||
| S5‑196289 | Rel-16 CR TS 28.530 Add concept descritipn for tenant information | Huawei | CR | Agreement |
6.4.14Enhancement of 3GPP management system for multiple tenant environment support
| Yes |
Yes
| revised | No | S5‑196753 | |
| S5‑196290 | Rel-16 CR TS 28.533 Add concept descritipn for management capabiliy | Huawei | CR | Agreement |
6.4.14Enhancement of 3GPP management system for multiple tenant environment support
| Yes |
Yes
| revised | No | S5‑196754 | |
| S5‑196291 | Discussion paper about tenant information usage in network slice NRM | Huawei | discussion | Endorsement |
6.4.14Enhancement of 3GPP management system for multiple tenant environment support
| Yes |
Yes
| noted | No | ||
| S5‑196292 | Rel-16 CR TS 28.541 ServiceProfile extension to support multiple tenants environment | Huawei | CR | Agreement |
6.4.14Enhancement of 3GPP management system for multiple tenant environment support
| Yes |
Yes
| not pursued | No | ||
| S5‑196293 | Rel-16 CR TS 28.550 Performance management service enhancement for tenant supporting | Huawei | CR | Agreement |
6.4.14Enhancement of 3GPP management system for multiple tenant environment support
| Yes |
Yes
| revised | No | S5‑196755 | |
| S5‑196294 | Rel-16 CR TS 28.552 Performance measurement extension to support multiple tenants environment | Huawei | CR | Agreement |
6.4.14Enhancement of 3GPP management system for multiple tenant environment support
| Yes |
Yes
| revised | No | S5‑196756 | |
| S5‑196295 | Rel-16 CR 28.552 Correct measurements on RTT delay between PSA UPF and UE | Huawei | CR | Agreement |
6.4.5Enhancement of performance assurance for 5G networks including network slicing
| Yes |
Yes
| not pursued | No | ||
| S5‑196296 | Rel-16 CR TS 28.541 XML Solution Set for 5GC | Huawei | CR | Agreement |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
YesIntel pointed out that there was a procedure for stage2/3 in both release 15 and release 16 and this may not be followed here.
The vice Chair asked the group if there was a baseline for release 15 (stage 2 and stage 3 in sync?). The answer was no. Then Zou Lan asked if this was possible for December, but no clear answer was given.
| agreed | No | ||
| S5‑196297 | New WID on network slice management enhancements | Huawei | WID new | Agreement |
6.2New OAM&P Work Item proposals
| Yes |
YesHuawei clarified that this was bringing work from other SDOs in order to identify gaps with them. Nokia replied that SA2's activity was a feasibility study and this was a normative work item based on a study from another group. Nokia would prefer to see a study instead. On the GSMA activity, they have some work already and there is some activity ongoing in the form of LS, so no need for a WID for this. They also commented that informative work to keep track of what was done in SA2 and SDOs was alright for them, but a normative WID would be overkill for SA5. Ericsson agreed and noted that the objectives were written as "potential" which was study language anyway. Intel supported Nokia and Ericsson as well.
Nokia wanted to point out that the relationship with SA2's study had to be clearly shown.
| revised | No | S5‑196583 | |
| S5‑196298 | Presentation of TS 28.311 for Information to SA#86 | China Mobile Com. Corporation | TS or TR cover | Information |
6.4.3Network policy management for mobile networks based on NFV scenarios
| Yes |
Yes
| noted | No | ||
| S5‑196299 | Rel-11 CR TS 32.421 Remove the editor's notes | HUAWEI TECHNOLOGIES Co. Ltd. | CR | Agreement |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196805 | |
| S5‑196300 | Rel-12 CR TS 32.421 Remove the editor's notes | HUAWEI TECHNOLOGIES Co. Ltd. | CR | Agreement |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196806 | |
| S5‑196301 | Rel-13 CR TS 32.421 Remove the editor's notes | HUAWEI TECHNOLOGIES Co. Ltd. | CR | Agreement |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196807 | |
| S5‑196302 | Rel-14 CR TS 32.421 Remove the editor's notes | HUAWEI TECHNOLOGIES Co. Ltd. | CR | Agreement |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196808 | |
| S5‑196303 | Rel-15 CR TS 32.421 Remove the editor's notes | HUAWEI TECHNOLOGIES Co. Ltd. | CR | Agreement |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196809 | |
| S5‑196304 | Add support of Configurable FM | Ericsson LM | CR | Approval |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
YesHuawei: Why alarm information as IoC?
Orange: Alarm notification target should be addressed more globally, all kinds of notifications.
Nokia: a logical description of the notifications is needed here.
The contribution was not clear to Huawei and Nokia so it had to be taken offline.Tdoc 425 was related to this one as had to be discussed together.
| revised | No | S5‑196598 | |
| S5‑196305 | Add missing (E-UTRAN) cell and freq relation | Ericsson LM | CR | Approval |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
YesSame comments w.r.t the changes (removal instead of change of format).
| revised | No | S5‑196589 | |
| S5‑196306 | Rel-16 CR TS 28.541 Add OAM support for RIM parameters | HUAWEI TECHNOLOGIES Co. Ltd. | CR | Agreement |
6.4.7NRM enhancements
| Yes |
Yes
| revised | No | S5‑196810 | |
| S5‑196307 | Rel-16 CR TS 28.540 Add OAM support for RIM parameters | HUAWEI TECHNOLOGIES Co. Ltd. | CR | Agreement |
6.4.7NRM enhancements
| Yes |
Yes
| revised | No | S5‑196780 | |
| S5‑196308 | Add missing stage 3 CORBA/IDL solution | Ericsson LM | CR | Approval |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
YesSame comments w.r.t the changes (removal instead of change of format). MCC added that new clauses should have the form A.3.X.
| revised | No | S5‑196590 | |
| S5‑196309 | Rel-16 CR TS 28.550 add clarification of the NSI and NSSI performance assurance | Huawei Telecommunication India | CR | Agreement |
6.4.5Enhancement of performance assurance for 5G networks including network slicing
| Yes |
Yes
| not pursued | No | ||
| S5‑196310 | pCR 28.313 Add PCI configuration use case and requirements | HUAWEI TECHNOLOGIES Co. Ltd. | pCR | Approval |
6.4.13Self-Organizing Networks (SON) for 5G networks
| Yes |
Yes
| revised | No | S5‑196751 | |
| S5‑196311 | pCR 28.313 Add ANR management use case and requirements | HUAWEI TECHNOLOGIES Co. Ltd. | pCR | Approval |
6.4.13Self-Organizing Networks (SON) for 5G networks
| Yes |
Yes
| noted | No | ||
| S5‑196312 | pCR 28.313 Add CCO use cases and requriements | HUAWEI TECHNOLOGIES Co. Ltd. | pCR | Approval |
6.4.13Self-Organizing Networks (SON) for 5G networks
| Yes |
Yes
| not treated | No | ||
| S5‑196313 | pCR 28.313 Add MRO use cases and requriements | HUAWEI TECHNOLOGIES Co. Ltd. | pCR | Approval |
6.4.13Self-Organizing Networks (SON) for 5G networks
| Yes |
Yes
| revised | No | S5‑196750 | |
| S5‑196314 | Rel-15 CR TS 28.622 update the definition of attribute measurementsList | ZTE Corporation, Ericsson | CR | Agreement |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| not pursued | No | ||
| S5‑196315 | Rel-16 CR TS 28.622 Add measurementsList attribute into related IOCs | ZTE Corporation, Ericsson | CR | Agreement |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
YesHuawei: dependency with stage 3?
Intel: relation between measurement type and gPS.
Nokia:we need to think how in stage 3 we are to manipulate huge list of arrays.
This was taken offline.
| not pursued | No | ||
| S5‑196316 | Rel-15 CR 28.532 Corrections to provisioning MnS notification definitions (Stage 2) | Orange | CR | Approval |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| merged | No | S5‑196758 | |
| S5‑196317 | Rel-16 CR 28.532 Corrections to provisioning MnS notification definitions (Stage 2) | Orange | CR | Approval |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| merged | No | S5‑196759 | |
| S5‑196318 | pCR 28.861 Remove work not in Rel-16 | Ericsson France S.A.S | pCR | Approval |
6.5.2Study on Self-Organizing Networks (SON) for 5G
| Yes |
Yes
| not treated | No | ||
| S5‑196319 | pCR 28.313 ANR Business level requirements | Ericsson France S.A.S | pCR | Agreement |
6.4.13Self-Organizing Networks (SON) for 5G networks
| Yes |
Yes
| revised | No | S5‑196802 | |
| S5‑196320 | pCR 28.313 ANR Specification level requirements for NR RAN | Ericsson France S.A.S | pCR | Agreement |
6.4.13Self-Organizing Networks (SON) for 5G networks
| Yes |
Yes
| revised | No | S5‑196803 | |
| S5‑196321 | pCR 28.313 ANR Specification level requirements for E-UTRAN | Ericsson France S.A.S | pCR | Agreement |
6.4.13Self-Organizing Networks (SON) for 5G networks
| Yes |
Yes
| revised | No | S5‑196804 | |
| S5‑196322 | UC Deployment of a stand-alone NPN with 3GPP and non-3GPP segments | TELEFONICA S.A. | pCR | Approval |
6.5.3Study on non-public networks management
| Yes |
Yes
| revised | No | S5‑196734 | |
| S5‑196323 | pCR 28.810 Add skeleton | China Mobile, Huawei, ZTE, Turkcell | pCR | Approval |
6.5.6Study on autonomous network levels
| Yes |
Yes
| approved | No | ||
| S5‑196324 | pCR 28.810 Add background | China Mobile, Huawei | pCR | Approval |
6.5.6Study on autonomous network levels
| Yes |
Yes
| revised | No | S5‑196739 | |
| S5‑196325 | pCR 28.810 Add scope | China Mobile, Huawei | pCR | Approval |
6.5.6Study on autonomous network levels
| Yes |
Yes
| revised | No | S5‑196740 | |
| S5‑196326 | pCR Add skeleton of draft TR 28.809 | Intel Finland Oy | pCR | Agreement |
6.5.5Study on enhancement of Management Data Analytics Service
| Yes |
Yes
| revised | No | S5‑196752 | |
| S5‑196327 | pCR Add overview for MDA | Intel Finland Oy | pCR | Agreement |
6.5.5Study on enhancement of Management Data Analytics Service
| Yes |
Yes
| revised | No | S5‑196812 | |
| S5‑196328 | Add MDA process | Intel Finland Oy | pCR | Agreement |
6.5.5Study on enhancement of Management Data Analytics Service
| Yes |
Yes
| noted | No | ||
| S5‑196329 | Add relation between MDA and SON | Intel Finland Oy | pCR | Agreement |
6.5.5Study on enhancement of Management Data Analytics Service
| Yes |
Yes
| noted | No | ||
| S5‑196330 | Add UC on coverage issue analysis | Intel Finland Oy | pCR | Agreement |
6.5.5Study on enhancement of Management Data Analytics Service
| Yes |
Yes
| revised | No | S5‑196814 | |
| S5‑196331 | Rel-15 CR 28.550 Add stream information management related operations | Intel Finland Oy | CR | Agreement |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
YesIntel: you can change the configuration on the fly.
Nokia had some concerns on the streams and it had to be taken offline.
| not pursued | No | ||
| S5‑196332 | Rel-16 CR 28.550 Add stream information management related operations | Intel Finland Oy | CR | Agreement |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| not pursued | No | ||
| S5‑196333 | Discussion paper on LS to RAN3 on QoS monitoring for URLLC | Intel Finland Oy | discussion | Endorsement |
6.4.5Enhancement of performance assurance for 5G networks including network slicing
| Yes |
Yes
| endorsed | No | ||
| S5‑196334 | LS to RAN3 on QoS monitoring for URLLC | Intel Finland Oy | LS out | Approval |
6.4.5Enhancement of performance assurance for 5G networks including network slicing
| Yes |
Yes
| revised | No | S5‑196840 | |
| S5‑196335 | Rel-16 CR 28.552 Add measurements related to handover between 5GS and EPS | Intel Finland Oy | CR | Agreement |
6.4.5Enhancement of performance assurance for 5G networks including network slicing
| Yes |
Yes
| revised | No | S5‑196817 | |
| S5‑196336 | Rel-16 CR 28.552 Add measurements related to registration via trusted non-3GPP access | Intel Finland Oy | CR | Agreement |
6.4.5Enhancement of performance assurance for 5G networks including network slicing
| Yes |
Yes
| agreed | No | ||
| S5‑196337 | Rel-16 CR 28.552 Add measurements related to service request via trusted non-3GPP access | Intel Finland Oy | CR | Agreement |
6.4.5Enhancement of performance assurance for 5G networks including network slicing
| Yes |
Yes
| agreed | No | ||
| S5‑196338 | Rel-16 CR 28.552 Add measurements related to QoS flow modification in NG-RAN | Intel Finland Oy | CR | Agreement |
6.4.5Enhancement of performance assurance for 5G networks including network slicing
| Yes |
Yes
| revised | No | S5‑196610 | |
| S5‑196339 | Rel-16 CR 28.552 Add measurements related to QoS flow setup via untrusted non-3GPP access | Intel Finland Oy | CR | Agreement |
6.4.5Enhancement of performance assurance for 5G networks including network slicing
| Yes |
Yes
| revised | No | S5‑196772 | |
| S5‑196340 | Rel-16 CR 28.552 Add measurements related to QoS flow modification via untrusted non-3GPP access | Intel Finland Oy | CR | Agreement |
6.4.5Enhancement of performance assurance for 5G networks including network slicing
| Yes |
Yes
| revised | No | S5‑196773 | |
| S5‑196341 | Rel-16 CR 28.552 Add measurements related to handover between 5GS and EPS via N26 interface | Intel Finland Oy | CR | Agreement |
6.4.5Enhancement of performance assurance for 5G networks including network slicing
| Yes |
Yes
| revised | No | S5‑196774 | |
| S5‑196342 | Rel-16 CR TS 28.540 Add GSMA GST mapping related requirements | Huawei, China Mobile | CR | Approval |
6.4.15Management Aspects of 5G Service-Level Agreement
| Yes |
Yes
| revised | No | S5‑196641 | |
| S5‑196343 | Rel-16 CR TS 28.541 Update on slice model | Huawei, China Mobile | CR | Approval |
6.4.15Management Aspects of 5G Service-Level Agreement
| Yes |
Yes
| revised | No | S5‑196642 | |
| S5‑196344 | Living document of review of GSMA GST | Huawei, China Mobile | other | Approval |
6.4.15Management Aspects of 5G Service-Level Agreement
| Yes |
Yes
| approved | No | ||
| S5‑196345 | Rel-16 CR 28.541 Add relation of GST and profiles | Huawei, China Mobile | CR | Approval |
6.4.15Management Aspects of 5G Service-Level Agreement
| Yes |
Yes
| revised | No | S5‑196620 | |
| S5‑196346 | Rel-16 CR TS 28.554 Add 5G Energy Efficiency KPI | Huawei, Orange | CR | Approval |
6.4.2Energy Efficiency of 5G
| Yes |
Yes
| revised | No | S5‑196770 | |
| S5‑196347 | pCR 28.310 Cleanup proposal | Huawei | pCR | Approval |
6.4.2Energy Efficiency of 5G
| Yes |
Yes
| approved | No | ||
| S5‑196348 | pCR 28.310 Add requirements for energy saving cell overlaid cases | Huawei, Orange | pCR | Approval |
6.4.2Energy Efficiency of 5G
| Yes |
Yes
| revised | No | S5‑196647 | |
| S5‑196349 | pCR 28.310 Add basic concepts related to energy saving | Huawei, Orange | pCR | Approval |
6.4.2Energy Efficiency of 5G
| Yes |
Yes
| approved | No | ||
| S5‑196350 | pCR 28.310 Add solutions for energy efficiency | Huawei, Orange | pCR | Approval |
6.4.2Energy Efficiency of 5G
| Yes |
Yes
| approved | No | ||
| S5‑196351 | pCR 28.310 Add overview for various energy saving solutions | Huawei, Orange | pCR | Approval |
6.4.2Energy Efficiency of 5G
| Yes |
Yes
| revised | No | S5‑196649 | |
| S5‑196352 | pCR 28.807 Update on general concept | Huawei | pCR | Approval |
6.5.3Study on non-public networks management
| Yes |
Yes
| revised | No | S5‑196710 | |
| S5‑196353 | pCR 28.807 clean-up use case of NPN provisioning by a network slice of a PLMN | Huawei | pCR | Approval |
6.5.3Study on non-public networks management
| Yes |
Yes
| revised | No | S5‑196709 | |
| S5‑196354 | pCR 28.807 Management of stand-alone non-public networks | Huawei | pCR | Approval |
6.5.3Study on non-public networks management
| Yes |
Yes
| revised | No | S5‑196711 | |
| S5‑196355 | pCR 28.807 Management of public network integrated NPN | Huawei | pCR | Approval |
6.5.3Study on non-public networks management
| Yes |
Yes
| revised | No | S5‑196712 | |
| S5‑196356 | pCR 28.807 Add use case of NPN provisioning by a stand-alone non-public network | Huawei | pCR | Approval |
6.5.3Study on non-public networks management
| Yes |
Yes
| noted | No | ||
| S5‑196357 | pCR 28.807 Add requirements for management of public network integrated NPN | Huawei | pCR | Approval |
6.5.3Study on non-public networks management
| Yes |
Yes
| revised | No | S5‑196737 | |
| S5‑196358 | pCR 28.807 Add use case of providing traffic management and monitoring capability to an NPN operator | Huawei | pCR | Approval |
6.5.3Study on non-public networks management
| Yes |
Yes
| revised | No | S5‑196736 | |
| S5‑196359 | pCR 28.807 Add use case of 3rd party management of NPN | Huawei | pCR | Approval |
6.5.3Study on non-public networks management
| Yes |
Yes
| noted | No | ||
| S5‑196360 | pCR 28.812 Add an example of utilization intent Driven MnS for factory private network | Huawei | pCR | Approval |
6.4.4Intent driven management service for mobile networks
| Yes |
Yes
| noted | No | ||
| S5‑196361 | pCR 28.313 Add SON Concept | Huawei,China Telecommunications | pCR | Approval |
6.4.13Self-Organizing Networks (SON) for 5G networks
| Yes |
Yes
| merged | No | S5‑196675 | |
| S5‑196362 | pCR 28.313 Add usecase and requirements for establishment of new NF in network | Huawei,China Telecommunications | pCR | Approval |
6.4.13Self-Organizing Networks (SON) for 5G networks
| Yes |
Yes
| not treated | No | ||
| S5‑196363 | pCR 28.810 Add concept of network autonomy levels | Huawei,China Mobile | pCR | Approval |
6.5.6Study on autonomous network levels
| Yes |
Yes
| noted | No | ||
| S5‑196364 | Rel-16 pCR 28.812 Solution for CSI deployemnt at the edge | Samsung Electronics France SA | pCR | Agreement |
6.4.4Intent driven management service for mobile networks
| Yes |
Yes
| revised | No | S5‑196537 | |
| S5‑196365 | Editorial revision for Introduction | Nanjing Ericsson Panda Com Ltd | pCR | Approval |
6.4.1Management of QoE measurement collection
| Yes |
Yes
| approved | No | ||
| S5‑196366 | Revise the Introduction | Nanjing Ericsson Panda Com Ltd | CR | Approval |
6.4.1Management of QoE measurement collection
| Yes |
Yes
| agreed | No | ||
| S5‑196367 | Add missing definition for matching-criteria-attributes | Ericsson LM | CR | Approval |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
YesEricsson clarified that the definition was used in the specification three times.
Nokia didn’t agree with this, as they found the use of identifier here very misleading.
It was agreed to just refer to the spec in [x].
Intel considered that this should also be addressed in release 15. This was taken offline.
| revised | No | S5‑196599 | |
| S5‑196368 | Rel-16 CR 32.290 Explanation of when Units Usage must be reported | Ericsson | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196693 | |
| S5‑196369 | Rel-16 CR 32.290 Explanation of Units Usage in Initial | Ericsson | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196694 | |
| S5‑196370 | Rel-16 CR 32.298 Correction of Multiple Unit Usage | Ericsson | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | ||
| S5‑196371 | Rel-16 CR 32.255 Correction of Container definition | Ericsson | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | ||
| S5‑196372 | Rel-16 CR 32.290 Wrong name on CR | Ericsson | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | ||
| S5‑196373 | Rel-16 CR 32.255 Correction of QoS Based Charging description | Ericsson | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196695 | |
| S5‑196374 | Rel-16 CR 32.255 Definition of Emergency Session handling | Ericsson | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196714 | |
| S5‑196375 | Rel-16 CR 32.255 Correction of Charging Identifier | Ericsson | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| not pursued | No | ||
| S5‑196376 | DP Way forward of KPI reporting related MnS | ZTE Corporation, China Telecom | discussion | Endorsement |
6.4.12KPI reporting
| Yes |
Yes
| revised | No | S5‑196661 | |
| S5‑196377 | Rel-16 CR 32.255 Missing default trigger for Offline | Ericsson | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196715 | |
| S5‑196378 | Rel-16 CR 32.298 Correction of ServingNetworkFunctionID | Ericsson | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196678 | |
| S5‑196379 | Rel-16 CR 32.291 Correction of yaml | Ericsson | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196716 | |
| S5‑196380 | Rel-16 CR 32.290 Definition of State Machine | Ericsson | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| postponed | No | ||
| S5‑196381 | Rel-16 CR 32.290 Correction of redirect at termination | Ericsson | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| postponed | No | ||
| S5‑196382 | Rel-16 CR 32.290 Correction of Converged Charging principles | Ericsson | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196717 | |
| S5‑196383 | Rel-16 CR 32.291 Correction of pDUSessionChargingInformation | Ericsson | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196718 | |
| S5‑196384 | Rel-16 CR 32.291 Adding Exposure Function Northbound API Specified Data Type | Ericsson | CR | Agreement |
7.4.2Network Exposure Charging in 5G System Architecture
| Yes |
Yes
| revised | No | S5‑196545 | |
| S5‑196385 | Rel-16 CR 32.275 Addition of convergent flows | Ericsson | CR | Agreement |
7.4.4IMS Charging in 5G System Architecture
| Yes |
Yes
| revised | No | S5‑196547 | |
| S5‑196386 | Rel-16 CR 32.281 Addition of convergent flows | Ericsson | CR | Agreement |
7.4.4IMS Charging in 5G System Architecture
| Yes |
Yes
| revised | No | S5‑196548 | |
| S5‑196387 | Rel-16 pCR 28.201 Architecture considerations | Ericsson | pCR | Agreement |
7.4.6Network Slice Performance and Analytics Charging in 5G System
| Yes |
Yes
| revised | No | S5‑196556 | |
| S5‑196388 | Rel-16 pCR 28.202 Architecture considerations | Ericsson | pCR | Agreement |
7.4.7Network Slice Management Charging in 5G System
| Yes |
Yes
| noted | No | ||
| S5‑196389 | Rel-16 CR TS 28.550 Add UC and requirements for NF KPI job control | China Telecommunications, ZTE | CR | Agreement |
6.4.12KPI reporting
| Yes |
Yes
| revised | No | S5‑196662 | |
| S5‑196390 | Add a new description of KPI that related to Mean number of successful periodic registration updates | China Mobile E-Commerce Co. | CR | Agreement |
6.4.5Enhancement of performance assurance for 5G networks including network slicing
| Yes |
Yes
| revised | No | S5‑196784 | |
| S5‑196391 | Study on concept, requirements and solutions for levels of autonomous network | China Mobile, Huawei, ZTE, Turkcell | draft TR | Information |
6.5.6Study on autonomous network levels
| Yes |
Yes
| approved | No | ||
| S5‑196392 | Add a new description of KPI that related to successful rate of mobility registration updates of Single Network Slice Instance | China Mobile E-Commerce Co. | CR | Agreement |
6.4.5Enhancement of performance assurance for 5G networks including network slicing
| Yes |
Yes
| revised | No | S5‑196785 | |
| S5‑196393 | Rel-16 CR TS 28.550 Add UC and requirements for NSSI KPI job control | China Telecommunications, ZTE | CR | Agreement |
6.4.12KPI reporting
| Yes |
Yes
| merged | No | S5‑196662 | |
| S5‑196394 | Rel-16 CR TS 28.550 Add UC and requirements for NSI KPI job control | China Telecommunications, ZTE | CR | Agreement |
6.4.12KPI reporting
| Yes |
Yes
| merged | No | S5‑196662 | |
| S5‑196395 | Add Automatic CSI to NSI mapping use case | China Mobile E-Commerce Co. | discussion | Approval |
6.5.5Study on enhancement of Management Data Analytics Service
| Yes |
Yes
| not treated | No | ||
| S5‑196396 | Add description and requirements of communication service instance monitoring | China Mobile E-Commerce Co. | CR | Agreement |
6.4.15Management Aspects of 5G Service-Level Agreement
| Yes |
Yes
| not pursued | No | ||
| S5‑196397 | Rel-16 CR TS 28.550 Add UC and requirements for NetworkSubNetwork KPI job control | China Telecommunications, ZTE | CR | Agreement |
6.4.12KPI reporting
| Yes |
Yes
| merged | No | S5‑196662 | |
| S5‑196398 | Add description of communication service lifecycle prepareation phase | China Mobile E-Commerce Co. | CR | Agreement |
6.4.15Management Aspects of 5G Service-Level Agreement
| Yes |
Yes
| not pursued | No | ||
| S5‑196399 | Add description of communication service catelogue | China Mobile E-Commerce Co. | CR | Agreement |
6.4.15Management Aspects of 5G Service-Level Agreement
| Yes |
Yes
| not pursued | No | ||
| S5‑196400 | Add Concept for Establishment of new NF in network | China Telecommunications, Huawei | pCR | Approval |
6.4.13Self-Organizing Networks (SON) for 5G networks
| Yes |
Yes
| not treated | No | ||
| S5‑196401 | Add Concept for Establishment of new NF in network | China Telecommunications, Huawei | pCR | Approval |
6.4.13Self-Organizing Networks (SON) for 5G networks
| No |
Yes
| withdrawn | Yes | ||
| S5‑196402 | pCR28.805 Add New Possible Parameters in the Mapping Between GSMA GST and SA5 NST | China Mobile E-Commerce Co. | CR | Approval |
6.4.15Management Aspects of 5G Service-Level Agreement
| Yes |
Yes
| not pursued | No | ||
| S5‑196403 | Discussion on the effect to existed 5G management system when introduced 5G SLA | China Mobile E-Commerce Co. | discussion | Discussion |
6.4.15Management Aspects of 5G Service-Level Agreement
| Yes |
Yes
| revised | No | S5‑196783 | |
| S5‑196404 | pCR 28.809 Add MDAS assisted NWDAF related use cases | Huawei | pCR | Approval |
6.5.5Study on enhancement of Management Data Analytics Service
| Yes |
Yes
| not treated | No | ||
| S5‑196405 | pCR 28.809 Add descriptions of different data types for analytics purpose | Huawei | pCR | Approval |
6.5.5Study on enhancement of Management Data Analytics Service
| Yes |
Yes
| not treated | No | ||
| S5‑196406 | pCR 28.809 Add use case of MDAS assisted KPI anomaly detection | Huawei | pCR | Approval |
6.5.5Study on enhancement of Management Data Analytics Service
| Yes |
Yes
| not treated | No | ||
| S5‑196407 | pCR 28.809 Add use case of MDAS assisted alarm incident detection | Huawei | pCR | Approval |
6.5.5Study on enhancement of Management Data Analytics Service
| Yes |
Yes
| not treated | No | ||
| S5‑196408 | pCR 28.809 Add use case of MDAS assisted resource allocation analysis across multiple NSI | Huawei | pCR | Approval |
6.5.5Study on enhancement of Management Data Analytics Service
| Yes |
Yes
| not treated | No | ||
| S5‑196409 | Rel-16 CR TS 28.550 Add KPI job control service | ZTE Corporation, China Telecom | CR | Agreement |
6.4.12KPI reporting
| Yes |
Yes
| revised | No | S5‑196748 | |
| S5‑196410 | Rel-16 CR TS 28.550 Update the description of scope | ZTE, China Telecom | CR | Agreement |
6.4.12KPI reporting
| Yes |
Yes
| agreed | No | ||
| S5‑196411 | Rel-16 CR TS 28.552 Re-orgnize the structure of TS 28.552 | HUAWEI TECHNOLOGIES Co. Ltd. | CR |
6.4.5Enhancement of performance assurance for 5G networks including network slicing
| Yes |
Yes
| revised | No | S5‑196776 | ||
| S5‑196412 | Rel-16 CR TS 28.554 Update the KPI template | ZTE, China Telecom | CR | Agreement |
6.4.12KPI reporting
| Yes |
Yes
| merged | No | S5‑196793 | |
| S5‑196413 | pCR 28.861 Trace and MDT | Ericsson France S.A.S | pCR | Approval |
6.5.2Study on Self-Organizing Networks (SON) for 5G
| Yes |
Yes
| not treated | No | ||
| S5‑196414 | Organizing Self Organizing Specifications | Ericsson France S.A.S | discussion | Endorsement |
6.4.13Self-Organizing Networks (SON) for 5G networks
| Yes |
Yes
| revised | No | S5‑196673 | |
| S5‑196415 | Rel-16 CR 32.298 Correction of missing otherQutaType in sMFTrigger | Ericsson | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196719 | |
| S5‑196416 | pCR 28.809 Add use case of MDAS assisted user data congestion analysis | Huawei | pCR | Approval |
6.5.5Study on enhancement of Management Data Analytics Service
| Yes |
Yes
| withdrawn | Yes | ||
| S5‑196417 | pCR 28.809 Add use case of MDAS assisted traffic load analysis | Huawei | pCR | Approval |
6.5.5Study on enhancement of Management Data Analytics Service
| Yes |
Yes
| not treated | No | ||
| S5‑196418 | pCR 28.313 Add ANR Use Case: Start | Ericsson France S.A.S | pCR | Approval |
6.4.13Self-Organizing Networks (SON) for 5G networks
| Yes |
Yes
| revised | No | S5‑196794 | |
| S5‑196419 | pCR 28.313 Add ANR Use Case: Stop | Ericsson France S.A.S | pCR | Approval |
6.4.13Self-Organizing Networks (SON) for 5G networks
| Yes |
Yes
| revised | No | S5‑196795 | |
| S5‑196420 | pCR 28.313 Add ANR Use Case: Notification | Ericsson France S.A.S | pCR | Approval |
6.4.13Self-Organizing Networks (SON) for 5G networks
| Yes |
Yes
| revised | No | S5‑196796 | |
| S5‑196421 | pCR 28.313 Add ANR Use Case: Handover whitelisting | Ericsson France S.A.S | pCR | Approval |
6.4.13Self-Organizing Networks (SON) for 5G networks
| Yes |
Yes
| revised | No | S5‑196797 | |
| S5‑196422 | pCR 28.313 Add ANR Use Case: Handover blacklisting | Ericsson France S.A.S | pCR | Approval |
6.4.13Self-Organizing Networks (SON) for 5G networks
| Yes |
Yes
| revised | No | S5‑196798 | |
| S5‑196423 | pCR 28.313 Add ANR Use Case: Prohibit X2/Xn | Ericsson France S.A.S | pCR | Approval |
6.4.13Self-Organizing Networks (SON) for 5G networks
| Yes |
Yes
| revised | No | S5‑196799 | |
| S5‑196424 | pCR 28.313 Add ANR Use Case: Prohibit X2/Xn handover | Ericsson France S.A.S | pCR | Approval |
6.4.13Self-Organizing Networks (SON) for 5G networks
| Yes |
Yes
| revised | No | S5‑196800 | |
| S5‑196425 | CR 28.622 Add subscription NRM fragment | Orange, Nokia, Nokia Shanghai Bell | CR | Approval |
6.4.9Integration of ONAP and 3GPP 5G management framework
| Yes |
Yes
| not pursued | No | ||
| S5‑196426 | CR 28.622 Add heartbeat NRM fragment | Nokia, Nokia Shanghai Bell | CR | Approval |
6.4.9Integration of ONAP and 3GPP 5G management framework
| Yes |
Yes
| not pursued | No | ||
| S5‑196427 | Rel-16 CR 32.255 Adding ETSUN architecture with I-SMF insertion | Ericsson | CR | Agreement |
7.4.5Charging aspects of Enhancing Topology of SMF and UPF in 5G Networks
| Yes |
Yes
| postponed | No | ||
| S5‑196428 | CR 28.623 Add subscription NRM fragment | Orange, Nokia, Nokia Shanghai Bell | CR | Approval |
6.4.9Integration of ONAP and 3GPP 5G management framework
| No |
Yes
| withdrawn | Yes | ||
| S5‑196429 | Rel-16 CR 32.255 Adding I-SMF in 5G data connectivity charging requirements | Ericsson | CR | Agreement |
7.4.5Charging aspects of Enhancing Topology of SMF and UPF in 5G Networks
| Yes |
Yes
| merged | No | S5‑196724 | |
| S5‑196430 | CR 28.623 Add heartbeat NRM fragment | Nokia, Nokia Shanghai Bell | CR | Approval |
6.4.9Integration of ONAP and 3GPP 5G management framework
| No |
Yes
| withdrawn | Yes | ||
| S5‑196431 | Rel-16 CR 32.255 Adding I-SMF in 5G data connectivity charging information | Ericsson | CR | Agreement |
7.4.5Charging aspects of Enhancing Topology of SMF and UPF in 5G Networks
| Yes |
Yes
| revised | No | S5‑196728 | |
| S5‑196432 | Rel-16 CR 32.255 Adding I-SMF in applicable triggers for FBC | Ericsson | CR | Agreement |
7.4.5Charging aspects of Enhancing Topology of SMF and UPF in 5G Networks
| Yes |
Yes
| not pursued | No | ||
| S5‑196433 | CR 32.158 Clarify design pattern for scoping and filtering | Nokia, Nokia Shanghai Bell | CR | Approval |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
YesMCC commented that it should be cat-B, otherwise the question would be why release 15 was not being corrected.
| not pursued | No | ||
| S5‑196434 | CR 32.158 Clarify design pattern for attribute field selection | Nokia; Nokia Shanghai Bell | CR | Approval |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| No |
Yes
| withdrawn | Yes | ||
| S5‑196435 | CR 32.158 Correct basic design patterns | Nokia, Nokia Shanghai Bell | CR | Approval |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | ||
| S5‑196436 | CR 32.158 Add design pattern for patching multiple resources | Nokia, Nokia Shanghai Bell | CR | Approval |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
YesIt was commented that the CRshould be in fact for Release 15. It was agreed to change it to Release 15 in the cover before next SA.
| agreed | No | ||
| S5‑196437 | CR 32.158 Correct resource representation formats | Nokia, Nokia Shanghai Bell | CR | Approval |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
YesIt was commented that the CRshould be in fact for Release 15. It was agreed to change it to Release 15 in the cover before next SA.
| agreed | No | ||
| S5‑196438 | CR 32.158 Add examples | Nokia, Nokia Shanghai Bell | CR | Approval |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
YesIt was commented that the CRshould be in fact for Release 15. It was agreed to change it to Release 15 in the cover before next SA.
| agreed | No | ||
| S5‑196439 | CR 28.532 Make scoping and filtering optional in the ProvMnS | Nokia, Nokia Shanghai Bell | CR | Approval |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
YesEricsson: this increases complexity in stage 3.
| not pursued | No | ||
| S5‑196440 | CR 28.532 Correct and update the RESTful HTTP-based solution set of provisioning | Nokia, Nokia Shanghai Bell | CR | Approval |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| No |
Yes
| withdrawn | Yes | ||
| S5‑196441 | pCR 28.808 Editorial corrections | TNO | pCR | Approval |
6.5.4Study on management and orchestration aspects with integrated satellite components in a 5G network
| Yes |
Yes
| revised | No | S5‑196664 | |
| S5‑196442 | pCR 28.809 Add use case of MDAS assisted user data congestion analysis | Huawei | pCR | Approval |
6.5.5Study on enhancement of Management Data Analytics Service
| Yes |
Yes
| revised | No | S5‑196816 | |
| S5‑196443 | pCR 28.808 Add use case for creation of a network slice instance associated with a Satellite RAN and a Terrestrial RAN | TNO | pCR | Approval |
6.5.4Study on management and orchestration aspects with integrated satellite components in a 5G network
| Yes |
Yes
| revised | No | S5‑196665 | |
| S5‑196444 | Add streaming format for Trace | Ericsson LM | draftCR | Endorsement |
6.4.11Streaming trace reporting
| Yes |
Yes
| withdrawn | Yes | ||
| S5‑196445 | Discussion paper around RRM Policy | Ericsson LM | discussion | Endorsement |
6.4.7NRM enhancements
| Yes |
Yes
| noted | No | ||
| S5‑196446 | CR 32.158 Clarify design pattern for attribute field selection | Nokia, Nokia Shanghai Bell | CR | Approval |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| not pursued | No | ||
| S5‑196447 | Rel-16 CR 28.541 Update of RRM Policy | Ericsson LM | CR | Agreement |
6.4.7NRM enhancements
| Yes |
Yes
| not pursued | No | ||
| S5‑196448 | Discussion on SA5 OA&M SWG OpenAPI files, JSON specifications and ZIP files | Orange | discussion | Discussion |
6.1OAM&P Plenary
| Yes |
YesMCC commented that the storage of files should be together with the rest of other groups documents.
Nokia queried about the use of ETSI FORGE, which it seemed a tool "hidden" for the outside World. MCC commented that ETSI FORGE was a working tool like the other 3GPP tools used in 3GPP. All results and files were public in any case and FORGE would be used for issues like compilation. It had to be taken offline a clarification of the use of ETSI FORGE since it also seemed that nobody in SA5 OAM had administrative rights to access the tool and someone in CT had to be contacted for that.
| noted | No | ||
| S5‑196449 | Add YANG/Netconf-based solution set for Generic provisioning MnS | Ericsson LM | CR | Approval |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
YesIntel: there is no agreed way forwad for netconf.
Nokia: there is no agrrement in the stage 1 of what is proposed here.
| revised | No | S5‑196791 | |
| S5‑196450 | Rel-16 pCR TR 32.845 Conclusion on key issue 1.3 for topic 1 | Openet Telecom | pCR | Approval |
7.5.1Study on Charging Aspects of Network Slicing
| Yes |
Yes
| merged | No | S5‑196552 | |
| S5‑196451 | CR 28.532 Correct and update the RESTful HTTP-based solution set of provisioning | Nokia, Nokia Shanghai Bell | CR | Approval |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| not pursued | No | ||
| S5‑196452 | Correct faulty implementation of figure 4.4.3.1 | Ericsson India Private Limited | CR | Approval |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | ||
| S5‑196453 | Implement Edithelp comments | Ericsson India Private Limited | CR | Approval |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | ||
| S5‑196454 | Add State Handling diagram for NF service | Nokia, Nokia Shanghai Bell | CR | Agreement |
6.4.7NRM enhancements
| Yes |
Yes
| not pursued | No | ||
| S5‑196455 | Update Stage 2 SEPP definition in 5GC NRM | Nokia, Nokia Shanghai Bell | CR | Agreement |
6.4.7NRM enhancements
| Yes |
Yes
| revised | No | S5‑196700 | |
| S5‑196456 | Update Stage 3 SEPP definition in 5GC NRM | Nokia, Nokia Shanghai Bell | CR | Agreement |
6.4.7NRM enhancements
| No |
Yes
| left for email approval | No | ||
| S5‑196457 | Add Stage 2 NEF definition in 5GC NRM | Nokia, Nokia Shanghai Bell | CR | Agreement |
6.4.7NRM enhancements
| Yes |
Yes
| revised | No | S5‑196703 | |
| S5‑196458 | Add Stage 3 NEF definition in 5GC NRM | Nokia, Nokia Shanghai Bell | CR | Agreement |
6.4.7NRM enhancements
| No |
Yes
| left for email approval | No | ||
| S5‑196459 | Add Stage 2 SCP definition in 5GC NRM | Nokia, Nokia Shanghai Bell | CR | Agreement |
6.4.7NRM enhancements
| Yes |
Yes
| revised | No | S5‑196702 | |
| S5‑196460 | Add Stage 3 definitions of 5GC NRM to align with stage 2 | Nokia, Nokia Shanghai Bell | CR | Agreement |
6.4.7NRM enhancements
| No |
Yes
| left for email approval | No | ||
| S5‑196461 | Support communication model in 5GC NF - Stage 2 | Nokia, Nokia Shanghai Bell | CR | Agreement |
6.4.7NRM enhancements
| Yes |
Yes
| revised | No | S5‑196704 | |
| S5‑196462 | Support communication model in 5GC NF - Stage 3 | Nokia, Nokia Shanghai Bell | CR | Agreement |
6.4.7NRM enhancements
| No |
Yes
| left for email approval | No | ||
| S5‑196463 | Add requirement in NRM to support GST attributes | Nokia, Nokia Shanghai Bell | CR | Agreement |
6.4.15Management Aspects of 5G Service-Level Agreement
| Yes |
Yes
| merged | No | S5‑196641 | |
| S5‑196464 | Add generic characters of GST in slice NRM - stage 2 | Nokia, Nokia Shanghai Bell | CR | Agreement |
6.4.15Management Aspects of 5G Service-Level Agreement
| Yes |
Yes
| merged | No | S5‑196642 | |
| S5‑196465 | Add generic characters of GST in slice NRM - stage 3 | Nokia, Nokia Shanghai Bell | CR | Agreement |
6.4.15Management Aspects of 5G Service-Level Agreement
| No |
Yes
| withdrawn | Yes | ||
| S5‑196466 | Update CoverageArea attribute in service profile - stage 2 | Nokia, Nokia Shanghai Bell | CR | Agreement |
6.4.15Management Aspects of 5G Service-Level Agreement
| Yes |
Yes
| merged | No | S5‑196642 | |
| S5‑196467 | Update CoverageArea attribute in service profile - stage 3 | Nokia, Nokia Shanghai Bell | CR | Agreement |
6.4.15Management Aspects of 5G Service-Level Agreement
| No |
Yes
| withdrawn | Yes | ||
| S5‑196468 | Fix merging errors of the specification | Nokia, Nokia Shanghai Bell | CR | Agreement |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| not treated | No | ||
| S5‑196469 | Solutions for Editor's notes | Ericsson India Private Limited | CR | Approval |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | ||
| S5‑196470 | Add passedById and other updates | Ericsson India Private Limited | CR | Approval |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | ||
| S5‑196471 | Implement Edithelp comments | Ericsson India Private Limited | CR | Approval |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | ||
| S5‑196472 | CR Rel-16 TR 28.806 Implementation of fixes for issues identified by EditHelp | Nokia | CR | Approval |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196786 | |
| S5‑196473 | Solutions for Editor's note | Ericsson India Private Limited | CR | Approval |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | ||
| S5‑196474 | pCR 28.535 Add introduction to concepts and background | Ericsson India Private Limited,Deutsche Telekom | pCR | Agreement |
6.4.10Closed loop SLS Assurance
| Yes |
Yes
| revised | No | S5‑196614 | |
| S5‑196475 | Add introduction | Ericsson India Private Limited,Deutsche Telekom | pCR | Agreement |
6.4.10Closed loop SLS Assurance
| Yes |
Yes
| revised | No | S5‑196612 | |
| S5‑196476 | Add lifecycle of a communication service | Ericsson India Private Limited,Deutsche Telekom | pCR | Agreement |
6.4.10Closed loop SLS Assurance
| Yes |
Yes
| revised | No | S5‑196615 | |
| S5‑196477 | Discussion paper on Heartbeat MnS specification approach | AT&T GNS Belgium SPRL | discussion |
6.4.9Integration of ONAP and 3GPP 5G management framework
| Yes |
Yes
| revised | No | S5‑196707 | ||
| S5‑196478 | Add management control loops | Ericsson India Private Limited | pCR | Agreement |
6.4.10Closed loop SLS Assurance
| Yes |
Yes
| approved | No | ||
| S5‑196479 | Discussion paper on Integration of ONAP and 3GPP 5G management WoW | Ericsson Telecomunicazioni SpA | discussion | Endorsement |
6.4.9Integration of ONAP and 3GPP 5G management framework
| Yes |
Yes
| withdrawn | Yes | ||
| S5‑196480 | Add scope | Ericsson India Private Limited | pCR | Agreement |
6.4.10Closed loop SLS Assurance
| Yes |
Yes
| revised | No | S5‑196611 | |
| S5‑196481 | Communication service assurance business use case and requirements | Ericsson India Private Limited,Deutsche Telekom | pCR | Agreement |
6.4.10Closed loop SLS Assurance
| Yes |
Yes
| revised | No | S5‑196619 | |
| S5‑196482 | Rel-15 CR TS 28.541 Add NRM Info Model definitions for beam managed object classes | Pivotal Commware, ZTE, Intel, P.I. Works, China Mobile, Verizon, BT, AT&T, Cisco, Deutsche Telekom | CR | Agreement |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
YesPivotal commented that in the previous version all changes were agreed and only stage 3 issues needed to be considered in parallel. This was addressed in tdoc 489.
Huawei: 4.3.X.1, NRSectorCarrier meaning? Pivotal suggested writing "associated" instead.
Nokia: IoC in 4.3.X does not have any attributes. Pivotal commented that this was a container.
Nokia also commented that the definition in 4.3.x.1 was introducing a requirement ("may"). Pivotal replied that this was an Ericsson request.
This was taken offline.
| revised | No | S5‑196600 | S5‑195914 |
| S5‑196483 | Introduce table of content | Ericsson India Private Limited | pCR | Agreement |
6.4.10Closed loop SLS Assurance
| Yes |
Yes
| approved | No | ||
| S5‑196484 | Add introduction | Ericsson India Private Limited,Deutsche Telekom | pCR |
6.4.10Closed loop SLS Assurance
| Yes |
Yes
| revised | No | S5‑196742 | ||
| S5‑196485 | Add lifecycle of a communication service | Ericsson India Private Limited,Deutsche Telekom | pCR | Agreement |
6.4.10Closed loop SLS Assurance
| Yes |
Yes
| noted | No | ||
| S5‑196486 | Add scope | Ericsson India Private Limited | pCR | Agreement |
6.4.10Closed loop SLS Assurance
| Yes |
Yes
| revised | No | S5‑196741 | |
| S5‑196487 | Rel-16 CR TS 32.421 Addition of streaming trace requirements | Nokia | CR | Approval |
6.4.11Streaming trace reporting
| Yes |
Yes
| revised | No | S5‑196708 | |
| S5‑196488 | Discussion paper on structure of 28.536 | Ericsson India Private Limited | discussion | Discussion |
6.4.10Closed loop SLS Assurance
| Yes |
Yes
| noted | No | ||
| S5‑196489 | Rel-15 CR TS 28.541 Stage 3 Add NRM Info Model definitions for beam managed object classes | Pivotal Commware, ZTE, Intel, P.I. Works, China Mobile, Verizon, BT, AT&T, Cisco, Deutsche Telekom | CR | Agreement |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
YesPivotal expected other companies to provide the stage 3 content fo these clauses.The guidelines in TS 32.160 had to be used in this case, and Ericsson volunteered to help here.
Ericsson proposed to postpone this for the next meeting since both stage 2 and 3 needed to go together and there was no agreement in 482 at that time.
MCC clarified that stage 2 CRs could be conditionally agreed, meaning that their final agreement depended on the stage 3 CRs but no further technical discussions would be needed. If the stage 3 CRs were agreed, then the stage 2 CRs could be resubmitted to the same meeting to change their status to "agreed" and then both sent together in a pack. If the stage 3 CR was not agreed, the stage 2 would remain "conditionally agreed" and would not go to SA.
| not pursued | No | ||
| S5‑196490 | Introduce table of content | Ericsson India Private Limited | pCR | Agreement |
6.4.10Closed loop SLS Assurance
| Yes |
Yes
| revised | No | S5‑196744 | |
| S5‑196491 | Rel-16 CR 32.255 Adding I-SMF in applicable triggers for QBC | Ericsson | CR | Agreement |
7.4.5Charging aspects of Enhancing Topology of SMF and UPF in 5G Networks
| Yes |
Yes
| not pursued | No | ||
| S5‑196492 | Discussion paper on SLA and SLS | Ericsson India Private Limited | discussion | Endorsement |
6.4.10Closed loop SLS Assurance
| No |
Yes
| withdrawn | Yes | ||
| S5‑196493 | Rel-16 CR 32.255 Adding I-SMF in PDU Session Charging message flow | Ericsson | CR | Agreement |
7.4.5Charging aspects of Enhancing Topology of SMF and UPF in 5G Networks
| Yes |
Yes
| revised | No | S5‑196729 | |
| S5‑196494 | Add Annex A Analysis of automation enablement use cases | Ericsson India Private Limited | pCR | Approval |
6.4.10Closed loop SLS Assurance
| No |
Yes
| withdrawn | Yes | ||
| S5‑196495 | Communication service assurance scenario | Ericsson India Private Limited | pCR | Agreement |
6.4.10Closed loop SLS Assurance
| Yes |
Yes
| not treated | No | ||
| S5‑196496 | Introduce definition of SLS | Ericsson India Private Limited | pCR |
6.4.10Closed loop SLS Assurance
| No |
Yes
| withdrawn | Yes | |||
| S5‑196497 | Correct definition of network resource | Ericsson Telecomunicazioni SpA | CR | Approval |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
YesSamsung: what is "intelligence" meaning here? The previous definition was OK.
Ericsson: the previous only talked about hardware. Samsung replied that there was no hardware mentioned in there.
Nokia: the NOTE is actually the definition of network resource. Huawei supported this and added that information was a too wide concept.
Deutsche Telekom didn’t agree with the wording of the Note.
Intel, Orange: management of MnS is implied here.
Zou Lan (Huawei) suggested to check this definition in other 3GPP groups since it was a very common term.
| revised | No | S5‑196594 | |
| S5‑196498 | Correct definition of network resource | Ericsson Telecomunicazioni SpA | CR | Approval |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196595 | |
| S5‑196499 | Proposal for revised SA5 ToR | Ericsson Telecomunicazioni SpA | other | Agreement |
5.1Administrative issues at SA5 level
| Yes |
YesAnatoly (Nokia) asked at what level the ToR was to be approved. It was replied that this would have to be sent to SA.
| revised | No | S5‑196576 | |
| S5‑196500 | New WID on management of MDT in 5G | Ericsson Telecomunicazioni SpA | WID new | Agreement |
6.2New OAM&P Work Item proposals
| Yes |
YesHuawei: if this is for release 16, we should adjust the scope for this release and then leave some work for release 17.
| revised | No | S5‑196584 | |
| S5‑196501 | pCR TR28.809 Add concept for Management Data Analytics | NEC Corporation | pCR | Approval |
6.5.5Study on enhancement of Management Data Analytics Service
| Yes |
Yes
| merged | No | S5‑196812 | |
| S5‑196502 | Correction of NR definition to avoid misalignment with RAN2 | Ericsson Telecomunicazioni SpA | CR | Agreement |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
YesEricsson commented that the content had been agreed in the last meeting but the spec number on the cover was wrong and it was not possible to implement it.
| agreed | No | ||
| S5‑196503 | Add streaming format for Trace | Ericsson Telecomunicazioni SpA | CR | Approval |
6.4.11Streaming trace reporting
| Yes |
Yes
| not pursued | No | ||
| S5‑196504 | pCR R16 28.405-080 Correcting UE request session id | Ericsson Telecomunicazioni SpA | pCR | Agreement |
6.4.1Management of QoE measurement collection
| Yes |
Yes
| approved | No | ||
| S5‑196505 | Correcting recording session id | Ericsson Telecomunicazioni SpA | pCR | Agreement |
6.4.1Management of QoE measurement collection
| Yes |
Yes
| approved | No | ||
| S5‑196506 | Discussion paper on Integration of ONAP and 3GPP 5G management WoW | Ericsson Telecomunicazioni SpA | discussion | Endorsement |
6.4.9Integration of ONAP and 3GPP 5G management framework
| Yes |
Yes
| noted | No | ||
| S5‑196507 | LS on 3GPP – ONAP Cooperation & WoW | Ericsson Telecomunicazioni SpA | LS out | Agreement |
5.3Liaison statements at SA5 level
| Yes |
Yes
| revised | No | S5‑196792 | |
| S5‑196508 | LS from NGMN to SA5 on 5G End-to-End Architecture Framework | NGMN | LS in |
5.3Liaison statements at SA5 level
| Yes |
Yes
| replied to | No | |||
| S5‑196509 | LS from CT4 ccSA5 on ExternalDoc version number change enhancement to 21.900 | C4-193801 | LS in |
5.3Liaison statements at SA5 level
| Yes |
YesMaryse(Nokia) commented that this affected Charging specifications and it had been taken into account already.
| noted | No | |||
| S5‑196510 | LS from GSMA NEST to SA5 on End-to-End Network Slicing Gap analysis | GSMA | LS in |
6.1OAM&P Plenary
| Yes |
YesNokia: This shows that our specs are not user friendly. The gaps referred here are not gaps but the structure of the SA5 specifications.A reply was agreed in 580.
| replied to | No | |||
| S5‑196511 | LS from ETSI NFV to SA5 on ETSI completes work on YANG models for Virtualised Network Function and Network Services Descriptor specification | ETSI ISG NFV | LS in |
6.1OAM&P Plenary
| Yes |
Yes
| noted | No | |||
| S5‑196512 | LS on O-RAN Alliance & 3GPP Coordination on O-RAN Alliance Outputs | O-RAN Alliance | LS in |
5.3Liaison statements at SA5 level
| Yes |
YesEdwin (Ericsson) commented that WG8 had an impact on SA5.The split described there was not clear and it was a depart from SA5's work. Anatoly (Nokia) commented that the model in O-RAN was different and there was no request to align 3GPP NRM and O-RAN. The concern from Ericsson was not relevant since there was no specific demand on aligning anything.
This was taken offline to decide whether a response was needed.
It was decided to note it and answer to the LS that was received late during the meeting (to be treated in the next meeting).
| noted | No | |||
| S5‑196513 | Reply LS to “O-RAN Alliance & 3GPP Coordination on O-RAN Alliance Outputs” | SP-190947 | LS in |
5.3Liaison statements at SA5 level
| Yes |
Yes
| noted | No | |||
| S5‑196514 | LS from RAN1 on response to SA5 LS on clarification of OAM requirements for RIM | R1-1909904 | LS in |
6.4.7NRM enhancements
| Yes |
Yes
| noted | No | |||
| S5‑196515 | LS from RAN2 ccSA5 on System Impacts of NR-U | R2-1911533 | LS in |
7.1Charging Plenary
| Yes |
Yes
| noted | No | |||
| S5‑196516 | LS on alignment between SA5 and RAN2 on L2 measurements | R2-1911841 | LS in |
6.4.5Enhancement of performance assurance for 5G networks including network slicing
| Yes |
Yes
| replied to | No | |||
| S5‑196517 | LS from RAN3 Reply on radio resource management policy | R3-194550 | LS in |
6.4.7NRM enhancements
| Yes |
Yes
| postponed | No | |||
| S5‑196518 | LS from RAN2 to SA5 on radio resource management policy | R2-1911791 | LS in |
6.4.7NRM enhancements
| Yes |
Yes
| postponed | No | |||
| S5‑196519 | LS from RAN3 Reply on Data activity reporting | R3-194572 | LS in |
6.1OAM&P Plenary
| Yes |
Yes
| noted | No | |||
| S5‑196520 | Ls from RAN3 Reply on User Data Congestion Analytics | R3-194749 | LS in |
6.5.5Study on enhancement of Management Data Analytics Service
| Yes |
Yes
| postponed | No | |||
| S5‑196521 | LS from RAN3 ccSA5 on the IAB-indication to core network | R3-194787 | LS in |
6.1OAM&P Plenary
| Yes |
Yes
| noted | No | |||
| S5‑196522 | Reply LS from SA6 ccSA5 on 3GPP SA6 Study on Edge Computing | S6-191841 | LS in |
5.3Liaison statements at SA5 level
| Yes |
YesSamsung: Bullet 2 refers to SA5. Samsung asked if there was any work on network management for Edge Computing in SA5? The Chair replied that there had been a study and it was completed without a conclusion for future normative work.
Nokia suggested to reply clarifying that there had been a study already.
Intel added that stating that there would be no normative work was a negative statement. Any work could be added with CRs under the current NRM work item. MCC clarified that the NRM WID would have to be revised in order to change its scope to add the MEC work. ORANGE also commented that a new WID could also cover the work with CRs.
| postponed | No | |||
| S5‑196523 | Liaison from ETSI ISG ZSM to 3GPP SA5 Network slicing performance assurance and fault management | ETSI ISG ZSM | LS in |
6.1OAM&P Plenary
| Yes |
YesHuawei: they are asking for general information on slicing, so we can reply in this meeting.
| replied to | No | |||
| S5‑196524 | Rel-16 CR 32.291 Add nssai query parameter | Amdocs Software Systems Ltd | CR | Approval |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| postponed | No | ||
| S5‑196525 | New WID CCS-controlled Quota Management in Nchf Converged Charging | Amdocs Software Systems Ltd | WID new | Approval |
7.2New Charging Work Item proposals
| Yes |
Yes
| revised | No | S5‑196544 | |
| S5‑196526 | Rel-15 CR 32.291 Correction of nfIdentification in yaml | Ericsson | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196721 | |
| S5‑196527 | Resubmitted Reply LS from RAN2 to SA5 on the user plane latency measurement | R2-1908144 | LS in |
6.1OAM&P Plenary
| Yes |
Yes
| noted | No | |||
| S5‑196528 | Resubmitted LS from GSMA to SA2 and SA5 on VoWiFi – VoLTE handover | GSMA | LS in |
7.1Charging Plenary
| Yes |
Yes
| postponed | No | |||
| S5‑196529 | Resubmitted LS from ITU-T to SA5 on cooperation on methodology harmonization and REST-based network management framework (reply to 3GPPTSGSA5-S5-185553 and 3GPP TSG SA5 - S5-187340) | ITU-T SG2 | LS in |
6.1OAM&P Plenary
| Yes |
YesThe Chair commented that ITU-T had asked him to send a reply before December.
A draft reply would be done for the next meeting.
| postponed | No | |||
| S5‑196530 | Rel-16 pCR 32.256 Corrections from EditHelp | Nokia, Nokia Shanghai Bell | pCR | Approval |
7.4.3Charging AMF in 5G System Architecture Phase 1
| Yes |
Yes
| approved | No | ||
| S5‑196531 | Sequence of pCR discussion | Intel Corporation (UK) Ltd | other | Approval |
6.4.13Self-Organizing Networks (SON) for 5G networks
| Yes |
Yes
| noted | No | ||
| S5‑196532 | Sequence of pCR discussion | Intel Corporation (UK) Ltd | other | Approval |
6.5.2Study on Self-Organizing Networks (SON) for 5G
| Yes |
Yes
| noted | No | ||
| S5‑196533 | Discussion on choices for 28.311 Solution Set | China Mobile Com. Corporation | discussion | Agreement |
6.4.3Network policy management for mobile networks based on NFV scenarios
| Yes |
Yes
| revised | No | S5‑196657 | |
| S5‑196534 | Rel-15 CR 32.291 Alignement with TS 29.501 template | Nokia, Nokia Shanghai Bell | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196722 | |
| S5‑196535 | Rel-16 CR 32.291 Alignement with TS 29.501 template | Nokia, Nokia Shanghai Bell | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196723 | |
| S5‑196536 | Sequence proposal for 6.4.1 | Ericsson | other |
6.4.1Management of QoE measurement collection
| Yes |
Yes
| noted | No | |||
| S5‑196537 | Rel-16 pCR 28.812 Solution for CSI deployemnt at the edge | Samsung Electronics France SA | pCR | Agreement |
6.4.4Intent driven management service for mobile networks
| Yes |
Yes
| not treated | No | S5‑196364 | |
| S5‑196538 | RP-192295 SA5 work areas with potential RAN impact (SA5 contribution to RAN#85 plenary) | Ericsson | other | Information |
4.3Inter-organizational reports
| Yes |
Yes
| noted | No | ||
| S5‑196539 | Rel-16 CR 28.532 Repair broken links in References | AT&T, Deutsche Telekom, Orange | CR | Agreement |
6.4.9Integration of ONAP and 3GPP 5G management framework
| Yes |
Yes
| not treated | No | ||
| S5‑196540 | LS/r on Energy Efficiency on 5G (3GPP TSG SA5-S5-195667) | ITU-T SG5 | LS in | discussion |
6.4.2Energy Efficiency of 5G
| Yes |
Yes
| postponed | No | ||
| S5‑196541 | IPR and legal declaration | WG Chairman | other | - |
3IPR and legal declaration
| Yes |
Yes
| noted | No | S5‑196001 | |
| S5‑196542 | New WID Charging Access Traffic Steering, Switching and Splitting in 5G system architecture | Nokia, Nokia Shanghai Bell | WID new | - |
7.2New Charging Work Item proposals
| Yes |
Yes
| agreed | No | S5‑196057 | |
| S5‑196543 | NWI on Charging for 5WWC | Huawei Telecommunication India | WID new | Agreement |
7.2New Charging Work Item proposals
| Yes |
Yes
| agreed | No | S5‑196167 | |
| S5‑196544 | New WID CCS-controlled Quota Management in Nchf Converged Charging | Amdocs Software Systems Ltd | WID new | Approval |
7.2New Charging Work Item proposals
| Yes |
Yes
| agreed | No | S5‑196525 | |
| S5‑196545 | Rel-16 CR 32.291 Adding Exposure Function Northbound API Specified Data Type | Ericsson | CR | Agreement |
7.4.2Network Exposure Charging in 5G System Architecture
| Yes |
Yes
| agreed | No | S5‑196384 | |
| S5‑196546 | Rel-16 CR 32.260 IMS Charging architecture introduction | Huawei | CR | Agreement |
7.4.4IMS Charging in 5G System Architecture
| Yes |
Yes
| agreed | No | S5‑196138 | |
| S5‑196547 | Rel-16 CR 32.275 Addition of convergent flows | Ericsson | CR | Agreement |
7.4.4IMS Charging in 5G System Architecture
| Yes |
Yes
| agreed | No | S5‑196385 | |
| S5‑196548 | Rel-16 CR 32.281 Addition of convergent flows | Ericsson | CR | Agreement |
7.4.4IMS Charging in 5G System Architecture
| Yes |
Yes
| agreed | No | S5‑196386 | |
| S5‑196549 | Rel-16 pCR TR 32.845 Conclusion on Business to Consumer | Huawei | pCR | Agreement |
7.5.1Study on Charging Aspects of Network Slicing
| Yes |
Yes
| approved | No | S5‑196131 | |
| S5‑196550 | Rel-16 pCR TR 32.845 Conclusion on event based charging | Huawei | pCR | Agreement |
7.5.1Study on Charging Aspects of Network Slicing
| Yes |
Yes
| approved | No | S5‑196132 | |
| S5‑196551 | Rel-16 pCR TR 32.845 Conclusion on solution 1.6 | Huawei | pCR | Agreement |
7.5.1Study on Charging Aspects of Network Slicing
| Yes |
Yes
| approved | No | S5‑196133 | |
| S5‑196552 | Rel-16 pCR TR 32.845 Relocate the conclusion of topic 1 | Huawei,Openet | pCR | Agreement |
7.5.1Study on Charging Aspects of Network Slicing
| Yes |
Yes
| approved | No | S5‑196134 | |
| S5‑196553 | Rel-16 pCR TR 32.845 Correction on the editorial Comments | Huawei | pCR | - |
7.5.1Study on Charging Aspects of Network Slicing
| Yes |
Yes
| approved | No | S5‑196161 | |
| S5‑196554 | Rel-16 pCR TS 28.201 Update of the Skeleton | Huawei | pCR | Agreement |
7.4.6Network Slice Performance and Analytics Charging in 5G System
| Yes |
Yes
| approved | No | S5‑196135 | |
| S5‑196555 | Rel-16 pCR TS 28.201 Scope | Huawei | pCR | Agreement |
7.4.6Network Slice Performance and Analytics Charging in 5G System
| Yes |
Yes
| approved | No | S5‑196136 | |
| S5‑196556 | Rel-16 pCR 28.201 Architecture considerations | Ericsson | pCR | Agreement |
7.4.6Network Slice Performance and Analytics Charging in 5G System
| Yes |
Yes
| noted | No | S5‑196387 | |
| S5‑196557 | Rel-16 pCR 32.256 Update triggers description | Nokia, Nokia Shanghai Bell | pCR | Approval |
7.4.3Charging AMF in 5G System Architecture Phase 1
| Yes |
Yes
| approved | No | S5‑196246 | |
| S5‑196558 | Rel-16 pCR 32.256 Solve Editor's Note for UE Presence in Presence Reporting Area (PRA) | Nokia, Nokia Shanghai Bell | pCR | Approval |
7.4.3Charging AMF in 5G System Architecture Phase 1
| Yes |
Yes
| approved | No | S5‑196247 | |
| S5‑196559 | Rel-16 pCR 32.256 Introduce Roaming | Nokia, Nokia Shanghai Bell | pCR | Approval |
7.4.3Charging AMF in 5G System Architecture Phase 1
| Yes |
Yes
| approved | No | S5‑196249 | |
| S5‑196560 | Rel-16 pCR 32.256 Update message content | Nokia, Nokia Shanghai Bell | pCR | Approval |
7.4.3Charging AMF in 5G System Architecture Phase 1
| Yes |
Yes
| approved | No | S5‑196250 | |
| S5‑196561 | Rel-16 pCR 32.256 Add Detailed message format | Nokia, Nokia Shanghai Bell | pCR | Approval |
7.4.3Charging AMF in 5G System Architecture Phase 1
| Yes |
Yes
| approved | No | S5‑196251 | |
| S5‑196562 | Rel-16 pCR 32.256 Introduce CHF CDR description for AMF | Nokia, Nokia Shanghai Bell | pCR | Approval |
7.4.3Charging AMF in 5G System Architecture Phase 1
| Yes |
Yes
| approved | No | S5‑196252 | |
| S5‑196563 | Draft TS 32.256 | Nokia, Nokia Shanghai Bell | draft TS | Approval |
7.4.3Charging AMF in 5G System Architecture Phase 1
| No |
Yes
| left for email approval | No | ||
| S5‑196564 | Draft TS 28.201 | Huawei | draft TS | Approval |
7.4.6Network Slice Performance and Analytics Charging in 5G System
| No |
Yes
| left for email approval | No | ||
| S5‑196565 | Rel-15 CR 32.291 Add the Service Specification information | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | S5‑196059 | |
| S5‑196566 | Rel-16 CR 32.291 Add the Service Specification information | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | S5‑196107 | |
| S5‑196567 | Rel-15 CR 32.298 Add the Service Specification information | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | S5‑196060 | |
| S5‑196568 | Rel-16 CR 32.298 Add the Service Specification information | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | S5‑196108 | |
| S5‑196569 | Rel-15 CR 32.255 Add the QNC support | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | S5‑196064 | |
| S5‑196570 | Rel-16 CR 32.255 Add the QNC support | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | S5‑196111 | |
| S5‑196571 | Rel-15 CR 32.291 Add the QNC support | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | S5‑196065 | |
| S5‑196572 | LS reply from 3GPP SA5 to NGMN on 5G End-to-End Architecture Framework | HUAWEI TECHNOLOGIES Co. Ltd. | LS out | - |
5.3Liaison statements at SA5 level
| Yes |
YesEricsson didn’t agree with the mapping part.
| revised | No | S5‑196765 | S5‑196173 |
| S5‑196573 | Notes of OAM sessions from the vice Chair | Huawei | other | Information |
6.1OAM&P Plenary
| Yes |
Yes
| noted | No | ||
| S5‑196574 | Reply to: Reply LS from SA6 ccSA5 on 3GPP SA6 Study on Edge Computing | Samsung | LS out | approval |
5.3Liaison statements at SA5 level
| No |
Yes
| withdrawn | Yes | ||
| S5‑196575 | Discussion on supporting end-to-end slicing management | AsiaInfo, CMCC | discussion | Endorsement |
6.2New OAM&P Work Item proposals
| Yes |
Yes
| noted | No | ||
| S5‑196576 | Proposal for revised SA5 ToR | Ericsson Telecomunicazioni SpA | discussion | Endorsement |
5.1Administrative issues at SA5 level
| Yes |
YesMore input is welcome for the next meeting.
| endorsed | No | S5‑196499 | |
| S5‑196577 | Add new NRM fragment supporting resource allocation and deallocation | Nokia | CR | Agreement |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| not pursued | No | ||
| S5‑196578 | Update allocation and deallocation specification due to new NRM fragment for resource allocation and deallocation | Nokia | CR | Agreement |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| not pursued | No | ||
| S5‑196579 | SA5 Summary of OAM WIs/SIs and Work Plan | WG Vice Chair (Huawei) | other | Endorsement |
6.1OAM&P Plenary
| Yes |
YesThe SA5 OAM time plan has a summary on slide 18 for the way forward. There were no objections to this.
| noted | No | S5‑196168 | |
| S5‑196580 | Reply to: LS from GSMA NEST to SA5 on End-to-End Network Slicing Gap analysis | Nokia | LS out | approval |
6.1OAM&P Plenary
| Yes |
Yes
| revised | No | S5‑196821 | |
| S5‑196581 | Reply to: Liaison from ETSI ISG ZSM to 3GPP SA5 Network slicing performance assurance and fault management | Huawei | LS out | approval |
6.1OAM&P Plenary
| Yes |
YesNokia: add MDAS and SON work items.
Intel: don’t mention Release 16 here.
| revised | No | S5‑196819 | |
| S5‑196582 | New WID network policy management for 5G mobile networks based on NFV scenarios | China Mobile Com. Corporation | WID new | Agreement |
6.2New OAM&P Work Item proposals
| Yes |
Yes
| revised | No | S5‑196854 | S5‑196272 |
| S5‑196583 | New SID on network slice management enhancements | Huawei | SID new | Agreement |
6.2New OAM&P Work Item proposals
| Yes |
Yes
| revised | No | S5‑196881 | S5‑196297 |
| S5‑196584 | New WID on management of MDT in 5G | Ericsson Telecomunicazioni SpA | WID new | Agreement |
6.2New OAM&P Work Item proposals
| Yes |
Yes
| agreed | No | S5‑196500 | |
| S5‑196585 | Rel-16 CR TS 28.552 Add Registered subscribers related measurements for AMF | China Mobile Com. Corporation | CR | Approval |
6.4.5Enhancement of performance assurance for 5G networks including network slicing
| Yes |
Yes
| not pursued | No | S5‑196163 | |
| S5‑196586 | Rel-16 CR TS 28.552 Add Unregistered subscribers measurements for UDM | China Mobile Com. Corporation | CR | Approval |
6.4.5Enhancement of performance assurance for 5G networks including network slicing
| Yes |
Yes
| agreed | No | S5‑196165 | |
| S5‑196587 | Add missing (E-UTRAN) cell and freq relation | Ericsson Inc.,Huawei | CR | Approval |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | S5‑196153 | |
| S5‑196588 | Add missing stage 3 CORBA/IDL solution | Ericsson LM | CR | Approval |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | S5‑196156 | |
| S5‑196589 | Add missing (E-UTRAN) cell and freq relation | Ericsson, Huawei | CR | Approval |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | S5‑196305 | |
| S5‑196590 | Add missing stage 3 CORBA/IDL solution | Ericsson LM | CR | Approval |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | S5‑196308 | |
| S5‑196591 | To syn up with v1540 stage 2 | Ericsson, Huawei | CR | Approval |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | S5‑196243 | |
| S5‑196592 | Rel-15 CR TS 28.622 update the definition of attribute measurementsList | ZTE Corporation, Ericsson | CR | Agreement |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| No |
Yes
| withdrawn | Yes | ||
| S5‑196593 | Rel-16 CR TS 28.622 Add measurementsList attribute into related IOCs | ZTE Corporation, Ericsson | CR | Agreement |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| No |
Yes
| withdrawn | Yes | ||
| S5‑196594 | Correct definition of network resource | Ericsson Telecomunicazioni SpA | CR | Approval |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196827 | S5‑196497 |
| S5‑196595 | Correct definition of network resource | Ericsson Telecomunicazioni SpA | CR | Approval |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196828 | S5‑196498 |
| S5‑196596 | Correct use of ProxyCellList | Ericsson LM | CR | Approval |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | S5‑196159 | |
| S5‑196597 | Rel-15 CR TS 28.541 Correct the parameter sNSSAIList | Huawei | CR | Agreement |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| not pursued | No | S5‑196220 | |
| S5‑196598 | Add support of Configurable FM | Ericsson LM | CR | Approval |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| not pursued | No | S5‑196304 | |
| S5‑196599 | Add missing definition for matching-criteria-attributes | Ericsson LM | CR | Approval |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| not treated | No | S5‑196367 | |
| S5‑196600 | Rel-15 CR TS 28.541 Add NRM Info Model definitions for beam managed object classes | Pivotal Commware, ZTE, Intel, P.I. Works, China Mobile, Verizon, BT, AT&T, Cisco, Deutsche Telekom | CR | Agreement |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196845 | S5‑196482 |
| S5‑196601 | Rel-15 CR TS 28.541 Stage 3 Add NRM Info Model definitions for beam managed object classes | Pivotal Commware, ZTE, Intel, P.I. Works, China Mobile, Verizon, BT, AT&T, Cisco, Deutsche Telekom | CR | Agreement |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| No |
Yes
| withdrawn | Yes | ||
| S5‑196602 | Correct Import table | Ericsson Inc. | CR | Approval |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | S5‑196154 | |
| S5‑196603 | Correct Import table | Ericsson Inc. | CR | Approval |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | S5‑196160 | |
| S5‑196604 | Reply to: LS on alignment between SA5 and RAN2 on L2 measurements | Intel | LS out | approval |
6.4.5Enhancement of performance assurance for 5G networks including network slicing
| Yes |
Yes
| revised | No | S5‑196841 | |
| S5‑196605 | Double S1/NG discussion in relation to retainability | Nokia Solutions & Networks (I) | discussion | Endorsement |
6.4.5Enhancement of performance assurance for 5G networks including network slicing
| Yes |
Yes
| endorsed | No | S5‑196043 | |
| S5‑196606 | Add new Use case related to extended 5QI 1 QoS Flow establishment via Initial Context Setup into A30 | Nokia Solutions & Networks (I) | CR | Agreement |
6.4.5Enhancement of performance assurance for 5G networks including network slicing
| Yes |
Yes
| revised | No | S5‑196836 | S5‑196044 |
| S5‑196607 | Add new measurements related to QoS Flow Setup via Initial Context Setup | Nokia Solutions & Networks (I) | CR | Agreement |
6.4.5Enhancement of performance assurance for 5G networks including network slicing
| Yes |
Yes
| revised | No | S5‑196837 | S5‑196045 |
| S5‑196608 | Add new Use case related to QCI1 E-RAB establishment via Initial Context Setup into A2 | Nokia Solutions & Networks (I) | CR | Agreement |
6.4.5Enhancement of performance assurance for 5G networks including network slicing
| Yes |
Yes
| revised | No | S5‑196838 | S5‑196046 |
| S5‑196609 | Add new Use case related to extended 5QI 1 QoS Flow Retainability monitoring into A30 | Nokia Solutions & Networks (I) | CR | Agreement |
6.4.5Enhancement of performance assurance for 5G networks including network slicing
| Yes |
Yes
| agreed | No | S5‑196047 | |
| S5‑196610 | Rel-16 CR 28.552 Add measurements related to QoS flow modification in NG-RAN | Intel Finland Oy | CR | Agreement |
6.4.5Enhancement of performance assurance for 5G networks including network slicing
| Yes |
Yes
| not treated | No | S5‑196338 | |
| S5‑196611 | Add scope | Ericsson India Private Limited,Deutsche Telekom | pCR | Agreement |
6.4.10Closed loop SLS Assurance
| Yes |
Yes
| approved | No | S5‑196480 | |
| S5‑196612 | Add introduction | Ericsson India Private Limited,Deutsche Telekom | pCR | Agreement |
6.4.10Closed loop SLS Assurance
| Yes |
Yes
| approved | No | S5‑196475 | |
| S5‑196613 | Introduce table of content | Ericsson India Private Limited | pCR | Agreement |
6.4.10Closed loop SLS Assurance
| No |
Yes
| withdrawn | Yes | ||
| S5‑196614 | pCR 28.535 Add introduction to concepts and background | Ericsson India Private Limited,Deutsche Telekom | pCR | Agreement |
6.4.10Closed loop SLS Assurance
| Yes |
Yes
| approved | No | S5‑196474 | |
| S5‑196615 | Add lifecycle of a communication service | Ericsson India Private Limited,Deutsche Telekom | pCR | Agreement |
6.4.10Closed loop SLS Assurance
| Yes |
Yes
| approved | No | S5‑196476 | |
| S5‑196616 | Rel-16 CR TS 28.533 Update Clause A.7 Utilization of management data analystic services | Huawei | CR | Agreement |
6.4.10Closed loop SLS Assurance
| No |
Yes
| withdrawn | Yes | ||
| S5‑196617 | Rel-16 CR TS 28.533 Add the description of data analytics utilization in closed loop SLA assurance | HUAWEI TECHNOLOGIES Co. Ltd. | CR | Agreement |
6.4.10Closed loop SLS Assurance
| Yes |
Yes
| revised | No | S5‑196850 | |
| S5‑196618 | Draft TS 28.535 | Ericsson | draft TS | Approval |
6.4.10Closed loop SLS Assurance
| No |
Yes
| left for email approval | No | ||
| S5‑196619 | Communication service assurance business use case and requirements | Ericsson India Private Limited,Deutsche Telekom | pCR | Agreement |
6.4.10Closed loop SLS Assurance
| Yes |
Yes
| approved | No | S5‑196481 | |
| S5‑196620 | Rel-16 CR 28.541 Add relation of GST and profiles | Huawei, China Mobile | CR | Approval |
6.4.15Management Aspects of 5G Service-Level Agreement
| Yes |
Yes
| revised | No | S5‑196867 | S5‑196345 |
| S5‑196621 | Rel-15 CR 32.291 Add the QNC support | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | S5‑196112 | |
| S5‑196622 | Rel-15 CR 32.291 Clarify the QoS change trigger | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | S5‑196066 | |
| S5‑196623 | Rel-16 CR 32.291 Clarify the QoS change trigger | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | S5‑196113 | |
| S5‑196624 | Rel-15 CR 32.255 correction of PCC rules description | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | S5‑196068 | |
| S5‑196625 | Rel-16 CR 32.255 correction of PCC rules description | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | S5‑196115 | |
| S5‑196626 | Rel-15 CR 32.290 Correction of notify response | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| postponed | No | S5‑196070 | |
| S5‑196627 | Rel-16 CR 32.290 Correction of notify response | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| postponed | No | S5‑196117 | |
| S5‑196628 | Rel-15 CR 32.291 Correction of notify response | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| postponed | No | S5‑196071 | |
| S5‑196629 | Rel-16 CR 32.291 Correction of notify response | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| postponed | No | S5‑196118 | |
| S5‑196630 | Rel-15 CR 32.291 Correction of ChargingDataResponse description | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| postponed | No | S5‑196072 | |
| S5‑196631 | Rel-16 CR 32.291 Correction of ChargingDataResponse description | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| postponed | No | S5‑196119 | |
| S5‑196632 | Rel-15 CR 32.290 Correction of ChargingNotifyResponse description | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | ||
| S5‑196633 | Rel-16 CR 32.290 Correction of ChargingNotifyResponse description | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | ||
| S5‑196634 | Rel-15 CR 32.291 Correction of Nchf_ConvergedCharging_Release operation | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | S5‑196073 | |
| S5‑196635 | Rel-16 CR 32.291 Correction of Nchf_ConvergedCharging_Release operation | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | S5‑196120 | |
| S5‑196636 | Rel-15 CR 32.255 Correction of reportTime | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | S5‑196074 | |
| S5‑196637 | Rel-15 CR 32.298 Correct inconsistent CHF CDR parameter | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | S5‑196075 | |
| S5‑196638 | Rel-16 CR 32.298 Correct inconsistent CHF CDR parameter | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | S5‑196122 | |
| S5‑196639 | Rel-15 CR 32.255 Add the sponsor based charging | Huawei | CR | Discussion |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | S5‑196077 | |
| S5‑196640 | Rel-16 CR 32.255 Add the sponsor based charging | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | S5‑196124 | |
| S5‑196641 | Rel-16 CR TS 28.540 Add GSMA GST mapping related requirements | Huawei, China Mobile,Nokia | CR | Approval |
6.4.15Management Aspects of 5G Service-Level Agreement
| Yes |
Yes
| agreed | No | S5‑196342 | |
| S5‑196642 | Rel-16 CR TS 28.541 Update on slice model | Huawei, China Mobile, Nokia, Nokia Shanghai Bell | CR | Approval |
6.4.15Management Aspects of 5G Service-Level Agreement
| Yes |
YesDepending on stage 3 CR for the next meeting.
| conditionally agreed | No | S5‑196343 | |
| S5‑196643 | Add generic characters of GST in slice NRM - stage 2 | Nokia, Nokia Shanghai Bell | CR | Agreement |
6.4.15Management Aspects of 5G Service-Level Agreement
| No |
Yes
| withdrawn | Yes | ||
| S5‑196644 | Update CoverageArea attribute in service profile - stage 2 | Nokia, Nokia Shanghai Bell | CR | Agreement |
6.4.15Management Aspects of 5G Service-Level Agreement
| No |
Yes
| withdrawn | Yes | ||
| S5‑196645 | Draft TS 28.310 | Orange | draft TS | Approval |
6.4.2Energy Efficiency of 5G
| No |
Yes
| left for email approval | No | ||
| S5‑196646 | Update Intra-RAT energy saving scenario with distributed decision-making | Nokia | pCR | Approval |
6.4.2Energy Efficiency of 5G
| Yes |
Yes
| revised | No | S5‑196831 | S5‑196185 |
| S5‑196647 | pCR 28.310 Add requirements for energy saving cell overlaid cases | Huawei, Orange | pCR | Approval |
6.4.2Energy Efficiency of 5G
| Yes |
Yes
| approved | No | S5‑196348 | |
| S5‑196648 | Update use case on Automatic Cell Clustering for Energy Management | Nokia | pCR | Approval |
6.4.2Energy Efficiency of 5G
| Yes |
Yes
| not treated | No | ||
| S5‑196649 | pCR 28.310 Add overview for various energy saving solutions | Huawei, Orange | pCR | Approval |
6.4.2Energy Efficiency of 5G
| Yes |
Yes
| approved | No | S5‑196351 | |
| S5‑196650 | Add Rollback operation to intent Lifecycle management | Nokia | pCR | Approval |
6.4.4Intent driven management service for mobile networks
| Yes |
Yes
| approved | No | S5‑196186 | |
| S5‑196651 | pCR 28.812 Add intent driven coverage optimization scenario | Huawei | pCR | Approval |
6.4.4Intent driven management service for mobile networks
| Yes |
Yes
| revised | No | S5‑196833 | S5‑196206 |
| S5‑196652 | Draft TR 28.812 | Huawei | draft TR | Approval |
6.4.4Intent driven management service for mobile networks
| No |
Yes
| left for email approval | No | ||
| S5‑196653 | pCR 28.812 Add the description of MnS component type C in the concept | Huawei | pCR | Approval |
6.4.4Intent driven management service for mobile networks
| Yes |
Yes
| approved | No | S5‑196210 | |
| S5‑196654 | pCR 28.812 Add the relation between IDMS and SON | Huawei | pCR | Approval |
6.4.4Intent driven management service for mobile networks
| Yes |
Yes
| revised | No | S5‑196835 | S5‑196211 |
| S5‑196655 | Revised WID network policy management for mobile networks based on NFV scenarios | China Mobile Com. Corporation | WID revised | Approval |
6.4.3Network policy management for mobile networks based on NFV scenarios
| Yes |
Yes
| revised | No | S5‑196834 | S5‑196273 |
| S5‑196656 | pCR 28.311 Add Information Object Classes | China Mobile Com. Corporation | pCR | Approval |
6.4.3Network policy management for mobile networks based on NFV scenarios
| Yes |
Yes
| noted | No | S5‑196274 | |
| S5‑196657 | Discussion on choices for 28.311 Solution Set | China Mobile Com. Corporation | discussion | Agreement |
6.4.3Network policy management for mobile networks based on NFV scenarios
| Yes |
Yes
| noted | No | S5‑196533 | |
| S5‑196658 | pCR 28.311 Add Solution Set(SS)definitions | China Mobile Com. Corporation | pCR | Approval |
6.4.3Network policy management for mobile networks based on NFV scenarios
| Yes |
Yes
| approved | No | S5‑196276 | |
| S5‑196659 | pCR 28.311 Add XML definition | China Mobile Com. Corporation | pCR | Approval |
6.4.3Network policy management for mobile networks based on NFV scenarios
| Yes |
Yes
| noted | No | S5‑196277 | |
| S5‑196660 | pCR 28.311 Add SOAP Solution Set | China Mobile Com. Corporation | pCR | Approval |
6.4.3Network policy management for mobile networks based on NFV scenarios
| Yes |
Yes
| noted | No | S5‑196278 | |
| S5‑196661 | DP Way forward of KPI reporting related MnS | ZTE Corporation, China Telecom | discussion | Endorsement |
6.4.12KPI reporting
| Yes |
Yes
| endorsed | No | S5‑196376 | |
| S5‑196662 | Rel-16 CR TS 28.550 Add UC and requirements for NF KPI job control | China Telecommunications, ZTE | CR | Agreement |
6.4.12KPI reporting
| Yes |
Yes
| revised | No | S5‑196853 | S5‑196389 |
| S5‑196663 | Rel-16 CR TS 28.550 Add UC and requirements for NSSI KPI job control | China Telecommunications, ZTE | CR | Agreement |
6.4.12KPI reporting
| No |
Yes
| withdrawn | Yes | ||
| S5‑196664 | pCR 28.808 Editorial corrections and requirement removals | TNO | pCR | Approval |
6.5.4Study on management and orchestration aspects with integrated satellite components in a 5G network
| Yes |
Yes
| approved | No | S5‑196441 | |
| S5‑196665 | pCR 28.808 Add use case for creation of a network slice instance associated with a Satellite RAN and a Terrestrial RAN | TNO | pCR | Approval |
6.5.4Study on management and orchestration aspects with integrated satellite components in a 5G network
| Yes |
Yes
| approved | No | S5‑196443 | |
| S5‑196666 | pCR 28.812 Update Intent Driven Object | Huawei | pCR | Approval |
6.4.4Intent driven management service for mobile networks
| Yes |
Yes
| approved | No | S5‑196212 | |
| S5‑196667 | Discussion paper about exposure governance | Huawei | discussion | Endorsement |
6.4.6Discovery of management services in 5G
| Yes |
Yes
| revised | No | S5‑196855 | S5‑196287 |
| S5‑196668 | Draft TS 28.405 | Ericsson | draft TS | Approval |
6.4.1Management of QoE measurement collection
| No |
Yes
| left for email approval | No | ||
| S5‑196669 | Draft TS 28.406 | Ericsson | draft TS | Approval |
6.4.1Management of QoE measurement collection
| No |
Yes
| left for email approval | No | ||
| S5‑196670 | pCR 28.812 Add solution for Intent driven NSI performance assurance scenario | Huawei | pCR | Approval |
6.4.4Intent driven management service for mobile networks
| Yes |
Yes
| noted | No | S5‑196208 | |
| S5‑196671 | draft TS 28313-000 | Intel Corporation (UK) Ltd | draft TS | Approval |
6.4.13Self-Organizing Networks (SON) for 5G networks
| Yes |
Yes
| approved | No | S5‑196192 | |
| S5‑196672 | pCR 28.313 skeleton | Intel Corporation (UK) Ltd | pCR | Approval |
6.4.13Self-Organizing Networks (SON) for 5G networks
| Yes |
Yes
| approved | No | S5‑196194 | |
| S5‑196673 | Organizing Self Organizing Specifications | Ericsson France S.A.S | discussion | Endorsement |
6.4.13Self-Organizing Networks (SON) for 5G networks
| Yes |
Yes
| endorsed | No | S5‑196414 | |
| S5‑196674 | pCR 28.313 introduction and scope | Intel Corporation (UK) Ltd | pCR | Approval |
6.4.13Self-Organizing Networks (SON) for 5G networks
| Yes |
Yes
| approved | No | S5‑196196 | |
| S5‑196675 | pCR 28.313 concepts | Huawei, Intel, China Telecommunications, Ericsson | pCR | Approval |
6.4.13Self-Organizing Networks (SON) for 5G networks
| Yes |
Yes
| approved | No | S5‑196198 | |
| S5‑196676 | Rel-15 32.255 Correction of Unit Count Inactivity Timer | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | S5‑196078 | |
| S5‑196677 | Rel-16 32.255 Correction of Unit Count Inactivity Timer | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | S5‑196125 | |
| S5‑196678 | Rel-15 CR 32.298 Correction of Correction of Network Function ID | Ericsson | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | S5‑196378 | |
| S5‑196679 | Rel-15 CR 32.298 Correction of Correction of Network Function ID | Ericsson | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | ||
| S5‑196680 | Rel-15 32.298 Correction of ASN.1 AMFID | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | S5‑196102 | |
| S5‑196681 | Rel-15 CR 32.290 Add clarifications to failure handling | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | S5‑196150 | |
| S5‑196682 | Rel-16 CR 32.290 Add clarifications to failure handling | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | S5‑196149 | |
| S5‑196683 | Rel-15 CR 32.274 Addition of Post Event Charging flows | Nokia, Nokia Shanghai Bell | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | S5‑196254 | |
| S5‑196684 | Rel-15 CR 32.274 Clarify CHF selection via NRF and roaming | Nokia, Nokia Shanghai Bell | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | S5‑196258 | |
| S5‑196685 | Rel-15 CR 32.274 Correction of Multiple Unit Information | Nokia, Nokia Shanghai Bell | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | S5‑196259 | |
| S5‑196686 | Rel-15 CR 32.291 Correction InvocationResult description and binding | Nokia, Nokia Shanghai Bell | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | S5‑196260 | |
| S5‑196687 | Rel-16 CR 32.291 Correction InvocationResult description and binding | Nokia, Nokia Shanghai Bell | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | S5‑196261 | |
| S5‑196688 | Draft TR 32.845 | Huawei | draft TR | Approval |
7.5.1Study on Charging Aspects of Network Slicing
| No |
Yes
| left for email approval | No | ||
| S5‑196689 | Rel-16 CR 32.291 Correction on OpenAPI for usedunitcontainer | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | S5‑196130 | |
| S5‑196690 | Rel-16 CR 32.255 Correction of Interworking flow | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | S5‑196148 | |
| S5‑196691 | Rel-16 CR 32.291 Add Retransmission IE for alignment with TS 32.290 | Nokia, Nokia Shanghai Bell | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | S5‑196257 | |
| S5‑196692 | Rel-16 CR 32.290 Clarify Retransmission IE | Nokia, Nokia Shanghai Bell | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | ||
| S5‑196693 | Rel-16 CR 32.290 Explanation of when Units Usage must be reported | Ericsson | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | S5‑196368 | |
| S5‑196694 | Rel-16 CR 32.290 Explanation of Units Usage in Initial | Ericsson | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | S5‑196369 | |
| S5‑196695 | Rel-16 CR 32.255 Correction of QoS Based Charging description | Ericsson | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | S5‑196373 | |
| S5‑196696 | pCR 28.313 RACH optimization use case | Intel Corporation (UK) Ltd,Ericsson | pCR | Approval |
6.4.13Self-Organizing Networks (SON) for 5G networks
| Yes |
Yes
| approved | No | S5‑196199 | |
| S5‑196697 | pCR 28.313 RACH optimization procedure | Intel Corporation (UK) Ltd,Ericsson | pCR | Approval |
6.4.13Self-Organizing Networks (SON) for 5G networks
| Yes |
Yes
| approved | No | S5‑196201 | |
| S5‑196698 | pCR 28.313 RACH optimization information | Intel Corporation (UK) Ltd,Ericsson | pCR | Approval |
6.4.13Self-Organizing Networks (SON) for 5G networks
| Yes |
Yes
| approved | No | S5‑196202 | |
| S5‑196699 | Extensions to PCF and UPF IOCs for support of TSC (Time Sensitive Communication) | Nokia | CR | Approval |
6.4.7NRM enhancements
| Yes |
Yes
| agreed | No | S5‑196187 | |
| S5‑196700 | Update Stage 2 SEPP definition in 5GC NRM | Nokia, Nokia Shanghai Bell | CR | Agreement |
6.4.7NRM enhancements
| Yes |
Yes
| revised | No | S5‑196843 | S5‑196455 |
| S5‑196701 | Add State Handling diagram for NF service | Nokia, Nokia Shanghai Bell | CR | Agreement |
6.4.7NRM enhancements
| Yes |
Yes
| agreed | No | ||
| S5‑196702 | Add Stage 2 SCP definition in 5GC NRM | Nokia, Nokia Shanghai Bell | CR | Agreement |
6.4.7NRM enhancements
| Yes |
Yes
| agreed | No | S5‑196459 | |
| S5‑196703 | Add Stage 2 NEF definition in 5GC NRM | Nokia, Nokia Shanghai Bell | CR | Agreement |
6.4.7NRM enhancements
| Yes |
Yes
| agreed | No | S5‑196457 | |
| S5‑196704 | Support communication model in 5GC NF - Stage 2 | Nokia, Nokia Shanghai Bell | CR | Agreement |
6.4.7NRM enhancements
| Yes |
Yes
| agreed | No | S5‑196461 | |
| S5‑196705 | Request email approval of Stage 3 YANG solution set | Ericsson | discussion | Endorsement |
6.1OAM&P Plenary
| Yes |
Yes
| noted | No | ||
| S5‑196706 | Shadow TS for Heartbeat Stage 1 | AT&T, Deutsche Telekom, Orange | other | Agreement |
6.4.9Integration of ONAP and 3GPP 5G management framework
| Yes |
Yes
| revised | No | S5‑196813 | S5‑196050 |
| S5‑196707 | Discussion paper on Heartbeat MnS specification approach | AT&T GNS Belgium SPRL | discussion | - |
6.4.9Integration of ONAP and 3GPP 5G management framework
| Yes |
Yes
| endorsed | No | S5‑196477 | |
| S5‑196708 | Rel-16 CR TS 32.421 Addition of streaming trace requirements | Nokia | CR | Approval |
6.4.11Streaming trace reporting
| Yes |
Yes
| agreed | No | S5‑196487 | |
| S5‑196709 | pCR 28.807 clean-up use case of NPN provisioning by a network slice of a PLMN | Huawei | pCR | Approval |
6.5.3Study on non-public networks management
| Yes |
Yes
| approved | No | S5‑196353 | |
| S5‑196710 | pCR 28.807 Update on general concept | Huawei | pCR | Approval |
6.5.3Study on non-public networks management
| Yes |
Yes
| approved | No | S5‑196352 | |
| S5‑196711 | pCR 28.807 Management of stand-alone non-public networks | Huawei | pCR | Approval |
6.5.3Study on non-public networks management
| Yes |
Yes
| approved | No | S5‑196354 | |
| S5‑196712 | pCR 28.807 Management of public network integrated NPN | Huawei | pCR | Approval |
6.5.3Study on non-public networks management
| Yes |
Yes
| approved | No | S5‑196355 | |
| S5‑196713 | pCR TR 28.807 Roles related to NPN management | TELEFONICA S.A. | pCR | Approval |
6.5.3Study on non-public networks management
| Yes |
Yes
| approved | No | S5‑196245 | |
| S5‑196714 | Rel-16 CR 32.255 Definition of Emergency Session handling | Ericsson | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | S5‑196374 | |
| S5‑196715 | Rel-16 CR 32.255 Missing default trigger for Offline only | Ericsson | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | S5‑196377 | |
| S5‑196716 | Rel-16 CR 32.291 Correction of yaml | Ericsson | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | S5‑196379 | |
| S5‑196717 | Rel-16 CR 32.290 Correction of Converged Charging principles | Ericsson | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | S5‑196382 | |
| S5‑196718 | Rel-16 CR 32.291 Correction of pDUSessionChargingInformation | Ericsson | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | S5‑196383 | |
| S5‑196719 | Rel-16 CR 32.298 Correction of missing otherQutaType in sMFTrigger | Ericsson | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | S5‑196415 | |
| S5‑196720 | Correction of missing otherQutaType in sMFTrigger | Ericsson | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | ||
| S5‑196721 | Rel-15 CR 32.291 Correction of nfIdentification in yaml | Ericsson | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | S5‑196526 | |
| S5‑196722 | Rel-15 CR 32.291 Alignement with TS 29.501 template | Nokia, Nokia Shanghai Bell | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | S5‑196534 | |
| S5‑196723 | Rel-16 CR 32.291 Alignement with TS 29.501 template | Nokia, Nokia Shanghai Bell | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | S5‑196535 | |
| S5‑196724 | Rel-16 CR 32.255 Add charging requirement for I-SMF | Huawei | CR | Agreement |
7.4.5Charging aspects of Enhancing Topology of SMF and UPF in 5G Networks
| Yes |
Yes
| agreed | No | S5‑196139 | |
| S5‑196725 | Rel-16 CR 32.255 Add charging principle for I-SMF | Huawei | CR | Agreement |
7.4.5Charging aspects of Enhancing Topology of SMF and UPF in 5G Networks
| Yes |
Yes
| agreed | No | S5‑196140 | |
| S5‑196726 | Rel-16 CR 32.255 Add charging trigger conditions for I-SMF | Huawei | CR | Agreement |
7.4.5Charging aspects of Enhancing Topology of SMF and UPF in 5G Networks
| Yes |
Yes
| agreed | No | S5‑196141 | |
| S5‑196727 | Rel-16 CR 32.255 Add I-SMF PDU session charging information | Huawei | CR | Agreement |
7.4.5Charging aspects of Enhancing Topology of SMF and UPF in 5G Networks
| Yes |
Yes
| agreed | No | S5‑196142 | |
| S5‑196728 | Rel-16 CR 32.255 Adding I-SMF in 5G data connectivity charging information | Ericsson | CR | Agreement |
7.4.5Charging aspects of Enhancing Topology of SMF and UPF in 5G Networks
| Yes |
Yes
| agreed | No | S5‑196431 | |
| S5‑196729 | Rel-16 CR 32.255 Adding I-SMF in PDU Session Charging message flow | Ericsson | CR | Agreement |
7.4.5Charging aspects of Enhancing Topology of SMF and UPF in 5G Networks
| Yes |
Yes
| agreed | No | S5‑196493 | |
| S5‑196730 | Rel-16 CR 32.255 Add the QoS Characteristics | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | S5‑196109 | |
| S5‑196731 | Rel-16 CR 32.291 Add the QoS Characteristics | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | S5‑196110 | |
| S5‑196732 | Rel-15 32.298 Correction of ASN.1 userLocationInformation | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | S5‑196103 | |
| S5‑196733 | Rel-16 32.298 Correction of ASN.1 userLocationInformation | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | S5‑196128 | |
| S5‑196734 | UC Deployment of a stand-alone NPN with 3GPP and non-3GPP segments | TELEFONICA S.A. | pCR | Approval |
6.5.3Study on non-public networks management
| Yes |
Yes
| approved | No | S5‑196322 | |
| S5‑196735 | pCR 28.807 Add use case of NPN provisioning by a stand-alone non-public network | Huawei | pCR | Approval |
6.5.3Study on non-public networks management
| No |
Yes
| withdrawn | Yes | ||
| S5‑196736 | pCR 28.807 Add use case of providing traffic management and monitoring capability to an NPN operator | Huawei | pCR | Approval |
6.5.3Study on non-public networks management
| Yes |
Yes
| approved | No | S5‑196358 | |
| S5‑196737 | pCR 28.807 Add requirements for management of public network integrated NPN | Huawei | pCR | Approval |
6.5.3Study on non-public networks management
| Yes |
Yes
| approved | No | S5‑196357 | |
| S5‑196738 | Draft TR 28.810 | China Mobile | draft TR | Approval |
6.5.6Study on autonomous network levels
| No |
Yes
| left for email approval | No | ||
| S5‑196739 | pCR 28.810 Add background | China Mobile, Huawei | pCR | Approval |
6.5.6Study on autonomous network levels
| Yes |
Yes
| revised | No | S5‑196878 | S5‑196324 |
| S5‑196740 | pCR 28.810 Add scope | China Mobile, Huawei | pCR | Approval |
6.5.6Study on autonomous network levels
| Yes |
Yes
| approved | No | S5‑196325 | |
| S5‑196741 | Add scope | Ericsson India Private Limited,Deutsche Telekom | pCR | Agreement |
6.4.10Closed loop SLS Assurance
| Yes |
Yes
| approved | No | S5‑196486 | |
| S5‑196742 | Add introduction | Ericsson India Private Limited,Deutsche Telekom | pCR | - |
6.4.10Closed loop SLS Assurance
| Yes |
Yes
| approved | No | S5‑196484 | |
| S5‑196743 | Draft TS 28.536 | Ericsson | draft TS | Approval |
6.4.10Closed loop SLS Assurance
| No |
Yes
| left for email approval | No | ||
| S5‑196744 | Introduce table of content | Ericsson India Private Limited | pCR | Agreement |
6.4.10Closed loop SLS Assurance
| Yes |
Yes
| approved | No | S5‑196490 | |
| S5‑196745 | Way of working for translation of GSMA GST/NEST | Ericsson | discussion | discussion |
6.4.15Management Aspects of 5G Service-Level Agreement
| Yes |
Yes
| not treated | No | ||
| S5‑196746 | pCR 28.313 MRO use case | Intel Corporation (UK) Ltd | pCR | Approval |
6.4.13Self-Organizing Networks (SON) for 5G networks
| Yes |
Yes
| revised | No | S5‑196857 | S5‑196203 |
| S5‑196747 | pCR 28.313 MRO procedure | Intel Corporation (UK) Ltd,Ericsson | pCR | Approval |
6.4.13Self-Organizing Networks (SON) for 5G networks
| Yes |
Yes
| approved | No | S5‑196204 | |
| S5‑196748 | Rel-16 CR TS 28.550 Add KPI job control service | ZTE Corporation, China Telecom | CR | Agreement |
6.4.12KPI reporting
| Yes |
Yes
| agreed | No | S5‑196409 | |
| S5‑196749 | pCR 28.313 MRO information | Intel Corporation (UK) Ltd | pCR | Approval |
6.4.13Self-Organizing Networks (SON) for 5G networks
| Yes |
Yes
| revised | No | S5‑196858 | S5‑196205 |
| S5‑196750 | pCR 28.313 Add MRO use cases and requriements | HUAWEI TECHNOLOGIES Co. Ltd. | pCR | Approval |
6.4.13Self-Organizing Networks (SON) for 5G networks
| Yes |
Yes
| not treated | No | S5‑196313 | |
| S5‑196751 | pCR 28.313 Add PCI configuration use case and requirements | HUAWEI TECHNOLOGIES Co. Ltd. | pCR | Approval |
6.4.13Self-Organizing Networks (SON) for 5G networks
| Yes |
Yes
| not treated | No | S5‑196310 | |
| S5‑196752 | pCR Add skeleton of draft TR 28.809 | Intel Finland Oy | pCR | Agreement |
6.5.5Study on enhancement of Management Data Analytics Service
| Yes |
Yes
| approved | No | S5‑196326 | |
| S5‑196753 | Rel-16 CR TS 28.530 Add concept descritipn for tenant information | Huawei | CR | Agreement |
6.4.14Enhancement of 3GPP management system for multiple tenant environment support
| Yes |
Yes
| agreed | No | S5‑196289 | |
| S5‑196754 | Rel-16 CR TS 28.533 Add concept descritipn for management capabiliy | Huawei | CR | Agreement |
6.4.14Enhancement of 3GPP management system for multiple tenant environment support
| Yes |
Yes
| agreed | No | S5‑196290 | |
| S5‑196755 | Rel-16 CR TS 28.550 Performance management service enhancement for tenant supporting | Huawei | CR | Agreement |
6.4.14Enhancement of 3GPP management system for multiple tenant environment support
| Yes |
Yes
| agreed | No | S5‑196293 | |
| S5‑196756 | Rel-16 CR TS 28.552 Performance measurement extension to support multiple tenants environment | Huawei | CR | Agreement |
6.4.14Enhancement of 3GPP management system for multiple tenant environment support
| Yes |
Yes
| agreed | No | S5‑196294 | |
| S5‑196757 | LS to GSMA on GST | Orange | LS out | Approval |
6.4.15Management Aspects of 5G Service-Level Agreement
| Yes |
Yes
| revised | No | S5‑196868 | |
| S5‑196758 | Rel-15 CR TS 28.532 Correct provisioning management service | Huawei,Orange | CR | Agreement |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | S5‑196227 | |
| S5‑196759 | Rel-16 CR TS 28.532 Correct provisioning management service | Huawei,Orange | CR | Agreement |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | S5‑196228 | |
| S5‑196760 | Rel-15 CR TS 28.532 Correct fault supervision management service | Huawei | CR | Agreement |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196823 | S5‑196229 |
| S5‑196761 | Rel-16 CR TS 28.532 Correct fault supervision management service | Huawei | CR | Agreement |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196824 | S5‑196230 |
| S5‑196762 | Rel-15 CR TS 28.533 Update of Management service description and diagram | Huawei | CR | Agreement |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196825 | S5‑196231 |
| S5‑196763 | Rel-16 CR TS 28.533 Update of Management service description and diagram | Huawei | CR | Agreement |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196826 | S5‑196232 |
| S5‑196764 | LS to SA5 and SA2 on 5G Cell ID(s) in the 3GPP SA5 billing system, related to Retained Data regulations | ETSI TC LI | LS in | discussion |
7.1Charging Plenary
| Yes |
Yes
| postponed | No | ||
| S5‑196765 | LS reply from 3GPP SA5 to NGMN on 5G End-to-End Architecture Framework | HUAWEI TECHNOLOGIES Co. Ltd. | LS out | - |
5.3Liaison statements at SA5 level
| No |
Yes
| left for email approval | No | S5‑196572 | |
| S5‑196766 | (reserved) | Charging SWG | other | discussion |
7.3Charging Maintenance and Rel-16 small Enhancements
| No |
Yes
| withdrawn | Yes | ||
| S5‑196767 | (reserved) | Charging SWG | other | discussion |
7.3Charging Maintenance and Rel-16 small Enhancements
| No |
Yes
| withdrawn | Yes | ||
| S5‑196768 | (reserved) | Charging SWG | other | discussion |
7.3Charging Maintenance and Rel-16 small Enhancements
| No |
Yes
| withdrawn | Yes | ||
| S5‑196769 | pCR 28.310 solution for energy saving | Intel Corporation (UK) Ltd | pCR | Approval |
6.4.2Energy Efficiency of 5G
| Yes |
Yes
| approved | No | S5‑196191 | |
| S5‑196770 | Rel-16 CR TS 28.554 Add 5G Energy Efficiency KPI | Huawei, Orange | CR | Approval |
6.4.2Energy Efficiency of 5G
| Yes |
Yes
| agreed | No | S5‑196346 | |
| S5‑196771 | LS to RAN3 on energy efficiency of 5G | Orange | LS out | Approval |
6.4.2Energy Efficiency of 5G
| No |
Yes
| left for email approval | No | S5‑196054 | |
| S5‑196772 | Rel-16 CR 28.552 Add measurements related to QoS flow setup via untrusted non-3GPP access | Intel Finland Oy | CR | Agreement |
6.4.5Enhancement of performance assurance for 5G networks including network slicing
| Yes |
Yes
| agreed | No | S5‑196339 | |
| S5‑196773 | Rel-16 CR 28.552 Add measurements related to QoS flow modification via untrusted non-3GPP access | Intel Finland Oy | CR | Agreement |
6.4.5Enhancement of performance assurance for 5G networks including network slicing
| Yes |
Yes
| agreed | No | S5‑196340 | |
| S5‑196774 | Rel-16 CR 28.552 Add measurements related to handover between 5GS and EPS via N26 interface | Intel Finland Oy | CR | Agreement |
6.4.5Enhancement of performance assurance for 5G networks including network slicing
| Yes |
Yes
| agreed | No | S5‑196341 | |
| S5‑196775 | Rel-16 CR TS 28.550 add clarification of the NSI and NSSI performance assurance | Huawei Telecommunication India | CR | Agreement |
6.4.5Enhancement of performance assurance for 5G networks including network slicing
| No |
Yes
| withdrawn | Yes | ||
| S5‑196776 | Rel-16 CR TS 28.552 Re-orgnize the structure of TS 28.552 | HUAWEI TECHNOLOGIES Co. Ltd. | CR | - |
6.4.5Enhancement of performance assurance for 5G networks including network slicing
| Yes |
YesIt was pointed out that this restructuring would affect the CRs for the next meeting and this CR had to be taken into account in order to avoid clashes.
| agreed | No | S5‑196411 | |
| S5‑196777 | Discussion on URI dynamic discovery | Huawei | discussion | Endorsement |
6.4.6Discovery of management services in 5G
| Yes |
Yes
| not treated | No | S5‑196284 | |
| S5‑196778 | Rel-16 CR TS 28.533 Obtaining URI of MnS instance | Huawei | CR | Agreement |
6.4.6Discovery of management services in 5G
| Yes |
Yes
| not pursued | No | S5‑196285 | |
| S5‑196779 | Rel-16 CR TS 28.532 MnS instance URI discovery | Huawei | CR | Agreement |
6.4.6Discovery of management services in 5G
| Yes |
Yes
| not treated | No | S5‑196286 | |
| S5‑196780 | Rel-16 CR TS 28.540 Add OAM support for RIM parameters | HUAWEI TECHNOLOGIES Co. Ltd. | CR | Agreement |
6.4.7NRM enhancements
| Yes |
Yes
| revised | No | S5‑196842 | S5‑196307 |
| S5‑196781 | Rel-16 CR TS 28.530 Clean up for incosistence | Huawei | CR | Agreement |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | S5‑196218 | |
| S5‑196782 | Rel-16 CR TS 28.531 Clean up for incosistence | Huawei | CR | Agreement |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | S5‑196219 | |
| S5‑196783 | Discussion on the effect to existed 5G management system when introduced 5G SLA | China Mobile E-Commerce Co. | discussion | Discussion |
6.4.15Management Aspects of 5G Service-Level Agreement
| Yes |
Yes
| endorsed | No | S5‑196403 | |
| S5‑196784 | Add a new description of KPI that related to Mean number of successful periodic registration updates | China Mobile E-Commerce Co. | CR | Agreement |
6.4.5Enhancement of performance assurance for 5G networks including network slicing
| Yes |
Yes
| agreed | No | S5‑196390 | |
| S5‑196785 | Add a new description of KPI that related to successful rate of mobility registration updates of Single Network Slice Instance | China Mobile E-Commerce Co. | CR | Agreement |
6.4.5Enhancement of performance assurance for 5G networks including network slicing
| Yes |
Yes
| agreed | No | S5‑196392 | |
| S5‑196786 | CR Rel-16 TR 28.806 Implementation of fixes for issues identified by EditHelp | Nokia | CR | Approval |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| No |
Yes
| agreed | No | S5‑196472 | |
| S5‑196787 | Rel-15 CR TS 28.531 fix inconsistencies in feasibility check use cases and requirements | Nokia | CR | Approval |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | S5‑196188 | |
| S5‑196788 | Rel-16 CR TS 28.531 fix inconsistencies in feasibility check use cases and requirements | Nokia | CR | Approval |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | S5‑196189 | |
| S5‑196789 | CR 28.622 Add heartbeat NRM fragment | Nokia, Nokia Shanghai Bell,AT&T, Deutsche Telekom, Orange | CR | Approval |
6.4.9Integration of ONAP and 3GPP 5G management framework
| No |
Yes
| withdrawn | Yes | ||
| S5‑196790 | Rel-16 CR 28.623 Introduce Stage 3 for configurable heartbeat | AT&T, Deutsche Telekom, Orange | CR | Approval |
6.4.9Integration of ONAP and 3GPP 5G management framework
| No |
Yes
| withdrawn | Yes | ||
| S5‑196791 | Add YANG/Netconf-based solution set for Generic provisioning MnS | Ericsson LM,Huawei | CR | Approval |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| not pursued | No | S5‑196449 | |
| S5‑196792 | LS on 3GPP – ONAP Cooperation & WoW | Ericsson Telecomunicazioni SpA | LS out | Agreement |
5.3Liaison statements at SA5 level
| No |
Yes
| left for email approval | No | S5‑196507 | |
| S5‑196793 | Rel-16 CR TS 28.554 Update the template of KPI definition for TS 28.554 | Huawei,ZTE, China Telecom | CR | Approval |
6.4.12KPI reporting
| Yes |
Yes
| not pursued | No | S5‑196169 | |
| S5‑196794 | pCR 28.313 Add ANR Use Case: Start | Ericsson France S.A.S | pCR | Approval |
6.4.13Self-Organizing Networks (SON) for 5G networks
| Yes |
Yes
| revised | No | S5‑196860 | S5‑196418 |
| S5‑196795 | pCR 28.313 Add ANR Use Case: Stop | Ericsson France S.A.S | pCR | Approval |
6.4.13Self-Organizing Networks (SON) for 5G networks
| Yes |
Yes
| revised | No | S5‑196861 | S5‑196419 |
| S5‑196796 | pCR 28.313 Add ANR Use Case: Notification | Ericsson France S.A.S | pCR | Approval |
6.4.13Self-Organizing Networks (SON) for 5G networks
| Yes |
Yes
| revised | No | S5‑196862 | S5‑196420 |
| S5‑196797 | pCR 28.313 Add ANR Use Case: Handover whitelisting | Ericsson France S.A.S | pCR | Approval |
6.4.13Self-Organizing Networks (SON) for 5G networks
| Yes |
Yes
| revised | No | S5‑196863 | S5‑196421 |
| S5‑196798 | pCR 28.313 Add ANR Use Case: Handover blacklisting | Ericsson France S.A.S | pCR | Approval |
6.4.13Self-Organizing Networks (SON) for 5G networks
| Yes |
Yes
| revised | No | S5‑196864 | S5‑196422 |
| S5‑196799 | pCR 28.313 Add ANR Use Case: Prohibit X2/Xn | Ericsson France S.A.S | pCR | Approval |
6.4.13Self-Organizing Networks (SON) for 5G networks
| Yes |
Yes
| revised | No | S5‑196865 | S5‑196423 |
| S5‑196800 | pCR 28.313 Add ANR Use Case: Prohibit X2/Xn handover | Ericsson France S.A.S | pCR | Approval |
6.4.13Self-Organizing Networks (SON) for 5G networks
| Yes |
Yes
| revised | No | S5‑196866 | S5‑196424 |
| S5‑196801 | pCR 28.313 Add ANR management use case and requirements | HUAWEI TECHNOLOGIES Co. Ltd. | pCR | Approval |
6.4.13Self-Organizing Networks (SON) for 5G networks
| No |
Yes
| withdrawn | Yes | ||
| S5‑196802 | pCR 28.313 ANR Business level requirements | Ericsson France S.A.S | pCR | Agreement |
6.4.13Self-Organizing Networks (SON) for 5G networks
| Yes |
Yes
| approved | No | S5‑196319 | |
| S5‑196803 | pCR 28.313 ANR Specification level requirements for NR RAN | Ericsson France S.A.S | pCR | Agreement |
6.4.13Self-Organizing Networks (SON) for 5G networks
| Yes |
Yes
| approved | No | S5‑196320 | |
| S5‑196804 | pCR 28.313 ANR Specification level requirements for E-UTRAN | Ericsson France S.A.S | pCR | Agreement |
6.4.13Self-Organizing Networks (SON) for 5G networks
| Yes |
Yes
| noted | No | S5‑196321 | |
| S5‑196805 | Rel-11 CR TS 32.421 Remove the editor's notes | HUAWEI TECHNOLOGIES Co. Ltd. | CR | Agreement |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196882 | S5‑196299 |
| S5‑196806 | Rel-12 CR TS 32.421 Remove the editor's notes | HUAWEI TECHNOLOGIES Co. Ltd. | CR | Agreement |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196883 | S5‑196300 |
| S5‑196807 | Rel-13 CR TS 32.421 Remove the editor's notes | HUAWEI TECHNOLOGIES Co. Ltd. | CR | Agreement |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196884 | S5‑196301 |
| S5‑196808 | Rel-14 CR TS 32.421 Remove the editor's notes | HUAWEI TECHNOLOGIES Co. Ltd. | CR | Agreement |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196885 | S5‑196302 |
| S5‑196809 | Rel-15 CR TS 32.421 Remove the editor's notes | HUAWEI TECHNOLOGIES Co. Ltd. | CR | Agreement |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| revised | No | S5‑196886 | S5‑196303 |
| S5‑196810 | Rel-16 CR TS 28.541 Add OAM support for RIM parameters | HUAWEI TECHNOLOGIES Co. Ltd. | CR | Agreement |
6.4.7NRM enhancements
| Yes |
Yes
| not treated | No | S5‑196306 | |
| S5‑196811 | LS to SA on GSMA GST/NEST translation | Ericsson | LS out | Approval |
5.3Liaison statements at SA5 level
| Yes |
Yes
| revised | No | S5‑196891 | |
| S5‑196812 | pCR Add overview for MDA | Intel Finland Oy | pCR | Agreement |
6.5.5Study on enhancement of Management Data Analytics Service
| Yes |
Yes
| approved | No | S5‑196327 | |
| S5‑196813 | Shadow TS for Heartbeat Stage 1 | AT&T, Deutsche Telekom, Orange | other | Agreement |
6.4.9Integration of ONAP and 3GPP 5G management framework
| Yes |
Yes
| approved | No | S5‑196706 | |
| S5‑196814 | Add UC on coverage issue analysis | Intel Finland Oy | pCR | Agreement |
6.5.5Study on enhancement of Management Data Analytics Service
| Yes |
Yes
| revised | No | S5‑196877 | S5‑196330 |
| S5‑196815 | pCR 28.535 on MDAS assisted coverage performance assuranace | HUAWEI TECHNOLOGIES Co. Ltd. | pCR | - |
6.5.5Study on enhancement of Management Data Analytics Service
| Yes |
Yes
| merged | No | S5‑196877 | S5‑196271 |
| S5‑196816 | pCR 28.809 Add use case of MDAS assisted user data congestion analysis | Huawei | pCR | Approval |
6.5.5Study on enhancement of Management Data Analytics Service
| Yes |
Yes
| revised | No | S5‑196876 | S5‑196442 |
| S5‑196817 | Rel-16 CR 28.552 Add measurements related to handover between 5GS and EPS | Intel Finland Oy | CR | Agreement |
6.4.5Enhancement of performance assurance for 5G networks including network slicing
| Yes |
Yes
| agreed | No | S5‑196335 | |
| S5‑196818 | Allow for service-centric load redistribution to concurrently optimize load distribution and service performance | Nokia | pCR | Approval |
6.5.2Study on Self-Organizing Networks (SON) for 5G
| Yes |
Yes
| revised | No | S5‑196870 | S5‑196176 |
| S5‑196819 | Reply to: Liaison from ETSI ISG ZSM to 3GPP SA5 Network slicing performance assurance and fault management | Huawei | LS out | approval |
6.1OAM&P Plenary
| Yes |
Yes
| approved | No | S5‑196581 | |
| S5‑196820 | Extend the usecase to allow for PCI optimization in multi-layer scenarios | Nokia | pCR | Approval |
6.5.2Study on Self-Organizing Networks (SON) for 5G
| Yes |
Yes
| revised | No | S5‑196871 | S5‑196177 |
| S5‑196821 | Reply to: LS from GSMA NEST to SA5 on End-to-End Network Slicing Gap analysis | Nokia | LS out | approval |
6.1OAM&P Plenary
| Yes |
Yes
| revised | No | S5‑196879 | S5‑196580 |
| S5‑196822 | Rel-16 CR 28.532 RESTful CM notifications for integration with ONAP VES | AT&T, Deutsche Telekom, Orange | CR | Approval |
6.4.9Integration of ONAP and 3GPP 5G management framework
| Yes |
Yes
| agreed | No | S5‑196048 | |
| S5‑196823 | Rel-15 CR TS 28.532 Correct fault supervision management service | Huawei | CR | Agreement |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | S5‑196760 | |
| S5‑196824 | Rel-16 CR TS 28.532 Correct fault supervision management service | Huawei | CR | Agreement |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | S5‑196761 | |
| S5‑196825 | Rel-15 CR TS 28.533 Update of Management service description and diagram | Huawei | CR | Agreement |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | S5‑196762 | |
| S5‑196826 | Rel-16 CR TS 28.533 Update of Management service description and diagram | Huawei | CR | Agreement |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | S5‑196763 | |
| S5‑196827 | Correct definition of network resource | Ericsson Telecomunicazioni SpA | CR | Approval |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | S5‑196594 | |
| S5‑196828 | Correct definition of network resource | Ericsson Telecomunicazioni SpA | CR | Approval |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
Yes
| agreed | No | S5‑196595 | |
| S5‑196829 | Extend the usecase to allow for PCI optimization in multi-layer scenarios | Nokia | pCR | Approval |
6.1OAM&P Plenary
| No |
Yes
| withdrawn | Yes | ||
| S5‑196830 | Chair notes on OAM sessions | WG Chair | report | Information |
6.1OAM&P Plenary
| Yes |
Yes
| noted | No | ||
| S5‑196831 | Update Intra-RAT energy saving scenario with distributed decision-making | Nokia | pCR | Approval |
6.4.2Energy Efficiency of 5G
| Yes |
Yes
| not treated | No | S5‑196646 | |
| S5‑196832 | Draft TS 28.311 | China Mobile | draft TS | Approval |
6.4.3Network policy management for mobile networks based on NFV scenarios
| No |
Yes
| left for email approval | No | ||
| S5‑196833 | pCR 28.812 Add intent driven coverage optimization scenario | Huawei | pCR | Approval |
6.4.4Intent driven management service for mobile networks
| Yes |
Yes
| approved | No | S5‑196651 | |
| S5‑196834 | Revised WID network policy management for mobile networks based on NFV scenarios | China Mobile Com. Corporation | WID revised | Approval |
6.4.3Network policy management for mobile networks based on NFV scenarios
| Yes |
Yes
| noted | No | S5‑196655 | |
| S5‑196835 | pCR 28.812 Add the relation between IDMS and SON | Huawei | pCR | Approval |
6.4.4Intent driven management service for mobile networks
| Yes |
Yes
| not treated | No | S5‑196654 | |
| S5‑196836 | Add new Use case related to extended 5QI 1 QoS Flow establishment via Initial Context Setup into A30 | Nokia Solutions & Networks (I) | CR | Agreement |
6.4.5Enhancement of performance assurance for 5G networks including network slicing
| Yes |
Yes
| agreed | No | S5‑196606 | |
| S5‑196837 | Add new measurements related to QoS Flow Setup via Initial Context Setup | Nokia Solutions & Networks (I) | CR | Agreement |
6.4.5Enhancement of performance assurance for 5G networks including network slicing
| Yes |
Yes
| agreed | No | S5‑196607 | |
| S5‑196838 | Add new Use case related to QCI1 E-RAB establishment via Initial Context Setup into A2 | Nokia Solutions & Networks (I) | CR | Agreement |
6.4.5Enhancement of performance assurance for 5G networks including network slicing
| Yes |
Yes
| agreed | No | S5‑196608 | |
| S5‑196839 | Rel-16 CR TS 28.552 Add Registered subscribers related measurements for AMF | China Mobile Com. Corporation | CR | Approval |
6.4.5Enhancement of performance assurance for 5G networks including network slicing
| No |
Yes
| withdrawn | Yes | ||
| S5‑196840 | LS to RAN3 on QoS monitoring for URLLC | Intel Finland Oy | LS out | Approval |
6.4.5Enhancement of performance assurance for 5G networks including network slicing
| No |
Yes
| left for email approval | No | S5‑196334 | |
| S5‑196841 | Reply to: LS on alignment between SA5 and RAN2 on L2 measurements | Intel | LS out | approval |
6.4.5Enhancement of performance assurance for 5G networks including network slicing
| Yes |
Yes
| approved | No | S5‑196604 | |
| S5‑196842 | Rel-16 CR TS 28.540 Add OAM support for RIM parameters | HUAWEI TECHNOLOGIES Co. Ltd. | CR | Agreement |
6.4.7NRM enhancements
| No |
Yes
| agreed | No | S5‑196780 | |
| S5‑196843 | Update Stage 2 SEPP definition in 5GC NRM | Nokia, Nokia Shanghai Bell | CR | Agreement |
6.4.7NRM enhancements
| Yes |
Yes
| not treated | No | S5‑196700 | |
| S5‑196844 | Minutes of Closed loop SLS Assurance | Rapporteur (Ericsson) | report | - |
6.4.10Closed loop SLS Assurance
| Yes |
Yes
| noted | No | S5‑196029 | |
| S5‑196845 | Rel-15 CR TS 28.541 Add NRM Info Model definitions for beam managed object classes | Pivotal Commware, ZTE, Intel, P.I. Works, China Mobile, Verizon, BT, AT&T, Cisco, Deutsche Telekom | CR | Agreement |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| Yes |
YesStage 3 issues and mirror CR will be brought next meeting.
| conditionally agreed | No | S5‑196600 | |
| S5‑196846 | Update requirements for Load Balancing Optimization to allow for service centric resource optimization | Nokia | pCR | Approval |
6.5.2Study on Self-Organizing Networks (SON) for 5G
| Yes |
Yes
| revised | No | S5‑196872 | S5‑196184 |
| S5‑196847 | Rel-16 CR TS 28.541 Correct XML Solution Set for NR | Huawei | CR | Agreement |
6.4.7NRM enhancements
| No |
Yes
| left for email approval | No | S5‑196235 | |
| S5‑196848 | Rel-16 CR TS 28.623 Correct XML Solution Set for generic NRM | Huawei | CR | Agreement |
6.4.7NRM enhancements
| No |
Yes
| left for email approval | No | S5‑196237 | |
| S5‑196849 | Rel-16 CR TS 28.541 Correct Network slice NRM | Huawei,Ericsson | CR | Agreement |
6.4.7NRM enhancements
| No |
Yes
| left for email approval | No | S5‑196236 | |
| S5‑196850 | Rel-16 CR TS 28.533 Add the description of data analytics utilization in closed loop SLA assurance | HUAWEI TECHNOLOGIES Co. Ltd. | CR | Agreement |
6.4.10Closed loop SLS Assurance
| Yes |
Yes
| not treated | No | S5‑196617 | |
| S5‑196851 | Draft TS 28.535 | Ericsson | draft TS | Approval |
6.4.10Closed loop SLS Assurance
| No |
Yes
| withdrawn | Yes | ||
| S5‑196852 | Draft TS 28.536 | Ericsson | draft TS | Approval |
6.4.10Closed loop SLS Assurance
| No |
Yes
| withdrawn | Yes | ||
| S5‑196853 | Rel-16 CR TS 28.550 Add UC and requirements for NF KPI job control | China Telecommunications, ZTE | CR | Agreement |
6.4.12KPI reporting
| Yes |
Yes
| not treated | No | S5‑196662 | |
| S5‑196854 | New WID network policy management for 5G mobile networks based on NFV scenarios | China Mobile Com. Corporation | WID new | Agreement |
6.2New OAM&P Work Item proposals
| Yes |
Yes
| revised | No | S5‑196880 | S5‑196582 |
| S5‑196855 | Discussion paper about exposure governance | Huawei | discussion | Endorsement |
6.4.6Discovery of management services in 5G
| Yes |
Yes
| revised | No | S5‑196887 | S5‑196667 |
| S5‑196856 | Draft TS 28.313 | Intel | draft TS | Approval |
6.4.13Self-Organizing Networks (SON) for 5G networks
| No |
Yes
| left for email approval | No | ||
| S5‑196857 | pCR 28.313 MRO use case | Intel Corporation (UK) Ltd,Ericsson | pCR | Approval |
6.4.13Self-Organizing Networks (SON) for 5G networks
| No |
YesIt fixes the term "send" as commented by Nokia.
| approved | No | S5‑196746 | |
| S5‑196858 | pCR 28.313 MRO information | Intel Corporation (UK) Ltd | pCR | Approval |
6.4.13Self-Organizing Networks (SON) for 5G networks
| No |
Yes
| left for email approval | No | S5‑196749 | |
| S5‑196859 | ANR Specification level requirements for E-UTRAN | Ericsson France S.A.S | CR | Agreement |
6.4.13Self-Organizing Networks (SON) for 5G networks
| No |
Yes
| left for email approval | No | ||
| S5‑196860 | pCR 28.313 Add ANR Use Case: Start | Ericsson France S.A.S | pCR | Approval |
6.4.13Self-Organizing Networks (SON) for 5G networks
| Yes |
Yes
| approved | No | S5‑196794 | |
| S5‑196861 | pCR 28.313 Add ANR Use Case: Stop | Ericsson France S.A.S | pCR | Approval |
6.4.13Self-Organizing Networks (SON) for 5G networks
| Yes |
Yes
| approved | No | S5‑196795 | |
| S5‑196862 | pCR 28.313 Add ANR Use Case: Notification | Ericsson France S.A.S | pCR | Approval |
6.4.13Self-Organizing Networks (SON) for 5G networks
| Yes |
Yes
| approved | No | S5‑196796 | |
| S5‑196863 | pCR 28.313 Add ANR Use Case: Handover whitelisting | Ericsson France S.A.S | pCR | Approval |
6.4.13Self-Organizing Networks (SON) for 5G networks
| Yes |
Yes
| approved | No | S5‑196797 | |
| S5‑196864 | pCR 28.313 Add ANR Use Case: Handover blacklisting | Ericsson France S.A.S | pCR | Approval |
6.4.13Self-Organizing Networks (SON) for 5G networks
| Yes |
Yes
| approved | No | S5‑196798 | |
| S5‑196865 | pCR 28.313 Add ANR Use Case: Prohibit X2/Xn | Ericsson France S.A.S | pCR | Approval |
6.4.13Self-Organizing Networks (SON) for 5G networks
| Yes |
Yes
| approved | No | S5‑196799 | |
| S5‑196866 | pCR 28.313 Add ANR Use Case: Prohibit X2/Xn handover | Ericsson France S.A.S | pCR | Approval |
6.4.13Self-Organizing Networks (SON) for 5G networks
| Yes |
Yes
| approved | No | S5‑196800 | |
| S5‑196867 | Rel-16 CR 28.541 Add relation of GST and profiles | Huawei, China Mobile | CR | Approval |
6.4.15Management Aspects of 5G Service-Level Agreement
| Yes |
Yes
| agreed | No | S5‑196620 | |
| S5‑196868 | LS to GSMA on GST | Orange | LS out | Approval |
6.4.15Management Aspects of 5G Service-Level Agreement
| No |
Yes
| left for email approval | No | S5‑196757 | |
| S5‑196869 | Draft TR 28.861 | Intel | draft TR | Approval |
6.5.2Study on Self-Organizing Networks (SON) for 5G
| No |
Yes
| left for email approval | No | ||
| S5‑196870 | Allow for service-centric load redistribution to concurrently optimize load distribution and service performance | Nokia | pCR | Approval |
6.5.2Study on Self-Organizing Networks (SON) for 5G
| No |
Yes
| left for email approval | No | S5‑196818 | |
| S5‑196871 | Extend the usecase to allow for PCI optimization in multi-layer scenarios | Nokia | pCR | Approval |
6.5.2Study on Self-Organizing Networks (SON) for 5G
| No |
Yes
| left for email approval | No | S5‑196820 | |
| S5‑196872 | Update requirements for Load Balancing Optimization to allow for service centric resource optimization | Nokia | pCR | Approval |
6.5.2Study on Self-Organizing Networks (SON) for 5G
| No |
Yes
| left for email approval | No | S5‑196846 | |
| S5‑196873 | Draft TR 28.807 | Huawei | draft TR | Approval |
6.5.3Study on non-public networks management
| No |
Yes
| left for email approval | No | ||
| S5‑196874 | Draft TR 28.808 | Thales | draft TR | Approval |
6.5.4Study on management and orchestration aspects with integrated satellite components in a 5G network
| No |
Yes
| left for email approval | No | ||
| S5‑196875 | Draft TR 28.809 | Intel | draft TR | Approval |
6.5.5Study on enhancement of Management Data Analytics Service
| No |
Yes
| left for email approval | No | ||
| S5‑196876 | pCR 28.809 Add use case of MDAS assisted user data congestion analysis | Huawei | pCR | Approval |
6.5.5Study on enhancement of Management Data Analytics Service
| No |
Yes
| left for email approval | No | S5‑196816 | |
| S5‑196877 | Add UC on coverage issue analysis | Intel Finland Oy,Huawei | pCR | Agreement |
6.5.5Study on enhancement of Management Data Analytics Service
| Yes |
Yes
| approved | No | S5‑196814 | |
| S5‑196878 | pCR 28.810 Add background | China Mobile, Huawei | pCR | Approval |
6.5.6Study on autonomous network levels
| Yes |
Yes
| approved | No | S5‑196739 | |
| S5‑196879 | Reply to: LS from GSMA NEST to SA5 on End-to-End Network Slicing Gap analysis | Nokia | LS out | approval |
6.1OAM&P Plenary
| No |
Yes
| left for email approval | No | S5‑196821 | |
| S5‑196880 | New WID network policy management for 5G mobile networks based on NFV scenarios | China Mobile Com. Corporation | WID new | Agreement |
6.2New OAM&P Work Item proposals
| Yes |
Yes
| agreed | No | S5‑196854 | |
| S5‑196881 | New SID on network slice management enhancements | Huawei | SID new | Agreement |
6.2New OAM&P Work Item proposals
| Yes |
YesIt was agreed that the work would start once the release 16 work items were finished.
| agreed | No | S5‑196583 | |
| S5‑196882 | Rel-11 CR TS 32.421 Remove the editor's notes | HUAWEI TECHNOLOGIES Co. Ltd. | CR | Agreement |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| No |
Yes
| left for email approval | No | S5‑196805 | |
| S5‑196883 | Rel-12 CR TS 32.421 Remove the editor's notes | HUAWEI TECHNOLOGIES Co. Ltd. | CR | Agreement |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| No |
Yes
| left for email approval | No | S5‑196806 | |
| S5‑196884 | Rel-13 CR TS 32.421 Remove the editor's notes | HUAWEI TECHNOLOGIES Co. Ltd. | CR | Agreement |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| No |
Yes
| left for email approval | No | S5‑196807 | |
| S5‑196885 | Rel-14 CR TS 32.421 Remove the editor's notes | HUAWEI TECHNOLOGIES Co. Ltd. | CR | Agreement |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| No |
Yes
| left for email approval | No | S5‑196808 | |
| S5‑196886 | Rel-15 CR TS 32.421 Remove the editor's notes | HUAWEI TECHNOLOGIES Co. Ltd. | CR | Agreement |
6.3OAM&P Maintenance and Rel-16 small Enhancements
| No |
Yes
| left for email approval | No | S5‑196809 | |
| S5‑196887 | Discussion paper about exposure governance | Huawei | discussion | Endorsement |
6.4.6Discovery of management services in 5G
| Yes |
Yes
| endorsed | No | S5‑196855 | |
| S5‑196888 | Remove Network Slicing SS | Ericsson | CR | Agreement |
6.1OAM&P Plenary
| No |
Yes
| left for email approval | No | ||
| S5‑196889 | Updates to YANG SS | Ericsson | CR | Agreement |
6.1OAM&P Plenary
| No |
Yes
| left for email approval | No | ||
| S5‑196890 | Updates to YANG SS | Ericsson | CR | Agreement |
6.1OAM&P Plenary
| No |
Yes
| left for email approval | No | ||
| S5‑196891 | LS to SA on GSMA GST/NEST translation | Ericsson | LS out | Approval |
5.3Liaison statements at SA5 level
| Yes |
Yes
| approved | No | S5‑196811 |