Tdoc List
2019-01-25 15:11
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‑191000 | Agenda | WG Chairman | agenda | Yes |
Yes
| approved | No | |||
3 | IPR declaration | S5‑191001 | IPR and legal declaration | WG Chairman | other | Yes |
Yes
| noted | No | |||
4 | Meetings and activities reports |   | ||||||||||
4.1 | Last SA5 meeting report | S5‑191002 | Report from last SA5 meeting | MCC | report | Yes |
Yes
| approved | No | |||
4.2 | Last SA meeting report | S5‑191305 | SA5 status report at last SA meeting | WG Chair | other | Information | Yes |
Yes
| noted | No | ||
S5‑191306 | SA5 results at last SA meeting | WG Chair | other | Information | Yes |
Yes
| noted | No | ||||
4.3 | Inter-organizational reports |   | ||||||||||
5 | Cross-SWG issues |   | ||||||||||
5.1 | Administrative issues at SA5 level | S5‑191003 | Leaders meeting agenda | WG Chairman | agenda | Yes |
Yes
| noted | No | |||
S5‑191004 | Leaders meeting minutes | WG Chairman | report | Yes |
Yes
| noted | No | |||||
S5‑191005 | SA5 Working Procedures | WG Vice Chair (Huawei) | other | Yes |
Yes
| noted | No | |||||
S5‑191006 | SA5 Meeting Facility Requirements | WG Vice Chair (Orange) | other | No |
Yes
| withdrawn | Yes | |||||
S5‑191007 | Process for management of draft TSs/TRs | WG Chairman | other | Yes |
Yes
| noted | No | |||||
S5‑191008 | CR Quality Check | MCC | other | Yes |
YesMirko (MCC) commented that NETSLICE Rel-15 CRs with cat-B or wrong cat-F were being still sent. He recommended to start discussing a Rel-16 WID to address these changes since it was too late to keep adding features to Rel-15 and it would be hard to defend this at Plenary level.
| noted | No | |||||
S5‑191009 | Status of email approvals | WG Vice Chair (Orange) | other | No |
No
| reserved | No | |||||
5.2 | Technical issues at SA5 level |   | ||||||||||
5.3 | Liaison statements at SA5 level | S5‑191282 | Reply LS from CT4 cc SA5 on API specification and API version number maintenance | C4-188646 | LS in | Yes |
YesMaryse (Nokia) commented that Charging SWG would follow the guidelines in TS 29.501. Charging will answer the LS in their Charging meeting.
Olaf (Nokia) commented that CT4's requirements and SA5's were different.
Ericsson commented that this was not agreable to them and that there were unfinished email discussions.
| noted | No | |||
S5‑191283 | Ls Response from BBF to 3GPP SA2 cc SA5 liaison S2-1811575 on ‘general status of work’ | BBF | LS in | Yes |
Yes
| noted | No | |||||
S5‑191284 | LS Response from BBF cc SA5 to 3GPP SA2 liaison S2-1812643 | BBF | LS in | Yes |
Yes
| noted | No | |||||
S5‑191286 | LS from ETSI ISG NFV to SA5 on Publication of SOL001 V 2.5.1 | ETSI ISG NFV | LS in | Yes |
Yes
| noted | No | |||||
S5‑191287 | Lsout from ETSI NFV to 3GPP SA5 on NFV Specification Adoption | ETSI ISG NFV | LS in | Yes |
YesJan (Ericsson) asked whether SA5 had to create CRs to update the specifications as a result of this. An action point for OAM was created for that effect.
| noted | No | |||||
S5‑191288 | LS from ITU-T to SA5 on Draft new Recommendation E.RQST – “KPI targets for mobile networks” | ITU-T SG12 | LS in | Yes |
YesORANGE commented that they were referring to 800 series TRs, which wasn't normative and in some cases really early work that wasn't relevant anymore.
It was postponed in order to prepare a proper response.
| postponed | No | |||||
S5‑191293 | LS from ITU-T to SA5 on consent of Recommendation Y.3103 (formerly Y.IMT2020-BM) (reply to 3GPP TSG SA5 -LS15) | ITU-T SG13 | LS in | Yes |
YesORANGE: there are some common things, although their scope is very large. They don’t seem eager to colaborate or try to get to a converging solution.
| noted | No | |||||
S5‑191294 | LS from ITU-T to SA5 on Update of Technical Report – “Transport network support of IMT-2020/5G” | ITU-T SG15 | LS in | Yes |
YesIntel considered that this should be discussed, so it was decided to postpone it.
| postponed | No | |||||
5.4 | SA5 meeting calendar | S5‑191010 | SA5 Meeting Calendar | WG Chairman | other | Yes |
YesEricsson commented that RAN2 and RAN3 would be late in March 2020 so in some cases SA5 could get to those dates if our work depended on their work.
| noted | No | |||
5.5 | Review of the Work Plan | S5‑191011 | 3GPP SA5 Work Plan | MCC | other | Yes |
Yes
| noted | No | |||
6 | OAM&P |   | ||||||||||
6.1 | OAM&P Plenary | S5‑191012 | Time Plan for OAM&P | WG Vice Chair (Huawei) | other | Yes |
Yes
| noted | No | |||
S5‑191338 | Time Plan for OAM&P | WG Vice Chair (Huawei) | other | - | No |
Yes
| withdrawn | Yes | ||||
S5‑191013 | OAM Executive Report | WG Vice Chair (Huawei) | report | Yes |
Yes
| revised | No | S5‑191503 | ||||
S5‑191503 | OAM Executive Report | WG Vice Chair (Huawei) | report | - | No |
Yes
| noted | No | S5‑191013 | |||
S5‑191014 | OAM&P SWG action list | WG Vice Chair (Huawei) | other | Yes |
Yes
| revised | No | S5‑191395 | ||||
S5‑191395 | OAM&P SWG action list | WG Vice Chair (Huawei) | other | - | Yes |
Yes
| revised | No | S5‑191493 | S5‑191014 | ||
S5‑191493 | OAM&P SWG action list | WG Vice Chair (Huawei) | other | - | Yes |
Yes
| noted | No | S5‑191395 | |||
S5‑191015 | Minutes of OAM&P SWG opening session | WG Vice Chair (ORANGE) | report | Yes |
Yes
| noted | No | |||||
S5‑191074 | Improvement of handling of revisions in OAM&P SWG | OAM&P SWG chair | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑191339 | |||
S5‑191339 | Improvement of handling of revisions in OAM&P SWG | OAM&P SWG chair | discussion | Endorsement | Yes |
Yes
| endorsed | No | S5‑191074 | |||
S5‑191242 | LS reply on energy efficiency | Orange Romania | LS out | Agreement | Yes |
Yes
| revised | No | S5‑191344 | |||
S5‑191344 | LS reply on energy efficiency | Orange Romania | LS out | Approval | Yes |
Yes
| approved | No | S5‑191242 | |||
S5‑191271 | LS on Reply on Reply LS on Slice related Data Analytics | Ericsson Telecomunicazioni SpA | LS out | Approval | Yes |
Yes
| revised | No | S5‑191342 | |||
S5‑191342 | LS on Reply on Reply LS on Slice related Data Analytics | Ericsson Telecomunicazioni SpA | LS out | Approval | Yes |
Yes
| approved | No | S5‑191271 | |||
S5‑191280 | Ls from GSMA cc SA5 on Cooperation on Generic Slice Template definition | GSMA | LS in | Yes |
Yes
| noted | No | |||||
S5‑191289 | Reply LS from RAn3 cc SA5 on QoS monitoring | R3-187051 | LS in | Yes |
Yes
| noted | No | |||||
S5‑191290 | Ls from SA2 to SA5 on Collection of Slice Related Data Analytics from UEs | S2-1813384 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑191340 | Reply to: Ls from SA2 to SA5 on Collection of Slice Related Data Analytics from UEs | Ericsson | LS out | approval | Yes |
Yes
| approved | No | ||||
S5‑191291 | LS from SA2 to SA5 on slice related Data Analytics | S2-1813404 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑191292 | Reply LS from SA4 to SA5 on Attributes for QoE measurement collection | S4-181418 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑191343 | Reply to: Reply LS from SA4 to SA5 on Attributes for QoE measurement collection | Ericsson | LS out | approval | Yes |
Yes
| approved | No | ||||
S5‑191295 | Resubmitted Ls from ITU-T to SA5 on Energy Efficiency (reply to ETSI TC EE - EE(18)053033-E) | ITU-T SG5 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑191461 | Overview of the 5G specification strcuture | Huawei | discussion | Information | Yes |
Yes
| noted | No | ||||
6.2 | New OAM&P Work Item proposals | S5‑191016 | Minutes of New Work Item proposals - OAM&P | WG Vice Chair (Ericsson) | report | Yes |
Yes
| noted | No | |||
S5‑191196 | New WID on Study on non-public networks management | Huawei | SID new | Approval | Yes |
Yes
| revised | No | S5‑191345 | |||
S5‑191345 | New Study on non-public networks management | Huawei | SID new | Agreement | Yes |
Yes
| agreed | No | S5‑191196 | |||
S5‑191232 | New SID: Study on management and orchestration aspects with integrated satellite components in a 5G networks | THALES | SID new | Approval | Yes |
Yes
| revised | No | S5‑191346 | |||
S5‑191346 | New SID: Study on management and orchestration aspects with integrated satellite components in a 5G network | THALES | SID new | Agreement | Yes |
Yes
| revised | No | S5‑191412 | S5‑191232 | ||
S5‑191412 | New SID: Study on management and orchestration aspects with integrated satellite components in a 5G network | THALES | SID new | Agreement | Yes |
Yes
| agreed | No | S5‑191346 | |||
S5‑191235 | Discussion on a new Work Item proposal on integration of 3GPP and ONAP | AT&T, Deutsche Telekom, Ericsson, Huawei, Nokia, Orange | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑191347 | |||
S5‑191347 | Discussion on a new Work Item proposal on integration of 3GPP and ONAP | AT&T, Deutsche Telekom, Ericsson, Huawei, Nokia, Orange | discussion | Endorsement | Yes |
Yes
| endorsed | No | S5‑191235 | |||
S5‑191237 | New WID proposal on integration of ONAP and 3GPP management framework | AT&T, Orange | WID new | Approval | Yes |
Yes
| revised | No | S5‑191348 | |||
S5‑191348 | New WID proposal on integration of ONAP and 3GPP management framework | AT&T, Orange,Deutsche Telekom | WID new | Agreement | Yes |
Yes
| revised | No | S5‑191413 | S5‑191237 | ||
S5‑191413 | New WID proposal on integration of ONAP and 3GPP management framework | AT&T, Orange,Deutsche Telekom | WID new | Agreement | Yes |
Yes
| agreed | No | S5‑191348 | |||
S5‑191303 | Supporting document for S5-19123 (Proposed New SID on Management and orchestration aspects with integrated satellite components in a 5G networks) | THALES | discussion | Discussion | Yes |
Yes
| noted | No | ||||
6.3 | OAM&P Maintenance and Rel-16 small Enhancements | S5‑191017 | Minutes of OAM&P Maintenance and Rel-16 small Enhancements | MCC | report | Yes |
Yes
| noted | No | |||
S5‑191066 | CR Rel-15 28.552 Revise performance measurements for UDM | Huawei Telecommunication India | CR | Yes |
Yes
| revised | No | S5‑191349 | ||||
S5‑191349 | CR Rel-15 28.552 Revise performance measurements for UDM | Huawei Telecommunication India | CR | - | Yes |
Yes
| revised | No | S5‑191414 | S5‑191066 | ||
S5‑191414 | CR Rel-15 28.552 Revise performance measurements for UDM | Huawei Telecommunication India | CR | - | Yes |
Yes
| agreed | No | S5‑191349 | |||
S5‑191067 | CR Rel-16 28.552 Revise performance measurements for UDM | Huawei Telecommunication India | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑191350 | CR Rel-16 28.552 Revise performance measurements for UDM | Huawei Telecommunication India | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
S5‑191068 | CR Rel-15 28.554 Revise KPI subscribers of single network slice instance through UDM | Huawei Telecommunication India | CR | Agreement | Yes |
Yes
| revised | No | S5‑191351 | |||
S5‑191351 | CR Rel-15 28.554 Revise KPI subscribers of single network slice instance through UDM | Huawei Telecommunication India | CR | Agreement | Yes |
Yes
| revised | No | S5‑191494 | S5‑191068 | ||
S5‑191494 | CR Rel-15 28.554 Revise KPI subscribers of single network slice instance through UDM | Huawei Telecommunication India | CR | Agreement | Yes |
Yes
| agreed | No | S5‑191351 | |||
S5‑191069 | CR Rel-16 28.554 Revise KPI subscribers of single network slice instance through UDM | Huawei Telecommunication India | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑191352 | CR Rel-16 28.554 Revise KPI subscribers of single network slice instance through UDM | Huawei Telecommunication India | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
S5‑191075 | Update State management data definition Solution Set to support JSON | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑191353 | Update State management data definition Solution Set to support JSON | Nokia, Nokia Shanghai Bell | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
S5‑191077 | R15 CR 28.541 Add definition of beam IOC | ZTE Corporation | CR | Agreement | Yes |
Yes
| revised | No | S5‑191354 | |||
S5‑191354 | R15 CR 28.541 Add NRM Info Model definitions for beam managed object class | Pivotal Commware, Intel, PIWorks, ZTE | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑191077 | |||
S5‑191078 | R15 CR TS 28.532 change notificationIRP to notificationMnSProducer | ZTE Corporation | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑191082 | Cell and frequency relation | Ericsson Hungary Ltd | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑191355 | |||
S5‑191355 | Cell and frequency relation | Ericsson Hungary Ltd | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑191500 | S5‑191082 | ||
S5‑191500 | Cell and frequency relation | Ericsson Hungary Ltd | discussion | Endorsement | No |
Yes
| left for email approval | No | S5‑191355 | |||
S5‑191084 | CR Rel-15 28541 Add NR attributes | Ericsson Inc. | CR | Approval | Yes |
Yes
| revised | No | S5‑191356 | S5‑186363 | ||
S5‑191356 | CR Rel-15 28541 Add NR attributes | Ericsson Inc. | CR | Approval | Yes |
Yes
| agreed | No | S5‑191084 | |||
S5‑191085 | TS 28541 use of nCI and plmnIdList | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| revised | No | S5‑191357 | |||
S5‑191357 | TS 28541 correct the use of nCI and plmnIdList | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| agreed | No | S5‑191085 | |||
S5‑191116 | Add exposure governance related use case and business level requirement | Huawei Telecommunication India | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
S5‑191117 | Add exposure governance related use case and business level requirement | Huawei Telecommunication India | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑191118 | Add exposure governance related use case and business level requirement | Huawei Telecommunication India | CR | Agreement | Yes |
Yes
| revised | No | S5‑191358 | |||
S5‑191358 | Add exposure governance related use case and business level requirement | Huawei Telecommunication India | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑191118 | |||
S5‑191134 | Rel-15 CR TS 28.531 Update management services tables | Huawei | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑191135 | Rel-16 CR TS 28.531 Update management services tables | Huawei | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑191136 | Rel-15 CR TS 28.531 Correction on procedure of Network Slice Subnet Instance Deallocation | Huawei | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑191137 | Rel-16 CR TS 28.531 Correction on procedure of Network Slice Subnet Instance Deallocation | Huawei | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑191138 | Rel-15 CR TS 28.532 Add stage 2 and stage 3 definition for MnS Query | Huawei | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑191139 | Rel-15 CR TS 28.541 Remove duplicate definition for ExternalNRCellCU | Huawei | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑191140 | Rel-15 CR TS 28.541 Correct class diagram for view on external entities | Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑191462 | |||
S5‑191462 | Rel-15 CR TS 28.541 Correct class diagram for view on external entities | Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑191501 | S5‑191140 | ||
S5‑191501 | Rel-15 CR TS 28.541 Correct class diagram for view on external entities | Huawei | CR | Approval | No |
Yes
| left for email approval | No | S5‑191462 | |||
S5‑191141 | Rel-15 CR TS 28.532 Correction of references | Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑191359 | |||
S5‑191359 | Rel-15 CR TS 28.532 Correction of references | Huawei | CR | Approval | Yes |
Yes
| agreed | No | S5‑191141 | |||
S5‑191142 | Rel-15 CR TS 28.541 Correct the definition for resourceSharingLevel | Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑191440 | |||
S5‑191440 | Rel-15 CR TS 28.541 Correct the definition for resourceSharingLevel | Huawei | CR | Approval | Yes |
Yes
| agreed | No | S5‑191142 | |||
S5‑191149 | CR Rel-15 28.550 Add the missing RESTFul API definitions | Intel | CR | Agreement | Yes |
Yes
| revised | No | S5‑191397 | |||
S5‑191397 | CR Rel-15 28.550 Add the missing RESTFul API definitions | Intel | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑191149 | |||
S5‑191150 | Discussion paper on stage 3 protocol for performance data streaming | Intel | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑191418 | |||
S5‑191418 | Discussion paper on stage 3 protocol for performance data streaming | Intel | discussion | Endorsement | Yes |
Yes
| endorsed | No | S5‑191150 | |||
S5‑191151 | CR Rel-15 28.552 Editorial clean-up | Intel, Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑191419 | |||
S5‑191419 | CR Rel-15 28.552 Editorial clean-up | Intel, Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑191151 | |||
S5‑191152 | CR Rel-16 28.552 Editorial clean-up | Intel,Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑191420 | |||
S5‑191420 | CR Rel-16 28.552 Editorial clean-up | Intel,Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑191152 | |||
S5‑191203 | CR Rel-11 28.658 Correct PLMN ID List Type in Solution Set Stage 2 | Ericsson GmbH, Eurolab | CR | Approval | Yes |
Yes
| revised | No | S5‑191421 | S5‑187427 | ||
S5‑191421 | CR Rel-11 28.658 Correct PLMN ID List Type in Stage 2 | Ericsson GmbH, Eurolab | CR | Approval | Yes |
Yes
| agreed | No | S5‑191203 | |||
S5‑191204 | Correction of references | Ericsson España S.A. | CR | Agreement | Yes |
Yes
| revised | No | S5‑191427 | |||
S5‑191427 | Correction of references | Ericsson España S.A. | CR | Agreement | Yes |
Yes
| agreed | No | S5‑191204 | |||
S5‑191205 | CR Rel-12 28.658 Correct PLMN ID List Type in Solution Set Stage 2 | Ericsson GmbH, Eurolab | CR | Approval | Yes |
Yes
| revised | No | S5‑191422 | S5‑187428 | ||
S5‑191422 | CR Rel-12 28.658 Correct PLMN ID List Type in Stage 2 | Ericsson GmbH, Eurolab | CR | Approval | Yes |
Yes
| agreed | No | S5‑191205 | |||
S5‑191206 | CR Rel-13 28.658 Correct PLMN ID List Type in Solution Set Stage 2 | Ericsson GmbH, Eurolab | CR | Approval | Yes |
Yes
| revised | No | S5‑191423 | S5‑187429 | ||
S5‑191423 | CR Rel-13 28.658 Correct PLMN ID List Type in Stage 2 | Ericsson GmbH, Eurolab | CR | Approval | Yes |
Yes
| agreed | No | S5‑191206 | |||
S5‑191207 | Removal of reference to a temporary joint working group | Ericsson España S.A. | CR | Approval | Yes |
Yes
| revised | No | S5‑191428 | |||
S5‑191428 | Removal of reference to a temporary joint working group | Ericsson España S.A. | CR | Approval | Yes |
Yes
| agreed | No | S5‑191207 | |||
S5‑191208 | CR Rel-14 28.658 Correct PLMN ID List Type in Solution Set Stage 2 | Ericsson GmbH, Eurolab | CR | Approval | Yes |
Yes
| revised | No | S5‑191424 | S5‑187430 | ||
S5‑191424 | CR Rel-14 28.658 Correct PLMN ID List Type in Stage 2 | Ericsson GmbH, Eurolab | CR | Approval | Yes |
Yes
| agreed | No | S5‑191208 | |||
S5‑191209 | Removal of reference to a temporary joint working group | Ericsson España S.A. | CR | Approval | Yes |
Yes
| revised | No | S5‑191429 | |||
S5‑191429 | Removal of reference to a temporary joint working group | Ericsson España S.A. | CR | Approval | Yes |
Yes
| agreed | No | S5‑191209 | |||
S5‑191210 | CR Rel-15 28.658 Correct PLMN ID List Type in Solution Set Stage 2 | Ericsson GmbH, Eurolab | CR | Approval | Yes |
Yes
| revised | No | S5‑191425 | S5‑187431 | ||
S5‑191425 | CR Rel-15 28.658 Correct PLMN ID List Type in Stage 2 | Ericsson GmbH, Eurolab | CR | Approval | Yes |
Yes
| agreed | No | S5‑191210 | |||
S5‑191211 | CR Rel-16 28.658 Correct PLMN ID List Type in Solution Set Stage 2 | Ericsson GmbH, Eurolab | CR | Approval | Yes |
Yes
| revised | No | S5‑191426 | |||
S5‑191426 | CR Rel-16 28.658 Correct PLMN ID List Type in Stage 2 | Ericsson GmbH, Eurolab | CR | Approval | Yes |
Yes
| agreed | No | S5‑191211 | |||
S5‑191212 | Resolution of Editor's note | Ericsson España S.A. | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑191213 | Resolution of Editor's note | Ericsson España S.A. | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑191214 | Resolution of Editor's note | Ericsson España S.A. | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑191215 | Resolution of Editor's note | Ericsson España S.A. | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑191216 | Resolution of Editor's note | Ericsson España S.A. | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑191217 | CR Rel-11 28.659 Correct PLMN ID Type in Solution Set Stage 3 | Ericsson GmbH, Eurolab | CR | Approval | Yes |
Yes
| agreed | No | S5‑187432 | |||
S5‑191218 | CR Rel-12 28.659 Correct PLMN ID Type in Solution Set Stage 3 | Ericsson GmbH, Eurolab | CR | Approval | Yes |
Yes
| agreed | No | S5‑187433 | |||
S5‑191219 | CR Rel-13 28.659 Correct PLMN ID Type in Solution Set Stage 3 | Ericsson GmbH, Eurolab | CR | Approval | Yes |
Yes
| agreed | No | S5‑187434 | |||
S5‑191220 | CR Rel-14 28.659 Correct PLMN ID Type in Solution Set Stage 3 | Ericsson GmbH, Eurolab | CR | Approval | Yes |
Yes
| agreed | No | S5‑187435 | |||
S5‑191221 | CR Rel-15 28.659 Correct PLMN ID Type in Solution Set Stage 3 | Ericsson GmbH, Eurolab | CR | Approval | Yes |
Yes
| agreed | No | S5‑187436 | |||
S5‑191222 | CR Rel-16 28.659 Correct PLMN ID Type in Solution Set Stage 3 | Ericsson GmbH, Eurolab | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑191241 | Update Generic NRM Solution Set to support JSON | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑191261 | Add read-only NRM Info Model definitions for NRBeam IOC and attributes | Pivotal Commware | CR | Approval | Yes |
Yes
| merged | No | S5‑191354 | |||
S5‑191437 | Removal of reference to a temporary joint working group | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑191438 | Removal of reference to a temporary joint working group | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑191439 | Removal of reference to a temporary joint working group | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑191447 | Removal of reference to a temporary joint working group | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
6.4 | Rel-16 Operations, Administration, Maintenance and Provisioning (OAM&P) |   | ||||||||||
6.4.1 | Management of QoE measurement collection | S5‑191018 | Minutes of Management of QoE measurement collection | Rapporteur (Ericsson) | report | Yes |
Yes
| noted | No | |||
S5‑191296 | pCR R16 28.307-010 Including DASH and MTSI in Scope | Ericsson | pCR | Yes |
Yes
| approved | No | |||||
S5‑191297 | pCR R16 28.307-010 Restrict to UMTS and LTE | Ericsson | pCR | Yes |
Yes
| approved | No | |||||
S5‑191298 | pCR R16 28.404-050 Introduce the use case and requirement for changing QoE measurement collection job | Ericsson | pCR | Yes |
Yes
| revised | No | S5‑191361 | ||||
S5‑191361 | pCR R16 28.404-050 Introduce the use case and requirement for changing QoE measurement collection job | Ericsson | pCR | - | Yes |
Yes
| revised | No | S5‑191415 | S5‑191298 | ||
S5‑191415 | pCR R16 28.404-050 Introduce the use case and requirement for changing QoE measurement collection job | Ericsson | pCR | - | Yes |
Yes
| approved | No | S5‑191361 | |||
S5‑191299 | pCR R16 28.404-050 Refer to specification level requirements and use cases | Ericsson | pCR | Yes |
Yes
| approved | No | |||||
S5‑191300 | Presentation of Specification to TSG: TS 28.404 | Ericsson | TS or TR cover | Yes |
Yes
| approved | No | |||||
S5‑191360 | Draft TS 28.307 | Ericsson | draft TS | Approval | No |
Yes
| left for email approval | No | ||||
S5‑191362 | Draft TS 28.404 | Ericsson | draft TS | Approval | No |
Yes
| left for email approval | No | ||||
6.4.2 | Energy Efficiency of 5G | S5‑191019 | Minutes of Energy effciency of 5G | Rapporteur (ORANGE) | report | Yes |
Yes
| noted | No | |||
S5‑191038 | pCR TS 28.310 – Add use cases and requirements on data streaming | Orange Romania | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑191039 | pCR TS 28.310 – Add use case on PEE fault supervision, actor roles and telecommunication resources | Orange Romania | pCR | Approval | Yes |
Yes
| revised | No | S5‑191364 | |||
S5‑191364 | pCR TS 28.310 – Add use case on PEE fault supervision, actor roles and telecommunication resources | Orange Romania | pCR | Approval | Yes |
Yes
| approved | No | S5‑191039 | |||
S5‑191040 | Add Power, Energy and Environmental (PEE) measurements and related use case description | Orange Romania | CR | Agreement | Yes |
Yes
| revised | No | S5‑191365 | |||
S5‑191365 | Add Power, Energy and Environmental (PEE) measurements and related use case description | Orange Romania | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑191040 | |||
S5‑191265 | Discussion paper around Data Volume measurement for EE | Ericsson GmbH, Eurolab | discussion | Endorsement | Yes |
Yes
| endorsed | No | ||||
S5‑191266 | CR Rel-16 28.552 Add PDCP data volume measurements for EE | Ericsson GmbH, Eurolab | CR | Approval | Yes |
Yes
| revised | No | S5‑191366 | |||
S5‑191366 | CR Rel-16 28.552 Add PDCP data volume measurements for EE | Ericsson GmbH, Eurolab | CR | Approval | Yes |
Yes
| agreed | No | S5‑191266 | |||
S5‑191363 | Draft TS 28.310 | ORANGE | draft TS | Approval | No |
Yes
| left for email approval | No | ||||
6.4.3 | OAM aspects of LTE and WLAN integration | S5‑191020 | Minutes of Study on OAM aspects of LTE and WLAN integration | Rapporteur (Intel) | report | Yes |
Yes
| noted | No | |||
S5‑191164 | CR Rel-16 28.658 Enhance ENBFunction for LWIP management | Intel | CR | Agreement | Yes |
Yes
| revised | No | S5‑191367 | |||
S5‑191367 | CR Rel-16 28.658 Enhance ENBFunction for LWIP management | Intel | CR | Agreement | Yes |
Yes
| agreed | No | S5‑191164 | |||
S5‑191165 | CR Rel-16 28.659 Enhance ENBFunction for LWIP management | Intel | CR | Agreement | Yes |
Yes
| revised | No | S5‑191368 | |||
S5‑191368 | CR Rel-16 28.659 Enhance ENBFunction for LWIP management | Intel | CR | Agreement | Yes |
Yes
| agreed | No | S5‑191165 | |||
S5‑191166 | CR Rel-16 32.425 Add measurements related to user data transmission via WLAN for LWIP | Intel | CR | Agreement | Yes |
Yes
| revised | No | S5‑191369 | |||
S5‑191369 | CR Rel-16 32.425 Add measurements related to user data transmission via WLAN for LWIP | Intel | CR | Agreement | Yes |
Yes
| agreed | No | S5‑191166 | |||
S5‑191167 | CR Rel-16 32.425 Add measurements related to RRC procedures for LWIP | Intel | CR | Agreement | Yes |
Yes
| revised | No | S5‑191370 | |||
S5‑191370 | CR Rel-16 32.425 Add measurements related to RRC procedures for LWIP | Intel | CR | Agreement | Yes |
Yes
| agreed | No | S5‑191167 | |||
6.4.4 | Network policy management for mobile networks based on NFV scenarios | S5‑191021 | Minutes of Network policy management for mobile networks based on NFV scenarios | Rapporteur (China Mobile) | report | No |
Yes
| withdrawn | Yes | |||
6.4.5 | Methodology for 5G management specifications | S5‑191022 | Minutes of Methodology for 5G management specifications | Rapporteur (Ericsson) | report | Yes |
Yes
| noted | No | |||
S5‑191083 | YANG solution style guide | Ericsson Hungary Ltd | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑191224 | Discussion paper on stage 2 template for data types | Ericsson Telecomunicazioni SpA | discussion | Endorsement | Yes |
Yes
| endorsed | No | ||||
S5‑191225 | pCR 32.160 Implement Edithelp comments | Ericsson Telecomunicazioni SpA | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑191226 | pCR 32.160 Update editors note on attributes | Ericsson Telecomunicazioni SpA | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑191227 | pCR 32.160 Introduce stage 2 template for data types | Ericsson Telecomunicazioni SpA | pCR | Approval | Yes |
Yes
| revised | No | S5‑191371 | |||
S5‑191371 | pCR 32.160 Introduce stage 2 template for data types | Ericsson Telecomunicazioni SpA | pCR | Approval | Yes |
Yes
| approved | No | S5‑191227 | |||
S5‑191264 | Some thoughts on XML, JSON and YANG style guides | Nokia Corporation | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑191372 | Draft TS 32.160 | Ericsson | draft TS | Approval | No |
Yes
| left for email approval | No | ||||
6.4.6 | Intent driven management service for mobile networks | S5‑191023 | Minutes of Intent driven management service for mobile networks | Rapporteur (Huawei) | report | Yes |
Yes
| noted | No | |||
S5‑191062 | pCR 28.812 Role of a formal language | Ericsson Telecomunicazioni SpA | pCR | No |
Yes
| withdrawn | Yes | |||||
S5‑191063 | pCR 28.812 Abstraction versus layering | Ericsson Telecomunicazioni SpA | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑191064 | pCR 28.812 BSS layer intent scenario | Ericsson Telecomunicazioni SpA | pCR | Approval | Yes |
Yes
| revised | No | S5‑191373 | |||
S5‑191373 | pCR 28.812 BSS layer intent scenario | Ericsson Telecomunicazioni SpA | pCR | Approval | Yes |
Yes
| revised | No | S5‑191416 | S5‑191064 | ||
S5‑191416 | pCR 28.812 BSS layer intent scenario | Ericsson Telecomunicazioni SpA | pCR | Approval | Yes |
Yes
| approved | No | S5‑191373 | |||
S5‑191065 | pCR 28.812 Physical layer intent scenario | Ericsson Telecomunicazioni SpA | pCR | Approval | Yes |
Yes
| revised | No | S5‑191374 | |||
S5‑191374 | pCR 28.812 Physical layer intent scenario | Ericsson Telecomunicazioni SpA | pCR | Approval | Yes |
Yes
| revised | No | S5‑191487 | S5‑191065 | ||
S5‑191487 | pCR 28.812 Physical layer intent scenario | Ericsson Telecomunicazioni SpA | pCR | Approval | Yes |
Yes
| approved | No | S5‑191374 | |||
S5‑191120 | pCR 28.812 Reorganize clause 5 to categorize the scenarios | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑191375 | |||
S5‑191375 | pCR 28.812 Reorganize clause 5 to categorize the scenarios | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑191120 | |||
S5‑191121 | pCR 28.812 Add description for intent-CSP and Intent-NOP | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑191377 | |||
S5‑191377 | pCR 28.812 Add description for intent-CSP and Intent-NOP | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑191121 | |||
S5‑191122 | pCR 28.812 Add intent driven virtualized NE deployment scenario | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑191378 | |||
S5‑191378 | pCR 28.812 Add intent driven virtualized NE deployment scenario | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑191122 | |||
S5‑191123 | pCR 28.812 Update clause 4.1.3 Intent expression | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑191379 | |||
S5‑191379 | pCR 28.812 Update clause 4.1.3 Intent expression | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑191123 | |||
S5‑191124 | pCR 28.812 Add description of using domain specific language for intent expression | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑191199 | pCR28.812 Add intent driven NSI capacity planning scenario | ETRI | pCR | Approval | Yes |
Yes
| revised | No | S5‑191380 | |||
S5‑191380 | pCR28.812 Add intent driven NSI capacity planning scenario | ETRI | pCR | Approval | Yes |
Yes
| revised | No | S5‑191495 | S5‑191199 | ||
S5‑191495 | pCR28.812 Add intent driven NSI capacity planning scenario | ETRI | pCR | Approval | Yes |
Yes
| approved | No | S5‑191380 | |||
S5‑191200 | pCR28.812 Add intent driven NSI performance assurance scenario | ETRI | pCR | Approval | Yes |
Yes
| revised | No | S5‑191381 | |||
S5‑191381 | pCR28.812 Add intent driven NSI performance assurance scenario | ETRI | pCR | Approval | Yes |
Yes
| revised | No | S5‑191496 | S5‑191200 | ||
S5‑191496 | pCR28.812 Add intent driven NSI performance assurance scenario | ETRI | pCR | Approval | Yes |
Yes
| approved | No | S5‑191381 | |||
S5‑191376 | Draft TR 28.812 | Huawei | draft TR | Approval | No |
Yes
| left for email approval | No | ||||
6.4.7 | Enhancement of performance assurance for 5G networks including network slicing | S5‑191024 | Minutes of Enhancement of performance assurance for 5G networks including network slicing | Rapporteur (Intel) | report | Yes |
Yes
| noted | No | |||
S5‑191079 | R16 CR28.552 Add RSRP measurements | ZTE, Intel | CR | Agreement | Yes |
Yes
| revised | No | S5‑191382 | |||
S5‑191382 | R16 CR28.552 Add RSRP measurements | ZTE, Intel | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑191079 | |||
S5‑191080 | R16 CR28.552 Add UE Rx-Tx time difference related measurements | ZTE Corporation | CR | Agreement | Yes |
Yes
| revised | No | S5‑191383 | |||
S5‑191383 | R16 CR28.552 Add UE Rx-Tx time difference related measurements | ZTE Corporation | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑191080 | |||
S5‑191081 | R16 CR28.552 Add MCS distribution measurement | ZTE Corporation | CR | Agreement | Yes |
Yes
| merged | No | S5‑191441 | |||
S5‑191143 | Rel-16 CR TS 28.552 Add measurements of CQI distribution | Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑191384 | |||
S5‑191384 | Rel-16 CR TS 28.552 Add measurements of CQI distribution | Huawei | CR | Approval | Yes |
Yes
| agreed | No | S5‑191143 | |||
S5‑191144 | Rel-16 CR TS 28.552 Add measurements of MCS distribution | Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑191441 | |||
S5‑191441 | Rel-16 CR TS 28.552 Add measurements of MCS distribution | Huawei,ZTE | CR | Approval | Yes |
Yes
| agreed | No | S5‑191144 | |||
S5‑191145 | Rel-16 CR TS 28.552 Add measurements of QoS flow release | Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑191385 | |||
S5‑191385 | Rel-16 CR TS 28.552 Add measurements related to QoS flow retainability | Huawei | CR | Approval | Yes |
Yes
| agreed | No | S5‑191145 | |||
S5‑191146 | Rel-16 CR TS 28.554 Add KPI of E-RAB Retainability | Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑191386 | |||
S5‑191386 | Rel-16 CR TS 28.554 Add KPI of QoS flow Retainability | Huawei | CR | Approval | Yes |
Yes
| agreed | No | S5‑191146 | |||
S5‑191147 | Rel-16 CR TS 28.552 Add measurements of PDCP data volume in DC scenarios | Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑191387 | |||
S5‑191387 | Rel-16 CR TS 28.552 Add measurements of PDCP data volume in DC scenarios | Huawei | CR | Approval | Yes |
Yes
| agreed | No | S5‑191147 | |||
S5‑191148 | Rel-16 CR TS 28.552 Add QoS flow related performance measurements | Huawei, ZTE, Ericsson | CR | Approval | Yes |
Yes
| revised | No | S5‑191388 | |||
S5‑191388 | Rel-16 CR TS 28.552 Add QoS flow related performance measurements | Huawei, ZTE, Ericsson | CR | Approval | Yes |
Yes
| agreed | No | S5‑191148 | |||
S5‑191153 | Discussion paper on threshold monitoring | Intel | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑191154 | CR Rel-16 28.550 Add performance threshold monitoring service | Intel | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑191155 | CR Rel-16 28.552 Add QoS flow management related measurements for SMF | Intel | CR | Agreement | Yes |
Yes
| revised | No | S5‑191390 | |||
S5‑191390 | CR Rel-16 28.552 Add QoS flow management related measurements for SMF | Intel | CR | Agreement | Yes |
Yes
| agreed | No | S5‑191155 | |||
S5‑191163 | CR Rel-16 28.552 Add service request related measurements for AMF | Intel | CR | Agreement | Yes |
Yes
| revised | No | S5‑191389 | |||
S5‑191389 | CR Rel-16 28.552 Add service request related measurements for AMF | Intel | CR | Agreement | Yes |
Yes
| agreed | No | S5‑191163 | |||
S5‑191197 | Add use case and definitions of PDCP end user throughput measurements | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑191484 | |||
S5‑191484 | Add use case and definitions of PDCP end user throughput measurements | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑191197 | |||
S5‑191198 | Discussion on calculation of PDCP data volume in DC-Scenarios | Huawei | discussion | Yes |
Yes
| noted | No | |||||
S5‑191201 | CR Rel-16 28.552 Add measurements and UC related to RRC connection establishment | Ericsson GmbH, Eurolab | CR | Approval | Yes |
Yes
| revised | No | S5‑191392 | |||
S5‑191392 | CR Rel-16 28.552 Add measurements and UC related to RRC connection establishment | Ericsson GmbH, Eurolab | CR | Approval | Yes |
Yes
| agreed | No | S5‑191201 | |||
S5‑191202 | CR Rel-16 28.552 Add measurements and UC related to setup of NG signalling connection | Ericsson GmbH, Eurolab | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑191234 | Add definitions related to Utilization KPI | ETRI | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑191245 | Discussion paper around KPI for DRB Accessibility | Ericsson GmbH, Eurolab | discussion | Endorsement | Yes |
Yes
| endorsed | No | ||||
S5‑191248 | CR R-16 28.554 Add DRB Accessibility KPI and Use Case | Ericsson GmbH, Eurolab | CR | Approval | Yes |
Yes
| revised | No | S5‑191481 | |||
S5‑191481 | CR R-16 28.554 Add DRB Accessibility KPI and Use Case | Ericsson GmbH, Eurolab | CR | Approval | Yes |
Yes
| agreed | No | S5‑191248 | |||
S5‑191279 | R16 CR 28.552 Add Flow measurements for N3 | ETRI | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑191430 | R16 CR 28.552 Add Flow measurements for N3 | ETRI | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑191341 | discussion sequence | Intel | other | Information | Yes |
Yes
| noted | No | ||||
S5‑191391 | LS on use case and definitions of PDCP end user throughput measurements | Nokia | LS out | Approval | No |
Yes
| left for email approval | No | ||||
6.4.8 | Discovery of management services in 5G | S5‑191025 | Minutes of Discovery of management services in 5G | Rapporteur (Huawei) | report | Yes |
Yes
| noted | No | |||
S5‑191109 | Add discovery of MnS use cases and requirements | Huawei Telecommunication India | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
S5‑191110 | Add general information for discovery of MnS | Huawei Telecommunication India | CR | Agreement | Yes |
Yes
| revised | No | S5‑191463 | |||
S5‑191463 | Add general information for discovery of MnS | Huawei Telecommunication India,Cisco | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑191110 | |||
S5‑191111 | Add discovery of MnS capability | Huawei Telecommunication India | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
S5‑191112 | Discussion on TS 28.533 content inconsistency and way forward | Huawei Telecommunication India | discussion | Discussion | Yes |
Yes
| revised | No | S5‑191393 | |||
S5‑191393 | Discussion on TS 28.533 content inconsistency and way forward | Huawei Telecommunication India | discussion | Discussion | Yes |
Yes
| noted | No | S5‑191112 | |||
S5‑191114 | Revised WID on management service discovery in 5G network management | Huawei Telecommunication India | WID revised | Agreement | Yes |
Yes
| revised | No | S5‑191394 | |||
S5‑191394 | Revised WID on management service discovery in 5G network management | Huawei Telecommunication India | WID revised | Agreement | Yes |
Yes
| noted | No | S5‑191114 | |||
S5‑191119 | Add discovery of management service use case and business level requirement | Huawei Telecommunication India | CR | Agreement | Yes |
Yes
| revised | No | S5‑191396 | |||
S5‑191396 | Add discovery of management service use case and business level requirement | Huawei Telecommunication India | CR | Agreement | Yes |
Yes
| revised | No | S5‑191488 | S5‑191119 | ||
S5‑191488 | Add discovery of management service use case and business level requirement | Huawei Telecommunication India | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑191396 | |||
S5‑191169 | pCR to DraftCR S5-187464 cleanup | Cisco Systems Inc. | draftCR | Yes |
Yes
| noted | No | |||||
S5‑191170 | pCR to DraftCR S5-187530 cleanup | Cisco Systems Inc. | draftCR | Yes |
Yes
| noted | No | |||||
S5‑191223 | Add deployment example for discovery of MnS | Huawei Telecommunication India | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
S5‑191259 | Domain Names for Management Services | Nokia Corporation | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑191260 | DN to URI mapping | Nokia Corporation | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑191262 | Management Service discovery | Nokia Corporation | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑191263 | Issues with the allowed character set of DNs | Nokia Corporation | discussion | Yes |
Yes
| noted | No | |||||
6.4.9 | NRM enhancements | S5‑191026 | Minutes of NRM enhancements | Rapporteur (Nokia) | report | No |
Yes
| withdrawn | Yes | |||
6.4.10 | Trace Management in the context of Services Based Management Architecture | S5‑191027 | Minutes of Trace Management in the context of Services Based Management Architecture | Rapporteur (Nokia) | report | No |
Yes
| withdrawn | Yes | |||
6.5 | OAM&P Studies |   | ||||||||||
6.5.1 | Study on integration of ONAP DCAE and 3GPP management architecture | S5‑191028 | Minutes of Study on integration of ONAP DCAE and 3GPP management architecture | Rapporteur ORANGE) | report | Yes |
Yes
| noted | No | |||
S5‑191061 | pCR TS 28.890 - Conclusions on FM and PM | AT&T, ORANGE | pCR | Approval | Yes |
Yes
| revised | No | S5‑191436 | |||
S5‑191436 | pCR TS 28.890 - Conclusions on FM and PM | AT&T, ORANGE | pCR | Approval | Yes |
Yes
| approved | No | S5‑191061 | |||
S5‑191125 | pCR 28.890 Align the term MnS and MnF | Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑191126 | pCR 28.890 Update clause 5.2.2.3.1 mapping 3GPP alarm notification to ONAP R3 VES JSON API | Huawei | pCR | Approval | Yes |
Yes
| merged | No | S5‑191431 | |||
S5‑191127 | pCR 28.890 Update clause 5.2.3.3.3 Reporting 3GPP Rel-15 PM data to DCAE R3 VES JSON Collector | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑191433 | |||
S5‑191433 | pCR 28.890 Update clause 5.2.3.3.3 Reporting 3GPP Rel-15 PM data to DCAE R3 VES JSON Collector | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑191127 | |||
S5‑191128 | pCR 28.890 Add Handling of configuration notification | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑191174 | pCR TR 28890 Editorial and Minor Technical Corrections | AT&T, Orange | pCR | Yes |
Yes
| revised | No | S5‑191431 | ||||
S5‑191431 | pCR TR 28890 Editorial and Minor Technical Corrections | AT&T, Orange, Huawei,Ericsson | pCR | - | Yes |
Yes
| revised | No | S5‑191486 | S5‑191174 | ||
S5‑191486 | pCR TR 28890 Editorial and Minor Technical Corrections | AT&T, Orange, Huawei,Ericsson | pCR | - | Yes |
Yes
| approved | No | S5‑191431 | |||
S5‑191267 | pCR 28.890 Alarm Life Cycle management in ONAP | Ericsson España S.A. | pCR | Approval | Yes |
Yes
| revised | No | S5‑191434 | |||
S5‑191434 | pCR 28.890 Alarm Life Cycle management in ONAP | Ericsson España S.A. | pCR | Approval | Yes |
Yes
| approved | No | S5‑191267 | |||
S5‑191268 | pCR 28.890 Remove non-valid information | Ericsson España S.A. | pCR | Approval | Yes |
Yes
| merged | No | S5‑191431 | |||
S5‑191269 | pCR 28.890 Remove proposal to modifications to 3GPP specifications | Ericsson España S.A. | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑191435 | pCR 28.890 Remove proposal to modifications to 3GPP specifications | Ericsson España S.A. | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑191432 | Draft TR 28.890 | ORANGE | draft TR | Approval | No |
Yes
| left for email approval | No | ||||
6.5.2 | Study on integration of ONAP and 3GPP configuration management services for 5G networks | S5‑191029 | Minutes of Study on integration of ONAP and 3GPP configuration management services for 5G networks | Rapporteur (Ericsson) | report | Yes |
Yes
| noted | No | |||
S5‑191129 | pCR 28.890 Replace 3GPP managment system with 3GPP MnF | Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||||
6.5.3 | Study on protocol enhancement for real time communication | S5‑191030 | Minutes of Study on protocol enhancement for real time communication | Rapporteur(Nokia) | report | No |
Yes
| withdrawn | Yes | |||
6.5.4 | Study on management aspects of edge computing | S5‑191031 | Minutes of Study on management aspects of edge computing | Rapporteur (Intel) | report | Yes |
Yes
| noted | No | |||
S5‑191179 | pCR 28.803 use case for available UPF to support edge computing | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑191443 | |||
S5‑191443 | pCR 28.803 use case for available UPF to support edge computing | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| approved | No | S5‑191179 | |||
S5‑191180 | pCR 28.803 use case to NRF configuration | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑191417 | |||
S5‑191417 | pCR 28.803 use case to NRF configuration | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| approved | No | S5‑191180 | |||
S5‑191181 | pCR 28.803 solutions for UPF lifecycle management | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑191182 | pCR 28.803 solutions for SMF configuration | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑191445 | |||
S5‑191445 | pCR 28.803 solutions for SMF configuration | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| approved | No | S5‑191182 | |||
S5‑191183 | pCR 28.803 solution for NRF configuration | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑191446 | |||
S5‑191446 | pCR 28.803 solution for NRF configuration | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| approved | No | S5‑191183 | |||
S5‑191184 | pCR 28.803 use case for performance measurements to support edge computing | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑191448 | pCR 28.803 use case for performance measurements to support edge computing | Intel Corporation (UK) Ltd | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑191185 | pCR 28.803 use case for fault management to support edge computing | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑191449 | pCR 28.803 use case for fault management to support edge computing | Intel Corporation (UK) Ltd | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑191186 | pCR 28.803 use case for configuration management to support edge computing | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑191450 | |||
S5‑191450 | pCR 28.803 use case for configuration management to support edge computing | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| noted | No | S5‑191186 | |||
S5‑191285 | LS from ETSI ISG MEC to SA5 on Information on MEC work on 5G | ETSI ISG MEC | LS in | Yes |
Yes
| replied to | No | |||||
S5‑191302 | Reply LS on information on MEC work in 5G | Intel Corporation (UK) Ltd | LS out | Approval | Yes |
Yes
| revised | No | S5‑191442 | |||
S5‑191442 | Reply LS on information on MEC work in 5G | Intel Corporation (UK) Ltd | LS out | Approval | Yes |
Yes
| approved | No | S5‑191302 | |||
S5‑191444 | Draft TR 28.803 | Intel | draft TR | Approval | No |
Yes
| left for email approval | No | ||||
6.5.5 | Study on tenancy concept in 5G networks and network slicing management | S5‑191032 | Minutes of Study on tenancy concept in 5G networks and network slicing management | Rapporteur (Huawei) | report | Yes |
Yes
| noted | No | |||
S5‑191070 | Tenancy concept isolation | Huawei Telecommunication India | pCR | Approval | Yes |
Yes
| revised | No | S5‑191451 | |||
S5‑191451 | Tenancy concept isolation | Huawei Telecommunication India | pCR | Approval | Yes |
Yes
| noted | No | S5‑191070 | |||
S5‑191071 | Problem statement and open issues of tenancy concept in 3GPP management system | Huawei Telecommunication India | pCR | Approval | Yes |
Yes
| revised | No | S5‑191452 | |||
S5‑191452 | Problem statement and open issues of tenancy concept in 3GPP management system | Huawei Telecommunication India | pCR | Approval | Yes |
Yes
| noted | No | S5‑191071 | |||
S5‑191072 | Use case of management capability exposed to tenants related to communication service | Huawei Telecommunication India | pCR | Approval | Yes |
Yes
| revised | No | S5‑191453 | |||
S5‑191453 | Use case of management capability exposed to tenants related to communication service | Huawei Telecommunication India | pCR | Approval | Yes |
Yes
| noted | No | S5‑191072 | |||
S5‑191073 | Use case of 3GPP network as tenant accessing virtual resource environment | Huawei Telecommunication India | pCR | Approval | Yes |
Yes
| revised | No | S5‑191454 | |||
S5‑191454 | Use case of 3GPP network as tenant accessing virtual resource environment | Huawei Telecommunication India | pCR | Approval | Yes |
Yes
| noted | No | S5‑191073 | |||
S5‑191113 | Add tenancy concept of multiple exposure of same MnS with different management data isolation option | Huawei Telecommunication India | pCR | Approval | Yes |
Yes
| revised | No | S5‑191455 | |||
S5‑191455 | Add tenancy concept of multiple exposure of same MnS with different management data isolation option | Huawei Telecommunication India | pCR | Approval | Yes |
Yes
| noted | No | S5‑191113 | |||
S5‑191115 | Use cases for tenancy concept to access MnS capability | Huawei Telecommunication India | pCR | Agreement | Yes |
Yes
| revised | No | S5‑191456 | |||
S5‑191456 | Use cases for tenancy concept to access MnS capability | Huawei Telecommunication India | pCR | Agreement | Yes |
Yes
| noted | No | S5‑191115 | |||
6.5.6 | Study on management aspects of communication services | S5‑191033 | Minutes of Study on management aspects of communication services | Rapporteur (Ericsson) | report | Yes |
Yes
| noted | No | |||
S5‑191086 | Add UC and requirements for UE communication service status query | Huawei Telecommunication India | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑191187 | pCR 28.805 Reorganizing subclauses in clause 4 | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑191464 | |||
S5‑191464 | pCR 28.805 Reorganizing subclauses in clause 4 | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑191187 | |||
S5‑191188 | pCR 28.805 Update on SLA monitoring for network slicing | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑191468 | |||
S5‑191468 | pCR 28.805 Update on SLA monitoring for network slicing | Huawei, Ericsson, DT | pCR | Approval | Yes |
Yes
| approved | No | S5‑191188 | |||
S5‑191189 | pCR 28.805 Update on UC of realizing a communication service instance | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑191465 | |||
S5‑191465 | pCR 28.805 Update on UC of realizing a communication service instance | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑191189 | |||
S5‑191190 | pCR 28.805 Update on UC of removing a communication service instance | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑191466 | pCR 28.805 Update on UC of removing a communication service instance | Huawei | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑191191 | pCR 28.805 Solution for obtaining resource requirements for a given communication service requirement | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑191469 | |||
S5‑191469 | pCR 28.805 Solution for obtaining resource requirements for a given communication service requirement | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑191497 | S5‑191191 | ||
S5‑191497 | pCR 28.805 Solution for obtaining resource requirements for a given communication service requirement | Huawei | pCR | Approval | Yes |
Yes
| noted | No | S5‑191469 | |||
S5‑191192 | pCR 28.805 Management aspects of NSIs shared by multiple communication services | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑191467 | |||
S5‑191467 | pCR 28.805 Management aspects of NSIs shared by multiple communication services | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑191489 | S5‑191192 | ||
S5‑191489 | pCR 28.805 Management aspects of NSIs shared by multiple communication services | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑191467 | |||
S5‑191193 | pCR 28.805 Service management aspects of NSI-as-a-service | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑191470 | |||
S5‑191470 | pCR 28.805 Service management aspects of NSI-as-a-service | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑191490 | S5‑191193 | ||
S5‑191490 | pCR 28.805 Service management aspects of NSI-as-a-service | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑191470 | |||
S5‑191194 | pCR 28.805 Solution for communication service instances realized in a single network slice instance | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑191471 | |||
S5‑191471 | pCR 28.805 Solution for communication service instances realized in a single network slice instance | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑191491 | S5‑191194 | ||
S5‑191491 | pCR 28.805 Solution for communication service instances realized in a single network slice instance | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑191471 | |||
S5‑191195 | pCR 28.805 Add business roles and services related to verticals | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑191458 | |||
S5‑191458 | pCR 28.805 Add business roles and services related to verticals | Huawei | pCR | Approval | Yes |
Yes
| noted | No | S5‑191195 | |||
S5‑191272 | Discussion paper on lifecycle management of communication services | Ericsson Telecomunicazioni SpA | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑191459 | Discussion paper on lifecycle management of communication services | Ericsson Telecomunicazioni SpA | discussion | Endorsement | No |
Yes
| withdrawn | Yes | ||||
S5‑191273 | pCR 28.805 Resolution of Editors note on communication service instance | Ericsson Telecomunicazioni SpA | pCR | Approval | Yes |
Yes
| revised | No | S5‑191457 | |||
S5‑191457 | pCR 28.805 Resolution of Editors note on communication service instance | Ericsson Telecomunicazioni SpA | pCR | Approval | Yes |
Yes
| revised | No | S5‑191492 | S5‑191273 | ||
S5‑191492 | pCR 28.805 Resolution of Editors note on communication service instance | Ericsson Telecomunicazioni SpA,Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑191498 | S5‑191457 | ||
S5‑191498 | pCR 28.805 Resolution of Editors note on communication service instance | Ericsson Telecomunicazioni SpA,Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑191499 | S5‑191492 | ||
S5‑191499 | pCR 28.805 Resolution of Editors note on communication service instance | Ericsson Telecomunicazioni SpA,Huawei | pCR | Approval | No |
Yes
| left for email approval | No | S5‑191498 | |||
S5‑191274 | pCR 28.805 Clarify communication service concept | Ericsson Telecomunicazioni SpA | pCR | Approval | Yes |
Yes
| revised | No | S5‑191460 | |||
S5‑191460 | pCR 28.805 Clarify communication service concept | Ericsson Telecomunicazioni SpA | pCR | Approval | Yes |
Yes
| approved | No | S5‑191274 | |||
S5‑191275 | pCR 28.805 Use case and requirement to activate a resource communication service | Ericsson Telecomunicazioni SpA | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑191276 | pCR 28.805 Use case and requirement to create a resource communication service | Ericsson Telecomunicazioni SpA | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑191277 | pCR 28.805 Use case and requirement to de-activate a resource communication service | Ericsson Telecomunicazioni SpA | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑191278 | pCR 28.805 Use case and requirement to modify the capacity of a resource communication service | Ericsson Telecomunicazioni SpA | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑191301 | pCR 28.805 Use case and requirement for adjust network slice resources until network slice is stable | Ericsson Telecomunicazioni SpA | pCR | Approval | Yes |
Yes
| merged | No | S5‑191468 | |||
S5‑191304 | Sequence proposal for study on management aspects of communication services | Ericsson | other | Information | Yes |
Yes
| noted | No | ||||
S5‑191485 | Draft TR 28.805 | Ericsson | draft TR | Approval | No |
Yes
| left for email approval | No | ||||
6.5.7 | Study on Self-Organizing Networks (SON) for 5G | S5‑191034 | Minutes of Study on Self-Organizing Networks (SON) for 5G | Rapporteur (Intel) | report | Yes |
Yes
| noted | No | |||
S5‑191130 | Discussion on MDAS and SON | Huawei | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑191472 | Discussion on MDAS and SON | Huawei | discussion | Endorsement | No |
Yes
| withdrawn | Yes | ||||
S5‑191131 | pCR 28.861 Add concept, usecase and requirements for Automatic Radio Network Configuration Data Preparation | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑191473 | |||
S5‑191473 | pCR 28.861 Add concept, usecase and requirements for Automatic Radio Network Configuration Data Preparation | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑191131 | |||
S5‑191132 | pCR 28.861 Add concept, usecase and requirements for multi-vendor plug and play NFs | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑191474 | |||
S5‑191474 | pCR 28.861 Add concept, usecase and requirements for multi-vendor plug and play NFs | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑191132 | |||
S5‑191133 | pCR 28.861 Add NSI Coverage and Capacity Optimization | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑191475 | |||
S5‑191475 | pCR 28.861 Add NSI Coverage and Capacity Optimization | Huawei | pCR | Approval | Yes |
Yes
| noted | No | S5‑191133 | |||
S5‑191171 | pCR to 28.861 E2E Service Quality Optimization | Cisco Systems Inc. | pCR | Yes |
Yes
| noted | No | |||||
S5‑191476 | pCR to 28.861 E2E Service Quality Optimization | Cisco Systems Inc. | pCR | - | No |
Yes
| withdrawn | Yes | ||||
S5‑191172 | pCR 28.861 SON in case of disaggregated RAN | Cisco Systems Inc. | pCR | Yes |
Yes
| noted | No | |||||
S5‑191477 | pCR 28.861 SON in case of disaggregated RAN | Cisco Systems Inc. | pCR | - | No |
Yes
| withdrawn | Yes | ||||
S5‑191173 | pCR to the TR 28.861 Categories of SON Actions | Cisco Systems Inc. | pCR | Yes |
Yes
| noted | No | |||||
S5‑191478 | pCR to the TR 28.861 Categories of SON Actions | Cisco Systems Inc. | pCR | - | No |
Yes
| withdrawn | Yes | ||||
S5‑191175 | pCR 28.861 restructure and corrections | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑191483 | |||
S5‑191483 | pCR 28.861 restructure and corrections | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| approved | No | S5‑191175 | |||
S5‑191176 | pCR 28.861 add use case for RACH optimization | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑191479 | |||
S5‑191479 | pCR 28.861 add use case for RACH optimization | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| approved | No | S5‑191176 | |||
S5‑191177 | pCR 28.861 revise use case for Automatic Neighbour Relation (ANR) optimization | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑191178 | pCR 28.861 add use case for beam coverage and capacity optimization | Intel Corporation (UK) Ltd, ZTE, Pivotal Commware | pCR | Approval | Yes |
Yes
| revised | No | S5‑191480 | |||
S5‑191480 | pCR 28.861 add use case for beam coverage and capacity optimization | Intel Corporation (UK) Ltd, ZTE, Pivotal Commware | pCR | Approval | Yes |
Yes
| noted | No | S5‑191178 | |||
S5‑191243 | pCR R16 28.861-020 TR Introduction | Ericsson | pCR | Yes |
Yes
| approved | No | |||||
S5‑191244 | pCR R16 28.861-020 Correction of Scope | Ericsson | pCR | Yes |
Yes
| approved | No | |||||
S5‑191246 | pCR R16 28.861-020 Corrections of references | Ericsson | pCR | Yes |
Yes
| approved | No | |||||
S5‑191247 | pCR R16 28.861-020 Introduction of used abbreviations | Ericsson | pCR | Yes |
Yes
| approved | No | |||||
S5‑191249 | pCR R16 28.861-020 Correcting requirements | Ericsson | pCR | Yes |
Yes
| approved | No | |||||
S5‑191250 | pCR R16 28.861-020 Correction of clause heading | Ericsson | pCR | Yes |
Yes
| approved | No | |||||
S5‑191251 | pCR R16 28.861-020 ANR | Ericsson | pCR | Yes |
Yes
| approved | No | |||||
S5‑191252 | pCR R16 28.861-020 PCI | Ericsson | pCR | Yes |
Yes
| approved | No | |||||
S5‑191253 | pCR R16 28.861-020 LB | Ericsson | pCR | Yes |
Yes
| approved | No | |||||
S5‑191254 | pCR R16 28.861-020 MRO | Ericsson | pCR | Yes |
Yes
| approved | No | |||||
S5‑191255 | pCR R16 28.861-020 RACH | Ericsson | pCR | Yes |
Yes
| approved | No | |||||
S5‑191256 | pCR R16 28.861-020 Energy saving | Ericsson | pCR | Yes |
Yes
| approved | No | |||||
S5‑191257 | pCR R16 28.861-020 D-CCO | Ericsson | pCR | Yes |
Yes
| approved | No | |||||
S5‑191258 | pCR R16 28.861-020 Trace and MDT | Ericsson | pCR | Yes |
Yes
| approved | No | |||||
S5‑191482 | Draft TR 28.861 | Ericsson | draft TR | Approval | No |
Yes
| left for email approval | No | ||||
6.5.8 | Study on non-file-based trace reporting | S5‑191035 | Minutes of Study on non-file-based trace reporting | Rapporteur(Nokia) | report | No |
Yes
| withdrawn | Yes | |||
7 | Charging |   | ||||||||||
7.1 | Charging Plenary | S5‑191036 | CH Agenda and Time Plan | CH SWG Chair | agenda | Yes |
Yes
| approved | No | |||
S5‑191037 | CH Executive Report | CH SWG Chair | report | Yes |
Yes
| revised | No | S5‑191502 | ||||
S5‑191502 | CH Executive Report | CH SWG Chair | report | - | Yes |
Yes
| noted | No | S5‑191037 | |||
S5‑191281 | LS reply from CT3 to SA5 on PRA extension for offline charging | C3-187490 | LS in | Yes |
Yes
| noted | No | |||||
7.2 | New Charging Work Item proposals |   | ||||||||||
7.3 | Charging Maintenance and Rel-16 small Enhancements | S5‑191041 | Rel-15 CR 32.291 Correction of create operation description for event | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑191328 | |
S5‑191328 | Rel-15 CR 32.291 Correction of create operation description for event | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑191041 | |||
S5‑191042 | Rel-15 CR 32.291 Correction of data type associated to volume | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑191411 | |||
S5‑191411 | Rel-15 CR 32.291 Correction of data type associated to volume | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑191042 | |||
S5‑191043 | Rel-15 CR 32.291 Correction on reference for common data types | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑191329 | |||
S5‑191329 | Rel-15 CR 32.291 Correction on reference for common data types | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑191043 | |||
S5‑191044 | Rel-15 CR 32.291 Correction of inconsistencies in data types | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑191330 | |||
S5‑191330 | Rel-15 CR 32.291 Correction of inconsistencies in data types | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑191044 | |||
S5‑191045 | Rel-15 CR 32.298 Correction of NSSAI | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑191332 | |||
S5‑191332 | Rel-15 CR 32.298 Correction of NSSAI | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑191045 | |||
S5‑191046 | Rel-15 CR 32.298 Correction of subscriber equipment number | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑191047 | Rel-15 CR 32.255 Correction of category for subscriber identifier | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑191048 | Rel-15 CR 32.260 Correction of GGSN field for SMF address | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑191335 | |||
S5‑191335 | Rel-15 CR 32.260 Correction of GGSN field for SMF address | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑191048 | |||
S5‑191049 | Rel-15 CR 32.299 Correction of GGSN field for SMF address | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑191050 | Rel-15 CR 32.290 Correction of NF Consumer Information | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑191336 | |||
S5‑191336 | Rel-15 CR 32.290 Correction of NF Consumer Information | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑191050 | |||
S5‑191051 | Rel-15 CR 32.291 Correction of NF Consumer Information | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑191398 | |||
S5‑191398 | Rel-15 CR 32.291 Correction of NF Consumer Information | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑191051 | |||
S5‑191052 | Rel-15 CR 32.255 Correction of NF Consumer Information | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑191399 | |||
S5‑191399 | Rel-15 CR 32.255 Correction of NF Consumer Information | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑191052 | |||
S5‑191053 | Rel-15 CR 32.298 Correction of NF Consumer Information | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑191054 | Rel-15 CR 32.274 Correction of NF Consumer Information | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑191055 | Rel-15 CR 32.274 Correction of category Invocation result | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑191056 | Rel-15 CR 32.298 Correction of SMSF as NF Consumer | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑191057 | Rel-15 CR 32.291 Correction of SMSF as NF Consumer | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑191058 | Rel-15 CR 32.299 Correction of missing Presence-Reporting-Area-Node AVP | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑191059 | Rel-15 CR 32.298 Correction of PresenceReportingAreaNode ASN1 syntax | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑191400 | |||
S5‑191400 | Rel-15 CR 32.298 Correction of PresenceReportingAreaNode ASN1 syntax | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑191059 | |||
S5‑191094 | Rel-15 CR 32.291 Correction of ValidityTime data type | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑191156 | Rel-15 CR 32.291 Correction of API versioning and externalDocs field | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑191402 | |||
S5‑191402 | Rel-15 CR 32.291 Correction of API versioning and externalDocs field | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑191156 | |||
S5‑191157 | Rel-15 CR 32.291 Correction of Qos Information | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| postponed | No | ||||
S5‑191158 | Rel-15 CR 32.298 Correction of Qos Information | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| postponed | No | ||||
S5‑191159 | Rel-12 CR 32.298 Correction for multiple recipients in SC-SMO CDR | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑191407 | |||
S5‑191407 | Rel-12 CR 32.298 Correction for multiple recipients in SC-SMO CDR | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑191159 | |||
S5‑191160 | Rel-13 CR 32.298 Correction for multiple recipients in SC-SMO CDR | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑191325 | |||
S5‑191325 | Rel-13 CR 32.298 Correction for multiple recipients in SC-SMO CDR | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑191160 | |||
S5‑191161 | Rel-14 CR 32.298 Correction for multiple recipients in SC-SMO CDR | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑191326 | |||
S5‑191326 | Rel-14 CR 32.298 Correction for multiple recipients in SC-SMO CDR | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑191161 | |||
S5‑191162 | Rel-15 CR 32.298 Correction for multiple recipients in SC-SMO CDR | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑191327 | |||
S5‑191327 | Rel-15 CR 32.298 Correction for multiple recipients in SC-SMO CDR | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑191162 | |||
S5‑191168 | Rel-15 CR 32.290 Correction of SMSF as NF Consumer | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑191228 | Correct usedUnitContainer to sequence of | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑191403 | |||
S5‑191403 | Correct usedUnitContainer to sequence of | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑191228 | |||
S5‑191229 | Correct missing Session Identifier | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑191405 | |||
S5‑191405 | Correct missing Session Identifier | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑191229 | |||
S5‑191230 | Correct missing Session Identifier | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑191404 | |||
S5‑191404 | Correct missing Session Identifier | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑191230 | |||
S5‑191231 | Correct faults in yaml part | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑191331 | |||
S5‑191331 | Correct faults in yaml part | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑191231 | |||
S5‑191233 | Correct definition of Individual Partial record mechanism | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑191406 | |||
S5‑191406 | Correct definition of Individual Partial record mechanism | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑191233 | |||
S5‑191236 | Correct missing error handling | Ericsson | CR | Agreement | Yes |
Yes
| postponed | No | ||||
S5‑191238 | Correct missing error handling | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑191270 | Rel-15 CR 32.298 Corrections on ASN.1 syntax and charging modules version | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑191408 | |||
S5‑191408 | Rel-15 CR 32.298 Corrections on ASN.1 syntax and charging modules version | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑191270 | |||
S5‑191333 | Rel-15 CR 32.290 Correction of create operation for subscriber identifier | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
7.4 | Rel-16 Charging |   | ||||||||||
7.4.1 | Volume Based Charging Aspects for VoLTE |   | ||||||||||
7.4.2 | Nchf Online and Offline Charging Services | S5‑191076 | Discussion on 5G offline charging service | Huawei Telecommunication India | discussion | Discussion | Yes |
Yes
| noted | No | ||
S5‑191098 | Rel-16 CR 32.255 Offline charging service | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑191307 | |||
S5‑191307 | Rel-16 CR 32.255 Offline only charging service | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑191098 | |||
S5‑191099 | Rel-16 CR 32.290 Offline charging service | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑191308 | |||
S5‑191308 | Rel-16 CR 32.290 Offline only charging service | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑191099 | |||
S5‑191100 | Rel-16 CR 32.255 Offline charging service selection | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑191309 | |||
S5‑191309 | Rel-16 CR 32.255 Offline only charging service selection | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑191100 | |||
S5‑191101 | Rel-16 CR 32.255 Principles of offline charging | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑191102 | Rel-16 CR 32.255 offline charging service CDR generation | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑191310 | |||
S5‑191310 | Rel-16 CR 32.255 offline only charging service CDR generation | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑191102 | |||
S5‑191103 | Rel-16 CR 32.255 charging information for offline charging | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑191311 | |||
S5‑191311 | Rel-16 CR 32.255 charging information for offline only charging | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑191103 | |||
S5‑191104 | Rel-16 CR 32.290 Offline charging service Definition | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑191312 | |||
S5‑191312 | Rel-16 CR 32.290 Offline only charging service Definition | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑191104 | |||
S5‑191105 | Rel-16 CR 32.255 offline charging scenario and FBC | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑191313 | |||
S5‑191313 | Rel-16 CR 32.255 offline only charging scenario and FBC | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑191105 | |||
S5‑191106 | Rel-16 CR 32.255 offline charging scenario and QBC | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑191409 | |||
S5‑191409 | Rel-16 CR 32.255 offline only charging scenario and QBC | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑191106 | |||
S5‑191107 | Rel-16 CR 32.255 offline charging service procedures | Huawei | CR | Agreement | Yes |
Yes
| withdrawn | Yes | ||||
S5‑191108 | Rel-16 CR 32.255 offline charging service triggers for SSC modes | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑191410 | |||
S5‑191410 | Rel-16 CR 32.255 offline charging service triggers for SSC modes | Huawei | CR | Agreement | Yes |
Yes
| postponed | No | S5‑191108 | |||
S5‑191334 | Discussion on 5G offline charging service | Huawei | discussion | discussion | Yes |
Yes
| noted | No | ||||
S5‑191337 | Rel-16 CR 32.255 offline charging service procedures | Huawei | CR | Agreement | Yes |
Yes
| postponed | No | ||||
7.4.3 | Charging Enhancement of 5GC interworking with EPC | S5‑191095 | Rel-16 CR 32.255 Clarification on the Charging Identifier | Huawei | CR | Agreement | Yes |
Yes
| postponed | No | ||
S5‑191096 | Rel-16 CR 32.255 Addition of the Triggers for Interworking | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑191316 | |||
S5‑191316 | Rel-16 CR 32.255 Addition of the Triggers for Interworking | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑191096 | |||
S5‑191097 | Rel-16 CR 32.255 Addition of the Message Flow for Interworking | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑191317 | |||
S5‑191317 | Rel-16 CR 32.255 Addition of the Message Flow for Interworking | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑191097 | |||
7.4.4 | Network Exposure Charging in 5G System Architecture | S5‑191239 | Add convergent charging architecture | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑191314 | |
S5‑191314 | Add convergent charging architecture | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑191239 | |||
S5‑191240 | Add basic principles for convergent charging | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑191315 | |||
S5‑191315 | Add basic principles for convergent charging | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑191240 | |||
7.4.5 | Charging AMF in 5G System Architecture Phase 1 | S5‑191060 | Draft TS 32.256 skeleton v0.0.0 | Nokia France | draft TS | Approval | Yes |
Yes
| noted | No | ||
7.5 | Charging Studies |   | ||||||||||
7.5.1 | Study on Charging Aspects of Network Slicing | S5‑191087 | Rel-16 pCR TR 32.845 Addition of Key Issues and Solution for Usage based Charging | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑191322 | |
S5‑191322 | Rel-16 pCR TR 32.845 Addition of Key Issues and Solution for Usage based Charging | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑191087 | |||
S5‑191088 | Rel-16 pCR TR 32.845 Addition of Key Issues and Solution for SLA based Charging | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑191323 | |||
S5‑191323 | Rel-16 pCR TR 32.845 Addition of Key Issues and Solution for SLA based Charging | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑191088 | |||
S5‑191089 | Rel-16 pCR TR 32.845 Addition of Use Case and Potential Charging Requirements | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑191321 | |||
S5‑191321 | Rel-16 pCR TR 32.845 Addition of Use Case and Potential Charging Requirements | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑191089 | |||
S5‑191090 | Rel-16 pCR TR 32.845 Addition of the References and Abbreviations | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑191401 | |||
S5‑191401 | Rel-16 pCR TR 32.845 Addition of the References and Abbreviations | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑191090 | |||
S5‑191091 | Rel-16 pCR TR 32.845 Introduce the Roles related Network Slicing | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑191319 | |||
S5‑191319 | Rel-16 pCR TR 32.845 Introduce the Roles related Network Slicing | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑191091 | |||
S5‑191092 | Rel-16 pCR TR 32.845 Introduce the Network Slicing Related Concept | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑191318 | |||
S5‑191318 | Rel-16 pCR TR 32.845 Introduce the Network Slicing Related Concept | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑191092 | |||
S5‑191093 | Rel-16 pCR TR 32.845 Addition of Charging Aspect Requirements | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑191320 | |||
S5‑191320 | Rel-16 pCR TR 32.845 Addition of Charging Aspect Requirements | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑191093 | |||
S5‑191324 | Draft TR 32.845 | Huawei | draft TR | Approval | No |
Yes
| left for email approval | No | ||||
8 | Any Other Business |   | ||||||||||
9 | Closing of the meeting |   |