Tdoc List
2019-04-26 16:49
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‑193000 | Agenda | WG Chairman | agenda | Yes |
Yes
| approved | No | |||
3 | IPR and legal declaration | S5‑193001 | IPR and legal declaration | WG Chairman | other | Yes |
Yes
| noted | No | |||
4 | Meetings and activities reports |   | ||||||||||
4.1 | Last SA5 meeting report | S5‑193002 | Report from last SA5 meeting | MCC | report | Yes |
YesIt was argued that the action item "Create a stage 3 CR dependent on this CR" was not relevant for this CR, so it was closed.
On the topic of stage 2 and stage 3 CRs the Chair proposed to work on stage 2CRs in the form of draftCRs in order to align them with the stage 3 CRs before they were created.
The action points were moved to the OAM action list.
| approved | No | |||
4.2 | Last SA meeting report | S5‑193015 | SA5 status report at last SA meeting | WG Chairman | report | Yes |
Yes
| noted | No | |||
S5‑193016 | SA5 results at last SA meeting | WG Chairman | report | Yes |
YesThe Chair reminded the delegates that WIDs containing both a normative and a study part should be avoided.
It was discussed the use of ETSI FORGE at OMA level and delegates were encouraged to get familiar with the process agreed in SA/CT on the use of OPENAPIs.
MCC reminded the delegates about two CRs approved for TR 21.801 and TR 21.900:
- Use of the term "sub-clause" is deprecated, so just the term "clause" should be used.
- Clarifications for the use of the WID code "TEIx" in CRs. This should not be used for cat-B/C CRs, better create a new Work Item.
Release 16 deadline is December 2019, although there are discussions to extend it to March 2020. In case of dependency of RAN groups, exceptions can be requested. Maryse (Nokia) commented that moving to March 2020 would be very welcome from the Charging SWG perspective.
| noted | No | |||||
S5‑193346 | SA presentation on the process for OPEN APIs | WG Chair | other | Presentation | Yes |
Yes
| noted | No | ||||
4.3 | Inter-organizational reports | S5‑193309 | General SA5 presentation to Layer123/ZTA congress | Ericsson LM | other | Information | Yes |
Yes
| noted | No | ||
S5‑193310 | General SA5 presentation to ONAP M-SDO workshop | Ericsson LM | other | Information | Yes |
Yes
| noted | No | ||||
S5‑193347 | SA5 presentation for ONAP | Nokia | other | Information | Yes |
Yes
| noted | No | ||||
5 | Cross-SWG issues |   | ||||||||||
5.1 | Administrative issues at SA5 level | S5‑193003 | Leaders meeting agenda | WG Chairman | agenda | Yes |
Yes
| noted | No | |||
S5‑193004 | Leaders meeting minutes | WG Chairman | report | Yes |
Yes
| noted | No | |||||
S5‑193005 | SA5 Working Procedures | WG Vice Chair (Huawei) | other | Yes |
Yes
| noted | No | |||||
S5‑193006 | SA5 Meeting Facility Requirements | WG Vice Chair (Orange) | other | Yes |
Yes
| noted | No | |||||
S5‑193007 | Process for management of draft TSs/TRs | WG Chairman | other | Yes |
Yes
| noted | No | |||||
S5‑193008 | CR Quality Check | MCC | other | Yes |
Yes
| noted | No | |||||
S5‑193009 | Status of email approvals | WG Vice Chair (Orange) | other | No |
No
| reserved | No | |||||
S5‑193547 | Draft OAM agenda for Sapporo | WG Chair | other | Information | Yes |
Yes
| endorsed | No | S5‑193531 | |||
5.2 | Technical issues at SA5 level |   | ||||||||||
5.3 | Liaison statements at SA5 level | S5‑193245 | LS from CT to SA5 on Handling of non-essential corrections (non-FASMO) CRs and non-backwards compatible CRs | CP-190218 | LS in | Yes |
YesEricsson pointed out that it may be difficult to judge at CT/SA level whether an agreed SA5 CR was FASMO or non-FASMO.
MCC pointed out that tdoc S5-193040 was a cat-B CR for Rel-15 and it could be rejected at SA if there were implications for CT.
| noted | No | |||
S5‑193257 | LS from TSG SA ccSA5 on Information on MEC work on 5G | SP-190251 | LS in | Yes |
Yes
| noted | No | |||||
S5‑193258 | LS from SA2 ccSA5 on Information on MEC work on 5G | S2-1902907 | LS in | Yes |
Yes
| noted | No | |||||
S5‑193308 | Response LS to GSMA ccSA5 on NEST_59_004 on ‘GST and Cooperation with industry partners | BBF | LS in | Yes |
YesNokia: there's an issue here. If NFV works on the GSMA GST skipping slice profiles, the whole 3GPP NRM is bypassed. BBF does not support 5G slices. Their job is to support connectivity.We should have been copied in the original LS from GSMA and it seems to imply that 3GPP has been ignored here.
| replied to | No | |||||
S5‑193350 | Reply to: Response LS to GSMA ccSA5 on NEST_59_004 on ‘GST and Cooperation with industry partners | Huawei | LS out | approval | Yes |
Yes
| approved | No | ||||
5.4 | SA5 meeting calendar | S5‑193010 | SA5 Meeting Calendar | WG Chairman | other | Yes |
Yes
| noted | No | |||
5.5 | Review of the Work Plan | S5‑193011 | 3GPP SA5 Work Plan | MCC | other | Yes |
Yes
| noted | No | |||
6 | OAM&P |   | ||||||||||
6.1 | OAM&P Plenary | S5‑193012 | Time Plan for OAM&P | WG Vice Chair (Huawei) | other | Yes |
Yes
| noted | No | |||
S5‑193013 | OAM Executive Report | WG Vice Chair (ORANGE) | report | Yes |
Yes
| revised | No | S5‑193551 | ||||
S5‑193551 | OAM Executive Report | WG Vice Chair (ORANGE) | report | - | Yes |
Yes
| noted | No | S5‑193013 | |||
S5‑193014 | OAM&P SWG action list | WG Vice Chair (Huawei) | other | Yes |
Yes
| revised | No | S5‑193510 | ||||
S5‑193510 | OAM&P SWG action list | WG Vice Chair (Huawei) | other | - | Yes |
Yes
| revised | No | S5‑193550 | S5‑193014 | ||
S5‑193550 | OAM&P SWG action list | WG Vice Chair (Huawei) | other | - | Yes |
Yes
| noted | No | S5‑193510 | |||
S5‑193017 | Minutes of OAM&P SWG opening session | WG Vice Chair (Huawei) | report | Yes |
Yes
| noted | No | |||||
S5‑193246 | LS from RAN1 to SA5 on completion of CLI-RIM in RAN1 | R1-1903676 | LS in | Yes |
Yes
| postponed | No | |||||
S5‑193247 | Ls from RAN2 cc SA5 on L1 and L2 measurements | R2-1902806 | LS in | Yes |
Yes
| noted | No | |||||
S5‑193248 | LS from RAN2 to SA5 on network slicing terminology | R2-1902823 | LS in | Yes |
Yes
| noted | No | |||||
S5‑193250 | Reply LS from RAN3 ccSA5 on providing information on SLA fulfilment to NG-RAN | R3-191091 | LS in | Yes |
Yes
| noted | No | |||||
S5‑193251 | Resubmitted LS from ITU-TSG12 to SA5 on Draft new Recommendation E.RQST – “KPI targets for mobile networks” | ITU-T SG12 | LS in | Yes |
Yes
| noted | No | |||||
S5‑193252 | LS from TSG RAN ccSA5 on Draft new Recommendation E.RQST – “KPI targets for mobile networks” | RP-190673 | LS in | Yes |
Yes
| noted | No | |||||
S5‑193253 | LS from TSG SA ccSA5 in reply to LS on Draft new Recommendation E.RQST – “KPI targets for mobile networks”LS in reply to LS on Draft new Recommendation E.RQST – “KPI targets for mobile networks” | SP-190269 | LS in | Yes |
Yes
| noted | No | |||||
S5‑193254 | LS from SA2 to SA5 on the slicing terminology and the role of S-NSSAI parameter | S2-1902847 | LS in | Yes |
Yes
| postponed | No | |||||
S5‑193351 | Reply to: LS from SA2 to SA5 on the slicing terminology and the role of S-NSSAI parameter | Ericsson | LS out | approval | No |
Yes
| withdrawn | Yes | ||||
S5‑193259 | LS from ITU-T SG2 to SA5 on cooperation on methodology harmonization and REST-based network management framework | ITU-T SG2 | LS in | Yes |
Yes
| postponed | No | |||||
S5‑193260 | LS from ITU-T to SA5 on new Recommendation Q.5020 (formerly Q.NS-LCMP): Protocol requirements and procedures for network slice lifecycle management | ITU-T SG11 | LS in | Yes |
Yes
| noted | No | |||||
S5‑193349 | Discussion paper on levels of autonomous network | China Mobile, China Telecom, China Unicom, Huawei, Turkcell, Vodafone, ZTE | discussion | discussion | Yes |
Yes
| noted | No | ||||
S5‑193460 | Title Stage 2-3 alignment process | WG chair | discussion | Endorsement | No |
Yes
| withdrawn | Yes | ||||
S5‑193531 | Draft OAM agenda for Sapporo | WG Chair | other | Information | Yes |
Yes
| revised | No | S5‑193547 | |||
6.2 | New OAM&P Work Item proposals | S5‑193018 | Minutes of New Work Item proposals - OAM&P | WG Vice Chair (Orange) | report | No |
Yes
| withdrawn | Yes | |||
6.3 | OAM&P Maintenance and Rel-16 small Enhancements | S5‑193019 | Minutes of OAM&P Maintenance and Rel-16 small Enhancements | MCC | report | Yes |
Yes
| noted | No | |||
S5‑193040 | Rel-15 CR TS 28.541 Add NRM Info Model definitions for beam managed object class | Pivotal Commware, ZTE, Intel, P.I. Works, China Mobile, Verizon, BT | CR | Agreement | Yes |
Yes
| revised | No | S5‑193401 | S5‑192312 | ||
S5‑193401 | Rel-15 CR TS 28.541 Add NRM Info Model definitions for beam managed object class | Pivotal Commware, ZTE, Intel, P.I. Works, China Mobile, Verizon, BT | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑193040 | |||
S5‑193056 | Discussion paper on the need to restructure TS 28.532 | AT&T, Orange | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑193352 | |||
S5‑193352 | Discussion paper on the need to restructure TS 28.532 | AT&T, Orange | discussion | Endorsement | Yes |
Yes
| endorsed | No | S5‑193056 | |||
S5‑193057 | Introducing GST and NEST | Orange Romania | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑193353 | Introducing GST and NEST | Orange Romania | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑193089 | Corrections of the document references information | Ericsson Inc. | CR | Approval | Yes |
Yes
| revised | No | S5‑193364 | |||
S5‑193364 | Corrections of the document references information | Ericsson Inc. | CR | Approval | Yes |
Yes
| agreed | No | S5‑193089 | |||
S5‑193101 | Add missing annex with information on probable causes | Ericsson Inc. | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑193102 | Corrections of the document references information | Ericsson Inc. | CR | Approval | Yes |
Yes
| revised | No | S5‑193362 | |||
S5‑193362 | Corrections of the document references information | Ericsson Inc. | CR | Approval | Yes |
Yes
| agreed | No | S5‑193102 | |||
S5‑193103 | Corrections of the document references information | Ericsson Inc. | CR | Approval | Yes |
Yes
| revised | No | S5‑193361 | |||
S5‑193361 | Corrections of the document references information | Ericsson Inc. | CR | Approval | Yes |
Yes
| agreed | No | S5‑193103 | |||
S5‑193104 | Corrections of the document references information | Ericsson Inc. | CR | Approval | Yes |
Yes
| revised | No | S5‑193360 | |||
S5‑193360 | Corrections of the document references information | Ericsson Inc. | CR | Approval | Yes |
Yes
| agreed | No | S5‑193104 | |||
S5‑193105 | Corrections of the document references information | Ericsson Inc. | CR | Approval | Yes |
Yes
| revised | No | S5‑193359 | |||
S5‑193359 | Corrections of the document references information | Ericsson Inc. | CR | Approval | Yes |
Yes
| agreed | No | S5‑193105 | |||
S5‑193106 | Corrections of the document references information | Ericsson Inc. | CR | Approval | Yes |
Yes
| revised | No | S5‑193358 | |||
S5‑193358 | Corrections of the document references information | Ericsson Inc. | CR | Approval | Yes |
Yes
| agreed | No | S5‑193106 | |||
S5‑193107 | Corrections of the document references information | Ericsson Inc. | CR | Approval | Yes |
Yes
| revised | No | S5‑193357 | |||
S5‑193357 | Corrections of the document references information | Ericsson Inc. | CR | Approval | Yes |
Yes
| agreed | No | S5‑193107 | |||
S5‑193108 | Corrections of the document references information | Ericsson Inc. | CR | Approval | Yes |
Yes
| revised | No | S5‑193356 | |||
S5‑193356 | Corrections of the document references information | Ericsson Inc. | CR | Approval | Yes |
Yes
| agreed | No | S5‑193108 | |||
S5‑193129 | Rel-16 CR 32.425 Add measurement on RRC connection usage per UE multi-RAT capability | P.I. WORKS | CR | Agreement | Yes |
Yes
| revised | No | S5‑193363 | |||
S5‑193363 | Rel-16 CR 32.425 Add measurement on RRC connection usage per UE multi-RAT capability | P.I. WORKS | CR | Agreement | Yes |
Yes
| agreed | No | S5‑193129 | |||
S5‑193137 | Rel-15 CR TS 28.541 Address the inconsistent issue for attribute rRMPolicyNSSI | Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑193451 | |||
S5‑193451 | Rel-15 CR TS 28.541 Address the inconsistent issue for attribute rRMPolicyNSSI | Huawei | CR | Approval | Yes |
YesTechnical content was agreed, postponed for stage 3 CR.
| conditionally agreed | No | S5‑193137 | |||
S5‑193138 | Rel-16 CR TS 28.541 Address the inconsistent issue for attribute rRMPolicyNSSI | Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑193452 | |||
S5‑193452 | Rel-16 CR TS 28.541 Address the inconsistent issue for attribute rRMPolicyNSSI | Huawei | CR | Approval | Yes |
YesContent was agreed but it will be resubmitted for the next meeting in order to prepare the stage 3 CR.
| conditionally agreed | No | S5‑193138 | |||
S5‑193139 | Rel-15 CR TS 28.541 Remove attribute availabilityStatus in NRCellDU IOC | Huawei,Ericsson | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑193140 | Rel-16 CR TS 28.541 Remove attribute availabilityStatus in NRCellDU IOC | Huawei,Ericsson | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑193141 | Rel-15 CR TS 28.541 Correct the definition for nsInfo | Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑193413 | |||
S5‑193413 | Rel-15 CR TS 28.541 Correct the definition for nsInfo | Huawei | CR | Approval | Yes |
Yes
| agreed | No | S5‑193141 | |||
S5‑193142 | Rel-16 CR TS 28.541 Correct the definition for nsInfo | Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑193414 | |||
S5‑193414 | Rel-16 CR TS 28.541 Correct the definition for nsInfo | Huawei | CR | Approval | Yes |
Yes
| agreed | No | S5‑193142 | |||
S5‑193143 | Rel-16 CR 28.531 Editor's change for configuration management service | Huawei Tech.(UK) Co., Ltd | CR | Approval | Yes |
Yes
| revised | No | S5‑193416 | |||
S5‑193416 | Rel-16 CR 28.531 Editor's change for configuration management service | Huawei Tech.(UK) Co., Ltd | CR | Approval | Yes |
Yes
| agreed | No | S5‑193143 | |||
S5‑193144 | Rel-15 CR TS 32.425 Correction on kbits abbreviation | Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑193417 | |||
S5‑193417 | Rel-15 CR TS 32.425 Correction on kbits abbreviation | Huawei | CR | Approval | Yes |
Yes
| agreed | No | S5‑193144 | |||
S5‑193145 | Rel-16 CR TS 32.425 Correction on kbits abbreviation | Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑193418 | |||
S5‑193418 | Rel-16 CR TS 32.425 Correction on kbits abbreviation | Huawei | CR | Approval | Yes |
Yes
| agreed | No | S5‑193145 | |||
S5‑193151 | Mapping rule between DN and URI | Ericsson Inc. | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑193419 | |||
S5‑193419 | Mapping rule between DN and URI | Ericsson Inc. | discussion | Endorsement | Yes |
Yes
| noted | No | S5‑193151 | |||
S5‑193184 | Add missing (NR) cell and frequency relation | Ericsson Inc. | CR | Approval | Yes |
Yes
| revised | No | S5‑193529 | |||
S5‑193529 | Add missing (NR) cell and frequency relation | Ericsson Inc.,Huawei | CR | Approval | Yes |
Yes
| conditionally agreed | No | S5‑193184 | |||
S5‑193185 | Update Information Service of NR to fix unclear Note issue | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑193409 | |||
S5‑193409 | Update Information Service of NR to fix unclear Note issue | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑193185 | |||
S5‑193197 | Add missing (E-UTRAN) cell and freq relation | Ericsson Inc. | CR | Approval | Yes |
Yes
| revised | No | S5‑193420 | |||
S5‑193420 | Add missing (E-UTRAN) cell and freq relation | Ericsson Inc.,Huawei | CR | Approval | Yes |
Yes
| conditionally agreed | No | S5‑193197 | |||
S5‑193198 | Correct pLMNIdList parameter | Ericsson Inc. | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑193421 | Correct pLMNIdList parameter | Ericsson Inc. | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑193201 | CR 32.158 Correct the DN to URI mapping rules | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑193479 | |||
S5‑193479 | CR 32.158 Correct the DN to URI mapping rules | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑193201 | |||
S5‑193210 | Discussion paper around beam types | Ericsson-LG Co., LTD | discussion | Approval | Yes |
Yes
| revised | No | S5‑193422 | |||
S5‑193422 | Discussion paper around beam types | Ericsson-LG Co., LTD | discussion | Approval | Yes |
Yes
| endorsed | No | S5‑193210 | |||
S5‑193239 | Correct UML diagram and role-attribute of slice NRM | Ericsson Inc. Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑193438 | |||
S5‑193438 | Correct UML diagram and role-attribute of slice NRM | Ericsson Inc. Huawei | CR | Approval | Yes |
Yes
| conditionally agreed | No | S5‑193239 | |||
S5‑193240 | Correct definition of configuredMaxTxPower | Ericsson Inc. | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑193241 | Correct style for Definition | Ericsson Inc. | CR | Approval | Yes |
Yes
| revised | No | S5‑193439 | |||
S5‑193439 | Correct style for Definition | Ericsson Inc. | CR | Approval | Yes |
Yes
| agreed | No | S5‑193241 | |||
S5‑193242 | Add RP attribute and disambiguate the delivery method attributes | Ericsson Inc. | CR | Approval | Yes |
Yes
| revised | No | S5‑193440 | |||
S5‑193440 | Add RP attribute and disambiguate the delivery method attributes | Ericsson Inc. | CR | Approval | Yes |
Yes
| conditionally agreed | No | S5‑193242 | |||
S5‑193243 | Correct use of Proxy class | Ericsson Inc. | CR | Approval | Yes |
Yes
| revised | No | S5‑193447 | |||
S5‑193447 | Correct use of Proxy class | Ericsson Inc. | CR | Approval | Yes |
Yes
| conditionally agreed | No | S5‑193243 | |||
S5‑193244 | correct the use of plmnIdList | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑193405 | |||
S5‑193405 | correct the use of plmnIdList | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑193548 | S5‑193244 | ||
S5‑193548 | correct the use of plmnIdList | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑193405 | |||
S5‑193265 | Correction of Throughput KPI | Ericsson-LG Co., LTD | CR | Approval | Yes |
Yes
| revised | No | S5‑193448 | |||
S5‑193448 | Correction of Throughput KPI | Ericsson-LG Co., LTD | CR | Approval | Yes |
Yes
| agreed | No | S5‑193265 | |||
S5‑193266 | Correction of Throughput KPI | Ericsson-LG Co., LTD | CR | Approval | Yes |
Yes
| revised | No | S5‑193449 | |||
S5‑193449 | Correction of Throughput KPI | Ericsson-LG Co., LTD | CR | Approval | Yes |
Yes
| agreed | No | S5‑193266 | |||
S5‑193271 | Correction of F1 measurements | Ericsson-LG Co., LTD | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑193272 | Correction of F1 measurements | Ericsson-LG Co., LTD | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑193273 | Correction of RRMPolicy | Ericsson-LG Co., LTD | CR | Approval | Yes |
Yes
| merged | No | S5‑193409 | |||
S5‑193275 | Correction of RRMPolicy | Ericsson-LG Co., LTD | CR | Approval | Yes |
Yes
| merged | No | S5‑193410 | |||
S5‑193277 | CR R15 32421-F00 Update eNB/NG-RAN List of interfaces for NSA support of trace activation of trace activation | Ericsson, NTT DOCOMO | CR | Yes |
Yes
| agreed | No | |||||
S5‑193278 | CR R15 32.422-f10 Update eNB/NG-RAN List of interfaces for NSA support of trace activation | Ericsson, NTT DOCOMO | CR | Yes |
Yes
| revised | No | S5‑193546 | ||||
S5‑193546 | CR R15 32.422-f10 Update eNB/NG-RAN List of interfaces for NSA support of trace activation | Ericsson, NTT DOCOMO | CR | - | No |
Yes
| agreed | No | S5‑193278 | |||
S5‑193279 | CR R15 32423-f00 Update Trace Record Content to reflect the NR NRM in 28.541 for NSA support | Ericsson, NTT DOCOMO | CR | Yes |
Yes
| revised | No | S5‑193450 | ||||
S5‑193450 | CR R15 32423-f00 Update Trace Record Content to reflect the NR NRM in 28.541 for NSA support | Ericsson, NTT DOCOMO | CR | - | Yes |
Yes
| agreed | No | S5‑193279 | |||
S5‑193304 | Fix the implementation errors | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑193305 | Correct the use of plmnIdList | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑193404 | |||
S5‑193404 | Correct the use of plmnIdList | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑193549 | S5‑193305 | ||
S5‑193549 | Correct the use of plmnIdList | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑193404 | |||
S5‑193415 | Rel-15 CR 28.531 Editor's change for configuration management service | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑193442 | Correct style for Definition | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑193443 | Correct style for Definition | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑193444 | Correct style for Definition | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑193445 | Correct style for Definition | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑193446 | Correct style for Definition | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑193463 | Rel-13 CR TS 32.425 Correction on kbits abbreviation | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑193464 | Rel-14 CR TS 32.425 Correction on kbits abbreviation | Huawei | 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‑193020 | Minutes of Management of QoE measurement collection | Rapporteur (Ericsson) | report | Yes |
Yes
| noted | No | |||
S5‑193211 | pCR R16 28405-050 Change clause structure | Ericsson | pCR | Yes |
Yes
| approved | No | |||||
S5‑193212 | pCR R16 28405-050 Introduce missing abbreviations | Ericsson | pCR | Yes |
Yes
| approved | No | |||||
S5‑193213 | Introduction of deactivation of QMC in LTE | Ericsson | pCR | Yes |
Yes
| approved | No | |||||
S5‑193215 | Introduction of management based activated QMC handling at handover for LTE | Ericsson | pCR | Yes |
Yes
| approved | No | |||||
S5‑193216 | Introduction of Management based activation QMC for LTE | Ericsson | pCR | Yes |
Yes
| approved | No | |||||
S5‑193365 | Draft TS 28.405 | Ericsson | draft TS | Approval | Yes |
Yes
| approved | No | ||||
6.4.2 | Energy Efficiency of 5G | S5‑193021 | Minutes of Energy effciency of 5G | Rapporteur (ORANGE) | report | Yes |
Yes
| noted | No | |||
S5‑193164 | Discussion paper on PEE measurement data collection for NG-RAN | Huawei, Ericsson, Orange | discussion | Endorsement | Yes |
Yes
| endorsed | No | ||||
S5‑193165 | pCR 28.310 Add requirements of PEE measurement data collection for NG-RAN | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑193366 | |||
S5‑193366 | pCR 28.310 Add requirements of PEE measurement data collection for NG-RAN | Huawei,Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S5‑193165 | |||
S5‑193166 | pCR 28.310 Update EE concept | Huawei, Orange | pCR | Approval | Yes |
Yes
| revised | No | S5‑193367 | |||
S5‑193367 | pCR 28.310 Update EE concept | Huawei, Orange | pCR | Approval | Yes |
Yes
| approved | No | S5‑193166 | |||
S5‑193179 | Revised WID on energy efficiency of 5G | Orange Romania | WID revised | Approval | Yes |
Yes
| revised | No | S5‑193368 | |||
S5‑193368 | Revised WID on energy efficiency of 5G | Orange Romania | WID revised | Approval | Yes |
Yes
| agreed | No | S5‑193179 | |||
S5‑193528 | Draft TS 28.310 | ORANGE | draft TS | Approval | Yes |
Yes
| approved | No | ||||
6.4.3 | Network policy management for mobile networks based on NFV scenarios | S5‑193022 | Minutes of Network policy management for mobile networks based on NFV scenarios | Rapporteur (China Mobile) | report | No |
Yes
| withdrawn | Yes | |||
6.4.4 | Methodology for 5G management specifications | S5‑193023 | Minutes of Methodology for 5G management specifications | Rapporteur (Ericsson) | report | Yes |
Yes
| revised | No | S5‑193532 | ||
S5‑193532 | Minutes of Methodology for 5G management specifications | Rapporteur (Ericsson) | report | - | Yes |
Yes
| noted | No | S5‑193023 | |||
S5‑193147 | YANG solution additional considerations | Ericsson Inc. | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑193457 | YANG solution additional considerations | Ericsson Inc. | discussion | Endorsement | No |
Yes
| withdrawn | Yes | ||||
S5‑193148 | YANG solution Recommendation to Stage 2 Model Design | Ericsson Inc. | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑193149 | YANG solution style guide | Ericsson Inc. | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑193456 | YANG solution style guide | Ericsson Inc. | discussion | Endorsement | No |
Yes
| withdrawn | Yes | ||||
S5‑193150 | Use one style for all enumeration | Ericsson Inc. | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑193455 | |||
S5‑193455 | Use one style for all enumeration | Ericsson Inc. | discussion | Endorsement | Yes |
Yes
| endorsed | No | S5‑193150 | |||
S5‑193167 | pCR 32.160 Resolution of the editors note in W4.3.a.2 | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑193202 | pCR 32.160 JSON schema and YANG mapping rules | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑193203 | TD Various issues in JSON schema and YANG stage 3 defintions | Nokia, Nokia Shanghai Bell | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑193231 | pCR 32.160 Stage 2 to stage 3 mapping | Ericsson GmbH, Eurolab | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑193234 | Presentation of Specification to TSG TS 32.160 | Ericsson GmbH, Eurolab | TS or TR cover | Information | Yes |
Yes
| noted | No | ||||
S5‑193355 | Sequence proposal for Methodology for 5G management specifications | Ericsson | other | Information | Yes |
Yes
| revised | No | S5‑193441 | |||
S5‑193441 | Sequence proposal for Methodology for 5G management specifications | Ericsson | other | Information | Yes |
Yes
| noted | No | S5‑193355 | |||
S5‑193497 | Report on Breakout session on Yang style guide | Ericsson | report | Information | Yes |
Yes
| noted | No | ||||
6.4.5 | Intent driven management service for mobile networks | S5‑193024 | Minutes of Intent driven management service for mobile networks | Rapporteur (Huawei) | report | Yes |
Yes
| revised | No | S5‑193533 | ||
S5‑193533 | Minutes of Intent driven management service for mobile networks | Rapporteur (Huawei) | report | - | Yes |
Yes
| noted | No | S5‑193024 | |||
S5‑193130 | pCR 28.812 Update Clause 4.3 Automation mechanisms and intent driven management | Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑193131 | pCR 28.812 Add description of intent translation | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑193370 | |||
S5‑193370 | pCR 28.812 Add description of intent translation | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑193131 | |||
S5‑193132 | pCR 28.812 Add key information for intent expression of existing scenarios | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑193371 | pCR 28.812 Add key information for intent expression of existing scenarios | Huawei | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑193133 | pCR 28.812 Add introduction and standard consideration for IDMS | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑193372 | |||
S5‑193372 | pCR 28.812 Add introduction and standard consideration for IDMS | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑193133 | |||
S5‑193173 | pCR 28.812 Add description for level of automation in mobile network management | Huawei Tech.(UK) Co., Ltd | pCR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑193174 | Discussion paper on Scope and bounderies for Intent Based Management | Ericsson Inc. | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑193373 | |||
S5‑193373 | Discussion paper on Scope and bounderies for Intent Based Management | Ericsson Inc. | discussion | Endorsement | Yes |
Yes
| endorsed | No | S5‑193174 | |||
S5‑193175 | pCR 28.812 Clarification of the dimensions | Ericsson Inc. | pCR | Approval | Yes |
Yes
| revised | No | S5‑193374 | |||
S5‑193374 | pCR 28.812 Clarification of the dimensions | Ericsson Inc. | pCR | Approval | Yes |
Yes
| approved | No | S5‑193175 | |||
S5‑193180 | Update the feedback description | Huawei Tech.(UK) Co., Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑193375 | |||
S5‑193375 | Update the feedback description | Huawei Tech.(UK) Co., Ltd | pCR | Approval | Yes |
Yes
| approved | No | S5‑193180 | |||
S5‑193181 | pCR 28.812 Abstraction versus layering | Ericsson Inc. | pCR | Approval | Yes |
Yes
| revised | No | S5‑193376 | |||
S5‑193376 | pCR 28.812 Abstraction versus layering | Ericsson Inc. | pCR | Approval | Yes |
Yes
| approved | No | S5‑193181 | |||
S5‑193182 | pCR 28.812 Clarification of relation between intent and policy | Ericsson Inc. | pCR | Approval | Yes |
Yes
| revised | No | S5‑193377 | |||
S5‑193377 | pCR 28.812 Clarification of relation between intent and policy | Ericsson Inc. | pCR | Approval | Yes |
Yes
| approved | No | S5‑193182 | |||
S5‑193183 | pCR 28.812 Intent lifecycle management aspects | Ericsson Inc. | pCR | Approval | Yes |
Yes
| revised | No | S5‑193378 | |||
S5‑193378 | pCR 28.812 Intent lifecycle management aspects | Ericsson Inc. | pCR | Approval | Yes |
Yes
| revised | No | S5‑193534 | S5‑193183 | ||
S5‑193534 | pCR 28.812 Intent lifecycle management aspects | Ericsson Inc. | pCR | Approval | Yes |
Yes
| approved | No | S5‑193378 | |||
S5‑193199 | pCR TR28.812: Editorial clarifications on Intent expression | NEC Telecom MODUS Ltd. | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑193369 | Draft TR 28.812 | Huawei | draft TR | Approval | Yes |
Yes
| approved | No | ||||
6.4.6 | Enhancement of performance assurance for 5G networks including network slicing | S5‑193025 | Minutes of Enhancement of performance assurance for 5G networks including network slicing | Rapporteur (Intel) | report | Yes |
Yes
| revised | No | S5‑193535 | ||
S5‑193535 | Minutes of Enhancement of performance assurance for 5G networks including network slicing | Rapporteur (Intel) | report | - | Yes |
Yes
| noted | No | S5‑193025 | |||
S5‑193058 | Add use case and definitions of packet loss measurement over N3 | ETRI | CR | Approval | Yes |
Yes
| revised | No | S5‑193382 | |||
S5‑193382 | Add use case and definitions of packet loss measurement over N3 | ETRI,KT | CR | Approval | Yes |
Yes
| agreed | No | S5‑193058 | |||
S5‑193059 | Add use case and definitions of packet delay measurement over N3 | ETRI | CR | Approval | Yes |
Yes
| revised | No | S5‑193383 | |||
S5‑193383 | Add use case and definitions of packet delay measurement over N3 | ETRI,KT | CR | Approval | Yes |
Yes
| agreed | No | S5‑193059 | |||
S5‑193061 | Rel-16 CR TS 32.425 Add measurements related to Secondary Node Addition for E-UTRA-NR Dual Connectivity | ZTE Corporation, China Mobile | CR | Agreement | Yes |
Yes
| revised | No | S5‑193384 | |||
S5‑193384 | Rel-16 CR TS 32.425 Add measurements related to Secondary Node Addition for E-UTRA-NR Dual Connectivity | ZTE Corporation, China Mobile | CR | Agreement | Yes |
Yes
| agreed | No | S5‑193061 | |||
S5‑193062 | Rel-16 CR TS 32.425 Add measurements related to Secondary Node Change for E-UTRA-NR Dual Connectivity | ZTE Corporation, China Mobile | CR | Agreement | Yes |
Yes
| withdrawn | Yes | ||||
S5‑193063 | Rel-16 CR TS 32.425 Add measurements related to Secondary Node Modification for E-UTRA-NR Dual Connectivity | ZTE Corporation, China Mobile | CR | Agreement | Yes |
Yes
| withdrawn | Yes | ||||
S5‑193064 | Rel-16 CR TS 32.425 Add measurements related to Secondary Node Release for E-UTRA-NR Dual Connectivity | ZTE Corporation, China Mobile | CR | Agreement | Yes |
Yes
| withdrawn | Yes | ||||
S5‑193116 | Rel-16 CR 28.622 Add IOCs for threshold monitoring control | Intel Corporation SAS | CR | Approval | Yes |
Yes
| revised | No | S5‑193379 | |||
S5‑193379 | Rel-16 CR 28.622 Add IOCs for threshold monitoring control | Intel Corporation SAS | CR | Approval | Yes |
Yes
| revised | No | S5‑193516 | S5‑193116 | ||
S5‑193516 | Rel-16 CR 28.622 Add IOCs for threshold monitoring control | Intel Corporation SAS | CR | Approval | Yes |
Yes
| agreed | No | S5‑193379 | |||
S5‑193117 | Rel-16 CR 28.623 Add IOCs for threshold monitoring control | Intel Corporation SAS | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑193380 | Rel-16 CR 28.623 Add IOCs for threshold monitoring control | Intel Corporation SAS | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑193118 | Rel-16 CR 28.550 Add performance threshold monitoring service | Intel Corporation SAS | CR | Approval | Yes |
Yes
| revised | No | S5‑193381 | |||
S5‑193381 | Rel-16 CR 28.550 Add performance threshold monitoring service | Intel Corporation SAS | CR | Approval | Yes |
Yes
| agreed | No | S5‑193118 | |||
S5‑193119 | Discussion on Stage 3 of performance data streaming based on WebSocket | Intel Corporation SAS | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑193120 | Discussion on way forward for MDAS | Intel Corporation SAS | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑193121 | Rel-16 CR 28.552 Add measurements related to Service Requests via Untrusted non-3GPP Access | Intel Corporation SAS | CR | Approval | Yes |
Yes
| revised | No | S5‑193385 | |||
S5‑193385 | Rel-16 CR 28.552 Add measurements related to Service Requests via Untrusted non-3GPP Access | Intel Corporation SAS | CR | Approval | Yes |
Yes
| agreed | No | S5‑193121 | |||
S5‑193122 | Rel-16 CR 28.552 Add measurements related to PDU session resource management via Untrusted non-3GPP Access | Intel Corporation SAS | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑193194 | TD Broadcasting cell quality issue | Nokia, Nokia Shanghai Bell | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑193195 | Add measurement related to QoS of cell | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| withdrawn | Yes | ||||
S5‑193196 | Add measurement related to QoS of cell | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| withdrawn | Yes | ||||
S5‑193214 | Add measurements related to inter gNB Handover | Ericsson-LG Co., LTD | CR | Approval | Yes |
Yes
| revised | No | S5‑193386 | |||
S5‑193386 | Add measurements related to inter gNB Handover | Ericsson-LG Co., LTD | CR | Approval | Yes |
Yes
| agreed | No | S5‑193214 | |||
S5‑193217 | Add measurements related to intra gNB Handover | Ericsson-LG Co., LTD | CR | Approval | Yes |
Yes
| revised | No | S5‑193387 | |||
S5‑193387 | Add measurements related to intra gNB Handover | Ericsson-LG Co., LTD | CR | Approval | Yes |
Yes
| agreed | No | S5‑193217 | |||
S5‑193218 | Add KPI for NG-RAN Handover Success Rate | Ericsson-LG Co., LTD | CR | Approval | Yes |
Yes
| revised | No | S5‑193388 | |||
S5‑193388 | Add KPI for NG-RAN Handover Success Rate | Ericsson-LG Co., LTD | CR | Approval | Yes |
Yes
| agreed | No | S5‑193218 | |||
S5‑193267 | Add measurements related to DRB retainability | Ericsson-LG Co., LTD | CR | Approval | Yes |
Yes
| revised | No | S5‑193389 | |||
S5‑193389 | Add measurements related to DRB retainability | Ericsson-LG Co., LTD | CR | Approval | Yes |
Yes
| not pursued | No | S5‑193267 | |||
S5‑193268 | Add KPI for DRB Retainability | Ericsson-LG Co., LTD | CR | Approval | Yes |
Yes
| revised | No | S5‑193390 | |||
S5‑193390 | Add KPI for DRB Retainability | Ericsson-LG Co., LTD | CR | Approval | Yes |
Yes
| not pursued | No | S5‑193268 | |||
S5‑193269 | LS on Data activity reporting | Ericsson-LG Co., LTD | LS out | Approval | Yes |
Yes
| revised | No | S5‑193391 | |||
S5‑193391 | LS on Data activity reporting | Ericsson-LG Co., LTD | LS out | Approval | Yes |
Yes
| approved | No | S5‑193269 | |||
S5‑193270 | Correct DRB successfully setup measurements | Ericsson-LG Co., LTD | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑193274 | CR R15 Correction of monitoring of PDCP data volume measurements | Ericsson | CR | Yes |
Yes
| revised | No | S5‑193453 | ||||
S5‑193453 | CR R15 Correction of monitoring of PDCP data volume measurements | Ericsson | CR | - | Yes |
Yes
| agreed | No | S5‑193274 | |||
S5‑193276 | Correction of PRB measurements | Ericsson-LG Co., LTD | CR | Approval | Yes |
Yes
| revised | No | S5‑193454 | |||
S5‑193454 | Correction of PRB measurements | Ericsson-LG Co., LTD | CR | Approval | Yes |
Yes
| revised | No | S5‑193536 | S5‑193276 | ||
S5‑193536 | Correction of PRB measurements | Ericsson-LG Co., LTD | CR | Approval | Yes |
Yes
| agreed | No | S5‑193454 | |||
S5‑193300 | Rel-16 CR TS 32.425 Add measurements related to Secondary Node Change for E-UTRA-NR Dual Connectivity | ZTE Corporation, China Mobile | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑193301 | Rel-16 CR TS 32.425 Add measurements related to Secondary Node Modification for E-UTRA-NR Dual Connectivity | ZTE Corporation, China Mobile | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑193302 | Rel-16 CR TS 32.425 Add measurements related to Secondary Node Release for E-UTRA-NR Dual Connectivity | ZTE Corporation, China Mobile | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑193348 | Tdoc discussion sequence | Intel | other | Information | Yes |
Yes
| noted | No | ||||
S5‑193402 | Rel-16 CR 32.532 Add notifications for threshold monitoring | Intel | CR | Agreement | Yes |
Yes
| revised | No | S5‑193538 | |||
S5‑193538 | Rel-16 CR 32.532 Add notifications for threshold monitoring | Intel | CR | Agreement | Yes |
Yes
| agreed | No | S5‑193402 | |||
6.4.7 | Discovery of management services in 5G | S5‑193026 | Minutes of Discovery of management services in 5G | Rapporteur (Huawei) | report | Yes |
Yes
| revised | No | S5‑193539 | ||
S5‑193539 | Minutes of Discovery of management services in 5G | Rapporteur (Huawei) | report | - | Yes |
Yes
| noted | No | S5‑193026 | |||
S5‑193158 | CR Rel-16 TS 28.533 Add further clarification of metadata attributes | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑193393 | CR Rel-16 TS 28.533 Add further clarification of metadata attributes | Huawei | CR | Agreement | Yes |
Yes
| withdrawn | Yes | ||||
S5‑193159 | CR Rel-16 TS 28.533 Add two use cases of discovery of MnS instance | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑193392 | |||
S5‑193392 | CR Rel-16 TS 28.533 Add two use cases of discovery of MnS instance | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑193159 | |||
S5‑193540 | Draft CR Rel-16 TS 28.533 Add two use cases of discovery of MnS instance | Huawei | draftCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑193160 | Discussion paper about MnS instance metainformation | Huawei | discussion | Discussion | Yes |
Yes
| noted | No | ||||
S5‑193200 | MnS discovery | Nokia, Nokia Shanghai Bell | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑193395 | |||
S5‑193395 | MnS discovery | Nokia, Nokia Shanghai Bell | discussion | Endorsement | Yes |
Yes
| endorsed | No | S5‑193200 | |||
S5‑193261 | CR Rel-16 TS 28.533 Add use case of discovery of MnS instance metainformation | Huawei Technologies (Korea) | CR | Agreement | Yes |
Yes
| revised | No | S5‑193394 | |||
S5‑193394 | CR Rel-16 TS 28.533 Add use case of discovery of MnS instance metainformation | Huawei Technologies (Korea) | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑193261 | |||
6.4.8 | NRM enhancements | S5‑193027 | Minutes of NRM enhancements | Rapporteur (Nokia) | report | Yes |
Yes
| revised | No | S5‑193515 | ||
S5‑193515 | Minutes of NRM enhancements | Rapporteur (Nokia) | report | - | Yes |
Yes
| noted | No | S5‑193027 | |||
S5‑193186 | Update Information Service of NR to fix unclear Note issue | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑193410 | |||
S5‑193410 | Update Information Service of NR to fix unclear Note issue | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑193186 | |||
S5‑193187 | Update NRM requirement to support SBA management | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑193396 | |||
S5‑193396 | Update NRM requirement to support SBA management | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑193187 | |||
S5‑193188 | Update UIM Information Service to support Service_ Object | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑193397 | |||
S5‑193397 | Update UIM Information Service to support Service_ Object | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑193188 | |||
S5‑193517 | Update UIM Information Service to support Service_ Object | Nokia, Nokia Shanghai Bell | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
S5‑193189 | Update generic NRM Information Service to support Managed Service Object | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑193398 | |||
S5‑193398 | Update generic NRM Information Service to support Managed Service Object | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑193518 | S5‑193189 | ||
S5‑193518 | Update generic NRM Information Service to support Managed Service Object | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑193398 | |||
S5‑193190 | Update 5GC Information Service to align with Managed Service Definition | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑193399 | |||
S5‑193399 | Update 5GC Information Service to align with Managed Service Definition | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
YesTechnical content was agreed but will no be sent to SA until the stage 3 CR is agreed in the next meeting.
| conditionally agreed | No | S5‑193190 | |||
S5‑193191 | TD Resource sharing between multiple PLMNs | Nokia, Nokia Shanghai Bell | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑193400 | TD Resource sharing between multiple PLMNs | Nokia, Nokia Shanghai Bell | discussion | Endorsement | No |
Yes
| withdrawn | Yes | ||||
S5‑193192 | Enhance RRM Policy to support resource sharing between multiple PLMNs | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑193403 | Enhance RRM Policy to support resource sharing between multiple PLMNs | Nokia, Nokia Shanghai Bell | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
S5‑193262 | CR Rel-16 28.541 Add datatype definition for NfProfile | Ericsson GmbH, Eurolab | CR | Approval | Yes |
Yes
| revised | No | S5‑193406 | |||
S5‑193406 | CR Rel-16 28.541 Add datatype definition for NfProfile | Ericsson GmbH, Eurolab | CR | Approval | Yes |
Yes
| conditionally agreed | No | S5‑193262 | |||
S5‑193263 | CR Rel-16 28.541 Add missing clauses to RRMPolicyRatio2 data type | Ericsson GmbH, Eurolab | CR | Approval | Yes |
Yes
| revised | No | S5‑193407 | |||
S5‑193407 | CR Rel-16 28.541 Add missing clauses to RRMPolicyRatio2 data type | Ericsson GmbH, Eurolab | CR | Approval | Yes |
Yes
| agreed | No | S5‑193263 | |||
S5‑193264 | CR Rel-16 28.541 Update RRMPolicyRatio2 data type name in stage 3 | Ericsson GmbH, Eurolab | CR | Approval | Yes |
Yes
| revised | No | S5‑193408 | |||
S5‑193408 | CR Rel-16 28.541 Update RRMPolicyRatio2 data type name in stage 3 | Ericsson GmbH, Eurolab | CR | Approval | Yes |
Yes
| agreed | No | S5‑193264 | |||
S5‑193303 | Fix the implementation errors | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | ||||
6.4.9 | Trace Management in the context of Services Based Management Architecture | S5‑193028 | Minutes of Trace Management in the context of Services Based Management Architecture | Rapporteur (Nokia) | report | Yes |
Yes
| noted | No | |||
S5‑193193 | TD Trace Management in the context of Services Based Management Architecture | Nokia, Nokia Shanghai Bell | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑193411 | TD Trace Management in the context of Services Based Management Architecture | Nokia, Nokia Shanghai Bell | discussion | Endorsement | No |
Yes
| withdrawn | Yes | ||||
6.4.10 | Integration of ONAP and 3GPP 5G management framework | S5‑193029 | Minutes of Integration of ONAP and 3GPP 5G management framework | Rapporteur (AT&T) | report | Yes |
Yes
| noted | No | |||
S5‑193152 | Add RESTful HTTP-based solution set of fault supervision for integration with ONAP VES | AT&T, Deutsche Telekom, Orange | CR | Approval | Yes |
Yes
| revised | No | S5‑193462 | |||
S5‑193462 | Add RESTful HTTP-based solution set of fault supervision for integration with ONAP VES | AT&T, Deutsche Telekom, Orange | CR | Approval | Yes |
Yes
| revised | No | S5‑193519 | S5‑193152 | ||
S5‑193519 | Add RESTful HTTP-based solution set of fault supervision for integration with ONAP VES | AT&T, Deutsche Telekom, Orange | CR | Approval | Yes |
Yes
| agreed | No | S5‑193462 | |||
S5‑193153 | Rel-16 CR 28.622 Add NRM fragment supporting the management of notifications recipients | AT&T, Deutsche Telekom, Orange | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑193156 | Rel-16 CR 28.533 Add examples of ONAP utilizing the MnSs provided by 3GPP MnS Producer | Huawei Tech.(UK) Co., Ltd | CR | Approval | Yes |
Yes
| revised | No | S5‑193412 | |||
S5‑193412 | Rel-16 CR 28.533 Add examples of ONAP utilizing the MnSs provided by 3GPP MnS Producer | Huawei Tech.(UK) Co., Ltd | CR | Approval | Yes |
Yes
| agreed | No | S5‑193156 | |||
6.5 | OAM&P Studies |   | ||||||||||
6.5.1 | Study on protocol enhancement for real time communication | S5‑193030 | Minutes of Study on protocol enhancement for real time communication | Rapporteur(Nokia) | report | No |
Yes
| withdrawn | Yes | |||
6.5.2 | Study on management aspects of edge computing | S5‑193031 | Minutes of Study on management aspects of edge computing | Rapporteur (Intel) | report | Yes |
Yes
| revised | No | S5‑193537 | ||
S5‑193537 | Minutes of Study on management aspects of edge computing | Rapporteur (Intel) | report | - | Yes |
Yes
| noted | No | S5‑193031 | |||
S5‑193109 | pCR 28.803 add introduction | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑193458 | |||
S5‑193458 | pCR 28.803 add introduction | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| approved | No | S5‑193109 | |||
S5‑193110 | pCR 28.803 add a solution for end-to-end performance assurance | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑193459 | |||
S5‑193459 | pCR 28.803 add a solution for end-to-end performance assurance | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| approved | No | S5‑193110 | |||
S5‑193111 | pCR 28.803 add conclusion | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑193461 | |||
S5‑193461 | pCR 28.803 add conclusion | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| approved | No | S5‑193111 | |||
S5‑193306 | Presentation of TR 28.803 to SA for Information | Intel Corporation (UK) Ltd | TS or TR cover | Approval | Yes |
Yes
| approved | No | ||||
S5‑193541 | Draft TR 28.803 | Intel | draft TR | Approval | Yes |
Yes
| approved | No | ||||
6.5.3 | Study on tenancy concept in 5G networks and network slicing management | S5‑193032 | Minutes of Study on tenancy concept in 5G networks and network slicing management | Rapporteur (Huawei) | report | Yes |
Yes
| noted | No | |||
S5‑193161 | Representation for tenant in 3GPP management system | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑193475 | |||
S5‑193475 | Representation for tenant in 3GPP management system | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑193161 | |||
S5‑193162 | Management entity for tenant in 3GPP management system | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑193476 | |||
S5‑193476 | Management entity for tenant in 3GPP management system | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑193162 | |||
S5‑193163 | Add tenant definition in 3GPP management system | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑193478 | |||
S5‑193478 | Add tenant definition in 3GPP management system | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑193163 | |||
S5‑193172 | pCR 28.804 Add tenant type description | Huawei | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑193209 | pCR 28.804 Add tenant type description | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑193477 | |||
S5‑193477 | pCR 28.804 Add tenant type description | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑193209 | |||
S5‑193530 | Draft TR 28.804 | Nokia | draft TR | Approval | Yes |
Yes
| approved | No | ||||
6.5.4 | Study on management aspects of communication services | S5‑193033 | Minutes of Study on management aspects of communication services | Rapporteur (Ericsson) | report | Yes |
Yes
| noted | No | |||
S5‑193054 | pCR to TR 28.805 SLA assurance | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| revised | No | S5‑193480 | |||
S5‑193480 | pCR to TR 28.805 SLA assurance | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| revised | No | S5‑193542 | S5‑193054 | ||
S5‑193542 | pCR to TR 28.805 SLA assurance | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| noted | No | S5‑193480 | |||
S5‑193055 | pCR to TR 28.805 Types of communication services | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| revised | No | S5‑193481 | |||
S5‑193481 | pCR to TR 28.805 Types of communication services | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| approved | No | S5‑193055 | |||
S5‑193065 | pCR to TR 28.805 Service quality assurance and optimization | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| revised | No | S5‑193489 | |||
S5‑193489 | pCR to TR 28.805 Service quality assurance and optimization | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| approved | No | S5‑193065 | |||
S5‑193157 | 28.805 Add UC and requirements for CSI monitoring | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑193488 | |||
S5‑193488 | 28.805 Add UC and requirements for CSI monitoring | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑193157 | |||
S5‑193168 | pCR 28.805 CSMF functionalities | Huawei, Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S5‑193487 | |||
S5‑193487 | pCR 28.805 CSMF functionalities | Huawei, Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S5‑193168 | |||
S5‑193169 | pCR 28.805 Update use case of communication service instances realization | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑193490 | |||
S5‑193490 | pCR 28.805 Update use case of communication service instances realization | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑193169 | |||
S5‑193170 | pCR 28.805 Add CSI lifecyle concept | Huawei, Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S5‑193485 | |||
S5‑193485 | pCR 28.805 Add CSI lifecyle concept | Huawei, Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S5‑193170 | |||
S5‑193171 | pCR 28.805 Add CSI-NSI lifecycle relation concept | Huawei, Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S5‑193486 | |||
S5‑193486 | pCR 28.805 Add CSI-NSI lifecycle relation concept | Huawei, Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S5‑193171 | |||
S5‑193222 | pCR 28.805 Introduce connection to layering | Ericsson GmbH, Eurolab | pCR | Approval | Yes |
Yes
| revised | No | S5‑193482 | |||
S5‑193482 | pCR 28.805 Introduce connection to layering | Ericsson GmbH, Eurolab | pCR | Approval | Yes |
Yes
| approved | No | S5‑193222 | |||
S5‑193223 | pCR 28.805 Introduce management model | Ericsson GmbH, Eurolab | pCR | Approval | Yes |
Yes
| revised | No | S5‑193483 | |||
S5‑193483 | pCR 28.805 Introduce management model | Ericsson GmbH, Eurolab | pCR | Approval | Yes |
Yes
| approved | No | S5‑193223 | |||
S5‑193224 | pCR 28.805 Introduction communication service management exposure model | Ericsson GmbH, Eurolab | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑193225 | pCR 28.805 Use case and requirement for management of multi-site communication service | Ericsson GmbH, Eurolab,Deutsche Telekom | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑193491 | pCR 28.805 Use case and requirement for management of multi-site communication service | Ericsson GmbH, Eurolab | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑193226 | pCR 28.805 Use case and requirement to activate a resource facing communication service | Ericsson GmbH, Eurolab,Deutsche Telekom | pCR | Approval | Yes |
Yes
| revised | No | S5‑193492 | |||
S5‑193492 | pCR 28.805 Use case and requirement to activate a resource facing communication service | Ericsson GmbH, Eurolab | pCR | Approval | Yes |
Yes
| approved | No | S5‑193226 | |||
S5‑193227 | S5-193xxx pCR 28.805 Use case and requirement to create a resource facing communication service | Ericsson GmbH, Eurolab | pCR | Approval | Yes |
Yes
| revised | No | S5‑193493 | |||
S5‑193493 | pCR 28.805 Use case and requirement to create a resource facing communication service | Ericsson GmbH, Eurolab,Deutsche Telekom | pCR | Approval | Yes |
Yes
| approved | No | S5‑193227 | |||
S5‑193228 | pCR 28.805 Use case and requirement to de-activate a resource facing communication service | Ericsson GmbH, Eurolab | pCR | Approval | Yes |
Yes
| revised | No | S5‑193494 | |||
S5‑193494 | pCR 28.805 Use case and requirement to de-activate a resource facing communication service | Ericsson GmbH, Eurolab,Deutsche Telekom | pCR | Approval | Yes |
Yes
| approved | No | S5‑193228 | |||
S5‑193229 | pCR 28.805 Use case and requirement to modify a resource facing communication service | Ericsson GmbH, Eurolab | pCR | Approval | Yes |
Yes
| revised | No | S5‑193495 | |||
S5‑193495 | pCR 28.805 Use case and requirement to modify a resource facing communication service | Ericsson GmbH, Eurolab,Deutsche Telekom | pCR | Approval | Yes |
Yes
| approved | No | S5‑193229 | |||
S5‑193230 | pCR 28.805 Use case and requirement to terminate a resource facing communication service | Ericsson GmbH, Eurolab | pCR | Approval | Yes |
Yes
| revised | No | S5‑193496 | |||
S5‑193496 | pCR 28.805 Use case and requirement to terminate a resource facing communication service | Ericsson GmbH, Eurolab,Deutsche Telekom | pCR | Approval | Yes |
Yes
| approved | No | S5‑193230 | |||
S5‑193232 | Presentation of Specification to TSG TR 28.805 | Ericsson GmbH, Eurolab | TS or TR cover | Information | Yes |
Yes
| approved | No | ||||
S5‑193233 | Presentation of Specification to TSG TS 32.160 | Ericsson GmbH, Eurolab | TS or TR cover | Information | No |
Yes
| withdrawn | Yes | ||||
S5‑193235 | Sequence proposal for study on management aspects of communication services | Ericsson GmbH, Eurolab | other | Information | Yes |
Yes
| noted | No | ||||
S5‑193484 | Draft TR 28.805 | Ericsson | draft TR | Approval | Yes |
Yes
| approved | No | ||||
6.5.5 | Study on Self-Organizing Networks (SON) for 5G | S5‑193034 | Minutes of Study on Self-Organizing Networks (SON) for 5G | Rapporteur (Intel) | report | Yes |
Yes
| noted | No | |||
S5‑193042 | pCR to TR 28.861 Service quality optimization | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| revised | No | S5‑193498 | |||
S5‑193498 | pCR to TR 28.861 Service quality optimization | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| approved | No | S5‑193042 | |||
S5‑193043 | pCR to TR 28.861 CCO and Coordination | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| revised | No | S5‑193499 | |||
S5‑193499 | pCR to TR 28.861 CCO and Coordination | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| approved | No | S5‑193043 | |||
S5‑193044 | pCR to TR 28.861 Inter-Cell Interference | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| revised | No | S5‑193500 | |||
S5‑193500 | pCR to TR 28.861 Inter-Cell Interference | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| approved | No | S5‑193044 | |||
S5‑193045 | pCR to TR 28.861 MRO Use Case corrections | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| revised | No | S5‑193501 | |||
S5‑193501 | pCR to TR 28.861 MRO Use Case corrections | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| approved | No | S5‑193045 | |||
S5‑193046 | pCR to TR 28.861 Multi-vendor Plug and Play UC | Cisco Systems Inc. | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑193047 | pCR to TR 28.861 Neighbour Cell Relations | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑193048 | pCR to TR 28.861 NSI resource allocation optimization | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| revised | No | S5‑193504 | |||
S5‑193504 | pCR to TR 28.861 NSI resource allocation optimization | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| revised | No | S5‑193543 | S5‑193048 | ||
S5‑193543 | pCR to TR 28.861 NSI resource allocation optimization | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| approved | No | S5‑193504 | |||
S5‑193049 | pCR to TR 28.861 RACH Optimization | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| revised | No | S5‑193505 | |||
S5‑193505 | pCR to TR 28.861 RACH Optimization | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| approved | No | S5‑193049 | |||
S5‑193050 | pCR to TR 28.861 References fix | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| revised | No | S5‑193502 | |||
S5‑193502 | pCR to TR 28.861 References fix | Cisco Systems Inc.,Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑193050 | |||
S5‑193051 | pCR to TR 28.861 Self-establishment of the NF | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| revised | No | S5‑193506 | |||
S5‑193506 | pCR to TR 28.861 Self-establishment of the NF | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| approved | No | S5‑193051 | |||
S5‑193052 | pCR to TR 28.861 SON in multiple domains | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| revised | No | S5‑193507 | |||
S5‑193507 | pCR to TR 28.861 SON in multiple domains | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| revised | No | S5‑193544 | S5‑193052 | ||
S5‑193544 | pCR to TR 28.861 SON in multiple domains | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| approved | No | S5‑193507 | |||
S5‑193053 | pCR to TR 28.861 Trace and MDT | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑193112 | pCR 28.861 add use case for automatic NSI creation | Intel Corporation (UK) Ltd, Verizon | pCR | Approval | Yes |
Yes
| revised | No | S5‑193509 | |||
S5‑193509 | pCR 28.861 add use case for automatic NSI creation | Intel Corporation (UK) Ltd, Verizon | pCR | Approval | Yes |
Yes
| approved | No | S5‑193112 | |||
S5‑193113 | pCR 28.861 add use case for PCI configuration | Intel Corporation (UK) Ltd, Verizon | pCR | Approval | Yes |
Yes
| merged | No | S5‑193511 | |||
S5‑193114 | pCR 28.803 solution for ANR optimization | Intel Corporation (UK) Ltd, Verizon | pCR | Approval | Yes |
Yes
| revised | No | S5‑193512 | |||
S5‑193512 | pCR 28.803 solution for ANR optimization | Intel Corporation (UK) Ltd, Verizon | pCR | Approval | Yes |
Yes
| noted | No | S5‑193114 | |||
S5‑193115 | pCR 28.861 add use case for beam optimization in CCO | Intel Corporation (UK) Ltd, Verizon, ZTE, Pivotal Commware, PI Works | pCR | Approval | Yes |
Yes
| revised | No | S5‑193513 | |||
S5‑193513 | pCR 28.861 add use case for beam optimization in CCO | Intel Corporation (UK) Ltd, Verizon, ZTE, Pivotal Commware, PI Works | pCR | Approval | Yes |
Yes
| revised | No | S5‑193545 | S5‑193115 | ||
S5‑193545 | pCR 28.861 add use case for beam optimization in CCO | Intel Corporation (UK) Ltd, Verizon, ZTE, Pivotal Commware, PI Works | pCR | Approval | Yes |
Yes
| approved | No | S5‑193513 | |||
S5‑193134 | pCR 28.861 add use case of PCI configuration | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑193511 | |||
S5‑193511 | pCR 28.861 add use case of PCI configuration | Huawei,Intel | pCR | Approval | Yes |
Yes
| approved | No | S5‑193134 | |||
S5‑193135 | pCR 28.861 update the title and concept of ANR management | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑193503 | |||
S5‑193503 | pCR 28.861 update the title and concept of ANR management | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑193135 | |||
S5‑193136 | pCR 28.861 update the concept of trace and MDT | Huawei | pCR | Approval | Yes |
Yes
| merged | No | S5‑193502 | |||
S5‑193155 | pCR 28.861 add use case for cross-slice network resource optimization | KPN N.V. | pCR | Approval | Yes |
Yes
| revised | No | S5‑193514 | |||
S5‑193514 | pCR 28.861 add use case for cross-slice network resource optimization | KPN N.V. | pCR | Approval | Yes |
Yes
| approved | No | S5‑193155 | |||
S5‑193221 | pCR 28.861 Add Multi-dimensional Resource Optimization | Nokia, Nokia Shanghai Bell, Verizon | pCR | Approval | Yes |
Yes
| revised | No | S5‑193520 | |||
S5‑193520 | pCR 28.861 Add Multi-dimensional Resource Optimization | Nokia, Nokia Shanghai Bell, Verizon | pCR | Approval | Yes |
Yes
| approved | No | S5‑193221 | |||
S5‑193307 | pCR discussion sequence | Intel Corporation (UK) Ltd | other | Information | Yes |
Yes
| noted | No | ||||
S5‑193508 | Draft TR 28.861 | Intel | draft TR | Approval | Yes |
Yes
| approved | No | ||||
6.5.6 | Study on non-file-based trace reporting | S5‑193035 | Minutes of Study on non-file-based trace reporting | Rapporteur(Nokia) | report | No |
Yes
| withdrawn | Yes | |||
6.5.7 | Study on non-public networks management | S5‑193036 | Minutes of Study on non-public networks management | Rapporteur (Huawei) | report | Yes |
Yes
| noted | No | |||
S5‑193146 | Initial skeleton of TR 28.807 | Huawei | draft TR | Approval | Yes |
Yes
| revised | No | S5‑193521 | |||
S5‑193521 | Initial skeleton of TR 28.807 | Huawei | draft TR | Approval | Yes |
Yes
| approved | No | S5‑193146 | |||
6.5.8 | Study on management and orchestration aspects with integrated satellite components in a 5G network | S5‑193037 | Minutes of Study on management and orchestration aspects with integrated satellite components in a 5G network | Rapporteur (Thales) | report | Yes |
Yes
| noted | No | |||
S5‑193123 | Table of Content for TR 28.808 (FS_5GSAT_MO) | THALES | draft TR | Agreement | Yes |
Yes
| approved | No | ||||
S5‑193124 | Draft Introduction to TR 28.808 (FS_5GSAT_MO) | THALES | pCR | Agreement | Yes |
Yes
| revised | No | S5‑193522 | |||
S5‑193522 | Introduction to TR 28.808 (FS_5GSAT_MO) | THALES | pCR | Agreement | Yes |
Yes
| approved | No | S5‑193124 | |||
S5‑193125 | Draft Scope of TR 28.808 (FS_5GSAT_MO) | THALES | pCR | Agreement | Yes |
Yes
| revised | No | S5‑193523 | |||
S5‑193523 | Scope of TR 28.808 (FS_5GSAT_MO) | THALES | pCR | Agreement | Yes |
Yes
| approved | No | S5‑193125 | |||
S5‑193126 | Draft Informative Annex A on General Characterics of Satellite Systems for TR 28.808 | THALES | pCR | Agreement | Yes |
Yes
| revised | No | S5‑193524 | |||
S5‑193524 | Informative Annex A on General Characterics of Satellite Systems for TR 28.808 | THALES | pCR | Agreement | Yes |
Yes
| approved | No | S5‑193126 | |||
S5‑193127 | Informative Annex B on Reference Models for Satellite Components for TR 28.808 | THALES | pCR | Agreement | Yes |
Yes
| approved | No | ||||
S5‑193128 | Use case on network slice with a satellite component | THALES | pCR | Agreement | Yes |
Yes
| revised | No | S5‑193526 | |||
S5‑193526 | Use case on network slice with a satellite component | THALES | pCR | Agreement | Yes |
Yes
| approved | No | S5‑193128 | |||
S5‑193236 | Use case on RAN Sharing of Satellite components | THALES | pCR | Agreement | Yes |
Yes
| revised | No | S5‑193527 | |||
S5‑193527 | Use case on RAN Sharing of Satellite components | THALES | pCR | Agreement | Yes |
Yes
| approved | No | S5‑193236 | |||
S5‑193237 | Use case of Management of Satellite components | THALES | pCR | Agreement | Yes |
Yes
| approved | No | ||||
S5‑193525 | Draft TR 28.808 | Thales | draft TR | Approval | Yes |
Yes
| approved | No | ||||
7 | Charging |   | ||||||||||
7.1 | Charging Plenary | S5‑193038 | CH Agenda and Time Plan | CH SWG Chair | agenda | Yes |
Yes
| approved | No | |||
S5‑193039 | CH Executive Report | CH SWG Chair | report | Yes |
Yes
| noted | No | |||||
S5‑193249 | Reply LS from RAN3 cc SA5 on Data Volume Reporting for 5GC | R3-190935 | LS in | Yes |
Yes
| noted | No | |||||
S5‑193255 | Resubmitted LS to SA2 and SA5 on VoWiFi – VoLTE handover | GSMA | LS in | Yes |
Yes
| postponed | No | |||||
S5‑193256 | LS from SA2 cc SA5 on VoWiFi – VoLTE handover | S2-1902884 | LS in | Yes |
Yes
| noted | No | |||||
S5‑193474 | Rel-16 SA5 Charging work – input for further consideration | Charging SWG Chair | discussion | discussion | Yes |
Yes
| noted | No | ||||
7.2 | New Charging Work Item proposals | S5‑193041 | IMS Charging in 5G System Architecture | T-Mobile USA | WID new | Agreement | Yes |
Yes
| revised | No | S5‑193311 | |
S5‑193311 | IMS Charging in 5G System Architecture | T-Mobile USA | WID new | Agreement | Yes |
Yes
| agreed | No | S5‑193041 | |||
S5‑193070 | New WID on Network Slice Charging in 5G System | Huawei | WID new | Agreement | Yes |
Yes
| noted | No | ||||
7.3 | Charging Maintenance and Rel-16 small Enhancements | S5‑193077 | Rel-16 CR 32.290 Clarify the trigger mechanism | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑193425 | |
S5‑193425 | Rel-16 CR 32.290 Clarify the trigger mechanism | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑193077 | |||
S5‑193078 | Rel-15 CR 32.290 Clarify the trigger mechanism | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑193424 | |||
S5‑193424 | Rel-15 CR 32.290 Clarify the trigger mechanism | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑193078 | |||
S5‑193079 | Rel-16 CR 32.291 Add the reference for SMS charging | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑193080 | Rel-16 CR 32.291 Correct the failure handling | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑193341 | |||
S5‑193341 | Rel-16 CR 32.291 Correct the failure handling | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑193080 | |||
S5‑193081 | Rel-16 CR 32.290 Addition of message retry | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑193473 | |||
S5‑193473 | Rel-16 CR 32.290 Addition of message retry | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑193081 | |||
S5‑193082 | Rel-15 CR 32.290 Addition of message retry | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑193096 | Rel-15 CR 32.290 Correction on error handling | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑193342 | |||
S5‑193342 | Rel-15 CR 32.290 Correction on error handling | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑193096 | |||
S5‑193097 | Rel-16 CR 32.290 Correction on error handling | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑193343 | |||
S5‑193343 | Rel-16 CR 32.290 Correction on error handling | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑193097 | |||
S5‑193098 | Rel-15 CR 32.291 Correction on errors description | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑193423 | |||
S5‑193423 | Rel-15 CR 32.291 Correction on errors description | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑193098 | |||
S5‑193099 | Rel-15 CR 32.291 Correction on Gateway timeout code | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑193177 | Rel-15 CR 32.298 Corrections on ASN.1 | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑193178 | Rel-16 CR 32.298 Corrections on ASN.1 | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑193204 | Rel-15 CR 32.298 Correction of local sequence number | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑193426 | |||
S5‑193426 | Rel-15 CR 32.298 Correction of local sequence number | Nokia, Nokia Shanghai Bell,Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑193204 | |||
S5‑193205 | Rel-16 CR 32.298 Correction of local sequence number | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑193427 | |||
S5‑193427 | Rel-16 CR 32.298 Correction of local sequence number | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑193205 | |||
S5‑193206 | Rel-15 CR 32.291 Correction of used unit container attributes | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑193207 | Rel-15 CR 32.291 Correction on binding | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑193471 | |||
S5‑193471 | Rel-15 CR 32.291 Correction on binding | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑193207 | |||
S5‑193283 | Rel-15 CR 32.290 Correction of Failure and Retry handling | Ericsson | CR | Approval | Yes |
Yes
| revised | No | S5‑193344 | |||
S5‑193344 | Rel-15 CR 32.290 Correction of Failure and Retry handling | Ericsson | CR | Approval | Yes |
Yes
| agreed | No | S5‑193283 | |||
S5‑193284 | Rel-15 CR 32.255 Correction of Termination action | Ericsson | CR | Approval | Yes |
Yes
| revised | No | S5‑193345 | |||
S5‑193345 | Rel-15 CR 32.255 Correction of Termination action | Ericsson | CR | Approval | Yes |
Yes
| agreed | No | S5‑193284 | |||
S5‑193285 | Rel-15 CR 32.290 Correction of result code classification | Ericsson | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑193286 | Rel-15 CR 32.251 Adding APN rate-control information and remove editor's notes | Ericsson | CR | Approval | Yes |
Yes
| revised | No | S5‑193428 | |||
S5‑193428 | Rel-15 CR 32.251 Adding APN rate-control information and remove editor's notes | Ericsson | CR | Approval | Yes |
Yes
| agreed | No | S5‑193286 | |||
S5‑193287 | Rel-15 CR 32.298 Adding Rate-Control information and triggers to CDRs | Ericsson | CR | Approval | Yes |
Yes
| revised | No | S5‑193429 | |||
S5‑193429 | Rel-15 CR 32.298 Adding Rate-Control information and triggers to CDRs | Ericsson | CR | Approval | Yes |
Yes
| agreed | No | S5‑193287 | |||
S5‑193288 | Rel-15 CR 32.299 Adding Rate-Control information and triggers to Rf offline charging | Ericsson | CR | Approval | Yes |
Yes
| revised | No | S5‑193430 | |||
S5‑193430 | Rel-15 CR 32.299 Adding Rate-Control information and triggers to Rf offline charging | Ericsson | CR | Approval | Yes |
Yes
| agreed | No | S5‑193288 | |||
S5‑193289 | Rel-15 CR 32.290 Correction of termination handling | Ericsson | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑193290 | Rel-15 CR 32.298 Correction of Presence Reporting Area | Ericsson | CR | Approval | Yes |
Yes
| revised | No | S5‑193433 | |||
S5‑193433 | Rel-15 CR 32.298 Correction of Presence Reporting Area | Ericsson | CR | Approval | Yes |
Yes
| agreed | No | S5‑193290 | |||
S5‑193291 | Rel-15 CR 32.290 Correction of QBC roaming definition | Ericsson | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑193292 | Rel-15 CR 32.255 Correction of Start of a QoS Flow trigger | Ericsson | CR | Approval | Yes |
Yes
| revised | No | S5‑193436 | |||
S5‑193436 | Rel-15 CR 32.255 Correction of Start of a QoS Flow trigger | Ericsson | CR | Approval | Yes |
Yes
| agreed | No | S5‑193292 | |||
S5‑193293 | Rel-15 CR 32.255 Correction of missing SDF abbreviation | Ericsson | CR | Approval | Yes |
Yes
| revised | No | S5‑193465 | |||
S5‑193465 | Rel-16 CR 32.255 Correction of missing SDF abbreviation | Ericsson | CR | Approval | Yes |
Yes
| agreed | No | S5‑193293 | |||
S5‑193294 | Rel-15 CR 32.291 Correction of trigger type for start of service data flow | Ericsson | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑193295 | Rel-15 CR 32.291 Correction of trigger type unit count inactivity timer | Ericsson | CR | Approval | Yes |
Yes
| revised | No | S5‑193466 | |||
S5‑193466 | Rel-15 CR 32.291 Correction of trigger type unit count inactivity timer | Ericsson | CR | Approval | Yes |
Yes
| agreed | No | S5‑193295 | |||
S5‑193296 | Rel-15 CR 32.298 Correction of usage of local sequence number import | Ericsson | CR | Approval | Yes |
Yes
| merged | No | S5‑193426 | |||
S5‑193297 | Rel-15 CR 32.291 Correction of Nchf_ConvergedCharging release usage | Ericsson | CR | Approval | Yes |
Yes
| revised | No | S5‑193467 | |||
S5‑193467 | Rel-15 CR 32.291 Correction of Nchf_ConvergedCharging release usage | Ericsson | CR | Approval | Yes |
Yes
| agreed | No | S5‑193297 | |||
S5‑193298 | Rel-15 CR 32.290 Correction of Release naming | Ericsson | CR | Approval | Yes |
Yes
| revised | No | S5‑193468 | |||
S5‑193468 | Rel-15 CR 32.290 Correction of Release naming | Ericsson | CR | Approval | Yes |
Yes
| agreed | No | S5‑193298 | |||
S5‑193299 | Rel-15 CR 32.291 Correction of missing http status codes | Ericsson | CR | Approval | Yes |
Yes
| revised | No | S5‑193470 | |||
S5‑193470 | Rel-15 CR 32.291 Correction of missing http status codes | Ericsson | CR | Approval | Yes |
Yes
| agreed | No | S5‑193299 | |||
S5‑193431 | Adding Rate-Control information and triggers to CDRs | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑193432 | Adding Rate-Control information and triggers to Rf offline charging | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑193434 | Rel-16 CR 32.298 Correction of Presence Reporting Area | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑193435 | Rel-16 CR 32.290 Correction of QBC roaming definition | Ericsson | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
S5‑193437 | Rel-16 CR 32.255 Correction of Start of a QoS Flow trigger | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑193469 | Rel-16 CR 32.290 Correction of Release naming | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
7.4 | Rel-16 Charging |   | ||||||||||
7.4.1 | Volume Based Charging Aspects for VoLTE | S5‑193060 | Revised WID on Volume Based Charging Aspects for VoLTE | China Mobile | WID revised | Yes |
Yes
| revised | No | S5‑193312 | ||
S5‑193312 | Revised WID on Volume Based Charging Aspects for VoLTE | China Mobile | WID revised | - | Yes |
Yes
| agreed | No | S5‑193060 | |||
7.4.2 | Nchf Online and Offline Charging Services | S5‑193083 | CR Rel-16 32.255 Add detailed message format for offline only charging | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑193313 | |
S5‑193313 | CR Rel-16 32.255 Add detailed message format for offline only charging | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑193083 | |||
S5‑193084 | CR Rel-16 32.291 Add Offline only charging service API name | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑193316 | |||
S5‑193316 | CR Rel-16 32.291 Add Offline only charging service API name | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑193084 | |||
S5‑193085 | CR Rel-16 32.291 Add Offline only charging service API resource definition | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑193319 | |||
S5‑193319 | CR Rel-16 32.291 Add Offline only charging service API resource definition | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑193085 | |||
S5‑193086 | CR Rel-16 32.291 Add Offline only charging service API data model | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑193320 | |||
S5‑193320 | CR Rel-16 32.291 Add Offline only charging service API data model | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑193086 | |||
S5‑193087 | CR Rel-16 32.291 Add Offline only charging service API error handling | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑193321 | |||
S5‑193321 | CR Rel-16 32.291 Add Offline only charging service API error handling | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑193087 | |||
S5‑193088 | CR Rel-16 32.255 Add PCF rule for offline only charging service | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑193314 | |||
S5‑193314 | CR Rel-16 32.255 Add PCF rule for offline only charging service | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑193088 | |||
S5‑193100 | Rel-16 CR 32.255 CHF selection in offline only | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑193318 | |||
S5‑193318 | Rel-16 CR 32.255 CHF selection in offline only | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑193100 | |||
S5‑193154 | Rel-16 CR 32.290 Correct offline only charging service API name | Huawei Tech.(UK) Co., Ltd | CR | Agreement | Yes |
Yes
| revised | No | S5‑193315 | |||
S5‑193315 | Rel-16 CR 32.290 Correct offline only charging service API name | Huawei Tech.(UK) Co., Ltd | CR | Agreement | Yes |
Yes
| agreed | No | S5‑193154 | |||
S5‑193176 | Rel-16 CR 32.290 CHF profile for offline only | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑193317 | CR Rel-16 32.291 Add Offline only charging service API description | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
7.4.3 | Charging Enhancement of 5GC interworking with EPC | S5‑193071 | Rel-16 Discussion Paper on Charging Identifier for 5GS and EPS | Huawei | discussion | Agreement | Yes |
Yes
| noted | No | ||
S5‑193072 | Rel-16 CR 32.255 Clarification on the Charging Identifier | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑193322 | |||
S5‑193322 | Rel-16 CR 32.255 Clarification on the Charging Identifier | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑193072 | |||
S5‑193073 | Rel-16 CR 32.255 Clarify the Charging Session for interworking | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑193323 | |||
S5‑193323 | Rel-16 CR 32.255 Clarify the Charging Session for interworking | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑193073 | |||
S5‑193074 | Rel-16 CR 32.255 Add the quota management for interworking | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑193324 | |||
S5‑193324 | Rel-16 CR 32.255 Add the quota management for interworking | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑193074 | |||
S5‑193075 | Rel-16 CR 32.255 Definition of charging information for interworking with EPC | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑193325 | |||
S5‑193325 | Rel-16 CR 32.255 Definition of charging information for interworking with EPC | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑193075 | |||
S5‑193076 | Rel-16 CR 32.291 Definition of data model for interworking with EPC | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑193472 | |||
S5‑193472 | Rel-16 CR 32.291 Definition of data model for interworking with EPC | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑193076 | |||
7.4.4 | Network Exposure Charging in 5G System Architecture | S5‑193280 | Rel-16 CR 32.254 Addition of NEF charging data for Converged Charging | Ericsson | CR | Approval | Yes |
Yes
| revised | No | S5‑193327 | |
S5‑193327 | Rel-16 CR 32.254 Addition of NEF charging data for Converged Charging | Ericsson | CR | Approval | Yes |
Yes
| agreed | No | S5‑193280 | |||
S5‑193281 | Rel-16 CR 32.254 Addition of NEF charging information | Ericsson | CR | Approval | Yes |
Yes
| revised | No | S5‑193328 | |||
S5‑193328 | Rel-16 CR 32.254 Addition of NEF charging information | Ericsson | CR | Approval | Yes |
Yes
| agreed | No | S5‑193281 | |||
S5‑193282 | Rel-16 CR 32.254 Addition of NEF trigger information | Ericsson | CR | Approval | Yes |
Yes
| revised | No | S5‑193326 | |||
S5‑193326 | Rel-16 CR 32.254 Addition of NEF trigger information | Ericsson | CR | Approval | Yes |
Yes
| agreed | No | S5‑193282 | |||
7.4.5 | Charging AMF in 5G System Architecture Phase 1 | S5‑193090 | Rel-16 pCR 32.256 N2 connection message flows | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑193329 | |
S5‑193329 | Rel-16 pCR 32.256 N2 connection message flows | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑193090 | |||
S5‑193091 | Rel-16 pCR 32.256 Applicable Triggers | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑193330 | |||
S5‑193330 | Rel-16 pCR 32.256 Applicable Triggers | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑193091 | |||
S5‑193092 | Rel-16 pCR 32.256 CDRs generation | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑193331 | |||
S5‑193331 | Rel-16 pCR 32.256 CDRs generation | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑193092 | |||
S5‑193093 | Rel-16 pCR 32.256 CDRs transfer | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑193332 | |||
S5‑193332 | Rel-16 pCR 32.256 CDRs transfer | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑193093 | |||
S5‑193094 | Rel-16 pCR 32.256 Message content description | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑193333 | |||
S5‑193333 | Rel-16 pCR 32.256 Message content description | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| agreed | No | S5‑193094 | |||
S5‑193095 | Rel-16 pCR 32.256 Connection Mobility charging information | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑193334 | |||
S5‑193334 | Rel-16 pCR 32.256 Connection Mobility charging information | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| agreed | No | S5‑193095 | |||
S5‑193340 | Draft TS 32.256 | Nokia, Nokia Shanghai Bell | draft TR | Approval | Yes |
Yes
| approved | No | ||||
7.5 | Charging Studies |   | ||||||||||
7.5.1 | Study on Charging Aspects of Network Slicing | S5‑193066 | Rel-16 Discussion Paper on the performance based charging for network slice | Huawei | discussion | Agreement | Yes |
Yes
| noted | No | ||
S5‑193067 | Rel-16 pCR TR 32.845 Add the solution evaluation for performance based charging | Huawei | pCR | Agreement | Yes |
Yes
| noted | No | ||||
S5‑193068 | Rel-16 pCR TR 32.845 Clarify the interaction with management system | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑193337 | |||
S5‑193337 | Rel-16 pCR TR 32.845 Clarify the interaction with management system | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑193068 | |||
S5‑193069 | Rel-16 pCR TR 32.845 Clarify the Network slice instance charging | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | ||||
S5‑193208 | Rel-16 pCR 32.845 Addition of solution for NSI Performance Charging | Openet Telecom | pCR | Agreement | Yes |
Yes
| revised | No | S5‑193335 | |||
S5‑193335 | Rel-16 pCR 32.845 Addition of solution for NSI Performance Charging | Openet Telecom | pCR | Agreement | Yes |
Yes
| approved | No | S5‑193208 | |||
S5‑193219 | Rel-16 pCR 32.845 Addition of solution evaluation for solution #1.4 | Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S5‑193336 | |||
S5‑193336 | Rel-16 pCR 32.845 Addition of solution evaluation for solution #1.4 | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S5‑193219 | |||
S5‑193220 | Rel-16 pCR 32.845 Updating evaluation | Ericsson | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑193238 | Rel-16 pCR 32.845 Clarification of aggregation for NSI Charging | Openet Telecom | pCR | Approval | Yes |
Yes
| revised | No | S5‑193338 | |||
S5‑193338 | Rel-16 pCR 32.845 Clarification of aggregation for NSI Charging | Openet Telecom | pCR | Approval | Yes |
Yes
| approved | No | S5‑193238 | |||
S5‑193339 | Draft R 32.845 | Huawei | draft TR | Approval | Yes |
Yes
| approved | No | ||||
8 | Any Other Business |   | ||||||||||
9 | Closing of the meeting |   |