Tdoc List
2020-05-12 12:17
Agenda | Topic | TDoc | Title | Source | Type | For | Avail | Treated | Decision | Wdrn | Replaced-by | Replaces |
---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | Opening of the meeting |   | ||||||||||
2 | Approval of the agenda | S5‑202000 | Agenda | WG Chair | agenda | Yes |
Yes
| approved | No | |||
3 | IPR and legal declaration |   | ||||||||||
4 | Meetings and activities reports |   | ||||||||||
4.1 | Last SA5 meeting report (previous 2 meetings) | S5‑202001 | SA5#128 meeting report | MCC | report | Yes |
Yes
| approved | No | |||
S5‑202002 | SA5#129e meeting report | MCC | report | Yes |
Yes
| approved | No | |||||
4.2 | Last SA meeting report |   | ||||||||||
4.3 | Inter-organizational reports |   | ||||||||||
5 | Cross-SWG issues |   | ||||||||||
5.1 | Administrative issues at SA5 level | S5‑202013 | SA5-130e E-Meeting Process | WG Chair | other | Information | Yes |
Yes
| approved | No | ||
S5‑202460 | Post SA5#130e Email approval status | WG Chair | other | Information | Yes |
No
| available | No | ||||
5.2 | Technical issues at SA5 level |   | ||||||||||
5.3 | Liaison statements at SA5 level | S5‑202023 | Formation of a new ETSI ISG for the Fifth Generation Fixed Network (F5G) | ETSI ISG F5G | LS in | Yes |
Yes
| noted | No | |||
S5‑202029 | Reply LS to SA5 on support for eCall over NR | SP-200287 | LS in | Yes |
Yes
| postponed | No | |||||
S5‑202030 | LS reply to SA5 on Technical Community Cooperation: Generic Network Management | ONAP | LS in | Yes |
Yes
| replied to | No | |||||
S5‑202087 | Discussion paper on QoS requirements for OAM and Charging traffic on IAB | Intel Finland Oy | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑202457 | |||
S5‑202457 | Discussion paper on QoS requirements for OAM and Charging traffic on IAB | Intel Finland Oy | discussion | Endorsement | Yes |
Yes
| endorsed | No | S5‑202087 | |||
S5‑202300 | Reply LS to ONAP on liaison coordinator and VES API reference | Ericsson | LS out | Approval | Yes |
YesAT&T requested to have minuted the following:
“In an offline letter to the 3GPP Liaisons Coordinator entitled “Response to 3GPP LS S5-196792,” which was not an official input to SA5#130e, it was confirmed that: 1) Magnus Buhrgard has been appointed the role of “ONAP Technical Community Coordinator – Generic Network Management;” and 2) in the ONAP TSC Decision Log from 2020-Feb-06 it was recorded that the ONAP TSC approved the response to the 3 requests from SA5 as outlined in Slide 3 of their LS response.”
| approved | No | ||||
S5‑202458 | LS to SA2 on QoS requirements for OAM traffic on IAB | Intel | LS out | Approval | Yes |
Yes
| approved | No | ||||
5.4 | SA5 meeting calendar |   | ||||||||||
5.5 | Review of the Work Plan |   | ||||||||||
6 | OAM&P |   | ||||||||||
6.1 | OAM&P Plenary | S5‑202242 | OAM&P SWG action list | Huawei Technologies (Korea) | other | Yes |
Yes
| noted | No | |||
S5‑202243 | SA5#130e_agenda_with_Tdocs_sequence_proposal_OAM | Huawei Technologies (Korea) | agenda | Yes |
Yes
| noted | No | |||||
S5‑202244 | SA5#130e OAM Exec Report | Huawei Technologies (Korea) | report | No |
No
| reserved | No | |||||
S5‑202348 | SA5#130e OAM Chair notes and conclusions | WG Chair | report | Information | Yes |
No
| available | No | ||||
6.2 | New OAM&P Work Item proposals |   | ||||||||||
6.3 | OAM&P Maintenance and Rel-16 small Enhancements | S5‑202004 | Rel-16 CR TS 28.532 Void meaningless clause | AT&T, Orange | CR | Approval | Yes |
Yes
| revised | No | S5‑202351 | |
S5‑202351 | Rel-16 CR TS 28.532 Void meaningless clause | AT&T, Orange | CR | Approval | Yes |
Yes
| agreed | No | S5‑202004 | |||
S5‑202005 | Rel 16 CR TS 28.554 Fixing Equations | Samsung Electronics France SA | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑202019 | Resubmitted LS to SA5 on EN-DC related MDT configuration details | R2-1916579 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑202025 | LS to SA5 on EN-DC related MDT configuration details | R2-1916579 | LS in | No |
Yes
| withdrawn | Yes | |||||
S5‑202031 | LS to SA5 on removal of Management Based MDT Allowed IE for NR | R3-201437 | LS in | Yes |
Yes
| postponed | No | |||||
S5‑202032 | LS ccSA5 on Generic Slice Template with Public Safety Feedback | TCCA | LS in | Yes |
Yes
| noted | No | |||||
S5‑202049 | Rel-16 CR 28.532 Add summary CM notification to the ProvMnS | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑202356 | S5‑201385 | ||
S5‑202356 | Rel-16 CR 28.532 Add summary CM notification to the ProvMnS | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑202049 | |||
S5‑202050 | Rel-16 CR 28.532 Remove subscribe and unsubscribe operation from ProvMnS | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑201390 | |||
S5‑202051 | Reply LS to LS on removal of Management Based MDT Allowed IE for NR | Oy LM Ericsson AB | LS out | Agreement | Yes |
Yes
| withdrawn | Yes | ||||
S5‑202052 | Reply LS to LS on EN-DC related MDT configuration details | Oy LM Ericsson AB | LS out | Agreement | Yes |
Yes
| approved | No | ||||
S5‑202088 | Rel-15 CR 28.550 Add service components for configurable performance measurement control | Intel Finland Oy | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑202089 | Rel-16 CR 28.550 Add service components for configurable performance measurement control | Intel Finland Oy | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑202113 | Replace Management based MDT Allowed IE with Management based MDT PLMN List IE for MDT user consent handling in NR | Oy LM Ericsson AB | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑202114 | Add missing notification attributes for Matching-Criteria-Attributes | Oy LM Ericsson AB | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑202115 | Add missing notification attributes for Matching-Criteria-Attributes | Oy LM Ericsson AB | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑202116 | Rel-16 CR TS 28.541 Correction of reference | CATT | CR | Approval | Yes |
Yes
| revised | No | S5‑202352 | |||
S5‑202352 | Rel-16 CR TS 28.541 Correction of reference | CATT | CR | Approval | Yes |
Yes
| agreed | No | S5‑202116 | |||
S5‑202117 | Rel-16 CR 28.541 Update NRM attribute definitions | CATT, Ericsson | CR | Approval | Yes |
Yes
| merged | No | S5‑202303 | |||
S5‑202118 | Rel-16 CR 28.658 Update NRM attribute definitions | CATT, Ericsson | CR | Approval | Yes |
Yes
| revised | No | S5‑202353 | |||
S5‑202353 | Rel-16 CR 28.658 Update NRM attribute definitions | CATT, Ericsson | CR | Approval | Yes |
Yes
| agreed | No | S5‑202118 | |||
S5‑202122 | Rel-6 CR TS 32.423 clean up editor notes | Huawei Technologies (Korea) | CR | Yes |
Yes
| not pursued | No | |||||
S5‑202123 | Rel-7 CR TS 32.423 clean up editor notes | Huawei Technologies (Korea) | CR | Yes |
Yes
| not pursued | No | |||||
S5‑202124 | Rel-8 CR TS 32.423 clean up editor notes | Huawei Technologies (Korea) | CR | Yes |
Yes
| revised | No | S5‑202350 | ||||
S5‑202350 | Rel-8 CR TS 32.423 clean up editor notes | Huawei Technologies (Korea) | CR | - | Yes |
Yes
| agreed | No | S5‑202124 | |||
S5‑202125 | Rel-9 CR TS 32.423 clean up editor notes | Huawei Technologies (Korea) | CR | Yes |
Yes
| agreed | No | |||||
S5‑202126 | Rel-10 CR TS 32.423 clean up editor notes | Huawei Technologies (Korea) | CR | Yes |
Yes
| agreed | No | |||||
S5‑202127 | Rel-11 CR TS 32.423 clean up editor notes | Huawei Technologies (Korea) | CR | Yes |
Yes
| agreed | No | |||||
S5‑202128 | Rel-12 CR TS 32.423 clean up editor notes | Huawei Technologies (Korea) | CR | Yes |
Yes
| agreed | No | |||||
S5‑202129 | Rel-13 CR TS 32.423 clean up editor notes | Huawei Technologies (Korea) | CR | Yes |
Yes
| agreed | No | |||||
S5‑202130 | Rel-14 CR TS 32.423 clean up editor notes | Huawei Technologies (Korea) | CR | Yes |
Yes
| agreed | No | |||||
S5‑202131 | Rel-15 CR TS 32.423 clean up editor notes | Huawei Technologies (Korea) | CR | Yes |
Yes
| agreed | No | |||||
S5‑202132 | Rel-16 CR TS 32.423 clean up editor notes | Huawei Technologies (Korea) | CR | Yes |
Yes
| agreed | No | |||||
S5‑202145 | Rel-16 CR TS 28.531 Fix inconsistencies | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑202146 | Rel-16 CR TS 28.530 Fix inconsistencies | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑202147 | Rel-16 CR 28.550 Correct Typos of Reference | Huawei | CR | Agreement | Yes |
Yes
| withdrawn | Yes | ||||
S5‑202148 | Rel-16 CR TS 28.531 fix Network Slice subnet termination use case | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑202358 | |||
S5‑202358 | Rel-16 CR TS 28.531 fix Network Slice subnet termination use case | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑202148 | |||
S5‑202149 | Rel-16 CR TS 28.531 fix NSI activation and deactivation use case | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑202359 | |||
S5‑202359 | Rel-16 CR TS 28.531 fix NSI activation and deactivation use case | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑202149 | |||
S5‑202150 | Rel-15 CR TS 28.531 fix Network Slice subnet termination use case | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑202360 | |||
S5‑202360 | Rel-15 CR TS 28.531 fix Network Slice subnet termination use case | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑202150 | |||
S5‑202225 | Rel-16 CR 28.532 Add missing callbacks for notifications to ProvMnS | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑202226 | Discussion on general CRUD operation for different management purposes | Huawei | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑202227 | Rel-16 CR TS 28.532 Update the generic provisioning MnS to support different management purposes | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑202228 | Rel-16 CR TS 28.550 Add description for configurable PM control MnS | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑202229 | Rel-16 CR TS 28.5450 Add description for configurable FM control MnS | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑202230 | Rel-16 CR TS 28.532 Remove attribute referenceObjectInstance which is not supported by solution set | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑202231 | Rel-16 CR TS 28.532 Update URI for generic fault supervision management service | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑202361 | |||
S5‑202361 | Rel-16 CR TS 28.532 Update URI for generic fault supervision management service | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑202231 | |||
S5‑202232 | Rel-16 CR TS 28.532 Update URI for performance data file reporting service | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑202362 | |||
S5‑202362 | Rel-16 CR TS 28.532 Update URI for performance data file reporting service | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑202232 | |||
S5‑202233 | Rel-15 CR TS 32.158 Add the missing definition for LDN-first-part | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑202363 | |||
S5‑202363 | Rel-15 CR TS 32.158 Add the missing definition for LDN-first-part | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑202233 | |||
S5‑202234 | Rel-16 CR TS 32.158 Add the missing definition for LDN-first-part | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑202251 | Rel-16 CR 28.532 Remove data object from response types in the ProvMnS | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑202357 | |||
S5‑202357 | Rel-16 CR 28.532 Remove data object from response types in the ProvMnS | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑202251 | |||
S5‑202255 | Discussion paper on release planning of GST attributes | Ericsson LM | discussion | Discussion | Yes |
Yes
| noted | No | ||||
S5‑202256 | CR TS 28.541 Align ServiceProfile with GST Option 1 | Ericsson LM | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑202257 | CR TS 28.541 Align ServiceProfile with GST Option 2 | Ericsson LM | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑202278 | TD proposal for cleanup network slice related definitions | Nokia, Nokia Shanghai Bell, Intel | discussion | Endorsement | Yes |
Yes
| merged | No | S5‑202364 | |||
S5‑202279 | Fix Network Slice related definitions in OAM space | Nokia, Nokia Shanghai Bell, Intel | CR | Agreement | Yes |
Yes
| revised | No | S5‑202366 | |||
S5‑202366 | Fix Network Slice related definitions in OAM space | Nokia, Nokia Shanghai Bell, Intel, Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑202279 | |||
S5‑202280 | Cleanup network slice instance | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑202295 | Rel-16 CR 28.622 Fix inconsistent formatting | Nokia | CR | Approval | Yes |
Yes
| revised | No | S5‑202355 | |||
S5‑202355 | Rel-16 CR 28.622 Fix inconsistent formatting | Nokia | CR | Approval | Yes |
Yes
| agreed | No | S5‑202295 | |||
S5‑202298 | Rel-16 CR 28.623 Fix inconsistent formatting | Nokia | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑202299 | Correct Typos of Reference | Huawei Tech.(UK) Co., Ltd | CR | Agreement | Yes |
Yes
| revised | No | S5‑202354 | |||
S5‑202354 | Correct Typos of Reference | Huawei Tech.(UK) Co., Ltd | CR | Agreement | Yes |
Yes
| agreed | No | S5‑202299 | |||
6.4 | Rel-16 Operations, Administration, Maintenance and Provisioning (OAM&P) |   | ||||||||||
6.4.1 | Management of QoE measurement collection | S5‑202010 | pCR TS 28.406 Add definitions of terms, symbols and abbreviations | Nanjing Ericsson Panda Com Ltd | pCR | Yes |
Yes
| approved | No | |||
S5‑202011 | pCR TS 28.406 Add QoE record contents | Nanjing Ericsson Panda Com Ltd | pCR | Yes |
Yes
| revised | No | S5‑202324 | ||||
S5‑202324 | pCR TS 28.406 Add QoE record contents | Nanjing Ericsson Panda Com Ltd | pCR | - | Yes |
Yes
| revised | No | S5‑202406 | S5‑202011 | ||
S5‑202406 | pCR TS 28.406 Add QoE record contents | Nanjing Ericsson Panda Com Ltd | pCR | - | Yes |
Yes
| approved | No | S5‑202324 | |||
S5‑202020 | Resubmitted LS to SA5 on Reply on QoE Measurement Collection | S4-200241 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑202304 | Reply to: LS to SA5 on Reply on QoE Measurement Collection | Ericsson | LS out | approval | Yes |
Yes
| approved | No | ||||
S5‑202021 | Resubmitted Reply LS to SA5 on QoE Measurement Collection | R2-1916328 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑202305 | Reply to: Resubmitted Reply LS to SA5 on QoE Measurement Collection | Ericsson | LS out | approval | Yes |
Yes
| approved | No | ||||
S5‑202112 | Add QoE Specifications | Oy LM Ericsson AB | CR | Agreement | Yes |
Yes
| revised | No | S5‑202459 | |||
S5‑202459 | Add QoE Specifications | Oy LM Ericsson AB | CR | Agreement | Yes |
Yes
| agreed | No | S5‑202112 | |||
S5‑202220 | CR nR16 32.101-f00 Introduction of QMC | Ericsson | CR | Yes |
Yes
| revised | No | S5‑202301 | ||||
S5‑202301 | CR nR16 32.101-f00 Introduction of QMC | Ericsson | CR | - | Yes |
Yes
| agreed | No | S5‑202220 | |||
S5‑202221 | pCR R16 28308-030 QMC operations | Ericsson | pCR | Yes |
Yes
| revised | No | S5‑202302 | ||||
S5‑202302 | pCR R16 28308-030 QMC operations | Ericsson | pCR | - | Yes |
Yes
| approved | No | S5‑202221 | |||
S5‑202222 | pCR R16 28.405-120 Update of R16 | Ericsson | pCR | Yes |
Yes
| revised | No | S5‑202453 | ||||
S5‑202453 | pCR R16 28.405-120 Update of R16 | Ericsson | pCR | - | Yes |
Yes
| approved | No | S5‑202222 | |||
S5‑202223 | Presentation of Specification to TSG: TS 28.307, Version 1.0.0 | Ericsson | TS or TR cover | Yes |
Yes
| approved | No | |||||
S5‑202343 | draft TS 28.308 | Ericsson | draft TS | Approval | Yes |
Yes
| approved | No | ||||
S5‑202344 | draft TS 28.406 | Ericsson | draft TS | Approval | Yes |
Yes
| approved | No | ||||
S5‑202345 | draft TS 28.405 | Ericsson | draft TS | Approval | Yes |
Yes
| approved | No | ||||
6.4.2 | Energy Efficiency of 5G |   | ||||||||||
6.4.3 | Enhancement of performance assurance for 5G networks including network slicing | S5‑202003 | New measuremenst for average call duration | Nokia Solutions & Networks (I) | CR | Approval | Yes |
Yes
| revised | No | S5‑202317 | |
S5‑202317 | New measuremenst for average call duration | Nokia Solutions & Networks (I) | CR | Approval | Yes |
Yes
| agreed | No | S5‑202003 | |||
S5‑202006 | Rel 15 CR TS 28.554 Fixing Equations | Samsung Electronics France SA | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑202008 | Rel 15 CR Adding Per Slice N3 Measurements | Samsung Electronics France SA | CR | Agreement | Yes |
Yes
| revised | No | S5‑202455 | |||
S5‑202455 | Rel 15 CR Adding Per Slice N3 Measurements | Samsung Electronics France SA | CR | Agreement | Yes |
Yes
| agreed | No | S5‑202008 | |||
S5‑202009 | Rel 16 CR Adding Per Slice N3 Measurements | Samsung Electronics France SA | CR | Yes |
Yes
| revised | No | S5‑202456 | ||||
S5‑202456 | Rel 16 CR Adding Per Slice N3 Measurements | Samsung Electronics France SA | CR | - | Yes |
Yes
| agreed | No | S5‑202009 | |||
S5‑202012 | LS to CT4 on SNSSAI support in N4 Session Establishment | Samsung Electronics France SA | LS out | Agreement | Yes |
Yes
| revised | No | S5‑202308 | |||
S5‑202308 | LS to CT4 on SNSSAI support in N4 Session Establishment | Samsung Electronics France SA | LS out | Agreement | Yes |
Yes
| approved | No | S5‑202012 | |||
S5‑202014 | Corrections of Number of Active UEs measurements | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑202015 | Correction of Average delay UL on over-the-air interface measurement | Ericsson LM | CR | Approval | Yes |
Yes
| revised | No | S5‑202313 | |||
S5‑202016 | Add measurement Average RLC packet delay in the UL | Ericsson LM | CR | Approval | Yes |
Yes
| revised | No | S5‑202311 | |||
S5‑202311 | Add measurement Average RLC packet delay in the UL | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | S5‑202016 | |||
S5‑202017 | Add measurement Average PDCP re-ordering delay in the UL | Ericsson LM | CR | Approval | Yes |
Yes
| revised | No | S5‑202312 | |||
S5‑202312 | Add measurement Average PDCP re-ordering delay in the UL | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | S5‑202017 | |||
S5‑202018 | Add Number of stored inactive UE contexts measurements | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑202028 | Reply LS to SA5 on QoS monitoring for URLLC | R3-201372 | LS in | Yes |
Yes
| noted | No | |||||
S5‑202035 | Add KPI for UL packet delay in NG-RAN | Ericsson LM | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑202036 | Correction of Integrated downlink delay in RAN KPI | Ericsson LM | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑202037 | Correction of Downlink latency in gNB-DU KPI | Ericsson LM | CR | Approval | Yes |
Yes
| revised | No | S5‑202314 | |||
S5‑202314 | Correction of Downlink latency in gNB-DU KPI | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | S5‑202037 | |||
S5‑202038 | Removal of the KPI named KPI categories | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑202045 | Rel-16 CR TS 28.552 Update the measurements related to the delay of DL air-interface | Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑202318 | |||
S5‑202318 | Rel-16 CR TS 28.552 Update the measurements related to the delay of DL air-interface | Huawei | CR | Approval | Yes |
Yes
| agreed | No | S5‑202045 | |||
S5‑202046 | Rel-16 CR TS 28.552 Update the precision of packet delay | Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑202313 | |||
S5‑202313 | Rel-16 CR TS 28.552 Update the precision of packet delay | Huawei,Ericsson | CR | Approval | Yes |
Yes
| agreed | No | S5‑202046 | |||
S5‑202047 | Rel-16 CR TS 28.552 Move the network slice related measurements to clause 6 | Huawei | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑202048 | Rel-16 CR TS 28.552 add the referrence to slice related measurements in clause 6 | Huawei | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑202090 | Rel-16 CR 28.552 Add measurements on DL delay between PSA UPF and UE | Intel Corporation (UK) Ltd, ETRI | CR | Approval | Yes |
Yes
| revised | No | S5‑202309 | S5‑201182 | ||
S5‑202309 | Rel-16 CR 28.552 Add measurements on DL delay between PSA UPF and UE | Intel Corporation (UK) Ltd, ETRI | CR | Approval | Yes |
Yes
| agreed | No | S5‑202090 | |||
S5‑202091 | Rel-16 CR 28.552 Add measurements on UL delay between PSA UPF and UE | Intel Corporation (UK) Ltd, ETRI | CR | Approval | Yes |
Yes
| revised | No | S5‑202310 | S5‑201183 | ||
S5‑202310 | Rel-16 CR 28.552 Add measurements on UL delay between PSA UPF and UE | Intel Corporation (UK) Ltd, ETRI | CR | Approval | Yes |
Yes
| agreed | No | S5‑202091 | |||
S5‑202102 | Update of KPI template | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑202104 | Discussion paper around KPI Template | Ericsson LM | discussion | Approval | Yes |
Yes
| endorsed | No | ||||
S5‑202105 | Rel-16 CR 28.552 Add measurements on DL packet delay between NG-RAN and UE | Intel Finland Oy | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑202106 | Rel-16 CR 28.552 Add measurements on UL packet delay between NG-RAN and UE | Intel Finland Oy | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑202107 | Discussion paper around UPF measurements | Ericsson LM | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑202108 | Rel-16 CR 28.552 Add measurements on DL packet delay in NG-RAN for Network Slice | Intel Finland Oy | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑202109 | Rel-16 CR 28.552 Add measurements on UL packet delay in NG-RAN for Network Slice | Intel Finland Oy | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑202208 | R16 CR TS28.552 Add DSS PRB usage measurements | ZTE Corporation, China Telecom | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑202210 | R16 CR TS28.552 Add Initial BWP PRB usage measurements | ZTE Corporation, China Telecom | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑202211 | R16 CR TS28.552 Modify Distribution PRB usage measurements | ZTE Corporation, China Telecom | CR | Agreement | Yes |
Yes
| revised | No | S5‑202316 | |||
S5‑202316 | R16 CR TS28.552 Modify Distribution PRB usage measurements | ZTE Corporation, China Telecom | CR | Agreement | Yes |
Yes
| agreed | No | S5‑202211 | |||
S5‑202213 | Rel-16 CR TS 28.552 Add use case and defintion of the maximum round-trip packet delay between PSA UPF and UE | Huawei | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑202214 | Rel-16 CR TS 28.552 Add use case and definition of the maximum delay of DL air-interface | Huawei | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑202275 | CR TS 28.552 editorial correction of TS 28.552 | Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑202307 | |||
S5‑202307 | CR TS 28.552 editorial correction of TS 28.552 | Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑202319 | S5‑202275 | ||
S5‑202319 | CR TS 28.552 editorial correction of TS 28.552 | Huawei | CR | Approval | Yes |
Yes
| agreed | No | S5‑202307 | |||
S5‑202276 | CR TS 28.552 update the definition of UE throughput related measurements | Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑202315 | |||
S5‑202315 | CR TS 28.552 update the definition of UE throughput related measurements | Huawei | CR | Approval | Yes |
Yes
| agreed | No | S5‑202276 | |||
6.4.4 | Discovery of management services in 5G | S5‑202151 | Revised WID on Discovery of management services in 5G | Huawei | WID revised | Approval | Yes |
Yes
| noted | No | ||
S5‑202152 | Rel-16 CR TS 28.533 Clarify the MnS producer profile | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑202153 | Rel-16 CR TS 28.622 Clarify systemDN usage for MnS producer profile notification | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
6.4.5 | NRM enhancements | S5‑202024 | LS reply ccSA5 on initiation of a new work item Y.IMT2020-NSC “IMT-2020 network slice configuration | GSMA | LS in | Yes |
Yes
| noted | No | |||
S5‑202033 | Discussion on restructure RRMPolicyRatio | Huawei, Ericsson,CATT,China Telecom, China Mobile | discussion | Endorsement | Yes |
Yes
| endorsed | No | ||||
S5‑202034 | Rel-16 CR TS 28.541 Update on RRMPolicyRatio | Huawei, Ericsson,CATT,China Telecom, China Mobile | CR | Agreement | Yes |
Yes
| revised | No | S5‑202368 | |||
S5‑202368 | Rel-16 CR TS 28.541 Update on RRMPolicyRatio | Huawei, Ericsson,CATT,China Telecom, China Mobile | CR | Agreement | Yes |
Yes
| agreed | No | S5‑202034 | |||
S5‑202086 | YANG-Push Notifications | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑202101 | Rel-16 CR 28.541 Add IOC for control of QoS monitoring per QoS flow per UE | Intel Finland Oy | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑202103 | Rel-16 CR 28.541 Add IOC for control of GTP-U path QoS monitoring | Intel Finland Oy | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑202182 | Rel-16 CR 28.623 Add OpenAPI definitions for the FM control fragment | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑202183 | Rel-16 CR TS 28.541 Add NRPhysicalCellDU and NRCarrier NRM to support Multi-SSBs and network sharing | ZTE Corporation | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑202184 | Rel-16 CR 28.623 Correct OpenAPI definition for notificationTypes | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑202375 | |||
S5‑202375 | Rel-16 CR 28.623 Correct OpenAPI definition for notificationTypes | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑202184 | |||
S5‑202190 | Discussion paper clarification on network slice related identifiers | Huawei | discussion | Discussion | Yes |
Yes
| revised | No | S5‑202364 | |||
S5‑202364 | Discussion paper clarification on network slice related identifiers | Huawei, Nokia, Nokia Shanghai Bell | discussion | Discussion | Yes |
Yes
| endorsed | No | S5‑202190 | |||
S5‑202191 | Rel-16 CR 28.541 Clarification on network slice related identifiers | Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑202365 | |||
S5‑202365 | Rel-16 CR 28.541 Clarification on network slice related identifiers | Huawei, Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑202191 | |||
S5‑202192 | Rel-16 CR 28.530 Clarification on network slice related identifiers | Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑202366 | |||
S5‑202193 | Rel-16 CR 28.531 Clarification on network slice related identifiers | Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑202367 | |||
S5‑202367 | Rel-16 CR 28.531 Clarification on network slice related identifiers | Huawei | CR | Approval | Yes |
Yes
| agreed | No | S5‑202193 | |||
S5‑202194 | Rel-16 CR 28.541 Stage 3 update for clarification on network slice related identifiers | Huawei | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑202195 | LS to SA2 on network slice identifiers | Huawei | LS out | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑202201 | Discussion paper on non-binary description of neighbor cell relations | Nokia Germany | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑202203 | Rel-16 CR TS 28.622 Add TOP_ as parent class | ZTE Corporation | CR | Agreement | Yes |
Yes
| revised | No | S5‑202376 | |||
S5‑202376 | Rel-16 CR TS 28.622 Add TOP_ as parent class | ZTE Corporation | CR | Agreement | Yes |
Yes
| agreed | No | S5‑202203 | |||
S5‑202204 | Rel-16 CR 28.541 Extend description of NRCellRelation | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑202205 | Discussion paper on non-binary description of neighbor cell relations | Nokia, Nokia Shanghai Bell | discussion | Agreement | Yes |
Yes
| noted | No | ||||
S5‑202206 | Rel-16 CR TS 28.541 Add TOP_ as parent class | ZTE Corporation | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑202207 | Rel-16 CR TS 28.541 Correct sNSSAI definition in XML solution | ZTE Corporation | CR | Agreement | Yes |
Yes
| revised | No | S5‑202380 | |||
S5‑202380 | Rel-16 CR TS 28.541 Correct sNSSAI definition in XML solution | ZTE Corporation | CR | Agreement | Yes |
Yes
| agreed | No | S5‑202207 | |||
S5‑202212 | Update YANG Guidelines | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| revised | No | S5‑202381 | |||
S5‑202381 | Update YANG Guidelines | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| agreed | No | S5‑202212 | |||
S5‑202219 | CR TS 28.622 Update concept of ME and MF | Huawei Technologies (Korea) | CR | Yes |
Yes
| revised | No | S5‑202377 | ||||
S5‑202377 | CR TS 28.622 Update concept of ME and MF | Huawei Technologies (Korea) | CR | - | Yes |
Yes
| agreed | No | S5‑202219 | |||
S5‑202235 | Rel-16 CR TS 28.622 Update the attribute priorityLabel for several IOCs | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑202236 | Rel-16 CR TS 28.541 Clarify the NR NRM used for different deployment scenarios | Huawei,China Mobile | CR | Agreement | Yes |
Yes
| revised | No | S5‑202379 | |||
S5‑202379 | Rel-16 CR TS 28.541 Clarify the NR NRM used for different deployment scenarios | Huawei,China Mobile | CR | Agreement | Yes |
Yes
| agreed | No | S5‑202236 | |||
S5‑202250 | Discussion on the NRM of MF contains other MF | China Mobile E-Commerce Co., Huawei | discussion | Discussion | Yes |
Yes
| noted | No | ||||
S5‑202253 | Rel-16 CR TS 28.622 Updated MF description with nested clarification | China Mobile E-Commerce Co., Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑202378 | |||
S5‑202378 | Rel-16 CR TS 28.622 Updated MF description with nested clarification | China Mobile E-Commerce Co., Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑202253 | |||
S5‑202262 | Rel-16 CR 28.541 Add missing notification types to the definition of common notifications | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑202269 | Rel-16 CR TS 28.541 Update on NRCellDU | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑202371 | |||
S5‑202371 | Rel-16 CR TS 28.541 Update on NRCellDU | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑202269 | |||
S5‑202270 | Rel-15 CR TS 28.541 Update on NRCellDU | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑202372 | |||
S5‑202372 | Rel-15 CR TS 28.541 Update on NRCellDU | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑202270 | |||
S5‑202271 | Rel-16 CR TS 28.541 Update Clause 4.2.1.2 Inheritance UML diagram | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑202373 | |||
S5‑202373 | Rel-16 CR TS 28.541 Update Clause 4.2.1.2 Inheritance UML diagram | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑202271 | |||
S5‑202272 | Rel-15 CR TS 28.541 Update Clause 4.2.1.2 Inheritance UML diagram | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑202374 | |||
S5‑202374 | Rel-15 CR TS 28.541 Update Clause 4.2.1.2 Inheritance UML diagram | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑202272 | |||
S5‑202281 | TD proposal of NRM change to support RIM | Nokia, Nokia Shanghai Bell | discussion | Agreement | Yes |
Yes
| revised | No | S5‑202369 | |||
S5‑202369 | TD proposal of NRM change to support RIM | Nokia, Nokia Shanghai Bell | discussion | Agreement | Yes |
Yes
| endorsed | No | S5‑202281 | |||
S5‑202282 | new NRM fragment to support RIM stage 2 | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑202370 | |||
S5‑202370 | new NRM fragment to support RIM stage 2 | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑202282 | |||
S5‑202283 | new NRM fragment to support RIM stage 3 | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑202342 | |||
S5‑202342 | new NRM fragment to support RIM stage 3 | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑202283 | |||
S5‑202297 | Update stage3 on the RRMpolicyRatio | Huawei,Ericsson, CATT, China Telecom, China Mobile | CR | Agreement | Yes |
Yes
| agreed | No | ||||
6.4.6 | Trace Management in the context of Services Based Management Architecture | S5‑202292 | Rel-16 CR 28.622 Add trace control NRM fragment stage 2 | Nokia | CR | Approval | Yes |
Yes
| revised | No | S5‑202320 | |
S5‑202320 | Rel-16 CR 28.622 Add trace control NRM fragment stage 2 | Nokia | CR | Approval | Yes |
Yes
| agreed | No | S5‑202292 | |||
S5‑202293 | Rel-16 CR 28.622 Add trace control NRM fragment stage 3 | Nokia | CR | Approval | No |
Yes
| revised | No | S5‑202296 | |||
S5‑202296 | Rel-16 CR 28.623 Add trace control NRM fragment stage 3 | Nokia | CR | Approval | Yes |
Yes
| revised | No | S5‑202321 | S5‑202293 | ||
S5‑202321 | Rel-16 CR 28.623 Add trace control NRM fragment stage 3 | Nokia | CR | Approval | Yes |
Yes
| agreed | No | S5‑202296 | |||
6.4.7 | Closed loop SLS Assurance | S5‑202154 | Discussion paper on CSI clarification in close loop control context | Huawei | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑202384 | |
S5‑202384 | Discussion paper on CSI clarification in close loop control context | Huawei | discussion | Endorsement | Yes |
Yes
| endorsed | No | S5‑202154 | |||
S5‑202202 | Rel-16 pCR TS 28.535 update of use case in subclause 6.1.1 | HuaWei Technologies Co., Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑202395 | |||
S5‑202395 | Rel-16 pCR TS 28.535 update of use case in subclause 6.1.1 | HuaWei Technologies Co., Ltd | pCR | Approval | Yes |
Yes
| approved | No | S5‑202202 | |||
S5‑202218 | Update Clause 4.2 Management control loops | Huawei Technologies (Korea) | pCR | Yes |
Yes
| noted | No | |||||
S5‑202224 | Update clause 6.2 requirements | Huawei Technologies (Korea) | pCR | Yes |
Yes
| revised | No | S5‑202382 | ||||
S5‑202382 | Update clause 6.2 requirements | Huawei Technologies (Korea) | pCR | - | Yes |
Yes
| approved | No | S5‑202224 | |||
S5‑202237 | pCR TS 28.535 Move Annex A Management control loop in different layers to TS 28.536 | Huawei,China Mobile | pCR | Approval | Yes |
Yes
| revised | No | S5‑202340 | |||
S5‑202340 | pCR TS 28.535 Move Annex A Management control loop in different layers to TS 28.536 | Huawei,China Mobile | pCR | Approval | Yes |
Yes
| approved | No | S5‑202237 | |||
S5‑202238 | pCR TS 28.536 Move and update Annex A Management control loop in different later from TS 28.535 | Huawei,China Mobile | pCR | Approval | Yes |
Yes
| revised | No | S5‑202341 | |||
S5‑202341 | pCR TS 28.536 Move and update Annex A Management control loop in different later from TS 28.535 | Huawei,China Mobile | pCR | Approval | Yes |
Yes
| approved | No | S5‑202238 | |||
S5‑202247 | TS28.535 pCR clarify service load in use case fro interaction with core network for service assurance | China Mobile E-Commerce Co., Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑202383 | |||
S5‑202383 | TS28.535 pCR clarify service load in use case fro interaction with core network for service assurance | China Mobile E-Commerce Co., Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑202247 | |||
S5‑202248 | TS 28.535 pCR Add business level use case and requirements | China Mobile E-Commerce Co., Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑202258 | pCR TS 28.536 Communication service assurance stage 2 solution | Ericsson LM | pCR | Agreement | Yes |
Yes
| revised | No | S5‑202399 | |||
S5‑202399 | pCR TS 28.536 Communication service assurance stage 2 solution | Ericsson LM,Nokia,Deutsche Telekom | pCR | Agreement | Yes |
Yes
| approved | No | S5‑202258 | |||
S5‑202259 | pCR TS 28.536 Assurance data | Ericsson LM | pCR | Agreement | Yes |
Yes
| noted | No | ||||
S5‑202260 | pCR TS 28.536 Add the procedure of NWDAF assisted SLA assurance | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑202261 | pCR TS 28.536 Add list of interfaces in 4.1.1 | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑202274 | NWDAF assisted CSI SLS Assurance MnS and Procedure | Samsung Electronics France SA | pCR | Agreement | Yes |
Yes
| noted | No | ||||
S5‑202397 | draft TS 28.535 | Ericsson | draft TS | Approval | Yes |
Yes
| approved | No | ||||
S5‑202398 | draft TS 28.536 | Ericsson | draft TS | Approval | Yes |
Yes
| approved | No | ||||
6.4.8 | Streaming trace reporting | S5‑202287 | Rel-16 CR 28.532 Add streaming trace data reporting service stage 2 definition | Nokia | CR | Approval | Yes |
Yes
| revised | No | S5‑202385 | |
S5‑202385 | Rel-16 CR 28.532 Add streaming trace data reporting service stage 2 definition | Nokia | CR | Approval | Yes |
Yes
| agreed | No | S5‑202287 | |||
S5‑202288 | Rel-16 CR 28.532 Add streaming trace data reporting service stage 3 mapping of operations | Nokia | CR | Approval | Yes |
Yes
| revised | No | S5‑202386 | |||
S5‑202386 | Rel-16 CR 28.532 Add streaming trace data reporting service stage 3 mapping of operations | Nokia | CR | Approval | Yes |
Yes
| agreed | No | S5‑202288 | |||
S5‑202289 | Rel-16 CR 28.532 Add streaming trace data reporting service stage 3 resources | Nokia | CR | Approval | Yes |
Yes
| revised | No | S5‑202387 | |||
S5‑202387 | Rel-16 CR 28.532 Add streaming trace data reporting service stage 3 resources | Nokia | CR | Approval | Yes |
Yes
| agreed | No | S5‑202289 | |||
S5‑202290 | Rel-16 CR 28.532 Add streaming trace data reporting service stage 3 data types | Nokia | CR | Approval | Yes |
Yes
| revised | No | S5‑202388 | |||
S5‑202388 | Rel-16 CR 28.532 Add streaming trace data reporting service stage 3 data types | Nokia | CR | Approval | Yes |
Yes
| agreed | No | S5‑202290 | |||
S5‑202291 | Rel-16 CR 28.532 Add streaming trace data reporting service stage 3 open API definition | Nokia | CR | Approval | Yes |
Yes
| revised | No | S5‑202389 | |||
S5‑202389 | Rel-16 CR 28.532 Add streaming trace data reporting service stage 3 open API definition | Nokia | CR | Approval | Yes |
Yes
| agreed | No | S5‑202291 | |||
6.4.9 | Self-Organizing Networks (SON) for 5G networks | S5‑202027 | Reply LS ccSA5 on Information Needed for MRO in UE RLF Report | R2-2002393 | LS in | Yes |
Yes
| noted | No | |||
S5‑202040 | pCR 28.313 changes to PCI configuration | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑202327 | |||
S5‑202327 | pCR 28.313 changes to PCI configuration | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| approved | No | S5‑202040 | |||
S5‑202041 | pCR 28.313 revise MRO use case, requirements, information, and procedure | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑202306 | |||
S5‑202306 | pCR 28.313 revise MRO use case, requirements, information, and procedure | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| approved | No | S5‑202041 | |||
S5‑202042 | pCR 28.313 changes to RACH optimization | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑202326 | |||
S5‑202326 | pCR 28.313 changes to RACH optimization | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| approved | No | S5‑202042 | |||
S5‑202043 | Rel-16 CR 28.552 Add measurements related to RACH optimization | Intel Corporation (UK) Ltd | CR | Approval | Yes |
Yes
| revised | No | S5‑202349 | |||
S5‑202349 | Rel-16 CR 28.552 Add measurements related to RACH optimization | Intel Corporation (UK) Ltd | CR | Approval | Yes |
Yes
| not pursued | No | S5‑202043 | |||
S5‑202044 | Rel-16 CR 28.552 Add handover measurements related to MRO | Intel Corporation (UK) Ltd | CR | Approval | Yes |
Yes
| revised | No | S5‑202325 | |||
S5‑202325 | Rel-16 CR 28.552 Add handover measurements related to MRO | Intel Corporation (UK) Ltd | CR | Approval | Yes |
Yes
| agreed | No | S5‑202044 | |||
S5‑202084 | Replace DN with better identifier for whitelists and blacklists management | Ericsson France S.A.S | discussion | Endorsement | Yes |
Yes
| endorsed | No | ||||
S5‑202085 | Replace DN with better identifier for whitelists and blacklists management | Ericsson France S.A.S | CR | Approval | Yes |
Yes
| revised | No | S5‑202303 | |||
S5‑202303 | Replace DN with better identifier for whitelists and blacklists management | Ericsson France S.A.S | CR | Approval | Yes |
Yes
| agreed | No | S5‑202085 | |||
S5‑202110 | Discussion paper for PCI related measurement | Intel Corporation (UK) Ltd | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑202111 | Rel-16 CR 28.552 Add PCI related measurement of candidate cells | Intel Corporation (UK) Ltd | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑202185 | CR TS 28.541 Add the NRM fragement for SON management | Huawei, Orange, Intel | CR | Approval | Yes |
Yes
| revised | No | S5‑202330 | |||
S5‑202330 | CR TS 28.541 Add the NRM fragement for SON management | Huawei, Orange, Intel | CR | Approval | Yes |
Yes
| agreed | No | S5‑202185 | |||
S5‑202186 | CR TS 28.541 ANR management for EN-DC architecture | Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑202328 | |||
S5‑202328 | CR TS 28.541 ANR management for EN-DC architecture | Huawei | CR | Approval | Yes |
Yes
| agreed | No | S5‑202186 | |||
S5‑202187 | pCR TS 28.313 clarification on RAN-related discriptions of SON management service | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑202322 | |||
S5‑202322 | pCR TS 28.313 clarification on RAN-related discriptions of SON management service | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑202187 | |||
S5‑202188 | pCR TS 28.313 Clarification on the D-SON terminologies | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑202323 | |||
S5‑202323 | pCR TS 28.313 Clarification on the D-SON terminologies | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑202188 | |||
S5‑202189 | LS for D-SON management | Huawei | LS out | Approval | Yes |
Yes
| noted | No | ||||
S5‑202209 | pCR TS 28.313 Management service description | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑202245 | pCR 28.313 Update usecase and procedures for establishment of a new RAN NE in network | Huawei,China Telecom | pCR | Approval | Yes |
Yes
| revised | No | S5‑202329 | S5‑201585 | ||
S5‑202329 | pCR 28.313 Update usecase and procedures for establishment of a new RAN NE in network | Huawei,China Telecom | pCR | Approval | Yes |
Yes
| approved | No | S5‑202245 | |||
S5‑202346 | draft TS 28.313 | Intel | draft TS | Approval | Yes |
Yes
| approved | No | ||||
6.4.10 | Enhancement of 3GPP management system for multiple tenant environment support | S5‑202155 | Rel-16 CR TS 28.530 Extend roles related to 5G networks and network slicing management | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑202334 | |
S5‑202334 | Rel-16 CR TS 28.530 Extend roles related to 5G networks and network slicing management | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑202155 | |||
S5‑202156 | Rel-16 CR TS 28.530 Update use case exposure of network slice management data for network slice as a service | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑202157 | Rel-16 CR TS 28.533 Clarify management framework support in multiple tenant environment | Huawei | CR | Agreement | Yes |
Yes
| merged | No | S5‑202331 | |||
S5‑202158 | Rel-16 CR TS 28.541 Add tenantList attribute to ServiceProfile | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑202159 | Revised WID on enhancement of 3GPP management system for multiple tenant envorinment support | Huawei | WID revised | Approval | Yes |
Yes
| revised | No | S5‑202335 | |||
S5‑202335 | Revised WID on enhancement of 3GPP management system for multiple tenant envorinment support | Huawei | WID revised | Approval | Yes |
Yes
| agreed | No | S5‑202159 | |||
S5‑202160 | Rel-16 CR 28.550 Clarify performance measurement for a tenant | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑202332 | |||
S5‑202332 | Rel-16 CR 28.550 Clarify performance measurement for a tenant | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑202160 | |||
S5‑202161 | Rel-16 CR 28.552 Clarify performance indicators exposed to a tenant | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑202333 | |||
S5‑202333 | Rel-16 CR 28.552 Clarify performance indicators exposed to a tenant | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑202161 | |||
S5‑202217 | Rel16 CR 28.533 Add clarifications to description of tenant concept | Telefónica S.A. | CR | Agreement | Yes |
Yes
| revised | No | S5‑202331 | |||
S5‑202331 | Rel16 CR 28.533 Add clarifications to description of tenant concept | Telefónica S.A. | CR | Agreement | Yes |
Yes
| agreed | No | S5‑202217 | |||
6.5 | Rel-17 Operations, Administration, Maintenance and Provisioning (OAM&P) |   | ||||||||||
6.5.1 | Network policy management for 5G mobile networks based on NFV scenarios |   | ||||||||||
6.5.2 | Intent driven management service for mobile networks |   | ||||||||||
6.5.3 | Enhancements on EE for 5G networks |   | ||||||||||
6.5.4 | Management of non-public networks |   | ||||||||||
6.5.5 | Enhancement on Management Aspects of 5G Service-Level Agreement |   | ||||||||||
6.5.6 | Management of MDT enhancement in 5G |   | ||||||||||
6.5.7 | Additional NRM features |   | ||||||||||
6.5.8 | Enhancement of QoE Measurement Collection |   | ||||||||||
6.5.9 | Self-Organizing Networks (SON) for 5G networks |   | ||||||||||
6.5.10 | Enhanced Closed loop SLS Assurance |   | ||||||||||
6.6 | OAM&P Studies |   | ||||||||||
6.6.1 | Study on protocol enhancement for real time communication |   | ||||||||||
6.6.2 | Study on non-public networks management | S5‑202026 | Reply LS to SA5 on CAG definition | R2-2001703 | LS in | Yes |
Yes
| noted | No | |||
S5‑202133 | pCR 28.807 Add requirements for management of SNPN and PNI-NPN | TELEFONICA S.A. | pCR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑202196 | pCR 28.807 Use PNI-NPN terminology | Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑202197 | pCR 28.807 Rapporteur clean up proposal | Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑202198 | pCR 28.807 clarification on NPN supported by network slice instance of a PLMN | Huawei, Telefónica S.A. | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑202199 | pCR 28.807 Add CAG configuration requirement | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑202336 | |||
S5‑202336 | pCR 28.807 Add CAG configuration requirement | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑202199 | |||
S5‑202200 | pCR 28.807 Add management requirement | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑202337 | |||
S5‑202337 | pCR 28.807 Add management requirement | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑202200 | |||
S5‑202215 | pCR 28.807 Add requirements for management of SNPN and PNI-NPN | Telefónica S.A., Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑202338 | |||
S5‑202338 | pCR 28.807 Add requirements for management of SNPN and PNI-NPN | Telefónica S.A., Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑202215 | |||
S5‑202216 | pCR 28.807 Neutral host in the management of PNI-NPN | Telefónica S.A. | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑202273 | pCR 28.807 Additional considerations on NPN | Orange, Telefonica | pCR | Approval | Yes |
Yes
| revised | No | S5‑202339 | |||
S5‑202339 | pCR 28.807 Additional considerations on NPN | Orange, Telefonica | pCR | Approval | Yes |
Yes
| approved | No | S5‑202273 | |||
S5‑202347 | draft TS 28.807 | Huawei | draft TS | Approval | Yes |
Yes
| approved | No | ||||
6.6.3 | Study on management and orchestration aspects with integrated satellite components in a 5G network |   | ||||||||||
6.6.4 | Study on autonomous network levels | S5‑202119 | pCR 28.810 Update capacity optimization scenario example for network autonomy level | CATT, China Mobile | pCR | Approval | Yes |
Yes
| revised | No | S5‑202390 | |
S5‑202390 | pCR 28.810 Update capacity optimization scenario example for network autonomy level | CATT, China Mobile,Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑202119 | |||
S5‑202239 | pCR 28.810 Update Clause 5.3 NE deployment scenario example for classification of network autonomy levels | Huawei,China Mobile | pCR | Approval | Yes |
Yes
| revised | No | S5‑202391 | |||
S5‑202391 | pCR 28.810 Update Clause 5.3 NE deployment scenario example for classification of network autonomy levels | Huawei,China Mobile | pCR | Approval | Yes |
Yes
| approved | No | S5‑202239 | |||
S5‑202240 | pCR 28.810 Update Clause 5.2 Coverage optimization scenario example for classification of network autonomy levels | Huawei,China Mobile | pCR | Approval | Yes |
Yes
| revised | No | S5‑202392 | |||
S5‑202392 | pCR 28.810 Update Clause 5.2 Coverage optimization scenario example for classification of network autonomy levels | Huawei,China Mobile | pCR | Approval | Yes |
Yes
| approved | No | S5‑202240 | |||
S5‑202246 | pCR 28.810 Update Clause 4.4 Potential dimensions for classification of network autonomy | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑202393 | |||
S5‑202393 | pCR 28.810 Update Clause 4.4 Potential dimensions for classification of network autonomy | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑202246 | |||
S5‑202249 | pCR 28.810 Update Clause 5 Scenarios | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| merged | No | S5‑202393 | |||
S5‑202254 | pCR 28.810 Update Clause 5.1 Fault RCA and recovery scenario example for classification of network autonomy | China Mobile, Huawei, CATT | pCR | Approval | Yes |
Yes
| revised | No | S5‑202394 | |||
S5‑202394 | pCR 28.810 Update Clause 5.1 Fault RCA and recovery scenario example for classification of network autonomy | China Mobile, Huawei, CATT | pCR | Approval | Yes |
Yes
| approved | No | S5‑202254 | |||
S5‑202396 | draft TR 28.810 | China mobile | draft TR | Approval | Yes |
Yes
| approved | No | ||||
6.6.5 | Study on enhancement of Management Data Analytics Service |   | ||||||||||
6.6.6 | Study on network slice management enhancements |   | ||||||||||
6.6.7 | Study on new aspects of EE for 5G networks |   | ||||||||||
6.6.8 | Study on management aspects of edge computing |   | ||||||||||
7 | Charging |   | ||||||||||
7.1 | Charging Plenary | S5‑202022 | LS Out to SA2 and SA5 on making PSCELL ID available at the SGW of EPC | ETSI TC LI | LS in | Yes |
Yes
| postponed | No | |||
S5‑202294 | CH Agenda and Time Plan | SA5 Vice Chair (Nokia) | agenda | Approval | Yes |
Yes
| revised | No | S5‑202405 | |||
S5‑202405 | CH Agenda and Time Plan | SA5 Vice Chair (Nokia) | agenda | Approval | Yes |
Yes
| approved | No | S5‑202294 | |||
7.2 | New Charging Work Item proposals |   | ||||||||||
7.3 | Charging Maintenance and Rel-16 small Enhancements | S5‑202053 | Rel-16 CR 32.290 Default handling for one time events | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||
S5‑202054 | Rel-16 CR 32.291 Default handling for one time events | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑202055 | Rel-16 CR 32.255 Correcting charging characteristics category to mandatory | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑202056 | Rel-16 CR 32.291 Correcting charging characteristics category to mandatory | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑202057 | Rel-16 CR 32.298 Correcting charging characteristics category to mandatory | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑202058 | Rel-16 CR 32.255 Correcting triggers as mandatory for QFI container | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑202059 | Rel-16 CR 32.291 Correcting triggers as mandatory for QFI container | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑202060 | Rel-16 CR 32.255 Correcting time and volume as mandatory for Qos flow usage reporting | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑202061 | Rel-16 CR 32.291 Correcting time and volume as mandatory for Qos flow usage reporting | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑202062 | Rel-16 CR 32.290 Correction of local sequence number handling | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑202063 | Rel-16 CR 32.240 Correcting reference point naming for non-5G | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑202064 | Rel-16 CR 32.255 Missing network slice instance identifier for QBC | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑202065 | Rel-16 CR 32.291 Missing network slice info for QBC | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑202433 | |||
S5‑202433 | Rel-16 CR 32.291 Missing network slice info for QBC | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑202065 | |||
S5‑202066 | Rel-16 CR 32.298 Missing network slice instance identifier for QBC | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑202067 | Rel-15 CR 32.291 Missing AMF as network function | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑202068 | Rel-16 CR 32.291 Missing AMF as network function | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑202069 | Rel-16 CR 32.298 Correction of startOfServiceDataFlowNoSession naming | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑202461 | |||
S5‑202461 | Rel-16 CR 32.298 Correction of startOfServiceDataFlowNoSession naming | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑202069 | |||
S5‑202070 | Rel-15 CR 32.298 Missing trigger for GFBR guaranteed status change | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑202071 | Rel-16 CR 32.298 Missing trigger for GFBR guaranteed status change | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑202072 | Rel-16 CR 32.298 Missing I-SMF as network function | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑202434 | |||
S5‑202073 | Rel-16 CR 32.298 Missing QoS characteristics in QFI container | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑202435 | |||
S5‑202074 | Rel-16 CR 32.298 Missing time in QFI container | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑202436 | |||
S5‑202075 | Rel-16 CR 32.291 Missing event limit in trigger type | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑202437 | |||
S5‑202076 | Rel-16 CR 32.291 Missing constraint of SMSC Address | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑202077 | Rel-16 CR 32.291 Missing downlink volume in QFI container | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑202078 | Rel-16 CR 32.291 Correction of content problem, callback and version | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑202120 | Rel-15 CR 32.298 Correction of UserLocationInformation | China Mobile Com. Corporation | CR | Yes |
Yes
| not pursued | No | |||||
S5‑202121 | Rel-16 CR 32.298 Correction of UserLocationInformation | China Mobile Com. Corporation | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑202162 | Rel-16 CR 32.254 Add the Retransmission Indicator | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑202417 | |||
S5‑202163 | Rel-16 CR 32.255 Add the Retransmission Indicator | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑202418 | |||
S5‑202164 | Rel-16 CR 32.256 Add the Retransmission Indicator | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑202419 | |||
S5‑202165 | Rel-16 CR 32.291 Add the Retransmission Indicator in Open API | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑202420 | |||
S5‑202166 | Rel-16 CR 32.254 Correct the message content for NEF charging | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑202421 | |||
S5‑202167 | Rel-16 CR 32.256 Correct the Event offline charging scenarios | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑202422 | |||
S5‑202168 | Rel-16 CR 32.291 Correct the PDU Address | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑202169 | Rel-15 CR 32.291 Add the reference about the storage of OPENAPI in FORGE | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑202170 | Rel-16 CR 32.291 Add the reference about the storage of OPENAPI in FORGE | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑202431 | |||
S5‑202171 | Rel-15 CR 32.290 Correction on Service Termination | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑202172 | Rel-16 CR 32.290 Correction on Service Termination | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑202432 | |||
S5‑202173 | Rel-16 CR 32.255 Add PDU address for IPv6 multi-homing | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑202174 | Rel-16 CR 32.291 Add PDU address for IPv6 multi-homing | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑202175 | Rel-16 CR 32.298 Add PDU address for IPv6 multi-homing | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑202241 | Rel-16 CR 32.291 Correction of NodeFunctionality | China Mobile Com. Corporation | CR | Approval | Yes |
Yes
| revised | No | S5‑202411 | |||
S5‑202252 | Rel-16 CR 32.255 Correction of Charging Identifier definition | China Mobile Com. Corporation | CR | Approval | Yes |
Yes
| revised | No | S5‑202413 | |||
S5‑202285 | Rel-15 CR 32.298 Correction ASN.1 imported module version | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑202286 | Rel-16 CR 32.298 Correction ASN.1 imported module version | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑202402 | Rel-15 CR 32.298 Correction of startOfServiceDataFlowNoSession naming | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑202411 | Rel-16 CR 32.291 Correction of NodeFunctionality | China Mobile Com. Corporation | CR | Approval | Yes |
Yes
| agreed | No | S5‑202241 | |||
S5‑202412 | Rel-16 CR 32.255 Correction of Serving Network Function Functionality for I-SMF | China Mobile Com. Corporation | CR | Approval | Yes |
Yes
| agreed | No | S5‑202401 | |||
S5‑202413 | Rel-16 CR 32.255 Correction of Charging Identifier definition | China Mobile Com. Corporation | CR | Approval | Yes |
Yes
| agreed | No | S5‑202252 | |||
S5‑202417 | Rel-16 CR 32.254 Add the Retransmission Indicator | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑202162 | |||
S5‑202418 | Rel-16 CR 32.255 Add the Retransmission Indicator | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑202163 | |||
S5‑202419 | Rel-16 CR 32.256 Add the Retransmission Indicator | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑202164 | |||
S5‑202420 | Rel-16 CR 32.291 Add the Retransmission Indicator in Open API | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑202165 | |||
S5‑202421 | Rel-16 CR 32.254 Correct the message content for NEF charging | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑202166 | |||
S5‑202422 | Rel-16 CR 32.256 Correct the Event offline charging scenarios | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑202167 | |||
S5‑202431 | Rel-16 CR 32.291 Add the reference about the storage of OPENAPI in FORGE | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑202170 | |||
S5‑202432 | Rel-16 CR 32.290 Correction on Service Termination | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑202172 | |||
S5‑202434 | Rel-16 CR 32.298 Missing I-SMF as network function | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑202072 | |||
S5‑202435 | Rel-16 CR 32.298 Missing QoS characteristics in QFI container | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑202073 | |||
S5‑202436 | Rel-16 CR 32.298 Missing time in QFI container | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑202074 | |||
S5‑202437 | Rel-16 CR 32.291 Missing event limit in trigger type | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑202075 | |||
S5‑202401 | Rel-16 CR 32.255 Correction of Serving Network Function Functionality for I-SMF | China Mobile Com. Corporation | CR | Discussion | No |
Yes
| revised | No | S5‑202412 | |||
7.4 | Rel-16 Charging |   | ||||||||||
7.4.1 | IMS Charging in 5G System Architecture |   | ||||||||||
7.4.2 | Network Slice Performance and Analytics Charging in 5G System | S5‑202079 | Rel-16 pCR 28.201 Introduction of flows for NWDAF for subscribing to analytics information | Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S5‑202439 | |
S5‑202080 | Rel-16 pCR 28.201 Introduction of MnS service consumption | Ericsson | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑202081 | Rel-16 pCR 28.201 Update of triggers | Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S5‑202440 | |||
S5‑202082 | Rel-16 pCR 28.201 Adding charging data request and response message | Ericsson | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑202134 | LS on NWDAF for Network Slice Performance and Analytics Charging | Huawei | LS out | Agreement | Yes |
Yes
| noted | No | ||||
S5‑202135 | Rel-16 pCR 28.201 Add the general message flows description in clause 5.2 | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑202425 | |||
S5‑202136 | Rel-16 pCR 28.201 Add the NWDAF and MnS producer message flows description | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑202427 | |||
S5‑202137 | Rel-16 pCR 28.201 Add the Charging Data request and response | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑202438 | |||
S5‑202138 | Rel-16 pCR 28.201 Add the Network slice performance and analytics CHF CDR data | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑202430 | |||
S5‑202139 | Rel-16 pCR 28.201 Add detailed message format for converged charging | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑202428 | |||
S5‑202140 | Rel-16 pCR 28.201 Remove the editor's note in clause 4 | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑202429 | |||
S5‑202141 | Rel-16 pCR 28.201 Remove the editor's note in clause 5.1.5 | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑202424 | |||
S5‑202142 | Rel-16 pCR 28.201 Remove the editor's note in clause 5.2.1.1 | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑202423 | |||
S5‑202143 | Rel-16 CR 32.290 API definition for network slice performance and analytics charging | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑202144 | Rel-16 pCR 28.201 Add charging requirements | Huawei | pCR | Agreement | Yes |
Yes
| noted | No | ||||
S5‑202416 | Rel-16 pCR 28.201 Add charging requirements | Huawei | pCR | Agreement | Yes |
Yes
| withdrawn | Yes | ||||
S5‑202423 | Rel-16 pCR 28.201 Remove the editor's note in clause 5.2.1.1 | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑202142 | |||
S5‑202424 | Rel-16 pCR 28.201 Remove the editor's note in clause 5.1.5 | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑202141 | |||
S5‑202425 | Rel-16 pCR 28.201 Add the general message flows description in clause 5.2 | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑202135 | |||
S5‑202427 | Rel-16 pCR 28.201 Add the NWDAF and MnS producer message flows description | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑202136 | |||
S5‑202428 | Rel-16 pCR 28.201 Add detailed message format for converged charging | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑202139 | |||
S5‑202429 | Rel-16 pCR 28.201 Remove the editor's note in clause 4 | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑202140 | |||
S5‑202430 | Rel-16 pCR 28.201 Add the Network slice performance and analytics CHF CDR data | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑202138 | |||
S5‑202438 | Rel-16 pCR 28.201 Add the Charging Data request and response | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑202137 | |||
S5‑202439 | Rel-16 pCR 28.201 Introduction of flows for NWDAF for subscribing to analytics information | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S5‑202079 | |||
S5‑202440 | Rel-16 pCR 28.201 Update of triggers | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S5‑202081 | |||
S5‑202403 | Draft TS 28.201 | Huawei | draft TS | Approval | Yes |
Yes
| approved | No | ||||
7.4.3 | Network Slice Management Charging in 5G System | S5‑202039 | Rel-16 pCR 28.202 Create initial text for the Scope clause | Openet Telecom | pCR | Approval | Yes |
Yes
| revised | No | S5‑202426 | |
S5‑202083 | Rel-16 pCR 28.202 Introduction of architecture considerations | Ericsson | pCR | Approval | Yes |
Yes
| merged | No | S5‑202442 | |||
S5‑202092 | DP Charging architecture for Network Slice Management Charging in 5GS | Nokia, Nokia Shanghai Bell | discussion | Discussion | Yes |
Yes
| noted | No | ||||
S5‑202093 | Rel-16 pCR 28.202 Introduce symbols abbreviations and references | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑202441 | |||
S5‑202094 | Rel-16 pCR 28.202 Introduce Architecture | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑202442 | |||
S5‑202095 | Rel-16 pCR 28.202 Introduce Charging Principles | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑202443 | |||
S5‑202096 | Rel-16 pCR 28.202 Introduce NS management Charging scenarios principles | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑202444 | |||
S5‑202097 | Rel-16 pCR 28.202 Introduce NS management charging triggers and flows | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑202445 | |||
S5‑202098 | Rel-16 pCR 28.202 Introduce CDR generation | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑202446 | |||
S5‑202099 | Rel-16 pCR 28.202 Introduce Message content | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑202447 | |||
S5‑202100 | Rel-16 pCR 28.202 Introduce NS management charging information | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑202448 | |||
S5‑202426 | Rel-16 pCR 28.202 Create initial text for the Scope clause | Openet Telecom | pCR | Approval | Yes |
Yes
| approved | No | S5‑202039 | |||
S5‑202441 | Rel-16 pCR 28.202 Introduce symbols abbreviations and references | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑202093 | |||
S5‑202442 | Rel-16 pCR 28.202 Introduce Architecture | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑202094 | |||
S5‑202443 | Rel-16 pCR 28.202 Introduce Charging Principles | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑202095 | |||
S5‑202444 | Rel-16 pCR 28.202 Introduce NS management Charging scenarios principles | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑202096 | |||
S5‑202445 | Rel-16 pCR 28.202 Introduce NS management charging triggers and flows | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑202097 | |||
S5‑202446 | Rel-16 pCR 28.202 Introduce CDR generation | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑202098 | |||
S5‑202447 | Rel-16 pCR 28.202 Introduce Message content | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑202099 | |||
S5‑202448 | Rel-16 pCR 28.202 Introduce NS management charging information | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑202100 | |||
S5‑202400 | Charging architecture for Network Slice Charging in 5GS | Nokia, Nokia Shanghai Bell | discussion | Information | Yes |
Yes
| noted | No | ||||
S5‑202404 | Draft TS 28.202 | Nokia | draft TS | Approval | Yes |
Yes
| approved | No | ||||
7.4.4 | Charging Access Traffic Steering, Switching and Splitting in 5G system architecture | S5‑202007 | S5-201156 Rel-16 CR 32.255 Introduction of ATSSS triggers | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑202449 | |
S5‑202264 | Rel-16 CR 32.255 Introduction of MA PDU session indicator | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑202450 | |||
S5‑202265 | Rel-16 CR 32.255 Clarify ATSSS when same rating group for 3GPP and non-3GPP | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑202451 | |||
S5‑202266 | Rel-16 CR 32.255 Introduction of ATSSS Roaming Home Routed Network requested | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑202267 | Rel-16 CR 32.255 Introduction of ATSSS Roaming Home Routed UE requested | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑202452 | |||
S5‑202268 | Rel-16 CR 32.255 Introduction of ATSSS EPS interworking | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑202449 | S5-201156 Rel-16 CR 32.255 Introduction of ATSSS triggers | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑202007 | |||
S5‑202450 | Rel-16 CR 32.255 Introduction of MA PDU session indicator | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑202264 | |||
S5‑202451 | Rel-16 CR 32.255 Clarify ATSSS when same rating group for 3GPP and non-3GPP | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑202265 | |||
S5‑202452 | Rel-16 CR 32.255 Introduction of ATSSS Roaming Home Routed UE requested | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑202267 | |||
7.4.5 | Charging Aspect for 5WWC | S5‑202176 | Rel-16 CR 32.291 Add description on identifier for 5G RG and FN RG | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑202410 | |
S5‑202177 | Rel-16 CR 32.255 Add 5WWC charging information | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑202415 | |||
S5‑202178 | Rel-16 CR 32.255 Add procedure for 5G-RG handover | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑202414 | |||
S5‑202179 | Rel-16 CR 32.255 Add trigger for access network handover | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑202410 | Rel-16 CR 32.291 Add description on identifier for 5G RG and FN RG | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑202176 | |||
S5‑202414 | Rel-16 CR 32.255 Add procedure for 5G-RG handover | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑202178 | |||
S5‑202415 | Rel-16 CR 32.255 Add 5WWC charging information | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑202177 | |||
7.4.6 | CHF-controlled quota management | S5‑202180 | Rel-16 CR 32.290 Addition of suspend or resume quota management | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||
S5‑202181 | Rel-16 CR 32.291 Addition of suspend or resume quota management | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑202263 | DP CHF- controlled quota management impact beyond SMF | Nokia, Nokia Shanghai Bell | discussion | Discussion | Yes |
Yes
| noted | No | ||||
S5‑202277 | Add CHF-Controlled Quota Management functionality | Amdocs Software Systems Ltd | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑202284 | Add Quota Management new data types | Amdocs Software Systems Ltd | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
8 | Any Other Business |   | ||||||||||
9 | Closing of the meeting |   |