Tdoc List
2022-05-27 16:05
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‑223000 | 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‑223001 | 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‑223002 | e-meeting process | WG Chair | discussion | Yes |
Yes
| noted | No | |||
S5‑223003 | Post e-meeting email approval status | WG Chair | other | Yes |
No
| available | No | |||||
S5‑223010 | SA5 working procedures | WG Chair | other | Yes |
Yes
| approved | No | |||||
S5‑223011 | Process for management of draft TS-TRs | WG Chair | other | Yes |
Yes
| noted | No | |||||
5.2 | Technical issues at SA5 level |   | ||||||||||
5.3 | Liaison statements at SA5 level | S5‑223020 | LS on Logical relationship between query parameters | C4-222302 | LS in | Yes |
Yes
| replied to | No | |||
S5‑223517 | Reply to: LS on Logical relationship between query parameters | Huawei | LS out | approval | Yes |
Yes
| approved | No | ||||
S5‑223021 | Response to request for TM Forum AN Use Case material at Joint Workshop 23rd February 2022 and updated slides meeting 16th March 2022- LS22-0003 | TM Forum | LS in | Yes |
Yes
| noted | No | |||||
S5‑223022 | Ls ccSA5 Request to clarify whether there are IPR issues with using 3GPP terminology and information objects and names in code contributed to ONAP | ONAP | LS in | Yes |
Yes
| noted | No | |||||
S5‑223026 | Reply LS to ETSI MEC ccSA5 on MEC Federation and interest to collaborate | S6-220931 | LS in | Yes |
Yes
| noted | No | |||||
S5‑223391 | Application Enablement Standards in SA6 | Samsung | discussion | Discussion | Yes |
Yes
| noted | No | ||||
S5‑223515 | LS on Issues Network Slice information delivery to a 3rd party | S6-220975 | LS in | discussion | Yes |
Yes
| replied to | No | ||||
S5‑223516 | Reply to: LS on Issues Network Slice information delivery to a 3rd party | Samsung | LS out | approval | Yes |
Yes
| approved | No | ||||
5.4 | SA5 meeting calendar | S5‑223012 | SA5 meeting calendar | WG CHair | other | Yes |
Yes
| revised | No | S5‑223526 | ||
S5‑223526 | SA5 meeting calendar | WG CHair | other | - | Yes |
Yes
| agreed | No | S5‑223012 | |||
6 | OAM&P |   | ||||||||||
6.1 | OAM&P Plenary | S5‑223004 | OAM&P action list | WG Vice Chair (Huawei) | other | Yes |
Yes
| noted | No | |||
S5‑223005 | agenda_with_Tdocs_sequence_proposal_OAM | WG Vice Chair (Huawei) | agenda | Yes |
Yes
| noted | No | |||||
S5‑223006 | OAM Exec Report | WG Vice Chair (Huawei) | report | Yes |
No
| available | No | |||||
S5‑223007 | OAM Chair notes and conclusions | WG Chair | report | Yes |
Yes
| noted | No | |||||
S5‑223013 | Collection of useful endorsed document and external communication documents | WG Vice Chair (Huawei) | discussion | Yes |
Yes
| noted | No | |||||
S5‑223014 | Collection of Rel-18 3GPP SA5 OAM WoP | WG Vice Chair (Huawei) | discussion | Yes |
Yes
| noted | No | |||||
S5‑223015 | Resubmitted Reply LS to SA5 on beam measurement reports | R3-221383 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑223524 | Reply to: Resubmitted Reply LS to SA5 on beam measurement reports | Ericsson | LS out | approval | Yes |
Yes
| approved | No | ||||
S5‑223016 | Resubmitted LS on configuration updates of MDT M1, M8 and M9 in RAN3 specifications | R3-221445 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑223504 | Reply to: Resubmitted LS on configuration updates of MDT M1, M8 and M9 in RAN3 specifications | Nokia | LS out | approval | Yes |
Yes
| revised | No | S5‑223583 | |||
S5‑223583 | Reply to: Resubmitted LS on configuration updates of MDT M1, M8 and M9 in RAN3 specifications | Nokia | LS out | approval | Yes |
Yes
| approved | No | S5‑223504 | |||
S5‑223017 | Resubmitted LS on RAN3 agreements for NR QoE | R3-222890 | LS in | Yes |
Yes
| postponed | No | |||||
S5‑223018 | Resubmitted LS Reply on QoE configuration and reporting related issues | S4-220309 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑223518 | Reply to: Resubmitted LS Reply on QoE configuration and reporting related issues | Ericsson | LS out | approval | Yes |
Yes
| approved | No | ||||
S5‑223019 | Resubmitted LS on TS 28.404/TS 28.405 Clarification | S4-211234 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑223519 | Reply to: Resubmitted LS on TS 28.404/TS 28.405 Clarification | Ericsson | LS out | approval | Yes |
Yes
| revised | No | S5‑223546 | |||
S5‑223546 | Reply to: Resubmitted LS on TS 28.404/TS 28.405 Clarification | Ericsson | LS out | approval | Yes |
Yes
| approved | No | S5‑223519 | |||
S5‑223025 | LS on FS_eEDGEAPP, Solution for Dynamic EAS instantiation | S6-220848 | LS in | Yes |
Yes
| postponed | No | |||||
S5‑223520 | Reply to: LS on FS_eEDGEAPP, Solution for Dynamic EAS instantiation | Samsung | LS out | approval | Yes |
Yes
| noted | No | ||||
S5‑223027 | LS on network slice LCM consumption and use cases | S6-220932 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑223521 | Reply to: LS on network slice LCM consumption and use cases | Ericsson | LS out | approval | Yes |
Yes
| approved | No | ||||
S5‑223386 | Living document for stage 2-3 alignment | WG chair | discussion | Information | Yes |
Yes
| noted | No | ||||
S5‑223522 | LS on Study on KQIs for 5G service experience | Ericsson | LS out | Approval | Yes |
Yes
| approved | No | ||||
S5‑223525 | LS on Inclusive language updates related to BBF TR-196 | Ericsson | LS out | Approval | Yes |
Yes
| approved | No | ||||
6.2 | New OAM&P Work Item proposals | S5‑223240 | New R18 SID on MP-CP Conflict management and coordination | Lenovo | SID new | Yes |
Yes
| revised | No | S5‑223584 | ||
S5‑223584 | New R18 SID on MP-CP Conflict management and coordination | Lenovo | SID new | - | Yes |
Yes
| noted | No | S5‑223240 | |||
S5‑223298 | Rel-18 SID on Closed control loop governance for autonomous network | ZTE Corporation, China Telecom | SID new | Approval | Yes |
Yes
| revised | No | S5‑223585 | |||
S5‑223585 | Rel-18 SID on Closed control loop governance for autonomous network | ZTE Corporation, China Telecom | SID new | Approval | Yes |
Yes
| noted | No | S5‑223298 | |||
S5‑223348 | New SID on Data Collection for Digital Twin in Network Management System | China Mobile E-Commerce Co. | SID new | Approval | Yes |
Yes
| noted | No | ||||
S5‑223351 | Discussion on Data Collection for Digital Twin in Network Management System | China Mobile E-Commerce Co. | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑223409 | New WID on continuous integration continuous delivery support for 3GPP NFs | Lenovo | WID new | Approval | Yes |
Yes
| noted | No | ||||
S5‑223432 | New WID on QoE Measurement collection automation support | Ericsson | WID new | Yes |
Yes
| noted | No | |||||
S5‑223433 | New WID on deprecation | Ericsson | WID new | Yes |
Yes
| noted | No | |||||
S5‑223486 | New Rel-18 WID Enhancement of Management Data Analytics phase 2 | Intel, NEC | WID new | Agreement | Yes |
Yes
| noted | No | ||||
S5‑223513 | Study on Data management | Nokia, Nokia Shanghai Bell | SID new | Approval | Yes |
Yes
| not treated | No | ||||
S5‑223523 | New Rel-18 SID Enhancement of Management Data Analytics phase 2 | Intel | SID new | Agreement | No |
Yes
| withdrawn | Yes | ||||
6.3 | OAM&P Maintenance and Rel-18 small Enhancements | S5‑223052 | Rel-16 TS 28.541 OpenAPI file name and dependence change-5gcNrm.yaml | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑223527 | S5‑222581 |
S5‑223527 | Rel-16 TS 28.541 OpenAPI file name and dependence change-5gcNrm.yaml | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑223052 | |||
S5‑223053 | Rel-16 TS 28.541 OpenAPI file name and dependence change-nrNrm.yaml | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑223528 | S5‑222582 | ||
S5‑223528 | Rel-16 TS 28.541 OpenAPI file name and dependence change-nrNrm.yaml | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑223053 | |||
S5‑223054 | Rel-16 TS 28.541 OpenAPI file name and dependence change-sliceNrm.yaml | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑223529 | S5‑222583 | ||
S5‑223529 | Rel-16 TS 28.541 OpenAPI file name and dependence change-sliceNrm.yaml | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑223054 | |||
S5‑223055 | Rel-17 TS 28.541 OpenAPI file name and dependence change-5gcNrm.yaml | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑223530 | |||
S5‑223530 | Rel-17 TS 28.541 OpenAPI file name and dependence change-5gcNrm.yaml | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑223055 | |||
S5‑223056 | Rel-17 TS 28.541 OpenAPI file name and dependence change-nrNrm.yaml | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑223531 | |||
S5‑223531 | Rel-17 TS 28.541 OpenAPI file name and dependence change-nrNrm.yaml | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑223056 | |||
S5‑223057 | Rel-17 TS 28.541 OpenAPI file name and dependence change-sliceNrm.yaml | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑223532 | |||
S5‑223532 | Rel-17 TS 28.541 OpenAPI file name and dependence change-sliceNrm.yaml | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑223057 | |||
S5‑223058 | Rel-16 TS 28.623 OpenAPI file name and dependence change-comDefs | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑223533 | S5‑222584 | ||
S5‑223533 | Rel-16 TS 28.623 OpenAPI file name and dependence change-comDefs | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑223058 | |||
S5‑223059 | Rel-16 TS 28.623 OpenAPI file name and dependence change-genericNrm | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑223534 | S5‑222585 | ||
S5‑223534 | Rel-16 TS 28.623 OpenAPI file name and dependence change-genericNrm | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑223059 | |||
S5‑223060 | Rel-17 TS 28.623 OpenAPI file name and dependence change-comDefs | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑223535 | |||
S5‑223535 | Rel-17 TS 28.623 OpenAPI file name and dependence change-comDefs | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑223060 | |||
S5‑223061 | Rel-17 TS 28.623 OpenAPI file name and dependence change-genericNrm | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑223536 | |||
S5‑223536 | Rel-17 TS 28.623 OpenAPI file name and dependence change-genericNrm | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑223061 | |||
S5‑223068 | Rel-16 CR TS 28.536 OpenAPI file name and dependence change-coslaNrm | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223069 | Rel-17 CR TS 28.536 OpenAPI file name and dependence change-coslaNrm | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223072 | Rel-17 CR TS 28.538 OpenAPI file name and dependence change-edgeNrm | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑223537 | |||
S5‑223537 | Rel-17 CR TS 28.538 OpenAPI file name and dependence change-edgeNrm | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑223072 | |||
S5‑223073 | Rel-17 CR TS28541 Correction to property of EP_Transport attribute ipAddress | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑223124 | Rel-17 Correct the definition of DRB setup related counters | Nubia Technology Co.,Ltd | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223125 | yaml indentation correction for comDefs.yaml | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑223538 | |||
S5‑223538 | yaml indentation correction for comDefs.yaml | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑223125 | |||
S5‑223126 | yaml indentation correction for comDefs.yam | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223133 | Rel-17 CR for TS28.537 editorialCorrections | ZTE Corporation | CR | Approval | Yes |
Yes
| revised | No | S5‑223539 | |||
S5‑223539 | Rel-17 CR for TS28.537 editorialCorrections | ZTE Corporation | CR | Approval | Yes |
Yes
| agreed | No | S5‑223133 | |||
S5‑223134 | Rel-17 CR for TS28.552 editorialCorrections | ZTE Corporation | CR | Approval | Yes |
Yes
| revised | No | S5‑223540 | |||
S5‑223540 | Rel-17 CR for TS28.552 editorialCorrections | ZTE Corporation | CR | Approval | Yes |
Yes
| agreed | No | S5‑223134 | |||
S5‑223146 | Rel-17 CR TS28541 Fixing attribute properties for ServiceProfile attribute networkSliceSharingIndicator | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑223541 | |||
S5‑223541 | Rel-17 CR TS28541 Fixing attribute properties for ServiceProfile attribute networkSliceSharingIndicator | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑223146 | |||
S5‑223152 | Correct isOrdered-isUnique for multivalue attributes | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| revised | No | S5‑223542 | |||
S5‑223542 | Correct isOrdered-isUnique for multivalue attributes | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| agreed | No | S5‑223152 | |||
S5‑223153 | Correct isOrdered-isUnique for multivalue attributes | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| revised | No | S5‑223543 | |||
S5‑223543 | Correct isOrdered-isUnique for multivalue attributes | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| agreed | No | S5‑223153 | |||
S5‑223155 | Correct isOrdered-isUnique for multivalue attributes | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| revised | No | S5‑223544 | |||
S5‑223544 | Correct isOrdered-isUnique for multivalue attributes | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| agreed | No | S5‑223155 | |||
S5‑223165 | Rel-17 CR 28.622 Add missing definitions of common data types | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑223166 | CR Rel-17 TS 32.592 Non-inclusive language correction | Nokia | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223186 | Correct isOrdered-isUnique for multivalue attributes | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| revised | No | S5‑223545 | |||
S5‑223545 | Correct isOrdered-isUnique for multivalue attributes | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| agreed | No | S5‑223186 | |||
S5‑223194 | Rel-17 CR 28.532 Align allowed file transfer protocols in stage 2 with stage 1 requirements | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223195 | Rel-16 CR 32.158 Clarify clause Design pattern for reading a resource | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223196 | Rel-17 CR 32.158 Clarify clause Design pattern for reading a resource | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223198 | Rel-18 CR 28.313 Correct non-inclusive language | Intel Korea, Ltd. | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223199 | Alarm Handling Clarifications | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| revised | No | S5‑223548 | |||
S5‑223548 | Alarm Handling Clarifications | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| agreed | No | S5‑223199 | |||
S5‑223200 | Alarm Handling Clarifications | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| revised | No | S5‑223549 | |||
S5‑223549 | Alarm Handling Clarifications | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| agreed | No | S5‑223200 | |||
S5‑223233 | Rel-17 CR 28.541 Correction on attribute latency of SubnetProfiles | Huawei | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223244 | Rel-17 CR 28.623 Fix description of attribute mnsScope | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑223245 | Rel-16 CR 32.422 adding missing signaling and interface related to SMF for trace | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑223550 | |||
S5‑223550 | Rel-16 CR 32.422 adding missing signaling and interface related to SMF for trace | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑223245 | |||
S5‑223246 | Rel-17 CR 32.422 adding missing signaling and interface related to SMF for trace | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑223551 | |||
S5‑223551 | Rel-17 CR 32.422 adding missing signaling and interface related to SMF for trace | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑223246 | |||
S5‑223247 | Rel-16 CR 32.423 adding missing interface related to SMF for trace | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑223552 | |||
S5‑223552 | Rel-16 CR 32.423 adding missing interface related to SMF for trace | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑223247 | |||
S5‑223248 | Rel-17 CR 32.423 adding missing interface related to SMF for trace | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑223553 | |||
S5‑223553 | Rel-17 CR 32.423 adding missing interface related to SMF for trace | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑223248 | |||
S5‑223299 | Rel-17 CR for TS28.552 Change the measurement object class to support MOCN network sharing with multiple Cell Identity broadcast scenarios | ZTE Corporation | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑223300 | Rel-17 CR for TS28.552 Add the measurement object class to support MOCN network sharing with multiple Cell Identity broadcast scenarios | ZTE Corporation | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑223301 | Rel-17 CR for TS28.552 Correct Mean and Max Time of requested conditional handover executions | ZTE Corporation | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑223309 | Rel-17 CR TS 28.541 Address the unnecessary reference for the yaml file | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑223310 | Rel-16 CR 28.536 Minor correction on the format for cosla yaml file | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑223311 | Rel-17 CR 28.536 Minor correction on the format for cosla yaml file | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑223312 | Rel-16 CR 28.532 OpenAPI file name and dependence change- part1 | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑223313 | Rel-16 CR 28.532 OpenAPI file name and dependence change- part2 | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑223314 | Rel-16 CR 28.550 OpenAPI file name and dependence change | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑223315 | Rel-17 CR 28.532 OpenAPI file name and dependence change- part1 | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑223316 | Rel-17 CR 28.532 OpenAPI file name and dependence change- part2 | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑223317 | Rel-17 CR 28.550 OpenAPI file name and dependence change | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑223331 | Rel-17 TS 28.658 Non-inclusive language correction | HuaWei Technologies Co., Ltd | CR | Yes |
Yes
| agreed | No | |||||
S5‑223332 | CR Rel-17 TS 28.659 Non-inclusive language correction | HuaWei Technologies Co., Ltd | CR | Yes |
Yes
| agreed | No | |||||
S5‑223357 | Rel-16 CR 28.532 Correct definition of Resource | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑223554 | |||
S5‑223554 | Rel-16 CR 28.532 Correct definition of Resource | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑223357 | |||
S5‑223358 | Rel-17 CR 28.532 Correct definition of Resource | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑223555 | |||
S5‑223555 | Rel-17 CR 28.532 Correct definition of Resource | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑223358 | |||
S5‑223359 | Rel-17 CR 28.532 Correct notifyMOIChanges (stage 2) | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑223556 | |||
S5‑223556 | Rel-17 CR 28.532 Correct notifyMOIChanges (stage 2) | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑223359 | |||
S5‑223360 | Rel-17 CR 28.532 Correct notifyMOIChanges (REST SS) | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑223557 | |||
S5‑223557 | Rel-17 CR 28.532 Correct notifyMOIChanges (REST SS) | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑223360 | |||
S5‑223362 | Rel-17 CR 28.532 Correct notifyMOIChanges (OpenAPI definitions) | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑223558 | |||
S5‑223558 | Rel-17 CR 28.532 Correct notifyMOIChanges (OpenAPI definitions) | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑223362 | |||
S5‑223369 | CR Rel-17 TS 32.406 Non-inclusive language correction | China Mobile | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223371 | Remove Editor's Note in clause 4.2.5.3 | Ericsson LM, Verizon | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223375 | Correct attribute properties in assuranceTargetList | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223377 | Correct attribute properties in assuranceTargetList | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223388 | Data change notifications YANG-in-Rest format | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| revised | No | S5‑223559 | |||
S5‑223559 | Data change notifications YANG-in-Rest format | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| agreed | No | S5‑223388 | |||
S5‑223393 | CR Rel-17 TS 32.452 Non-inclusive language correction | China Mobile E-Commerce Co. | CR | Approval | Yes |
Yes
| revised | No | S5‑223547 | |||
S5‑223547 | CR Rel-17 TS 32.452 Non-inclusive language correction | China Mobile E-Commerce Co. | CR | Approval | Yes |
Yes
| agreed | No | S5‑223393 | |||
S5‑223405 | Rel-15 CR 28.622 Clarification for IRP and SBMA framework | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑223406 | Rel-16 CR 28.622 Clarification for IRP and SBMA framework | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑223407 | Rel-17 CR 28.622 Clarification for IRP and SBMA framework | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑223419 | Rel-16 CR 32.156 Clarification of property defaultValue | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑223560 | |||
S5‑223560 | Rel-16 CR 32.156 Clarification of property defaultValue | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑223419 | |||
S5‑223420 | Rel-17 CR 32.156 Clarification of property defaultValue | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑223561 | |||
S5‑223561 | Rel-17 CR 32.156 Clarification of property defaultValue | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑223420 | |||
S5‑223422 | Add granularity period examples | Ericsson LM | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑223423 | Add granularity period examples | Ericsson LM | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑223425 | Add granularity period examples | Ericsson LM | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑223435 | CR R17 32.511-h00 Correcting non inclusive language | Ericsson | CR | Yes |
Yes
| agreed | No | |||||
S5‑223451 | Rel-17 CR TS 28.541 Correction to multiplicity of relation between NetworkSlice IOC and NetworkSliceSubnet IOC | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑223490 | Rel-17 CR 28.541 Update Figure L.2.1 and accompanying paragraph. | TELEFONICA S.A. | CR | Agreement | Yes |
Yes
| revised | No | S5‑223562 | S5‑221030 | ||
S5‑223562 | Rel-17 CR 28.541 Update Figure L.2.1 and accompanying paragraph. | TELEFONICA S.A. | CR | Agreement | Yes |
Yes
| agreed | No | S5‑223490 | |||
S5‑223507 | Rel-16 CR 28.623 Alignment of attribute values of attribute tjMDTReportInterval to TS 32.422, TS 38.413 and TS 38.423 | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223508 | Rel-17 CR 28.623 Alignment of attribute values of attribute tjMDTReportInterval to TS 32.422, TS 38.413 and TS 38.423 | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223514 | Rel-17 CR 28.532 Clarify usage of notifyMOIChanges for NRMs defined in YANG | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| merged | No | S5‑223559 | |||
6.4 | Rel-18 Operations, Administration, Maintenance and Provisioning (OAM&P) |   | ||||||||||
6.4.1 | Self-Configuration of RAN NEs |   | ||||||||||
6.4.1.1 | RANSC_WoP#1 | S5‑223361 | pCR 28.317 Add Concept | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||
S5‑223364 | pCR 28.317 Usecase and requirement for ARCF data handling | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
6.4.1.2 | RANSC_WoP#2 |   | ||||||||||
6.4.1.3 | RANSC_WoP#3 |   | ||||||||||
6.4.2 | Network slicing provisioning rules |   | ||||||||||
6.4.2.1 | NSRULE_WoP#1 | S5‑223221 | Specify network slicing provisioning rules requirements | Ericsson LM, Deutsche Telekom | CR | Approval | Yes |
Yes
| not pursued | No | ||
6.4.2.2 | NSRULE_WoP#2 | S5‑223222 | Add network slice rules to NRM | Ericsson LM, Deutsche Telekom | CR | Approval | Yes |
Yes
| not pursued | No | ||
S5‑223295 | Rel-18 network slice isolation | Nokia, Nokia Shanghai Bell, Huawei | CR | Approval | Yes |
Yes
| not pursued | No | ||||
6.4.3 | Additional NRM features phase 2 |   | ||||||||||
6.4.3.1 | AdNRM_ph2_WoP#1 | S5‑223180 | Rel-18 Input to draftCR 28.622 Add Scheduler IOC (stage 2) | Nokia, Nokia Shanghai Bell | other | Approval | Yes |
Yes
| noted | No | ||
S5‑223181 | Rel-18 Input to draftCR 28.623 Add Scheduler IOC (stage 3) | Nokia, Nokia Shanghai Bell | other | Approval | Yes |
Yes
| noted | No | ||||
S5‑223182 | Rel-18 Input to draftCR 28.622 Enhance PerfMetricJob by scheduler (stage 2) | Nokia, Nokia Shanghai Bell | other | Approval | Yes |
Yes
| noted | No | ||||
S5‑223183 | Rel-18 Input to draftCR 28.623 Enhance PerfMetricJob by scheduler (stage 3) | Nokia, Nokia Shanghai Bell | other | Approval | Yes |
Yes
| noted | No | ||||
S5‑223491 | Discussion to add BWP Set configuration support in NRM | Ericsson Inc. | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑223563 | |||
S5‑223563 | Discussion to add BWP Set configuration support in NRM | Ericsson Inc. | discussion | Endorsement | Yes |
Yes
| approved | No | S5‑223491 | |||
S5‑223493 | Discussion on enhanced QoS model for RLC and PDCP | Ericsson Inc. | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
6.4.3.2 | AdNRM_ph2_WoP#2 |   | ||||||||||
6.4.3.3 | AdNRM_ph2_WoP#3 |   | ||||||||||
6.4.4 | Enhanced Edge Computing Management | S5‑223752 | DraftCR for eECM – TS 28.538 | Samsung | draftCR | Approval | Yes |
Yes
| approved | No | ||
6.4.4.1 | eECM_WoP#1 |   | ||||||||||
6.4.4.2 | eECM_WoP#2 | S5‑223224 | Rel-18 InputToDraftCR 28.538 EESFunction IOC Stage 3 | Samsung R&D Institute India | other | Yes |
Yes
| merged | No | S5‑223564 | ||
S5‑223338 | Rel-18 InputTodraftCR 28.538 EASFunction IOC | AsiaInfo Technologies Inc | draftCR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑223372 | Rel-18 InputTodraftCR 28.538 EASFunction IOC | AsiaInfo Technologies Inc | draftCR | Approval | Yes |
Yes
| revised | No | S5‑223564 | |||
S5‑223564 | Rel-18 InputTodraftCR 28.538 EASFunction IOC | AsiaInfo Technologies Inc | draftCR | Approval | Yes |
Yes
| approved | No | S5‑223372 | |||
6.4.4.3 | eECM_WoP#3 |   | ||||||||||
6.4.4.4 | eECM_WoP#4 |   | ||||||||||
6.4.4.5 | eECM_WoP#5 | S5‑223076 | Rel-18 CR 28.622 Add stage 2 solution for LcmJob IOC | Intel Korea, Ltd. | CR | Approval | No |
Yes
| withdrawn | Yes | ||
S5‑223077 | Rel-18 CR 28.623 Add stage 3 solution for LcmJob IOC | Intel Korea, Ltd. | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑223078 | Rel-18 CR 28.622 Add stage 2 solution for LcmJob IOC | Intel Korea, Ltd. | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑223079 | Rel-18 CR 28.538 Revise EAS VNF instantiation procedure | Intel Korea, Ltd. | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑223080 | Rel-18 CR 28.538 Revise EAS VNF termination procedure | Intel Korea, Ltd. | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑223081 | Rel-18 CR 28.538 Add EAS VNF update procedure | Intel Korea, Ltd. | CR | Approval | Yes |
Yes
| not pursued | No | ||||
6.4.4.6 | eECM_WoP#6 |   | ||||||||||
6.4.4.7 | eECM_WoP#7 |   | ||||||||||
6.4.4.8 | eECM_WoP#8 |   | ||||||||||
6.4.5 | Enhancements of EE for 5G Phase 2 |   | ||||||||||
6.4.5.1 | EE5GPLUS_Ph2_WoP#1 |   | ||||||||||
6.4.5.2 | EE5GPLUS_Ph2_WoP#2 |   | ||||||||||
6.5 | OAM&P Studies |   | ||||||||||
6.5.1 | Study on enhancement of autonomous network levels | S5‑223659 | Latest draft TR 28.910 | China Mobile | draft TR | Approval | Yes |
Yes
| approved | No | ||
6.5.1.1 | FS_eANL_WoP#1 | S5‑223318 | pCR 28.910 Add introduction on relevant SI/WI in 3GPP | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||
S5‑223323 | pCR TR 28.910 Add key issues for enhancement of ANL for network optimization | Huawei,China Mobile | pCR | Approval | Yes |
Yes
| revised | No | S5‑223565 | |||
S5‑223565 | pCR TR 28.910 Add key issues for enhancement of ANL for network optimization | Huawei,China Mobile | pCR | Approval | Yes |
Yes
| approved | No | S5‑223323 | |||
6.5.1.2 | FS_eANL_WoP#2 |   | ||||||||||
6.5.1.3 | FS_eANL_WoP#3 | S5‑223255 | pCR 28.910 Add key issue for autonomous network level for 5GC NF deployment | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑223566 | |
S5‑223566 | pCR 28.910 Add key issue for autonomous network level for 5GC NF deployment | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑223255 | |||
S5‑223256 | pCR 28.910 Add key issue for autonomous network level for 5GC network disaster recovery | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑223322 | pCR TR 28.910 Update the key issue of autonomous network level for RAN energy saving scenario | Huawei, AsiaInfo, China Mobile | pCR | Approval | Yes |
Yes
| revised | No | S5‑223567 | |||
S5‑223567 | pCR TR 28.910 Update the key issue of autonomous network level for RAN energy saving scenario | Huawei, AsiaInfo, China Mobile | pCR | Approval | Yes |
Yes
| approved | No | S5‑223322 | |||
S5‑223426 | pCR TR 28.910 Add autonomous network level for service experience optimization | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
6.5.1.4 | FS_eANL_WoP#4 |   | ||||||||||
6.5.2 | Study on evaluation of autonomous network levels |   | ||||||||||
6.5.2.1 | FS_ANLEVA_WoP#1 | S5‑223319 | pCR 28.909 Add key issue of dimensions for autonomous network levels | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||
S5‑223320 | pCR TR 28.909 Add key issues of generic methodology for autonomous network levels evaluation | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑223325 | pCR TS 28.909 Add general process of evaluating the autonomous network level | Huawei,China Mobile | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑223337 | pCR 28.909 Add new Key Issue determine evaluated object of autonomous | AsiaInfo Technologies Inc | pCR | Approval | Yes |
Yes
| noted | No | ||||
6.5.2.2 | FS_ANLEVA_WoP#2 | S5‑223324 | pCR TR 28.909 Add key issues for KEI and process of autonomous network levels evaluation for network optimization | Huawei,China Mobile | pCR | Approval | Yes |
Yes
| noted | No | ||
6.5.2.3 | FS_ANLEVA_WoP#3 |   | ||||||||||
6.5.2.4 | FS_ANLEVA_WoP#4 |   | ||||||||||
6.5.3 | Study on enhanced intent driven management services for mobile networks | S5‑223660 | Latest draft TR 28.912 | Huawei | draft TR | Approval | Yes |
Yes
| approved | No | ||
6.5.3.1 | FS_eIDMS_MN_WoP#1 | S5‑223257 | pCR TR 28.912 add key issues for 5GC intent expectation | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑223568 | |
S5‑223568 | pCR TR 28.912 add key issues for 5GC intent expectation | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑223257 | |||
S5‑223328 | pCR TR 28.912 Add potential solutions for RAN energy saving to clause 4.1.2 | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑223569 | |||
S5‑223569 | pCR TR 28.912 Add potential solutions for RAN energy saving to clause 4.1.2 | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑223328 | |||
6.5.3.2 | FS_eIDMS_MN_WoP#2 |   | ||||||||||
6.5.3.3 | FS_eIDMS_MN_WoP#3 | S5‑223326 | pCR TR 28.912 add key issue for missing solution for radio service intent expectation | Huawei,Deutsche Telekom | pCR | Approval | Yes |
Yes
| revised | No | S5‑223570 | |
S5‑223570 | pCR TR 28.912 add key issue for missing solution for radio service intent expectation | Huawei,Deutsche Telekom | pCR | Approval | Yes |
Yes
| approved | No | S5‑223326 | |||
S5‑223327 | pCR TR 28.912 add key issue for enhancement of radio network intent expectation | Huawei,Deutsche Telekom | pCR | Approval | Yes |
Yes
| revised | No | S5‑223571 | |||
S5‑223571 | pCR TR 28.912 add key issue for enhancement of radio network intent expectation | Huawei,Deutsche Telekom | pCR | Approval | Yes |
Yes
| approved | No | S5‑223327 | |||
6.5.3.4 | FS_eIDMS_MN_WoP#4 |   | ||||||||||
6.5.4 | Study on intent-driven management for network slicing | S5‑223661 | Latest draft TR 28.836 | Ericsson | draft TR | Approval | Yes |
Yes
| approved | No | ||
6.5.4.1 | FS_NETSLICE_IDMS_WoP#1 | S5‑223258 | pCR 28.836 Add concept of service profile and slice profile | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑223572 | |
S5‑223572 | pCR 28.836 Add concept of service profile and slice profile | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑223258 | |||
S5‑223259 | pCR 28.836 Add use case of network slicing allocation | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑223573 | |||
S5‑223573 | pCR 28.836 Add use case of network slicing allocation | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑223259 | |||
S5‑223260 | pCR 28.836 Add key issue of network slice life cycle management | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑223574 | |||
S5‑223574 | pCR 28.836 Add key issue of network slice life cycle management | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑223260 | |||
S5‑223261 | pCR 28.836 Add key issue of network slice service assurance | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑223575 | |||
S5‑223575 | pCR 28.836 Add key issue of network slice service assurance | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑223261 | |||
6.5.4.2 | FS_NETSLICE_IDMS_WoP#2 |   | ||||||||||
6.5.4.3 | FS_NETSLICE_IDMS_WoP#3 |   | ||||||||||
6.5.4.4 | FS_NETSLICE_IDMS_WoP#4 |   | ||||||||||
6.5.4.5 | FS_NETSLICE_IDMS_WoP#5 |   | ||||||||||
6.5.5 | Study on AI/ ML management | S5‑223662 | Latest draft TR 28.908 | Intel | draft TR | Approval | Yes |
Yes
| approved | No | ||
6.5.5.1 | FS_AIML_MGMT_WoP#1 | S5‑223347 | pCR 28.908 Add use case on AI/ML model performance | China Mobile E-Commerce Co. | pCR | Approval | Yes |
Yes
| revised | No | S5‑223576 | |
S5‑223576 | pCR 28.908 Add use case on AI/ML model performance | China Mobile E-Commerce Co. | pCR | Approval | Yes |
Yes
| approved | No | S5‑223347 | |||
S5‑223384 | Rel-18 pCR TR 28.908 Add AIML training workflow and deployment scenarios for AI-ML | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑223488 | pCR 28.908 Add AI-ML workflow for 5GS | Intel, NEC | pCR | Approval | Yes |
Yes
| noted | No | ||||
6.5.5.2 | FS_AIML_MGMT_WoP#2 | S5‑223489 | pCR 28.908 Add use case on AI-ML model validation | Intel, NEC | pCR | Approval | Yes |
Yes
| noted | No | ||
6.5.5.3 | FS_AIML_MGMT_WoP#3 |   | ||||||||||
6.5.5.4 | FS_AIML_MGMT_WoP#4 | S5‑223385 | Rel-18 pCR TR 28.908 Add Key Issue of AIML management for model deployment | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||
S5‑223499 | pCR 28.908 Add use case on AI/ML model deployment | CATT | pCR | Approval | Yes |
Yes
| noted | No | ||||
6.5.5.5 | FS_AIML_MGMT_WoP#5 |   | ||||||||||
6.5.5.6 | FS_AIML_MGMT_WoP#6 |   | ||||||||||
6.5.5.7 | FS_AIML_MGMT_WoP#7 |   | ||||||||||
6.5.5.8 | FS_AIML_MGMT_WoP#8 |   | ||||||||||
6.5.5.9 | FS_AIML_MGMT_WoP#9 |   | ||||||||||
6.5.5.10 | FS_AIML_MGMT_WoP#10 |   | ||||||||||
6.5.6 | Study on Enhancement of the management aspects related to NWDAF | S5‑223663 | Latest draft TR 28.864 | China Telecom | draft TR | Approval | Yes |
Yes
| approved | No | ||
6.5.6.1 | FS_MANWDAF_WoP#1 |   | ||||||||||
6.5.6.2 | FS_MANWDAF_WoP#2 | S5‑223408 | pCR 28.864 New KI about performance metrics of NWDAF on data collection aspect | China Telecom Corporation Ltd. | pCR | Approval | Yes |
Yes
| revised | No | S5‑223587 | |
S5‑223587 | pCR 28.864 New KI about performance metrics of NWDAF on data collection aspect | China Telecom Corporation Ltd. | pCR | Approval | Yes |
Yes
| approved | No | S5‑223408 | |||
S5‑223424 | pCR 28.864 New KI about performance metrics of NWDAF on Efficiency Aspect | China Telecom Corporation Ltd. | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑223455 | pCR 28.864 Add potential solution for KI#1 | Chinatelecom Cloud | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑223456 | pCR 28.864 Add potential solution for KI#2 | Chinatelecom Cloud | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑223458 | pCR 28.864 Add potential solution for KI#3 | Chinatelecom Cloud | pCR | Approval | Yes |
Yes
| revised | No | S5‑223578 | |||
S5‑223578 | pCR 28.864 Add potential solution for KI#3 | Chinatelecom Cloud | pCR | Approval | Yes |
Yes
| approved | No | S5‑223458 | |||
S5‑223459 | pCR 28.864 New key issue for the performance management of the NWDAF on the result aspect | Chinatelecom Cloud | pCR | Approval | Yes |
Yes
| noted | No | ||||
6.5.7 | Study on Fault Supervision Evolution |   | ||||||||||
6.5.7.1 | FS_FSEV_WoP#1 | S5‑223398 | pCR TR 28.830 Add framework of FSEV | Huawei, CMCC | pCR | Approval | Yes |
Yes
| noted | No | ||
S5‑223411 | pCR TR 28.830 Add background | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑223412 | pCR TR 28.830 Add relation description with existing MnS | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
6.5.7.2 | FS_FSEV_WoP#2 | S5‑223413 | pCR TR 28.830 Add description of key issue service outage | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||
S5‑223414 | pCR TR 28.830 Add description of key issue performance degradation | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑223415 | pCR TR 28.830 Add description of key issue 5GC service failure prediction | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑223416 | pCR TR 28.830 Add solution of key issue service outage | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑223417 | pCR TR 28.830 Add solution of key issue performance degradation | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑223418 | pCR TR 28.830 Add solution of key issue 5GC service failure prediction | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
6.5.7.3 | FS_FSEV_WoP#3 |   | ||||||||||
6.5.8 | Study on Enhancement of service based management architecture | S5‑223664 | Latest draft TR 28.925 | Huawei | draft TR | Approval | Yes |
Yes
| approved | No | ||
6.5.8.1 | FS_eSBMA_WoP#1 | S5‑223333 | pCR TR 28.925 Add issue on illustration of using MnS in management reference model in TS 32.101 | HuaWei Technologies Co., Ltd | pCR | Yes |
Yes
| revised | No | S5‑223579 | ||
S5‑223579 | pCR TR 28.925 Add issue on illustration of using MnS in management reference model in TS 32.101 | HuaWei Technologies Co., Ltd | pCR | - | Yes |
Yes
| approved | No | S5‑223333 | |||
S5‑223434 | Add key issue requirements of management service discovery | China Unicom | pCR | Approval | Yes |
Yes
| revised | No | S5‑223580 | |||
S5‑223580 | Add key issue requirements of management service discovery | China Unicom | pCR | Approval | Yes |
Yes
| noted | No | S5‑223434 | |||
6.5.8.2 | FS_eSBMA_WoP#2 | S5‑223334 | pCR TR 28.925 Add issue on analysis on IRP specifications needs to support SBMA | HuaWei Technologies Co., Ltd | pCR | Yes |
Yes
| revised | No | S5‑223581 | ||
S5‑223581 | pCR TR 28.925 Add issue on analysis on IRP specifications needs to support SBMA | HuaWei Technologies Co., Ltd | pCR | - | Yes |
Yes
| approved | No | S5‑223334 | |||
6.5.8.3 | FS_eSBMA_WoP#3 |   | ||||||||||
6.5.8.4 | FS_eSBMA_WoP#4 |   | ||||||||||
6.5.8.5 | FS_eSBMA_WoP#5 |   | ||||||||||
6.5.8.6 | FS_eSBMA_WoP#6 |   | ||||||||||
6.5.9 | Study on Basic SBMA enabler enhancements | S5‑223665 | Latest draft TR 28.831 | Nokia | draft TR | Approval | Yes |
Yes
| approved | No | ||
6.5.9.1 | FS_eSBMAe_WoP#1 |   | ||||||||||
6.5.9.2 | FS_eSBMAe_WoP#2 |   | ||||||||||
6.5.9.3 | FS_eSBMAe_WoP#3 |   | ||||||||||
6.5.9.4 | FS_eSBMAe_WoP#4 | S5‑223373 | Rel-18 pCR 28.831 Improve description of current situation for key issue 2 (Targeted notification subscription) | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑223582 | |
S5‑223582 | Rel-18 pCR 28.831 Improve description of current situation for key issue 2 (Targeted notification subscription) | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑223373 | |||
S5‑223374 | Rel-18 pCR 28.831 Improve analysis and potential requirements for key issue 2 (Targeted notification subscription) | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑223376 | Rel-18 pCR 28.831 Add potential solution for key issue 2 (Targeted notification subscription) | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
6.5.9.5 | FS_eSBMAe_WoP#5 |   | ||||||||||
6.5.9.6 | FS_eSBMAe_WoP#6 |   | ||||||||||
6.5.9.7 | FS_eSBMAe_WoP#7 |   | ||||||||||
6.5.9.8 | FS_eSBMAe_WoP#8 |   | ||||||||||
6.5.9.9 | FS_eSBMAe_WoP#9 |   | ||||||||||
6.5.9.10 | FS_eSBMAe_WoP#10 |   | ||||||||||
6.5.10 | Study on Management Aspects of URLLC | S5‑223727 | Latest draft TR 28.832 | China Unicom | draft TR | Approval | Yes |
Yes
| approved | No | ||
6.5.10.1 | FS_URLLC_Mgt_WoP#1 |   | ||||||||||
6.5.10.2 | FS_URLLC_Mgt_WoP#2 | S5‑223367 | Add candidates for study of feature management | China Unicom | pCR | Approval | Yes |
Yes
| approved | No | ||
6.5.10.3 | FS_URLLC_Mgt_WoP#3 | S5‑223368 | Add Key Issue on the Performance measurements related to URLLC | China Unicom | pCR | Approval | Yes |
Yes
| revised | No | S5‑223593 | |
S5‑223593 | Add Key Issue on the Performance measurements related to URLLC | China Unicom | pCR | Approval | Yes |
Yes
| noted | No | S5‑223368 | |||
6.5.10.4 | FS_URLLC_Mgt_WoP#4 |   | ||||||||||
6.5.11 | Study on Management Aspect of 5GLAN | S5‑223728 | Latest draft TR 28.833 | China mobile | draft TR | Approval | Yes |
Yes
| approved | No | ||
6.5.11.1 | FS_5GLAN_Mgt_WoP#1 | S5‑223339 | pCR TR 28.833 Change TR structure | China Mobile E-Commerce Co. | pCR | Approval | Yes |
Yes
| revised | No | S5‑223594 | |
S5‑223594 | pCR TR 28.833 Change TR structure | China Mobile E-Commerce Co. | pCR | Approval | Yes |
Yes
| approved | No | S5‑223339 | |||
S5‑223340 | Add use case1 for 5G VN group data management of FS_5GLAN_Mgt | China Mobile E-Commerce Co. | pCR | Approval | Yes |
Yes
| revised | No | S5‑223595 | |||
S5‑223595 | Add use case1 for 5G VN group data management of FS_5GLAN_Mgt | China Mobile E-Commerce Co. | pCR | Approval | Yes |
Yes
| approved | No | S5‑223340 | |||
S5‑223341 | Add use case2 for PDU Session management of FS_5GLAN_Mgt | China Mobile E-Commerce Co. | pCR | Approval | Yes |
Yes
| revised | No | S5‑223596 | |||
S5‑223596 | Add use case2 for PDU Session management of FS_5GLAN_Mgt | China Mobile E-Commerce Co. | pCR | Approval | Yes |
Yes
| approved | No | S5‑223341 | |||
S5‑223342 | Add use case3 for user plane handing of FS_5GLAN_Mgt | China Mobile E-Commerce Co. | pCR | Approval | Yes |
Yes
| revised | No | S5‑223597 | |||
S5‑223597 | Add use case3 for user plane handing of FS_5GLAN_Mgt | China Mobile E-Commerce Co. | pCR | Approval | Yes |
Yes
| approved | No | S5‑223342 | |||
S5‑223343 | Add use case4 for 5G VN performance measurement management of FS_5GLAN_Mgt | China Mobile E-Commerce Co. | pCR | Approval | Yes |
Yes
| revised | No | S5‑223598 | |||
S5‑223598 | Add use case4 for 5G VN performance measurement management of FS_5GLAN_Mgt | China Mobile E-Commerce Co. | pCR | Approval | Yes |
Yes
| approved | No | S5‑223343 | |||
S5‑223344 | Add use case5 for 5G VN group end-to-end network KPIS management of FS_5GLAN_Mgt | China Mobile E-Commerce Co. | pCR | Approval | Yes |
Yes
| revised | No | S5‑223599 | |||
S5‑223599 | Add use case5 for 5G VN group end-to-end network KPIS management of FS_5GLAN_Mgt | China Mobile E-Commerce Co. | pCR | Approval | Yes |
Yes
| approved | No | S5‑223344 | |||
6.5.11.2 | FS_5GLAN_Mgt_WoP#2 |   | ||||||||||
6.5.11.3 | FS_5GLAN_Mgt_WoP#3 |   | ||||||||||
6.5.11.4 | FS_5GLAN_Mgt_WoP#4 |   | ||||||||||
6.5.12 | Study on Management of Cloud Native Virtualized Network Functions | S5‑223729 | Latest draft TR 28.834 | China Mobile | draft TR | Approval | Yes |
Yes
| approved | No | ||
6.5.12.1 | FS_MCVNF_WoP#1 | S5‑223354 | TR 28.834 Initial Skeleton v0.0.0 | China Mobile Com. Corporation | draft TR | Approval | Yes |
Yes
| approved | No | ||
S5‑223355 | pCR 28.834 Add TR structure | China Mobile Com. Corporation | pCR | Approval | Yes |
Yes
| revised | No | S5‑223600 | |||
S5‑223600 | pCR 28.834 Add TR structure | China Mobile Com. Corporation | pCR | Approval | Yes |
Yes
| approved | No | S5‑223355 | |||
S5‑223356 | pCR 28.834 Add scope | China Mobile Com. Corporation | pCR | Approval | Yes |
Yes
| revised | No | S5‑223601 | |||
S5‑223601 | pCR 28.834 Add scope | China Mobile Com. Corporation | pCR | Approval | Yes |
Yes
| approved | No | S5‑223356 | |||
S5‑223437 | Discussion paper on cloud-native NF deployment | Microsoft Europe SARL | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑223444 | pCR 28.834 Add use case on cloud-native VNF deployment | Microsoft Europe SARL | pCR | Approval | Yes |
Yes
| noted | No | ||||
6.5.12.2 | FS_MCVNF_WoP#2 |   | ||||||||||
6.5.12.3 | FS_MCVNF_WoP#3 |   | ||||||||||
6.5.13 | Study on Management Aspects of 5G MOCN Network Sharing Phase2 | S5‑223730 | Latest draft TR 28.835 | China Unicom | draft TR | Approval | Yes |
Yes
| approved | No | ||
6.5.13.1 | FS_MANS_ph2_WoP#1 | S5‑223352 | Add Concepts and overview | China Unicom | pCR | Approval | Yes |
Yes
| revised | No | S5‑223602 | |
S5‑223602 | Add Concepts and overview | China Unicom | pCR | Approval | Yes |
Yes
| approved | No | S5‑223352 | |||
S5‑223353 | Add key issue management requirement between MOP-NM and MOP-SR-DM | China Unicom | pCR | Approval | Yes |
Yes
| revised | No | S5‑223603 | |||
S5‑223603 | Add key issue management requirement between MOP-NM and MOP-SR-DM | China Unicom | pCR | Approval | Yes |
Yes
| approved | No | S5‑223353 | |||
6.5.13.2 | FS_MANS_ph2_WoP#2 | S5‑223363 | Add key issue service-based management architecture for MOCN | China Unicom | pCR | Approval | Yes |
Yes
| revised | No | S5‑223604 | |
S5‑223604 | Add key issue service-based management architecture for MOCN | China Unicom | pCR | Approval | Yes |
Yes
| approved | No | S5‑223363 | |||
S5‑223365 | Add potential solution for performance measurements without PLMN ID at NRcellCU | China Unicom | pCR | Approval | Yes |
Yes
| noted | No | ||||
6.5.13.3 | FS_MANS_ph2_WoP#3 |   | ||||||||||
6.5.14 | Study on continuous integration continuous delivery support for 3GPP NFs | S5‑223731 | Latest draft TR 28.819 | China Mobile | draft TR | Approval | Yes |
Yes
| approved | No | ||
6.5.14.1 | FS_CICDNS_WoP#1 | S5‑223262 | pCR 28.819 Add process for multiple vendor case | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑223605 | |
S5‑223605 | pCR 28.819 Add process for multiple vendor case | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑223262 | |||
S5‑223263 | pCR 28.819 Add description of deployment options | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑223606 | |||
S5‑223606 | pCR 28.819 Add description of deployment options | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑223263 | |||
S5‑223264 | pCR 28.819 Update text for editorial issues | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑223607 | |||
S5‑223607 | pCR 28.819 Update text for editorial issues | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑223264 | |||
S5‑223265 | pCR 28.819 Update text for vendor feedback use case | Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑223392 | pCR 28.819 Proposed overall process | China Mobile Com. Corporation, Lenovo, Motorola Mobility | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑223592 | Presentation sheet for FS_CICDNS | China Mobile | TS or TR cover | Approval | Yes |
Yes
| approved | No | ||||
6.5.14.2 | FS_CICDNS_WoP#2 |   | ||||||||||
6.5.15 | Study on Management of Trace/MDT phase 2 | S5‑223732 | Latest draft TR 28.837 | Nokia | draft TR | Approval | Yes |
Yes
| approved | No | ||
6.5.15.1 | FS_5GMDT_Ph2_WoP#1 | S5‑223403 | Rel-18 pCR 28.837 Reporting of Collected Management Data | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||
6.5.15.2 | FS_5GMDT_Ph2_WoP#2 | S5‑223184 | Rel-18 pCR 28.837 Gaps in Signalling Based Trace Activation | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||
S5‑223404 | Rel-18 pCR 28.837 Name Containment in case of Handover for Signalling Based Trace Activation | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
6.5.15.3 | FS_5GMDT_Ph2_WoP#3 |   | ||||||||||
6.5.15.4 | FS_5GMDT_Ph2_WoP#4 |   | ||||||||||
6.5.15.5 | FS_5GMDT_Ph2_WoP#5 |   | ||||||||||
6.5.15.6 | FS_5GMDT_Ph2_WoP#6 |   | ||||||||||
6.5.15.7 | FS_5GMDT_Ph2_WoP#7 |   | ||||||||||
6.5.15.8 | FS_5GMDT_Ph2_WoP#8 |   | ||||||||||
6.5.16 | Study on YANG PUSH |   | ||||||||||
6.5.16.1 | FS_YANG_WoP#1 |   | ||||||||||
6.5.16.2 | FS_YANG_WoP#2 |   | ||||||||||
6.5.16.3 | FS_YANG_WoP#3 |   | ||||||||||
6.5.16.4 | FS_YANG_WoP#4 |   | ||||||||||
6.5.16.5 | FS_YANG_WoP#5 |   | ||||||||||
6.5.17 | Study on enhancement of management of non-public networks | S5‑223733 | Latest draft TR 28.907 | Huawei | draft TR | Approval | Yes |
Yes
| approved | No | ||
6.5.17.1 | FS_OAM_eNPN_WoP#1 |   | ||||||||||
6.5.17.2 | FS_OAM_eNPN_WoP#2 | S5‑223236 | pCR 28.907 Potential solution for KI#2 | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑223608 | |
S5‑223608 | pCR 28.907 Potential solution for KI#2 | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑223236 | |||
6.5.17.3 | FS_OAM_eNPN_WoP#3 | S5‑223234 | pCR 28.907 Key Issue on SLA monitoring and evaluation | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑223609 | |
S5‑223609 | pCR 28.907 Key Issue on SLA monitoring and evaluation | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑223234 | |||
S5‑223235 | pCR 28.907 Potential solution for KI#1 | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑223610 | |||
S5‑223610 | pCR 28.907 Potential solution for KI#1 | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑223235 | |||
6.5.17.4 | FS_OAM_eNPN_WoP#4 |   | ||||||||||
6.5.18 | Study on new aspects of EE for 5G networks Phase 2 |   | ||||||||||
6.5.18.1 | FS_EE5G_Ph2_WoP#1 |   | ||||||||||
6.5.18.2 | FS_EE5G_Ph2_WoP#2 |   | ||||||||||
6.5.19 | Study on Network and Service Operations for Energy Utilities | S5‑223734 | Latest draft TR 28.829 | Samsung | draft TR | Approval | Yes |
Yes
| approved | No | ||
6.5.19.1 | FS_NSOEU_WoP#1 |   | ||||||||||
6.5.19.2 | FS_NSOEU_WoP#2 | S5‑223390 | pCR TR 28.829 Business use case - MNO provides performance info | Samsung, EUTC, BMWK, Vodafone | pCR | Approval | Yes |
Yes
| revised | No | S5‑223611 | |
S5‑223611 | pCR TR 28.829 Business use case - MNO provides performance info | Samsung, EUTC, BMWK, Vodafone | pCR | Approval | Yes |
Yes
| approved | No | S5‑223390 | |||
6.5.19.3 | FS_NSOEU_WoP#3 |   | ||||||||||
6.5.19.4 | FS_NSOEU_WoP#4 |   | ||||||||||
6.5.19.5 | FS_NSOEU_WoP#5 | S5‑223389 | pCR TR 28.829 Business use case - Utility provides performance and failure info | Samsung, EUTC, BMWK, Vodafone | pCR | Approval | Yes |
Yes
| revised | No | S5‑223612 | |
S5‑223612 | pCR TR 28.829 Business use case - Utility provides performance and failure info | Samsung, EUTC, BMWK, Vodafone | pCR | Approval | Yes |
Yes
| approved | No | S5‑223389 | |||
6.5.19.6 | FS_NSOEU_WoP#6 |   | ||||||||||
6.5.19.7 | FS_NSOEU_WoP#7 |   | ||||||||||
6.5.19.8 | FS_NSOEU_WoP#8 | S5‑223387 | pCR TR 28.829 Business use case - Energy outage coordination | Samsung, EUTC, BMWK, Vodafone | pCR | Approval | Yes |
Yes
| revised | No | S5‑223613 | |
S5‑223613 | pCR TR 28.829 Business use case - Energy outage coordination | Samsung, EUTC, BMWK, Vodafone | pCR | Approval | Yes |
Yes
| approved | No | S5‑223387 | |||
6.5.19.9 | FS_NSOEU_WoP#9 |   | ||||||||||
6.5.19.10 | FS_NSOEU_WoP#10 |   | ||||||||||
6.5.19.11 | FS_NSOEU_WoP#11 |   | ||||||||||
6.5.19.12 | FS_NSOEU_WoP#12 |   | ||||||||||
6.5.19.13 | FS_NSOEU_WoP#13 |   | ||||||||||
6.5.20 | Study on Key Quality Indicators (KQIs)for 5G service experience | S5‑223751 | Latest draft TR 28.863 | Huawei | draft TR | Approval | Yes |
Yes
| approved | No | ||
6.5.20.1 | FS_KQI_5G_WoP#1 |   | ||||||||||
6.5.20.2 | FS_KQI_5G_WoP#2 | S5‑223436 | pCR TR 28.863 Key Issue#1 Definition of KQI | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑223741 | |
S5‑223741 | pCR TR 28.863 Key Issue#1 Definition of KQI | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑223436 | |||
S5‑223443 | pCR TR 28.863 Key Issue#3 Solution of Key influencing factors for service experience of Video Uploading | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑223445 | pCR TR 28.863 Key Issue#3 Solution of KQIs for Video Uploading | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑223446 | pCR TR 28.863 Key Issue#3 Evaluation of KQI for Video Uploading | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑223447 | pCR TR 28.863 Key Issue#3 Solution of related KPIs which will influence the KQIs for Video Uploading | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
6.5.20.3 | FS_KQI_5G_WoP#3 | S5‑223448 | pCR TR 28.863 Key Issue#4 Solution of Key influencing factors for Remote Controlling | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||
S5‑223449 | pCR TR 28.863 Key Issue#4 Solution of KQIs for Remote Controlling | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑223450 | pCR TR 28.863 Key Issue#4 Solution of related KPIs which will influence the KQIs for remote controlling | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
6.5.20.4 | FS_KQI_5G_WoP#4 |   | ||||||||||
6.5.20.5 | FS_KQI_5G_WoP#5 |   | ||||||||||
6.5.21 | Study on Deterministic Communication Service Assurance | S5‑223735 | Latest draft TR 28.865 | Huawei | draft TR | discussion | Yes |
Yes
| approved | No | ||
6.5.21.1 | FS_DCSA_WoP#1 |   | ||||||||||
6.5.21.2 | FS_DCSA_WoP#2 | S5‑223463 | pCR TR 28.865 Add framework of FS_DCSA | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑223614 | |
S5‑223614 | pCR TR 28.865 Add framework of FS_DCSA | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑223463 | |||
S5‑223466 | pCR TR 28.865 Add key issue provisioning of network functions related to DCSA | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑223615 | |||
S5‑223615 | pCR TR 28.865 Add key issue provisioning of network functions related to DCSA | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑223466 | |||
6.5.21.3 | FS_DCSA_WoP#3 |   | ||||||||||
6.5.21.4 | FS_DCSA_WoP#4 | S5‑223467 | pCR TR 28.865 Add key issue service assurance for video monitoring | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑223616 | |
S5‑223616 | pCR TR 28.865 Add key issue service assurance for video monitoring | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑223467 | |||
S5‑223469 | pCR TR 28.865 Add key issue service assurance for PLC control | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑223617 | |||
S5‑223617 | pCR TR 28.865 Add key issue service assurance for PLC control | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑223469 | |||
S5‑223470 | pCR TR 28.865 Add solution service assurance for video monitoring | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑223618 | |||
S5‑223618 | pCR TR 28.865 Add solution service assurance for video monitoring | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑223470 | |||
S5‑223472 | pCR TR 28.865 Add solution service assurance for PLC control | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑223619 | |||
S5‑223619 | pCR TR 28.865 Add solution service assurance for PLC control | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑223472 | |||
6.5.21.5 | FS_DCSA_WoP#5 |   | ||||||||||
6.5.22 | Study on management aspects of network slice management capability exposure | S5‑223736 | Latest draft TR 28.824 | Alibaba | draft TR | Approval | Yes |
Yes
| approved | No | ||
6.5.22.1 | FS_NSCE_WoP#1 | S5‑223230 | Make descriptions in issues and gaps more uniform | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑223620 | |
S5‑223620 | Make descriptions in issues and gaps more uniform | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑223230 | |||
S5‑223237 | pCR 28.824 Add new requirements related to exposure interface via OSS | Huawei, Deutsche Telekom | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑223238 | pCR 28.824 Update use case exposure of network slice as a service | Huawei, Deutsche Telekom | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑223242 | Update position and add solution for direct MnS exposure | Lenovo Information Technology | pCR | Yes |
Yes
| revised | No | S5‑223621 | ||||
S5‑223621 | Update position and add solution for direct MnS exposure | Lenovo Information Technology | pCR | - | Yes |
Yes
| approved | No | S5‑223242 | |||
S5‑223266 | pCR 28.824 Add scenario of management exposure | China Southern Power Grid, Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
6.5.22.2 | FS_NSCE_WoP#2 |   | ||||||||||
6.5.22.3 | FS_NSCE_WoP#3 | S5‑223123 | Update to solution regarding CAPIF based management capability | Alibaba Group | pCR | Approval | Yes |
Yes
| revised | No | S5‑223622 | |
S5‑223622 | Update to solution regarding CAPIF based management capability | Alibaba Group | pCR | Approval | Yes |
Yes
| approved | No | S5‑223123 | |||
S5‑223208 | pCR 28.824 Solution for Network slice management capability exposure | Samsung R&D Institute India | pCR | Agreement | Yes |
Yes
| revised | No | S5‑223624 | |||
S5‑223624 | pCR 28.824 Solution for Network slice management capability exposure | Samsung R&D Institute India | pCR | Agreement | Yes |
Yes
| approved | No | S5‑223208 | |||
S5‑223229 | Add procedure for consumption of exposed MnS after service order is completed | Ericsson LM, Deutsche Telekom | pCR | Approval | Yes |
Yes
| revised | No | S5‑223625 | |||
S5‑223625 | Add procedure for consumption of exposed MnS after service order is completed | Ericsson LM, Deutsche Telekom | pCR | Approval | Yes |
Yes
| approved | No | S5‑223229 | |||
S5‑223231 | Discussion paper on filtering, enrichment and converting of management information | Ericsson LM, Deutsche Telekom | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑223744 | |||
S5‑223744 | Discussion paper on filtering, enrichment and converting of management information | Ericsson LM, Deutsche Telekom | discussion | Endorsement | Yes |
Yes
| noted | No | S5‑223231 | |||
S5‑223241 | pCR 28.824 Add note on possible charging impact | Lenovo Information Technology | pCR | Yes |
Yes
| revised | No | S5‑223623 | ||||
S5‑223623 | pCR 28.824 Add note on possible charging impact | Lenovo Information Technology | pCR | - | Yes |
Yes
| approved | No | S5‑223241 | |||
S5‑223378 | pCR 28.824 add procedure of MnS exposure via CAPIF | AsiaInfo | pCR | Approval | Yes |
Yes
| noted | No | ||||
6.5.22.4 | FS_NSCE_WoP#4 |   | ||||||||||
6.5.22.5 | FS_NSCE_WoP#5 |   | ||||||||||
6.5.23 | Study on alignment with ETSI MEC for Edge computing management | S5‑223737 | Latest draft TR 28.903 | Huawei | draft TR | discussion | Yes |
Yes
| approved | No | ||
6.5.23.1 | FS_MEC_ECM_WoP#1 | S5‑223267 | pCR 28.903 background information for ETSI MEC | Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||
S5‑223268 | pCR 28.903 adding key issue for package management | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑223269 | pCR 28.903 adding key issue for EAS LCM management | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
6.5.23.2 | FS_MEC_ECM_WoP#2 |   | ||||||||||
6.6 | Rel-17 Operations, Administration, Maintenance and Provisioning (OAM&P) |   | ||||||||||
6.6.1 | Enhancement of QoE Measurement Collection | S5‑223431 | Rel-17 CR 28.623 Add QMC job, stage 3 (YANG) | Ericsson Inc. | CR | Approval | Yes |
Yes
| not pursued | No | ||
S5‑223506 | Alignment of 28404 with 28405 | Ericsson Limited | CR | Agreement | Yes |
Yes
| revised | No | S5‑223746 | |||
S5‑223746 | Alignment of 28404 with 28405 | Ericsson Limited | CR | Agreement | Yes |
Yes
| agreed | No | S5‑223506 | |||
S5‑223509 | Adding Signaling Based Activation for NR | Ericsson Limited | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑223510 | Handling QMC measurements at Handover for NR | Ericsson Limited | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑223511 | Adding QMCJob | Ericsson Limited | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑223512 | Attribute updates | Ericsson Limited | CR | Approval | Yes |
Yes
| revised | No | S5‑223747 | |||
S5‑223747 | Attribute updates | Ericsson Limited | CR | Approval | Yes |
Yes
| agreed | No | S5‑223512 | |||
6.6.2 | Management data collection control and discovery | S5‑223154 | Rel-17 Input to DraftCR 28.622 Enhancement and corrections for IOC "ManagementDataCollection" (stage 2) | Nokia, Nokia Shanghai Bell | other | Approval | Yes |
Yes
| revised | No | S5‑223626 | |
S5‑223626 | Rel-17 Input to DraftCR 28.622 Enhancement and corrections for IOC "ManagementDataCollection" (stage 2) | Nokia, Nokia Shanghai Bell | other | Approval | Yes |
Yes
| approved | No | S5‑223154 | |||
S5‑223174 | Rel-17 Input to draftCR 28.622 Add information about supported trace metrics (stage 2) | Nokia, Nokia Shanghai Bell | other | Approval | Yes |
Yes
| approved | No | ||||
S5‑223175 | Rel-17 Input to draftCR 28.623 Add information about supported trace metrics (stage 3) | Nokia, Nokia Shanghai Bell | other | Approval | Yes |
Yes
| approved | No | ||||
S5‑223176 | Rel-17 Input to draftCR 28.622 Reporting for IOC "ManagementDataCollection" (stage 2) | Nokia, Nokia Shanghai Bell | other | Approval | Yes |
Yes
| noted | No | ||||
S5‑223185 | Discussion on reporting for IOC "ManagementDataCollection" | Nokia, Nokia Shanghai Bell | discussion | Approval | Yes |
Yes
| noted | No | ||||
S5‑223427 | Rel-17 Input to DraftCR 28.623 Enhancement and corrections for IOC "ManagementDataCollection" (stage 3) | Nokia, Nokia Shanghai Bell | other | Approval | Yes |
Yes
| revised | No | S5‑223627 | |||
S5‑223627 | Rel-17 Input to DraftCR 28.623 Enhancement and corrections for IOC "ManagementDataCollection" (stage 3) | Nokia, Nokia Shanghai Bell | other | Approval | Yes |
Yes
| approved | No | S5‑223427 | |||
S5‑223428 | Rel-17 Input to DraftCR 28.623 Reporting for IOC "ManagementDataCollection" (stage 3) | Nokia, Nokia Shanghai Bell | other | Approval | Yes |
Yes
| noted | No | ||||
S5‑223588 | Rel-17 CR 28.622 Add stage 2 for management data collection and discovery | Nokia | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑223589 | Rel-17 CR 28.623 Add stage 3 for management data collection and discovery (OpenAPI definitions) | Nokia | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑223590 | Rel-17 CR 28.537 Add requirements for management data collection and discovery | Nokia | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑223657 | DraftCR for MADCOL TS 28.622 | Nokia | draftCR | discussion | Yes |
Yes
| approved | No | ||||
S5‑223658 | DraftCR for MADCOL TS 28.623 | Nokia | draftCR | Approval | Yes |
Yes
| approved | No | ||||
6.6.3 | Intent driven management service for mobile networks | S5‑223070 | Rel-17 pCR TS 28.312 OpenAPI file name and dependence change-intentNrm | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑223628 | |
S5‑223628 | Rel-17 pCR TS 28.312 OpenAPI file name and dependence change-intentNrm | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑223070 | |||
S5‑223071 | Rel-18 pCR TS 28.312 OpenAPI file name and dependence change-intentNrm | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑223321 | pCR 28.312 Update description of value DEGRADED in clause 6.2.1.3.6 | China Mobile, Huawei, Nokia | pCR | Approval | Yes |
Yes
| revised | No | S5‑223629 | |||
S5‑223629 | pCR 28.312 Update description of value DEGRADED in clause 6.2.1.3.6 | China Mobile, Huawei, Nokia | pCR | Approval | Yes |
Yes
| approved | No | S5‑223321 | |||
S5‑223329 | pCR TS 28.312 Rapporteur clean up | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑223630 | |||
S5‑223630 | pCR TS 28.312 Rapporteur clean up | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑223329 | |||
S5‑223330 | pCR TS 28.312 Rapporteur final udpate on stage3 | Huawei, Deutsche Telekom | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑223335 | add Service Support Expectation in clause 7.2.2 stage3 | AsiaInfo, Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑223633 | |||
S5‑223633 | add Service Support Expectation in clause 7.2.2 stage3 | AsiaInfo, Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑223335 | |||
S5‑223336 | update the stage 2 of Service Support Expectation | AsiaInfo,Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑223429 | Rel-18 pCR 28.312 Fix Create an Intent procedure numbering | Ericsson Inc. | pCR | Approval | Yes |
Yes
| revised | No | S5‑223631 | |||
S5‑223631 | Rel-18 pCR 28.312 Fix Create an Intent procedure numbering | Ericsson Inc. | pCR | Approval | Yes |
Yes
| approved | No | S5‑223429 | |||
S5‑223430 | Rel-18 pCR 28.312 Fix intentFulfillment attribute definition | Ericsson Inc. | pCR | Approval | Yes |
Yes
| revised | No | S5‑223632 | |||
S5‑223632 | Rel-18 pCR 28.312 Fix intentFulfillment attribute definition | Ericsson Inc. | pCR | Approval | Yes |
Yes
| approved | No | S5‑223430 | |||
S5‑223738 | Latest draft TS 28.312 | Huawei | draft TS | discussion | Yes |
Yes
| approved | No | ||||
6.6.4 | Enhanced Closed loop SLS Assurance | S5‑223239 | R17 Add disable list for a specific DN attribute of ACCL NRM | Lenovo, Ericsson | CR | Approval | Yes |
Yes
| revised | No | S5‑223634 | |
S5‑223634 | R17 Add disable list for a specific DN attribute of ACCL NRM | Lenovo, Ericsson | CR | Approval | Yes |
Yes
| agreed | No | S5‑223239 | |||
S5‑223494 | R17 CR for Stage 3 for enabledordisabled list | Lenovo Information Technology | CR | Yes |
Yes
| not pursued | No | |||||
6.6.5 | Enhancements of Management Data Analytics Service | S5‑223131 | Removing recommendations options | Nokia Germany | pCR | Approval | Yes |
Yes
| noted | No | ||
S5‑223210 | pCR 28.104 Handover Optimization | Samsung R&D Institute India | pCR | Agreement | Yes |
Yes
| revised | No | S5‑223748 | |||
S5‑223748 | pCR 28.104 Handover Optimization | Samsung R&D Institute India | pCR | Agreement | Yes |
Yes
| approved | No | S5‑223210 | |||
S5‑223270 | pCR TS 28.104 Add Alarm analytics solution-stage 2 | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑223271 | pCR TS 28.104 update EsRecommendationsOnUPF and EsRecommendationsOnNRcell | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑223635 | |||
S5‑223635 | pCR TS 28.104 update EsRecommendationsOnUPF and EsRecommendationsOnNRcell | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑223271 | |||
S5‑223272 | pCR TS 28.104 update TrafficProjections data type | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑223640 | |||
S5‑223640 | pCR TS 28.104 update TrafficProjections data type | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑223272 | |||
S5‑223273 | pCR 28.104 Add clause for energy saving analysis | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑223636 | |||
S5‑223636 | pCR 28.104 Add clause for energy saving analysis | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑223273 | |||
S5‑223274 | pCR 28.104 Editorial improvement | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑223637 | |||
S5‑223637 | pCR 28.104 Editorial improvement | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑223274 | |||
S5‑223275 | pCR 28.104 Rename tables for failure prediction analysis | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑223345 | PM-based and KPI-based analytics outputs | Nokia Germany | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑223346 | Adding MDA output IOC | Nokia Germany | pCR | Approval | Yes |
Yes
| revised | No | S5‑223641 | |||
S5‑223641 | Adding MDA output IOC | Nokia Germany | pCR | Approval | Yes |
Yes
| approved | No | S5‑223346 | |||
S5‑223349 | Stage 2 solution for paging analytics use case | Nokia, Nokia Shangai Bell, Samsung | pCR | Approval | Yes |
Yes
| revised | No | S5‑223750 | |||
S5‑223750 | Stage 2 solution for paging analytics use case | Nokia, Nokia Shangai Bell, Samsung | pCR | Approval | Yes |
Yes
| approved | No | S5‑223349 | |||
S5‑223350 | Update the paging use case description to indicate the geographical area-based and group of users based analytics | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑223366 | Rel-17 CR 28.532 Add alarm prediction solution (stage 2) | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑223370 | Rel-17 CR 28.532 Add alarm prediction solution (REST SS, OpenAPI definition) | Nokia, Nokia Shanghai Bell | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑223379 | Rel-17 pCR 28.104 Add MDA capability for handover optimization | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑223380 | Rel-17 pCR TS 28.105 Add AIML training attribute in case of AIML training initiated by producer | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑223646 | |||
S5‑223646 | Rel-17 pCR TS 28.105 Add AIML training attribute in case of AIML training initiated by producer | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑223380 | |||
S5‑223381 | Rel-17 pCR TS 28.104 add MDA analysis request and report generic workflow | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑223649 | |||
S5‑223649 | Rel-17 pCR TS 28.104 add MDA analysis request and report generic workflow | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑223381 | |||
S5‑223382 | Rel-17 pCR TS 28.105 Update the definition of performanceScore | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑223745 | |||
S5‑223745 | Rel-17 pCR TS 28.105 Update the definition of performanceScore | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑223382 | |||
S5‑223383 | Rel-17 pCR TS 28.105 Correct the attribute definitions of NRMs for AI-ML model training | Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑223394 | Add requirements for handling erroneous data & decisions | Nokia Italy | pCR | Approval | Yes |
Yes
| revised | No | S5‑223652 | |||
S5‑223652 | Add requirements for handling erroneous data & decisions | Nokia Italy | pCR | Approval | Yes |
Yes
| approved | No | S5‑223394 | |||
S5‑223395 | Add requirements for pre-processed event data for ML training | Nokia Italy | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑223396 | Add requirements for sandboxing ML solutions | Nokia Italy | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑223397 | MDA output for proactive coverage analytics | Nokia Italy | pCR | Approval | Yes |
Yes
| revised | No | S5‑223645 | |||
S5‑223645 | MDA output for proactive coverage analytics | Nokia Italy | pCR | Approval | Yes |
Yes
| approved | No | S5‑223397 | |||
S5‑223410 | enhance MDA information model | Nokia Italy | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑223461 | pCR draft TS28.104, v1.1.0 Rapporteur clean-up | NEC, Intel | pCR | Approval | Yes |
Yes
| revised | No | S5‑223638 | |||
S5‑223638 | pCR draft TS28.104, v1.1.0 Rapporteur clean-up | NEC, Intel | pCR | Approval | Yes |
Yes
| approved | No | S5‑223461 | |||
S5‑223471 | pCR 28.104 Add data type definitions | Intel | pCR | Approval | Yes |
Yes
| revised | No | S5‑223642 | |||
S5‑223642 | pCR 28.104 Add data type definitions | Intel | pCR | Approval | Yes |
Yes
| approved | No | S5‑223471 | |||
S5‑223473 | pCR 28.104 Enhance MDA NRM | Intel | pCR | Approval | Yes |
Yes
| revised | No | S5‑223643 | |||
S5‑223643 | pCR 28.104 Enhance MDA NRM | Intel | pCR | Approval | Yes |
Yes
| approved | No | S5‑223473 | |||
S5‑223474 | pCR 28.105 Update AI-ML NRM | Intel, NEC | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑223475 | pCR draft TS28.105, v1.1.0 Rapporteur clean-up | NEC, Intel | pCR | Approval | Yes |
Yes
| revised | No | S5‑223650 | |||
S5‑223650 | pCR draft TS28.105, v1.1.0 Rapporteur clean-up | NEC, Intel | pCR | Approval | Yes |
Yes
| approved | No | S5‑223475 | |||
S5‑223476 | pCR 28.105 Add stage 3 solution sets for AI-ML NRM | Intel | pCR | Approval | Yes |
Yes
| revised | No | S5‑223647 | |||
S5‑223647 | pCR 28.105 Add stage 3 solution sets for AI-ML NRM | Intel | pCR | Approval | Yes |
Yes
| approved | No | S5‑223476 | |||
S5‑223477 | pCR 28.104 Add stage 3 solution sets for MDA NRM | Intel | pCR | Approval | Yes |
Yes
| revised | No | S5‑223644 | |||
S5‑223644 | pCR 28.104 Add stage 3 solution sets for MDA NRM | Intel | pCR | Approval | Yes |
Yes
| approved | No | S5‑223477 | |||
S5‑223478 | pCR 28.104 Add file format definitions for MDA outputs | Intel | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑223479 | pCR 28.104 Add streaming data format for MDA outputs | Intel | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑223480 | Presentation of TS 28.104 for approval | Intel | TS or TR cover | Approval | Yes |
Yes
| revised | No | S5‑223639 | |||
S5‑223639 | Presentation of TS 28.104 for approval | Intel | TS or TR cover | Approval | Yes |
Yes
| approved | No | S5‑223480 | |||
S5‑223481 | Presentation of TS 28.105 for approval | Intel | TS or TR cover | Approval | Yes |
Yes
| approved | No | ||||
S5‑223482 | pCR draft TS28.104, add AI/ML optional support for MDA | NEC, Intel | pCR | Approval | Yes |
Yes
| revised | No | S5‑223648 | |||
S5‑223648 | pCR draft TS28.104, add AI/ML optional support for MDA | NEC, Intel | pCR | Approval | Yes |
Yes
| approved | No | S5‑223482 | |||
S5‑223484 | CR Rel-17 28.622 Generalize the ThresholdInfo data type | Intel | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑223485 | pCR draft TS28.104, add reporting MnS components | NEC, Intel | pCR | Approval | Yes |
Yes
| revised | No | S5‑223749 | |||
S5‑223749 | pCR draft TS28.104, add reporting MnS components | NEC, Intel | pCR | Approval | Yes |
Yes
| approved | No | S5‑223485 | |||
S5‑223487 | pCR draft TS28.105, updates to AI/ML NRM | NEC Europe Ltd | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑223492 | CR draft TS28.104, revisions to Network slice traffic prediction | NEC Europe Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑223651 | |||
S5‑223651 | CR draft TS28.104, revisions to Network slice traffic prediction | NEC Europe Ltd | pCR | Approval | Yes |
Yes
| approved | No | S5‑223492 | |||
S5‑223505 | pCR draft TS28.104, revisions to clause 7.3.2 obtaining MDA Output | NEC Europe Ltd | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑223739 | Latest draft TS 28.104 | Intel | draft TS | Approval | Yes |
Yes
| approved | No | ||||
S5‑223740 | Latest draft TS 28.105 | Intel | draft TS | Approval | Yes |
Yes
| approved | No | ||||
6.6.6 | Edge Computing Management | S5‑223040 | Rel-17 CR 28.538 Add the terminologies for PLMN and ECSP management systems | Intel Korea, Ltd. | CR | Approval | Yes |
Yes
| agreed | No | ||
S5‑223041 | Rel-17 CR 28.538 Add editorial changes | Intel Korea, Ltd. | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑223223 | Presentation of Specification TS 28.538 (Edge Computing Management) | Samsung R&D Institute India | TS or TR cover | Agreement | Yes |
Yes
| noted | No | ||||
S5‑223591 | Rel-17 CR 28.552 performance measurements for ECS - Service Provisioning | Samsung Electronics Benelux BV | CR | Agreement | Yes |
Yes
| agreed | No | ||||
6.6.7 | Access control for management service | S5‑223399 | Rel-17 TS28.532 enhance OpenAPI to support access control | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | ||
S5‑223400 | Rel-17 TS28.622 enhance NRM to support access control | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑223401 | Rel-17 TS28.623 enhance NRM to support access control Stage 3 | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑223402 | Rel-17 TS28.533 enhancement to support access control | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | ||||
6.6.8 | Network slice provisioning enhancement | S5‑223074 | Rel-17 CR TS28531 Update procedure of reservation and checking feasibility of network slice | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑223653 | |
S5‑223653 | Rel-17 CR TS28531 Update procedure of reservation and checking feasibility of network slice | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑223074 | |||
S5‑223212 | Rel-17 CR 28.531 Deleting service priority | Samsung R&D Institute India | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑223213 | Rel-17 CR 28.541 Network slice subnet provider capability IOC | Samsung R&D Institute India | CR | Agreement | Yes |
Yes
| revised | No | S5‑223742 | |||
S5‑223742 | Rel-17 CR 28.541 Network slice subnet provider capability IOC | Samsung R&D Institute India | CR | Agreement | Yes |
Yes
| agreed | No | S5‑223213 | |||
S5‑223216 | Rel-17 CR 28.531 Network slice subnet capabilities | Samsung R&D Institute India | CR | Agreement | Yes |
Yes
| revised | No | S5‑223743 | |||
S5‑223743 | Rel-17 CR 28.531 Network slice subnet capabilities | Samsung R&D Institute India | CR | Agreement | Yes |
Yes
| agreed | No | S5‑223216 | |||
S5‑223218 | Add asynchronous network slicing provisioning procedures | Ericsson LM, Deutsche Telekom | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑223219 | Rel-17 Work Item Exception for eNETSLICE_PRO | Samsung R&D Institute India | WI exception request | Agreement | Yes |
Yes
| noted | No | ||||
S5‑223220 | Add Job IOCs for asynchronous network slicing provisioning procedures | Ericsson LM, Deutsche Telekom | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑223243 | Rel-17 CR 28.531 adding procedure network service priority management | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑223654 | |||
S5‑223654 | Rel-17 CR 28.531 adding procedure network service priority management | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑223243 | |||
S5‑223421 | Rel-17 TS 28.531 Update operations of allocateNsi, allocateNssi, deallocateNsi, deallocateNssi | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑223655 | |||
S5‑223655 | Rel-17 TS 28.531 Update operations of allocateNsi, allocateNssi, deallocateNsi, deallocateNssi | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑223421 | |||
S5‑223452 | Rel-17 CR TS 28.531 Update procedures for asynchronous mode of operations for Network Slice and Network Slice Subnet LCM | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑223453 | Rel-17 CR TS 28.541 Add lifecycleState and availabilityStatus attributes to NetworkSlice and NetworkSliceSubnet | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑223454 | Rel-17 CR TS 28.623 Add AvailabilityStatus and LifecycleState to comDefs | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | ||||
6.7 | Converted CRs from DraftCRs approved at SA5#142e | S5‑223028 | Rel-17 CR 28.552 Correct implementation mistakes | Ericsson France S.A.S, Nokia | CR | Approval | Yes |
Yes
| agreed | No | ||
S5‑223029 | Rel-17 CR 28.541 Correct maximumDeviationHoTrigger for D-LBO | Ericsson France S.A.S | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223030 | Rel-16 CR 28.623 Stage 3 Yang fix for 3GPP Common Trace | Nokia, Nokia Shanghai Bell, Ericsson | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑223031 | Rel-16 CR 28.623 Stage 3 Yang fix for 3GPP Common Trace | Nokia, Nokia Shanghai Bell, Ericsson | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223032 | Rel 17 TS 28.623 Stage 3 Yang fix for 3GPP Common Trace | Nokia, Nokia Shanghai Bell, Ericsson | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223033 | Rel-16 CR 28.541 Diagram fix for NRM fragment for RRM policies | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223034 | Rel-17 TS 28.541 Diagram fix for NRM fragment for RRM policies | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223035 | Rel-16 Fixing OpenAPI Discoverability issue in CoslaNrm.yaml stage 3 | Nokia, Nokia Shangai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223036 | Rel-17 Fixing OpenAPI Discoverability issue in CoslaNrm.yaml stage 3 | Nokia, Nokia Shangai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223037 | Rel-17 Fixing OpenAPI Discoverability issue in EdgeNrm.yaml stage 3 | Nokia, Nokia Shangai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223038 | Rel-17 CR 28.538 Add the concept for edge computing management | Intel Korea, Ltd., Samsung | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223039 | Rel-17 CR 28.538 Add the missing procedure not implemented from approved pCR | Intel Korea, Ltd. | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223042 | Rel-16 TS 28.541 Fixing OpenAPI Discoverability issue in Stage3-5gcNrm.yaml | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223043 | Rel-16 TS 28.541 Fixing OpenAPI Discoverability issue in Stage3-nrNrm.yaml | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223044 | Rel-16 TS 28.541 Fixing OpenAPI Discoverability issue in Stage3-sliceNrm.yaml | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223045 | Rel-17 TS 28.541 Fixing OpenAPI Discoverability issue in Stage3-5gcNrm.yaml | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223046 | Rel-17 TS 28.541 Fixing OpenAPI Discoverability issue in Stage3-nrNrm.yaml | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223047 | Rel-17 TS 28.541 Fixing OpenAPI Discoverability issue in Stage3-sliceNrm.yaml | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223048 | Rel-16 TS 28.541 CT OpenAPI file relative-path URI references and dependence change for 5gcNrm.yaml | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223049 | Rel-17 TS 28.541 CT OpenAPI file relative-path URI references and dependence change for 5gcNrm.yaml | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223050 | TS 28.541 Fixing a few issues with attribute related to nextHopInfoList in EP_transport | Nokia, Nokia Shanghai Bell, KDDI, TELUS, Juniper Networks | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223051 | Rel-17 CR TS 28.531 Update procedure of reservation and checking feasibility of network slice subnet | Nokia, Nokia Shanghai Bell, Huawei, China Unicom, Deutsche Telekom,China Mobile,Ericsson | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223062 | Rel-16 CR TS 28.541 Correction to RRMPolicy_ IOC reference in RRMPolicyRatio IOC | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223063 | Rel-17 CR TS 28.541 Correction to RRMPolicy_ IOC reference in RRMPolicyRatio IOC | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223064 | Rel-16 CR TS 28.541 Add attribute properties for NetworkSliceSubnet attribute priorityLabel | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223065 | Rel-17 CR TS 28.541 Add attribute properties for NetworkSliceSubnet attribute priorityLabel | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223066 | Rel-17 CR TS 28.541 Fix to change Support Qualifier to S | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223067 | Rel-17 CR TS 28.541 Define LogicInterfaceInfo datatype and fix attribute properties for logicInterfaceInfo | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223127 | Rel-16 CR 32.158 Add definition of secondary resource | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223128 | Rel-17 CR 32.158 Add definition of secondary resource | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223129 | Rel-16 CR 32.158 Add definition of resource "/{MnSName}/{MnSVersion}" | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223130 | Rel-17 CR 32.158 Add definition of resource "/{MnSName}/{MnSVersion}" | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223132 | Rel-16 CR 32.158 Clarify clause Creating a resource with identifier creation by the MnS Producer | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223137 | Rel-17 CR 32.158 Clarify clause Creating a resource with identifier creation by the MnS Producer | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223138 | Rel-16 CR 32.158 Clarify clause Creating a resource with identifier creation by the MnS Consumer | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223139 | Rel-17 CR 32.158 Clarify clause Creating a resource with identifier creation by the MnS Consumer | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223140 | Rel-16 CR 32.158 Clarify clause Design pattern for updating a resource | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223141 | Rel-17 CR 32.158 Clarify clause Design pattern for updating a resource | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223142 | Rel-16 CR 32.158 Clarify clause Design pattern for deleting a resource | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223143 | Rel-17 CR 32.158 Clarify clause Design pattern for deleting a resource | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223144 | Rel-16 CR 32.158 Clarify clause Design pattern for subscribe/notify | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223145 | Rel-17 CR 32.158 Clarify clause Design pattern for subscribe/notify | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223147 | Rel-16 CR 32.158 Clarify clause Design pattern for scoping and filtering | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223148 | Rel-17 CR 32.158 Clarify clause Design pattern for scoping and filtering | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223149 | Rel-16 CR 32.158 Clarify clause Design patterns for attribute and attribute field selection | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223150 | Rel-17 CR 32.158 Clarify clause Design patterns for attribute and attribute field selection | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223151 | Rel-16 CR 32.158 Clarify clause Design patterns for partially updating a resource | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223156 | Rel-17 CR 32.158 Clarify clause Design patterns for partially updating a resource | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223157 | Rel-16 CR 32.158 Clarify clause Design patterns for patching multiple resources | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223158 | Rel-17 CR 32.158 Clarify clause Design patterns for patching multiple resources | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223159 | Rel-16 CR 32.158 Add missing clause Large queries | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223160 | Rel-17 CR 32.158 Add missing clause Large queries | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223161 | Rel-16 CR 32.158 Correct examples in Annex A | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223162 | Rel-17 CR 32.158 Correct examples in Annex A | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223163 | Rel-16 CR 28.532 Correct REST SS of deleteMOI | Nokia, Nokia Shanghai Bell | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑223164 | Rel-17 CR 28.532 Correct REST SS of deleteMOI | Nokia, Nokia Shanghai Bell | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑223167 | Rel-16 CR 28.622 Alignment of attribute names of TraceJob IOC to TS 32.422 (stage 2) | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223168 | Rel-17 CR 28.622 Alignment of attribute names of TraceJob IOC to TS 32.422 (stage 2) | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223169 | Rel-16 CR 28.623 Alignment of attribute names of TraceJob IOC to TS 32.422 (stage 3) | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223170 | Rel-17 CR 28.623 Alignment of attribute names of TraceJob IOC to TS 32.422 (stage 3) | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223171 | Rel-16 CR 28.622 Clean up of attribute properties | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223172 | Rel-17 CR 28.622 Clean up of attribute properties | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223173 | Rel-17 CR 32.422 Add metric identifier for trace metrics | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑223656 | |||
S5‑223656 | Rel-17 CR 32.422 Add metric identifier for trace metrics | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑223173 | |||
S5‑223177 | Rel-17 CR 28.552 Correct handover execution failure per beam pair measurement | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223178 | Rel-16 CR 28.552 Clean up of PM related to MRO | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223179 | Rel-17 CR 28.552 Clean up of PM related to MRO | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223188 | Rel-16 CR 28.532 Correct REST SS of deleteMOI | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223189 | Rel-17 CR 28.532 Correct REST SS of deleteMOI | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223201 | YANG Mapping Corrections | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223202 | Rel-18 CR 28.541 Access specific GST configuration | Samsung R&D Institute India | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑223203 | Rel-17 CR 28.552 Mean number of DRBs undergoing from User Plane Path Failures | Samsung R&D Institute India | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑223204 | Rel-17 CR 28.538 Notifications | Samsung R&D Institute India | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
S5‑223205 | Rel-17 CR 28.538 Notifications | Samsung R&D Institute India | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑223206 | Rel-17 CR 28.538 Resolving ED | Samsung R&D Institute India | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑223207 | Rel-17 CR 28.531 Deleting network slice capability exposure | Samsung R&D Institute India | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑223215 | CR eCOSLA for TS 28.535 | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223217 | CR for TS 28.536 | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223232 | Rel-17 CR 28.541 Correction on two SLA attributes | Huawei | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223249 | Rel-17 CR 28.538 update description of ECM LCM | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑223250 | Rel-17 CR 28.538 update ECM NRM stage 2 | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑223251 | Rel-17 CR 28.538 update ECM NRM stage 3 | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑223252 | Rel-16 CR 28.554 update formula of of PDU session establishment success rate | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑223253 | Rel-17 CR 28.554 update formula of of PDU session establishment success rate | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑223254 | Rel-17 CR 28.538 correct EAS lifecycle management procedure | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑223302 | Rel-16 CR 28.541 Correction on minor errrors in nrNRM.yaml | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑223303 | Rel-17 CR 28.541 Correction on minor errrors in nrNRM.yaml | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑223304 | Rel-16 CR 28.541 Correcton on the attribute definition in the wrong yaml file | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑223305 | Rel-17 CR 28.541 Correcton on the attribute definition in the wrong yaml file | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑223306 | Rel-17 CR 28.532 Update provMnS yaml file to include the resources-intentNrm | Huawei,Deutsche Telekom | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑223307 | Rel-17 CR 28.541 Add feasibility check NRM fragment | Huawei,China Unicom, Deutsche Telekom,China Mobile, Samsung, Nokia, TELUS, KDDI,Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑223308 | Rel-17 CR 28.531 Update procedure of reservation and checking feasibility of network slice subnet | Huawei,China Unicom, Deutsche Telekom,China Mobile | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑223483 | CR Rel-17 28.552 Enhance UE Context Release measurements for MDA | Intel | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑223495 | Rel-16 CR 28.532 Fix FileDataType (OpenAPI) | Ericsson Inc. | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223496 | Rel-17 CR 28.532 Fix FileDataType (OpenAPI) | Ericsson Inc. | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223497 | Rel-16 CR 28.541 Fix BWP association to NRCellDU | Ericsson Inc. | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223498 | Rel-17 CR 28.541 Fix BWP association to NRCellDU | Ericsson Inc. | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223500 | Rel-16 CR 28.541 Update 5QI set attribute definition | Ericsson Inc. | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223501 | Rel-17 CR 28.541 Update 5QI set description (YANG) | Ericsson Inc. | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223502 | Rel-16 CR 28.541 Update 5QI set description (YANG) | Ericsson Inc. | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223503 | Rel-17 CR 28.541 Update 5QI set attribute definition | Ericsson Inc. | CR | Approval | Yes |
Yes
| agreed | No | ||||
7 | Charging |   | ||||||||||
7.1 | Charging Plenary | S5‑223008 | CH agenda and time plan | WG vice Chair (Matrixx) | agenda | Yes |
Yes
| revised | No | S5‑223666 | ||
S5‑223666 | CH agenda and time plan | WG vice Chair (Matrixx) | agenda | - | Yes |
Yes
| approved | No | S5‑223008 | |||
S5‑223009 | Charging exec report | WG vice Chair (Matrixx) | report | Yes |
Yes
| noted | No | |||||
S5‑223023 | Reply LS on Traffic usage reporting on 5MBS service | S2-2203019 | LS in | Yes |
Yes
| noted | No | |||||
S5‑223024 | Reply LS on maximum number of MBS sessions that can be associated to a PDU session | S2-2203050 | LS in | Yes |
Yes
| withdrawn | Yes | |||||
7.2 | New Charging Work Item proposals |   | ||||||||||
7.3 | Charging Maintenance and Rel-18 small Enhancements | S5‑223085 | Rel-17 CR 32.291 Correcting response codes | Ericsson LM | CR | Agreement | Yes |
Yes
| not pursued | No | ||
S5‑223086 | Rel-17 CR 32.291 Correcting response code 3xx | Ericsson LM | CR | Agreement | Yes |
Yes
| revised | No | S5‑223694 | S5‑221305 | ||
S5‑223694 | Rel-17 CR 32.291 Correcting response code 3xx | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | S5‑223086 | |||
S5‑223087 | Rel-17 CR 32.291 Correcting response code 5xx | Ericsson LM | CR | Agreement | Yes |
Yes
| revised | No | S5‑223695 | S5‑221307 | ||
S5‑223695 | Rel-17 CR 32.291 Correcting response code 5xx | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | S5‑223087 | |||
S5‑223088 | Rel-17 CR 32.291 Correcting error handling | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑223089 | Rel-17 CR 32.255 Correcting charging termination flow at roaming | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑223090 | Rel-17 CR 32.256 Correcting support of charging scenarios for roaming | Ericsson LM | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑223091 | Rel-17 CR 32.274 Correcting session and charging identifiers | Ericsson LM | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑223092 | Rel-17 CR 32.255 Correcting usage of PDU session information | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑223093 | Rel-17 CR 32.291 Correcting usage of PDU session information | Ericsson LM | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑223094 | Rel-17 CR 32.254 Missing operation and identifier in NEF charging information | Ericsson LM | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑223095 | Rel-17 CR 32.291 Missing operation and identifier in NEF charging information | Ericsson LM | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑223096 | Rel-17 CR 32.298 Missing operation and identifier in NEF charging information | Ericsson LM | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑223097 | Rel-17 CR 32.290 Correcting CHF detected failure handling | Ericsson LM | CR | Agreement | Yes |
Yes
| revised | No | S5‑223707 | |||
S5‑223707 | Rel-17 CR 32.290 Correcting CHF detected failure handling | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | S5‑223097 | |||
S5‑223098 | Rel-17 CR 32.255 Correcting home routed CHF selection | Ericsson LM | CR | Agreement | Yes |
Yes
| revised | No | S5‑223698 | |||
S5‑223698 | Rel-17 CR 32.255 Correcting home routed CHF selection | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | S5‑223098 | |||
S5‑223099 | Rel-17 CR 32.255 Correcting IMS handling | Ericsson LM | CR | Agreement | Yes |
Yes
| revised | No | S5‑223699 | |||
S5‑223699 | Rel-17 CR 32.255 Correcting IMS handling | Ericsson LM | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑223099 | |||
S5‑223100 | Rel-17 CR 32.291 Missing IMS binding | Ericsson LM | CR | Agreement | Yes |
Yes
| revised | No | S5‑223682 | |||
S5‑223682 | Rel-17 CR 32.291 Missing IMS binding | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | S5‑223100 | |||
S5‑223101 | Rel-17 CR 32.291 Correcting IMS called identity as array | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑223102 | Rel-17 CR 32.260 Correcting IMS charging information | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑223103 | Rel-17 CR 32.298 Correcting IMS called identity as array | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑223187 | Rel-17 CR 32.260 Supported fields in Charging Data Request message | Nokia, Nokia Shangai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑223687 | |||
S5‑223687 | Rel-17 CR 32.260 Supported fields in Charging Data Request message | Nokia, Nokia Shangai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑223187 | |||
S5‑223190 | Rel-17 CR 32.291 RedirectAdresssType datatype missing | Nokia, Nokia Shangai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑223690 | |||
S5‑223690 | Rel-17 CR 32.291 RedirectAdresssType datatype missing | Nokia, Nokia Shangai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑223190 | |||
S5‑223191 | Rel-17 CR 32.260 Final Unit Indication missing | Nokia, Nokia Shangai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑223688 | |||
S5‑223688 | Rel-17 CR 32.260 Final Unit Indication missing | Nokia, Nokia Shangai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑223191 | |||
S5‑223192 | Rel-17 CR 32.291 Time Unit granularity missing | Nokia, Nokia Shangai Bell | CR | Agreement | Yes |
Yes
| withdrawn | Yes | ||||
S5‑223193 | Rel-17 CR 32.291 Tariff Change support | Nokia, Nokia Shangai Bell | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
S5‑223276 | Rel-16 CR 32.255 Correction on the Trigger Conditions | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑223685 | |||
S5‑223685 | Rel-16 CR 32.255 Correction on the Trigger Conditions | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑223276 | |||
S5‑223277 | Rel-17 CR 32.255 Correction on the Trigger Conditions | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑223686 | |||
S5‑223686 | Rel-17 CR 32.255 Correction on the Trigger Conditions | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑223277 | |||
S5‑223278 | Rel-16 CR 32.255 Correction on the Trigger type for QBC | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑223691 | |||
S5‑223691 | Rel-16 CR 32.255 Correction on the Trigger type for QBC | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑223278 | |||
S5‑223279 | Rel-17 CR 32.255 Correction on the Trigger type for QBC | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑223692 | |||
S5‑223692 | Rel-17 CR 32.255 Correction on the Trigger type for QBC | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑223279 | |||
S5‑223280 | Rel-17 CR 32.291 Correction on the QoS Monitoring Report | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑223693 | |||
S5‑223693 | Rel-17 CR 32.291 Correction on the QoS Monitoring Report | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑223280 | |||
S5‑223281 | Rel-16 CR 32.291 Correction on the Time attribute | Huawei,Deutsche Telekom | CR | Agreement | Yes |
Yes
| revised | No | S5‑223723 | |||
S5‑223723 | Rel-16 CR 32.291 Correction on the Time attribute | Huawei,Deutsche Telekom | CR | Agreement | Yes |
Yes
| agreed | No | S5‑223281 | |||
S5‑223282 | Rel-17 CR 32.291 Correction on the Time attribute | Huawei,Deutsche Telekom | CR | Agreement | Yes |
Yes
| revised | No | S5‑223689 | |||
S5‑223689 | Rel-17 CR 32.291 Correction on the Time attribute | Huawei,Deutsche Telekom | CR | Agreement | Yes |
Yes
| agreed | No | S5‑223282 | |||
S5‑223283 | Rel-17 CR 32.255 Addition of the Start Time | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑223701 | |||
S5‑223701 | Rel-17 CR 32.255 Addition of the Start Time | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑223283 | |||
S5‑223284 | Rel-17 CR 32.291 Addition of the Start Time | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑223703 | |||
S5‑223703 | Rel-17 CR 32.291 Addition of the Start Time | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑223284 | |||
S5‑223285 | Rel-17 CR 32.298 Addition of the Start Time | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑223717 | |||
S5‑223717 | Rel-17 CR 32.298 Addition of the Start Time | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑223285 | |||
S5‑223286 | Rel-17 CR 32.255 Correction on the description for Interworking Charging | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑223296 | Rel-16 CR 32.298 Correction on presence reporting area information | China Mobile E-Commerce Co. | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223297 | Rel-17 CR 32.298 Correction on presence reporting area information | China Mobile E-Commerce Co. | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223724 | Rel-17 CR 32.298 Correction on the QoS Monitoring Report | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑223725 | Rel-16 CR 32.291 Update OpenAPI version | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑223726 | Rel-17 CR 32.291 Update OpenAPI version | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
7.4 | Rel-17 Charging |   | ||||||||||
7.4.1 | Charging aspects of Edge Computing | S5‑223457 | pCR 32.257 Add charging information definition for EES exposed 5GC NF services | Intel | pCR | Approval | Yes |
Yes
| revised | No | S5‑223674 | |
S5‑223674 | pCR 32.257 Add charging information definition for EES exposed 5GC NF services | Intel | pCR | Approval | Yes |
Yes
| agreed | No | S5‑223457 | |||
S5‑223460 | pCR 32.257 Rapporteur clean-up | Intel | pCR | Approval | Yes |
Yes
| revised | No | S5‑223673 | |||
S5‑223673 | pCR 32.257 Rapporteur clean-up | Intel | pCR | Approval | Yes |
Yes
| agreed | No | S5‑223460 | |||
S5‑223462 | CR 32.291 Update Nchf_ConvergedCharging service API for Edge Computing | Intel | CR | Approval | Yes |
Yes
| revised | No | S5‑223675 | |||
S5‑223675 | CR 32.291 Update Nchf_ConvergedCharging service API for Edge Computing | Intel | CR | Approval | Yes |
Yes
| agreed | No | S5‑223462 | |||
S5‑223464 | CR 32.298 Add Edge Computing related CHF CDR(s) definition and ASN.1 format | Intel | CR | Approval | Yes |
Yes
| revised | No | S5‑223672 | |||
S5‑223672 | CR 32.298 Add Edge Computing related CHF CDR(s) definition and ASN.1 format | Intel | CR | Approval | Yes |
Yes
| agreed | No | S5‑223464 | |||
S5‑223465 | CR 32.297 Add CDR file format for Edge Computing charging | Intel | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑223468 | Presentation of TS 32.257 for approval | Intel | TS or TR cover | Approval | Yes |
Yes
| revised | No | S5‑223684 | |||
S5‑223684 | Presentation of TS 32.257 for approval | Intel | TS or TR cover | Approval | Yes |
Yes
| approved | No | S5‑223468 | |||
S5‑223667 | Draft TS 32.257 | intel | draft TR | Approval | Yes |
Yes
| approved | No | ||||
7.4.2 | Charging aspects of Proximity-based Services in 5GS | S5‑223438 | Rel-17 CR 32.291 Introduce OpenAPI extension for 5G ProSe charging | CATT | CR | Approval | Yes |
Yes
| revised | No | S5‑223676 | |
S5‑223676 | Rel-17 CR 32.291 Introduce OpenAPI extension for 5G ProSe charging | CATT | CR | Approval | Yes |
Yes
| agreed | No | S5‑223438 | |||
S5‑223439 | Rel-17 CR 32.291 Introduce Binding for 5G Prose charging | CATT | CR | Approval | Yes |
Yes
| revised | No | S5‑223678 | |||
S5‑223678 | Rel-17 CR 32.291 Introduce Binding for 5G Prose charging | CATT | CR | Approval | Yes |
Yes
| agreed | No | S5‑223439 | |||
S5‑223440 | Rel-17 CR 32.291 Introduce Data Type for 5G ProSe charging | CATT | CR | Approval | Yes |
Yes
| revised | No | S5‑223679 | |||
S5‑223679 | Rel-17 CR 32.291 Introduce Data Type for 5G ProSe charging | CATT | CR | Approval | Yes |
Yes
| agreed | No | S5‑223440 | |||
S5‑223441 | Rel-17 CR 32.298 Introduce 5G ProSe charging information to CHF CDR | CATT | CR | Approval | Yes |
Yes
| revised | No | S5‑223680 | |||
S5‑223680 | Rel-17 CR 32.298 Introduce 5G ProSe charging information to CHF CDR | CATT | CR | Approval | Yes |
Yes
| agreed | No | S5‑223441 | |||
S5‑223442 | Rel-17 CR 32.298 Introduce 5G ProSe charging to CHF CDR | CATT | CR | Approval | Yes |
Yes
| revised | No | S5‑223677 | |||
S5‑223677 | Rel-17 CR 32.298 Introduce 5G ProSe charging to CHF CDR | CATT | CR | Approval | Yes |
Yes
| agreed | No | S5‑223442 | |||
7.4.3 | 5G Charging for Local breakout roaming of data connectivity | S5‑223075 | Discussion paper on FBC and QBC for LBO | MATRIXX Software | discussion | Agreement | Yes |
Yes
| noted | No | ||
S5‑223104 | Rel-17 CR 32.255 QBC triggering for LBO | Ericsson LM | CR | Agreement | Yes |
Yes
| revised | No | S5‑223681 | |||
S5‑223681 | Rel-17 CR 32.255 QBC triggering for LBO | Ericsson LM | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑223104 | |||
S5‑223105 | Rel-17 CR 32.291 QBC triggering for LBO | Ericsson LM | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑223209 | Rel-17 CR 32.255 Additional charging principles for LBO_was_S5-222809 | Huawei, Ericsson, MATRIXX Software | CR | Agreement | Yes |
Yes
| revised | No | S5‑223683 | S5‑222809 | ||
S5‑223683 | Rel-17 CR 32.255 Additional charging principles for LBO_was_S5-222809 | Huawei, Ericsson, MATRIXX Software | CR | Agreement | Yes |
Yes
| agreed | No | S5‑223209 | |||
S5‑223211 | Rel-17 CR 32.255 Additional charging message flow for LBO_was_S5-222808 | Huawei, Ericsson, MATRIXX Software | CR | Agreement | Yes |
Yes
| revised | No | S5‑223722 | S5‑222808 | ||
S5‑223722 | Rel-17 CR 32.255 Additional charging message flow for LBO_was_S5-222808 | Huawei, Ericsson, MATRIXX Software | CR | Agreement | Yes |
Yes
| agreed | No | S5‑223211 | |||
S5‑223214 | Rel-17 CR 32.255 Introduction of possibility for Flow based charging in VPLMN for LBO | MATRIXX Software | CR | Agreement | Yes |
Yes
| merged | No | S5‑223681 | |||
S5‑223287 | Rel-17 CR 32.255 Additional charging message flow for MVNO | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑223704 | |||
S5‑223704 | Rel-17 CR 32.255 Additional charging message flow for MVNO | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑223287 | |||
S5‑223288 | Rel-17 CR 32.255 Additional charging principles for MVNO | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑223705 | |||
S5‑223705 | Rel-17 CR 32.255 Additional charging principles for MVNO | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑223288 | |||
7.4.4 | MMS Charging in 5G System Architecture |   | ||||||||||
7.5 | Charging studies |   | ||||||||||
7.5.1 | Study on charging aspects for enhancements of Network Slicing Phase 2 | S5‑223225 | Rel-18 pCR 32.847 Add new solution for Key issue#8 | MATRIXX Software | pCR | Agreement | Yes |
Yes
| revised | No | S5‑223697 | |
S5‑223697 | Rel-18 pCR 32.847 Add new solution for Key issue#8 | MATRIXX Software | pCR | Agreement | Yes |
Yes
| agreed | No | S5‑223225 | |||
S5‑223226 | Rel-18 pCR 32.847 Add evaluation and conclusion for Key issue#8 | MATRIXX Software | pCR | Agreement | Yes |
Yes
| approved | No | ||||
S5‑223227 | Rel-18 pCR 32.847 Add NSACF based NS charging new solution for Key issue#6 | MATRIXX Software | pCR | Agreement | Yes |
Yes
| approved | No | ||||
S5‑223228 | Rel-18 pCR 32.847 Add NWDAF based NS charging new solution for Key issue#6 | MATRIXX Software | pCR | Agreement | Yes |
Yes
| revised | No | S5‑223696 | |||
S5‑223696 | Rel-18 pCR 32.847 Add NWDAF based NS charging new solution for Key issue#6 | MATRIXX Software | pCR | Agreement | Yes |
Yes
| approved | No | S5‑223228 | |||
S5‑223289 | Rel-18 pCR 32.847 Clarify the Evaluation for the key issue 7 | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑223711 | |||
S5‑223711 | Rel-18 pCR 32.847 Clarify the Evaluation for the key issue 7 | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑223289 | |||
S5‑223668 | Draft TR 32.847 | MATRIXX | draft TR | discussion | Yes |
Yes
| approved | No | ||||
7.5.2 | Study on Nchf charging services phase 2 | S5‑223106 | Rel-18 pCR 28.826 Adding service identifier based solution to clause 5.3 | Ericsson LM | pCR | Approval | Yes |
Yes
| merged | No | S5‑223716 | |
S5‑223107 | Rel-18 pCR 28.826 Correcting clause 5.5.5 | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑223702 | |||
S5‑223702 | Rel-18 pCR 28.826 Correcting clause 5.5.5 | Ericsson LM | pCR | Approval | Yes |
Yes
| noted | No | S5‑223107 | |||
S5‑223108 | Rel-18 pCR 28.826 Adding new trigger category solution clause 5.1 | Ericsson LM | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑223109 | Rel-18 pCR 28.826 Adding trigger solutions to clause 5.2 | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑223700 | |||
S5‑223700 | Rel-18 pCR 28.826 Adding trigger solutions to clause 5.2 | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑223109 | |||
S5‑223197 | Rel-17 pCR 28.826 ServiceID in Charging Data Request | Nokia, Nokia Shangai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑223716 | |||
S5‑223716 | Rel-17 pCR 28.826 ServiceID in Charging Data Request | Nokia, Nokia Shangai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑223197 | |||
S5‑223290 | Rel-18 pCR 28.826 Add the solution for CHF Rating | Huawei | pCR | Agreement | Yes |
Yes
| noted | No | ||||
S5‑223291 | Rel-18 pCR 28.826 Addition of Threshold based re-authorization triggers optimization | Huawei | pCR | Agreement | Yes |
Yes
| noted | No | ||||
S5‑223669 | Draft TR 28.826 | Ericsson | draft TR | Approval | No |
Yes
| approved | No | ||||
7.5.3 | Study on 5G roaming charging architecture for wholesale and retail scenarios | S5‑223110 | Rel-18 pCR 28.827 Correcting solution 1.3 | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑223715 | |
S5‑223715 | Rel-18 pCR 28.827 Correcting solution 1.3 | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑223110 | |||
S5‑223111 | Rel-18 pCR 28.827 Solution for roaming charging profile | Ericsson LM | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑223112 | Rel-18 pCR 28.827 Use case for 5G connection and mobility in clause 7.2 | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑223113 | Rel-18 pCR 28.827 Updating solution 2.1 with SMSF and AMF | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑223713 | |||
S5‑223713 | Rel-18 pCR 28.827 Updating solution 2.1 with SMSF and AMF | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑223113 | |||
S5‑223114 | Rel-18 pCR 28.827 Adding AMF solution to clause 7.2 | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑223712 | |||
S5‑223712 | Rel-18 pCR 28.827 Adding AMF solution to clause 7.2 | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑223114 | |||
S5‑223115 | Rel-18 pCR 28.827 Updating solution 2.2 with SMF | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑223116 | Rel-18 pCR 28.827 Adding CHF to CHF solution to clause 7.4 | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑223117 | Rel-18 pCR 28.827 Updating solution 5.1 | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑223118 | Rel-18 pCR 28.827 Adding SMF to multiple CHF solution to clause 7.5 | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑223720 | |||
S5‑223720 | Rel-18 pCR 28.827 Adding SMF to multiple CHF solution to clause 7.5 | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑223118 | |||
S5‑223119 | Rel-18 pCR 28.827 Use case for 5G connection and mobility in clause 7.3 | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑223719 | |||
S5‑223719 | Rel-18 pCR 28.827 Use case for 5G connection and mobility in clause 7.3 | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑223119 | |||
S5‑223120 | Rel-18 pCR 28.827 Solution for issue 2c CHF selection | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑223721 | |||
S5‑223721 | Rel-18 pCR 28.827 Solution for issue 2c CHF selection | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑223120 | |||
S5‑223121 | Rel-18 pCR 28.827 Solution for issue 2d servce to use between CHFs | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑223122 | Rel-18 pCR 28.827 Solution for issue 2e trigger handling between CHFs | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑223718 | |||
S5‑223718 | Rel-18 pCR 28.827 Solution for issue 2e trigger handling between CHFs | Ericsson LM | pCR | Approval | Yes |
Yes
| noted | No | S5‑223122 | |||
S5‑223292 | Rel-18 pCR 28.827 Optimization on the QBC triggers | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑223714 | |||
S5‑223714 | Rel-18 pCR 28.827 Optimization on the QBC triggers | Huawei | pCR | Agreement | Yes |
Yes
| noted | No | S5‑223292 | |||
S5‑223670 | Draft TR 28.827 | Ericsson | draft TR | Approval | No |
Yes
| approved | No | ||||
7.5.4 | Study on Charging Aspects for Enhanced support of Non-Public Networks | S5‑223082 | Rel-18 pCR 28.828 Introduction of general background | China Mobile | pCR | Approval | Yes |
Yes
| approved | No | ||
S5‑223083 | pCR 28.828 Introduction of non-public networks functionality and architecture | China Mobile | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑223084 | Rel-18 pCR 28.828 Introduction of charging modes | China Mobile | pCR | Approval | Yes |
Yes
| revised | No | S5‑223709 | |||
S5‑223709 | Rel-18 pCR 28.828 Introduction of charging modes | China Mobile | pCR | Approval | Yes |
Yes
| approved | No | S5‑223084 | |||
S5‑223135 | Rel-18 pCR 28.828 Add charging scenarios and key issues for PNI-NPN on converged charging for access connection | China Mobile | pCR | Approval | Yes |
Yes
| revised | No | S5‑223710 | |||
S5‑223710 | Rel-18 pCR 28.828 Add charging scenarios and key issues for PNI-NPN on converged charging for access connection | China Mobile | pCR | Approval | Yes |
Yes
| approved | No | S5‑223135 | |||
S5‑223136 | Rel-18 pCR 28.828 Add charging scenarios and key issues for SNPN on converged charging for access connection | China Mobile | pCR | Approval | Yes |
Yes
| revised | No | S5‑223708 | |||
S5‑223708 | Rel-18 pCR 28.828 Add charging scenarios and key issues for SNPN on converged charging for access connection | China Mobile | pCR | Approval | Yes |
Yes
| approved | No | S5‑223136 | |||
S5‑223293 | Rel-18 pCR 28.828 Add the business roles for NPN | Huawei | pCR | Agreement | Yes |
Yes
| merged | No | S5‑223709 | |||
S5‑223294 | Rel-18 pCR 28.828 Add the use case for SNPN | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑223706 | |||
S5‑223706 | Rel-18 pCR 28.828 Add the use case for SNPN | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑223294 | |||
S5‑223671 | Draft TR 28.828 | China Mobile | draft TR | Approval | Yes |
Yes
| approved | No | ||||
8 | Any Other Business |   | ||||||||||
9 | Closing of the meeting |   |