Tdoc List
2020-11-02 15:15
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‑205000 | Agenda | WG Chair | agenda | Yes |
Yes
| approved | No | |||
3 | IPR and legal declaration |   | ||||||||||
4 | Meetings and activities reports |   | ||||||||||
4.1 | Last SA5 meeting report | S5‑205001 | Report from last SA5 meeting | MCC | report | Yes |
Yes
| approved | No | |||
4.2 | Last SA meeting report |   | ||||||||||
4.3 | Inter-organizational reports |   | ||||||||||
5 | Cross-SWG issues |   | ||||||||||
5.1 | Administrative issues at SA5 level | S5‑205002 | SA5#133e e-meeting process | WG Chair | discussion | Yes |
Yes
| noted | No | |||
S5‑205003 | Post SA5#133e Email approval status | WG Chair | other | Yes |
No
| available | No | |||||
S5‑205011 | SA5 working procedures | WG Chair | other | Yes |
Yes
| noted | No | |||||
5.2 | Technical issues at SA5 level |   | ||||||||||
5.3 | Liaison statements at SA5 level | S5‑205020 | Reply LS to SA5 on QoS requirements for OAM traffic on IAB | S2-2006489 | LS in | Yes |
Yes
| noted | No | |||
S5‑205024 | LS to SA5 on Rel-17 schedule | 3GPP TSG SA | LS in | Yes |
Yes
| noted | No | |||||
S5‑205194 | Reply LS on Counter of UEs Registering Network Slice | China Mobile Com. Corporation | LS out | Yes |
Yes
| noted | No | |||||
S5‑205271 | LS on Counter of UEs Registering Network Slice | C4-204421 | LS in | Yes |
Yes
| postponed | No | |||||
5.4 | SA5 meeting calendar | S5‑205010 | SA5 meeting calendar | WG Chair | other | Yes |
Yes
| noted | No | |||
6 | OAM&P |   | ||||||||||
6.1 | OAM&P Plenary | S5‑205004 | OAM&P SWG action list | WG Chair | other | No |
Yes
| noted | No | |||
S5‑205005 | SA5#133e_agenda_with_Tdocs_sequence_proposal_OAM | WG Vice Chair | agenda | Yes |
Yes
| noted | No | |||||
S5‑205006 | SA5#132e OAM Exec Report | WG Vice Chair | report | No |
No
| reserved | No | |||||
S5‑205007 | SA5#133e OAM Chair notes and conclusions | WG Chair | report | Yes |
Yes
| revised | No | S5‑205406 | ||||
S5‑205406 | SA5#133e OAM Chair notes and conclusions | WG Chair | report | - | Yes |
No
| available | No | S5‑205007 | |||
S5‑205013 | LS to SA5 on TM Forum implementation experiences 3GPP NRM Models | TM Forum | LS in | Yes |
Yes
| replied to | No | |||||
S5‑205348 | Reply to: LS to SA5 on TM Forum implementation experiences 3GPP NRM Models | Huawei | LS out | approval | Yes |
Yes
| approved | No | ||||
S5‑205015 | LS to SA5 for End-to-End Network Slicing Gap analysis | GSMA NEST | LS in | Yes |
Yes
| noted | No | |||||
S5‑205016 | Reply LS to SA5 on the clarification of handover and reselection parameters | R3-205542 | LS in | Yes |
Yes
| noted | No | |||||
S5‑205017 | Reply LS to SA5 on energy efficiency | R3-205657 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑205357 | Reply to: Reply LS to SA5 on energy efficiency | ORANGE | LS out | approval | Yes |
Yes
| approved | No | S5‑205232 | |||
S5‑205018 | LS ccSA5 on New service type of NR QoE | R3-205724 | LS in | Yes |
Yes
| noted | No | |||||
S5‑205019 | LS to SA5 on URI for streaming trace reporting in LTE | R3-205798 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑205021 | Resubmitted Reply LS to SA5 on QoE Measurement Collection | R2-2005778 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑205347 | Reply to: Resubmitted Reply LS to SA5 on QoE Measurement Collection | Ericsson | LS out | approval | Yes |
Yes
| approved | No | ||||
S5‑205022 | Resubmitted LS to SA5 on QoE Measurement Collection | S4-200962 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑205023 | Resubmitted LS to SA5 on O-RAN – 3GPP Cooperation on Management Services | O-RAN | LS in | Yes |
Yes
| postponed | No | |||||
S5‑205045 | LS to SA5 on Introduction of TM Forum Autonomous Network project and Coordination Proposal | TM Forum | LS in | Yes |
Yes
| noted | No | |||||
S5‑205062 | Collection of useful endorsed document and external communication documents | Huawei Technologies (Korea) | other | Yes |
Yes
| noted | No | |||||
S5‑205092 | Reply LS on URI for streaming trace reporting in LTE | Ericsson LM | LS out | Information | Yes |
Yes
| revised | No | S5‑205356 | |||
S5‑205356 | Reply LS on URI for streaming trace reporting in LTE | Ericsson LM | LS out | Information | Yes |
Yes
| approved | No | S5‑205092 | |||
S5‑205198 | TD Creation of a new TS with example MnFs and procedures | Nokia, Nokia Shanghai Bell | discussion | Agreement | Yes |
Yes
| noted | No | ||||
S5‑205199 | Rel-16 OAM Stage2 and Stage3 Mapping Status | SA5 Vice Chair(Huawei), SA5 Chair | other | Yes |
Yes
| revised | No | S5‑205358 | ||||
S5‑205358 | Rel-16 OAM Stage2 and Stage3 Mapping Status | SA5 Vice Chair(Huawei), SA5 Chair | other | - | Yes |
Yes
| noted | No | S5‑205199 | |||
S5‑205230 | Specification investigation | Ericsson | discussion | Yes |
Yes
| revised | No | S5‑205359 | ||||
S5‑205359 | Specification investigation | Ericsson | discussion | - | Yes |
Yes
| endorsed | No | S5‑205230 | |||
S5‑205232 | LS Reply to RAN3 on Energy Efficiency | Orange | LS out | Approval | Yes |
Yes
| revised | No | S5‑205357 | |||
S5‑205276 | fix description related to service profile | Nokia | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑205323 | List of draftCRs | SA WG5 | other | Information | Yes |
No
| available | No | ||||
S5‑205349 | Discussion on YANG interface for Network Slice Management | Cisco | discussion | discussion | No |
Yes
| withdrawn | Yes | ||||
S5‑205354 | Discussion paper for discontinuing XML solution set from Rel-16 | Huawei | discussion | discussion | Yes |
Yes
| endorsed | No | ||||
S5‑205355 | Reply LS to O-RAN – 3GPP Cooperation on Management Services | Huawei | LS out | Approval | Yes |
Yes
| noted | No | ||||
6.2 | New OAM&P Work Item proposals |   | ||||||||||
6.3 | OAM&P Maintenance and Rel-16 small Enhancements | S5‑205047 | Rel-15 CR 28.554 Correct UDM e2e KPI | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑205360 | |
S5‑205360 | Rel-15 CR 28.554 Correct UDM e2e KPI | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑205047 | |||
S5‑205048 | Rel-16 CR 28.554 Correct UDM e2e KPI | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑205361 | |||
S5‑205361 | Rel-16 CR 28.554 Correct UDM e2e KPI | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑205048 | |||
S5‑205049 | Rel-17 CR 28.554 Correct UDM e2e KPI | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑205362 | |||
S5‑205362 | Rel-17 CR 28.554 Correct UDM e2e KPI | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑205049 | |||
S5‑205053 | Rel-16 CR 28.536 Update references to other specifications | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑205399 | |||
S5‑205399 | Rel-16 CR 28.536 Update references to other specifications | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑205053 | |||
S5‑205054 | Rel-16 CR TS 28.536 Clarify predicted value of the AssuranceGoalStatus | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑205404 | |||
S5‑205404 | Rel-16 CR TS 28.536 Clarify predicted value of the AssuranceGoalStatus | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑205054 | |||
S5‑205055 | Rel-16 CR TS 28.554 Fix the formula for upstream throughout | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑205056 | Rel-17 CR TS 28.554 Fix the formula for upstream throughout | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑205057 | Rel-16 CR TS 32.422 Clarification of tracing roaming UE for 5GC | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑205365 | |||
S5‑205365 | Rel-16 CR TS 32.422 Clarification of tracing roaming UE for 5GC | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑205057 | |||
S5‑205058 | Rel-17 CR TS 32.422 Clarification of tracing roaming UE for 5GC | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑205366 | |||
S5‑205366 | Rel-17 CR TS 32.422 Clarification of tracing roaming UE for 5GC | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑205058 | |||
S5‑205059 | Correct streaming trace record concept figure | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑205060 | YANG corrections by Code Moderator | Ericsson Hungary Ltd | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑205395 | |||
S5‑205395 | YANG corrections by Code Moderator | Ericsson Hungary Ltd | discussion | Endorsement | Yes |
Yes
| endorsed | No | S5‑205060 | |||
S5‑205061 | Correction of NRM YANG errors | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑205063 | Correction of NRM YANG errors | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑205094 | R16 CR TS 28.541 add subclause reference of MRO related attribute | Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑205373 | |||
S5‑205373 | R16 CR TS 28.541 add subclause reference of MRO related attribute | Huawei | CR | Approval | Yes |
Yes
| agreed | No | S5‑205094 | |||
S5‑205095 | R16 CR TS 28.313 add subclause reference for ranges of handover parameters | Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑205379 | |||
S5‑205379 | R16 CR TS 28.313 add subclause reference for ranges of handover parameters | Huawei | CR | Approval | Yes |
Yes
| agreed | No | S5‑205095 | |||
S5‑205096 | R16 CR TS 28.313 corrections on notification information of PCI configuration | Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑205380 | |||
S5‑205380 | R16 CR TS 28.313 corrections on notification information of PCI configuration | Huawei | CR | Approval | Yes |
Yes
| agreed | No | S5‑205096 | |||
S5‑205101 | Rel-16 CR TS 28.532 Correction on generic file data report MnS | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑205385 | |||
S5‑205385 | Rel-16 CR TS 28.532 Correction on generic file data report MnS | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑205101 | |||
S5‑205102 | Rel-16 CR TS 28.532 Update generic streaming MnS | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑205386 | |||
S5‑205386 | Rel-16 CR TS 28.532 Update generic streaming MnS | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑205102 | |||
S5‑205103 | Rel-15 CR TS 28.658 Add missing inheritance diagram for EUtranFrequency and EUtranFreqRelation | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑205104 | Rel-16 CR TS 28.658 Add missing inheritance diagram for EUtranFrequency and EUtranFreqRelation | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑205105 | Rel-16 CR TS 28.541 Correct the definition for configurable5QI and dynamic5QI | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑205106 | Rel-17 CR TS 28.541 Correct the definition for configurable5QI and dynamic5QI | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑205110 | Rel-16 CR 32.422 Fix inconsistencies in NR positioning method | Nokia | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑205111 | Rel-17 CR 32.422 Fix inconsistencies in NR positioning method | Nokia | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑205129 | Rel-16 CR 28.313 address the issues discovered by Edithelp | Intel Sweden AB | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
S5‑205130 | Rel-16 CR 28.313 address the issues discovered by Edithelp | Intel Corporation (UK) Ltd | CR | Approval | Yes |
Yes
| revised | No | S5‑205378 | |||
S5‑205378 | Rel-16 CR 28.313 address the issues discovered by Edithelp | Intel Corporation (UK) Ltd | CR | Approval | Yes |
Yes
| agreed | No | S5‑205130 | |||
S5‑205131 | Rel.16 CR 28.313 Fix the wrong references | Intel Corporation (UK) Ltd | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑205136 | Rel-16 CR 28.313 Change RACH control attributes from beam to cell | Ericsson France S.A.S, Intel | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑205137 | Rel-16 CR 28.541 Change RACH control attributes from beam to cell | Ericsson France S.A.S, Intel | CR | Approval | Yes |
Yes
| revised | No | S5‑205374 | |||
S5‑205374 | Rel-16 CR 28.541 Change RACH control attributes from beam to cell | Ericsson France S.A.S, Intel | CR | Approval | Yes |
Yes
| agreed | No | S5‑205137 | |||
S5‑205138 | Rel-17 CR 28.541 Change RACH control attributes from beam to cell | Ericsson France S.A.S, Intel | CR | Approval | Yes |
Yes
| revised | No | S5‑205375 | |||
S5‑205375 | Rel-17 CR 28.541 Change RACH control attributes from beam to cell | Ericsson France S.A.S, Intel | CR | Approval | Yes |
Yes
| agreed | No | S5‑205138 | |||
S5‑205139 | Rel-16 CR 28.541 Move Distributed RACH control IOC from CU to DU | Ericsson France S.A.S | CR | Approval | Yes |
Yes
| revised | No | S5‑205376 | |||
S5‑205376 | Rel-16 CR 28.541 Move Distributed RACH control IOC from CU to DU | Ericsson France S.A.S | CR | Approval | Yes |
Yes
| agreed | No | S5‑205139 | |||
S5‑205140 | Rel-17 CR 28.541 Move Distributed RACH control IOC from CU to DU | Ericsson France S.A.S | CR | Approval | Yes |
Yes
| revised | No | S5‑205377 | |||
S5‑205377 | Rel-17 CR 28.541 Move Distributed RACH control IOC from CU to DU | Ericsson France S.A.S | CR | Approval | Yes |
Yes
| agreed | No | S5‑205140 | |||
S5‑205141 | Rel-16 CR 28.313 Correct Distributed PCI optimization | Ericsson France S.A.S | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑205142 | Rel-16 CR 28.541 Move Distributed PCI control IOC from DU to CU | Ericsson France S.A.S | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑205143 | Rel-17 CR 28.541 Move Distributed PCI control IOC from DU to CU | Ericsson France S.A.S | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑205151 | Rel-17 CR 28.554 Editorial Correction of TS 28.554 | Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑205363 | |||
S5‑205363 | Rel-17 CR 28.554 Editorial Correction of TS 28.554 | Huawei.ORANGE | CR | Approval | Yes |
Yes
| agreed | No | S5‑205151 | |||
S5‑205152 | Rel-16 CR 28.554 Editorial Correction of TS 28.554 | Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑205364 | |||
S5‑205364 | Rel-16 CR 28.554 Editorial Correction of TS 28.554 | Huawei,ORANGE | CR | Approval | Yes |
Yes
| agreed | No | S5‑205152 | |||
S5‑205153 | Rel-17 CR 28.541 Correction of cell neighbour relations related attributes in openAPI solution | Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑205367 | |||
S5‑205367 | Rel-17 CR 28.541 Correction of cell neighbour relations related attributes in openAPI solution | Huawei | CR | Approval | Yes |
Yes
| agreed | No | S5‑205153 | |||
S5‑205154 | Rel-16 CR 28.541 Correction of cell neighbour relations related attributes in openAPI solution | Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑205368 | |||
S5‑205368 | Rel-16 CR 28.541 Correction of cell neighbour relations related attributes in openAPI solution | Huawei | CR | Approval | Yes |
Yes
| agreed | No | S5‑205154 | |||
S5‑205155 | Cleanup based on refined slice definition | Ericsson LM | CR | Approval | Yes |
Yes
| revised | No | S5‑205390 | |||
S5‑205390 | Cleanup based on refined slice definition | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | S5‑205155 | |||
S5‑205156 | Rel-16 CR 28.532 Correct CR implementation errors (Fault MnS) | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑205381 | |||
S5‑205381 | Rel-16 CR 28.532 Correct CR implementation errors (Fault MnS) | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑205156 | |||
S5‑205157 | Rel-16 CR 28.532 Extend object creation method with id selection by the MnS producer (stage 2) | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑205158 | Rel-16 CR 28.532 Correct ThresholdLevelInd (REST SS, OpenAPI definition) | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑205388 | |||
S5‑205388 | Rel-16 CR 28.532 Correct ThresholdLevelInd (REST SS, OpenAPI definition) | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑205158 | |||
S5‑205187 | Rel-16 CR 28.532 Correct notifyThresholdCrossing (stage 2) | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑205188 | Rel-16 CR 28.532 Correct notifyThresholdCrossing (REST SS, OpenAPI definition) | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑205387 | |||
S5‑205387 | Rel-16 CR 28.532 Correct notifyThresholdCrossing (REST SS, OpenAPI definition) | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑205188 | |||
S5‑205189 | Rel-16 CR 28.532 Correct notifyHeartbeat (stage 2, REST SS, OpenAPI definition) | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑205382 | |||
S5‑205382 | Rel-16 CR 28.532 Correct notifyHeartbeat (stage 2, REST SS, OpenAPI definition) | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑205189 | |||
S5‑205190 | Rel-16 CR 28.622 Remove thresholdLevel attribute from ThresholdMonitor (stage 2) | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑205389 | |||
S5‑205389 | Rel-16 CR 28.622 Remove thresholdLevel attribute from ThresholdMonitor (stage 2) | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑205190 | |||
S5‑205191 | Rel-16 CR 28.623 Remove thresholdLevel attribute from ThresholdMonitor (OpenAPI definition) | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑205193 | Rel-16 CR 28.532 Correct small errors in faultMnS.yaml (OpenAPI definition) | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑205195 | Rel-16 CR 28.623 Correct and add types in comDefs.yaml (OpenAPI definition) | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑205393 | |||
S5‑205393 | Rel-16 CR 28.623 Correct and add types in comDefs.yaml (OpenAPI definition) | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑205195 | |||
S5‑205200 | Rel-16 CR 28.530 Add missing definition of SLA and update definition of SLS | Huawei | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑205218 | Correction of NRM YANG errors | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑205225 | Rel-16 CR TS 28.541 Correct Network slice NRM | CATT | CR | Approval | Yes |
Yes
| revised | No | S5‑205369 | |||
S5‑205369 | Rel-16 CR TS 28.541 Correct Network slice NRM | CATT | CR | Approval | Yes |
Yes
| agreed | No | S5‑205225 | |||
S5‑205228 | Rel-17 CR TS 28.541 Correct Network slice NRM | CATT | CR | Approval | Yes |
Yes
| revised | No | S5‑205370 | |||
S5‑205370 | Rel-17 CR TS 28.541 Correct Network slice NRM | CATT | CR | Approval | Yes |
Yes
| agreed | No | S5‑205228 | |||
S5‑205231 | Import prefix rule for YANG | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| revised | No | S5‑205396 | |||
S5‑205396 | Import prefix rule for YANG | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| agreed | No | S5‑205231 | |||
S5‑205235 | Clarification on emission of threshold crossing notifications for non-cumulative counters | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑205238 | Move and update content of clause 4.1.1 Overview to Annex | Ericsson LM, Deutsche Telekom, NEC | CR | Approval | Yes |
Yes
| revised | No | S5‑205397 | |||
S5‑205397 | Move and update content of clause 4.1.1 Overview to Annex | Ericsson LM, Deutsche Telekom, NEC | CR | Approval | Yes |
Yes
| agreed | No | S5‑205238 | |||
S5‑205240 | Update and make closed control loop term consistent | Ericsson LM, Deutsche Telekom, NEC | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑205241 | Update and make closed control loop term consistent | Ericsson LM, Deutsche Telekom, NEC | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑205242 | Proposal on Assurance Closed Loop model updates | Ericsson LM, Deutsche Telekom, NEC | discussion | Yes |
Yes
| noted | No | |||||
S5‑205243 | Rel-16 CR 28.623 Use comDefs.yaml instead of local definitions in genericNrm.yaml (OpenAPI definition) | Nokia, Nokia Shanhai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑205394 | |||
S5‑205394 | Rel-16 CR 28.623 Use comDefs.yaml instead of local definitions in genericNrm.yaml (OpenAPI definition) | Nokia, Nokia Shanhai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑205243 | |||
S5‑205244 | Implement Assurance Closed Loop model changes | Ericsson LM, Deutsche Telekom, NEC | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑205398 | Implement Assurance Closed Loop model changes | Ericsson LM, Deutsche Telekom, NEC | draftCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑205245 | Rel-16 CR 32.423 Fix inconsistencies in NR positioning method | Nokia | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑205246 | Remove attribute perfMetricJobGroupId | Ericsson LM | CR | Agreement | Yes |
Yes
| revised | No | S5‑205391 | |||
S5‑205391 | Remove attribute perfMetricJobGroupId | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | S5‑205246 | |||
S5‑205247 | Remove attribute perfMetricJobGroupId | Ericsson LM | CR | Agreement | Yes |
Yes
| revised | No | S5‑205392 | |||
S5‑205392 | Remove attribute perfMetricJobGroupId | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | S5‑205247 | |||
S5‑205251 | add abbreviations | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑205252 | add abbreviations reference | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑205253 | add containment relationship for network slice IOC | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑205258 | Remove value handling from the granularityPeriod description. | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑205259 | Remove value handling from the granularityPeriod description. | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑205260 | add containment relationship for network slice IOC stage 3 | Nokia Germany | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑205261 | Correction of network slice NRM | Ericsson LM | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑205262 | Correction of network slice NRM | Ericsson LM | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑205263 | Stage3 Correction of network slice NRM | Ericsson LM | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑205264 | Stage 3 Correction of network slice NRM | Ericsson LM | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑205265 | Correction of allocateNsi operations and procedures | Ericsson LM | CR | Approval | Yes |
Yes
| revised | No | S5‑205372 | |||
S5‑205372 | Correction of allocateNsi operations and procedures | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | S5‑205265 | |||
S5‑205266 | Rel-16 CR 28.532 Correct notifyChangedAlarmGeneral (stage 2) | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑205383 | |||
S5‑205383 | Rel-16 CR 28.532 Correct notifyChangedAlarmGeneral (stage 2) | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑205266 | |||
S5‑205267 | Rel-16 CR 28.532 Correct notifyChangedAlarmGeneral (REST SS, OpenAPI definitions) | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑205384 | |||
S5‑205384 | Rel-16 CR 28.532 Correct notifyChangedAlarmGeneral (REST SS, OpenAPI definitions) | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑205267 | |||
S5‑205268 | Proposal on updates to network slice model and procedures | Ericsson LM | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑205405 | |||
S5‑205405 | Proposal on updates to network slice model and procedures | Ericsson LM | discussion | Endorsement | Yes |
Yes
| endorsed | No | S5‑205268 | |||
S5‑205269 | Rel-16 CR 28.532 Extend object creation method with id selection by the MnS producer (REST SS, OpenAPI definition) | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑205270 | Rel-16 CR TS28.535 Corrections to clause 4.1 and 4.2.1 | NEC Europe Ltd; Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑205350 | CR Rel-16 28.530 Correction of missing Figure 4.1.7.1 Examples of network slice as NOP internals | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑205351 | add containment relationship for network slice IOC | Nokia | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑205352 | add containment relationship for network slice IOC stage 3 | Nokia | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑205353 | R17 CR TS 28.541 add subclause reference of MRO related attribute | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
6.4 | Rel-17 Operations, Administration, Maintenance and Provisioning (OAM&P) |   | ||||||||||
6.4.1 | Management of non-public networks | S5‑205201 | pCR 28.557 Add use case of NPN provisioning by network slice of PLMN | Huawei, Telefónica S.A. | pCR | Approval | Yes |
Yes
| revised | No | S5‑205400 | |
S5‑205400 | pCR 28.557 Add use case of NPN provisioning by network slice of PLMN | Huawei, Telefónica S.A. | pCR | Approval | Yes |
Yes
| approved | No | S5‑205201 | |||
S5‑205202 | pCR 28.557 Add generic requirements for management of NPN | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑205401 | |||
S5‑205401 | pCR 28.557 Add generic requirements for management of NPN | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑205202 | |||
S5‑205203 | pCR 28.557 Add generic management aspects | Huawei, Telefónica S.A. | pCR | Approval | Yes |
Yes
| revised | No | S5‑205402 | |||
S5‑205402 | pCR 28.557 Add generic management aspects | Huawei, Telefónica S.A. | pCR | Approval | Yes |
Yes
| approved | No | S5‑205203 | |||
S5‑205233 | pCR 28.557 Add use case on SNPN provisioning | TELEFONICA S.A. | pCR | Approval | Yes |
Yes
| revised | No | S5‑205403 | |||
S5‑205403 | pCR 28.557 Add use case on SNPN provisioning | TELEFONICA S.A. | pCR | Approval | Yes |
Yes
| approved | No | S5‑205233 | |||
S5‑205272 | Draft TR 28.557 | Huawei | draft TR | Approval | Yes |
Yes
| approved | No | ||||
6.4.2 | Enhancement on Management Aspects of 5G Service-Level Agreement | S5‑205038 | CR Rel-17 28.541 GST Configuration | Samsung Research America | CR | Approval | Yes |
Yes
| not pursued | No | ||
S5‑205295 | Input to draftCR Rel-17 28.541 GST Configuration | Samsung Research America | other | Approval | Yes |
Yes
| approved | No | ||||
S5‑205039 | CR Rel-17 28.541 ServiceProfle to SliceProfile Translation | Samsung, China Mobile, Telefonica, Huawei | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑205292 | Input draftCR Rel-17 28.541 ServiceProfle to SliceProfile Translation | Samsung, China Mobile, Telefonica, Huawei | other | Approval | Yes |
Yesmerge of 205039, 205205 and 205236
| approved | No | ||||
S5‑205197 | Add requirements of SLA management | China Mobile Com. Corporation | CR | Yes |
Yes
| not pursued | No | |||||
S5‑205320 | Input draftCR Add requirements of SLA management | China Mobile Com. Corporation | other | - | No |
Yes
| approved | No | ||||
S5‑205204 | NRM modelling of SliceProfile | Huawei | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑205205 | Rel-17 CR 28.541 NRM modelling of SliceProfile for RAN domain | Huawei | CR | Approval | Yes |
YesContent is merged in the draft CR S5-205283.
| not pursued | No | ||||
S5‑205206 | Living document of review of GSMA GST SA5#133e | Huawei, China Mobile | other | Approval | Yes |
Yes
| revised | No | S5‑205297 | |||
S5‑205297 | Living document of review of GSMA GST SA5#133e | Huawei, China Mobile | other | Approval | Yes |
Yes
| endorsed | No | S5‑205206 | |||
S5‑205207 | Rel-17 CR 28.541 Add positioning support in ServiceProfile | Huawei, China Mobile | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑205293 | Rel-17 Input to DraftCR 28.541 Add positioning support in ServiceProfile | Huawei, China Mobile | other | Approval | Yes |
Yes
| approved | No | ||||
S5‑205208 | Rel-17 CR 28.541 Add synchronicity support in ServiceProfile | Huawei, China Mobile | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑205294 | Rel-17 Input to draftCR 28.541 Add synchronicity support in ServiceProfile | Huawei, China Mobile | other | Approval | Yes |
Yes
| approved | No | ||||
S5‑205234 | Discussion on updating slice profile according to different network slice subnets | China Mobile Com. Corporation | discussion | Endorsement | Yes |
Yes
| endorsed | No | ||||
S5‑205236 | Update sliceProfile considering different domains | China Mobile Com. Corporation | CR | Agreement | Yes |
YesContent merged in S5-205283
| not pursued | No | ||||
S5‑205248 | TD clarify concept of service level specification | Nokia, Nokia Shanghai Bell | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑205287 | |||
S5‑205287 | TD clarify concept of service level specification | Nokia, Nokia Shanghai Bell | discussion | Endorsement | Yes |
Yes
| endorsed | No | S5‑205248 | |||
S5‑205254 | decouple communication service and network slice | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑205288 | |||
S5‑205288 | decouple communication service and network slice | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑205254 | |||
S5‑205255 | move service profile definition from 28531 | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑205289 | |||
S5‑205289 | move service profile definition from 28531 | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑205255 | |||
S5‑205256 | move service profile definition to 28530 | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑205290 | |||
S5‑205290 | move service profile definition to 28530 | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑205256 | |||
S5‑205257 | fix description related to service profile | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑205291 | |||
S5‑205291 | fix description related to service profile | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑205257 | |||
S5‑205277 | DraftCR for 6.4.2 EMA5SLA - TS 28.540 | China Mobile | draftCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑205278 | DraftCR for 6.4.2 EMA5SLA - TS 28.541 | China Mobile | draftCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑205283 | Rel-17 Input to draftCR 28.541 ServiceProfile to SliceProfile Translation Stage 3 | Samsung Research America | other | discussion | Yes |
Yes
| approved | No | ||||
6.4.3 | Management of MDT enhancement in 5G | S5‑205046 | Add new MDT requirements for E-UTRAN | Ericsson LM | CR | Agreement | Yes |
Yes
| not pursued | No | ||
S5‑205302 | Input to DraftCR Add new MDT requirements for E-UTRAN | Ericsson LM | response | Agreement | Yes |
Yes
| approved | No | ||||
S5‑205093 | Add additional information for MDT specific parameters in NR aligning with RAN TSs | Ericsson LM | CR | Agreement | Yes |
Yes
| revised | No | S5‑205298 | |||
S5‑205298 | Add additional information for MDT specific parameters in NR aligning with RAN TSs | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | S5‑205093 | |||
S5‑205097 | Rel-17 Add additional information for MDT specific parameters in NR aligning with RAN TSs | Ericsson LM | CR | Agreement | Yes |
Yes
| revised | No | S5‑205299 | |||
S5‑205299 | Rel-17 Add additional information for MDT specific parameters in NR aligning with RAN TSs | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | S5‑205097 | |||
S5‑205098 | Add new MDT specific parameter collection period for NR aligning with 32.422 | Ericsson LM | CR | Agreement | Yes |
Yes
| revised | No | S5‑205300 | |||
S5‑205300 | Add new MDT specific parameter collection period for NR aligning with 32.422 | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | S5‑205098 | |||
S5‑205099 | Add new MDT specific parameter collection period for NR aligning with 28.622 for stage 3 | Ericsson LM | CR | Agreement | Yes |
Yes
| revised | No | S5‑205301 | |||
S5‑205301 | Add new MDT specific parameter collection period for NR aligning with 28.622 for stage 3 | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | S5‑205099 | |||
S5‑205279 | DraftCR for 6.4.3 e_5GMDT - TS 32.441 | Ericsson | draftCR | Approval | Yes |
Yes
| approved | No | ||||
6.4.4 | Additional NRM features | S5‑205050 | Rel-17 CR 28.541 Add attributes of NRM IOC for NRF | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||
S5‑205051 | Rel-17 CR 28.541 Add stage 3 NRM IOC for NRF | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑205107 | Discuss on NR NRM update to support MOCN network sharing scenario | Huawei, China Telecom, CATT, China Unicom | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑205304 | S5‑204151 | ||
S5‑205304 | Discuss on NR NRM update to support MOCN network sharing scenario | Huawei, China Telecom, CATT, China Unicom | discussion | Endorsement | Yes |
Yes
| endorsed | No | S5‑205107 | |||
S5‑205108 | Rel-17 CR TS 28.541 Update NR NRM to support MOCN network sharing scenario | Huawei,China Telecom,CATT,China Unicom | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑204153 | |||
S5‑205145 | Discussion on enhancement of NRM to support network sharing | ZTE Wistron Telecom AB | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑205146 | Rel-17 CR TS 28.541 Add NRPhysicalCellDU NRM to support network sharing | ZTE Wistron Telecom AB | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑205237 | Proposal for NR NRM update to support MOCN network sharing | Ericsson LM | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑205239 | Update NR NRM to support MOCN network sharing scenario | Ericsson LM | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑205280 | DraftCR for 6.4.4 adNRM - TS 28.541 | Nokia | draftCR | Approval | No |
Yes
| withdrawn | Yes | ||||
6.4.5 | Enhancement of QoE Measurement Collection | S5‑205217 | Adding Signalling Based Activation | Ericsson LM | CR | Yes |
Yes
| not pursued | No | |||
S5‑205305 | Input to draft CR Adding Signalling Based Activation | Ericsson LM | other | - | Yes |
Yes
| approved | No | ||||
S5‑205281 | DraftCR for 6.4.5 eQoE - TS 28.404 | Ericsson | draftCR | Approval | Yes |
Yes
| approved | No | ||||
6.4.6 | Enhancements of 5G performance measurements and KPIs | S5‑205044 | Add to A.28 new part related to interruption time interval for 5QI 1 QoS Flow released due to double NG (double UE context) monitoring. | Nokia Solutions & Networks (I) | CR | Approval | Yes |
Yes
| revised | No | S5‑205309 | |
S5‑205309 | Add to A.28 new part related to interruption time interval for 5QI 1 QoS Flow released due to double NG (double UE context) monitoring. | Nokia Solutions & Networks (I) | CR | Approval | Yes |
Yes
| agreed | No | S5‑205044 | |||
S5‑205116 | Rel-17 CR 28.552 Add measurements on AF traffic influence | Intel Sweden AB | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑205310 | Input to draft CR 28.552 Add measurements on AF traffic influence | Intel Sweden AB | other | Agreement | Yes |
Yes
| approved | No | ||||
S5‑205117 | Rel-17 CR 28.552 Add measurements on external parameter provisioning | Intel Sweden AB | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑205311 | Input to draft CR 28.552 Add measurements on external parameter provisioning | Intel Sweden AB | other | Agreement | Yes |
Yes
| approved | No | ||||
S5‑205118 | Rel-17 CR 28.552 Add measurements on NIDD configuration | Intel Sweden AB | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑205306 | Rel-17 input to draftCR 28.552 Add measurements on NIDD configuration | Intel Sweden AB | other | Agreement | Yes |
Yes
| approved | No | ||||
S5‑205119 | Rel-17 CR 28.552 Add measurements on NIDD service | Intel Sweden AB | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑205307 | Input to draft CR 28.552 Add measurements on NIDD service | Intel Sweden AB | other | Agreement | Yes |
Yes
| approved | No | ||||
S5‑205147 | R17 CR TS28.552 Add Intra and Inter-frequency Handover related measurements | ZTE Wistron Telecom AB | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑205308 | Input to draft CR TS28.552 Add Intra and Inter-frequency Handover related measurements | ZTE Wistron Telecom AB | other | Agreement | Yes |
Yes
| approved | No | ||||
S5‑205148 | R17 CR TS28.552 Add handover triggering measurements | ZTE Wistron Telecom AB | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑205282 | DraftCR for 6.4.6 ePM_KPI_5G - TS 28.552 | Intel | draftCR | Approval | Yes |
Yes
| approved | No | ||||
6.4.7 | Management of the enhanced tenant concept | S5‑205249 | TD tenant information to support multi-tenancy for network slice management | Nokia, Nokia Shanghai Bell | discussion | Endorsement | Yes |
Yes
| noted | No | ||
S5‑205250 | refine tenant information concept | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑205312 | |||
S5‑205312 | refine tenant information concept | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑205250 | |||
6.4.8 | Management data collection control and discovery | S5‑205196 | TD Issues in data collection and discovery | Nokia, Nokia Shanghai Bell | discussion | Agreement | Yes |
Yes
| noted | No | ||
S5‑205210 | Rel-17 Draft CR 28.622 Add PerfMetricStore | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑205212 | Rel-17 Draft CR 28.622 Add profiles for Trace/MDT control | Nokia, Nokia Shanghai Bell | other | Approval | Yes |
Yes
| noted | No | ||||
6.5 | OAM&P Studies |   | ||||||||||
6.5.1 | Study on management and orchestration aspects with integrated satellite components in a 5G network | S5‑205149 | Revise the multi-RAT load-balancing use case associated with satellite and terrestrial RANs | ETRI | pCR | Approval | Yes |
Yes
| approved | No | ||
S5‑205150 | Add a solution for multi-RAT load-balancing associated with satellite and terrestrial RANs | ETRI | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑205214 | pCR 28.808 Add a solution to create and manage a network slice associated with satellite components | TNO | pCR | Approval | Yes |
Yes
| revised | No | S5‑205315 | |||
S5‑205315 | pCR 28.808 Add a solution to create and manage a network slice associated with satellite components | TNO | pCR | Approval | Yes |
Yes
| approved | No | S5‑205214 | |||
S5‑205215 | pCR 28.808 Add a solution to manage transparent and regenerative satellite components | TNO | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑205216 | pCR 28.808 Add conclusions and recommendations | TNO | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑205273 | Draft TR 28.808 | TNO | draft TR | Approval | Yes |
Yes
| approved | No | ||||
6.5.2 | Study on new aspects of EE for 5G networks | S5‑205109 | LS on energySaving state information exposure | China Telecom Corporation Ltd. | LS out | Agreement | Yes |
Yes
| revised | No | S5‑205318 | |
S5‑205318 | LS on energySaving state information exposure | China Telecom Corporation Ltd. | LS out | Agreement | Yes |
Yes
| approved | No | S5‑205109 | |||
S5‑205112 | Solutions on EE KPI for 5GC | China Telecom Corporation Ltd. | pCR | Approval | Yes |
Yes
| revised | No | S5‑205317 | |||
S5‑205317 | Solutions on EE KPI for 5GC | China Telecom Corporation Ltd. | pCR | Approval | Yes |
Yes
| approved | No | S5‑205112 | |||
S5‑205144 | Discussion paper on energySaving state information exposure | China Telecom Corporation Ltd. | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑205319 | |||
S5‑205319 | Discussion paper on energySaving state information exposure | China Telecom Corporation Ltd. | discussion | Endorsement | Yes |
Yes
| approved | No | S5‑205144 | |||
S5‑205209 | pCR 28.813 Key Issue EE KPI for network slice types - Potential solution #3 enhancement | Huawei, Orange | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑205211 | pCR 28.813 Add Key Issue Service-oriented energy saving strategy | China Mobile Com. Corporation | pCR | Yes |
Yes
| noted | No | |||||
S5‑205221 | pCR TR 28.813 EE KPI in case of RAN sharing – Potential solution No. 2 | Orange, AT&T, Deutsche Telekom, Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑205223 | pCR TR 28.813 EE KPI for 5GC – Further analysis of N3 based potential solution | Orange, AT&T, Deutsche Telekom | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑205224 | pCR TR 28.813 EE KPI for 5GC – Further analysis of the N6 based potential solution | Orange, AT&T, Deutsche Telekom, Ericsson | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑205226 | pCR TR 28.813 Network Function energy consumption estimation – detailed potential solution | Orange | pCR | Approval | Yes |
Yes
| revised | No | S5‑205316 | |||
S5‑205316 | pCR TR 28.813 Network Function energy consumption estimation – detailed potential solution | Orange | pCR | Approval | Yes |
Yes
| approved | No | S5‑205226 | |||
S5‑205227 | pCR TR 28.813 New Key Issue: Network Slice Energy Consumption | Orange, Deutsche Telekom, Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑205274 | draft TR 28.813 | ORANGE | draft TR | Approval | Yes |
Yes
| approved | No | ||||
6.5.3 | Study on management aspects of edge computing | S5‑205035 | pCR 28.814 Solution for EAS deployment | Samsung Research America | pCR | Approval | Yes |
Yes
| revised | No | S5‑205285 | |
S5‑205285 | pCR 28.814 Solution for EAS deployment | Samsung Research America | pCR | Approval | Yes |
Yes
| approved | No | S5‑205035 | |||
S5‑205036 | pCR 28.814 Use Case of Edge Performance Assurance | Samsung Research America | pCR | Approval | Yes |
Yes
| revised | No | S5‑205322 | |||
S5‑205322 | pCR 28.814 Use Case of Edge Performance Assurance | Samsung Research America | pCR | Approval | Yes |
Yes
| approved | No | S5‑205036 | |||
S5‑205037 | pCR 28.814 Solution for Edge Performance Assurance | Samsung Research America | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑205052 | pCR 28.814 support of MEC for EAS LCM management | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑205132 | pCR 28.814 edge computing deployment scenarios | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑205133 | pCR 28.814 use case of EAS configuration | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑205284 | |||
S5‑205284 | pCR 28.814 use case of EAS configuration | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| approved | No | S5‑205133 | |||
S5‑205134 | pCR 28.814 solution for EAS lifecycle management | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑205286 | |||
S5‑205286 | pCR 28.814 solution for EAS lifecycle management | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| approved | No | S5‑205134 | |||
S5‑205135 | pCR 28.814 add solutions for ECSP and PLMN deployment | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑205192 | Update the solution of Jitter analysis | China Mobile Com. Corporation | pCR | Yes |
Yes
| withdrawn | Yes | |||||
S5‑205275 | Draft TR 28.814 | Intel | draft TR | Agreement | Yes |
Yes
| approved | No | ||||
S5‑205321 | LS to SA6 on the relation between EDGEAPP and ETSI MEC architectures | Huawei | LS out | Approval | Yes |
Yes
| approved | No | ||||
7 | Charging |   | ||||||||||
7.1 | Charging Plenary | S5‑205008 | CH agenda and time plan | WG vice Chair (Nokia) | agenda | Yes |
Yes
| revised | No | S5‑205478 | ||
S5‑205478 | CH agenda and time plan | WG vice Chair (Nokia) | agenda | - | Yes |
Yes
| noted | No | S5‑205008 | |||
S5‑205009 | Charging exec report | WG vice Chair (Nokia) | report | Yes |
Yes
| noted | No | |||||
S5‑205012 | LS ccSA5 on support of stateless NFs | C3-204386 | LS in | Yes |
Yes
| noted | No | |||||
S5‑205014 | Resubmitted LS Out to SA2 and SA5 on making PSCELL ID available at the SGW of EPC | ETSI TC LI | LS in | Yes |
Yes
| noted | No | |||||
S5‑205121 | 3GPP Forge process for CH SWG | Nokia, Nokia Shanghai Bell | discussion | Discussion | Yes |
Yes
| noted | No | ||||
7.2 | New Charging Work Item proposals | S5‑205100 | New SID on Charging Aspects for Network Slicing Phase 2 | Matrixx | SID new | Approval | Yes |
Yes
| noted | No | ||
7.3 | Charging Maintenance and Rel-16 small Enhancements | S5‑205025 | Add Area of service as the NS Performance and analytics charging attribute | China Telecomunication Corp. | CR | Approval | Yes |
Yes
| not pursued | No | ||
S5‑205026 | Add Abbreviations NSM and remove Subscriber Identifier in CHF record data | China Telecomunication Corp. | CR | Approval | Yes |
Yes
| revised | No | S5‑205433 | |||
S5‑205433 | Add Abbreviations NSM and remove Subscriber Identifier in CHF record data | China Telecomunication Corp. | CR | Approval | Yes |
Yes
| agreed | No | S5‑205026 | |||
S5‑205027 | Correction of the Category and Operation Types | China Telecomunication Corp. | CR | Approval | Yes |
Yes
| revised | No | S5‑205434 | |||
S5‑205434 | Correction of the Category and Operation Types | China Telecomunication Corp. | CR | Approval | Yes |
Yes
| agreed | No | S5‑205027 | |||
S5‑205028 | Correction of the stye of all table index from hyphen to dot | China Telecomunication Corp. | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑205029 | Change the Category of Invocation Sequence Number and Remove Subscriber Identifier from CHF record data | China Telecomunication Corp. | CR | Approval | Yes |
Yes
| revised | No | S5‑205435 | |||
S5‑205435 | Change the Category of Invocation Sequence Number and Remove Subscriber Identifier from CHF record data | China Telecomunication Corp. | CR | Approval | Yes |
Yes
| agreed | No | S5‑205029 | |||
S5‑205031 | Rel-16 CR 32.255 Correction of Charing Id in roaming HR scenario upon V-SMF change | China Mobile Com. Corporation | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑205032 | Rel-15 CR 32.291 Correction of TriggerType | China Mobile Com. Corporation | CR | Approval | Yes |
Yes
| revised | No | S5‑205428 | |||
S5‑205428 | Rel-15 CR 32.291 Correction of TriggerType | China Mobile Com. Corporation | CR | Approval | Yes |
Yes
| agreed | No | S5‑205032 | |||
S5‑205033 | Rel-16 CR 32.291 Correction of TriggerType | China Mobile Com. Corporation | CR | Approval | Yes |
Yes
| revised | No | S5‑205429 | |||
S5‑205429 | Rel-16 CR 32.291 Correction of TriggerType | China Mobile Com. Corporation | CR | Approval | Yes |
Yes
| agreed | No | S5‑205033 | |||
S5‑205034 | LS on Network Slice PA Charging per maximum utilized bandwidth | China Mobile Com. Corporation | LS out | Approval | Yes |
Yes
| revised | No | S5‑205436 | |||
S5‑205436 | LS on Network Slice PA Charging per maximum utilized bandwidth | China Mobile Com. Corporation | LS out | Approval | Yes |
Yes
| agreed | No | S5‑205034 | |||
S5‑205040 | Rel-16 CR 28.201 Update description of Charging Enablement Function | China Mobile | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑205041 | Rel-16 CR 28.201 Correction on Subscriber Identifier in Charging Data Request message | China Mobile | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑205042 | Rel-16 CR 28.201 Correction on sender of Charging Data Response message | China Mobile | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑205043 | Rel-16 CR 28.201 Correction on NSPA Container Information in Charging Data Request message | China Mobile | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑205064 | Rel-16 CR 32.255 Add multi-homed PDU address in CDR for IPv6 multi-homing | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑205437 | |||
S5‑205437 | Rel-16 CR 32.255 Add multi-homed PDU address in CDR for IPv6 multi-homing | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑205064 | |||
S5‑205065 | Rel-16 CR 32.291 Add multi-homed PDU address for IPv6 multi-homing | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑205066 | Rel-16 CR 32.298 Add multi-homed PDU address for IPv6 multi-homing | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑205438 | |||
S5‑205438 | Rel-16 CR 32.298 Add multi-homed PDU address for IPv6 multi-homing | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑205066 | |||
S5‑205067 | Rel-16 CR TS 32.290 Add SCP interaction | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑205068 | Rel-15 CR TS 32.291 Change map data type for presence area information | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑205069 | Rel-16 CR TS 32.291 Change map data type for presence area information | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑205073 | Discussion paper on Charging Control based on QNC | Huawei | discussion | Discussion | Yes |
Yes
| noted | No | ||||
S5‑205074 | Rel-16 CR 32.255 Add QNC subscription | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑205439 | |||
S5‑205439 | Rel-16 CR 32.255 Add QNC subscription | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑205074 | |||
S5‑205075 | Rel-16 CR 32.291 Add QNC subscription | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑205440 | |||
S5‑205440 | Rel-16 CR 32.291 Add QNC subscription | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑205075 | |||
S5‑205076 | Rel-16 CR 32.255 Support the QoS assurance | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑205077 | Rel-16 CR 32.291 Support the QoS assurance | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑205078 | Rel-16 CR 32.255 Add the enhanced Diagnostics for 5G Charging | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑205441 | |||
S5‑205441 | Rel-16 CR 32.255 Add the enhanced Diagnostics for 5G Charging | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑205078 | |||
S5‑205079 | Rel-16 CR 32.291 Add the enhanced Diagnostics for 5G Charging | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑205442 | |||
S5‑205442 | Rel-16 CR 32.291 Add the enhanced Diagnostics for 5G Charging | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑205480 | S5‑205079 | ||
S5‑205480 | Rel-16 CR 32.291 Add the enhanced Diagnostics for 5G Charging | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑205442 | |||
S5‑205080 | Rel-16 CR 32.298 Add the enhanced Diagnostics for 5G Charging | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑205443 | |||
S5‑205443 | Rel-16 CR 32.298 Add the enhanced Diagnostics for 5G Charging | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑205080 | |||
S5‑205081 | Rel-16 CR 32.291 Correct the InvocationSequenceNumber | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑205444 | |||
S5‑205444 | Rel-16 CR 32.291 Correct the InvocationSequenceNumber | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑205081 | |||
S5‑205082 | Rel-16 CR 32.290 Fialue handing for InvocationSequemceNumber | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑205445 | |||
S5‑205445 | Rel-16 CR 32.290 Fialue handing for InvocationSequemceNumber | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑205082 | |||
S5‑205086 | Discussion paper on Non-blocking Mode | Huawei | discussion | Discussion | Yes |
Yes
| noted | No | ||||
S5‑205087 | Rel-16 CR 32.291 Add the charging control for non-blocking charging | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑205088 | Rel-16 CR 32.290 Add the charging control for non-blocking charging | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑205089 | Rel-16 CR 32.291 Correct the Bindings for 5G data connectivity | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑205090 | Rel-16 CR 32.298 Correct the NSPA Charging Information | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑205446 | |||
S5‑205446 | Rel-16 CR 32.298 Correct the NSPA Charging Information | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑205479 | S5‑205090 | ||
S5‑205479 | Rel-16 CR 32.298 Correct the NSPA Charging Information | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑205446 | |||
S5‑205091 | Rel-16 CR 32.291 Correct the Open API | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑205447 | |||
S5‑205447 | Rel-16 CR 32.291 Correct the Open API | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑205091 | |||
S5‑205122 | Rel-16 CR 32.274 Correction on Triggers field for converged charging | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑205123 | Rel-16 CR 32.290 Correction on missing NEF and PGW-C+SMF as NF consumers | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑205124 | Rel-16 CR 32.291 Correction on missing NEF and PGW-C+SMF as NF consumers | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑205448 | |||
S5‑205448 | Rel-16 CR 32.291 Correction on missing NEF and PGW-C+SMF as NF consumers | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑205124 | |||
S5‑205125 | Rel-16 CR 32.298 Correction on missing NEF and PGW-C+SMF as NF consumers | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑205126 | Rel-16 CR 32.291 Correction on imported data type references | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑205449 | |||
S5‑205449 | Rel-16 CR 32.291 Correction on imported data type references | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑205126 | |||
S5‑205127 | Rel-16 CR 32.298 Correction on User Equipment Info field format | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑205128 | Rel-16 CR 32.298 Correction on User Identifier field format | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑205460 | |||
S5‑205460 | Rel-16 CR 32.298 Correction on User Identifier field format | Nokia, Nokia Shanghai Bell, Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑205128 | |||
S5‑205159 | Rel-16 CR 32.290 Correcting trigger of usage reporting | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑205432 | |||
S5‑205432 | Rel-16 CR 32.290 Correcting trigger of usage reporting | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑205159 | |||
S5‑205160 | Rel-15 CR 32.298 Correction of SMS node address in CHF CDR | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑205450 | |||
S5‑205450 | Rel-15 CR 32.298 Correction of SMS node address in CHF CDR | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑205160 | |||
S5‑205161 | Rel-16 CR 32.298 Correction of SMS node address in CHF CDR | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑205451 | |||
S5‑205451 | Rel-16 CR 32.298 Correction of SMS node address in CHF CDR | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑205161 | |||
S5‑205162 | Rel-15 CR 32.298 Correction of mandatory SMS message reference in CHF CDR | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑205452 | |||
S5‑205452 | Rel-15 CR 32.298 Correction of mandatory SMS message reference in CHF CDR | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑205162 | |||
S5‑205163 | Rel-16 CR 32.298 Correction of mandatory SMS message reference in CHF CDR | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑205453 | |||
S5‑205453 | Rel-16 CR 32.298 Correction of mandatory SMS message reference in CHF CDR | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑205163 | |||
S5‑205164 | Rel-16 CR 32.298 Correction of SMS message class in CHF CDR | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑205165 | Rel-16 CR 32.274 Correction of roamer in out from SMSF | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑205166 | Rel-15 CR 32.298 Correction of SMS originator and recipient info in CHF CDR | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑205454 | |||
S5‑205454 | Rel-15 CR 32.298 Correction of SMS originator and recipient info in CHF CDR | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑205166 | |||
S5‑205167 | Rel-16 CR 32.298 Correction of SMS originator and recipient info in CHF CDR | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑205455 | |||
S5‑205455 | Rel-16 CR 32.298 Correction of SMS originator and recipient info in CHF CDR | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑205167 | |||
S5‑205168 | Rel-16 CR 32.274 Correction of flows for IEC, ECUR and PEC | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑205458 | |||
S5‑205458 | Rel-16 CR 32.274 Correction of flows for IEC, ECUR and PEC | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑205168 | |||
S5‑205169 | Rel-15 CR 32.290 Correcting duplicate detection using charging id | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑205472 | |||
S5‑205472 | Rel-15 CR 32.290 Correcting duplicate detection using charging id | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑205169 | |||
S5‑205170 | Rel-16 CR 32.290 Correcting duplicate detection using charging id | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑205473 | |||
S5‑205473 | Rel-16 CR 32.290 Correcting duplicate detection using charging id | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑205170 | |||
S5‑205171 | Rel-15 CR 32.291 Correcting charging id availability for all NF | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑205172 | Rel-16 CR 32.291 Correcting charging id availability for all NF | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑205475 | |||
S5‑205475 | Rel-16 CR 32.291 Correcting charging id availability for all NF | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑205172 | |||
S5‑205173 | Rel-15 CR 32.298 Correcting charging id availability for all NF in CHF CDR | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑205476 | |||
S5‑205476 | Rel-15 CR 32.298 Correcting charging id availability for all NF in CHF CDR | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑205173 | |||
S5‑205174 | Rel-16 CR 32.298 Correcting charging id availability for all NF in CHF CDR | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑205477 | |||
S5‑205477 | Rel-16 CR 32.298 Correcting charging id availability for all NF in CHF CDR | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑205174 | |||
S5‑205175 | Rel-15 CR 32.298 Correcting triggers as optional in CHF CDR | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑205430 | |||
S5‑205430 | Rel-15 CR 32.298 Correcting triggers as optional in CHF CDR | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑205175 | |||
S5‑205176 | Rel-16 CR 32.298 Correcting triggers as optional in CHF CDR | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑205431 | |||
S5‑205431 | Rel-16 CR 32.298 Correcting triggers as optional in CHF CDR | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑205176 | |||
S5‑205177 | Rel-15 CR 32.291 Correcting SMS message types | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑205456 | |||
S5‑205456 | Rel-15 CR 32.291 Correcting SMS message types | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑205177 | |||
S5‑205178 | Rel-16 CR 32.291 Correcting SMS message types | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑205457 | |||
S5‑205457 | Rel-16 CR 32.291 Correcting SMS message types | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑205178 | |||
S5‑205179 | Rel-16 CR 32.291 Correcting binding of event time stamp in SMS | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑205180 | Rel-16 CR 32.255 Correcting UPF addition trigger | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑205459 | |||
S5‑205459 | Rel-16 CR 32.255 Correcting UPF addition trigger | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑205180 | |||
S5‑205181 | Rel-16 CR 32.298 Correcting involved party definition in CHF CDR | Ericsson | CR | Agreement | Yes |
Yes
| merged | No | S5‑205460 | |||
S5‑205185 | Discussion on reference points | Ericsson | discussion | Discussion | Yes |
Yes
| noted | No | ||||
S5‑205186 | Discussion on API organization | Ericsson | discussion | Discussion | Yes |
Yes
| noted | No | ||||
S5‑205213 | Rel-16 CR 32.290 Correction on quota managed scenario | Matrixx | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑205422 | Rel-16 CR 32.291 Correction of roamer in out from SMSF | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑205423 | Rel-16 CR 32.298 Correction of roamer in out from SMSF | Ericsson | CR | discussion | Yes |
Yes
| agreed | No | ||||
7.4 | Rel-17 Charging |   | ||||||||||
7.4.1 | IMS Charging in 5G System Architecture | S5‑205182 | Rel-17 CR 32.260 Update of IMS nodes supporting Nchf | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑205424 | |
S5‑205424 | Rel-17 CR 32.260 Update of IMS nodes supporting Nchf | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑205182 | |||
S5‑205183 | Rel-17 CR 32.260 Adding data description for IMS converged charging | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑205425 | |||
S5‑205425 | Rel-17 CR 32.260 Adding data description for IMS converged charging | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑205183 | |||
S5‑205184 | Rel-17 CR 32.260 Definition of the IMS converged charging information | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
7.4.2 | Charging enhancement for URLLC | S5‑205083 | Rel-16 CR 32.255 Add URLLC Charging Architecture | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||
S5‑205084 | Rel-16 CR 32.255 Add URLLC Charging Requirement | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑205426 | |||
S5‑205426 | Rel-17 CR 32.255 Add URLLC Charging Requirement | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑205084 | |||
S5‑205085 | Rel-17 CR 32.255 Add Highly reliable URLLC services Charging | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑205427 | |||
S5‑205427 | Rel-17 CR 32.255 Add Highly reliable URLLC services Charging | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑205085 | |||
7.4.3 | N40 Interface Enhancements to Support GERAN and UTRAN |   | ||||||||||
7.5 | Charging studies |   | ||||||||||
7.5.1 | Study on charging aspects of Edge Computing | S5‑205113 | pCR 28.815 Add overview for EC charging | Intel Sweden AB | pCR | Approval | Yes |
Yes
| revised | No | S5‑205461 | |
S5‑205461 | pCR 28.815 Add overview for EC charging | Intel Sweden AB | pCR | Approval | Yes |
Yes
| approved | No | S5‑205113 | |||
S5‑205114 | pCR 28.815 Add architecture considerations on charging aspects of edge computing | Intel Sweden AB | pCR | Approval | Yes |
Yes
| revised | No | S5‑205462 | |||
S5‑205462 | pCR 28.815 Add architecture considerations on charging aspects of edge computing | Intel Sweden AB | pCR | Approval | Yes |
Yes
| approved | No | S5‑205114 | |||
S5‑205115 | pCR 28.815 Add charging scenarios and key issues on 5GS charging for edge computing | Intel Sweden AB | pCR | Approval | Yes |
Yes
| revised | No | S5‑205463 | |||
S5‑205463 | pCR 28.815 Add charging scenarios and key issues on 5GS charging for edge computing | Intel Sweden AB | pCR | Approval | Yes |
Yes
| approved | No | S5‑205115 | |||
S5‑205464 | Draft TR 28.815 | Intel | draft TR | Approval | Yes |
Yes
| approved | No | ||||
7.5.2 | Study on charging aspects of 5GS CIoT | S5‑205030 | Add initial skeleton | Huawei Tech.(UK) Co., Ltd | draft TR | Approval | Yes |
Yes
| approved | No | ||
S5‑205070 | pCR 28.816 Add scope | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑205465 | |||
S5‑205465 | pCR 28.816 Add scope | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑205070 | |||
S5‑205071 | pCR 28.816 Add introduction | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑205466 | |||
S5‑205466 | pCR 28.816 Add introduction | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑205071 | |||
S5‑205072 | pCR 28.816 Add data connectivity scenario | Huawei | pCR | Agreement | No |
Yes
| withdrawn | Yes | ||||
S5‑205229 | pCR 28.816 Add proposal for skeleton for TR 28.816 | Huawei | pCR | Yes |
Yes
| approved | No | |||||
S5‑205467 | Draft TR 28.816 | Huawei | draft TR | Approval | Yes |
Yes
| approved | No | ||||
7.5.3 | Study on charging aspects of Proximity-based Services in 5GC | S5‑205120 | draft TS 32846-000 | CATT | draft TR | No |
Yes
| withdrawn | Yes | |||
S5‑205219 | Revised SID on charging aspects of Proximity-based Services in 5GC | CATT | SID revised | Approval | Yes |
Yes
| revised | No | S5‑205468 | |||
S5‑205468 | Revised SID on charging aspects of Proximity-based Services in 5GC | CATT | SID revised | Approval | Yes |
Yes
| agreed | No | S5‑205219 | |||
S5‑205220 | pCR Add skeleton to draft TR 32.846 | CATT | pCR | Approval | Yes |
Yes
| revised | No | S5‑205469 | |||
S5‑205469 | pCR Add skeleton to draft TR 32.846 | CATT | pCR | Approval | Yes |
Yes
| approved | No | S5‑205220 | |||
S5‑205222 | pCR 32.846 Add scope and reference | CATT | pCR | Approval | Yes |
Yes
| revised | No | S5‑205470 | |||
S5‑205470 | pCR 32.846 Add scope and reference | CATT | pCR | Approval | Yes |
Yes
| approved | No | S5‑205222 | |||
S5‑205471 | Draft TR 32.846 | CATT | draft TR | Approval | Yes |
Yes
| approved | No | ||||
8 | Any Other Business |   | ||||||||||
9 | Closing of the meeting |   |