Tdoc List
2023-10-17 16:04
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‑236200 | Agenda | WG Chair | agenda | Yes |
Yes
| approved | No | |||
3 | IPR and legal declaration | S5‑236201 | IPR and legal declaration | WG Chair | other | Yes |
Yes
| noted | No | |||
4 | Meetings and activities reports |   | ||||||||||
4.1 | Last SA5 meeting report | S5‑236202 | 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‑236203 | Post e-meeting email approval status | WG Vice Chair (Ericsson) | other | No |
No
| reserved | No | |||
S5‑236213 | SA5 working procedures | WG Chair | other | Yes |
Yes
| merged | No | S5‑236926 | ||||
S5‑236254 | Update on SA5 working procedures | Nokia, Nokia Shanghai Bell, Ericsson | other | Approval | Yes |
Yes
| revised | No | S5‑236926 | |||
S5‑236926 | Update on SA5 working procedures | Nokia, Nokia Shanghai Bell, Ericsson | other | Approval | Yes |
Yes
| approved | No | S5‑236254 | |||
S5‑236217 | Process for management of draft TS-TRs | WG Chair | discussion | Yes |
Yes
| noted | No | |||||
S5‑236214 | SA5 Meeting facility requirements | WG Chair | other | Yes |
Yes
| approved | No | |||||
S5‑236570 | Rel-18 & Rel-19 time plan proposal | SA5 Chair | Work Plan | Information | Yes |
Yes
| revised | No | S5‑237057 | S5‑235580 | ||
S5‑237057 | Rel-18 & Rel-19 time plan proposal | SA5 Chair | Work Plan | Information | Yes |
Yes
| noted | No | S5‑236570 | |||
5.2 | Technical issues at SA5 level | S5‑236351 | Using Forge for SA5 | Nokia, Nokia Shanghai Bell | other | Presentation | Yes |
Yes
| noted | No | ||
5.3 | Liaison statements at SA5 level | S5‑236220 | IETF HTTP RFCs obsoleted by RFCs 9110, 9111 and 9113 | C4-233513 | LS in | Yes |
Yes
| postponed | No | |||
S5‑236937 | Reply to: IETF HTTP RFCs obsoleted by RFCs 9110, 9111 and 9113 | Nokia | LS out | approval | No |
Yes
| withdrawn | Yes | ||||
S5‑236231 | LS to SA, SA3 and SA5 on potential collaboration between 3GPP SA3/SA5 and ETSI SAI ISG | ETSI ISG SAI | LS in | Yes |
Yes
| postponed | No | |||||
S5‑236884 | LS to 3GPP re Monitoring of Encrypted 5GS Signalling Traffic | GSMA | LS in | Discussion | Yes |
Yes
| postponed | No | ||||
5.4 | SA5 meeting calendar | S5‑236218 | SA5 meeting calendar | WG Chair | other | Yes |
Yes
| noted | No | |||
6 | OAM&P |   | ||||||||||
6.1 | OAM&P Plenary | S5‑236204 | OAM&P action list | WG Vice Chair (Nokia) | other | No |
Yes
| noted | No | |||
S5‑236205 | OAM meeting process | WG Vice Chair (Ericsson) | other | Yes |
Yes
| noted | No | |||||
S5‑236206 | agenda_with_Tdocs_sequence_proposal_OAM | WG Chair | agenda | No |
Yes
| noted | No | |||||
S5‑236207 | OAM Exec Report | WG Vice Chair (Nokia) | report | No |
Yes
| noted | No | |||||
S5‑236208 | OAM Chair notes and conclusions | WG Chair | report | No |
Yes
| noted | No | |||||
S5‑236211 | Collection of external communication documents in OAM | WG Vice Chair (Nokia) | discussion | Yes |
Yes
| noted | No | |||||
S5‑236215 | Collection of Rel-18 3GPP SA5 OAM WoP | WG Chair | discussion | Yes |
Yes
| noted | No | |||||
S5‑236216 | Living document for stage 2-3 alignment | WG Vice Chair (Ericsson) | discussion | No |
Yes
| email approval | No | |||||
S5‑236219 | Time Plan for OAM&P sessions | WG Chair | other | No |
Yes
| noted | No | |||||
S5‑236221 | Liaison Statement to 3GPP SA5 | ETSI TC EE | LS in | Yes |
Yes
| replied to | No | |||||
S5‑236222 | LS on user consent for SON/MDT for NB-IoT UEs | R2-2309030 | LS in | Yes |
Yes
| postponed | No | |||||
S5‑236223 | LS on MDT measurements collection in MR-DC | R3-232070 | LS in | Yes |
Yes
| postponed | No | |||||
S5‑236927 | Reply to: LS on MDT measurements collection in MR-DC | Samsung | LS out | approval | Yes |
Yes
| noted | No | ||||
S5‑236224 | LS on QoE measurement collection for application sessions delivered via MBS broadcast or multicast | R3-233457 | LS in | Yes |
Yes
| postponed | No | |||||
S5‑236225 | Reply LS on QoE measurement collection for application sessions delivered via MBS broadcast or multicast | S4-231491 | LS in | Yes |
Yes
| noted | No | |||||
S5‑236226 | Reply LS on area scope for QoE measurements | S4-231490 | LS in | Yes |
Yes
| postponed | No | |||||
S5‑236227 | Reply LS on area scope for QoE measurements | R3-234746 | LS in | Yes |
Yes
| noted | No | |||||
S5‑236228 | LS on MDT for NPN | R3-234744 | LS in | Yes |
Yes
| postponed | No | |||||
S5‑236229 | LS on QMC support in RRC_IDLE and RRC_INACTIVE | R3-234745 | LS in | Yes |
Yes
| noted | No | |||||
S5‑236232 | LS on information about the progress of draft Recommendation ITU-T Y.AN-Arch-fw ""Architecture Framework for Autonomous Networks"" | ITU-T SG13 | LS in | Yes |
Yes
| noted | No | |||||
S5‑236233 | ZSM work on AI enablers and intent-driven autonomous networks | ETSI ISG ZSM | LS in | Yes |
Yes
| replied to | No | |||||
S5‑236234 | LS on NCR Solutions | R3-225253 | LS in | Yes |
Yes
| noted | No | |||||
S5‑236235 | Reply LS on RAN UE Id optionality | R3-233476 | LS in | Yes |
Yes
| noted | No | |||||
S5‑236929 | Reply to: Reply LS on RAN UE Id optionality | Ericsson | LS out | approval | No |
Yes
| withdrawn | Yes | ||||
S5‑236236 | LS on REl-18 work on architecture for enabling Edge Applications | S6-232197 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑236933 | Reply to: LS on REl-18 work on architecture for enabling Edge Applications | Samsung | LS out | approval | Yes |
Yes
| revised | No | S5‑237241 | |||
S5‑237241 | Reply to: LS on REl-18 work on architecture for enabling Edge Applications | Samsung | LS out | approval | Yes |
Yes
| approved | No | S5‑236933 | |||
S5‑236512 | Reply to Liaison Statement from ETSI EE PS | Huawei Tech.(UK) Co.. Ltd | LS out | Approval | Yes |
Yes
| revised | No | S5‑236930 | |||
S5‑236930 | Reply to Liaison Statement from ETSI EE PS | Huawei Tech.(UK) Co.. Ltd | LS out | Approval | Yes |
Yes
| approved | No | S5‑236512 | |||
S5‑236547 | Reply LS to ZSM Work on AI enablers and intent-driven autonomous networks | Intel | LS out | Approval | No |
Yes
| email approval | No | ||||
S5‑236768 | Reply LS on user consent of Non-public Network | Ericsson LM | LS out | Yes |
Yes
| revised | No | S5‑236771 | ||||
S5‑236771 | LS on user consent of Non-public Network | Ericsson LM | LS out | Agreement | Yes |
Yes
| revised | No | S5‑236928 | S5‑236768 | ||
S5‑236928 | LS on user consent of Non-public Network | Ericsson LM | LS out | Agreement | Yes |
Yes
| approved | No | S5‑236771 | |||
S5‑236781 | LS on the progress update of AI/ML Management specifications in SA5 | NEC, Intel | LS out | Agreement | Yes |
Yes
| revised | No | S5‑236932 | |||
S5‑236932 | LS on the progress update of AI/ML Management specifications in SA5 | NEC, Intel | LS out | Approval | Yes |
Yes
| noted | No | S5‑236781 | |||
S5‑236787 | DP highlighting areas of potential overlap between SA5 and other working group | NEC, Intel | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑236871 | LS on issues with Packet Uu Loss Rate with delay threshold in the DL per DRB per UE | Samsung Electronics Czech | LS out | Yes |
Yes
| noted | No | |||||
S5‑237222 | LS on issues with Packet Uu Loss Rate with delay threshold in the DL per DRB per UE | Samsung Electronics Czech | LS out | - | No |
Yes
| withdrawn | Yes | ||||
S5‑236878 | Liaison Multi-SDO Autonomous Networks (AN) Formal Liaison: Call for Candidate Proposals for AN SDO Information Sharing | TM Forum | LS in | Yes |
Yes
| postponed | No | |||||
S5‑236880 | Discussion Paper on Service Management for Rel-19 | Telefonica Germany GmbH, Huawei, Deustche Telekom | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑237203 | |||
S5‑237203 | Discussion Paper on Service Management for Rel-19 | Telefónica, Huawei, Deutsche Telekom, Ericsson | discussion | Endorsement | Yes |
Yes
| endorsed | No | S5‑236880 | |||
S5‑236931 | Collection of useful endorsed documents in OAM | WG Vice Chair (Nokia( | discussion | discussion | Yes |
Yes
| noted | No | ||||
S5‑237186 | Rel-19 OAM topic Progress in SA5#151 | WG Chair | discussion | Information | No |
Yes
| noted | No | ||||
6.2 | New OAM&P Work Item proposals |   | ||||||||||
6.2.1 | Intelligence and Automation | S5‑236546 | New Rel-19 SID Study on AI and ML management phase 2 | Intel, NEC | SID new | Discussion | Yes |
Yes
| revised | No | S5‑237204 | |
S5‑237204 | New Rel-19 SID Study on AI and ML management phase 2 | Intel, NEC | SID new | Discussion | Yes |
Yes
| revised | No | S5‑237224 | S5‑236546 | ||
S5‑237224 | New Rel-19 SID Study on AI and ML management phase 2 | Intel, NEC | SID new | Discussion | Yes |
Yes
| noted | No | S5‑237204 | |||
S5‑236592 | New SID on Closed Control Loop Management | Samsung R&D Institute India | SID new | Agreement | Yes |
Yes
| noted | No | ||||
S5‑237206 | New SID on Closed Control Loop Management | Samsung R&D Institute India | SID new | Agreement | Yes |
Yes
| noted | No | ||||
S5‑236763 | Report of SA5 Rel-19 23Q3 moderated discussion – EZTO | China Mobile | report | Information | Yes |
Yes
| noted | No | ||||
S5‑236764 | New SID on effectiveness of zero-touch orchestration and management | China Mobile, China Telecomunication | SID new | Agreement | Yes |
Yes
| revised | No | S5‑237225 | |||
S5‑237225 | New SID on effectiveness of zero-touch orchestration and management | China Mobile, China Telecomunication | SID new | Agreement | Yes |
Yes
| noted | No | S5‑236764 | |||
S5‑236790 | New SID Study on Management Data Analytics (MDA) – Phase 3 | NEC, Intel | SID new | Agreement | Yes |
Yes
| revised | No | S5‑237205 | |||
S5‑237205 | New SID Study on Management Data Analytics (MDA) – Phase 3 | NEC, Intel | SID new | Agreement | Yes |
Yes
| noted | No | S5‑236790 | |||
S5‑236804 | New SID on Management aspect of Network Digital Twin | China Mobile Group Device Co. | SID new | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑236807 | New Rel-19 Study on intent driven management services for mobile networks phase 3 | Huawei | SID new | Approval | Yes |
Yes
| revised | No | S5‑237207 | |||
S5‑237207 | New Rel-19 Study on intent driven management services for mobile networks phase 3 | Huawei | SID new | Approval | Yes |
Yes
| revised | No | S5‑237226 | S5‑236807 | ||
S5‑237226 | New Rel-19 Study on intent driven management services for mobile networks phase 3 | Huawei | SID new | Approval | Yes |
Yes
| noted | No | S5‑237207 | |||
S5‑236812 | Status report on SA5 Rel-19 23Q3 moderated discussion - Management Data Analytics (MDA) - phase 3 | NEC | report | Information | Yes |
Yes
| noted | No | ||||
S5‑236816 | Report of SA5 Rel-19 23Q3 moderated discussion – IDMS_MN_ph3 | Huawei (Moderator) | report | Information | Yes |
Yes
| noted | No | ||||
S5‑236830 | New SID on data management, subscriptions and reporting | Ericsson | SID new | Yes |
Yes
| noted | No | |||||
S5‑236832 | New WID on Provide management functions for Rel-19 traffic and radio functions in the RAN and the core network | Ericsson | WID new | Yes |
Yes
| noted | No | |||||
S5‑236838 | New SID on Management aspect of Network Digital Twin | China Mobile Group Device Co. | SID new | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑236839 | New SID on Management aspect of Network Digital Twin | China Mobile Group Device Co. | SID new | Approval | Yes |
Yes
| revised | No | S5‑237208 | |||
S5‑237208 | New SID on Management aspect of Network Digital Twin | China Mobile Group Device Co. | SID new | Approval | Yes |
Yes
| revised | No | S5‑237227 | S5‑236839 | ||
S5‑237227 | New SID on Management aspect of Network Digital Twin | China Mobile Group Device Co. | SID new | Approval | Yes |
Yes
| noted | No | S5‑237208 | |||
S5‑236847 | Report of SA5 Rel-19 23Q3 moderated discussion | Nokia | report | Information | Yes |
Yes
| noted | No | ||||
S5‑236852 | Report of SA5 Rel-19 23Q3 moderated discussion - AI/ML management phase 2 | Intel | report | Information | Yes |
Yes
| noted | No | ||||
S5‑236873 | Report of SA5 Rel-19 23Q3 moderated discussion - CCL | Samsung R&D Institute India | report | Agreement | Yes |
Yes
| noted | No | ||||
S5‑236879 | Report of SA5 Rel-19 23Q3 moderated discussion - Digital Twin aspects of management | China Mobile Group Device Co. | discussion | Yes |
Yes
| noted | No | |||||
S5‑237220 | BO_MoM-5 Rel-19_Breakout-1_minutes | Nokia | other | discussion | Yes |
Yes
| noted | No | ||||
6.2.2 | Management Architecture and Mechanisms | S5‑236253 | TS28.541 Rel18 Move normative OpenAPI code to Forge | Nokia, Nokia Shanghai Bell, Ericsson | CR | Approval | Yes |
Yes
| revised | No | S5‑236962 | |
S5‑236962 | TS28.541 Rel18 Move normative OpenAPI code to Forge | Nokia, Nokia Shanghai Bell, Ericsson | CR | Approval | Yes |
Yes
| agreed | No | S5‑236253 | |||
S5‑236257 | Rel-18 CR 28.541 Move normative YANG code to Forge | Ericsson India Private Limited | CR | Approval | Yes |
Yes
| merged | No | S5‑236962 | |||
S5‑236261 | Rel-18 CR 28.623 Move normative YANG code to Forge | Ericsson India Private Limited | CR | Approval | Yes |
Yes
| revised | No | S5‑236963 | |||
S5‑236963 | Rel-18 CR 28.623 Move normative YANG and YAML code to Forge | Ericsson India Private Limited | CR | Approval | Yes |
Yes
| agreed | No | S5‑236261 | |||
S5‑236266 | DP Migrating code to Forge Step1 | Ericsson India Private Limited | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑236350 | Revised WID on 5G Advanced NRM features phase 2 (adNRM_ph2) | Nokia, Nokia Shanghai Bell | WID revised | Approval | Yes |
Yes
| revised | No | S5‑236961 | |||
S5‑236961 | Revised WID on 5G Advanced NRM features phase 2 (adNRM_ph2) | Nokia, Nokia Shanghai Bell | WID revised | Approval | Yes |
Yes
| agreed | No | S5‑236350 | |||
S5‑236451 | New SID on SBMA enhancement phase 3 | Huawei | SID new | Agreement | Yes |
Yes
| revised | No | S5‑237209 | |||
S5‑237209 | New SID on SBMA enhancement phase 3 | Huawei | SID new | Agreement | Yes |
Yes
| revised | No | S5‑237228 | S5‑236451 | ||
S5‑237228 | New SID on SBMA enhancement phase 3 | Huawei | SID new | Agreement | Yes |
Yes
| noted | No | S5‑237209 | |||
S5‑236452 | Report of SA5 Rel-19 23Q3 moderated discussion – SBMA (continuation) | Huawei | report | Information | Yes |
Yes
| noted | No | ||||
S5‑236567 | New Study on Enhancement of Management Aspects Related to NWDAF Phase 2 | China Telecomunication Corp. | SID new | Approval | Yes |
Yes
| revised | No | S5‑237213 | |||
S5‑237213 | New Study on Enhancement of Management Aspects Related to NWDAF Phase 2 | China Telecomunication Corp. | SID new | Approval | Yes |
Yes
| revised | No | S5‑237229 | S5‑236567 | ||
S5‑237229 | New Study on Enhancement of Management Aspects Related to NWDAF Phase 2 | China Telecomunication Corp. | SID new | Approval | Yes |
Yes
| noted | No | S5‑237213 | |||
S5‑236568 | Rel-19 New SID on Plan and transaction management | Nokia, Nokia Shanghai Bell | SID new | Approval | Yes |
Yes
| revised | No | S5‑237215 | |||
S5‑237215 | Rel-19 New SID on Plan and transaction management | Nokia, Nokia Shanghai Bell | SID new | Approval | Yes |
Yes
| revised | No | S5‑237230 | S5‑236568 | ||
S5‑237230 | Rel-19 New SID on Plan and transaction management | Nokia, Nokia Shanghai Bell | SID new | Approval | No |
Yes
| noted | No | S5‑237215 | |||
S5‑236648 | New_SID_Enablers_for_Security_Monitoring | Nokia UK | SID new | Approval | Yes |
Yes
| revised | No | S5‑237237 | |||
S5‑237237 | New_SID_Enablers_for_Security_Monitoring | Nokia UK | SID new | Approval | Yes |
Yes
| noted | No | S5‑236648 | |||
S5‑236755 | New SID on Management Aspects of NTN Phase 2 | CATT,China Unicom | SID new | Approval | Yes |
Yes
| revised | No | S5‑237210 | |||
S5‑237210 | New SID on Management Aspects of NTN Phase 2 | CATT,China Unicom | SID new | Approval | Yes |
Yes
| revised | No | S5‑237231 | S5‑236755 | ||
S5‑237231 | New SID on Management Aspects of NTN Phase 2 | CATT,China Unicom | SID new | Approval | Yes |
Yes
| noted | No | S5‑237210 | |||
S5‑236758 | Moderator status report for Management aspect of NWDAF Phase 2 | China Telecomunication Corp. | discussion | Approval | Yes |
Yes
| noted | No | ||||
S5‑236770 | Moderator status report for 5G PM&KPls and 5G NRM and QoE collection | China Telecomunication Corp. | discussion | Yes |
Yes
| noted | No | |||||
S5‑236773 | Report of SA5 Rel-19 23Q3 moderated discussion – NTN_OAM_Phase2 | CATT | report | Information | Yes |
Yes
| noted | No | ||||
S5‑236774 | New WID on Management aspects of 5G system with satellite backhaul | CATT | WID new | Approval | Yes |
Yes
| revised | No | S5‑237211 | |||
S5‑237211 | New WID on Management aspects of 5G system with satellite backhaul | CATT | WID new | Approval | Yes |
Yes
| agreed | No | S5‑236774 | |||
S5‑236809 | New SID on Management of IAB Nodes | Ericsson Telecomunicazioni SpA | SID new | Approval | Yes |
Yes
| revised | No | S5‑237232 | |||
S5‑237232 | New SID on Management of IAB Nodes | Ericsson Telecomunicazioni SpA | SID new | Approval | Yes |
Yes
| noted | No | S5‑236809 | |||
S5‑236827 | New WID on Support for Subscriber and Equipment Trace and QoE collection functionality in RAN and core network | Ericsson | WID new | No |
Yes
| withdrawn | Yes | |||||
S5‑236829 | New WID on Support for Subscriber and Equipment Trace and QoE collection functionality in RAN and core network | Ericsson | WID new | Yes |
Yes
| noted | No | |||||
S5‑236835 | Discussion on management aspects of 5G system with satellite backhaul | China Telecom Corporation Ltd. | discussion | Yes |
Yes
| noted | No | |||||
S5‑236858 | Report of SA5 Rel-19 23Q3 moderated discussion-Cloud aspects of management and orchestration | Microsoft Europe SARL | report | Information | Yes |
Yes
| noted | No | ||||
S5‑236859 | New SID on Management of Network Sharing Phase 3 | China Unicom, China Telecom | SID new | Approval | Yes |
Yes
| revised | No | S5‑237212 | |||
S5‑237212 | New SID on Management of Network Sharing Phase 3 | China Unicom, China Telecom | SID new | Approval | Yes |
Yes
| revised | No | S5‑237233 | S5‑236859 | ||
S5‑237233 | New SID on Management of Network Sharing Phase 3 | China Unicom, China Telecom | SID new | Approval | Yes |
Yes
| noted | No | S5‑237212 | |||
S5‑236860 | Report of SA5 Rel-19 23Q3 moderated discussion Management of Network Sharing | China Unicom | report | Information | Yes |
Yes
| noted | No | ||||
S5‑236861 | New SID on cloud aspects of management and orchestration | Microsoft Europe SARL | SID new | Agreement | Yes |
Yes
| revised | No | S5‑237234 | |||
S5‑237234 | New SID on cloud aspects of management and orchestration | Microsoft Europe SARL | SID new | Agreement | Yes |
Yes
| noted | No | S5‑236861 | |||
S5‑236881 | Moderator report for Data Management | Ericsson France S.A.S | discussion | Yes |
Yes
| noted | No | |||||
S5‑236882 | Report of SA5_Rel-19_23Q3_moderated_discussion_-_Management_of_IAB_nodes-v0.0.2 | Ericsson Telecomunicazioni SpA | discussion | Yes |
Yes
| noted | No | |||||
S5‑236883 | New WID on Migrating code to Forge Step1 | Ericsson India Private Limited | WID new | Yes |
Yes
| noted | No | |||||
S5‑236925 | SA5 Rel-19 23Q3 moderated discussion – Management aspects of Integrated Sensing and Communication - Version 0.0.4 | ZTE | discussion | discussion | Yes |
Yes
| noted | No | ||||
S5‑237217 | BO_MoM-2 S Forge_Migration discussion | Nokia | other | discussion | Yes |
Yes
| noted | No | ||||
6.2.3 | Support of New Services | S5‑236520 | New SID on energy efficiency and energy saving aspects of 5G networks and services | Huawei Tech.(UK) Co.. Ltd | SID new | Agreement | Yes |
Yes
| revised | No | S5‑237214 | |
S5‑237214 | New SID on energy efficiency and energy saving aspects of 5G networks and services | Huawei Tech.(UK) Co.. Ltd | SID new | Agreement | Yes |
Yes
| revised | No | S5‑237235 | S5‑236520 | ||
S5‑237235 | New SID on energy efficiency and energy saving aspects of 5G networks and services | Huawei Tech.(UK) Co.. Ltd | SID new | Agreement | Yes |
Yes
| noted | No | S5‑237214 | |||
S5‑236521 | Report of SA5 Rel-19 23Q3 moderated discussion – 5GEE | Huawei Tech.(UK) Co.. Ltd | report | Information | Yes |
Yes
| noted | No | ||||
S5‑236793 | New SID on Management aspects of Integrated Sensing and Communication | ZTE Corporation,China Unicom | SID new | Agreement | Yes |
Yes
| revised | No | S5‑237236 | |||
S5‑237236 | New SID on Management aspects of Integrated Sensing and Communication | ZTE Corporation,China Unicom | SID new | Agreement | Yes |
Yes
| noted | No | S5‑236793 | |||
S5‑236853 | New SID on management aspects of RedCap feature | AsiaInfo | SID new | Yes |
Yes
| noted | No | |||||
S5‑236854 | Report of SA5 Rel-19 23Q3 moderated discussion Management aspects of RedCap feature | AsiaInfo | report | Yes |
Yes
| noted | No | |||||
6.3 | OAM&P Maintenance and Rel-18 small Enhancements |   | ||||||||||
6.3.1 | Methodology | S5‑236315 |
Rel-18 CR TS 32.156 Supplement the specification for establishing a relationship between < | China Mobile Com. Corporation | CR | Agreement | Yes |
Yes
| revised | No | S5‑237121 | |
S5‑237121 |
Rel-18 CR TS 32.156 Supplement the specification for establishing a relationship between < | China Mobile Com. Corporation | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑236315 | |||
6.3.2 | ANL |   | ||||||||||
6.3.3 | MDAS | S5‑236321 | Rel-17_CR_28104_Correct issues for AnalyticsSchedule datatype | ZTE Corporation | CR | Approval | Yes |
Yes
| withdrawn | Yes | ||
S5‑236322 | Rel-18_CR_28104_Correct issues for AnalyticsSchedule datatype | ZTE Corporation | CR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑236323 | Rel-17_CR_28104_Correct issues for MDA information model | ZTE Corporation | CR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑236324 | Rel-18_CR_28104_Correct issues for MDA information model | ZTE Corporation | CR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑236515 | Correct issues for AnalyticsSchedule datatype | ZTE Corporation | CR | Approval | Yes |
Yes
| revised | No | S5‑237122 | |||
S5‑237122 | Correct issues for AnalyticsSchedule datatype | ZTE Corporation | CR | Approval | Yes |
Yes
| agreed | No | S5‑236515 | |||
S5‑236516 | Correct issues for AnalyticsSchedule datatype | ZTE Corporation | CR | Approval | Yes |
Yes
| revised | No | S5‑237123 | |||
S5‑237123 | Correct issues for AnalyticsSchedule datatype | ZTE Corporation | CR | Approval | Yes |
Yes
| agreed | No | S5‑236516 | |||
S5‑236517 | Rel-17_CR_28104_Correct issues for MDA information model | ZTE Corporation | CR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑236518 | Rel-18 CR TS 28.104 Correcting | ZTE Corporation | CR | Approval | Yes |
Yes
| revised | No | S5‑237124 | |||
S5‑237124 | Rel-18 CR TS 28.104 Correcting | ZTE Corporation | CR | Approval | Yes |
Yes
| agreed | No | S5‑236518 | |||
S5‑236519 | Rel-17 CR TS 28.104 Correcting | ZTE Corporation | CR | Approval | Yes |
Yes
| revised | No | S5‑237125 | |||
S5‑237125 | Rel-17 CR TS 28.104 Correcting | ZTE Corporation | CR | Approval | Yes |
Yes
| agreed | No | S5‑236519 | |||
6.3.4 | AI/ML | S5‑236360 | 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‑236361 | Rel-18 CR TS 28.105 Adding the missing relation between ML entity and ML process | Nokia, Nokia Shangai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑237164 | |||
S5‑237164 | Rel-18 CR TS 28.105 Adding the missing relation between ML entity and ML process | Nokia, Nokia Shangai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑236361 | |||
S5‑236393 | Correction on ModelPerformance | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑237126 | |||
S5‑237126 | Correction on ModelPerformance | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑236393 | |||
S5‑236394 | Rel-18 CR 28.105 correction on ModelPerformace | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑237127 | |||
S5‑237127 | Rel-18 CR 28.105 correction on ModelPerformace | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑236394 | |||
S5‑236479 | Rel-17 CR TS 28.105 Corrections of ML training related use cases description | Huawei | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑236480 | Rel-18 CR TS 28.105 Corrections of ML training related use cases description | Huawei | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑236501 | Rel18 Input to draft CR TS28.105 information on ML training convergence | Nokia Italy | draftCR | Yes |
Yes
| approved | No | |||||
S5‑236522 | Rel-18 Input to draft CR TS 28.105 ML inference policy-based activation | Nokia Italy | draftCR | Yes |
Yes
| noted | No | |||||
S5‑236664 | Rel 17 CR TS 28.105 Remove unused decision entity term | Ericsson | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑236665 | Rel 18 CR TS 28.105 Remove unused decision entity term | Ericsson | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑236747 | Rel 17 CR TS 28.105 Clarify the description of confidenceIndication attribute | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑237128 | Rel 17 CR TS 28.105 Clarify the description of confidenceIndication attribute | Nokia, Nokia Shanghai Bell | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑236748 | Rel 18 CR TS 28.105 Clarify the description of confidenceIndication attribute | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑237129 | Rel 18 CR TS 28.105 Clarify the description of confidenceIndication attribute | Nokia, Nokia Shanghai Bell | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑236849 | Rel 17 CR TS 28.105 Remove unused attribute mLEntityList | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑236850 | Rel 18 CR TS 28.105 Remove unused attribute mLEntityList | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
6.3.5 | Energy efficiency |   | ||||||||||
6.3.6 | Intent driven management | S5‑236268 | Rel-17 CR TS 28.312 Correct the Relationship UML diagram for intent | China Mobile Com. Corporation | CR | Approval | Yes |
Yes
| agreed | No | ||
S5‑236269 | Rel-17 CR TS 28.312 Correct issues for redefined Objectcontext in OpenAPI document | China Mobile Com. Corporation | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑236302 | Rel-17 CR TS28.312 Correct issues for area related attributes definition in stage2 and stage3 | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑236303 | Rel-18 CR TS28.312 Correct issues for area related attributes definition in stage2 and stage3 | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑236833 | |||
S5‑236304 | Rel-17 CR TS28.312 Correct stage2 issues for Edge Service Support Expectation | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑236834 | |||
S5‑236396 | Clarification on intent management procedure | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑236397 | Clarification on intent management procedure | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑236423 | Rel-17 CR TS 28.312 Update the definition of expectationId in Table 6.2.1.4-1 | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑237130 | |||
S5‑237130 | Rel-17 CR TS 28.312 Update the definition of expectationId in Table 6.2.1.4-1 | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑236423 | |||
S5‑236424 | Rel-18 CR TS 28.312 Update the definition of expectationId in Table 6.2.1.4-1 | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑236836 | |||
S5‑236789 | Modify expectationId to expectationName | China Mobile Com. Corporation | CR | Agreement | Yes |
Yes
| merged | No | S5‑237131 | |||
S5‑236795 | Modify expectationId to expectationName | China Mobile Com. Corporation | CR | Agreement | Yes |
Yes
| merged | No | S5‑237130 | |||
S5‑236808 |
Rel-17 CR TS28.312 Correct the description for Context < | China Mobile Com. Corporation | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑236811 | Rel-18 CR TS 28.312 Correct the description for Context dataType | China Mobile Com. Corporation | CR | Agreement | Yes |
Yes
| revised | No | S5‑237132 | |||
S5‑237132 | Rel-18 CR TS 28.312 Correct the description for Context dataType | China Mobile Com. Corporation | CR | Agreement | Yes |
Yes
| agreed | No | S5‑236811 | |||
S5‑236833 | Rel-18 CR TS28.312 Correct issues for area related attributes definition in stage2 and stage3 | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑236303 | |||
S5‑236834 | Rel-17 CR TS28.312 Correct stage2 issues for Edge Service Support Expectation | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑236304 | |||
S5‑236836 | Rel-18 CR TS 28.312 Update the definition of expectationId in Table 6.2.1.4-1 | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑237131 | S5‑236424 | ||
S5‑237131 | Rel-18 CR TS 28.312 Update the definition of expectationId in Table 6.2.1.4-1 | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑236836 | |||
6.3.7 | SON | S5‑236473 | Rel-17 CR TS 28.313 correction of performance measurements for MRO | Huawei | CR | Approval | Yes |
Yes
| agreed | No | ||
S5‑236474 | Rel-16 CR TS 28.313 correction of performance measurements for MRO | Huawei | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑236475 | Rel-17 CR TS 28.313 correction performance measurements for CHO and DAPS MRO | Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑237133 | |||
S5‑237133 | Rel-17 CR TS 28.313 correction performance measurements for CHO and DAPS MRO | Huawei | CR | Approval | Yes |
Yes
| agreed | No | S5‑236475 | |||
6.3.8 | QMC |   | ||||||||||
6.3.9 | Network slicing management | S5‑236305 | Rel-18 CR TS28.531 Update procedure of feasibility check and reservation of NSI and NSSI to align with FeasibilityCheckAndReservationJob | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑237134 | |
S5‑237134 | Rel-18 CR TS28.531 Update procedure of feasibility check and reservation of NSI and NSSI to align with FeasibilityCheckAndReservationJob | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑236305 | |||
S5‑236328 | Rel-18 CR TS 28.531 Clarify initiation of Procedure of Network Slice Instance Deallocation | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑237136 | |||
S5‑237136 | Rel-18 CR TS 28.531 Clarify initiation of Procedure of Network Slice Instance Deallocation | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑236328 | |||
S5‑236329 | Rel-18 CR TS 28.531 Clarify initiation of Procedure of network slice subnet instance deallocation | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑237137 | |||
S5‑237137 | Rel-18 CR TS 28.531 Clarify initiation of Procedure of network slice subnet instance deallocation | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑236329 | |||
S5‑236330 | Rel-18 CR TS 28.531 Clarify initiation of Procedure of Network Slice Instance Modification | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑237138 | |||
S5‑237138 | Rel-18 CR TS 28.531 Clarify initiation of Procedure of Network Slice Instance Modification | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑236330 | |||
S5‑236331 | Rel-18 CR TS 28.531 Clarify initiation of Procedure of Network Slice Subnet Instance Modification | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑237139 | |||
S5‑237139 | Rel-18 CR TS 28.531 Clarify initiation of Procedure of Network Slice Subnet Instance Modification | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑236331 | |||
S5‑236341 | Rel-18 CR TS 28.531 Corrections to description of Procedure of Network Slice Instance and Network Slice Subnet Instance allocations | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑236416 | Add missing scenario for network slice provisioning | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑236045 | |||
S5‑236417 | Add missing scenario for network slice provisioning | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑236046 | |||
S5‑236688 | Rel-16 CR TS 28.541 Clarify the role of jitter as attribute in service profile | L.M. Ericsson Limited, Deutsche Telekom AG | CR | Approval | Yes |
Yes
| not pursued | No | S5‑235072 | |||
S5‑236689 | Rel-17 CT TS 28542 Clarify the role of jitter as attribute in service profile | L.M. Ericsson Limited, Deutsche Telekom AG | CR | Approval | Yes |
Yes
| not pursued | No | S5‑235073 | |||
S5‑236690 | Rel-18 CR TS 28.541 Clarify the role of jitter as attribute in service profile | L.M. Ericsson Limited, Deutsche Telekom AG | CR | Approval | Yes |
Yes
| not pursued | No | S5‑235074 | |||
S5‑236798 | Correction of NEFFunction and Sliceprofile | Ericsson India Private Limited | CR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑236799 | Correction of NEFFunction and Sliceprofile | Ericsson India Private Limited | CR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
6.3.10 | MEC management | S5‑236401 | Correction on performance assurance | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑237140 | |
S5‑237140 | Correction on performance assurance | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑236401 | |||
S5‑236402 | Rel-18 CR 28.538 correction on Performance Assurance | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑237141 | |||
S5‑237141 | Rel-18 CR 28.538 correction on Performance Assurance | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑236402 | |||
S5‑236801 | Correction of 5GC NF measurements to evaluate EAS performance | China Telecom, Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑236805 | Correction of 5GC NF measurements to evaluate EAS performance | China Telecom, Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
6.3.11 | General NRM | S5‑236247 | TS28.541 Rel17 correction to stage3 of NROperatorCellDU containment | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||
S5‑236248 | TS28.541 Rel18 correction to stage3 of NROperatorCellDU containment | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑236249 | TS28.541 Rel17 correction to NPNIdentity stage2 stage 3 issue | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑236250 | TS28.541 Rel18 correction to NPNIdentity stage2 stage 3 issue | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑236259 | Rel17 CR 32.160 Correct YANG mapping of isInvariant | Ericsson India Private Limited | CR | Approval | Yes |
Yes
| revised | No | S5‑237081 | |||
S5‑237081 | Rel17 CR 32.160 Correct YANG mapping of isInvariant | Ericsson India Private Limited | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑236260 | Rel18 CR 32.160 Correct YANG mapping of isInvariant | Ericsson India Private Limited | CR | Approval | Yes |
Yes
| revised | No | S5‑237144 | |||
S5‑237144 | Rel18 CR 32.160 Correct YANG mapping of isInvariant | Ericsson India Private Limited | CR | Approval | Yes |
Yes
| agreed | No | S5‑236260 | |||
S5‑236262 | Rel-17 CR 32.160 Clarify YANG Vendor extensions | Ericsson India Private Limited | CR | Approval | Yes |
Yes
| revised | No | S5‑237145 | |||
S5‑237145 | Rel-17 CR 32.160 Clarify YANG Vendor extensions | Ericsson India Private Limited | CR | Approval | Yes |
Yes
| agreed | No | S5‑236262 | |||
S5‑236263 | Rel-18 CR 32.160 Clarify YANG Vendor extensions | Ericsson India Private Limited | CR | Approval | Yes |
Yes
| revised | No | S5‑237146 | |||
S5‑237146 | Rel-18 CR 32.160 Clarify YANG Vendor extensions | Ericsson India Private Limited | CR | Approval | Yes |
Yes
| agreed | No | S5‑236263 | |||
S5‑236344 | TS28.541 Rel16 correction to data type property for aMFIdentifier & aMFSetId & aMFRegionId and sD | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑237198 | |||
S5‑237198 | TS28.541 Rel16 correction to data type property for aMFIdentifier & aMFSetId & aMFRegionId and sD | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑236344 | |||
S5‑236345 | TS28.541 Rel17 correction to data type property for aMFIdentifier & aMFSetId & aMFRegionId and sD | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑237199 | |||
S5‑237199 | TS28.541 Rel17 correction to data type property for aMFIdentifier & aMFSetId & aMFRegionId and sD | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑236345 | |||
S5‑236346 | TS28.541 Rel18 correction to data type property for aMFIdentifier & aMFSetId & aMFRegionId and sD | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑237200 | |||
S5‑237200 | TS28.541 Rel18 correction to data type property for aMFIdentifier & aMFSetId & aMFRegionId and sD | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑236346 | |||
S5‑236352 | Rel-17 CR 28.623 YANG Corrections and inVariant | Ericsson India Private Limited | CR | Approval | Yes |
Yes
| revised | No | S5‑237147 | |||
S5‑237147 | Rel-17 CR 28.623 YANG Corrections and inVariant | Ericsson India Private Limited | CR | Approval | Yes |
Yes
| agreed | No | S5‑236352 | |||
S5‑236353 | Rel-17 CR 28.541 YANG Corrections and inVariant | Ericsson India Private Limited | CR | Approval | Yes |
Yes
| revised | No | S5‑237088 | |||
S5‑237088 | Rel-17 CR 28.541 YANG Corrections and inVariant | Ericsson India Private Limited | CR | Approval | Yes |
Yes
| agreed | No | S5‑236353 | |||
S5‑236354 | Rel-18 CR 28.623 YANG Corrections and inVariant | Ericsson India Private Limited | CR | Approval | Yes |
Yes
| revised | No | S5‑237148 | |||
S5‑237148 | Rel-18 CR 28.623 YANG Corrections and inVariant | Ericsson India Private Limited | CR | Approval | Yes |
Yes
| agreed | No | S5‑236354 | |||
S5‑236355 | Rel-18 CR 28.541 YANG Corrections and inVariant | Ericsson India Private Limited | CR | Approval | Yes |
Yes
| revised | No | S5‑236947 | |||
S5‑236947 | Rel-18 CR 28.541 YANG Corrections and inVariant | Ericsson India Private Limited | CR | Approval | Yes |
Yes
| agreed | No | S5‑236355 | |||
S5‑236373 | Rel-17 CR TS 28.541 Correct issues for the attribute with the ENUM type for NR NRM fragment | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑237149 | |||
S5‑237149 | Rel-17 CR TS 28.541 Correct issues for the attribute with the ENUM type for NR NRM fragment | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑236373 | |||
S5‑236374 | Rel-18 CR TS 28.541 Correct issues for the attribute with the ENUM type for NR NRM fragment | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑237150 | |||
S5‑237150 | Rel-18 CR TS 28.541 Correct issues for the attribute with the ENUM type for NR NRM fragment | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑236374 | |||
S5‑236464 | Rel-15 CR TS 32.156 Clarifying Terminology | Ericsson Limited | CR | Agreement | Yes |
Yes
| revised | No | S5‑237151 | |||
S5‑237151 | Rel-15 CR TS 32.156 Clarifying Terminology | Ericsson, Nokia, Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑236464 | |||
S5‑236466 | Rel-16 CR TS 32.156 Clarifying Terminology | Ericsson Limited | CR | Agreement | Yes |
Yes
| revised | No | S5‑237152 | |||
S5‑237152 | Rel-16 CR TS 32.156 Clarifying Terminology | Ericsson, Nokia, Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑236466 | |||
S5‑236467 | Rel-17 CR TS 32.156 Clarifying Terminology | Ericsson Limited | CR | Agreement | Yes |
Yes
| revised | No | S5‑237153 | |||
S5‑237153 | Rel-17 CR TS 32.156 Clarifying Terminology | Ericsson, Nokia, Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑236467 | |||
S5‑236470 | Rel-18 CR TS 32.156 Clarifying Terminology | Ericsson Limited | CR | Agreement | Yes |
Yes
| revised | No | S5‑237154 | |||
S5‑237154 | Rel-18 CR TS 32.156 Clarifying Terminology | Ericsson, Nokia, Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑236470 | |||
S5‑236743 | Rel-16 CR 28.622 Correction of IOC ManagedNFService attribute values | Ericsson Limited | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑236744 | Rel-17 CR 28.622 Correction of IOC ManagedNFService attribute values | Ericsson Limited | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑236745 | Rel-18 CR 28.622 Correction of IOC ManagedNFService attribute values | Ericsson Limited | CR | Agreement | Yes |
Yes
| agreed | No | ||||
6.3.12 | PM/KPI | S5‑236356 | Rel-15 CR TS 28.550 Removal of updateStreamInfo operation | Nokia, Nokia Shanghai Bell, Intel, Mavenir | CR | Approval | Yes |
Yes
| revised | No | S5‑237155 | |
S5‑237155 | Rel-15 CR TS 28.550 Removal of updateStreamInfo operation | Nokia, Nokia Shanghai Bell, Intel, Mavenir,Ericsson | CR | Approval | Yes |
Yes
| agreed | No | S5‑236356 | |||
S5‑236357 | Rel-16 CR TS 28.550 Removal of updateStreamInfo operation | Nokia, Nokia Shanghai Bell, Intel, Mavenir | CR | Approval | Yes |
Yes
| revised | No | S5‑237156 | |||
S5‑237156 | Rel-16 CR TS 28.550 Removal of updateStreamInfo operation | Nokia, Nokia Shanghai Bell, Intel, Mavenir,Ericsson | CR | Approval | Yes |
Yes
| agreed | No | S5‑236357 | |||
S5‑236358 | Rel-17 CR TS 28.550 Removal of updateStreamInfo operation | Nokia, Nokia Shanghai Bell, Intel, Mavenir | CR | Approval | Yes |
Yes
| revised | No | S5‑237157 | |||
S5‑237157 | Rel-17 CR TS 28.550 Removal of updateStreamInfo operation | Nokia, Nokia Shanghai Bell, Intel, Mavenir,Ericsson | CR | Approval | Yes |
Yes
| agreed | No | S5‑236358 | |||
S5‑236359 | Rel-18 CR TS 28.550 Removal of updateStreamInfo operation | Nokia, Nokia Shanghai Bell, Intel, Mavenir | CR | Approval | Yes |
Yes
| revised | No | S5‑237158 | |||
S5‑237158 | Rel-18 CR TS 28.550 Removal of updateStreamInfo operation | Nokia, Nokia Shanghai Bell, Intel, Mavenir,Ericsson | CR | Approval | Yes |
Yes
| agreed | No | S5‑236359 | |||
S5‑236549 | Discussion Paper on how to handle undefined PM streaming operation | Ericsson Inc. | discussion | Decision | Yes |
Yes
| noted | No | ||||
S5‑236749 | Rel-17 CR 28.552 Correction of PDSCH MCS distribution measurement | China Unicom | CR | Approval | Yes |
Yes
| revised | No | S5‑237160 | |||
S5‑237160 | Rel-17 CR 28.552 Correction of PDSCH MCS distribution measurement | China Unicom | CR | Approval | Yes |
Yes
| agreed | No | S5‑236749 | |||
S5‑236750 | Rel-18 CR 28.552 Correction of PDSCH MCS distribution measurement | China Unicom | CR | Approval | Yes |
Yes
| revised | No | S5‑237161 | |||
S5‑237161 | Rel-18 CR 28.552 Correction of PDSCH MCS distribution measurement | China Unicom | CR | Approval | Yes |
Yes
| agreed | No | S5‑236750 | |||
S5‑236780 | Rel-18 CR TS 28.554 Correction Utilization KPI definition of PDU session establishment time of network slice | China Mobile | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑236783 | Rel-17 CR TS28.552 Fix Packet Drop Rate | ZTE Corporation | CR | Approval | Yes |
Yes
| revised | No | S5‑237142 | |||
S5‑237142 | Rel-17 CR TS28.552 Fix Packet Drop Rate | ZTE Corporation | CR | Approval | Yes |
Yes
| agreed | No | S5‑236783 | |||
S5‑236784 | Rel-18 CR TS28.552 Fix Packet Drop Rate | ZTE Corporation | CR | Approval | Yes |
Yes
| revised | No | S5‑237143 | |||
S5‑237143 | Rel-18 CR TS28.552 Fix Packet Drop Rate | ZTE Corporation | CR | Approval | Yes |
Yes
| agreed | No | S5‑236784 | |||
S5‑237167 | Rel-15 CR TS28.552 Fix Packet Drop Rate | ZTE Corporation | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑237168 | Rel-16 CR TS28.552 Fix Packet Drop Rate | ZTE Corporation | CR | Approval | Yes |
Yes
| agreed | No | ||||
6.3.13 | Trace/MDT | S5‑236369 | Rel-17 CR TS 28.623 Stage 3 Correction of ExcessPacketDelayThreshold definition | Nokia, Nokia Shangai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||
S5‑236370 | Rel-18 CR TS 28.623 Stage 3 Correction of ExcessPacketDelayThreshold definition | Nokia, Nokia Shangai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑236672 | Rel-17 CR TS 32.423 Correcting the reference to E1AP specification for gnb-DU record content | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑236673 | Rel-18 CR TS 32.423 Correcting the reference to E1AP specification for gnb-DU record content | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑236674 | Rel-15 CR TS 32.423 RRC IEs added for trace record description for gnb-CU-CP | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑236675 | Rel-16 CR TS 32.423 RRC IEs added for trace record description for gnb-CU-CP | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑236676 | Rel-17 CR TS 32.423 RRC IEs added for trace record description for gnb-CU-CP | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑236677 | Rel-18 CR TS 32.423 RRC IEs added for trace record description for gnb-CU-CP | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑237163 | |||
S5‑237163 | Rel-18 CR TS 32.423 RRC IEs added for trace record description for gnb-CU-CP | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑236677 | |||
6.3.14 | Other | S5‑236347 | TS28.532 Rel16 correction to eventTime description for NotifyMoiDeletion & NotifyMoiAttributeValueChanges | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||
S5‑236348 | TS28.532 Rel17 correction to eventTime description for NotifyMoiDeletion & NotifyMoiAttributeValueChanges | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑236349 | TS28.532 Rel18 correction to eventTime description for NotifyMoiDeletion & NotifyMoiAttributeValueChanges | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑236482 | Rel-15 CR 28.500 Remove references to deprecated ETSI GS NFV MAN001 | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑236483 | Rel-16 CR 28.500 Remove references to deprecated ETSI GS NFV MAN001 | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑236484 | Rel-17 CR 28.500 Remove references to deprecated ETSI GS NFV MAN001 | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑236525 | Rel-16 32.158 Clarify mapping of DNs to URIs | Ericsson Inc. | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑236526 | Rel-17 32.158 Clarify mapping of DNs to URIs | Ericsson Inc. | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑236527 | Rel-17 CR 28.622 Clarify MnS scope value for Managed Elements | Ericsson Inc. | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑236528 | Rel-17 CR 28.623 Clarify MnS scope value for Managed Elements (stage3, yang) | Ericsson Inc. | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑236529 | Rel-18 CR 28.622 Clarify MnS scope value for Managed Elements | Ericsson Inc. | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑236530 | Rel-18 CR 28.623 Clarify MnS scope value for Managed Elements (stage3, yang) | Ericsson Inc. | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑236531 | Rel-17 CR 28.623 Clarify HeartBeatControl IOC definition (stage3, yang) | Ericsson Inc. | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑236532 | Rel-16 CR 28.623 Clarify HeartbeatControl IOC definition (stage3, yang) | Ericsson Inc. | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑236533 | Rel-18 CR 28.623 Clarify HeartbeatControl IOC definition (stage3, yang) | Ericsson Inc. | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑236534 | Rel-16 CR 28.622 Clarify HeartbeatControl IOC definition | Ericsson Inc. | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑236535 | Rel-17 CR 28.622 Clarify HeartbeatControl IOC definition | Ericsson Inc. | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑236536 | Rel-18 CR 28.622 Clarify HeartbeatControl IOC definition | Ericsson Inc. | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑236550 | Rel-16 CR 28.532 Clarify Heartbeat MnS capability definition | Ericsson Inc. | CR | Approval | Yes |
Yes
| not pursued | No | S5‑235419 | |||
S5‑236551 | Rel-17 CR 28.532 Clarify Heartbeat MnS capability definition | Ericsson Inc. | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑236555 | Rel-16 CR 28.532 Correct inconsistencies in MnS version number handling in OpenAPI files | Ericsson Inc. | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑236556 | Rel-17 CR 28.532 Correct inconsistencies in MnS version number handling in OpenAPI | Ericsson Inc. | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑236557 | Rel-16 CR 28.532 Correct URI definition inconsistencies | Ericsson Inc. | CR | Approval | Yes |
Yes
| not pursued | No | S5‑235428 | |||
S5‑236558 | Rel-17 CR 28.532 Correct URI definition inconsistencies | Ericsson Inc. | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑236559 | Rel-18 CR 28.532 Correct URI definition inconsistencies | Ericsson Inc. | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑236560 | Rel-18 CR 28.532 Correct inconsistencies in version number handling in OpenAPI | Ericsson Inc. | CR | Approval | No |
Yes
| withdrawn | Yes | S5‑236556 | |||
S5‑236561 | Rel-18 CR 28.532 Correct inconsistencies in MnS version number handling in OpenAPI | Ericsson Inc. | CR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑236569 | Rel-16 CR 28.532 Clarify usage of the attributes container in notifyMOIChanges | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑236571 | Rel-17 CR 32.156 Add missing definition of node | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑236573 | Rel-18 CR 32.156 Add missing definition of node | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑237201 | |||
S5‑237201 | Rel-18 CR 32.156 Add missing definition of node | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑236573 | |||
S5‑236687 | Rel-17 CR 28.537 Clarify management service discovery use cases | Ericsson Inc. | CR | Agreement | Yes |
Yes
| revised | No | S5‑237202 | |||
S5‑237202 | Rel-17 CR 28.537 Clarify management service discovery use cases | Ericsson Inc. | CR | Agreement | Yes |
Yes
| agreed | No | S5‑236687 | |||
S5‑236843 | Rel-17 CR 28.622 h70 NodeFilter | Nokia | CR | Agreement | Yes |
Yes
| withdrawn | Yes | ||||
S5‑236844 | Rel-18 CR 28.622 i40 NodeFilter | Nokia | CR | Agreement | Yes |
Yes
| withdrawn | Yes | ||||
S5‑236845 | Rel-17 CR 28.622 h70 MDC | Nokia | CR | Agreement | Yes |
Yes
| withdrawn | Yes | ||||
S5‑236846 | Rel-18 CR 28.622 i40 MDC | Nokia | CR | Agreement | Yes |
Yes
| withdrawn | Yes | ||||
S5‑236875 | Rel-18 CR TS28.405 Fix API name | ZTE Corporation | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑236876 | Rel-18 CR TS28.532 editorial Correction | ZTE Corporation | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑236877 | Rel-18 CR TS28.552 editorial Corrections | ZTE Corporation | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑237219 | BO_MoM-4 AI-ML_breakout_session_minutes | Nokia | other | discussion | Yes |
Yes
| noted | No | ||||
6.4 | OAM&P Rel-18 Work Items - Intelligence and Automation |   | ||||||||||
6.4.1 | Self-Configuration of RAN NEs |   | ||||||||||
6.4.1.1 | RANSC_WoP#1 | S5‑236276 | 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‑237113 | |
S5‑237113 | 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‑236276 | |||
6.4.1.2 | RANSC_WoP#2 | S5‑236281 | Rel-18 CR TS28.313 Update procedure for Sel-configuration to refer to TS 28.317 | China Mobile, Huawei | CR | Approval | Yes |
Yes
| not pursued | No | ||
6.4.1.3 | RANSC_WoP#3 | S5‑236277 | pCR TS 28.317 Add MnS component type A for self-configuration management | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||
S5‑236278 | pCR TS 28.317 Add MnS component type B for self-configuration management | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑237238 | draft TS 28.317 | China Mobile | draft TS | Approval | No |
Yes
| email approval | No | ||||
6.4.1.4 | Draft TS email approval |   | ||||||||||
6.4.2 | Management Data Analytics phase 2 |   | ||||||||||
6.4.2.1 | eMDAS_Ph2_WoP#1 | S5‑236792 | Rel-18 Input to draft CR TS 28.104 Add Recommendation Scope | China Mobile Com. Corporation | CR | Yes |
Yes
| not pursued | No | |||
S5‑237075 | Rel-18 Input to draft CR TS 28.104 Add Recommendation Scope | China Mobile Com. Corporation | other | - | No |
Yes
| withdrawn | Yes | ||||
S5‑237247 | Draft CR MDA TS 28.104 | NEC | draftCR | Approval | No |
Yes
| email approval | No | ||||
6.4.2.2 | eMDAS_Ph2_WoP#2 | S5‑236371 | Rel-18 Input to draft CR TS 28.104 Add enabling data for mobility and EE related PMs | Nokia, Nokia Shangai Bell | draftCR | Approval | Yes |
Yes
| revised | No | S5‑237077 | |
S5‑237077 | Rel-18 Input to draft CR TS 28.104 Add enabling data for mobility and EE related PMs | Nokia, Nokia Shangai Bell | draftCR | Approval | Yes |
Yes
| approved | No | S5‑236371 | |||
S5‑236411 | Rel18 Input to draft CR TS28.104 Event data analytics use case and requirements | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑237078 | Rel18 Input to draft CR TS28.104 Event data analytics use case and requirements | Nokia, Nokia Shanghai Bell | draftCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑236412 | Rel18 Input to draft CR TS28.104 Performance Measurement data correlation analytics use case and requirements | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑237079 | Rel18 Input to draft CR TS28.104 Performance Measurement data correlation analytics use case and requirements | Nokia, Nokia Shanghai Bell | draftCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑236765 | Rel18 Input to draft CR TS 28.104 training data effectiveness analytics use case and requirements | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| noted | No | ||||
6.4.2.3 | eMDAS_Ph2_WoP#3 |   | ||||||||||
6.4.2.4 | eMDAS_Ph2_WoP#4 |   | ||||||||||
6.4.2.5 | eMDAS_Ph2_WoP#5 |   | ||||||||||
6.4.2.6 | eMDAS_Ph2_WoP#6 | S5‑236486 | Update MDA capability of service failure recovery | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||
S5‑237080 | Input to DraftCR Update MDA capability of service failure recovery | Huawei | other | Agreement | Yes |
Yes
| approved | No | ||||
6.4.2.7 | eMDAS_Ph2_WoP#7 | S5‑236407 | Rel-18 draftCR 28.104 Add solution for MDA assisted control plane congestion analysis | Huawei | draftCR | Approval | Yes |
Yes
| not treated | No | ||
6.4.3 | AI/ML management |   | ||||||||||
6.4.3.1 | AIML_MGT_WoP#1 | S5‑236366 | Rel-18 Input to draft CR TS 28.105 Complete ML Update Solution | Nokia, Nokia Shangai Bell | draftCR | Approval | Yes |
Yes
| not treated | No | ||
S5‑236367 | Rel-18 Input to draft CR TS 28.105 NRM for producer initiated training | Nokia, Nokia Shangai Bell | draftCR | Approval | Yes |
Yes
| revised | No | S5‑236941 | |||
S5‑236941 | Rel-18 Input to draft CR TS 28.105 NRM for producer initiated training | Nokia, Nokia Shangai Bell | draftCR | Approval | Yes |
Yes
| approved | No | S5‑236367 | |||
S5‑236368 | Rel-18 Input to draft CR TS 28.105 Description, Use case and requirements for Context of ML Entities | Nokia, Nokia Shangai Bell | draftCR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑236409 | Rel18 Input to draft CR TS 28.105 Use case and requirements for ML Inference activation | Nokia, Nokia Shanghai Bell, NTT DOCOMO, Intel | draftCR | Approval | Yes |
Yes
| revised | No | S5‑236934 | |||
S5‑236934 | Rel18 Input to draft CR TS 28.105 Use case and requirements for ML Inference activation | Nokia, Nokia Shanghai Bell, NTT DOCOMO, Intel | draftCR | Approval | Yes |
Yes
| noted | No | S5‑236409 | |||
S5‑236410 | Rel18 Input to draft CR TS 28.105 Use case and requirements for ML Training activation | Nokia, Nokia Shanghai Bell, NTT DOCOMO, Intel | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑237159 | Rel18 Input to draft CR TS 28.105 Use case and requirements for ML Training activation | Nokia, Nokia Shanghai Bell, NTT DOCOMO, Intel | draftCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑236453 | Rel-18 Input to draft CR TS 28.105 Add ML performance metrics | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| revised | No | S5‑236649 | |||
S5‑236454 | Rel-18 Input to draft CR TS 28.105 ML Inference NRM | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| revised | No | S5‑236650 | |||
S5‑236455 | Rel-18 Input to draft CR TS 28.105 ML knowledge sharing | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| revised | No | S5‑236651 | |||
S5‑236456 | Rel-18 Input to draft CR TS 28.105 ML Inference emulation Requirements | Nokia, Nokia Shanghai Bell, NTT DOCOMO, NEC | draftCR | Approval | Yes |
Yes
| revised | No | S5‑236652 | |||
S5‑236457 | Rel-18 Input to draft CR TS 28.105 Information on executed AIML Actions | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| revised | No | S5‑236653 | |||
S5‑236458 | Rel-18 Input to draft CR TS 28.105 ML Activation NRM | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| revised | No | S5‑236654 | |||
S5‑236459 | Rel-18 Input to draft CR TS 28.105 ML Training policy-based activation | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| revised | No | S5‑236655 | |||
S5‑236460 | Rel-18 Input to draft CR TS 28.105 Coordinating ML Inference | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| revised | No | S5‑236656 | |||
S5‑236461 | Rel-18 Input to draft CR TS 28.105 ML Inference emulation NRM | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| revised | No | S5‑236657 | |||
S5‑236476 | Rel-18 draftCR TS 28.105 Corrections of term of AIML management | Huawei | draftCR | Approval | Yes |
Yes
| merged | No | S5‑237114 | |||
S5‑236477 | Rel-18 draftCR TS 28.105 corrections for ML performance indicator selection | Huawei | draftCR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑236478 | Rel-18 draftCR TS 28.105 Add solution for AIML inference function management | Huawei | draftCR | Approval | Yes |
Yes
| merged | No | S5‑237162 | |||
S5‑236543 | Input to DraftCR 28.105 Add NRMs for RAN intelligence functions | Intel, NEC | other | Agreement | Yes |
Yes
| merged | No | S5‑237162 | |||
S5‑236544 | Input to DraftCR 28.105 Correction of ML update related IOCs | Intel, NEC | other | Agreement | Yes |
Yes
| not treated | No | ||||
S5‑236545 | Input to DraftCR 28.105 Add NRMs for ML entity loading | Intel, NEC, CATT | other | Agreement | Yes |
Yes
| revised | No | S5‑236939 | |||
S5‑236939 | Input to DraftCR 28.105 Add NRMs for ML entity loading | Intel, NEC, CATT | other | Agreement | Yes |
Yes
| approved | No | S5‑236545 | |||
S5‑236548 | Input to DraftCR 28.105 Add use case and requirements for ML entity loading | Intel, NEC, CATT | other | Agreement | Yes |
Yes
| revised | No | S5‑236938 | |||
S5‑236938 | Input to DraftCR 28.105 Add use case and requirements for ML entity loading | Intel, NEC, CATT, China Mobile, Nokia, Ericsson, Huawei | other | Agreement | Yes |
Yes
| approved | No | S5‑236548 | |||
S5‑236649 | Rel-18 Input to draft CR TS 28.105 Add ML performance metrics | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| not treated | No | S5‑236453 | |||
S5‑236650 | Rel-18 Input to draft CR TS 28.105 ML Inference NRM | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| noted | No | S5‑236454 | |||
S5‑237162 | Rel-18 Input to draft CR TS 28.105 ML Inference NRM | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑236651 | Rel-18 Input to draft CR TS 28.105 ML knowledge sharing | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| not treated | No | S5‑236455 | |||
S5‑236652 | Rel-18 Input to draft CR TS 28.105 ML Inference emulation Requirements | Nokia, Nokia Shanghai Bell, NTT DOCOMO, NEC | draftCR | Approval | Yes |
Yes
| not treated | No | S5‑236456 | |||
S5‑236653 | Rel-18 Input to draft CR TS 28.105 Information on executed AIML Actions | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| not treated | No | S5‑236457 | |||
S5‑236654 | Rel-18 Input to draft CR TS 28.105 ML Activation NRM | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| noted | No | S5‑236458 | |||
S5‑236655 | Rel-18 Input to draft CR TS 28.105 ML Training policy-based activation | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| not treated | No | S5‑236459 | |||
S5‑236656 | Rel-18 Input to draft CR TS 28.105 Coordinating ML Inference | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| noted | No | S5‑236460 | |||
S5‑236657 | Rel-18 Input to draft CR TS 28.105 ML Inference emulation NRM | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| not treated | No | S5‑236461 | |||
S5‑236680 | Rel-18 Input to DraftCR 28.105 add AI ML management capabilities for ML deployment and inference | China Mobile Com. Corporation | draftCR | Approval | Yes |
Yes
| merged | No | S5‑236938 | |||
S5‑236681 | Rel-18 Input to Draft CR 28.105 Modification on ML training initiated by producer | China Mobile Com. Corporation | draftCR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑236682 | Rel-18 Input to Draft CR 28.105 Add new use case of ML entity exposure management | China Mobile Com. Corporation | draftCR | Approval | Yes |
Yes
| revised | No | S5‑236940 | |||
S5‑236940 | Rel-18 Input to Draft CR 28.105 Add new use case of ML entity exposure management | China Mobile Com. Corporation | draftCR | Approval | Yes |
Yes
| approved | No | S5‑236682 | |||
S5‑236683 | Rel-18 Input to Draft CR 28.105 Add use cases for ML emulation phase | China Mobile Com. Corporation | draftCR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑236684 | Rel-18 Input to Draft CR 28.105 Modification on description of AIML update control | China Mobile Com. Corporation | draftCR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑236685 | Rel-18 Input to draft CR TS 28.105 ML Inference History use case and requirements | Nokia, Nokia Shanghai Bell, NEC, NTT DOCOMO | draftCR | Approval | Yes |
Yes
| revised | No | S5‑236935 | |||
S5‑236935 | Rel-18 Input to draft CR TS 28.105 ML Inference History use case and requirements | Nokia, Nokia Shanghai Bell, NEC, NTT DOCOMO | draftCR | Approval | Yes |
Yes
| approved | No | S5‑236685 | |||
S5‑236686 | Rel-18 Input to draft CR TS 28.105 ML Inference History NRM | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| revised | No | S5‑237166 | |||
S5‑237166 | Rel-18 Input to draft CR TS 28.105 ML Inference History NRM | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| noted | No | S5‑236686 | |||
S5‑236759 | Rel18 Input to draft CR TS28.105 Training data effectiveness reporting use cases and requirements | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑236782 | pCR Input to DraftCR TS 28.105 Harmonize usage of ML model and entity | Ericsson Limited | draftCR | Agreement | Yes |
Yes
| revised | No | S5‑237114 | |||
S5‑237114 | pCR Input to DraftCR TS 28.105 Harmonize usage of ML model and entity | Ericsson Limited | draftCR | Agreement | Yes |
Yes
| approved | No | S5‑236782 | |||
S5‑236810 | Add description for AIML inference capabilities management | China Mobile | CR | Approval | Yes |
Yes
| revised | No | S5‑236936 | |||
S5‑236936 | Add description for AIML inference capabilities management | China Mobile | CR | Approval | Yes |
Yes
| not pursued | No | S5‑236810 | |||
S5‑237036 | Add description for AIML inference capabilities management | China Mobile | other | Approval | Yes |
Yes
| approved | No | ||||
S5‑236813 | Rel18 Input to draft CR TS 28.105 Coordination of the ML capabilities | Nokia, Nokia Shanghai Bell, TELUS | draftCR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑236814 | Add use case and requirements for AIML inference configuration management | China Mobile | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑236818 | Add use case and requirements for ML entity loading control and monitoring | China Mobile | CR | Approval | Yes |
YesContent merged into S5-236938.
| not pursued | No | ||||
S5‑236825 | Add use case and requirements for pre-processed event data for ML training | China Mobile | CR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑236826 | Add use case and requirements for tracking AI/ML inference decision and context | China Mobile | CR | Approval | Yes |
YesContent will go into 935.
| not pursued | No | ||||
S5‑236828 | Add use case and requirements for training data effectiveness reporting and analytics | China Mobile | CR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑237244 | Draft CR AIML | Intel | draftCR | Approval | No |
Yes
| email approval | No | ||||
6.4.3.2 | AIML_MGT_WoP#2 | S5‑236794 | Rel-17 CR 28.105 Correction of attribute properties | Ericsson Limited | CR | Agreement | Yes |
Yes
| not treated | No | ||
S5‑236797 | Rel-18 CR 28.105 Correction of attribute properties | Ericsson Limited | CR | Agreement | Yes |
Yes
| not treated | No | ||||
S5‑236803 | Correction of IOC name | Ericsson | CR | Agreement | Yes |
Yes
| not treated | No | ||||
S5‑236806 | CR correction of IOC Name | Ericsson | CR | Agreement | Yes |
Yes
| not treated | No | ||||
6.4.4 | Intent driven Management Service for mobile network phase 2 |   | ||||||||||
6.4.4.1 | IDMS_MN_ph2_WoP#1 | S5‑236255 | Rel-18 CR TS 28.312 Update the stage3 for intent report to align with the stage2 definition | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑236831 | |
S5‑236270 | Rel-18 CR TS 28.312 Correct issues for Relationship UML diagram for intent | China Mobile Com. Corporation | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑236271 | Rel-18 CR TS 28.312 Correct issues for the use of context in the OpenAPI document. | China Mobile Com. Corporation | CR | Yes |
Yes
| agreed | No | |||||
S5‑236306 | Rel-18 CR TS28.312 Update the stage3 to align with the stage2 | Huawei | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
S5‑236314 | Rel-18 CR TS 28.312 Rapporteur clean up | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑236775 | Correct issues for Class definition including Intent and IntentReport | ZTE Corporation | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑236817 | Rel-18 CR 28.312 Add REPORT to allowedValues in expectationVerb attributes | China Mobile Com. Corporation | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑236819 | Rel-18 CR TS 28.312 Enable MnS consumers to obtain historical intent reports | China Mobile Com. Corporation | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑236945 | Rel-18 CR TS 28.312 Enable MnS consumers to obtain historical intent reports | China Mobile Com. Corporation | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
S5‑236821 | Rel-18 CR TS 28312 Add requirements for intent decomposition | China Mobile Com. Corporation | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑236823 | Rel-18 CR TS 28.312 Add requirements and solution for intent probe and intent negotiate | China Mobile | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑236831 | Rel-18 CR TS 28.312 Update the stage3 for intent report to align with the stage2 definition | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑236944 | S5‑236255 | ||
S5‑236944 | Rel-18 CR TS 28.312 Update the stage3 for intent report to align with the stage2 definition | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑236831 | |||
6.4.4.2 | IDMS_MN_ph2_WoP#2 | S5‑236398 | Adding 5GC expectation in Intent IOC stage 3 | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||
S5‑236399 | Update 5GC expectation | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑236946 | |||
S5‑236946 | Update 5GC expectation | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑236399 | |||
S5‑236449 | Rel-18 CR TS 28.310 Add reference to TS 28.312 for intent driven approach for RAN energy saving use case | Huawei, Deutsche Telekom | CR | Agreement | Yes |
Yes
| revised | No | S5‑237068 | |||
S5‑237068 | Rel-18 CR TS 28.310 Add reference to TS 28.312 for intent driven approach for RAN energy saving use case | Huawei, Deutsche Telekom | CR | Agreement | Yes |
Yes
| agreed | No | S5‑236449 | |||
S5‑236500 | Rel-18 CR TS 28.312 Correct issues for the reference to maxNumberofPDUsessions | China Mobile Com. Corporation | CR | Approval | Yes |
Yes
| revised | No | S5‑236948 | |||
S5‑236948 | Rel-18 CR TS 28.312 Correct issues for the reference to maxNumberofPDUsessions | China Mobile Com. Corporation | CR | Approval | Yes |
Yes
| agreed | No | S5‑236500 | |||
S5‑236576 | Add one case and requirement for supporting change of intent handling function | ZTE Corporation | CR | Approval | Yes |
Yes
| revised | No | S5‑236949 | |||
S5‑236949 | Add one case and requirement for supporting change of intent handling function | ZTE Corporation | CR | Approval | Yes |
Yes
| agreed | No | S5‑236576 | |||
S5‑236579 | Clarify MnS consumer how handling infeasible results of intent fulfilment feasibility check | ZTE Corporation | CR | Approval | Yes |
Yes
| revised | No | S5‑236951 | |||
S5‑236951 | Clarify MnS consumer how handling infeasible results of intent fulfilment feasibility check | ZTE Corporation | CR | Approval | Yes |
Yes
| not pursued | No | S5‑236579 | |||
S5‑236581 | Enhance the description of intent report | ZTE Corporation | CR | Approval | Yes |
Yes
| revised | No | S5‑236952 | |||
S5‑236952 | Enhance the description of intent report | ZTE Corporation | CR | Approval | Yes |
Yes
| agreed | No | S5‑236581 | |||
S5‑236663 | Add description and potential requirement for intent report | ZTE Corporation | CR | Approval | Yes |
Yes
| revised | No | S5‑237076 | |||
S5‑237076 | Add description and potential requirement for intent report | ZTE Corporation | CR | Approval | Yes |
Yes
| agreed | No | S5‑236663 | |||
S5‑236788 | Rel-18 CR TS 28.312 Correct use case for Intent containing an expectation for 5GC network | China Mobile, Huawei | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑236791 | Rel-18 CR TS 28.312 Correct use case for Intent fulfillment feasibility check | China Mobile, Huawei | CR | Approval | Yes |
Yes
| merged | No | S5‑236951 | |||
6.4.4.3 | IDMS_MN_ph2_WoP#3 | S5‑236307 | Rel-18 CR TS 28.312 Update 6.1 and 7.1 to support intent report and intent handling capability obtaining | Huawei, Deutsche Telekom | CR | Agreement | Yes |
Yes
| agreed | No | ||
S5‑236308 | Add YAML document examples for intent report instance | Huawei, Deutsche Telekom | CR | Agreement | Yes |
Yes
| revised | No | S5‑236954 | |||
S5‑236954 | Add YAML document examples for intent report instance | Huawei, Deutsche Telekom | CR | Agreement | Yes |
Yes
| agreed | No | S5‑236308 | |||
S5‑236309 | Rel-18 CR TS 28.312 Add procedure for intent report and intent handling capability obtaining | Huawei, Deutsche Telekom | CR | Agreement | Yes |
Yes
| revised | No | S5‑237074 | |||
S5‑237074 | Rel-18 CR TS 28.312 Add procedure for intent report and intent handling capability obtaining | Huawei, Deutsche Telekom | CR | Agreement | Yes |
Yes
| agreed | No | S5‑236309 | |||
S5‑236310 | Rel-18 CR TS 28.312 Correct issues for IntentReport model(6.4.4.3) | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑236955 | |||
S5‑236955 | Rel-18 CR TS 28.312 Correct issues for IntentReport model(6.4.4.3) | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑236310 | |||
S5‑236462 | Rel-18 CR TS 28.312 Selection among Expectation, targets and contexts | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑236956 | |||
S5‑236956 | Rel-18 CR TS 28.312 Selection among Expectation, targets and contexts | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑236462 | |||
S5‑236463 | Rel18 CR 28312 Requirements on intent Reporting | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑236953 | |||
S5‑236953 | Rel18 CR 28312 Requirements on intent Reporting | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑236463 | |||
S5‑236485 | Rel-18 CR 28.312 Intent Conflict Resolution Procedure | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑237116 | |||
S5‑237116 | Rel-18 CR 28.312 Intent Conflict Resolution Procedure | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑236485 | |||
S5‑236502 | Rel-18_CR_28312_Correct issues for Class definition including Intent and IntentReport | ZTE Corporation | CR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑236503 | Correct issues of attibutes in IntentFulfillmentReport. | ZTE Corporation | CR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑236504 | Rel-18 CR TS 28.312 Correct issues of attibutes in IntentFulfillmentReport. | ZTE Corporation | CR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑236505 | Rel-18_CR_28312_Enhancement for Intent handling capability | ZTE Corporation | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑236506 | Rel-18 CR TS 28.312 Correct issues of attibutes in IntentFulfillmentReport. | ZTE Corporation | CR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑236564 | Rel-18 CR TS 28.312 add intent conflict resolution based on intent preemption | NTT DOCOMO | CR | Agreement | Yes |
Yes
| revised | No | S5‑237041 | |||
S5‑237041 | Rel-18 CR TS 28.312 add intent conflict resolution based on intent preemption | NTT DOCOMO | CR | Agreement | Yes |
Yes
| agreed | No | S5‑236564 | |||
S5‑236565 | Rel-18 CR TS 28.312 add attributes of intent preemption | NTT DOCOMO | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑237042 | Rel-18 CR TS 28.312 add attributes of intent preemption | NTT DOCOMO | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
S5‑236776 | Correct issues of attibutes in IntentFulfillmentReport. | ZTE Corporation | CR | Approval | Yes |
Yes
| merged | No | S5‑236955 | |||
S5‑236777 | Rel-18 CR TS 28.312 Correct issues of attibutes in IntentFulfillmentReport. | ZTE Corporation | CR | Approval | Yes |
Yes
| revised | No | S5‑237050 | |||
S5‑237050 | Rel-18 CR TS 28.312 Correct issues of attibutes in IntentFulfillmentReport. | ZTE Corporation | CR | Approval | Yes |
Yes
| agreed | No | S5‑236777 | |||
S5‑236778 | Rel-18 CR TS 28.312 Enhancement for Intent handling capability obtaining | ZTE Corporation | CR | Approval | Yes |
Yes
| revised | No | S5‑236950 | |||
S5‑236950 | Rel-18 CR TS 28.312 Enhancement for Intent handling capability obtaining | ZTE Corporation | CR | Approval | Yes |
Yes
| agreed | No | S5‑236778 | |||
S5‑236779 | Rel-18 CR TS 28.312 Correct issues of attibutes in IntentFulfillmentReport. | ZTE Corporation | CR | Approval | Yes |
Yes
| merged | No | S5‑237116 | |||
6.4.4.4 | IDMS_MN_ph2_WoP#4 | S5‑236311 | Rel-18 CR TS28.312 Enhance the RadioNetworkExpectation | Huawei, Deutsche Telekom | CR | Agreement | Yes |
Yes
| agreed | No | ||
S5‑236313 | Add RadioServiceExpectation | Huawei, Deutsche Telekom | CR | Agreement | Yes |
Yes
| revised | No | S5‑237049 | |||
S5‑237049 | Add RadioServiceExpectation | Huawei, Deutsche Telekom | CR | Agreement | Yes |
Yes
| agreed | No | S5‑236313 | |||
S5‑236966 | Report for IDMS_MN_Ph2 breakout session | Huawei | discussion | Information | Yes |
Yes
| noted | No | ||||
6.4.4.5 | IDMS_MN_ph2_WoP#5 | S5‑236312 | Rel-18 CR TS 28.312 Add Intent interface deployment scenarios in Annex | Huawei, Deutsche Telekom | CR | Agreement | Yes |
Yes
| revised | No | S5‑237048 | |
S5‑237048 | Rel-18 CR TS 28.312 Add Intent interface deployment scenarios in Annex | Huawei, Deutsche Telekom, Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑236312 | |||
6.5 | OAM&P Rel-18 Work Items - Management Architecture and Mechanisms |   | ||||||||||
6.5.1 | Service based management architecture |   | ||||||||||
6.5.1.1 | eSBMA_WoP#1 | S5‑236258 | Rel-18 dCR 28.622 Remove FM related parts | Ericsson India Private Limited | draftCR | Approval | Yes |
Yes
| revised | No | S5‑237043 | |
S5‑237043 | Rel-18 dCR 28.622 Remove FM related parts | Ericsson India Private Limited | draftCR | Approval | Yes |
Yes
| approved | No | S5‑236258 | |||
S5‑236264 | Rel-18 dCR 28.623 Remove-Update FM related parts | Ericsson India Private Limited | draftCR | Approval | Yes |
Yes
| revised | No | S5‑237044 | |||
S5‑237044 | Rel-18 dCR 28.623 Remove-Update FM related parts | Ericsson India Private Limited | draftCR | Approval | Yes |
Yes
| approved | No | S5‑236264 | |||
S5‑236265 | Rel-18 dCR 28.532 Remove-Update FM related parts | Ericsson India Private Limited | draftCR | Approval | Yes |
Yes
| revised | No | S5‑237045 | |||
S5‑237045 | Rel-18 dCR 28.532 Remove-Update FM related parts | Ericsson India Private Limited | draftCR | Approval | Yes |
Yes
| approved | No | S5‑236265 | |||
S5‑236267 | Rel-18 pCR 28.111 FM updates | Ericsson India Private Limited | pCR | Approval | Yes |
Yes
| revised | No | S5‑237046 | |||
S5‑237046 | Rel-18 pCR 28.111 FM updates | Ericsson India Private Limited | pCR | Approval | Yes |
Yes
| approved | No | S5‑236267 | |||
S5‑236851 | DP Notification filtering | Ericsson Hungary Ltd | discussion | Endorsement | Yes |
Yes
| noted | No | S5‑235250 | |||
S5‑237248 | Draft CR eSBMA TS 32.101 | Nokia | draftCR | Approval | No |
Yes
| email approval | No | ||||
S5‑237249 | Draft CR eSBMA TS 28.622 | Nokia | draftCR | Approval | No |
Yes
| email approval | No | ||||
6.5.1.2 | eSBMA_WoP#2 | S5‑236660 | Rel-18 CR TS 28.533 Add example of RAN domain management capabilities mapped with ZSM | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑237047 | |
S5‑237047 | Rel-18 CR TS 28.533 Add example of RAN domain management capabilities mapped with ZSM | Huawei, Telefónica, Deutsche Telekom | CR | Agreement | Yes |
Yes
| agreed | No | S5‑236660 | |||
S5‑236661 | Rel-18 CR TS 28.533 Using Management Services to support multiple players interoperability | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑237051 | |||
S5‑237051 | Rel-18 CR TS 28.533 Using Management Services to support multiple players interoperability | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑236661 | |||
6.5.1.3 | eSBMA_WoP3# |   | ||||||||||
6.5.1.4 | eSBMA_WoP#4 | S5‑236820 | Revised WID on Service Based Management Architecture (SBMA) | Ericsson | WID revised | Yes |
Yes
| revised | No | S5‑237052 | ||
S5‑237052 | Revised WID on Service Based Management Architecture (SBMA) | Ericsson | WID revised | - | Yes |
Yes
| agreed | No | S5‑236820 | |||
S5‑236822 | Input to DraftCR 32.300 Move of info about IOC/MOC name to 32.156 | Ericsson | other | Yes |
Yes
| approved | No | |||||
S5‑236824 | Moving IOC/MOC info from 32.300 | Ericsson | CR | Yes |
Yes
| not pursued | No | |||||
S5‑237246 | Draft CR eSBMA | Ericsson | draftCR | Approval | No |
Yes
| email approval | No | ||||
6.5.1.5 | eSBMA_WoP#5 |   | ||||||||||
6.5.1.6 | eSBMA_WoP#6 | S5‑236575 | Rel-18 32.161 JSON expressions (Jex) skeleton | Nokia, Nokia Shanghai Bell | draft TS | Approval | Yes |
Yes
| approved | No | ||
S5‑236577 | Rel-18 pCR 32.161 Add Jex definitions | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑236578 | Rel-18 Input to DraftCR 28.622 Add new method for specifying the scope of subscriptions | Nokia, Nokia Shanghai Bell | other | Approval | Yes |
Yes
| revised | No | S5‑237053 | |||
S5‑237053 | Rel-18 Input to DraftCR 28.622 Add new method for specifying the scope of subscriptions | Nokia, Nokia Shanghai Bell | other | Approval | Yes |
Yes
| approved | No | S5‑236578 | |||
6.5.1.7 | eSBMA_WoP#7 | S5‑236252 | TS28.623 Rel18 OpenAPI SS for SupportedNotifications | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||
S5‑236580 | Rel-18 CR 28.532 Update definition of createMOI (stage 2) | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑237054 | |||
S5‑237054 | Rel-18 CR 28.532 Update definition of createMOI (stage 2) | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑236580 | |||
S5‑236582 | Rel-18 CR 28.532 Update definition of modifyMOIAttributes | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑237055 | |||
S5‑237055 | Rel-18 CR 28.532 Update definition of modifyMOIAttributes | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑236582 | |||
S5‑236583 | Rel-18 CR 28.532 Add definition of changeMOIs (stage 2) | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑237056 | |||
S5‑237056 | Rel-18 CR 28.532 Add definition of changeMOIs (stage 2) | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑236583 | |||
S5‑236862 | Discussion paper on version control of interfaces | Nokia Germany | discussion | Endorsement | Yes |
Yes
| not treated | No | ||||
6.5.1.8 | Draft TS email approval | S5‑237037 | Draft TS 28.111 | Ericsson | draft TS | Approval | No |
Yes
| email approval | No | ||
S5‑237038 | Draft TS 32.161 | Nokia | draft TS | Approval | No |
Yes
| email approval | No | ||||
6.5.2 | Network slicing provisioning rules |   | ||||||||||
6.5.2.1 | NSRULE_WoP#1 |   | ||||||||||
6.5.2.2 | NSRULE_WoP#2 | S5‑236332 | Rel-18 CR TS 28.541 Add NRM for network slice isolation | Nokia, Nokia Shanghai Bell, Telefonica | CR | Approval | Yes |
Yes
| revised | No | S5‑237083 | S5‑235170 |
S5‑237083 | Rel-18 CR TS 28.541 Add NRM for network slice isolation | Nokia, Nokia Shanghai Bell, Telefonica | CR | Approval | Yes |
Yes
| not pursued | No | S5‑236332 | |||
S5‑236333 | Rel-18 CR TS 28.531 Add and update use case for network slice isolation support | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑237082 | S5‑235176 | ||
S5‑237082 | Rel-18 CR TS 28.531 Add and update use case for network slice isolation support | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | S5‑236333 | |||
S5‑236691 | Discussion paper on slice agnostic service profile solutions | L.M. Ericsson Limited, Deutsche Telekom AG | discussion | Approval | Yes |
Yes
| revised | No | S5‑237221 | |||
S5‑237221 | Discussion paper on slice agnostic service profile solutions | L.M. Ericsson Limited, Deutsche Telekom AG | discussion | Approval | Yes |
Yes
| noted | No | S5‑236691 | |||
S5‑236692 | Discussion paper on solutions for sharing and isolation | L.M. Ericsson Limited, Deutsche Telekom AG | discussion | Approval | Yes |
Yes
| noted | No | ||||
S5‑236693 | Rel-18 CR TS 28.541 Add NRM solution for network slice sharing | L.M. Ericsson Limited, Deutsche Telekom AG | CR | Approval | Yes |
Yes
| not pursued | No | ||||
6.5.3 | Management of Trace/MDT phase 2 |   | ||||||||||
6.5.3.1 | 5GMDT_Ph2_WoP#1 | S5‑236766 | Clarify user consent handling for MDT in private networks | Ericsson | CR | Agreement | No |
Yes
| revised | No | S5‑236769 | |
S5‑236769 | Clarify user consent handling for MDT in private networks | Ericsson LM | CR | Approval | Yes |
Yes
| revised | No | S5‑237084 | S5‑236766 | ||
S5‑237084 | Clarify user consent handling for MDT in private networks | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | S5‑236769 | |||
6.5.3.2 | 5GMDT_Ph2_WoP#2 | S5‑236362 | Rel-18 CR TS 28.622 Aligning ReportAmount LTE parameters with ImmediateMDT datatype | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||
S5‑236363 | Rel-18 CR TS 28.622 Report Amount parameter in NR | Nokia, Nokia Shangai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑236364 | Rel-18 CR TS 28.623 Stage 3 Report Amount parameter in NR | Nokia, Nokia Shangai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑236365 | Rel-18 CR TS 32.422 Report Amount parameter in NR | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑237086 | |||
S5‑237086 | Rel-18 CR TS 32.422 Report Amount parameter in NR | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑236365 | |||
6.5.3.3 | 5GMDT_Ph2_WoP#3 |   | ||||||||||
6.5.3.4 | 5GMDT_Ph2_WoP#4 |   | ||||||||||
6.5.3.5 | 5GMDT_Ph2_WoP#5 |   | ||||||||||
6.5.4 | 5G performance measurements and KPIs phase 3 |   | ||||||||||
6.5.4.1 | PM_KPI_5G_Ph3_WoP#1 | S5‑236468 | Rel-18 CR TS 28.552 Add measurements for NG-RAN Initiated paging sent by gNB-CU | China Telecomunication Corp., ZTE | CR | Agreement | Yes |
Yes
| agreed | No | ||
S5‑236751 | Rel-18 CR 28.554 Add new KPI on air-interface efficiency based on MCS | China Unicom | CR | Approval | Yes |
Yes
| revised | No | S5‑237117 | |||
S5‑237117 | Rel-18 CR 28.554 Add new KPI on air-interface efficiency based on MCS | China Unicom | CR | Approval | Yes |
Yes
| agreed | No | S5‑236751 | |||
S5‑236756 | Rel-18 CR 28.552 Add formula for packet success rate measurement | China Unicom,Ericsson | CR | Yes |
Yes
| not pursued | No | |||||
S5‑236757 | Rel-18 TS 28.552 Add new measurement for average value of Timing Advance per UE | China Unicom | CR | Approval | Yes |
Yes
| revised | No | S5‑236964 | |||
S5‑236964 | Rel-18 TS 28.552 Add new measurement for average value of Timing Advance per UE | China Unicom | CR | Approval | Yes |
Yes
| not pursued | No | S5‑236757 | |||
6.5.4.2 | PM_KPI_5G_Ph3_WoP#2 | S5‑236372 | Rel-18 CR TS 28.552 Addition of measurements related to Number of successful RRC connection setups in relation to the time between successful RRC connection setup and last RRC connection release | Nokia, Nokia Shangai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑236965 | |
S5‑236965 | Rel-18 CR TS 28.552 Addition of measurements related to Number of successful RRC connection setups in relation to the time between successful RRC connection setup and last RRC connection release | Nokia, Nokia Shangai Bell | CR | Approval | Yes |
Yes
| not pursued | No | S5‑236372 | |||
S5‑236785 | Rel-18 CR TS28.552 Add Total number of DL PDCP SDU Packets in gNB-CU-UP for split gNB deployment scenario | ZTE Corporation | CR | Approval | Yes |
Yes
| revised | No | S5‑237104 | |||
S5‑237104 | Rel-18 CR TS28.552 Add Total number of DL PDCP SDU Packets in gNB-CU-UP for split gNB deployment scenario | ZTE Corporation | CR | Approval | Yes |
Yes
| agreed | No | S5‑236785 | |||
S5‑236786 | Rel-18 CR TS28.552 Add Total number of DL RLC SDU Packets in gNB-DU for split gNB deployment scenario | ZTE Corporation | CR | Approval | Yes |
Yes
| revised | No | S5‑237105 | |||
S5‑237105 | Rel-18 CR TS28.552 Add Total number of DL RLC SDU Packets in gNB-DU for split gNB deployment scenario | ZTE Corporation | CR | Approval | Yes |
Yes
| agreed | No | S5‑236786 | |||
6.5.4.3 | PM_KPI_5G_Ph3_WoP#3 |   | ||||||||||
6.5.4.4 | PM_KPI_5G_Ph3_WoP#4 | S5‑236447 | Rel-18 CR TS 28.552 Add DL/UL PRB Usage per SSB to support AI/ML enabled NG-RAN | China Telecomunication Corp., Intel | CR | Agreement | Yes |
Yes
| revised | No | S5‑236967 | |
S5‑236967 | Rel-18 CR TS 28.552 Add DL/UL PRB Usage per SSB to support AI/ML enabled NG-RAN | China Telecomunication Corp., Intel | CR | Agreement | Yes |
Yes
| agreed | No | S5‑236447 | |||
S5‑236448 | Rel-18 CR TS 28.552 Update DL/UL PRB Usage per cell to support AI/ML enabled NG-RAN | China Telecom Corporation Ltd.,Intel | CR | Agreement | Yes |
Yes
| revised | No | S5‑236968 | |||
S5‑236968 | Rel-18 CR TS 28.552 Update DL/UL PRB Usage per cell to support AI/ML enabled NG-RAN | China Telecom Corporation Ltd.,Intel | CR | Agreement | Yes |
Yes
| agreed | No | S5‑236448 | |||
S5‑236537 | DP on defining measurements per UE | Intel, Nokia, CATT, NEC | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑236538 | Revised WID on enhancements of 5G performance measurements and KPIs phase3 | Intel, Nokia, CATT, NEC | WID revised | Agreement | Yes |
YesThe Chair declared this document as agreed, with the sole objection of ZTE. This was declared a working agreement.
| agreed | No | ||||
S5‑236539 | Initial Skeleton of draft TS 28.abc UE level measurements | Intel | other | Agreement | Yes |
Yes
| noted | No | ||||
S5‑236540 | pCR Add structure for new draft TS 28.abc UE level measurements | Intel | other | Agreement | Yes |
Yes
| noted | No | ||||
S5‑236541 | pCR TS 28.abc Add template for UE level measurement definition | Intel | other | Agreement | Yes |
Yes
| noted | No | ||||
S5‑236542 | pCR TS 28.abc Add Per-UE measurement related to DL packet delay between PSA UPF and UE | Intel | other | Agreement | Yes |
Yes
| revised | No | S5‑237216 | |||
S5‑237216 | pCR TS 28.abc Add Per-UE measurement related to DL packet delay between PSA UPF and UE | Intel | other | Agreement | Yes |
Yes
| noted | No | S5‑236542 | |||
S5‑236566 | pCR TS 28.abc Add Per-UE measurement related to average DL/UL UE throughput | China Telecomunication Corp., Intel | other | Approval | Yes |
Yes
| noted | No | ||||
S5‑236572 | pCR TS 28.abc Add Per-UE measurement related to average packet loss | China Telecom Corporation Ltd., Intel | other | Approval | Yes |
Yes
| noted | No | ||||
6.5.5 | Additional NRM features phase 2 |   | ||||||||||
6.5.5.1 | AdNRM_ph2_WoP#1 | S5‑236319 | Discussion paper on separate yaml file for different control NRM fragments in TS 28.623 | Huawei | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑237197 | S5‑235431 |
S5‑237197 | Discussion paper on separate yaml file for different control NRM fragments in TS 28.623 | Huawei | discussion | Endorsement | Yes |
Yes
| endorsed | No | S5‑236319 | |||
S5‑236320 | Rel-18 CR TS 28.623 separate yaml file for different control NRM fragment | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑235432 | |||
S5‑236869 | Rel-18 CR TS 28.541 Add slice validity info to ServiceProfile | Samsung R&D Institute UK | CR | Approval | Yes |
Yes
| revised | No | S5‑236969 | |||
S5‑236969 | Rel-18 CR TS 28.541 Add slice validity info to ServiceProfile | Samsung R&D Institute UK | CR | Approval | Yes |
Yes
| not pursued | No | S5‑236869 | |||
6.5.5.2 | AdNRM_ph2_WoP#2 |   | ||||||||||
6.5.5.3 | AdNRM_ph2_WoP#3 | S5‑236574 | Rel-18 CR 28.622 Add NRM fragment for scheduler and condition monitor (stage 2) | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑236970 | |
S5‑236970 | Rel-18 CR 28.622 Add NRM fragment for scheduler and condition monitor (stage 2) | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑236574 | |||
S5‑236867 | Rel-18 CR 28.622 Explicit target of CM operations | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑237135 | Rel-18 CR 28.622 Explicit target of CM operations | Nokia, Nokia Shanghai Bell | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑236868 | Add DNN to ServiceProfile and SliceProfile | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
6.5.5.4 | AdNRM_ph2_WoP#4 | S5‑236242 | TS28.541 Rel18 NRM enhancements for NRFFunction and AmfInfo and SmfInfo | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||
S5‑236243 | TS28.541 Rel18 NRM enhancements for UpfInfo and PcfInfo and NetInfo | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑236244 | TS28.541 Rel18 NRM enhancements for MBUPFFunction | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑236245 | TS28.541 Rel18 NRM enhancements for MBSMFFunction | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑236246 | TS28.541 Rel18 NRM enhancements for class diagram | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑236251 | TS28.623 Rel18 OpenAPI SS for QMCJob | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑236334 | Rel-18 CR TS 28.541 Fix inconsitencies related to network slice SLA attribute jitter | Nokia, Nokia Shanghai Bell, KDDI, TELUS | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑236335 | Rel-18 CR TS 28.541 Fix inconsitencies related to network slice SLA attribute availability | Nokia, Nokia Shanghai Bell, KDDI, TELUS | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑236336 | Rel-18 CR TS 28.541 Fix inconsitencies related to network slice SLA attribute kPIMonitoring | Nokia, Nokia Shanghai Bell, KDDI, TELUS | CR | Approval | Yes |
Yes
| revised | No | S5‑237120 | |||
S5‑237120 | Rel-18 CR TS 28.541 Fix inconsitencies related to network slice SLA attribute kPIMonitoring | Nokia, Nokia Shanghai Bell, KDDI, TELUS | CR | Approval | Yes |
Yes
| agreed | No | S5‑236336 | |||
S5‑236337 | Rel-18 CR TS 28.541 Fix inconsitencies related to network slice SLA attribute nBIoT | Nokia, Nokia Shanghai Bell, KDDI, TELUS | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑236338 | Rel-18 CR TS 28.541 Fix inconsitencies related to network slice SLA attribute maxDLDataVolume and maxULDataVolume | Nokia, Nokia Shanghai Bell, KDDI, TELUS | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑236339 | Rel-18 CR TS 28.541 Add support for GSMA attribute for slice QoS | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑236340 | Rel-18 CR TS 28.541 Add support for GSMA attributes related to data networks | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑236450 | Rel18 TS28.623 Add NRM fragments for scheduler and condition monitor (OpenAPI definition) | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑237119 | |||
S5‑237119 | Rel18 TS28.623 Add NRM fragments for scheduler and condition monitor (OpenAPI definition) | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑236450 | |||
S5‑236590 | Rel-18 CR 28.541 User Data Access Stage-2 | Samsung R&D Institute India | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑236591 | Rel-18 CR 28.541 User Data Access Stage-3 | Samsung R&D Institute India | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑237218 | BO_MoM-3 Report for AdNRM_Breakout_Session_Notes | Nokia | other | discussion | Yes |
Yes
| noted | No | ||||
6.5.6 | Management Aspects related to NWDAF |   | ||||||||||
6.5.6.1 | MANWDAF_WoP#1 | S5‑236662 | Rel-18 CR 28.552 Removing duplicate clauses for measurements related to NWDAF data collection | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑236957 | |
S5‑236957 | Rel-18 CR 28.552 Removing duplicate clauses for measurements related to NWDAF data collection | Nokia, Nokia Shanghai Bell,China Telecom | CR | Approval | Yes |
Yes
| agreed | No | S5‑236662 | |||
S5‑236815 | Update Performance measurements for NWDAF | China Telecom | CR | Agreement | Yes |
Yes
| merged | No | S5‑236957 | |||
6.5.6.2 | MANWDAF_WoP#2 | S5‑236647 | Rel-18 CR 28.552 Update use case on coordination among multiple NWDAFs | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | ||
S5‑236958 | Rel-18 CR 28.552 Update use case on coordination among multiple NWDAFs | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑236658 | Rel-18 CR 28.552 Update measurements related to coordination among multiple NWDAFs | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑236959 | |||
S5‑236959 | Rel-18 CR 28.552 Update measurements related to coordination among multiple NWDAFs | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑236658 | |||
S5‑236659 | Rel-18 CR 28.552 Add new measurements related to coordination among multiple NWDAFs | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑237060 | Rel-18 CR 28.552 Add new measurements related to coordination among multiple NWDAFs | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| approved | No | ||||
6.5.6.3 | MANWDAF_WoP#3 | S5‑236642 | Rel-18 CR 28.552 Add use case on NWDAF ML model related measurements | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑236960 | |
S5‑236960 | Rel-18 CR 28.552 Add use case on NWDAF ML model related monitoring | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑236642 | |||
S5‑236644 | Rel-18 CR 28.552 Add measurements related to number of ML models in NWDAF | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑236645 | Rel-18 CR 28.552 Add measurements related to size of ML models in NWDAF | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑236646 | Rel-18 CR 28.552 Add measurements related to usage of ML models in NWDAF | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑237165 | |||
S5‑237165 | Rel-18 CR 28.552 Add measurements related to usage of ML models in NWDAF | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑236646 | |||
6.5.7 | Enhanced Edge Computing Management |   | ||||||||||
6.5.7.1 | eECM_WoP#1 | S5‑236272 | Rel-18 CR TS 28.538 Correct the errors in the requirement label in section 5.1.14 | AsiaInfo, China Unicom | CR | Approval | Yes |
Yes
| withdrawn | Yes | ||
S5‑236273 | Rel-18 CR TS 28.538 Adding SLA requirements in EASRequirements IOC | AsiaInfo, China Unicom | CR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑236279 | Rel-18 CR TS 28.538 Correct the errors in the requirement label in section 5.1.14 | AsiaInfo, China Unicom | CR | Approval | Yes |
Yes
| revised | No | S5‑237087 | |||
S5‑237087 | Rel-18 CR TS 28.538 Correct the errors in the requirement label in section 5.1.14 | AsiaInfo, China Unicom | CR | Approval | Yes |
Yes
| agreed | No | S5‑236279 | |||
S5‑236280 | Adding SLA requirements in EASRequirements IOC | AsiaInfo, China Unicom | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑236594 | Rel-18 InputToDraftCR 28.538 Federated ECS Management Requirements | Samsung R&D Institute India | other | Agreement | Yes |
Yes
| revised | No | S5‑237089 | |||
S5‑237089 | Rel-18 InputToDraftCR 28.538 Federated ECS Management Requirements | Samsung R&D Institute India | other | Agreement | Yes |
Yes
| approved | No | S5‑236594 | |||
S5‑237245 | Draft CR ECM | Samusng | draftCR | Approval | No |
Yes
| email approval | No | ||||
6.5.7.2 | eECM_WoP#2 | S5‑236404 | Rel-18 DraftCR 28.538 update UC description for EAS LCM | Huawei | draftCR | Approval | Yes |
Yes
| revised | No | S5‑237090 | |
S5‑237090 | Rel-18 DraftCR 28.538 update UC description for EAS LCM | Huawei | draftCR | Approval | Yes |
Yes
| approved | No | S5‑236404 | |||
6.5.7.3 | eECM_WoP#3 | S5‑236400 | Rel-18 DraftCR 28.538 add query EDN availalbe edge resource requirements | Huawei | draftCR | Approval | Yes |
Yes
| revised | No | S5‑237091 | |
S5‑237091 | Rel-18 DraftCR 28.538 add query EDN availalbe edge resource requirements | Huawei | draftCR | Approval | Yes |
Yes
| approved | No | S5‑236400 | |||
S5‑236403 | Rel-18 DraftCR 28.538 EAS resource reservation requirements | Huawei | draftCR | Approval | Yes |
Yes
| revised | No | S5‑237093 | |||
S5‑237093 | Rel-18 DraftCR 28.538 EAS resource reservation requirements | Huawei | draftCR | Approval | Yes |
Yes
| approved | No | S5‑236403 | |||
S5‑236405 | Rel-18 DraftCR 28.538 add support for virtual infra resource requirement | Huawei | draftCR | Approval | Yes |
Yes
| revised | No | S5‑237185 | |||
S5‑237185 | Rel-18 DraftCR 28.538 add support for virtual infra resource requirement | Huawei | draftCR | Approval | Yes |
Yes
| approved | No | S5‑236405 | |||
S5‑236406 | Rel-18 draftCR 28.538 adding aVailableEdgeResources in EDN | Huawei | draftCR | Approval | Yes |
Yes
| revised | No | S5‑237092 | |||
S5‑237092 | Rel-18 draftCR 28.538 adding aVailableEdgeResources in EDN | Huawei | draftCR | Approval | Yes |
Yes
| approved | No | S5‑236406 | |||
S5‑236408 | Rel-18 draftCR 28.538 adding EAS resource reservation procedure | Huawei | draftCR | Approval | Yes |
Yes
| revised | No | S5‑237095 | |||
S5‑237095 | Rel-18 draftCR 28.538 adding EAS resource reservation procedure | Huawei | draftCR | Approval | Yes |
Yes
| approved | No | S5‑236408 | |||
S5‑236584 | Rel-18 InputToDraftCR 28.538 Federation Procedure | Samsung R&D Institute India | other | Agreement | Yes |
Yes
| revised | No | S5‑237183 | |||
S5‑237183 | Rel-18 InputToDraftCR 28.538 Federation Procedure | Samsung R&D Institute India | other | Agreement | Yes |
Yes
| approved | No | S5‑236584 | |||
S5‑236586 | Rel-18 InputToDraftCR 28.538 Federation NRM | Samsung R&D Institute India | other | Agreement | Yes |
Yes
| revised | No | S5‑237184 | |||
S5‑237184 | Rel-18 InputToDraftCR 28.538 Federation NRM | Samsung R&D Institute India | other | Agreement | Yes |
Yes
| approved | No | S5‑236586 | |||
S5‑236588 | Rel-18 InputToDraftCR 28.538 Federated EAS Lifecycle Management Procedure | Samsung R&D Institute India | other | Agreement | Yes |
Yes
| revised | No | S5‑237096 | |||
S5‑237096 | Rel-18 InputToDraftCR 28.538 Federated EAS Lifecycle Management Procedure | Samsung R&D Institute India | other | Agreement | Yes |
Yes
| approved | No | S5‑236588 | |||
S5‑236589 | Rel-18 InputToDraftCR 28.538 Federated EAS Lifecycle Management NRM | Samsung R&D Institute India | other | Agreement | Yes |
Yes
| revised | No | S5‑237097 | |||
S5‑237097 | Rel-18 InputToDraftCR 28.538 Federated EAS Lifecycle Management NRM | Samsung R&D Institute India | other | Agreement | Yes |
Yes
| approved | No | S5‑236589 | |||
6.5.8 | Management Aspect of 5GLAN |   | ||||||||||
6.5.8.1 | 5GLAN_Mgt_WoP#1 |   | ||||||||||
6.5.8.2 | 5GLAN_Mgt_WoP#2 |   | ||||||||||
6.5.9 | Management Aspects of NTN |   | ||||||||||
6.5.9.1 | OAM_NTN_WoP#1 | S5‑236643 | Rel-18 CR TS 28.530 Add management capability support for integration with satellite networking | China Unicom, CATT | CR | Approval | Yes |
Yes
| revised | No | S5‑237098 | |
S5‑237098 | Rel-18 CR TS 28.530 Add management capability support for integration with satellite networking | China Unicom, CATT,China Telecom | CR | Approval | Yes |
Yes
| not pursued | No | S5‑236643 | |||
S5‑236752 | Add requirement for IOT-NTN management | CATT | CR | Approval | Yes |
Yes
| revised | No | S5‑237099 | |||
S5‑237099 | Add requirement for IOT-NTN management | CATT | CR | Approval | Yes |
Yes
| agreed | No | S5‑236752 | |||
S5‑236870 | Rel-17 CR TS 28.530 Add management capability to support IoT NTN scenario | China Telecom | CR | Agreement | Yes |
Yes
| merged | No | S5‑237098 | |||
6.5.9.2 | OAM_NTN_WoP#2 | S5‑236465 | Rel-18 CR TS28.541 Remove the duplicated attributes | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑236837 | |
S5‑236753 | Add NRM Info Model definitions for IOT-NTN management | CATT | CR | Approval | Yes |
Yes
| revised | No | S5‑237100 | |||
S5‑237100 | Add NRM Info Model definitions for IOT-NTN management | CATT | CR | Approval | Yes |
Yes
| agreed | No | S5‑236753 | |||
S5‑236754 | Add NRM solution set definitions for IOT-NTN management | CATT | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑236837 | Rel-18 CR TS28.541 Remove the duplicated attributes | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑236465 | |||
6.5.9.3 | OAM_NTN_WoP#3 | S5‑236593 | Rel-18 CR TS 28.552 Adapt the Average delay DL air-interface measurement and Distribution of delay DL air-interface measurement to support cases for MEO and GEO satellite links | China Unicom | CR | Approval | Yes |
Yes
| revised | No | S5‑237101 | |
S5‑237101 | Rel-18 CR TS 28.552 Adapt the Average delay DL air-interface measurement and Distribution of delay DL air-interface measurement to support cases for MEO and GEO satellite links | China Unicom | CR | Approval | Yes |
Yes
| agreed | No | S5‑236593 | |||
S5‑236595 | Rel-18 CR TS 28.554 Adapt the Downlink delay in NG-RAN and gNB-DU to support cases for MEO and GEO satellite links | China Unicom | CR | Approval | Yes |
Yes
| revised | No | S5‑237102 | |||
S5‑237102 | Rel-18 CR TS 28.554 Adapt the Downlink delay in NG-RAN and gNB-DU to support cases for MEO and GEO satellite links | China Unicom | CR | Approval | Yes |
Yes
| agreed | No | S5‑236595 | |||
6.5.10 | Management of cloud-native Virtualized Network Functions |   | ||||||||||
6.5.10.1 | MCVNF_WoP#1 | S5‑236488 | Rel-18 CR TS 28.533 Add a note sentence in clause A.4 | China Mobile (Hangzhou) Inf. | CR | Agreement | Yes |
Yes
| withdrawn | Yes | ||
S5‑236510 | Rel-18 CR TS 28.533 Add a note sentence in clause A.4 | China Mobile (Hangzhou) Inf. | CR | Agreement | Yes |
Yes
| withdrawn | Yes | ||||
S5‑236511 | Add a note sentence in clause A.4 | China Mobile | CR | Agreement | Yes |
Yes
| revised | No | S5‑237103 | |||
S5‑237103 | Add a note sentence in clause A.4 | China Mobile | CR | Agreement | Yes |
Yes
| agreed | No | S5‑236511 | |||
6.5.10.2 | MCVNF_WoP#2 | S5‑236739 | Add the introduction for the procedure of NF instance creation | ZTE Corporation | CR | Approval | Yes |
Yes
| revised | No | S5‑237106 | |
S5‑237106 | Add the introduction for the procedure of NF instance creation | ZTE Corporation | CR | Approval | Yes |
Yes
| not pursued | No | S5‑236739 | |||
S5‑236740 | Add the introduction for the procedure of NF instance deletion | ZTE Corporation | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑236742 | Add the introduction for the procedure of NF instance modification | ZTE Corporation | CR | Approval | Yes |
Yes
| revised | No | S5‑237107 | |||
S5‑237107 | Add the introduction for the procedure of NF instance modification | ZTE Corporation | CR | Approval | Yes |
Yes
| revised | No | S5‑237223 | S5‑236742 | ||
S5‑237223 | Add the introduction for the procedure of NF instance modification | ZTE Corporation | CR | Approval | Yes |
Yes
| agreed | No | S5‑237107 | |||
6.5.10.3 | MCVNF_WoP#3 | S5‑236523 | Update the scope of TS 28.531 | Ericsson | CR | Approval | Yes |
Yes
| revised | No | S5‑237108 | |
S5‑237108 | Update the scope of TS 28.531 | Ericsson | CR | Approval | Yes |
Yes
| agreed | No | S5‑236523 | |||
6.5.11 | Management Aspects of 5G Network Sharing Phase2 |   | ||||||||||
6.5.11.1 | MANS_ph2_WoP#1 | S5‑236316 | Rel-18 CR TS 28.541 Add YAML solution set for NRM for operator specific QoS model for RAN sharing | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||
S5‑236317 | Rel-18 CR TS28.541 Udpate clause O.3 RAN Sharing usage recommendation | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑236318 | Rel-18 CR TS 28.541 Address EP_F1 issue for MOCN RAN sharing scenario | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑237109 | Rel-18 CR TS 28.541 Address EP_F1 issue for MOCN RAN sharing scenario | Huawei | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
6.5.11.2 | MANS_ph2_WoP#2 | S5‑236524 | Rel-18 CR 28.541 Update recommended QoS model usage for Shared RAN (yang update) | Ericsson Inc. | CR | Approval | Yes |
Yes
| revised | No | S5‑237110 | |
S5‑237110 | Rel-18 CR 28.541 Update recommended QoS model usage for Shared RAN (yang update) | Ericsson Inc. | CR | Approval | Yes |
Yes
| agreed | No | S5‑236524 | |||
S5‑236767 | Rel-18 CR TS 28.552 Add PLMN granularity for performance measurements for NG-RAN MOCN network sharing scenario | S5 | CR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑236772 | Rel-18 CR TS 28.552 Add PLMN granularity for performance measurements for NG-RAN MOCN network sharing scenario | China Unicom | CR | Approval | Yes |
Yes
| revised | No | S5‑237111 | |||
S5‑237111 | Rel-18 CR TS 28.552 Add PLMN granularity for performance measurements for NG-RAN MOCN network sharing scenario | China Unicom | CR | Approval | Yes |
Yes
| agreed | No | S5‑236772 | |||
6.5.12 | Management Aspects of URLLC |   | ||||||||||
6.5.12.1 | URLLC_Mgt_WoP#1 | S5‑236382 | Rel-18 CR TS 28.541 Fix Slice NRM YAML definition for dLReliability and uLReliability | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||
S5‑236856 | Rel-18 CR 28.541 Modify the attributes of UL and DL latency in RAN | China Unicom | CR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑236864 | Rel-18 CR 28.541 Modify the attributes of UL and DL latency in RAN | China Unicom | CR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑236866 | Rel-18 CR 28.541 Modify the attributes of UL and DL latency in RAN | China Unicom | CR | Approval | Yes |
Yes
| revised | No | S5‑237112 | |||
S5‑237112 | Rel-18 CR 28.541 Modify the attributes of UL and DL latency in RAN | China Unicom | CR | Approval | Yes |
Yes
| not pursued | No | S5‑236866 | |||
6.5.12.2 | URLLC_Mgt_WoP#2 | S5‑236857 | Rel-18 CR 28.554 Add new KPI on DL reliability with delay threshold in RAN | China Unicom | CR | Approval | Yes |
Yes
| withdrawn | Yes | ||
S5‑236865 | Rel-18 CR 28.554 Add new KPI on DL reliability with delay threshold in RAN | China Unicom | CR | Approval | Yes |
Yes
| not pursued | No | ||||
6.6 | OAM&P Rel-18 Work Items - Support of New Services |   | ||||||||||
6.6.1 | Access control for management service |   | ||||||||||
6.6.1.1 | MSAC_WoP#1 | S5‑236666 | Rewised WID Access control for management service | Nokia UK | WID revised | Approval | Yes |
Yes
| revised | No | S5‑237169 | |
S5‑237169 | Rewised WID Access control for management service | Nokia UK | WID revised | Approval | Yes |
Yes
| agreed | No | S5‑236666 | |||
S5‑236668 | Rel-18 InputToDraftCR 28.533 on Entities and interactions for Access control | Nokia UK | draftCR | Approval | Yes |
Yes
| noted | No | ||||
6.6.1.2 | MSAC_WoP#2 | S5‑236667 | Rel-18 InputToDraftCR on 28.533 on Access control related to ConditionForMOIs | Nokia UK | draftCR | Yes |
Yes
| noted | No | |||
6.6.1.3 | MSAC_WoP#3 | S5‑236669 | Rel-18 InputToDraftCR 28.533 on Stage 3 for Access control for management service | Nokia UK | draftCR | Approval | Yes |
Yes
| noted | No | ||
6.6.1.4 | MSAC_WoP#4 | S5‑236670 | Rel-18 pCR 28.xxx sections and headers for new proposed TS on access control | Nokia UK | other | Approval | Yes |
Yes
| revised | No | S5‑237170 | |
S5‑237170 | Rel-18 pCR 28.xxx sections and headers for new proposed TS on access control | Nokia UK | other | Approval | Yes |
Yes
| approved | No | S5‑236670 | |||
S5‑236671 | TS 28.xxx Skeleton TS on Access control of Management services | Nokia UK | other | Approval | Yes |
Yes
| approved | No | ||||
6.6.2 | Enhancements of EE for 5G Phase 2 |   | ||||||||||
6.6.2.1 | EE5GPLUS_Ph2_WoP#1 | S5‑236418 | Rel-18 CR 28.310 Update on energy saving for UPFs | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑237058 | |
S5‑237058 | Rel-18 CR 28.310 Update on energy saving for UPFs | Huawei, China Mobile | CR | Agreement | Yes |
Yes
| agreed | No | S5‑236418 | |||
S5‑236421 | Rel-18 CR 28.622 Add energy saving attributes to IOC ManagedFunction | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑236422 | Rel-18 CR 28.623 Add energy saving attributes to IOC ManagedFunction | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑236513 | Add definitions | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑237094 | |||
S5‑237094 | Add definitions | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑236513 | |||
S5‑236514 | Describe example scenarios involving multiple roles in EE KPI building | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑237085 | |||
S5‑237085 | Describe example scenarios involving multiple roles in EE KPI building | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑236514 | |||
S5‑236796 | Rel-18 CR TS 28.310 Fix the description on UPFs for energy saving | China Mobile | CR | Approval | Yes |
Yes
| merged | No | S5‑237058 | |||
S5‑236800 | Rel-18 CR TS 28.310 Update on energy saving for NEs and NFs | China Mobile | CR | Approval | Yes |
Yes
| merged | No | S5‑237058 | |||
S5‑237059 | LS to SA2 on the scope of the ES solutions for 5GC functions | Huawei | LS out | Approval | No |
Yes
| withdrawn | Yes | ||||
6.6.2.2 | EE5GPLUS_Ph2_WoP#2 | S5‑236855 | Rel-18 Add KPI on Energy Efficiency of URLLC Network Slice based on reliability | China Unicom, Ericsson | CR | Approval | Yes |
Yes
| withdrawn | Yes | ||
S5‑236863 | Rel-18 Add KPI on Energy Efficiency of URLLC Network Slice based on reliability | China Unicom, Ericsson | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑236872 | Rel-18 CR TS 28.554 KPI for EE of URLLC NS based on its reliability | Samsung Electronics Czech | CR | Approval | Yes |
Yes
| not treated | No | ||||
6.6.3 | Management of non-public networks phase 2 |   | ||||||||||
6.6.3.1 | OAM_NPN_Ph2_WoP#1 |   | ||||||||||
6.6.3.2 | OAM_NPN_Ph2_WoP#2 | S5‑236420 | Rel-18 CR TS 28.557 Add use case and requirements for SLA monitoring and assurance | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑236942 | |
S5‑236942 | Rel-18 CR TS 28.557 Add use case and requirements for SLA monitoring and assurance | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑236420 | |||
6.6.3.3 | OAM_NPN_Ph2_WoP#3 | S5‑236419 | Rel-18 CR TS 28.557 Add use case and requirements for dedicated resource demand for Smart Grid Utilities | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑236943 | |
S5‑236943 | Rel-18 CR TS 28.557 Add use case and requirements for dedicated resource demand for Smart Grid Utilities | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑236419 | |||
6.6.3.4 | OAM_NPN_Ph2_WoP#4 |   | ||||||||||
6.6.4 | Network and Service Operations for Energy Utilities |   | ||||||||||
6.6.4.1 | NSOEU_WoP#1 | S5‑236842 | Rel-18 pCR 28.318 clause 3 Definitions and Acronyms | Nokia | pCR | Agreement | Yes |
Yes
| revised | No | S5‑237061 | |
S5‑237061 | Rel-18 pCR 28.318 clause 3 Definitions and Acronyms | Nokia | pCR | Agreement | Yes |
Yes
| approved | No | S5‑236842 | |||
S5‑237039 | Draft TS 28.318 | Samsung | draft TS | Approval | No |
Yes
| email approval | No | ||||
S5‑237062 | Draft TS 28.318 | Samsung | draft TS | Approval | No |
Yes
| email approval | No | ||||
S5‑237118 | Documenting KPIs in TS 28.318 | Samsung | discussion | Discussion | Yes |
Yes
| noted | No | ||||
6.6.4.2 | NSOEU_WoP#2 | S5‑236238 | Rel-18 pCR 28.318 5.Y Exposed performance monitoring requirements | Samsung, EUTC, BMWK, EDF, Deutsche Telekom | pCR | Approval | Yes |
Yes
| revised | No | S5‑237063 | |
S5‑237063 | Rel-18 pCR 28.318 5.Y Exposed performance monitoring requirements | Samsung, EUTC, BMWK, EDF, Deutsche Telekom | pCR | Approval | Yes |
Yes
| approved | No | S5‑236238 | |||
S5‑236342 | Rel-18 pCR 28.318 Availability KPI definition | Nokia Hungary | pCR | Approval | Yes |
Yes
| revised | No | S5‑237064 | |||
S5‑237064 | Rel-18 pCR 28.318 Availability KPI definition | Nokia Hungary | pCR | Approval | Yes |
Yes
| approved | No | S5‑236342 | |||
S5‑236375 | Measurements for cell service status for energy utilities | Samsung, EUTC, Deutsche Telekom, EDF | CR | Agreement | Yes |
Yes
| not treated | No | ||||
S5‑236376 | PI for cell and network availability for energy utilities | Samsung, EUTC, EDF, Deutsche Telekom | CR | Agreement | Yes |
Yes
| not treated | No | ||||
S5‑236378 | NRM enhancements to support Network Performance Monitoring for Energy utilities | Samsung, EUTC, EDF, Deutsche Telekom | CR | Agreement | Yes |
Yes
| not treated | No | ||||
6.6.4.3 | NSOEU_WoP#3 | S5‑236237 | Rel-18 pCR 28.318 5.X Exposed coordinated recovery requirements | Samsung, EUTC, BMWK, EDF, Deutsche Telekom | pCR | Approval | Yes |
Yes
| revised | No | S5‑237067 | |
S5‑237067 | Rel-18 pCR 28.318 5.X Exposed coordinated recovery requirements | Samsung, EUTC, BMWK, EDF, Deutsche Telekom | pCR | Approval | Yes |
Yes
| approved | No | S5‑236237 | |||
S5‑236239 | Rel-18 pCR 28.318 Annex X Coordinated energy service recovery business relationship model | Samsung, EUTC, BMWK, EDF, Deutsche Telekom | pCR | Approval | Yes |
Yes
| revised | No | S5‑237069 | |||
S5‑237069 | Rel-18 pCR 28.318 Annex X Coordinated energy service recovery business relationship model | Samsung, EUTC, BMWK, EDF, Deutsche Telekom | pCR | Approval | Yes |
Yes
| approved | No | S5‑236239 | |||
S5‑236240 | Rel-18 pCR 28.318 Annex Y Coordinated energy recovery scenarios | Samsung, EUTC, BMWK, EDF, Deutsche Telekom | pCR | Approval | Yes |
Yes
| revised | No | S5‑237070 | |||
S5‑237070 | Rel-18 pCR 28.318 Annex Y Coordinated energy recovery scenarios | Samsung, EUTC, BMWK, EDF, Deutsche Telekom | pCR | Approval | Yes |
Yes
| approved | No | S5‑236240 | |||
S5‑236343 | Rel-18 pCR 28.318 Availability KPI definition | Nokia Hungary | pCR | Discussion | No |
Yes
| withdrawn | Yes | ||||
S5‑236377 | NRM enhancements to support Energy utility and telecommunication coordinated rapid recovery of energy service | Samsung, EUTC, EDF, Deutsche Telekom | CR | Agreement | Yes |
Yes
| not treated | No | ||||
S5‑236379 | Rel-18 pCR 28.318 6.X Coordinated energy recovery procedures | Samsung, EUTC, EDF, Deutsche Telekom | pCR | Approval | Yes |
Yes
| revised | No | S5‑237071 | |||
S5‑237071 | Rel-18 pCR 28.318 6.X Coordinated energy recovery procedures | Samsung, EUTC, EDF, Deutsche Telekom | pCR | Approval | Yes |
Yes
| approved | No | S5‑236379 | |||
S5‑236380 | NOSEU approach to exposing UPS capacity | Samsung, EUTC, EDF, Deutsche Telekom | discussion | Discussion | Yes |
Yes
| noted | No | ||||
S5‑236840 | Rel-18 pCR 28.318 Annex A.Y perf thresh procedure | Nokia | pCR | Agreement | Yes |
Yes
| revised | No | S5‑237065 | |||
S5‑237065 | Rel-18 pCR 28.318 Annex A.Y perf thresh procedure | Nokia | pCR | Agreement | Yes |
Yes
| approved | No | S5‑236840 | |||
S5‑236841 | Rel-18 pCR 28.318 Annex A.Y mgmtdata procedure | Nokia | pCR | Agreement | Yes |
Yes
| revised | No | S5‑237066 | |||
S5‑237066 | Rel-18 pCR 28.318 Annex A.Y mgmtdata procedure | Nokia | pCR | Agreement | Yes |
Yes
| approved | No | S5‑236841 | |||
6.6.4.4 | NSOEU_WoP#4 | S5‑236241 | Rel-18 pCR 28.318 Address editor's notes | Samsung, EUTC, EDF, BMWK, Deutsche Telekom | pCR | Approval | Yes |
Yes
| revised | No | S5‑237072 | |
S5‑237072 | Rel-18 pCR 28.318 Address editor's notes | Samsung, EUTC, EDF, BMWK, Deutsche Telekom | pCR | Approval | Yes |
Yes
| approved | No | S5‑236241 | |||
S5‑236256 | Rel-18 pCR 28.318 Clarifications | EUTC, Samsung, BMWK, EDF, Deutsche Telekom | pCR | Approval | Yes |
Yes
| revised | No | S5‑237073 | |||
S5‑237073 | Rel-18 pCR 28.318 Clarifications | EUTC, Samsung, BMWK, EDF, Deutsche Telekom | pCR | Approval | Yes |
Yes
| approved | No | S5‑236256 | |||
S5‑236381 | Rel-18 pCR 28.318 Exposure of SA5 APIs to verticals through CAPIF | Nokia Hungary | discussion | Discussion | Yes |
Yes
| noted | No | ||||
S5‑236848 | Discussion DNs in NSOEU | Nokia | discussion | Discussion | No |
Yes
| withdrawn | Yes | ||||
6.7 | OAM&P Studies - Intelligence and Automation |   | ||||||||||
6.7.1 | Study on enhancement of autonomous network levels |   | ||||||||||
6.7.1.1 | FS_eANL_WoP#1 | S5‑236760 | pCR TR 28.910 rapporteur clean up | China Mobile | pCR | Approval | Yes |
Yes
| approved | No | ||
S5‑236761 | pCR TR 28.910 Add conclusion and recommendation | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑237171 | |||
S5‑237171 | pCR TR 28.910 Add conclusion and recommendation | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑236761 | |||
S5‑237239 | pCR TR 28.910 Add conclusion and recommendation | China Mobile, Huawei | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑236762 | Presentation of Report to TSG TR 28.910 Version 1.0.0 | China Mobile | TS or TR cover | Approval | Yes |
Yes
| approved | No | ||||
6.7.1.2 | FS_eANL_WoP#2 |   | ||||||||||
6.7.1.3 | FS_eANL_WoP#3 | S5‑236395 | pCR TR 28.910 Add solution for 5GC NF deployment | Huawei, China Mobile | draftCR | Approval | Yes |
Yes
| revised | No | S5‑237172 | |
S5‑237172 | pCR TR 28.910 Add solution for 5GC NF deployment | Huawei, China Mobile | draftCR | Approval | Yes |
Yes
| revised | No | S5‑237243 | S5‑236395 | ||
S5‑237243 | pCR TR 28.910 Add solution for 5GC NF deployment | Huawei, China Mobile | draftCR | Approval | Yes |
Yes
| approved | No | S5‑237172 | |||
6.7.1.4 | FS_eANL_WoP#4 |   | ||||||||||
6.7.1.5 | Draft TR email approval | S5‑237115 | Draft TR 28.910 | China Mobile | draft TR | Approval | No |
Yes
| email approval | No | ||
6.7.2 | Study on evaluation of autonomous network levels |   | ||||||||||
6.7.2.1 | FS_ANLEVA_WoP#1 |   | ||||||||||
6.7.2.2 | FS_ANLEVA_WoP#2 | S5‑236802 | DP on Effectiveness Indicators in Autonomous Network | China Mobile Com. Corporation | discussion | Discussion | Yes |
Yes
| noted | No | ||
6.7.2.3 | FS_ANLEVA_WoP#3 |   | ||||||||||
6.7.2.4 | FS_ANLEVA_WoP#4 |   | ||||||||||
6.7.2.5 | Draft TR email approval |   | ||||||||||
6.7.3 | Study on intent-driven management for network slicing |   | ||||||||||
6.7.3.1 | FS_NETSLICE_IDMS_WoP#1 | S5‑236487 | pCR 28.836 Add solution of modelling CNSliceProfile attributes as intent expectation for CN network slice subnetwork | Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||
6.7.3.2 | FS_NETSLICE_IDMS_WoP#2 | S5‑236694 | pCR TR 28.836 Add definitions | L.M. Ericsson Limited, Deutsche Telekom AG | pCR | Approval | Yes |
Yes
| noted | No | ||
S5‑236695 | pCR TR 28.836 Enhance benefit description in 4.6 | L.M. Ericsson Limited, Deutsche Telekom AG, Telefónica, Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑237174 | |||
S5‑237174 | pCR TR 28.836 Enhance benefit description in 4.6 | L.M. Ericsson Limited, Deutsche Telekom AG, Telefónica, Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑236695 | |||
6.7.3.3 | FS_NETSLICE_IDMS_WoP#3 |   | ||||||||||
6.7.3.4 | FS_NETSLICE_IDMS_WoP#4 | S5‑236507 | Rel-18_CR_28836_Correct issues of procedure for NS delivering and assurance | ZTE Corporation | CR | Approval | Yes |
Yes
| withdrawn | Yes | ||
S5‑236509 | Rel-18_CR_28836_Correct issues of procedure for NS delivering and assurance | ZTE Corporation | pCR | Approval | Yes |
Yes
| approved | No | ||||
6.7.3.5 | FS_NETSLICE_IDMS_WoP#5 |   | ||||||||||
6.7.3.6 | Draft TR email approval | S5‑237173 | Draft TR 28.836 | Ericsson | draft TR | Approval | No |
Yes
| email approval | No | ||
6.7.4 | Study on Fault Supervision Evolution |   | ||||||||||
6.7.4.1 | FS_FSEV_WoP#1 | S5‑236425 | pCR TR 28.830 Add description of relation with performance management | Huawei, China Mobile | pCR | Approval | Yes |
Yes
| revised | No | S5‑237175 | |
S5‑237175 | pCR TR 28.830 Add description of relation with performance management | Huawei, China Mobile | pCR | Approval | Yes |
Yes
| noted | No | S5‑236425 | |||
6.7.4.2 | FS_FSEV_WoP#2 | S5‑236426 | pCR TR 28.830 Add solution of performance related alarm analysis | Huawei, China Mobile | pCR | Approval | Yes |
Yes
| revised | No | S5‑237176 | |
S5‑237176 | pCR TR 28.830 Add solution of performance related alarm analysis | Huawei, China Mobile | pCR | Approval | Yes |
Yes
| noted | No | S5‑236426 | |||
S5‑236427 | pCR TR 28.830 Add solution of root cause analysis enhancement | Huawei, China Mobile | pCR | Approval | Yes |
Yes
| revised | No | S5‑237177 | |||
S5‑237177 | pCR TR 28.830 Add solution of root cause analysis enhancement | Huawei, China Mobile | pCR | Approval | Yes |
Yes
| noted | No | S5‑236427 | |||
S5‑236428 | pCR TR 28.830 Add solution of fault impact analysis | Huawei, China Mobile | pCR | Approval | Yes |
Yes
| revised | No | S5‑237178 | |||
S5‑237178 | pCR TR 28.830 Add solution of fault impact analysis | Huawei, China Mobile | pCR | Approval | Yes |
Yes
| approved | No | S5‑236428 | |||
6.7.4.3 | FS_FSEV_WoP#3 | S5‑236429 | pCR TR 28.830 Add description for MDA and close loop control | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑237179 | |
S5‑237179 | pCR TR 28.830 Add description for MDA and close loop control | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑236429 | |||
6.7.4.4 | Draft TR email approval | S5‑237040 | Draft TR 28.830 | China Mobile | draft TR | Approval | No |
Yes
| email approval | No | ||
6.8 | OAM&P Studies - Management Architecture and Mechanisms |   | ||||||||||
6.8.1 | Study on Data management phase 2 |   | ||||||||||
6.8.1.1 | FS_MADCOL_ph2_WoP#1 | S5‑236563 | pCR TR 28.842 Potential solution for discovery of stored management data | Microsoft Europe SARL | pCR | Approval | Yes |
Yes
| noted | No | ||
S5‑237180 | pCR TR 28.842 Potential solution for discovery of stored management data | Microsoft Europe SARL | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
6.8.1.2 | FS_MADCOL_ph2_WoP#2 | S5‑236562 | pCR TR 28.842 Potential solution for retrieval of stored management data | Microsoft Europe SARL | pCR | Approval | Yes |
Yes
| revised | No | S5‑237181 | |
S5‑237181 | pCR TR 28.842 Potential solution for retrieval of stored management data | Microsoft Europe SARL, Ericsson, Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑236562 | |||
S5‑236585 | Rel-18 pCR 28.842 New KI on Management data model | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑236587 | Rel-18 pCR 28.842 New KI on Context information for historical data | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
6.8.1.3 | FS_MADCOL_ph2_WoP#3 |   | ||||||||||
6.8.1.4 | FS_MADCOL_ph2_WoP#4 |   | ||||||||||
6.8.1.5 | Draft TR email approval | S5‑237182 | Draft TR 28.842 | Nokia | draft TR | Approval | No |
Yes
| email approval | No | ||
6.9 | OAM&P Studies - Support of New Services |   | ||||||||||
6.9.1 | Study on Key Quality Indicators (KQIs)for 5G service experience |   | ||||||||||
6.9.1.1 | FS_KQI_5G_WoP#1 |   | ||||||||||
6.9.1.2 | FS_KQI_5G_WoP#2 | S5‑236469 | pCR TR 28.863 Issue # 3: Description for KQIs for Video Uploading | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑237187 | |
S5‑237187 | pCR TR 28.863 Issue # 3: Description for KQIs for Video Uploading | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑236469 | |||
S5‑236471 | pCR TR 28.863 Issue # 3: Solution of KQIs for Video Uploading | Hawei | pCR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑236678 | pCR TR 28.863 Issue4 definition of Remote controll | Huawei | pCR | Yes |
Yes
| withdrawn | Yes | |||||
S5‑236741 | pCR TR 28.863 Issue # 3: Solution of KQIs for Video Uploading | HUAWEI TECHNOLOGIES Co. Ltd. | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑236746 | pCR TR 28.863 Issue # 3: Solution of KQIs for Video Uploading | HUAWEI | pCR | Approval | Yes |
Yes
| revised | No | S5‑237189 | |||
S5‑237189 | pCR TR 28.863 Issue # 3: Solution of KQIs for Video Uploading | HUAWEI | pCR | Approval | Yes |
Yes
| approved | No | S5‑236746 | |||
6.9.1.3 | FS_KQI_5G_WoP#3 | S5‑236472 | pCR TR 28.863 Issue4 definition of Remote controll | Hawei | pCR | Approval | Yes |
Yes
| withdrawn | Yes | ||
S5‑236679 | pCR TR 28.863 Issue4 definition of Remote controll | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑237190 | |||
S5‑237190 | pCR TR 28.863 Issue4 definition of Remote controll | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑236679 | |||
6.9.1.4 | FS_KQI_5G_WoP#4 |   | ||||||||||
6.9.1.5 | FS_KQI_5G_WoP#5 | S5‑236481 | pCR TR 28.863 Issue5 Description of SLS requirements | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑237191 | |
S5‑237191 | pCR TR 28.863 Issue5 Description of SLS requirements | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑237240 | S5‑236481 | ||
S5‑237240 | pCR TR 28.863 Issue5 Description of SLS requirements | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑237191 | |||
6.9.1.6 | Draft TR email approval | S5‑237188 | Draft TR 28.863 | Huawei | draft TR | Approval | No |
Yes
| email approval | No | ||
6.9.2 | Study on Deterministic Communication Service Assurance |   | ||||||||||
6.9.2.1 | FS_DCSA_WoP#1 |   | ||||||||||
6.9.2.2 | FS_DCSA_WoP#2 | S5‑236432 | pCR TR 28.865 Add conclusion of issue1 provisioning of network functions | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑237192 | |
S5‑237192 | pCR TR 28.865 Add conclusion of issue1 provisioning of network functions | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑236432 | |||
6.9.2.3 | FS_DCSA_WoP#3 |   | ||||||||||
6.9.2.4 | FS_DCSA_WoP#4 | S5‑236430 | pCR TR 28.865 Update solution of service assurance for video monitoring | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑237193 | |
S5‑237193 | pCR TR 28.865 Update solution of service assurance for video monitoring | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑236430 | |||
S5‑236431 | pCR TR 28.865 Update solution of service assurance for PLC control | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑237194 | |||
S5‑237194 | pCR TR 28.865 Update solution of service assurance for PLC control | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑236431 | |||
S5‑236433 | pCR TR 28.865 Add conclusion of issue2 service assurance for video monitoring | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑237195 | |||
S5‑237195 | pCR TR 28.865 Add conclusion of issue2 service assurance for video monitoring | Huawei | pCR | Approval | Yes |
Yes
| noted | No | S5‑236433 | |||
S5‑236434 | pCR TR 28.865 Add conclusion of issue3 service assurance for PLC control | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑237196 | |||
S5‑237196 | pCR TR 28.865 Add conclusion of issue3 service assurance for PLC control | Huawei | pCR | Approval | Yes |
Yes
| noted | No | S5‑236434 | |||
S5‑236435 | pCR TR 28.865 Add conclusions and recommendations for the FS_DCSA study item | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
6.9.2.5 | FS_DCSA_WoP#5 |   | ||||||||||
6.9.2.6 | Draft TR email approval | S5‑237242 | Draft TR 28.865 | Huawei | draft TR | Approval | No |
Yes
| email approval | No | ||
7 | Charging |   | ||||||||||
7.1 | Charging Plenary | S5‑236209 | CH agenda and time plan | SA5 SWG CH Chair (MATRIXX Software) | agenda | Yes |
Yes
| revised | No | S5‑236885 | ||
S5‑236885 | CH agenda and time plan | SA5 SWG CH Chair (MATRIXX Software) | agenda | - | Yes |
Yes
| noted | No | S5‑236209 | |||
S5‑236210 | Collection of useful contributions and external communication documents | Huawei Tech.(UK) Co.. Ltd | discussion | Yes |
Yes
| revised | No | S5‑236886 | ||||
S5‑236886 | Collection of useful contributions and external communication documents | Huawei Tech.(UK) Co.. Ltd | discussion | - | Yes |
Yes
| noted | No | S5‑236210 | |||
S5‑236212 | Charging exec report | SA5 SWG CH Chair (MATRIXX Software) | report | Yes |
Yes
| noted | No | |||||
S5‑236230 | Reply LS on CHF Logic Realization wrt/ Spending Limits functionality | S2-2309511 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑236896 | Reply to: Reply LS on CHF Logic Realization wrt/ Spending Limits functionality | MATRIXX Software | LS out | approval | Yes |
Yes
| approved | No | ||||
S5‑236274 | Discussion paper on Rel-19 preparation – CH group | SWG CH Chair | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑236596 | Discussion paper on charging open API in forge | Huawei | discussion | Discussion | Yes |
Yes
| noted | No | ||||
7.2 | New Charging Work Item proposals | S5‑236275 | NEF charging framework enhancements for AI/ML | OPPO | discussion | Decision | Yes |
Yes
| noted | No | ||
7.3 | Charging Maintenance and Rel-18 small Enhancements | S5‑236384 | Rel-18 CR TS 32.291 Service Consumption with unlimited quota | Nokia. Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | ||
S5‑236385 | Discussion Paper for Unlimited Quota charging scenario | Nokia, Nokia Shanghai Bell | discussion | Agreement | Yes |
Yes
| noted | No | ||||
S5‑236597 | Discussion paper on triggers in charging stage 2 and stage 3 | Huawei | discussion | Discussion | Yes |
Yes
| noted | No | ||||
S5‑236598 | Remove the triggers in charging data message | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑236599 | Remove the triggers in charging data message | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑236600 | Remove the triggers in charging data message | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑236601 | Remove the triggers in charging data message | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑236602 | Correction on triggers for AMF charging | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑236603 | Correction on triggers for AMF charging | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑237019 | |||
S5‑237019 | Correction on triggers for AMF charging | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑236603 | |||
S5‑236604 | Correction on triggers for AMF charging | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑237020 | |||
S5‑237020 | Correction on triggers for AMF charging | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑236604 | |||
S5‑236605 | Editorial correction | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑236606 | Editorial correction | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑236607 | Rel-18 CR 32.255 Clarification on roaming charging profile | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑237029 | |||
S5‑237029 | Rel-18 CR 32.255 Clarification on roaming charging profile | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑236607 | |||
S5‑236608 | Update the roaming charging profile transfer | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑237030 | |||
S5‑237030 | Update the roaming charging profile transfer | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑236608 | |||
S5‑236609 | Clarification on QBC triggers | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑237031 | |||
S5‑237031 | Clarification on QBC triggers | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑236609 | |||
S5‑236610 | Clarification on message flow of home routed charging | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑236696 | Rel-18 CR 32.291 Correction of HTTP reference | Ericsson LM | CR | Agreement | Yes |
Yes
| revised | No | S5‑237032 | |||
S5‑237032 | Rel-18 CR 32.291 Correction of HTTP reference | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | S5‑236696 | |||
S5‑236697 | Rel-18 CR 32.291 Correction of content of type problem json | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑236698 | Rel-17 CR 32.298 Correction of record opening time | Ericsson LM | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑236699 | Rel-18 CR 32.298 Correction of record opening time | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑236700 | Rel-17 CR 32.255 Correction of record opening time | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑236701 | Rel-18 CR 32.255 Correction of record opening time | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑236702 | Rel-17 CR 32.298 Correction of duration | Ericsson LM | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑236703 | Rel-18 CR 32.298 Correction of duration | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑236704 | Rel-17 CR 32.298 Correction of invocation timestamp | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑236705 | Rel-18 CR 32.298 Correction of invocation timestamp | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑236706 | Rel-17 CR 32.255 Correction of invocation timestamp | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑236707 | Rel-18 CR 32.255 Correction of invocation timestamp | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑236708 | Rel-17 CR 32.291 Correction of invocation timestamp | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑236709 | Rel-18 CR 32.291 Correction of invocation timestamp | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑236710 | Rel-17 CR 32.260 Correction of invocation timestamp | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑236711 | Rel-18 CR 32.260 Correction of invocation timestamp | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑236712 | Rel-17 CR 32.255 Correction of event time stamp and service specific units in CDR | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑236713 | Rel-18 CR 32.255 Correction of event time stamp and service specific units in CDR | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑236714 | Rel-17 CR 32.255 Correction of management trigger | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑237021 | |||
S5‑237021 | Rel-17 CR 32.255 Correction of management trigger | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑236714 | |||
S5‑236715 | Rel-18 CR 32.255 Correction of management trigger | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑237022 | |||
S5‑237022 | Rel-18 CR 32.255 Correction of management trigger | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑236715 | |||
S5‑236716 | Rel-17 CR 32.255 QBC Charging Session Continuity Identification at V-SMF Change | Ericsson LM | CR | Agreement | Yes |
Yes
| revised | No | S5‑237023 | |||
S5‑237023 | Rel-17 CR 32.255 QBC Charging Session Continuity Identification at V-SMF Change | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | S5‑236716 | |||
S5‑236717 | Rel-18 CR 32.255 QBC Charging Session Continuity Identification at V-SMF Change | Ericsson LM | CR | Agreement | Yes |
Yes
| revised | No | S5‑237024 | |||
S5‑237024 | Rel-18 CR 32.255 QBC Charging Session Continuity Identification at V-SMF Change | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | S5‑236717 | |||
S5‑236718 | Rel-17 CR 32.291 QBC Charging Session Continuity Identification at V-SMF Change | Ericsson LM | CR | Agreement | Yes |
Yes
| revised | No | S5‑237025 | |||
S5‑237025 | Rel-17 CR 32.291 QBC Charging Session Continuity Identification at V-SMF Change | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | S5‑236718 | |||
S5‑236719 | Rel-18 CR 32.291 QBC Charging Session Continuity Identification at V-SMF Change | Ericsson LM | CR | Agreement | Yes |
Yes
| revised | No | S5‑237026 | |||
S5‑237026 | Rel-18 CR 32.291 QBC Charging Session Continuity Identification at V-SMF Change | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | S5‑236719 | |||
S5‑236720 | Rel-17 CR 32.298 QBC Charging Session Continuity Identification at v-SMF Change | Ericsson LM | CR | Agreement | Yes |
Yes
| revised | No | S5‑237027 | |||
S5‑237027 | Rel-17 CR 32.298 QBC Charging Session Continuity Identification at v-SMF Change | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | S5‑236720 | |||
S5‑236721 | Rel-18 CR 32.298 QBC Charging Session Continuity Identification at v-SMF Change | Ericsson LM | CR | Agreement | Yes |
Yes
| revised | No | S5‑237028 | |||
S5‑237028 | Rel-18 CR 32.298 QBC Charging Session Continuity Identification at v-SMF Change | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | S5‑236721 | |||
7.4 | Rel-18 Charging |   | ||||||||||
7.4.1 | Charging Aspects of Network Slicing Phase 2 | S5‑236282 | Rel-18 pCR 28.203 Introduce Reference Point for NSACF | MATRIXX Software | pCR | Approval | Yes |
Yes
| approved | No | ||
S5‑236283 | Rel-18 CR 32.240 Introduce Reference Point for NSACF | MATRIXX Software | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
S5‑236284 | Rel-18 pCR 28.203 Solve Editor's Note - partial CDRs | MATRIXX Software | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑236285 | Rel-18 pCR 28.203 Solve Editor's Note - trigger description table | MATRIXX Software | pCR | Approval | Yes |
Yes
| revised | No | S5‑236897 | |||
S5‑236897 | Rel-18 pCR 28.203 Solve Editor's Note - trigger description table | MATRIXX Software | pCR | Approval | Yes |
Yes
| approved | No | S5‑236285 | |||
S5‑236286 | Rel-18 pCR 28.203 Solve Editor's Note - charging information | MATRIXX Software | pCR | Approval | Yes |
Yes
| revised | No | S5‑236900 | |||
S5‑236900 | Rel-18 pCR 28.203 Solve Editor's Note - charging information | MATRIXX Software | pCR | Approval | Yes |
Yes
| approved | No | S5‑236286 | |||
S5‑236287 | Rel-18 pCR 28.203 Introduction of Detailed message format for converged charging | MATRIXX Software | pCR | Approval | Yes |
Yes
| revised | No | S5‑236902 | |||
S5‑236902 | Rel-18 pCR 28.203 Introduction of Detailed message format for converged charging | MATRIXX Software | pCR | Approval | Yes |
Yes
| approved | No | S5‑236287 | |||
S5‑236288 | Rel-18 pCR 28.203 Introduction of Bindings for Network slice admission control converged charging | MATRIXX Software | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑236298 | Rel-18 pCR 28.203 Introduction of CHF selection | MATRIXX Software | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑236299 | Rel-18 pCR 28.203 Introduction of CDR description | MATRIXX Software | pCR | Approval | Yes |
Yes
| approved | No | S5‑236903 | |||
S5‑236903 | Rel-18 pCR 28.203 Introduction of CDR description | MATRIXX Software | pCR | Approval | Yes |
Yes
| approved | No | S5‑236299 | |||
S5‑236300 | Rel-18 pCR 28.203 Introduction of Formal network slice admission control charging parameter description | MATRIXX Software | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑236301 | Rel-18 pCR 28.203 Solve Editor's Note on Abort | MATRIXX Software | pCR | Approval | Yes |
Yes
| revised | No | S5‑236898 | |||
S5‑236898 | Rel-18 pCR 28.203 Solve Editor's Note on Abort | MATRIXX Software | pCR | Approval | Yes |
Yes
| approved | No | S5‑236301 | |||
S5‑236611 | Rel-18 pCR 28.203 Clarification on the quota management | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑236899 | |||
S5‑236899 | Rel-18 pCR 28.203 Clarification on the quota management | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑236611 | |||
S5‑236612 | Rel-18 pCR 28.203 Clarification on the triggers | Huawei | pCR | Approval | Yes |
Yes
| merged | No | S5‑236897 | |||
S5‑236722 | Rel-18 pCR 28.203 Update of triggers | Ericsson LM | pCR | Approval | Yes |
Yes
| merged | No | S5‑236897 | |||
S5‑236723 | Rel-18 pCR 28.203 Update of charging data request | Ericsson LM | pCR | Approval | Yes |
Yes
| merged | No | S5‑236900 | |||
S5‑236901 | Rel-18 pCR 28.203 Update of charging data request | Ericsson LM | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑236887 | Draft TS 28.203 | MATRIXX Software | draft TS | Approval | No |
Yes
| email approval | No | ||||
7.4.2 | Charging Aspects for NSSAA | S5‑236289 | Rel-18 pCR 28.204 Introduce Reference Point for NSSAAF | MATRIXX Software | pCR | Approval | Yes |
Yes
| approved | No | ||
S5‑236290 | Rel-18 CR 32.240 Introduce Reference Point for NSSAAF | MATRIXX Software | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
S5‑236291 | Rel-18 pCR 28.204 Addition of applicable triggers | MATRIXX Software | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑236292 | Rel-18 pCR 28.204 Introduction of AAA-S Re-authentication and Re-authorization flows | MATRIXX Software | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑236293 | Rel-18 pCR 28.204 Introduction of AAA-S triggered Network Slice-Specific Authorization Revocation flows | MATRIXX Software | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑236294 | Rel-18 pCR 28.204 Introduce CDR generation | MATRIXX Software | pCR | Approval | Yes |
Yes
| revised | No | S5‑236904 | |||
S5‑236904 | Rel-18 pCR 28.204 Introduce CDR generation | MATRIXX Software | pCR | Approval | Yes |
Yes
| approved | No | S5‑236294 | |||
S5‑236295 | Rel-18 pCR 28.204 Introduce Ga record and CDR file transfer | MATRIXX Software | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑236296 | Rel-18 pCR 28.204 Introduce definition of charging information | MATRIXX Software | pCR | Approval | Yes |
Yes
| revised | No | S5‑236905 | |||
S5‑236905 | Rel-18 pCR 28.204 Introduce definition of charging information | MATRIXX Software | pCR | Approval | Yes |
Yes
| approved | No | S5‑236296 | |||
S5‑236297 | Rel-18 pCR 28.204 Introduce NSSAA specific charging information | MATRIXX Software | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑236888 | Draft TS 28.204 | MATRIXX Software | draft TS | Approval | No |
Yes
| email approval | No | ||||
7.4.3 | Charging Aspects for Enhanced Support of Non-Public Networks | S5‑236414 | Rel-18 CR 32.256 Addition of end user charging for PNI-NPN network usage of access | China Mobile | CR | Approval | Yes |
Yes
| revised | No | S5‑236906 | |
S5‑236906 | Rel-18 CR 32.256 Addition of end user charging for PNI-NPN network usage of access | China Mobile | CR | Approval | Yes |
Yes
| agreed | No | S5‑236414 | |||
S5‑236415 | Rel-18 CR 32.256 Addition of end user charging for SNPN network usage of access | China Mobile | CR | Approval | Yes |
Yes
| revised | No | S5‑236907 | |||
S5‑236907 | Rel-18 CR 32.256 Addition of end user charging for SNPN network usage of access | China Mobile | CR | Approval | Yes |
Yes
| agreed | No | S5‑236415 | |||
S5‑236613 | Addition of the charging principle for SNPN charging | Huawei, China Mobile | CR | Agreement | Yes |
Yes
| revised | No | S5‑236908 | |||
S5‑236908 | Addition of the charging principle for SNPN charging | Huawei, China Mobile | CR | Agreement | Yes |
Yes
| agreed | No | S5‑236613 | |||
7.4.4 | Charging Aspects of IMS Data Channel | S5‑236383 | Rel-18 CR TS 32.260 IMS data channel duration-based charging termination process | Nokia, Nokia Shanghai Bell | CR | Yes |
Yes
| revised | No | S5‑236909 | ||
S5‑236909 | Rel-18 CR TS 32.260 IMS data channel duration-based charging termination process | Nokia, Nokia Shanghai Bell | CR | - | Yes |
Yes
| agreed | No | S5‑236383 | |||
S5‑236413 | Rel-18 CR 32.260 Addition of media information for IMS data channel | China Mobile | CR | Approval | Yes |
Yes
| revised | No | S5‑236910 | |||
S5‑236910 | Rel-18 CR 32.260 Addition of media information for IMS data channel | China Mobile | CR | Approval | Yes |
Yes
| agreed | No | S5‑236413 | |||
S5‑236614 | Support of caller and callee information in stage 3 | Huawei, China Mobile | CR | Agreement | Yes |
Yes
| revised | No | S5‑236911 | |||
S5‑236911 | Support of caller and callee information in stage 3 | Huawei, China Mobile | CR | Agreement | Yes |
Yes
| agreed | No | S5‑236614 | |||
S5‑236615 | Update CHF CDRs | Huawei, China Mobile | CR | Agreement | Yes |
Yes
| revised | No | S5‑236912 | |||
S5‑236912 | Update CHF CDRs | Huawei, China Mobile | CR | Agreement | Yes |
Yes
| agreed | No | S5‑236615 | |||
7.4.5 | Charging Aspects for SMF and MB-SMF to Support 5G Multicast-broadcast Services | S5‑236325 | Add CHF selection mechanism for MB-SMF | China Mobile Com. Corporation, Huawei | CR | Approval | Yes |
Yes
| not pursued | No | ||
S5‑236913 | Add CHF selection mechanism for MB-SMF | China Mobile Com. Corporation, Huawei | other | Approval | Yes |
Yes
| approved | No | ||||
S5‑236326 | Add basic principles for MBS session charging | China Mobile Com. Corporation, Huawei | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑236914 | Add basic principles for MBS session charging | China Mobile Com. Corporation, Huawei | other | Approval | Yes |
Yes
| approved | No | ||||
S5‑236327 | Add 5MBS CDR genartion requirements | China Mobile Com. Corporation, Huawei | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑236915 | Add 5MBS CDR genartion requirements | China Mobile Com. Corporation, Huawei | other | Approval | Yes |
Yes
| noted | No | ||||
S5‑236552 | MBS Charging Data Request and Response Messages | Nokia. Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑236553 | MBS Tariff change trigger and charging event | Nokia. Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑236917 | MBS Tariff change trigger and charging event | Nokia. Nokia Shanghai Bell | other | Approval | Yes |
Yes
| approved | No | ||||
S5‑236616 | Clarification on reference point between MB-SMF and the CHF and MBS charging ID | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑236918 | Clarification on reference point between MB-SMF and the CHF and MBS charging ID | Huawei | other | Agreement | Yes |
Yes
| approved | No | ||||
S5‑236617 | Add PDU session charging procedures for multicast communication | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑236919 | Add PDU session charging procedures for multicast communication | Huawei | other | Agreement | Yes |
Yes
| approved | No | ||||
S5‑236618 | Add 5G MBS charging procedure for multicast and broadcast communication creation and deletion | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑236920 | Add 5G MBS charging procedure for multicast and broadcast communication creation and deletion | Huawei | other | Agreement | Yes |
Yes
| approved | No | ||||
S5‑236619 | Add 5G MBS charging procedure of broadcast session establishment | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑236921 | Add 5G MBS charging procedure of broadcast session establishment | Huawei | other | Agreement | Yes |
Yes
| approved | No | ||||
S5‑236620 | Add 5G MBS charging procedure of shared and individual delivery establishment for multicast | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑236922 | Add 5G MBS charging procedure of shared and individual delivery establishment for multicast | Huawei | other | Agreement | Yes |
Yes
| approved | No | ||||
S5‑236621 | Add 5G MBS charging information definition | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑236916 | Add 5G MBS charging information definition | Huawei | other | Agreement | Yes |
Yes
| approved | No | ||||
S5‑236923 | Rel-18 pCR 32.2xx Add 5G MBS charging information definition | Huawei | other | Approval | Yes |
Yes
| approved | No | ||||
S5‑236924 | Revised WID on Charging Aspects for SMF and MB-SMF to Support 5G Multicast-broadcast Services (SP-230623) | China Mobile | WID revised | Agreement | Yes |
Yes
| approved | No | ||||
S5‑237033 | Rel-18 pCR 32.27x Initial skeleton of TS 32.27x v0.0.0 | China Mobile Com. Corporation | other | discussion | Yes |
Yes
| approved | No | ||||
S5‑237034 | Draft TS 32.27x | China Mobile Com. Corporation | other | discussion | No |
Yes
| email approval | No | ||||
7.4.6 | Charging Aspects of TSN | S5‑236622 | Rel-18 pCR 32.282 Initial skeleton of TS 32.282 v0.0.0 | Huawei | draft TS | Agreement | Yes |
Yes
| revised | No | S5‑236894 | |
S5‑236894 | Rel-18 pCR 32.282 Initial skeleton of TS 32.282 v0.0.0 | Huawei | draft TS | Agreement | Yes |
Yes
| approved | No | S5‑236622 | |||
S5‑236623 | Rel-18 pCR 32.282 Update of skeleton | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑236895 | |||
S5‑236895 | Rel-18 pCR 32.282 Update of skeleton | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑236623 | |||
S5‑236624 | Rel-18 pCR 32.282 Update scope, references and definitions | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑236971 | |||
S5‑236971 | Rel-18 pCR 32.282 Update scope, references and definitions | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑236624 | |||
S5‑236625 | Rel-18 pCR 32.282 Update architecture considerations | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑236972 | |||
S5‑236972 | Rel-18 pCR 32.282 Update architecture considerations | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑236625 | |||
S5‑236626 | Rel-18 pCR 32.282 Update charging principles | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑236973 | |||
S5‑236973 | Rel-18 pCR 32.282 Update charging principles | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑236626 | |||
S5‑236627 | Rel-18 pCR 32.282 Update basic principles in charging scenarios | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑236974 | |||
S5‑236974 | Rel-18 pCR 32.282 Update basic principles in charging scenarios | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑236627 | |||
S5‑236628 | Add charging support for TSN service | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑236975 | |||
S5‑236975 | Add charging support for TSN service | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑236628 | |||
S5‑236629 | Add architecture and principles for TSC traffic charging | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑236976 | |||
S5‑236976 | Add architecture and principles for TSC traffic charging | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑236629 | |||
S5‑236889 | Draft TS 32.282 | Huawei | draft TS | Approval | No |
Yes
| email approval | No | ||||
7.4.7 | Charging Aspects of B2B | S5‑236630 | Add annex for B2B charging | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑236977 | |
S5‑236977 | Add annex for B2B charging | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑236630 | |||
S5‑236631 | Update B2B charging principles | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑236978 | |||
S5‑236978 | Update B2B charging principles | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑236631 | |||
S5‑236632 | Add common CHF to CHF interaction | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑236979 | |||
S5‑236979 | Add common CHF to CHF interaction | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑236632 | |||
7.4.8 | Charging Aspects of 5WWC phase 2 |   | ||||||||||
7.4.9 | Charging for roaming and additional actor using CHF to CHF interface | S5‑236633 | Add CHF to CHF interaction in LBO roaming scenario | Huawei | CR | Agreement | Yes |
Yes
| merged | No | S5‑236981 | |
S5‑236634 | Quota mangement for CHF to CHF communication | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑236984 | |||
S5‑236984 | Quota mangement for CHF to CHF communication | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑236634 | |||
S5‑236724 | Rel-18 CR 32.240 Addition of CHF as consumer in LBO architecture | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑236980 | |||
S5‑236980 | Rel-18 CR 32.240 Addition of CHF as consumer in LBO architecture | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑236724 | |||
S5‑236725 | Rel-18 CR 32.255 Addition of CHF as consumer in LBO architecture | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑236981 | |||
S5‑236981 | Rel-18 CR 32.255 Addition of CHF as consumer in LBO architecture | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑236725 | |||
S5‑236726 | Rel-18 CR 32.256 Addition of CHF as consumer in LBO architecture | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑236982 | |||
S5‑236982 | Rel-18 CR 32.256 Addition of CHF as consumer in LBO architecture | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑236726 | |||
S5‑236727 | Rel-18 CR 32.290 Addition of CHF as consumer | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑236983 | |||
S5‑236983 | Rel-18 CR 32.290 Addition of CHF as consumer | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑236727 | |||
S5‑236728 | Rel-18 CR 32.291 Addition of CHF as consumer | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
7.4.10 | Charging aspects of Satellite Access in 5GS | S5‑236499 | Add charging description for 5G data connectivity via satellite access | CATT | CR | Approval | Yes |
Yes
| revised | No | S5‑236994 | |
S5‑236994 | Add charging description for 5G data connectivity via satellite access | CATT | CR | Approval | Yes |
Yes
| agreed | No | S5‑236499 | |||
S5‑236635 | Add charging support for 5G data connectivity via satellite access | Huawei | CR | Agreement | Yes |
Yes
| merged | No | S5‑236994 | |||
S5‑236636 | Add charging support for 5G connection via satellite access | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑236995 | |||
S5‑236995 | Add charging support for 5G connection via satellite access | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑236636 | |||
7.5 | Charging studies |   | ||||||||||
7.5.1 | Study on Nchf charging services phase 2 | S5‑236389 | Rel-18 pCR TR 28.826 Payload Data reference | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑237013 | |
S5‑237013 | Rel-18 pCR TR 28.826 Payload Data reference | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑236389 | |||
S5‑236390 | Rel-18 pCR TR 28.826 Update of evaluation and conclusions clause 5.1 | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| merged | No | S5‑237017 | |||
S5‑236391 | Rel-18 pCR TR 28.826 Update of evaluation and conclusions clause 5.3 | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| merged | No | S5‑237017 | |||
S5‑236637 | Rel-18 pCR 28.826 Update the solution evaluation and conclusion in clause 5 | Huawei | pCR | Approval | Yes |
Yes
| merged | No | S5‑237014 | |||
S5‑236638 | Rel-18 pCR 28.826 Update the solution evaluation and conclusion in clause 6 | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑237018 | |||
S5‑237018 | Rel-18 pCR 28.826 Update the solution evaluation and conclusion in clause 6 | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑236638 | |||
S5‑236729 | Rel-18 pCR 28.826 Evaluation and clarification charging information optimization solutions | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑237014 | |||
S5‑237014 | Rel-18 pCR 28.826 Evaluation and clarification charging information optimization solutions | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑236729 | |||
S5‑236730 | Rel-18 pCR 28.826 Conclusion for charging request optimization | Ericsson LM | pCR | Approval | Yes |
Yes
| merged | No | S5‑237017 | |||
S5‑236731 | Rel-18 pCR 28.826 Evaluation and conclusion for rating input enhancement | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑237015 | |||
S5‑237015 | Rel-18 pCR 28.826 Evaluation and conclusion for rating input enhancement | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑236731 | |||
S5‑236732 | Rel-18 pCR 28.826 Correction of solution 4.1 and evaluation | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑237016 | |||
S5‑237016 | Rel-18 pCR 28.826 Correction of solution 4.1 and evaluation | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑236732 | |||
S5‑236733 | Rel-18 pCR 28.826 Evaluation and conclusion for non-blocking mechanism enhancement | Ericsson LM | pCR | Approval | Yes |
Yes
| merged | No | S5‑237017 | |||
S5‑236734 | Rel-18 pCR 28.826 Study conclusion for documentation improvements | Ericsson LM | pCR | Approval | Yes |
Yes
| merged | No | S5‑237017 | |||
S5‑236735 | Rel-18 pCR 28.826 Final conclusion and recommendations | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑237017 | |||
S5‑237017 | Rel-18 pCR 28.826 Final conclusion and recommendations | Ericsson LM | pCR | Approval | No |
Yes
| email approval | No | S5‑236735 | |||
S5‑236890 | Draft TR 28.826 | Ericsson | draft TR | Approval | No |
Yes
| email approval | No | ||||
7.5.2 | Study on CHF Segmentation | S5‑236386 | Rel-18 pCR TR 28.840 Abreviations section update | Amdocs, Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||
S5‑236387 | Rel-18 pCR TR 28.840 Latency Optimisation Solution | Amdocs, Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑236985 | |||
S5‑236985 | Rel-18 pCR TR 28.840 Latency Optimisation Solution | Amdocs, Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑236387 | |||
S5‑236388 | Rel-18 pCR 28.840 References section update | Amdocs, Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑236392 | Rel-18 pCR TR 28.840 NF Consumers Information Solution 1 | Amdocs, Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑236998 | |||
S5‑236998 | Rel-18 pCR TR 28.840 NF Consumers Information Solution 1 | Amdocs, Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑236392 | |||
S5‑236508 | Update CHF Selection By Charging Domains | Amdocs, Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑236986 | |||
S5‑236986 | Update CHF Selection By Charging Domains | Amdocs, Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑236508 | |||
S5‑236554 | Rel-18 pCR 28.840 NF Consumers Information Solution 2 | Nokia, Nokia Shanghai Bell, Amdocs | pCR | Approval | Yes |
Yes
| revised | No | S5‑236987 | |||
S5‑236987 | Rel-18 pCR 28.840 NF Consumers Information Solution 2 | Nokia, Nokia Shanghai Bell, Amdocs | pCR | Approval | Yes |
Yes
| approved | No | S5‑236554 | |||
S5‑236639 | Rel-18 pCR 28.840 Add solution for CHF selection by location | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑236988 | |||
S5‑236988 | Rel-18 pCR 28.840 Add solution for CHF selection by location | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑236639 | |||
S5‑236640 | Rel-18 pCR 28.840 Add solution for CHF selection by NF instance | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑236989 | |||
S5‑236989 | Rel-18 pCR 28.840 Add solution for CHF selection by NF instance | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑236640 | |||
S5‑236641 | Rel-18 pCR 28.840 Add solution for CHF selection by user group | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑236990 | |||
S5‑236990 | Rel-18 pCR 28.840 Add solution for CHF selection by user group | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑236641 | |||
S5‑236736 | Rel-18 pCR 28.840 Addition of solution for NF instance location | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑236991 | |||
S5‑236991 | Rel-18 pCR 28.840 Addition of solution for NF instance location | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑236736 | |||
S5‑236737 | Rel-18 pCR 28.840 Addition of solution for CHF selection | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑236992 | |||
S5‑236992 | Rel-18 pCR 28.840 Addition of solution for CHF selection | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑236737 | |||
S5‑236738 | Rel-18 pCR 28.840 Addition of solution for domain based discovery | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑236993 | |||
S5‑236993 | Rel-18 pCR 28.840 Addition of solution for domain based discovery | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑236738 | |||
S5‑236874 | Rel-18 pCR 28.840 NF Consumers Information Solution 2 | Nokia, Nokia Shanghai Bell | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑236891 | Draft TR 28.840 | Nokia, Nokia Shanghai Bell | draft TR | discussion | No |
Yes
| email approval | No | ||||
7.5.3 | Study on charging aspects of Satellite in 5GS | S5‑236489 | Discussion paper on the need of NR NTN TAI information for Satellite access Charging | CATT | discussion | Decision | Yes |
Yes
| noted | No | ||
S5‑236490 | Update solutions for satellite access charging | CATT | pCR | Agreement | Yes |
Yes
| noted | No | ||||
S5‑236491 | Update evaluation for satellite access charging | CATT | pCR | Agreement | Yes |
Yes
| noted | No | ||||
S5‑236492 | Update solutions for edge computing with satellite backhaul | CATT | pCR | Agreement | Yes |
Yes
| revised | No | S5‑236996 | |||
S5‑236996 | Update solutions for edge computing with satellite backhaul | CATT | pCR | Agreement | Yes |
Yes
| approved | No | S5‑236492 | |||
S5‑236493 | Add Evaluation for edge computing charging with satellite backhaul | CATT | pCR | Agreement | Yes |
Yes
| revised | No | S5‑236997 | |||
S5‑236997 | Add Evaluation for edge computing charging with satellite backhaul | CATT | pCR | Agreement | Yes |
Yes
| approved | No | S5‑236493 | |||
S5‑236494 | Add Conclusion for edge computing charging with satellite backhaul | CATT | pCR | Agreement | Yes |
Yes
| approved | No | ||||
S5‑236495 | Update solutions for SSC-to-SSC communications via satellite backhaul | CATT | pCR | Agreement | Yes |
Yes
| revised | No | S5‑236999 | |||
S5‑236999 | Update solutions for SSC-to-SSC communications via satellite backhaul | CATT | pCR | Agreement | Yes |
Yes
| approved | No | S5‑236495 | |||
S5‑236496 | Add Evaluation for SSC-to-SSC communications via satellite backhaul | CATT | pCR | Agreement | Yes |
Yes
| revised | No | S5‑237000 | |||
S5‑237000 | Add Evaluation for SSC-to-SSC communications via satellite backhaul | CATT | pCR | Agreement | Yes |
Yes
| approved | No | S5‑236496 | |||
S5‑236497 | Add Conclusion for SSC-to-SSC communications via satellite backhaul | CATT | pCR | Agreement | Yes |
Yes
| revised | No | S5‑237001 | |||
S5‑237001 | Add Conclusion for SSC-to-SSC communications via satellite backhaul | CATT | pCR | Agreement | Yes |
Yes
| approved | No | S5‑236497 | |||
S5‑236498 | Add Conclusion and Recommendations | CATT | pCR | Agreement | Yes |
Yes
| revised | No | S5‑237002 | |||
S5‑237002 | Add Conclusion and Recommendations | CATT | pCR | Agreement | Yes |
Yes
| approved | No | S5‑236498 | |||
S5‑236892 | Draft TR 28.844 | CATT | draft TR | Approval | No |
Yes
| email approval | No | ||||
S5‑237003 | Presentation of TR 28.844 for Approval | CATT | TS or TR cover | Approval | Yes |
Yes
| approved | No | ||||
S5‑237035 | LS to CT4 on the need of the NR NTN TAI information | CATT | LS out | Approval | No |
Yes
| email approval | No | ||||
7.5.4 | Study on Charging Aspects of Ranging and Sidelink Positioning | S5‑236436 | Rel-18 pCR TR 28.845 Resolve Editor's Note of Business roles | Chinatelecom Cloud | pCR | Approval | Yes |
Yes
| approved | No | ||
S5‑236437 | Rel-18 pCR TR 28.845 Resolve Editor's Note of charging scenarios and key issues for Ranging Sidelink Positioning UE Discovery | Chinatelecom Cloud | pCR | Approval | Yes |
Yes
| revised | No | S5‑237004 | |||
S5‑237004 | Rel-18 pCR TR 28.845 Resolve Editor's Note of charging scenarios and key issues for Ranging Sidelink Positioning UE Discovery | Chinatelecom Cloud | pCR | Approval | Yes |
Yes
| approved | No | S5‑236437 | |||
S5‑236438 | Rel-18 pCR TR 28.845 Update Clause 5.2 for Alignment with SA2 on UE based SL positioning | Chinatelecom Cloud | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑236439 | Rel-18 pCR TR 28.845 Add solution for Ranging Sidelink Positioning UE Discovery | Chinatelecom Cloud | pCR | Approval | Yes |
Yes
| revised | No | S5‑237005 | |||
S5‑237005 | Rel-18 pCR TR 28.845 Add solution for Ranging Sidelink Positioning UE Discovery | Chinatelecom Cloud | pCR | Approval | Yes |
Yes
| approved | No | S5‑236439 | |||
S5‑236440 | Rel-18 pCR TR 28.845 Add solution#2.X for 5GS charging for mobile originated UE positioning assisted by Sidelink Positioning and involving 5GC | Chinatelecom Cloud | pCR | Approval | Yes |
Yes
| revised | No | S5‑237006 | |||
S5‑237006 | Rel-18 pCR TR 28.845 Add solution#2.X for 5GS charging for mobile originated UE positioning assisted by Sidelink Positioning and involving 5GC | Chinatelecom Cloud | pCR | Approval | Yes |
Yes
| approved | No | S5‑236440 | |||
S5‑236441 | Rel-18 pCR TR 28.845 Add solution#2.Y for 5GS charging for mobile terminated UE positioning assisted by Sidelink Positioning and involving 5GC | Chinatelecom Cloud | pCR | Approval | Yes |
Yes
| revised | No | S5‑237007 | |||
S5‑237007 | Rel-18 pCR TR 28.845 Add solution#2.Y for 5GS charging for mobile terminated UE positioning assisted by Sidelink Positioning and involving 5GC | Chinatelecom Cloud | pCR | Approval | Yes |
Yes
| approved | No | S5‑236441 | |||
S5‑236442 | Rel-18 pCR TR 28.845 Add Solution for UE only Sidelink Positioning for Target UE using Located UE | Chinatelecom Cloud | pCR | Approval | Yes |
Yes
| revised | No | S5‑237008 | |||
S5‑237008 | Rel-18 pCR TR 28.845 Add Solution for UE only Sidelink Positioning for Target UE using Located UE | Chinatelecom Cloud | pCR | Approval | Yes |
Yes
| approved | No | S5‑236442 | |||
S5‑236443 | Rel-18 pCR TR 28.845 Add Solution for Ranging SL Positioning service exposure to Client UE through PC5 | Chinatelecom Cloud | pCR | Approval | Yes |
Yes
| revised | No | S5‑237009 | |||
S5‑237009 | Rel-18 pCR TR 28.845 Add Solution for Ranging SL Positioning service exposure to Client UE through PC5 | Chinatelecom Cloud | pCR | Approval | Yes |
Yes
| approved | No | S5‑236443 | |||
S5‑236444 | Rel-18 pCR TR 28.845 Add Solution for Ranging SL Positioning service exposure to Client UE through NEF | Chinatelecom Cloud | pCR | Approval | Yes |
Yes
| revised | No | S5‑237010 | |||
S5‑237010 | Rel-18 pCR TR 28.845 Add Solution for Ranging SL Positioning service exposure to Client UE through NEF | Chinatelecom Cloud | pCR | Approval | Yes |
Yes
| approved | No | S5‑236444 | |||
S5‑236445 | Rel-18 pCR TR 28.845 Add Solution for Ranging SL Positioning service exposure to Client UE through 5GC network via control plane | Chinatelecom Cloud | pCR | Approval | Yes |
Yes
| revised | No | S5‑237011 | |||
S5‑237011 | Rel-18 pCR TR 28.845 Add Solution for Ranging SL Positioning service exposure to Client UE through 5GC network via control plane | Chinatelecom Cloud | pCR | Approval | Yes |
Yes
| approved | No | S5‑236445 | |||
S5‑236446 | Rel-18 pCR TR 28.845 Add Solution for Ranging SL Positioning service exposure to the AF | Chinatelecom Cloud | pCR | Approval | Yes |
Yes
| revised | No | S5‑237012 | |||
S5‑237012 | Rel-18 pCR TR 28.845 Add Solution for Ranging SL Positioning service exposure to the AF | Chinatelecom Cloud | pCR | Approval | Yes |
Yes
| approved | No | S5‑236446 | |||
S5‑236893 | Draft TR 28.845 | China Telecom | draft TR | Approval | No |
Yes
| email approval | No | ||||
8 | Any Other Business |   | ||||||||||
9 | Closing of the meeting |   |