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