Tdoc List
2023-09-06 16:01
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‑235000 | Agenda | WG Chair | agenda | Yes |
Yes
| revised | No | S5‑235737 | ||
S5‑235737 | Agenda | WG Chair | agenda | Yes |
Yes
| approved | No | S5‑235000 | ||||
3 | IPR and legal declaration | S5‑235001 | IPR and legal declaration | WG Chair | other | Yes |
Yes
| noted | No | |||
4 | Meetings and activities reports |   | ||||||||||
4.1 | Last SA5 meeting report | S5‑235002 | Report from last SA5 meeting | MCC | report | Yes |
Yes
| approved | No | |||
4.2 | Inter-organizational reports |   | ||||||||||
5 | SA5 level issues |   | ||||||||||
5.1 | Administrative issues at SA5 level | S5‑235003 | Post e-meeting email approval status | WG Chair | other | Yes |
No
| available | No | |||
S5‑235013 | SA5 working procedures | WG Chair | other | Yes |
Yes
| approved | No | |||||
S5‑235014 | SA5 Meeting facility requirements | WG Chair | other | Yes |
Yes
| noted | No | |||||
S5‑235017 | Process for management of draft TS-TRs | WG Chair | discussion | Yes |
Yes
| noted | No | |||||
S5‑235736 | Using Forge for SA5 | Nokia, Nokia Shanghai Bell | other | Information | Yes |
Yes
| noted | No | S5‑231146 | |||
5.2 | Technical issues at SA5 level | S5‑235536 | Huawei inputs to SA1 Rel-19 UAV topics | Huawei | discussion | Approval | Yes |
YesEricsson was concerned about having only a work item per area. Huawei replied that this was a starting point and discussions could start from there. It may be found later that more than one work item would be needed for a specific area.Nokia added that a technical justification was required to go further.
NEC: the moderator role will take long time in SA5, it is not appropriate for this group.
The Chair replied that this as a strong request from the SA leadership, but it was a guideline that SA5 may not follow (e.g. hard to find 20 volunteers for 20 WIDs).
| noted | No | ||
S5‑235577 | SA5 Collection of Rel-19 potential topics | SA5 Vice chair (Huawei) | Work Plan | Endorsement | Yes |
Yes
| revised | No | S5‑236126 | S5‑234823 | ||
S5‑236126 | SA5 Collection of Rel-19 potential topics | SA5 Vice chair (Huawei) | discussion | Endorsement | Yes |
Yes
| endorsed | No | S5‑235577 | |||
S5‑235690 | Service Management | Ericsson | discussion | Yes |
YesMatrixx: this doesn’t concern the converged charging system at all.
| endorsed | No | |||||
S5‑235769 | LS on documenting code changes in FORGE | Ericsson | LS out | Approval | Yes |
Yes
| approved | No | ||||
5.3 | Liaison statements at SA5 level | S5‑235020 | Reply LS on having OpenAPI changes only in GitLab | C1-234390 | LS in | Yes |
Yes
| noted | No | |||
S5‑235022 | LS on having OpenAPI changes only in GitLab | C3-232461 | LS in | Yes |
Yes
| noted | No | |||||
S5‑235023 | LS on having OpenAPI changes only in GitLab | C4-232464 | LS in | Yes |
Yes
| noted | No | |||||
S5‑235052 | Reply LS on GSMA requirements regarding intermediaries in the roaming ecosystem and related LSs | SP-230763 | LS in | Yes |
Yes
| noted | No | |||||
S5‑235215 | LS on GSMA OPG PRDs publication and document name change | GSMA | LS in | Yes |
Yes
| noted | No | |||||
S5‑235506 | LS on Enhancement on the attribute for 5GLAN management | China Mobile E-Commerce Co. | LS out | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑235507 | Reply LS on OAM input data for QoS Sustainability Analytics | China Mobile E-Commerce Co. | LS out | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑235855 | LS on documenting code in Forge-GitLab | Ericsson | LS out | Approval | Yes |
Yes
| approved | No | ||||
5.4 | SA5 meeting calendar | S5‑235018 | SA5 meeting calendar | WG Chair | other | Yes |
Yes
| noted | No | |||
6 | OAM&P |   | ||||||||||
6.1 | OAM&P Plenary | S5‑235004 | OAM&P action list | WG Vice Chair (Huawei) | other | Yes |
Yes
| noted | No | |||
S5‑235005 | OAM meeting process | WG Chair | other | Yes |
Yes
| noted | No | |||||
S5‑235006 | agenda_with_Tdocs_sequence_proposal_OAM | WG Vice Chair (Huawei) | agenda | Yes |
Yes
| noted | No | |||||
S5‑235007 | OAM Exec Report | WG Vice Chair (Huawei) | report | Yes |
No
| available | No | |||||
S5‑235008 | OAM Chair notes and conclusions | WG Chair | report | Yes |
Yes
| noted | No | |||||
S5‑235011 | Collection of useful endorsed document and external communication documents in OAM | WG Vice Chair (Huawei) | discussion | Yes |
Yes
| noted | No | |||||
S5‑235015 | Collection of Rel-18 3GPP SA5 OAM WoP | WG Vice Chair (Huawei) | discussion | Yes |
Yes
| noted | No | |||||
S5‑235016 | Living document for stage 2-3 alignment | WG Chair | discussion | Yes |
Yes
| noted | No | |||||
S5‑235019 | Time Plan for OAM&P sessions | WG Chair | other | Yes |
Yes
| noted | No | |||||
S5‑235021 | Reply LS on MBS service area update clarification | C3-232410 | LS in | Yes |
Yes
| withdrawn | Yes | |||||
S5‑235024 | Reply LS on 3GPP work on Energy Efficiency | C4-232465 | LS in | Yes |
Yes
| noted | No | |||||
S5‑235025 | LSout to 3GPP SA5 about status of FEAT24 ^VNF-OAM" development by ETSI NFV | ETSI ISG NFV | LS in | Yes |
Yes
| replied to | No | |||||
S5‑235026 | Reply LS on Approval of eQoE CRs for NR | R2-2304401 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑235027 | LS on area scope for QoE measurements | R2-2306569 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑235782 | Reply to: LS on area scope for QoE measurements | Huawei | LS out | approval | Yes |
Yes
| approved | No | ||||
S5‑235028 | LS on the feasibility of introducing assistance information for handling of QoE reporting during RAN overload | R3-232047 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑235029 | LS on NCR Solutions | R3-225253 | LS in | Yes |
Yes
| postponed | No | |||||
S5‑235030 | LS on MDT measurements collection in MR-DC | R3-232070 | LS in | Yes |
Yes
| postponed | No | |||||
S5‑235031 | LS on collecting QoE measurements per MBS service area and MBS session ID | R3-232079 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑235781 | Reply to: LS on collecting QoE measurements per MBS service area and MBS session ID | Huawei | LS out | approval | Yes |
Yes
| approved | No | ||||
S5‑235032 | Response to Reply LS on Support of network slices which have area of service not matching deployed tracking areas | R3-233432 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑235774 | Reply to: Response to Reply LS on Support of network slices which have area of service not matching deployed tracking areas | Huawei | LS out | approval | Yes |
Yes
| approved | No | ||||
S5‑235033 | LS on QoE measurement collection for application sessions delivered via MBS broadcast or multicast | R3-233457 | LS in | Yes |
Yes
| postponed | No | |||||
S5‑235034 | Reply LS on RAN UE Id optionality | R3-233476 | LS in | Yes |
Yes
| postponed | No | |||||
S5‑235035 | LS on Multiple Trace/MDT configurations | R3-233481 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑235036 | LS on AI/ML for NG-RAN Energy Saving Energy Cost index | R3-233515 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑235037 | LS on cell ID (re)configuration for mobile IAB cell | R3-233516 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑235038 | Reply LS on customer acceptance of limited QoS degradation to save energy in the network | S1-231468 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑235039 | Reply LS on Reply LS on DN energy efficiency | S1-231469 | LS in | Yes |
Yes
| noted | No | |||||
S5‑235040 | Reply LS on 3GPP work on Energy Efficiency | S1-231805 | LS in | Yes |
Yes
| noted | No | |||||
S5‑235041 | LS for improved KPIs involving end-to-end data volume transfer time analytics | S2-2304067 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑235043 | LS on OAM input data for QoS Sustainability Analytics | S2-2306095 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑235044 | LS on MDAF discovery mechanisms | S2-2308078 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑235045 | LS to SA5 on NFc registration using OAM | S3-233351 | LS in | Yes |
Yes
| noted | No | |||||
S5‑235046 | LS on 3GPP work on Energy Efficiency | S4-231111 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑235047 | LS to GSMA on publication of GSMA OPG and OPAG documents | S6-232145 | LS in | Yes |
Yes
| noted | No | |||||
S5‑235048 | LS on REl-18 work on architecture for enabling Edge Applications | S6-232197 | LS in | Yes |
Yes
| postponed | No | |||||
S5‑235049 | LS for clarification on EAS instantiation duration time | S6-232198 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑235050 | LS/r on initiation of new work item ITU-T Q.PMEE ""Protocol for managing energy efficiency with AI-assisted analysis in IMT-2020 networks and beyond"" (SG5-LS54) [to ITU-T SG5, SG13, and 3GPP SA5] | ITU-T | LS in | Yes |
Yes
| replied to | No | |||||
S5‑235051 | LS on initiation of draft new Recommendation ITU-T Y.IMT2020-MEVE-req-frame ""Future networks including IMT-2020: requirements and framework for measurement of effectiveness and value evaluation of autonomous networks"" | ITU-T | LS in | Yes |
Yes
| noted | No | |||||
S5‑235053 | ZSM work on AI enablers and intent-driven autonomous networks | ETSI ISG ZSM | LS in | Yes |
Yes
| postponed | No | |||||
S5‑235056 | LSout reply to ITU-T SG13 LSin on the NWI "Requirements and framework on network function enhancements of IMT-2020 networks and beyond from the energy efficiency perspective" | ETSI ISG NFV | LS in | Yes |
Yes
| noted | No | |||||
S5‑235057 | Liaison Statement to 3GPP SA5 | ETSI TC EE | LS in | Yes |
Yes
| postponed | No | |||||
S5‑235109 | LS/r on consideration of a new work item “Requirements and framework of network function enhancements of IMT-2020 networks and beyond from the energy efficiency perspective” (reply to SG13-LS78) | ITU-T | LS in | Yes |
Yes
| noted | No | |||||
S5‑235110 | New WID on network slice management capability exposure | Alibaba Group, AsiaInfo, China Mobile, China Unicom | WID new | Approval | Yes |
Yes
| noted | No | ||||
S5‑235770 | New WID on network slice management capability exposure | Alibaba Group, AsiaInfo, China Mobile, China Unicom | WID new | Agreement | No |
Yes
| withdrawn | Yes | ||||
S5‑235152 | LS reply to LS on Cell ID (re)configuration for mobile IAB cell | Oy LM Ericsson AB | LS out | Approval | Yes |
Yes
| revised | No | S5‑235773 | |||
S5‑235773 | LS reply to LS on Cell ID (re)configuration for mobile IAB cell | Oy LM Ericsson AB | LS out | Approval | Yes |
Yes
| revised | No | S5‑236128 | S5‑235152 | ||
S5‑236128 | LS reply to LS on Cell ID (re)configuration for mobile IAB cell | Oy LM Ericsson AB | LS out | Approval | Yes |
Yes
| approved | No | S5‑235773 | |||
S5‑235342 | LS reply to LSout to 3GPP SA5 about status of FEAT24 “VNF-OAM” development by ETSI NFV | China Mobile Com. Corporation | LS out | Yes |
Yes
| revised | No | S5‑235771 | ||||
S5‑235771 | LS reply to LSout to 3GPP SA5 about status of FEAT24 “VNF-OAM” development by ETSI NFV | China Mobile Com. Corporation | LS out | - | Yes |
Yes
| approved | No | S5‑235342 | |||
S5‑235362 | Reply to LS on initiation of new work item ITU-T Q.PMEE “Protocol for managing energy efficiency with AI-assisted analysis in IMT-2020 networks and beyond” | Huawei | LS out | Approval | Yes |
Yes
| revised | No | S5‑235779 | |||
S5‑235779 | Reply to LS on initiation of new work item ITU-T Q.PMEE “Protocol for managing energy efficiency with AI-assisted analysis in IMT-2020 networks and beyond” | Huawei | LS out | Approval | Yes |
Yes
| approved | No | S5‑235362 | |||
S5‑235363 | Reply to LS on AI/ML for NG-RAN Energy Saving Energy Cost index | Huawei | LS out | Approval | Yes |
Yes
| revised | No | S5‑235777 | |||
S5‑235777 | Reply to LS on AI/ML for NG-RAN Energy Saving Energy Cost index | Huawei | LS out | Approval | Yes |
Yes
| approved | No | S5‑235363 | |||
S5‑235364 | Reply to LS on customer acceptance of limited QoS degradation to save energy in the network | Huawei | LS out | Approval | Yes |
Yes
| approved | No | ||||
S5‑235453 | DP on SA2 LS for improved KPIs involving end-to-end data volume transfer time analytics | Intel, Verizon | discussion | Endorsement | Yes |
Yes
| endorsed | No | ||||
S5‑235454 | Reply LS to SA2 on improved KPIs involving end-to-end data volume transfer time analytics | Intel, Verizon | LS out | Endorsement | Yes |
Yes
| approved | No | ||||
S5‑235501 | Reply LS on Multiple TraceMDT configurations | Nokia, Nokia Shanghai Bell | LS out | Approval | Yes |
Yes
| revised | No | S5‑235775 | |||
S5‑235775 | Reply LS on Multiple TraceMDT configurations | Nokia, Nokia Shanghai Bell | LS out | Approval | Yes |
Yes
| approved | No | S5‑235501 | |||
S5‑235502 | DP on multiple traceMDT configurations during HO | Nokia, Nokia Shanghai Bell | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑235514 | Reply to S6_on_clarification on EAS instantiation duration | Huawei | LS out | Approval | Yes |
Yes
| revised | No | S5‑236121 | |||
S5‑236121 | Reply to S6_on_clarification on EAS instantiation duration | Huawei | LS out | Approval | Yes |
Yes
| revised | No | S5‑236127 | S5‑235514 | ||
S5‑236127 | Reply to S6_on_clarification on EAS instantiation duration | Huawei | LS out | Approval | Yes |
Yes
| approved | No | S5‑236121 | |||
S5‑235542 | Reply LS on the feasibility of introducing assistance information for handling of QoE reporting during RAN overload | Huawei | LS out | Approval | Yes |
Yes
| approved | No | ||||
S5‑235580 | Rel-18 & Rel-19 time plan proposal for OAM | SA5 Vice chair (Huawei),SA5 Chair | discussion | Endorsement | Yes |
Yes
| noted | No | S5‑234062 | |||
S5‑235584 | Reply to LS on 3GPP work on energy efficiency | Huawei | LS out | Approval | Yes |
Yes
| revised | No | S5‑235778 | |||
S5‑235778 | Reply to LS on 3GPP work on energy efficiency | Huawei | LS out | Approval | Yes |
Yes
| approved | No | S5‑235584 | |||
S5‑235672 | LS on Enhancement on the attribute for 5GLAN management | China Mobile E-Commerce Co. | LS out | Approval | Yes |
Yes
| revised | No | S5‑235780 | |||
S5‑235780 | LS on Enhancement on the attribute for 5GLAN management | China Mobile E-Commerce Co. | LS out | Approval | Yes |
Yes
| approved | No | S5‑235672 | |||
S5‑235673 | Reply LS on OAM input data for QoS Sustainability Analytics | China Mobile E-Commerce Co. | LS out | Approval | Yes |
Yes
| revised | No | S5‑235776 | |||
S5‑235776 | Reply LS on OAM input data for QoS Sustainability Analytics | China Mobile E-Commerce Co. | LS out | Approval | Yes |
Yes
| approved | No | S5‑235673 | |||
S5‑235729 | Reply LS MDAF service discovery by NWDAF | NEC, Intel | LS out | Approval | Yes |
Yes
| approved | No | ||||
S5‑235738 | LS on the user consent for trace reporting S3-223162 | S3-234267 | LS in | discussion | Yes |
Yes
| noted | No | ||||
S5‑236129 | Rel-19 topic OAM moderator list | WG Vice Chair (Huawei) | discussion | Information | Yes |
Yes
| noted | No | ||||
6.2 | New OAM&P Work Item proposals |   | ||||||||||
6.2.1 | Intelligence and Automation |   | ||||||||||
6.2.2 | Management Architecture and Mechanisms |   | ||||||||||
6.2.3 | Support of New Services |   | ||||||||||
6.3 | OAM&P Maintenance and Rel-18 small Enhancements |   | ||||||||||
6.3.1 | Methodology | S5‑235055 | Clarifying Terminology | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| revised | No | S5‑236009 | |
S5‑236009 | Rel-18 TS 32.156 Clarifying Terminology | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| not pursued | No | S5‑235055 | |||
S5‑235097 | Rel-15 TS 32.156 Clarifying Terminology | Ericsson-LG Co., LTD | CR | Agreement | Yes |
Yes
| revised | No | S5‑236008 | |||
S5‑236008 | Rel-15 TS 32.156 Clarifying Terminology | Ericsson-LG Co., LTD | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑235097 | |||
S5‑235098 | Rel-16 CR TS 32.156 Clarifying Terminology | Ericsson-LG Co., LTD | CR | Agreement | Yes |
Yes
| revised | No | S5‑236010 | |||
S5‑236010 | Rel-16 CR TS 32.156 Clarifying Terminology | Ericsson-LG Co., LTD | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑235098 | |||
S5‑235099 | Rel-17 CR TS 32.156 Clarifying Terminology | Ericsson-LG Co., LTD | CR | Agreement | Yes |
Yes
| revised | No | S5‑236011 | |||
S5‑236011 | Rel-17 CR TS 32.156 Clarifying Terminology | Ericsson-LG Co., LTD | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑235099 | |||
S5‑235145 | Discussion paper on Using Forge-Git as the primary storage for Code | Ericsson Hungary Ltd | discussion | Endorsement | Yes |
Yes
| endorsed | No | S5‑232751 | |||
S5‑235248 | Add Forge as a potential normative storage for Code | Ericsson Hungary Ltd | draftCR | Approval | Yes |
Yes
| revised | No | S5‑236113 | |||
S5‑236113 | Add Forge as a potential normative storage for Code | Ericsson Hungary Ltd | draftCR | Approval | Yes |
Yes
| approved | No | S5‑235248 | |||
S5‑235378 | Rel-17 CR TS 32.156 Add clarification for attrubute properities | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑235379 | Rel-18 CR TS 32.156 Add clarification for attrubute properities | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑235556 | Rel-18 CR TS 32.156 Supplement the specification for establishing a relationship between dataType and model elements in UML class diagram | China Mobile Com. Corporation | CR | Agreement | Yes |
Yes
| revised | No | S5‑236012 | |||
S5‑236012 | Rel-18 CR TS 32.156 Supplement the specification for establishing a relationship between dataType and model elements in UML class diagram | China Mobile Com. Corporation | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑235556 | |||
S5‑235697 | Add Forge as a potential normative storage for Stage 3 OpenAPI code | Ericsson Hungary Ltd | draftCR | Approval | Yes |
Yes
| revised | No | S5‑236114 | |||
S5‑236114 | Add Forge as a potential normative storage for Stage 3 OpenAPI code | Ericsson Hungary Ltd | draftCR | Approval | Yes |
Yes
| approved | No | S5‑235697 | |||
6.3.2 | ANL |   | ||||||||||
6.3.3 | MDAS | S5‑235205 | Rel-17 CR TS 28.104 Correcting datatype for Energy Saving Recommendation for NRCELL and UPF | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||
S5‑235206 | Rel-18 CR TS 28.104 Correcting datatype for Energy Saving Recommendation for NRCELL and UPF | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
6.3.4 | AI/ML | S5‑235715 | Rel-17 CR TS 28.105 Clarify ML models as proprietary | Ericsson-LG Co., LTD | CR | Agreement | Yes |
Yes
| agreed | No | ||
S5‑235716 | Clarify ML models as proprietary | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑235727 | Restore the wrongly voided clause “5 Service and functional framework” | NEC, Intel | CR | Agreement | Yes |
Yes
| withdrawn | Yes | ||||
6.3.5 | Energy efficiency | S5‑235153 | Rel-16 CR TS 28.310 Update NG-RAN data EE KPI definition with reference to TS 28.554 | Nokia, Nokia Shanghai Bell, Huawei | CR | Approval | Yes |
Yes
| agreed | No | S5‑233887 | |
S5‑235154 | Rel-17 CR TS 28.310 Update NG-RAN data EE KPI definition with reference to TS 28.554 | Nokia, Nokia Shanghai Bell, Huawei | CR | Approval | Yes |
Yes
| agreed | No | S5‑233888 | |||
S5‑235155 | Rel-18 CR TS 28.310 Update NG-RAN data EE KPI definition with reference to TS 28.554 | Nokia, Nokia Shanghai Bell, Huawei | CR | Approval | Yes |
Yes
| agreed | No | S5‑233889 | |||
S5‑235156 | Rel-17 CR TS 28.310 Remove redundant Network Slice EE KPI definition | Nokia, Nokia Shanghai Bell, Huawei | CR | Approval | Yes |
Yes
| agreed | No | S5‑233890 | |||
S5‑235157 | Rel-18 CR TS 28.310 Remove redundant Network Slice EE KPI definition | Nokia, Nokia Shanghai Bell, Huawei | CR | Approval | Yes |
Yes
| agreed | No | S5‑233891 | |||
6.3.6 | Intent driven management | S5‑235116 | Rel-18 CR TS 28.312 Correct use case for delivering a service at the edge | L.M. Ericsson Limited, Deutsche Telekom, Telefonica | CR | Approval | Yes |
Yes
| revised | No | S5‑236014 | |
S5‑236014 | Rel-18 CR TS 28.312 Correct use case for delivering a service at the edge | L.M. Ericsson Limited, Deutsche Telekom, Telefonica | CR | Approval | Yes |
Yes
| agreed | No | S5‑235116 | |||
S5‑235117 | Rel-18 CR TS 28.312 Add missing stage 3 | L.M. Ericsson Limited, Deutsche Telekom, Telefonica | CR | Approval | Yes |
Yes
| revised | No | S5‑236016 | |||
S5‑236015 | Rel-17 CR TS 28.312 Add missing stage 3 | L.M. Ericsson Limited, Deutsche Telekom, Telefonica | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑236016 | Rel-18 CR TS 28.312 Add missing stage 3 | L.M. Ericsson Limited, Deutsche Telekom, Telefonica | CR | Approval | Yes |
Yes
| agreed | No | S5‑235117 | |||
S5‑235372 | Rel-17 CR TS 28.312 Correct issues for generic intent information model | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑236017 | |||
S5‑236017 | Rel-17 CR TS 28.312 Correct issues for generic intent information model | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235372 | |||
S5‑235373 | Rel-18 CR TS 28.312 Correct issues for generic intent information model | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑236018 | |||
S5‑236018 | Rel-18 CR TS 28.312 Correct issues for generic intent information model | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235373 | |||
S5‑235374 | Rel-17 CR TS 28.312 Correct issues for Service Support Expectation | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑236019 | |||
S5‑236019 | Rel-17 CR TS 28.312 Correct issues for Service Support Expectation | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235374 | |||
S5‑235375 | Rel-18 CR TS 28.312 Correct issues for Service Support Expectation | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑235717 | |||
S5‑235376 | Rel-17 CR TS 28.312 Update satge3 to align with stage2 | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑235377 | Rel-18 CR TS 28.312 Update satge3 to align with stage2 | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑235518 | Clarification on intent translate | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑236021 | |||
S5‑236021 | Clarification on intent translate | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235518 | |||
S5‑235519 | Clarification on intent translate | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑236022 | |||
S5‑236022 | Clarification on intent translate | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235519 | |||
S5‑235563 | Rel-17 CR TS 28.312 Correct the errors in Table 6.2.1.4-1 | China Mobile Com. Corporation | CR | Agreement | Yes |
Yes
| revised | No | S5‑236023 | |||
S5‑236023 | Rel-17 CR TS 28.312 Correct the errors in Table 6.2.1.4-1 | China Mobile Com. Corporation | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235563 | |||
S5‑235564 | Rel-17 CR TS 28.312 Correct the Relationship UML diagram for intent | China Mobile Com. Corporation | CR | Agreement | Yes |
Yes
| revised | No | S5‑235834 | |||
S5‑235834 | Rel-17 CR TS 28.312 Correct the Relationship UML diagram for intent | China Mobile Com. Corporation | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑235564 | |||
S5‑235717 | Rel-18 CR TS 28.312 Correct issues for Service Support Expectation | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑236020 | S5‑235375 | ||
S5‑236020 | Rel-18 CR TS 28.312 Correct issues for Service Support Expectation | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235717 | |||
S5‑236013 | Rel-17 CR TS 28.312 Correct use case for delivering a service at the edge of the network | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
6.3.7 | SON | S5‑235540 | Rel-17 CR TS 28.313 correction of performance measurements | Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑236025 | |
S5‑236025 | Rel-17 CR TS 28.313 correction of performance measurements | Huawei | CR | Approval | Yes |
Yes
| not pursued | No | S5‑235540 | |||
S5‑235541 | Rel-16 CR TS 28.313 correction of performance measurements | Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑236024 | |||
S5‑236024 | Rel-16 CR TS 28.313 correction of performance measurements | Huawei | CR | Approval | Yes |
Yes
| not pursued | No | S5‑235541 | |||
6.3.8 | QMC | S5‑235537 | Rel-18 CR TS 28.405 add area scope in QMC | Huawei | CR | Approval | Yes |
Yes
| not pursued | No | ||
S5‑236028 | Rel-18 CR TS 28.405 add area scope in QMC | Huawei | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑235538 | Rel-18 CR TS 28.622 add area scope in QMC | Huawei | CR | Approval | Yes |
Yes
| not pursued | No | S5‑236026 | |||
S5‑236026 | Rel-18 CR TS 28.622 add area scope in QMC | Huawei | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑235539 | Rel-18 CR TS 28.623 add area scope in QMC | Huawei | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑236027 | Rel-18 CR TS 28.623 add area scope in QMC | Huawei | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
6.3.9 | Network slicing management | S5‑235072 | Clarify the role of jitter as attribute in service profile | Ericsson | CR | Approval | Yes |
Yes
| not pursued | No | ||
S5‑235073 | Clarify the role of jitter as attribute in service profile | Ericsson | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑235074 | Clarify the role of jitter as attribute in service profile | L.M. Ericsson Limited | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑235075 | Correct datatype definition of support in service profile | L.M. Ericsson Limited | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑235076 | Correct datatype definition of support in service profile | L.M. Ericsson Limited | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑235077 | Correct datatype definition of support in service profile | L.M. Ericsson Limited | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑235078 | Correct attribute name for indication of v2XCommMode | Ericsson | CR | Approval | Yes |
Yes
| revised | No | S5‑236029 | |||
S5‑236029 | Correct attribute name for indication of v2XCommMode | Ericsson | CR | Approval | Yes |
Yes
| agreed | No | S5‑235078 | |||
S5‑235079 | Correct attribute name for indication of v2XCommMode | Ericsson | CR | Approval | Yes |
Yes
| revised | No | S5‑236030 | |||
S5‑236030 | Correct attribute name for indication of v2XCommMode | Ericsson | CR | Approval | Yes |
Yes
| agreed | No | S5‑235079 | |||
S5‑235080 | Correct definition of data type support in service profile | Ericsson | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑235081 | Correct attribute name for frequency prediction | Ericsson | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑235082 | Correct attribute name for frequency prediction | Ericsson | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑235086 | Discussion paper on GSMA GST to ServiceProfile mapping | L.M. Ericsson Limited, Huawei, Deutsche Telekom | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑235087 | Update Annex L with mapping table | Ericsson, Huawei, Deutsche Telekom | CR | Approval | Yes |
Yes
| revised | No | S5‑236031 | |||
S5‑236031 | Update Annex L with mapping table | Ericsson, Huawei, Deutsche Telekom | CR | Approval | Yes |
Yes
| agreed | No | S5‑235087 | |||
S5‑235088 | Update Annex L with mapping table | Ericsson, Huawei, Deutsche Telekom | CR | Approval | Yes |
Yes
| revised | No | S5‑236032 | |||
S5‑236032 | Update Annex L with mapping table | Ericsson, Huawei, Deutsche Telekom | CR | Approval | Yes |
Yes
| agreed | No | S5‑235088 | |||
S5‑235089 | Update Annex L with mapping table | Ericsson, Huawei, Deutsche Telekom | CR | Yes |
Yes
| revised | No | S5‑236033 | ||||
S5‑236033 | Update Annex L with mapping table | Ericsson, Huawei, Deutsche Telekom | CR | - | Yes |
Yes
| agreed | No | S5‑235089 | |||
S5‑235090 | Update reference to GST | Ericsson, Huawei, Deutsche Telekom | CR | Approval | Yes |
Yes
| revised | No | S5‑236034 | |||
S5‑236034 | Update reference to GST | Ericsson, Huawei, Deutsche Telekom | CR | Approval | Yes |
Yes
| agreed | No | S5‑235090 | |||
S5‑235091 | Update reference to GST | Ericsson, Huawei, Deutsche Telekom | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑235094 | Update reference to GST | Ericsson, Huawei, Deutsche Telekom | CR | Approval | Yes |
Yes
| revised | No | S5‑236035 | |||
S5‑236035 | Update reference to GST | Ericsson, Huawei, Deutsche Telekom | CR | Approval | Yes |
Yes
| agreed | No | S5‑235094 | |||
S5‑235095 | Update reference to GST | Ericsson, Huawei, Deutsche Telekom | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑235096 | Discussion paper on support for V2X in service profile | L.M. Ericsson Limited | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑235159 | Rel-16 CR TS 28.541 Correction to type defintion of coverageAreaTAList | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑236036 | |||
S5‑236036 | Rel-16 CR TS 28.541 Correction to type defintion of coverageAreaTAList | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑235159 | |||
S5‑235160 | Rel-17 CR TS 28.541 Correction to type defintion of coverageAreaTAList | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑236037 | |||
S5‑236037 | Rel-17 CR TS 28.541 Correction to type defintion of coverageAreaTAList | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑235160 | |||
S5‑235161 | Rel-18 CR TS 28.541 Correction to type defintion of coverageAreaTAList | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑236038 | |||
S5‑236038 | Rel-18 CR TS 28.541 Correction to type defintion of coverageAreaTAList | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑235161 | |||
S5‑235164 | Rel-17 CR TS 28.541 Add missing SLS attributes supported in serviceProfile to sliceProfile | Nokia, Nokia Shanghai Bell, KDDI, TELUS | CR | Approval | Yes |
Yes
| not pursued | No | S5‑233892 | |||
S5‑235165 | Rel-18 CR TS 28.541 Add missing SLS attributes supported in serviceProfile to sliceProfile | Nokia, Nokia Shanghai Bell, KDDI, TELUS | CR | Approval | Yes |
Yes
| not pursued | No | S5‑233893 | |||
S5‑235166 | Rel-17 CR TS 28.541 Add SLS attribute availability to sliceProfile | Nokia, Nokia Shanghai Bell, KDDI, TELUS | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑235167 | Rel-18 CR TS 28.541 Add SLS attribute availability to sliceProfile | Nokia, Nokia Shanghai Bell, KDDI, TELUS | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑235168 | Rel-17 CR TS 28.541 Add SLS attribute jitter to sliceProfile | Nokia, Nokia Shanghai Bell, KDDI, TELUS | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑235169 | Rel-18 CR TS 28.541 Add SLS attribute jitter to sliceProfile | Nokia, Nokia Shanghai Bell, KDDI, TELUS | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑235235 | Update RRMPolicyRatio | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑236039 | |||
S5‑236039 | Update RRMPolicyRatio | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235235 | |||
S5‑235236 | Update RRMPolicyRatio | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑236040 | |||
S5‑236040 | Update RRMPolicyRatio | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235236 | |||
S5‑235237 | Update RRMPolicyRatio | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑236041 | |||
S5‑236041 | Update RRMPolicyRatio | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235237 | |||
S5‑235279 | Correct the description of network slice subnet instance | ZTE Corporation | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑235280 | Correct the description of network slice subnet instance | ZTE Corporation | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑235286 | Correct the description of network slice subnet instance | ZTE Corporation | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑235382 | Rel-16 CR TS 28.541 Correct the issues for the attribute with the ENUM type for network slicing NRM fragment | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑236042 | |||
S5‑236042 | Rel-16 CR TS 28.541 Correct the issues for the attribute with the ENUM type for network slicing NRM fragment | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235382 | |||
S5‑235383 | Rel-17 CR TS 28.541 Correct the issues for the attribute with the ENUM type for network slicing NRM fragment | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑236043 | |||
S5‑236043 | Rel-17 CR TS 28.541 Correct the issues for the attribute with the ENUM type for network slicing NRM fragment | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235383 | |||
S5‑235384 | Rel-18 CR TS 28.541 Correct the issues for the attribute with the ENUM type for network slicing NRM fragment | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑236044 | |||
S5‑236044 | Rel-18 CR TS 28.541 Correct the issues for the attribute with the ENUM type for network slicing NRM fragment | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235384 | |||
S5‑235387 | Rel-15 CR 28.531 Fix incomplete procedure for network function instance creation | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑235388 | Rel-16 CR 28.531 Fix incomplete procedure for network function instance creation | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑235389 | Rel-17 CR 28.531 Fix incomplete procedure for network function instance creation | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑235390 | Rel-18 CR 28.531 Fix incomplete procedure for network function instance creation | Huawei | CR | Agreement | Yes |
YesThere is no mirror given that the text is removed by another CR (5943).
| not pursued | No | ||||
S5‑235391 | Rel-15 CR 28.533 Fix incorrect references | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑235392 | Rel-16 CR 28.533 Fix incorrect references | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑235393 | Rel-17 CR 28.533 Fix incorrect references | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑235437 | Add missing scenario for network slice provisioning | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑236045 | |||
S5‑236045 | Add missing scenario for network slice provisioning | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑235437 | |||
S5‑235438 | Add missing scenario for network slice provisioning | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑236046 | |||
S5‑236046 | Add missing scenario for network slice provisioning | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑235438 | |||
S5‑235606 | Rel-18 CR 28.824 EN resolution | Alibaba Group | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑236047 | Rel-18 CR 28.824 EN resolution | Alibaba Group | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
S5‑235638 | Rel-18 CR 28.824 Update references | Alibaba Group | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑236054 | Rel-18 CR 28.824 Update references | Alibaba Group | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
S5‑235664 | Discussion paper on GST version and Release | L.M. Ericsson Limited, Deutsche Telekom, Telefonica, Huawei | discussion | Agreement | Yes |
Yes
| endorsed | No | ||||
6.3.10 | MEC management | S5‑235520 | Correction of EAS to connect with UPF UC | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||
S5‑235521 | Correction of EAS to connect with UPF UC | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑235530 | Correction of EcmConnectionInfo | Huawei, Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑235531 | Correction of EcmConnectionInfo | Huawei, Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
6.3.11 | General NRM | S5‑235054 | Update DateTime definition | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| revised | No | S5‑236062 | |
S5‑236062 | Update DateTime definition | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| agreed | No | S5‑235054 | |||
S5‑235058 | Clarifying isInvariant true | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| revised | No | S5‑236056 | |||
S5‑236056 | Clarifying isInvariant true | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| agreed | No | S5‑235058 | |||
S5‑235059 | Rel-17 CR TS 32.256 Clarify definition of AllowedValues | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑236057 | S5‑221496 | ||
S5‑236057 | Rel-17 CR TS 32.256 Clarify definition of AllowedValues | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑235059 | |||
S5‑235060 | DP Why the stage 1-2-3 process needs to be simplified for external solutions | Ericsson Hungary Ltd | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑235061 | Update DateTime definition | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑236061 | |||
S5‑236061 | Update DateTime definition | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235061 | |||
S5‑235062 | Update DateTime definition | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑236060 | |||
S5‑236060 | Update DateTime definition | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235062 | |||
S5‑235063 | Update DateTime definition | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑236059 | |||
S5‑236059 | Update DateTime definition | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235063 | |||
S5‑235064 | Correction of RFC reference | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑235065 | Update DateTime definition | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑235066 | Update DateTime definition | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑235067 | Update DateTime definition | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑235068 | YANG Corrections 28.623 R17 | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑235069 | YANG Corrections 28.541 R17 | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑235070 | YANG Corrections 28.623 R18 | Ericsson Hungary Ltd | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑235071 | YANG Corrections 28.541 R18 | Ericsson Hungary Ltd | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑235083 | Correct data type name for deterministic communication | Ericsson | CR | Approval | Yes |
Yes
| merged | No | S5‑236089 | |||
S5‑235084 | Correct data type name for deterministic communication | Ericsson | CR | Approval | Yes |
Yes
| merged | No | S5‑236090 | |||
S5‑235085 | Correct data type name for deterministic communication | Ericsson | CR | Approval | Yes |
Yes
| merged | No | S5‑236091 | |||
S5‑235107 | Include copyright in YANG Files R17 | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑235108 | Include copyright in YANG Files R18 | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑235111 | Clarify MnsRegistry handling | Ericsson Hungary Ltd | CR | Agreement | Yes |
Yes
| revised | No | S5‑236063 | S5‑234748 | ||
S5‑236063 | Clarify MnsRegistry handling | Ericsson Hungary Ltd | CR | Agreement | Yes |
Yes
| revised | No | S5‑236130 | S5‑235111 | ||
S5‑236130 | Clarify MnsRegistry handling | Ericsson Hungary Ltd | CR | Agreement | Yes |
Yes
| agreed | No | S5‑236063 | |||
S5‑235112 | Clarify MnsRegistry handling | Ericsson Hungary Ltd | CR | Agreement | Yes |
Yes
| revised | No | S5‑236064 | S5‑234749 | ||
S5‑236064 | Clarify MnsRegistry handling | Ericsson Hungary Ltd | CR | Agreement | Yes |
Yes
| revised | No | S5‑236131 | S5‑235112 | ||
S5‑236131 | Clarify MnsRegistry handling | Ericsson Hungary Ltd | CR | Agreement | Yes |
Yes
| agreed | No | S5‑236064 | |||
S5‑235113 | Clarify MnsRegistry handling, YANG SS | Ericsson Hungary Ltd | CR | Agreement | Yes |
Yes
| revised | No | S5‑236065 | S5‑234750 | ||
S5‑236065 | Clarify MnsRegistry handling, YANG SS | Ericsson Hungary Ltd | CR | Agreement | Yes |
Yes
| revised | No | S5‑236132 | S5‑235113 | ||
S5‑236132 | Clarify MnsRegistry handling, YANG SS | Ericsson Hungary Ltd | CR | Agreement | Yes |
Yes
| agreed | No | S5‑236065 | |||
S5‑235114 | Clarify MnsRegistry handling, YANG SS | Ericsson Hungary Ltd | CR | Agreement | Yes |
Yes
| revised | No | S5‑236066 | S5‑234751 | ||
S5‑236066 | Clarify MnsRegistry handling, YANG SS | Ericsson Hungary Ltd | CR | Agreement | Yes |
Yes
| revised | No | S5‑236133 | S5‑235114 | ||
S5‑236133 | Clarify MnsRegistry handling, YANG SS | Ericsson Hungary Ltd | CR | Agreement | Yes |
Yes
| agreed | No | S5‑236066 | |||
S5‑235115 | Make probableCause mandatory in notifyChangedAlarmGeneral | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑235223 | TS28.541 Rel16 Removing redundant Tai definition in NR NRM | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑235678 | |||
S5‑235224 | TS28.541 Rel17 Removing redundant Tai definition in NR NRM | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑235679 | |||
S5‑235225 | TS28.541 Rel18 Removing redundant Tai definition in NR NRM | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑235680 | |||
S5‑235227 | TS28.541 Rel16 fix small inconsistent issues in stage2, typo in stage 2 and 3 | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑235682 | |||
S5‑235228 | TS28.541 Rel17 fix small inconsistent issues in stage2, typo in stage 2 and 3 | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑235683 | |||
S5‑235229 | TS28.541 Rel18 fix small inconsistent issues in stage2, typo in stage 2 and 3 | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑235684 | |||
S5‑235230 | TS28.541 Rel16 fix a few inheritance diagram issues in NR NRM | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑235685 | |||
S5‑235231 | TS28.541 Rel17 fix a few inheritance diagram issues in NR NRM | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑235686 | |||
S5‑235232 | TS28.541 Rel18 fix a few inheritance diagram issues in NR NRM | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑235687 | |||
S5‑235233 | TS28.532 Rel16 correction to ProvMnS stage3 issue concerning parameter attributes | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑235676 | |||
S5‑235234 | TS28.532 Rel17 correction to ProvMnS stage3 issue concerning parameter attributes | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑235677 | |||
S5‑235365 | Remove duplicated notifications | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑235366 | Remove duplicated notifications | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑235367 | Remove duplicated notifications | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑235380 | Re-17 CR TS 28.541 Correct issues for NRM fragment for NG-RAN MOCN sharing | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑235381 | Re-15 CR TS 28.541 Correct issues for NRM fragment for NG-RAN MOCN sharing | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑235409 | Rel-18 CR TS 32.256 Clarify definition of AllowedValues | Ericsson Inc. | CR | Agreement | Yes |
Yes
| revised | No | S5‑236058 | |||
S5‑236058 | Rel-18 CR TS 32.256 Clarify definition of AllowedValues | Ericsson Inc. | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑235409 | |||
S5‑235410 | Rel-17 CR 32.156 Clarifying isInvariant true | Ericsson Inc. | CR | Approval | Yes |
Yes
| revised | No | S5‑236055 | |||
S5‑236055 | Rel-17 CR 32.156 Clarifying isInvariant true | Ericsson Inc. | CR | Approval | Yes |
Yes
| agreed | No | S5‑235410 | |||
S5‑235412 | Rel-16 CR 28.532 Correct inconsistencies in version number handling in OpenAPI files | Ericsson Inc. | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑236077 | Rel-16 CR 28.532 Correct inconsistencies in version number handling in OpenAPI files | Ericsson Inc. | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑235413 | Rel-17 CR 28.532 Correct inconsistencies in version number handling in OpenAPI | Ericsson Inc. | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑236078 | Rel-17 CR 28.532 Correct inconsistencies in version number handling in OpenAPI | Ericsson Inc. | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑235416 | Rel-17 CR 28.537 Clarify management service discovery use cases | Ericsson Inc. | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑234370 | |||
S5‑235421 | Rel-16 CR 28.622 Clarify HeartbeatControl IOC definition | Ericsson Inc. | CR | Approval | Yes |
Yes
| revised | No | S5‑236083 | |||
S5‑236083 | Rel-16 CR 28.622 Clarify HeartbeatControl IOC definition | Ericsson Inc. | CR | Approval | Yes |
Yes
| agreed | No | S5‑235421 | |||
S5‑235422 | Rel-16 CR 28.623 Clarify HeartbeatControl IOC definition (stage3, yang) | Ericsson Inc. | CR | Approval | Yes |
Yes
| revised | No | S5‑236084 | |||
S5‑236084 | Rel-16 CR 28.623 Clarify HeartbeatControl IOC definition (stage3, yang) | Ericsson Inc. | CR | Approval | Yes |
Yes
| agreed | No | S5‑235422 | |||
S5‑235423 | Rel-17 CR 28.622 Clarify HeartbeatControl IOC definition | Ericsson Inc. | CR | Approval | Yes |
Yes
| revised | No | S5‑236085 | |||
S5‑236085 | Rel-17 CR 28.622 Clarify HeartbeatControl IOC definition | Ericsson Inc. | CR | Approval | Yes |
Yes
| agreed | No | S5‑235423 | |||
S5‑235424 | Rel-17 CR 28.622 Clarify HeartbeatControl IOC definition (stage3, yang) | Ericsson Inc. | CR | Approval | Yes |
Yes
| revised | No | S5‑236086 | |||
S5‑236086 | Rel-17 CR 28.622 Clarify HeartbeatControl IOC definition (stage3, yang) | Ericsson Inc. | CR | Approval | Yes |
Yes
| agreed | No | S5‑235424 | |||
S5‑235425 | Rel-18 CR 28.622 Clarify HeartbeatControl IOC definition | Ericsson Inc. | CR | Approval | Yes |
Yes
| revised | No | S5‑236087 | |||
S5‑236087 | Rel-18 CR 28.622 Clarify HeartbeatControl IOC definition | Ericsson Inc. | CR | Approval | Yes |
Yes
| agreed | No | S5‑235425 | |||
S5‑235426 | Rel-18 CR 28.623 Clarify HeartbeatControl IOC definition (stage3, yang) | Ericsson Inc. | CR | Approval | Yes |
Yes
| revised | No | S5‑236088 | |||
S5‑236088 | Rel-18 CR 28.623 Clarify HeartbeatControl IOC definition (stage3, yang) | Ericsson Inc. | CR | Approval | Yes |
Yes
| agreed | No | S5‑235426 | |||
S5‑235441 | Rel-15 CR TS 28.622 Remove the IOCs which are not applicable for SBMA | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑235442 | Rel-16 CR TS 28.622 Remove the IOCs which are not applicable for SBMA | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑235443 | Rel-17 CR TS 28.622 Remove the IOCs which are not applicable for SBMA | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑235444 | Rel-18 CR TS 28.622 Remove the IOCs which are not applicable for SBMA | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑235515 | Correction on DeterministicComm data type | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑236089 | |||
S5‑236089 | Correction on DeterministicComm data type | Huawei, Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235515 | |||
S5‑235516 | Correction on DeterministicComm data type | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑236090 | |||
S5‑236090 | Correction on DeterministicComm data type | Huawei, Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235516 | |||
S5‑235517 | Correction on DeterministicComm data type | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑236091 | |||
S5‑236091 | Correction on DeterministicComm data type | Huawei,Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235517 | |||
S5‑235605 | Rel-18 CR 28.541 Fixing not defined CM support Qualifier | Samsung Electronics France SA | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑235676 | TS28.532 Rel16 correction to ProvMnS stage3 issue concerning parameter attributes | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑235233 | |||
S5‑235677 | TS28.532 Rel17 correction to ProvMnS stage3 issue concerning parameter attributes | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑235234 | |||
S5‑235678 | TS28.541 Rel16 Removing redundant Tai definition in NR NRM | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑235223 | |||
S5‑236067 | TS28.541 Rel16 Removing redundent and incorrect Tac dataType in NRNRM | Nokia, Nokia Shanghai Bell | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑235679 | TS28.541 Rel17 Removing redundant Tai definition in NR NRM | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑235224 | |||
S5‑236068 | TS28.541 Rel17 Removing redundant Tai definition in NR NRM | Nokia, Nokia Shanghai Bell | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑235680 | TS28.541 Rel18 Removing redundant Tai definition in NR NRM | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑235225 | |||
S5‑236069 | TS28.541 Rel18 Removing redundant Tai definition in NR NRM | Nokia, Nokia Shanghai Bell | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑235682 | TS28.541 Rel16 fix small inconsistent issues in stage2, typo in stage 2 and 3 | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑235227 | |||
S5‑235683 | TS28.541 Rel17 fix small inconsistent issues in stage2, typo in stage 2 and 3 | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑235228 | |||
S5‑235684 | TS28.541 Rel18 fix small inconsitent issues in stage2, typo in stage 2 and 3 | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑235229 | |||
S5‑235685 | TS28.541 Rel16 fix a few inheritance diagram issues in NR NRM | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑236071 | S5‑235230 | ||
S5‑236071 | TS28.541 Rel16 fix a few inheritance diagram issues in NR NRM | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑235685 | |||
S5‑235686 | TS28.541 Rel17 fix a few inheritance diagram issues in NR NRM | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑236072 | S5‑235231 | ||
S5‑236072 | TS28.541 Rel17 fix a few inheritance diagram issues in NR NRM | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑235686 | |||
S5‑235687 | TS28.541 Rel18 fix a few inheritance diagram issues in NR NRM | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑236073 | S5‑235232 | ||
S5‑236073 | TS28.541 Rel18 fix a few inheritance diagram issues in NR NRM | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑235687 | |||
S5‑235724 | Improve Distinguished Name tatern in YANG - R17 | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑235725 | Improve DistinguishedName pattern in YANG - R18 | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| agreed | No | ||||
6.3.12 | PM/KPI | S5‑235178 | Rel-18 CR TS 28.554 Correct reference and fix void section | Telefonica Germany GmbH | CR | Agreement | Yes |
Yes
| revised | No | S5‑236048 | |
S5‑236048 | Rel-18 CR TS 28.554 Correct reference and fix void section | Telefonica Germany GmbH | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235178 | |||
S5‑235179 | Rel-17 CR TS 28.554 Correct reference and fix void section | Telefonica Germany GmbH | CR | Agreement | Yes |
Yes
| revised | No | S5‑236049 | |||
S5‑236049 | Rel-17 CR TS 28.554 Correct reference and fix void section | Telefonica Germany GmbH | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235179 | |||
S5‑235180 | Rel-16 CR TS 28.554 Correct reference and fix void section | Telefonica Germany GmbH | CR | Agreement | Yes |
Yes
| revised | No | S5‑236050 | |||
S5‑236050 | Rel-16 CR TS 28.554 Correct reference and fix void section | Telefonica Germany GmbH | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235180 | |||
S5‑235184 | Rel-16 CR TS 28.552 Clarification of Average delay over F1U measurement | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑236051 | |||
S5‑236051 | Rel-16 CR TS 28.552 Clarification of Average delay over F1U measurement | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑235184 | |||
S5‑235185 | Rel-17 CR TS 28.552 Clarification of Average delay over F1U measurement | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑236052 | |||
S5‑236052 | Rel-17 CR TS 28.552 Clarification of Average delay over F1U measurement | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑235185 | |||
S5‑235186 | Rel-18 CR TS 28.552 Clarification of Average delay over F1U measurement | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑236053 | |||
S5‑236053 | Rel-18 CR TS 28.552 Clarification of Average delay over F1U measurement | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑235186 | |||
S5‑235263 | Rel-17 CR for TS28.552 Add Total number of UL PDCP SDU Packets for split gNB deployment scenario | ZTE Corporation | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑235264 | Rel-18 CR for TS28.552 Add Total number of UL PDCP SDU Packets for split gNB deployment scenario | ZTE Corporation | CR | Approval | Yes |
Yes
| revised | No | S5‑236125 | |||
S5‑236125 | Rel-18 CR for TS28.552 Add Total number of UL PDCP SDU Packets for split gNB deployment scenario | ZTE Corporation | CR | Approval | Yes |
Yes
| agreed | No | S5‑235264 | |||
S5‑235265 | Rel-17 CR for TS28.552 Add Total number of DL PDCP SDU Packets in gNB-CU-UP for split gNB deployment scenario | ZTE Corporation | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑235266 | Rel-18 CR for TS28.552 Add Total number of DL PDCP SDU Packets in gNB-CU-UP for split gNB deployment scenario | ZTE Corporation | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑235267 | Rel-17 CR for TS28.552 Add Total number of DL RLC SDU Packets in gNB-DU for split gNB deployment scenario | ZTE Corporation | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑235268 | Rel-18 CR for TS28.552 Add Total number of DL RLC SDU Packets in gNB-DU for split gNB deployment scenario | ZTE Corporation | CR | Approval | Yes |
Yes
| not pursued | No | ||||
6.3.13 | Trace/MDT | S5‑235203 | Rel-16 CR TS 32.423 Correcting the reference to E1AP specification | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||
S5‑235204 | Rel-17 CR TS 32.423 Correcting the reference to E1AP specification | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
6.3.14 | Other | S5‑235269 | Rel-17 CR for TS28.536 Fix isWritable property of assuranceScope in AssuranceGoal | ZTE Corporation | CR | Approval | Yes |
Yes
| revised | No | S5‑236112 | |
S5‑236112 | Rel-17 CR for TS28.536 Fix isWritable property of assuranceScope in AssuranceGoal | ZTE Corporation | CR | Approval | Yes |
Yes
| agreed | No | S5‑235269 | |||
S5‑235270 | Rel-17 CR for TS28.536 Fix wrong clauses numbering in class definitions | ZTE Corporation | CR | Approval | Yes |
Yes
| revised | No | S5‑236101 | |||
S5‑236101 | Rel-17 CR for TS28.536 Fix wrong clauses numbering in class definitions | ZTE Corporation | CR | Approval | Yes |
Yes
| agreed | No | S5‑235270 | |||
S5‑235271 | Rel-16 CR for TS28.536 Fix ambiguous description in SLS Assurance Procedure | ZTE Corporation | CR | Approval | Yes |
Yes
| revised | No | S5‑236102 | |||
S5‑236102 | Rel-16 CR for TS28.536 Fix ambiguous description in SLS Assurance Procedure | ZTE Corporation | CR | Approval | Yes |
Yes
| agreed | No | S5‑235271 | |||
S5‑235272 | Rel-17 CR for TS28.536 Fix ambiguous description in SLS Assurance Procedure | ZTE Corporation | CR | Approval | Yes |
Yes
| revised | No | S5‑236103 | |||
S5‑236103 | Rel-17 CR for TS28.536 Fix ambiguous description in SLS Assurance Procedure | ZTE Corporation | CR | Approval | Yes |
Yes
| agreed | No | S5‑235272 | |||
S5‑235273 | Rel-16 CR for TS28.535 Fix invalid clause and wrong description of requirements | ZTE Corporation | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑235274 | Rel-17 CR for TS28.535 Fix invalid clause and wrong description of requirements | ZTE Corporation | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑235287 | Rel-18 CR for TS28.554 editorial Correction | ZTE Corporation | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑235288 | Rel-16 CR for TS28.531 Fix wrong clause reference | ZTE Corporation | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑235289 | Rel-17 CR for TS28.531 Fix wrong clause reference | ZTE Corporation | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑235290 | Rel-18 CR for TS28.531 Fix wrong clause reference | ZTE Corporation | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑235291 | Rel-17 CR for TS28.541 Fix wrong annex reference | ZTE Corporation | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑235292 | Rel-18 CR for TS28.541 Fix wrong annex reference | ZTE Corporation | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑235293 | Rel-18 CR for TS28.550 editorial Corrections | ZTE Corporation | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑235294 | Rel-18 CR for TS28.622 editorial Corrections | ZTE Corporation | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑235368 | Update figure A.1.1 | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑235369 | Update figure A.1.1 | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑235395 | Rel-16 CR 32.158 Clarify URI path components need to be percent encoded | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑235396 | Rel-17 CR 32.158 Clarify URI path components need to be percent encoded | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑235397 | Rel-16 CR 32.158 Add missing example for large queries | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑235398 | Rel-17 CR 32.158 Add missing example for large queries | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑235399 | Rel-16 CR 32.158 Clarify an empty result set produced by scoping and filtering is not an error | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑236104 | |||
S5‑236104 | Rel-16 CR 32.158 Clarify an empty result set produced by scoping and filtering is not an error | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑235399 | |||
S5‑235400 | Rel-17 CR 32.158 Clarify an empty result set produced by scoping and filtering is not an error | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑236105 | |||
S5‑236105 | Rel-17 CR 32.158 Clarify an empty result set produced by scoping and filtering is not an error | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑235400 | |||
S5‑235401 | Rel-16 CR 32.158 Add missing example for data model partitioning | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑235402 | Rel-17 CR 32.158 Add missing example for data model partitioning | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑235403 | Rel-16 CR 28.532 Clarify complete attribute values must be included in notifyMOIAttributeValueChanges | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑235404 | Rel-17 CR 28.532 Clarify complete attribute values must be included in notifyMOIAttributeValueChanges | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑235405 | Rel-16 CR 28.532 Clarify usage of the attributes container in notifyMOIChanges | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑235406 | Rel-17 CR 28.532 Clarify usage of the attributes container in notifyMOIChanges | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑235417 | Rel-16 CR 32.158 Correct URI definition inconsistencies | Ericsson Inc. | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑235418 | Rel-17 CR 32.158 Correct URI definition inconsistencies | Ericsson Inc. | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑235419 | Rel-16 CR 28.532 Clarify heartbeat notification handling | Ericsson Inc. | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑235420 | Rel-17 CR 28.532 Clarify heartbeat notification handling | Ericsson Inc. | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑235428 | Rel-16 CR 28.532 Correct URI definition inconsistencies | Ericsson Inc. | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑235429 | Rel-17 CR 28.532 Correct URI definition inconsistencies | Ericsson Inc. | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑235554 | Correction of reference to Forge OpenAPI definition | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑236115 | |||
S5‑236115 | Correction of reference to Forge OpenAPI definition | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235554 | |||
S5‑235555 | Correction of reference to Forge OpenAPI definition | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑236116 | |||
S5‑236116 | Correction of reference to Forge OpenAPI definition | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235555 | |||
S5‑235645 | Rel-17 CR 28.622 Clarify MnS scope value for Managed Elements | Ericsson Inc. | CR | Approval | Yes |
Yes
| revised | No | S5‑236107 | |||
S5‑236107 | Rel-17 CR 28.622 Clarify MnS scope value for Managed Elements | Ericsson Inc. | CR | Approval | Yes |
Yes
| not pursued | No | S5‑235645 | |||
S5‑235646 | Rel-17 CR 28.623 Clarify MnS scope value for Managed Elements (stage3, yang) | Ericsson Inc. | CR | Approval | Yes |
Yes
| revised | No | S5‑236109 | |||
S5‑236109 | Rel-17 CR 28.623 Clarify MnS scope value for Managed Elements (stage3, yang) | Ericsson Inc. | CR | Approval | Yes |
Yes
| not pursued | No | S5‑235646 | |||
S5‑235647 | Rel-18 CR 28.622 Clarify MnS scope value for Managed Elements | Ericsson Inc. | CR | Approval | Yes |
Yes
| revised | No | S5‑236108 | |||
S5‑236108 | Rel-18 CR 28.622 Clarify MnS scope value for Managed Elements | Ericsson Inc. | CR | Approval | Yes |
Yes
| not pursued | No | S5‑235647 | |||
S5‑235648 | Rel-18 CR 28.623 Clarify MnS scope value for Managed Elements (stage3, yang) | Ericsson Inc. | CR | Approval | Yes |
Yes
| revised | No | S5‑236110 | |||
S5‑236110 | Rel-18 CR 28.623 Clarify MnS scope value for Managed Elements (stage3, yang) | Ericsson Inc. | CR | Approval | Yes |
Yes
| not pursued | No | S5‑235648 | |||
S5‑235674 | Rel-16 CR 28.532 Clarify description of generic provisioning service | Ericsson Inc. | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑235675 | Rel-17 CR 28.532 Clarify description of generic provisioning service | Ericsson Inc. | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑235691 | Rel-18 CR Corrections on Signalling Based Activation for NR | Ericsson France S.A.S | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑235694 | Reply LS on Approval of eQoE CRs for NR | Ericsson France S.A.S | LS out | Approval | Yes |
Yes
| revised | No | S5‑235772 | |||
S5‑235772 | Reply LS on Approval of eQoE CRs for NR | Ericsson France S.A.S | LS out | Approval | Yes |
Yes
| approved | No | S5‑235694 | |||
6.4 | Intelligence and Automation |   | ||||||||||
6.4.1 | Self-Configuration of RAN NEs |   | ||||||||||
6.4.1.1 | RANSC_WoP#1 | S5‑235326 | pCR TS 28.317 Add concept, use case and requirements for network configuration data handling | China Mobile, Huawei | pCR | Approval | Yes |
YesNokia: lot of text that is not needed, we don’t talk about things that we don’t follow up in stage 2 and 3. The requirement doesn’t make much sense.
Huawei: The proposed requirement only focus on the MnS/Interface, there is no functional requirements proposed in the pCR. I suggest Nokia to check the document carefully.
| noted | No | ||
6.4.1.2 | RANSC_WoP#2 | S5‑235325 | pCR TS 28.317 Add procedure for Self-configuration management | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑235818 | |
S5‑235818 | pCR TS 28.317 Add procedure for Self-configuration management | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑235325 | |||
6.4.1.3 | RANSC_WoP#3 | S5‑235322 | pCR TS 28.317 Add MnS component type B for self-configuration management | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑235817 | |
S5‑235817 | pCR TS 28.317 Add MnS component type B for self-configuration management | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| noted | No | S5‑235322 | |||
6.4.1.4 | Draft TS email approval | S5‑235816 | Draft TS 28.317 | China Mobile | draft TS | Approval | Yes |
Yes
| approved | No | ||
6.4.2 | Management Data Analytics phase 2 |   | ||||||||||
6.4.2.1 | eMDAS_Ph2_WoP#1 | S5‑235451 | Input to Draft CR Rel-18 28.104 Add recommended actions for non-3GPP operations | Intel, NEC | other | Agreement | Yes |
Yes
| revised | No | S5‑235819 | |
S5‑235819 | Input to Draft CR Rel-18 28.104 Add recommended actions for non-3GPP operations | Intel, NEC | other | Agreement | Yes |
Yes
| approved | No | S5‑235451 | |||
S5‑235733 | Draft CR eMDAS_Ph2 – TS28.104 Further enhancements into the Management Data Analytics (Phase 2) | NEC | draftCR | Information | Yes |
Yes
| approved | No | ||||
S5‑235762 | Draft CR eMDAS_Ph2 – TS28.104 Further enhancements into the Management Data Analytics (Phase 2) | NEC | draftCR | Approval | Yes |
Yes
| approved | No | ||||
6.4.2.2 | eMDAS_Ph2_WoP#2 | S5‑235207 | Rel-18 Input to draft CR TS 28.104 Adding enabling data for Coverage and SLS use cases for PM predictions | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| approved | No | ||
6.4.2.3 | eMDAS_Ph2_WoP#3 | S5‑235209 | Rel-18 Input to draft CR TS 28.104 Filtering MDA Recommendations | Nokia, Nokia Shanghai Bell, Samsung R&D Institute UK | draftCR | Approval | Yes |
Yes
| revised | No | S5‑235820 | |
S5‑235820 | Rel-18 Input to draft CR TS 28.104 Filtering MDA Recommendations | Nokia, Nokia Shanghai Bell, Samsung R&D Institute UK | draftCR | Approval | Yes |
Yes
| approved | No | S5‑235209 | |||
S5‑235210 | Rel-18 Input to draft CR TS 28.104 Support in stage 2 for cross domain MDA | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| revised | No | S5‑236118 | |||
S5‑236118 | Rel-18 Input to draft CR TS 28.104 Support in stage 2 for cross domain MDA | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| noted | No | S5‑235210 | |||
6.4.2.4 | eMDAS_Ph2_WoP#4 |   | ||||||||||
6.4.2.5 | eMDAS_Ph2_WoP#5 |   | ||||||||||
6.4.2.6 | eMDAS_Ph2_WoP#6 |   | ||||||||||
6.4.2.7 | eMDAS_Ph2_WoP#7 | S5‑235208 | Rel-18 Input to draft CR TS 28.104 Enhancing resource analytics use case with correlation across NFs | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| revised | No | S5‑235821 | |
S5‑235821 | Rel-18 Input to draft CR TS 28.104 Enhancing resource analytics use case with correlation across NFs | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| approved | No | S5‑235208 | |||
S5‑235452 | Input to Draft CR Rel-18 28.104 Add MDA capability for resource utilization analysis | Intel, NEC | other | Agreement | Yes |
Yes
| revised | No | S5‑236093 | |||
S5‑236093 | Input to Draft CR Rel-18 28.104 Add MDA capability for resource utilization analysis | Intel, NEC | other | Agreement | Yes |
Yes
| approved | No | S5‑235452 | |||
S5‑235522 | Rel-18 Input to draft CR 28.104 Add use case of MDA assisted control plane congestion analysis | Huawei | draftCR | Approval | Yes |
Yes
| revised | No | S5‑235942 | |||
S5‑235942 | Rel-18 Input to draft CR 28.104 Add use case of MDA assisted control plane congestion analysis | Huawei | draftCR | Approval | Yes |
Yes
| approved | No | S5‑235522 | |||
S5‑235560 | Update MDA capability of fault management for interruption scenario | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
6.4.3 | AI/ML management |   | ||||||||||
6.4.3.1 | AIML_MGT_WoP#1 | S5‑235139 | Draft CR AIML_MGMT - TS 28.105; Enhancements for AI-ML management (Revision of S5-234847 with updated baseline) | Intel | draftCR | Approval | Yes |
Yes
| approved | No | ||
S5‑235211 | Rel-18 CR TS 28.105 Modelling ML Entity | Nokia, Nokia Shanghai Bell, Intel, NEC, Ericsson | CR | Approval | Yes |
Yes
| revised | No | S5‑235822 | S5‑234657 | ||
S5‑235822 | Rel-18 CR TS 28.105 Modelling ML Entity | Nokia, Nokia Shanghai Bell, Intel, NEC, Ericsson | CR | Approval | Yes |
Yes
| agreed | No | S5‑235211 | |||
S5‑235212 | Rel-18 Input to draft CR TS 28.105 NRM Solution for producer initiated re-training | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑235823 | Rel-18 Input to draft CR TS 28.105 NRM Solution for producer initiated re-training | Nokia, Nokia Shanghai Bell | draftCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑235213 | Rel-18 Input to draft CR TS 28.105 Description, Use case and requirements for Context of ML Entitiesy | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑235214 | Rel-18 Input to draft CR TS 28.105 solution for ML capability | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑236122 | Rel-18 Input to draft CR TS 28.105 solution for ML capability | Nokia, Nokia Shanghai Bell | draftCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑235314 | Rel-18 Input to draft CR TS 28.105 Event data for ML training | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑235824 | Rel-18 Input to draft CR TS 28.105 Event data for ML training | Nokia, Nokia Shanghai Bell | draftCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑235315 | Rel-18 Input to draft CR TS 28.105 Measurement data correlation analytics for ML training | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑235316 | Rel-18 Input to draft CR TS 28.105 Training data effectiveness reporting and analytics | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑235825 | Rel-18 Input to draft CR TS 28.105 Training data effectiveness reporting and analytics | Nokia, Nokia Shanghai Bell | draftCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑235317 | Rel-18 Input to draft CR TS 28.105 ML Training activation | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| revised | No | S5‑235826 | |||
S5‑235826 | Rel-18 Input to draft CR TS 28.105 ML Training activation | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| noted | No | S5‑235317 | |||
S5‑235318 | Rel-18 Input to draft CR TS 28.105 ML Training policy-based activation | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| revised | No | S5‑236119 | |||
S5‑236119 | Rel-18 Input to draft CR TS 28.105 ML Training policy-based activation | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| noted | No | S5‑235318 | |||
S5‑235345 | Rel-18_Draft CR_TS28.105 AI/ML Testing Performance management | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| revised | No | S5‑235827 | |||
S5‑235827 | Rel-18_Draft CR_TS28.105 AI/ML Testing Performance management | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| approved | No | S5‑235345 | |||
S5‑235346 | Rel18_DraftCR_TS28105_ML performance indicator selection NRM | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| revised | No | S5‑235828 | |||
S5‑235828 | Rel18_DraftCR_TS28105_ML performance indicator selection NRM | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| approved | No | S5‑235346 | |||
S5‑235347 | Rel-18_Draft CR TS 28.105 ML knowledge-based transfer Learning | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| revised | No | S5‑235835 | |||
S5‑235835 | Rel-18_Draft CR TS 28.105 ML knowledge-based transfer Learning | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| noted | No | S5‑235347 | |||
S5‑235348 | Rel18_DraftCR_TS28105_AIML Inference Emulation Requirements | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑236070 | Rel18_DraftCR_TS28105_AIML Inference Emulation Requirements | Nokia, Nokia Shanghai Bell | draftCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑235349 | Rel18_DraftCR_TS28105_AIML Inference_emulation NRM | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| revised | No | S5‑236074 | |||
S5‑236074 | Rel18_DraftCR_TS28105_AIML Inference_emulation NRM | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| noted | No | S5‑235349 | |||
S5‑235350 | Rel18_DraftCR_TS28105_ML update NRM | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| revised | No | S5‑236075 | |||
S5‑236075 | Rel18_DraftCR_TS28105_ML update NRM | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| approved | No | S5‑235350 | |||
S5‑235351 | Rel18_DraftCR_TS28105_ML Inference NRM | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| revised | No | S5‑236076 | |||
S5‑236076 | Rel18_DraftCR_TS28105_ML Inference NRM | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| noted | No | S5‑235351 | |||
S5‑235352 | Rel18_DraftCR_TS28105_ML Inference History Requirements | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑235353 | Rel18_DraftCR_TS28105_ML Inference_History NRM | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑235445 | S5-23xxx01 Input to DraftCR 28.105 Add MLEntityGroup IOC | Intel, NEC, CATT | other | Agreement | Yes |
Yes
| revised | No | S5‑235837 | |||
S5‑235837 | S5-235837 Input to DraftCR 28.105 Add MLEntityGroup IOC | Intel, NEC, CATT,Ericsson | other | Agreement | Yes |
Yes
| approved | No | S5‑235445 | |||
S5‑235446 | Input to DraftCR 28.105 Update NRMs to support ML entities joint training | Intel, NEC, CATT | other | Agreement | Yes |
Yes
| revised | No | S5‑235838 | |||
S5‑235838 | Input to DraftCR 28.105 Update NRMs to support ML entities joint training | Intel, NEC, CATT | other | Agreement | Yes |
Yes
| approved | No | S5‑235446 | |||
S5‑235448 | Input to DraftCR 28.105 Update NRMs to support ML entities joint testing | Intel, NEC, CATT | other | Agreement | Yes |
Yes
| revised | No | S5‑235839 | |||
S5‑235839 | Input to DraftCR 28.105 Update NRMs to support ML entities joint testing | Intel, NEC, CATT | other | Agreement | Yes |
Yes
| approved | No | S5‑235448 | |||
S5‑235449 | Input to DraftCR 28.105 Add use case and requirements for ML entity loading | Intel, NEC, CATT | other | Agreement | Yes |
Yes
| noted | No | ||||
S5‑235450 | Input to DraftCR 28.105 Add NRMs for ML entity loading | Intel, NEC, CATT | other | Agreement | Yes |
Yes
| noted | No | ||||
S5‑235508 | Add use case and requirements for ML entity loading control and monitoring | China Mobile | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑235565 | Rel-18 Input to Draft CR TS 28.105 Description, Use case and requirements for AIML trustworthiness indicators | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑235572 | Rel-18 Input to Draft CR TS 28.105 Use case and requirements for AIML data trustworthiness | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑235573 | Rel-18 Input to Draft CR TS 28.105 Use case and requirements for AIML training trustworthiness | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑235576 | Rel-18 Input to Draft CR TS 28.105 Use case and requirements for AIML testing trustworthiness | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑235578 | Rel-18 Input to Draft CR TS 28.105 Add solution for AIML data, training and testing trustworthiness | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑235721 | pCR input to Draft CR TS 28.105 add AI/ML management capabilities description | NEC, Intel | draftCR | Agreement | Yes |
Yes
| revised | No | S5‑235840 | |||
S5‑235840 | pCR input to Draft CR TS 28.105 add AI/ML management capabilities description | NEC, Intel | draftCR | Agreement | Yes |
Yes
| approved | No | S5‑235721 | |||
S5‑235726 | pCR input to DraftCR TS28.105 Corrections including rapporteur cleanup into the draft CR TS28.105 Enhancements for AI-ML management | NEC, Intel | draftCR | Approval | Yes |
Yes
| revised | No | S5‑235999 | |||
S5‑235999 | pCR input to DraftCR TS28.105 Corrections including rapporteur cleanup into the draft CR TS28.105 Enhancements for AI-ML management | NEC, Intel | draftCR | Approval | Yes |
Yes
| approved | No | S5‑235726 | |||
S5‑235728 | Restore the wrongly voided clause “5 Service and functional framework” | NEC, Intel | CR | Agreement | Yes |
Yes
| withdrawn | Yes | ||||
S5‑235730 | DP on WF on previously agreed CRs TS28.105 including clause restructure & modelling of ML Entity | NEC, Intel | discussion | Decision | Yes |
Yes
| noted | No | ||||
S5‑235731 | Restore the wrongly voided clause “5 Service and functional framework” | NEC, Intel | CR | Agreement | Yes |
Yes
| revised | No | S5‑235841 | |||
S5‑235841 | Restore the wrongly voided clause “5 Service and functional framework” | NEC, Intel | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235731 | |||
S5‑235732 | Restore the wrongly voided clause “5 Service and functional framework” | NEC, Intel | CR | Agreement | Yes |
Yes
| revised | No | S5‑235842 | |||
S5‑235842 | Restore the wrongly voided clause “5 Service and functional framework” | NEC, Intel | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235732 | |||
S5‑235988 | Draft CR AIML_MGMT - TS 28.105; Enhancements for AI-ML management | Intel | draftCR | Approval | Yes |
Yes
| approved | No | ||||
6.4.3.2 | AIML_MGT_WoP#2 |   | ||||||||||
6.4.4 | Intent driven Management Service for mobile network phase 2 |   | ||||||||||
6.4.4.1 | IDMS_MN_ph2_WoP#1 | S5‑235427 | Rel-18 CR TS 28.623 Stage 3 Re-structuring Trace job (yang) | Ericsson Inc. | CR | Approval | Yes |
Yes
| agreed | No | ||
S5‑235579 | Editorial corrections in 3GPP TS 28.312 stage 3 OpenAPI section | Nokia Solutions & Networks (I) | CR | Approval | Yes |
Yes
| revised | No | S5‑235843 | |||
S5‑235843 | Editorial corrections in 3GPP TS 28.312 stage 3 OpenAPI section | Nokia Solutions & Networks (I) | CR | Approval | Yes |
Yes
| agreed | No | S5‑235579 | |||
S5‑235844 | Editorial corrections in 3GPP TS 28.312 stage 3 OpenAPI section | Nokia Solutions & Networks (I) | CR | Approval | Yes |
Yes
| agreed | No | ||||
6.4.4.2 | IDMS_MN_ph2_WoP#2 | S5‑235216 | Rel-18 CR TS 28.312 Add communication service expectation | Ericsson, Deutsche Telekom | CR | Approval | Yes |
Yes
| not pursued | No | ||
S5‑235845 | Rel-18 CR TS 28.312 Add communication service expectation | Ericsson, Deutsche Telekom | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑235242 | Rel-18 CR TS 28.312 Add solution for intent driven approach for RAN energy saving | Huawei, Deutsche Telekom | CR | Agreement | Yes |
Yes
| revised | No | S5‑235846 | |||
S5‑235846 | Rel-18 CR TS 28.312 Add solution for intent driven approach for RAN energy saving | Huawei, Deutsche Telekom | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235242 | |||
S5‑235244 | Rel-18 CR TS 28.312 Add solution for intent driven approach for radio network capacity optimization | Huawei, Deutsche Telekom | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑235246 | Rel-18 CR TS 28.312 Update the RadioNetworkExpectation to support targeted scope | Huawei, Deutsche Telekom | CR | Agreement | Yes |
Yes
| revised | No | S5‑235847 | |||
S5‑235847 | Rel-18 CR TS 28.312 Update the RadioNetworkExpectation to support targeted scope | Huawei, Deutsche Telekom | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235246 | |||
S5‑235275 | Rel-18 TS 28.312 Correct the description in clause 5.3.2 Intent report | ZTE Corporation | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑235278 | Enhance descriptions and requirements for Intent fulfilment feasibility check | ZTE Corporation | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑235523 | 5GC use case updates | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑235849 | |||
S5‑235849 | 5GC use case updates | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235523 | |||
S5‑235525 | Add the solution for 5GC Network Expectation | Huawei, AsiaInfo | CR | Agreement | Yes |
Yes
| revised | No | S5‑235850 | |||
S5‑235850 | Add the solution for 5GC Network Expectation | Huawei, AsiaInfo | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235525 | |||
S5‑235693 | Correct the use of ExpectationObjects | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
6.4.4.3 | IDMS_MN_ph2_WoP#3 | S5‑235243 | Rel-18 CR TS 28.312 Add solution for intent driven approach for intent report and intent handling capability obtaining | Huawei,Ericsson, Deutsche Telekom | CR | Agreement | Yes |
Yes
| revised | No | S5‑235851 | |
S5‑235851 | Rel-18 CR TS 28.312 Add solution for intent driven approach for intent report and intent handling capability obtaining | Huawei,Ericsson, Deutsche Telekom | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235243 | |||
S5‑235245 | Rel-18 CR TS 28.312 Add requirements and solution for intent activate and intent deactivate | Huawei, Deutsche Telekom | CR | Agreement | Yes |
Yes
| revised | No | S5‑235854 | |||
S5‑235854 | Rel-18 CR TS 28.312 Add requirements and solution for intent activate and intent deactivate | Huawei, Deutsche Telekom | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235245 | |||
S5‑235247 | Rel-18 CR TS 28.312 Extend the allowed value for contextValueRange and targetValueRange | Huawei, Deutsche Telekom | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑235276 | Add the definition of intent report in intent IOC | ZTE Corporation | CR | Approval | Yes |
Yes
| merged | No | S5‑235851 | |||
S5‑235327 | Rel-18 CR TS 28.312 Add intent priority | NTT DOCOMO INC. | CR | Agreement | Yes |
Yes
| merged | No | S5‑235856 | |||
S5‑235331 | Rel-18 CR TS 28.312 Resolve intent conflict | NTT DOCOMO | CR | Agreement | Yes |
Yes
| revised | No | S5‑235857 | |||
S5‑235857 | Rel-18 CR TS 28.312 Resolve intent conflict | NTT DOCOMO | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235331 | |||
S5‑235354 | Rel-18_CR_TS28.312 Selection among Expectation, targets and contexts | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑236117 | |||
S5‑236117 | Rel-18_CR_TS28.312 Selection among Expectation, targets and contexts | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | S5‑235354 | |||
S5‑235355 | Rel18 CR 28312 Requirements on Intent conflicts | Nokia, Nokia Shangai Bell,Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑235859 | |||
S5‑235859 | Rel18 CR 28312 Requirements on Intent conflicts | Nokia, Nokia Shangai Bell,Huawei | CR | Approval | Yes |
Yes
| agreed | No | S5‑235355 | |||
S5‑235356 | Rel-18_CR_TS28.312 Support for intent priorities | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑235856 | |||
S5‑235856 | Rel-18_CR_TS28.312 Support for intent priorities | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑235356 | |||
S5‑235357 | Rel18_CR_TS28312 Solution for end-to-end Network Resource Expectation | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑235860 | |||
S5‑235860 | Rel18_CR_TS28312 Solution for end-to-end Network Resource Expectation | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑235357 | |||
S5‑235358 | Rel18_CR_TS28312 Requirements on intent feedback | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑235359 | Rel18_CR_28312 Requirements on Mapping Intents to ML capabilities | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑235360 | Rel18_CR_28312 Requirements on Intent-driven SON orchestration | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑235361 | Rel18_CR_28312 Requirements on Testing Intent MnS Capabilities | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑235524 | Adding new requirement for feasibility check | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑235848 | |||
S5‑235848 | Adding new requirement for feasibility check | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235524 | |||
S5‑235575 | Rel-18 CR 28.312 Add intent report information model | China Mobile Com. Corporation | CR | Agreement | Yes |
Yes
| merged | No | S5‑235851 | |||
S5‑235581 | Rel-18 CR 28.312 Add intent report notifications | China Mobile Com. Corporation | CR | Agreement | Yes |
Yes
| revised | No | S5‑235852 | |||
S5‑235852 | Rel-18 CR 28.312 Add intent report notifications | China Mobile Com. Corporation | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑235581 | |||
S5‑235583 | Rel-18 CR 28.312 Add REPORT to allowedValues in expectationVerb attributes | China Mobile Com. Corporation | CR | Agreement | Yes |
Yes
| revised | No | S5‑235853 | |||
S5‑235853 | Rel-18 CR 28.312 Add REPORT to allowedValues in expectationVerb attributes | China Mobile Com. Corporation | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑235583 | |||
S5‑235585 | Rel-18 CR 28.312 Intent Conflict Resolution Requirements | Samsung Electronics France SA, NTT DOCOMO INC. | CR | Agreement | Yes |
Yes
| merged | No | S5‑235859 | |||
S5‑235588 | Rel-18 CR TS 28.312 Add fulfilmentDeadline in Intent IOC | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑235861 | |||
S5‑235861 | Rel-18 CR TS 28.312 Add fulfilmentDeadline in Intent IOC | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑235588 | |||
S5‑235722 | Rel-18 CR 28.312 Intent Conflict Resolution Procedure | Samsung Electronics France SA | CR | Agreement | Yes |
Yes
| revised | No | S5‑235858 | |||
S5‑235858 | Rel-18 CR 28.312 Intent Conflict Resolution Procedure | Samsung Electronics France SA | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235722 | |||
S5‑235723 | Rel-18 CR 28.312 Intent Conflict Resolution NRM Enhancements | Samsung Electronics France SA | CR | Agreement | Yes |
Yes
| merged | No | S5‑235851 | |||
6.4.4.4 | IDMS_MN_ph2_WoP#4 | S5‑235277 | Enhance clause 6.3 Procedures for intent management | ZTE Corporation | CR | Approval | Yes |
Yes
| revised | No | S5‑236111 | |
S5‑236111 | Enhance clause 6.3 Procedures for intent management | ZTE Corporation | CR | Approval | Yes |
Yes
| agreed | No | S5‑235277 | |||
6.4.4.5 | IDMS_MN_ph2_WoP#5 |   | ||||||||||
6.5 | Management Architecture and Mechanisms |   | ||||||||||
6.5.1 | Service based management architecture |   | ||||||||||
6.5.1.1 | eSBMA_WoP#1 | S5‑235642 | Rel-18 CR TS 28.533 Update the overview of 5G management specifications | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||
6.5.1.2 | eSBMA_WoP#2 | S5‑235601 | Rel-18 CR TS 28.533 Using Management Services to support multiple players interoperability | Huawei | CR | Yes |
Yes
| revised | No | S5‑235865 | ||
S5‑235865 | Rel-18 CR TS 28.533 Using Management Services to support multiple players interoperability | Huawei | CR | - | Yes |
Yes
| not pursued | No | S5‑235601 | |||
S5‑235604 | Rel-18 CR TS 28.533 Add example of RAN domain management deployment scenario | Huawei | CR | Yes |
Yes
| revised | No | S5‑235866 | ||||
S5‑235866 | Rel-18 CR TS 28.533 Add example of RAN domain management deployment scenario | Huawei | CR | - | Yes |
Yes
| not pursued | No | S5‑235604 | |||
6.5.1.3 | eSBMA_WoP3# | S5‑235092 | 28.111 skeleton | Ericsson Hungary Ltd | draft TS | Approval | Yes |
Yes
| revised | No | S5‑235867 | |
S5‑235867 | 28.111 skeleton | Ericsson Hungary Ltd | draft TS | Approval | Yes |
Yes
| approved | No | S5‑235092 | |||
S5‑235093 | Rel-18 pCR 28.111 FM service first draft | Ericsson Hungary Ltd | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑235106 | Rel-18 pCR 28.111 FM service, definition updates | Ericsson Hungary Ltd | pCR | Approval | Yes |
Yes
| approved | No | ||||
6.5.1.4 | eSBMA_WoP#4 | S5‑235688 | Introduction of SBMA in 32.300 | Ericsson | CR | Yes |
Yes
| not pursued | No | |||
S5‑235869 | Introduction of SBMA in 32.300 | Ericsson | draftCR | - | Yes |
Yes
| approved | No | ||||
6.5.1.5 | eSBMA_WoP#5 | S5‑235689 | Introduction of SBMA in 32.404 | Ericsson | CR | Yes |
Yes
| agreed | No | |||
6.5.1.6 | eSBMA_WoP#6 | S5‑235407 | Revised WID on Service Based Management Architecture (SBMA) | Nokia, Nokia Shanghai Bell | WID revised | Approval | Yes |
Yes
| revised | No | S5‑235870 | |
S5‑235870 | Revised WID on Service Based Management Architecture (SBMA) | Nokia, Nokia Shanghai Bell | WID revised | Approval | Yes |
Yes
| agreed | No | S5‑235407 | |||
S5‑235408 | Rel-18 Input to DraftCR 32.158 Add design pattern for error responses | Nokia, Nokia Shanghai Bell | other | Approval | Yes |
Yes
| revised | No | S5‑235871 | |||
S5‑235871 | Rel-18 Input to DraftCR 32.158 Add design pattern for error responses | Nokia, Nokia Shanghai Bell | other | Approval | Yes |
Yes
| approved | No | S5‑235408 | |||
S5‑235704 | Rel-18 TS 32.158 Add Jpath discussion | Nokia, Nokia Shanghai Bell | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑235872 | |||
S5‑235872 | Rel-18 TS 32.158 Add Jpath discussion | Nokia, Nokia Shanghai Bell | discussion | Endorsement | Yes |
Yes
| noted | No | S5‑235704 | |||
6.5.1.7 | eSBMA_WoP#7 | S5‑235181 | Rel-18 CR TS 28.533 Add capability for advertising NRM properties - Stage 1 | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | ||
S5‑235182 | Rel-18 CR TS 28.622 Add capability for advertising NRM properties - Stage 2 | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑235183 | Rel-18 CR TS 28.623 Add capability for advertising NRM properties - Stage 3 | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑235249 | Deprecate FM subscribe-unsubscribe | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑235250 | DP Notification filtering | Ericsson Hungary Ltd | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑235328 | Introduce MnS Producer Notification Capabilility | Ericsson Hungary Ltd | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑235329 | Introduce MnS Producer Notification Capabilility | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑235330 | Introduce MnS Producer Notification Capabilility | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| agreed | No | ||||
6.5.1.8 | Draft TS email approval | S5‑235868 | Draft TS 28.111 | Ericsson | draft TS | Approval | Yes |
Yes
| approved | No | ||
6.5.2 | Network slicing provisioning rules |   | ||||||||||
6.5.2.1 | NSRULE_WoP#1 | S5‑235665 | Discussion paper on isolation and sharing | L.M. Ericsson Limited, Deutsche Telekom | discussion | Agreement | Yes |
Yes
| noted | No | ||
S5‑235906 | Discussion paper on isolation and sharing | L.M. Ericsson Limited, Deutsche Telekom | discussion | Agreement | No |
Yes
| withdrawn | Yes | ||||
S5‑235666 | Discussion paper on communication services and service profiles | L.M. Ericsson Limited, Deutsche Telekom | discussion | Agreement | Yes |
Yes
| noted | No | ||||
S5‑235668 | Rel-18 CR TS 28.541 Update service profile to be network slice agnostic | Ericsson, Deutsche Telekom | CR | Approval | Yes |
Yes
| not pursued | No | ||||
6.5.2.2 | NSRULE_WoP#2 | S5‑235170 | Rel-18 CR TS 28.541 Add NRM for network slice isolation | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑235905 | S5‑234700 |
S5‑235905 | Rel-18 CR TS 28.541 Add NRM for network slice isolation | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | S5‑235170 | |||
S5‑235176 | Rel-18 CR TS 28.531 Update use case and requirements for network slice isolation support | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑236124 | |||
S5‑236124 | Rel-18 CR TS 28.531 Update use case and requirements for network slice isolation support | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | S5‑235176 | |||
6.5.3 | Network slice provisioning enhancement |   | ||||||||||
6.5.3.1 | eNETSLICE_PRO_WoP#1 | S5‑235158 | Rel-18 CR TS 28.531 Add UML source code for Network Slice LCM procedures | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||
S5‑235162 | Rel-18 CR TS 28.531 Fix MnS for network slice provisioning information | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑235873 | |||
S5‑235873 | Rel-18 CR TS 28.531 Fix MnS for network slice provisioning information | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑235162 | |||
S5‑235163 | Rel-18 CR TS 28.531 Fix MnS for network slice subnet provisioning information | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑235874 | |||
S5‑235874 | Rel-18 CR TS 28.531 Fix MnS for network slice subnet provisioning information | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑235163 | |||
6.5.3.2 | eNETSLICE_PRO_WoP#2 |   | ||||||||||
6.5.4 | Management of Trace/MDT phase 2 |   | ||||||||||
6.5.4.1 | 5GMDT_Ph2_WoP#1 | S5‑235193 | Rel-18 CR TS 28.622 Enhance the applicable notifications for Trace Job | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||
S5‑235194 | Rel-18 CR TS 28.622 Name containment of Trace job in case of Signalling based activation | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑235196 | Rel-18 CR TS 28.622 Re-structuring Trace job | Nokia, Nokia Shanghai Bell, Ericsson | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑235197 | Rel18 CR TS 28.623 Stage 3 Re-structuring Trace job | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
6.5.4.2 | 5GMDT_Ph2_WoP#2 | S5‑235200 | Rel-18 CR TS 32.423 Example trace file for RCEF report | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||
S5‑235201 | Rel-18 CR TS 32.423 Example trace file for RLF report | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
6.5.4.3 | 5GMDT_Ph2_WoP#3 | S5‑235195 | Rel-18 CR TS 28.622 Report Amount for M4, M5, M6 and M7 measurements in LTE | Nokia, Nokia Shangai Bell, China Telecomunication Corp., Huawei | CR | Approval | Yes |
Yes
| agreed | No | ||
S5‑235199 | Rel-18 CR TS 32.422 Report Amount for M4, M5, M6 and M7 measurements in LTE | Nokia, Nokia Shangai Bell, China Telecomunication Corp., Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑235862 | |||
S5‑235862 | Rel-18 CR TS 32.422 Report Amount for M4, M5, M6 and M7 measurements in LTE | Nokia, Nokia Shangai Bell, China Telecomunication Corp., Huawei | CR | Approval | Yes |
Yes
| agreed | No | S5‑235199 | |||
S5‑235202 | Rel-18 CR TS 32.423 Reporting per direction per UE measurements | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑235863 | |||
S5‑235863 | Rel-18 CR TS 32.423 Reporting per direction per UE measurements | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑235202 | |||
S5‑235238 | Rel-18 CR TS 28.623 Report Amount for M4, M5, M6 and M7 measurements in LTE | China Telecomunication Corp., Huawei, Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | ||||
6.5.4.4 | 5GMDT_Ph2_WoP#4 | S5‑235198 | Rel-18 CR TS 32.421 Requirements for MDT in NPN | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑235864 | |
S5‑235864 | Rel-18 CR TS 32.421 Requirements for MDT in NPN | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑235198 | |||
6.5.4.5 | 5GMDT_Ph2_WoP#5 |   | ||||||||||
6.5.5 | 5G performance measurements and KPIs phase 3 |   | ||||||||||
6.5.5.1 | PM_KPI_5G_Ph3_WoP#1 | S5‑235239 | Rel-18 CR TS 28.552 Add number of MA PDU sessions for ATSSS | China Telecomunication Corp., Intel | CR | Agreement | Yes |
Yes
| agreed | No | ||
S5‑235240 | Rel-18 CR TS 28.552 Add MA PDU session conversion measurements | China Telecomunication Corp., Intel | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑235241 | Rel-18 CR TS 28.552 Add MA PDU session creation measurements in HR roaming scenario for ATSSS | China Telecom Corporation Ltd.,Intel | CR | Agreement | Yes |
Yes
| agreed | No | ||||
6.5.5.2 | PM_KPI_5G_Ph3_WoP#2 | S5‑235187 | Rel-18 CR TS 28.552 Addition of measurements for “Average Downlink delay in NG-RAN for a NRCellCU” | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | ||
S5‑235188 | Rel-18 CR TS 28.552 Addition of measurement for optimization of the SN initiated inter-SN CPC | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑235907 | |||
S5‑235907 | Rel-18 CR TS 28.552 Addition of measurement for optimization of the SN initiated inter-SN CPC | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑235188 | |||
S5‑235189 | Rel-18 CR TS 28.554 Addition of “Average Downlink delay in NG-RAN for a NRCellCU” KPI | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑235455 | Add measurements for UL delay between PSA UPF and UE (including D1) | Intel | CR | Agreement | Yes |
Yes
| revised | No | S5‑235908 | |||
S5‑235908 | Add measurements for UL delay between PSA UPF and UE (including D1) | Intel | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235455 | |||
S5‑235535 | New performance measurements for the UE assistance information | Apple, Ericsson | CR | Approval | Yes |
Yes
| revised | No | S5‑235909 | |||
S5‑235909 | New performance measurements for the UE assistance information | Apple, Ericsson | CR | Approval | Yes |
Yes
| not pursued | No | S5‑235535 | |||
S5‑235547 | New KPIs for the UE assistance information | Apple | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑235910 | New KPIs for the UE assistance information | Apple | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑235551 | New measurement “Number of RRC release” | Apple, Ericsson | CR | Approval | Yes |
Yes
| revised | No | S5‑235911 | S5‑234429 | ||
S5‑235911 | New measurement “Number of RRC release” | Apple, Ericsson | CR | Approval | Yes |
Yes
| agreed | No | S5‑235551 | |||
S5‑235552 | New KPI “UE Context Retainability Failure” | Apple | CR | Approval | Yes |
Yes
| revised | No | S5‑235912 | |||
S5‑235912 | New KPI “UE Context Retainability Failure” | Apple | CR | Approval | Yes |
Yes
| not pursued | No | S5‑235552 | |||
S5‑235553 | New KPIs for Inactive and Idle Mode Paging Accessibility | Apple, Ericsson | CR | Approval | Yes |
Yes
| revised | No | S5‑235913 | |||
S5‑235913 | New KPIs for Inactive and Idle Mode Paging Accessibility | Apple, Ericsson | CR | Approval | Yes |
Yes
| agreed | No | S5‑235553 | |||
6.5.5.3 | PM_KPI_5G_Ph3_WoP#3 | S5‑235190 | Rel-18 CR TS 28.550 Enhance the streaming format of PM | Nokia, Nokia Shanghai Bell, Deutsche Telekom AG | CR | Approval | Yes |
Yes
| not pursued | No | S5‑234711 | |
S5‑235914 | Rel-18 CR TS 28.550 Enhance the streaming format of PM | Nokia, Nokia Shanghai Bell, Deutsche Telekom AG | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
6.5.5.4 | PM_KPI_5G_Ph3_WoP#4 |   | ||||||||||
6.5.6 | Additional NRM features phase 2 |   | ||||||||||
6.5.6.1 | AdNRM_ph2_WoP#1 | S5‑235431 | Discussion paper on separate yaml file for different control NRM fragments in TS 28.623 | Huawei | discussion | Endorsement | Yes |
Yes
| noted | No | S5‑234074 | |
S5‑235432 | Rel-18 CR TS 28.623 separate yaml file for different control NRM fragment | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑235718 | S5‑234075 | ||
S5‑235434 | Rel-18 CR TS28.541 Update the feasiibility check NRM fragment to support the missing requirements | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑235925 | |||
S5‑235925 | Rel-18 CR TS28.541 Update the feasiibility check NRM fragment to support the missing requirements | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235434 | |||
S5‑235718 | Rel-18 CR TS 28.623 separate yaml file for different control NRM fragment | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑235432 | |||
6.5.6.2 | AdNRM_ph2_WoP#2 |   | ||||||||||
6.5.6.3 | AdNRM_ph2_WoP#3 | S5‑235433 | Rel-18 CR TS28.541 Correct the stage2 and stage3 issues for BWP configuration | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||
S5‑235607 | Rel-18 CR 28.541 Non IP Support Stage-2 | Samsung Electronics France SA | CR | Agreement | Yes |
Yes
| revised | No | S5‑235926 | |||
S5‑235926 | Rel-18 CR 28.541 Non IP Support Stage-2 | Samsung Electronics France SA | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235607 | |||
S5‑235636 | Rel-18 CR 28.541 Non IP Support Stage-3 | Samsung Electronics France SA | CR | Agreement | Yes |
Yes
| revised | No | S5‑235927 | |||
S5‑235927 | Rel-18 CR 28.541 Non IP Support Stage-3 | Samsung Electronics France SA | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235636 | |||
S5‑235637 | Rel-18 CR 28.541 User Data Access Stage-2 | Samsung Electronics France SA | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑235928 | Rel-18 CR 28.541 User Data Access Stage-2 | Samsung Electronics France SA | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
S5‑235639 | Rel-18 CR 28.541 User Data Access Stage-3 | Samsung Electronics France SA | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑235929 | Rel-18 CR 28.541 User Data Access Stage-3 | Samsung Electronics France SA | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
S5‑235702 | Rel-18 CR TS 28.541 Add missing Attribute Constraints for NROperatorCellDU | China Unicom | CR | Approval | Yes |
Yes
| revised | No | S5‑235930 | |||
S5‑235930 | Rel-18 CR TS 28.541 Add missing Attribute Constraints for NROperatorCellDU | China Unicom | CR | Approval | Yes |
Yes
| agreed | No | S5‑235702 | |||
S5‑235707 | Rel-18 CR TS 28.541 Add slice validity info to ServiceProfile | Samsung Electronics GmbH | CR | Approval | Yes |
Yes
| not pursued | No | ||||
6.5.6.4 | AdNRM_ph2_WoP#4 | S5‑235217 | TS28.541 Rel18 NRM enhancements for NRFFunction | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||
S5‑235931 | TS28.541 Rel18 NRM enhancements for NRFFunction | Nokia, Nokia Shanghai Bell | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑235218 | TS28.541 Rel18 NRM enhancements for BSFFunction | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑235219 | TS28.541 Rel18 NRM enhancements for AANFFunction | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑235220 | TS28.541 Rel18 NRM enhancements for TSCTSFFunction | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑235221 | TS28.541 Rel18 NRM enhancements for GMLCFunction | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑235222 | TS28.541 Rel18 NRM enhancements for class Diagram | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑235932 | |||
S5‑235932 | TS28.541 Rel18 NRM enhancements for class Diagram | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑235222 | |||
S5‑235226 | TS28.541 Rel18 Improve LogicalInterfaceInfo model to add support of static route | Nokia, Nokia Shanghai Bell, KDDI | CR | Approval | Yes |
Yes
| revised | No | S5‑235681 | |||
S5‑235681 | TS28.541 Rel18 Improve LogicalInterfaceInfo model to add support of static route | Nokia, Nokia Shanghai Bell, KDDI | CR | Approval | Yes |
Yes
| revised | No | S5‑235933 | S5‑235226 | ||
S5‑235933 | TS28.541 Rel18 Improve LogicalInterfaceInfo model to add support of static route | Nokia, Nokia Shanghai Bell, KDDI | CR | Approval | Yes |
Yes
| agreed | No | S5‑235681 | |||
6.5.7 | Management Aspects related to NWDAF |   | ||||||||||
6.5.7.1 | MANWDAF_WoP#1 |   | ||||||||||
6.5.7.2 | MANWDAF_WoP#2 |   | ||||||||||
6.5.7.3 | MANWDAF_WoP#3 | S5‑235566 | Add use case on monitoring of machine learning model provisioning at NWDAF | China Telecom | CR | Approval | Yes |
Yes
| agreed | No | ||
S5‑235574 | Add measurements related to NWDAF ML model provision service | China Telecommunications | CR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑235644 | Add measurements related to NWDAF ML model provision service | China Telecom | CR | Yes |
Yes
| agreed | No | |||||
S5‑235649 | Update use case related to performance measurements of NWDAF | China Telecom | CR | Yes |
Yes
| agreed | No | |||||
S5‑235650 | Update NRM enhancements for NWDAFFunction | China Telecom | CR | Yes |
Yes
| revised | No | S5‑235934 | ||||
S5‑235934 | Update NRM enhancements for NWDAFFunction | China Telecom | CR | - | Yes |
Yes
| agreed | No | S5‑235650 | |||
6.5.8 | Enhanced Edge Computing Management |   | ||||||||||
6.5.8.1 | eECM_WoP#1 | S5‑235526 | Update EAS Discovery procedure related measurements | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑235915 | |
S5‑235915 | Update EAS Discovery procedure related measurements | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235526 | |||
S5‑235528 | Rel-18 draftCR 28.538 adding support of ETSI MEC | Huawei | draftCR | Approval | Yes |
Yes
| revised | No | S5‑235916 | |||
S5‑235916 | Rel-18 draftCR 28.538 adding support of ETSI MEC | Huawei | draftCR | Approval | Yes |
Yes
| approved | No | S5‑235528 | |||
S5‑235529 | Rel-18 draftCR 28.538 update ECM NRM | Huawei | draftCR | Approval | Yes |
Yes
| revised | No | S5‑235917 | |||
S5‑235917 | Rel-18 draftCR 28.538 update ECM NRM | Huawei | draftCR | Approval | Yes |
Yes
| approved | No | S5‑235529 | |||
S5‑235989 | Draft CR 28.538 Revise EAS VNF instantiation and termination procedures | Samsung | draftCR | Approval | Yes |
Yes
| approved | No | ||||
6.5.8.2 | eECM_WoP#2 | S5‑235599 | CR 28.538 Federated EAS Lifecycle Management Requirements | Samsung Electronics France SA | CR | Agreement | Yes |
Yes
| revised | No | S5‑235918 | |
S5‑235918 | CR 28.538 Federated EAS Lifecycle Management Requirements | Samsung Electronics France SA | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235599 | |||
S5‑235600 | Rel-18 CR 28.538 Federated ECS Management Requirements | Samsung Electronics France SA | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑235603 | Rel-18 CR 28.538 Federation Management Requirements | Samsung Electronics France SA | CR | Agreement | Yes |
Yes
| revised | No | S5‑235919 | |||
S5‑235919 | Rel-18 CR 28.538 Federation Management Requirements | Samsung Electronics France SA | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235603 | |||
6.5.8.3 | eECM_WoP#3 | S5‑235527 | Rel-18 draftCR 28.538 adding EASResourceReservationJob IOC | Huawei | draftCR | Approval | Yes |
Yes
| revised | No | S5‑235920 | |
S5‑235920 | Rel-18 draftCR 28.538 adding EASResourceReservationJob IOC | Huawei | draftCR | Approval | Yes |
Yes
| approved | No | S5‑235527 | |||
S5‑235595 | Rel-18 InputToDraftCR 28.538 EAS Relocation NRM Enhancements Stage 2 | Samsung Electronics France SA | other | Agreement | Yes |
Yes
| revised | No | S5‑235921 | |||
S5‑235921 | Rel-18 InputToDraftCR 28.538 EAS Relocation NRM Enhancements Stage 2 | Samsung Electronics France SA | other | Agreement | Yes |
Yes
| approved | No | S5‑235595 | |||
S5‑235596 | Rel-18 CR 28.538 EAS Relocation NRM Enhancements Stage 3 | Samsung Electronics France SA | other | Agreement | Yes |
Yes
| revised | No | S5‑235922 | |||
S5‑235922 | Rel-18 CR 28.538 EAS Relocation NRM Enhancements Stage 3 | Samsung Electronics France SA | other | Agreement | Yes |
Yes
| approved | No | S5‑235596 | |||
S5‑235597 | Rel-18 InputToDraftCR 28.538 EAS Relocation Procedure | Samsung Electronics France SA | other | Agreement | Yes |
Yes
| revised | No | S5‑235923 | |||
S5‑235923 | Rel-18 InputToDraftCR 28.538 EAS Relocation Procedure | Samsung Electronics France SA | other | Agreement | Yes |
Yes
| approved | No | S5‑235597 | |||
S5‑235598 | Rel-18 CR 28.538 EAS Relocation Requirements | Samsung Electronics France SA | CR | Agreement | Yes |
Yes
| revised | No | S5‑235924 | |||
S5‑235924 | Rel-18 CR 28.538 EAS Relocation Requirements | Samsung Electronics France SA | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235598 | |||
6.5.9 | Management Aspect of 5GLAN |   | ||||||||||
6.5.9.1 | 5GLAN_Mgt_WoP#1 | S5‑235177 | TS28.541 Rel-18 NRM enhancements to support 5GLAN management | China Mobile | CR | Approval | Yes |
Yes
| not pursued | No | ||
6.5.9.2 | 5GLAN_Mgt_WoP#2 | S5‑235503 | Rel-18 CR 28.554 Add Accessibility KPIs for 5G VN group measurements | China Mobile E-Commerce Co. | CR | Approval | Yes |
Yes
| withdrawn | Yes | ||
S5‑235504 | Rel-18 CR 28.554 Add Integrity KPIs for 5G VN group measurements | China Mobile E-Commerce Co. | CR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑235505 | Rel-18 CR 28.554 Add Utilization KPIs for 5G VN group measurements | China Mobile E-Commerce Co. | CR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑235667 | Rel-18 CR 28.554 Add Accessibility KPIs for 5G VN group measurements | China Mobile | CR | Approval | Yes |
Yes
| revised | No | ||||
S5‑235936 | Rel-18 CR 28.554 Add Accessibility KPIs for 5G VN group measurements | China Mobile | CR | Approval | Yes |
Yes
| agreed | No | S5‑235667 | |||
S5‑235669 | Rel-18 CR 28.554 Add Integrity KPIs for 5G VN group measurements | China Mobile | CR | Approval | Yes |
Yes
| revised | No | S5‑235937 | |||
S5‑235937 | Rel-18 CR 28.554 Add Integrity KPIs for 5G VN group measurements | China Mobile | CR | Approval | Yes |
Yes
| agreed | No | S5‑235669 | |||
S5‑235670 | Rel-18 CR 28.554 Add Utilization KPIs for 5G VN group measurements | China Mobile | CR | Approval | Yes |
Yes
| revised | No | S5‑235938 | |||
S5‑235938 | Rel-18 CR 28.554 Add Utilization KPIs for 5G VN group measurements | China Mobile | CR | Approval | Yes |
Yes
| agreed | No | S5‑235670 | |||
6.5.10 | Management Aspects of NTN |   | ||||||||||
6.5.10.1 | OAM_NTN_WoP#1 | S5‑235567 | Rel-18 CR TS 28.533 Add management capability support for integration with satellite networking | China Unicom, CATT | CR | Approval | Yes |
Yes
| not pursued | No | ||
S5‑236094 | Rel-18 CR TS 28.530 Add management capability support for integration with satellite networking | China Unicom, CATT | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑235569 | Rel-18 CR TS 28.533 Add Annex of reference architecture with integrated satellite component of management service | China Unicom, CATT | CR | Approval | Yes |
Yes
| not pursued | No | ||||
6.5.10.2 | OAM_NTN_WoP#2 | S5‑235511 | Rel-18 CR 28.541 Add satellite coverage availability information for NTN Mobility Management enhancement with discontinuous satellite coverage | China Telecommunications | CR | Yes |
Yes
| merged | No | S5‑236095 | ||
S5‑235640 | Rel-18 CR 28.541 NTN Location Restriction Stage-2 | Samsung Electronics France SA | CR | Agreement | Yes |
Yes
| revised | No | S5‑236097 | |||
S5‑236097 | Rel-18 CR 28.541 NTN Location Restriction Stage-2 | Samsung Electronics France SA | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235640 | |||
S5‑235641 | Rel-18 CR 28.541 NTN Location Restriction Stage 3 | Samsung Electronics France SA | CR | Agreement | Yes |
Yes
| revised | No | S5‑236098 | |||
S5‑236098 | Rel-18 CR 28.541 NTN Location Restriction Stage 3 | Samsung Electronics France SA | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235641 | |||
S5‑235651 | Rel-18 CR TS 28.541 Add NRM Info Model definitions for NTN management(stage2) | CATT | CR | Approval | Yes |
Yes
| revised | No | S5‑236099 | |||
S5‑236099 | Rel-18 CR TS 28.541 Add NRM Info Model definitions for NTN management(stage2) | CATT | CR | Approval | Yes |
Yes
| agreed | No | S5‑235651 | |||
S5‑235652 | Rel-18 CR TS 28.541 Add NRM Info Model definitions for NTN management(Stage3 Yaml) | CATT | CR | Approval | Yes |
Yes
| revised | No | S5‑236100 | |||
S5‑236100 | Rel-18 CR TS 28.541 Add NRM Info Model definitions for NTN management(Stage3 Yaml) | CATT | CR | Approval | Yes |
Yes
| agreed | No | S5‑235652 | |||
S5‑235653 | Rel-17 CR TS 28.541 Add NRM Info Model definitions for NTN management(stage2) | CATT | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑235654 | Rel-17 CR TS 28.541 Add NRM Info Model definitions for NTN management(Stage3 Yaml) | CATT | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑235701 | Rel-18 CR 28.541 NTN Coverage Availability Information Configuration Stage 2 | Samsung Electronics GmbH | CR | Approval | Yes |
Yes
| revised | No | S5‑236095 | |||
S5‑236095 | Rel-18 CR 28.541 NTN Coverage Availability Information Configuration Stage 2 | Samsung Electronics GmbH | CR | Approval | Yes |
Yes
| agreed | No | S5‑235701 | |||
S5‑235706 | Rel-18 CR 28.541 NTN Coverage Availability Information Configuration Stage 3 | Samsung Electronics GmbH | CR | Approval | Yes |
Yes
| revised | No | S5‑236096 | |||
S5‑236096 | Rel-18 CR 28.541 NTN Coverage Availability Information Configuration Stage 3 | Samsung Electronics GmbH | CR | Approval | Yes |
Yes
| agreed | No | S5‑235706 | |||
6.5.10.3 | OAM_NTN_WoP#3 |   | ||||||||||
6.5.11 | Management of cloud-native Virtualized Network Functions |   | ||||||||||
6.5.11.1 | MCVNF_WoP#1 | S5‑235252 | Update NF instance creation and configuration use case and procedure | Ericsson | CR | Approval | Yes |
Yes
| not pursued | No | ||
S5‑235253 | Update NF instance modification procedure | Ericsson | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑235254 | Update NF instance deletion procedure | Ericsson | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑235281 | Enhance the description in clause 5.1.17 creation of a 3GPP NF | ZTE Corporation | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑235282 | Enhance the description in clause 5.1.18 Configuration of a 3GPP NF instance | ZTE Corporation | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑235283 | Rel-18 TS 28.531 Enhance the description in clause 5.1.19 Creation of a 3GPP sub-network | ZTE Corporation | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑235284 | Rel-18 TS 28.531 Enhance the description in clause 5.1.19 Creation of a 3GPP sub-network | ZTE Corporation | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑235285 | Enhance the description in clause 5.1.19 Creation of a 3GPP sub-network | ZTE Corporation | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑235295 | Add the interactions with NFV-MANO in NF instance creation procedure | AsiaInfo | CR | Approval | Yes |
Yes
| revised | No | S5‑235943 | |||
S5‑235943 | Add the interactions with NFV-MANO in NF instance creation procedure | AsiaInfo, Huawei | CR | Approval | Yes |
Yes
| agreed | No | S5‑235295 | |||
S5‑235296 | Add the interactions with NFV-MANO in NF instance deletion procedure | AsiaInfo | CR | Approval | Yes |
Yes
| revised | No | S5‑235944 | |||
S5‑235944 | Add the interactions with NFV-MANO in NF instance deletion procedure | AsiaInfo, Huawei | CR | Approval | Yes |
Yes
| agreed | No | S5‑235296 | |||
S5‑235695 | Update the reference in clause A.4 | China Mobile | CR | Approval | Yes |
Yes
| not pursued | No | ||||
6.5.11.2 | MCVNF_WoP#2 | S5‑235297 | Update the reference information in clause 7.17 | AsiaInfo | CR | Approval | Yes |
Yes
| revised | No | S5‑235945 | |
S5‑235945 | Update the reference information in clause 7.17 | AsiaInfo | CR | Approval | Yes |
Yes
| agreed | No | S5‑235297 | |||
6.5.11.3 | MCVNF_WoP#3 | S5‑235298 | Rel-18 CR TS 28.526 Remove some VNF Package procedures which are not supported in NFV-IFA013 | AsiaInfo Technologies Inc | CR | No |
Yes
| withdrawn | Yes | |||
S5‑235299 | Rel-18 CR TS 28.526 Remove some VNF Package procedures which are not supported in NFV-IFA013 | AsiaInfo Technologies Inc | CR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑235301 | Remove some VNF Package procedures which are not supported in NFV-IFA013 | AsiaInfo | CR | Approval | Yes |
Yes
| agreed | No | ||||
6.5.12 | Management Aspects of 5G Network Sharing Phase2 |   | ||||||||||
6.5.12.1 | MANS_ph2_WoP#1 | S5‑235705 | Rel-18 CR TS 32.130 Add new requirements for management support for NG-RAN MOCN network sharing scenario | China Unicom | CR | Approval | Yes |
Yes
| revised | No | S5‑235939 | |
S5‑235939 | Rel-18 CR TS 32.130 Add new requirements for management support for NG-RAN MOCN network sharing scenario | China Unicom | CR | Approval | Yes |
Yes
| agreed | No | S5‑235705 | |||
6.5.12.2 | MANS_ph2_WoP#2 | S5‑235414 | Rel-18 CR 28.541 Update recommended QoS model usage for Shared RAN | Ericsson Inc. | CR | Approval | Yes |
Yes
| revised | No | S5‑235940 | |
S5‑235940 | Rel-18 CR 28.541 Update recommended QoS model usage for Shared RAN | Ericsson Inc. | CR | Approval | Yes |
Yes
| agreed | No | S5‑235414 | |||
S5‑235415 | Rel-18 CR 28.541 Update NRM for operator specific QoS model for RAN Sharing | Ericsson Inc. | CR | Approval | Yes |
Yes
| revised | No | S5‑235941 | |||
S5‑235941 | Rel-18 CR 28.541 Update NRM for operator specific QoS model for RAN Sharing | Ericsson Inc. | CR | Approval | Yes |
Yes
| agreed | No | S5‑235415 | |||
6.5.13 | Management Aspects of URLLC |   | ||||||||||
6.5.13.1 | URLLC_Mgt_WoP#1 | S5‑235703 | Rel-18 CR TS 28.541 UL and DL reliability configuration in slice and subnet profiles | China Unicom | CR | Approval | Yes |
Yes
| revised | No | S5‑236092 | |
S5‑236092 | Rel-18 CR TS 28.541 UL and DL reliability configuration in slice and subnet profiles | China Unicom | CR | Approval | Yes |
Yes
| agreed | No | S5‑235703 | |||
6.5.13.2 | URLLC_Mgt_WoP#2 | S5‑235692 | Rel-18 CR 28.554 Add new KPI on DL reliability with delay threshold in RAN | China Unicom | CR | Approval | Yes |
Yes
| not pursued | No | ||
6.6 | Support of New Services |   | ||||||||||
6.6.1 | Access control for management service | S5‑235998 | DraftCR 28.533 on Access control for management service | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| approved | No | ||
6.6.1.1 | MSAC_WoP#1 |   | ||||||||||
6.6.1.2 | MSAC_WoP#2 | S5‑235512 | InputToDraftCR Rel-18 28.533 on Access control related to ConditionForMOIs | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| revised | No | S5‑235946 | |
S5‑235946 | InputToDraftCR Rel-18 28.533 on Access control related to ConditionForMOIs | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| noted | No | S5‑235512 | |||
S5‑235513 | InputToDraftCR Rel-18 28.533 on Access control related to PermissionsForMnSs | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| revised | No | S5‑235947 | |||
S5‑235947 | InputToDraftCR Rel-18 28.533 on Access control related to PermissionsForMnSs | Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| approved | No | S5‑235513 | |||
6.6.1.3 | MSAC_WoP#3 |   | ||||||||||
6.6.1.4 | MSAC_WoP#4 |   | ||||||||||
6.6.2 | Enhancements of EE for 5G Phase 2 |   | ||||||||||
6.6.2.1 | EE5GPLUS_Ph2_WoP#1 | S5‑235370 | Living document on 3GPP work on energy efficiency | Huawei, Deutsche Telekom | discussion | Presentation | Yes |
Yes
| endorsed | No | ||
S5‑235371 | Discussion on the living document on 3GPP work on energy efficiency | Huawei, Deutsche Telekom | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑235385 | Adding additional virtual resources usage to estimate VNF energy consumption | Huawei, Deutsche Telekom | CR | Agreement | Yes |
Yes
| revised | No | S5‑235948 | |||
S5‑235948 | Adding additional virtual resources usage to estimate VNF energy consumption | Huawei, Deutsche Telekom | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235385 | |||
S5‑235386 | Introduce clause on roles involved in EE KPI building | Huawei, Deutsche Telekom | CR | Agreement | Yes |
Yes
| revised | No | S5‑235949 | |||
S5‑235949 | Introduce clause on roles involved in EE KPI building | Huawei, Deutsche Telekom | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235386 | |||
S5‑235439 | Update on energy saving for UPFs | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑235440 | Update on energy saving for UPFs | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
6.6.2.2 | EE5GPLUS_Ph2_WoP#2 | S5‑235643 | Rel-18 CR 28.554 add KPI on Energy Efficiency KPI of URLLC Network Slice based on reliability | China Unicom | CR | Approval | Yes |
Yes
| not pursued | No | ||
S5‑235950 | Rel-18 CR 28.554 add KPI on Energy Efficiency KPI of URLLC Network Slice based on reliability | China Unicom | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑235708 | Rel-18 CR TS 28.554 KPI for EE of URLLC NS based on its reliability | Samsung Electronics GmbH | CR | Approval | Yes |
Yes
| not pursued | No | ||||
6.6.3 | Management of non-public networks phase 2 |   | ||||||||||
6.6.3.1 | OAM_NPN_Ph2_WoP#1 |   | ||||||||||
6.6.3.2 | OAM_NPN_Ph2_WoP#2 | S5‑235436 | Add solution for management of NPN service customer | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑236007 | |
S5‑236007 | Add solution for management of NPN service customer | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235436 | |||
6.6.3.3 | OAM_NPN_Ph2_WoP#3 | S5‑235435 | Add solution for NPN fault management | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||
6.6.3.4 | OAM_NPN_Ph2_WoP#4 |   | ||||||||||
6.6.4 | Network and Service Operations for Energy Utilities |   | ||||||||||
6.6.4.1 | NSOEU_WoP#1 | S5‑235332 | Skeleton of TS 28.318 | Rapporteur (Samsung) | draft TS | Agreement | Yes |
Yes
| revised | No | S5‑235951 | |
S5‑235951 | Skeleton of TS 28.318 | Rapporteur (Samsung) | draft TS | Agreement | Yes |
Yes
| approved | No | S5‑235332 | |||
S5‑235333 | Rel-18 pCR 28.318 clause 1 Scope | Samsung, EUTC, EDF | pCR | Approval | Yes |
Yes
| revised | No | S5‑235952 | |||
S5‑235952 | Rel-18 pCR 28.318 clause 1 Scope | Samsung, EUTC, EDF | pCR | Approval | Yes |
Yes
| approved | No | S5‑235333 | |||
S5‑235334 | Rel-18 pCR 28.318 Introduction | Samsung, EUTC, EDF | pCR | Approval | Yes |
Yes
| revised | No | S5‑235953 | |||
S5‑235953 | Rel-18 pCR 28.318 Introduction | Samsung, EUTC, EDF | pCR | Approval | Yes |
Yes
| approved | No | S5‑235334 | |||
S5‑235335 | Rel-18 pCR 28.318 clause 3 Terms and Acronyms | Samsung, EUTC, EDF | pCR | Approval | Yes |
Yes
| revised | No | S5‑235954 | |||
S5‑235954 | Rel-18 pCR 28.318 clause 3 Terms and Acronyms | Samsung, EUTC, EDF | pCR | Approval | Yes |
Yes
| approved | No | S5‑235335 | |||
S5‑235336 | Rel-18 pCR 28.318 clause 4 Overview | Samsung, EUTC, EDF | pCR | Approval | Yes |
Yes
| revised | No | S5‑235955 | |||
S5‑235955 | Rel-18 pCR 28.318 clause 4 Overview | Samsung, EUTC, EDF | pCR | Approval | Yes |
Yes
| approved | No | S5‑235336 | |||
S5‑235337 | Rel-18 pCR 28.318 5.1 General | Samsung, EUTC, EDF | pCR | Approval | Yes |
Yes
| revised | No | S5‑235956 | |||
S5‑235956 | Rel-18 pCR 28.318 5.1 General | Samsung, EUTC, EDF | pCR | Approval | Yes |
Yes
| approved | No | S5‑235337 | |||
S5‑235341 | Rel-18 pCR 28.318 6.1 General | Samsung | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑235709 | Nokia comments on Samsung pCR 5.X Exposed network performance monitoring and prediction | Nokia | discussion | Discussion | Yes |
Yes
| noted | No | ||||
S5‑235710 | Rel-18 pCR 28.318 clause 5 Requirements | Nokia | pCR | Agreement | Yes |
Yes
| revised | No | S5‑236000 | |||
S5‑236000 | Rel-18 pCR 28.318 clause 5 Requirements | Nokia | pCR | Agreement | Yes |
Yes
| noted | No | S5‑235710 | |||
S5‑235712 | Rel-18 pCR 28.318 Annex A.Y Procedures | Nokia | pCR | Agreement | Yes |
Yes
| revised | No | S5‑236001 | |||
S5‑236001 | Rel-18 pCR 28.318 Annex A.Y Procedures | Nokia | pCR | Agreement | Yes |
Yes
| approved | No | S5‑235712 | |||
S5‑235713 | Rel-18 pCR 28.318 Annex Skeleton | Nokia | pCR | Agreement | Yes |
Yes
| noted | No | ||||
6.6.4.2 | NSOEU_WoP#2 | S5‑235338 | Rel-18 pCR 28.318 5.X Exposed network performance monitoring and prediction requirements | Samsung, EUTC, EDF | pCR | Approval | Yes |
Yes
| revised | No | S5‑235548 | |
S5‑235343 | Rel-18 pCR 28.318 6.X Exposed network performance monitoring | Samsung | pCR | Approval | Yes |
Yes
| merged | No | S5‑236001 | |||
S5‑235548 | Rel-18 pCR 28.318 5.X Exposed network performance monitoring and prediction requirements | Samsung, EUTC, EDF, Deutsche Telekom | pCR | Approval | Yes |
Yes
| merged | No | S5‑236000 | S5‑235338 | ||
S5‑235711 | Rel-18 pCR 28.318 clause 3 Definitions and Acronyms | Nokia | pCR | Agreement | Yes |
Yes
| revised | No | S5‑236002 | |||
S5‑236002 | Rel-18 pCR 28.318 clause 3 Definitions and Acronyms | Nokia | pCR | Agreement | Yes |
Yes
| approved | No | S5‑235711 | |||
6.6.4.3 | NSOEU_WoP#3 | S5‑235339 | Rel-18 pCR 28.318 5.X Energy utility and telecommunciations coordinated recovery with redundant topology | Samsung, EUTC, EDF | pCR | Approval | Yes |
Yes
| revised | No | S5‑235549 | |
S5‑235340 | Rel-18 pCR 28.318 5.X Coordinated service recovery without redundent topology | Samsung, EUTC, EDF | pCR | Approval | Yes |
Yes
| revised | No | S5‑235550 | |||
S5‑235549 | Rel-18 pCR 28.318 5.X Energy utility and telecommunciations coordinated recovery with redundant topology | Samsung, EUTC, EDF | pCR | Approval | Yes |
Yes
| noted | No | S5‑235339 | |||
S5‑235550 | Rel-18 pCR 28.318 5.X Coordinated service recovery without redundent topology | Samsung, EUTC, EDF | pCR | Approval | Yes |
Yes
| noted | No | S5‑235340 | |||
S5‑235714 | Rel-18 pCR 28.318 7.Z NRM enhancements, measurements and KPIs for monitoring procedure | Samsung Electronics GmbH | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑236006 | Rel-18 pCR 28.318 7.Z NRM enhancements, measurements and KPIs for monitoring procedure | Samsung Electronics GmbH | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
6.6.4.4 | NSOEU_WoP#4 |   | ||||||||||
6.7 | Intelligence and Automation |   | ||||||||||
6.7.1 | Study on enhancement of autonomous network levels |   | ||||||||||
6.7.1.1 | FS_eANL_WoP#1 |   | ||||||||||
6.7.1.2 | FS_eANL_WoP#2 | S5‑235590 | pCR TR 28.910 Add gap analysis and recommendation for key issue#5.1b RAN UE throughput optimization | China Mobile, Huawei, ZTE, AsiaInfo, China Unicom, CATT | pCR | Approval | Yes |
Yes
| revised | No | S5‑236003 | S5‑234502 |
S5‑236003 | pCR TR 28.910 Add gap analysis and recommendation for key issue#5.1b RAN UE throughput optimization | China Mobile, Huawei, ZTE, AsiaInfo, China Unicom, CATT | pCR | Approval | Yes |
Yes
| approved | No | S5‑235590 | |||
6.7.1.3 | FS_eANL_WoP#3 | S5‑235591 | pCR TR 28.910 Add use cases and requirements for management of ANL | China Mobile, Huawei, Deutsche Telecom, AsiaInfo, CATT, China Unicom, ZTE | pCR | Approval | Yes |
Yes
| revised | No | S5‑236004 | S5‑234176 |
S5‑236004 | pCR TR 28.910 Add use cases and requirements for management of ANL | China Mobile, Huawei, Deutsche Telecom, AsiaInfo, CATT, China Unicom, ZTE | pCR | Approval | Yes |
Yes
| approved | No | S5‑235591 | |||
6.7.1.4 | FS_eANL_WoP#4 | S5‑235698 | pCR TR 28.910 Add potential solutions for Key Issue #6-1: Autonomous network level for RAN energy saving use case | Huawei, Deutsche Telekom, China Mobile | pCR | Approval | Yes |
Yes
| revised | No | S5‑236005 | S5‑234253 |
S5‑236005 | pCR TR 28.910 Add potential solutions for Key Issue #6-1: Autonomous network level for RAN energy saving use case | Huawei, Deutsche Telekom, China Mobile | pCR | Approval | Yes |
Yes
| approved | No | S5‑235698 | |||
S5‑235699 | pCR TR 28.910 Add potential solution for management of ANL | Huawei, China Mobile,Deutsche Telekom | pCR | Approval | Yes |
Yes
| noted | No | S5‑234254 | |||
6.7.1.5 | Draft TR email approval | S5‑236135 | Draft TS 28.318 | Samsung | draft TS | Approval | Yes |
Yes
| approved | No | ||
S5‑236136 | Draft TR 28.910 | China Mobile | draft TR | Approval | Yes |
Yes
| approved | No | ||||
6.7.2 | Study on evaluation of autonomous network levels |   | ||||||||||
6.7.2.1 | FS_ANLEVA_WoP#1 | S5‑235593 | pCR TR 28.909 Add conclusion and recommendation | China Mobile,Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑236106 | |
S5‑236106 | pCR TR 28.909 Add conclusion and recommendation | China Mobile,Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑235593 | |||
S5‑235700 | pCR TR 28.909 Add potential solution for NRM fragment for autonomous network evaluation | Huawei, China Mobile,Deutsche Telekom | pCR | Approval | Yes |
Yes
| noted | No | S5‑234744 | |||
6.7.2.2 | FS_ANLEVA_WoP#2 | S5‑235592 | pCR TR 28.909 Add potential KEI for fault management | China Mobile,Huawei | pCR | Approval | Yes |
Yes
| noted | No | S5‑234745 | |
S5‑235594 | pCR TR 28.909 Update concept for key effectiveness indicator | China Mobile | pCR | Approval | Yes |
Yes
| approved | No | ||||
6.7.2.3 | FS_ANLEVA_WoP#3 |   | ||||||||||
6.7.2.4 | FS_ANLEVA_WoP#4 |   | ||||||||||
6.7.2.5 | Draft TR email approval |   | ||||||||||
6.7.3 | Study on intent-driven management for network slicing |   | ||||||||||
6.7.3.1 | FS_NETSLICE_IDMS_WoP#1 | S5‑235103 | Enhance benefit description in 4.6 | L.M. Ericsson Limited, Deutsche Telekom | pCR | Approval | Yes |
Yes
| noted | No | ||
S5‑235829 | Enhance benefit description in 4.6 | L.M. Ericsson Limited, Deutsche Telekom | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑235394 | pCR 28.836 Clarifications related to network slice provisioning and assurance | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑235830 | |||
S5‑235830 | pCR 28.836 Clarifications related to network slice provisioning and assurance | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑235394 | |||
6.7.3.2 | FS_NETSLICE_IDMS_WoP#2 | S5‑235102 | Add solution for communication service expectation | L.M. Ericsson Limited, Deutsche Telekom, Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||
S5‑235831 | Add solution for communication service expectation | L.M. Ericsson Limited, Deutsche Telekom, Huawei | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
6.7.3.3 | FS_NETSLICE_IDMS_WoP#3 | S5‑235344 | pCR TR 28.836 Remove figure of how ServiceProfile can be represented by intent expectation components | Telefonica Germany GmbH | pCR | Approval | Yes |
Yes
| approved | No | ||
S5‑235561 | pCR 28.836 Add solution of modelling CNSliceProfile attributes as intent expectation for CN network slice subnetwork | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑235833 | |||
S5‑235833 | pCR 28.836 Add solution of modelling CNSliceProfile attributes as intent expectation for CN network slice subnetwork | Huawei | pCR | Approval | Yes |
Yes
| noted | No | S5‑235561 | |||
6.7.3.4 | FS_NETSLICE_IDMS_WoP#4 | S5‑235101 | Add evaluation of alternatives in clause 6 | L.M. Ericsson Limited, Deutsche Telekom | pCR | Approval | Yes |
Yes
| noted | No | ||
S5‑235104 | Rapporteur update addressing edithelp comments | L.M. Ericsson Limited | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑235447 | pCR TR 28.836 Update the solution and procedure for Network slice and network slice subnet expectations | Huawei, Deutsche Telekom | pCR | Approval | Yes |
Yes
| revised | No | S5‑235935 | |||
S5‑235935 | pCR TR 28.836 Update the solution and procedure for Network slice and network slice subnet expectations | Huawei, Deutsche Telekom | pCR | Approval | Yes |
Yes
| approved | No | S5‑235447 | |||
6.7.3.5 | FS_NETSLICE_IDMS_WoP#5 | S5‑235100 | Add conclusions and recommendations to clause 7 | L.M. Ericsson Limited, Deutsche Telekom | pCR | Approval | Yes |
Yes
| noted | No | ||
S5‑236120 | Add conclusions and recommendations to clause 7 | L.M. Ericsson Limited, Deutsche Telekom | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑235105 | Presentation of TR 28.836 to SA for approval | L.M. Ericsson Limited | TS or TR cover | Approval | Yes |
Yes
| noted | No | ||||
S5‑235562 | pCR 28.836 Add desription related to conclusion and recommendation | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑235836 | pCR 28.836 Add desription related to conclusion and recommendation | Huawei | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
6.7.3.6 | Draft TR email approval | S5‑235832 | Draft TR 28.836 | Ericsson | draft TR | Approval | Yes |
Yes
| approved | No | ||
S5‑236137 | Draft TR 28.909 | China Mobile | draft TR | Approval | Yes |
Yes
| approved | No | ||||
6.7.4 | Study on Fault Supervision Evolution |   | ||||||||||
6.7.4.1 | FS_FSEV_WoP#1 | S5‑235558 | pCR 28.830 Add solution for performance KPI related analytics | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑235997 | |
S5‑235997 | pCR 28.830 Add solution for performance KPI related analytics | Huawei | pCR | Approval | Yes |
Yes
| noted | No | S5‑235558 | |||
6.7.4.2 | FS_FSEV_WoP#2 | S5‑235532 | pCR TR 28.830 Add description of failure prediction enhancement | Huawei, China Mobile | pCR | Approval | Yes |
Yes
| revised | No | S5‑236079 | |
S5‑236079 | pCR TR 28.830 Add description of failure prediction enhancement | Huawei, China Mobile | pCR | Approval | Yes |
Yes
| approved | No | S5‑235532 | |||
S5‑235533 | pCR TR 28.830 Add description of performance related alarm analysis | Huawei, China Mobile | pCR | Approval | Yes |
Yes
| revised | No | S5‑236080 | |||
S5‑236080 | pCR TR 28.830 Add description of performance related alarm analysis | Huawei, China Mobile | pCR | Approval | Yes |
Yes
| noted | No | S5‑235533 | |||
S5‑235534 | pCR TR 28.830 Add description of root cause analysis enhancement | Huawei, China Mobile | pCR | Approval | Yes |
Yes
| revised | No | S5‑236081 | |||
S5‑236081 | pCR TR 28.830 Add description of root cause analysis enhancement | Huawei, China Mobile | pCR | Approval | Yes |
Yes
| noted | No | S5‑235534 | |||
6.7.4.3 | FS_FSEV_WoP#3 | S5‑235559 | pCR 28.830 Add description for MDA and close loop control | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑235813 | |
S5‑235813 | pCR 28.830 Add description for MDA and close loop control | Huawei | pCR | Approval | Yes |
Yes
| noted | No | S5‑235559 | |||
6.7.4.4 | Draft TR email approval | S5‑236138 | Draft TR 28.830 | China Mobile | draft TR | Approval | Yes |
Yes
| approved | No | ||
6.8 | Management Architecture and Mechanisms |   | ||||||||||
6.8.1 | Study on Data management phase 2 |   | ||||||||||
6.8.1.1 | FS_MADCOL_ph2_WoP#1 | S5‑235719 | DP on discovery and retrieval of stored management data | Microsoft Europe SARL | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑235814 | |
S5‑235814 | DP on discovery and retrieval of stored management data | Microsoft Europe SARL | discussion | Endorsement | Yes |
Yes
| endorsed | No | S5‑235719 | |||
6.8.1.2 | FS_MADCOL_ph2_WoP#2 | S5‑235191 | Rel-18 pCR 28.842 New KI on logical harmonized representation of stored management data | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑235815 | |
S5‑235815 | Rel-18 pCR 28.842 New KI on logical harmonized representation of stored management data | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | S5‑235191 | |||
S5‑235192 | Rel-18 pCR 28.842 Potential solution for KI#1 | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑235251 | Rel-18 pCR 28.842 Potential solution for new KI on logical harmonized representation of stored management data | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑235411 | Rel-18 pCR 28.842 Add issue to Define Management Data Reporting Capabilities | Ericsson Inc. | pCR | Agreement | Yes |
Yes
| approved | No | ||||
S5‑235720 | pCR 28.842 Potential solution for retrieval of stored management data | Microsoft Europe SARL | pCR | Approval | Yes |
Yes
| noted | No | ||||
6.8.1.3 | FS_MADCOL_ph2_WoP#3 |   | ||||||||||
6.8.1.4 | FS_MADCOL_ph2_WoP#4 |   | ||||||||||
6.8.1.5 | Draft TR email approval | S5‑236139 | Draft TR 28.842 | Nokia | draft TR | Approval | Yes |
Yes
| approved | No | ||
6.9 | Support of New Services |   | ||||||||||
6.9.1 | Study on Key Quality Indicators (KQIs)for 5G service experience |   | ||||||||||
6.9.1.1 | FS_KQI_5G_WoP#1 | S5‑235586 | pCR TR 28.863 Issue 1: Correction of the background information | Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||
6.9.1.2 | FS_KQI_5G_WoP#2 | S5‑235587 | pCR TR 28.863 Issue # 3: Solution of KQIs for Video Uploading | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||
6.9.1.3 | FS_KQI_5G_WoP#3 | S5‑235589 | pCR TR 28.863 Issue#4 Definition of Remote control | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||
6.9.1.4 | FS_KQI_5G_WoP#4 |   | ||||||||||
6.9.1.5 | FS_KQI_5G_WoP#5 | S5‑235602 | pCR TR 28.863 Issue#6 Desription of SLS reqirements | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑236082 | |
S5‑236082 | pCR TR 28.863 Issue#6 Desription of SLS reqirements | Huawei | pCR | Approval | Yes |
Yes
| noted | No | S5‑235602 | |||
6.9.1.6 | Draft TR email approval | S5‑236123 | Draft TR 28.863 | Huawei | draft TR | Approval | Yes |
Yes
| approved | No | ||
6.9.2 | Study on Deterministic Communication Service Assurance |   | ||||||||||
6.9.2.1 | FS_DCSA_WoP#1 |   | ||||||||||
6.9.2.2 | FS_DCSA_WoP#2 | S5‑235545 | pCR TR 28.865 Add conclusion of issue#1 provisioning of network functions | Huawei | pCR | Approval | No |
Yes
| withdrawn | Yes | ||
6.9.2.3 | FS_DCSA_WoP#3 |   | ||||||||||
6.9.2.4 | FS_DCSA_WoP#4 | S5‑235543 | pCR TR 28.865 Update solution of service assurance for video monitoring | Huawei | pCR | Approval | No |
Yes
| withdrawn | Yes | ||
S5‑235544 | pCR TR 28.865 Update solution of service assurance for PLC control | Huawei | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑235546 | pCR TR 28.865 Add conclusion of issue#2 service assurance for video monitoring | Huawei | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
6.9.2.5 | FS_DCSA_WoP#5 |   | ||||||||||
6.9.2.6 | Draft TR email approval |   | ||||||||||
7 | Charging |   | ||||||||||
7.1 | Charging Plenary | S5‑235009 | CH agenda and time plan | WG vice Chair (Matrixx Software) | agenda | Yes |
Yes
| revised | No | S5‑235739 | ||
S5‑235739 | CH agenda and time plan | WG vice Chair (Matrixx Software) | agenda | - | Yes |
Yes
| noted | No | S5‑235009 | |||
S5‑235010 | Collection of useful endorsed document and external communication documents in Charging | WG vice Chair (Matrixx Software) | discussion | Yes |
Yes
| noted | No | |||||
S5‑235012 | Charging exec report | WG vice Chair (Matrixx Software) | report | Yes |
Yes
| noted | No | |||||
S5‑235042 | LS on charging aspects of AI/ML traffic | S2-2305426 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑235138 | LS on charging aspects of AI/ML traffic | MATRIXX Software | LS out | Approval | Yes |
Yes
| revised | No | S5‑235752 | |||
S5‑235752 | LS on charging aspects of AI/ML traffic | MATRIXX Software | LS out | Approval | Yes |
Yes
| approved | No | S5‑235138 | |||
7.2 | New Charging Work Item proposals | S5‑235456 | New WID on Charging Aspects of TSN | Huawei | WID new | Agreement | Yes |
Yes
| revised | No | S5‑235753 | |
S5‑235753 | New WID on Charging Aspects of TSN | Huawei | WID new | Agreement | Yes |
Yes
| agreed | No | S5‑235456 | |||
S5‑235457 | New WID on Charging Aspects of Vertical Charging | Huawei | WID new | Agreement | Yes |
Yes
| revised | No | S5‑235754 | |||
S5‑235754 | New WID on Charging Aspects of Vertical Charging | Huawei | WID new | Agreement | Yes |
Yes
| agreed | No | S5‑235457 | |||
S5‑235582 | New WID on charging enhancements on 5WWC phase 2 | China Unicom, Huawei | WID new | Approval | Yes |
Yes
| revised | No | S5‑235755 | |||
S5‑235755 | New WID on charging enhancements on 5WWC phase 2 | China Unicom, Huawei | WID new | Approval | Yes |
Yes
| agreed | No | S5‑235582 | |||
S5‑235608 | New WID on charging for roaming and additional actor using CHF to CHF interface | Ericsson LM | WID new | Agreement | Yes |
Yes
| revised | No | S5‑235756 | |||
S5‑235756 | New WID on charging for roaming and additional actor using CHF to CHF interface | Ericsson LM | WID new | Agreement | Yes |
Yes
| agreed | No | S5‑235608 | |||
S5‑235655 | New WID on charging aspects of Satellite in 5GS | CATT | WID new | Approval | Yes |
Yes
| revised | No | S5‑235757 | |||
S5‑235757 | New WID on charging aspects of Satellite access in 5GS | CATT | WID new | Approval | Yes |
Yes
| agreed | No | S5‑235655 | |||
7.3 | Charging Maintenance and Rel-18 small Enhancements | S5‑235130 | Correction on AMF identifier | MATRIXX Software | CR | Agreement | Yes |
Yes
| agreed | No | ||
S5‑235131 | Correction on AMF identifier | MATRIXX Software | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑235132 | Correction on AMF identifier | MATRIXX Software | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑235133 | Correction on AMF identifier in CHF CDR data | MATRIXX Software | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑235134 | Correction on AMF identifier | MATRIXX Software | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑235135 | Correction on AMF identifier | MATRIXX Software | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑235136 | Rel-17 CR 28.202 Correction on references | MATRIXX Software | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑235137 | Rel-17 CR 28.202 Correction on triggers for CEF based architecture | MATRIXX Software | CR | Agreement | Yes |
Yes
| revised | No | S5‑235964 | |||
S5‑235964 | Rel-17 CR 28.202 Correction on triggers for CEF based architecture | MATRIXX Software | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235137 | |||
S5‑235142 | Discussion Paper for CHF Connectivity | Nokia, Nokia Shanghai Bell | discussion | Discussion | Yes |
Yes
| noted | No | ||||
S5‑235143 | Discussion paper on NF charging profile and charging characteristics | MATRIXX Software | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑235146 | Correction on API Target Network Function information | AT&T, Ericsson, MATRIXX Software | CR | Agreement | Yes |
Yes
| revised | No | S5‑235965 | |||
S5‑235965 | Correction on API Target Network Function information | AT&T, Ericsson, MATRIXX Software | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235146 | |||
S5‑235147 | Correction on API Target Network Function information | AT&T, Ericsson, MATRIXX Software | CR | Agreement | Yes |
Yes
| revised | No | S5‑235966 | |||
S5‑235966 | Correction on API Target Network Function information | AT&T, Ericsson, MATRIXX Software | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235147 | |||
S5‑235148 | Correction on API Target Network Function information | AT&T, Ericsson, MATRIXX Software | CR | Agreement | Yes |
Yes
| revised | No | S5‑235967 | |||
S5‑235967 | Correction on API Target Network Function information | AT&T, Ericsson, MATRIXX Software | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235148 | |||
S5‑235149 | Correction on API Target Network Function information | AT&T, Ericsson, MATRIXX Software | CR | Agreement | Yes |
Yes
| revised | No | S5‑235968 | |||
S5‑235968 | Correction on API Target Network Function information | AT&T, Ericsson, MATRIXX Software | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235149 | |||
S5‑235150 | Correction on API Target Network Function information | AT&T, Ericsson, MATRIXX Software | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑235151 | Correction on API Target Network Function information | AT&T, Ericsson, MATRIXX Software | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑235255 | Discussion Paper on Edge Infrastructure Usage Charging Container | Amdocs Software Systems Ltd | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑235258 | Rel-17 CR 32.257 EAS Infrastructure Usage Charging | Amdocs Software Systems Ltd | CR | Approval | Yes |
Yes
| revised | No | S5‑235969 | S5‑233253 | ||
S5‑235969 | Rel-17 CR 32.257 EAS Infrastructure Usage Charging | Amdocs Software Systems Ltd | CR | Approval | Yes |
Yes
| agreed | No | S5‑235258 | |||
S5‑235259 | Rel-17 CR 32.291 Update EAS Infrastructure Usage Charging Information | Amdocs Software Systems Ltd | CR | Approval | Yes |
Yes
| revised | No | S5‑235970 | S5‑233257 | ||
S5‑235970 | Rel-17 CR 32.291 Update EAS Infrastructure Usage Charging Information | Amdocs Software Systems Ltd | CR | Approval | Yes |
Yes
| agreed | No | S5‑235259 | |||
S5‑235260 | Rel-17 CR 32.298 Update EAS Infrastructure Usage Charging Information | Amdocs Software Systems Ltd | CR | Approval | Yes |
Yes
| revised | No | S5‑235972 | S5‑233261 | ||
S5‑235972 | Rel-17 CR 32.298 Update EAS Infrastructure Usage Charging Information | Amdocs Software Systems Ltd | CR | Approval | Yes |
Yes
| agreed | No | S5‑235260 | |||
S5‑235261 | Rel-18 CR 32.291 Update EAS Infrastructure Usage Charging Information | Amdocs Software Systems Ltd | CR | Approval | Yes |
Yes
| revised | No | S5‑235971 | S5‑233258 | ||
S5‑235971 | Rel-18 CR 32.291 Update EAS Infrastructure Usage Charging Information | Amdocs Software Systems Ltd | CR | Approval | Yes |
Yes
| agreed | No | S5‑235261 | |||
S5‑235262 | Rel-18 CR 32.298 Update EAS Infrastructure Usage Charging Information | Amdocs Software Systems Ltd | CR | Approval | Yes |
Yes
| revised | No | S5‑235973 | S5‑233262 | ||
S5‑235973 | Rel-18 CR 32.298 Update EAS Infrastructure Usage Charging Information | Amdocs Software Systems Ltd | CR | Approval | Yes |
Yes
| agreed | No | S5‑235262 | |||
S5‑235476 | Addition of the NF Triggers in the CHF CDR | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑234287 | |||
S5‑235477 | Addition of the NF Triggers in the CHF CDR | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑234288 | |||
S5‑235478 | Correction on the Trigger Type | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑235479 | Correction on the TriggerType | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑235480 | Correction on Category | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑235962 | |||
S5‑235962 | Correction on Category | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235480 | |||
S5‑235481 | Correction on the data type of Trigger | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑235963 | |||
S5‑235963 | Correction on the data type of Trigger | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235481 | |||
S5‑235482 | Correct the NSPAContaiberInformation for NSPA | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑235902 | |||
S5‑235902 | Correct the NSPAContaiberInformation for NSPA | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235482 | |||
S5‑235483 | Correct the NSPAContaiberInformation for NSPA | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑235903 | |||
S5‑235903 | Correct the NSPAContaiberInformation for NSPA | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235483 | |||
S5‑235484 | Rel-17 CR 32.298 Correct the NSPAContainerInformation for NSPA | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑235904 | |||
S5‑235904 | Rel-17 CR 32.298 Correct the NSPAContainerInformation for NSPA | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235484 | |||
S5‑235485 | Rel-18 CR 32.298 Correct the NSPAContainerInformation for NSPA | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑235957 | |||
S5‑235957 | Rel-18 CR 32.298 Correct the NSPAContainerInformation for NSPA | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235485 | |||
S5‑235486 | Correct the NSPAContanierInformation for NSPA | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑235487 | Correct the NSPAContanierInformation for NSPA | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑235901 | |||
S5‑235901 | Correct the NSPAContanierInformation for NSPA | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235487 | |||
S5‑235488 | Correction on Charging Data message content for NSPA Charging | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑235958 | |||
S5‑235958 | Correction on Charging Data message content for NSPA Charging | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235488 | |||
S5‑235489 | Correction on Charging Data message content for NSPA Charging | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑235959 | |||
S5‑235959 | Correction on Charging Data message content for NSPA Charging | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235489 | |||
S5‑235490 | Rel-17 CR 32.255 Correction on Category | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑235960 | |||
S5‑235960 | Rel-17 CR 32.255 Correction on Category | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235490 | |||
S5‑235491 | Correction on Category | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑235961 | |||
S5‑235961 | Correction on Category | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235491 | |||
S5‑235492 | Add reference point between MMS node and CHF | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑235982 | |||
S5‑235982 | Add reference point between MMS node and CHF | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235492 | |||
S5‑235493 | Add reference point between MMS node and CHF | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑235983 | |||
S5‑235983 | Add reference point between MMS node and CHF | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235493 | |||
S5‑235609 | Rel-17 CR 32.291 Correction to QoSMonitoring feature | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑235979 | |||
S5‑235979 | Rel-17 CR 32.291 Correction to QoSMonitoring feature | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235609 | |||
S5‑235610 | Rel-18 CR 32.291 Correction to QoSMonitoring feature | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑235981 | |||
S5‑235981 | Rel-18 CR 32.291 Correction to QoSMonitoring feature | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235610 | |||
S5‑235611 | Rel-16 CR 32.291 Correction to triggerType in Nchf_ConvergedCharging API | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑235612 | Rel-17 CR 32.291 Correction to triggerType in Nchf_ConvergedCharging API | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑235613 | Rel-18 CR 32.291 Correction to triggerType in Nchf_ConvergedCharging API | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑235614 | Rel-18 CR 32.291 Corrections to NEF Charging Information | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑235984 | |||
S5‑235984 | Rel-18 CR 32.291 Corrections to NEF Charging Information | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235614 | |||
S5‑235615 | Rel-18 CR 32.254 Corrections to NEF Charging Information | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑235734 | Inter-PLMN Mobility, V-SMF Removal | Cisco Systems | CR | Approval | Yes |
Yes
| revised | No | S5‑235977 | |||
S5‑235977 | Inter-PLMN Mobility, V-SMF Removal | Cisco Systems | CR | Approval | Yes |
Yes
| agreed | No | S5‑235734 | |||
S5‑235735 | Inter-PLMN Mobility, V-SMF Removal | Cisco Systems | CR | Approval | Yes |
Yes
| revised | No | S5‑235978 | |||
S5‑235978 | Inter-PLMN Mobility, V-SMF Removal | Cisco Systems | CR | Approval | Yes |
Yes
| agreed | No | S5‑235735 | |||
S5‑235749 | Rel-16 CR 32.291 Update OpenAPI version | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑235750 | Rel-17 CR 32.291 Update OpenAPI version | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑235751 | Rel-18 CR 32.291 Update OpenAPI version | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑235980 | DP on Trigger collection aspect | Huawei | discussion | Presentation | Yes |
Yes
| noted | No | ||||
7.4 | Rel-18 Charging |   | ||||||||||
7.4.1 | Charging Aspects of Network Slicing Phase 2 | S5‑235123 | Rel-18 pCR 28.203 Clarify triggers and solve Editor's Note | MATRIXX Software | pCR | Approval | Yes |
Yes
| revised | No | S5‑235764 | |
S5‑235764 | Rel-18 pCR 28.203 Clarify triggers and solve Editor's Note | MATRIXX Software | pCR | Approval | Yes |
Yes
| approved | No | S5‑235123 | |||
S5‑235124 | Rel-18 pCR 28.203 Introduce CDR generation | MATRIXX Software | pCR | Approval | Yes |
Yes
| revised | No | S5‑235758 | |||
S5‑235758 | Rel-18 pCR 28.203 Introduce CDR generation | MATRIXX Software | pCR | Approval | Yes |
Yes
| approved | No | S5‑235124 | |||
S5‑235125 | Rel-18 pCR 28.203 Introduce Ga record and CDR file transfer | MATRIXX Software | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑235126 | Rel-18 pCR 28.203 Correction on Number of UEs per network slice flow description | MATRIXX Software | pCR | Approval | Yes |
Yes
| revised | No | S5‑235759 | |||
S5‑235759 | Rel-18 pCR 28.203 Correction on Number of UEs per network slice flow description | MATRIXX Software | pCR | Approval | Yes |
Yes
| approved | No | S5‑235126 | |||
S5‑235127 | Rel-18 pCR 28.203 Introduce definition of charging information | MATRIXX Software | pCR | Approval | Yes |
Yes
| revised | No | S5‑235760 | |||
S5‑235760 | Rel-18 pCR 28.203 Introduce definition of charging information | MATRIXX Software | pCR | Approval | Yes |
Yes
| approved | No | S5‑235127 | |||
S5‑235128 | Rel-18 pCR 28.203 Introduce NSACF specific charging information | MATRIXX Software | pCR | Approval | Yes |
Yes
| revised | No | S5‑235761 | |||
S5‑235761 | Rel-18 pCR 28.203 Introduce NSACF specific charging information | MATRIXX Software | pCR | Approval | Yes |
Yes
| approved | No | S5‑235128 | |||
S5‑235129 | Presentation of TS 28.203 to SA#101 | MATRIXX Software | TS or TR cover | Approval | Yes |
Yes
| approved | No | ||||
S5‑235144 | Rel-18 pCR 28.203 Introduce NSAC charging profile | MATRIXX Software | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑235616 | Rel-18 pCR 28.203 Update of quota management for NSACF | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑235763 | |||
S5‑235763 | Rel-18 pCR 28.203 Update of quota management for NSACF | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑235616 | |||
S5‑235617 | Rel-18 pCR 28.203 Update of trigger handling for NSACF | Ericsson LM | pCR | Approval | Yes |
Yes
| merged | No | S5‑235764 | |||
S5‑235618 | Rel-18 pCR 28.203 Update of basic principles for NSACF | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑235765 | |||
S5‑235765 | Rel-18 pCR 28.203 Update of basic principles for NSACF | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑235618 | |||
S5‑235740 | Draft TS 28.203 | MATRIXX Software | draft TS | Approval | Yes |
Yes
| approved | No | ||||
7.4.2 | Charging Aspects for NSSAA | S5‑235118 | Rel-18 pCR 28.204 Introduce charging scenarios principles | MATRIXX Software | pCR | Approval | Yes |
Yes
| revised | No | S5‑235766 | |
S5‑235766 | Rel-18 pCR 28.204 Introduce charging scenarios principles | MATRIXX Software | pCR | Approval | Yes |
Yes
| approved | No | S5‑235118 | |||
S5‑235119 | Rel-18 pCR 28.204 Introduce applicable triggers | MATRIXX Software | pCR | Approval | Yes |
Yes
| revised | No | S5‑235767 | |||
S5‑235767 | Rel-18 pCR 28.204 Introduce applicable triggers | MATRIXX Software | pCR | Approval | Yes |
Yes
| approved | No | S5‑235119 | |||
S5‑235120 | Rel-18 pCR 28.204 Introduce PEC message flow | MATRIXX Software | pCR | Approval | Yes |
Yes
| revised | No | S5‑235768 | |||
S5‑235768 | Rel-18 pCR 28.204 Introduce PEC message flow | MATRIXX Software | pCR | Approval | Yes |
Yes
| approved | No | S5‑235120 | |||
S5‑235121 | Rel-18 pCR 28.204 Introduce IEC message flow | MATRIXX Software | pCR | Approval | Yes |
Yes
| revised | No | S5‑235783 | |||
S5‑235783 | Rel-18 pCR 28.204 Introduce IEC message flow | MATRIXX Software | pCR | Approval | Yes |
Yes
| approved | No | S5‑235121 | |||
S5‑235122 | Rel-18 pCR 28.204 Introduce ECUR message flow | MATRIXX Software | pCR | Approval | Yes |
Yes
| revised | No | S5‑235784 | |||
S5‑235784 | Rel-18 pCR 28.204 Introduce ECUR message flow | MATRIXX Software | pCR | Approval | Yes |
Yes
| approved | No | S5‑235122 | |||
S5‑235741 | Draft TS 28.204 | MATRIXX Software | draft TS | Approval | Yes |
Yes
| approved | No | ||||
7.4.3 | Charging Aspects for Enhanced Support of Non-Public Networks | S5‑235313 | Rel-18 CR 32.255 Addition of access type for SNPN | China Mobile | CR | Approval | Yes |
Yes
| revised | No | S5‑235805 | |
S5‑235805 | Rel-18 CR 32.255 Addition of access type for SNPN | China Mobile | CR | Approval | Yes |
Yes
| agreed | No | S5‑235313 | |||
S5‑235319 | Rel-18 CR 32.291 Addition of access type for SNPN | China Mobile | CR | Approval | Yes |
Yes
| revised | No | S5‑235806 | |||
S5‑235806 | Rel-18 CR 32.291 Addition of access type for SNPN | China Mobile | CR | Approval | Yes |
Yes
| agreed | No | S5‑235319 | |||
S5‑235320 | Rel-18 CR 32.298 Addition of access type for SNPN | China Mobile | CR | Approval | Yes |
Yes
| revised | No | S5‑235807 | |||
S5‑235807 | Rel-18 CR 32.298 Addition of access type for SNPN | China Mobile | CR | Approval | Yes |
Yes
| agreed | No | S5‑235320 | |||
S5‑235321 | Rel-18 CR 32.256 Add identifier for PNI-NPN charging | China Mobile | CR | Approval | Yes |
Yes
| revised | No | S5‑235808 | |||
S5‑235808 | Rel-18 CR 32.256 Add identifier for PNI-NPN charging | China Mobile | CR | Approval | Yes |
Yes
| agreed | No | S5‑235321 | |||
S5‑235323 | Rel-18 CR 32.291 Add identifier for PNI-NPN charging | China Mobile | CR | Approval | Yes |
Yes
| revised | No | S5‑235809 | |||
S5‑235809 | Rel-18 CR 32.291 Add identifier for PNI-NPN charging | China Mobile | CR | Approval | Yes |
Yes
| agreed | No | S5‑235323 | |||
S5‑235324 | Rel-18 CR 32.298 Add identifier for PNI-NPN charging | China Mobile | CR | Approval | Yes |
Yes
| revised | No | S5‑235810 | |||
S5‑235810 | Rel-18 CR 32.298 Add identifier for PNI-NPN charging | China Mobile | CR | Approval | Yes |
Yes
| agreed | No | S5‑235324 | |||
7.4.4 | Charging Aspects of IMS Data Channel | S5‑235494 | Add charging principle of duration-based charging for IMS data channel | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| revised | No | S5‑235801 | |
S5‑235801 | Add charging principle of duration-based charging for IMS data channel | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235494 | |||
S5‑235495 | Add charging principle of volume-based charging for IMS data channel | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| revised | No | S5‑235802 | |||
S5‑235802 | Add charging principle of volume-based charging for IMS data channel | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235495 | |||
S5‑235496 | Support of Caller and Callee Information in PDU session charging | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| revised | No | S5‑235803 | |||
S5‑235803 | Support of Caller and Callee Information in PDU session charging | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235496 | |||
S5‑235497 | Support of Caller and Callee Information in Stage 3 | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| revised | No | S5‑235804 | |||
S5‑235804 | Support of Caller and Callee Information in Stage 3 | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235497 | |||
7.4.5 | Charging Aspects for SMF and MB-SMF to Support 5G Multicast-broadcast Services | S5‑235174 | Rel-18 CR 32.273 MBMS Charging | Nokia, Nokia Shanghai Bell | CR | Approval | No |
Yes
| withdrawn | Yes | ||
S5‑235175 | Rel-18 CR 32.255 CDR Request and Response Messages Update (MBS) | Nokia, Nokia Shanghai Bell | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑235430 | Rel-18 CR TS 32.240 Multicast-Broadcast Service | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| merged | No | S5‑235788 | |||
S5‑235498 | Add charging requirements for 5MBS | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑235790 | |||
S5‑235790 | Add charging requirements for 5MBS | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235498 | |||
S5‑235499 | CR TS 32.255 Add charging principle for 5MBS | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑235791 | |||
S5‑235791 | CR TS 32.255 Add charging principle for 5MBS | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235499 | |||
S5‑235500 | Add charging procedures for 5MBS | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑235793 | |||
S5‑235793 | Add charging procedures for 5MBS | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235500 | |||
S5‑235557 | Add MB-SMF as consumer of ConvergedCharging service | China Mobile Com. Corporation, Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑235794 | |||
S5‑235794 | Add MB-SMF as consumer of ConvergedCharging service | China Mobile Com. Corporation, Huawei | CR | Approval | Yes |
Yes
| agreed | No | S5‑235557 | |||
S5‑235568 | Add MB-SMF in charging architecture for 5GS | China Mobile Com. Corporation, Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑235788 | |||
S5‑235788 | Add MB-SMF in charging architecture for 5GS | China Mobile Com. Corporation, Huawei | CR | Approval | Yes |
Yes
| agreed | No | S5‑235568 | |||
S5‑235570 | Add 5MBS charging architecture | China Mobile Com. Corporation, Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑235789 | |||
S5‑235789 | Add 5MBS charging architecture | China Mobile Com. Corporation, Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑235570 | |||
S5‑235571 | Add 5MBS charging principles | China Mobile Com. Corporation | CR | Approval | Yes |
Yes
| revised | No | S5‑235792 | |||
S5‑235792 | Add 5MBS charging principles | China Mobile Com. Corporation | CR | Approval | Yes |
Yes
| agreed | No | S5‑235571 | |||
7.5 | Charging studies |   | ||||||||||
7.5.1 | Study on Nchf charging services phase 2 | S5‑235171 | Rel-18 pCR 28.826 IoT Solution | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑235875 | |
S5‑235875 | Rel-18 pCR 28.826 IoT Solution | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑235171 | |||
S5‑235465 | Rel-18 pCR 28.826 Clarify solution #1.2 on the reporting per RG | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑235877 | |||
S5‑235877 | Rel-18 pCR 28.826 Clarify solution #1.2 on the reporting per RG | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑235465 | |||
S5‑235466 | Rel-18 pCR 28.826 Correction to solution #1.1 on zero data transmission | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | ||||
S5‑235467 | Rel-18 pCR 28.826 Clarify use case #1d and add solution for the handling of undefined CDR values with reserved numbers | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑235878 | |||
S5‑235878 | Rel-18 pCR 28.826 Clarify use case #1d and add solution for the handling of undefined CDR values with reserved numbers | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑235467 | |||
S5‑235468 | Rel-18 pCR 28.826 Add the solution for bitrate charging supported by CHF | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑235879 | |||
S5‑235879 | Rel-18 pCR 28.826 Add the solution for bitrate charging supported by CHF | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑235468 | |||
S5‑235469 | Rel-18 pCR 28.826 Correction to solution #3.2, #3.3 and #3.4 on CHF rating enhancement | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑235880 | |||
S5‑235880 | Rel-18 pCR 28.826 Correction to solution #3.2, #3.3 and #3.4 on CHF rating enhancement | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑235469 | |||
S5‑235470 | Rel-18 pCR 28.826 Correcttion to solution #4.1 and #4.3 on event cancelling | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑235881 | |||
S5‑235881 | Rel-18 pCR 28.826 Correcttion to solution #4.1 and #4.3 on event cancelling | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑235470 | |||
S5‑235471 | Rel-18 pCR 28.826 Clarify solution #2.3 about the scope of trigger profile update | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑235882 | |||
S5‑235882 | Rel-18 pCR 28.826 Clarify solution #2.3 about the scope of trigger profile update | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑235471 | |||
S5‑235472 | Rel-18 pCR 28.826 Update the solution evaluation and conclusion in clause 5 | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑235883 | |||
S5‑235883 | Rel-18 pCR 28.826 Update the solution evaluation and conclusion in clause 5 | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑235472 | |||
S5‑235619 | Rel-18 pCR 28.826 New solution for IoT Charging information Optimization | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑235876 | |||
S5‑235876 | Rel-18 pCR 28.826 New solution for IoT Charging information Optimization | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑235619 | |||
S5‑235620 | Rel-18 pCR 28.826 Update of evaluation and conclusions clause 5.1 | Ericsson LM | pCR | Approval | Yes |
Yes
| merged | No | S5‑235883 | |||
S5‑235621 | Rel-18 pCR 28.826 Update of evaluation and conclusions clause 5.2 | Ericsson LM | pCR | Approval | Yes |
Yes
| merged | No | S5‑235883 | |||
S5‑235622 | Rel-18 pCR 28.826 Update of evaluation and conclusions clause 5.3 | Ericsson LM | pCR | Approval | Yes |
Yes
| merged | No | S5‑235883 | |||
S5‑235623 | Rel-18 pCR 28.826 Update of evaluation and conclusions clause 5.4 | Ericsson LM | pCR | Approval | Yes |
Yes
| merged | No | S5‑235883 | |||
S5‑235624 | Rel-18 pCR 28.826 Update of evaluation and conclusions clause 5.5 | Ericsson LM | pCR | Approval | Yes |
Yes
| merged | No | S5‑235883 | |||
S5‑235625 | Rel-18 pCR 28.826 Corrections to clause 6.5 | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑235626 | Rel-18 pCR 28.826 Update of evaluation and conclusions clause 6.5 | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑235742 | Draft TR 28.826 | Ericsson | draft TR | Approval | Yes |
Yes
| approved | No | ||||
7.5.2 | Study on 5G roaming charging architecture for wholesale and retail scenarios | S5‑235473 | Rel-18 pCR 28.827 Update evaluation and conclusion in clause 7.1 and 7.2 | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑235786 | |
S5‑235786 | Rel-18 pCR 28.827 Update evaluation and conclusion in clause 7.1 and 7.2 | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑235473 | |||
S5‑235627 | Rel-18 pCR 28.827 Architecture considerations | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑235628 | Rel-18 pCR 28.827 Correction of use case 1a | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑235785 | |||
S5‑235785 | Rel-18 pCR 28.827 Correction of use case 1a | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑235628 | |||
S5‑235629 | Rel-18 pCR 28.827 Update of evaluation and conclusions clause 7.1 | Ericsson LM | pCR | Approval | Yes |
Yes
| merged | No | S5‑235786 | |||
S5‑235630 | Rel-18 pCR 28.827 Update of evaluation and conclusions clause 7.2 | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑235787 | |||
S5‑235787 | Rel-18 pCR 28.827 Update of evaluation and conclusions clause 7.2 | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑235630 | |||
S5‑235631 | Rel-18 pCR 28.827 Update of evaluation and conclusions clause 7.3 | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑235632 | Rel-18 pCR 28.827 Update of evaluation and conclusions clause 7.4 | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑235795 | |||
S5‑235795 | Rel-18 pCR 28.827 Update of evaluation and conclusions clause 7.4 | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑235632 | |||
S5‑235633 | Rel-18 pCR 28.827 Update of evaluation and conclusions clause 7.5 | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑235796 | |||
S5‑235796 | Rel-18 pCR 28.827 Update of evaluation and conclusions clause 7.5 | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑235633 | |||
S5‑235634 | Rel-18 pCR 28.827 Update of evaluation and conclusions clause 7.6 | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑235797 | |||
S5‑235797 | Rel-18 pCR 28.827 Update of evaluation and conclusions clause 7.6 | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑235634 | |||
S5‑235635 | Rel-18 pCR 28.827 Update of conclusions clause 8 | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑235798 | |||
S5‑235798 | Rel-18 pCR 28.827 Update of conclusions clause 8 | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑235635 | |||
S5‑235671 | Presentation of TR 28.827 for approval | Ericsson LM | TS or TR cover | Approval | Yes |
Yes
| revised | No | S5‑235799 | |||
S5‑235799 | Presentation of TR 28.827 for approval | Ericsson LM | TS or TR cover | Approval | Yes |
Yes
| approved | No | S5‑235671 | |||
S5‑235743 | Draft TR 28.827 | Ericsson | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S5‑235800 | LS to GSMA WSOLU on 5G charging architecture for roaming scenarios phase 2 | Ericsson | LS out | Approval | Yes |
Yes
| approved | No | ||||
7.5.3 | Study on Time Sensitive Networking charging | S5‑235460 | Rel-18 pCR 28.839 Add the key issues and solutions mapping | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | ||
S5‑235461 | Rel-18 pCR 28.839 Add the evaluation and conclusion | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑235812 | |||
S5‑235812 | Rel-18 pCR 28.839 Add the evaluation and conclusion | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑235461 | |||
S5‑235462 | Rel-18 pCR 28.839 Resolve editor's note in solution #4 | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | ||||
S5‑235463 | Rel-18 pCR 28.839 Resolve editor's note in solution #5 | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | ||||
S5‑235464 | Rel-18 pCR 28.839 Resolve editor's note in solution #1 and clarify solution #2 | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑235811 | |||
S5‑235811 | Rel-18 pCR 28.839 Resolve editor's note in solution #1 and clarify solution #2 | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑235464 | |||
S5‑235509 | Presentation of TR 28.839 for approval | Huawei | TS or TR cover | Agreement | Yes |
Yes
| approved | No | ||||
S5‑235744 | Draft TR 28.839 | Huawei | draft TR | Approval | Yes |
Yes
| approved | No | ||||
7.5.4 | Study on CHF Segmentation | S5‑235140 | Rel-18 pCR 28.840 Key Issue for CHF Selection #1 | Nokia, Nokia Shanghai Bell, Amdocs | pCR | Approval | Yes |
Yes
| revised | No | S5‑235884 | |
S5‑235884 | Rel-18 pCR 28.840 Key Issue for CHF Selection #1 | Nokia, Nokia Shanghai Bell, Amdocs | pCR | Approval | Yes |
Yes
| approved | No | S5‑235140 | |||
S5‑235141 | Rel-18 pCR 28.840 Key Issue for CHF Selection #2 | Nokia, Nokia Shanghai Bell, Amdocs | pCR | Approval | Yes |
Yes
| revised | No | S5‑235885 | |||
S5‑235885 | Rel-18 pCR 28.840 Key Issue for CHF Selection #2 | Nokia, Nokia Shanghai Bell, Amdocs | pCR | Approval | Yes |
Yes
| approved | No | S5‑235141 | |||
S5‑235256 | Discussion Paper on Decomposing Charging Function by Domain | Amdocs, Nokia, Nokia Shanghai Bell | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑235886 | |||
S5‑235886 | Discussion Paper on Decomposing Charging Function by Domain | Amdocs, Nokia, Nokia Shanghai Bell | discussion | Endorsement | Yes |
Yes
| noted | No | S5‑235256 | |||
S5‑235257 | Rel-18 pCR 28.840 Addition of a Key Issue | Amdocs, Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑235887 | |||
S5‑235887 | Rel-18 pCR 28.840 Addition of a Key Issue | Amdocs, Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑235257 | |||
S5‑235745 | Draft TR 28.840 | Nokia, Nokia Shanghai Bell | draft TR | Approval | Yes |
Yes
| approved | No | ||||
7.5.5 | Study on Structure of Charging for Verticals | S5‑235458 | Rel18 pCR TR28.843 Clarify the concept and business roles | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑235888 | |
S5‑235888 | Rel18 pCR TR28.843 Clarify the concept and business roles | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑235458 | |||
S5‑235459 | Rel18 pCR TR28.843 Update references and terminologies | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | ||||
S5‑235510 | Presentation of TR 28.843 for approval | Huawei | TS or TR cover | Agreement | Yes |
Yes
| revised | No | S5‑235889 | |||
S5‑235889 | Presentation of TR 28.843 for approval | Huawei | TS or TR cover | Agreement | Yes |
Yes
| approved | No | S5‑235510 | |||
S5‑235746 | Draft TR 28.843 | Huawei | draft TR | Approval | Yes |
Yes
| approved | No | ||||
7.5.6 | Study on charging aspects of Satellite in 5GS | S5‑235172 | Rel-18 pCR 28.844 Converged Charging Sattellite backhaul Solution Update | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| merged | No | S5‑235891 | |
S5‑235173 | Rel-18 pCR 28.844 Satellite backhaul Key Issue | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑235890 | |||
S5‑235890 | Rel-18 pCR 28.844 Satellite backhaul Key Issue | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑235173 | |||
S5‑235474 | Rel-18 pCR 28.844 Add solution on charging for 5G connection via satellite access | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑235892 | |||
S5‑235892 | Rel-18 pCR 28.844 Add solution on charging for 5G connection via satellite access | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑235474 | |||
S5‑235475 | Rel-18 pCR 28.844 Add solution on charging for 5G data connectivity via satellite access | Huawei | pCR | Agreement | Yes |
Yes
| merged | No | S5‑235893 | |||
S5‑235656 | 28.844 Update solutions for satellite backhaul charging | CATT | pCR | Agreement | Yes |
Yes
| revised | No | S5‑235891 | |||
S5‑235891 | 28.844 Update solutions for satellite backhaul charging | CATT | pCR | Agreement | Yes |
Yes
| agreed | No | S5‑235656 | |||
S5‑235657 | 28.844 Resolve EN of edge computing charging with satellite backhaul | CATT | pCR | Agreement | Yes |
Yes
| revised | No | S5‑235894 | |||
S5‑235894 | 28.844 Resolve EN of edge computing charging with satellite backhaul | CATT | pCR | Agreement | Yes |
Yes
| approved | No | S5‑235657 | |||
S5‑235658 | 28.844 Add solutions for satellite access charging | CATT | pCR | Agreement | Yes |
Yes
| revised | No | S5‑235893 | |||
S5‑235893 | 28.844 Add solutions for satellite access charging | CATT | pCR | Agreement | Yes |
Yes
| approved | No | S5‑235658 | |||
S5‑235659 | 28.844 Add solutions for edge computing charging with satellite backhaul | CATT | pCR | Agreement | Yes |
Yes
| revised | No | S5‑235895 | |||
S5‑235895 | 28.844 Add solutions for edge computing charging with satellite backhaul | CATT | pCR | Agreement | Yes |
Yes
| approved | No | S5‑235659 | |||
S5‑235660 | 28.844 Add solutions for SSC-to-SSC communications via satellite backhaul | CATT | pCR | Agreement | Yes |
Yes
| revised | No | S5‑235896 | |||
S5‑235896 | 28.844 Add solutions for SSC-to-SSC communications via satellite backhaul | CATT | pCR | Agreement | Yes |
Yes
| approved | No | S5‑235660 | |||
S5‑235661 | 28.844 Add Evaluation for satellite backhaul charging | CATT | pCR | Agreement | Yes |
Yes
| revised | No | S5‑235898 | |||
S5‑235898 | 28.844 Add Evaluation for satellite backhaul charging | CATT | pCR | Agreement | Yes |
Yes
| approved | No | S5‑235661 | |||
S5‑235662 | 28.844 Add Conclusion for satellite backhaul charging | CATT | pCR | Agreement | Yes |
Yes
| approved | No | ||||
S5‑235663 | 28.844 Add Evaluation for satellite access charging | CATT | pCR | Agreement | Yes |
Yes
| revised | No | S5‑235899 | |||
S5‑235899 | 28.844 Add Evaluation for satellite access charging | CATT | pCR | Agreement | Yes |
Yes
| approved | No | S5‑235663 | |||
S5‑235696 | 28.844 Add solutions for EAS on-board deployment charging | CATT | pCR | Agreement | Yes |
Yes
| revised | No | S5‑235897 | |||
S5‑235897 | 28.844 Add solutions for EAS on-board deployment charging | CATT | pCR | Agreement | Yes |
Yes
| approved | No | S5‑235696 | |||
S5‑235747 | Draft TR 28.844 | CATT | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S5‑235900 | Presentation of TR 28.844 for information | CATT | TS or TR cover | Approval | Yes |
Yes
| approved | No | ||||
7.5.7 | Study on Charging Aspects of Ranging and Sidelink Positioning | S5‑235300 | Rel-18 pCR TR 28.845 v0.0.0 initial skeleton | China Telecom Corporation Ltd. | draft TR | Approval | Yes |
Yes
| approved | No | ||
S5‑235302 | Update of the skeleton | China Telecom Corporation Ltd. | pCR | No |
Yes
| withdrawn | Yes | |||||
S5‑235303 | Rel-18 pCR TR 28.845 Update of the skeleton | China Telecom Corporation Ltd. | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑235304 | Rel-18 pCR TR 28.845 Update of the Scope | China Telecom Corporation Ltd. | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑235305 | Rel-18 pCR TR 28.845 Update of the Reference | China Telecom Corporation Ltd. | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑235306 | Rel-18 pCR TR 28.845 Update of the terms, symbols and abbreviations | China Telecom Corporation Ltd. | pCR | Approval | Yes |
Yes
| revised | No | S5‑235974 | |||
S5‑235974 | Rel-18 pCR TR 28.845 Update of the terms, symbols and abbreviations | China Telecom Corporation Ltd. | pCR | Approval | Yes |
Yes
| approved | No | S5‑235306 | |||
S5‑235307 | Rel-18 pCR TR 28.845 Update of the Overview | China Telecom Corporation Ltd. | pCR | Approval | Yes |
Yes
| revised | No | S5‑235975 | |||
S5‑235975 | Rel-18 pCR TR 28.845 Update of the Overview | China Telecom Corporation Ltd. | pCR | Approval | Yes |
Yes
| approved | No | S5‑235307 | |||
S5‑235308 | Rel-18 pCR TR 28.845 Update of the Business roles | China Telecom Corporation Ltd. | pCR | Approval | Yes |
Yes
| revised | No | S5‑235976 | |||
S5‑235976 | Rel-18 pCR TR 28.845 Update of the Business roles | China Telecom Corporation Ltd. | pCR | Approval | Yes |
Yes
| approved | No | S5‑235308 | |||
S5‑235309 | Rel-18 pCR TR 28.845 Add charging scenarios and key issues for Ranging Sidelink Positioning UE Discovery | China Telecom Corporation Ltd. | pCR | Approval | Yes |
Yes
| revised | No | S5‑235987 | |||
S5‑235987 | Rel-18 pCR TR 28.845 Add charging scenarios and key issues for Ranging Sidelink Positioning UE Discovery | China Telecom Corporation Ltd. | pCR | Approval | Yes |
Yes
| approved | No | S5‑235309 | |||
S5‑235310 | Rel-18 pCR TR 28.845 Add charging scenarios and key issues for UE positioning assisted by Sidelink Positioning and involving 5GC | China Telecom Corporation Ltd. | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑235311 | Rel-18 pCR TR 28.845 Add charging scenarios and key issues for UE only Sidelink Positioning for Target UE using Located UE | China Telecom Corporation Ltd. | pCR | Approval | Yes |
Yes
| revised | No | S5‑235985 | |||
S5‑235985 | Rel-18 pCR TR 28.845 Add charging scenarios and key issues for UE only Sidelink Positioning for Target UE using Located UE | China Telecom Corporation Ltd. | pCR | Approval | Yes |
Yes
| approved | No | S5‑235311 | |||
S5‑235312 | Rel-18 pCR TR 28.845 Add charging scenarios and key issues for Ranging SL Positioning service exposure | China Telecom Corporation Ltd. | pCR | Approval | Yes |
Yes
| revised | No | S5‑235986 | |||
S5‑235986 | Rel-18 pCR TR 28.845 Add charging scenarios and key issues for Ranging SL Positioning service exposure | China Telecom Corporation Ltd. | pCR | Approval | Yes |
Yes
| approved | No | S5‑235312 | |||
S5‑235748 | Draft TR 28.845 | China Telecom | draft TR | Approval | Yes |
Yes
| approved | No | ||||
8 | Any Other Business |   | ||||||||||
9 | Closing of the meeting |   |