Tdoc List
2021-03-17 15:19
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‑212000 | 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‑212001 | 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‑212002 | e-meeting process | WG Chair | discussion | Yes |
Yes
| revised | No | S5‑212325 | ||
S5‑212325 | e-meeting process | WG Chair | discussion | - | Yes |
Yes
| noted | No | S5‑212002 | |||
S5‑212003 | Post e-meeting email approval status | WG Chair | other | Yes |
No
| available | No | |||||
S5‑212010 | SA5 working procedures | WG Chair | other | Yes |
Yes
| noted | No | |||||
S5‑212011 | Process for management of draft TS-TRs | WG Chair | other | Yes |
Yes
| noted | No | |||||
5.2 | Technical issues at SA5 level | S5‑212064 | 3GPP SA5 inputs to progressing the Multi SDO Autonomous Network coordination | SA5 Vice chair (Huawei) | other | Information | Yes |
Yes
| noted | No | ||
S5‑212129 | Discussion paper on Use Case template | SA5 Vice chair (Huawei) | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑212326 | |||
S5‑212326 | Discussion paper on Use Case template | SA5 Vice chair (Huawei) | discussion | Endorsement | Yes |
Yes
| noted | No | S5‑212129 | |||
S5‑212235 | Recommended OpenAPI specification file handling and design guidelines | 3GPP TSG CT chair | discussion | Decision | Yes |
Yes
| noted | No | ||||
S5‑212307 | Comparison between TS 32.158 and TS 29.501/21.900 | Nokia | discussion | discussion | Yes |
Yes
| noted | No | ||||
5.3 | Liaison statements at SA5 level | S5‑212015 | Resubmitted LS New Whitepaper: “Operator Platform Telco Edge proposal" | GSMA | LS in | Yes |
Yes
| replied to | No | |||
S5‑212319 | Reply to: Resubmitted LS New Whitepaper: “Operator Platform Telco Edge proposal" | Intel | LS out | approval | Yes |
Yes
| approved | No | ||||
S5‑212026 | Progressing the Multi SDO Autonomous Network coordination | TM Forum | LS in | Yes |
Yes
| replied to | No | |||||
S5‑212029 | LS on NG.116 support of service categories | GSMA 5G Joint-Activity (5GJA) | LS in | Yes |
Yes
| replied to | No | |||||
S5‑212320 | Reply to: LS on NG.116 support of service categories | Ericsson | LS out | approval | Yes |
Yes
| approved | No | ||||
S5‑212309 | LS on Postponement of Multi SDO Autonomous Network strategic coordination meeting | TMF | LS in | discussion | Yes |
Yes
| replied to | No | ||||
S5‑212310 | Reply to: LS on Postponement of Multi SDO Autonomous Network strategic coordination meeting | Huawei | LS out | approval | Yes |
Yes
| approved | No | ||||
S5‑212311 | LS on migration from ETSI forge to 3GPP forge | C4-211513 | LS in | discussion | Yes |
Yes
| noted | No | ||||
S5‑212312 | LS on OpenAPI guidelines | Ericsson | LS out | Approval | Yes |
Yes
| approved | No | ||||
5.4 | SA5 meeting calendar | S5‑212013 | SA5 meeting calendar | WG CHair | other | Yes |
Yes
| noted | No | |||
6 | OAM&P |   | ||||||||||
6.1 | OAM&P Plenary | S5‑212004 | OAM&P action list | WG Vice Chair | other | Yes |
Yes
| noted | No | |||
S5‑212005 | agenda_with_Tdocs_sequence_proposal_OAM | WG Vice Chair | agenda | Yes |
Yes
| noted | No | |||||
S5‑212006 | OAM Exec Report | WG Vice Chair | report | No |
No
| reserved | No | |||||
S5‑212007 | OAM Chair notes and conclusions | WG Chair | report | No |
No
| reserved | No | |||||
S5‑212012 | List of DraftCR input and output | WG Chair | other | No |
Yes
| withdrawn | Yes | |||||
S5‑212014 | Resubmitted LS reply to 3GPP SA5 on the relation between EDGEAPP and ETSI MEC architectures | ETSI ISG MEC | LS in | Yes |
Yes
| noted | No | |||||
S5‑212016 | Resubmitted LS to SA5 on Relation between 3GPP EDGEAPP and ETSI MEC architectures | S6-202355 | LS in | Yes |
Yes
| noted | No | |||||
S5‑212017 | Resubmitted LS on O-RAN – 3GPP Cooperation on Management Services | O-RAN | LS in | Yes |
Yes
| replied to | No | |||||
S5‑212328 | Reply to: Resubmitted LS on O-RAN – 3GPP Cooperation on Management Services | Ericsson | LS out | approval | Yes |
Yes
| approved | No | ||||
S5‑212018 | Resubmitted LS/r on methodology harmonization and REST-based network management framework (reply to 3GPP TSG SA5-S5-204647) | ITU-T SG2 | LS in | Yes |
Yes
| postponed | No | |||||
S5‑212019 | Resubmitted LS/r on work progress on M.resm-AI "Requirements for energy saving management of 5G RAN system with AI" (reply to 3GPP SA5-LS1225) | ITU-T SG2 | LS in | Yes |
Yes
| postponed | No | |||||
S5‑212020 | Liaison reply to 3GPP SA5/SA2 on relation between ENI and MDAF/NWDAF | ETSI ISG ENI | LS in | Yes |
Yes
| noted | No | |||||
S5‑212021 | Reply LS ccSA5 on SA WG2 assumptions from conclusion of study on architecture aspects for using satellite access in 5G | R2-2102498 | LS in | Yes |
Yes
| noted | No | |||||
S5‑212022 | LS reply to SA5 on QoE Measurement Collection | R2-2102500 | LS in | Yes |
Yes
| noted | No | |||||
S5‑212023 | Reply LS to SA5 on MDT Stage 2 and Stage 3 alignment | R3-211140 | LS in | Yes |
Yes
| noted | No | |||||
S5‑212024 | LS to SA5 on the details of logging forms reported by the gNB-CU-CP, gNB-CU-UP and gNB-DU under measurement pollution conditions | R3-211334 | LS in | Yes |
Yes
| postponed | No | |||||
S5‑212025 | Reply LS to SA5 on limitation of Propagation of immediate MDT configuration in case of Xn inter-RAT HO | R3-211335 | LS in | Yes |
Yes
| noted | No | |||||
S5‑212034 | Reply LS on work progress on ITU-T draft Rec. M.resm-AI | Orange | LS out | Agreement | Yes |
Yes
| noted | No | ||||
S5‑212061 | Rel-17 time plan proposal for OAM | SA5 Vice chair (Huawei) | other | Presentation | Yes |
Yes
| revised | No | S5‑212330 | S5‑211081 | ||
S5‑212330 | Rel-17 time plan proposal for OAM | SA5 Vice chair (Huawei) | other | Presentation | Yes |
Yes
| endorsed | No | S5‑212061 | |||
S5‑212062 | List of Approved DraftCR | SA5 Vice chair (Huawei) | other | Information | Yes |
Yes
| noted | No | S5‑211461 | |||
S5‑212063 | Collection of useful endorsed document and external communication documents | Huawei Technologies (Korea) | other | Yes |
Yes
| noted | No | S5‑211088 | ||||
S5‑212131 | Rel-17 CR TS 32.160 Update on template for requirement specifications | Huawei | CR | Yes |
Yes
| revised | No | S5‑212329 | S5‑211078 | |||
S5‑212329 | Rel-17 CR TS 32.160 Update on template for requirement specifications | Huawei | CR | - | Yes |
Yes
| not pursued | No | S5‑212131 | |||
S5‑212274 | Discussion on new WID Plug and Connect | Orange, AT&T, Deutsche Telekom, Telecom Italia, Telefonica S.A., Verizon | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑212308 | Ls to SA5 on Conclusion of NR QoE Management and Optimizations for Diverse Services SI in RAN3 | R3-211234 | LS in | discussion | Yes |
Yes
| noted | No | ||||
S5‑212313 | Mega CR plan | Huawei | discussion | discussion | Yes |
Yes
| noted | No | ||||
6.2 | New OAM&P Work Item proposals | S5‑212033 | New SID on management aspects of network slice management capability exposure | Alibaba Group | SID new | Yes |
Yes
| revised | No | S5‑212368 | S5‑211205 | |
S5‑212368 | New SID on management aspects of network slice management capability exposure | Alibaba Group | SID new | - | Yes |
Yes
| agreed | No | S5‑212033 | |||
S5‑212059 | New WID Enhancements of Management Data Analytics Service | Intel, NEC | WID new | Agreement | Yes |
Yes
| revised | No | S5‑212369 | |||
S5‑212369 | New WID Enhancements of Management Data Analytics Service | Intel, NEC | WID new | Agreement | Yes |
Yes
| agreed | No | S5‑212059 | |||
S5‑212074 | New WID on File Management | Nokia, Nokia Shanghai Bell | WID new | Approval | Yes |
Yes
| revised | No | S5‑212331 | |||
S5‑212331 | New WID on File Management | Nokia, Nokia Shanghai Bell | WID new | Approval | Yes |
Yes
| agreed | No | S5‑212074 | |||
S5‑212132 | New WID on enhancement of service based management architecture | Huawei, China Telecom, China Unicom, China Mobile, Ericsson | WID new | Yes |
Yes
| revised | No | S5‑212332 | S5‑211460 | |||
S5‑212332 | New WID on enhancement of service based management architecture | Huawei, China Telecom, China Unicom, China Mobile, Ericsson | WID new | - | Yes |
Yes
| agreed | No | S5‑212132 | |||
6.3 | OAM&P Maintenance and Rel-16 small Enhancements (only Rel-16 CRs or earlier) | S5‑212027 | Remove the XML Solution set | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| not pursued | No | ||
S5‑212028 | Remove the XML Solution set | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑212036 | Remove unneeded solution sets | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑212069 | Rel-16 CR 28.552 Update measurements to consider abnormal releases in RRC connected state | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑212070 | Rel-16 CR 28.554 Update retainability KPIs to consider abnormal releases in RRC connected state | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑212071 | Rel-17 CR 28.552 Update measurements to consider abnormal releases in RRC connected state | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑212072 | Rel-17 CR 28.554 Update retainability KPIs to consider abnormal releases in RRC connected state | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑212075 | Rel-16 CR 28.532 Correct definitions for the File MnS (stage 2) | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑212370 | S5‑211242 | ||
S5‑212370 | Rel-16 CR 28.532 Correct definitions for the File MnS (stage 2) | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑212075 | |||
S5‑212076 | Rel-16 CR 28.532 Correct definitions for the File MnS (REST SS) | Nokia; Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑212371 | S5‑211246 | ||
S5‑212371 | Rel-16 CR 28.532 Correct definitions for the File MnS (REST SS) | Nokia; Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑212076 | |||
S5‑212077 | Rel-16 CR 28.532 Correct definitions for the File MnS (OpenAPI definitions) | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑212372 | S5‑211247 | ||
S5‑212372 | Rel-16 CR 28.532 Correct definitions for the File MnS (OpenAPI definitions) | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑212077 | |||
S5‑212078 | Rel-16 CR 28.622 Correct notification support table for ManagedElement and ManagementNode | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑212080 | Rel-17 Input to DraftCR 28.537 Add requirements for File Management | Nokia, Nokia Shanghai Bell | other | Approval | Yes |
Yes
| approved | No | S5‑211300 | |||
S5‑212107 | Rel-16 CR 28.535 Clean up the business level use cases and requirements | Nokia Germany | CR | Approval | Yes |
Yes
| merged | No | S5‑212335 | |||
S5‑212108 | Rel-16 CR 28.535 Clean up the concepts and background | Nokia Germany | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑212109 | Rel-16 CR 28.535 Clean up the specification level use cases and requirements | Nokia Germany | CR | Approval | Yes |
Yes
| merged | No | S5‑212335 | |||
S5‑212110 | Rel-16 CR 28.536 Clean up the Stage 2 model | Nokia Germany | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑212145 | Add new clauses and clarification for MDT collection peroid in NR | Ericsson Japan K-K | CR | Approval | Yes |
Yes
| revised | No | S5‑212363 | |||
S5‑212363 | Add new clauses and clarification for MDT collection peroid in NR | Ericsson Japan K-K | CR | Approval | Yes |
Yes
| agreed | No | S5‑212145 | |||
S5‑212146 | Add new clauses and clarification for MDT collection peroid in NR | Ericsson Japan K-K | CR | Approval | Yes |
Yes
| revised | No | S5‑212364 | |||
S5‑212364 | Add new clauses and clarification for MDT collection peroid in NR | Ericsson Japan K-K | CR | Approval | Yes |
Yes
| agreed | No | S5‑212146 | |||
S5‑212147 | Correct MDT collection peroid in LTE | Ericsson Japan K-K | CR | Approval | Yes |
Yes
| revised | No | S5‑212355 | |||
S5‑212355 | Correct MDT collection peroid in LTE | Ericsson Japan K-K | CR | Approval | Yes |
Yes
| agreed | No | S5‑212147 | |||
S5‑212148 | Correct MDT collection peroid in LTE | Ericsson Japan K-K | CR | Approval | Yes |
Yes
| revised | No | S5‑212356 | |||
S5‑212356 | Correct MDT collection peroid in LTE | Ericsson Japan K-K | CR | Approval | Yes |
Yes
| agreed | No | S5‑212148 | |||
S5‑212153 | Correct MDT collection peroid in LTE | Ericsson Japan K-K | CR | Approval | Yes |
Yes
| revised | No | S5‑212357 | |||
S5‑212357 | Correct MDT collection peroid in LTE | Ericsson Japan K-K | CR | Approval | Yes |
Yes
| agreed | No | S5‑212153 | |||
S5‑212154 | Correct MDT collection peroid in LTE | Ericsson Japan K-K | CR | Yes |
Yes
| revised | No | S5‑212358 | ||||
S5‑212358 | Correct MDT collection peroid in LTE | Ericsson Japan K-K | CR | - | Yes |
Yes
| agreed | No | S5‑212154 | |||
S5‑212155 | Correct MDT collection peroid in LTE | Ericsson Japan K-K | CR | Approval | Yes |
Yes
| revised | No | S5‑212359 | |||
S5‑212359 | Correct MDT collection peroid in LTE | Ericsson Japan K-K | CR | Approval | Yes |
Yes
| agreed | No | S5‑212155 | |||
S5‑212157 | Update of PCI configuration for D-SON and C-SON | Huawei Telecommunication India | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑212159 | Update of PCI configuration for D-SON and C-SON | Huawei Telecommunication India | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑212192 | Update of the PCI and DESManagementFunction | Huawei Telecommunication India | CR | Approval | Yes |
Yes
| revised | No | S5‑212339 | |||
S5‑212339 | Update of the PCI and DESManagementFunction | Huawei Telecommunication India | CR | Approval | Yes |
Yes
| agreed | No | S5‑212192 | |||
S5‑212194 | Update of the PCI and DESManagementFunction | Huawei Telecommunication India | CR | Approval | Yes |
Yes
| revised | No | S5‑212340 | |||
S5‑212340 | Update of the PCI and DESManagementFunction | Huawei Telecommunication India | CR | Approval | Yes |
Yes
| agreed | No | S5‑212194 | |||
S5‑212198 | Rel-16 CR TS 28.541 Correction on misalignment issues on EP_Transport IOC | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑212341 | |||
S5‑212341 | Rel-16 CR TS 28.541 Correction on misalignment issues on EP_Transport IOC | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑212198 | |||
S5‑212199 | Rel-17 CR TS 28.541 Correction on misalignment issues on EP_Transport IOC | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑212342 | |||
S5‑212342 | Rel-17 CR TS 28.541 Correction on misalignment issues on EP_Transport IOC | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑212199 | |||
S5‑212200 | Rel-16 CR TS 28.622 Correction of attribute properties and IOC inheritance description | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑212354 | |||
S5‑212354 | Rel-16 CR TS 28.622 Correction of attribute properties and IOC inheritance description | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑212200 | |||
S5‑212201 | Rel-16 CR TS 28.532 Correct the misalignment information for stage 2 Fault Supervision MnS | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑212334 | |||
S5‑212334 | Rel-16 CR TS 28.532 Correct the misalignment information for stage 2 Fault Supervision MnS | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑212201 | |||
S5‑212202 | Rel-16 CR TS 28.541 Correct multiplicity issue for several attributes of NR NRM | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑212343 | S5‑211218 | ||
S5‑212343 | Rel-16 CR TS 28.541 Correct multiplicity issue for several attributes of NR NRM | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑212202 | |||
S5‑212203 | Rel-17 CR TS 28.541 Correct multiplicity issue for several attributes of NR NRM | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑212344 | S5‑211219 | ||
S5‑212344 | Rel-17 CR TS 28.541 Correct multiplicity issue for several attributes of NR NRM | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑212203 | |||
S5‑212204 | Rel-16 CR TS 28.536 Correct the misalignment information for COSLA | Huawei,Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑212338 | |||
S5‑212338 | Rel-16 CR TS 28.536 Correct the misalignment information for COSLA | Huawei,Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑212379 | S5‑212204 | ||
S5‑212379 | Rel-16 CR TS 28.536 Correct the misalignment information for COSLA | Huawei,Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑212338 | |||
S5‑212213 | Discussion on how to use the Network Slicing NRM fragment to support two network slicing business model defined in TS 28.530 | Huawei | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑212215 | Rel-16 CR TS 28.541 Correct the NF name in definition of EP_NgU | China Telecommunications, Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑212345 | S5‑211492 | ||
S5‑212345 | Rel-16 CR TS 28.541 Correct the NF name in definition of EP_NgU | China Telecommunications, Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑212215 | |||
S5‑212217 | Rel-17 CR TS 28.541 Correct the NF name in definition of EP_NgU | China Telecommunications, Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑212346 | S5‑211493 | ||
S5‑212346 | Rel-17 CR TS 28.541 Correct the NF name in definition of EP_NgU | China Telecommunications, Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑212217 | |||
S5‑212219 | Discussion on issues with NSI and NSSI state management | Huawei, Orange | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑212347 | |||
S5‑212347 | Discussion on issues with NSI and NSSI state management | Huawei, Orange,Telefonica | discussion | Endorsement | Yes |
Yes
| endorsed | No | S5‑212219 | |||
S5‑212220 | Rel-15 CR 28.541 Correction to NSI and NSSI state management | Huawei, Orange | CR | Agreement | Yes |
Yes
| revised | No | S5‑212348 | |||
S5‑212348 | Rel-15 CR 28.541 Correction to NSI and NSSI state management | Huawei, Orange,Telefonica | CR | Agreement | Yes |
Yes
| agreed | No | S5‑212220 | |||
S5‑212221 | Rel-16 CR 28.541 Correction to NSI and NSSI state management | Huawei, Orange | CR | Agreement | Yes |
Yes
| revised | No | S5‑212349 | |||
S5‑212349 | Rel-16 CR 28.541 Correction to NSI and NSSI state management | Huawei, Orange,Telefonica | CR | Agreement | Yes |
Yes
| agreed | No | S5‑212221 | |||
S5‑212222 | Rel-17 CR 28.541 Correction to NSI and NSSI state management | Huawei, Orange | CR | Agreement | Yes |
Yes
| revised | No | S5‑212350 | |||
S5‑212350 | Rel-17 CR 28.541 Correction to NSI and NSSI state management | Huawei, Orange,Telefonica | CR | Agreement | Yes |
Yes
| agreed | No | S5‑212222 | |||
S5‑212244 | TD clarify roles and actors related to network slice management | Nokia, Nokia Shanghai Bell | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑212271 | Add missing Alarm Requirements and Use Cases | Ericsson LM | CR | Approval | Yes |
Yes
| revised | No | S5‑212353 | |||
S5‑212353 | Add missing Alarm Requirements and Use Cases | Ericsson LM | CR | Approval | Yes |
Yes
| not pursued | No | S5‑212271 | |||
S5‑212276 | Rel-16 CR 28.532 Correct some minor errors in the Fault MnS definition (REST SS) | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑212333 | |||
S5‑212333 | Rel-16 CR 28.532 Correct some minor errors in the Fault MnS definition (REST SS) | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑212276 | |||
S5‑212277 | Rel-16 CR 28.532 Correct some minor errors in the Prov MnS definition (REST SS) | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑212283 | Rel-16 CR 28.541 Correction of ServiceProfile attributes | Ericsson LM | CR | Approval | Yes |
Yes
| revised | No | S5‑212351 | S5‑211362 | ||
S5‑212351 | Rel-16 CR 28.541 Correction of ServiceProfile attributes | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | S5‑212283 | |||
S5‑212285 | Rel-17 CR 28.541 Correction of ServiceProfile attributes | Ericsson LM | CR | Approval | Yes |
Yes
| revised | No | S5‑212352 | S5‑211363 | ||
S5‑212352 | Rel-17 CR 28.541 Correction of ServiceProfile attributes | Ericsson LM | CR | Approval | Yes |
Yes
| not pursued | No | S5‑212285 | |||
S5‑212287 | Correct NtfSubscriptionControl containment in YANG | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑212288 | Correct NR endpoint classes containment in YANG | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑212289 | Correct NR endpoint classes containment in YANG | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑212292 | Rel-16 CR 28.552 Message names correction | Ericsson France S.A.S | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑212293 | Rel-17 CR 28.552 Message names correction | Ericsson France S.A.S | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑212295 | Remove use cases clause 5.1.3 and 5.1.4 | Ericsson LM, Deutsche Telekom AG, Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑212337 | |||
S5‑212337 | Remove use cases clause 5.1.3 and 5.1.4 | Ericsson LM, Deutsche Telekom AG, Huawei | CR | Approval | Yes |
Yes
| agreed | No | S5‑212295 | |||
S5‑212297 | Update use cases and requirements to replace communication service | Ericsson LM, Deutsche Telekom AG, Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑212335 | |||
S5‑212335 | Update use cases and requirements to replace communication service | Ericsson LM, Deutsche Telekom AG, Huawei | CR | Approval | Yes |
Yes
| agreed | No | S5‑212297 | |||
S5‑212298 | Update use cases and requirements to replace communication service | Ericsson LM, Deutsche Telekom AG, Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑212336 | |||
S5‑212336 | Update use cases and requirements to replace communication service | Ericsson LM, Deutsche Telekom AG, Huawei | CR | Approval | Yes |
Yes
| agreed | No | S5‑212298 | |||
S5‑212302 | Rel 16 CR TS 28.536 add explanation for Entities in loop | Lenovo, Motorola Mobility | CR | Yes |
Yes
| revised | No | S5‑212375 | ||||
S5‑212375 | Rel 16 CR TS 28.536 add explanation for Entities in loop | Lenovo, Motorola Mobility | CR | - | Yes |
Yes
| agreed | No | S5‑212302 | |||
S5‑212314 | Rel-16 CR 28.536 Correct OpenAPI definition of the COSLA NRM | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑211529 | |||
S5‑212315 | Rel-16 fix containment relationship for EP_Transport IOC | Nokia | CR | Agreement | Yes |
Yes
| agreed | No | S5‑211456 | |||
S5‑212316 | Rel-17 fix containment relationship for EP_Transport IOC | Nokia | CR | Agreement | Yes |
Yes
| agreed | No | S5‑211457 | |||
S5‑212321 | Fix of compilation and other errors | Nokia | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑212322 | YANG update to follow stage 2 definitions and correct earlier YANG compilation errors. | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑212323 | Fix compilation and other errors | Nokia | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑212376 | YANG update to follow stage 2 definitions and correct earlier YANG compilation errors. | Ericsson | CR | discussion | Yes |
Yes
| agreed | No | ||||
6.4 | Rel-17 Operations, Administration, Maintenance and Provisioning (OAM&P) |   | ||||||||||
6.4.1 | Management of non-public networks | S5‑212073 | pCR 28.557 Add 5GLAN group management in UE related management aspects | TELEFONICA S.A. | pCR | Approval | Yes |
Yes
| revised | No | S5‑212360 | |
S5‑212360 | pCR 28.557 Add 5GLAN group management in UE related management aspects | TELEFONICA S.A. | pCR | Approval | Yes |
Yes
| approved | No | S5‑212073 | |||
S5‑212090 | pCR 28.557 Applicability of management modes considering the deployment options of individual NPN functions. | TELEFONICA S.A. | pCR | Approval | Yes |
Yes
| revised | No | S5‑212361 | |||
S5‑212361 | pCR 28.557 Applicability of management modes considering the deployment options of individual NPN functions. | TELEFONICA S.A. | pCR | Approval | Yes |
Yes
| approved | No | S5‑212090 | |||
S5‑212138 | pCR 28.557 Exposure of management capabilities | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑212139 | pCR 28.557 Add requirements for management of PNI-NPN | Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑212140 | pCR 28.557 Add requirements for management of SNPN | Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑212444 | Latest draft TS 28.557 | Huawei | draft TS | Approval | Yes |
Yes
| approved | No | ||||
6.4.2 | Enhancement on Management Aspects of 5G Service-Level Agreement | S5‑212037 | Rel-17 Input to draftCR 28.541 Define performance requirements in different domains and update the related slice profile | China Mobile Com. Corporation | draftCR | Yes |
Yes
| noted | No | |||
S5‑212079 | Update the information model definitions for network slice NRM | China Mobile Com. Corporation | CR | Yes |
Yes
| revised | No | S5‑212362 | ||||
S5‑212362 | Update the information model definitions for network slice NRM | China Mobile Com. Corporation | CR | - | Yes |
Yes
| agreed | No | S5‑212079 | |||
S5‑212141 | Rel-17 Input to draftCR 28.541 Delete the PerfReq and add some attributes of original perfReq to RANSliceSubnetProfile | Huawei | other | Approval | Yes |
Yes
| noted | No | ||||
S5‑212272 | Input to DraftCR 28.541 Discussion including perfRec mapping to domain specific attributes | Ericsson LM | other | Endorsement | Yes |
Yes
| approved | No | ||||
S5‑212275 | Rel-17 Input to DraftCR 28.541 Define perfRec domain specific attributes | Ericsson LM | other | Approval | Yes |
Yes
| noted | No | ||||
S5‑212279 | Updated WID Enhancement on Management Aspects of 5G Service-Level Agreement | Ericsson | WID revised | Yes |
Yes
| revised | No | S5‑212373 | ||||
S5‑212373 | Updated WID Enhancement on Management Aspects of 5G Service-Level Agreement | Ericsson,Deutsche Telekom | WID revised | - | Yes |
Yes
| agreed | No | S5‑212279 | |||
S5‑212280 | Handling of slice input data | Ericsson | CR | Yes |
Yes
| revised | No | S5‑212374 | ||||
S5‑212374 | Handling of slice input data | Ericsson,Deutsche Telekom | CR | - | Yes |
Yes
| agreed | No | S5‑212280 | |||
S5‑212282 | Rel-16 CR 28.541 Correction of ServiceProfile attributes | Ericsson LM | CR | Approval | No |
Yes
| withdrawn | Yes | S5‑211362 | |||
6.4.3 | Management of MDT enhancement in 5G | S5‑212144 | Add new MR-DC related requirements | Ericsson Japan K-K | CR | Approval | Yes |
Yes
| agreed | No | ||
6.4.4 | Additional NRM features | S5‑212038 | YANG NRM for Network Slicing | Cisco Systems Belgium | CR | Agreement | Yes |
Yes
| merged | No | S5‑212324 | |
S5‑212088 | Discussion paper: Modeling managed management entities | Nokia, Nokia Shanghai Bell | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑212089 | Rel-17 CR 28.622 Clarify model for managed Management Functions | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑212301 | Code begin end markers and longer prefix length | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑212324 | YANG stage 3 for Slice management | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
6.4.5 | Enhancement of QoE Measurement Collection | S5‑212273 | Adding Signalling Based Activation for UTRAN and LTE | Ericsson LM | other | Approval | Yes |
Yes
| approved | No | ||
S5‑212440 | DraftCR for eQoE - TS 28.405 | Ericsson | draftCR | Approval | Yes |
Yes
| approved | No | ||||
6.4.6 | Enhancements of 5G performance measurements and KPIs | S5‑212055 | Proposal to stop using draftCR for WI ePM_KPI_5G | Intel | discussion | Endorsement | Yes |
Yes
| endorsed | No | ||
S5‑212056 | CR Rel-17 28.552 CR for WI ePM_KPI_5G converted from draftCR S5-211355 | Intel | CR | Agreement | Yes |
Yes
| revised | No | S5‑212365 | |||
S5‑212365 | CR Rel-17 28.552 CR for WI ePM_KPI_5G converted from draftCR S5-211355 | Intel | CR | Agreement | Yes |
Yes
| agreed | No | S5‑212056 | |||
S5‑212057 | CR Rel-17 28.552 Add measurements related data management for UDR | Intel | CR | Agreement | Yes |
Yes
| revised | No | S5‑212366 | |||
S5‑212366 | CR Rel-17 28.552 Add measurements related data management for UDR | Intel | CR | Agreement | Yes |
Yes
| agreed | No | S5‑212057 | |||
S5‑212058 | CR Rel-17 28.552 Add measurements related to background data transfer policy control for PCF | Intel | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑212067 | Rel-17 CR 28.552 Add measurements to cover all accessibility types | Ericsson LM | CR | Approval | Yes |
Yes
| revised | No | S5‑212367 | |||
S5‑212367 | Rel-17 CR 28.552 Add measurements to cover all accessibility types | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | S5‑212067 | |||
S5‑212068 | Rel-17 CR 28.554 Update the Accessibility KPI to cover RRC Resume | Ericsson LM | CR | Approval | Yes |
Yes
| not pursued | No | ||||
6.4.7 | Management of the enhanced tenant concept |   | ||||||||||
6.4.8 | Management data collection control and discovery | S5‑212066 | Simplified Request for Data Collection | Nokia, Nokia Shanghai Bell | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑212382 | |
S5‑212382 | Simplified Request for Data Collection | Nokia, Nokia Shanghai Bell | discussion | Endorsement | Yes |
Yes
| endorsed | No | S5‑212066 | |||
S5‑212081 | Rel-17 Input to DraftCR 28.537 Add management data management requirements | Nokia, Nokia Shanghai Bell | other | Approval | Yes |
Yes
| revised | No | S5‑212384 | |||
S5‑212384 | Rel-17 Input to DraftCR 28.537 Add management data management requirements | Nokia, Nokia Shanghai Bell,Deutsche Telekom | other | Approval | Yes |
Yes
| approved | No | S5‑212081 | |||
S5‑212085 | Rel-17 Input to DraftCR 28.537 Add management data management requirements (pictures and video) | Nokia, Nokia Shanghai Bell, | other | Approval | Yes |
Yes
| revised | No | S5‑212385 | |||
S5‑212385 | Rel-17 Input to DraftCR 28.537 Add management data management requirements (pictures and video) | Nokia, Nokia Shanghai Bell,Deutsche Telekom | other | Approval | Yes |
Yes
| approved | No | S5‑212085 | |||
S5‑212086 | Rel-17 Input to DraftCR 28.537 Add management data management requirements (“easy-to-use” data request job) | Nokia, Nokia Shanghai Bell | other | Approval | Yes |
Yes
| revised | No | S5‑212383 | |||
S5‑212383 | Rel-17 Input to DraftCR 28.537 Add management data management requirements (“easy-to-use” data request job) | Nokia, Nokia Shanghai Bell,Deutsche Telekom | other | Approval | Yes |
Yes
| approved | No | S5‑212086 | |||
S5‑212087 | Rel-17 Input to DraftCR 28.622 Add data store control NRM fragment | Nokia, Nokia Shanghai Bell | other | Approval | Yes |
Yes
| noted | No | ||||
S5‑212441 | DraftCR for MADCOL TS 28.537 | Nokia | draftCR | Approval | Yes |
Yes
| approved | No | ||||
6.4.9 | Autonomous network levels | S5‑212205 | pCR TS 28.100 Add autonomous network level for RAN NE deployment | Huawei,China Mobile,China Telecom,China Unicom | pCR | Approval | Yes |
Yes
| revised | No | S5‑212386 | |
S5‑212386 | pCR TS 28.100 Add autonomous network level for RAN NE deployment | Huawei,China Mobile,China Telecom,China Unicom | pCR | Approval | Yes |
Yes
| approved | No | S5‑212205 | |||
S5‑212206 | pCR TS 28.100 Add autonomous network level for RAN UE throughput optimization | Huawei,China Mobile,China Telecom,China Unicom | pCR | Approval | Yes |
Yes
| revised | No | S5‑212387 | |||
S5‑212387 | pCR TS 28.100 Add autonomous network level for RAN UE throughput optimization | Huawei,China Mobile,China Telecom,China Unicom | pCR | Approval | Yes |
Yes
| approved | No | S5‑212206 | |||
S5‑212245 | pCR 28.100 Add definition of network and service planning | China Mobile, Huawei, China Telecom, China Unicom | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑212246 | pCR 28.100 Update Clause 4.1 Autonomous network concept | China Mobile, Huawei, China Telecom, China Unicom | pCR | Approval | Yes |
Yes
| revised | No | S5‑212388 | |||
S5‑212388 | pCR 28.100 Update Clause 4.1 Autonomous network concept | China Mobile, Huawei, China Telecom, China Unicom | pCR | Approval | Yes |
Yes
| approved | No | S5‑212246 | |||
S5‑212247 | pCR 28.100 Add generic classification of autonomous network level for network optimization | China Mobile, Huawei, China Telecom, China Unicom | pCR | Approval | Yes |
Yes
| revised | No | S5‑212389 | |||
S5‑212389 | pCR 28.100 Add generic classification of autonomous network level for network optimization | China Mobile, Huawei, China Telecom, China Unicom | pCR | Approval | Yes |
Yes
| approved | No | S5‑212247 | |||
S5‑212248 | LS to TM Forum on introduction of 3GPP Autonomous Network Levels | China Mobile | LS out | Approval | Yes |
Yes
| revised | No | S5‑212390 | |||
S5‑212390 | LS to TM Forum on introduction of 3GPP Autonomous Network Levels | China Mobile | LS out | Approval | Yes |
Yes
| approved | No | S5‑212248 | |||
S5‑212429 | Latest draft TS 28.100 | China Mobile | draft TS | Approval | Yes |
Yes
| approved | No | ||||
6.4.10 | Intent driven management service for mobile networks | S5‑212091 | pCR TS 28.312 Add conceptual description for intent MnS | Nokia | pCR | Approval | Yes |
Yes
| revised | No | S5‑212391 | |
S5‑212391 | pCR TS 28.312 Add conceptual description for intent MnS | Nokia | pCR | Approval | Yes |
Yes
| approved | No | S5‑212091 | |||
S5‑212101 | pCR TS 28.312 Add capabilities of an intent Driven MnS | Nokia | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑212207 | pCR TS 28.312 Add concept for intent lifecycle management | Huawei,China Mobile | pCR | Approval | Yes |
Yes
| approved | No | S5‑211222 | |||
S5‑212208 | pCR TS 28.312 Add stage 2 information model definition for intent | Huawei,China Mobile | pCR | Approval | Yes |
Yes
| revised | No | S5‑212443 | S5‑211223 | ||
S5‑212443 | pCR TS 28.312 Add stage 2 information model definition for intent | Huawei,China Mobile | pCR | Approval | Yes |
Yes
| approved | No | S5‑212208 | |||
S5‑212209 | pCR TS 28.312 Add stage 2 procedure for intent lifecycle management | Huawei,China Mobile | pCR | Approval | Yes |
Yes
| revised | No | S5‑212442 | S5‑211225 | ||
S5‑212442 | pCR TS 28.312 Add stage 2 procedure for intent lifecycle management | Huawei,China Mobile | pCR | Approval | Yes |
Yes
| approved | No | S5‑212209 | |||
S5‑212210 | pCR TS 28.312 Add stage 2 management operation for intent | Huawei,China Mobile | pCR | Approval | Yes |
Yes
| revised | No | S5‑212392 | S5‑211224 | ||
S5‑212392 | pCR TS 28.312 Add stage 2 management operation for intent | Huawei,China Mobile | pCR | Approval | Yes |
Yes
| approved | No | S5‑212210 | |||
S5‑212218 | pCR 28.312 Requirement of Intent for service at edge | Samsung R&D Institute UK | pCR | Agreement | Yes |
Yes
| revised | No | S5‑212448 | |||
S5‑212448 | pCR 28.312 Requirement of Intent for service at edge | Samsung R&D Institute UK | pCR | Agreement | Yes |
Yes
| approved | No | S5‑212218 | |||
S5‑212430 | Latest draft TS 28.312 | Huawei | draft TS | Approval | Yes |
Yes
| approved | No | ||||
6.4.11 | Network policy management for 5G mobile networks based on NFV scenarios | S5‑212111 | pCR 28.555 add specification level requirement | China Mobile Com. Corporation | pCR | Yes |
Yes
| noted | No | |||
S5‑212112 | pCR 28.555 add specification level use cases-policy deletion | China Mobile Com. Corporation | pCR | Yes |
Yes
| approved | No | |||||
S5‑212113 | pCR 28.555 add specification level use cases-policy update | China Mobile Com. Corporation | pCR | Yes |
Yes
| approved | No | |||||
S5‑212114 | pCR 28.555 add specification level use cases-policy query | China Mobile Com. Corporation | pCR | Yes |
Yes
| revised | No | S5‑212395 | ||||
S5‑212395 | pCR 28.555 add specification level use cases-policy query | China Mobile Com. Corporation | pCR | - | Yes |
Yes
| approved | No | S5‑212114 | |||
S5‑212115 | pCR 28.555 add specification level use cases-policy activation | China Mobile Com. Corporation | pCR | Yes |
Yes
| revised | No | S5‑212393 | ||||
S5‑212393 | pCR 28.555 add specification level use cases-policy activation | China Mobile Com. Corporation | pCR | - | Yes |
Yes
| approved | No | S5‑212115 | |||
S5‑212116 | pCR 28.555 add specification level use cases-policy deactivation | China Mobile Com. Corporation | pCR | Yes |
Yes
| revised | No | S5‑212394 | ||||
S5‑212394 | pCR 28.555 add specification level use cases-policy deactivation | China Mobile Com. Corporation | pCR | - | Yes |
Yes
| approved | No | S5‑212116 | |||
S5‑212117 | pCR 28.555 add specification level use cases-policy conflicts notification | China Mobile Com. Corporation | pCR | Yes |
Yes
| revised | No | S5‑212396 | ||||
S5‑212396 | pCR 28.555 add specification level use cases-policy conflicts notification | China Mobile Com. Corporation | pCR | - | Yes |
Yes
| approved | No | S5‑212117 | |||
S5‑212431 | Latest draft TS 28.555 | China Mobile | draft TS | Approval | Yes |
Yes
| approved | No | ||||
6.4.12 | Enhanced Closed loop SLS Assurance | S5‑212119 | DP on assurance policy for closed control loop | Huawei Technologies Japan K.K. | discussion | Approval | Yes |
Yes
| noted | No | ||
S5‑212120 | DP on assurance report for closed control loop | Huawei Technologies Japan K.K. | discussion | Approval | Yes |
Yes
| noted | No | ||||
S5‑212121 | Rel-17 Input to draftCR TS 28.536 Add assurance policy for closed control loop | Huawei Technologies Japan K.K. | draftCR | Agreement | Yes |
Yes
| noted | No | ||||
S5‑212122 | Rel-17 Input to draftCR TS 28.536 Add assurance report for closed control loop | Huawei Technologies Japan K.K. | draftCR | Agreement | Yes |
Yes
| noted | No | ||||
S5‑212123 | Rel-17 Input to draftCR TS 28.535 Configure policies for closed control loop | Huawei Technologies Japan K.K. | draftCR | Agreement | Yes |
Yes
| noted | No | ||||
S5‑212196 | Add requirements of closed loop SLS assurance | Huawei Telecommunication India | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑212294 | Rel 17 CR TS28.535 Add Use Case on ACCL Goal translation | Lenovo, Motorola Mobility | CR | Decision | Yes |
Yes
| not pursued | No | ||||
S5‑212296 | Rel 17 CR TS28.536 Solution for configuring conditions for ACCL state change | Lenovo, Motorola Mobility | CR | Yes |
Yes
| not pursued | No | |||||
S5‑212299 | Rel 17 draft CR TS28.536 Solution for pausing a closed loop | Lenovo, Motorola Mobility | other | Yes |
Yes
| noted | No | |||||
S5‑212300 | Input to eCOSLA draft CR S5-211358 | Ericsson LM, Deutsche Telekom AG | other | Approval | Yes |
Yes
| revised | No | S5‑212397 | |||
S5‑212397 | Input to eCOSLA draft CR S5-211358 | Ericsson LM, Deutsche Telekom AG | other | Approval | Yes |
Yes
| approved | No | S5‑212300 | |||
S5‑212303 | Add editors note to clause 5.1.3 and 5.1.4 | Ericsson LM, Deutsche Telekom AG, Huawei | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑212304 | Add lifecycle of closed control loop and clarify relationship between CSA and intent | Ericsson LM, Deutsche Telekom AG | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑212439 | DraftCR for eCOSLA - TS 28.535 | Ericsson | draftCR | Approval | Yes |
Yes
| approved | No | ||||
6.4.13 | Self-Organizing Networks (SON) for 5G networks | S5‑212291 | Requirements, use cases and services for C-PCI | Ericsson France S.A.S | CR | Approval | Yes |
Yes
| revised | No | S5‑212306 | |
S5‑212306 | Requirements, use cases and services for C-PCI | Ericsson France S.A.S | CR | Approval | Yes |
Yes
| not pursued | No | S5‑212291 | |||
6.4.14 | Enhancement of Handover Optimization | S5‑212290 | CHO measurements | Ericsson France S.A.S | CR | Approval | Yes |
Yes
| not pursued | No | S5‑211322 | |
6.4.15 | Enhancements on EE for 5G networks | S5‑212128 | Rel-17 CR TS 28.310 Add use case and requirements for switching off edge UPFs | Orange, AT&T, Deutsche Telekom,Telefonica | CR | Agreement | Yes |
Yes
| revised | No | S5‑212398 | |
S5‑212398 | Rel-17 CR TS 28.310 Add use case and requirements for switching off edge UPFs | Orange, AT&T, Deutsche Telekom,Telefonica | CR | Agreement | Yes |
Yes
| agreed | No | S5‑212128 | |||
6.4.16 | Discovery of management services in 5G | S5‑212082 | TS 28.533 Add Management Service Type | China Mobile Com. Corporation | draftCR | Yes |
Yes
| noted | No | |||
S5‑212083 | Discussion on AddMnSType | China Mobile Com. Corporation | discussion | Endorsement | No |
Yes
| withdrawn | Yes | ||||
S5‑212084 | Discussion on AddMnSType | China Mobile Com. Corporation | discussion | Yes |
Yes
| noted | No | |||||
S5‑212223 | Rel-17 CR 28.533 Add operations for discovery of management services | Huawei | other | Agreement | Yes |
Yes
| noted | No | ||||
S5‑212224 | Rel-17 CR 28.532 Add operations for discovery of management services | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑212225 | Revised WID on Discovery of management services in 5G | Huawei | WID revised | Agreement | Yes |
Yes
| revised | No | S5‑212399 | |||
S5‑212399 | Revised WID on Discovery of management services in 5G | Huawei | WID revised | Agreement | Yes |
Yes
| agreed | No | S5‑212225 | |||
6.4.17 | Management Aspects of 5G Network Sharing | S5‑212130 | Rel-17 CR TS 28.552 Add PLMN granularity for RRC connection number measurements | China Telecom Corporation Ltd. | CR | Agreement | Yes |
Yes
| revised | No | S5‑212400 | |
S5‑212400 | Rel-17 CR TS 28.552 Add PLMN granularity for RRC connection number measurements | China Telecom Corporation Ltd. | CR | Agreement | Yes |
Yes
| agreed | No | S5‑212130 | |||
S5‑212156 | Rel-17 CR TS 28.552 Add PLMN granularity for packet delay measurements in split gNB scenario | China Telecom Corporation Ltd., Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑212193 | LS from SA5 to RAN2,RAN3 on network sharing with multiple SSB | ZTE | LS out | Approval | Yes |
Yes
| revised | No | S5‑212403 | |||
S5‑212403 | LS from SA5 to RAN2,RAN3 on network sharing with multiple SSB | ZTE | LS out | Approval | Yes |
Yes
| approved | No | S5‑212193 | |||
S5‑212195 | Discussion on NRM enhancement to support NG-RAN network sharing | ZTE | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑212197 | Rel-17 CR TS 28.541 Enhance the NRM definitions to support NG-RAN network sharing | ZTE | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑212211 | Rel-17 CR TS 32.130 Add business level requirements for NG-RAN MOCN network sharing | Huawei,China Telecom,China Unicom | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑212212 | Rel-17 CR TS 32.130 Update role definition and business requirements for network sharing | Huawei,China Telecom,China Unicom | CR | Agreement | Yes |
Yes
| revised | No | S5‑212402 | |||
S5‑212402 | Rel-17 CR TS 32.130 Update role definition and business requirements for network sharing | Huawei,China Telecom,China Unicom | CR | Agreement | Yes |
Yes
| agreed | No | S5‑212212 | |||
S5‑212214 | Discussion on NG-RAN network sharing with multiple CellId | ZTE, China Unicom | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑212216 | Rel-17 CR TS 32.130 add NG-RAN sharing deployment example in Annex | ZTE | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑212234 | Discussion on support RRC connection number measurements per PLMN in MOCN network sharing | China Telecom Corporation Ltd. | discussion | Endorsement | Yes |
Yes
| endorsed | No | ||||
S5‑212249 | Rel-17 CR 28.552 Add Filter and Filter naming description | Ericsson LM | CR | Approval | Yes |
Yes
| revised | No | S5‑212401 | |||
S5‑212401 | Rel-17 CR 28.552 Add Filter and Filter naming description | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | S5‑212249 | |||
S5‑212270 | RAN Sharing NRM support for MOCN | Ericsson LM | CR | Approval | Yes |
Yes
| not pursued | No | ||||
6.5 | OAM&P Studies |   | ||||||||||
6.5.1 | Study on management and orchestration aspects with integrated satellite components in a 5G network | S5‑212044 | Reference architecture for the management of integrated satellite transport network for backhaul | Airbus | pCR | Approval | Yes |
Yes
| revised | No | S5‑212404 | |
S5‑212404 | Reference architecture for the management of integrated satellite transport network for backhaul | Airbus | pCR | Approval | Yes |
Yes
| approved | No | S5‑212044 | |||
S5‑212045 | Two architecture scenarios for 5G networks with an integrated satellite transport network for backhaul | Airbus; | pCR | Approval | Yes |
Yes
| revised | No | S5‑212405 | |||
S5‑212405 | Two architecture scenarios for 5G networks with an integrated satellite transport network for backhaul | Airbus; | pCR | Approval | Yes |
Yes
| approved | No | S5‑212045 | |||
S5‑212232 | Presentation sheet for approval of TR28.808 | TNO | TS or TR cover | Approval | Yes |
Yes
| approved | No | ||||
S5‑212432 | Latest 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‑212065 | pCR 28.813: Update Resource Consumption Estimation Methods | China Telecom Corporation Ltd. | pCR | Approval | Yes |
Yes
| revised | No | S5‑212406 | |
S5‑212406 | pCR 28.813: Update Resource Consumption Estimation Methods | China Telecom Corporation Ltd. | pCR | Approval | Yes |
Yes
| approved | No | S5‑212065 | |||
S5‑212126 | pCR TR 28.813 EE KPI definition for RAN-only eMBB network slice | Orange, AT&T, Deutsche Telekom | pCR | Approval | Yes |
Yes
| revised | No | S5‑212407 | |||
S5‑212407 | pCR TR 28.813 EE KPI definition for RAN-only eMBB network slice | Orange, AT&T, Deutsche Telekom | pCR | Approval | Yes |
Yes
| approved | No | S5‑212126 | |||
S5‑212127 | pCR TR 28.813 Potential solution for KI#5 (5GC NF Energy Consumption) | Orange, Intel, AT&T, Nokia, Deutsche Telekom | pCR | Approval | Yes |
Yes
| revised | No | S5‑212408 | |||
S5‑212408 | pCR TR 28.813 Potential solution for KI#5 (5GC NF Energy Consumption) | Orange, Intel, AT&T, Nokia, Deutsche Telekom | pCR | Approval | Yes |
Yes
| approved | No | S5‑212127 | |||
S5‑212137 | pCR 28.813 Update on EE KPI for URLLC type of network slice | Huawei, China Telecom | pCR | Approval | Yes |
Yes
| revised | No | S5‑212409 | |||
S5‑212409 | pCR 28.813 Update on EE KPI for URLLC type of network slice | Huawei, China Telecom | pCR | Approval | Yes |
Yes
| approved | No | S5‑212137 | |||
S5‑212231 | New Key Issue: SLS assurance for EE | Huawei Telecommunication India | pCR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑212236 | pCR TR 28.813 New Key Issue: SLS assurance for EE | Huawei Telecommunication India | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑212433 | Latest draft TR 28.813 | ORANGE | draft TR | Approval | Yes |
Yes
| approved | No | ||||
6.5.3 | Study on management aspects of edge computing | S5‑212030 | pCR 28.814 clarification of 3GPP management system | Intel Corporation Italia SpA | pCR | Approval | Yes |
Yes
| revised | No | S5‑212416 | |
S5‑212416 | pCR 28.814 clarification of 3GPP management system | Intel Corporation Italia SpA | pCR | Approval | Yes |
Yes
| approved | No | S5‑212030 | |||
S5‑212031 | pCR 28.814 UC of UPF selection to support EAS deployment | Intel Corporation Italia SpA | pCR | Approval | Yes |
Yes
| revised | No | S5‑212410 | |||
S5‑212410 | pCR 28.814 UC of UPF selection to support EAS deployment | Intel Corporation Italia SpA | pCR | Approval | Yes |
Yes
| approved | No | S5‑212031 | |||
S5‑212032 | pCR 28.814 add solutions for UPF selection to assist EAS deployment | Intel Corporation Italia SpA | pCR | Approval | Yes |
Yes
| revised | No | S5‑212411 | |||
S5‑212411 | pCR 28.814 add solutions for UPF selection to assist EAS deployment | Intel Corporation Italia SpA | pCR | Approval | Yes |
Yes
| approved | No | S5‑212032 | |||
S5‑212040 | pCR 28.814 5GC NF performance assurance use case | Intel Corporation Italia SpA | pCR | Approval | Yes |
Yes
| revised | No | S5‑212412 | |||
S5‑212412 | pCR 28.814 5GC NF performance assurance use case | Intel Corporation Italia SpA | pCR | Approval | Yes |
Yes
| approved | No | S5‑212040 | |||
S5‑212041 | pCR 28.814 5GC NF performance assurance solution | Intel Corporation Italia SpA | pCR | Approval | Yes |
Yes
| revised | No | S5‑212413 | |||
S5‑212413 | pCR 28.814 5GC NF performance assurance solution | Intel Corporation Italia SpA | pCR | Approval | Yes |
Yes
| approved | No | S5‑212041 | |||
S5‑212042 | pCR 28.814 5GC NF fault supervision use case | Intel Corporation Italia SpA | pCR | Approval | Yes |
Yes
| revised | No | S5‑212414 | |||
S5‑212414 | pCR 28.814 5GC NF fault supervision use case | Intel Corporation Italia SpA | pCR | Approval | Yes |
Yes
| approved | No | S5‑212042 | |||
S5‑212043 | pCR 28.814 5GC NF fault supervision solution | Intel Corporation Italia SpA | pCR | Approval | Yes |
Yes
| revised | No | S5‑212415 | |||
S5‑212415 | pCR 28.814 5GC NF fault supervision solution | Intel Corporation Italia SpA | pCR | Approval | Yes |
Yes
| approved | No | S5‑212043 | |||
S5‑212226 | pCR 28.814 correct EAS deployment UC | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑212447 | |||
S5‑212447 | pCR 28.814 correct EAS deployment UC | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑212226 | |||
S5‑212227 | pCR 28.814 correct EES and ECS deployment requirement | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑212417 | |||
S5‑212417 | pCR 28.814 correct EES and ECS deployment requirement | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑212227 | |||
S5‑212228 | pCR 28.814 correct EAS deployment solution | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑212434 | Latest draft TR 28.814 | Intel | draft TR | Approval | Yes |
Yes
| approved | No | ||||
6.5.4 | Study on enhancement of Management Data Analytics Service | S5‑212035 | pCR TR 28.809 Add reference to ITU-T draft Rec. M.resm-AI | Orange, Intel | pCR | Approval | Yes |
Yes
| noted | No | ||
S5‑212049 | pCR 28.809 Add evaluation for cross-slice resource optimization | Intel Sweden AB | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑212050 | pCR 28.809 Add evaluation for RAN user plane congestion analysis | Intel Sweden AB | pCR | Approval | Yes |
Yes
| revised | No | S5‑212419 | |||
S5‑212419 | pCR 28.809 Add evaluation for RAN user plane congestion analysis | Intel Sweden AB | pCR | Approval | Yes |
Yes
| approved | No | S5‑212050 | |||
S5‑212051 | pCR 28.809 Add evaluation for UE throughput in network slice analysis | Intel Sweden AB | pCR | Approval | Yes |
Yes
| revised | No | S5‑212420 | |||
S5‑212420 | pCR 28.809 Add evaluation for UE throughput in network slice analysis | Intel Sweden AB | pCR | Approval | Yes |
Yes
| approved | No | S5‑212051 | |||
S5‑212052 | pCR 28.809 Update and evaluate the solution for jitter analysis | Intel Sweden AB | pCR | Approval | Yes |
Yes
| revised | No | S5‑212421 | |||
S5‑212421 | pCR 28.809 Update and evaluate the solution for jitter analysis | Intel Sweden AB | pCR | Approval | Yes |
Yes
| approved | No | S5‑212052 | |||
S5‑212053 | pCR 28.809 Update and evaluate the mobility performance analysis | Intel Sweden AB | pCR | Approval | Yes |
Yes
| revised | No | S5‑212422 | |||
S5‑212422 | pCR 28.809 Update and evaluate the mobility performance analysis | Intel Sweden AB | pCR | Approval | Yes |
Yes
| approved | No | S5‑212053 | |||
S5‑212054 | Presentation of TR 28.809 for approval | Intel Sweden AB | TS or TR cover | Approval | Yes |
Yes
| approved | No | ||||
S5‑212060 | pCR 28.809 Add general conclusions and recommendations | Intel, HUAWEI | pCR | Approval | Yes |
Yes
| revised | No | S5‑212446 | |||
S5‑212446 | pCR 28.809 Add general conclusions and recommendations | Intel, HUAWEI | pCR | Approval | Yes |
Yes
| approved | No | S5‑212060 | |||
S5‑212102 | Report Validation | Nokia Germany | pCR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑212103 | Report Validation | Nokia Germany, Ericsson, Intel | pCR | Approval | Yes |
Yes
| revised | No | S5‑212445 | |||
S5‑212445 | Report Validation | Nokia Germany, Ericsson, Intel | pCR | Approval | Yes |
Yes
| approved | No | S5‑212103 | |||
S5‑212106 | Enahancing analytics request and reporting use case | Nokia Germany | pCR | Approval | Yes |
Yes
| revised | No | S5‑212418 | |||
S5‑212418 | Enahancing analytics request and reporting use case | Nokia Germany | pCR | Approval | Yes |
Yes
| approved | No | S5‑212106 | |||
S5‑212118 | SOD on MDAS use cases | Huawei Technologies (Korea) | other | Information | Yes |
Yes
| revised | No | S5‑212423 | S5‑211085 | ||
S5‑212423 | SOD on MDAS use cases | Huawei Technologies (Korea) | discussion | Information | Yes |
Yes
| noted | No | S5‑212118 | |||
S5‑212142 | pCR 28.809 Update on MDA assisted energy saving | China Telecom Corporation Ltd. | pCR | Yes |
Yes
| approved | No | |||||
S5‑212143 | pCR 28.809 Update the MDA process and Add Feedback Use case | China Telecom Corporation Ltd. | pCR | Yes |
Yes
| merged | No | S5‑212445 | ||||
S5‑212158 | pCR 28.809 update descriptions of MDA process | HuaWei Technologies Co., Ltd | pCR | Approval | Yes |
Yes
| merged | No | S5‑212445 | |||
S5‑212160 | pCR 28.809 Add MDA job creation and data reporting use cases | HuaWei Technologies Co., Ltd | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑212191 | pCR 28.809 Update descriptions of MDA overview architecture | HuaWei Technologies Co., Ltd | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑212229 | pCR 28.809 re-arranging paging UC | Samsung R&D Institute UK | pCR | Agreement | Yes |
Yes
| approved | No | ||||
S5‑212230 | pCR 28.809 re-arranging traffic projection UC | Samsung R&D Institute UK | pCR | Agreement | Yes |
Yes
| approved | No | ||||
S5‑212233 | pCR 28.809 re-arranging software upgrade UC | Samsung R&D Institute UK | pCR | Agreement | Yes |
Yes
| noted | No | ||||
S5‑212269 | ML Model training report | Nokia Germany | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑212435 | Latest draft TR 28.809 | Intel | draft TR | Approval | Yes |
Yes
| approved | No | ||||
6.5.5 | Study on network slice management enhancement (revised to include security aspects) | S5‑212250 | pCR 28.811 Enhancement of operations for network slice management | Ericsson LM | pCR | Approval | Yes |
Yes
| noted | No | ||
S5‑212281 | pCR 28.811 Addition of national roaming scenario | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑212424 | |||
S5‑212424 | pCR 28.811 Addition of national roaming scenario | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑212281 | |||
S5‑212436 | Latest draft TR 28.811 | Huawei | draft TR | Approval | Yes |
Yes
| approved | No | ||||
6.5.6 | Study on YANG PUSH | S5‑212039 | Functionality of YANG-Push | Ericsson Hungary Ltd | pCR | Approval | Yes |
Yes
| noted | No | ||
S5‑212284 | Using YANG-Push | Ericsson Hungary Ltd | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑212286 | YANG-Push Impact on Specifications | Ericsson Hungary Ltd | pCR | Approval | Yes |
Yes
| noted | No | ||||
6.5.7 | Study on access control for management service | S5‑212241 | 28.817 use case - granular access control by operator | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||
S5‑212242 | 28.817 use case - integrate with existing AAA system of operator | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑212243 | 28.817 use case - trust relationship between MnS producer and consumer | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑212425 | |||
S5‑212425 | 28.817 use case - trust relationship between MnS producer and consumer | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑212243 | |||
S5‑212437 | Latest draft TR 28.817 | Nokia | draft TR | Approval | Yes |
Yes
| approved | No | ||||
7 | Charging |   | ||||||||||
7.1 | Charging Plenary | S5‑212008 | CH agenda and time plan | WG vice Chair (Nokia) | agenda | Yes |
Yes
| revised | No | S5‑212458 | ||
S5‑212458 | CH agenda and time plan | WG vice Chair (Nokia) | agenda | - | Yes |
Yes
| approved | No | S5‑212008 | |||
S5‑212009 | Charging exec report | WG vice Chair (Nokia) | report | Yes |
Yes
| noted | No | |||||
S5‑212305 | LS from WSOLU to 3GPP SA5 - 5G charging architecture for wholesale scenarios | GSMA | LS in | Yes |
Yes
| postponed | No | |||||
S5‑212501 | List of approved DraftCRs | Nokia | discussion | Information | Yes |
Yes
| noted | No | ||||
7.2 | New Charging Work Item proposals |   | ||||||||||
7.3 | Charging Maintenance and Rel-16 small Enhancements | S5‑212092 | Rel-16 CR 32.291 Correction on different identities for NEF charging | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑212480 | |
S5‑212480 | Rel-16 CR 32.291 Correction on different identities for NEF charging | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑212092 | |||
S5‑212093 | Rel-16 CR 32.298 Correction on different identities for NEF charging | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑212481 | |||
S5‑212481 | Rel-16 CR 32.298 Correction on different identities for NEF charging | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑212093 | |||
S5‑212094 | Rel-16 CR 32.298 Correction on user location information | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑212482 | |||
S5‑212482 | Rel-16 CR 32.298 Correction on user location information | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑212508 | S5‑212094 | ||
S5‑212508 | Rel-16 CR 32.298 Correction on user location information | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑212482 | |||
S5‑212095 | Rel-16 CR 32.291 Correction on missing MnS producer | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑212096 | Rel-16 CR 32.298 Correction on missing MnS producer | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑212507 | |||
S5‑212507 | Rel-16 CR 32.298 Correction on missing MnS producer | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑212096 | |||
S5‑212097 | Rel-17 CR 32.240 Inclusive language review | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑212098 | Rel-16 CR 32.256 Correction on Registration flows and message content | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑212099 | Rel-16 CR 32.298 Correction on missing fields for CHF CDR - AMF | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑212100 | Rel-16 CR 32.291 Correction on missing attributes for AMF charging | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑212104 | Rel-16 CR 32.240 Correction for Network Slice Charging | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑212483 | |||
S5‑212483 | Rel-16 CR 32.240 Correction for Network Slice Charging | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑212104 | |||
S5‑212105 | Rel-17 CR 32.240 Correction for Network Slice Charging | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑212484 | |||
S5‑212484 | Rel-17 CR 32.240 Correction for Network Slice Charging | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑212105 | |||
S5‑212167 | Rel-16 32.255 charging id clarification | Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑212485 | |||
S5‑212485 | Rel-16 32.255 charging id clarification | Huawei | CR | Approval | Yes |
Yes
| agreed | No | S5‑212167 | |||
S5‑212168 | Rel-17 32.255 charging id clarification | Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑212486 | |||
S5‑212486 | Rel-17 32.255 charging id clarification | Huawei | CR | Approval | Yes |
Yes
| agreed | No | S5‑212168 | |||
S5‑212169 | Rel-16 32.255 Trigger Override Clarification | Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑212487 | |||
S5‑212487 | Rel-16 32.255 Trigger Override Clarification | Huawei | CR | Approval | Yes |
Yes
| agreed | No | S5‑212169 | |||
S5‑212170 | Rel-17 32.255 Trigger Override Clarification | Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑212488 | |||
S5‑212488 | Rel-17 32.255 Trigger Override Clarification | Huawei | CR | Approval | Yes |
Yes
| agreed | No | S5‑212170 | |||
S5‑212171 | Rel-16 32.291 Add the Bindings for NSM Charging | Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑212489 | |||
S5‑212489 | Rel-16 32.291 Add the Bindings for NSM Charging | Huawei | CR | Approval | Yes |
Yes
| agreed | No | S5‑212171 | |||
S5‑212172 | Rel-16 32.291 support of stateless NF | Huawei | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑212173 | Rel-17 32.291 Optional header clearification | Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑212498 | |||
S5‑212498 | Rel-17 32.291 Optional header clearification | Huawei | CR | Approval | Yes |
Yes
| agreed | No | S5‑212173 | |||
S5‑212174 | Rel-16 32.240 Add the CCS in the Definitions | Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑212490 | |||
S5‑212490 | Rel-16 32.240 Add the CCS in the Definitions | Huawei | CR | Approval | Yes |
Yes
| agreed | No | S5‑212174 | |||
S5‑212175 | Rel-17 32.240 Add the CCS in the Definitions | Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑212491 | |||
S5‑212491 | Rel-17 32.240 Add the CCS in the Definitions | Huawei | CR | Approval | Yes |
Yes
| agreed | No | S5‑212175 | |||
S5‑212176 | Rel-16 32.290 Trigger Clarification | Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑212492 | |||
S5‑212492 | Rel-16 32.290 Trigger Clarification | Huawei | CR | Approval | Yes |
Yes
| agreed | No | S5‑212176 | |||
S5‑212177 | Rel-17 32.290 Trigger Clarification | Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑212493 | |||
S5‑212493 | Rel-17 32.290 Trigger Clarification | Huawei | CR | Approval | Yes |
Yes
| agreed | No | S5‑212177 | |||
S5‑212178 | Rel-16 32.298 ECGI trigger and TAI trigger clarification | Huawei | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑212179 | Rel-16 32.255 Add the description for the trigger Condition | Huawei | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑212180 | Rel-17 32.255 Add the description for the trigger Condition | Huawei | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑212181 | Rel-16 32.255 Correct the description for the Multiple UPFs | Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑212494 | |||
S5‑212494 | Rel-16 32.255 Correct the description for the Multiple UPFs | Huawei | CR | Approval | Yes |
Yes
| agreed | No | S5‑212181 | |||
S5‑212182 | Rel-17 32.255 Correct the description for the Multiple UPFs | Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑212495 | |||
S5‑212495 | Rel-17 32.255 Correct the description for the Multiple UPFs | Huawei | CR | Approval | Yes |
Yes
| agreed | No | S5‑212182 | |||
S5‑212183 | Discussion paper on User Location for 5G Charging | Huawei | discussion | Approval | Yes |
Yes
| noted | No | ||||
S5‑212184 | Rel-17 32.290 Add the QCT mechanism | Huawei | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑212185 | Rel-17 32.290 Add the QCT Information Element | Huawei | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑212186 | Rel-17 32.290 Add the Combinational quota mechanism | Huawei | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑212187 | Rel-17 32.290 Add the Combinational quota in Message | Huawei | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑212237 | Rel-16 CR 32.255 Correction of Termination action | China Mobile Com. Corporation | CR | Approval | Yes |
Yes
| revised | No | S5‑212496 | |||
S5‑212496 | Rel-16 CR 32.255 Correction of Termination action | China Mobile Com. Corporation | CR | Approval | Yes |
Yes
| agreed | No | S5‑212237 | |||
S5‑212238 | Rel-17 CR 32.255 Correction of Termination action | China Mobile Com. Corporation | CR | Approval | Yes |
Yes
| revised | No | S5‑212497 | |||
S5‑212497 | Rel-17 CR 32.255 Correction of Termination action | China Mobile Com. Corporation | CR | Approval | Yes |
Yes
| agreed | No | S5‑212238 | |||
S5‑212239 | Rel-16 CR 32.255 Correction of Charging Id assigned by the V-SMF | China Mobile Com. Corporation | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑212240 | Rel-17 CR 32.255 Correction of Charging Id assigned by the V-SMF | China Mobile Com. Corporation | CR | Approval | Yes |
Yes
| revised | No | S5‑212459 | |||
S5‑212459 | Rel-17 CR 32.255 Correction of Charging Id assigned by the V-SMF | China Mobile Com. Corporation | CR | Approval | Yes |
Yes
| agreed | No | S5‑212240 | |||
S5‑212251 | Rel-17 CR 32.290 Correcting final unit handling | Ericsson LM | CR | Agreement | Yes |
Yes
| revised | No | S5‑212499 | |||
S5‑212499 | Rel-17 CR 32.290 Correcting final unit handling | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | S5‑212251 | |||
S5‑212252 | Rel-17 draftCR 32.291 DraftCR correcting filter rule as list | Ericsson LM | draftCR | Approval | Yes |
Yes
| revised | No | S5‑212500 | |||
S5‑212500 | Rel-17 draftCR 32.291 DraftCR correcting filter rule as list | Ericsson LM | draftCR | Approval | Yes |
Yes
| approved | No | S5‑212252 | |||
S5‑212253 | Rel-16 CR 32.255 Correcting QoS information description | Ericsson LM | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
S5‑212254 | Rel-17 CR 32.255 Correcting missing charging control policy data identifier | Ericsson LM | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑212255 | Rel-17 draftCR 32.291 DraftCR correcting missing charging control policy data identifier | Ericsson LM | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑212256 | Rel-17 draftCR 32.298 DraftCR correcting missing charging control policy data identifier | Ericsson LM | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑212278 | Rel-16 CR 32.255 Correcting QoS information description | Ericsson LM | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑212457 | Rel-16 CR 32.256 Correction on UE MM Core Network Capability | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑212502 | Rel-16 CR 32.291 Update OpenAPI version | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
7.4 | Rel-17 Charging |   | ||||||||||
7.4.1 | IMS Charging in 5G System Architecture | S5‑212188 | Rel-17 32.260 Correct the charging function | Huawei | CR | Approval | Yes |
Yes
| agreed | No | ||
S5‑212257 | Rel-17 CR 32.260 Updating CDR handling for converged charging | Ericsson LM | CR | Agreement | Yes |
Yes
| revised | No | S5‑212460 | |||
S5‑212460 | Rel-17 CR 32.260 Updating CDR handling for converged charging | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | S5‑212257 | |||
S5‑212258 | Rel-17 CR 32.260 Use of IMS node instead of the explicit nodes | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑212259 | Rel-17 CR 32.260 Adding converged charging to principles | Ericsson LM | CR | Agreement | Yes |
Yes
| revised | No | S5‑212461 | |||
S5‑212461 | Rel-17 CR 32.260 Adding converged charging to principles | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | S5‑212259 | |||
S5‑212260 | Rel-17 CR 32.281 Adding converged charging to scope | Ericsson LM | CR | Agreement | Yes |
Yes
| revised | No | S5‑212463 | |||
S5‑212463 | Rel-17 CR 32.281 Adding converged charging to scope | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | S5‑212260 | |||
7.4.2 | Charging enhancement for URLLC |   | ||||||||||
7.4.3 | N40 Interface Enhancements to Support GERAN and UTRAN | S5‑212261 | Rel-17 CR 32.255 Adding of annex for GERAN and UTRAN support | Ericsson LM | CR | Agreement | Yes |
Yes
| not pursued | No | ||
7.5 | Charging studies |   | ||||||||||
7.5.1 | Study on charging aspects of Edge Computing | S5‑212046 | pCR 28.815 Add solution based on aggregation of usage by MnS producer for inter-provider charging for 5GS | Intel Finland Oy | pCR | Approval | Yes |
Yes
| revised | No | S5‑212464 | |
S5‑212464 | pCR 28.815 Add solution based on aggregation of usage by MnS producer for inter-provider charging for 5GS | Intel Finland Oy | pCR | Approval | Yes |
Yes
| approved | No | S5‑212046 | |||
S5‑212047 | pCR 28.815 Udpate edge enabling infrastructure resource charging solution with quota management | Intel Finland Oy | pCR | Approval | Yes |
Yes
| merged | No | S5‑212503 | |||
S5‑212048 | pCR 28.815 Correction on solution for EAS application context transfer charging | Intel Finland Oy | pCR | Approval | Yes |
Yes
| merged | No | S5‑212504 | |||
S5‑212262 | Rel-17 pCR 28.815 Updating performance based charging | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑212503 | |||
S5‑212503 | Rel-17 pCR 28.815 Updating performance based charging | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑212262 | |||
S5‑212263 | Rel-17 pCR 28.815 Updating application server deployment charging | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑212264 | Rel-17 pCR 28.815 Updating enabling services charging | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑212504 | |||
S5‑212504 | Rel-17 pCR 28.815 Updating enabling services charging | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑212264 | |||
S5‑212265 | Rel-17 pCR 28.815 Updating performance based charging | Ericsson LM | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑212465 | Draft TR 28.815 | Intel | draft TR | Approval | Yes |
Yes
| approved | No | ||||
7.5.2 | Study on charging aspects of 5GS CIoT | S5‑212161 | pCR 28.816 add use case of support for monitoring events charging | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑212466 | |
S5‑212466 | pCR 28.816 add use case of support for monitoring events charging | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑212161 | |||
S5‑212162 | pCR 28.816 add use case rate control of user data in 5G data connectivity charging | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑212505 | |||
S5‑212505 | pCR 28.816 add use case rate control of user data in 5G data connectivity charging | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑212162 | |||
S5‑212163 | pCR 28.816 Add use case the access of 5GS CIoT device | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑212467 | |||
S5‑212467 | pCR 28.816 Add use case the access of 5GS CIoT device | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑212163 | |||
S5‑212164 | pCR 28.816 add use case rate control of user data in home-routed roaming scenario | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑212506 | |||
S5‑212506 | pCR 28.816 add use case rate control of user data in home-routed roaming scenario | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑212164 | |||
S5‑212165 | pCR 28.816 add description of key issues for 5G data connectivity domain charging | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑212166 | pCR 28.816 add description of key issues for CP data transfer domain charging | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑212468 | 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‑212133 | pCR 32.846 Add possible solution for ProSe Unicast mode Direct Communication | CATT | pCR | Approval | Yes |
Yes
| revised | No | S5‑212469 | |
S5‑212469 | pCR 32.846 Add possible solution for ProSe Unicast mode Direct Communication | CATT | pCR | Approval | Yes |
Yes
| approved | No | S5‑212133 | |||
S5‑212134 | pCR 32.846 Add topic for charging for ProSe Direct Communication based on QoS flow | CATT | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑212135 | pCR 32.846 Update reqirement and key issue | CATT | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑212136 | pCR 32.846 Update solution for Direct Discovery charging | CATT | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑212266 | Rel-17 pCR 32.846 Adding solutions to direct communication | Ericsson LM | pCR | Approval | Yes |
Yes
| merged | No | S5‑212469 | |||
S5‑212474 | Draft 32.846 | CATT | draft TR | Approval | Yes |
Yes
| approved | No | ||||
7.5.4 | Study on Charging Aspect of 5G LAN-type Services | S5‑212189 | Rel-17 pCR 28.822 Add the NEF based solution for 5G VN Group | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑212471 | |
S5‑212471 | Rel-17 pCR 28.822 Add the NEF based solution for 5G VN Group | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑212189 | |||
S5‑212190 | Rel-17 pCR 28.822 Add the Use case for 5G VN traffic forwarding | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑212472 | |||
S5‑212472 | Rel-17 pCR 28.822 Add the Use case for 5G VN traffic forwarding | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑212190 | |||
S5‑212473 | Draft TR 28.822 | Huawei | draft TR | Approval | Yes |
Yes
| approved | No | ||||
7.5.5 | Study on charging aspects for enhancements of Network Slicing Phase 2 | S5‑212124 | Rel-17 pCR TR 32.847 - add new solution for Key Issue #1 based on new charging service | Matrixx | pCR | Agreement | Yes |
Yes
| noted | No | ||
S5‑212125 | Rel-17 pCR TR 32.847 - update subclause on background from GSMA | Matrixx | pCR | Agreement | Yes |
Yes
| revised | No | S5‑212475 | |||
S5‑212475 | Rel-17 pCR TR 32.847 - update subclause on background from GSMA | Matrixx | pCR | Agreement | Yes |
Yes
| approved | No | S5‑212125 | |||
S5‑212149 | Rel-17 pCR 32.847 Introduction of NS converged charging sol#1.1 single CCS for KI#1 | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| rejected | No | ||||
S5‑212150 | Rel-17 pCR 28.847 Introduction NS converged charging sol#2.x single CCS for KI#2 | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| rejected | No | ||||
S5‑212151 | Rel-17 pCR 28.847 Introduction of new requirements and Key issues - volume and duration | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑212476 | |||
S5‑212476 | Rel-17 pCR 28.847 Introduction of new requirements and Key issues - volume and duration | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑212151 | |||
S5‑212152 | Rel-17 pCR 28.847 Introduction of NS converged charging solution#x.1 single CCS for KI#x | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| rejected | No | ||||
S5‑212267 | Rel-17 pCR 32.847 Adding key issue for number of UEs per network slice | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑212477 | |||
S5‑212477 | Rel-17 pCR 32.847 Adding key issue for number of UEs per network slice | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑212267 | |||
S5‑212268 | Rel-17 pCR 32.847 Adding key issue for number of PDU sessions per network slice | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑212478 | |||
S5‑212478 | Rel-17 pCR 32.847 Adding key issue for number of PDU sessions per network slice | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑212268 | |||
S5‑212479 | Draft TR 32.847 | Matrixx | draft TR | discussion | Yes |
Yes
| approved | No | ||||
8 | Any Other Business |   |