Tdoc List
2023-03-06 17:20
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‑232000 | Agenda | WG Chair | agenda | Yes |
Yes
| revised | No | S5‑232063 | ||
S5‑232063 | Agenda | WG Chair | agenda | Yes |
Yes
| approved | No | S5‑232000 | ||||
3 | IPR and legal declaration | S5‑232001 | IPR and legal declaration | WG Chair | other | Yes |
Yes
| noted | No | |||
4 | Meetings and activities reports |   | ||||||||||
4.1 | Last SA5 meeting report | S5‑232002 | Report from last SA5 meeting | MCC | report | Yes |
Yes
| approved | No | |||
4.2 | Inter-organizational reports |   | ||||||||||
5 | SA5 level issues |   | ||||||||||
5.1 | Administrative issues at SA5 level | S5‑232003 | Post e-meeting email approval status | WG Chair | other | No |
No
| reserved | No | |||
S5‑232010 | SA5 working procedures | WG Chair | other | Yes |
Yes
| approved | No | |||||
S5‑232014 | Process for management of draft TS-TRs | WG Chair | other | Yes |
Yes
| noted | No | |||||
S5‑232081 | Discussion paper on Using Forge-Git as the primary storage for Code | Ericsson Hungary Ltd | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑232751 | |||
S5‑232751 | Discussion paper on Using Forge-Git as the primary storage for Code | Ericsson Hungary Ltd | discussion | Endorsement | Yes |
Yes
| endorsed | No | S5‑232081 | |||
S5‑232235 | Using Forge for SA5 | Nokia, Nokia Shanghai Bell | other | Information | Yes |
YesNokia asked what happened at SA plenary, what was approved.Ericsson replied that the cover page stayed, stage 3 only would reside in FORGE.
Nokia was concerned what could be reviewed at SA level. Ericsson clarified that there would be a FORGE a link to the changes in FORGE (merge request). The SA5 Chair commented that this implied a change in the 3GPP working procedures that had to be approved at SA level.
| noted | No | ||||
S5‑232720 | Non-Rel18 OpenAPI files handling in Rel18 branch | Nokia, Nokia Shanghai Bell | discussion | Endorsement | Yes |
Yes
| endorsed | No | ||||
5.2 | Technical issues at SA5 level | S5‑232459 | SA5 Collection of Rel-19 potential topics for SA workshop preparation | SA5 Vice chair (Huawei) | Work Plan | Endorsement | Yes |
Yes
| revised | No | S5‑232752 | |
S5‑232752 | SA5 Collection of Rel-19 potential topics for SA workshop preparation | SA5 Vice chair (Huawei) | discussion | Endorsement | Yes |
Yes
| endorsed | No | S5‑232459 | |||
5.3 | Liaison statements at SA5 level | S5‑232020 | LS on Tracking IANA assignment requests | CP-223275 | LS in | Yes |
Yes
| noted | No | |||
S5‑232021 | LS on ENSWI PRD Publication | GSMA | LS in | Yes |
Yes
| replied to | No | |||||
S5‑232033 | Reply LS on Network federation interface for Telco edge consideration | S3-223914 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑232753 | Reply to: Reply LS on Network federation interface for Telco edge consideration | Samsung | LS out | approval | Yes |
Yes
| revised | No | S5‑233146 | |||
S5‑233146 | Reply to: Reply LS on Network federation interface for Telco edge consideration | Samsung | LS out | approval | Yes |
Yes
| approved | No | S5‑232753 | |||
S5‑232041 | Reply LS ccSA5 on Network federation interface for Telco edge consideration for a consolidated reply | S6-223553 | LS in | Yes |
Yes
| noted | No | |||||
S5‑232045 | LS on the new work item Y.Arch_NGNe_ncp ""Architectural evolution of NGN control plane by applying SDN technology"" | ITU-T | LS in | Yes |
Yes
| postponed | No | |||||
S5‑232046 | LS on the consent of draft new Recommendation ITU-T Y.3183 (ex. ITU-T Y.ML-IMT2020-VNS): ""Framework for network slicing management assisted by machine learning leveraging QoE feedback from verticals"" | ITU-T | LS in | Yes |
Yes
| postponed | No | |||||
S5‑232047 | Reply LS ccSA5 on Network federation interface for Telco edge consideration | SP-221321 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑232754 | Reply to: Reply LS ccSA5 on Network federation interface for Telco edge consideration | Samsung | LS out | approval | Yes |
Yes
| revised | No | S5‑233147 | |||
S5‑233147 | Reply to: Reply LS ccSA5 on Network federation interface for Telco edge consideration | Samsung | LS out | approval | Yes |
Yes
| approved | No | S5‑232754 | |||
S5‑232082 | LS on need for modeling isInvariant and SystemCreated in YANG | Ericsson Hungary Ltd | LS out | Approval | Yes |
Yes
| revised | No | S5‑232770 | |||
S5‑232770 | LS on need for modeling isInvariant and SystemCreated in YANG | Ericsson Hungary Ltd | LS out | Approval | Yes |
Yes
| approved | No | S5‑232082 | |||
S5‑232413 | LS to GSMA on E2E Network Slicing Requirements | Huawei | LS out | Approval | Yes |
Yes
| revised | No | S5‑232768 | |||
S5‑232768 | LS to GSMA on E2E Network Slicing Requirements | Huawei | LS out | Approval | Yes |
Yes
| approved | No | S5‑232413 | |||
5.4 | SA5 meeting calendar | S5‑232015 | SA5 meeting calendar | WG Chair | other | Yes |
Yes
| noted | No | |||
6 | OAM&P |   | ||||||||||
6.1 | OAM&P Plenary | S5‑232004 | OAM&P action list | WG Vice Chair (Huawei) | other | Yes |
Yes
| noted | No | |||
S5‑232005 | agenda_with_Tdocs_sequence_proposal_OAM | WG Vice Chair (Huawei) | agenda | Yes |
Yes
| noted | No | |||||
S5‑232006 | OAM Exec Report | WG Vice Chair (Huawei) | report | No |
No
| reserved | No | |||||
S5‑232007 | OAM Chair notes and conclusions | WG Chair | report | Yes |
No
| available | No | |||||
S5‑232011 | Collection of useful endorsed document and external communication documents | WG Vice Chair (Huawei) | discussion | Yes |
Yes
| noted | No | |||||
S5‑232012 | Collection of Rel-18 3GPP SA5 OAM WoP | WG Vice Chair (Huawei) | discussion | Yes |
Yes
| noted | No | |||||
S5‑232013 | Living document for stage 2-3 alignment | WG Chair | other | No |
Yes
| email approval | No | |||||
S5‑232016 | Time Plan for OAM&P sessions | WG Chair | other | Yes |
Yes
| noted | No | |||||
S5‑232017 | F2F meeting process for OAM | WG Chair | other | Yes |
Yes
| noted | No | |||||
S5‑232018 | NGMN Reply LS to 3GPP SA5 on customer acceptance of limited QoS degradation to save energy in the network | NGMN | LS in | Yes |
Yes
| replied to | No | |||||
S5‑232022 | LS on Autonomous Networks deliverables from ITU FG-AN | ITU FG-AN | LS in | Yes |
Yes
| noted | No | |||||
S5‑232024 | LS on QoE measurements in RRC IDLE/INACTIVE states | R2-2213054 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑232025 | Resubmitted LS on introduction of a new attribute “Only Resource Coordination” to support source coordination between LTE and NR SA | R3-225206 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑232026 | Resubmitted LS on NCR Solutions | R3-225253 | LS in | Yes |
Yes
| postponed | No | |||||
S5‑232027 | LS on Excess Packet Delay for MDT | R3-226873 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑232028 | Reply LS ccSA5 on DN energy efficiency data analytics | S1-223542 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑232764 | Reply to: Reply LS ccSA5 on DN energy efficiency data analytics | Huawei | LS out | approval | Yes |
Yes
| approved | No | ||||
S5‑232030 | LS on Performance measurement for AI/ML | S2-2211428 | LS in | Yes |
Yes
| postponed | No | |||||
S5‑232031 | LS on secured and trusted access to the serving PLMN OAM server by a MBSR | S2-2301465 | LS in | Yes |
Yes
| postponed | No | |||||
S5‑232034 | Resubmitted Reply LS to Study on KQIs for 5G service experience | S4-221120 | LS in | Yes |
Yes
| noted | No | |||||
S5‑232035 | Resubmitted Reply LS to SA5 on TS 28.404/TS 28.405 Clarification | S4-221121 | LS in | Yes |
Yes
| postponed | No | |||||
S5‑232036 | Reply LS ccSA5 on Rel-18 enhancement of NR QoE | S4-221493 | LS in | Yes |
Yes
| noted | No | |||||
S5‑232037 | Reply LS ccSA5 on EAS relocation affinity | S4-221495 | LS in | Yes |
Yes
| noted | No | |||||
S5‑232038 | Follow-up LS to SA5 on Study on KQIs for 5G service experience | S4-221496 | LS in | Yes |
Yes
| noted | No | |||||
S5‑232039 | Reply LS to RAN3 ccSA5 on RAN visible QoE value | S4-221604 | LS in | Yes |
Yes
| noted | No | |||||
S5‑232040 | Resubmitted reply LS on “Reply LS on FS_eEDGEAPP, Solution for Dynamic EAS instantiation” | S6-222344 | LS in | Yes |
Yes
| noted | No | |||||
S5‑232042 | Clarification on the deployment of bundle EAS | S6-223587 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑232043 | Reply LS ccSA5 on EAS type attribute for EAS discovery | S6-230452 | LS in | Yes |
Yes
| noted | No | |||||
S5‑232044 | LS on the initiation of the new work item Y.AN-Arch-fw: ""Architecture Framework for Autonomous Networks"" | SG13-LS37 | LS in | Yes |
Yes
| noted | No | |||||
S5‑232048 | Resubmitted LS to 3GPP SA5 on UE to application server latency | GSMA | LS in | Yes |
Yes
| replied to | No | |||||
S5‑232049 | Resubmitted LS on RAN3 agreements for NR QoE | R3-222890 | LS in | Yes |
Yes
| postponed | No | |||||
S5‑232050 | Resubmitted LS on O-RAN – Transport Network Slicing Enhancement IM/DM TS28.541 | O-RAN | LS in | Yes |
Yes
| postponed | No | |||||
S5‑232051 | LS/r on RAN visible QoE value (reply to 3GPP-LS8) | ITU-T SG12 | LS in | Yes |
Yes
| noted | No | |||||
S5‑232052 | Reply LS on customer acceptation of limited QoS degradation to save energy in the network | Huawei | LS out | Approval | Yes |
Yes
| revised | No | S5‑232757 | |||
S5‑232757 | Reply LS on customer acceptation of limited QoS degradation to save energy in the network | Huawei | LS out | Approval | Yes |
Yes
| approved | No | S5‑232052 | |||
S5‑232065 | LS to SA1 on Customer acceptation of QoS degradation to save energy | Huawei | LS out | Agreement | Yes |
Yes
| revised | No | S5‑232758 | |||
S5‑232758 | LS to SA1 on Customer acceptation of QoS degradation to save energy | Huawei | LS out | Agreement | Yes |
Yes
| approved | No | S5‑232065 | |||
S5‑232071 | LS on Invitation to the ETSI ISG NFV’s 10 years anniversary | ETSI ISG NFV | LS in | Yes |
Yes
| noted | No | |||||
S5‑232150 | Reply LS on Excess Packet Delay Threshold for MDT | Nokia, Nokia Shanghai Bell | LS out | Approval | Yes |
Yes
| approved | No | ||||
S5‑232268 | Reply LS on introduction of a new attribute “Only Resource Coordination” to support source coordination between LTE and NR SA | China Telecom Corporation Ltd. | LS out | Approval | Yes |
Yes
| revised | No | S5‑233142 | |||
S5‑233142 | Reply LS on introduction of a new attribute “Only Resource Coordination” to support source coordination between LTE and NR SA | China Telecom Corporation Ltd. | LS out | Approval | No |
Yes
| email approval | No | S5‑232268 | |||
S5‑232270 | Reply LS on QoE measurements in RRC IDLEINACTIVE states | Huawei | LS out | Approval | Yes |
Yes
| revised | No | S5‑232760 | |||
S5‑232760 | Reply LS on QoE measurements in RRC IDLEINACTIVE states | Huawei | LS out | Approval | Yes |
Yes
| approved | No | S5‑232270 | |||
S5‑232285 | LS reply to GSMA OPG on UE to application server latency | Huawei | LS out | Approval | Yes |
Yes
| revised | No | S5‑232759 | |||
S5‑232759 | LS reply to GSMA OPG on UE to application server latency | Huawei | LS out | Approval | Yes |
Yes
| approved | No | S5‑232285 | |||
S5‑232286 | Reply LS S6-223587 Clarification on the deployment of bundle EAS | Huawei | LS out | Approval | Yes |
Yes
| revised | No | S5‑232762 | |||
S5‑232762 | Reply LS S6-223587 Clarification on the deployment of bundle EAS | Huawei | LS out | Approval | Yes |
Yes
| approved | No | S5‑232286 | |||
S5‑232446 | Rel-18&Rel-19 time plan proposal for OAM | SA5 Vice chair (Huawei),SA5 Chair | discussion | Information | Yes |
Yes
| revised | No | S5‑232763 | S5‑231032 | ||
S5‑232763 | Rel-18&Rel-19 time plan proposal for OAM | SA5 Vice chair (Huawei),SA5 Chair | discussion | Endorsement | Yes |
Yes
| endorsed | No | S5‑232446 | |||
S5‑232458 | Collection of Rel-19 OAM potential topics for SA workshop preparation | HuaWei Technologies Co., Ltd | Work Plan | Endorsement | No |
Yes
| withdrawn | Yes | ||||
S5‑232528 | DP on way forward for mulitple data collection mechanisms | Huawei | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑232902 | S5‑231040 | ||
S5‑232902 | DP on way forward for mulitple data collection mechanisms | Huawei | discussion | Endorsement | Yes |
Yes
| noted | No | S5‑232528 | |||
S5‑232611 | LS on RAN UE Id optionality | Ericsson LM | LS out | Approval | Yes |
Yes
| revised | No | S5‑232761 | |||
S5‑232761 | LS on RAN UE Id optionality | Ericsson LM | LS out | Approval | Yes |
Yes
| approved | No | S5‑232611 | |||
S5‑232685 | Service Management | Ericsson | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑232766 | |||
S5‑232766 | Service Management | Ericsson | discussion | Endorsement | Yes |
Yes
| noted | No | S5‑232685 | |||
S5‑232779 | LS on O-RAN - Applicability of TS 32.404 in NR | O-RAN | LS in | discussion | Yes |
Yes
| postponed | No | ||||
6.2 | New OAM&P Work Item proposals |   | ||||||||||
6.2.1 | Intelligence and Automation | S5‑232400 | New WID on measurement data collection to support RAN intelligence | Intel Belgium SA/NV | WID new | Approval | Yes |
Yes
| revised | No | S5‑232756 | |
S5‑232756 | Revised WID on enhancements of 5G performance measurements and KPIs phase 2 | Intel Belgium SA/NV | WID revised | Approval | Yes |
Yes
| revised | No | S5‑233143 | S5‑232400 | ||
S5‑233143 | Revised WID on enhancements of 5G performance measurements and KPIs phase 2 | Intel Belgium SA/NV | WID revised | Approval | Yes |
Yes
| agreed | No | S5‑232756 | |||
S5‑232417 | New Rel-18 WID on Intent driven Management Service for mobile network phase 2 | Huawei | WID new | Agreement | Yes |
Yes
| revised | No | S5‑232767 | S5‑231200 | ||
S5‑232767 | New Rel-18 WID on Intent driven Management Service for mobile network phase 2 | Huawei | WID new | Agreement | Yes |
Yes
| agreed | No | S5‑232417 | |||
S5‑232530 | New WID on autonomous network levels phase 2 | China Mobile, Huawei, AsiaInfo, CATT, ZTE, China Unicom, Intel | WID new | Approval | Yes |
Yes
| revised | No | S5‑232769 | S5‑231089 | ||
S5‑232769 | New WID on autonomous network levels phase 2 | China Mobile, Huawei, AsiaInfo, CATT, ZTE, China Unicom, Intel | WID new | Approval | Yes |
Yes
| noted | No | S5‑232530 | |||
S5‑232557 | New Rel-18 WID on Enhancement of the Management Aspects related to NWDAF | Chinatelecom Cloud | WID new | Approval | Yes |
Yes
| revised | No | S5‑232773 | |||
S5‑232773 | New Rel-18 WID on Enhancement of the Management Aspects related to NWDAF | Chinatelecom Cloud | WID new | Approval | Yes |
Yes
| agreed | No | S5‑232557 | |||
S5‑232624 | Update of Study on Enhancement of the management aspects related to NWDAF | China Telecom | SID revised | Approval | Yes |
Yes
| endorsed | No | S5‑215499 | |||
S5‑232774 | LS on clarification on analytics related capabilities | China Telecom | LS out | Approval | Yes |
Yes
| approved | No | ||||
6.2.2 | Management Architecture and Mechanisms | S5‑232382 | New WID on SBMA enablers | Nokia, Nokia Shanghai Bell | WID new | Approval | Yes |
Yes
| merged | No | S5‑232775 | |
S5‑232427 | New WID on Management Aspect of 5GLAN | China Mobile Com. Corporation | WID new | Approval | Yes |
Yes
| revised | No | S5‑232776 | |||
S5‑232776 | New WID on Management Aspect of 5GLAN | China Mobile Com. Corporation | WID new | Approval | Yes |
Yes
| revised | No | S5‑233145 | S5‑232427 | ||
S5‑233145 | New WID on Management Aspect of 5GLAN | China Mobile Com. Corporation | WID new | Approval | Yes |
Yes
| agreed | No | S5‑232776 | |||
S5‑232452 | new WID on Enhancement of service based management architecture | HuaWei Technologies Co., Ltd | WID new | Yes |
Yes
| revised | No | S5‑232775 | S5‑231047 | |||
S5‑232775 | new WID on Enhancement of service based management architecture | HuaWei Technologies Co., Ltd | WID new | - | Yes |
Yes
| revised | No | S5‑233144 | S5‑232452 | ||
S5‑233144 | new WID on Enhancement of service based management architecture | Huawei,Ericsson, Nokia | WID new | - | Yes |
Yes
| agreed | No | S5‑232775 | |||
S5‑232462 | Rel-18 WI Management Features | 3GPP SA5 VC (Huawei) | discussion | Yes |
Yes
| noted | No | |||||
S5‑232472 | New WID on Management Aspects of NTN | China Unicom,CATT | WID new | Approval | Yes |
Yes
| revised | No | S5‑232809 | |||
S5‑232809 | New WID on Management Aspects of NTN | China Unicom,CATT | WID new | Approval | Yes |
Yes
| agreed | No | S5‑232472 | |||
S5‑232513 | New Rel-18 WID on Management Aspect of 5G Network Sharing Phase2 | China Unicom, Huawei, CATT, China Telecom, ZTE, CMCC, AsiaInfo | WID new | Approval | Yes |
Yes
| revised | No | S5‑233131 | |||
S5‑233131 | New Rel-18 WID on Management Aspect of 5G Network Sharing Phase2 | China Unicom, Huawei, CATT, China Telecom, ZTE, CMCC, AsiaInfo | WID new | Approval | Yes |
Yes
| noted | No | S5‑232513 | |||
S5‑232517 | New Rel-18 WID on Management Aspects of URLLC | China Unicom, Huawei, CATT, China Telecom, ZTE, CMCC, AsiaInfo | WID new | Approval | Yes |
Yes
| revised | No | S5‑233130 | |||
S5‑233130 | New Rel-18 WID on Management Aspects of URLLC | China Unicom, Huawei, CATT, China Telecom, ZTE, CMCC, AsiaInfo | WID new | Approval | Yes |
Yes
| noted | No | S5‑232517 | |||
S5‑232662 | New WID on Management of cloud-native Virtualized Network Functions | China Mobile E-Commerce Co. | WID new | Approval | Yes |
Yes
| revised | No | S5‑232810 | |||
S5‑232810 | New WID on Management of cloud-native Virtualized Network Functions | China Mobile E-Commerce Co. | WID new | Approval | Yes |
Yes
| noted | No | S5‑232662 | |||
S5‑232686 | New WID on enhance SBMA specifications structure | Ericsson | WID new | Yes |
Yes
| merged | No | S5‑232775 | ||||
6.2.3 | Support of New Services | S5‑232414 | New WID on enhanced management of non-public networks | Huawei | WID new | Approval | Yes |
Yes
| revised | No | S5‑232811 | |
S5‑232811 | New WID on enhanced management of non-public networks | Huawei | WID new | Approval | Yes |
Yes
| agreed | No | S5‑232414 | |||
S5‑232456 | New WID on network slice management capability exposure | Alibaba Group, AsiaInfo, China mobile, China Unicom | WID new | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑232567 | New WID on network slice management capability exposure | Alibaba Group, AsiaInfo, China mobile, China Unicom | WID new | Approval | Yes |
Yes
| revised | No | S5‑232812 | |||
S5‑232812 | New WID on network slice management capability exposure | Alibaba Group, AsiaInfo, China mobile, China Unicom | WID new | Approval | Yes |
Yes
| noted | No | S5‑232567 | |||
S5‑232651 | New Work Item on Network and Service Operations for Energy Utilities | Samsung, EUTC, EDF, BMWK, Deutsche Telekom | WID new | Agreement | Yes |
Yes
| revised | No | S5‑232813 | |||
S5‑232813 | New Work Item on Network and Service Operations for Energy Utilities | Samsung, EUTC, EDF, BMWK, Deutsche Telekom | WID new | Agreement | Yes |
YesNokia objected: not ready to start the normative work. We need to check the latest CRs on this subject.
Samsung: we would like to submit this in April to start the work in May.
| noted | No | S5‑232651 | |||
6.3 | OAM&P Maintenance and Rel-18 small Enhancements |   | ||||||||||
6.3.1 | Methodology | S5‑232075 | Deprecate passedById | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| not pursued | No | ||
S5‑232076 | Deprecate passedById | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| revised | No | S5‑233070 | |||
S5‑233070 | Deprecate passedById | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| agreed | No | S5‑232076 | |||
S5‑232078 | Clarifying multilevel attribute properties | Ericsson Hungary Ltd | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑232079 | Clarifying multilevel attribute properties | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| revised | No | S5‑233071 | |||
S5‑233071 | Clarifying multilevel attribute properties | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| not pursued | No | S5‑232079 | |||
S5‑232080 | Clarifying multilevel attribute properties | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| revised | No | S5‑233072 | |||
S5‑233072 | Clarifying multilevel attribute properties | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| not pursued | No | S5‑232080 | |||
S5‑232083 | DP on restructuring TS 28-545 | Ericsson Hungary Ltd | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑232771 | |||
S5‑232771 | DP on restructuring TS 28-545 | Ericsson Hungary Ltd | discussion | Endorsement | Yes |
Yes
| endorsed | No | S5‑232083 | |||
S5‑232269 | YANG Corrections | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| revised | No | S5‑232772 | |||
S5‑232772 | YANG Corrections | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| agreed | No | S5‑232269 | |||
S5‑232690 | Clarification of Requirements and Use Case template | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| revised | No | S5‑233073 | |||
S5‑233073 | Clarification of Requirements and Use Case template | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| revised | No | S5‑233148 | S5‑232690 | ||
S5‑233148 | Clarification of Requirements and Use Case template | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| agreed | No | S5‑233073 | |||
6.3.2 | ANL |   | ||||||||||
6.3.3 | MDAS | S5‑232061 | Fixing inconsistencies in Energy Saving related attribute definitions | Huawei | CR | Approval | Yes |
Yes
| agreed | No | ||
S5‑232164 | Rel-17 CR TS 28.622 Adding "altitude" to GeoArea datatype | Nokia, Nokia Shangai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑232167 | Rel-17 CR TS 28.623 Adding "altitude" to GeoArea datatype - Stage 3 | Nokia, Nokia Shangai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑232172 | Rel-18 CR TS 28.622 Adding "altitude" to GeoArea datatype | Nokia, Nokia Shangai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑232174 | Rel-18 CR TS 28.623 Adding "altitude" to GeoArea datatype - Stage 3 | Nokia, Nokia Shangai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑232204 | Rel-17 CR TS 28.105 Correction of the figure for ML training function | Ericsson India Private Limited | CR | Agreement | Yes |
Yes
| withdrawn | Yes | ||||
S5‑232271 | Rel-17 CR TS 28.104 correct error of references number | Huawei | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑232272 | Rel-17 CR TS 28.104 Adding missing support qualifier of maintenance analysis use case | Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑232981 | |||
S5‑232981 | Rel-17 CR TS 28.104 Adding missing support qualifier of maintenance analysis use case | Huawei | CR | Approval | Yes |
Yes
| not pursued | No | S5‑232272 | |||
S5‑232273 | Rel-17 CR TS 28.104 Correct errors in HOTargetType and NRM fragment note | Huawei | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑232290 | Improve definition of network slice throughput analysis | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑232297 | Correct multiplicity of attribute mDAOutputIEName | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑232368 | Correction of terminology | Intel, NEC | CR | Agreement | Yes |
Yes
| revised | No | S5‑233059 | |||
S5‑233059 | Correction of terminology | Intel, NEC | CR | Agreement | Yes |
Yes
| agreed | No | S5‑232368 | |||
S5‑232395 | Rel-18 CR 28.104 Clarification of energy saving analysis use case | Intel Belgium SA/NV | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑232716 | Rel-17 CR 28.532 Add predicted alarms (stage 2) | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | ||||
6.3.4 | AI/ML | S5‑232161 | Rel-17 CR TS 28.105 Adding the missing definition of attributes Stage 2 and Stage 3 | Nokia, Nokia Shangai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||
S5‑232162 | Rel-17 CR TS 28.105 Adding the missing relation between ML entity and ML process | Nokia, Nokia Shangai Bell | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑232163 | Rel-17 CR TS 28.105 Correcting the attribute properties | Nokia, Nokia Shangai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑233067 | |||
S5‑233067 | Rel-17 CR TS 28.105 Correcting the attribute properties | Nokia, Nokia Shangai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑232163 | |||
S5‑232202 | Correction of the Handling errors in data and ML decisions | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑233060 | |||
S5‑233060 | Correction of the Handling errors in data and ML decisions | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑232202 | |||
S5‑232203 | Rel-17 CR TS 28.105 Correction of terminologies | Ericsson India Private Limited | CR | Agreement | Yes |
Yes
| revised | No | S5‑233061 | |||
S5‑233061 | Rel-17 CR TS 28.105 Correction of terminologies | Ericsson India Private Limited | CR | Agreement | Yes |
Yes
| agreed | No | S5‑232203 | |||
S5‑232276 | Rel-17 CR TS 28.105 correct AI/ML related terms | Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑233062 | |||
S5‑233062 | Rel-17 CR TS 28.105 correct AI/ML related terms | Huawei | CR | Approval | Yes |
Yes
| agreed | No | S5‑232276 | |||
S5‑232277 | Rel-17 CR TS 28.105 correct formatting and spelling errors | Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑233068 | |||
S5‑233068 | Rel-17 CR TS 28.105 correct formatting and spelling errors | Huawei | CR | Approval | Yes |
Yes
| agreed | No | S5‑232277 | |||
S5‑232278 | Rel17 CR TS 28.105 correct attribute definitions | Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑233069 | |||
S5‑233069 | Rel17 CR TS 28.105 correct attribute definitions | Huawei | CR | Approval | Yes |
Yes
| agreed | No | S5‑232278 | |||
S5‑232370 | Correction of terminology | Intel, NEC | CR | Agreement | Yes |
Yes
| merged | No | S5‑233061 | |||
S5‑232715 | Rel-17 CR TS 28.105 Correction of the figure for ML training function | Ericsson India Private Limited | CR | Agreement | Yes |
Yes
| revised | No | S5‑233063 | |||
S5‑233063 | Rel-17 CR TS 28.105 Correction of the figure for ML training function | Ericsson India Private Limited | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑232715 | |||
6.3.5 | Energy efficiency | S5‑232053 | Correct latency-based URLLC EE KPI unit | Huawei | CR | Approval | Yes |
Yes
| agreed | No | ||
S5‑232054 | Correct latency-based URLLC EE KPI unit | Huawei | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑232055 | Correct measurement used for eMBB and URLLC EE KPIs | Huawei | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑232056 | Correct measurement used for eMBB and URLLC EE KPIs | Huawei | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑232057 | Correct error in definition of ‘Average e2e uplink delay for a network slice’ | Huawei | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑232058 | Correct error in definition of ‘Average e2e uplink delay for a network slice’ | Huawei | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑232059 | Correct error in estimated VNFC energy consumption | Huawei | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑232060 | Correct error in estimated VNFC energy consumption | Huawei | CR | Approval | Yes |
Yes
| agreed | No | ||||
6.3.6 | Intent driven management | S5‑232181 | Update procedures for delete an intent and query an intent | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑233074 | |
S5‑233074 | Update procedures for delete an intent and query an intent | Huawei, Deutsche Telekom | CR | Agreement | Yes |
Yes
| agreed | No | S5‑232181 | |||
S5‑232182 | Udpate Annex C Mapping the 3GPP and the TM Forum intentExpectation Models | Huawei, Deutsche Telekom | CR | Agreement | Yes |
Yes
| revised | No | S5‑233075 | |||
S5‑233075 | Udpate Annex C Mapping the 3GPP and the TM Forum intentExpectation Models | Huawei, Deutsche Telekom | CR | Agreement | Yes |
Yes
| agreed | No | S5‑232182 | |||
S5‑232183 | Update clause 4.2.2 Intent driven MnS | Huawei,Deutsche Telekom | CR | Agreement | Yes |
Yes
| revised | No | S5‑233076 | |||
S5‑233076 | Update clause 4.2.2 Intent driven MnS | Huawei,Deutsche Telekom | CR | Agreement | Yes |
Yes
| agreed | No | S5‑232183 | |||
S5‑232245 | Add clarification on cluase 4.5 General concept of Intent Content | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑233077 | |||
S5‑233077 | Add clarification on cluase 4.5 General concept of Intent Content | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑232245 | |||
S5‑232246 | Update clause 6.2.2.1.2.4 ExpectationContexts | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑232247 | Correct the value of the defaultValue in Table 6.2.2.2-1 | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑232287 | Correct Context date type definition | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑233078 | |||
S5‑233078 | Correct Context date type definition | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑232287 | |||
S5‑232288 | Change targetAttribute to targetName | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑232289 | Update the figure 6.2.1.1.1-1:Relationship UML diagram for intent | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑232518 | Rel-17 CR TS 28.312 Correction to Context and Expectation object definitions | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑232565 | |||
S5‑232558 | Rel-17 CR TS 28.312 Correction to Context and Expectation object definitions | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑232565 | Rel-17 CR TS 28.312 Correction to Context and Expectation object definitions Title | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑233079 | S5‑232518 | ||
S5‑233079 | Rel-17 CR TS 28.312 Correction to Context and Expectation object definitions Title | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑232565 | |||
6.3.7 | SON | S5‑232274 | Rel-17 CR TS 28.313 Align the attribute name of SON case with TS 28.541 | Huawei | CR | Approval | Yes |
Yes
| agreed | No | ||
S5‑232275 | Rel-16 CR TS 28.313 Align the attribute name of SON case with TS 28.541 | Huawei | CR | Approval | Yes |
Yes
| agreed | No | ||||
6.3.8 | QMC |   | ||||||||||
6.3.9 | Network slicing management | S5‑232062 | DP on TS 28.541 NSI-NSSI state diagrams | Huawei | discussion | Endorsement | Yes |
Yes
| noted | No | ||
S5‑232107 | Discussion paper on Add missing SLS attributes supported in serviceProfile to sliceProfile | Nokia, Nokia Shanghai Bell, KDDI | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑232108 | Add missing SLS attributes supported in serviceProfile to sliceProfile | Nokia, Nokia Shanghai Bell, KDDI | CR | Approval | Yes |
Yes
| revised | No | S5‑233080 | |||
S5‑233080 | Add missing SLS attributes supported in serviceProfile to sliceProfile | Nokia, Nokia Shanghai Bell, KDDI, Huawei | CR | Approval | Yes |
Yes
| not pursued | No | S5‑232108 | |||
S5‑232109 | Add missing SLS attributes supported in serviceProfile to sliceProfile | Nokia, Nokia Shanghai Bell, KDDI | CR | Approval | Yes |
Yes
| revised | No | S5‑233081 | |||
S5‑233081 | Add missing SLS attributes supported in serviceProfile to sliceProfile | Nokia, Nokia Shanghai Bell, KDDI, Huawei | CR | Approval | Yes |
Yes
| not pursued | No | S5‑232109 | |||
S5‑232110 | Fix missing reference to mid-haul interface for EP Transport | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑232111 | Fix missing reference to mid-haul interface for EP Transport | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑232112 | Fix duplicated SST attribute in RANSliceSubnetProfile | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑232113 | Fix duplicated SST attribute in RANSliceSubnetProfile | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑232139 | Removal of redundant network slice modification use case | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑232175 | Correct issues for feasibility check and resource reservation NRM fragment | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑233084 | |||
S5‑233084 | Correct issues for feasibility check and resource reservation NRM fragment | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑232175 | |||
S5‑232176 | Correct issues for feasibility check and resource reservation NRM fragment | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑233085 | |||
S5‑233085 | Correct issues for feasibility check and resource reservation NRM fragment | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑232176 | |||
S5‑232358 | Rel-17 CR 28.541 Clarify use of V2X in service profile | Ericsson LM, Deutsche Telekom | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑232363 | Rel-18 CR 28.541 Clarify use of V2X in service profile | Ericsson LM, Deutsche Telekom | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑232373 | Clarify network slicing provisioning use case | Ericsson | CR | Approval | Yes |
Yes
| revised | No | S5‑233086 | |||
S5‑233086 | Clarify network slicing provisioning use case | Ericsson | CR | Approval | Yes |
Yes
| not pursued | No | S5‑232373 | |||
S5‑232374 | Clarify network slicing provisioning use case | Ericsson | CR | Approval | Yes |
Yes
| revised | No | S5‑233087 | |||
S5‑233087 | Clarify network slicing provisioning use case | Ericsson | CR | Approval | Yes |
Yes
| not pursued | No | S5‑232374 | |||
S5‑232375 | Clarify network slicing provisioning use case | Ericsson | CR | Approval | Yes |
Yes
| revised | No | S5‑233088 | |||
S5‑233088 | Clarify network slicing provisioning use case | Ericsson | CR | Approval | Yes |
Yes
| not pursued | No | S5‑232375 | |||
S5‑232377 | Clarify network slicing provisioning use case | Ericsson | CR | Approval | Yes |
Yes
| revised | No | S5‑233089 | |||
S5‑233089 | Clarify network slicing provisioning use case | Ericsson | CR | Approval | Yes |
Yes
| not pursued | No | S5‑232377 | |||
S5‑232381 | Rel-16 CR 28.530 Correct network slice abbrevations | Ericsson LM | CR | Approval | Yes |
Yes
| revised | No | S5‑233090 | |||
S5‑233090 | Rel-16 CR 28.530 Correct network slice abbrevations | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | S5‑232381 | |||
S5‑232383 | Rel-17 CR 28.530 Correct network slice abbrevations | Ericsson LM | CR | Approval | Yes |
Yes
| revised | No | S5‑233091 | |||
S5‑233091 | Rel-17 CR 28.530 Correct network slice abbrevations | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | S5‑232383 | |||
S5‑232442 | Rel-17 CR 28.531 OpenAPI SS for 28.531 | Samsung R&D Institute UK | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑232443 | Rel-18 CR 28.531 OpenAPI SS for 28.531 | Samsung R&D Institute UK | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑232717 | DP on relationship between NEST, URSP and ServiceProfile | TELEFONICA S.A. | discussion | Approval | Yes |
Yes
| revised | No | S5‑233092 | |||
S5‑233092 | DP on relationship between NEST, URSP and ServiceProfile | TELEFONICA S.A. | discussion | Endorsement | Yes |
Yes
| endorsed | No | S5‑232717 | |||
6.3.10 | MEC management |   | ||||||||||
6.3.11 | General NRM | S5‑232129 | TS28.623 Rel-16 Fix IpAddr stage 3 definition | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑233093 | |
S5‑233093 | TS28.623 Rel-16 Fix IpAddr stage 3 definition | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑232129 | |||
S5‑232130 | TS28.623 Rel-17 Fix IpAddr stage 3 definition | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑232461 | |||
S5‑232131 | TS28.623 Rel-18 Fix IpAddr stage 3 definition | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑233095 | |||
S5‑233095 | TS28.623 Rel-18 Fix IpAddr stage 3 definition | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑232131 | |||
S5‑232132 | TS28.622 Rel-17 Fix diagram issue in MnS Registry NRM fragment | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| merged | No | S5‑233096 | |||
S5‑232133 | TS28.622 Rel-18 Fix diagram issue in MnS Registry NRM fragment | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| merged | No | S5‑233097 | |||
S5‑232177 | Correct issues for generic NRM Fragment | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑233096 | |||
S5‑233096 | Correct issues for generic NRM Fragment | Huawei,Nokia | CR | Agreement | Yes |
Yes
| agreed | No | S5‑232177 | |||
S5‑232178 | Correct issues for generic NRM Fragment | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑233097 | |||
S5‑233097 | Correct issues for generic NRM Fragment | Huawei,Nokia | CR | Agreement | Yes |
Yes
| agreed | No | S5‑232178 | |||
S5‑232189 | Correction of RFC reference | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑232190 | Correction of RFC reference | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑232191 | Rel-15 CR TS 28.541 Clarify mount information | Ericsson India Private Limited | CR | Agreement | Yes |
Yes
| revised | No | S5‑233098 | |||
S5‑233098 | Rel-15 CR TS 28.541 Clarify mount information | Ericsson India Private Limited | CR | Agreement | Yes |
Yes
| agreed | No | S5‑232191 | |||
S5‑232192 | Rel-16 CR TS 28.541 Clarify mount information | Ericsson India Private Limited | CR | Agreement | Yes |
Yes
| revised | No | S5‑233099 | |||
S5‑233099 | Rel-16 CR TS 28.541 Clarify mount information | Ericsson India Private Limited | CR | Agreement | Yes |
Yes
| agreed | No | S5‑232192 | |||
S5‑232193 | Rel-17 CR TS 28.541 Clarify mount information | Ericsson India Private Limited | CR | Agreement | Yes |
Yes
| revised | No | S5‑233100 | |||
S5‑233100 | Rel-17 CR TS 28.541 Clarify mount information | Ericsson India Private Limited | CR | Agreement | Yes |
Yes
| agreed | No | S5‑232193 | |||
S5‑232194 | Rel-18 CR TS 28.541 Clarify mount information | Ericsson India Private Limited | CR | Agreement | Yes |
Yes
| revised | No | S5‑233101 | |||
S5‑233101 | Rel-18 CR TS 28.541 Clarify mount information | Ericsson India Private Limited | CR | Agreement | Yes |
Yes
| agreed | No | S5‑232194 | |||
S5‑232196 | Missing Mount information | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑232197 | Missing Mount information | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑232198 | Missing Mount information | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑232199 | Missing Mount information | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑232237 | TS28.312 Rel-17 update stage 3 definition PlmnId | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑232463 | |||
S5‑232238 | TS28.538 Rel-17 update stage 3 definition PlmnId | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑232239 | TS28.538 Rel-18 update stage 3 definition PlmnId | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑232265 | R17 CR TS 28.541 Update attributes in ANR to support “Resource Coordination Only” in NCRT | China Telecom Corporation Ltd., Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑233102 | |||
S5‑233102 | R17 CR TS 28.541 Update attributes in ANR to support “Resource Coordination Only” in NCRT | China Telecom Corporation Ltd., Huawei | CR | Agreement | No |
Yes
| not pursued | No | S5‑232265 | |||
S5‑232266 | R18 CR TS 28.541 Update attributes in ANR to support “Resource Coordination Only” in NCRT | China Telecom Corporation Ltd. | CR | Agreement | Yes |
Yes
| revised | No | S5‑233103 | |||
S5‑233103 | R18 CR TS 28.541 Update attributes in ANR to support “Resource Coordination Only” in NCRT | China Telecom Corporation Ltd. | CR | Agreement | No |
Yes
| not pursued | No | S5‑232266 | |||
S5‑232386 | Rel-17 CR 28.622 Remove unused create link subscription attribute definition. | Ericsson LM | CR | Approval | Yes |
Yes
| revised | No | S5‑233104 | |||
S5‑233104 | Rel-17 CR 28.622 Remove unused create link subscription attribute definition. | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | S5‑232386 | |||
S5‑232387 | Rel-18 CR 28.622 Remove unused create link subscription attribute definition. | Ericsson LM | CR | Approval | Yes |
Yes
| revised | No | S5‑233105 | |||
S5‑233105 | Rel-18 CR 28.622 Remove unused create link subscription attribute definition. | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | S5‑232387 | |||
S5‑232405 | TS28.312 Rel-17 update stage 3 definition PlmnId | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑232445 | Rel-17 CR 28.541 fixing coverageArea | Samsung R&D Institute UK | CR | Agreement | Yes |
Yes
| revised | No | S5‑233106 | |||
S5‑233106 | Rel-17 CR 28.541 fixing coverageArea | Samsung R&D Institute UK | CR | Agreement | Yes |
Yes
| revised | No | S5‑233149 | S5‑232445 | ||
S5‑233149 | Rel-17 CR 28.541 fixing coverageArea | Samsung R&D Institute UK | CR | Agreement | Yes |
Yes
| agreed | No | S5‑233106 | |||
S5‑232447 | Rel-18 CR 28.541 fixing coverageArea | Samsung R&D Institute UK | CR | Agreement | Yes |
Yes
| revised | No | S5‑233107 | |||
S5‑233107 | Rel-18 CR 28.541 fixing coverageArea | Samsung R&D Institute UK | CR | Agreement | Yes |
Yes
| revised | No | S5‑233150 | S5‑232447 | ||
S5‑233150 | Rel-18 CR 28.541 fixing coverageArea | Samsung R&D Institute UK | CR | Agreement | Yes |
Yes
| agreed | No | S5‑233107 | |||
S5‑232461 | TS28.623 Rel-17 Fix IpAddr stage 3 definition | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑233094 | S5‑232130 | ||
S5‑233094 | TS28.623 Rel-17 Fix IpAddr stage 3 definition | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑232461 | |||
S5‑232463 | TS28.312 Rel-17 update stage 3 definition PlmnId | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑232237 | |||
S5‑232719 | YANG Corrections | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| agreed | No | ||||
6.3.12 | PM/KPI | S5‑232070 | Modify the counter name for Total error number of DL/UL TBs | RadiSys | CR | Yes |
Yes
| agreed | No | |||
S5‑232074 | Modify the criteria for incrementing counters of Intra-GNB Handover Preparation | RadiSys | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑232388 | Clarify reporting and monitoring period usage in SupportedPerfMetricGroup datatype. | Ericsson | CR | Approval | Yes |
Yes
| revised | No | S5‑233109 | |||
S5‑233109 | Clarify reporting and monitoring period usage in SupportedPerfMetricGroup datatype. | Ericsson | CR | Approval | Yes |
Yes
| agreed | No | S5‑232388 | |||
S5‑232389 | Clarify reporting and monitoring period usage in SupportedPerfMetricGroup datatype. | Ericsson | CR | Approval | Yes |
Yes
| revised | No | S5‑233110 | |||
S5‑233110 | Clarify reporting and monitoring period usage in SupportedPerfMetricGroup datatype. | Ericsson | CR | Approval | Yes |
Yes
| agreed | No | S5‑232389 | |||
S5‑232390 | Clarify reporting and monitoring period usage in SupportedPerfMetricGroup datatype. | Ericsson | CR | Approval | Yes |
Yes
| revised | No | S5‑233111 | |||
S5‑233111 | Clarify reporting and monitoring period usage in SupportedPerfMetricGroup datatype. | Ericsson | CR | Approval | Yes |
Yes
| agreed | No | S5‑232390 | |||
S5‑232392 | Clarify reporting and monitoring period usage in SupportedPerfMetricGroup datatype (stage3) | Ericsson | CR | Approval | Yes |
Yes
| revised | No | S5‑233112 | |||
S5‑233112 | Clarify reporting and monitoring period usage in SupportedPerfMetricGroup datatype (stage3) | Ericsson | CR | Approval | Yes |
Yes
| agreed | No | S5‑232392 | |||
S5‑232393 | Rel-17 CR 28.623 Clarify reporting and monitoring period usage in SupportedPerfMetricGroup datatype (stage3) | Ericsson LM | CR | Approval | Yes |
Yes
| revised | No | S5‑233113 | |||
S5‑233113 | Rel-17 CR 28.623 Clarify reporting and monitoring period usage in SupportedPerfMetricGroup datatype (stage3) | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | S5‑232393 | |||
S5‑232394 | Rel-18 CR 28.623 Clarify reporting and monitoring period usage in SupportedPerfMetricGroup datatype (stage3) | Ericsson LM | CR | Approval | Yes |
Yes
| revised | No | S5‑233114 | |||
S5‑233114 | Rel-18 CR 28.623 Clarify reporting and monitoring period usage in SupportedPerfMetricGroup datatype (stage3) | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | S5‑232394 | |||
S5‑232436 | Rel18 CR for TS28.552 editorial correction | NTT DOCOMO INC. | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑232568 | Correction of integrity KPIs | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑232569 | Correction of integrity KPIs | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑232570 | Correction of integrity KPIs | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑232571 | Correction of integrity KPIs | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑232632 | Rel-17 CR for TS28.552 Correct conditions of Number of UEs configured with conditional handover | ZTE Corporation | CR | Approval | Yes |
Yes
| revised | No | S5‑233115 | |||
S5‑233115 | Rel-17 CR for TS28.552 Correct conditions of Number of UEs configured with conditional handover | ZTE Corporation | CR | Approval | Yes |
Yes
| agreed | No | S5‑232632 | |||
S5‑232634 | Rel-18 CR for TS28.552 Correct conditions of Number of UEs configured with conditional handover | ZTE Corporation | CR | Approval | Yes |
Yes
| revised | No | S5‑233116 | |||
S5‑233116 | Rel-18 CR for TS28.552 Correct conditions of Number of UEs configured with conditional handover | ZTE Corporation | CR | Approval | Yes |
Yes
| agreed | No | S5‑232634 | |||
S5‑232635 | Rel-18 CR for TS28.552 Correct Mean and Max Time of requested conditional handover executions | ZTE Corporation | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑232636 | Rel-18 CR for TS28.552 Correct Mean and Max Time of requested legacy handover executions | ZTE Corporation | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑232639 | Rel-18 CR for TS28.552 editorial Corrections | ZTE Corporation | CR | Approval | Yes |
Yes
| agreed | No | ||||
6.3.13 | Trace/MDT | S5‑232136 | Correcting traceRecordingSessionReference property | Ericsson Limited | CR | Approval | Yes |
Yes
| revised | No | S5‑233134 | |
S5‑233134 | Correcting traceRecordingSessionReference property | Ericsson Limited | CR | Approval | Yes |
Yes
| agreed | No | S5‑232136 | |||
S5‑232137 | Correcting traceRecordingSessionReference property. Aligning with 32.422. | Ericsson | CR | Approval | Yes |
Yes
| revised | No | S5‑233135 | |||
S5‑233135 | Correcting traceRecordingSessionReference property. Aligning with 32.422. | Ericsson | CR | Approval | Yes |
Yes
| agreed | No | S5‑232137 | |||
S5‑232138 | Correcting traceRecordingSessionReference property. Aligning with 32.422. | Ericsson | CR | Approval | Yes |
Yes
| revised | No | S5‑233136 | |||
S5‑233136 | Correcting traceRecordingSessionReference property. Aligning with 32.422. | Ericsson | CR | Approval | Yes |
Yes
| agreed | No | S5‑232138 | |||
S5‑232160 | Rel-16 CR TS 28.622 Correcting attribute constraints for Trace Job | Nokia, Nokia Shangai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑232165 | Rel-17 CR TS 28.622 Correcting attribute constraints for Trace Job | Nokia, Nokia Shangai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑232166 | Rel-17 CR TS 28.622 Correcting the attribute properties for Excess packet delay threshold attribute | Nokia, Nokia Shangai Bell | CR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑232168 | Rel-17 CR TS 28.623 Correcting the min and max Items possible for fiveQIValue attribute in Stage 3 | Nokia, Nokia Shangai Bell | CR | Approval | Yes |
Yes
| endorsed | No | ||||
S5‑232169 | Rel17 CR 32.422 Correcting the definition for Excess packet delay threshold | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑232173 | Rel-18 CR TS 28.622 Correcting attribute constraints for Trace Job | Nokia, Nokia Shangai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑232212 | Rel-16 CR 28.623 Correcting traceRecordingSessionReference property (stage3) | Ericsson LM | CR | Approval | Yes |
Yes
| revised | No | S5‑233139 | |||
S5‑233139 | Rel-16 CR 28.623 Correcting traceRecordingSessionReference property (stage3) | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | S5‑232212 | |||
S5‑232213 | Rel-17 CR 28.623 Correcting traceRecordingSessionReference property (stage3) | Ericsson LM | CR | Approval | Yes |
Yes
| revised | No | S5‑233140 | |||
S5‑233140 | Rel-17 CR 28.623 Correcting traceRecordingSessionReference property (stage3) | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | S5‑232213 | |||
S5‑232214 | Rel-18 CR 28.623 Correcting traceRecordingSessionReference property (stage3) | Ericsson LM | CR | Approval | Yes |
Yes
| revised | No | S5‑233141 | |||
S5‑233141 | Rel-18 CR 28.623 Correcting traceRecordingSessionReference property (stage3) | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | S5‑232214 | |||
S5‑232312 | Rel-17 CR TS 32.422 Correcting the attribute properties for Excess packet delay threshold attribute | Nokia, Nokia Shangai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑232313 | Rel-17 CR TS 28.622 Correcting the attribute properties for Excess packet delay threshold attribute | Nokia, Nokia Shangai Bell | CR | Approval | Yes |
Yes
| endorsed | No | ||||
S5‑232376 | Correct Trace IOC attribute names (stage3, yang) | Ericsson | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑232378 | Rel-17 CR 28.623 Correct Trace IOC attribute names (stage3, yang) | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑232379 | Rel-18 CR 28.623 Correct Trace IOC attribute names (stage3, yang) | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑232384 | Rel-16 CR 32.422 Clarify behaviour when cell list is undefined | Ericsson LM | CR | Approval | Yes |
Yes
| revised | No | S5‑233117 | |||
S5‑233117 | Rel-16 CR 32.422 Clarify behaviour when cell list is undefined | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | S5‑232384 | |||
S5‑232385 | Rel-17 CR 32.422 Clarify behaviour when cell list is undefined | Ericsson LM | CR | Approval | Yes |
Yes
| revised | No | S5‑233118 | |||
S5‑233118 | Rel-17 CR 32.422 Clarify behaviour when cell list is undefined | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | S5‑232385 | |||
S5‑232398 | Rel-16 CR 32.423 Align trace record formats for different reporting methods | Ericsson LM | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑232399 | Rel-17 CR 32.423 Align trace record formats for different reporting methods | Ericsson LM | CR | Approval | Yes |
Yes
| not pursued | No | ||||
6.3.14 | Other | S5‑232123 | TS28.541 Rel-16 remove redundant stage 3 definition for Mnc and PlmnId | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||
S5‑232124 | TS28.541 Rel-17 remove redundant stage 3 definition for Mnc and PlmnId | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑232125 | TS28.541 Rel-18 remove redundant stage 3 definition for Mnc and PlmnId | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑232457 | |||
S5‑232126 | TS28.541 Rel-16 Fix IpAddr definition and references | Nokia, Nokia Shanghai Bell | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑232127 | TS28.541 Rel-17 Fix IpAddr definition and references | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑232460 | |||
S5‑232128 | Fix IpAddr definition and references | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑233119 | |||
S5‑233119 | Fix IpAddr definition and references | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑232128 | |||
S5‑232179 | Add missing supporting management capabilities for several control NRM Fragments | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑232180 | Add missing supporting management capabilities for several control NRM Fragments | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑232184 | Rel-17 CR TS 28.537 Correct the description and requirements for producing and reporting management data (6.3.14) | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑233120 | |||
S5‑233120 | Rel-17 CR TS 28.537 Correct the description and requirements for producing and reporting management data (6.3.14) | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑232184 | |||
S5‑232319 | Rel-16 CR 32.158 Clarify URI concept | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑233121 | |||
S5‑233121 | Rel-16 CR 32.158 Clarify URI concept | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑232319 | |||
S5‑232320 | Rel-17 CR 32.158 Clarify URI concept | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑233122 | |||
S5‑233122 | Rel-17 CR 32.158 Clarify URI concept | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑232320 | |||
S5‑232321 | Rel-16 CR 32.158 Correct media type of 3GPP JSON Patch and 3GPP JSON Merge Patch | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑232322 | Rel-17 CR 32.158 Correct media type of 3GPP JSON Patch and 3GPP JSON Merge Patch | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑232324 | Rel-16 CR 32.158 Align and clarify definitions for the “Accept” header | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑232325 | Rel-17 CR 32.158 Align and clarify definitions for the “Accept” header | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑232326 | Rel-16 CR 32.158 Clarify an object must exist when adding members with JSON Patch | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑233123 | |||
S5‑233123 | Rel-16 CR 32.158 Clarify an object must exist when adding members with JSON Patch | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑232326 | |||
S5‑232327 | Rel-17 CR 32.158 Clarify an object must exist when adding members with JSON Patch | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑233124 | |||
S5‑233124 | Rel-17 CR 32.158 Clarify an object must exist when adding members with JSON Patch | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑232327 | |||
S5‑232328 | Rel-16 CR 32.158 Correct objectInstance values in examples | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑232329 | Rel-17 CR 32.158 Correct objectInstance values in examples | Nokia, Nokia Shnaghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑232330 | Rel-16 CR 32.158 Remove HTTP GET response examples not used in TS 28.532 | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑232331 | Rel-17 CR 32.158 Remove HTTP GET response examples not used in TS 28.532 | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑232332 | Rel-16 CR 32.158 Add missing JSON schema fragment for the JSON Patch document | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑232333 | Rel-17 CR 32.158 Add missing JSON schema fragment for the JSON Patch document | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑232334 | Rel-16 CR 32.158 Correct format of MnS versions in examples | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑232335 | Rel-17 CR 32.158 Correct format of MnS versions in examples | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑232336 | Rel-16 CR 32.158 Correct attribute value null | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑232337 | Rel-17 CR 32.158 Correct attribute value null | Nokia, Nokia Shanghai Bell | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑232338 | Rel-16 CR 32.158 Clarify the JSON Merge Patch document is a partial resource representation | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑232339 | Rel-17 CR 32.158 Clarify the JSON Merge Patch document is a partial resource representation | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑232340 | Rel-16 CR 28.532 Align media type names with TS 32.158 | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑232341 | Rel-17 CR 28.532 Align media type names with TS 32.158 | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑232342 | Rel-16 CR 28.532 Add examples for notifyMOICreation, notifyMOIDeletion and notifyAttributeValueChanges | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑232954 | |||
S5‑232954 | Rel-16 CR 28.532 Add examples for notifyMOICreation, notifyMOIDeletion and notifyAttributeValueChanges | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑232342 | |||
S5‑232343 | Rel-17 CR 28.532 Add examples for notifyMOICreation, notifyMOIDeletion and notifyAttributeValueChanges | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑232955 | |||
S5‑232955 | Rel-17 CR 28.532 Add examples for notifyMOICreation, notifyMOIDeletion and notifyAttributeValueChanges | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑232343 | |||
S5‑232344 | Rel-17 CR 28.532 Clarify definitions related to attributes | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑233125 | |||
S5‑233125 | Rel-17 CR 28.532 Clarify definitions related to attributes | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑232344 | |||
S5‑232450 | Rel-17 CR 28.536 adding missing assuranceScope in AssuranceGoal | Samsung R&D Institute UK | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑232457 | remove redundant stage 3 definition for Mnc and PlmnId | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑232125 | |||
S5‑232460 | TS28.541 Rel-17 Fix IpAddr definition and references | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑232127 | |||
S5‑232464 | Correct the Management Data Analytics Capability Description | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑232985 | |||
S5‑232985 | Correct the Management Data Analytics Capability Description | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑232464 | |||
S5‑232465 | Correct the Management Data Analytics Capability Description | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑232986 | |||
S5‑232986 | Correct the Management Data Analytics Capability Description | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑232465 | |||
S5‑232466 | Correct the Management Data Analytics Capability Description | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑232987 | |||
S5‑232987 | Correct the Management Data Analytics Capability Description | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑232466 | |||
S5‑232467 | Updates for generic management services | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑232468 | Updates for generic management services | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑232469 | Updates for generic management services | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑232512 | Rel-17 CR 32.158 Correct attribute value null | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑232547 | Update lifecycle phase description of closed control loop | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑232548 | Update coordination between closed control loops | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑232679 | Rel-17 CR for TS28.535 delete redundant monitoring content of the management system | ZTE Corporation | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑232680 | Rel-17 CR for TS32.130 correct the wrong figure number | ZTE Corporation | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑232681 | Rel-17 CR for TS28.557 Correct wrong abbreviation for Data Centre Service Provider | ZTE Corporation | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑232684 | Correct YANG for ReportingCtrl | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑232697 | Correction of reference list | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑232698 | Correction of reference list | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑232699 | Correction of reference list | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑232702 | Rel-11 CR TS 28.622 Correction of attribute dnPrefix | Ericsson India Private Limited | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑232703 | Correction of attribute dnPrefix | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑232704 | Correction of attribute dnPrefix | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑232705 | Correction of attribute dnPrefix | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑232706 | Correction of attribute dnPrefix | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑232708 | Correction of attribute dnPrefix | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑232709 | Correction of attribute dnPrefix | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑232710 | Correction of attribute dnPrefix | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑233132 | |||
S5‑233132 | Correction of attribute dnPrefix | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑232710 | |||
S5‑232713 | Correction of attribute availableRANqoEMetrics properties | 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‑232144 | pCR TS 28.317 Add concept, use case and requirements for network configuration data handling | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑232905 | |
S5‑232905 | pCR TS 28.317 Add concept, use case and requirements for network configuration data handling | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| noted | No | S5‑232144 | |||
S5‑232145 | pCR TS 28.317 Update the requirement format to follow the stage1 templated in TS 32.160 | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑232906 | Draft TS 28.317 | China Mobile | draft TS | Approval | No |
Yes
| email approval | No | ||||
6.4.1.2 | RANSC_WoP#2 |   | ||||||||||
6.4.1.3 | RANSC_WoP#3 |   | ||||||||||
6.4.2 | Management Data Analytics phase 2 |   | ||||||||||
6.4.2.1 | eMDAS_Ph2_WoP#1 | S5‑232357 | Input to Draft CR Rel-18 28.104 Add recommended actions for non-3GPP operations | Intel, NEC | other | Agreement | Yes |
Yes
| noted | No | ||
S5‑232755 | Input to Draft CR Rel-18 28.104 Add recommended actions for non-3GPP operations | Intel, NEC | other | Agreement | No |
Yes
| withdrawn | Yes | ||||
S5‑233174 | Draft CR eMDAS_Ph2 – TS28.104; Further enhancements into the Management Data Analytics (Phase 2). | NEC | draftCR | Approval | No |
Yes
| email approval | No | ||||
6.4.2.2 | eMDAS_Ph2_WoP#2 | S5‑232148 | Input to draft CR TS 28.104 Stage 2 and Stage 3 for Predictions use case | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| noted | No | ||
S5‑232149 | Input to draft CR TS 28.104 Stage 2 and Stage 3 for Statistics use case | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| revised | No | S5‑232982 | |||
S5‑232982 | Input to draft CR TS 28.104 Stage 2 and Stage 3 for Statistics use case | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| noted | No | S5‑232149 | |||
S5‑232296 | Input to draft CR 28.104 Improve description of prediction and statistics of management data | Huawei | other | Approval | Yes |
Yes
| revised | No | S5‑232983 | |||
S5‑232983 | Input to draft CR 28.104 Improve description of prediction and statistics of management data | Huawei | other | Approval | Yes |
Yes
| approved | No | S5‑232296 | |||
6.4.2.3 | eMDAS_Ph2_WoP#3 | S5‑232291 | Add coordination requirement and domain MDAF reporting | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||
S5‑232984 | Input to draft CR Add coordination requirement and domain MDAF reporting | Huawei | other | Agreement | Yes |
Yes
| approved | No | ||||
S5‑232292 | Improve definition of network slice traffic prediction | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑232293 | Improve requirements for network slice throughput analysis | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑232989 | Input to draft CR Improve requirements for network slice throughput analysis | Huawei | other | Agreement | Yes |
Yes
| approved | No | ||||
S5‑232294 | Improve requirements for network slice traffic prediction | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑232988 | Input to draft CR Improve requirements for network slice traffic prediction | Huawei | other | Agreement | Yes |
Yes
| noted | No | ||||
S5‑232295 | Add coodination requirement for user experience case | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑232990 | Input to draft CR Add coodination requirement for user experience case | Huawei | other | Agreement | Yes |
Yes
| approved | No | ||||
6.4.2.4 | eMDAS_Ph2_WoP#4 |   | ||||||||||
6.4.2.5 | eMDAS_Ph2_WoP#5 | S5‑232449 | Rel-18 CR 28.104 MDAS COSLA interworking | Samsung R&D Institute UK | CR | Agreement | Yes |
Yes
| not pursued | No | ||
S5‑232992 | Rel-18 CR 28.104 MDAS COSLA interworking | Samsung R&D Institute UK | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
6.4.2.6 | eMDAS_Ph2_WoP#6 | S5‑232396 | Rel-18 CR 28.552 Revise the PNF Energy consumption measurement | Intel Belgium SA/NV | CR | Approval | Yes |
Yes
| not pursued | No | ||
S5‑232993 | Rel-18 CR 28.552 Revise the PNF Energy consumption measurement | Intel Belgium SA/NV | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑232714 | Input to draft CR Rel-18 28.104 Revise energy saving analysis use case | Intel Belgium SA/NV | other | Approval | Yes |
Yes
| revised | No | S5‑232994 | |||
S5‑232994 | Input to draft CR Rel-18 28.104 Revise energy saving analysis use case | Intel Belgium SA/NV | other | Approval | Yes |
Yes
| noted | No | S5‑232714 | |||
6.4.2.7 | eMDAS_Ph2_WoP#7 | S5‑232355 | Input to Draft CR Rel-18 28.104 Add MDA capability for resource utilization analysis | Intel, NEC | other | Agreement | Yes |
Yes
| revised | No | S5‑232995 | |
S5‑232995 | Input to Draft CR Rel-18 28.104 Add MDA capability for resource utilization analysis | Intel, NEC | other | Agreement | Yes |
Yes
| noted | No | S5‑232355 | |||
6.5 | Management Architecture and Mechanisms |   | ||||||||||
6.5.1 | Network slicing provisioning rules |   | ||||||||||
6.5.1.1 | NSRULE_WoP#1 | S5‑232354 | Rel-18 CR 28.541 Add network slice selection information | Ericsson LM | CR | Approval | Yes |
Yes
| not pursued | No | ||
S5‑233056 | Rel-18 CR 28.541 Add network slice selection information | Ericsson LM | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑232415 | Proposed way forward for NSRULE isolation topic | Huawei, Telefónica | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑233058 | |||
S5‑233058 | Proposed way forward for NSRULE isolation topic | Huawei, Telefónica | discussion | Endorsement | Yes |
Yes
| endorsed | No | S5‑232415 | |||
S5‑232416 | Revised Rel-18 WID on network slicing provisioning rules | Huawei | WID revised | Approval | Yes |
Yes
| noted | No | ||||
6.5.1.2 | NSRULE_WoP#2 | S5‑232114 | Add NRM for network slice isolation | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | ||
S5‑233057 | Add NRM for network slice isolation | Nokia, Nokia Shanghai Bell | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
6.5.2 | Additional NRM features phase 2 |   | ||||||||||
6.5.2.1 | AdNRM_ph2_WoP#1 | S5‑232418 | DP on TS structure proposal for generic NRM Fragment | Huawei | discussion | Endorsement | Yes |
Yes
| noted | No | S5‑231015 | |
6.5.2.2 | AdNRM_ph2_WoP#2 |   | ||||||||||
6.5.2.3 | AdNRM_ph2_WoP#3 | S5‑232086 | Fix vague issues in EP_Transport with Federated network modelling | Nokia, Nokia Shanghai Bell, KDDI, Juniper, TELUS, Telefonica | CR | Approval | Yes |
Yes
| revised | No | S5‑232907 | S5‑226755 |
S5‑232907 | Fix vague issues in EP_Transport with Federated network modelling | Nokia, Nokia Shanghai Bell, KDDI, Juniper, TELUS, Telefonica,Huawei,Verizon | CR | Approval | Yes |
Yes
| not pursued | No | S5‑232086 | |||
S5‑232117 | NRM enhancements for SMSFFunction | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑232908 | |||
S5‑232908 | NRM enhancements for SMSFFunction | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑232117 | |||
S5‑232118 | NRM enhancements for NRFFunction | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑232909 | |||
S5‑232909 | NRM enhancements for NRFFunction | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑232118 | |||
S5‑232119 | NRM enhancements for LMFFunction | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑232910 | |||
S5‑232910 | NRM enhancements for LMFFunction | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑232119 | |||
S5‑232134 | TS28.541 Rel-17 ManagedNFProfile stage3 not consistent with Stage 2 | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑232135 | TS28.541 Rel-18 ManagedNFProfile stage3 not consistent with Stage 2 | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑232185 | Rel-18 CR TS 28.541 Add Enhanced QoS support in NRM (stage 3, YAML) | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑232911 | |||
S5‑232911 | Rel-18 CR TS 28.541 Add Enhanced QoS support in NRM (stage 3, YAML) | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑232185 | |||
S5‑232186 | Update NRM fragment for 5QI configuration for NG-RAN | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑232912 | |||
S5‑232912 | Update NRM fragment for 5QI configuration for NG-RAN | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑232186 | |||
S5‑232187 | Rel-18 CR TS 28.541 Correct the description and definition fro NWDAFFucntion IOC | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑232914 | |||
S5‑232914 | Rel-18 CR TS 28.541 Correct the description and definition fro NWDAFFucntion IOC | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑232187 | |||
S5‑232264 | Correct the RRMPolicyRatio Description | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑232391 | Add Annex recommending QoS model usage | Ericsson | CR | Approval | Yes |
Yes
| revised | No | S5‑232913 | |||
S5‑232913 | Add Annex recommending QoS model usage | Ericsson | CR | Approval | Yes |
Yes
| agreed | No | S5‑232391 | |||
6.5.2.4 | AdNRM_ph2_WoP#4 | S5‑232120 | NRM enhancements for AFFunction | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑232915 | |
S5‑232915 | NRM enhancements for AFFunction | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑232120 | |||
S5‑232121 | TS28.541 Rel-18 NRM enhancements for EASDFFunction | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑232122 | TS28.541 Rel-18 NRM enhancements for NSSAAFFunction | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑232916 | |||
S5‑232916 | TS28.541 Rel-18 NRM enhancements for NSSAAFFunction | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑232122 | |||
6.5.3 | Enhanced Edge Computing Management |   | ||||||||||
6.5.3.1 | eECM_WoP#1 | S5‑233154 | Rel-18 CR 28.538 Add stage 3 solution for LcmProcess IOC | Intel Corporation (UK) Ltd | draftCR | Approval | Yes |
Yes
| noted | No | ||
S5‑232073 | Rel-18 CR 28.538 Add stage 3 solution for request identifier attributes | Intel Corporation (UK) Ltd | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑233016 | Rel-18 CR 28.538 Add stage 3 solution for request identifier attributes | Intel Corporation (UK) Ltd | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑232223 | Rel-18 CR 28.622 Add stage 2 solution for LcmProcess IOC | Intel Belgium SA/NV | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑233017 | Rel-18 CR 28.538 Add stage 2 solution for LcmProcess IOC | Intel Belgium SA/NV | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑233153 | Rel-18 CR 28.538 Add stage 2 solution for LcmProcess IOC | Intel Belgium SA/NV | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑232224 | Rel-18 CR 28.538 Add stage 2 solution for request identifier attributes | Intel Belgium SA/NV | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑233015 | Rel-18 CR 28.538 Add stage 2 solution for request identifier attributes | Intel Belgium SA/NV | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑232228 | Rel-18 CR 28.538 Revise EAS VNF instantiation and termination procedures | Intel Belgium SA/NV | CR | Approval | Yes |
Yes
| revised | No | S5‑233014 | |||
S5‑233014 | Rel-18 CR 28.538 Revise EAS VNF instantiation and termination procedures | Intel Belgium SA/NV | CR | Approval | Yes |
Yes
| not pursued | No | S5‑232228 | |||
S5‑233152 | Draft CR 28.538 Revise EAS VNF instantiation and termination procedures | Intel Belgium SA/NV | draftCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑232448 | Rel-18 CR 28.538 eECM | Samsung R&D Institute UK | CR | Agreement | Yes |
Yes
| revised | No | S5‑233019 | |||
S5‑233019 | Rel-18 CR 28.538 eECM | Samsung R&D Institute UK | CR | Agreement | Yes |
Yes
| agreed | No | S5‑232448 | |||
6.5.3.2 | eECM_WoP#2 |   | ||||||||||
6.5.3.3 | eECM_WoP#3 |   | ||||||||||
6.5.4 | Enhancement of QoE Measurement Collection |   | ||||||||||
6.5.4.1 | eQoE_WoP#1 | S5‑232188 | TS28.622 add missing UML diagram for QoE Measurement Collection | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑232996 | |
S5‑232996 | TS28.622 add missing UML diagram for QoE Measurement Collection | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑232188 | |||
6.5.4.2 | eQoE_WoP#2 | S5‑232115 | Add MDT Alignment Information and RAN visible QoE Metrics to Signalling Based Activation | Ericsson Limited | CR | Approval | Yes |
Yes
| agreed | No | ||
S5‑232116 | LS on Approval of eQoE CRs for NR | Ericsson Limited | LS out | Yes |
Yes
| revised | No | S5‑232997 | ||||
S5‑232997 | LS on Approval of eQoE CRs for NR | Ericsson Limited | LS out | - | Yes |
Yes
| approved | No | S5‑232116 | |||
6.5.5 | Access control for management service |   | ||||||||||
6.5.5.1 | MSAC_WoP#1 |   | ||||||||||
6.5.5.2 | MSAC_WoP#2 |   | ||||||||||
6.5.5.3 | MSAC_WoP#3 |   | ||||||||||
6.5.5.4 | MSAC_WoP#4 | S5‑232606 | Rel-18 28.533 DraftCR for Authentication and Authorization usecase | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| revised | No | S5‑233005 | |
S5‑233005 | Rel-18 28.533 DraftCR for Authentication and Authorization usecase | Nokia, Nokia Shanghai Bell,Deutsche Telekom | draftCR | Approval | Yes |
Yes
| approved | No | S5‑232606 | |||
S5‑232607 | Rel-18 28.533 DraftCR for Identity to roles usecase | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| revised | No | S5‑233006 | |||
S5‑233006 | Rel-18 28.533 DraftCR for Identity to roles usecase | Nokia, Nokia Shanghai Bell,Deutsche Telekom | draftCR | Approval | Yes |
Yes
| approved | No | S5‑232607 | |||
S5‑232608 | Rel-18 28.533 DraftCR for roles to policies and criteria usecase | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| revised | No | S5‑233007 | |||
S5‑233007 | Rel-18 28.533 DraftCR for roles to policies and criteria usecase | Nokia, Nokia Shanghai Bell,Deutsche Telekom | draftCR | Approval | Yes |
Yes
| approved | No | S5‑232608 | |||
S5‑232609 | Rel-18 28.533 DraftCR for policies related to resources and operations usecase | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| merged | No | S5‑233005 | |||
S5‑232610 | Rel-18 28.533 DraftCR for granularity of resources and operations usecase | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| merged | No | S5‑233005 | |||
S5‑233137 | DraftCR 28.533 on Access control for management service | Nokia,Deutsche Telekom | draftCR | Approval | No |
Yes
| email approval | No | ||||
6.5.6 | 5G performance measurements and KPIs phase 3 |   | ||||||||||
6.5.6.1 | PM_KPI_5G_Ph3_WoP#1 | S5‑232404 | R18 CR TS 28.552 Add MA PDU session creation measurements for ATSSS | China Telecomunication Corp.,Intel | CR | Agreement | Yes |
Yes
| not pursued | No | ||
6.5.6.2 | PM_KPI_5G_Ph3_WoP#2 | S5‑232159 | Rel 18 TS 28.552 Add definition of DL PDCP buffered throughput per UE per DRB | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑233033 | |
S5‑233033 | Rel 18 TS 28.552 Add definition of DL PDCP buffered throughput per UE per DRB | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑232159 | |||
S5‑232346 | Add measurements for distribution of UL delay between NG-RAN and UE (including D1) | Intel | CR | Agreement | Yes |
Yes
| revised | No | S5‑233008 | |||
S5‑233008 | Add measurements for distribution of UL delay between NG-RAN and UE (including D1) | Intel | CR | Agreement | Yes |
Yes
| agreed | No | S5‑232346 | |||
S5‑232349 | Add measurements for average delay between NG-RAN and UE | Intel | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑232351 | Add measurements for DL packet loss rate on Uu | Intel | CR | Agreement | Yes |
Yes
| revised | No | S5‑233010 | |||
S5‑233010 | Add measurements for DL packet loss rate on Uu | Intel | CR | Agreement | Yes |
Yes
| agreed | No | S5‑232351 | |||
6.5.6.3 | PM_KPI_5G_Ph3_WoP#3 | S5‑232146 | DP on enhancing streaming format of PMs | Nokia, Nokia Shanghai Bell | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑233012 | |
S5‑233012 | DP on enhancing streaming format of PMs | Nokia, Nokia Shanghai Bell | discussion | Endorsement | Yes |
Yes
| endorsed | No | S5‑232146 | |||
S5‑232170 | Rel-18 CR TS 28.550 Enhance the streaming format of PM | Nokia, Nokia Shangai Bell | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑233011 | Rel-18 CR TS 28.550 Enhance the streaming format of PM | Nokia, Nokia Shangai Bell | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑232171 | Rel-18 CR TS 28.550 Example of ASN.1 schema for Streaming of PMs | Nokia, Nokia Shangai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑233013 | |||
S5‑233013 | Rel-18 CR TS 28.550 Example of ASN.1 schema for Streaming of PMs | Nokia, Nokia Shangai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑232171 | |||
6.5.7 | Methodology for deprecation |   | ||||||||||
6.5.7.1 | OAM_MetDep_ WoP#1 | S5‑232077 | Clarifications for lifecycleStatus property | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| revised | No | S5‑232968 | |
S5‑232968 | Clarifications for lifecycleStatus property | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| agreed | No | S5‑232077 | |||
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‑232064 | LS on 3GPP work on Energy Efficiency | Huawei | LS out | Agreement | Yes |
Yes
| revised | No | S5‑232903 | |
S5‑232903 | LS on 3GPP work on Energy Efficiency | Huawei | LS out | Agreement | Yes |
Yes
| approved | No | S5‑232064 | |||
S5‑232106 | Adding traceablity for ES compensation activation and deactivation procedures | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑232904 | |||
S5‑232904 | Adding traceablity for ES compensation activation and deactivation procedures | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑232106 | |||
S5‑232314 | DP to consider additional virtual resources usage to estimate VNF energy consumption | Nanjing Ericsson Panda Com Ltd | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑232397 | Rel-18 CR 28.554 Add the KPI of VNF energy consumption | Intel Belgium SA/NV | CR | Approval | Yes |
Yes
| not pursued | No | ||||
6.6.1.2 | EE5GPLUS_Ph2_WoP#2 | S5‑232693 | S5-232693 Rel-17 CR TS 28.554 Energy Efficiency KPI of a URLLC network slice based on reliability | BEIJING SAMSUNG TELECOM R&D | CR | Approval | No |
Yes
| withdrawn | Yes | ||
S5‑232695 | Rel-18 CR TS 28.554 Energy Efficiency KPI of a URLLC network slice based on reliability | BEIJING SAMSUNG TELECOM R&D | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑233082 | Rel-18 CR TS 28.554 Energy Efficiency KPI of a URLLC network slice based on reliability | BEIJING SAMSUNG TELECOM R&D | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
6.6.2 | Network slice provisioning enhancement |   | ||||||||||
6.6.2.1 | eNETSLICE_PRO_WoP#1 | S5‑232072 | Rel-18 CR 28.623 Add stage 3 solution for LcmProcess IOC | Intel Corporation (UK) Ltd | CR | Approval | Yes |
Yes
| not pursued | No | ||
S5‑233018 | Rel-18 CR 28.538 Add stage 3 solution for LcmProcess IOC | Intel Corporation (UK) Ltd | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑232101 | Rel-18 CR TS28.622 Add abstract IOC Controller_ to support asynchronous LCM operations | Nokia, Nokia Shanghai Bell | CR | Approval | No |
Yes
| withdrawn | Yes | S5‑226110 | |||
S5‑232102 | Add NetworkSliceController and NetworkSliceSubnetController IOCs to support asynchronous LCM operations | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | S5‑226557 | |||
S5‑232103 | Procedures to support asynchronous Network Slice LCM operations | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | S5‑226560 | |||
S5‑232104 | Rel-18 CR TS 28.623 Add stage 3 for abstract IOC Controller_ | Nokia, Nokia Shanghai Bell | CR | Approval | No |
Yes
| withdrawn | Yes | S5‑226132 | |||
S5‑232105 | Add stage 3 for data type AvailabilityStatus | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | S5‑226383 | |||
S5‑232210 | pCR TR 28.836 Add procedures for using intent driven approach to support async network slice provisioning | Huawei, Deutsche Telekom | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑232225 | Discussion paper for asynchronous LCM solutions | Intel Belgium SA/NV | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑232226 | Rel-18 CR 28.531 Update NSI / NSSI allocation procedures | Intel Belgium SA/NV | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑232227 | Rel-18 CR 28.531 Update NSI / NSSI deallocation procedures | Intel Belgium SA/NV | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑232347 | Way forward discussion on network slice in Rel-18 | Ericsson LM, Deutsche Telekom | discussion | Information | Yes |
Yes
| revised | No | S5‑232970 | |||
S5‑232970 | Way forward discussion on network slice in Rel-18 | Ericsson LM, Deutsche Telekom,Huawei | discussion | Information | Yes |
Yes
| revised | No | S5‑233155 | S5‑232347 | ||
S5‑233155 | Way forward discussion on network slice in Rel-18 | Ericsson, Deutsche Telekom, Huawei, Intel, Samsung, Telefónica, Nokia | discussion | Endorsement | Yes |
Yes
| endorsed | No | S5‑232970 | |||
S5‑232648 | Discussion on network slice controller in Rel-18 | Nokia, Nokia Shanghai Bell | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
6.6.2.2 | eNETSLICE_PRO_WoP#2 |   | ||||||||||
6.7 | Intelligence and Automation |   | ||||||||||
6.7.1 | Study on enhancement of autonomous network levels |   | ||||||||||
6.7.1.1 | FS_eANL_WoP#1 | S5‑232531 | pCR TR 28.910 Add key issues and potential solutions for existing scenarios in TS 28.100 | China Mobile, Huawei, AsiaInfo, CATT, ZTE, China Unicom | pCR | Approval | Yes |
Yes
| revised | No | S5‑232887 | |
S5‑232887 | pCR TR 28.910 Add key issues and potential solutions for existing scenarios in TS 28.100 | China Mobile, Huawei, AsiaInfo, CATT, ZTE, China Unicom | pCR | Approval | Yes |
YesEricsson objected.
The Chair asked for a show of hands.
Support: China Mobile, ZTE,China Telecom,CATT,China Unicom, Huawei.
No support: Ericsson, Nokia.
The Chair declared tdoc 887 as a working agreement.
| approved | No | S5‑232531 | |||
S5‑232544 | pCR TR 28.910 Add key issues for management of ANL | Huawei, China Mobile, AsiaInfo, CATT, China Unicom | pCR | Approval | Yes |
Yes
| noted | No | S5‑226213 | |||
S5‑232687 | Recommendation and conclusion for 28.910 | Ericsson | pCR | Yes |
Yes
| noted | No | |||||
S5‑233165 | Draft TR 28.910 | China Mobile | draft TR | Approval | No |
Yes
| email approval | No | ||||
6.7.1.2 | FS_eANL_WoP#2 | S5‑232298 | pCR TR 28.910 Add potential solution for 5GC NF deployment | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||
6.7.1.3 | FS_eANL_WoP#3 |   | ||||||||||
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‑232532 | pCR TR 28.909 Add key issues and potential solutions for ANLEVA | China Mobile, Huawei, AsiaInfo, CATT, ZTE, China Unicom | pCR | Approval | Yes |
Yes
| revised | No | S5‑232888 | |
S5‑232888 | pCR TR 28.909 Add key issues and potential solutions for ANLEVA | China Mobile, Huawei, AsiaInfo, CATT, ZTE, China Unicom | pCR | Approval | Yes |
YesThe Chair asked for a show of hands;
Support: Huawei, China Telecom, ZTE, CATT,China Mobile, China Unicom.
No support: Ericsson, Nokia.
The Chair declared a working agreement on this tdoc.
| approved | No | S5‑232532 | |||
S5‑232688 | Recommendation and conclusion for 28.909 | Ericsson GmbH, Eurolab | pCR | Yes |
Yes
| noted | No | |||||
S5‑233163 | Draft TR 28.909 | China Mobile | draft TR | Approval | No |
Yes
| email approval | No | ||||
6.7.2.2 | FS_ANLEVA_WoP#2 |   | ||||||||||
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‑232087 | pCR TR 28.912 Update the description of Issue#4.7 monitoring intent fulfilment information | Jetflow | pCR | Approval | Yes |
Yes
| noted | No | ||
S5‑232088 | pCR TR 28.912 Update the description of Issue#4.4 5GC related intent expectation | Jetflow | pCR | Approval | Yes |
Yes
| merged | No | S5‑232782 | |||
S5‑232089 | pCR TR 28.912 Add Issue#4.x user service experience based RAN energy saving | Jetflow | pCR | Approval | Yes |
Yes
| revised | No | S5‑232814 | |||
S5‑232814 | pCR TR 28.912 Add Issue#4.x user service experience based RAN energy saving | Jetflow | pCR | Approval | Yes |
Yes
| approved | No | S5‑232089 | |||
S5‑232090 | pCR TR 28.912 Add enhancement aspect6 and potential solution for user experience assurance | Jetflow | pCR | Approval | Yes |
Yes
| revised | No | S5‑232786 | |||
S5‑232786 | pCR TR 28.912 Add enhancement aspect6 and potential solution for user experience assurance | Jetflow | pCR | Approval | Yes |
Yes
| approved | No | S5‑232090 | |||
S5‑232206 | pCR TR 28.912 Address the inconsistent issue for intent report (WOP#2) | Huawei, China Mobile, Deutsche Telekom, Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S5‑232901 | |||
S5‑232901 | pCR TR 28.912 Address the inconsistent issue for intent report (WOP#2) | Huawei, China Mobile, Deutsche Telekom, Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S5‑232206 | |||
S5‑232207 | pCR TR 28.912 Add Comparison and analysis of potential solutions (WOP#2) | Huawei, Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S5‑232783 | |||
S5‑232783 | pCR TR 28.912 Add Comparison and analysis of potential solutions (WOP#2) | Huawei, Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S5‑232207 | |||
S5‑232261 | pCR TR 28.912 Intent Fullfillment feedback | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑232627 | |||
S5‑232262 | pCR TR 28.912 enhance service support expectation | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑232628 | |||
S5‑232299 | pCR 28.912 update potential solution for 5GC related intent expectation | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑232782 | |||
S5‑232782 | pCR 28.912 update potential solution for 5GC related intent expectation | Huawei, ZTE | pCR | Approval | Yes |
Yes
| approved | No | S5‑232299 | |||
S5‑232323 | pCR TR 28.912 Add Recommendation for Intent Reporting | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑232419 | pCR TS 28.912 Update Issue#4.7 Monitoring intent fulfilment information | Huawei Device Co., Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑232778 | |||
S5‑232778 | pCR TS 28.912 Update Issue#4.7 Monitoring intent fulfilment information | Huawei Device Co., Ltd | pCR | Approval | Yes |
Yes
| approved | No | S5‑232419 | |||
S5‑232432 | pCR TR 28.912 Add solutions for monitoring intent fulfilment | China Mobile Com. Corporation | pCR | Approval | Yes |
Yes
| revised | No | S5‑232780 | |||
S5‑232780 | pCR TR 28.912 Add solutions for monitoring intent fulfilment | China Mobile Com. Corporation | pCR | Approval | Yes |
Yes
| noted | No | S5‑232432 | |||
S5‑232433 | pCR TR 28.912 Add conclusion and recommendation for monitoring intent fulfilment | China Mobile Com. Corporation | pCR | Approval | Yes |
Yes
| revised | No | S5‑232781 | |||
S5‑232781 | pCR TR 28.912 Add conclusion and recommendation for monitoring intent fulfilment | China Mobile Com. Corporation | pCR | Approval | Yes |
Yes
| approved | No | S5‑232433 | |||
S5‑232453 | pCR 28.912 Transparent Intent Reporting Window | Samsung R&D Institute UK | pCR | Agreement | No |
Yes
| withdrawn | Yes | ||||
S5‑232455 | pCR 28.912 Transparent Intent Reporting Window | Samsung R&D Institute UK | pCR | Agreement | Yes |
Yes
| revised | No | S5‑232784 | |||
S5‑232784 | pCR 28.912 Transparent Intent Reporting Window | Samsung R&D Institute UK | pCR | Agreement | Yes |
Yes
| approved | No | S5‑232455 | |||
S5‑232627 | pCR TR 28.912 Intent Fullfillment feedback | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑232877 | S5‑232261 | ||
S5‑232877 | pCR TR 28.912 Intent Fullfillment feedback | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | S5‑232627 | |||
S5‑232628 | pCR TR 28.912 enhance service support expectation | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑232787 | S5‑232262 | ||
S5‑232787 | pCR TR 28.912 enhance service support expectation | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | S5‑232628 | |||
S5‑232785 | Draft TR 28.912 | Huawei | draft TR | Approval | No |
Yes
| email approval | No | ||||
6.7.3.3 | FS_eIDMS_MN_WoP#3 | S5‑232259 | pCR TR 28.912 Potential Solution on Intent-driven Closed Loop control | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑232625 | |
S5‑232260 | pCR TR 28.912 Potential solution for Intent handling capability | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑232626 | |||
S5‑232300 | pCR 28.912 add potential solution for intent-driven for MDA | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑232991 | |||
S5‑232991 | pCR 28.912 add potential solution for intent-driven for MDA | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑232300 | |||
S5‑232434 | pCR 28.912 Add potential solution for intent conflicts | NTT DOCOMO INC. | pCR | Approval | Yes |
Yes
| revised | No | S5‑232788 | |||
S5‑232788 | pCR 28.912 Add potential solution for intent conflicts | NTT DOCOMO INC. | pCR | Approval | Yes |
Yes
| approved | No | S5‑232434 | |||
S5‑232435 | pCR 28.912 Add reexecution point of intent after intent conflicts resolution | NTT DOCOMO INC. | pCR | Approval | Yes |
Yes
| revised | No | S5‑232789 | |||
S5‑232789 | pCR 28.912 Add reexecution point of intent after intent conflicts resolution | NTT DOCOMO INC. | pCR | Approval | Yes |
Yes
| approved | No | S5‑232435 | |||
S5‑232625 | pCR TR 28.912 Potential Solution on Intent-driven Closed Loop control | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑232876 | S5‑232259 | ||
S5‑232876 | pCR TR 28.912 Potential Solution on Intent-driven Closed Loop control | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | S5‑232625 | |||
S5‑232626 | pCR TR 28.912 Potential solution for Intent handling capability | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | S5‑232260 | |||
6.7.3.4 | FS_eIDMS_MN_WoP#4 |   | ||||||||||
6.7.3.5 | FS_eIDMS_MN_WoP#5 | S5‑232205 | pCR TR 28.912 Rapporteur clean up | Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||
S5‑232208 | pCR TR 28.912 Add conclusion and recommendation for issues related to collaboration with other SDOs (WOP#5) | Huawei, Deutsche Telekom | pCR | Approval | Yes |
Yes
| revised | No | S5‑232790 | |||
S5‑232790 | pCR TR 28.912 Add conclusion and recommendation for issues related to collaboration with other SDOs (WOP#5) | Huawei, Deutsche Telekom, Telefónica, Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S5‑232208 | |||
S5‑232209 | pCR TS 28.912 Add conclusion and recommendation for issues which need further investigation (WOP#5) | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑232791 | |||
S5‑232791 | pCR TS 28.912 Add conclusion and recommendation for issues which need further investigation (WOP#5) | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑232209 | |||
S5‑232263 | pCR TR 28.912 Additions to Conclusion and recommendation | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑232629 | |||
S5‑232444 | Presentation sheet of TR 28.912 for SA Approval | Huawei Device Co., Ltd | TS or TR cover | Approval | Yes |
Yes
| noted | No | ||||
S5‑232629 | pCR TR 28.912 Additions to Conclusion and recommendation | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑232792 | S5‑232263 | ||
S5‑232792 | pCR TR 28.912 Additions to Conclusion and recommendation | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑232629 | |||
6.7.4 | Study on intent-driven management for network slicing |   | ||||||||||
6.7.4.1 | FS_NETSLICE_IDMS_WoP#1 | S5‑232091 | pCR TR 28.836 Add Use case of Intent driven management to support the operation of network slice instance | Jetflow | pCR | Approval | Yes |
Yes
| revised | No | S5‑232947 | |
S5‑232947 | pCR TR 28.836 Add Use case of Intent driven management to support the operation of network slice instance | Jetflow,Huawei | pCR | Approval | Yes |
Yes
| noted | No | S5‑232091 | |||
S5‑232211 | pCR TR 28.836 Add solutions for expressing service and slice profile requirements as intent expectations | Huawei, China Mobile, Deutsche Telekom, Telefónica | pCR | Approval | Yes |
Yes
| revised | No | S5‑232948 | |||
S5‑232948 | pCR TR 28.836 Add solutions for expressing service and slice profile requirements as intent expectations | Huawei, China Mobile, Deutsche Telekom, Telefónica | pCR | Approval | Yes |
Yes
| approved | No | S5‑232211 | |||
S5‑232301 | pCR 28.836 Add use case of intent driven management to modify a network slice | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑233054 | |||
S5‑233054 | pCR 28.836 Add use case of intent driven management to modify a network slice | Huawei | pCR | Approval | Yes |
Yes
| noted | No | S5‑232301 | |||
S5‑232302 | pCR 28.836 Add use case of intent driven management for network slice feasibility check | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑232303 | pCR 28.836 Add use case of intent driven management to obtain intent fulfillment report of network slice | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑233166 | Draft TR 28.836 | Ericsson | draft TR | Approval | No |
Yes
| email approval | No | ||||
6.7.4.2 | FS_NETSLICE_IDMS_WoP#2 | S5‑232304 | pCR 28.836 Add potential solution for IDM to express expectation of network slice service assurance | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑232949 | |
S5‑232949 | pCR 28.836 Add potential solution for IDM to express expectation of network slice service assurance | Huawei | pCR | Approval | Yes |
Yes
| noted | No | S5‑232304 | |||
S5‑232311 | pCR TR 28.912 intents for slice-based cell reselection | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑232630 | |||
S5‑232630 | pCR TR 28.912 intents for slice-based cell reselection | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑232950 | S5‑232311 | ||
S5‑232950 | pCR TR 28.912 intents for slice-based cell reselection | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | S5‑232630 | |||
6.7.4.3 | FS_NETSLICE_IDMS_WoP#3 |   | ||||||||||
6.7.4.4 | FS_NETSLICE_IDMS_WoP#4 |   | ||||||||||
6.7.4.5 | FS_NETSLICE_IDMS_WoP#5 | S5‑232631 | pCR TR 28.912 Conclusion on Testing Intent-driven MnS Capabilities | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑232951 | |
S5‑232951 | pCR TR 28.912 Conclusion on Testing Intent-driven MnS Capabilities | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑232631 | |||
6.7.5 | Study on AI/ ML management |   | ||||||||||
6.7.5.1 | FS_AIML_MGMT_WoP#1 | S5‑232248 | pCR TR28.908 update AIML management capabilities | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑232612 | |
S5‑232284 | pCR TR 28.908 Add description of the AIML management relationship with 3GPP groups | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑232316 | pCR TR 28.908 Add Definitions and terms | Ericsson India Private Limited | pCR | Agreement | Yes |
Yes
| revised | No | S5‑232794 | |||
S5‑232794 | pCR TR 28.908 Add Definitions and terms | Ericsson India Private Limited | pCR | Agreement | Yes |
Yes
| approved | No | S5‑232316 | |||
S5‑232612 | pCR TR28.908 update AIML management capabilities | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑232793 | S5‑232248 | ||
S5‑232793 | pCR TR28.908 update AIML management capabilities | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑232612 | |||
S5‑232701 | pCR TR 28.908 Add definitions and terms | Ericsson India Private Limited | pCR | Agreement | Yes |
Yes
| revised | No | S5‑232795 | |||
S5‑232795 | pCR TR 28.908 Correction of terminologies | Ericsson India Private Limited | pCR | Agreement | Yes |
Yes
| approved | No | S5‑232701 | |||
S5‑233167 | Draft TR 28.908 | Intel | draft TR | Approval | No |
Yes
| email approval | No | ||||
6.7.5.2 | FS_AIML_MGMT_WoP#2 | S5‑232084 | pCR TR 28.908 Re-structing content of clause 5 Use cases, potential requirements, and possible solutions | NEC, Intel | pCR | Approval | Yes |
Yes
| revised | No | S5‑232807 | |
S5‑232807 | pCR TR 28.908 Re-structing content of clause 5 Use cases, potential requirements, and possible solutions | NEC, Intel | pCR | Approval | Yes |
Yes
| approved | No | S5‑232084 | |||
S5‑232255 | pCR 28.908 Use case & Potential solution on Transfer learning | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑232621 | |||
S5‑232257 | pCR TR28.908 AIML Update control | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑232623 | |||
S5‑232258 | pCR TR28.908 ML energy consumption aware ML training | Nokia, Nokia Shanghai Bell | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑232280 | pCR TR 28.908 Update the use case of ML entity performance evaluation | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑232796 | |||
S5‑232796 | pCR TR 28.908 Update the use case of ML entity performance evaluation | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑232280 | |||
S5‑232621 | pCR 28.908 Use case & Potential solution on Transfer learning | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑232808 | S5‑232255 | ||
S5‑232808 | pCR 28.908 Use case & Potential solution on Transfer learning | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑232621 | |||
S5‑232623 | pCR TR28.908 AIML Update control | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑232975 | S5‑232257 | ||
S5‑232975 | pCR TR28.908 AIML Update control | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑232623 | |||
S5‑232642 | pCR 28.908 Add use case on multiple ML entities testing | CATT | pCR | Approval | Yes |
Yes
| revised | No | S5‑233009 | |||
S5‑233009 | pCR 28.908 Add use case on multiple ML entities testing | CATT | pCR | Approval | Yes |
Yes
| approved | No | S5‑232642 | |||
S5‑232682 | pCR TR 28.908 Resolving overlap in use cases – Trustworthy Machine Learning | NEC, Intel | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑232683 | pCR TR 28.908 Resolving overlap in use cases – Performance evaluation | NEC, Intel | pCR | Approval | Yes |
Yes
| noted | No | ||||
6.7.5.3 | FS_AIML_MGMT_WoP#3 | S5‑232241 | TR28.908 Potential Solution and evaluation on Measurement data correlation analytics for ML training | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑232848 | |
S5‑232848 | TR28.908 Potential Solution and evaluation on Measurement data correlation analytics for ML training | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑232241 | |||
S5‑232242 | TR28.908 Potential Solution and evaluation on Training data effectiveness analytics | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑233040 | |||
S5‑233040 | TR28.908 Potential Solution and evaluation on Training data effectiveness analytics | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑232242 | |||
S5‑232243 | TR28.908 Potential Solution and evaluation on Training data effectiveness reporting | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑233041 | |||
S5‑233041 | TR28.908 Potential Solution and evaluation on Training data effectiveness reporting | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑232243 | |||
S5‑232249 | pCR TR28.908 Potential Solution on AIML trustworthiness indicators | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑232613 | |||
S5‑232250 | pCR TR28.908 Potential Solution on AIML data trustworthiness | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑232614 | |||
S5‑232251 | pCR TR28.908 Potential Solution on AIML training trustworthiness | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑232615 | |||
S5‑232252 | pCR TR28.908 Potential Solution on AIML inference trustworthiness | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑232616, S5‑232617 | |||
S5‑232253 | pCR 28.908 Assessment of ML trustworthiness | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑232618 | |||
S5‑232254 | pCR 28.908 Extend coordination of AIML capabilities | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑232619 | |||
S5‑232256 | pCR 28.908 Extend ML update management | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑232622 | |||
S5‑232279 | pCR TR 28.908 Add the evaluation of AIML update management | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑232847 | |||
S5‑232847 | pCR TR 28.908 Add the evaluation of AIML update management | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑232279 | |||
S5‑232281 | pCR TR 28.908 Update the solution of ML entity performance evaluation | Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑232282 | pCR TR 28.908 Add the solution of ML entity configuration | Huawei | pCR | Approval | Yes |
Yes
| merged | No | S5‑233083 | |||
S5‑232360 | pCR 28.908 Split AI-ML configuration management into two phases (inference and ML training) | Intel, NEC | pCR | Approval | Yes |
Yes
| revised | No | S5‑233083 | |||
S5‑233083 | pCR 28.908 Split AI-ML configuration management into two phases (inference and ML training) | Intel, NEC,Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑232360 | |||
S5‑232613 | pCR TR28.908 Potential Solution on AIML trustworthiness indicators | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑232974 | S5‑232249 | ||
S5‑232974 | pCR TR28.908 Potential Solution on AIML trustworthiness indicators | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑232613 | |||
S5‑232614 | pCR TR28.908 Potential Solution on AIML data trustworthiness | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑232250 | |||
S5‑232615 | pCR TR28.908 Potential Solution on AIML training trustworthiness | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑232251 | |||
S5‑232616 | pCR TR28.908 Potential Solution on AIML inference trustworthiness | Nokia, Nokia Shanghai Bell | pCR | Approval | No |
Yes
| withdrawn | Yes | S5‑232252 | |||
S5‑232617 | pCR TR28.908 Potential Solution on AIML inference trustworthiness | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑232252 | |||
S5‑232618 | pCR 28.908 Assessment of ML trustworthiness | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑232253 | |||
S5‑232619 | pCR 28.908 Extend coordination of AIML capabilities | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | S5‑232254 | |||
S5‑232620 | pCR 28.908 Updates and Corrections for Configuration Management | Ericsson Telecomunicazioni SpA | pCR | Agreement | Yes |
Yes
| revised | No | S5‑232815 | |||
S5‑232815 | pCR 28.908 Updates and Corrections for Configuration Management | Ericsson Telecomunicazioni SpA | pCR | Agreement | Yes |
Yes
| approved | No | S5‑232620 | |||
S5‑232622 | pCR 28.908 Extend ML update management | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | S5‑232256 | |||
S5‑232846 | pCR 28.908 Extend ML update management | Nokia, Nokia Shanghai Bell | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑232643 | pCR 28.908 Add possible solution for multiple ML entities testing | CATT | pCR | Approval | Yes |
Yes
| approved | No | ||||
6.7.5.4 | FS_AIML_MGMT_WoP#4 | S5‑232240 | TR28.908 Potential Solution and evaluation on coordination of capabilities | Nokia, Nokia Shanghai Bell, TELUS | pCR | Approval | Yes |
Yes
| revised | No | S5‑233039 | |
S5‑233039 | TR28.908 Potential Solution and evaluation on coordination of capabilities | Nokia, Nokia Shanghai Bell, TELUS | pCR | Approval | Yes |
Yes
| approved | No | S5‑232240 | |||
6.7.5.5 | FS_AIML_MGMT_WoP#5 |   | ||||||||||
6.7.5.6 | FS_AIML_MGMT_WoP#6 | S5‑232283 | pCR TR 28.908 Add AIML capabilities deployment scenarios | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑233138 | |
S5‑233138 | pCR TR 28.908 Add AIML capabilities deployment scenarios | Huawei,Intel,NEC | pCR | Approval | Yes |
Yes
| approved | No | S5‑232283 | |||
S5‑232364 | pCR 28.908 Add deployment scenarios of AI-ML related capabilities | Intel, NEC | pCR | Approval | Yes |
Yes
| merged | No | S5‑233138 | |||
6.7.5.7 | FS_AIML_MGMT_WoP#7 | S5‑232085 | pCR TR28.908 Add general conclusions and recommendations | NEC, Intel | pCR | Approval | Yes |
Yes
| approved | No | ||
S5‑232366 | Presentation of TR 28.908 for approval | Intel, NEC | pCR | Approval | Yes |
Yes
| noted | No | ||||
6.7.6 | Study on Enhancement of the management aspects related to NWDAF |   | ||||||||||
6.7.6.1 | FS_MANWDAF_WoP#1 | S5‑232559 | Add conclusions for KI#1 and KI#2 | Chinatelecom Cloud | pCR | Yes |
Yes
| approved | No | |||
S5‑232633 | Presentation of Specification/Report to TSG: TR28.864, Version 0.6.0 | China Telecommunications | TS or TR cover | Approval | Yes |
Yes
| approved | No | ||||
S5‑232638 | Update the Scope section of TR 28864 | China Telecommunications | pCR | Approval | Yes |
Yes
| revised | No | S5‑232999 | |||
S5‑232999 | Update the Scope section of TR 28864 | China Telecommunications | pCR | Approval | Yes |
Yes
| approved | No | S5‑232638 | |||
S5‑232666 | Providing Requirement Text for KI#1 and KI#2 in TR 28864 | China Telecommunications | pCR | Approval | Yes |
Yes
| revised | No | S5‑233000 | |||
S5‑233000 | Providing Requirement Text for KI#1 and KI#2 in TR 28864 | China Telecommunications | pCR | Approval | Yes |
Yes
| approved | No | S5‑232666 | |||
S5‑232694 | Update KI#3 KI#4 Requirements in TR28864 | China Telecommunications | pCR | Approval | Yes |
Yes
| revised | No | S5‑233001 | |||
S5‑233001 | Update KI#3 KI#4 Requirements in TR28864 | China Telecommunications | pCR | Approval | Yes |
Yes
| approved | No | S5‑232694 | |||
S5‑232696 | Provide description of the requirements having been discussed in KI#5 TR28864 | China Telecommunications | pCR | Approval | Yes |
Yes
| revised | No | S5‑233002 | |||
S5‑233002 | Provide description of the requirements having been discussed in KI#5 TR28864 | China Telecommunications | pCR | Approval | Yes |
Yes
| approved | No | S5‑232696 | |||
S5‑232998 | Draft TR 28.864 | China Telecom | draft TR | Approval | No |
Yes
| email approval | No | ||||
6.7.6.2 | FS_MANWDAF_WoP#2 | S5‑232560 | pCR 28.864 Update the evaluation and add the conclusion for KI#3 | Chinatelecom Cloud | pCR | Approval | Yes |
Yes
| approved | No | ||
S5‑232561 | pCR 28.864 Add the evaluation and conclusion for KI#4 | Chinatelecom Cloud | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑232562 | pCR 28.864 Add conclusions for KI#5 and KI#6 | Chinatelecom Cloud | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑232563 | pCR 28.864 Add the evaluation and conclusion for KI#7 | Chinatelecom Cloud | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑232564 | pCR 28.864 Add conclusions and recommendations for TR 28.864 | Chinatelecom Cloud | pCR | Yes |
Yes
| revised | No | S5‑233004 | ||||
S5‑233004 | pCR 28.864 Add conclusions and recommendations for TR 28.864 | Chinatelecom Cloud | pCR | - | Yes |
Yes
| approved | No | S5‑232564 | |||
6.7.7 | Study on Fault Supervision Evolution |   | ||||||||||
6.7.7.1 | FS_FSEV_WoP#1 | S5‑232550 | pCR TR 28.830 Add concept of anomaly report | Huawei, China Mobile | pCR | Approval | Yes |
Yes
| revised | No | S5‑233020 | |
S5‑233020 | pCR TR 28.830 Add concept of anomaly report | Huawei, China Mobile | pCR | Approval | Yes |
Yes
| noted | No | S5‑232550 | |||
S5‑232551 | pCR TR 28.830 Add description of management capability | Huawei, China Mobile | pCR | Approval | Yes |
Yes
| revised | No | S5‑233021 | |||
S5‑233021 | pCR TR 28.830 Add description of management capability | Huawei, China Mobile,Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S5‑233156 | S5‑232551 | ||
S5‑233156 | pCR TR 28.830 Add description of management capability | Huawei, CMCC, Nokia, Nokia Shangai Bell, Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S5‑233021 | |||
S5‑233161 | Draft TR 28.830 | China Mobile | draft TR | Approval | No |
Yes
| email approval | No | ||||
6.7.7.2 | FS_FSEV_WoP#2 | S5‑232552 | pCR TR 28.830 Add description of fault related analysis | Huawei, China Mobile | pCR | Approval | Yes |
Yes
| revised | No | S5‑233022 | |
S5‑233022 | pCR TR 28.830 Add description of fault related analysis | Huawei, China Mobile | pCR | Approval | Yes |
Yes
| revised | No | S5‑233157 | S5‑232552 | ||
S5‑233157 | pCR TR 28.830 Add description of fault related analysis | Huawei, China Mobile | pCR | Approval | Yes |
Yes
| approved | No | S5‑233022 | |||
6.7.7.3 | FS_FSEV_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‑232317 | pCR TR 28.925 Rapporteur cleanup | HuaWei Technologies Co., Ltd | pCR | Yes |
Yes
| approved | No | |||
S5‑232891 | Draft TR 28.925 | Huawei | draft TR | Approval | No |
Yes
| email approval | No | ||||
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‑232318 | pCR 28.925 Add an example for management function deployment scenarios | HuaWei Technologies Co., Ltd | pCR | Yes |
Yes
| revised | No | S5‑232952 | ||
S5‑232952 | pCR 28.925 Add an example for management function deployment scenarios | HuaWei Technologies Co., Ltd | pCR | - | Yes |
Yes
| approved | No | S5‑232318 | |||
6.8.1.6 | FS_eSBMA_WoP#6 | S5‑232140 | pCR TR 28.925 Add issue about extending TS 32.300 to support SBMA | Oy LM Ericsson AB | pCR | Approval | Yes |
Yes
| revised | No | S5‑232953 | |
S5‑232953 | pCR TR 28.925 Add issue about extending TS 32.300 to support SBMA | Oy LM Ericsson AB | pCR | Approval | Yes |
Yes
| approved | No | S5‑232140 | |||
6.8.2 | Study on Basic SBMA enabler enhancements |   | ||||||||||
6.8.2.1 | FS_eSBMAe_WoP#1 | S5‑232511 | pCR 28.831 Multiple alarms in single notifyNewAlarm Key Issue | Samsung R&D Institute UK | pCR | Agreement | Yes |
Yes
| revised | No | S5‑233034 | |
S5‑233034 | pCR 28.831 Multiple alarms in single notifyNewAlarm Key Issue | Samsung R&D Institute UK | pCR | Agreement | Yes |
Yes
| noted | No | S5‑232511 | |||
6.8.2.2 | FS_eSBMAe_WoP#2 | S5‑232345 | Rel-18 CR 28.831 Add conclusion for issue 3 Definition of createMOI | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑233035 | |
S5‑233035 | Rel-18 CR 28.831 Add conclusion for issue 3 Definition of createMOI | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑232345 | |||
S5‑232348 | Rel-18 CR 28.831 Add conclusion for issue 4 Definition of modifyMOIAttributes | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑233036 | |||
S5‑233036 | Rel-18 CR 28.831 Add conclusion for issue 4 Definition of modifyMOIAttributes | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑232348 | |||
S5‑232350 | Rel-18 CR 28.831 Add issue on Bulk CM operations (stage 2) | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑233037 | |||
S5‑233037 | Rel-18 CR 28.831 Add issue on Bulk CM operations (stage 2) | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑232350 | |||
S5‑232352 | Rel-18 CR 28.831 Add CR proposal and conclusion for issue on Bulk CM operations (stage 2) | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑233038 | |||
S5‑233038 | Rel-18 CR 28.831 Add CR proposal and conclusion for issue on Bulk CM operations (stage 2) | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑232352 | |||
S5‑233162 | Draft TR 28.831 | Nokia | draft TR | Approval | No |
Yes
| email approval | No | ||||
6.8.2.3 | FS_eSBMAe_WoP#3 | S5‑232098 | Rel-18 pCR TR 28.831 Add a new key issue for Advertising NRM properties by the MnS producer | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑233042 | |
S5‑233042 | Rel-18 pCR TR 28.831 Add a new key issue for Advertising NRM properties by the MnS producer | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | S5‑232098 | |||
S5‑232099 | Rel-18 pCR TR 28.831 Add potential requirements for KI for Advertising NRM properties by the MnS producer | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑233043 | |||
S5‑233043 | Rel-18 pCR TR 28.831 Add potential requirements for KI for Advertising NRM properties by the MnS producer | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | S5‑232099 | |||
S5‑232100 | Rel-18 pCR TR 28.831 Add a potential solution for KI for Advertising NRM properties by the MnS producer | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑233044 | |||
S5‑233044 | Rel-18 pCR TR 28.831 Add a potential solution for KI for Advertising NRM properties by the MnS producer | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | S5‑232100 | |||
S5‑232353 | Rel-18 CR 28.831 Add issue on advertising communication options (REST SS) | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑232356 | Rel-18 CR 28.831 Add general solution for advertising communication options (REST SS) | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑232359 | Rel-18 CR 28.831 Add solution for advertising supported HTTP request methods (REST SS) | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑233045 | |||
S5‑233045 | Rel-18 CR 28.831 Add solution for advertising supported HTTP request methods (REST SS) | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑232359 | |||
S5‑232361 | Rel-18 CR 28.831 Add solution for advertising supported patch request formats (REST SS) | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑232362 | Rel-18 CR 28.831 Add solution for advertising supported query parameters (REST SS) | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑232365 | Rel-18 CR 28.831 Add conclusion for issue on advertising communication options (REST SS) | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑233047 | |||
S5‑233047 | Rel-18 CR 28.831 Add conclusion for issue on advertising communication options (REST SS) | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑232365 | |||
S5‑232367 | Rel-18 CR 28.831 Add CR proposal for error response – Supported HTTP error codes | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑233048 | |||
S5‑233048 | Rel-18 CR 28.831 Add CR proposal for error response – Supported HTTP error codes | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑232367 | |||
S5‑232369 | Rel-18 CR 28.831 Add CR proposal for error response – Error response body format | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑233049 | |||
S5‑233049 | Rel-18 CR 28.831 Add CR proposal for error response – Error response body format | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑232369 | |||
S5‑232371 | Rel-18 CR 28.831 Add CR proposal for error response – Type property | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑233050 | |||
S5‑233050 | Rel-18 CR 28.831 Add CR proposal for error response – Type property | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑232371 | |||
S5‑232372 | Rel-18 CR 28.831 Add CR proposal for error response – Reason property | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑233051 | |||
S5‑233051 | Rel-18 CR 28.831 Add CR proposal for error response – Reason property | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑232372 | |||
6.8.2.4 | FS_eSBMAe_WoP#4 | S5‑232380 | Rel-18 CR 28.831 Clarify the mapping from a JSON document into the XPath data model | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑233052 | |
S5‑233052 | Rel-18 CR 28.831 Clarify the mapping from a JSON document into the XPath data model | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑232380 | |||
6.8.2.5 | FS_eSBMAe_WoP#5 |   | ||||||||||
6.8.2.6 | FS_eSBMAe_WoP#6 |   | ||||||||||
6.8.2.7 | FS_eSBMAe_WoP#7 | S5‑232510 | pCR 28.831 Logging Key Issues | Samsung R&D Institute UK | pCR | Agreement | Yes |
Yes
| revised | No | S5‑233053 | |
S5‑233053 | pCR 28.831 Logging Key Issues | Samsung R&D Institute UK | pCR | Agreement | Yes |
Yes
| approved | No | S5‑232510 | |||
6.8.2.8 | FS_eSBMAe_WoP#8 |   | ||||||||||
6.8.2.9 | FS_eSBMAe_WoP#9 | S5‑232707 | pCR 28.831 Trigger Key Issues | Samsung R&D Institute UK | pCR | Agreement | Yes |
Yes
| revised | No | S5‑233055 | |
S5‑233055 | pCR 28.831 Trigger Key Issues | Samsung R&D Institute UK | pCR | Agreement | Yes |
Yes
| noted | No | S5‑232707 | |||
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 | S5‑232527 | Add Conclusion and recommendation for Issue#1 | China Unicom | pCR | Approval | Yes |
Yes
| revised | No | S5‑232956 | |
S5‑232956 | Add Conclusion and recommendation for Issue#1 | China Unicom | pCR | Approval | Yes |
Yes
| approved | No | S5‑232527 | |||
S5‑233032 | Draft TR 28.832 | China Unicom | draft TR | Approval | No |
Yes
| email approval | No | ||||
6.8.3.2 | FS_URLLC_Mgt_WoP#2 | S5‑232529 | Add Conclusion and recommendation for Issue #4 | China Unicom | pCR | Approval | Yes |
Yes
| revised | No | S5‑232957 | |
S5‑232957 | Add Conclusion and recommendation for Issue #4 | China Unicom | pCR | Approval | Yes |
Yes
| noted | No | S5‑232529 | |||
S5‑232533 | Add Solution for configuration of latency for URLLC in RAN over the air interface | China Unicom, Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑232958 | |||
S5‑232958 | Add Solution for configuration of latency for URLLC in RAN over the air interface | China Unicom, Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑233151 | S5‑232533 | ||
S5‑233151 | Add Solution for configuration of latency for URLLC in RAN over the air interface | China Unicom, Huawei | pCR | Approval | Yes |
Yes
| noted | No | S5‑232958 | |||
S5‑232689 | URLLC solutions | Ericsson | pCR | Yes |
Yes
| revised | No | S5‑232959 | ||||
S5‑232959 | URLLC solutions | Ericsson | pCR | - | Yes |
Yes
| noted | No | S5‑232689 | |||
6.8.3.3 | FS_URLLC_Mgt_WoP#3 | S5‑232534 | Add new solution for support for performance measurements related on URLLC resource load | China Unicom | pCR | Approval | Yes |
Yes
| noted | No | ||
S5‑233128 | Add new solution for support for performance measurements related on URLLC resource load | China Unicom | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑232535 | Add New Solution for URLLC performance management related to reliability in RAN | China Unicom | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑233129 | Add New Solution for URLLC performance management related to reliability in RAN | China Unicom | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
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 |   | ||||||||||
6.8.4.4 | FS_5GLAN_Mgt_WoP#4 | S5‑232429 | pCR TR28.833 Adding editorial and technical changes | China Mobile Com. Corporation | pCR | Approval | Yes |
Yes
| withdrawn | Yes | ||
S5‑232431 | Presentation sheet of TR 28.833 for SA Approval | China Mobile Com. Corporation | TS or TR cover | Approval | Yes |
Yes
| approved | No | ||||
S5‑232454 | pCR TR28.833 Adding editorial and technical changes | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑233003 | |||
S5‑233003 | pCR TR28.833 Adding editorial and technical changes | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑232454 | |||
S5‑232892 | Draft TR 28.833 | China Mobile | draft TR | discussion | No |
Yes
| email approval | No | ||||
6.8.5 | Study on Management of Cloud Native Virtualized Network Functions |   | ||||||||||
6.8.5.1 | FS_MCVNF_WoP#1 | S5‑232195 | pCR TR 28.834 Add issues and requirements for usecase# 3 | Jetflow | pCR | Approval | Yes |
Yes
| revised | No | S5‑232960 | |
S5‑232960 | pCR TR 28.834 Add issues and requirements for usecase# 3 | Jetflow | pCR | Approval | Yes |
Yes
| noted | No | S5‑232195 | |||
S5‑232236 | pCR 28.834 Add key issues for usecase 6 and usecase 7 | AsiaInfo Technologies Inc | pCR | Approval | Yes |
Yes
| revised | No | S5‑232961 | |||
S5‑232961 | pCR 28.834 Add key issues for usecase 6 and usecase 7 | AsiaInfo Technologies Inc | pCR | Approval | Yes |
Yes
| approved | No | S5‑232236 | |||
S5‑232441 | PCR 28.834 Add use case and solution for healing of cloud-native VNF | AsiaInfo Technologies Inc | pCR | Approval | Yes |
Yes
| revised | No | S5‑232962 | |||
S5‑232962 | PCR 28.834 Add use case and solution for healing of cloud-native VNF | AsiaInfo Technologies Inc | pCR | Approval | Yes |
Yes
| approved | No | S5‑232441 | |||
S5‑232536 | pCR 28.834 Add use case and solution for VNF package management of the cloud-native VNF | AsiaInfo Technologies Inc | pCR | Approval | Yes |
Yes
| revised | No | S5‑232963 | |||
S5‑232963 | pCR 28.834 Add use case and solution for VNF package management of the cloud-native VNF | AsiaInfo Technologies Inc,Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑232536 | |||
6.8.5.2 | FS_MCVNF_WoP#2 |   | ||||||||||
6.8.5.3 | FS_MCVNF_WoP#3 | S5‑232305 | pCR 28.834 move VNF package update solution to clause 6 | Huawei | pCR | Approval | Yes |
Yes
| merged | No | S5‑232963 | |
S5‑232964 | pCR 28.834 move VNF package update solution to clause 6 | Huawei | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑232306 | pCR 28.834 Add potential solution for scaling | Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑232307 | pCR 28.834 add conclusion and recommentation for cloud native VNF creation | Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑232664 | pCR 28.834 Add conclusion and recommendation | China Mobile E-Commerce Co. | pCR | Approval | Yes |
Yes
| revised | No | S5‑232966 | |||
S5‑232966 | pCR 28.834 Add conclusion and recommendation | China Mobile E-Commerce Co. | pCR | Approval | Yes |
Yes
| approved | No | S5‑232664 | |||
S5‑232665 | pCR 28.834 Update solution for management of the cloud-native VNF using generic OAM functions | China Mobile E-Commerce Co. | pCR | Approval | Yes |
Yes
| revised | No | S5‑232967 | |||
S5‑232967 | pCR 28.834 Update solution for management of the cloud-native VNF using generic OAM functions | China Mobile E-Commerce Co. | pCR | Approval | Yes |
Yes
| approved | No | S5‑232665 | |||
S5‑232965 | Draft TR 28.834 | China Mobile | draft TR | Approval | No |
Yes
| email approval | No | ||||
S5‑233158 | Cover sheet TR 28.834 | China Mobile | TS or TR cover | Approval | No |
Yes
| email approval | No | ||||
6.8.6 | Study on Management Aspects of 5G MOCN Network Sharing Phase2 |   | ||||||||||
6.8.6.1 | FS_MANS_ph2_WoP#1 | S5‑232519 | Add conclusion and recommendation for issue #1 | China Unicom | pCR | Approval | Yes |
Yes
| revised | No | S5‑232971 | |
S5‑232971 | Add conclusion and recommendation for issue #1 | China Unicom | pCR | Approval | Yes |
Yes
| noted | No | S5‑232519 | |||
S5‑232520 | Add conclusion and recommendation for issue #2 | China Unicom | pCR | Approval | Yes |
Yes
| revised | No | S5‑232969 | |||
S5‑232969 | Add conclusion and recommendation for issue #2 | China Unicom | pCR | Approval | Yes |
Yes
| noted | No | S5‑232520 | |||
S5‑232521 | Add conclusion and recommendation for issue #3 | China Unicom | pCR | Approval | Yes |
Yes
| revised | No | S5‑233126 | |||
S5‑233126 | Add conclusion and recommendation for issue #3 | China Unicom | pCR | Approval | Yes |
Yes
| noted | No | S5‑232521 | |||
S5‑232522 | Add conclusion and recommendation for issue #5 | China Unicom | pCR | Approval | Yes |
Yes
| revised | No | S5‑233127 | |||
S5‑233127 | Add conclusion and recommendation for issue #5 | China Unicom | pCR | Approval | Yes |
Yes
| noted | No | S5‑232522 | |||
S5‑232523 | Add conclusion and recommendation for issue #7 | China Unicom | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑232524 | Add conclusion and recommendation for issue #8 | China Unicom | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑232525 | Add conclusion and recommendation for issue #4 | China Unicom | pCR | Approval | Yes |
Yes
| revised | No | S5‑232973 | |||
S5‑232973 | Add conclusion and recommendation for issue #4 | China Unicom | pCR | Approval | Yes |
Yes
| noted | No | S5‑232525 | |||
S5‑232526 | Add conclusion and recommendation for issue #6 | China Unicom | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑232637 | pCR TR 28.835 Add recommendation for KI#2 | ZTE Corporation | pCR | Approval | Yes |
Yes
| merged | No | S5‑232969 | |||
S5‑232653 | pCR TR 28.835 Add issue and potential solution for collection of operator specific performance measurements | ZTE Corporation | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑232976 | pCR TR 28.835 Add issue and potential solution for collection of operator specific performance measurements | ZTE Corporation | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑232972 | Draft TR 28.835 | China Unicom | draft TR | Approval | No |
Yes
| email approval | No | ||||
6.8.6.2 | FS_MANS_ph2_WoP#2 |   | ||||||||||
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 |   | ||||||||||
6.8.7.2 | FS_5GMDT_Ph2_WoP#2 | S5‑232156 | pCR TR28.837 Potential Solution and conclusion for name containment of Trace job in Signalling based trace activation | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||
S5‑232157 | pCR TR28.837 Potential Solution and conclusion for reporting of per direction per DRB measurements | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑232158 | pCR TR28.837 Potential Solution and conclusion for structuring of Trace job IOC | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑232977 | Draft TR 28.837 | Nokia | draft TR | Approval | No |
Yes
| email approval | No | ||||
6.8.7.3 | FS_5GMDT_Ph2_WoP#3 |   | ||||||||||
6.8.7.4 | FS_5GMDT_Ph2_WoP#4 | S5‑232147 | Overview of Trace Management of Non-Public Networks | Nokia, Nokia Shanghai Bell | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑232978 | |
S5‑232978 | Overview of Trace Management of Non-Public Networks | Nokia, Nokia Shanghai Bell | discussion | Endorsement | Yes |
Yes
| noted | No | S5‑232147 | |||
S5‑232152 | pCR TR28.837 NPN_KI_1 Problem Statement for support of NPN for TraceMDT | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑232979 | |||
S5‑232979 | pCR TR28.837 NPN_KI_1 Problem Statement for support of NPN for TraceMDT | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑232152 | |||
S5‑232153 | pCR TR28.837 NPN_KI_1 Solution and conclusion for support of NPN for TraceMDT | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| merged | No | S5‑232979 | |||
S5‑232154 | pCR TR28.837 NPN_KI_2 Problem Statement to support RLF and RCEF reports for NPN | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑232980 | |||
S5‑232980 | pCR TR28.837 NPN_KI_2 Problem Statement to support RLF and RCEF reports for NPN | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑232154 | |||
S5‑232155 | pCR TR28.837 NPN_KI_2 Solution and conclusion to support RLF and RCEF reports for NPN | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| merged | No | S5‑232980 | |||
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 | S5‑232151 | pCR TR28.837 Conclusions and Recommendations | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||
6.8.8 | Study on Management Aspects of IoT NTN Enhancements |   | ||||||||||
6.8.8.1 | FS_IOT_NTN_WoP#1 | S5‑232644 | pCR 28.841 Add use case for NTN mobility management enhancement | CATT | pCR | Approval | Yes |
Yes
| revised | No | S5‑232867 | |
S5‑232867 | pCR 28.841 Add use case for NTN mobility management enhancement | CATT | pCR | Approval | Yes |
Yes
| approved | No | S5‑232644 | |||
S5‑232645 | pCR 28.841 Add potential requirement for NTN mobility management enhancement | CATT | pCR | Approval | Yes |
Yes
| revised | No | S5‑232868 | |||
S5‑232868 | pCR 28.841 Add potential requirement for NTN mobility management enhancement | CATT | pCR | Approval | Yes |
Yes
| approved | No | S5‑232645 | |||
S5‑233160 | Draft TR 28.841 | China Unicom | TS or TR cover | Approval | No |
Yes
| email approval | No | ||||
6.8.8.2 | FS_IOT_NTN_WoP#2 | S5‑232646 | pCR 28.841 Add possible solution for NTN mobility management enhancement | CATT | pCR | Approval | Yes |
Yes
| revised | No | S5‑232869 | |
S5‑232869 | pCR 28.841 Add possible solution for NTN mobility management enhancement | CATT | pCR | Approval | Yes |
Yes
| approved | No | S5‑232646 | |||
6.8.8.3 | FS_IOT_NTN_WoP#3 | S5‑232437 | pCR 28.841 add management architectures for satellite components | China Unicom | pCR | Approval | Yes |
Yes
| revised | No | S5‑232870 | |
S5‑232870 | pCR 28.841 add management architectures for satellite components | China Unicom | pCR | Approval | Yes |
Yes
| approved | No | S5‑232437 | |||
S5‑232438 | pCR 28.841 add references and abbreviations | China Unicom | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑232439 | pCR 28.841 Rapporteur clean up | China Unicom | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑232440 | pCR 28.841 add conclusions and recommendations | China Unicom, CATT | pCR | Approval | Yes |
Yes
| revised | No | S5‑232871 | |||
S5‑232871 | pCR 28.841 add conclusions and recommendations | China Unicom, CATT | pCR | Approval | Yes |
Yes
| approved | No | S5‑232440 | |||
S5‑232899 | Draft TR 28.841 | China Unicom | draft TR | Approval | No |
Yes
| email approval | No | ||||
6.8.9 | Study on Data management phase 2 |   | ||||||||||
6.8.9.1 | FS_MADCOL_ph2_WoP#1 | S5‑232401 | pCR TR 28.842 New KI on discovery of stored management data | Microsoft Europe SARL | pCR | Yes |
Yes
| revised | No | S5‑232872 | ||
S5‑232872 | pCR TR 28.842 New KI on discovery of stored management data | Microsoft Europe SARL | pCR | - | Yes |
Yes
| approved | No | S5‑232401 | |||
S5‑232718 | Add key issue on enhancing the description of management data | Nokia Germany | pCR | Approval | Yes |
Yes
| revised | No | S5‑232873 | |||
S5‑232873 | Add key issue on enhancing the description of management data | Nokia Germany | pCR | Approval | Yes |
Yes
| noted | No | S5‑232718 | |||
6.8.9.2 | FS_MADCOL_ph2_WoP#2 | S5‑232402 | pCR TR 28.842 New KI on storage of management data | Microsoft Europe SARL | pCR | Yes |
Yes
| revised | No | S5‑232874 | ||
S5‑232874 | pCR TR 28.842 New KI on storage of management data | Microsoft Europe SARL | pCR | - | Yes |
Yes
| approved | No | S5‑232402 | |||
S5‑233168 | Draft TR 28.842 | Nokia | draft TR | Approval | No |
Yes
| email approval | No | ||||
6.8.9.3 | FS_MADCOL_ph2_WoP#3 | S5‑232403 | pCR TR 28.842 New KI on enhancing control of management data production | Microsoft Europe SARL | pCR | Yes |
Yes
| noted | No | |||
6.8.9.4 | FS_MADCOL_ph2_WoP#4 |   | ||||||||||
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‑232407 | pCR 28.907 Update conclusion for KI resource isolation demand for Smart Grid Utilities | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑232875 | |
S5‑232875 | pCR 28.907 Update conclusion for KI resource isolation demand for Smart Grid Utilities | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑232407 | |||
S5‑232409 | pCR 28.907 Conclusion for KI exposure of management capabilities and corresponding managed resources | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑232878 | |||
S5‑232878 | pCR 28.907 Conclusion for KI exposure of management capabilities and corresponding managed resources | Huawei | pCR | Approval | Yes |
Yes
| noted | No | S5‑232409 | |||
S5‑232410 | Update SID on enhancement of management of NPN | Huawei | SID revised | Approval | Yes |
Yes
| revised | No | S5‑232879 | |||
S5‑232879 | Update SID on enhancement of management of NPN | Huawei | SID revised | Approval | Yes |
Yes
| approved | No | S5‑232410 | |||
S5‑232411 | pCR 28.907 Rapporteur proposal | Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑232412 | Presentation sheet of TR 28.907 for SA Approval | Huawei | TS or TR cover | Approval | Yes |
Yes
| approved | No | ||||
S5‑232880 | Draft TR 28.907 | Huawei | draft TR | Approval | No |
Yes
| email approval | No | ||||
6.9.1.2 | FS_OAM_eNPN_WoP#2 | S5‑232406 | pCR 28.907 Conclusion for KI management of NPN service customer | Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||
6.9.1.3 | FS_OAM_eNPN_WoP#3 | S5‑232408 | pCR 28.907 Conclusion for KI SLA monitoring and evaluation | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑232881 | |
S5‑232881 | pCR 28.907 Conclusion for KI SLA monitoring and evaluation | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑232408 | |||
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‑232066 | pCR 28.913 Potential solution #2 for KI#4 - EE KPI for V2X | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑232884 | |
S5‑232884 | pCR 28.913 Potential solution #2 for KI#4 - EE KPI for V2X | Huawei, Deutsche Telekom | pCR | Approval | Yes |
Yes
| noted | No | S5‑232066 | |||
S5‑232539 | Add New Key issue on Energy Efficiency of URLLC network slice- RAN based | China Unicom | pCR | Approval | Yes |
Yes
| revised | No | S5‑232711 | |||
S5‑232540 | Add potential solution for Energy Efficiency KPI of URLLC Network Slice based on both latency and reliability | China Unicom | pCR | Approval | Yes |
Yes
| revised | No | S5‑232712 | |||
S5‑232700 | Rel-18 pCR 28.913 Add Conclusion and Recommendation for Key Issue 6 | BEIJING SAMSUNG TELECOM R&D | pCR | Approval | Yes |
Yes
| revised | No | S5‑232883 | |||
S5‑232883 | Rel-18 pCR 28.913 Add Conclusion and Recommendation for Key Issue 6 | BEIJING SAMSUNG TELECOM R&D | pCR | Approval | Yes |
Yes
| noted | No | S5‑232700 | |||
S5‑232711 | Add New Key issue on Energy Efficiency of URLLC network slice- RAN based | China Unicom, China Telecom | pCR | Approval | Yes |
Yes
| noted | No | S5‑232539 | |||
S5‑232882 | Add New Key issue on Energy Efficiency of URLLC network slice- RAN based | China Unicom, China Telecom | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑232712 | Add potential solution for Energy Efficiency KPI of URLLC Network Slice based on both latency and reliability | China Unicom, China Telecom | pCR | Approval | Yes |
Yes
| noted | No | S5‑232540 | |||
6.9.2.2 | FS_EE5G_Ph2_WoP#2 | S5‑232067 | pCR 28.913 Clean up KI#8 - Energy Saving compensation procedure | Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||
S5‑232068 | pCR 28.913 Potential solution for KI#10 - Digital Sobriety | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑232885 | |||
S5‑232885 | pCR 28.913 Potential solution for KI#10 - Digital Sobriety | Huawei, Deutsche Telekom | pCR | Approval | Yes |
Yes
| noted | No | S5‑232068 | |||
S5‑232069 | pCR 28.913 Potential solution for KI#9 | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑232886 | |||
S5‑232886 | pCR 28.913 Potential solution for KI#9 | Huawei,Samsung | pCR | Approval | Yes |
Yes
| noted | No | S5‑232069 | |||
S5‑233169 | Draft TR 28.913 | Huawei | draft TR | Approval | No |
Yes
| email approval | 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‑232656 | Rel-18 pCR 28.829 Completion of 7.1.2.1 | Samsung, EUTC, EDF, BMWK | pCR | Approval | Yes |
Yes
| revised | No | S5‑232850 | |
S5‑232850 | Rel-18 pCR 28.829 Completion of 7.1.2.1 | Samsung, EUTC, EDF, BMWK | pCR | Approval | Yes |
Yes
| approved | No | S5‑232656 | |||
S5‑232658 | Rel-18 pCR 28.829 Clean Up 6.1, 6.3 | Samsung, EUTC, EDF, BMWK | pCR | Approval | Yes |
Yes
| revised | No | S5‑232851 | |||
S5‑232851 | Rel-18 pCR 28.829 Clean Up 6.1, 6.3 | Samsung, EUTC, EDF, BMWK | pCR | Approval | Yes |
Yes
| approved | No | S5‑232658 | |||
S5‑232659 | Rel-18 pCR 28.829 Update 6.4, 6.5, 6.6 | Samsung, EUTC, EDF, BMWK | pCR | Approval | Yes |
Yes
| revised | No | S5‑232852 | |||
S5‑232852 | Rel-18 pCR 28.829 Update 6.4, 6.5, 6.6 | Samsung, EUTC, EDF, BMWK | pCR | Approval | Yes |
Yes
| approved | No | S5‑232659 | |||
6.9.3.5 | FS_NSOEU_WoP#5 |   | ||||||||||
6.9.3.6 | FS_NSOEU_WoP#6 |   | ||||||||||
6.9.3.7 | FS_NSOEU_WoP#7 | S5‑232657 | Rel-18 pCR 28.829 Discontinuing work on objective #2 | Samsung, EUTC, EDF, BMWK | pCR | Approval | Yes |
Yes
| approved | No | ||
S5‑232853 | Draft TR 28.829 | Samsung | draft TR | Approval | No |
Yes
| email approval | No | ||||
6.9.3.8 | FS_NSOEU_WoP#8 |   | ||||||||||
6.9.3.9 | FS_NSOEU_WoP#9 | S5‑232660 | Rel-18 pCR 28.829 – Update 6.7 | Samsung, EUTC, EDF, BMWK | pCR | Approval | Yes |
Yes
| revised | No | S5‑232854 | |
S5‑232854 | Rel-18 pCR 28.829 – Update 6.7 | Samsung, EUTC, EDF, BMWK,Nokia | pCR | Approval | Yes |
Yes
| approved | No | S5‑232660 | |||
S5‑232661 | Rel-18 pCR 28.829 – Update 6.8 | Samsung, EUTC, EDF, BMWK | pCR | Approval | Yes |
Yes
| revised | No | S5‑232856 | |||
S5‑232856 | Rel-18 pCR 28.829 – Update 6.8 | Samsung, EUTC, EDF, BMWK | pCR | Approval | Yes |
Yes
| approved | No | S5‑232661 | |||
S5‑232670 | Rel-18 pCR 28.829 – Update 6.1 | Nokia | pCR | Agreement | Yes |
Yes
| revised | No | S5‑232857 | |||
S5‑232857 | Rel-18 pCR 28.829 – Update 6.1 | Nokia | pCR | Agreement | Yes |
Yes
| approved | No | S5‑232670 | |||
S5‑232671 | Rel-18 pCR 28.829 – Update 6.2 | Nokia | pCR | Agreement | Yes |
Yes
| approved | No | ||||
S5‑232672 | Rel-18 pCR 28.829 – Update 6.3 | Nokia | pCR | Agreement | Yes |
Yes
| revised | No | S5‑232858 | |||
S5‑232858 | Rel-18 pCR 28.829 – Update 6.3 | Nokia | pCR | Agreement | Yes |
Yes
| approved | No | S5‑232672 | |||
S5‑232673 | Rel-18 pCR 28.829 – Update 6.4 | Nokia | pCR | Agreement | Yes |
Yes
| approved | No | ||||
S5‑232674 | Rel-18 pCR 28.829 – Update 6.5 | Nokia | pCR | Agreement | Yes |
Yes
| revised | No | S5‑232859 | |||
S5‑232859 | Rel-18 pCR 28.829 – Update 6.5 | Nokia | pCR | Agreement | Yes |
Yes
| approved | No | S5‑232674 | |||
S5‑232675 | Rel-18 pCR 28.829 – Update 6.6 | Nokia | pCR | Agreement | Yes |
Yes
| approved | No | ||||
S5‑232676 | Rel-18 pCR 28.829 – Update 6.7 | Nokia | pCR | Agreement | Yes |
Yes
| merged | No | S5‑232854 | |||
S5‑232677 | Rel-18 pCR 28.829 – Update 6.8 | Nokia | pCR | Agreement | Yes |
Yes
| revised | No | S5‑232855 | |||
S5‑232855 | Rel-18 pCR 28.829 – Update 6.8 | Nokia | pCR | Agreement | Yes |
Yes
| approved | No | S5‑232677 | |||
S5‑232678 | Rel-18 pCR 28.829 – Update 7 | Nokia | pCR | Agreement | Yes |
Yes
| approved | No | ||||
6.9.3.10 | FS_NSOEU_WoP#10 | S5‑232647 | Rel-18 pCR 28.829 – Key Issue for Energy utility and telecommunication coordinated rapid recovery of energy service | Samsung, EUTC, EDF, BMWK, Deutsche Telekom | pCR | Approval | Yes |
Yes
| revised | No | S5‑232896 | |
S5‑232896 | Rel-18 pCR 28.829 – Key Issue for Energy utility and telecommunication coordinated rapid recovery of energy service | Samsung, EUTC, EDF, BMWK, Deutsche Telekom | pCR | Approval | Yes |
Yes
| approved | No | S5‑232647 | |||
S5‑232649 | Rel-18 pCR 28.829 – Potential Solution for Energy utility and telecommunication coordinated rapid recovery of energy service | Samsung, EUTC, EDF, BMWK, Deutsche Telekom | pCR | Approval | Yes |
Yes
| revised | No | S5‑232897 | |||
S5‑232897 | Rel-18 pCR 28.829 – Potential Solution for Energy utility and telecommunication coordinated rapid recovery of energy service | Samsung, EUTC, EDF, BMWK, Deutsche Telekom | pCR | Approval | Yes |
Yes
| noted | No | S5‑232649 | |||
S5‑232650 | Rel-18 pCR 28.829 – New use case for Rapid Intervention for Outages without Redundant Topology | Samsung, EUTC, EDF, BMWK, Deutsche Telekom | pCR | Approval | Yes |
Yes
| revised | No | S5‑232898 | |||
S5‑232898 | Rel-18 pCR 28.829 – New use case for Rapid Intervention for Outages without Redundant Topology | Samsung, EUTC, EDF, BMWK, Deutsche Telekom | pCR | Approval | Yes |
Yes
| approved | No | S5‑232650 | |||
6.9.3.11 | FS_NSOEU_WoP#11 |   | ||||||||||
6.9.3.12 | FS_NSOEU_WoP#12 |   | ||||||||||
6.9.3.13 | FS_NSOEU_WoP#13 | S5‑232640 | Rel-18 pCR 28.829 – Conclusion and Recommendation for Key Issue 1 - MNO exposes Network Performance Monitoring to DSO | Samsung, EUTC, EDF, BMWK, Deutsche Telekom | pCR | Approval | Yes |
Yes
| revised | No | S5‑232894 | |
S5‑232894 | Rel-18 pCR 28.829 – Conclusion and Recommendation for Key Issue 1 - MNO exposes Network Performance Monitoring to DSO | Samsung, EUTC, EDF, BMWK, Deutsche Telekom | pCR | Approval | Yes |
Yes
| approved | No | S5‑232640 | |||
S5‑232641 | Rel-18 pCR 28.829 – Conclusion and Recommendation for Key Issue i (energy utility and telecommunication coordinated recovery of energy service) | Samsung, EUTC, EDF, BMWK | pCR | Approval | Yes |
Yes
| revised | No | S5‑232895 | |||
S5‑232895 | Rel-18 pCR 28.829 – Conclusion and Recommendation for Key Issue i (energy utility and telecommunication coordinated recovery of energy service) | Samsung, EUTC, EDF, BMWK | pCR | Approval | Yes |
Yes
| approved | No | S5‑232641 | |||
S5‑232652 | Presentation of Report to TSG: TR 28.829, Version 0.6.0 | Samsung | TS or TR cover | Approval | Yes |
Yes
| revised | No | S5‑233064 | |||
S5‑233064 | Presentation of Report to TSG: TR 28.829, Version 1.0.0 | Samsung | TS or TR cover | Approval | Yes |
Yes
| revised | No | S5‑233159 | S5‑232652 | ||
S5‑233159 | Presentation of Report to TSG: TR 28.829, Version 1.0.0 | Samsung | TS or TR cover | Approval | No |
Yes
| email approval | No | S5‑233064 | |||
S5‑232655 | 28829 pCR Annex on NSOEU Applicability | Samsung | pCR | Approval | Yes |
Yes
| revised | No | S5‑233065 | |||
S5‑233065 | 28829 pCR Annex on NSOEU Applicability | Samsung | pCR | Approval | Yes |
YesSamsung clarified that further work was required and the annex would be improved next meeting.
| approved | No | S5‑232655 | |||
S5‑232663 | FS_NSOEU and NSOEU WoP | Samsung | other | Approval | Yes |
Yes
| noted | No | ||||
S5‑233066 | FS_NSOEU and NSOEU WoP | Samsung | other | Approval | No |
Yes
| withdrawn | Yes | ||||
6.9.4 | Study on Key Quality Indicators (KQIs)for 5G service experience |   | ||||||||||
6.9.4.1 | FS_KQI_5G_WoP#1 | S5‑232541 | pCR TR 28.863 Issue #1 Concept of KQI | Huawei | pCR | Approval | Yes |
Yes
| merged | No | S5‑233108 | |
S5‑232668 | pCR TR 28.863 definition of KQI | Nokia | pCR | Agreement | Yes |
Yes
| revised | No | S5‑233108 | |||
S5‑233108 | pCR TR 28.863 definition of KQI | Nokia,Huawei | pCR | Agreement | Yes |
Yes
| noted | No | S5‑232668 | |||
6.9.4.2 | FS_KQI_5G_WoP#2 | S5‑232542 | pCR TR 28.863 Issue3 Video uploading description | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑232866 | |
S5‑232866 | pCR TR 28.863 Issue3 Video uploading description | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑232542 | |||
6.9.4.3 | FS_KQI_5G_WoP#3 | S5‑232545 | pCR TR 28.863 Issue4 Remote control description | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||
S5‑232669 | pCR TR 28.863 definition of Remote controlling | Nokia | pCR | Agreement | Yes |
Yes
| noted | No | ||||
S5‑233170 | Draft TR 28.863 | Huawei | draft TR | Approval | No |
Yes
| email approval | No | ||||
6.9.4.4 | FS_KQI_5G_WoP#4 |   | ||||||||||
6.9.4.5 | FS_KQI_5G_WoP#5 | S5‑232546 | pCR TR 28.863 Issue5 Description of SLS requirements | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||
6.9.5 | Study on Deterministic Communication Service Assurance |   | ||||||||||
6.9.5.1 | FS_DCSA_WoP#1 | S5‑232553 | pCR TR 28.865 Add requirements for DCSA | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑232849 | |
S5‑232849 | pCR TR 28.865 Add requirements for DCSA | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑232553 | |||
S5‑233171 | Draft TR 28.865 | Huawei | draft TR | Approval | No |
Yes
| email approval | No | ||||
6.9.5.2 | FS_DCSA_WoP#2 | S5‑232554 | pCR TR 28.865 Add solution of network capability preparation | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑232889 | |
S5‑232889 | pCR TR 28.865 Add solution of network capability preparation | Huawei | pCR | Approval | Yes |
Yes
| noted | No | S5‑232554 | |||
S5‑232555 | pCR TR 28.865 Add solution of service and network analysis | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑233133 | |||
S5‑233133 | pCR TR 28.865 Add solution of service and network analysis | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑232555 | |||
6.9.5.3 | FS_DCSA_WoP#3 |   | ||||||||||
6.9.5.4 | FS_DCSA_WoP#4 |   | ||||||||||
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 |   | ||||||||||
6.9.6.2 | FS_NSCE_WoP#2 |   | ||||||||||
6.9.6.3 | FS_NSCE_WoP#3 | S5‑232308 | pCR 28.824 Clarify usage of CAPIF-1 and CAPIF-1e | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑232890 | |
S5‑232890 | pCR 28.824 Clarify usage of CAPIF-1 and CAPIF-1e | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑232308 | |||
S5‑233172 | Draft TR 28.824 | Alibaba | draft TR | Approval | No |
Yes
| email approval | No | ||||
6.9.6.4 | FS_NSCE_WoP#4 | S5‑232451 | pCR 28.824 Add Conclusion for network slice management capability exposure via CAPIF | Alibaba (China) Group., Ltd. AsiaInfo | pCR | Approval | No |
Yes
| withdrawn | Yes | ||
S5‑232537 | NaaS ecosystem and 3GPP SA5 work on capability exposure | TELEFONICA S.A., AT&T, Deustche Telekom | discussion | Discussion | Yes |
Yes
| noted | No | ||||
S5‑232538 | SA5 way forward on capability exposure topic | TELEFONICA S.A. | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑232893 | |||
S5‑232893 | SA5 way forward on capability exposure topic | TELEFONICA S.A. | discussion | Endorsement | Yes |
Yes
| endorsed | No | S5‑232538 | |||
S5‑232566 | pCR 28.824 Add Conclusion for network slice management capability exposure via CAPIF | Alibaba Group, AsiaInfo | pCR | Approval | Yes |
Yes
| revised | No | S5‑232900 | |||
S5‑232900 | pCR 28.824 Add Conclusion for network slice management capability exposure via CAPIF | Alibaba Group, AsiaInfo | pCR | Approval | Yes |
Yes
| noted | No | S5‑232566 | |||
S5‑233164 | Draft TR 28.824 | Alibaba | draft TR | Approval | No |
Yes
| email approval | No | ||||
6.9.7 | Study on alignment with ETSI MEC for Edge computing management |   | ||||||||||
6.9.7.1 | FS_MEC_ECM_WoP#1 |   | ||||||||||
6.9.7.2 | FS_MEC_ECM_WoP#2 | S5‑232309 | pCR 28.903 add potential solution for resource reservation | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑232864 | |
S5‑232864 | pCR 28.903 add potential solution for resource reservation | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑232309 | |||
S5‑232310 | pCR 28.903 add potential solution for application LCM with MEC-v2 | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑233046 | |||
S5‑233046 | pCR 28.903 add potential solution for application LCM with MEC-v2 | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑232310 | |||
S5‑232470 | pCR 28.903 Add KI for Federation Management | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑232861 | |||
S5‑232861 | pCR 28.903 Add KI for Federation Management | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑232470 | |||
S5‑232471 | pCR 28.903 NBI Related Key Issues | Samsung R&D Institute UK | pCR | Agreement | Yes |
Yes
| revised | No | S5‑232862 | |||
S5‑232862 | pCR 28.903 NBI Related Key Issues | Samsung R&D Institute UK | pCR | Agreement | Yes |
Yes
| approved | No | S5‑232471 | |||
S5‑232473 | pCR 28.903 NBI Related Solutions | Samsung R&D Institute UK | pCR | Agreement | Yes |
Yes
| revised | No | S5‑232863 | |||
S5‑232863 | pCR 28.903 NBI Related Solutions | Samsung R&D Institute UK | pCR | Agreement | Yes |
Yes
| approved | No | S5‑232473 | |||
S5‑232474 | pCR 28.903 GSMA OP and ECM Concept Mapping | Samsung R&D Institute UK | pCR | Agreement | Yes |
Yes
| revised | No | S5‑232865 | |||
S5‑232865 | pCR 28.903 GSMA OP and ECM Concept Mapping | Samsung R&D Institute UK | pCR | Agreement | Yes |
Yes
| approved | No | S5‑232474 | |||
S5‑232509 | pCR 28.903 EWBI Related Key Issues | Samsung R&D Institute UK | pCR | Agreement | Yes |
Yes
| revised | No | S5‑232860 | |||
S5‑232860 | pCR 28.903 EWBI Related Key Issues | Samsung R&D Institute UK | pCR | Agreement | Yes |
Yes
| approved | No | S5‑232509 | |||
S5‑233173 | Draft TR 28.903 | Huawei | draft TR | Approval | No |
Yes
| email approval | No | ||||
6.10 | Latest draft TS/TR email approvals |   | ||||||||||
7 | Charging |   | ||||||||||
7.1 | Charging Plenary | S5‑232008 | CH agenda and time plan | WG vice Chair (Matrixx Software) | agenda | Yes |
Yes
| revised | No | S5‑232721 | ||
S5‑232721 | CH agenda and time plan | WG vice Chair (Matrixx Software) | agenda | - | Yes |
Yes
| noted | No | S5‑232008 | |||
S5‑232009 | Charging exec report | WG vice Chair (Matrixx Software) | report | Yes |
Yes
| noted | No | |||||
S5‑232019 | LS out Rel17 Reply LS on Enhancement on Charging Identifier Uniqueness Mechanism | C4-225411 | LS in | Yes |
Yes
| postponed | No | |||||
S5‑232023 | Resubmitted LS reply to 3GPP SA2 on shared EHE and HR PDU session with SBO in V-PLMN | GSMA | LS in | Yes |
Yes
| noted | No | |||||
S5‑232029 | Resubmitted LS on shared EHE and HR PDU session with SBO in V-PLMN | S2-2209884 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑232734 | LS Reply on shared EHE and HR PDU session with SBO in V-PLMN | MATRIXX Software | LS out | approval | Yes |
Yes
| approved | No | ||||
S5‑232032 | LS about CHF Logic Realization wrt/ Spending Limits functionality | S2-2301634 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑232244 | Reply LS on CHF Logic Realization wrt/ Spending Limits functionality | China Telecommunications | LS out | Approval | Yes |
Yes
| revised | No | S5‑232735 | |||
S5‑232735 | Reply LS on CHF Logic Realization wrt/ Spending Limits functionality | China Telecommunications | LS out | Approval | Yes |
Yes
| approved | No | S5‑232244 | |||
S5‑232505 | Collection of useful charging endorsed and external communication documents | Huawei | discussion | Agreement | Yes |
Yes
| revised | No | S5‑233031 | |||
S5‑233031 | Collection of useful charging endorsed and external communication documents | Huawei | discussion | Agreement | Yes |
Yes
| endorsed | No | S5‑232505 | |||
S5‑232765 | Reply LS on controlling number of UEs and PDU sessions for NPN | S2-2303687 | LS in | discussion | Yes |
Yes
| noted | No | ||||
S5‑232777 | LS on charging aspects for Ranging/Sidelink Positioning | S2-2303231 | LS in | discussion | Yes |
Yes
| postponed | No | ||||
7.2 | New Charging Work Item proposals | S5‑232142 | New WID on CHF Distributed Availability | Nokia, Nokia Shanghai Bell | WID new | Agreement | Yes |
Yes
| revised | No | S5‑232739 | |
S5‑232739 | New WID on CHF Distributed Availability | Nokia, Nokia Shanghai Bell | WID new | Agreement | Yes |
Yes
| agreed | No | S5‑232142 | |||
S5‑232221 | Revision of SP-221159 WID on Charging Aspects of Network Slicing Phase 2 | MATRIXX Software | WID revised | Approval | Yes |
Yes
| revised | No | S5‑232736 | |||
S5‑232736 | Revision of SP-221159 WID on Charging Aspects of Network Slicing Phase 2 | MATRIXX Software | WID revised | Approval | Yes |
Yes
| agreed | No | S5‑232221 | |||
S5‑232267 | Rescoping of the Study on Structure of Charging for Verticals | VODAFONE Group Plc | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑232430 | New WID on Charging Aspects for Enhanced Support of Non-Public Networks | China Mobile | WID new | Approval | Yes |
Yes
| revised | No | S5‑232737 | |||
S5‑232737 | New WID on Charging Aspects for Enhanced Support of Non-Public Networks | China Mobile | WID new | Approval | Yes |
Yes
| agreed | No | S5‑232430 | |||
S5‑232654 | Decomposing Charging Function by Domain | Amdocs Software Systems Ltd | discussion | Agreement | Yes |
Yes
| noted | No | ||||
S5‑232667 | Rescoping of New Study on Structure of Charging for Verticals | VODAFONE Group Plc | SID revised | Approval | Yes |
Yes
| revised | No | S5‑232738 | |||
S5‑232738 | Rescoping of New Study on Structure of Charging for Verticals | VODAFONE Group Plc | SID revised | Approval | Yes |
Yes
| agreed | No | S5‑232667 | |||
S5‑232800 | New WID on Charging Aspects for NSSAA of Network Slicing Phase 2 | MATRIXX Software | WID new | Agreement | Yes |
Yes
| agreed | No | ||||
7.3 | Charging Maintenance and Rel-18 small Enhancements | S5‑232143 | Rel-18 CR 32.291 IMS Charging Diagnostics | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑233026 | |
S5‑233026 | Rel-18 CR 32.291 IMS Charging Diagnostics | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | S5‑232143 | |||
S5‑232201 | Rel-18 CR 32.291 UsedUnitContainer and MultipleUnitUsage Description Enhancement | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑233030 | |||
S5‑233030 | Rel-18 CR 32.291 UsedUnitContainer and MultipleUnitUsage Description Enhancement | Nokia, Nokia Shanghai Bell | CR | Approval | No |
Yes
| agreed | No | S5‑232201 | |||
S5‑232229 | Rel-17 CR 32.291 Add EAS Deployment Requirements | Amdocs Software Systems Ltd | CR | Approval | Yes |
Yes
| revised | No | S5‑232919 | |||
S5‑232919 | Rel-17 CR 32.291 Add EAS Deployment Requirements | Amdocs Software Systems Ltd | CR | Approval | Yes |
Yes
| agreed | No | S5‑232229 | |||
S5‑232230 | Rel-18 CR 32.291 Add EAS Deployment Requirements | Amdocs Software Systems Ltd | CR | Approval | Yes |
Yes
| revised | No | S5‑232920 | |||
S5‑232920 | Rel-18 CR 32.291 Add EAS Deployment Requirements | Amdocs Software Systems Ltd | CR | Approval | Yes |
Yes
| agreed | No | S5‑232230 | |||
S5‑232231 | Rel-17 32.298 Add Missing RAT Types in CHF CDRs | Amdocs Software Systems Ltd | CR | Approval | Yes |
Yes
| revised | No | S5‑233024 | |||
S5‑233024 | Rel-17 32.298 Add Missing RAT Types in CHF CDRs | Amdocs Software Systems Ltd | CR | Approval | No |
Yes
| agreed | No | S5‑232231 | |||
S5‑232232 | Rel-18 32.298 Add Missing RAT Types in CHF CDRs | Amdocs Software Systems Ltd | CR | Approval | Yes |
Yes
| revised | No | S5‑233025 | |||
S5‑233025 | Rel-18 32.298 Add Missing RAT Types in CHF CDRs | Amdocs Software Systems Ltd | CR | Approval | No |
Yes
| agreed | No | S5‑232232 | |||
S5‑232233 | Rel-17 CR 32.240 Add Missing Consumer in Charging Architecture | Amdocs Software Systems Ltd | CR | Approval | Yes |
Yes
| revised | No | S5‑232946 | |||
S5‑232946 | Rel-17 CR 32.240 Add Missing Consumer in Charging Architecture | Amdocs Software Systems Ltd | CR | Approval | Yes |
Yes
| agreed | No | S5‑232233 | |||
S5‑232234 | Rel-18 32.240 Add Missing Consumer in Charging Architecture | Amdocs Software Systems Ltd | CR | Approval | Yes |
Yes
| revised | No | S5‑233023 | |||
S5‑233023 | Rel-18 32.240 Add Missing Consumer in Charging Architecture | Amdocs Software Systems Ltd | CR | Approval | Yes |
Yes
| agreed | No | S5‑232234 | |||
S5‑232506 | Correct the change of PRA for Roaming | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑232507 | Correction on the YAML | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑232921 | |||
S5‑232921 | Correction on the YAML | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑232507 | |||
S5‑232508 | Correction on the Yaml | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑232923 | |||
S5‑232923 | Correction on the Yaml | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑232508 | |||
S5‑232543 | DP on roaming charging data collection | Nokia, Nokia Shanghai Bell | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑232549 | Rel-18 CR 32.291 Slice-aware charging for Roaming partners | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑232572 | Rel-17 CR 32.255 Correction of UPFId in QBC | Ericsson LM | CR | Agreement | Yes |
Yes
| revised | No | S5‑232924 | |||
S5‑232924 | Rel-17 CR 32.255 Correction of UPFId in QBC | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | S5‑232572 | |||
S5‑232573 | Rel-17 CR 32.291 Correction of UPFId in QBC | Ericsson LM | CR | Agreement | Yes |
Yes
| revised | No | S5‑232925 | |||
S5‑232925 | Rel-17 CR 32.291 Correction of UPFId in QBC | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | S5‑232573 | |||
S5‑232574 | Rel-18 CR 32.291 Correction of UPFId in QBC | Ericsson LM | CR | Agreement | Yes |
Yes
| revised | No | S5‑232926 | |||
S5‑232926 | Rel-18 CR 32.291 Correction of UPFId in QBC | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | S5‑232574 | |||
S5‑232575 | Rel-17 CR 32.298 Correction of UPFId in QBC | Ericsson LM | CR | Agreement | Yes |
Yes
| revised | No | S5‑232927 | |||
S5‑232927 | Rel-17 CR 32.298 Correction of UPFId in QBC | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | S5‑232575 | |||
S5‑232576 | Rel-18 CR 32.298 Correction of UPFId in QBC | Ericsson LM | CR | Agreement | Yes |
Yes
| revised | No | S5‑232928 | |||
S5‑232928 | Rel-18 CR 32.298 Correction of UPFId in QBC | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | S5‑232576 | |||
S5‑232577 | Rel-17 CR 32.255 Inconsistent use of charging identifier | Ericsson LM | CR | Agreement | Yes |
Yes
| revised | No | S5‑232929 | |||
S5‑232929 | Rel-17 CR 32.255 Inconsistent use of charging identifier | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | S5‑232577 | |||
S5‑232578 | Rel-18 CR 32.291 Correction of quota management indicator | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑232579 | Rel-18 CR 32.254 Correcting supported feature and charging identifier | Ericsson LM | CR | Agreement | Yes |
Yes
| revised | No | S5‑232930 | |||
S5‑232930 | Rel-18 CR 32.254 Correcting supported feature and charging identifier | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | S5‑232579 | |||
S5‑232580 | Rel-18 CR 32.254 Missing operation and identifier in NEF charging information | Ericsson LM | CR | Agreement | Yes |
Yes
| revised | No | S5‑232931 | S5‑226659 | ||
S5‑232931 | Rel-18 CR 32.254 Missing operation and identifier in NEF charging information | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | S5‑232580 | |||
S5‑232581 | Rel-18 CR 32.291 Missing operation and identifier in NEF charging information | Ericsson LM | CR | Agreement | Yes |
Yes
| revised | No | S5‑232932 | S5‑226419 | ||
S5‑232932 | Rel-18 CR 32.291 Missing operation and identifier in NEF charging information | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | S5‑232581 | |||
S5‑232582 | Rel-18 CR 32.298 Missing operation and identifier in NEF charging information | Ericsson LM | CR | Agreement | Yes |
Yes
| revised | No | S5‑232933 | S5‑226420 | ||
S5‑232933 | Rel-18 CR 32.298 Missing operation and identifier in NEF charging information | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | S5‑232582 | |||
S5‑232583 | Rel-18 CR 32.291 Correction of QBC roaming | Ericsson LM | CR | Agreement | Yes |
Yes
| withdrawn | Yes | ||||
S5‑232691 | Rel-17 CR 32.240 Fixing IRP definitions | CATT | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑232692 | Rel-18 CR 32.240 Fixing IRP definitions | CATT | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑232731 | Rel-16 CR 32.291 Update OpenAPI version | Huawei | other | Agreement | No |
Yes
| withdrawn | Yes | ||||
S5‑232732 | Rel-17 CR 32.291 Update OpenAPI version | Huawei | CR | Agreement | No |
Yes
| email approval | No | ||||
S5‑232733 | Rel-18 CR 32.291 Update OpenAPI version | Huawei | CR | Agreement | No |
Yes
| email approval | No | ||||
S5‑232922 | Rel-18 CR 32.291 Correction on the Yaml for EDGE charging | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑233027 | Rel-18 CR 32.298 IMS Charging Diagnostics | Nokia | other | Agreement | No |
Yes
| withdrawn | Yes | ||||
S5‑233028 | Rel-18 CR 32.260 IMS Charging Diagnostics | Nokia | other | Agreement | No |
Yes
| withdrawn | Yes | ||||
S5‑233029 | Rel-18 CR 32.275 IMS Charging Diagnostics | Nokia | other | Agreement | No |
Yes
| withdrawn | Yes | ||||
7.4 | Rel-18 Charging |   | ||||||||||
7.4.1 | Charging Aspects of Network Slicing Phase 2 | S5‑232092 | Rel-18 TS 28.203 v0.0.0 Initial skeleton | MATRIXX Software | draft TS | Approval | Yes |
Yes
| agreed | No | ||
S5‑232093 | Rel-18 pCR 28.203 Introduction of the Reference | MATRIXX Software | pCR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑232094 | Rel-18 pCR 28.203 Introduction of the Scope | MATRIXX Software | pCR | Approval | Yes |
Yes
| revised | No | S5‑232740 | |||
S5‑232740 | Rel-18 pCR 28.203 Introduction of the Scope | MATRIXX Software | pCR | Approval | Yes |
Yes
| approved | No | S5‑232094 | |||
S5‑232215 | Rel-18 pCR 28.203 Introduction of the Terms | MATRIXX Software | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑232216 | Rel-18 pCR 28.203 Introduction of the Abbreviations | MATRIXX Software | pCR | Approval | Yes |
Yes
| revised | No | S5‑232741 | |||
S5‑232741 | Rel-18 pCR 28.203 Introduction of the Abbreviations | MATRIXX Software | pCR | Approval | No |
Yes
| approved | No | S5‑232216 | |||
S5‑232722 | Draft TS 28.203 | MATRIXX Software | draft TS | Approval | No |
Yes
| email approval | No | ||||
7.5 | Charging studies |   | ||||||||||
7.5.1 | Study on charging aspects for enhancements of Network Slicing Phase 2 | S5‑232200 | Questions and comments related to Charging Aspects for Network Slicing | VODAFONE Group Plc | discussion | Discussion | Yes |
Yes
| noted | No | ||
S5‑232217 | Rel-18 pCR 32.847 Solve Editor's Note in Key issue#6 | MATRIXX Software | pCR | Approval | Yes |
Yes
| revised | No | S5‑232742 | |||
S5‑232742 | Rel-18 pCR 32.847 Solve Editor's Note in Key issue#6 | MATRIXX Software | pCR | Approval | Yes |
Yes
| approved | No | S5‑232217 | |||
S5‑232218 | Rel-18 pCR 32.847 Refinements on conclusions for Key issue#6 | MATRIXX Software | pCR | Approval | Yes |
Yes
| revised | No | S5‑232743 | |||
S5‑232743 | Rel-18 pCR 32.847 Refinements on conclusions for Key issue#6 | MATRIXX Software | pCR | Approval | Yes |
Yes
| approved | No | S5‑232218 | |||
S5‑232219 | Rel-18 pCR 32.847 Correction on pCR implementation | MATRIXX Software | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑232220 | Presentation of TR 32.847 for approval | MATRIXX Software | TS or TR cover | Approval | Yes |
Yes
| revised | No | S5‑232744 | |||
S5‑232744 | Presentation of TR 32.847 for approval | MATRIXX Software | TS or TR cover | Approval | Yes |
Yes
| approved | No | S5‑232220 | |||
S5‑232222 | Rel-18 pCR 32.847 Notes addition | VODAFONE Group Plc | pCR | Approval | Yes |
Yes
| revised | No | S5‑232745 | |||
S5‑232745 | Rel-18 pCR 32.847 Notes addition | VODAFONE Group Plc | pCR | Approval | Yes |
Yes
| approved | No | S5‑232222 | |||
S5‑232315 | Rel-18 pCR 32.847 Solution for Key Issue #9 Network Slice Charging by the Tenant | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑232746 | |||
S5‑232746 | Rel-18 pCR 32.847 Solution for Key Issue #9 Network Slice Charging by the Tenant | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑232315 | |||
S5‑232723 | Draft TR TR 32.847 | MATRIXX Software | draft TR | Approval | No |
Yes
| email approval | No | ||||
7.5.2 | Study on Nchf charging services phase 2 | S5‑232141 | Rel-18 pCR 28.826 Solution for Key issue#1f and #1g | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑232820 | |
S5‑232820 | Rel-18 pCR 28.826 Solution for Key issue#1f and #1g | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑232141 | |||
S5‑232475 | Rel-18 pCR 28.826 Add the potential solution for Common IEs applied | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑232747 | |||
S5‑232747 | Rel-18 pCR 28.826 Add the potential solution for Common IEs applied | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑232475 | |||
S5‑232476 | Rel-18 pCR 28.826 Add the solution for reporting depending on the triggers | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑232748 | |||
S5‑232748 | Rel-18 pCR 28.826 Add the solution for reporting depending on the triggers | Huawei | pCR | Agreement | Yes |
Yes
| noted | No | S5‑232476 | |||
S5‑232477 | Rel-18 pCR 28.826 Clarify the solution 1.1 | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑232749 | |||
S5‑232749 | Rel-18 pCR 28.826 Clarify the solution 1.1 | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑232477 | |||
S5‑232478 | Rel-18 pCR 28.826 Correction on the potential solutions for key issue #1l | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑232750 | |||
S5‑232750 | Rel-18 pCR 28.826 Correction on the potential solutions for key issue #1l | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑232478 | |||
S5‑232479 | Rel-18 pCR 28.826 Add the solution for Bitrate charging | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑232798 | |||
S5‑232798 | Rel-18 pCR 28.826 Add the solution for Bitrate charging | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑232479 | |||
S5‑232480 | Rel-18 pCR 28.826 Evaluation and Conclusion | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑232819 | |||
S5‑232819 | Rel-18 pCR 28.826 Evaluation and Conclusion | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑232480 | |||
S5‑232556 | Rel-18 pCR 28.826 Solution for Key issues #1f and #1g (Essential CDR) | Nokia, Nokia Shanghai Bell | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑232584 | Rel-18 pCR 28.826 Correcting use cases and key issues in clause 5.1 | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑232585 | Rel-18 pCR 28.826 Adding service identifier based solution to clause 5.3 | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑232799 | |||
S5‑232799 | Rel-18 pCR 28.826 Adding service identifier based solution to clause 5.3 | Ericsson LM | pCR | Approval | Yes |
Yes
| noted | No | S5‑232585 | |||
S5‑232586 | Rel-18 pCR 28.826 Adding solutions to undefined attribute handling in CDR | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑232801 | |||
S5‑232801 | Rel-18 pCR 28.826 Adding solutions to undefined attribute handling in CDR | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑232586 | |||
S5‑232587 | Rel-18 pCR 28.826 Adding use case requested units and quota management indication | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑232802 | |||
S5‑232802 | Rel-18 pCR 28.826 Adding use case requested units and quota management indication | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑232587 | |||
S5‑232588 | Rel-18 pCR 28.826 Additional evaluation to clause 5.1 | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑232805 | |||
S5‑232805 | Rel-18 pCR 28.826 Additional evaluation to clause 5.1 | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑232588 | |||
S5‑232589 | Rel-18 pCR 28.826 Solving termination action issue | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑232797 | |||
S5‑232797 | Rel-18 pCR 28.826 Solving termination action issue | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑232589 | |||
S5‑232590 | Rel-18 pCR 28.826 Additional evaluation to clause 5.3 | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑232816 | |||
S5‑232816 | Rel-18 pCR 28.826 Additional evaluation to clause 5.3 | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑232590 | |||
S5‑232591 | Rel-18 pCR 28.826 Updating solution in clause 5.4 | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑232804 | |||
S5‑232804 | Rel-18 pCR 28.826 Updating solution in clause 5.4 | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑232591 | |||
S5‑232592 | Rel-18 pCR 28.826 Additional evaluation in clause 5.4 | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑232817 | |||
S5‑232817 | Rel-18 pCR 28.826 Additional evaluation in clause 5.4 | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑232592 | |||
S5‑232593 | Rel-18 pCR 28.826 Adding evaluation to clause 5.2 | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑232806 | |||
S5‑232806 | Rel-18 pCR 28.826 Adding evaluation to clause 5.2 | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑232593 | |||
S5‑232594 | Rel-18 pCR 28.826 Adding solution to clause 5.1 on location accuracy | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑232803 | |||
S5‑232803 | Rel-18 pCR 28.826 Adding solution to clause 5.1 on location accuracy | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑232594 | |||
S5‑232595 | Rel-18 pCR 28.826 Add evaluation to clause 5.5 of solution #5.6 | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑232818 | |||
S5‑232818 | Rel-18 pCR 28.826 Add evaluation to clause 5.5 of solution #5.6 | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑232595 | |||
S5‑232724 | Draft TR TR 28.826 | Ericsson | draft TR | Approval | No |
Yes
| email approval | No | ||||
7.5.3 | Study on 5G roaming charging architecture for wholesale and retail scenarios | S5‑232481 | Rel-18 pCR 28.827 Minor corrections | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | ||
S5‑232482 | Rel-18 pCR 28.827 Clarification on SMS related solutions | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑232821 | |||
S5‑232821 | Rel-18 pCR 28.827 Clarification on SMS related solutions | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑232482 | |||
S5‑232483 | Rel-18 pCR 28.827 Correction on solution #1.4 | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑232822 | |||
S5‑232822 | Rel-18 pCR 28.827 Correction on solution #1.4 | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑232483 | |||
S5‑232484 | Rel-18 pCR 28.827 Corrections on solution #1.11 | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑232934 | |||
S5‑232934 | Rel-18 pCR 28.827 Corrections on solution #1.11 | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑232484 | |||
S5‑232485 | Rel-18 pCR 28.827 EN removal and clarification in solution #2.10 | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑232935 | |||
S5‑232935 | Rel-18 pCR 28.827 EN removal and clarification in solution #2.10 | Huawei | pCR | Agreement | Yes |
Yes
| noted | No | S5‑232485 | |||
S5‑232486 | Rel-18 pCR 28.827 Conclusion of clause 7.1 | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑232939 | |||
S5‑232939 | Rel-18 pCR 28.827 Conclusion of clause 7.1 | Huawei | pCR | Agreement | Yes |
Yes
| noted | No | S5‑232486 | |||
S5‑232487 | Rel-18 pCR 28.827 Conclusion of clause 7.2 | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑232941 | |||
S5‑232941 | Rel-18 pCR 28.827 Conclusion of clause 7.2 | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑232487 | |||
S5‑232488 | Rel-18 pCR 28.827 Enhancement of solution #5.1 | Huawei | pCR | Agreement | Yes |
Yes
| merged | No | S5‑232943 | |||
S5‑232596 | Rel-18 pCR 28.827 Adding evaluation of solutions for clause 7.1 | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑232938 | |||
S5‑232938 | Rel-18 pCR 28.827 Adding evaluation of solutions for clause 7.1 | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑232596 | |||
S5‑232597 | Rel-18 pCR 28.827 Correcting solution #1.11 in clause 7.1 | Ericsson LM | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑232598 | Rel-18 pCR 28.827 Adding solution in clause 7.1 for PDU session triggers | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑232936 | |||
S5‑232936 | Rel-18 pCR 28.827 Adding solution in clause 7.1 for PDU session triggers | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑232598 | |||
S5‑232599 | Rel-18 pCR 28.827 Adding solution in clause 7.1 for QoS flow session triggers | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑232937 | |||
S5‑232937 | Rel-18 pCR 28.827 Adding solution in clause 7.1 for QoS flow session triggers | Ericsson LM | pCR | Approval | Yes |
Yes
| noted | No | S5‑232599 | |||
S5‑232600 | Rel-18 pCR 28.827 Additional evaluation of solutions for clause 7.2 | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑232940 | |||
S5‑232940 | Rel-18 pCR 28.827 Additional evaluation of solutions for clause 7.2 | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑232600 | |||
S5‑232601 | Rel-18 pCR 28.827 Additional evaluation of solutions for clause 7.4 | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑232942 | |||
S5‑232942 | Rel-18 pCR 28.827 Additional evaluation of solutions for clause 7.4 | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑232601 | |||
S5‑232602 | Rel-18 pCR 28.827 Additional solutions for key issue #5d in clause 7.5 | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑232943 | |||
S5‑232943 | Rel-18 pCR 28.827 Additional solutions for key issue #5d in clause 7.5 | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑232602 | |||
S5‑232603 | Rel-18 pCR 28.827 Additional solution for key issue #5f in clause 7.5 | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑232945 | |||
S5‑232945 | Rel-18 pCR 28.827 Additional solution for key issue #5f in clause 7.5 | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑232603 | |||
S5‑232604 | Rel-18 pCR 28.827 Additional solutions for key issue #5e in clause 7.5 | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑232944 | |||
S5‑232944 | Rel-18 pCR 28.827 Additional solutions for key issue #5e in clause 7.5 | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑232604 | |||
S5‑232605 | Rel-18 pCR 28.827 Adding solution in clause 7.6 for UE usage information reporting | Ericsson LM | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑232725 | Draft TR TR 28.827 | Ericsson | draft TR | Approval | No |
Yes
| email approval | No | ||||
7.5.4 | Study on Charging Aspects for Enhanced support of Non-Public Networks | S5‑232420 | Rel-18 pCR 28.828 Solve Editor's Note in SNPN topic 2 | China Mobile | pCR | Approval | Yes |
Yes
| revised | No | S5‑232829 | |
S5‑232829 | Rel-18 pCR 28.828 Solve Editor's Note in SNPN topic 2 | China Mobile | pCR | Approval | Yes |
Yes
| approved | No | S5‑232420 | |||
S5‑232421 | Rel-18 pCR 28.828 Correction on solution #2 for PNI-NPN topic 1 | China Mobile | pCR | Approval | Yes |
Yes
| revised | No | S5‑232823 | |||
S5‑232823 | Rel-18 pCR 28.828 Correction on solution #2 for PNI-NPN topic 1 | China Mobile | pCR | Approval | Yes |
Yes
| approved | No | S5‑232421 | |||
S5‑232422 | Rel-18 pCR 28.828 Solve Editor's Note in PNI-NPN topic 1 | China Mobile | pCR | Approval | Yes |
Yes
| revised | No | S5‑232824 | |||
S5‑232824 | Rel-18 pCR 28.828 Solve Editor's Note in PNI-NPN topic 1 | China Mobile | pCR | Approval | Yes |
Yes
| approved | No | S5‑232422 | |||
S5‑232423 | Rel-18 pCR 28.828 Correction on conclusion for SNPN topic 2 | China Mobile | pCR | Approval | Yes |
Yes
| revised | No | S5‑232825 | |||
S5‑232825 | Rel-18 pCR 28.828 Correction on conclusion for SNPN topic 2 | China Mobile | pCR | Approval | Yes |
Yes
| approved | No | S5‑232423 | |||
S5‑232424 | Rel-18 pCR 28.828 Correction on conclusion for PNI-NPN topic 1 | China Mobile | pCR | Approval | Yes |
Yes
| revised | No | S5‑232826 | |||
S5‑232826 | Rel-18 pCR 28.828 Correction on conclusion for PNI-NPN topic 1 | China Mobile | pCR | Approval | Yes |
Yes
| approved | No | S5‑232424 | |||
S5‑232425 | Rel-18 pCR 28.828 Add converged charging for data connectivity in PNI-NPN | China Mobile | pCR | Approval | Yes |
Yes
| revised | No | S5‑232832 | |||
S5‑232832 | Rel-18 pCR 28.828 Add converged charging for data connectivity in PNI-NPN | China Mobile | pCR | Approval | Yes |
Yes
| approved | No | S5‑232425 | |||
S5‑232426 | Rel-18 pCR 28.828 Update conclusions and recommendations | China Mobile | pCR | Approval | Yes |
Yes
| revised | No | S5‑232833 | |||
S5‑232833 | Rel-18 pCR 28.828 Update conclusions and recommendations | China Mobile | pCR | Approval | Yes |
Yes
| approved | No | S5‑232426 | |||
S5‑232428 | Presentation of TR 28.828 for approval | China Mobile | TS or TR cover | Approval | Yes |
Yes
| approved | No | ||||
S5‑232489 | Rel-18 pCR 28.828 Remove editor's note for the Topic 1 | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑232828 | |||
S5‑232828 | Rel-18 pCR 28.828 Remove editor's note for the Topic 1 | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑232489 | |||
S5‑232490 | Rel-18 pCR 28.828 Remove editor's note for the Topic 3 | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑232831 | |||
S5‑232831 | Rel-18 pCR 28.828 Remove editor's note for the Topic 3 | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑232490 | |||
S5‑232491 | Rel-18 pCR 28.828 Correction on the solution 3 in the Topic 1 | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑232827 | |||
S5‑232827 | Rel-18 pCR 28.828 Correction on the solution 3 in the Topic 1 | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑232491 | |||
S5‑232492 | Rel-18 pCR 28.828 Correction on the solution 2 in the Topic 3 | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑232830 | |||
S5‑232830 | Rel-18 pCR 28.828 Correction on the solution 2 in the Topic 3 | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑232492 | |||
S5‑232726 | Draft TR 28.828 | China Mobile | draft TR | Approval | No |
Yes
| email approval | No | ||||
7.5.5 | Study on Time Sensitive Networking charging | S5‑232493 | Rel-18 pCR 28.839 Add Use Case for Enablers for Time Sensitive Communications | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑232834 | |
S5‑232834 | Rel-18 pCR 28.839 Add Use Case for Enablers for Time Sensitive Communications | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑232493 | |||
S5‑232494 | Rel-18 pCR 28.839 Add Use Case for Time Sensitive Communication | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑232835 | |||
S5‑232835 | Rel-18 pCR 28.839 Add Use Case for Time Sensitive Communication | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑232494 | |||
S5‑232495 | Rel-18 pCR 28.839 Add Use Case for TSN 5GS bridge Charging | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑232836 | |||
S5‑232836 | Rel-18 pCR 28.839 Add Use Case for TSN 5GS bridge Charging | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑232495 | |||
S5‑232496 | Rel-18 pCR TR 28.839 Add solution for the Network Exposure Charging | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑232837 | |||
S5‑232837 | Rel-18 pCR TR 28.839 Add solution for the Network Exposure Charging | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑232496 | |||
S5‑232727 | draft TR 28.839 | Huawei | draft TR | Approval | No |
Yes
| email approval | No | ||||
7.5.6 | Study on CHF Segmentation | S5‑232095 | Rel-18 TR 28.840 Initial skeleton (v0.0.0) | Nokia, Nokia Shanghai Bell | draft TR | Approval | Yes |
Yes
| approved | No | ||
S5‑232096 | Rel-18 pCR 28.840 Update of the Reference | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑232097 | Rel-18 pCR 28.840 Update of the Scope | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑232918 | |||
S5‑232918 | Rel-18 pCR 28.840 Update of the Scope | Nokia, Nokia Shanghai Bell | pCR | Approval | No |
Yes
| approved | No | S5‑232097 | |||
S5‑232728 | Draft TR 28.840 | Nokia | draft TR | Approval | No |
Yes
| email approval | No | ||||
7.5.7 | Study on Structure of Charging for Verticals | S5‑232497 | Rel-18 pCR TR28.843 v0.0.0 Initial skeleton | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | ||
S5‑232498 | Rel-18 pCR TR28.843 Update of the Skeleton | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑232840 | |||
S5‑232840 | Rel-18 pCR TR28.843 Update of the Skeleton | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑232498 | |||
S5‑232499 | Rel-18 pCR TR28.843 Update of the Scope | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑232841 | |||
S5‑232841 | Rel-18 pCR TR28.843 Update of the Scope | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑232499 | |||
S5‑232500 | Rel-18 pCR TR28.843 Update of the Reference | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑232842 | |||
S5‑232842 | Rel-18 pCR TR28.843 Update of the Reference | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑232500 | |||
S5‑232501 | Rel-18 pCR TR28.843 Addition of Charging Specification Reference Consideration | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑232843 | |||
S5‑232843 | Rel-18 pCR TR28.843 Addition of Charging Specification Reference Consideration | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑232501 | |||
S5‑232502 | Rel-18 pCR TR28.843 Addition of General description for background | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑232844 | |||
S5‑232844 | Rel-18 pCR TR28.843 Addition of General description for background | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑232502 | |||
S5‑232503 | Rel-18 pCR TR28.843 Addition of the Business Roles | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑232845 | |||
S5‑232845 | Rel-18 pCR TR28.843 Addition of the Business Roles | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑232503 | |||
S5‑232504 | Rel-18 pCR TR28.843 Addition of the key issue for consideration | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑232917 | |||
S5‑232917 | Rel-18 pCR TR28.843 Addition of the key issue for consideration | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑232504 | |||
S5‑232729 | Draft TR 28.843 | Charging | draft TR | Approval | No |
Yes
| email approval | No | ||||
7.5.8 | Study on charging aspects of Satellite in 5GS | S5‑232514 | 3GPP TR 28.844-000 initial skeleton | CATT | draft TR | Agreement | Yes |
Yes
| revised | No | S5‑232839 | |
S5‑232839 | 3GPP TR 28.844-000 initial skeleton | CATT | draft TR | Agreement | Yes |
Yes
| approved | No | S5‑232514 | |||
S5‑232515 | Add the skeleton to TR 28.844 | CATT | pCR | Agreement | Yes |
Yes
| approved | No | ||||
S5‑232516 | Add scope and reference to TR 28.844 | CATT | pCR | Agreement | Yes |
Yes
| revised | No | S5‑232838 | |||
S5‑232838 | Add scope and reference to TR 28.844 | CATT | pCR | Agreement | Yes |
Yes
| approved | No | S5‑232516 | |||
S5‑232730 | Draft TR TR 28.844 | CATT | draft TR | Approval | No |
Yes
| email approval | No | ||||
8 | Any Other Business |   | ||||||||||
9 | Closing of the meeting |   |