Tdoc List
2022-04-20 16:30
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‑222000 | Agenda | WG Chair | agenda | Yes |
Yes
| approved | No | |||
3 | IPR and legal declaration |   | ||||||||||
4.1 | Last SA5 meeting report | S5‑222001 | Report from last SA5 meeting | MCC | report | Yes |
Yes
| approved | No | |||
4.2 | Last SA meeting report |   | ||||||||||
4.3 | Inter-organizational reports |   | ||||||||||
5.1 | Administrative issues at SA5 level | S5‑222002 | e-meeting process | WG Chair | discussion | Yes |
Yes
| noted | No | |||
S5‑222003 | Post e-meeting email approval status | WG Chair | other | No |
No
| reserved | No | |||||
S5‑222010 | SA5 working procedures | WG Chair | other | Yes |
Yes
| approved | No | |||||
S5‑222011 | Process for management of draft TS-TRs | WG Chair | other | Yes |
Yes
| approved | No | |||||
S5‑222028 | SA5 working procedures Forge | Nokia, Nokia Shanghai Bell | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑222572 | |||
S5‑222572 | SA5 working procedures Forge | Nokia, Nokia Shanghai Bell | discussion | Endorsement | Yes |
Yes
| approved | No | S5‑222028 | |||
S5‑222029 | Discussion paper on Forge change in SA5 OAM proposed in SP-220341 | Nokia, Nokia Shanghai Bell | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑222573 | |||
S5‑222573 | Discussion paper on Forge change in SA5 OAM proposed in SP-220341 | Nokia, Nokia Shanghai Bell | discussion | Endorsement | Yes |
Yes
| endorsed | No | S5‑222029 | |||
5.2 | Technical issues at SA5 level | S5‑222286 | DP on the relationship of CAMARA and SA work on capability exposure | TELEFONICA S.A. | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑222574 | |
S5‑222574 | DP on the relationship of CAMARA and SA work on capability exposure | TELEFONICA S.A. | discussion | Endorsement | Yes |
Yes
| endorsed | No | S5‑222286 | |||
S5‑222489 | DP Deprecating attributes, data types and IOCs | Ericsson | discussion | Yes |
Yes
| endorsed | No | |||||
5.3 | Liaison statements at SA5 level | S5‑222140 | LS reply from ENSWI to 3GPP SA5 on overall architecture for network slice ordering, provisioning and assurance | GSMA | LS in | Yes |
Yes
| replied to | No | |||
S5‑222141 | Resubmitted LS on the first deliverable on use cases for autonomous networks from ITU FG-AN | ITU FG-AN | LS in | Yes |
Yes
| replied to | No | |||||
S5‑222142 | TM Forum E2E team Response to liaison S5-215530 | TM Forum | LS in | Yes |
Yes
| replied to | No | |||||
S5‑222143 | Minutes Formal Liaison Meeting #15 Minutes 21st February 2022 Liaison AN-SDO2022-02 | TM Forum | LS in | Yes |
Yes
| noted | No | |||||
S5‑222145 | Further Operator Platform Group questions following SDO Workshop | GSMA | LS in | Yes |
Yes
| noted | No | |||||
S5‑222152 | LS ccSA5 on User consent Updating | R3-221210 | LS in | Yes |
Yes
| noted | No | |||||
S5‑222159 | Reply LS ccSA5 on MINT functionality for Disaster Roaming | S2-2201514 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑222160 | Reply LS ccSA5 on MBS Service Area Identity and start procedure for broadcast service | S2-2201517 | LS in | Yes |
Yes
| noted | No | |||||
S5‑222161 | Reply LS ccSA5 on Further GSMA OPAG questions following SDO Workshop | S2-2201721 | LS in | Yes |
Yes
| noted | No | |||||
S5‑222162 | Reply LS ccSA5 on User Consent Updating | S3-220474 | LS in | Yes |
Yes
| noted | No | |||||
S5‑222163 | Reply LS ccSA5 on Reply LS on MINT functionality for Disaster Roaming | S3-220518 | LS in | Yes |
Yes
| noted | No | |||||
S5‑222164 | Reply LS ccSA5 on Further Operator Platform Group questions following SDO Workshop | S3-220571 | LS in | Yes |
Yes
| noted | No | |||||
S5‑222168 | Reply LS ccSA5 on Prioritized Vehicle to Cloud Technical Solutions (Automotive Edge Computing Consortium (AECC)) | S6-220265 | LS in | Yes |
Yes
| noted | No | |||||
S5‑222289 | Reply LS to GSMA NG ENSWI on overall architecture for network slice ordering, provisioning and assurance | Orange | LS out | Agreement | Yes |
Yes
| revised | No | S5‑222814 | |||
S5‑222814 | Reply LS to GSMA NG ENSWI on overall architecture for network slice ordering, provisioning and assurance | Orange | LS out | Agreement | Yes |
Yes
| approved | No | S5‑222289 | |||
S5‑222290 | Reply LS to TM Forum on overall architecture for network slice ordering, provisioning and assurance | Orange | LS out | Agreement | Yes |
Yes
| revised | No | S5‑222815 | |||
S5‑222815 | Reply LS to TM Forum on overall architecture for network slice ordering, provisioning and assurance | Orange | LS out | Agreement | Yes |
Yes
| approved | No | S5‑222290 | |||
S5‑222351 | LS ccSA5 on MEC Federation and interest to collaborate | ETSI ISG MEC | LS in | Yes |
Yes
| noted | No | |||||
S5‑222430 | Reply to LS on MINT functionality for Disaster Roaming | Ericsson LM | LS out | Approval | Yes |
Yes
| revised | No | S5‑222575 | |||
S5‑222575 | Reply to LS on MINT functionality for Disaster Roaming | Ericsson LM | LS out | Approval | Yes |
Yes
| approved | No | S5‑222430 | |||
S5‑222553 | Reply LS ccSA5 to GSMA Operator Platform Group on edge computing definition and integration | SP-220003 | LS in | Yes |
Yes
| noted | No | |||||
S5‑222554 | Reply LS ccSA5 to GSMA OPG on Further Operator Platform Group questions following SDO Workshop | SP-220346 | LS in | Yes |
Yes
| noted | No | |||||
S5‑222555 | LS ccSA5 on Request to clarify whether there are IPR issues with using 3GPP terminology and information objects and names in code contributed to ONAP | ONAP | LS in | discussion | Yes |
Yes
| noted | No | ||||
S5‑222560 | Reply LS on the first deliverable on use cases for autonomous networks from ITU FG-AN (ITU FG-AN) | Huawei | LS out | Approval | Yes |
Yes
| approved | No | ||||
5.4 | SA5 meeting calendar | S5‑222012 | SA5 meeting calendar | WG CHair | other | Yes |
Yes
| revised | No | S5‑222576 | ||
S5‑222576 | SA5 meeting calendar | WG CHair | other | - | Yes |
Yes
| noted | No | S5‑222012 | |||
6.1 | OAM&P Plenary | S5‑222004 | OAM&P action list | WG Vice Chair (Huawei) | other | Yes |
Yes
| noted | No | |||
S5‑222005 | agenda_with_Tdocs_sequence_proposal_OAM | WG Vice Chair (Huawei) | agenda | Yes |
Yes
| noted | No | |||||
S5‑222006 | OAM Exec Report | WG Vice Chair (Huawei) | report | No |
No
| reserved | No | |||||
S5‑222007 | OAM Chair notes and conclusions | WG Chair | report | No |
Yes
| noted | No | |||||
S5‑222013 | Collection of useful endorsed document and external communication documents | WG Vice Chair (Huawei) | discussion | Yes |
Yes
| noted | No | |||||
S5‑222067 | DP on WoPs of FS_MANWDAF | China Telecom Corporation Ltd. | discussion | Endorsement | Yes |
Yes
| merged | No | S5‑222551 | |||
S5‑222074 | LS on changes over E1AP due to RACH NSA Measurements | Nokia Solutions & Networks (I) | LS out | Approval | Yes |
Yes
| revised | No | S5‑222816 | |||
S5‑222816 | LS on changes over E1AP due to RACH NSA Measurements | Nokia Solutions & Networks (I) | LS out | Approval | Yes |
Yes
| approved | No | S5‑222074 | |||
S5‑222100 | WoP proposal for eECM | Samsung R&D Institute India | other | Agreement | Yes |
Yes
| merged | No | S5‑222551 | |||
S5‑222104 | Wop of FS_DCSA | Huawei | discussion | Approval | Yes |
Yes
| merged | No | S5‑222551 | |||
S5‑222106 | FS_NSOEU Work Package (WoP) Proposal | Samsung Electronics GmbH | other | Endorsement | Yes |
Yes
| merged | No | S5‑222551 | |||
S5‑222110 | Wop of FS_KQI_5G | Huawei | discussion | Endorsement | Yes |
Yes
| merged | No | S5‑222551 | |||
S5‑222122 | Discussion on WoP of FS_ANLEVA | China Mobile, Huawei | discussion | Endorsement | Yes |
Yes
| merged | No | S5‑222551 | |||
S5‑222127 | Discussion on WoP of FS_eANL | China Mobile, Huawei | discussion | Endorsement | Yes |
Yes
| merged | No | S5‑222551 | |||
S5‑222136 | LS on the specification of AT commands for NR QoE | C1-222058 | LS in | Yes |
Yes
| noted | No | |||||
S5‑222137 | Reply LS ccSA5 On User Consent Updating | C4-221413 | LS in | Yes |
Yes
| noted | No | |||||
S5‑222144 | Publication of NFV SOL001 V4.2.1 | ETSI ISG NFV | LS in | Yes |
Yes
| noted | No | |||||
S5‑222146 | Further reply LS ccSA5 on QoE report handling at QoE pause | R2-2201862 | LS in | Yes |
Yes
| noted | No | |||||
S5‑222147 | LS ccSA5 on the specification of AT commands for NR QoE | R2-2202017 | LS in | Yes |
Yes
| noted | No | |||||
S5‑222148 | Reply LS ccSA5 on maximum container size for QoE configuration and report | R2-2202018 | LS in | Yes |
Yes
| noted | No | |||||
S5‑222149 | LS ccSA5 on logged MDT configuration at SN in DC scenario | R2-2204063 | LS in | Yes |
Yes
| noted | No | |||||
S5‑222150 | LS on RAN2 agreements on NR QoE | R2-2204202 | LS in | Yes |
Yes
| noted | No | |||||
S5‑222151 | Resubmitted Response to LS Reply LS on Enhancement of RAN Slicing | R3-216238 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑222153 | LS ccSA5 on QoE Measurement Session Start and Measurement Session End Indication from the UE | R3-221243 | LS in | Yes |
Yes
| noted | No | |||||
S5‑222154 | Reply LS to SA5 on beam measurement reports | R3-221383 | LS in | Yes |
Yes
| postponed | No | |||||
S5‑222155 | LS on QMC related RAN3 progress | R3-221437 | LS in | Yes |
Yes
| noted | No | |||||
S5‑222156 | LS on configuration updates of MDT M1, M8 and M9 in RAN3 specifications | R3-221445 | LS in | Yes |
Yes
| postponed | No | |||||
S5‑222157 | Reply LS on MDT M6 calculation for split bearers in MR-DC | R3-222868 | LS in | Yes |
Yes
| noted | No | |||||
S5‑222158 | LS on RAN3 agreements for NR QoE | R3-222890 | LS in | Yes |
Yes
| postponed | No | |||||
S5‑222165 | LS Reply ccSA5 on maximum container size for QoE configuration and report | S4-220237 | LS in | Yes |
Yes
| noted | No | |||||
S5‑222166 | LS Reply on QoE configuration and reporting related issues | S4-220309 | LS in | Yes |
Yes
| postponed | No | |||||
S5‑222167 | Resubmitted LS on TS 28.404/TS 28.405 Clarification | S4-211234 | LS in | Yes |
Yes
| postponed | No | |||||
S5‑222169 | Reply LS ccSA5 on further Operator Platform Group questions following SDO Workshop | S6-220432 | LS in | Yes |
Yes
| noted | No | |||||
S5‑222170 | Resubmitted LS/r on methodology harmonization update (reply to 3GPP TSG SA5-S5-215481) | ITU-T SG2 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑222187 | WoPs for AI-ML management study | Intel, NEC | other | Endorsement | Yes |
Yes
| merged | No | S5‑222551 | |||
S5‑222212 | Work Packages (WoPs) for SID on further Enhancements of Management of Trace/MDT (FS_5GMDT_Ph2) | Nokia, Nokia Shanghai Bell | discussion | Endorsement | Yes |
Yes
| merged | No | S5‑222551 | |||
S5‑222257 | Rel-18 3GPP_SA5 OAM WoP_FS_eIDMS_MN | Huawei,Ericsson | discussion | Endorsement | Yes |
Yes
| merged | No | S5‑222551 | |||
S5‑222273 | Rel-18 3GPP_SA5 OAM WoP_FS_OAM_eNPN | Huawei | other | Information | Yes |
Yes
| merged | No | S5‑222551 | |||
S5‑222305 | WoP of FS_5GLAN_Mgt | China Mobile Com. Corporation | discussion | Endorsement | Yes |
Yes
| merged | No | S5‑222551 | |||
S5‑222306 | WoP Proposal for Rel-18 Study on 5G energy efficiency phase 2 | Orange | discussion | Endorsement | Yes |
Yes
| merged | No | S5‑222551 | |||
S5‑222317 | WoP Proposal for Rel-18 Work Item on Enhancements of EE for 5G Phase 2 | Orange | discussion | Endorsement | Yes |
Yes
| merged | No | S5‑222551 | |||
S5‑222318 | WoP of FS_URLLC_Mgt | China Unicom | discussion | Endorsement | Yes |
Yes
| merged | No | S5‑222551 | |||
S5‑222319 | Wop of FS_MANS_ph2 | China Unicom | discussion | Endorsement | Yes |
Yes
| merged | No | S5‑222551 | |||
S5‑222331 | Wop of FS_MEC_ECM | Huawei | other | Endorsement | Yes |
Yes
| merged | No | S5‑222551 | |||
S5‑222349 | Rel-18 WoP FS_eSBMA | Huawei Technologies (Korea) | other | Yes |
Yes
| merged | No | S5‑222551 | ||||
S5‑222372 | Discussion on Rel-18 3GPP SA5 OAM WoP of FS_FSEV | China Mobile, Huawei | discussion | Endorsement | Yes |
Yes
| merged | No | S5‑222551 | |||
S5‑222396 | Rel-18 3GPP_SA5 OAM WoP _RANSC | China Mobile, Huawei | discussion | Endorsement | Yes |
Yes
| merged | No | S5‑222551 | |||
S5‑222455 | LS on Response to LS on Enhancement of RAN Slicing from RAN3 | Nokia, Nokia Shanghai Bell | LS out | Approval | Yes |
Yes
| revised | No | S5‑222577 | |||
S5‑222577 | LS on Response to LS on Enhancement of RAN Slicing from RAN3 | Nokia, Nokia Shanghai Bell | LS out | Approval | Yes |
Yes
| revised | No | S5‑222645 | S5‑222455 | ||
S5‑222645 | LS on Response to LS on Enhancement of RAN Slicing from RAN3 | Nokia, Nokia Shanghai Bell | LS out | Approval | Yes |
Yes
| approved | No | S5‑222577 | |||
S5‑222529 | Work Packages (WoPs) for Study on Basic SBMA enabler enhancements (FS_eSBMAe) | Nokia, Nokia Shanghai Bell | other | Approval | Yes |
Yes
| merged | No | S5‑222551 | |||
S5‑222550 | Rel-18 3GPP_SA5 OAM WoP FS_NETSLICE_IDMS | Huawei Tech.(UK) Co.. Ltd, Ericsson | other | Endorsement | Yes |
Yes
| merged | No | S5‑222551 | |||
S5‑222551 | Collection of Rel-18 3GPP SA5 OAM WoPs | Huawei Technologies (Korea) | other | Yes |
Yes
| endorsed | No | |||||
S5‑222556 | LS on enforcement of maximum number of UEs and maximum number of PDU sessions in a network slice. | GSMA | LS in | discussion | Yes |
Yes
| noted | No | ||||
S5‑222557 | WoP of FS_MCVNF | China Mobile | other | discussion | Yes |
Yes
| merged | No | S5‑222551 | |||
S5‑222558 | Add Rel-18 3GPP_SA5 OAM WoP for NSRULE | Ericsson | other | discussion | Yes |
Yes
| merged | No | S5‑222551 | |||
S5‑222559 | WoP for AdNRM_ph2 | Huawei | other | discussion | Yes |
Yes
| merged | No | S5‑222551 | |||
S5‑222561 | WoP proposal for 6.5.14 FS_CICDN | Lenovo, Motorola Mobile, CMCC | discussion | discussion | Yes |
Yes
| merged | No | S5‑222551 | |||
S5‑222562 | WoP proposal for 6.5.16 FS_YANG | Ericsson | discussion | discussion | Yes |
Yes
| merged | No | S5‑222551 | |||
S5‑222563 | WoP proposal for 6.5.22 FS_NSCE | Alibaba | discussion | discussion | Yes |
Yes
| merged | No | S5‑222551 | |||
S5‑222570 | Reply LS on methodology harmonization update | Ericsson | LS out | Approval | Yes |
Yes
| approved | No | ||||
6.2 | New OAM&P Work Item proposals | S5‑222051 | New SID Study on measurement data collection to support RAN intelligence | Intel Korea, Ltd. Verizon, AT&T, CMCC | SID new | Approval | Yes |
Yes
| revised | No | S5‑222631 | |
S5‑222631 | New SID Study on measurement data collection to support RAN intelligence | Intel Korea, Ltd. Verizon, AT&T, CMCC | SID new | Approval | Yes |
Yes
| agreed | No | S5‑222051 | |||
S5‑222243 | New Rel-18 WID 5G advanced performance measurements and KPIs | China Telecomunication Corp., Intel | WID new | Approval | Yes |
Yes
| revised | No | S5‑222578 | |||
S5‑222578 | New Rel-18 WID 5G advanced performance measurements and KPIs | China Telecomunication Corp., Intel | WID new | Approval | Yes |
Yes
| agreed | No | S5‑222243 | |||
S5‑222247 | Study on Advanced Alarm Management for 5G | China Unicom | SID new | Yes |
Yes
| noted | No | |||||
S5‑222341 | Rel-18 SID on Closed control loop governance for autonomous network | ZTE Corporation, China Telecom | SID new | Agreement | Yes |
Yes
| noted | No | ||||
S5‑222347 | New Rel-18 SID on precise network traffic abstraction information for service planning | China Telecomunication Corp., Huawei | SID new | Approval | Yes |
Yes
| noted | No | ||||
S5‑222348 | New WID on continuous integration continuous delivery support for 3GPP NFs | China Mobile Com. Corporation | WID new | Approval | Yes |
Yes
| noted | No | ||||
S5‑222401 | New SID on Management Aspects of 5G Location | China Unicom | SID new | Approval | Yes |
Yes
| noted | No | ||||
S5‑222402 | New SID on Management Aspects of IoT NTN Enhancement | China Unicom | SID new | Approval | Yes |
Yes
| revised | No | S5‑222579 | |||
S5‑222579 | New SID on Management Aspects of IoT NTN Enhancement | China Unicom | SID new | Approval | Yes |
Yes
| agreed | No | S5‑222402 | |||
S5‑222458 | New R18 SID on conflict management | Lenovo Mobile Com. Technology | SID new | Yes |
Yes
| noted | No | |||||
S5‑222492 | Discussion on new SID for conflict managment | Lenovo Mobile Com. Technology | discussion | Yes |
Yes
| noted | No | |||||
6.3 | OAM&P Maintenance and Rel-17 small Enhancements | S5‑222058 | TS 28.541 Fixing a few issues with attribute related to nextHopInfoList in EP_transport | Nokia, Nokia Shanghai Bell, KDDI | draftCR | Approval | Yes |
Yes
| revised | No | S5‑222594 | |
S5‑222594 | TS 28.541 Fixing a few issues with attribute related to nextHopInfoList in EP_transport | Nokia, Nokia Shanghai Bell, KDDI | draftCR | Approval | Yes |
Yes
| approved | No | S5‑222058 | |||
S5‑222062 | Correction to RRMPolicy_ IOC reference in RRMPolicyRatio IOC | Nokia, Nokia Shangai Bell | draftCR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑222063 | Rel-16 CR 28.623 Stage 3 Yang fix for 3GPP Common Trace | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑222065 | Rel 17 TS 28.623 Stage 3 Yang fix for 3GPP Common Trace | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑222066 | Rel-16 CR 28.541 Diagram fix for NRM fragment for RRM policies | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑222068 | Rel-17 TS 28.541 Diagram fix for NRM fragment for RRM policies | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑222069 | Correction to RRMPolicy_ IOC reference in RRMPolicyRatio IOC | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑222070 | Add attribute properties for NetworkSliceSubnet attribute priorityLabel | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑222071 | Correction to RRMPolicy_ IOC reference in RRMPolicyRatio IOC | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑222072 | Add attribute properties for NetworkSliceSubnet attribute priorityLabel | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑222073 | Fix to change “Support Qualifier" to "S" | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑222075 | Rel-16 CR 32.158 Add definition of secondary resource | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑222076 | Rel-16 CR 32.158 Add definition of resource "/{MnSName}/{MnSVersion}" | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| revised | No | S5‑222586 | |||
S5‑222586 | Rel-16 CR 32.158 Add definition of resource "/{MnSName}/{MnSVersion}" | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| approved | No | S5‑222076 | |||
S5‑222077 | Define LogicInterfaceInfo datatype and fix attribute properties for logicInterfaceInfo | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑222078 | Rel-16 CR 32.158 Clarify clause Creating a resource with identifier creation by the MnS Producer | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| revised | No | S5‑222587 | |||
S5‑222587 | Rel-16 CR 32.158 Clarify clause Creating a resource with identifier creation by the MnS Producer | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| approved | No | S5‑222078 | |||
S5‑222079 | Rel-16 CR 32.158 Clarify clause Creating a resource with identifier creation by the MnS Consumer | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| revised | No | S5‑222588 | |||
S5‑222588 | Rel-16 CR 32.158 Clarify clause Creating a resource with identifier creation by the MnS Consumer | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| approved | No | S5‑222079 | |||
S5‑222080 | Rel-16 CR 32.158 Clarify clause Design pattern for reading a resource | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑222081 | Rel-16 CR TS 28.541 Fix attribute properties for configurable5QISetRef and dynamic5QISetRef | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| merged | No | S5‑222604 | |||
S5‑222082 | Rel-16 CR 32.158 Clarify clause Design pattern for updating a resource | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑222083 | Rel-16 CR 32.158 Clarify clause Design pattern for deleting a resource | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑222084 | Rel-16 CR 32.158 Clarify clause Design pattern for subscribe/notify | Nokia, Nokia Shanghai Bell | draftCR | Yes |
Yes
| approved | No | |||||
S5‑222085 | Rel-16 CR 32.158 Clarify clause Design pattern for scoping and filtering | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| revised | No | S5‑222589 | |||
S5‑222589 | Rel-16 CR 32.158 Clarify clause Design pattern for scoping and filtering | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| approved | No | S5‑222085 | |||
S5‑222086 | Rel-16 CR 32.158 Clarify clause Design patterns for attribute and attribute field selection | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑222087 | Rel-16 CR 32.158 Clarify clause Design patterns for partially updating a resource | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑222088 | Rel-17 CR TS 28.541 Fix attribute properties for configurable5QISetRef and dynamic5QISetRef | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑222092 | Rel-16 CR 32.158 Clarify clause Design patterns for patching multiple resources | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑222094 | Rel-16 CR 32.158 Add missing clause Large queries | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑222095 | Rel-16 CR 32.158 Correct examples in Annex A | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| revised | No | S5‑222590 | |||
S5‑222590 | Rel-16 CR 32.158 Correct examples in Annex A | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| approved | No | S5‑222095 | |||
S5‑222096 | Rel-16 CR 28.532 Correct definition of Resource | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑222099 | Rel-16 CR 28.532 Correct REST SS of deleteMOI | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| revised | No | S5‑222591 | |||
S5‑222591 | Rel-16 CR 28.532 Correct REST SS of deleteMOI | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| approved | No | S5‑222099 | |||
S5‑222102 | Re-16 CR 28.622 Add missing definitions of common data types | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑222111 | Rel-16 CR 28.623 Stage 3 Yang fix for 3GPP Common Trace | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| revised | No | S5‑222592 | |||
S5‑222592 | Rel-16 CR 28.623 Stage 3 Yang fix for 3GPP Common Trace | Nokia, Nokia Shanghai Bell,Ericsson | draftCR | Approval | Yes |
Yes
| approved | No | S5‑222111 | |||
S5‑222116 | Rel 17 TS 28.623 Stage 3 Yang fix for 3GPP Common Trace | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑222119 | Rel-16 CR 28.541 Diagram fix for NRM fragment for RRM policies | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| revised | No | S5‑222593 | |||
S5‑222593 | Rel-16 CR 28.541 Diagram fix for NRM fragment for RRM policies | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| approved | No | S5‑222119 | |||
S5‑222120 | Rel-17 TS 28.541 Diagram fix for NRM fragment for RRM policies | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑222131 | Fixing OpenAPI Discoverability issue in EdgeNrm.yaml stage 3 | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑222132 | Fixing OpenAPI Discoverability issue in CoslaNrm.yaml stage 3 | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑222133 | Fixing OpenAPI Discoverability issue in CoslaNrm.yaml stage 3 | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑222134 | Add attributes for EP_transport | TELUS | draftCR | Approval | Yes |
Yes
| merged | No | S5‑222594 | |||
S5‑222202 | Rel-16 draftCR 28.622 Alignment of parameter names to 32.422 (stage 2) | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| revised | No | S5‑222595 | |||
S5‑222595 | Rel-16 draftCR 28.622 Alignment of parameter names to 32.422 (stage 2) | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| approved | No | S5‑222202 | |||
S5‑222203 | Rel-16 draftCR 28.623 Alignment of parameter names to 32.422 (stage 3) | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑222204 | Rel-17 draftCR 28.622 Structuring of TraceJob IOC and Clean Up (stage 2) | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑222205 | Rel-17 draftCR 28.623 Structuring of TraceJob IOC and Clean Up (stage 3) | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑222206 | Rel-16 draftCR 28.622 Clean up of attribute properties | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| revised | No | S5‑222596 | |||
S5‑222596 | Rel-16 draftCR 28.622 Clean up of attribute properties | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| approved | No | S5‑222206 | |||
S5‑222207 | Rel-17 draftCR 28.622 Clean up of attribute properties | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑222209 | Rel-17 draftCR 28.552 Correct handover execution failure per beam pair measurement | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑222210 | Rel-17 draftCR 28.552 Clean up of PM related to MRO | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑222215 | Rel-16 TS 28.541 Fixing OpenAPI Discoverability issue in Stage3-5gcNrm.yaml | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑222216 | Rel-16 TS 28.541 Fixing OpenAPI Discoverability issue in Stage3-nrNrm.yaml | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑222217 | Rel-16 TS 28.541 Fixing OpenAPI Discoverability issue in Stage3-sliceNrm.yaml | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑222218 | Rel-17 TS 28.541 Fixing OpenAPI Discoverability issue in Stage3-5gcNrm.yaml | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑222219 | Rel-17 TS 28.541 Fixing OpenAPI Discoverability issue in Stage3-nrNrm.yaml | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑222220 | Rel-17 TS 28.541 Fixing OpenAPI Discoverability issue in Stage3-sliceNrm.yaml | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑222221 | Rel-16 TS 28.541 OpenAPI file name and dependence change-5gcNrm.yaml | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| revised | No | S5‑222581 | |||
S5‑222581 | Rel-16 TS 28.541 OpenAPI file name and dependence change-5gcNrm.yaml | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| approved | No | S5‑222221 | |||
S5‑222222 | Rel-16 TS 28.541 OpenAPI file name and dependence change-nrNrm.yaml | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| revised | No | S5‑222582 | |||
S5‑222582 | Rel-16 TS 28.541 OpenAPI file name and dependence change-nrNrm.yaml | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| approved | No | S5‑222222 | |||
S5‑222223 | Rel-16 TS 28.541 OpenAPI file name and dependence change-sliceNrm.yaml | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| revised | No | S5‑222583 | |||
S5‑222583 | Rel-16 TS 28.541 OpenAPI file name and dependence change-sliceNrm.yaml | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| approved | No | S5‑222223 | |||
S5‑222224 | Rel-17 TS 28.541 OpenAPI file name and dependence change-5gcNrm.yaml | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑222225 | Rel-17 TS 28.541 OpenAPI file name and dependence change-nrNrm.yaml | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑222226 | Rel-17 TS 28.541 OpenAPI file name and dependence change-sliceNrm.yaml | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑222248 | Rel-16 Draft CR 28.541 Correction on minor errrors in nrNRM yaml | Huawei | draftCR | Approval | Yes |
Yes
| revised | No | S5‑222597 | |||
S5‑222597 | Rel-16 Draft CR 28.541 Correction on minor errrors in nrNRM yaml | Huawei | draftCR | Approval | Yes |
Yes
| approved | No | S5‑222248 | |||
S5‑222249 | Rel-17 Draft CR 28.541 Correction on minor errrors in nrNRM yaml | Huawei | draftCR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑222250 | Rel-16 Draft CR 28.541 Correcton on the attribute definition in the wrong yaml file | Huawei | draftCR | Approval | Yes |
Yes
| revised | No | S5‑222598 | |||
S5‑222598 | Rel-16 Draft CR 28.541 Correcton on the attribute definition in the wrong yaml file | Huawei | draftCR | Approval | Yes |
Yes
| approved | No | S5‑222250 | |||
S5‑222251 | Rel-17 Draft CR 28.541 Correcton on the attribute definition in the wrong yaml file | Huawei | draftCR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑222264 | Rel-17 Draft CR 28.541 Correction on two SLA attributes | Huawei | draftCR | Approval | Yes |
Yes
| revised | No | S5‑222599 | |||
S5‑222599 | Rel-17 Draft CR 28.541 Correction on two SLA attributes | Huawei | draftCR | Approval | Yes |
Yes
| approved | No | S5‑222264 | |||
S5‑222285 | Rel-17 draftCR 28.541 Access specific slice configuration | Samsung R&D Institute India | draftCR | Agreement | Yes |
Yes
| revised | No | S5‑222606 | |||
S5‑222606 | Rel-17 draftCR 28.541 Access specific slice configuration | Samsung R&D Institute India | draftCR | Agreement | Yes |
Yes
| approved | No | S5‑222285 | |||
S5‑222293 | Rel-16 TS 28.623 OpenAPI file name and dependence change-comDefs.yaml | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| revised | No | S5‑222584 | |||
S5‑222584 | Rel-16 TS 28.623 OpenAPI file name and dependence change-comDefs.yaml | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| approved | No | S5‑222293 | |||
S5‑222294 | Rel-16 TS 28.623 OpenAPI file name and dependence change-genericNrm.yaml | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| revised | No | S5‑222585 | |||
S5‑222585 | Rel-16 TS 28.623 OpenAPI file name and dependence change-genericNrm.yaml | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| approved | No | S5‑222294 | |||
S5‑222295 | Rel-17 TS 28.623 OpenAPI file name and dependence change-comDefs.yaml | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑222296 | Rel-17 TS 28.623 OpenAPI file name and dependence change-genericNrm.yaml | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑222320 | Rel-16 draftCR 28.554 update formula of of PDU session establishment success rate | Huawei | other | Agreement | Yes |
Yes
| approved | No | ||||
S5‑222321 | Rel-17 draftCR 28.554 update formula of of PDU session establishment success rate | Huawei | draftCR | Agreement | Yes |
Yes
| withdrawn | Yes | ||||
S5‑222342 | Rel-17 draftCR for TS28.552 Correct the QoS flow setup related counters | ZTE | draftCR | Agreement | Yes |
Yes
| revised | No | S5‑222632 | |||
S5‑222632 | Rel-17 draftCR for TS28.552 Correct the QoS flow setup related counters | ZTE | draftCR | Agreement | Yes |
Yes
| noted | No | S5‑222342 | |||
S5‑222363 | Rel-17 draftCR for TS28.552 Change the measurement object class to support MOCN network sharing with multiple Cell Identity broadcast scenarios | ZTE | draftCR | Agreement | Yes |
Yes
| noted | No | ||||
S5‑222380 | Rel-17 draftCR for TS28.552 Add the measurement object class to support MOCN network sharing with multiple Cell Identity broadcast scenarios | ZTE | draftCR | Agreement | Yes |
Yes
| noted | No | ||||
S5‑222382 | Rel-16 CR TS 28.536 OpenAPI file name and dependence change-coslaNrm | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑222383 | Rel-17 CR TS 28.536 OpenAPI file name and dependence change-coslaNrm | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑222384 | Rel-17 CR TS 28.312 OpenAPI file name and dependence change-intentNrm | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑222385 | Rel-17 CR TS 28.538 OpenAPI file name and dependence change-edgeNrm | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑222386 | Rel-16 CR TS 28.541 Correction to RRMPolicy_ IOC reference in RRMPolicyRatio IOC | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑222387 | Rel-17 CR TS 28.541 Correction to RRMPolicy_ IOC reference in RRMPolicyRatio IOC | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑222388 | Rel-16 CR TS 28.541 Add attribute properties for NetworkSliceSubnet attribute priorityLabel | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑222389 | Rel-17 CR TS 28.541 Add attribute properties for NetworkSliceSubnet attribute priorityLabel | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑222390 | Rel-17 CR TS 28.541 Fix to change Support Qualifier to S | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑222391 | Rel-17 CR TS 28.541 Define LogicInterfaceInfo datatype and fix attribute properties for logicInterfaceInfo | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| revised | No | S5‑222600 | |||
S5‑222600 | Rel-17 CR TS 28.541 Define LogicInterfaceInfo datatype and fix attribute properties for logicInterfaceInfo | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| approved | No | S5‑222391 | |||
S5‑222470 | Rel-16 draftCR 28.552 Clean up of PM related to MRO | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| revised | No | S5‑222601 | |||
S5‑222601 | Rel-16 draftCR 28.552 Clean up of PM related to MRO | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| approved | No | S5‑222470 | |||
S5‑222487 | Rel-17 Draft CR 28.552 Correct implementation mistakes | Ericsson France S.A.S,Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑222495 | DraftCR 28.541 Correct NR NRM defaultValue Null | Ericsson | draftCR | Yes |
Yes
| approved | No | |||||
S5‑222501 | Rel-16 Draft CR 28.532 OpenAPI file name and dependence change- part1 | Huawei | draftCR | Approval | Yes |
Yes
| revised | No | S5‑222580 | |||
S5‑222580 | Rel-16 Draft CR 28.532 OpenAPI file name and dependence change- part1 | Huawei | draftCR | Approval | Yes |
Yes
| approved | No | S5‑222501 | |||
S5‑222502 | Rel-16 Draft CR 28.532 OpenAPI file name and dependence change- part2 | Huawei | draftCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑222503 | Rel-16 Draft CR 28.550 OpenAPI file name and dependence change | Huawei | draftCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑222504 | Rel-17 Draft CR 28.532 OpenAPI file name and dependence change- part1 | Huawei | draftCR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑222505 | Rel-17 Draft CR 28.532 OpenAPI file name and dependence change- part2 | Huawei | draftCR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑222518 | CT OpenAPI file relative-path URI references and dependence change for 5gcNrm.yaml | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑222519 | Rel-17 CT OpenAPI file relative-path URI references and dependence change for 5gcNrm.yaml | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑222521 | Rel-17 Draft CR For TS 28.554 Updating Packet transmission reliability KPI in DL on N3 | Samsung Electronics Co., Ltd | draftCR | Approval | Yes |
Yes
| revised | No | S5‑222613 | |||
S5‑222613 | Rel-17 Draft CR For TS 28.554 Updating Packet transmission reliability KPI in DL on N3 | Samsung Electronics Co., Ltd | draftCR | Approval | Yes |
Yes
| approved | No | S5‑222521 | |||
S5‑222526 | Rel-17 DraftCR Dont use isNullable true | Ericsson Hungary Ltd | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑222527 | Rel-17 Draft CR 28.541 Correct maximumDeviationHoTrigger for D-LBO | Ericsson France S.A.S | draftCR | Approval | Yes |
Yes
| revised | No | S5‑222602 | |||
S5‑222602 | Rel-17 Draft CR 28.541 Correct maximumDeviationHoTrigger for D-LBO | Ericsson France S.A.S | draftCR | Approval | Yes |
Yes
| approved | No | S5‑222527 | |||
S5‑222528 | Rel-16 draftCR 28.541 Fix BWP association to NRCellDU | Ericsson LM | draftCR | Approval | Yes |
Yes
| revised | No | S5‑222571 | |||
S5‑222571 | Rel-16 draftCR 28.541 Fix BWP association to NRCellDU | Ericsson LM | draftCR | Approval | Yes |
Yes
| approved | No | S5‑222528 | |||
S5‑222530 | Rel-16 draftCR 28.532 Fix FileDataType definition (OpenAPI) | Ericsson LM | draftCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑222532 | Rel-16 draftCR 28.541 Update 5QI set description (YANG) | Ericsson LM | draftCR | Approval | Yes |
Yes
| revised | No | S5‑222603 | |||
S5‑222603 | Rel-16 draftCR 28.541 Update 5QI set description (YANG) | Ericsson LM | draftCR | Approval | Yes |
Yes
| approved | No | S5‑222532 | |||
S5‑222535 | Rel-16 draftCR 28.541 Rel-16 Update 5QI set attribute definition | Ericsson LM | draftCR | Approval | Yes |
Yes
| revised | No | S5‑222604 | |||
S5‑222604 | Rel-16 draftCR 28.541 Rel-16 Update 5QI set attribute definition | Ericsson LM | draftCR | Approval | Yes |
Yes
| approved | No | S5‑222535 | |||
S5‑222536 | draftCR R17 Add support for disabling CL for certain MOI | Lenovo, Motorola Mobility | CR | Agreement | Yes |
Yes
| withdrawn | Yes | ||||
S5‑222537 | Rel-16 DraftCR Alarm Handling Clarifications | Ericsson Hungary Ltd | other | Approval | Yes |
Yes
| noted | No | ||||
S5‑222539 | Rel-16 DraftCR YANG corrections | Ericsson Hungary Ltd | draftCR | Approval | Yes |
Yes
| merged | No | S5‑222592 | |||
S5‑222546 | Rel-17 DraftCR Data change notifications YANG-in-Rest format | Ericsson Hungary Ltd | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑222547 | Rel-17 Input to DraftCR YANG Mapping Corrections | Ericsson Hungary Ltd | other | Approval | Yes |
Yes
| approved | No | ||||
S5‑222548 | Rel-17 Input to DraftCR Correct isOrdered-NA and isUnique-NA for multivalue attributes | Ericsson Hungary Ltd | other | Approval | Yes |
Yes
| noted | No | ||||
S5‑222549 | Rel-17 Input to DraftCR Correct isOrdered-NA and isUnique-NA for multivalue attributes | Ericsson Hungary Ltd | other | Approval | Yes |
Yes
| noted | No | ||||
S5‑222552 | draftCR R17 Add support for disabling CL for certain MOI | Lenovo, Motorola Mobility | draftCR | Yes |
Yes
| conditionally approved | No | |||||
6.4.1 | Self-Configuration of RAN NEs | S5‑222252 | pCR TS 28.317 Add scope | Huawei,China Mobile | pCR | Approval | Yes |
Yes
| revised | No | S5‑222605 | |
S5‑222605 | pCR TS 28.317 Add scope | Huawei,China Mobile | pCR | Approval | Yes |
Yes
| approved | No | S5‑222252 | |||
S5‑222393 | Initial skeleton (v000) of TS 28.317 | China Mobile, Huawei | draft TS | Approval | Yes |
Yes
| approved | No | ||||
S5‑222397 | 28.317 Skeleton Proposal | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑222634 | |||
S5‑222634 | 28.317 Skeleton Proposal | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑222397 | |||
S5‑222399 | 28.317 Add Concept | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑222726 | draft TS 28.317 | China Mobile | draft TS | Approval | No |
Yes
| approved | No | ||||
6.4.2 | Network slicing provisioning rules | S5‑222488 | Input to draftCR 28.541 Add network slice rules to NRM | Ericsson GmbH, Eurolab | other | Approval | Yes |
Yes
| noted | No | ||
S5‑222490 | Input to draftCR 28.531 Specify network slicing provisioning rules requirements | Ericsson GmbH, Eurolab | other | Approval | Yes |
Yes
| noted | No | ||||
6.4.3 | Additional NRM features phase 2 | S5‑222451 | Rel-18 Input to draftCR 28.622 Add Scheduler IOC (stage 2) | Nokia, Nokia Shanghai Bell | other | Approval | Yes |
Yes
| noted | No | ||
S5‑222452 | Rel-18 Input to draftCR 28.623 Add Scheduler IOC (stage 3) | Nokia, Nokia Shanghai Bell | other | Approval | Yes |
Yes
| noted | No | ||||
S5‑222453 | Rel-17 draftCR 28.622 Enhancement of SupportedPerfMetricGroup (stage 2) | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑222454 | Rel-17 draftCR 28.623 Enhancement of SupportedPerfMetricGroup (stage 3) | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑222510 | NRM enhacements for UPFFunction (stage 2) | Nokia Germany | CR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑222514 | NRM enhancements for UPFFunction (Stage 3) | Nokia Germany | CR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑222516 | Enhance 5G Core managed NF Profile NRM fragment (Stage 3) | Nokia Germany | CR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑222517 | Enhance 5G Core managed NF Profile NRM fragment (Stage 2) | Nokia Germany | CR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑222541 | Discussion on enhanced BWP configuration support in NRM | Ericsson LM | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑222542 | Discussion on enhanced QoS model | Ericsson LM | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑222627 | |||
S5‑222627 | Discussion on enhanced QoS model | Ericsson LM | discussion | Endorsement | Yes |
Yes
| endorsed | No | S5‑222542 | |||
S5‑222544 | Rel-18 Input to draftCR 28.622 Enhance PerfMetricJob by scheduling condition (stage 2) | Nokia, Nokia Shanghai Bell | other | Approval | Yes |
Yes
| noted | No | ||||
S5‑222545 | Rel-18 Input to draftCR 28.623 Enhance PerfMetricJob by scheduling condition (stage 3) | Nokia, Nokia Shanghai Bell | other | Approval | Yes |
Yes
| noted | No | ||||
S5‑222564 | Rel-18 DraftCR NRM enhacements for UPFFunction (stage 2) | Nokia | draftCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑222565 | Rel-18 DraftCR NRM enhancements for UPFFunction (Stage 3) | Nokia | draftCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑222566 | Rel-18 DraftCR Enhance 5G Core managed NF Profile NRM fragment (Stage 3) | Nokia | draftCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑222567 | Rel-18 DraftCR Enhance 5G Core managed NF Profile NRM fragment (Stage 2) | Nokia | draftCR | Approval | No |
Yes
| withdrawn | Yes | ||||
6.4.4 | Enhanced Edge Computing Management | S5‑222042 | [Draft CR] Rel-18 28.622 Add stage 2 solution for LcmJob IOC | Intel Korea, Ltd. | draftCR | Approval | Yes |
Yes
| noted | No | ||
S5‑222043 | [Draft CR] Rel-18 28.623 Add stage 3 solution for LcmJob IOC | Intel Korea, Ltd. | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑222047 | [Draft CR] Rel-18 28.538 Add a use case for EAS discovery failure | Intel Korea, Ltd. | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑222048 | [Draft CR] Rel-18 28.538 Add a procedurefor EAS discovery failure | Intel Korea, Ltd. | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑222049 | [Draft CR] Rel-18 28.538 Add the stage 2 solution for EASDiscovery IOC | Intel Korea, Ltd. | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑222050 | [Draft CR] Rel-18 28.538 Add the stage 2 solution for EASDiscovery IOC | Intel Korea, Ltd. | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑222059 | R17 TS 28.538 add modification procedures | AsiaInfo Technologies Inc | draftCR | Approval | Yes |
Yes
| revised | No | S5‑222607 | |||
S5‑222607 | R17 TS 28.538 add modification procedures | AsiaInfo Technologies Inc | draftCR | Approval | Yes |
Yes
| approved | No | S5‑222059 | |||
S5‑222060 | R17 TS 28.538 add query procedures | AsiaInfo Technologies Inc | draftCR | Approval | Yes |
Yes
| revised | No | S5‑222608 | |||
S5‑222608 | R17 TS 28.538 add query procedures | AsiaInfo Technologies Inc | draftCR | Approval | Yes |
Yes
| approved | No | S5‑222060 | |||
S5‑222291 | Rel-18 InputToDraftCR 28.538 EESFunction IOC | Samsung R&D Institute India | other | Agreement | Yes |
Yes
| revised | No | S5‑222628 | |||
S5‑222628 | Rel-18 InputToDraftCR 28.538 EESFunction IOC | Samsung R&D Institute India | other | Agreement | Yes |
Yes
| conditionally approved | No | S5‑222291 | |||
S5‑222337 | DraftCR 28.538 update description of ECM LCM | Huawei | draftCR | Approval | Yes |
Yes
| revised | No | S5‑222609 | |||
S5‑222609 | DraftCR 28.538 update description of ECM LCM | Huawei | draftCR | Approval | Yes |
Yes
| approved | No | S5‑222337 | |||
S5‑222338 | DraftCR 28.538 update ECM NRM stage 2 | Huawei | draftCR | Approval | Yes |
Yes
| revised | No | S5‑222610 | |||
S5‑222610 | DraftCR 28.538 update ECM NRM stage 2 | Huawei | draftCR | Approval | Yes |
Yes
| approved | No | S5‑222338 | |||
S5‑222339 | DraftCR 28.538 update ECM NRM stage 3 | Huawei | draftCR | Approval | Yes |
Yes
| revised | No | S5‑222611 | |||
S5‑222611 | DraftCR 28.538 update ECM NRM stage 3 | Huawei | draftCR | Approval | Yes |
Yes
| approved | No | S5‑222339 | |||
S5‑222340 | DraftCR 28.538 correct EAS lifecycle management procedure | Huawei | draftCR | Approval | Yes |
Yes
| revised | No | S5‑222612 | |||
S5‑222612 | DraftCR 28.538 correct EAS lifecycle management procedure | Huawei | draftCR | Approval | Yes |
Yes
| approved | No | S5‑222340 | |||
S5‑222568 | LS on the clarification of Dynamic EAS instantiation triggering | Intel | LS out | Approval | Yes |
Yes
| approved | No | ||||
6.4.5 | Enhancements of EE for 5G Phase 2 |   | ||||||||||
6.5.1 | Study on enhancement of autonomous network levels | S5‑222061 | Add key issue #X: ANL for RAN Energy Saving | AsiaInfo Technologies Inc | pCR | Approval | Yes |
Yes
| merged | No | S5‑222614 | |
S5‑222126 | TR 28.910 v0.0.0 Initial skeleton | China Mobile, Huawei | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S5‑222128 | pCR 28.910 Add TR structure | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑222615 | |||
S5‑222615 | pCR 28.910 Add TR structure | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑222128 | |||
S5‑222129 | pCR 28.910 Add scope | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑222616 | |||
S5‑222616 | pCR 28.910 Add scope | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑222129 | |||
S5‑222253 | pCR TR 28.910 Add autonomous network level for radio network planning | Huawei,China Mobile | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑222254 | pCR TS 28.910 Add autonomous network level for RAN energy saving scenario | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑222614 | |||
S5‑222614 | pCR TS 28.910 Add autonomous network level for RAN energy saving scenario | Huawei,AsiaInfo, China Mobile | pCR | Approval | Yes |
Yes
| approved | No | S5‑222254 | |||
S5‑222727 | draft TR 28.910 | China Mobile | draft TR | Approval | Yes |
Yes
| approved | No | ||||
6.5.2 | Study on evaluation of autonomous network levels | S5‑222121 | TR 28.909 v0.0.0 Initial skeleton | China Mobile, Huawei | draft TR | Approval | Yes |
Yes
| approved | No | ||
S5‑222123 | pCR 28.909 Add TR structure and abbreviation | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑222617 | |||
S5‑222617 | pCR 28.909 Add TR structure and abbreviation | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑222123 | |||
S5‑222124 | pCR 28.909 Add scope | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑222618 | |||
S5‑222618 | pCR 28.909 Add scope | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑222124 | |||
S5‑222125 | pCR 28.909 Add concept description for autonomous network level evaluation | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑222619 | |||
S5‑222619 | pCR 28.909 Add concept description for autonomous network level evaluation | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑222125 | |||
S5‑222728 | draft TR 28.909 | China Mobile | draft TR | Approval | Yes |
Yes
| approved | No | ||||
6.5.3 | Study on enhanced intent driven management services for mobile networks | S5‑222244 | TR 28.912 initial version-0.0.0 | Huawei,Ericsson | draft TR | Approval | Yes |
Yes
| approved | No | ||
S5‑222255 | pCR TR 28.912 Add scope | Huawei,Ericsson | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑222256 | pCR TR 28.912 Add structure | Huawei,Ericsson | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑222299 | pCR TR 28.912 Add key issue for intent driven approach for RAN energy saving | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑222620 | |||
S5‑222620 | pCR TR 28.912 Add key issue for intent driven approach for RAN energy saving | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑222299 | |||
S5‑222569 | pCR TR 28.912 Add potential requirements for intent conflict information | Nokia | pCR | Approval | No |
Yes
| approved | No | ||||
S5‑222729 | draft TR 28.912 | Huawei | draft TR | Approval | Yes |
Yes
| approved | No | ||||
6.5.4 | Study on intent-driven management for network slicing | S5‑222038 | Rel-18 TR 28.836-Cover Sheet | Ericsson GmbH, Eurolab | TS or TR cover | No |
Yes
| withdrawn | Yes | |||
S5‑222039 | Rel-18 pCR TR 28.836 Structure | Ericsson GmbH, Eurolab | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑222040 | Rel-18 pCR TR 28.836 Add scope | Ericsson GmbH, Eurolab, Deutsche Telekom | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑222041 | Rel-18 pCR TR 28.836 Add introduction | Ericsson GmbH, Eurolab, Deutsche Telekom | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑222098 | TR 28.836 skeleton -0.0.0 | Ericsson | draft TR | Yes |
Yes
| approved | No | |||||
S5‑222322 | pCR 28.836 Add background of mapping in TS 28.531 | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑222636 | |||
S5‑222636 | pCR 28.836 Add background of mapping in TS 28.531 | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑222322 | |||
S5‑222323 | pCR 28.836 Add background information related to 28.312 | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑222637 | |||
S5‑222637 | pCR 28.836 Add background information related to 28.312 | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑222323 | |||
S5‑222730 | draft TR 28.836 | Ericsson | draft TR | Approval | Yes |
Yes
| approved | No | ||||
6.5.5 | Study on AI/ ML management | S5‑222178 | Initial skeleton (v000) of TR 28.908 | Intel Technology Poland SP Zoo | draft TR | Information | Yes |
Yes
| approved | No | ||
S5‑222188 | pCR 28.908 Add scope | Intel, NEC | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑222191 | pCR 28.908 Add AI-ML workflow for 5GS | Intel, NEC | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑222192 | pCR 28.908 Add use case on AI-ML model validation | Intel, NEC | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑222464 | Rel-18 pCR TR 28.908 Add key issues of Model deployment for MDA | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑222465 | Rel-18 pCR TR 28.908 Add key issues of Energy saving AIML management | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑222477 | pCR 28.908 Add AI/ML management overview | NEC, Intel | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑222731 | draft TR 28.908 | Intel | draft TR | Approval | Yes |
Yes
| approved | No | ||||
6.5.6 | Study on Enhancement of the management aspects related to NWDAF | S5‑222052 | TR 28.864-0.0.0 initial skeleton | China Telecom Corporation Ltd. | draft TR | Yes |
Yes
| approved | No | |||
S5‑222053 | pCR 28.864 Clause titles for TR28.864 | China Telecom Corporation Ltd. | pCR | Yes |
Yes
| revised | No | S5‑222621 | ||||
S5‑222621 | pCR 28.864 Clause titles for TR28.864 | China Telecom Corporation Ltd. | pCR | - | Yes |
Yes
| approved | No | S5‑222053 | |||
S5‑222064 | pCR 28.864 new KI on NRM enhancement to support Multiple NWDAF Deployment | China Telecom Corporation Ltd. | pCR | Yes |
Yes
| revised | No | S5‑222622 | ||||
S5‑222622 | pCR 28.864 new KI on NRM enhancement to support Multiple NWDAF Deployment | China Telecom Corporation Ltd. | pCR | - | Yes |
Yes
| approved | No | S5‑222064 | |||
S5‑222475 | pCR 28.864 Add new key issue for the performance management of the NWDAF on the interaction aspect | China Telecom Corporation Ltd. | pCR | Approval | Yes |
Yes
| revised | No | S5‑222624 | |||
S5‑222624 | pCR 28.864 Add new key issue for the performance management of the NWDAF on the interaction aspect | China Telecom Corporation Ltd. | pCR | Approval | Yes |
Yes
| approved | No | S5‑222475 | |||
S5‑222476 | pCR 28.864 Add new key issue for the NRM enhancement of NWDAF to support the logical decomposition of NWDAF | China Telecom Corporation Ltd. | pCR | Approval | Yes |
Yes
| revised | No | S5‑222623 | |||
S5‑222623 | pCR 28.864 Add new key issue for the NRM enhancement of NWDAF to support the logical decomposition of NWDAF | China Telecom Corporation Ltd. | pCR | Approval | Yes |
Yes
| approved | No | S5‑222476 | |||
S5‑222732 | draft TR 28.864 | China Telecom | draft TR | Approval | Yes |
Yes
| approved | No | ||||
6.5.7 | Study on Fault Supervision Evolution | S5‑222371 | TR 28.830 v0.0.0 Initial skeleton | China Mobile, Huawei | draft TR | Approval | Yes |
Yes
| approved | No | ||
S5‑222373 | pCR 28.830 Add TR structure | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑222625 | |||
S5‑222625 | pCR 28.830 Add TR structure | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑222373 | |||
S5‑222374 | pCR 28.830 Add background | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑222375 | pCR 28.830 Add scope | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑222626 | |||
S5‑222626 | pCR 28.830 Add scope | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑222375 | |||
S5‑222733 | draft TR 28.830 | China Mobile | draft TR | Approval | Yes |
Yes
| approved | No | ||||
6.5.8 | Study on Enhancement of service based management architecture | S5‑222353 | pCR TR 28.925 Add key issue on the applicable content from TS 32.101 section 4 | Huawei Technologies (Korea) | pCR | Yes |
Yes
| noted | No | |||
S5‑222354 | pCR TR 28.925 Add key issue on the applicable content from TS 32.101 section 7 | Huawei Technologies (Korea) | pCR | Yes |
Yes
| revised | No | S5‑222629 | ||||
S5‑222629 | pCR TR 28.925 Add key issue on the applicable content from TS 32.101 section 7 | Huawei Technologies (Korea) | pCR | - | Yes |
Yes
| approved | No | S5‑222354 | |||
S5‑222358 | pCR TR 28.925 Add Key issue on management reference model analysis in TS 32.101 | Huawei Technologies (Korea) | pCR | Yes |
Yes
| noted | No | |||||
S5‑222491 | pCR R18 28.925-030 Proposal to update 32.401 and 32.404 for SBMA | Ericsson | pCR | Yes |
Yes
| revised | No | S5‑222630 | ||||
S5‑222630 | pCR R18 28.925-030 Proposal to update 32.401 and 32.404 for SBMA | Ericsson | pCR | - | Yes |
Yes
| approved | No | S5‑222491 | |||
S5‑222734 | draft TR 28.925 | Huawei | draft TR | Approval | Yes |
Yes
| approved | No | ||||
6.5.9 | Study on Basic SBMA enabler enhancements | S5‑222173 | S5-222173 Rel-18 pCR 28.831 Add skeleton | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||
S5‑222174 | Rel-18 pCR 28.831 Add key issue 1 Schema for notifyMOIChanges | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑222175 | Rel-18 pCR 28.831 Add key issue 2 Targeted notification subscriptions | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑222176 | Rel-18 pCR 28.831 Add material key issue 2 Targeted notification subscriptions | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑222520 | Draft TR 28.831 | Nokia, Nokia Shanghai Bell | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S5‑222735 | draft TR 28.831 | Nokia | draft TR | Approval | No |
Yes
| approved | No | ||||
6.5.10 | Study on Management Aspects of URLLC | S5‑222292 | TR 28.832-0.0.0 initial skeleton | China Unicom | draft TR | Approval | Yes |
Yes
| approved | No | ||
S5‑222307 | Add scope | China Unicom | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑222344 | pCR 28.832 Add Concepts and overview | China Unicom | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑222350 | pCR TR28.832 Add key issue on classification of URLLC related RAN features from management perspective | China Unicom | pCR | Approval | Yes |
Yes
| revised | No | S5‑222660 | |||
S5‑222660 | pCR TR28.832 Add key issue on classification of URLLC related RAN features from management perspective | China Unicom | pCR | Approval | Yes |
Yes
| approved | No | S5‑222350 | |||
S5‑222736 | draft TR 28.832 | China Unicom | draft TR | Approval | Yes |
Yes
| approved | No | ||||
6.5.11 | Study on Management Aspect of 5GLAN | S5‑222300 | TR 28.833 Initial Skeleton v0.0.0 | China Mobile Com. Corporation | draft TR | Yes |
Yes
| approved | No | |||
S5‑222301 | TR 28.833 Add TR structure | China Mobile Com. Corporation | pCR | Yes |
Yes
| approved | No | |||||
S5‑222302 | TR 28.833 Add scope of management aspect of 5GLAN | China Mobile Com. Corporation | pCR | Yes |
Yes
| revised | No | S5‑222661 | ||||
S5‑222661 | TR 28.833 Add scope of management aspect of 5GLAN | China Mobile Com. Corporation | pCR | - | Yes |
Yes
| approved | No | S5‑222302 | |||
S5‑222303 | TR 28.833 Add concepts and background of FS_5GLAN_Mgt | China Mobile Com. Corporation | pCR | Yes |
Yes
| revised | No | S5‑222662 | ||||
S5‑222662 | TR 28.833 Add concepts and background of FS_5GLAN_Mgt | China Mobile Com. Corporation | pCR | - | Yes |
Yes
| approved | No | S5‑222303 | |||
S5‑222737 | draft TR 28.833 | China Mobile | draft TS | Approval | Yes |
Yes
| approved | No | ||||
6.5.12 | Study on Management of Cloud Native Virtualized Network Functions |   | ||||||||||
6.5.13 | Study on Management Aspects of 5G MOCN Network Sharing Phase2 | S5‑222297 | TR 28.835-0.0.0 initial skeleton | China Unicom | draft TR | Approval | Yes |
Yes
| approved | No | ||
S5‑222308 | Add scope to TR 28.835 | China Unicom | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑222343 | Add key issue management requirement for different POP’s network operation | China Unicom | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑222356 | Add key issue performance measurements without PLMN ID at NRcellCU | China Unicom | pCR | Approval | Yes |
Yes
| revised | No | S5‑222663 | |||
S5‑222663 | Add key issue performance measurements without PLMN ID at NRcellCU | China Unicom | pCR | Approval | Yes |
Yes
| approved | No | S5‑222356 | |||
S5‑222359 | Add potential solution for performance measurements without PLMN ID at NRcellCU | China Unicom | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑222738 | draft TR 28.835 | China Unicom | draft TR | Approval | Yes |
Yes
| approved | No | ||||
6.5.14 | Study on continuous integration continuous delivery support for 3GPP NFs | S5‑222324 | pCR 28.819 Add description of roles | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑222664 | |
S5‑222664 | pCR 28.819 Add description of roles | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑222324 | |||
S5‑222325 | pCR 28.819 Add description of deployment options | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑222326 | pCR 28.819 Update the phase of 3GPP NF monitoring | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑222665 | |||
S5‑222665 | pCR 28.819 Update the phase of 3GPP NF monitoring | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑222326 | |||
S5‑222345 | pCR 28.819 Solution of test orchestration | China Mobile Com. Corporation, Lenovo, Motorola Mobility | pCR | Approval | Yes |
Yes
| revised | No | S5‑222666 | |||
S5‑222666 | pCR 28.819 Solution of test orchestration | China Mobile Com. Corporation, Lenovo, Motorola Mobility | pCR | Approval | Yes |
Yes
| approved | No | S5‑222345 | |||
S5‑222346 | pCR 28.819 Proposed overall process | China Mobile Com. Corporation, Lenovo, Motorola Mobility | pCR | Approval | Yes |
Yes
| revised | No | S5‑222755 | |||
S5‑222755 | pCR 28.819 Proposed overall process | China Mobile Com. Corporation, Lenovo, Motorola Mobility | pCR | Approval | Yes |
Yes
| noted | No | S5‑222346 | |||
S5‑222739 | draft TR 28.819 | Lenovo | draft TR | Approval | Yes |
Yes
| approved | No | ||||
6.5.15 | Study on Management of Trace/MDT phase 2 | S5‑222186 | draft TR 28.837 | Nokia, Nokia Shanghai Bell | draft TR | Approval | Yes |
Yes
| approved | No | ||
S5‑222190 | pCR 28.837 skeleton | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑222211 | pCR 28.837 scope | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑222213 | pCR 28.837 Reporting Methods of TraceJob and PerfMetricJob | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑222740 | draft TR 28.837 | Nokia | draft TR | Approval | Yes |
Yes
| approved | No | ||||
6.5.16 | Study on YANG PUSH |   | ||||||||||
6.5.17 | Study on enhancement of management of non-public networks | S5‑222265 | TR 28.907 initial skeleton | Huawei | draft TR | Approval | Yes |
Yes
| approved | No | ||
S5‑222266 | pCR 28.907 Skeleton proposal from Rapporteur | Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑222267 | pCR 28.907 Scope proposal from Rapporteur | Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑222268 | pCR 28.907 Overview proposal | Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑222269 | Update SID on enhancement of management of NPN | Huawei | SID revised | Approval | Yes |
Yes
| approved | No | ||||
S5‑222270 | pCR 28.907 Key Issue on Resource isolation demand for vertical applications | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑222667 | |||
S5‑222667 | pCR 28.907 Key Issue on Resource isolation demand for vertical applications | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑222270 | |||
S5‑222271 | pCR 28.907 Key Issue on E2E fault management | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑222668 | |||
S5‑222668 | pCR 28.907 Key Issue on E2E fault management | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑222271 | |||
S5‑222272 | pCR 28.907 Key Issue on Management of NPN service customer | Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑222741 | draft TR 28.907 | Huawei | draft TR | Approval | Yes |
Yes
| approved | No | ||||
6.5.18 | Study on new aspects of EE for 5G networks Phase 2 | S5‑222022 | TR 28.913 skeleton | Orange | draft TR | Approval | Yes |
Yes
| approved | No | ||
S5‑222023 | pCR TR 28.913 Clause titles for key issues and solutions | Orange | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑222024 | pCR TR 28.913 New Key Issue Considering additional virtual resources usage | Orange, AT&T, Telefonica | pCR | Approval | Yes |
YesDeutsche Telekom supported this contribution.
| approved | No | ||||
S5‑222025 | pCR TR 28.913 New key issue Considering Containerized Network Functions | Orange, AT&T, Telefonica, Deutsche Telekom | pCR | Approval | Yes |
Yes
| revised | No | S5‑222669 | |||
S5‑222669 | pCR TR 28.913 New key issue Considering Containerized Network Functions | Orange, AT&T, Telefonica, Deutsche Telekom | pCR | Approval | Yes |
Yes
| approved | No | S5‑222025 | |||
S5‑222026 | pCR TR 28.913 New key issue Energy Consumption of RAN nodes | Orange, Deutsche Telekom | pCR | Approval | Yes |
Yes
| revised | No | S5‑222670 | |||
S5‑222670 | pCR TR 28.913 New key issue Energy Consumption of RAN nodes | Orange, Deutsche Telekom | pCR | Approval | Yes |
Yes
| approved | No | S5‑222026 | |||
S5‑222742 | draft TR 28.913 | Orange | draft TR | Approval | Yes |
Yes
| approved | No | ||||
6.5.19 | Study on Network and Service Operations for Energy Utilities | S5‑222016 | Rel-18 pCR TR 28.829-Annex-B-IT Services Model | Samsung, EUTC, EDF, BMWK | pCR | Approval | Yes |
Yes
| approved | No | ||
S5‑222017 | TR 22.829 skeleton cover sheet | Samsung (Rapporteur) | draft TR | Agreement | Yes |
Yes
| revised | No | S5‑222671 | |||
S5‑222671 | TR 22.829 skeleton cover sheet | Samsung (Rapporteur) | draft TR | Agreement | Yes |
Yes
| approved | No | S5‑222017 | |||
S5‑222018 | pCR 28.829 Structure | Samsung (Rapporteur) | pCR | Approval | Yes |
Yes
| revised | No | S5‑222672 | |||
S5‑222672 | pCR 28.829 Structure | Samsung (Rapporteur) | pCR | Approval | Yes |
Yes
| approved | No | S5‑222018 | |||
S5‑222019 | pCR TR 28.829 Scope | Samsung, EUTC, EDF, BMWK | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑222020 | pCR TR 28.829 Overview | Samsung, EUTC, EDF, BMWK | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑222743 | draft TR 28.829 | Samsung | draft TR | Approval | Yes |
Yes
| approved | No | ||||
6.5.20 | Study on Key Quality Indicators (KQIs)for 5G service experience | S5‑222107 | TR 28.863-0.0.0 initial skeleton | Huawei | draft TR | Approval | Yes |
Yes
| revised | No | S5‑222673 | |
S5‑222673 | TR 28.863-0.0.0 initial skeleton | Huawei | draft TR | Approval | Yes |
Yes
| approved | No | S5‑222107 | |||
S5‑222108 | pCR TR28.863 Skeleton proposal for TR28.863 | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑222674 | |||
S5‑222674 | pCR TR28.863 Skeleton proposal for TR28.863 | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑222108 | |||
S5‑222109 | pCR TR 28.863 add scope | Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑222112 | pCR TR 28.863 Key Issue # 1 Definition of KQI | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑222114 | pCR TR 28.863 Key Issue # 2 Scenarios for 5G KQI | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑222675 | |||
S5‑222675 | pCR TR 28.863 Key Issue # 2 Scenarios for 5G KQI | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑222114 | |||
S5‑222744 | draft TR 28.863 | Huawei | draft TR | Approval | Yes |
Yes
| approved | No | ||||
6.5.21 | Study on Deterministic Communication Service Assurance | S5‑222113 | TR 28.865 Skeleton | Huawei | draft TR | Approval | Yes |
Yes
| approved | No | ||
S5‑222115 | pCR TR 28.865 Add scope of FS_DCSA | Huawei Technologies Japan K.K. | pCR | Approval | Yes |
Yes
| revised | No | S5‑222677 | |||
S5‑222677 | pCR TR 28.865 Add scope of FS_DCSA | Huawei Technologies Japan K.K. | pCR | Approval | Yes |
Yes
| approved | No | S5‑222115 | |||
S5‑222117 | pCR TR 28.865 Add overview of FS_DCSA | Huawei Technologies Japan K.K. | pCR | Approval | Yes |
Yes
| revised | No | S5‑222678 | |||
S5‑222678 | pCR TR 28.865 Add overview of FS_DCSA | Huawei Technologies Japan K.K. | pCR | Approval | Yes |
Yes
| approved | No | S5‑222117 | |||
S5‑222118 | pCR TR 28.865 Skeleton proposa | Huawei Technologies Japan K.K. | pCR | Approval | Yes |
Yes
| revised | No | S5‑222676 | |||
S5‑222676 | pCR TR 28.865 Skeleton proposa | Huawei Technologies Japan K.K. | pCR | Approval | Yes |
Yes
| approved | No | S5‑222118 | |||
S5‑222745 | draft TR 28.865 | Huawei | draft TR | discussion | Yes |
Yes
| approved | No | ||||
6.5.22 | Study on management aspects of network slice management capability exposure | S5‑222135 | Add procedure for consumption of exposed MnS after service order is completed | Ericsson GmbH, Eurolab, Deutsche Telekom | pCR | Approval | Yes |
Yes
| noted | No | ||
S5‑222189 | Discussion paper on management capability exposure using CAPIF | Ericsson, Orange, AT&T, Telefonica, Deutsche Telekom | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑222274 | pCR 28.824 Add new requirements related to exposure interface via OSS | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑222275 | pCR 28.824 Update potential solution for exposed MnS consumption via OSS interface | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑222276 | pCR 28.824 Update use case Exposure of network slice as a service | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑222327 | pCR 28.824 Describe possible solution for EGMF | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑222756 | |||
S5‑222756 | pCR 28.824 Describe possible solution for EGMF | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑222327 | |||
S5‑222328 | pCR 28.824 Add scenario of management exposure | China Southern Power Grid, Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑222457 | Discussion Paper on 5G exposure | AT&T, Deutsche Telekom, Ericsson, Huawei, Intel, Orange, Samsung, Telefonica, Verizon | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑222723 | |||
S5‑222723 | Discussion Paper on 5G exposure | AT&T, Deutsche Telekom, Ericsson, Huawei, Intel, Orange, Samsung, Telefonica, Verizon | discussion | Endorsement | Yes |
Yes
| approved | No | S5‑222457 | |||
S5‑222466 | LS out to SA6 about using CAPIF for 5G management capabilities exposure | AT&T, Deutsche Telekom, Orange, Telefonica | LS out | Agreement | Yes |
Yes
| noted | No | ||||
S5‑222467 | Discussion Paper on exposure via OSS | AsiaInfo Technologies Inc, Alibaba | discussion | Endorsement | No |
Yes
| withdrawn | Yes | ||||
S5‑222468 | Update potential solution for MnS discovery service for exposure | AsiaInfo Technologies Inc, Alibaba | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑222469 | Discussion Paper on exposure via OSS | AsiaInfo Technologies Inc, Alibaba | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑222506 | pCR 28.824 solution on exposure architecture and related API | Alibaba Group, AsiaInfo | pCR | Approval | Yes |
Yes
| revised | No | S5‑222725 | |||
S5‑222725 | pCR 28.824 solution on exposure architecture and related API | Alibaba Group, AsiaInfo | pCR | Approval | Yes |
Yes
| approved | No | S5‑222506 | |||
S5‑222507 | Update position and add solution for direct MnS exposure | Lenovo, Motorola Mobility | pCR | Agreement | Yes |
Yes
| noted | No | ||||
S5‑222511 | Update use case 5.2 | Alibaba Group, AsiaInfo | pCR | Approval | Yes |
Yes
| revised | No | S5‑222680 | |||
S5‑222680 | Update use case 5.2 | Alibaba Group, AsiaInfo | pCR | Approval | Yes |
Yes
| approved | No | S5‑222511 | |||
S5‑222513 | DP on external API for Capability Exposure | Alibaba Group, AsiaInfo | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑222679 | |||
S5‑222679 | DP on external API for Capability Exposure | Alibaba Group, AsiaInfo | discussion | Endorsement | Yes |
Yes
| endorsed | No | S5‑222513 | |||
S5‑222515 | pCR 28.824 Add note on possible charging impact | Lenovo, Motorola Mobility | pCR | Yes |
Yes
| noted | No | |||||
S5‑222746 | draft TR 28.824 | Alibaba | draft TR | Approval | No |
Yes
| approved | No | ||||
6.5.23 | Study on alignment with ETSI MEC for Edge computing management | S5‑222103 | Initial version of TR28.903 | HUAWEI TECH. GmbH | draft TR | Approval | Yes |
Yes
| approved | No | ||
S5‑222329 | pCR 28.903 add scope | Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑222330 | pCR TR 28.903 Add skeleton | Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑222747 | draft TR 28.903 | Huawei | draft TR | Approval | Yes |
Yes
| approved | No | ||||
6.6.1 | Enhancement of QoE Measurement Collection | S5‑222499 | Input to DraftCR Adding Signalling Based Activation for NR | Ericsson | other | Yes |
Yes
| withdrawn | Yes | |||
S5‑222508 | Input to DraftCR Adding Signalling Based Activation for NR | Ericsson | other | Yes |
Yes
| revised | No | S5‑222757 | ||||
S5‑222757 | Input to DraftCR Adding Signalling Based Activation for NR | Ericsson | other | - | Yes |
Yes
| noted | No | S5‑222508 | |||
S5‑222509 | Input to DraftCR Handling of QoE measurement collection at handover in NR | Ericsson | other | Yes |
Yes
| noted | No | |||||
S5‑222512 | Input to DraftCR Adding QMC job | Ericsson | other | Yes |
Yes
| noted | No | |||||
S5‑222540 | Rel-17 Input to draft CR 28.623 Add QMC job, stage 3 (YANG) | Ericsson LM | other | Approval | Yes |
Yes
| noted | No | ||||
S5‑222758 | LS out to CT4 Adding attribute qoETarget | Ericsson | LS out | Approval | Yes |
Yes
| noted | No | ||||
6.6.2 | Management data collection control and discovery | S5‑222097 | Rel-17 InputToDraftCR 28.537 Targeted management data collection | Samsung R&D Institute India | other | Agreement | Yes |
Yes
| merged | No | S5‑222759 | |
S5‑222101 | Rel-17 InputToDraftCR 28.622 ManagementDataSubscription | Samsung, Ericsson | other | Agreement | Yes |
Yes
| revised | No | S5‑222633 | |||
S5‑222633 | Rel-17 InputToDraftCR 28.622 ManagementDataSubscription | Samsung, Ericsson | other | Agreement | Yes |
Yes
| approved | No | S5‑222101 | |||
S5‑222171 | Rel-17 Input to DraftCR 28.622 Add data discovery NRM fragment | Nokia, Nokia Shanghai Bell | other | Approval | Yes |
Yes
| noted | No | ||||
S5‑222172 | Rel-17 CR 28.623 Add data discovery NRM fragment (OpenAPI definition) | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑222199 | Rel-17 draftCR 28.537 Add requirements for data management | Nokia, Nokia Shanghai Bell, Samsung | draftCR | Approval | Yes |
Yes
| revised | No | S5‑222759 | |||
S5‑222759 | Rel-17 draftCR 28.537 Add requirements for data management | Nokia, Nokia Shanghai Bell, Samsung | draftCR | Approval | Yes |
Yes
| approved | No | S5‑222199 | |||
S5‑222200 | Rel-17 draftCR 28.622 Add data collection job to allow consumers without detailed knowledge of the network to request for data (stage 2) | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑222201 | Rel-17 draftCR 28.623 Add data collection job to allow consumers without detailed knowledge of the network to request for data (stage 3) | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑222208 | Rel-17 draftCR 32.422 Add metric identifier for trace metrics | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| revised | No | S5‑222635 | |||
S5‑222635 | Rel-17 draftCR 32.422 Add metric identifier for trace metrics | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| approved | No | S5‑222208 | |||
S5‑222643 | DraftCR for MADCOL TS 28.622 | Nokia | draftCR | Approval | No |
Yes
| approved | No | ||||
S5‑222644 | DraftCR for MADCOL TS 28.623 | Samsung | draftCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑222753 | DraftCR for MADCOL TS 28.537 | Nokia | draftCR | Approval | No |
Yes
| withdrawn | Yes | ||||
6.6.3 | Intent driven management service for mobile networks | S5‑222030 | pCR TS 28.312 Add verbalization of expectation to intent Model | Nokia | pCR | Approval | Yes |
Yes
| revised | No | S5‑222681 | |
S5‑222681 | pCR TS 28.312 Add verbalization of expectation to intent Model | Nokia | pCR | Approval | No |
Yes
| approved | No | S5‑222030 | |||
S5‑222031 | pCR TS 28.312 Update intent fulfillment tracking in information model | Nokia | pCR | Approval | Yes |
Yes
| revised | No | S5‑222682 | S5‑221238 | ||
S5‑222682 | pCR TS 28.312 Update intent fulfillment tracking in information model | Nokia | pCR | Approval | No |
Yes
| approved | No | S5‑222031 | |||
S5‑222032 | pCR TS 28.312 Add requirements for intent conflict information | Nokia | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑222130 | pCR 28.312 Update procedures for intent management | China Mobile | pCR | Approval | Yes |
Yes
| revised | No | S5‑222683 | |||
S5‑222683 | pCR 28.312 Update procedures for intent management | China Mobile | pCR | Approval | Yes |
Yes
| approved | No | S5‑222130 | |||
S5‑222258 | pCR TS 28.312 Address the Editor's Notes issues | Huawei,Nokia, Deutsche Telekom | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑222259 | pCR TS 28.312 Move clause 6.4 scenario specific IntentExpectationto 6.2 | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑222684 | |||
S5‑222684 | pCR TS 28.312 Move clause 6.4 scenario specific IntentExpectationto 6.2 | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑222259 | |||
S5‑222260 | pCR TS 28.312 Update clause 7 stage3 to align with clause 2 stage2 | Huawei,Deutsche Telekom | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑222261 | Rel-17draft CR TS 28.532 Update provMnS yaml file to include the resources-intentNrm | Huawei,Deutsche Telekom | draftCR | Approval | Yes |
Yes
| revised | No | S5‑222685 | |||
S5‑222685 | Rel-17draft CR TS 28.532 Update provMnS yaml file to include the resources-intentNrm | Huawei,Deutsche Telekom | draftCR | Approval | Yes |
Yes
| approved | No | S5‑222261 | |||
S5‑222262 | pCR TS 28.312 Rapporteur clean up | Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑222263 | Presentation sheet of TS 28.312 for SA Information and Approval | Huawei | TS or TR cover | Approval | Yes |
Yes
| approved | No | ||||
S5‑222316 | pCR TS 28.312 Update the clause 4.2.2 | China Mobile Com. Corporation | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑222543 | Rel-17 pCR TS 28.312 Update intent information model | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑222638 | |||
S5‑222638 | Rel-17 pCR TS 28.312 Update intent information model | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑222543 | |||
S5‑222748 | draft TS 28.312 | Huawei | draft TR | Approval | Yes |
Yes
| approved | No | ||||
6.6.4 | Enhanced Closed loop SLS Assurance | S5‑222522 | Rel-17 draftCR TS 28.536 Closed loop assurance stage 2 and 3 | Ericsson GmbH, Eurolab | draftCR | Approval | Yes |
Yes
| approved | No | ||
S5‑222523 | Rel-17 Input to draftCR TS 28.536 Clean-up abbreviations and references | Ericsson GmbH, Eurolab | other | Approval | Yes |
Yes
| approved | No | ||||
S5‑222524 | Rel-17 Input to draftCR TS 28.535 Clean-up use cases and requirements | Ericsson GmbH, Eurolab, Deutsche Telekom | other | Approval | Yes |
Yes
| revised | No | S5‑222686 | |||
S5‑222686 | Rel-17 Input to draftCR TS 28.535 Clean-up use cases and requirements | Ericsson GmbH, Eurolab, Deutsche Telekom | other | Approval | Yes |
Yes
| approved | No | S5‑222524 | |||
S5‑222525 | Input to draftCR TS 28.535 Remove use cases and requirements without solution | Ericsson GmbH, Eurolab, Deutsche Telekom | other | Approval | Yes |
Yes
| revised | No | S5‑222687 | |||
S5‑222687 | Input to draftCR TS 28.535 Remove use cases and requirements without solution | Ericsson GmbH, Eurolab, Deutsche Telekom | other | Approval | Yes |
Yes
| approved | No | S5‑222525 | |||
S5‑222751 | DraftCR for eCOSLA - TS 28.535 | Ericsson | draftCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑222752 | DraftCR for eCOSLA - TS 28.536 | Ericsson | draftCR | Approval | Yes |
Yes
| approved | No | ||||
6.6.5 | Enhancements of Management Data Analytics Service | S5‑222033 | pCR 28.105 Add requirements for AI/ML selection | Nokia Germany | pCR | Approval | Yes |
Yes
| revised | No | S5‑222688 | |
S5‑222688 | pCR 28.105 Add requirements for AI/ML selection | Nokia Germany | pCR | Approval | No |
Yes
| approved | No | S5‑222033 | |||
S5‑222034 | pCR 28.105 Add requirements for control of AI/ML Training | Nokia Germany | pCR | Approval | Yes |
Yes
| revised | No | S5‑222689 | |||
S5‑222689 | pCR 28.105 Add requirements for control of AI/ML Training | Nokia Germany | pCR | Approval | No |
Yes
| approved | No | S5‑222034 | |||
S5‑222035 | pCR 28.105 Add NRM fragments for AI/ML Training | Nokia Germany | pCR | Approval | Yes |
Yes
| revised | No | S5‑222690 | |||
S5‑222690 | pCR 28.105 Add NRM fragments for AI/ML Training | Nokia Germany | pCR | Approval | No |
Yes
| approved | No | S5‑222035 | |||
S5‑222036 | pCR 28.105 Support for Training of ML-based functions | Nokia Germany | pCR | Approval | Yes |
Yes
| revised | No | S5‑222691 | |||
S5‑222691 | pCR 28.105 Support for Training of ML-based functions | Nokia Germany | pCR | Approval | No |
Yes
| approved | No | S5‑222036 | |||
S5‑222037 | pCR 28.104 Extend requirements for coverage Analytics | Nokia Germany | pCR | Approval | Yes |
Yes
| revised | No | S5‑222692 | |||
S5‑222692 | pCR 28.104 Extend requirements for coverage Analytics | Nokia Germany | pCR | Approval | No |
Yes
| approved | No | S5‑222037 | |||
S5‑222089 | pCR 28.104 Critical Maintenance Management | Samsung R&D Institute India | pCR | Agreement | Yes |
Yes
| revised | No | S5‑222693 | |||
S5‑222693 | pCR 28.104 Critical Maintenance Management | Samsung R&D Institute India | pCR | Agreement | Yes |
Yes
| approved | No | S5‑222089 | |||
S5‑222090 | pCR 28.104 Handover Optimization | Samsung R&D Institute India | pCR | Agreement | Yes |
Yes
| noted | No | ||||
S5‑222091 | pCR 28.104 Network Slice Traffic Prediction | Samsung R&D Institute India | pCR | Agreement | Yes |
Yes
| revised | No | S5‑222695 | |||
S5‑222695 | pCR 28.104 Network Slice Traffic Prediction | Samsung R&D Institute India | pCR | Agreement | Yes |
Yes
| approved | No | S5‑222091 | |||
S5‑222093 | pCR 28.104 Paging Optimization | Samsung R&D Institute India | pCR | Agreement | Yes |
Yes
| noted | No | ||||
S5‑222105 | Rel-17 pCR 28.104 correct the referred clauses | HUAWEI | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑222180 | pCR 28.105 Add AI-ML background | Intel, NEC | pCR | Approval | Yes |
Yes
| revised | No | S5‑222696 | |||
S5‑222696 | pCR 28.105 Add AI-ML background | Intel, NEC | pCR | Approval | Yes |
Yes
| approved | No | S5‑222180 | |||
S5‑222181 | pCR 28.105 Enhance NRMs for AI-ML model training | Intel, NEC | pCR | Approval | Yes |
Yes
| merged | No | S5‑222690 | |||
S5‑222182 | pCR 28.104 Add common information elements of analytics outputs | Intel, NEC, China Telecom, HUAWEI | pCR | Approval | Yes |
Yes
| revised | No | S5‑222697 | |||
S5‑222697 | pCR 28.104 Add common information elements of analytics outputs | Intel, NEC, China Telecom, HUAWEI, Nokia | pCR | Approval | Yes |
Yes
| approved | No | S5‑222182 | |||
S5‑222183 | pCR 28.104 Add data type definitions | Intel | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑222184 | pCR 28.104 Update NRM for MDA request | Intel | pCR | Approval | Yes |
Yes
| revised | No | S5‑222698 | |||
S5‑222698 | pCR 28.104 Update NRM for MDA request | Intel, Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑222184 | |||
S5‑222185 | Draft CR Rel-17 28.552 Enhance UE Context Release measurements for MDA | Intel | draftCR | Agreement | Yes |
Yes
| revised | No | S5‑222700 | |||
S5‑222700 | Draft CR Rel-17 28.552 Enhance UE Context Release measurements for MDA | Intel | draftCR | Agreement | Yes |
Yes
| approved | No | S5‑222185 | |||
S5‑222288 | Rel-17 draftCR 28.552 Mean number of DRBs undergoing from User Plane Path Failures | Samsung R&D Institute India | draftCR | Agreement | Yes |
Yes
| revised | No | S5‑222694 | |||
S5‑222694 | Rel-17 draftCR 28.552 Mean number of DRBs undergoing from User Plane Path Failures | Samsung R&D Institute India | draftCR | Agreement | Yes |
Yes
| approved | No | S5‑222288 | |||
S5‑222332 | pCR 28.104 Clarify MDA interactions | Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑222333 | pCR 28.104 Prediction of service failures | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑222701 | |||
S5‑222701 | pCR 28.104 Prediction of service failures | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑222333 | |||
S5‑222334 | pCR 28.104 Remove conflicting text regarding MDA context | Huawei | pCR | Approval | Yes |
Yes
| merged | No | S5‑222703 | |||
S5‑222335 | pCR TS 28.104 Add Alarm analytics solution-stage 2 | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑222704 | |||
S5‑222704 | pCR TS 28.104 Add Alarm analytics solution-stage 2 | Huawei | pCR | Approval | Yes |
Yes
| noted | No | S5‑222335 | |||
S5‑222336 | pCR 28.104 Add stage 2 description of failure predication analytics | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑222702 | |||
S5‑222702 | pCR 28.104 Add stage 2 description of failure predication analytics | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑222336 | |||
S5‑222352 | Add an enumeration value in output for “Network slice throughput analysis” Usecase | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑222355 | Enhance the description of the requirement of network slice thourhgout analysis | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑222357 | Multiplicity change for “Affected Objects” IE in “E2E latency analysis” Usecase | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑222705 | |||
S5‑222705 | Multiplicity change for “Affected Objects” IE in “E2E latency analysis” Usecase | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑222357 | |||
S5‑222360 | Multiplicity change for “Affected Objects” IE in “NW slice load analysis” Usecase | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑222706 | |||
S5‑222706 | Multiplicity change for “Affected Objects” IE in “NW slice load analysis” Usecase | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑222360 | |||
S5‑222361 | Multiplicity change for “Affected Objects” IE in “Service experience analysis” Usecase | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑222707 | |||
S5‑222707 | Multiplicity change for “Affected Objects” IE in “Service experience analysis” Usecase | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑222361 | |||
S5‑222362 | Modify the paging requirements based on geographical area | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑222708 | |||
S5‑222708 | Modify the paging requirements based on geographical area | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑222362 | |||
S5‑222364 | Update the analytics output of coverage analysis usecase | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑222376 | pCR 28.104 Add alarm analysis use case | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑222377 | pCR 28.104 Add general requirements | China Mobile | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑222378 | pCR 28.104 add inter-gNB beam selection optimization solution | China Mobile | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑222379 | pCR 28.104 Add MDA capability for MDA assisted energy saving analysis | China Mobile | pCR | Approval | Yes |
Yes
| revised | No | S5‑222709 | |||
S5‑222709 | pCR 28.104 Add MDA capability for MDA assisted energy saving analysis | China Mobile | pCR | Approval | Yes |
Yes
| approved | No | S5‑222379 | |||
S5‑222459 | Rel-17 pCR 28.104 Add MDA capability for handover optimization | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑222460 | Rel-17 pCR 28.104 Update use case description for MDA assisted energy saving analysis | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑222710 | |||
S5‑222710 | Rel-17 pCR 28.104 Update use case description for MDA assisted energy saving analysis | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑222460 | |||
S5‑222461 | Rel-17 pCR TS 28.104 add MDA related service components | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑222711 | |||
S5‑222711 | Rel-17 pCR TS 28.104 add MDA related service components | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑222461 | |||
S5‑222462 | Rel-17 pCR TS 28.104 add mobility performance analysis solution | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑222712 | |||
S5‑222712 | Rel-17 pCR TS 28.104 add mobility performance analysis solution | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑222462 | |||
S5‑222463 | Rel-17 pCR TS 28.104 MDARequest IOC NRM correction | Huawei | pCR | Approval | Yes |
Yes
| merged | No | S5‑222698 | |||
S5‑222474 | pCR 28.104 Define the data type of statistics of cells energy saving state | China Telecom Corporation Ltd. | pCR | Approval | Yes |
Yes
| revised | No | S5‑222641 | |||
S5‑222641 | pCR 28.104 Define the data type of statistics of cells energy saving state | China Telecom Corporation Ltd. | pCR | Approval | Yes |
Yes
| approved | No | S5‑222474 | |||
S5‑222478 | pCR draft TS28.104, Rapporteur clean-up | NEC, Intel | pCR | Approval | Yes |
Yes
| revised | No | S5‑222713 | |||
S5‑222713 | pCR draft TS28.104, Rapporteur clean-up | NEC, Intel | pCR | Approval | Yes |
Yes
| approved | No | S5‑222478 | |||
S5‑222479 | Editorial, enhancements and modifications on MDA overview | Nokia Germany | pCR | Approval | Yes |
Yes
| revised | No | S5‑222714 | |||
S5‑222714 | Editorial, enhancements and modifications on MDA overview | Nokia Germany | pCR | Approval | Yes |
Yes
| approved | No | S5‑222479 | |||
S5‑222480 | Editorial modifications on MDA functionality and service framework | Nokia Germany | pCR | Approval | Yes |
Yes
| revised | No | S5‑222715 | |||
S5‑222715 | Editorial modifications on MDA functionality and service framework | Nokia Germany | pCR | Approval | Yes |
Yes
| approved | No | S5‑222480 | |||
S5‑222481 | pCR draft TS28.104, add historical data handling for MDA | NEC, Intel | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑222482 | pCR draft TS28.104, clarifications on MDA Types | NEC, Intel | pCR | Approval | Yes |
Yes
| revised | No | S5‑222716 | |||
S5‑222716 | pCR draft TS28.104, clarifications on MDA Types | NEC, Intel | pCR | Approval | Yes |
Yes
| approved | No | S5‑222482 | |||
S5‑222483 | Adding domain observation data as input in cross-domain MDA | Nokia Germany | pCR | Approval | Yes |
Yes
| revised | No | S5‑222717 | |||
S5‑222717 | Adding domain observation data as input in cross-domain MDA | Nokia Germany | pCR | Approval | Yes |
Yes
| approved | No | S5‑222483 | |||
S5‑222484 | pCR draft TS28.104, clarifications on MDA Context | NEC, Intel | pCR | Approval | Yes |
Yes
| revised | No | S5‑222703 | |||
S5‑222703 | pCR draft TS28.104, clarifications on MDA Context | NEC, Intel | pCR | Approval | Yes |
Yes
| approved | No | S5‑222484 | |||
S5‑222485 | Additions in MDA types and in enabling data | Nokia Germany | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑222486 | Additions of common information elements of MDA outputs | Nokia Germany | pCR | Approval | Yes |
Yes
| merged | No | S5‑222697 | |||
S5‑222493 | PM-based and KPI-based analytics outputs | Nokia Germany | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑222494 | Enhancing MDA type related to MDA capabilities | Nokia Germany | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑222496 | Enhancing MDA request IOC | Nokia Germany | pCR | Approval | Yes |
Yes
| revised | No | S5‑222699 | |||
S5‑222699 | Enhancing MDA request IOC | Nokia Germany | pCR | Approval | Yes |
Yes
| approved | No | S5‑222496 | |||
S5‑222497 | Adding MDA output IOC | Nokia Germany | pCR | Approval | Yes |
Yes
| revised | No | S5‑222639 | |||
S5‑222639 | Adding MDA output IOC | Nokia Germany | pCR | Approval | Yes |
Yes
| noted | No | S5‑222497 | |||
S5‑222498 | Removing recommendations options | Nokia Germany | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑222500 | Problems in MDA output data | Nokia Germany | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑222749 | draft TS 28.104 | Intel | draft TS | Approval | No |
Yes
| approved | No | ||||
S5‑222750 | draft TS 28.105 | Intel | draft TS | Approval | Yes |
Yes
| approved | No | ||||
6.6.6 | Edge Computing Management | S5‑222044 | [Draft CR] Rel-17 28.538 Add the concept for edge computing management | Intel Korea, Samsung | draftCR | Approval | Yes |
Yes
| revised | No | S5‑222718 | |
S5‑222718 | [Draft CR] Rel-17 28.538 Add the concept for edge computing management | Intel Korea, Ltd. | draftCR | Approval | Yes |
Yes
| approved | No | S5‑222044 | |||
S5‑222045 | [Draft CR] Rel-17 28.538 Add notification to ECM IOCs | Intel Korea, Ltd. | draftCR | Approval | Yes |
Yes
| merged | No | S5‑222720 | |||
S5‑222046 | [Draft CR] Rel-17 28.538 Add the missing procedure not implemented from approved pCR | Intel Korea, Ltd. | draftCR | Approval | Yes |
Yes
| revised | No | S5‑222754 | |||
S5‑222754 | [Draft CR] Rel-17 28.538 Add the missing procedure not implemented from approved pCR | Intel Korea, Ltd. | draftCR | Approval | Yes |
Yes
| approved | No | S5‑222046 | |||
S5‑222282 | Rel-17 draftCR 28.538 Concept and Overview | Samsung R&D Institute India | draftCR | Yes |
Yes
| merged | No | S5‑222718 | ||||
S5‑222284 | Rel-17 draftCR 28.538 Resolving ED | Samsung R&D Institute India | draftCR | Agreement | Yes |
Yes
| revised | No | S5‑222719 | |||
S5‑222719 | Rel-17 draftCR 28.538 Resolving ED | Samsung R&D Institute India | draftCR | Agreement | Yes |
Yes
| approved | No | S5‑222284 | |||
S5‑222642 | DraftCR for eECM – TS 28.538 | Samsung | draftCR | Approval | Yes |
Yes
| approved | No | ||||
6.6.7 | Access control for management service | S5‑222054 | Rel-17 28.622 enhance NRM to support access control | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| noted | No | ||
S5‑222055 | TS32.158 enhance OpenAPI to support access control | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑222056 | Rel-17 TS28.623 enhance NRM to support access control Stage 3 | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑222057 | TS28.533 enhancement to support access control | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| noted | No | ||||
6.6.8 | Network slice provisioning enhancement | S5‑222245 | Rel-17 draftCR TS 28.541 Add feasibility check NRM fragment | Huawei,China Unicom, Deutsche Telekom,China Mobile | draftCR | Approval | Yes |
Yes
| revised | No | S5‑222724 | S5‑221150 |
S5‑222724 | Rel-17 draftCR TS 28.541 Add feasibility check NRM fragment | Huawei,China Unicom, Deutsche Telekom,China Mobile | draftCR | Approval | Yes |
Yes
| approved | No | S5‑222245 | |||
S5‑222246 | Rel-17 draftCR TS 28.531 Update procedure of reservation and checking feasibility of network slice subnet | Huawei,China Unicom,Deutsche Telekom,China Mobile | draftCR | Approval | Yes |
Yes
| revised | No | S5‑222721 | S5‑221151 | ||
S5‑222721 | Rel-17 draftCR TS 28.531 Update procedure of reservation and checking feasibility of network slice subnet | Huawei,China Unicom,Deutsche Telekom,China Mobile | draftCR | Approval | Yes |
Yes
| approved | No | S5‑222246 | |||
S5‑222277 | Rel-17 draftCR 28.531 Deleting capacity planning use case | Samsung R&D Institute India | draftCR | Agreement | Yes |
Yes
| approved | No | ||||
S5‑222278 | Rel-17 draftCR 28.531 Deleting CreateMOI for Network Slice provisioning MnS | Samsung R&D Institute India | draftCR | Agreement | Yes |
Yes
| noted | No | ||||
S5‑222279 | Rel-17 draftCR 28.531 Deleting network slice capability exposure | Samsung R&D Institute India | draftCR | Agreement | Yes |
Yes
| revised | No | S5‑222722 | |||
S5‑222722 | Rel-17 draftCR 28.531 Deleting network slice capability exposure | Samsung R&D Institute India | draftCR | Agreement | Yes |
Yes
| approved | No | S5‑222279 | |||
S5‑222280 | Rel-17 draftCR 28.531 Deleting service priority | Samsung R&D Institute India | draftCR | Agreement | Yes |
Yes
| noted | No | ||||
S5‑222281 | Rel-17 draftCR 28.531 Update procedures and operations to support asynchronous mode of operation | Samsung R&D Institute India | draftCR | Agreement | Yes |
Yes
| noted | No | ||||
S5‑222283 | Rel-17 draftCR 28.538 Notifications | Samsung R&D Institute India | draftCR | Yes |
Yes
| revised | No | S5‑222720 | ||||
S5‑222720 | Rel-17 draftCR 28.538 Notifications | Samsung R&D Institute India | draftCR | - | Yes |
Yes
| approved | No | S5‑222283 | |||
S5‑222287 | Rel-17 draftCR 28.541 adding processMonitor in NetworkSlice and NetworkSliceSubnet | Samsung R&D Institute India | draftCR | Agreement | Yes |
Yes
| noted | No | ||||
S5‑222298 | Rel-17 draftCR 28.541 Network slice subnet capability IOC | Samsung, Nokia | draftCR | Agreement | Yes |
Yes
| noted | No | ||||
S5‑222304 | Rel-17 draftCR 28.531 Network slice subnet capabilities | Samsung R&D Institute India | draftCR | Agreement | Yes |
Yes
| noted | No | ||||
S5‑222398 | Rel-17 CR TS 28.531 Update procedure of reservation and checking feasibility of network slice subnet | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| revised | No | S5‑222640 | |||
S5‑222640 | Rel-17 CR TS 28.531 Update procedure of reservation and checking feasibility of network slice subnet | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| approved | No | S5‑222398 | |||
S5‑222400 | Rel-17 TS 28.541 Add Reservation NRM fragment | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| merged | No | S5‑222724 | |||
S5‑222456 | Discussion paper on correction to multiplicity of relation between NetworkSlice IOC and NetworkSliceSubnet IOC | Nokia, Nokia Shanghai Bell | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑222471 | Rel-16 CR TS 28.541 Correction to multiplicity of relation between NetworkSlice IOC and NetworkSliceSubnet IOC | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑222472 | Rel-17 CR TS 28.541 Correction to multiplicity of relation between NetworkSlice IOC and NetworkSliceSubnet IOC | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑222473 | Rel-17 CR TS 28.531 Remove Use cases and Procedures for AllocateNSI and DeallocateNSI | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑222531 | Discussion paper on asynchronous provisioning procedures for network slicing | Ericsson GmbH, Eurolab | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑222533 | Rel-17 Input to DraftCR 28.541 Add Job IOCs for asynchronous network slicing provisioning procedures | Ericsson GmbH, Eurolab | other | Approval | Yes |
Yes
| noted | No | ||||
S5‑222534 | Rel-17 Input to DraftCR 28.531 Add asynchronous network slicing provisioning procedures | Ericsson GmbH, Eurolab | other | Approval | Yes |
Yes
| noted | No | ||||
7.1 | Charging Plenary | S5‑222008 | CH agenda and time plan | WG vice Chair (Matrixx) | agenda | Yes |
Yes
| revised | No | S5‑222760 | ||
S5‑222760 | CH agenda and time plan | WG vice Chair (Matrixx) | agenda | - | Yes |
Yes
| noted | No | S5‑222008 | |||
S5‑222009 | Charging exec report | WG vice Chair (Matrixx) | report | Yes |
Yes
| noted | No | |||||
S5‑222138 | LS ccSA5 on Traffic usage reporting on 5MBS service | C4-221443 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑222139 | Reply LS on Enhancement on Charging Identifier Uniqueness Mechanism | C4-221440 | LS in | Yes |
Yes
| noted | No | |||||
S5‑222431 | Reply to LS on Traffic usage reporting on 5MBS service | Ericsson LM | LS out | Approval | Yes |
Yes
| revised | No | S5‑222812 | |||
S5‑222812 | Reply to LS on Traffic usage reporting on 5MBS service | Ericsson LM | LS out | Approval | Yes |
Yes
| approved | No | S5‑222431 | |||
7.2 | New Charging Work Item proposals | S5‑222432 | New WID MMS Charging in 5G System Architecture | Ericsson LM | WID new | Agreement | Yes |
Yes
| revised | No | S5‑222789 | |
S5‑222789 | New WID MMS Charging in 5G System Architecture | Ericsson LM | WID new | Agreement | Yes |
Yes
| agreed | No | S5‑222432 | |||
7.3 | Charging Maintenance and Rel-17 small Enhancements | S5‑222015 | Rel-17 pCR 32.290 CHF Set Concept and Retry Handling | Nokia | CR | No |
Yes
| withdrawn | Yes | |||
S5‑222021 | pCR 32.290 CHF Set Concept and Retry Handling | Nokia | draftCR | Yes |
Yes
| noted | No | |||||
S5‑222365 | Rel-15 CR 32.274 Add descriptions for SMS Charging information | China Mobile E-Commerce Co. | CR | Approval | Yes |
Yes
| revised | No | S5‑222794 | |||
S5‑222794 | Rel-15 CR 32.274 Add descriptions for SMS Charging information | China Mobile E-Commerce Co. | CR | Approval | Yes |
Yes
| agreed | No | S5‑222365 | |||
S5‑222366 | Rel-16 CR 32.274 Add descriptions for SMS Charging information | China Mobile E-Commerce Co. | CR | Approval | Yes |
Yes
| revised | No | S5‑222795 | |||
S5‑222795 | Rel-16 CR 32.274 Add descriptions for SMS Charging information | China Mobile E-Commerce Co. | CR | Approval | Yes |
Yes
| agreed | No | S5‑222366 | |||
S5‑222367 | Rel-17 CR 32.274 Add descriptions for SMS Charging information | China Mobile E-Commerce Co. | CR | Approval | Yes |
Yes
| revised | No | S5‑222796 | |||
S5‑222796 | Rel-17 CR 32.274 Add descriptions for SMS Charging information | China Mobile E-Commerce Co. | CR | Approval | Yes |
Yes
| agreed | No | S5‑222367 | |||
S5‑222403 | Rel-16 CR 32.255 Correction on the Charging Identifier Uniqueness | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑222404 | Rel-17 CR 32.255 Correction on the Charging Identifier Uniqueness | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑222405 | Rel-16 CR 32.291 Correction on the Charging Identifier Uniqueness | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑222406 | Rel-17 CR 32.291 Correction on the Charging Identifier Uniqueness | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑222407 | Rel-16 CR 32.298 Correction on the Charging Identifier Uniqueness | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑222408 | Rel-17 CR 32.298 Correction on the Charging Identifier Uniqueness | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑222409 | Rel-17 CR 32.291 Correct the 307 and 308 Http Status Code | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑222410 | Rel-17 CR 32.291 Correct the resource operation to support 307 and 308 | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑222411 | Rel-16 CR 32.254 Correction on the NEF API Charging information | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑222805 | |||
S5‑222805 | Rel-16 CR 32.254 Correction on the NEF API Charging information | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑222411 | |||
S5‑222412 | Rel-17 CR 32.254 Correction on the NEF API Charging information | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑222806 | |||
S5‑222806 | Rel-17 CR 32.254 Correction on the NEF API Charging information | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑222412 | |||
S5‑222413 | Rel-16 CR 32.291 Correction on the identifiers for NEF API Charging information | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑222801 | |||
S5‑222801 | Rel-16 CR 32.291 Correction on the identifiers for NEF API Charging information | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑222413 | |||
S5‑222414 | Rel-17 CR 32.291 Correction on the identifiers for NEF API Charging information | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑222802 | |||
S5‑222802 | Rel-17 CR 32.291 Correction on the identifiers for NEF API Charging information | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑222414 | |||
S5‑222415 | Rel-16 CR 32.298 Correction on the identifiers for NEF API Charging information | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑222803 | |||
S5‑222803 | Rel-16 CR 32.298 Correction on the identifiers for NEF API Charging information | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑222415 | |||
S5‑222416 | Rel-17 CR 32.298 Correction on the identifiers for NEF API Charging information | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑222804 | |||
S5‑222804 | Rel-17 CR 32.298 Correction on the identifiers for NEF API Charging information | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑222416 | |||
S5‑222417 | Rel-16 CR 32.255 Correction on the Trigger Conditions | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑222418 | Rel-17 CR 32.255 Correction on the Trigger Conditions | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑222419 | Rel-16 CR 32.255 Clarify the trigger type for QBC | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑222420 | Rel-17 CR 32.255 Clarify the trigger type for QBC | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑222433 | Rel-17 CR 32.260 Correcting triggering for PLMN change | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑222434 | Rel-17 CR 32.291 Correcting IMS triggering for PLMN change | Ericsson LM | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑222435 | Rel-17 CR 32.291 Correcting response code 5xx | Ericsson LM | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑222436 | Rel-17 CR 32.256 Correcting support of charging scenarios for roaming | Ericsson LM | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑222437 | Rel-17 CR 32.255 Correcting IMS handling | Ericsson LM | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑222438 | Rel-17 CR 32.274 Correcting session and charging identifiers | Ericsson LM | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑222439 | Rel-17 CR 32.291 Correcting V-SMF as node functionality | Ericsson LM | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑222440 | Rel-17 CR 32.255 Correcting charging termination flow at roaming | Ericsson LM | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑222772 | Rel-17 CR 32.291 Correcting IMS triggering for PLMN change | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑222774 | Rel-17 CR 32.291 Correcting V-SMF as node functionality | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑222775 | Rel-17 CR 32.290 CHF Set Concept and Retry Handling | Nokia | CR | Agreement | Yes |
Yes
| agreed | No | ||||
7.4.1 | Charging aspects of Edge Computing | S5‑222193 | pCR 32.257 Add charging information definition for edge enabling services charging | Intel | pCR | Approval | Yes |
Yes
| revised | No | S5‑222768 | |
S5‑222768 | pCR 32.257 Add charging information definition for edge enabling services charging | Intel | pCR | Approval | Yes |
Yes
| approved | No | S5‑222193 | |||
S5‑222198 | Draft CR Rel-17 32.240 Enhance charging architecture for Edge Computing | Intel | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑222233 | Rel-17 pCR 32.257 Correction on the charging information description | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑222776 | |||
S5‑222776 | Rel-17 pCR 32.257 Correction on the charging information description | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑222233 | |||
S5‑222234 | Rel-17 pCR 32.257 Clarification on the EAS Deployment Charging | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑222777 | |||
S5‑222777 | Rel-17 pCR 32.257 Clarification on the EAS Deployment Charging | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑222234 | |||
S5‑222235 | Rel-17 pCR 32.257 Clarification on the Edge Enabling Infrastructure Resource | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑222778 | |||
S5‑222778 | Rel-17 pCR 32.257 Clarification on the Edge Enabling Infrastructure Resource | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑222235 | |||
S5‑222761 | Draft TS 32.257 | Intel | draft TS | Approval | Yes |
Yes
| approved | No | ||||
S5‑222769 | Rel-17 CR 32.240 Enhance charging architecture for Edge Computing | Intel Sweden AB | CR | Agreement | Yes |
Yes
| agreed | No | ||||
7.4.2 | Charging aspects of Architecture Enhancement for NR Reduced Capability Devices | S5‑222368 | Rel-17 CR 32.256 Add charging requirement for AMF to support NR RedCap | China Mobile E-Commerce Co. | CR | Approval | Yes |
Yes
| revised | No | S5‑222787 | |
S5‑222787 | Rel-17 CR 32.256 Add charging requirement for AMF to support NR RedCap | China Mobile E-Commerce Co. | CR | Approval | Yes |
Yes
| agreed | No | S5‑222368 | |||
S5‑222369 | Rel-17 CR 32.274 Add charging requirement for SMSF to support NR RedCap | China Mobile E-Commerce Co. | CR | Approval | Yes |
Yes
| revised | No | S5‑222788 | |||
S5‑222788 | Rel-17 CR 32.274 Add charging requirement for SMSF to support NR RedCap | China Mobile E-Commerce Co. | CR | Approval | Yes |
Yes
| agreed | No | S5‑222369 | |||
S5‑222370 | Rel-17 DraftCR 32.298 Update RAT Type to support NR RedCap | China Mobile E-Commerce Co. | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑222771 | Rel-17 CR 32.298 Update RAT Type to support NR RedCap | China Mobile | CR | Agreement | Yes |
Yes
| agreed | No | ||||
7.4.3 | Charging aspects of Proximity-based Services in 5GS | S5‑222309 | Update requirement | CATT | CR | Approval | Yes |
Yes
| revised | No | S5‑222770 | |
S5‑222770 | Update requirement | CATT | CR | Approval | Yes |
Yes
| agreed | No | S5‑222309 | |||
S5‑222310 | Adding message flows for 5G ProSe Direct Communication converged charging | CATT | CR | Approval | Yes |
Yes
| revised | No | S5‑222780 | |||
S5‑222780 | Adding message flows for 5G ProSe Direct Communication converged charging | CATT | CR | Approval | Yes |
Yes
| agreed | No | S5‑222310 | |||
S5‑222311 | Introduction of CDR generation and handling for converged charging | CATT | CR | Approval | Yes |
Yes
| revised | No | S5‑222781 | |||
S5‑222781 | Introduction of CDR generation and handling for converged charging | CATT | CR | Approval | Yes |
Yes
| agreed | No | S5‑222311 | |||
S5‑222312 | Introduction of Message content charging | CATT | CR | Approval | Yes |
Yes
| revised | No | S5‑222782 | |||
S5‑222782 | Introduction of Message content charging | CATT | CR | Approval | Yes |
Yes
| agreed | No | S5‑222312 | |||
S5‑222313 | Introduction of 5G ProSe converged charging information | CATT | CR | Approval | Yes |
Yes
| revised | No | S5‑222783 | |||
S5‑222783 | Introduction of 5G ProSe converged charging information | CATT | CR | Approval | Yes |
Yes
| agreed | No | S5‑222313 | |||
S5‑222314 | Introduction of Detailed message format for converged charging | CATT | CR | Approval | Yes |
Yes
| revised | No | S5‑222784 | |||
S5‑222784 | Introduction of Detailed message format for converged charging | CATT | CR | Approval | Yes |
Yes
| agreed | No | S5‑222314 | |||
S5‑222315 | Introduction of clauses on formal description and binding | CATT | CR | Approval | Yes |
Yes
| revised | No | S5‑222785 | |||
S5‑222785 | Introduction of clauses on formal description and binding | CATT | CR | Approval | Yes |
Yes
| agreed | No | S5‑222315 | |||
7.4.4 | Charging Aspects of 5G LAN VN Group | S5‑222227 | Rel-17 CR 32.240 Addition of the architeure for 5G LAN charging | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑222790 | |
S5‑222790 | Rel-17 CR 32.240 Addition of the architeure for 5G LAN charging | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑222227 | |||
S5‑222228 | Rel-17 CR 32.254 Addition of the 5G VN group management Charging Architecture | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑222791 | |||
S5‑222791 | Rel-17 CR 32.254 Addition of the 5G VN group management Charging Architecture | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑222228 | |||
S5‑222229 | Rel-17 CR 32.254 Addition of the 5G VN group management Charging Principles | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑222792 | |||
S5‑222792 | Rel-17 CR 32.254 Addition of the 5G VN group management Charging Principles | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑222229 | |||
S5‑222230 | Rel-17 CR 32.254 Addition of the 5G VN group management Charging Information | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑222793 | |||
S5‑222793 | Rel-17 CR 32.254 Addition of the 5G VN group management Charging Information | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑222230 | |||
S5‑222231 | Rel-17 CR 32.291 Additional charging information for the 5G LAN management | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑222232 | Rel-17 CR 32.298 Additional charging information for the 5G LAN Charging | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑222813 | |||
S5‑222813 | Rel-17 CR 32.298 Additional charging information for the 5G LAN Charging | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑222232 | |||
7.4.5 | Charging enhancements for 5G CIoT | S5‑222242 | Rel-17 CR 32.298 Add charging information in CDR | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑222786 | |
S5‑222786 | Rel-17 CR 32.298 Add charging information in CDR | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑222242 | |||
7.4.6 | 5G Charging for Local breakout roaming of data connectivity | S5‑222027 | CR R17 32.240 Missing section number correction | Vodafone GmbH | CR | Agreement | No |
Yes
| withdrawn | Yes | ||
S5‑222177 | CR R17 32.240 Missing section number correction | Vodafone GmbH | CR | Agreement | Yes |
Yes
| revised | No | S5‑222767 | |||
S5‑222767 | CR R17 32.240 Missing section number correction | Vodafone GmbH | CR | Agreement | Yes |
Yes
| agreed | No | S5‑222177 | |||
S5‑222421 | Rel-17 CR 32.255 Additional charging information for LBO | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑222422 | Rel-17 CR 32.255 Additional the architecture for LBO | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑222811 | |||
S5‑222811 | Rel-17 CR 32.255 Additional the architecture for LBO | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑222422 | |||
S5‑222423 | Rel-17 CR 32.255 Additional converged charging architecture for LBO | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑222766 | |||
S5‑222766 | Rel-17 CR 32.255 Additional converged charging architecture for LBO | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑222423 | |||
S5‑222424 | Rel-17 CR 32.255 Additional charging requirement for LBO | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑222779 | |||
S5‑222779 | Rel-17 CR 32.255 Additional charging requirement for LBO | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑222424 | |||
S5‑222425 | Rel-17 CR 32.255 Clarification on Sponsored data connectivity charging for LBO | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑222807 | |||
S5‑222807 | Rel-17 CR 32.255 Clarification on Sponsored data connectivity charging for LBO | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑222425 | |||
S5‑222426 | Rel-17 CR 32.255 Additional charging message flow for LBO | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑222808 | |||
S5‑222808 | Rel-17 CR 32.255 Additional charging message flow for LBO | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑222426 | |||
S5‑222427 | Rel-17 CR 32.255 Additional charging principles for LBO | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑222809 | |||
S5‑222809 | Rel-17 CR 32.255 Additional charging principles for LBO | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑222427 | |||
S5‑222428 | Rel-17 CR 32.255 Additional charging architecture for MVNO | Huawei | CR | Agreement | Yes |
Yes
| merged | No | S5‑222766 | |||
S5‑222429 | Rel-17 CR 32.255 Additional charging message flow and charging information for MVNO | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑222441 | Rel-17 CR 32.290 Scenarios for interaction with two CHFs | Ericsson LM | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑222442 | Rel-17 CR 32.290 Function for interaction with two CHFs | Ericsson LM | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑222443 | Rel-17 CR 32.290 Error handling for interaction with two CHFs | Ericsson LM | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑222444 | Rel-17 CR 32.255 CHF selection when interaction with two CHFs | Ericsson LM | CR | Agreement | Yes |
Yes
| merged | No | S5‑222809 | |||
S5‑222445 | Rel-17 CR 32.255 FBC and QBC when interaction with two CHFs | Ericsson LM | CR | Agreement | Yes |
Yes
| merged | No | S5‑222809 | |||
S5‑222446 | Rel-17 CR 32.255 Triggers for interacting with two CHFs | Ericsson LM | CR | Agreement | Yes |
Yes
| merged | No | S5‑222809 | |||
7.5.1 | Study on charging aspects for enhancements of Network Slicing Phase 2 | S5‑222014 | Rel-17 pCR 28.826 ServiceID in Charging Data Request | Nokia | pCR | Approval | No |
Yes
| withdrawn | Yes | ||
S5‑222179 | Introduction of a solution for KI#6 | Apple GmbH | pCR | Yes |
Yes
| noted | No | |||||
S5‑222538 | Rel-18 pCR 32,847 Add evaluation for Key issue #7 | MATRIXX Software | pCR | Agreement | Yes |
Yes
| approved | No | ||||
S5‑222762 | Draft TR 32.847 | MATRIXX Software | draft TR | discussion | Yes |
Yes
| approved | No | ||||
7.5.2 | Study on Nchf charging services phase 2 | S5‑222214 | Rel-17 pCR 28.826 ServiceID in Charging Data Request | Nokia | pCR | Yes |
Yes
| noted | No | |||
S5‑222236 | Rel-17 pCR 28.826 Add the solution for NB Enhancement | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑222773 | |||
S5‑222773 | Rel-17 pCR 28.826 Add the solution for NB Enhancement | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑222236 | |||
S5‑222447 | Rel-18 pCR 28.826 Adding service identifier based solution to clause 5.3 | Ericsson LM | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑222448 | Rel-18 pCR 28.826 Adding trigger solutions to clause 5.2 | Ericsson LM | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑222449 | Rel-18 pCR 28.826 Adding new trigger category solution to clause 5.1 | Ericsson LM | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑222450 | Rel-18 pCR 28.826 Adding general clause for documentation | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑222763 | Draft TR 28.826 | Ericsson LM | draft TR | Approval | Yes |
Yes
| approved | No | ||||
7.5.3 | Study on 5G roaming charging architecture for wholesale and retail scenarios | S5‑222194 | Rel-18 pCR 28.827 Add a SMS use case and solution for 7.1 | MATRIXX Software | pCR | Agreement | Yes |
Yes
| revised | No | S5‑222797 | |
S5‑222797 | Rel-18 pCR 28.827 Add a SMS use case and solution for 7.1 | MATRIXX Software | pCR | Agreement | Yes |
Yes
| approved | No | S5‑222194 | |||
S5‑222195 | Rel-18 pCR 28.827 Add a SMS use case Key issues and requirements for 7.2 | MATRIXX Software | pCR | Agreement | Yes |
Yes
| revised | No | S5‑222798 | |||
S5‑222798 | Rel-18 pCR 28.827 Add a SMS use case Key issues and requirements for 7.2 | MATRIXX Software | pCR | Agreement | Yes |
Yes
| approved | No | S5‑222195 | |||
S5‑222196 | Rel-18 pCR 28.827 Add CHF to CHF solution for SMS in 7.2 | MATRIXX Software | pCR | Agreement | Yes |
Yes
| revised | No | S5‑222799 | |||
S5‑222799 | Rel-18 pCR 28.827 Add CHF to CHF solution for SMS in 7.2 | MATRIXX Software | pCR | Agreement | Yes |
Yes
| approved | No | S5‑222196 | |||
S5‑222197 | Rel-18 pCR 28.827 Add CTF to two CHFs solution for SMS in 7.2 | MATRIXX Software | pCR | Agreement | Yes |
Yes
| revised | No | S5‑222800 | |||
S5‑222800 | Rel-18 pCR 28.827 Add CTF to two CHFs solution for SMS in 7.2 | MATRIXX Software | pCR | Agreement | Yes |
Yes
| approved | No | S5‑222197 | |||
S5‑222237 | Rel-17 pCR 28.827 Additional BCE and TAP relationship | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑222810 | |||
S5‑222810 | Rel-17 pCR 28.827 Additional BCE and TAP relationship | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑222237 | |||
S5‑222238 | Rel-17 pCR 28.827 Additional new solutions for Topic 7.6 | Huawei | pCR | Agreement | Yes |
Yes
| noted | No | ||||
S5‑222239 | Rel-17 pCR 28.827 Clarification on the Roaming Charging Profile | Huawei | pCR | Agreement | Yes |
Yes
| noted | No | ||||
S5‑222240 | Rel-17 pCR 28.827 Addition of the solution for the Roaming Charging Profile | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | ||||
S5‑222241 | Rel-17 pCR 28.827 Correction on the solution 1.3 | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | ||||
S5‑222764 | Draft TR 28.827 | Ericsson | draft TR | Approval | Yes |
Yes
| approved | No | ||||
7.5.4 | Study on Charging Aspects for Enhanced support of Non-Public Networks | S5‑222381 | TR 28.828 v0.0.0 Initial skeleton | China Mobile | draft TR | Yes |
Yes
| approved | No | |||
S5‑222392 | Rel-18 pCR 28.828 Add scope | China Mobile | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑222394 | Rel-18 pCR 28.828 Add reference | China Mobile | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑222395 | Rel-18 pCR 28.828 Skeleton update | China Mobile | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑222765 | Draft TR 28.828 | China Mobile | draft TR | Approval | Yes |
Yes
| approved | No | ||||
8 | Any Other Business |   | ||||||||||
9 | Closing of the meeting |   |