Tdoc List
2022-09-02 10:03
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‑225000 | 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‑225001 | 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‑225002 | e-meeting process | WG Chair | discussion | Yes |
Yes
| revised | No | S5‑225611 | ||
S5‑225611 | e-meeting process | WG Chair | discussion | - | Yes |
Yes
| noted | No | S5‑225002 | |||
S5‑225003 | Post e-meeting email approval status | WG Chair | other | Yes |
No
| available | No | |||||
S5‑225010 | SA5 working procedures | WG Chair | other | Yes |
Yes
| approved | No | |||||
S5‑225014 | Process for management of draft TS-TRs | WG Chair | other | Yes |
Yes
| noted | No | |||||
S5‑225073 | Input to working procedures on FORGE process | Nokia, Nokia Shanghai Bell | other | Agreement | Yes |
Yes
| revised | No | S5‑225609 | |||
S5‑225609 | Input to working procedures on FORGE process | Nokia, Nokia Shanghai Bell | other | Agreement | Yes |
Yes
| approved | No | S5‑225073 | |||
S5‑225592 | Forge Usage Guide for Charging Management | Huawei | discussion | Endorsement | Yes |
Yes
| endorsed | No | ||||
S5‑225593 | working procedures on FORGE process | Huawei | other | Agreement | Yes |
Yes
| revised | No | S5‑225610 | |||
S5‑225610 | working procedures on FORGE process | Huawei | other | Agreement | Yes |
Yes
| endorsed | No | S5‑225593 | |||
S5‑225594 | Forge to become the main source of code | Nokia | discussion | discussion | Yes |
Yes
| endorsed | No | ||||
S5‑225595 | Moving all code to Git and Remove it from MsWord | Ericsson | discussion | discussion | Yes |
Yes
| endorsed | No | ||||
5.2 | Technical issues at SA5 level |   | ||||||||||
5.3 | Liaison statements at SA5 level | S5‑225019 | East/West Bound Interface for Telco Edge consideration | GSMA OPG Operator Platform API Group (OPAG) | LS in | Yes |
Yes
| postponed | No | |||
S5‑225031 | Resubmitted LS on Publication of GS ZSM009-2 and information about related ETSI ISG ZSM work | ETSI ISG ZSM | LS in | Yes |
Yes
| postponed | No | |||||
S5‑225206 | Reply LS on LS/r on methodology harmonization update | Ericsson Hungary Ltd | LS out | Approval | Yes |
Yes
| revised | No | S5‑225615 | |||
S5‑225615 | Reply LS on LS/r on methodology harmonization update | Ericsson Hungary Ltd | LS out | Approval | Yes |
Yes
| approved | No | S5‑225206 | |||
S5‑225598 | LS on UE to application server latency | GSMA OPG | LS in | discussion | Yes |
Yes
| postponed | No | ||||
5.4 | SA5 meeting calendar | S5‑225015 | SA5 meeting calendar | WG Chair | other | Yes |
Yes
| revised | No | S5‑225612 | ||
S5‑225612 | SA5 meeting calendar | WG Chair | other | - | Yes |
Yes
| noted | No | S5‑225015 | |||
6 | OAM&P |   | ||||||||||
6.1 | OAM&P Plenary | S5‑225004 | OAM&P action list | WG Vice Chair (Huawei) | other | Yes |
Yes
| noted | No | |||
S5‑225005 | agenda_with_Tdocs_sequence_proposal_OAM | WG Vice Chair (Huawei) | agenda | Yes |
Yes
| noted | No | |||||
S5‑225006 | OAM Exec Report | WG Vice Chair (Huawei) | report | No |
No
| reserved | No | |||||
S5‑225007 | OAM Chair notes and conclusions | WG Chair | report | Yes |
No
| available | No | |||||
S5‑225011 | Collection of useful endorsed document and external communication documents | WG Vice Chair (Huawei) | discussion | Yes |
Yes
| noted | No | |||||
S5‑225012 | Collection of Rel-18 3GPP SA5 OAM WoP | WG Vice Chair (Huawei) | discussion | Yes |
Yes
| noted | No | |||||
S5‑225013 | Living document for stage 2-3 alignment | WG Chair | other | Yes |
Yes
| approved | No | |||||
S5‑225017 | Resubmitted Liaison Response to 3GPP TSG-SA5 for Network Slice Ordering, Provisioning & Assurance | MEF Forum | LS in | Yes |
Yes
| replied to | No | |||||
S5‑225604 | Reply to: Resubmitted Liaison Response to 3GPP TSG-SA5 for Network Slice Ordering, Provisioning & Assurance | current meeting | LS out | approval | Yes |
Yes
| approved | No | ||||
S5‑225018 | LS on information about BBF’s release of technical report on network slicing management | BBF | LS in | Yes |
Yes
| noted | No | |||||
S5‑225020 | Resubmitted LS on RAN3 agreements for NR QoE | R3-222890 | LS in | Yes |
Yes
| postponed | No | |||||
S5‑225021 | Reply LS on User Consent Updating | R3-224076 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑225022 | Resubmitted LS on M6 Delay Threshold | R3-224079 | LS in | Yes |
Yes
| postponed | No | |||||
S5‑225023 | Resubmitted Reply LS on Report Amount for M4, M5, M6 and M7 measurements | R3-224084 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑225024 | Resubmitted LS on O-RAN – UML models and tools to be used by 3GPP SA5 | O-RAN | LS in | Yes |
Yes
| replied to | No | |||||
S5‑225602 | Reply to: LS on O-RAN – UML models and tools to be used by 3GPP SA5 | Samsung | LS out | approval | Yes |
Yes
| approved | No | ||||
S5‑225025 | Resubmitted LS on O-RAN – Transport Network Slicing Enhancement IM/DM TS28.541 | O-RAN | LS in | Yes |
Yes
| postponed | No | |||||
S5‑225026 | LS on initiation new work item M.fidtom: ""Framework of intent driven telecom operation and management"" | ITU-T Study Group 2 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑225599 | Reply to: LS on initiation new work item M.fidtom: ""Framework of intent driven telecom operation and management"" | Huawei | LS out | approval | Yes |
Yes
| approved | No | ||||
S5‑225027 | LS on progress about intelligence levels evaluation of AITOM in Q6/2 | ITU-T Study Group 2 | LS in | Yes |
Yes
| noted | No | |||||
S5‑225028 | LS on initiation of new Recommendation ITU-T M.rsmca, ""Requirements for smart maintenance of cell antenna"" | ITU-T Study Group 2 | LS in | Yes |
Yes
| noted | No | |||||
S5‑225029 | LS/r on feedback on the working on the energy efficiency of 5G networks (reply to 3GPP TSG SA5-S5-221502) | ITU-T Study Group 2 | LS in | Yes |
Yes
| noted | No | |||||
S5‑225030 | Resubmitted LS/r on methodology harmonization update (reply to 3GPP TSG SA5-S5-222570) | ITU-T Study Group 2 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑225032 | LS on the approval of a new ITU-T Supplement on use cases for autonomous networks | ITU-T SG13 | LS in | Yes |
Yes
| noted | No | |||||
S5‑225055 | LS/r on energy saving management of 5G RAN with AI (reply to 3GPP TSG SA5-S5-221502 ) | ITU-T SG5 | LS in | Yes |
Yes
| noted | No | |||||
S5‑225074 | LS/r on 5G Network Energy Efficiency and Energy Saving (reply to 3GPP TSG SA5-S5-221680) | ITU-T SG5 | LS in | Yes |
Yes
| noted | No | |||||
S5‑225114 | LS on Report Amount for M4, M5, M6 and M7 measurements | Nokia, Nokia Shanghai Bell | LS out | Approval | Yes |
Yes
| merged | No | S5‑225614 | |||
S5‑225172 | Reply LS on M6 Delay Threshold | Huawei | LS out | Approval | Yes |
Yes
| noted | No | ||||
S5‑225187 | Reply LS on Report Amount for M4, M5, M6 and M7 measurements | Huawei | LS out | Approval | Yes |
Yes
| revised | No | S5‑225614 | |||
S5‑225614 | Reply LS on Report Amount for M4, M5, M6 and M7 measurements | Huawei | LS out | Approval | Yes |
Yes
| approved | No | S5‑225187 | |||
S5‑225312 | LS reply to TMF, MEF and GSMA on overall architecture for network slice ordering, provisioning and assurance | Huawei Technologies France | LS out | Agreement | No |
Yes
| withdrawn | Yes | ||||
S5‑225321 | Reply LS on User Consent Updating | Nokia, Nokia Shanghai Bell | LS out | Approval | Yes |
Yes
| approved | No | ||||
S5‑225596 | LS/r on Use cases for Autonomous Networks (reply to 3GPP TSG SA5--222560-LS34) | ITU-T SG13 | LS in | discussion | Yes |
Yes
| noted | No | ||||
S5‑225597 | LS on 3GPP SA5 work on intent-driven management S5-224343 | TM Forum | LS in | discussion | Yes |
Yes
| noted | No | ||||
S5‑225603 | LS on O-RAN – Transport Network Slicing Enhancement IM/DM TS28.541 | Samsung | LS out | Approval | Yes |
Yes
| noted | No | ||||
S5‑225664 | Latest draft TR 28.831 | Nokia | draft TR | Approval | Yes |
Yes
| approved | No | ||||
6.2 | New OAM&P Work Item proposals | S5‑225194 | Revised WID for Additional NRM features phase 2 | Huawei | WID revised | Approval | Yes |
Yes
| noted | No | ||
S5‑225374 | New SID on Enhancement Management from OAM to NWDAF for Computing Awareness | China Telecommunications | SID new | Approval | Yes |
Yes
| noted | No | ||||
S5‑225376 | Study on Data Management | Nokia, Nokia Shanghai Bell | SID new | Approval | Yes |
Yes
| revised | No | S5‑225617 | |||
S5‑225617 | Study on Data Management | Nokia, Nokia Shanghai Bell | SID new | Approval | Yes |
Yes
| agreed | No | S5‑225376 | |||
S5‑225465 | New WID on overview and usage guide of Service Based Management (SBM) specifications | HuaWei Technologies Co., Ltd | WID new | Yes |
Yes
| noted | No | |||||
S5‑225505 | New WID on methodology for deprecation. | Ericsson | WID new | Yes |
Yes
| revised | No | S5‑225616 | ||||
S5‑225616 | New WID on methodology for deprecation. | Ericsson | WID new | - | Yes |
Yes
| agreed | No | S5‑225505 | |||
6.3 | OAM&P Maintenance and Rel-18 small Enhancements | S5‑225067 | TS28.541 Rel-17 fix incorrect Line Folding in TS28541_SliceNrm.yaml | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| merged | No | S5‑225857 | |
S5‑225068 | TS 28.541Rel-18 fix incorrect Line Folding in TS28541_SliceNrm.yaml | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| merged | No | S5‑225797 | |||
S5‑225069 | TS28.541 Rel-17 FiveQICharacteristics inheritance issue and reference issue in stage 3 | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑225828 | |||
S5‑225828 | TS28.541 Rel-17 FiveQICharacteristics inheritance issue and reference issue in stage 3 | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑225069 | |||
S5‑225070 | TS28.541 Rel-18 FiveQICharacteristics inheritance issue and reference issue in stage 3 | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑225827 | |||
S5‑225827 | TS28.541 Rel-18 FiveQICharacteristics inheritance issue and reference issue in stage 3 | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑225070 | |||
S5‑225071 | TS 28.541 Rel-17 fix inconsistency in AMFFunction stage 2 and stage 3 | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑225826 | |||
S5‑225826 | TS 28.541 Rel-17 fix inconsistency in AMFFunction stage 2 and stage 3 | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑225071 | |||
S5‑225072 | TS28.541 Rel-18 fix inconsistency in AMFFunction stage 2 and stage 3 | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑225825 | |||
S5‑225825 | TS28.541 Rel-18 fix inconsistency in AMFFunction stage 2 and stage 3 | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑225072 | |||
S5‑225076 | TS 28.541 Rel17 Correction to DESManagementFunction and CESManagementFunction | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑225077 | TS 28.541 Rel18 Correction to DESManagementFunction and CESManagementFunction | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑225080 | Rel16_CR_32422_Correcting the name of referenced RAN3 RRC IE | Nokia, Nokia Shanghai Bell | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑225081 | Rel17_CR_32422_Correcting the name of referenced RAN3 RRC IE | Nokia, Nokia Shanghai Bell | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑225092 | Rel-17 CR TS28.541 Correction to serviceType attribute | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑225822 | |||
S5‑225822 | Rel-17 CR TS28.541 Correction to serviceType attribute | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑225092 | |||
S5‑225093 | Rel-18 CR TS28.541 Correction to serviceType attribute | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑225821 | |||
S5‑225821 | Rel-18 CR TS28.541 Correction to serviceType attribute | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑225093 | |||
S5‑225094 | Rel-17 CR TS28.541 Add missing attributes from serviceProfile to sliceProfile | Nokia, Nokia Shanghai Bell, KDDI | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑225095 | Rel-18 CR TS28.541 Add missing attributes from serviceProfile to sliceProfile | Nokia, Nokia Shanghai Bell, KDDI | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑225097 | Rel17_CR_28104_Rectifying attribute properties for coverage problem analysis | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑225823 | |||
S5‑225823 | Rel17_CR_28104_Rectifying attribute properties for coverage problem analysis | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑225097 | |||
S5‑225098 | Rel17_CR_28104_Rectifying attribute properties for EsRecommendation DataType | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| merged | No | S5‑225823 | |||
S5‑225099 | Rel17_CR_28104_Rectifying attribute properties for HOTargetType Datatype | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| merged | No | S5‑225823 | |||
S5‑225100 | Rel17_CR_28104_Rectifying attribute properties for Maintanance management Analysis | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| merged | No | S5‑225823 | |||
S5‑225101 | Rel17_CR_28104_Rectifying attribute properties for MDA assisted Failure Prediction | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| merged | No | S5‑225823 | |||
S5‑225102 | Rel17_CR_28104_Rectifying attribute properties for Mobility Performance Analysis | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| merged | No | S5‑225823 | |||
S5‑225103 | Rel17_CR_28104_Rectifying attribute properties for Network Slice Load Analysis | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| merged | No | S5‑225823 | |||
S5‑225104 | Rel17_CR_28104_Rectifying attribute properties for Network Slice Traffic Prediction | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| merged | No | S5‑225823 | |||
S5‑225105 | Rel17_CR_28104_Rectifying attribute properties for Paging Analytics | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| merged | No | S5‑225823 | |||
S5‑225106 | Rel17_CR_28104_Rectifying attribute properties for Traffic Load Trend Datatype | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| merged | No | S5‑225823 | |||
S5‑225107 | Rel-16 CR 32.423 GPB schema fix for trace streaming | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑225108 | Rel-17 CR 32.423 GPB schema fix for trace streaming | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑225109 | Rel-17 CR 32.422 Correcting Support Qualifier for jobId attribute | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑225601 | Rel-17 CR 28.622 Correcting Support Qualifier for jobId attribute | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑225111 | Rel17_CR_28622_Report Amount for M4, M5, M6 and M7 measurements in LTE | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑225820 | Rel17_CR_28622_Report Amount for M4, M5, M6 and M7 measurements in LTE | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑225112 | Rel17_CR_28623_Report Amount for M4, M5, M6 and M7 measurements in LTE | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| merged | No | S5‑225798 | |||
S5‑225113 | Rel17_CR_32422_Report Amount for M4, M5, M6 and M7 measurements in LTE | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑225819 | Rel17_CR_32422_Report Amount for M4, M5, M6 and M7 measurements in LTE | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑225117 | Rel16_CR_32422_Correcting the name of referenced RAN3 RRC IE | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑225118 | Rel17_CR_32422_Correcting the name of referenced RAN3 RRC IE | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑225130 | Rel-17 CR 28.532 Updating Hysteresis from M to O in notifyThresholdCrossing | Samsung R&D Institute UK | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑225131 | Rel-17 CR 28.532 Updating Hysteresis from M to O in notifyThresholdCrossing | Samsung R&D Institute UK | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑225132 | Rel-17 CR 28.531 Deleting capacity planning use case | Samsung R&D Institute UK | CR | Agreement | Yes |
Yes
| revised | No | S5‑225829 | |||
S5‑225829 | Rel-17 CR 28.531 Deleting capacity planning use case | Samsung R&D Institute UK | CR | Agreement | Yes |
Yes
| agreed | No | S5‑225132 | |||
S5‑225133 | Rel-18 CR 28.531 Deleting capacity planning use case | Samsung R&D Institute UK | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑225138 | Rel-17 CR TS 28.312 Add missing guidelines for using scenario specific intent expectation for intent driven use cases | Huawei, Deutsche Telekom | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑225139 | Rel-17 CR TS 28.312 Correct the misalignment information in Annex C | Huawei, Deutsche Telekom | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑225140 | Rel-17 CR TS 28.312 Update intentNRM yaml file to distinguish the generic intent model and sceanrio specific intent model | Huawei, Deutsche Telekom | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑225141 | Rel-17 CR TS 28.541 Update stage2 and stage3 definition for FeasibilityCheckAndReservationJob | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑225857 | |||
S5‑225857 | Rel-17 CR TS 28.541 Update stage2 and stage3 definition for FeasibilityCheckAndReservationJob | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑225141 | |||
S5‑225142 | Rel-18 CR TS 28.541 Update stage2 and stage3 definition for FeasibilityCheckAndReservationJob | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑225797 | |||
S5‑225797 | Rel-18 CR TS 28.541 Update stage2 and stage3 definition for FeasibilityCheckAndReservationJob | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑225142 | |||
S5‑225143 | Rel-17 CR TS 28.531 Update feasibility check procedure to align with FeasibilityCheckAndReservationJob | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑225796 | |||
S5‑225796 | Rel-17 CR TS 28.531 Update feasibility check procedure to align with FeasibilityCheckAndReservationJob | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑225143 | |||
S5‑225144 | Rel-17 CR TS 28.105 Add references for missing management and orchestration features which can may the AIML capabilities | Huawei,Nokia, Deutsche Telekom,China Telecom | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑225145 | Rel-16 CR TS 28.532 Update provMnS yaml to include closaNRM yaml | Huawei,Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑225146 | Rel-17 CR TS 28.532 Update provMnS yaml to include closaNRM yaml | Huawei,Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑225147 | Rel-17 CR TS 28.104 OpenAPI file name and dependence change | Huawei,Intel | CR | Agreement | Yes |
Yes
| merged | No | S5‑225794 | |||
S5‑225148 | Rel-17 CR TS 28.105 OpenAPI file name and dependence change | Huawei,Intel | CR | Agreement | Yes |
Yes
| merged | No | S5‑225795 | |||
S5‑225149 | Rel-17 CR TS 28.532 Update provMnS yaml to include MDA NRM related resources | Huawei,Intel | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑225150 | Rel-17 CR TS 28.541 Add missing notifyMOIChanges in configuration notification table | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑225151 | Rel-18 CR TS 28.541 Add missing notifyMOIChanges in configuration notification table | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑225153 | Correct notifyMOIChanges handling for YANG leaf-lists | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑225165 | Rel-17 CR 28.541 Correction on two SLA attributes | Huawei | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑225166 | Rel-18 CR 28.541 Correction on two SLA attributes | Huawei | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑225167 | Rel-17 CR TS 32.422 Report Amount for M4, M5, M6 and M7 measurements in LTE | China Telecomunication Corp., Huawei | CR | Agreement | Yes |
Yes
| merged | No | S5‑225819 | |||
S5‑225168 | Rel-17 CR TS 28.622 Report Amount for M4, M5, M6 and M7 measurements in LTE | China Telecomunication Corp., Huawei | CR | Agreement | Yes |
Yes
| merged | No | S5‑225820 | |||
S5‑225169 | Rel-17 CR TS 32.422 add excess packet delay threshould for signalling-based and management-based MDT | Huawei | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑225170 | Rel-17 CR TS 28.622 add excess packet delay threshould for signalling-based and management-based MDT | Huawei | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑225171 | Rel-17 CR TS 28.623 add excess packet delay threshould for signalling-based and management-based MDT | Huawei | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑225173 | Rel-18 CR 28.104 Note in Generic flow on MDAS Consumer same with Notification consumer | Samsung R&D Institute UK | CR | Agreement | Yes |
Yes
| merged | No | S5‑225856 | |||
S5‑225204 | Asynchronous operations | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑225205 | DP AI/ML management terminologies and definitions | NEC, Intel, Nokia | discussion | Endorsement | Yes |
Yes
| endorsed | No | ||||
S5‑225207 | Rel-17 CR TS 28.105 Corrections to the terms and definition description and corresponding updates | NEC, Intel, Nokia | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑225209 | YANG Mapping Rule Corrections | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑225210 | YANG Corrections | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑225212 | YANG Corrections | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑225219 | Rel-16 CR TS 28.554 Correct wrong measurement names in KPI definition | Huawei Technologies France | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑225220 | Rel-17 CR TS 28.554 Correct wrong measurement names in KPI definition | Huawei Technologies France | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑225221 | Rel-17 CR TS 28.554 Correct 5G energy consumption definitions | Huawei Technologies France | CR | Agreement | Yes |
Yes
| revised | No | S5‑225793 | |||
S5‑225793 | Rel-17 CR TS 28.554 Correct 5G energy consumption definitions | Huawei Technologies France | CR | Agreement | Yes |
Yes
| agreed | No | S5‑225221 | |||
S5‑225222 | Rel-17 CR TS 28.310 Solutions to calculate the energy consumption of PNF/VNF/VNFCs | Huawei Technologies France | CR | Agreement | Yes |
Yes
| revised | No | S5‑225792 | |||
S5‑225792 | Rel-17 CR TS 28.310 Solutions to calculate the energy consumption of PNF/VNF/VNFCs | Huawei Technologies France | CR | Agreement | Yes |
Yes
| agreed | No | S5‑225222 | |||
S5‑225223 | Rel-16 CR 28.623 adding missing interface for SMF | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑225791 | |||
S5‑225791 | Rel-16 CR 28.623 adding missing interface for SMF | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑225223 | |||
S5‑225224 | Rel-17 CR 28.623 adding missing interface for SMF | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑225790 | |||
S5‑225790 | Rel-17 CR 28.623 adding missing interface for SMF | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑225224 | |||
S5‑225225 | Rel-17 CR 28.541 update EASDF IOC | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑225789 | |||
S5‑225789 | Rel-17 CR 28.541 update EASDF IOC | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑225225 | |||
S5‑225226 | Rel-18 CR 28.541 update EASDF IOC | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑225788 | |||
S5‑225788 | Rel-18 CR 28.541 update EASDF IOC | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑225226 | |||
S5‑225227 | Rel-17 CR 28.100 correct potential solution for fault management | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑225228 | Rel-17 CR 28.104 Corrections to MDAOutputIEFilter | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑225229 | Rel-17 CR 28.541 Correction to coverageAreaTAList | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑225787 | |||
S5‑225600 | Rel-17 CR 28.541 Correction to coverageAreaTAList | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑225787 | Rel-17 CR 28.541 Correction to coverageAreaTAList | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑225229 | |||
S5‑225230 | Rel-17 CR 28.538 correct EES deployment procedure | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑225307 | YANG Corrections | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑225315 | YANG Corrections | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑225322 | Rel-17 CR 32.422 Clarification of inclusion of Management based MDT PLMN (Modification) List IE in NG messages | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑225323 | Rel-16 CR 28.313 Correction of intra-RAT and inter-RAT too early and too late handover failures description | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑225786 | |||
S5‑225786 | Rel-16 CR 28.313 Correction of intra-RAT and inter-RAT too early and too late handover failures description | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑225323 | |||
S5‑225324 | Rel-17 CR 28.313 Correction of intra-RAT and inter-RAT too early and too late handover failures description | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑225785 | |||
S5‑225785 | Rel-17 CR 28.313 Correction of intra-RAT and inter-RAT too early and too late handover failures description | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑225324 | |||
S5‑225325 | Rel-16 CR 28.552 Clarification of inter-system too early and too late handover failures and unnecessary handovers for inter-system mobility | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑225784 | |||
S5‑225784 | Rel-16 CR 28.552 Clarification of inter-system too early and too late handover failures and unnecessary handovers for inter-system mobility | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑225325 | |||
S5‑225326 | Rel-17 CR 28.552 Clarification of inter-system too early and too late handover failures and unnecessary handovers for inter-system mobility | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑225643 | |||
S5‑225643 | Rel-17 CR 28.552 Clarification of inter-system too early and too late handover failures and unnecessary handovers for inter-system mobility | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑225326 | |||
S5‑225333 | Rel-17 CR 28.404 Align Requirements of handling QMC during RAN overload to RAN specifications | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑225334 | Rel-17 CR 28.405 Align Requirements of handling QMC during RAN overload to RAN specifications | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑225335 | Rel-17 CR 28.622 Include already approved changes or enhancements of attribute properties for IOC ManagementDataCollection | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑225642 | |||
S5‑225642 | Rel-17 CR 28.622 Include already approved changes or enhancements of attribute properties for IOC ManagementDataCollection | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑225335 | |||
S5‑225336 | Rel-16 CR 28.622 Correction of attribute names of IOC TraceJob | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑225337 | Rel-17 CR 28.622 Correction of attribute names of IOC TraceJob in the attribute property table | Nokia, Nokia Shanghai Bell, Ericsson | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑225350 | Correction on NG-RAN activation mechanism | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑225608 | |||
S5‑225608 | Correction on NG-RAN activation mechanism | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑225350 | |||
S5‑225351 | Correction on NG-RAN activation mechanism | Ericsson Limited | CR | Approval | Yes |
Yes
| revised | No | S5‑225607 | |||
S5‑225607 | Correction on NG-RAN activation mechanism | Ericsson Limited | CR | Approval | Yes |
Yes
| agreed | No | S5‑225351 | |||
S5‑225352 | Rel-17 CR TS 28.623 Report Amount for M4, M5, M6 and M7 measurements in LTE | China Telecomunication Corp., Huawei | CR | Yes |
Yes
| not pursued | No | |||||
S5‑225798 | Rel-17 CR TS 28.623 Report Amount for M4, M5, M6 and M7 measurements in LTE | China Telecomunication Corp., Huawei | draftCR | - | Yes |
Yes
| approved | No | ||||
S5‑225357 | TS28.541 Rel-17 Add missing attributes n6Protection and nssaaSupport defined in CNSliceSubnetProfile to TopSliceSubnetProfile | Nokia, Nokia Shanghai Bell, KDDI | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑225358 | TS28.541 Rel-18 Add missing attributes n6Protection and nssaaSupport defined in CNSliceSubnetProfile to TopSliceSubnetProfile | Nokia, Nokia Shanghai Bell, KDDI | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑225359 | fix incorrect yaml file name in TS28.105 | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑225795 | |||
S5‑225795 | fix incorrect yaml file name in TS28.105 | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑225359 | |||
S5‑225360 | fix incorrect yaml file name in TS28.104 | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑225794 | |||
S5‑225794 | fix incorrect yaml file name in TS28.104 | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑225360 | |||
S5‑225361 | TS 28.541 Rel-17 fix TaiList issues in stage 3 in TS28541_5gcNrm.yaml | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑225362 | TS 28.541 Rel-18 fix TaiList issues in stage 3 in TS28541_5gcNrm.yaml | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑225363 | Rel-17 TS28.541 Fix vague issues in EP_Transport with Federated network modelling | Nokia, Nokia Shanghai Bell, KDDI, Juniper, TELUS | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑225364 | Rel-18 TS28.541 Fix vague issues in EP_Transport with Federated network modelling | Nokia, Nokia Shanghai Bell, KDDI, Juniper, TELUS | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑225369 | Rel-17 CR 28.312 Correct procedures for intent management | China Mobile International Ltd | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑225377 | Rel-16 CR 32.158 Align examples for DNs and URIs in clause 4.2 with object class naming conventions | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑225641 | |||
S5‑225641 | Rel-16 CR 32.158 Align examples for DNs and URIs in clause 4.2 with object class naming conventions | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑225377 | |||
S5‑225378 | Rel-17 CR 32.158 Align examples for DNs and URIs in clause 4.2 with object class naming conventions | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑225640 | |||
S5‑225640 | Rel-17 CR 32.158 Align examples for DNs and URIs in clause 4.2 with object class naming conventions | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑225378 | |||
S5‑225379 | Rel-16 CR 32.158 Clarify concept of MnS root | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑225639 | |||
S5‑225639 | Rel-16 CR 32.158 Clarify concept of MnS root | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑225379 | |||
S5‑225380 | Rel-17 CR 32.158 Clarify concept of MnS root | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑225638 | |||
S5‑225638 | Rel-17 CR 32.158 Clarify concept of MnS root | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑225380 | |||
S5‑225381 | Rel-16 CR 32.158 Clarify only leaf resources can be created | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑225637 | |||
S5‑225637 | Rel-16 CR 32.158 Clarify only leaf resources can be created | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑225381 | |||
S5‑225382 | Rel-17 CR 32.158 Clarify only leaf resources can be created | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑225636 | |||
S5‑225636 | Rel-17 CR 32.158 Clarify only leaf resources can be created | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑225382 | |||
S5‑225383 | Rel-16 CR 32.158 Clarify HTTP POST and HTTP PUT response message format | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑225635 | |||
S5‑225635 | Rel-16 CR 32.158 Clarify HTTP POST and HTTP PUT response message format | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑225383 | |||
S5‑225384 | Rel-17 CR 32.158 Clarify HTTP POST and HTTP PUT response message format | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑225634 | |||
S5‑225634 | Rel-17 CR 32.158 Clarify HTTP POST and HTTP PUT response message format | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑225384 | |||
S5‑225386 | Rel-16 CR 32.158 Correct and clarify numerous smaller issues | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑225387 | Rel-17 CR 32.158 Correct and clarify numerous smaller issues | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑225388 | Rel-17 CR TS 28.313 align the discription between TS 28.541 for CSON PCI configuration | Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑225618 | |||
S5‑225618 | Rel-17 CR TS 28.313 align the discription between TS 28.541 for CSON PCI configuration | Huawei | CR | Approval | Yes |
Yes
| agreed | No | S5‑225388 | |||
S5‑225393 | Rel-16 CR 32.158 Clarify use of the JSON Patch test operation | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑225399 | Rel-17 CR 32.158 Clarify use of the JSON Patch test operation | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑225517 | CR Rel-17 28.104 Correction of MDA request and reporting workflow | Intel, NEC | CR | Agreement | Yes |
Yes
| revised | No | S5‑225856 | |||
S5‑225856 | CR Rel-17 28.104 Correction of MDA request and reporting workflow | Intel, NEC | CR | Agreement | Yes |
Yes
| agreed | No | S5‑225517 | |||
S5‑225518 | CR Rel-17 28.622 Generalize the ThresholdInfo data type | Intel | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑225532 | Rel-16 CR 32.421 Enhancement of scope regarding RCEF | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑225533 | Rel-17 CR 32.421 Enhancement of scope regarding RCEF | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑225534 | Rel-16 CR 32.422 Enhancement of scope regarding RCEF | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑225535 | Rel-17 CR 32.422 Enhancement of scope regarding RCEF | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑225536 | Rel-16 CR 32.423 Enhancement of scope regarding RCEF | Nokia, Nokia Shanghai Bell | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑225537 | Rel-17 CR 32.423 Enhancement of scope regarding RCEF | Nokia, Nokia Shanghai Bell | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑225538 | Rel-17 CR 28.623 Correction of file names in OpenAPI Solution Set | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑225542 | Rel-17 CR TS 28.554 Updating Packet transmission reliability KPI in DL on N3 | Samsung Electronics Nordic AB | CR | Approval | Yes |
Yes
| revised | No | S5‑225633 | |||
S5‑225633 | Rel-17 CR TS 28.554 Updating Packet transmission reliability KPI in DL on N3 | Samsung Electronics Nordic AB | CR | Approval | Yes |
Yes
| agreed | No | S5‑225542 | |||
S5‑225543 | Rel-18 CR TS 28.554 Updating Packet transmission reliability KPI in DL on N3 | Samsung Electronics Nordic AB | CR | Approval | Yes |
Yes
| revised | No | S5‑225632 | |||
S5‑225632 | Rel-18 CR TS 28.554 Updating Packet transmission reliability KPI in DL on N3 | Samsung Electronics Nordic AB | CR | Approval | Yes |
Yes
| agreed | No | S5‑225543 | |||
S5‑225544 | Rel-16 CR 28.623 Correction of attribute names according to Upper Camel Case Convention and WKA | Nokia, Nokia Shanghai Bell, Ericsson | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑225545 | Rel-17 CR 28.623 Correction of attribute names according to Upper Camel Case Convention and WKA | Nokia, Nokia Shanghai Bell, Ericsson | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑225553 | Rel-17 CR TS 28.105 Clarifications and corrections of Use cases | NEC, Intel | CR | Agreement | Yes |
Yes
| revised | No | S5‑225629 | |||
S5‑225629 | Rel-17 CR TS 28.105 Clarifications and corrections of Use cases | NEC, Intel | CR | Agreement | Yes |
Yes
| agreed | No | S5‑225553 | |||
S5‑225557 | Discussion paper on state management and network slicing | L.M. Ericsson Limited | discussion | Endorsement | Yes |
Yes
| not pursued | No | ||||
S5‑225558 | Clarify and update state management for network slicing | L.M. Ericsson Limited | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑225559 | Clarify and update state management for network slicing | L.M. Ericsson Limited | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑225560 | Clarify and update state management for network slicing | L.M. Ericsson Limited | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑225561 | Clarify and update state management for network slicing | L.M. Ericsson Limited | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑225562 | Add missing tags in stage 3 | L.M. Ericsson Limited | CR | Approval | Yes |
Yes
| revised | No | S5‑225628 | |||
S5‑225628 | Add missing tags in stage 3 | L.M. Ericsson Limited | CR | Approval | Yes |
Yes
| agreed | No | S5‑225562 | |||
S5‑225563 | Remove example from network slice subnet instance modification | L.M. Ericsson Limited | CR | Approval | Yes |
Yes
| revised | No | S5‑225627 | |||
S5‑225627 | Remove example from network slice subnet instance modification | L.M. Ericsson Limited | CR | Approval | Yes |
Yes
| agreed | No | S5‑225563 | |||
S5‑225564 | Remove example from network slice subnet instance modification | L.M. Ericsson Limited | CR | Approval | Yes |
Yes
| revised | No | S5‑225626 | |||
S5‑225626 | Remove example from network slice subnet instance modification | L.M. Ericsson Limited | CR | Approval | Yes |
Yes
| agreed | No | S5‑225564 | |||
S5‑225565 | Remove example from network slice instance modification | L.M. Ericsson Limited | CR | Approval | Yes |
Yes
| revised | No | S5‑225625 | |||
S5‑225625 | Remove example from network slice instance modification | L.M. Ericsson Limited | CR | Approval | Yes |
Yes
| agreed | No | S5‑225565 | |||
S5‑225566 | Rel-17 CR TS 28.105 Clarifications and corrections into the Class definitions and Attribute properties | NEC, Intel | CR | Agreement | Yes |
Yes
| revised | No | S5‑225630 | |||
S5‑225630 | Rel-17 CR TS 28.105 Clarifications and corrections into the Class definitions and Attribute properties | NEC, Intel | CR | Agreement | Yes |
Yes
| agreed | No | S5‑225566 | |||
S5‑225567 | Remove example from network slice instance modification | L.M. Ericsson Limited | CR | Approval | Yes |
Yes
| revised | No | S5‑225624 | |||
S5‑225624 | Remove example from network slice instance modification | L.M. Ericsson Limited | CR | Approval | Yes |
Yes
| agreed | No | S5‑225567 | |||
S5‑225568 | Rel-17 CR TS 28.105 Correction and clarifications of the Requirements | NEC, Intel | CR | Agreement | Yes |
Yes
| revised | No | S5‑225631 | |||
S5‑225631 | Rel-17 CR TS 28.105 Correction and clarifications of the Requirements | NEC, Intel | CR | Agreement | Yes |
Yes
| agreed | No | S5‑225568 | |||
S5‑225569 | Correct role in network slice subnet allocation use case | L.M. Ericsson Limited | CR | Approval | Yes |
Yes
| revised | No | S5‑225622 | |||
S5‑225622 | Correct role in network slice subnet allocation use case | L.M. Ericsson Limited | CR | Approval | Yes |
Yes
| agreed | No | S5‑225569 | |||
S5‑225570 | Correct role in network slice subnet allocation use case | L.M. Ericsson Limited, Deutsche Telekom | CR | Approval | Yes |
Yes
| revised | No | S5‑225621 | |||
S5‑225621 | Correct role in network slice subnet allocation use case | L.M. Ericsson Limited, Deutsche Telekom | CR | Approval | Yes |
Yes
| agreed | No | S5‑225570 | |||
S5‑225571 | Clarify 3GPP management system capability requirement | L.M. Ericsson Limited, Deutsche Telekom | CR | Approval | Yes |
Yes
| revised | No | S5‑225623 | |||
S5‑225623 | Clarify 3GPP management system capability requirement | L.M. Ericsson Limited, Deutsche Telekom | CR | Approval | Yes |
Yes
| agreed | No | S5‑225571 | |||
S5‑225572 | Clarify network slice subnet configuration use case and requirement | L.M. Ericsson Limited | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑225573 | Clarify network slice subnet configuration use case and requirement | L.M. Ericsson Limited | CR | Yes |
Yes
| not pursued | No | |||||
S5‑225574 | Clarify translation in network slice allocation use case | L.M. Ericsson Limited | CR | Approval | Yes |
Yes
| revised | No | S5‑225620 | |||
S5‑225620 | Clarify translation in network slice allocation use case | L.M. Ericsson Limited | CR | Approval | Yes |
Yes
| agreed | No | S5‑225574 | |||
S5‑225575 | Clarify capacity planning use case and requirement | L.M. Ericsson Limited | CR | Approval | Yes |
Yes
| merged | No | S5‑225829 | |||
S5‑225576 | Clarification and update of deallocation use case | L.M. Ericsson Limited | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑225577 | Clarification and update of deallocation use case | L.M. Ericsson Limited | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑225588 | Rel-17 CR for TS32.130 delete redundant figure | ZTE Corporation | CR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑225589 | Rel-17 CR for TS28.540 editorialCorrections | ZTE Corporation | CR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑225590 | Rel-17 CR for TS28.552 Correct Mean and Max Time of requested conditional handover executions | ZTE Corporation | CR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑225605 | Rel-15 CR TS 28.531 Remove example from network slice subnet instance modification | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑225606 | Rel-15 CR TS 28.531 Remove example from network slice instance modification | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
6.4 | Intelligence and Automation |   | ||||||||||
6.4.1 | Self-Configuration of RAN NEs |   | ||||||||||
6.4.1.1 | RANSC_WoP#1 | S5‑225213 | TS 28.317 Use case and requirement for ARCF data handling | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||
S5‑225214 | 28.317 Usecase and requirement for Self-configuration Management | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑225353 | TS 28.317 Add Concept | China Mobile, Huawei | pCR | Yes |
Yes
| noted | No | |||||
6.4.1.2 | RANSC_WoP#2 |   | ||||||||||
6.4.1.3 | RANSC_WoP#3 |   | ||||||||||
6.5 | Management Architecture and Mechanisms |   | ||||||||||
6.5.1 | Network slicing provisioning rules |   | ||||||||||
6.5.1.1 | NSRULE_WoP#1 | S5‑225550 | Specify network slicing provisioning rules requirements | L.M. Ericsson Limited, Deutsche Telekom | CR | Approval | Yes |
Yes
| not pursued | No | ||
6.5.1.2 | NSRULE_WoP#2 | S5‑225096 | Rel-18 CR TS 28.541 Add NRM for network slice isolation | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | ||
S5‑225156 | Add network slice isolation use case and requirements | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑225552 | Add network slice rules to NRM | L.M. Ericsson Limited, Deutsche Telekom | CR | Approval | Yes |
Yes
| not pursued | No | ||||
6.5.2 | Additional NRM features phase 2 |   | ||||||||||
6.5.2.1 | AdNRM_ph2_WoP#1 |   | ||||||||||
6.5.2.2 | AdNRM_ph2_WoP#2 | S5‑225061 | Enhance 5G Core managed NF Profile NRM fragment | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||
S5‑225062 | NRM enhancements for UPFFunction | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑225063 | TS28.541 Rel-18 NRM enhancements for NSSFFunction | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑225064 | TS28.541 Rel-18 NRM enhancements for PCFFunction | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑225839 | |||
S5‑225839 | TS28.541 Rel-18 NRM enhancements for PCFFunction | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑225064 | |||
S5‑225065 | TS28.541 Rel-18 NRM enhancements for UDMFunction | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑225838 | |||
S5‑225838 | TS28.541 Rel-18 NRM enhancements for UDMFunction | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑225065 | |||
S5‑225066 | TS28.541 Rel-18 NRM enhancements for UDRFunction | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑225837 | |||
S5‑225837 | TS28.541 Rel-18 NRM enhancements for UDRFunction | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑225066 | |||
S5‑225119 | Add Scheduler IOC - YANG | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑225120 | Rel-18 CR 28.541 Add Enhanced QoS support in NRM (stage 2) | Ericsson Inc. | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑225121 | Rel-18 CR 28.541 Add Enhanced QoS support in NRM (stage 3, YANG) | Ericsson Inc. | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑225122 | Rel-18 28.541 Add BWP set support to NRM (stage 2) | Ericsson Inc. | CR | Approval | Yes |
Yes
| revised | No | S5‑225832 | |||
S5‑225832 | Rel-18 28.541 Add BWP set support to NRM (stage 2) | Ericsson Inc. | CR | Approval | Yes |
Yes
| agreed | No | S5‑225122 | |||
S5‑225123 | Rel-18 28.541 Add BWP set support to NRM (stage 3, YANG) | Ericsson Inc. | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑225195 | DP on structure proposal for new generic NRM specification | Huawei | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑225196 | Rel-18 CR 28.541 Add BWP set support to NRM (Stage3, YAML) | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑225831 | |||
S5‑225831 | Rel-18 CR 28.541 Add BWP set support to NRM (Stage3, YAML) | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑225196 | |||
S5‑225327 | Rel-18 Input to draftCR 28.622 Modification and Correction of Scheduler IOC (stage 2) | Nokia, Nokia Shanghai Bell | other | Approval | Yes |
Yes
| revised | No | S5‑225836 | |||
S5‑225836 | Rel-18 Input to draftCR 28.622 Modification and Correction of Scheduler IOC (stage 2) | Nokia, Nokia Shanghai Bell | other | Approval | Yes |
Yes
| approved | No | S5‑225327 | |||
S5‑225328 | Rel-18 Input to draftCR 28.623 Modification and Correction of Scheduler IOC (stage 2) | Nokia, Nokia Shanghai Bell | other | Approval | Yes |
Yes
| revised | No | S5‑225835 | |||
S5‑225835 | Rel-18 Input to draftCR 28.623 Modification and Correction of Scheduler IOC (stage 2) | Nokia, Nokia Shanghai Bell | other | Approval | Yes |
Yes
| approved | No | S5‑225328 | |||
S5‑225329 | DP on Introduction of Stage 2 Common Data Type Definitions | Nokia, Nokia Shanghai Bell | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑225330 | Draft Skeleton for TS on Common Data Type Definitions | Nokia, Nokia Shanghai Bell | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑225331 | Rel-18 Input to draftCR 28.622 Introduce Condition Monitor and enhance PerfMetricJob to allow that service is executed only if conditions are satisfied (stage 2) | Nokia, Nokia Shanghai Bell | other | Approval | Yes |
Yes
| revised | No | S5‑225834 | |||
S5‑225834 | Rel-18 Input to draftCR 28.622 Introduce Condition Monitor and enhance PerfMetricJob to allow that service is executed only if conditions are satisfied (stage 2) | Nokia, Nokia Shanghai Bell | other | Approval | Yes |
Yes
| approved | No | S5‑225331 | |||
S5‑225332 | Rel-18 Input to draftCR 28.623 Introduce Condition Monitor and enhance PerfMetricJob to allow that service is executed only if conditions are satisfied (stage 2) | Nokia, Nokia Shanghai Bell | other | Approval | Yes |
Yes
| revised | No | S5‑225833 | |||
S5‑225833 | Rel-18 Input to draftCR 28.623 Introduce Condition Monitor and enhance PerfMetricJob to allow that service is executed only if conditions are satisfied (stage 2) | Nokia, Nokia Shanghai Bell | other | Approval | Yes |
Yes
| approved | No | S5‑225332 | |||
S5‑225495 | Revised WID on Additional NRM features phase 2 | Nokia, Nokia Shanghai Bell | WID revised | Approval | Yes |
Yes
| noted | No | ||||
S5‑225539 | Rel-18 Input to draftCR 28.537 Requirements for Conditional Execution of Management Services | Nokia, Nokia Shanghai Bell | other | Approval | Yes |
Yes
| noted | No | ||||
6.5.2.3 | AdNRM_ph2_WoP#3 | S5‑225197 | Rel-18 CR TS 28.541 Update NWDAFFunction IOC to support management and control purpose | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑225830 | |
S5‑225830 | Rel-18 CR TS 28.541 Update NWDAFFunction IOC to support management and control purpose | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑225197 | |||
6.5.3 | Enhanced Edge Computing Management |   | ||||||||||
6.5.3.1 | eECM_WoP#1 | S5‑225135 | Rel-18 InputToDraftCR 28.538 EAS Profile.doc | Samsung R&D Institute UK | other | Agreement | Yes |
Yes
| revised | No | S5‑225842 | |
S5‑225842 | Rel-18 InputToDraftCR 28.538 EAS Profile.doc | Samsung R&D Institute UK | other | Agreement | Yes |
Yes
| approved | No | S5‑225135 | |||
S5‑225136 | Rel-18 draftCR to CR conversion for eECM | Samsung R&D Institute UK | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑225137 | Rel-18 InputToDraftCR 28.538 Asynchronous support | Samsung R&D Institute UK | other | Agreement | Yes |
Yes
| noted | No | ||||
S5‑225174 | Discussion Paper on EES initiated EAS deployment | Samsung R&D Institute UK | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑225841 | |||
S5‑225841 | Discussion Paper on EES initiated EAS deployment | Samsung R&D Institute UK | discussion | Endorsement | Yes |
Yes
| endorsed | No | S5‑225174 | |||
S5‑225177 | Rel-18 InputToDraftCR 28.538 EES initiated EAS Deployment | Samsung R&D Institute UK | other | Agreement | Yes |
Yes
| noted | No | ||||
S5‑225231 | Rel-18 CR 28.552 update measurement for EES | Huawei | CR | Agreement | Yes |
Yes
| merged | No | S5‑225844 | |||
S5‑225232 | InputToDraftCR 28.538 ECSFunction IOC update | Huawei | other | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑225257 | Rel-18 CR 28.538 ECSFunction IOC update | Huawei Technologies Sweden AB | CR | Agreement | Yes |
Yes
| revised | No | S5‑225840 | |||
S5‑225840 | Rel-18 CR 28.538 ECSFunction IOC update | Huawei Technologies Sweden AB | CR | Agreement | Yes |
Yes
| agreed | No | S5‑225257 | |||
S5‑225345 | Rel-18 CR 28.622 Add stage 2 solution for LcmJob IOC | Intel Korea, Ltd. | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑225346 | Rel-18 CR 28.623 Add stage 3 solution for LcmJob IOC | Intel Korea, Ltd. | CR | Approval | Yes |
Yes
| not pursued | No | ||||
6.5.3.2 | eECM_WoP#2 | S5‑225175 | Rel-18 InputToDraftCR 28.538 GSMA OP and ECM concept mapping | Samsung R&D Institute UK | other | Agreement | Yes |
Yes
| revised | No | S5‑225847 | |
S5‑225847 | Rel-18 InputToDraftCR 28.538 GSMA OP and ECM concept mapping | Samsung R&D Institute UK | other | Agreement | Yes |
Yes
| approved | No | S5‑225175 | |||
S5‑225176 | Rel-18 InputToDraftCR 28.538 Availability Zone.doc | Samsung R&D Institute UK | other | Agreement | Yes |
Yes
| revised | No | S5‑225846 | |||
S5‑225846 | Rel-18 InputToDraftCR 28.538 Availability Zone.doc | Samsung R&D Institute UK | other | Agreement | Yes |
Yes
| approved | No | S5‑225176 | |||
S5‑225514 | Rel-18 CR 28.538 add a use case for EAS discovery failure measurement | Intel Korea, Ltd. | CR | Approval | Yes |
Yes
| revised | No | S5‑225845 | |||
S5‑225845 | Rel-18 CR 28.538 add a use case for EAS discovery failure measurement | Intel Korea, Ltd. | CR | Approval | Yes |
Yes
| agreed | No | S5‑225514 | |||
S5‑225515 | Rel-18 CR 28.552 add a EAS discovery failure measurement | Intel Korea, Ltd. | CR | Approval | Yes |
Yes
| revised | No | S5‑225844 | |||
S5‑225844 | Rel-18 CR 28.552 add a EAS discovery failure measurement | Intel Korea, Ltd. | CR | Approval | Yes |
Yes
| agreed | No | S5‑225515 | |||
S5‑225516 | Rel-18 CR 28.538 Add a procedure of EAS instantiation triggered by measurement data | Intel Korea, Ltd. | CR | Approval | Yes |
Yes
| revised | No | S5‑225843 | |||
S5‑225843 | Rel-18 CR 28.538 Add a procedure of EAS instantiation triggered by measurement data | Intel Korea, Ltd. | CR | Approval | Yes |
Yes
| agreed | No | S5‑225516 | |||
6.5.3.3 | eECM_WoP#3 |   | ||||||||||
6.5.4 | Enhancement of QoE Measurement Collection |   | ||||||||||
6.5.4.1 | eQoE_WoP#1 | S5‑225500 | Adding Signalling Based Activation for NR | Ericsson Limited, Nokia | CR | Approval | Yes |
Yes
| revised | No | S5‑225850 | |
S5‑225850 | Adding Signalling Based Activation for NR | Ericsson Limited, Nokia | CR | Approval | Yes |
Yes
| agreed | No | S5‑225500 | |||
S5‑225501 | Handling of QoE measurement collection at handover in NR | Ericsson Limited, Nokia | CR | Approval | Yes |
Yes
| revised | No | S5‑225849 | |||
S5‑225849 | Handling of QoE measurement collection at handover in NR | Ericsson Limited, Nokia | CR | Approval | Yes |
Yes
| agreed | No | S5‑225501 | |||
S5‑225504 | Adding QMC job | Ericsson Limited, Nokia | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑225506 | CR 28.623 Add QMC job (stage 3, YANG) | Ericsson Inc. | CR | Approval | Yes |
Yes
| revised | No | S5‑225848 | |||
S5‑225848 | CR 28.623 Add QMC job (stage 3, YANG) | Ericsson Inc. | CR | Approval | Yes |
Yes
| agreed | No | S5‑225506 | |||
6.5.4.2 | eQoE_WoP#2 | S5‑225420 | support QoE metrics collection for multiple MCEs | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | ||
S5‑225460 | support QoE metrics collection for multiple MCEs | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | ||||
6.5.5 | Access control for management service |   | ||||||||||
6.5.5.1 | MSAC_WoP#1 |   | ||||||||||
6.5.5.2 | MSAC_WoP#2 | S5‑225355 | Rel-18 TS28.532 enhance OpenAPI to support access control | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | ||
S5‑225356 | Rel-18 TS28.533 enhancement to support access control | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | ||||
6.5.5.3 | MSAC_WoP#3 |   | ||||||||||
6.5.6 | 5G performance measurements and KPIs phase 3 |   | ||||||||||
6.5.6.1 | PM_KPI_5G_Ph3_WoP#1 |   | ||||||||||
6.5.6.2 | PM_KPI_5G_Ph3_WoP#2 | S5‑225192 | R18 CR TS 28.552 Add use case of remote interference related performance measurement | China Telecomunication Corp., Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||
S5‑225338 | Rel-18 CR 28.313 Add beam specific inter-RAT handover counters related to MRO | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| endorsed | No | ||||
S5‑225339 | Rel-18 CR 28.552 Add beam specific inter-system handover counters related to MRO | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑225852 | |||
S5‑225852 | Rel-18 CR 28.552 Add beam specific inter-system handover counters related to MRO | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑225339 | |||
S5‑225344 | Rel-18 CR 28.552 Add the per SSB RSRQ and SINR measurements | Intel Korea, Ltd. | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑225354 | Rel-18 CR TS 28.552 Add measurements for UE throughput of Dedicated BWP | China Telecomunication Corp., ZTE, Nokia | CR | Agreement | Yes |
Yes
| revised | No | S5‑225851 | |||
S5‑225851 | Rel-18 CR TS 28.552 Add measurements for UE throughput of Dedicated BWP | China Telecomunication Corp., ZTE, Nokia | CR | Agreement | Yes |
Yes
| agreed | No | S5‑225354 | |||
S5‑225417 | CR TS28.552 Add new measurement on average air-interface efficiency | China Unicom, China Telecom | CR | Approval | Yes |
Yes
| not pursued | No | ||||
6.5.6.3 | PM_KPI_5G_Ph3_WoP#3 | S5‑225110 | Rel-18 CR 28.550 GPB schema introduction for PM streaming | Nokia, Nokia Shanghai Bell, Mavenir, Intel | CR | Approval | Yes |
Yes
| revised | No | S5‑225853 | |
S5‑225853 | Rel-18 CR 28.550 GPB schema introduction for PM streaming | Nokia, Nokia Shanghai Bell, Mavenir, Intel | CR | Approval | Yes |
Yes
| agreed | No | S5‑225110 | |||
S5‑225115 | DP on enhancing streaming format of PMs | Nokia, Nokia Shanghai Bell | discussion | Endorsement | No |
Yes
| withdrawn | Yes | ||||
S5‑225116 | Rel-18 CR 28.550 Enhancing the streaming format of PMs | Nokia, Nokia Shanghai Bell | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑225319 | DP to add GPB format for PM Counter streaming | Ericsson Inc. | discussion | Endorsement | Yes |
Yes
| endorsed | No | ||||
6.6 | Support of New Services |   | ||||||||||
6.6.1 | Enhancements of EE for 5G Phase 2 |   | ||||||||||
6.6.1.1 | EE5GPLUS_Ph2_WoP#1 | S5‑225396 | Rel-18 pCR TR 28.913 Add key issue for Energy Saving compensation procedure | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑225864 | |
S5‑225864 | Rel-18 pCR TR 28.913 Add key issue for Energy Saving compensation procedure | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑225396 | |||
S5‑225555 | Add new formula for the estimation of the energy consumption | Huawei Technologies France | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
6.6.1.2 | EE5GPLUS_Ph2_WoP#2 |   | ||||||||||
6.6.2 | Network slice provisioning enhancement |   | ||||||||||
6.6.2.1 | eNETSLICE_PRO_WoP#1 | S5‑225087 | Rel-18 CR TS 28.623 Add AvailabilityStatus and LifecycleState to comDefs | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | ||
S5‑225088 | Rel-18 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‑225089 | Rel-18 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‑225134 | Rel-18 CR 28.531 Fixing provisioning data reporting service | Samsung R&D Institute UK | CR | Agreement | Yes |
Yes
| revised | No | S5‑225855 | |||
S5‑225855 | Rel-18 CR 28.531 Fixing provisioning data reporting service | Samsung R&D Institute UK | CR | Agreement | Yes |
Yes
| agreed | No | S5‑225134 | |||
S5‑225546 | Discussion paper on asynchronous operations support for network slicing | L.M. Ericsson Limited | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑225547 | Add asynchronous network slicing provisioning procedures | L.M. Ericsson Limited, Deutsche Telekom | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑225548 | Add Job IOCs for asynchronous network slicing provisioning procedures | L.M. Ericsson Limited, Deutsche Telekom | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑225549 | Add use case and requirement for obtaining network slice subnet capability information | L.M. Ericsson Limited, Deutsche Telekom | CR | Approval | Yes |
Yes
| not pursued | No | ||||
6.6.2.2 | eNETSLICE_PRO_WoP#2 | S5‑225075 | TS28.531 Update operations of allocateNsi, allocateNssi, deallocateNsi, deallocateNssi | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | ||
S5‑225086 | Rel-18 CR TS 28.531 Update procedures for modification of Network Slice and Network Slice Subnet MOIs | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑225854 | |||
S5‑225854 | Rel-18 CR TS 28.531 Update procedures for modification of Network Slice and Network Slice Subnet MOIs | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑225086 | |||
S5‑225090 | Rel-18 CR TS 28.531 Removal of redundant network slice modification use case | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑225091 | Rel-18 CR TS 28.531 Add provisioning procedure for slice activation and deactivation using adminsitrative state | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑225180 | Rel-18 CR 28.531 Update procedures and operations to support asynchronous mode of operation.doc | Samsung R&D Institute UK | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑225184 | Rel-17 CR 28.541 adding processMonitor in NetworkSlice and NetworkSliceSubnet.doc | Samsung R&D Institute UK | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑225394 | Rel-18 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‑225395 | Rel-18 CR TS 28.531 Correction to informative annex on network slice journey | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | ||||
6.7 | Intelligence and Automation |   | ||||||||||
6.7.1 | Study on enhancement of autonomous network levels |   | ||||||||||
6.7.1.1 | FS_eANL_WoP#1 | S5‑225308 | pCR 28.910 Add introduction on relevant SI/WI in 3GPP | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑225679 | S5‑224127 |
S5‑225679 | pCR 28.910 Add introduction on relevant SI/WI in 3GPP | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑225308 | |||
S5‑225309 | pCR TR 28.910 Add key issue for enhancement of ANL for fault management | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| noted | No | S5‑224128 | |||
S5‑225313 | pCR TR 28.910 Add key issues for enhancement of network optimization | Huawei,China Mobile | pCR | Approval | Yes |
Yes
| noted | No | S5‑224049 | |||
S5‑225314 | pCR TR 28.910 Add key issues for enhancement of ANL for RAN NE deployment | Huawei,China Mobile | pCR | Approval | Yes |
Yes
| noted | No | S5‑224050 | |||
6.7.1.2 | FS_eANL_WoP#2 |   | ||||||||||
6.7.1.3 | FS_eANL_WoP#3 | S5‑225233 | pCR TR 28.910 Add key issue for autonomous network level for 5GC network disaster recovery | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||
S5‑225365 | Add key issue for autonomous network level for network slice subnet related requirements determination | AsiaInfo Technologies Inc | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑225478 | pCR TR 28.910 Add autonomous network level for service experience optimization | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
6.7.1.4 | FS_eANL_WoP#4 |   | ||||||||||
6.7.2 | Study on evaluation of autonomous network levels |   | ||||||||||
6.7.2.1 | FS_ANLEVA_WoP#1 | S5‑225310 | pCR 28.909 Add key issue of evaluation objects for autonomous network levels evaluation | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| noted | No | S5‑224129 | |
S5‑225311 | 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‑224130 | |||
S5‑225587 | pCR 28.909 Add ANLS evaluation of autonomous network | ZTE Corporation,China Mobile | pCR | Approval | Yes |
Yes
| not treated | No | ||||
6.7.2.2 | FS_ANLEVA_WoP#2 | S5‑225234 | pCR TR 28.909 Add key issues for KEI of autonomous network levels evaluation for 5GC energy saving | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||
S5‑225316 | pCR TR 28.909 Add key issues for KEI of autonomous network levels evaluation for radio network optimization | Huawei,China Mobile | pCR | Approval | Yes |
Yes
| noted | No | S5‑224046 | |||
S5‑225317 | pCR TR 28.909 Add general process of evaluating the autonomous network level | Huawei,China Mobile | pCR | Approval | Yes |
Yes
| noted | No | S5‑224047 | |||
6.7.2.3 | FS_ANLEVA_WoP#3 |   | ||||||||||
6.7.2.4 | FS_ANLEVA_WoP#4 |   | ||||||||||
6.7.3 | Study on enhanced intent driven management services for mobile networks |   | ||||||||||
6.7.3.1 | FS_eIDMS_MN_WoP#1 |   | ||||||||||
6.7.3.2 | FS_eIDMS_MN_WoP#2 | S5‑225056 | pCR 28.912 Potential solution on Intent conflicts | Nokia Italy | pCR | Approval | Yes |
Yes
| revised | No | S5‑225680 | |
S5‑225680 | pCR 28.912 Potential solution on Intent conflicts | Nokia Italy | pCR | Approval | Yes |
Yes
| approved | No | S5‑225056 | |||
S5‑225057 | pCR TR28.912 Key issue on enablers for Intent Fulfillment | Nokia Italy | pCR | Approval | Yes |
Yes
| revised | No | S5‑225685 | |||
S5‑225685 | pCR TR28.912 Key issue on enablers for Intent Fulfillment | Nokia Italy | pCR | Approval | Yes |
Yes
| approved | No | S5‑225057 | |||
S5‑225058 | pCR TR28.912 use case on Intent to AIML Capability Mapping | Nokia Italy | pCR | Approval | Yes |
Yes
| revised | No | S5‑225689 | |||
S5‑225689 | pCR TR28.912 use case on Intent to AIML Capability Mapping | Nokia Italy | pCR | Approval | Yes |
Yes
| approved | No | S5‑225058 | |||
S5‑225059 | pCR 28.912 Intent driven SON orchestration | Nokia Italy | pCR | Approval | Yes |
Yes
| revised | No | S5‑225691 | |||
S5‑225691 | pCR 28.912 Intent driven SON orchestration | Nokia Italy | pCR | Approval | Yes |
Yes
| approved | No | S5‑225059 | |||
S5‑225060 | pCR 28.912 Solution on AIMLEntity Capability Discovery and mapping | Nokia Italy | pCR | Approval | Yes |
Yes
| revised | No | S5‑225690 | |||
S5‑225690 | pCR 28.912 Solution on AIMLEntity Capability Discovery and mapping | Nokia Italy | pCR | Approval | Yes |
Yes
| approved | No | S5‑225060 | |||
S5‑225198 | pCR TR 28.912 Rapporteur clean up | Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑225199 | pCR TR 28.912 Add issue for enhencement of generic intent information model definition | Huawei, Deutsche Telekom | pCR | Approval | Yes |
Yes
| revised | No | S5‑225688 | |||
S5‑225688 | pCR TR 28.912 Add issue for enhencement of generic intent information model definition | Huawei, Deutsche Telekom | pCR | Approval | Yes |
Yes
| approved | No | S5‑225199 | |||
S5‑225200 | pCR TR 28.912 Update Issue#4.3 enhancement of radio network intent expectation to include the context for transport | Huawei, Deutsche Telekom | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑225201 | pCR TR 28.912 Add issue for Intent handling capability obtaining | Huawei, Deutsche Telekom | pCR | Approval | Yes |
Yes
| revised | No | S5‑225687 | |||
S5‑225687 | pCR TR 28.912 Add issue for Intent handling capability obtaining | Huawei, Deutsche Telekom | pCR | Approval | Yes |
Yes
| approved | No | S5‑225201 | |||
S5‑225202 | pCR TR 28.912 Add conclusion and recommendation for existing key issues | Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑225203 | Presentation sheet of TR28.912 for information | Huawei | other | Approval | Yes |
Yes
| approved | No | ||||
S5‑225235 | pCR TR 28.912 add potential solution for 5GC optimization | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑225683 | |||
S5‑225683 | pCR TR 28.912 add potential solution for 5GC optimization | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑225235 | |||
S5‑225236 | pCR TR 28.912 add potential solution for 5GC fault management | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑225682 | |||
S5‑225682 | pCR TR 28.912 add potential solution for 5GC fault management | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑225236 | |||
S5‑225318 | pCR TR 28.912 Add TMF procedure mappings | Ericsson Inc. | pCR | Approval | Yes |
Yes
| revised | No | S5‑225692 | |||
S5‑225692 | pCR TR 28.912 Add TMF procedure mappings | Ericsson Inc. | pCR | Approval | Yes |
Yes
| approved | No | S5‑225318 | |||
S5‑225366 | Add key issue for intent driven approach for fault predication | AsiaInfo Technologies Inc | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑225367 | Add key issue for intent feasibility check | AsiaInfo Technologies Inc | pCR | Approval | Yes |
Yes
| revised | No | S5‑225686 | |||
S5‑225686 | Add key issue for intent feasibility check | AsiaInfo Technologies Inc | pCR | Approval | Yes |
Yes
| approved | No | S5‑225367 | |||
S5‑225372 | pCR 28.912 Add potential solutions for intent conflict | China Mobile E-Commerce Co. | pCR | Approval | Yes |
Yes
| revised | No | S5‑225681 | |||
S5‑225681 | pCR 28.912 Add potential solutions for intent conflict | China Mobile E-Commerce Co. | pCR | Approval | Yes |
Yes
| approved | No | S5‑225372 | |||
S5‑225375 | pCR 28.912 Add key issue for intent execution monitoring | China Mobile E-Commerce Co. | pCR | Approval | Yes |
Yes
| revised | No | S5‑225684 | |||
S5‑225684 | pCR 28.912 Add key issue for intent execution monitoring | China Mobile E-Commerce Co. | pCR | Approval | Yes |
Yes
| approved | No | S5‑225375 | |||
S5‑225414 | pCR 28.912 issue#4.2.1 Intent conflicts description enhancement | CMDI | pCR | Decision | Yes |
Yes
| approved | No | ||||
S5‑225415 | Technical Discussion on General Class Condition Enhancement | CMDI | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑225416 | pCR 28.912 issue#4.x General class Condition enhancement | CMDI | pCR | Decision | Yes |
Yes
| noted | No | ||||
S5‑225421 | pCR TR 28.912 Update issue for enhancement of radio network intent expectation | Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑225521 | pCR TS 28.912 Add Intent Reporting support | Ericsson Inc. | pCR | Approval | Yes |
Yes
| noted | No | ||||
6.7.3.3 | FS_eIDMS_MN_WoP#3 |   | ||||||||||
6.7.3.4 | FS_eIDMS_MN_WoP#4 |   | ||||||||||
6.7.4 | Study on intent-driven management for network slicing |   | ||||||||||
6.7.4.1 | FS_NETSLICE_IDMS_WoP#1 | S5‑225237 | pCR TR 28.836 add use case of slice modification | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||
S5‑225238 | pCR 28.836 use case of Intent driven management for network slice feasibility check | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑225239 | pCR TR 28.836 add use case of intent LCM | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑225554 | Discussion paper on study intent driven management for network slicing | L.M. Ericsson Limited | discussion | Endorsement | No |
Yes
| withdrawn | Yes | ||||
6.7.4.2 | FS_NETSLICE_IDMS_WoP#2 |   | ||||||||||
6.7.4.3 | FS_NETSLICE_IDMS_WoP#3 | S5‑225240 | pCR TR 28.836 add intent model IntentExpectation for network slicing instance | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||
6.7.4.4 | FS_NETSLICE_IDMS_WoP#4 |   | ||||||||||
6.7.4.5 | FS_NETSLICE_IDMS_WoP#5 |   | ||||||||||
6.7.5 | Study on AI/ ML management |   | ||||||||||
6.7.5.1 | FS_AIML_MGMT_WoP#1 | S5‑225033 | pCR TR28.908 Updates terms | Nokia Italy | pCR | Approval | No |
Yes
| withdrawn | Yes | ||
S5‑225034 | pCR TR28.908 clarification on AIMLEntity Capability Mapping | Nokia Italy | pCR | Approval | Yes |
Yes
| revised | No | S5‑225696 | |||
S5‑225696 | pCR TR28.908 clarification on AIMLEntity Capability Mapping | Nokia Italy | pCR | Approval | Yes |
Yes
| approved | No | S5‑225034 | |||
S5‑225035 | pCR TR28.908 Potential Solution on AIMLEntity Capability Discovery | Nokia Italy | pCR | Approval | Yes |
Yes
| revised | No | S5‑225695 | |||
S5‑225695 | pCR TR28.908 Potential Solution on AIMLEntity Capability Discovery | Nokia Italy | pCR | Approval | Yes |
Yes
| approved | No | S5‑225035 | |||
S5‑225389 | pCR TR 28.908 Add AIML capabilities deployment scenarios | Huawei, Deutsche Telekom | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑225392 | pCR TR 28.908 Add illustration on AI-ML workflow | Huawei | pCR | Approval | Yes |
Yes
| merged | No | S5‑225693 | |||
S5‑225519 | pCR 28.908 Enhance AI-ML workflow | Intel, NEC | pCR | Approval | Yes |
Yes
| revised | No | S5‑225693 | |||
S5‑225693 | pCR 28.908 Enhance AI-ML workflow | Intel, NEC | pCR | Approval | Yes |
Yes
| approved | No | S5‑225519 | |||
6.7.5.2 | FS_AIML_MGMT_WoP#2 |   | ||||||||||
6.7.5.3 | FS_AIML_MGMT_WoP#3 | S5‑225036 | pCR 28.908 Potential solution on AIML Inference History | Nokia Italy | pCR | Approval | Yes |
Yes
| revised | No | S5‑225694 | |
S5‑225694 | pCR 28.908 Potential solution on AIML Inference History | Nokia Italy | pCR | Approval | Yes |
Yes
| approved | No | S5‑225036 | |||
S5‑225037 | pCR 28.908 Add use case on AIML data trustworthiness | Nokia Italy | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑225038 | pCR 28.908 Add use case on AIML training trustworthiness | Nokia Italy | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑225039 | pCR 28.908 Add use case on AIML trustworthiness indicators | Nokia Italy | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑225496 | pCR TR 28.908 Add use case on AI-ML Security | Ericsson-LG Co., LTD | pCR | Agreement | Yes |
Yes
| noted | No | ||||
S5‑225508 | pCR 28.908 Add use case on multiple AIML entity testing | CATT | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑225509 | pCR 28.908 Add use case on online AIML entity testing | CATT | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑225520 | pCR 28.908 Add possible solution for AI-ML entity validation | Intel, NEC | pCR | Approval | Yes |
Yes
| approved | No | ||||
6.7.5.4 | FS_AIML_MGMT_WoP#4 |   | ||||||||||
6.7.5.5 | FS_AIML_MGMT_WoP#5 | S5‑225040 | pCR TR28.908 Potential solution on AIML Testing | Nokia Italy | pCR | Approval | Yes |
Yes
| merged | No | S5‑225697 | |
S5‑225041 | pCR TR28.908 Potential solution on event data for ML training | Nokia Italy | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑225522 | pCR 28.908 Add possible solution for AI-ML entity testing | Intel, NEC | pCR | Approval | Yes |
Yes
| revised | No | S5‑225697 | |||
S5‑225697 | pCR 28.908 Add possible solution for AI-ML entity testing | Intel, NEC | pCR | Approval | Yes |
Yes
| approved | No | S5‑225522 | |||
6.7.5.6 | FS_AIML_MGMT_WoP#6 |   | ||||||||||
6.7.5.7 | FS_AIML_MGMT_WoP#7 | S5‑225391 | pCR TR 28.908 Add possible solution on AI-ML model update | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑225698 | |
S5‑225698 | pCR TR 28.908 Add possible solution on AI-ML model update | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑225391 | |||
S5‑225489 | pCR 28.908 Add possible solutions on AIML model deployment | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑225523 | pCR 28.908 Add possible solutions for AI-ML entity deployment | Intel, NEC | pCR | Approval | Yes |
Yes
| noted | No | ||||
6.7.5.8 | FS_AIML_MGMT_WoP#8 | S5‑225042 | pCR TR28.908 Usecase on AIML Capability Update | Nokia Italy | pCR | Approval | Yes |
Yes
| noted | No | ||
S5‑225043 | pCR TR28.908 Usecase on improving retraining efficiency | Nokia Italy | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑225044 | pCR TR28.908 Usecase on Producer Initiated AIML Training | Nokia Italy | pCR | Approval | Yes |
Yes
| revised | No | S5‑225706 | |||
S5‑225706 | pCR TR28.908 Usecase on Producer Initiated AIML Training | Nokia Italy | pCR | Approval | Yes |
Yes
| approved | No | S5‑225044 | |||
S5‑225045 | pCR TR28.908 usecase on Orchestrating AIML inference | Nokia Italy | pCR | Approval | Yes |
Yes
| revised | No | S5‑225802 | |||
S5‑225802 | pCR TR28.908 usecase on Orchestrating AIML inference | Nokia Italy | pCR | Approval | Yes |
Yes
| approved | No | S5‑225045 | |||
S5‑225046 | pCR TR28.908 Usecase on ML GRADUAL ACTIVATION | Nokia Italy | pCR | Approval | Yes |
Yes
| revised | No | S5‑225703 | |||
S5‑225703 | pCR TR28.908 Usecase on ML GRADUAL ACTIVATION | Nokia Italy | pCR | Approval | Yes |
Yes
| approved | No | S5‑225046 | |||
S5‑225047 | pCR TR28.908 Potential solutions on AIML context | Nokia Italy | pCR | Approval | Yes |
Yes
| revised | No | S5‑225705 | |||
S5‑225705 | pCR TR28.908 Potential solutions on AIML context | Nokia Italy | pCR | Approval | Yes |
Yes
| approved | No | S5‑225047 | |||
S5‑225048 | pCR TR28.908 Requirements on Mobility of AIML Context | Nokia Italy | pCR | Approval | Yes |
Yes
| revised | No | S5‑225704 | |||
S5‑225704 | pCR TR28.908 Requirements on Mobility of AIML Context | Nokia Italy | pCR | Approval | Yes |
Yes
| approved | No | S5‑225048 | |||
S5‑225049 | pCR TR28.908 Usecase on Abstraction of ML Performance | Nokia Italy | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑225050 | pCR TR28.908 selection of AIML performance indicators | Nokia Italy | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑225051 | pCR TR28.908 Usecase on Policy based selection of Performance Indicators | Nokia Italy | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑225052 | pCR TR28.908 usecase on impacts of AIML inference actions | Nokia Italy | pCR | Approval | Yes |
Yes
| revised | No | S5‑225702 | |||
S5‑225702 | pCR TR28.908 usecase on impacts of AIML inference actions | Nokia Italy | pCR | Approval | Yes |
Yes
| approved | No | S5‑225052 | |||
S5‑225053 | pCR TR28.908 Usecase on Abstract AIML Behavior | Nokia Italy | pCR | Approval | Yes |
Yes
| revised | No | S5‑225701 | |||
S5‑225701 | pCR TR28.908 Usecase on Abstract AIML Behavior | Nokia Italy | pCR | Approval | Yes |
Yes
| approved | No | S5‑225053 | |||
S5‑225390 | pCR TR 28.908 Add use case on AI-ML model configuration | Huawei, Deutsche Telekom | pCR | Approval | Yes |
Yes
| revised | No | S5‑225700 | |||
S5‑225700 | pCR TR 28.908 Add use case on AI-ML model configuration | Huawei, Deutsche Telekom | pCR | Approval | Yes |
Yes
| approved | No | S5‑225390 | |||
S5‑225502 | pCR 28.908 Use case on Coordination of the AIML capability between 5GC/RAN and OAM node | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑225699 | |||
S5‑225699 | pCR 28.908 Use case on Coordination of the AIML capability between 5GC/RAN and OAM node | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑225502 | |||
6.7.5.9 | FS_AIML_MGMT_WoP#9 |   | ||||||||||
6.7.5.10 | FS_AIML_MGMT_WoP#10 |   | ||||||||||
6.7.6 | Study on Enhancement of the management aspects related to NWDAF |   | ||||||||||
6.7.6.1 | FS_MANWDAF_WoP#1 |   | ||||||||||
6.7.6.2 | FS_MANWDAF_WoP#2 | S5‑225054 | pCR 28.864 Potential solution on service usage of NWDAF | Nokia Italy | pCR | Approval | Yes |
Yes
| revised | No | S5‑225712 | |
S5‑225712 | pCR 28.864 Potential solution on service usage of NWDAF | Nokia Italy | pCR | Approval | Yes |
Yes
| approved | No | S5‑225054 | |||
S5‑225152 | pCR TR28.864 Key issue on NWDAF Analytics-related Timing | Nokia Italy | pCR | Approval | Yes |
Yes
| revised | No | S5‑225711 | |||
S5‑225711 | pCR TR28.864 Key issue on NWDAF Analytics-related Timing | Nokia Italy | pCR | Approval | Yes |
Yes
| approved | No | S5‑225152 | |||
S5‑225368 | pCR TR 28.864 Add potential solution related with number of subscriptions and notifications for NWDAF Data Collection | China Mobile E-Commerce Co. | pCR | Approval | Yes |
Yes
| revised | No | S5‑225710 | |||
S5‑225710 | pCR TR 28.864 Add potential solution related with number of subscriptions and notifications for NWDAF Data Collection | China Mobile E-Commerce Co. | pCR | Approval | Yes |
Yes
| approved | No | S5‑225368 | |||
S5‑225488 | pCR 28.864 Update key issue for the performance measurement of the NWDAF on the interaction aspect | Chinatelecom Cloud | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑225490 | pCR 28.864 Add the potential solution for the performance measurement of the NWDAF on the interaction aspect | Chinatelecom Cloud | pCR | Approval | Yes |
Yes
| revised | No | S5‑225709 | |||
S5‑225709 | pCR 28.864 Add the potential solution for the performance measurement of the NWDAF on the interaction aspect | Chinatelecom Cloud | pCR | Approval | Yes |
Yes
| approved | No | S5‑225490 | |||
S5‑225491 | New key issue for the performance measurement of the NWDAF related to the analytics result generation | Chinatelecom Cloud | pCR | Approval | Yes |
Yes
| revised | No | S5‑225708 | |||
S5‑225708 | New key issue for the performance measurement of the NWDAF related to the analytics result generation | Chinatelecom Cloud | pCR | Approval | Yes |
Yes
| approved | No | S5‑225491 | |||
S5‑225513 | pCR Adding use case for KI#4 | China Telecom | pCR | Yes |
Yes
| revised | No | S5‑225707 | ||||
S5‑225707 | pCR Adding use case for KI#4 | China Telecom | pCR | - | Yes |
Yes
| approved | No | S5‑225513 | |||
6.7.7 | Study on Fault Supervision Evolution |   | ||||||||||
6.7.7.1 | FS_FSEV_WoP#1 | S5‑225422 | pCR 28.830 Add clause Background | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑225713 | |
S5‑225713 | pCR 28.830 Add clause Background | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑225422 | |||
S5‑225459 | pCR 28.830 Add alarm related definitions | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑225578 | Discussion paper on basic concepts in FSEV study | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑225579 | pCR TR 28.830 Add background | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑225580 | pCR TR 28.830 Add relation description with existing MnS | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
6.7.7.2 | FS_FSEV_WoP#2 | S5‑225486 | pCR 28.830 Add framework of FSEV | Huawei, China Mobile | pCR | Approval | Yes |
Yes
| noted | No | ||
S5‑225487 | pCR 28.830 Add interface description | Huawei, China Mobile | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑225581 | pCR TR 28.830 Add description of key issue service outage | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑225582 | pCR TR 28.830 Add description of key issue performance degradation | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑225583 | pCR TR 28.830 Add description of key issue 5GC service failure prediction | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑225584 | pCR TR 28.830 Add solution of key issue service outage | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑225585 | pCR TR 28.830 Add solution of key issue performance degradation | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑225586 | pCR TR 28.830 Add solution of key issue 5GC service failure prediction | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
6.7.7.3 | FS_FSEV_WoP#3 |   | ||||||||||
6.7.8 | Study on measurement data collection to support RAN intelligence |   | ||||||||||
6.7.8.1 | FS_MEDACO_RAN_WoP#1 | S5‑225193 | pCR TR 28.838 Use case on management data correlation analytics | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||
S5‑225208 | Add Use Case of load balancing | China Mobile Com. Corporation | pCR | Decision | Yes |
Yes
| noted | No | ||||
S5‑225340 | pCR 28.838 add use case of mobility optimization | Intel Korea, Ltd. | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑225341 | pCR 28.838 add the use case of network energy saving | Intel Korea, Ltd. | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑225342 | pCR 28.838 add concept | Intel Korea, Ltd. | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑225343 | pCR 28.838 add solution | Intel Korea, Ltd. | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑225503 | pCR 28.838 Use case on predictions alignment | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
6.7.8.2 | FS_MEDACO_RAN_WoP#2 |   | ||||||||||
6.7.8.3 | FS_MEDACO_RAN_WoP#3 |   | ||||||||||
6.8 | Management Architecture and Mechanisms |   | ||||||||||
6.8.1 | Study on Enhancement of service based management architecture |   | ||||||||||
6.8.1.1 | FS_eSBMA_WoP#1 |   | ||||||||||
6.8.1.2 | FS_eSBMA_WoP#2 | S5‑225467 | pCR TR28.925 Add conclusion for issue #14 | HuaWei Technologies Co., Ltd | pCR | Yes |
Yes
| revised | No | S5‑225800 | ||
S5‑225800 | pCR TR28.925 Add conclusion for issue #14 | HuaWei Technologies Co., Ltd | pCR | - | Yes |
Yes
| approved | No | S5‑225467 | |||
S5‑225479 | Add key issue on requirements and use cases to support multiple MnS discovery service producers | China Unicom | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑225507 | Update of the TR 28.925, due to the study being moved to Rel-18 and new proposals. | Ericsson | pCR | Yes |
Yes
| revised | No | S5‑225799 | ||||
S5‑225799 | Update of the TR 28.925, due to the study being moved to Rel-18 and new proposals. | Ericsson | pCR | - | Yes |
Yes
| approved | No | S5‑225507 | |||
6.8.1.3 | FS_eSBMA_WoP#3 |   | ||||||||||
6.8.1.4 | FS_eSBMA_WoP#4 |   | ||||||||||
6.8.1.5 | FS_eSBMA_WoP#5 | S5‑225466 | pCR TR28.925 Add description on MnFs to be managed | HuaWei Technologies Co., Ltd | pCR | Yes |
Yes
| revised | No | S5‑225670 | S5‑224161 | |
S5‑225670 | pCR TR28.925 Add description on MnFs to be managed | HuaWei Technologies Co., Ltd | pCR | - | Yes |
Yes
| approved | No | S5‑225466 | |||
6.8.1.6 | FS_eSBMA_WoP#6 |   | ||||||||||
6.8.2 | Study on Basic SBMA enabler enhancements |   | ||||||||||
6.8.2.1 | FS_eSBMAe_WoP#1 |   | ||||||||||
6.8.2.2 | FS_eSBMAe_WoP#2 |   | ||||||||||
6.8.2.3 | FS_eSBMAe_WoP#3 | S5‑225178 | pCR 28.831 Add Key Issue for attribute addition and deletion | Samsung R&D Institute UK | pCR | Agreement | Yes |
Yes
| noted | No | ||
S5‑225397 | Rel-18 pCR TR 28.831 Add a new key issue for Adding mechanism to advertise supported NRM capabilities by the MnS Producer | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑225468 | pCR 28.831 Add key issue: Definition of createMOI | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑225801 | |||
S5‑225801 | pCR 28.831 Add key issue: Definition of createMOI | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑225468 | |||
S5‑225469 | pCR 28.831 Add key issue: Definition of getMOIAttributes | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑225498 | Rel-18 pCR TR 28.831 Add a potential requirements for KI to Add mechanism to advertise supported NRM capabilities by the MnS Producer | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑225499 | Rel-18 pCR TR 28.831 Add a potential solution for KI to Add mechanism to advertise supported NRM capabilities by the MnS Producer | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑225541 | Add a potential solution for KI to Add mechanism to advertise supported NRM capabilities by the MnS Producer | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
6.8.2.4 | FS_eSBMAe_WoP#4 | S5‑225472 | pCR 28.831 Modify potential requirements for key issue Targeted notification subscription | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑225806 | |
S5‑225806 | pCR 28.831 Modify potential requirements for key issue Targeted notification subscription | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑225472 | |||
S5‑225473 | pCR 28.831 Add XPath as potential solution | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑225805 | |||
S5‑225805 | pCR 28.831 Add XPath as potential solution | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑225473 | |||
S5‑225475 | pCR 28.831 Add special XPath considerations for JSON and YANG | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑225804 | |||
S5‑225804 | pCR 28.831 Add special XPath considerations for JSON and YANG | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑225475 | |||
S5‑225476 | pCR 28.831 Add simple XPath profiles | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑225803 | |||
S5‑225803 | pCR 28.831 Add simple XPath profiles | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑225476 | |||
6.8.2.5 | FS_eSBMAe_WoP#5 |   | ||||||||||
6.8.2.6 | FS_eSBMAe_WoP#6 |   | ||||||||||
6.8.2.7 | FS_eSBMAe_WoP#7 |   | ||||||||||
6.8.2.8 | FS_eSBMAe_WoP#8 |   | ||||||||||
6.8.2.9 | FS_eSBMAe_WoP#9 |   | ||||||||||
6.8.2.10 | FS_eSBMAe_WoP#10 |   | ||||||||||
6.8.3 | Study on Management Aspects of URLLC |   | ||||||||||
6.8.3.1 | FS_URLLC_Mgt_WoP#1 |   | ||||||||||
6.8.3.2 | FS_URLLC_Mgt_WoP#2 | S5‑225418 | pCR TR28.832 Add Issue on URLLC features management of configuration | China Unicom | pCR | Approval | Yes |
Yes
| noted | No | ||
S5‑225423 | pCR TR28.832 Add Solution for URLLC features management of configuration | China Unicom | pCR | Approval | Yes |
Yes
| noted | No | ||||
6.8.3.3 | FS_URLLC_Mgt_WoP#3 | S5‑225419 | pCR TR28.832 Add Issue on URLLC performance management on reliability | China Unicom, CATT | pCR | Approval | Yes |
Yes
| revised | No | S5‑225808 | |
S5‑225808 | pCR TR28.832 Add Issue on URLLC performance management on reliability | China Unicom, CATT | pCR | Approval | Yes |
Yes
| approved | No | S5‑225419 | |||
S5‑225461 | pCR TR28.832 Add Sulotion for URLLC performance measurements related on reliability | China Unicom | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑225463 | pCR TR28.832 Add solution for support for performance measurements related on URLLC resource load | China Unicom | pCR | Approval | Yes |
Yes
| noted | No | ||||
6.8.3.4 | FS_URLLC_Mgt_WoP#4 |   | ||||||||||
6.8.4 | Study on Management Aspect of 5GLAN |   | ||||||||||
6.8.4.1 | FS_5GLAN_Mgt_WoP#1 |   | ||||||||||
6.8.4.2 | FS_5GLAN_Mgt_WoP#2 |   | ||||||||||
6.8.4.3 | FS_5GLAN_Mgt_WoP#3 | S5‑225246 | pCR TR 28.833 add potential solution of SMF configuration | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑225810 | |
S5‑225810 | pCR TR 28.833 add potential solution of SMF configuration | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑225246 | |||
S5‑225247 | pCR TR 28.833 add potential solution of performance meassurements for SMF and UPF | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑225462 | pCR TR28.832 Add Issue on support for performance management related on URLLC resource load | China Unicom, CATT | pCR | Approval | Yes |
Yes
| revised | No | S5‑225807 | |||
S5‑225807 | pCR TR28.832 Add Issue on support for performance management related on URLLC resource load | China Unicom, CATT | pCR | Approval | Yes |
Yes
| approved | No | S5‑225462 | |||
S5‑225524 | pCR TR 28.833 Add detailed description for topic #3 | China Mobile E-Commerce Co. | pCR | Approval | Yes |
Yes
| merged | No | S5‑225809 | |||
S5‑225525 | pCR TR 28.833 Add potential solutions for topic 3 | China Mobile E-Commerce Co. | pCR | Approval | Yes |
Yes
| revised | No | S5‑225809 | |||
S5‑225809 | pCR TR 28.833 Add potential solutions for topic 3 | China Mobile E-Commerce Co. | pCR | Approval | Yes |
Yes
| approved | No | S5‑225525 | |||
S5‑225526 | pCR TR 28.833 Add Annex A of UML code of FS_5GLAN_Mgt | China Mobile E-Commerce Co. | pCR | Approval | Yes |
Yes
| revised | No | S5‑225877 | |||
S5‑225877 | pCR TR 28.833 Add Annex A of UML code of FS_5GLAN_Mgt | China Mobile E-Commerce Co. | pCR | Approval | Yes |
Yes
| approved | No | S5‑225526 | |||
S5‑225527 | pCR TR 28.833 Add evaluation and conclusion for Topic 1 of FS_5GLAN_Mgt | China Mobile E-Commerce Co. | pCR | Approval | Yes |
Yes
| revised | No | S5‑225876 | |||
S5‑225876 | pCR TR 28.833 Add evaluation and conclusion for Topic 1 of FS_5GLAN_Mgt | China Mobile E-Commerce Co. | pCR | Approval | Yes |
Yes
| approved | No | S5‑225527 | |||
S5‑225528 | pCR TR 28.833 Add general description of solution 1 of FS_5GLAN_Mgt | China Mobile E-Commerce Co. | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑225529 | pCR TR 28.833 Add general description of solution 2 of FS_5GLAN_Mgt | China Mobile E-Commerce Co. | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑225530 | pCR TR 28.833 Add procedure of management of the PDU session of FS_5GLAN_Mgt | China Mobile E-Commerce Co. | pCR | Approval | Yes |
Yes
| revised | No | S5‑225875 | |||
S5‑225875 | pCR TR 28.833 Add procedure of management of the PDU session of FS_5GLAN_Mgt | China Mobile E-Commerce Co. | pCR | Approval | Yes |
Yes
| approved | No | S5‑225530 | |||
S5‑225531 | pCR TR 28.833 Add evaluation and conclusion for Topic 2 of FS_5GLAN_Mgt of FS_5GLAN_Mgt | China Mobile E-Commerce Co. | pCR | Approval | Yes |
Yes
| noted | No | ||||
6.8.4.4 | FS_5GLAN_Mgt_WoP#4 | S5‑225373 | pCR TR 28.833 Add key issue for topic 4 | China Mobile E-Commerce Co. | pCR | Approval | Yes |
Yes
| revised | No | S5‑225811 | |
S5‑225811 | pCR TR 28.833 Add key issue for topic 4 | China Mobile E-Commerce Co. | pCR | Approval | Yes |
Yes
| approved | No | S5‑225373 | |||
6.8.5 | Study on Management of Cloud Native Virtualized Network Functions |   | ||||||||||
6.8.5.1 | FS_MCVNF_WoP#1 | S5‑225154 | pCR 28.834 Add concepts and background | Microsoft, China Mobile | pCR | Yes |
Yes
| revised | No | S5‑225814 | ||
S5‑225814 | pCR 28.834 Add concepts and background | Microsoft, China Mobile | pCR | - | Yes |
Yes
| approved | No | S5‑225154 | |||
S5‑225241 | pCR 28.834 Add issues for use case 1 | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑225242 | pCR 28.834 Add issues for use case 2 | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑225243 | pCR 28.834 Add issues for use case 3 | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑225244 | pCR 28.834 Add issues for use case 4 | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑225878 | |||
S5‑225878 | pCR 28.834 Add issues for use case 4 | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑225244 | |||
S5‑225245 | pCR 28.834 Add use case for NF creation as cloud native VNF | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑225813 | |||
S5‑225813 | pCR 28.834 Add use case for NF creation as cloud native VNF | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑225245 | |||
S5‑225370 | pCR 28.834 Add Use Case on performance management of the cloud-native VNF using generic OAM functions | AsiaInfo Technologies Inc | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑225371 | pCR 28.834 Add Use Case on software modification of the cloud-native VNF | AsiaInfo Technologies Inc | pCR | Approval | Yes |
Yes
| revised | No | S5‑225812 | |||
S5‑225812 | pCR 28.834 Add Use Case on software modification of the cloud-native VNF | AsiaInfo Technologies Inc | pCR | Approval | Yes |
Yes
| approved | No | S5‑225371 | |||
S5‑225497 | pCR 28.834 Add Use Case on Upgrade management of the cloud-native VNF using generic OAM functions | China Mobile Com. Corporation | pCR | Approval | Yes |
Yes
| noted | No | ||||
6.8.5.2 | FS_MCVNF_WoP#2 |   | ||||||||||
6.8.5.3 | FS_MCVNF_WoP#3 | S5‑225155 | DP on solution timeline for generic OAM functions requirements | Microsoft Europe SARL | discussion | Yes |
Yes
| noted | No | |||
6.8.6 | Study on Management Aspects of 5G MOCN Network Sharing Phase2 |   | ||||||||||
6.8.6.1 | FS_MANS_ph2_WoP#1 | S5‑225409 | pCR TR 28.835 Update potential solution for management requirement between MOP-NM and MOP-SR-DM | China Unicom | pCR | Approval | Yes |
Yes
| revised | No | S5‑225817 | |
S5‑225817 | pCR TR 28.835 Update potential solution for management requirement between MOP-NM and MOP-SR-DM | China Unicom | pCR | Approval | Yes |
Yes
| approved | No | S5‑225409 | |||
S5‑225410 | pCR TR 28.835 Add key issue PLMN-related attribute requirement for operator specific IOC | China Unicom | pCR | Approval | Yes |
Yes
| revised | No | S5‑225816 | |||
S5‑225816 | pCR TR 28.835 Add key issue PLMN-related attribute requirement for operator specific IOC | China Unicom | pCR | Approval | Yes |
Yes
| approved | No | S5‑225410 | |||
S5‑225412 | Add potential solution for PLMN-related attribute requirement for operator specific IOC | China Unicom | pCR | Approval | Yes |
Yes
| revised | No | S5‑225815 | |||
S5‑225815 | Add potential solution for PLMN-related attribute requirement for operator specific IOC | China Unicom | pCR | Approval | Yes |
Yes
| approved | No | S5‑225412 | |||
S5‑225591 | pCR TR 28.835 Add issue and potential solution for collection of operator specific performance measurements | ZTE Corporation | pCR | Approval | Yes |
Yes
| not treated | No | ||||
6.8.6.2 | FS_MANS_ph2_WoP#2 | S5‑225413 | pCR TR 28.835 Add potential solutions for performance measurements without PLMN ID at NRcellCU | China Unicom, ZTE | pCR | Approval | Yes |
Yes
| approved | No | ||
6.8.6.3 | FS_MANS_ph2_WoP#3 |   | ||||||||||
6.8.7 | Study on Management of Trace/MDT phase 2 |   | ||||||||||
6.8.7.1 | FS_5GMDT_Ph2_WoP#1 | S5‑225320 | Rel-18 pCR 28.837 Structuring of TraceJob attributes | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||
6.8.7.2 | FS_5GMDT_Ph2_WoP#2 |   | ||||||||||
6.8.7.3 | FS_5GMDT_Ph2_WoP#3 | S5‑225078 | pCR TR28.837 Solution to Report Amount IE Misalignment | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||
S5‑225079 | Discussion_Configurability of Report Amount IE | Nokia, Nokia Shanghai Bell | discussion | Endorsement | Yes |
Yes
| approved | No | ||||
6.8.7.4 | FS_5GMDT_Ph2_WoP#4 |   | ||||||||||
6.8.7.5 | FS_5GMDT_Ph2_WoP#5 |   | ||||||||||
6.8.7.6 | FS_5GMDT_Ph2_WoP#6 |   | ||||||||||
6.8.7.7 | FS_5GMDT_Ph2_WoP#7 |   | ||||||||||
6.8.7.8 | FS_5GMDT_Ph2_WoP#8 |   | ||||||||||
6.8.8 | Study on Management Aspects of IoT NTN Enhancements |   | ||||||||||
6.8.8.1 | FS_IOT_NTN_WoP#1 | S5‑225385 | TR 28.825 update TR structure | China Unicom | pCR | Approval | Yes |
Yes
| approved | No | ||
6.8.8.2 | FS_IOT_NTN_WoP#2 | S5‑225405 | pCR 28.841 add scenarios for IOT networks with an integrated satellite componen | China Unicom | pCR | Approval | Yes |
Yes
| approved | No | ||
6.8.8.3 | FS_IOT_NTN_WoP#3 |   | ||||||||||
6.9 | Support of New Services |   | ||||||||||
6.9.1 | Study on enhancement of management of non-public networks |   | ||||||||||
6.9.1.1 | FS_OAM_eNPN_WoP#1 | S5‑225157 | Presentation of TR 28.907 for SA Information | Huawei | other | Approval | Yes |
Yes
| approved | No | ||
S5‑225158 | pCR 28.907 Rapporteur proposal | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑225860 | |||
S5‑225860 | pCR 28.907 Rapporteur proposal | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑225158 | |||
S5‑225159 | pCR 28.907 Add introduction of TR | Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑225160 | pCR 28.907 Update clause 4.1 | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑225859 | |||
S5‑225859 | pCR 28.907 Update clause 4.1 | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑225160 | |||
S5‑225161 | pCR 28.907 Add key issue for network capability exposure | Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑225162 | pCR 28.907 Potential solution for satisfying resource isolation demand for Smart Grid Utilities | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑225818 | |||
S5‑225818 | pCR 28.907 Potential solution for satisfying resource isolation demand for Smart Grid Utilities | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑225162 | |||
6.9.1.2 | FS_OAM_eNPN_WoP#2 |   | ||||||||||
6.9.1.3 | FS_OAM_eNPN_WoP#3 |   | ||||||||||
6.9.1.4 | FS_OAM_eNPN_WoP#4 |   | ||||||||||
6.9.2 | Study on new aspects of EE for 5G networks Phase 2 |   | ||||||||||
6.9.2.1 | FS_EE5G_Ph2_WoP#1 | S5‑225255 | pCR TR 28.913 New Issue – Roles involved in EE KPI building | Huawei, Deutsche Telekom | pCR | Approval | Yes |
Yes
| revised | No | S5‑225863 | |
S5‑225863 | pCR TR 28.913 New Issue – Roles involved in EE KPI building | Huawei, Deutsche Telekom | pCR | Approval | Yes |
Yes
| approved | No | S5‑225255 | |||
S5‑225551 | pCR TR 28.913 Potential solution No.2, conclusion and recommendation for KI #1 | Huawei Technologies France | pCR | Approval | Yes |
Yes
| revised | No | S5‑225862 | |||
S5‑225862 | pCR TR 28.913 Potential solution No.2, conclusion and recommendation for KI #1 | Huawei Technologies France | pCR | Approval | Yes |
Yes
| approved | No | S5‑225551 | |||
S5‑225556 | Rel-18 pCR 28.913 – New Key Issue for Energy Efficiency of a URLLC network slice based on reliability | Samsung Electronics Nordic AB | pCR | Approval | Yes |
Yes
| revised | No | S5‑225861 | |||
S5‑225861 | Rel-18 pCR 28.913 – New Key Issue for Energy Efficiency of a URLLC network slice based on reliability | Samsung Electronics Nordic AB | pCR | Approval | Yes |
Yes
| approved | No | S5‑225556 | |||
6.9.2.2 | FS_EE5G_Ph2_WoP#2 | S5‑225256 | pCR 28.913 Add new Issue on digital sobriety | Huawei Technologies France | pCR | Approval | Yes |
Yes
| noted | No | ||
S5‑225258 | pCR TR 28.913 New Key Issue-RAN energy saving when using backup batteries | Huawei Technologies France | pCR | Approval | Yes |
Yes
| noted | No | ||||
6.9.3 | Study on Network and Service Operations for Energy Utilities |   | ||||||||||
6.9.3.1 | FS_NSOEU_WoP#1 |   | ||||||||||
6.9.3.2 | FS_NSOEU_WoP#2 |   | ||||||||||
6.9.3.3 | FS_NSOEU_WoP#3 |   | ||||||||||
6.9.3.4 | FS_NSOEU_WoP#4 | S5‑225540 | Rel-18 pCR 28.829 Add new Key Issue and Solution | Samsung Electronics Nordic AB | pCR | Approval | Yes |
Yes
| revised | No | S5‑225865 | |
S5‑225865 | Rel-18 pCR 28.829 Add new Key Issue and Solution | Samsung Electronics Nordic AB | pCR | Approval | Yes |
Yes
| approved | No | S5‑225540 | |||
6.9.3.5 | FS_NSOEU_WoP#5 |   | ||||||||||
6.9.3.6 | FS_NSOEU_WoP#6 | S5‑225407 | pCR TR 28.829 Clean up | Samsung, EUTC, EDF | pCR | Approval | Yes |
Yes
| revised | No | S5‑225868 | |
S5‑225868 | pCR TR 28.829 Clean up | Samsung, EUTC, EDF | pCR | Approval | Yes |
Yes
| approved | No | S5‑225407 | |||
S5‑225408 | pCR TR 28.829 Business use case - DSO Provides an Incident Report | Samsung, EUTC, BMWK, Vodafone, Telefonica, EDF | pCR | Approval | Yes |
Yes
| revised | No | S5‑225867 | |||
S5‑225867 | pCR TR 28.829 Business use case - DSO Provides an Incident Report | Samsung, EUTC, BMWK, Vodafone, Telefonica, EDF | pCR | Approval | Yes |
Yes
| approved | No | S5‑225408 | |||
S5‑225411 | pCR TR 28.829 Business use case - DSO Provides Performance Reporting indicating Problems | Samsung, EUTC, BMWK, Vodafone, Telefonica, EDF | pCR | Approval | Yes |
Yes
| revised | No | S5‑225866 | |||
S5‑225866 | pCR TR 28.829 Business use case - DSO Provides Performance Reporting indicating Problems | Samsung, EUTC, BMWK, Vodafone, Telefonica, EDF | pCR | Approval | Yes |
Yes
| approved | No | S5‑225411 | |||
6.9.3.7 | FS_NSOEU_WoP#7 |   | ||||||||||
6.9.3.8 | FS_NSOEU_WoP#8 |   | ||||||||||
6.9.3.9 | FS_NSOEU_WoP#9 |   | ||||||||||
6.9.3.10 | FS_NSOEU_WoP#10 |   | ||||||||||
6.9.3.11 | FS_NSOEU_WoP#11 |   | ||||||||||
6.9.3.12 | FS_NSOEU_WoP#12 |   | ||||||||||
6.9.3.13 | FS_NSOEU_WoP#13 |   | ||||||||||
6.9.4 | Study on Key Quality Indicators (KQIs)for 5G service experience |   | ||||||||||
6.9.4.1 | FS_KQI_5G_WoP#1 | S5‑225179 | pCR TR 28.863 Key Issue # 1: add a description of KQI in ETSI GS F5G 005 | AsiaInfo,Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑225869 | |
S5‑225869 | pCR TR 28.863 Key Issue # 1: add a description of KQI in ETSI GS F5G 005 | AsiaInfo,Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑225179 | |||
S5‑225464 | pCR TR 28.863 Overview - 5G KQI management | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑225470 | pCR TR 28.863 Issue#1 Background description of KQI definition | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑225778 | |||
S5‑225778 | pCR TR 28.863 Issue#1 Background description of KQI definition | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑225470 | |||
S5‑225471 | pCR TR 28.863 Issue #1 Difference of KPI, KQI and QoE | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑225474 | pCR TR 28.863 Issue #3 Video uploading description | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑225477 | pCR TR 28.863 Issue#4 Remote controlling description | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
6.9.4.2 | FS_KQI_5G_WoP#2 |   | ||||||||||
6.9.4.3 | FS_KQI_5G_WoP#3 |   | ||||||||||
6.9.4.4 | FS_KQI_5G_WoP#4 | S5‑225181 | pCR TR 28.863 Key Issue # 5: KQIs for cloud VR- the background survey of the Cloud VR | AsiaInfo,Huawei | pCR | Approval | Yes |
Yes
| withdrawn | Yes | ||
S5‑225182 | pCR TR 28.863 Key Issue # 5: KQIs for cloud VR- use case of the Cloud VR | AsiaInfo,Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑225183 | pCR TR 28.863 Key Issue #5 KQIs for Cloud VR- the solution of KQIs for cloud VR | AsiaInfo,Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑225398 | pCR TR 28.863 Key Issue # 5: KQIs for cloud VR- the background survey of the Cloud VR | Asiainfo, Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
6.9.4.5 | FS_KQI_5G_WoP#5 |   | ||||||||||
6.9.5 | Study on Deterministic Communication Service Assurance |   | ||||||||||
6.9.5.1 | FS_DCSA_WoP#1 |   | ||||||||||
6.9.5.2 | FS_DCSA_WoP#2 | S5‑225480 | pCR 28.865 Add solution of service deployment related to DCSA | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||
S5‑225481 | pCR 28.865 Add solultion of service requirement modeling | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑225482 | pCR 28.865 Add solultion of network preparation | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑225483 | pCR 28.865 Add solution of service and network analysis | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
6.9.5.3 | FS_DCSA_WoP#3 |   | ||||||||||
6.9.5.4 | FS_DCSA_WoP#4 | S5‑225484 | pCR 28.865 Update solution of service assurance for video monitoring | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||
S5‑225485 | pCR 28.865 Update solution of service assurance for PLC control | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
6.9.5.5 | FS_DCSA_WoP#5 |   | ||||||||||
6.9.6 | Study on management aspects of network slice management capability exposure |   | ||||||||||
6.9.6.1 | FS_NSCE_WoP#1 | S5‑225248 | pCR 28.824 Cleanup of exposure without going through BSS | Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||
S5‑225249 | pCR 28.824 Removal of unused interfaces in alternative 3 | Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||||
6.9.6.2 | FS_NSCE_WoP#2 |   | ||||||||||
6.9.6.3 | FS_NSCE_WoP#3 | S5‑225163 | pCR 28.824 Concepts of simplification, filtering and abstration in exposure governance | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||
S5‑225164 | pCR 28.824 Possible solutions for EGMF implementing CAPIF functional entities | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑225215 | DP on relationship with CAMARA and related definition | Alibaba Group | pCR | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑225216 | Rephrase or replace eMnS with exposed MnS | Alibaba Group | pCR | Approval | Yes |
Yes
| revised | No | S5‑225870 | |||
S5‑225870 | Rephrase or replace eMnS with exposed MnS | Alibaba Group | pCR | Approval | Yes |
Yes
| approved | No | S5‑225216 | |||
S5‑225217 | Update of solution 7.9 | Alibaba Group | pCR | Approval | Yes |
Yes
| revised | No | S5‑225871 | |||
S5‑225871 | Update of solution 7.9 | Alibaba Group | pCR | Approval | Yes |
Yes
| approved | No | S5‑225217 | |||
S5‑225218 | Update Solution for Network slice management capability | Alibaba Group | pCR | Approval | Yes |
Yes
| noted | No | ||||
6.9.6.4 | FS_NSCE_WoP#4 |   | ||||||||||
6.9.7 | Study on alignment with ETSI MEC for Edge computing management |   | ||||||||||
6.9.7.1 | FS_MEC_ECM_WoP#1 | S5‑225250 | pCR 28.903 add potential solution for application LCM with MEC | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||
S5‑225251 | pCR 28.903 add potential solution for application LCM | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑225873 | |||
S5‑225873 | pCR 28.903 add potential solution for application LCM | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑225251 | |||
S5‑225252 | pCR 28.903 add potential solution for EES and MEP collocation | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑225872 | |||
S5‑225872 | pCR 28.903 add potential solution for EES and MEP collocation | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑225252 | |||
6.9.7.2 | FS_MEC_ECM_WoP#2 | S5‑225253 | pCR 28.903 add potential solution for resource reservation | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||
S5‑225254 | pCR 28.903 update background information for GSMA OPG | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑225874 | |||
S5‑225874 | pCR 28.903 update background information for GSMA OPG | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑225254 | |||
6.10 | Latest draft TS/TR email approvals | S5‑225655 | Latest draft TR 28.909 | China Mobile | other | Approval | Yes |
Yes
| withdrawn | Yes | ||
S5‑225656 | Latest draft TR 28.910 | China Mobile | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S5‑225657 | Latest draft TR 28.912 | Huawei | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S5‑225659 | Latest draft TR 28.908 | Intel | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S5‑225660 | Latest draft TR 28.864 | China telecom | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S5‑225661 | Latest draft TR 28.830 | China Mobile | draft TR | discussion | Yes |
Yes
| approved | No | ||||
S5‑225663 | Latest draft TR 28.925 | Huawei | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S5‑225665 | Latest draft TR 28.832 | China unicom | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S5‑225666 | Latest draft TR 28.833 | China Mobile | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S5‑225667 | Latest draft TR 28.834 | China Mobile | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S5‑225668 | Latest draft TR 28.835 | China Unicom | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S5‑225669 | Latest draft TR 28.837 | Nokia | draft TR | discussion | Yes |
Yes
| approved | No | ||||
S5‑225671 | Latest draft TR 28.841 | China Unicom | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S5‑225672 | Latest draft TR 28.907 | Huawei | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S5‑225673 | Latest draft TR 28.913 | Huawei | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S5‑225674 | Latest draft TR 28.829 | Samsung | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S5‑225675 | Latest draft TR 28.863 | Huawei | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S5‑225676 | Latest draft TR 28.865 | Huawei | other | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑225677 | Latest draft TR 28.824 | Alibaba | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S5‑225678 | Latest draft TR 28.903 | Huawei | draft TR | Approval | Yes |
Yes
| approved | No | ||||
7 | Charging |   | ||||||||||
7.1 | Charging Plenary | S5‑225008 | CH agenda and time plan | WG vice Chair (Matrixx Software) | agenda | Yes |
Yes
| revised | No | S5‑225714 | ||
S5‑225714 | CH agenda and time plan | WG vice Chair (Matrixx Software) | agenda | - | Yes |
Yes
| noted | No | S5‑225008 | |||
S5‑225009 | Charging exec report | WG vice Chair (Matrixx Software) | report | Yes |
Yes
| noted | No | |||||
S5‑225016 | Resubmitted Reply LS on Enhancement on Charging Identifier Uniqueness Mechanism | C3-223669 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑225445 | Reply to: Resubmitted Reply LS on Enhancement on Charging Identifier Uniqueness Mechanism | Huawei | LS out | approval | Yes |
Yes
| revised | No | S5‑225761 | |||
S5‑225761 | Reply to: Resubmitted Reply LS on Enhancement on Charging Identifier Uniqueness Mechanism | Huawei | LS out | approval | Yes |
Yes
| approved | No | S5‑225445 | |||
S5‑225775 | LS on Reference point allocation to support charging services | MATRIXX Software | LS out | discussion | Yes |
Yes
| approved | No | ||||
7.2 | New Charging Work Item proposals |   | ||||||||||
7.3 | Charging Maintenance and Rel-18 small Enhancements | S5‑225082 | Rel-17 CR 32.291 Adding missing NodeFunctionality value for IMS | Amdocs Software Systems Ltd | CR | Approval | Yes |
Yes
| revised | No | S5‑225741 | |
S5‑225741 | Rel-17 CR 32.291 Adding missing NodeFunctionality value for IMS | Amdocs Software Systems Ltd | CR | Approval | Yes |
Yes
| agreed | No | S5‑225082 | |||
S5‑225083 | Rel-17 CR 32.291 Alignment between IMSNodeFunctionality description and YAML | Amdocs Software Systems Ltd | CR | Approval | Yes |
Yes
| revised | No | S5‑225742 | |||
S5‑225742 | Rel-17 CR 32.291 Alignment between IMSNodeFunctionality description and YAML | Amdocs Software Systems Ltd | CR | Approval | Yes |
Yes
| agreed | No | S5‑225083 | |||
S5‑225084 | Rel-17 CR 32.240 Introduction of Reference point representation for Converged Charging | MATRIXX Software | CR | Approval | Yes |
Yes
| revised | No | S5‑225774 | |||
S5‑225774 | Rel-17 CR 32.240 Introduction of Reference point representation for Converged Charging | MATRIXX Software | CR | Approval | Yes |
Yes
| agreed | No | S5‑225084 | |||
S5‑225085 | Rel-17 CR 32.260 Missing Operation Type E for Multiple Unit Usage | Amdocs Software Systems Ltd | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑225211 | Rel-17 CR 32.255 Correction on Home Provided Charging Id and Roaming Charging Profile | China Mobile M2M Company Ltd. | CR | Approval | Yes |
Yes
| revised | No | S5‑225743 | |||
S5‑225743 | Rel-17 CR 32.255 Correction on Home Provided Charging Id and Roaming Charging Profile | China Mobile M2M Company Ltd. | CR | Approval | Yes |
Yes
| agreed | No | S5‑225211 | |||
S5‑225259 | Rel-16 CR 32.255 Correction of secondary RAT for EPC | Ericsson LM | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑225260 | Rel-17 CR 32.255 Correction of secondary RAT for EPC | Ericsson LM | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑225261 | Rel-16 CR 32.291 Correction of secondary RAT for EPC | Ericsson LM | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑225262 | Rel-17 CR 32.291 Correction of secondary RAT for EPC | Ericsson LM | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑225263 | Rel-16 CR 32.255 Correction of IPv6 prefixes in PDU address | Ericsson LM | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑225264 | Rel-17 CR 32.255 Correction of IPv6 prefixes in PDU address | Ericsson LM | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑225265 | Rel-16 CR 32.291 Correction of IPv6 prefixes in PDU address | Ericsson LM | CR | Agreement | Yes |
Yes
| revised | No | S5‑225744 | |||
S5‑225744 | Rel-16 CR 32.291 Correction of IPv6 prefixes in PDU address | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | S5‑225265 | |||
S5‑225266 | Rel-17 CR 32.291 Correction of IPv6 prefixes in PDU address | Ericsson LM | CR | Agreement | Yes |
Yes
| revised | No | S5‑225745 | |||
S5‑225745 | Rel-17 CR 32.291 Correction of IPv6 prefixes in PDU address | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | S5‑225266 | |||
S5‑225267 | Rel-17 CR 32.274 Correcting session and charging identifiers | Ericsson LM | CR | Agreement | Yes |
Yes
| revised | No | S5‑225644 | S5‑223091 | ||
S5‑225644 | Rel-17 CR 32.274 Correcting session and charging identifiers | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | S5‑225267 | |||
S5‑225268 | Rel-17 CR 32.254 Missing operation and identifier in NEF charging information | Ericsson LM | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑223094 | |||
S5‑225269 | Rel-17 CR 32.291 Missing operation and identifier in NEF charging information | Ericsson LM | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑223095 | |||
S5‑225270 | Rel-17 CR 32.298 Missing operation and identifier in NEF charging information | Ericsson LM | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑223096 | |||
S5‑225271 | Rel-17 CR 32.290 Correction of use of requested units at suspended | Ericsson LM | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑225272 | Rel-17 CR 32.291 Correction of use QMI in notify | Ericsson LM | CR | Agreement | Yes |
Yes
| revised | No | S5‑225768 | |||
S5‑225768 | Rel-17 CR 32.291 Correction of use QMI in notify | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | S5‑225272 | |||
S5‑225273 | Rel-17 CR 32.290 Correction of use QMI | Ericsson LM | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑225274 | Rel-17 CR 32.298 Correction ASN.1 check | Ericsson LM | CR | Agreement | Yes |
Yes
| revised | No | S5‑225738 | |||
S5‑225738 | Rel-17 CR 32.298 Correction ASN.1 check | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | S5‑225274 | |||
S5‑225275 | Rel-17 CR 32.291 Correcting missing user location mapping to ASN.1 | Ericsson LM | CR | Agreement | Yes |
Yes
| revised | No | S5‑225646 | |||
S5‑225646 | Rel-17 CR 32.291 Correcting missing user location mapping to ASN.1 | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | S5‑225275 | |||
S5‑225276 | Rel-17 CR 32.291 Correcting missing CIoT indicators in yaml | Ericsson LM | CR | Agreement | Yes |
Yes
| revised | No | S5‑225740 | |||
S5‑225740 | Rel-17 CR 32.291 Correcting missing CIoT indicators in yaml | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | S5‑225276 | |||
S5‑225277 | Rel-17 CR 32.291 Correcting missing node functionality as IMS | Ericsson LM | CR | Agreement | Yes |
Yes
| merged | No | S5‑225741 | |||
S5‑225278 | Rel-17 CR 32.290 Correcting service level usage for trigger mechanism | Ericsson LM | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑225279 | Rel-17 CR 32.291 Correcting missing V-SMF | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑225280 | Rel-17 CR 32.298 Correction missing V-SMF | Ericsson LM | CR | Agreement | Yes |
Yes
| revised | No | S5‑225760 | |||
S5‑225760 | Rel-17 CR 32.298 Correction missing V-SMF | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | S5‑225280 | |||
S5‑225281 | Rel-17 CR 32.298 Correction for undefined RAT type | Ericsson LM | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑225282 | Rel-17 CR 32.298 Correction for ATSSSCapability mapping | Ericsson LM | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑225283 | Rel-16 CR 32.298 Correction presence reporting in roaming QBC information | Ericsson LM | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑225284 | Rel-17 CR 32.298 Correction presence reporting in roaming QBC information | Ericsson LM | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑225285 | Rel-16 CR 32.291 Correction of DNN definition | Ericsson LM | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑225286 | Rel-17 CR 32.291 Correction of DNN definition | Ericsson LM | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑225287 | Rel-17 CR 32.240 Correction of IMS and SMSF in reference architecture | Ericsson LM | CR | Agreement | Yes |
Yes
| merged | No | S5‑225774 | |||
S5‑225440 | Rel-17 CR 32.291 Correction on the IPv6 address OpenAPI | Huawei | CR | Agreement | Yes |
Yes
| merged | No | S5‑225745 | |||
S5‑225441 | Rel-17 CR 32.291 Correction on the ProSe OpenAPI | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑225442 | Rel-17 CR 32.298 Correction on the Charging Identifier Uniqueness | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑225770 | |||
S5‑225770 | Rel-17 CR 32.298 Correction on the Charging Identifier Uniqueness | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑225442 | |||
S5‑225443 | Rel-17 CR 32.291 Correction on the Charging Identifier Uniqueness | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑225771 | |||
S5‑225771 | Rel-17 CR 32.291 Correction on the Charging Identifier Uniqueness | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑225443 | |||
S5‑225444 | Rel-17 CR 32.255 Correction on the Charging Identifier Uniqueness | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑225772 | |||
S5‑225772 | Rel-17 CR 32.255 Correction on the Charging Identifier Uniqueness | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑225444 | |||
S5‑225446 | Rel-17 CR 32.298 Correction on the 5G LAN VN management converged Charging | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑225447 | Rel-17 CR 32.291 Correction on the 5G LAN VN management converged Charging | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑225448 | Rel-17 CR 32.254 Correction on the 5G LAN VN management converged Charging | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑225449 | Rel-17 CR 32.257 Correction on reference for the EAS Deployment | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑225450 | Rel-17 CR 32.298 Correction on the EAS Deployment Requirements | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑225451 | Rel-17 CR 32.291 Correction on the EASRequirements | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑225452 | Rel-17 CR 32.291 Correction on the mapping between EC and NEF | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑225453 | Rel-17 CR 32.257 Correction on the mapping between EC and NEF | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑225454 | Rel-17 CR 32.257 Correction on the detailed message format for converged charging | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑225455 | Rel-17 CR 32.291 Add the EAS ID for EC charging | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑225456 | Rel-17 CR 32.298 Add the EAS ID for EC charging | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑225746 | |||
S5‑225746 | Rel-17 CR 32.298 Add the EAS ID for EC charging | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑225456 | |||
S5‑225457 | Rel-17 CR 32.297 Correction on the Symbols for the Edge Computing | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑225458 | Rel-17 CR 32.298 Correction on the CHF CDR ASN.1 format | Huawei | CR | Agreement | Yes |
Yes
| merged | No | S5‑225738 | |||
S5‑225510 | Rel-17 CR 32.277 Editorial clean up | CATT | CR | Approval | Yes |
Yes
| revised | No | S5‑225739 | |||
S5‑225739 | Rel-17 CR 32.277 Editorial clean up | CATT | CR | Approval | Yes |
Yes
| agreed | No | S5‑225510 | |||
S5‑225511 | Rel-17 CR 32.277 Remove editor note on 5G Direct Communication charging | CATT | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑225512 | Rel-17 CR 32.298 Correction on 5G ProSe charging information to CHF CDR | CATT | CR | Approval | Yes |
Yes
| revised | No | S5‑225776 | |||
S5‑225776 | Rel-17 CR 32.298 Correction on 5G ProSe charging information to CHF CDR | CATT | CR | Approval | Yes |
Yes
| agreed | No | S5‑225512 | |||
S5‑225731 | Rel-16 CR 32.291 Update OpenAPI version | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑225732 | Rel-17 CR 32.291 Update OpenAPI version | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑225735 | Discussion Paper on Charging ID Uniqueness | Huawei | discussion | discussion | Yes |
Yes
| noted | No | ||||
S5‑225737 | Rel-17 CR 32.277 Correction on the name of interface for usage information collection | CATT | CR | Agreement | Yes |
Yes
| agreed | No | ||||
7.4 | Rel-18 Charging |   | ||||||||||
7.4.1 | Multimedia Messaging Service Charging using service-based interface | S5‑225288 | Rel-18 CR 32.290 Addition of MMS relay and server | Ericsson LM | CR | Agreement | Yes |
Yes
| revised | No | S5‑225720 | |
S5‑225720 | Rel-18 CR 32.290 Addition of MMS relay and server | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | S5‑225288 | |||
S5‑225289 | Rel-18 CR 32.270 Addition of converged charging architecture | Ericsson LM | CR | Agreement | Yes |
Yes
| revised | No | S5‑225721 | |||
S5‑225721 | Rel-18 CR 32.270 Addition of converged charging architecture | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | S5‑225289 | |||
S5‑225290 | Rel-18 CR 32.270 Addition of converged charging scenarios | Ericsson LM | CR | Agreement | Yes |
Yes
| revised | No | S5‑225722 | |||
S5‑225722 | Rel-18 CR 32.270 Addition of converged charging scenarios | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | S5‑225290 | |||
S5‑225291 | Rel-18 CR 32.270 Addition of converged charging information | Ericsson LM | CR | Agreement | Yes |
Yes
| revised | No | S5‑225723 | |||
S5‑225723 | Rel-18 CR 32.270 Addition of converged charging information | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | S5‑225291 | |||
S5‑225349 | Rel-18 draftCR 32.240 Adding new consumer for MMS in Charging Architecture | Amdocs Software Systems Ltd | draftCR | Approval | Yes |
Yes
| merged | No | S5‑225724 | |||
S5‑225724 | Rel-18 CR 32.240 Adding new consumer for MMS in Charging Architecture | Amdocs Software Systems Ltd | CR | Approval | Yes |
Yes
| agreed | No | ||||
7.5 | Charging studies |   | ||||||||||
7.5.1 | Study on charging aspects for enhancements of Network Slicing Phase 2 | S5‑225124 | Rel-18 pCR 32.847 Solve Editor's Note on solution#1.1 | MATRIXX Software | pCR | Agreement | Yes |
Yes
| revised | No | S5‑225725 | |
S5‑225725 | Rel-18 pCR 32.847 Solve Editor's Note on solution#1.1 | MATRIXX Software | pCR | Agreement | Yes |
Yes
| approved | No | S5‑225124 | |||
S5‑225125 | Rel-18 pCR 32.847 Solve Editors Notes on solutions#1.3 | MATRIXX Software | pCR | Agreement | Yes |
Yes
| revised | No | S5‑225755 | |||
S5‑225755 | Rel-18 pCR 32.847 Solve Editors Notes on solutions#1.3 | MATRIXX Software | pCR | Agreement | Yes |
Yes
| approved | No | S5‑225125 | |||
S5‑225126 | Rel-18 pCR 32.847 New NSACF (CTF) - NS quota management solution for Key issue#1 | MATRIXX Software | pCR | Agreement | Yes |
Yes
| revised | No | S5‑225728 | |||
S5‑225728 | Rel-18 pCR 32.847 New NSACF (CTF) - NS quota management solution for Key issue#1 | MATRIXX Software | pCR | Agreement | Yes |
Yes
| approved | No | S5‑225126 | |||
S5‑225127 | Rel-18 pCR 32.847 Evaluation and conclusion for Key issue#1 | MATRIXX Software | pCR | Agreement | Yes |
Yes
| revised | No | S5‑225762 | |||
S5‑225762 | Rel-18 pCR 32.847 Evaluation and conclusion for Key issue#1 | MATRIXX Software | pCR | Agreement | Yes |
Yes
| approved | No | S5‑225127 | |||
S5‑225128 | Rel-18 pCR 32.847 New NSACF (CTF) - NS quota management solution for Key issue#2 | MATRIXX Software | pCR | Agreement | Yes |
Yes
| revised | No | S5‑225763 | |||
S5‑225763 | Rel-18 pCR 32.847 New NSACF (CTF) - NS quota management solution for Key issue#2 | MATRIXX Software | pCR | Agreement | Yes |
Yes
| approved | No | S5‑225128 | |||
S5‑225129 | Rel-18 pCR 32.847 Solve Editor’s Note on clause 4.1 | MATRIXX Software | pCR | Agreement | Yes |
Yes
| revised | No | S5‑225727 | |||
S5‑225727 | Rel-18 pCR 32.847 Solve Editor’s Note on clause 4.1 | MATRIXX Software | pCR | Agreement | Yes |
Yes
| approved | No | S5‑225129 | |||
S5‑225400 | Rel-18 pCR 32.847 Evaluation and conclusion for Key issue#2 | MATRIXX Software | pCR | Agreement | Yes |
Yes
| revised | No | S5‑225736 | |||
S5‑225736 | Rel-18 pCR 32.847 Evaluation and conclusion for Key issue#2 | MATRIXX Software | pCR | Agreement | Yes |
Yes
| approved | No | S5‑225400 | |||
S5‑225401 | Rel-18 pCR 32.847 Solve Editors Notes on solutions#6.2 | MATRIXX Software | pCR | Agreement | Yes |
Yes
| revised | No | S5‑225726 | |||
S5‑225726 | Rel-18 pCR 32.847 Solve Editors Notes on solutions#6.2 | MATRIXX Software | pCR | Agreement | Yes |
Yes
| approved | No | S5‑225401 | |||
S5‑225402 | Rel-18 pCR 32.847 Remove Key issue#4 | MATRIXX Software | pCR | Agreement | Yes |
Yes
| approved | No | ||||
S5‑225403 | Rel-18 pCR 32.847 Convert the Key issue#9 into background | MATRIXX Software | pCR | Agreement | Yes |
Yes
| revised | No | S5‑225651 | |||
S5‑225651 | Rel-18 pCR 32.847 Convert the Key issue#9 into background | MATRIXX Software | pCR | Agreement | Yes |
Yes
| approved | No | S5‑225403 | |||
S5‑225404 | Rel-18 pCR 32.847 Clarify Potential requirements in Key issues#1 and #2 | MATRIXX Software | pCR | Agreement | Yes |
Yes
| approved | No | ||||
S5‑225406 | Rel-18 pCR 32.847 Solve Editors Note on Key Issue #5 | MATRIXX Software | pCR | Agreement | Yes |
Yes
| revised | No | S5‑225729 | |||
S5‑225729 | Rel-18 pCR 32.847 Solve Editors Note on Key Issue #5 | MATRIXX Software | pCR | Agreement | Yes |
Yes
| approved | No | S5‑225406 | |||
S5‑225715 | Draft TR 32.847 | MATRIXX Software | draft TR | Approval | Yes |
Yes
| approved | No | ||||
7.5.2 | Study on Nchf charging services phase 2 | S5‑225292 | Rel-18 pCR 28.826 Adding solution in clause 5.1 using new trigger category | Ericsson LM | pCR | Approval | Yes |
Yes
| noted | No | ||
S5‑225293 | Rel-18 pCR 28.826 Adding solution for non-blocking mode change using PCF | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑225777 | |||
S5‑225777 | Rel-18 pCR 28.826 Adding solution for non-blocking mode change using PCF | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑225293 | |||
S5‑225294 | Rel-18 pCR 28.826 Adding issue and solution to identifying non-blocking mode | Ericsson LM | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑225295 | Rel-18 pCR 28.826 Adding use case and requirement for cancel failed session charging | Ericsson LM | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑225296 | Rel-18 pCR 28.826 Adding solution for size of charging information | Ericsson LM | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑225297 | Rel-18 pCR 28.826 Adding solution for documentation structure | Ericsson LM | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑225347 | Rel-18 pCR 28.826 Adding a key issue and potential solutions for cancel failed event | Amdocs Software Systems Ltd | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑225348 | Rel-18 pCR 28.826 Adding potential solution for locating cancel failed event | Amdocs Software Systems Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑225754 | |||
S5‑225754 | Rel-18 pCR 28.826 Adding potential solution for locating cancel failed event | Amdocs Software Systems Ltd | pCR | Approval | Yes |
Yes
| approved | No | S5‑225348 | |||
S5‑225424 | Rel-18 pCR 28.826Addition of optimization on charging information accuracy | Huawei | pCR | Agreement | Yes |
Yes
| noted | No | ||||
S5‑225425 | Rel-18 pCR 28.826 Addition of Real-rate charging | Huawei | pCR | Agreement | Yes |
Yes
| noted | No | ||||
S5‑225426 | Rel-18 pCR 28.826 Addition of Threshold based re-authorization triggers optimization | Huawei | pCR | Agreement | Yes |
Yes
| noted | No | ||||
S5‑225427 | Rel-18 pCR 28.826 Addition of Usage Data Report | Huawei | pCR | Agreement | Yes |
Yes
| noted | No | ||||
S5‑225716 | Draft TR 28.826 | Ericsson | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S5‑225733 | Presentation of TR 28.826 for Information | Ericsson | TS or TR cover | Approval | Yes |
Yes
| approved | No | ||||
7.5.3 | Study on 5G roaming charging architecture for wholesale and retail scenarios | S5‑225298 | Rel-18 pCR 28.827 Mapping requirement and issue in clause 7.2 | Ericsson, Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||
S5‑225299 | Rel-18 pCR 28.827 Adding solutions in clause 7.1 for VPLMN wholesale charging of HPLMN | Ericsson LM | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑225300 | Rel-18 pCR 28.827 Adding solutions in clause 7.2 for trigger handling between visited and home CHF | Ericsson LM | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑225301 | Rel-18 pCR 28.827 Adding use case in clause 7.4 where there are multiple additional actors | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑225730 | |||
S5‑225730 | Rel-18 pCR 28.827 Adding use case in clause 7.4 where there are multiple additional actors | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑225301 | |||
S5‑225302 | Rel-18 pCR 28.827 Adding use case in clause 7.5 for roaming where there are multiple additional actors | Ericsson LM | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑225303 | Rel-18 pCR 28.827 Adding solution in clause 7.6 for UE reported reconciliation | Ericsson LM | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑225304 | Rel-18 pCR 28.827 Adding solution in clause 7.6 for user reported reconciliation | Ericsson LM | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑225305 | Rel-18 pCR 28.827 Update of business roles | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑225734 | |||
S5‑225734 | Rel-18 pCR 28.827 Update of business roles | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑225305 | |||
S5‑225428 | Rel-18 pCR 28.827 Add new solution for FBC negotiation | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑225748 | |||
S5‑225748 | Rel-18 pCR 28.827 Add new solution for FBC negotiation | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑225428 | |||
S5‑225429 | Rel-18 pCR 28.827 Add new solution for PDU session level negotiation | Huawei | pCR | Agreement | Yes |
Yes
| noted | No | ||||
S5‑225430 | Rel-18 pCR 28.827 Add new solution for QBC trigger setting | Huawei | pCR | Agreement | Yes |
Yes
| noted | No | ||||
S5‑225431 | Rel-18 pCR 28.827 Add new solution for Roaming Charging Profile Update | Huawei | pCR | Agreement | Yes |
Yes
| noted | No | ||||
S5‑225432 | Rel-18 pCR 28.827 Add the solution of V-SMF connect to V-CHF with two charging sessions | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑225751 | |||
S5‑225751 | Rel-18 pCR 28.827 Add the solution of V-SMF connect to V-CHF with two charging sessions | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑225432 | |||
S5‑225433 | Rel-18 pCR 28.827 Add the solution of V-SMF connects to V-CHF with single charging session | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑225649 | |||
S5‑225649 | Rel-18 pCR 28.827 Add the solution of V-SMF connects to V-CHF with single charging session | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑225433 | |||
S5‑225434 | Rel-18 pCR 28.827 Add the solution V-CHF controls reporting in single charging session | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑225752 | |||
S5‑225752 | Rel-18 pCR 28.827 Add the solution V-CHF controls reporting in single charging session | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑225434 | |||
S5‑225435 | Rel-18 pCR 28.827 Add the solution V-SMF controls reporting in single charging session | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑225753 | |||
S5‑225753 | Rel-18 pCR 28.827 Add the solution V-SMF controls reporting in single charging session | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑225435 | |||
S5‑225436 | Rel-18 pCR 28.827 Correction on the Unified Term for NF in the HPLMN and VPLMN | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | ||||
S5‑225717 | Draft TR 28.827 | Ericsson | draft TR | Approval | Yes |
Yes
| approved | No | ||||
7.5.4 | Study on Charging Aspects for Enhanced support of Non-Public Networks | S5‑225185 | Rel-18 pCR 28.828 Add end user charging solution to SNPN network access and usage | China Mobile | pCR | Approval | Yes |
Yes
| revised | No | S5‑225652 | |
S5‑225652 | Rel-18 pCR 28.828 Add end user charging solution to SNPN network access and usage | China Mobile | pCR | Approval | Yes |
Yes
| approved | No | S5‑225185 | |||
S5‑225186 | Rel-18 pCR 28.828 Introduction of use case and solution on number of UEs | China Mobile | pCR | Approval | Yes |
Yes
| revised | No | S5‑225764 | |||
S5‑225764 | Rel-18 pCR 28.828 Introduction of use case and solution on number of UEs | China Mobile | pCR | Approval | Yes |
Yes
| approved | No | S5‑225186 | |||
S5‑225188 | Rel-18 pCR 28.828 New charging scenarios and key issues for PNI-NPN topic 1 | China Mobile | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑225189 | Rel-18 pCR 28.828 Adding solution on number of PDU sessions for PNI-NPN | China Mobile | pCR | Approval | Yes |
Yes
| revised | No | S5‑225765 | |||
S5‑225765 | Rel-18 pCR 28.828 Adding solution on number of PDU sessions for PNI-NPN | China Mobile | pCR | Approval | Yes |
Yes
| approved | No | S5‑225189 | |||
S5‑225190 | Rel-18 pCR 28.828 New charging scenarios and key issues for SNPN topic 2 | China Mobile | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑225191 | Rel-18 pCR 28.828 Adding solution on number of PDU sessions for SNPN | China Mobile | pCR | Approval | Yes |
Yes
| revised | No | S5‑225766 | |||
S5‑225766 | Rel-18 pCR 28.828 Adding solution on number of PDU sessions for SNPN | China Mobile | pCR | Approval | Yes |
Yes
| approved | No | S5‑225191 | |||
S5‑225306 | Rel-18 pCR 28.828 Addition of solution for converged charging for number of UEs | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑225647 | |||
S5‑225647 | Rel-18 pCR 28.828 Addition of solution for converged charging for number of UEs | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑225306 | |||
S5‑225437 | Rel-18 pCR 28.828 Add the solution for SNPN access the PLMN services | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑225653 | |||
S5‑225653 | Rel-18 pCR 28.828 Add the solution for SNPN access the PLMN services | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑225437 | |||
S5‑225438 | Rel-18 pCR 28.828 Correction on the use cases description in the Topic 1 | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | ||||
S5‑225439 | Rel-18 pCR 28.828 Correction on the use cases description in the Topic 3 | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | ||||
S5‑225718 | Draft TR 28.828 | China Mobile | draft TR | 28.828 | Yes |
Yes
| approved | No | ||||
S5‑225758 | Presentation of TR 28.828 for Information | China Mobile | TS or TR cover | Approval | Yes |
Yes
| approved | No | ||||
7.5.5 | New SID on Time Sensitive Networking charging | S5‑225492 | Rel-18 pCR 28.xxx Update of the Reference | Huawei | other | Agreement | Yes |
Yes
| approved | No | ||
S5‑225493 | Rel-18 pCR 28.xxx Update of the Scope | Huawei | other | Agreement | Yes |
Yes
| revised | No | S5‑225757 | |||
S5‑225757 | Rel-18 pCR 28.xxx Update of the Scope | Huawei | other | Agreement | Yes |
Yes
| approved | No | S5‑225493 | |||
S5‑225494 | Rel-18 TR 28.xxx v0.0.0 Initial skeleton | Huawei | other | Agreement | Yes |
Yes
| revised | No | S5‑225756 | |||
S5‑225756 | Rel-18 TR 28.xxx v0.0.0 Initial skeleton | Huawei | other | Agreement | Yes |
Yes
| approved | No | S5‑225494 | |||
S5‑225719 | Draft TR 28.XXX | Huawei | other | Approval | Yes |
Yes
| approved | No | ||||
8 | Any Other Business |   | ||||||||||
9 | Closing of the meeting |   |