Tdoc List
2020-12-04 15:23
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‑206000 | Agenda | WG Chair | agenda | Yes |
Yes
| approved | No | |||
3 | IPR and legal declaration |   | ||||||||||
4 | Meetings and activities reports |   | ||||||||||
4.1 | Last SA5 meeting report | S5‑206001 | Report from last SA5 meeting | MCC | report | Yes |
Yes
| approved | No | |||
4.2 | Last SA meeting report |   | ||||||||||
4.3 | Inter-organizational reports |   | ||||||||||
5 | Cross-SWG issues |   | ||||||||||
5.1 | Administrative issues at SA5 level | S5‑206002 | e-meeting process | WG Chair | discussion | Yes |
Yes
| noted | No | |||
S5‑206003 | Post e-meeting email approval status | WG Chair | other | Yes |
No
| available | No | |||||
S5‑206011 | SA5 working procedures | WG Chair | other | Yes |
Yes
| revised | No | S5‑206300 | ||||
S5‑206300 | SA5 working procedures | WG Chair | other | - | Yes |
Yes
| approved | No | S5‑206011 | |||
S5‑206012 | Process for management of draft TS-TRs | WG Chair | other | Yes |
Yes
| noted | No | |||||
S5‑206281 | SA5 ToR update | Ericsson LM | ToR | Approval | Yes |
Yes
| revised | No | S5‑206301 | |||
S5‑206301 | SA5 ToR update | Ericsson LM | ToR | Approval | Yes |
Yes
| agreed | No | S5‑206281 | |||
5.2 | Technical issues at SA5 level |   | ||||||||||
5.3 | Liaison statements at SA5 level | S5‑206015 | Resubmitted LS on Counter of UEs Registering Network Slice | C4-204421 | LS in | Yes |
Yes
| replied to | No | |||
S5‑206298 | Reply to: Resubmitted LS on Counter of UEs Registering Network Slice | China mobile | LS out | approval | Yes |
Yes
| revised | No | S5‑206346 | S5‑206148 | ||
S5‑206346 | Reply to: Resubmitted LS on Counter of UEs Registering Network Slice | China mobile | LS out | approval | Yes |
Yes
| approved | No | S5‑206298 | |||
S5‑206016 | LS ccSA5 on response to TCCA on Public Safety | GSMA | LS in | Yes |
Yes
| noted | No | |||||
S5‑206017 | LS to SA5 on Meeting minutes of Cross SDO Collaboration Workshop on Autonomous Networks & access to workshop materials | TM Forum | LS in | Yes |
Yes
| noted | No | |||||
S5‑206021 | LS to SA5 on Slice information collection | S2-2008034 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑206022 | Reply LS to SA5 on Counter of UEs Registering Network Slice | S2-2008238 | LS in | Yes |
Yes
| noted | No | |||||
S5‑206039 | Reply LS on Slice Information collection | Samsung Electronics France SA | LS out | Agreement | Yes |
Yes
| revised | No | S5‑206299 | |||
S5‑206299 | Reply LS on Slice Information collection | Samsung Electronics France SA | LS out | Agreement | Yes |
Yes
| approved | No | S5‑206039 | |||
S5‑206148 | Reply LS on Counter of UEs Registering Network Slice | China Mobile Com. Corporation | LS out | Yes |
Yes
| revised | No | S5‑206298 | ||||
5.4 | SA5 meeting calendar | S5‑206010 | SA5 meeting calendar | WG Chair | other | Yes |
Yes
| noted | No | |||
S5‑206282 | SA5 meeting calendar | Ericsson LM | other | Discussion | No |
Yes
| withdrawn | Yes | ||||
6 | OAM&P |   | ||||||||||
6.1 | OAM&P Plenary | S5‑206004 | OAM&P action list | WG vice Chair (Huawei) | other | Yes |
Yes
| noted | No | |||
S5‑206005 | agenda_with_Tdocs_sequence_proposal_OAM | WG Vice Chair | agenda | Yes |
Yes
| noted | No | |||||
S5‑206006 | OAM Exec Report | WG Vice Chair | report | No |
No
| reserved | No | |||||
S5‑206007 | OAM Chair notes and conclusions | WG Chair | report | No |
No
| reserved | No | |||||
S5‑206013 | List of DraftCR input and output | WG Chair | other | Yes |
Yes
| noted | No | |||||
S5‑206014 | Resubmitted LS on O-RAN – 3GPP Cooperation on Management Services | O-RAN | LS in | Yes |
Yes
| postponed | No | |||||
S5‑206018 | Reply LS to SA5 on dynamic 5QIs | S2-2006930 | LS in | Yes |
Yes
| noted | No | |||||
S5‑206019 | LS ccSA5 on Clarification on URLLC QoS Monitoring | S2-2007825 | LS in | Yes |
Yes
| noted | No | |||||
S5‑206023 | Reply LS ccSA5 on SA WG2 assumptions from conclusion of study on architecture aspects for using satellite access in 5G | S2-2008307 | LS in | Yes |
Yes
| noted | No | |||||
S5‑206024 | Reply to S5- 204407 on study items for security on management aspect | S3-202688 | LS in | Yes |
Yes
| noted | No | |||||
S5‑206071 | Collection of useful endorsed document and external communication documents | Huawei Technologies (Korea) | other | Yes |
Yes
| noted | No | S5‑205062 | ||||
S5‑206186 | LS to SA5 on policy models work in ETSI ISG NFV | ETSI ISG NFV | LS in | Yes |
Yes
| replied to | No | |||||
S5‑206286 | Reply to: LS to SA5 on policy models work in ETSI ISG NFV | China Mobile | LS out | approval | Yes |
Yes
| approved | No | ||||
S5‑206257 | Discussion paper on SA5 Requirements and Use Case template | SA5 Vice Chair (Huawei), SA5 Chair | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑206280 | Reply LS ccSA5 on SA WG2 assumptions from conclusion of study on architecture aspects for using satellite access in 5G | R3-207062 | LS in | Yes |
Yes
| noted | No | |||||
S5‑206287 | Reply LS on the user consent for trace reporting | R2-2010894 | LS in | discussion | Yes |
Yes
| postponed | No | ||||
S5‑206288 | LS on PCI conflict detection and reassignment | R3-206979 | LS in | discussion | Yes |
Yes
| noted | No | ||||
S5‑206289 | Reply LS on on energy efficiency | R3-207014 | LS in | discussion | Yes |
Yes
| noted | No | ||||
S5‑206290 | Reply LS on QoS Monitoring for URLLC | R3-207177 | LS in | discussion | Yes |
Yes
| postponed | No | ||||
S5‑206291 | LS on Framework for QoE Measurement Collection | R3-207189 | LS in | discussion | Yes |
Yes
| noted | No | ||||
S5‑206292 | LS to SA5 on MDT Stage 2 and Stage 3 alignment | R3-207222 | LS in | discussion | Yes |
Yes
| replied to | No | ||||
S5‑206297 | Reply to: LS to SA5 on MDT Stage 2 and Stage 3 alignment | Ericsson | LS out | approval | Yes |
Yes
| approved | No | ||||
S5‑206293 | Reply LS on URI for streaming trace reporting in LTE | R3-207232 | LS in | discussion | Yes |
Yes
| noted | No | ||||
S5‑206294 | Response to LS Reply on Enhancement of RAN Slicing | R3-207236 | LS in | discussion | Yes |
Yes
| postponed | No | ||||
S5‑206351 | Presentation sheet for TR28.808 | TNO | TS or TR cover | Approval | Yes |
Yes
| approved | No | ||||
6.2 | New OAM&P Work Item proposals | S5‑206043 | New WID for Management Aspects of 5G Network Sharing | China Unicom | WID new | Approval | No |
Yes
| withdrawn | Yes | ||
S5‑206044 | New WID for Management Aspects of 5G Network Sharing | China Unicom | WID new | Approval | Yes |
Yes
| revised | No | S5‑206304 | |||
S5‑206304 | New WID for Management Aspects of 5G Network Sharing | China Unicom | WID new | Approval | Yes |
Yes
| agreed | No | S5‑206044 | |||
S5‑206069 | YANG NRM for Network Slicing | Cisco Systems Belgium | WID new | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑206074 | GPB for File based Trace Format in 5G | Ericsson LM | WID new | Agreement | Yes |
Yes
| revised | No | S5‑206302 | |||
S5‑206302 | GPB for File based Trace Format in 5G | Ericsson LM | WID new | Agreement | Yes |
YesNoted due to the lack of minimum supporting companies (4).
| noted | No | S5‑206074 | |||
S5‑206076 | Add GPB trace record for file based support | Ericsson LM | CR | Approval | Yes |
Yes
| revised | No | S5‑206303 | |||
S5‑206303 | Add GPB trace record for file based support | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | S5‑206076 | |||
S5‑206273 | New SID on CI-CD support for network slicing | Lenovo Mobile Com. Technology | SID new | Yes |
Yes
| noted | No | |||||
6.3 | OAM&P Maintenance and Rel-16 small Enhancements (only Rel-16 CRs or earlier) | S5‑206031 | Move and update content of clause 4.1.1 to 28.535 | Ericsson LM, Deutsche Telekom, NEC | CR | Approval | Yes |
Yes
| agreed | No | S5‑205397 | |
S5‑206032 | Add description of Communication service assurance service coming from 28.536 | Ericsson LM, Deutsche Telekom, NEC | CR | Approval | Yes |
Yes
| revised | No | S5‑206320 | |||
S5‑206320 | Add description of Communication service assurance service coming from 28.536 | Ericsson LM, Deutsche Telekom, NEC | CR | Approval | Yes |
Yes
| agreed | No | S5‑206032 | |||
S5‑206034 | Correction of NRM YANG errors | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| revised | No | S5‑206308 | |||
S5‑206308 | Correction of NRM YANG errors | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| agreed | No | S5‑206034 | |||
S5‑206035 | Correction of NRM YANG errors | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| revised | No | S5‑206309 | |||
S5‑206309 | Correction of NRM YANG errors | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| agreed | No | S5‑206035 | |||
S5‑206036 | YANG improvements | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑206037 | YANG improvements | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑206045 | Add Annex on state management | Ericsson, Deutsche Telekom | CR | Approval | Yes |
Yes
| revised | No | S5‑206325 | |||
S5‑206325 | Add Annex on state management | Ericsson, Deutsche Telekom | CR | Approval | Yes |
Yes
| agreed | No | S5‑206045 | |||
S5‑206046 | Add serviceProfileId and sliceProfileId to stage 3 yaml | Ericsson, Deutsche Telekom | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑206049 | draft CR Implement Assurance Closed Loop model changes | Ericsson, Deutsche Telekom | other | Approval | Yes |
Yes
| revised | No | S5‑206333 | |||
S5‑206333 | draft CR Implement Assurance Closed Loop model changes | Ericsson, Deutsche Telekom | draftCR | Approval | Yes |
Yes
| approved | No | S5‑206049 | |||
S5‑206334 | Rel-16 CR TS 28.536 Implement Assurance Closed Loop model changes | Ericsson, Deutsche Telekom | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑206050 | Rel-17 CR 32.425 addition of SINR measurement | China Mobile Com. Corporation | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑206051 | Update figure and description of Communication service assurance service | Ericsson LM, Deutsche Telekom, NEC | CR | Approval | Yes |
Yes
| revised | No | S5‑206321 | |||
S5‑206321 | Update figure and description of Communication service assurance service | Ericsson LM, Deutsche Telekom, NEC | CR | Approval | Yes |
Yes
| agreed | No | S5‑206051 | |||
S5‑206052 | Rel-16 CR 28.313 Correct Distributed PCI optimization | Ericsson France S.A.S | CR | Approval | Yes |
Yes
| revised | No | S5‑206316 | S5‑205141 | ||
S5‑206316 | Rel-17 CR 28.313 Correct Distributed PCI optimization | Ericsson France S.A.S | CR | Approval | Yes |
Yes
| agreed | No | S5‑206052 | |||
S5‑206053 | Rel-16 CR 28.536 Observation of closed loop assurance loop | Huawei | other | Agreement | Yes |
Yes
| merged | No | S5‑206333 | |||
S5‑206054 | Rel-16 CR 28.536 Clarify valid values for AssuranceTarget | Huawei | other | Agreement | Yes |
Yes
| revised | No | S5‑206324 | |||
S5‑206324 | Input to draft CR 28.536 Clarify valid values for AssuranceTarget | Huawei | other | Agreement | Yes |
Yes
| approved | No | S5‑206054 | |||
S5‑206067 | Rel-16 CR 28.541 Move Distributed PCI control IOC from DU to CU | Ericsson France S.A.S | CR | Approval | Yes |
Yes
| revised | No | S5‑206310 | S5‑205142 | ||
S5‑206310 | Rel-16 CR 28.541 Move Distributed PCI control IOC from DU to CU | Ericsson France S.A.S | CR | Approval | Yes |
Yes
| agreed | No | S5‑206067 | |||
S5‑206068 | Rel-17 CR 28.541 Move Distributed PCI control IOC from DU to CU | Ericsson France S.A.S | CR | Approval | Yes |
Yes
| revised | No | S5‑206311 | S5‑205143 | ||
S5‑206311 | Rel-17 CR 28.541 Move Distributed PCI control IOC from DU to CU | Ericsson France S.A.S | CR | Approval | Yes |
Yes
| agreed | No | S5‑206068 | |||
S5‑206070 | Rel-16 CR 28.532 Fix inconsistencies in guidelines for integration with ONAP VES | Nokia, Orange, AT&T | CR | Approval | Yes |
Yes
| revised | No | S5‑206318 | |||
S5‑206318 | Rel-16 CR 28.532 Fix inconsistencies in guidelines for integration with ONAP VES | Nokia, Orange, AT&T | CR | Approval | Yes |
Yes
| agreed | No | S5‑206070 | |||
S5‑206072 | Rel-16 CR TS 28.532 Update generic streaming MnS | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑205386 | |||
S5‑206073 | Rel-16 CR TS 28.550 Update attribute measType used in Annex C | HUAWEI Technologies Japan K.K. | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑206075 | Add serviceProfileId and sliceProfileId to stage 3 yaml | Ericsson, Deutsche Telekom | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑206077 | Rel-16 CR 28.552 Add PCI related measurement | Intel Corporation (UK) Ltd | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑206078 | Rel-16 CR 28.313 Correct the PCI notifications | Intel Corporation (UK) Ltd | CR | Approval | Yes |
Yes
| merged | No | S5‑206316 | |||
S5‑206079 | Rel-16 CR 28.541 Add stage 2 solution for PCI notification attributes | Intel Corporation (UK) Ltd | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑206080 | Rel-16 CR 28.541 Add stage 2 solution for PCI notification attributes | Intel Corporation (UK) Ltd | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑206081 | Rel-16 CR 28.541 Add stage 3 solution for PCI notification attributes | Intel Corporation (UK) Ltd | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑206095 | Rel-16 CR TS 28.622 Correct the attributes description of the IOCs inherited from Top and Top_ | ZTE Corporation | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑206131 | Addition of MO SMS mesurements for SMSF | China Mobile Com. Corporation | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑206132 | Addition of Registration mesurements for SMSF | China Mobile Com. Corporation | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑206133 | Rel-16 CR 28.552 Correction of paging measurements | Ericsson LM | CR | Approval | Yes |
Yes
| revised | No | S5‑206306 | |||
S5‑206306 | Rel-16 CR 28.552 Correction of paging measurements | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | S5‑206133 | |||
S5‑206134 | Rel-16 CR 28.552 Add missing paging discard measurements | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑206135 | Rel-17 CR 28.552 Correction of paging measurements | Ericsson LM | CR | Approval | Yes |
Yes
| revised | No | S5‑206307 | |||
S5‑206307 | Rel-17 CR 28.552 Correction of paging measurements | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | S5‑206135 | |||
S5‑206136 | Rel-17 CR 28.552 Add missing paging discard measurements | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑206137 | Rel-16 CR TS 28.552 Correct measurements related to QoS Flow release and DRB release | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑206138 | Rel-16 CR 28.554 Correction and alignment of Retainability KPIs definitions | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑206140 | Rel-16 CR 28.554 Add missing KPI for inter system Handover success rate | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑206141 | Rel-17 CR TS 28.552 Correct measurements related to QoS Flow release and DRB release | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑206142 | Rel-17 CR 28.554 Correction and alignment of Retainability KPIs definitions | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑206143 | Rel-17 CR 28.554 Add missing KPI for inter system Handover success rate | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑206149 | Delete the KPI of Registered subscribers of network and network slice through UDM | China Mobile Com. Corporation | CR | Yes |
Yes
| not pursued | No | |||||
S5‑206157 | Rel-16 CR 28.532 Correct small errors in the Fault MnS (REST SS) | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑206319 | |||
S5‑206319 | Rel-16 CR 28.532 Correct small errors in the Fault MnS (REST SS) | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑206157 | |||
S5‑206160 | Rel-16 CR 28.532 Align ProvMnS data type names to UpperCamel (REST SS, OpenAPI definition) | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑206162 | Rel-16 CR 28.623 Correct and add types in comDefs.yaml (OpenAPI definition) | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑206328 | |||
S5‑206328 | Rel-16 CR 28.623 Correct and add types in comDefs.yaml (OpenAPI definition) | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑206162 | |||
S5‑206164 | Rel-16 CR 28.623 Correct validation errors in genericNrm.yaml (OpenAPI definition) | Nokia, Nokia Shanghai Bell | CR | No |
Yes
| withdrawn | Yes | |||||
S5‑206165 | Rel-16 CR 32.158 Correct REST SS specification template | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑206169 | Rel-16 CR TS 28.535 Add lifecycle management of control loops | Huawei Technologies Japan K.K. | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑206322 | Rel-16 input draftCR TS 28.535 Add lifecycle management of control loops | Huawei Technologies Japan K.K. | other | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑206181 | Rel-16 CR TS 28.535 Update open control loops | Huawei Technologies Japan K.K. | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑206183 | Rel-16 CR TS 28.536 Update SLS Assurance Procedure | Huawei Technologies Japan K.K. | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑206184 | Rel-16 CR TS 28.530 Add the chapter of high level features | Huawei Telecommunication India | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑206185 | Rel-16 CR TS 28.536 Update coslaNrm_yml | Huawei Technologies Japan K.K. | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑206187 | Rel-16 CR TS 28.530 add requirements of closed loop SLS assurance | Huawei Telecommunication India | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑206317 | Input to draftCR TS 28.530 add requirements of closed loop SLS assurance | Huawei Telecommunication India | other | Agreement | Yes |
Yes
| approved | No | ||||
S5‑206188 | Rel-16 CR TS 28.533 Add example of closed loop SLS assurance | Huawei Telecommunication India | CR | Agreement | Yes |
Yes
| revised | No | S5‑206330 | |||
S5‑206330 | Rel-16 CR TS 28.533 Add example of closed loop SLS assurance | Huawei Telecommunication India | CR | Agreement | Yes |
Yes
| agreed | No | S5‑206188 | |||
S5‑206202 | Rel-16 CR 28.532 Extend object creation method with id selection by the MnS producer (stage 2) | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | S5‑205157 | |||
S5‑206203 | Rel-16 CR 28.532 Extend object creation method with id selection by the MnS producer (REST SS, OpenAPI definition) | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | S5‑205269 | |||
S5‑206221 | Rel-16 CR 28.310 Correction on general descriptions of centralized energy saving activation and deactivation | Huawei, Orange | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑206222 | Rel-16 CR 28.310 Corrections on distributed ES solution | Huawei, Orange | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑206223 | Rel-16 CR 28.310 Correction on general descriptions of distributed energy saving activation and deactivation | Huawei, Orange | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑206224 | Discussion on AddRRMPolicyRatiointoSliceProfile | China Mobile Com. Corporation | discussion | Yes |
Yes
| noted | No | |||||
S5‑206226 | Add RRMPolicyRatiointoSliceProfile | China Mobile Com. Corporation | CR | Yes |
Yes
| not pursued | No | |||||
S5‑206236 | Correct trace target parameter for trace control in stage 3 | Ericsson LM,Nokia | CR | Approval | Yes |
Yes
| revised | No | S5‑206313 | |||
S5‑206313 | Correct trace target parameter for trace control in stage 3 | Ericsson LM,Nokia | CR | Approval | Yes |
Yes
| agreed | No | S5‑206236 | |||
S5‑206237 | Correct 5G trace parameter for trace control | Ericsson LM, Nokia | CR | Yes |
Yes
| revised | No | S5‑206314 | ||||
S5‑206314 | Correct 5G trace parameter for trace control | Ericsson LM, Nokia | CR | - | Yes |
Yes
| agreed | No | S5‑206237 | |||
S5‑206238 | Rel-16 CR TS 28.310 Remove distributed scenario from inter-RAT energy saving use case | Orange | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑206240 | Correction of reference list and adding references in the document | Ericsson LM | CR | Approval | Yes |
Yes
| revised | No | S5‑206331 | |||
S5‑206331 | Correction of reference list and adding references in the document | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | S5‑206240 | |||
S5‑206241 | Correction of reference list and adding references in the document | Ericsson LM | CR | Yes |
Yes
| revised | No | S5‑206332 | ||||
S5‑206332 | Correction of reference list and adding references in the document | Ericsson LM | CR | - | Yes |
Yes
| agreed | No | S5‑206241 | |||
S5‑206242 | Correction of reference in the document | Ericsson LM | CR | Yes |
Yes
| agreed | No | |||||
S5‑206243 | Correction of reference in the document | Ericsson LM | CR | Yes |
Yes
| agreed | No | |||||
S5‑206244 | Correction of reference in the document | Ericsson LM | CR | Yes |
Yes
| agreed | No | |||||
S5‑206245 | Correction of reference in the document | Ericsson LM | CR | Yes |
Yes
| agreed | No | |||||
S5‑206256 | Rel-16 28.541 Proposal on clarification of ServiceProfile representations | Ericsson LM | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑206329 | |||
S5‑206329 | Rel-16 28.541 Proposal on clarification of ServiceProfile representations | Ericsson LM | discussion | Endorsement | Yes |
Yes
| endorsed | No | S5‑206256 | |||
S5‑206259 | Remove incorrect S-NSSAI definition from YANG SS | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| revised | No | S5‑206315 | |||
S5‑206315 | Remove incorrect S-NSSAI definition from YANG SS | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| agreed | No | S5‑206259 | |||
S5‑206260 | Fix incorrect reference in notification template. | Ericsson LM | CR | Approval | Yes |
Yes
| revised | No | S5‑206305 | |||
S5‑206305 | Fix incorrect reference in notification template. | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | S5‑206260 | |||
S5‑206262 | Update notifyThresholdCrossing to be a common notification. | Ericsson LM | CR | Approval | Yes |
Yes
| revised | No | S5‑206312 | |||
S5‑206312 | Update notifyThresholdCrossing to be a common notification. | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | S5‑206262 | |||
S5‑206265 | Update notifyThresholdCrossing to be a common notification. | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑206266 | Update notifyThresholdCrossing to be a common notification. | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑206268 | Update notifyThresholdCrossing to be a common notification. | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑206270 | pLMNInfoList faulty attribute definition | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑206271 | pLMNInfoList faulty attribute definition | Ericsson Hungary Ltd | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑206284 | Rel-16 CR 28.541 Fix OpenAPI compilation errors in NRM | Nokia | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑206285 | Rel-17 CR 28.541 Fix OpenAPI compilation errors in NRM | Nokia | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑206295 | Rel-16 CR 28.541 CR fix containment relationship for EP_Transport IOC | Nokia | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑206296 | Rel-17 CR 28.541 CR fix containment relationship for EP_Transport IOC | Nokia | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑206349 | Draft CR TS 28.536 | Ericsson | draftCR | Approval | Yes |
Yes
| approved | No | ||||
6.4 | Rel-17 Operations, Administration, Maintenance and Provisioning (OAM&P) |   | ||||||||||
6.4.1 | Autonomous network levels | S5‑206167 | Add concept of autonomous network and autonomous network level | HUAWEI,China Mobile | pCR | Approval | Yes |
Yes
| revised | No | S5‑206352 | |
S5‑206352 | Add concept of autonomous network and autonomous network level | HUAWEI,China Mobile | pCR | Approval | Yes |
Yes
| approved | No | S5‑206167 | |||
S5‑206170 | pCR TS 28.100 Add use case and requirements for coverage optimization | HUAWEI,China Mobile | pCR | Approval | Yes |
Yes
| revised | No | S5‑206353 | |||
S5‑206353 | pCR TS 28.100 Add use case and requirements for coverage optimization | HUAWEI,China Mobile | pCR | Approval | Yes |
Yes
| approved | No | S5‑206170 | |||
S5‑206176 | pCR 28.100 Add Introduction | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑206354 | |||
S5‑206354 | pCR 28.100 Add Introduction | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑206176 | |||
S5‑206177 | pCR 28.100 Add definition for network and service management scenario types | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑206355 | |||
S5‑206355 | pCR 28.100 Add definition for network and service management scenario types | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑206177 | |||
S5‑206178 | pCR 28.100 Add dimensions for evaluating autonomous network levels | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑206356 | |||
S5‑206356 | pCR 28.100 Add dimensions for evaluating autonomous network levels | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑206178 | |||
S5‑206179 | pCR 28.100 Add framework approach for evaluating autonomous network levels | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑206357 | |||
S5‑206357 | pCR 28.100 Add framework approach for evaluating autonomous network levels | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑206179 | |||
S5‑206180 | pCR 28.100 Update skeleton for clause 5 | China Mobile, Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑206229 | pCR 28.100 Add use case network converage planning | ZTE Corporation | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑206342 | draft TS 28.100 | China Mobile | draft TS | Approval | Yes |
Yes
| approved | No | ||||
6.4.2 | Intent driven management service for mobile networks | S5‑206047 | Rel-17 CR 28.812 Modification to Figure 4.4-1 | China Mobile Com. Corporation | CR | Approval | Yes |
Yes
| not pursued | No | ||
S5‑206048 | Rel-17 CR 28.812 Modification to Figure 6.2-1 | China Mobile Com. Corporation | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑206214 | Rel-17 CR TR28.812 Address the issues requested by EditHelp | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑206215 | pCR TS 28312 Update Clause 4.1.3 Intent categorizes based on management scenario types | Huawei, China Mobile | pCR | Approval | Yes |
Yes
| revised | No | S5‑206358 | |||
S5‑206358 | pCR TS 28312 Update Clause 4.1.3 Intent categorizes based on management scenario types | Huawei, China Mobile | pCR | Approval | Yes |
Yes
| approved | No | S5‑206215 | |||
S5‑206216 | pCR TS 28312 Update Clause 4.1.1 Introduction | Huawei, China Mobie, Ericsson, China Unicom | pCR | Approval | Yes |
Yes
| revised | No | S5‑206359 | |||
S5‑206359 | pCR TS 28312 Update Clause 4.1.1 Introduction | Huawei, China Mobie, Ericsson, China Unicom | pCR | Approval | Yes |
Yes
| approved | No | S5‑206216 | |||
S5‑206217 | pCR TS 28312 Add relation of intent driven management and policy driven management. | Huawei,Ericsson, China Mobile, China Unicom | pCR | Approval | Yes |
Yes
| revised | No | S5‑206360 | |||
S5‑206360 | pCR TS 28312 Add relation of intent driven management and policy driven management. | Huawei,Ericsson, China Mobile, China Unicom | pCR | Approval | Yes |
Yes
| approved | No | S5‑206217 | |||
S5‑206218 | pCR TS 28312 Add use case and requirements for coverage optimization | Huawei, China Telecom | pCR | Approval | Yes |
Yes
| revised | No | S5‑206361 | |||
S5‑206361 | pCR TS 28312 Add use case and requirements for coverage optimization | Huawei, China Telecom | pCR | Approval | Yes |
Yes
| approved | No | S5‑206218 | |||
S5‑206219 | pCR TS 28312 Add use case and requirements for RAN UE throughut optimization | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑206362 | |||
S5‑206362 | pCR TS 28312 Add use case and requirements for RAN UE throughut optimization | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑206219 | |||
S5‑206220 | pCR TS 28312 Add use case and requirements for radio network deployment | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑206363 | |||
S5‑206363 | pCR TS 28312 Add use case and requirements for radio network deployment | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑206220 | |||
S5‑206341 | draft TS 28.312 | Huawei | draft TS | Approval | Yes |
Yes
| approved | No | ||||
6.4.3 | Network policy management for 5G mobile networks based on NFV scenarios | S5‑206027 | pCR 28.555 add specification level use cases | China Mobile Com. Corporation | pCR | Yes |
Yes
| revised | No | S5‑206364 | ||
S5‑206364 | pCR 28.555 add specification level use cases | China Mobile Com. Corporation | pCR | - | Yes |
Yes
| approved | No | S5‑206027 | |||
S5‑206028 | pCR 28.555 Editorial improvements | China Mobile Com. Corporation | pCR | Yes |
Yes
| approved | No | |||||
S5‑206029 | pCR 28.556 Add skeleton | China Mobile Com. Corporation | pCR | Yes |
Yes
| revised | No | S5‑206365 | ||||
S5‑206365 | pCR 28.556 Add skeleton | China Mobile Com. Corporation | pCR | - | Yes |
Yes
| approved | No | S5‑206029 | |||
S5‑206030 | pCR 28.556 add scope | China Mobile Com. Corporation | pCR | Yes |
Yes
| approved | No | |||||
S5‑206033 | Presentation of Spec 28.555 to SA for Approval | China Mobile Com. Corporation | WI status report | Yes |
Yes
| noted | No | |||||
S5‑206339 | draft TS 28.556 | China Mobile | draft TS | Approval | Yes |
Yes
| approved | No | ||||
S5‑206340 | draft TS 28.555 | China Mobile | draft TS | Approval | Yes |
Yes
| approved | No | ||||
6.4.4 | Enhanced Closed loop SLS Assurance | S5‑206151 | Add use case of network resource usage and performance prediction assisted SLS communication service Assurance | China Mobile Com. Corporation | CR | Yes |
Yes
| revised | No | S5‑206367 | ||
S5‑206367 | Add use case of network resource usage and performance prediction assisted SLS communication service Assurance | China Mobile Com. Corporation | CR | - | Yes |
Yes
| agreed | No | S5‑206151 | |||
S5‑206173 | Rel-17 draftCR TS 28.535 Add concept of closed control loop governing and monitoring | HUAWEI Technologies Japan K.K. | draftCR | Agreement | Yes |
Yes
| noted | No | ||||
S5‑206350 | Rel-17 CR TS 28.535 Add concept of closed control loop governing and monitoring | HUAWEI Technologies Japan K.K. | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑206204 | Discussion paper for coordination between control loops | Huawei Technologies Japan K.K. | discussion | Discussion | Yes |
Yes
| noted | No | ||||
S5‑206205 | Rel-17 CR TS 28.535 Coordination between control loops | Huawei Technologies Japan K.K. | draftCR | Agreement | Yes |
Yes
| revised | No | S5‑206326 | |||
S5‑206326 | Input to draftCR TS 28.535 Coordination between control loops | Huawei Technologies Japan K.K. | draftCR | Agreement | Yes |
Yes
| approved | No | S5‑206205 | |||
S5‑206210 | Rel-17 CR TS 28.535 Management types for control loop | Huawei Technologies Japan K.K. | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑206275 | Rel17 CR 28.535 Add use case and req for CL execution supervision | Lenovo Mobile Com. Technology, Huawei | CR | Yes |
Yes
| not pursued | No | |||||
S5‑206366 | Rel17 Input to draftCR 28.535 Add use case and req for CL execution supervision | Lenovo Mobile Com. Technology, Huawei | other | - | Yes |
Yes
| approved | No | ||||
S5‑206276 | Rel17 CR 28.535 Add use case for limiting actions of an assurance loop | Lenovo Mobile Com. Technology, Motorola Mobility | CR | Yes |
Yes
| revised | No | S5‑206368 | ||||
S5‑206368 | Rel17 CR 28.535 Add use case for limiting actions of an assurance loop | Lenovo Mobile Com. Technology, Motorola Mobility | CR | - | Yes |
Yes
| agreed | No | S5‑206276 | |||
S5‑206277 | Rel17 CR 28.535 Add use case for temporarily disabling NWDAF | Lenovo Mobile Com. Technology | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑206278 | Rel17 CR 28.535 Add use case for triggering assurance loop state change | Lenovo Mobile Com. Technology, Motorola Mobility | CR | Yes |
Yes
| revised | No | S5‑206369 | ||||
S5‑206369 | Rel17 CR 28.535 Add use case for triggering assurance loop state change | Lenovo Mobile Com. Technology, Motorola Mobility | CR | - | Yes |
Yes
| agreed | No | S5‑206278 | |||
S5‑206345 | DraftCR for 6.4.4 eCOSLA - TS 28.535 | Ericsson | draftCR | Approval | Yes |
Yes
| approved | No | ||||
6.4.5 | Self-Organizing Networks (SON) for 5G networks | S5‑206082 | Rel-17 CR 28.313 Add LBO use cases, requirements, and related information | Intel Corporation (UK) Ltd | CR | Approval | Yes |
Yes
| not pursued | No | ||
S5‑206272 | Rel-16 CR 28.313 Add Load Balancing Optimization Requirements and Use Case | Nokia Germany | CR | Approval | Yes |
Yes
| not pursued | No | ||||
6.4.6 | Enhancement of Handover Optimization | S5‑206209 | Discussion paper on Management of Conditional Handover | Ericsson France S.A.S | discussion | Endorsement | Yes |
Yes
| endorsed | No | ||
S5‑206212 | Rel-17 CR 28.313 CHO requirements | Ericsson France S.A.S | other | Approval | Yes |
Yes
| noted | No | ||||
6.4.7 | Enhancements on EE for 5G networks | S5‑206124 | Discussion Paper on providing cell energySaving Status information to NWDAF | China Telecom Corporation Ltd. | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑206373 | |
S5‑206373 | Discussion Paper on providing cell energySaving Status information to NWDAF | China Telecom Corporation Ltd. | discussion | Endorsement | Yes |
Yes
| endorsed | No | S5‑206124 | |||
S5‑206206 | Rel-17 CR TS 28.554 Add EE KPI definitions for network slices | Orange, AT&T, Huawei, Deutsche Telekom, China Unicom | CR | Approval | Yes |
Yes
| revised | No | S5‑206370 | |||
S5‑206370 | Rel-17 CR TS 28.554 Add EE KPI definitions for network slices | Orange, AT&T, Huawei, Deutsche Telekom, China Unicom | CR | Approval | Yes |
Yes
| agreed | No | S5‑206206 | |||
S5‑206208 | LS to ETSI EE EEPS and ITU-T Q6/5 on Network Slice EE KPIs | Orange | LS out | Approval | Yes |
Yes
| revised | No | S5‑206371 | |||
S5‑206371 | LS to ETSI EE EEPS and ITU-T Q6/5 on Network Slice EE KPIs | Orange | LS out | Approval | Yes |
Yes
| revised | No | S5‑206446 | S5‑206208 | ||
S5‑206446 | LS to ETSI EE EEPS and ITU-T Q6/5 on Network Slice EE KPIs | Orange | LS out | Approval | Yes |
Yes
| approved | No | S5‑206371 | |||
S5‑206211 | LS to GSMA 5GJA on Network Slice EE KPIs | Orange | LS out | Approval | Yes |
Yes
| revised | No | S5‑206372 | |||
S5‑206372 | LS to GSMA 5GJA on Network Slice EE KPIs | Orange | LS out | Approval | Yes |
Yes
| revised | No | S5‑206447 | S5‑206211 | ||
S5‑206447 | LS to GSMA 5GJA on Network Slice EE KPIs | Orange | LS out | Approval | Yes |
Yes
| approved | No | S5‑206372 | |||
S5‑206225 | Rel-16 CR TS 28.310 Remove the distributed scenario from the inter-RAT energy saving use case | Orange | CR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑206239 | Introducing ES probing procedure in TS 28.310 | KPN N.V. | draftCR | Approval | Yes |
Yes
| noted | No | ||||
6.4.8 | Discovery of management services in 5G | S5‑206040 | Rel-17 CR 28.532 Register and Query Operation | Samsung Electronics France SA | other | Agreement | Yes |
Yes
| noted | No | ||
S5‑206041 | Rel-17 CR 28.533 Registration and De-registration Use Case | Samsung Electronics France SA | other | Agreement | Yes |
Yes
| noted | No | ||||
S5‑206055 | Rel-17 CR 28.533 Clarify Management Service data | Huawei | other | Approval | Yes |
Yes
| revised | No | S5‑206374 | |||
S5‑206374 | Rel-17 CR 28.533 Clarify Management Service data | Huawei | other | Approval | Yes |
Yes
| approved | No | S5‑206055 | |||
S5‑206056 | Rel-17 CR 28.533 Add usecase for MnS publish | Huawei | other | Approval | Yes |
Yes
| noted | No | ||||
S5‑206057 | Rel-17 CR 28.533 Correct inconsistent terminology | Huawei | other | Approval | Yes |
Yes
| noted | No | ||||
S5‑206344 | Rel-16 CR 28.533 Correct inconsistent terminology | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑206348 | DraftCR for 6.4.8 5GDMS - TS 28.533 | Huawei | draftCR | Approval | Yes |
Yes
| approved | No | ||||
6.5 | OAM&P Studies |   | ||||||||||
6.5.1 | Study on enhancement of Management Data Analytics Service | S5‑206026 | Rel-17 pCR 28.809 Update potential solutions for the MDA assisted energy saving analysis | China Telecom Corporation Ltd. | pCR | Approval | Yes |
Yes
| revised | No | S5‑206375 | |
S5‑206375 | Rel-17 pCR 28.809 Update potential solutions for the MDA assisted energy saving analysis | China Telecom Corporation Ltd. | pCR | Approval | Yes |
Yes
| approved | No | S5‑206026 | |||
S5‑206038 | Add conclusion for resource utilization analytics use case | ETRI | pCR | Approval | Yes |
Yes
| merged | No | S5‑206377 | |||
S5‑206042 | pCR 28.809 HO Optimization based on UE Load | Samsung Electronics France SA | pCR | Agreement | Yes |
Yes
| revised | No | S5‑206380 | |||
S5‑206380 | pCR 28.809 HO Optimization based on UE Load | Samsung Electronics France SA | pCR | Agreement | Yes |
Yes
| approved | No | S5‑206042 | |||
S5‑206058 | pCR 28.809 Add analysis on agreed use cases | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑206059 | pCR 28.809 Add key issue in recommondation | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑206060 | pCR 28.809 suggested conclustion for Alarm incident analysis | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑206385 | |||
S5‑206385 | pCR 28.809 suggested conclustion for Alarm incident analysis | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑206060 | |||
S5‑206061 | pCR 28.809 conclusion for NAS congestion control | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑206386 | |||
S5‑206386 | pCR 28.809 conclusion for NAS congestion control | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑206061 | |||
S5‑206087 | pCR 28.809 Update solutions on subscription and reporting of Management Data Analytics Reports | Intel Ireland | pCR | Approval | Yes |
Yes
| revised | No | S5‑206383 | |||
S5‑206383 | pCR 28.809 Update solutions on subscription and reporting of Management Data Analytics Reports | Intel Ireland | pCR | Approval | Yes |
Yes
| approved | No | S5‑206087 | |||
S5‑206088 | pCR 28.809 Update solutions on request of Management Data Analytics Reports | Intel Ireland | pCR | Approval | Yes |
Yes
| revised | No | S5‑206384 | |||
S5‑206384 | pCR 28.809 Update solutions on request of Management Data Analytics Reports | Intel Ireland | pCR | Approval | Yes |
Yes
| approved | No | S5‑206088 | |||
S5‑206089 | pCR 28.809 Add conclusion for coverage issue analysis | Intel Ireland | pCR | Approval | Yes |
Yes
| revised | No | S5‑206378 | |||
S5‑206378 | pCR 28.809 Add conclusion for coverage issue analysis | Intel Ireland | pCR | Approval | Yes |
Yes
| approved | No | S5‑206089 | |||
S5‑206090 | pCR 28.809 Add conclusion for resource utilization analytics | Intel Ireland | pCR | Approval | Yes |
Yes
| revised | No | S5‑206377 | |||
S5‑206377 | pCR 28.809 Add conclusion for resource utilization analytics | Intel Ireland | pCR | Approval | Yes |
Yes
| approved | No | S5‑206090 | |||
S5‑206091 | pCR 28.809 Update solution on MDA assisted energy saving | Intel Ireland | pCR | Approval | Yes |
Yes
| revised | No | S5‑206376 | |||
S5‑206376 | pCR 28.809 Update solution on MDA assisted energy saving | Intel Ireland | pCR | Approval | Yes |
Yes
| approved | No | S5‑206091 | |||
S5‑206092 | Resubmission pCR 28.809 Add solution on MDA ML model training | Intel Ireland | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑206093 | pCR 28.809 Update based on comments provided by Edithelp | Intel Ireland | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑206094 | pCR 28.809 Add general conclusions and recommendations | Intel Ireland | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑206139 | pCR 28.809 Add general conclusions on eMDAS | HuaWei Technologies Co., Ltd | pCR | Yes |
Yes
| noted | No | |||||
S5‑206147 | pCR 28.809 Add the conclusion on coverage issue analysis | HuaWei Technologies Co., Ltd | pCR | Yes |
Yes
| merged | No | S5‑206378 | ||||
S5‑206150 | Update the solution of Jitter analysis | China Mobile Com. Corporation | pCR | Yes |
Yes
| revised | No | S5‑206387 | ||||
S5‑206387 | Update the solution of Jitter analysis | China Mobile Com. Corporation | pCR | - | Yes |
Yes
| approved | No | S5‑206150 | |||
S5‑206153 | pCR 28.809 Add the conclusion on KPI anomaly analysis | HuaWei Technologies Co., Ltd | pCR | Yes |
Yes
| merged | No | S5‑206379 | ||||
S5‑206154 | pCR 28.809 Add the conclusion on Network slice load analysis | HuaWei Technologies Co., Ltd | pCR | Yes |
Yes
| revised | No | S5‑206388 | ||||
S5‑206388 | pCR 28.809 Add the conclusion on Network slice load analysis | HuaWei Technologies Co., Ltd | pCR | - | Yes |
Yes
| approved | No | S5‑206154 | |||
S5‑206155 | pCR 28.809 Add conclulsion on E2E latency analysis | HuaWei Technologies Co., Ltd | pCR | Yes |
Yes
| revised | No | S5‑206389 | ||||
S5‑206389 | pCR 28.809 Add conclulsion on E2E latency analysis | HuaWei Technologies Co., Ltd | pCR | - | Yes |
Yes
| approved | No | S5‑206155 | |||
S5‑206156 | pCR 28.809 update the solution of traffic projection | HuaWei Technologies Co., Ltd | pCR | No |
Yes
| withdrawn | Yes | |||||
S5‑206158 | pCR 28.809 Add the conclusion on service experience analysis | HuaWei Technologies Co., Ltd | pCR | Yes |
Yes
| revised | No | S5‑206390 | ||||
S5‑206390 | pCR 28.809 Add the conclusion on service experience analysis | HuaWei Technologies Co., Ltd | pCR | - | Yes |
Yes
| approved | No | S5‑206158 | |||
S5‑206159 | pCR 28.809 Add the conclusion on throughput analysis | HuaWei Technologies Co., Ltd | pCR | Yes |
Yes
| revised | No | S5‑206391 | ||||
S5‑206391 | pCR 28.809 Add the conclusion on throughput analysis | HuaWei Technologies Co., Ltd | pCR | - | Yes |
Yes
| approved | No | S5‑206159 | |||
S5‑206166 | Load Balancing Optimization Solutions based on Resource Consumption and Service Specifics | Nokia Germany | pCR | Yes |
Yes
| revised | No | S5‑206382 | ||||
S5‑206382 | Load Balancing Optimization Solutions based on Resource Consumption and Service Specifics | Nokia Germany | pCR | - | Yes |
Yes
| approved | No | S5‑206166 | |||
S5‑206171 | pCR 28.809 Add the descriptions of coorditaion between cross domain MDAS and domain MDAS | HuaWei Technologies Co., Ltd | pCR | Yes |
Yes
| noted | No | |||||
S5‑206172 | pCR 28.809 Add the conclusion on resource utilization analysis | HuaWei Technologies Co., Ltd | pCR | Yes |
Yes
| merged | No | S5‑206377 | ||||
S5‑206182 | New use case on slice coverage and throughput optimization | Nokia Germany | pCR | Yes |
Yes
| revised | No | S5‑206392 | ||||
S5‑206392 | New use case on slice coverage and throughput optimization | Nokia Germany | pCR | - | Yes |
Yes
| approved | No | S5‑206182 | |||
S5‑206189 | Load Balancing Optimization Solution for SON | Nokia Germany | pCR | Yes |
Yes
| merged | No | S5‑206382 | ||||
S5‑206207 | Gap analysis for inter-gNB beam selection Optimization | Nokia Germany | pCR | Yes |
Yes
| revised | No | S5‑206393 | ||||
S5‑206393 | Gap analysis for inter-gNB beam selection Optimization | Nokia Germany | pCR | - | Yes |
Yes
| approved | No | S5‑206207 | |||
S5‑206213 | Alarm Malfunction Analytics | Nokia Germany | pCR | Yes |
Yes
| revised | No | S5‑206327 | ||||
S5‑206327 | Alarm Malfunction Analytics | Nokia Germany | pCR | - | Yes |
Yes
| approved | No | S5‑206213 | |||
S5‑206227 | Gap Analysis for Security Risk Assessment | Nokia Germany | pCR | Yes |
Yes
| revised | No | S5‑206394 | ||||
S5‑206394 | Gap Analysis for Security Risk Assessment | Nokia Germany | pCR | - | Yes |
Yes
| approved | No | S5‑206227 | |||
S5‑206235 | pCR 28.809 Add conclusion for fault predication analysis | ZTE Corporation | pCR | Approval | Yes |
Yes
| revised | No | S5‑206395 | |||
S5‑206395 | pCR 28.809 Add conclusion for fault predication analysis | ZTE Corporation | pCR | Approval | Yes |
Yes
| approved | No | S5‑206235 | |||
S5‑206258 | Gap Analysis for Handover Optimization based on UE trajectory | Nokia Germany | pCR | Yes |
Yes
| revised | No | S5‑206381 | ||||
S5‑206381 | Gap Analysis for Handover Optimization based on UE trajectory | Nokia Germany | pCR | - | Yes |
Yes
| approved | No | S5‑206258 | |||
S5‑206263 | Gap Analysis for KPI Anomaly Analysis | Nokia Germany | pCR | Yes |
Yes
| revised | No | S5‑206379 | ||||
S5‑206379 | Gap Analysis for KPI Anomaly Analysis | Nokia Germany | pCR | - | Yes |
Yes
| approved | No | S5‑206263 | |||
S5‑206264 | Gap Analysis for MDA assisted SON coordination | Nokia Germany | pCR | Yes |
Yes
| revised | No | S5‑206396 | ||||
S5‑206396 | Gap Analysis for MDA assisted SON coordination | Nokia Germany | pCR | - | Yes |
Yes
| approved | No | S5‑206264 | |||
S5‑206267 | Gap Analysis for Mobility performance Analysis | Nokia Germany | pCR | Yes |
Yes
| revised | No | S5‑206397 | ||||
S5‑206397 | Gap Analysis for Mobility performance Analysis | Nokia Germany | pCR | - | Yes |
Yes
| approved | No | S5‑206267 | |||
S5‑206274 | Rel 17 pCR - 28.809 MDAS detection of outlying MEs | Lenovo Mobile Com. Technology | pCR | Approval | Yes |
Yes
| revised | No | S5‑206398 | |||
S5‑206398 | Rel 17 pCR - 28.809 MDAS detection of outlying MEs | Lenovo Mobile Com. Technology | pCR | Approval | Yes |
Yes
| approved | No | S5‑206274 | |||
S5‑206338 | draft TR 28.809 | Intel | draft TR | Approval | Yes |
Yes
| approved | No | ||||
6.5.2 | Study on network slice management enhancement (revised to include security aspects) | S5‑206062 | pCR 28.811 Add cross-operator network slicing scenarios | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑206403 | |
S5‑206403 | pCR 28.811 Add cross-operator network slicing scenarios | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑206062 | |||
S5‑206063 | pCR 28.811 Update references and terms | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑206401 | |||
S5‑206401 | pCR 28.811 Update references and terms | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑206063 | |||
S5‑206064 | pCR 28.811 Add cross-operator concept | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑206399 | |||
S5‑206399 | pCR 28.811 Add cross-operator concept | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑206064 | |||
S5‑206065 | pCR 28.811 Update scope to include security aspects | Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑206066 | pCR 28.811 Add end to end concept | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑206400 | |||
S5‑206400 | pCR 28.811 Add end to end concept | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑206066 | |||
S5‑206251 | 28.811 deploy two network slcies by same customer | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑206402 | |||
S5‑206402 | 28.811 deploy two network slcies by same customer | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑206251 | |||
S5‑206252 | 28.811 extend skeleton to include security aspects | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑206337 | draft TR 28.811 | Huawei | draft TR | discussion | Yes |
Yes
| approved | No | ||||
6.5.3 | Study on YANG PUSH | S5‑206279 | 28.818 skeleton | Ericsson Hungary Ltd | draft TR | Approval | Yes |
Yes
| revised | No | S5‑206343 | |
S5‑206343 | 28.818 skeleton | Ericsson Hungary Ltd | draft TR | Approval | Yes |
Yes
| approved | No | S5‑206279 | |||
6.5.4 | Study on access control for management service | S5‑206253 | TR 28.817 skeleton | Nokia Germany | draft TR | Approval | Yes |
Yes
| approved | No | ||
7 | Charging |   | ||||||||||
7.1 | Charging Plenary | S5‑206008 | CH agenda and time plan | WG vice Chair (Nokia) | agenda | Yes |
Yes
| revised | No | S5‑206443 | ||
S5‑206443 | CH agenda and time plan | WG vice Chair (Nokia) | agenda | - | Yes |
Yes
| noted | No | S5‑206008 | |||
S5‑206009 | Charging exec report | WG vice Chair (Nokia) | report | Yes |
Yes
| noted | No | |||||
S5‑206020 | LS to SA5 on 5G ProSe charging | S2-2007947 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑206228 | Ls to SA5 on Alignment of API Versioning System with Semantic Versioning | C4-205484 | LS in | Yes |
Yes
| noted | No | |||||
S5‑206233 | LS reply on LS on 5G ProSe charging | Nokia, Nokia Shanghai Bell | LS out | Approval | Yes |
Yes
| revised | No | S5‑206404 | |||
S5‑206404 | LS reply on LS on 5G ProSe charging | Nokia, Nokia Shanghai Bell | LS out | Approval | Yes |
Yes
| approved | No | S5‑206233 | |||
S5‑206283 | Reply LS ccSA5 on support of stateless NFs | C4-205487 | LS in | discussion | Yes |
Yes
| postponed | No | ||||
7.2 | New Charging Work Item proposals | S5‑206113 | New SID on Charging Aspect of 5G LAN-type Services | Huawei | SID new | Agreement | Yes |
Yes
| revised | No | S5‑206408 | |
S5‑206408 | New SID on Charging Aspect of 5G LAN-type Services | Huawei | SID new | Agreement | Yes |
Yes
| agreed | No | S5‑206113 | |||
S5‑206152 | SID on charging aspects for enhancements of Network Slicing Phase 2 | Matrixx | SID new | Approval | Yes |
Yes
| revised | No | S5‑206445 | |||
S5‑206445 | SID on charging aspects for enhancements of Network Slicing Phase 2 | Matrixx | SID new | Approval | Yes |
Yes
| agreed | No | S5‑206152 | |||
7.3 | Charging Maintenance and Rel-16 small Enhancements | S5‑206096 | Rel-16 CR 32.255 Add Assistance information for Quota Request | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||
S5‑206097 | Rel-16 CR 32.291 Add Assistance Information for Quota Request | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑206098 | Rel-15 CR 32.255 Correction on the QoS inforamtion in PDU Container | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑206099 | Rel-16 CR 32.255 Correction on the QoS inforamtion in PDU Container | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑206417 | |||
S5‑206417 | Rel-16 CR 32.255 Correction on the QoS inforamtion in PDU Container | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑206099 | |||
S5‑206105 | Discussion paper on Non-blocking Mode Control | Huawei | discussion | Discussion | Yes |
Yes
| noted | No | ||||
S5‑206106 | Rel-16 CR 32.291 Add the Charging Control for NB Mode | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑206107 | Rel-16 CR 32.290 Add the General Description for NB Mode | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑206108 | Rel-16 CR 32.290 Add the Charging Control for NB Mode | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑206435 | |||
S5‑206435 | Rel-16 CR 32.290 Add the NB Mode disable | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑206108 | |||
S5‑206109 | Rel-15 CR 32.290 Correction on the Quota Management Mode | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑206110 | Rel-16 CR 32.290 Correction on the Quota Management Mode | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑206444 | |||
S5‑206444 | Rel-16 CR 32.290 Correction on the Quota Management Mode | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑206110 | |||
S5‑206111 | Rel-15 CR 32.255 Correction on the Quota Management Mode | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑206112 | Rel-16 CR 32.255 Correction on the Quota Management Mode | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑206418 | |||
S5‑206418 | Rel-16 CR 32.255 Correction on the Quota Management Mode | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑206112 | |||
S5‑206119 | Discussion on the use of MAP type for PRA information | Huawei | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑206120 | Rel-15 CR TS 32.291 Change map data type for presence area information Option 1 | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑206121 | Rel-15 CR TS 32.291 Change map data type for presence area information Option 2 | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑206144 | Rel-16 CR 32.291 Correction on Storage of YAML files in 3GPP Forge and Copyright | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑206406 | |||
S5‑206406 | Rel-16 CR 32.291 Correction on Storage of YAML files in 3GPP Forge and Copyright | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑206144 | |||
S5‑206145 | Rel-15 CR 32.291 Remove Unnecessary Re-used Data Type | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑206146 | Rel-16 CR 32.291 Remove Unnecessary Re-used Data Type | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑206190 | Rel-16 CR TS 32.255 Correction of PDU session modification flow | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑206419 | |||
S5‑206419 | Rel-16 CR TS 32.255 Correction of PDU session modification flow | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑206190 | |||
S5‑206191 | Rel-16 CR TS 32.298 Correction of cause for record closing | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑206192 | Rel-16 CR TS 32.255 Correction of partial record closing | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑206193 | Rel-16 CR TS 32.291 Correction of trigger type presence and cardinality | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑206194 | Rel-16 CR TS 32.291 Correction of data structure in post response body | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑206195 | Rel-16 CR TS 32.291 Correction of AMBR trigger usage | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑206196 | Rel-16 CR TS 32.291 Correction of not quota management tariff time trigger | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑206197 | Rel-16 CR TS 32.291 Correction of SMS TP status value | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑206230 | Rel-15 CR 32.298 Correction on CauseForRecClosing partial CHF record | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑206231 | Rel-16 CR 32.298 Correction on CauseForRecClosing partial CHF record | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑206232 | Rel-16 CR 32.298 Correction for alignment with drafting rules | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑206246 | Rel-16 CR 32.255 Correction of V-SMF Change in Roaming HR - flows | China Mobile E-Commerce Co. | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑206250 | Rel-16 CR 32.255 Correction of V-SMF Change in Roaming HR - flows | China Mobile E-Commerce Co. | CR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑206254 | Rel-15 CR 32.291 Add missing value to NodeFunctionality for EPC Interworking Charging | Openet Telecom | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑206255 | Rel-15 CR 32.298 Add missing value to NodeFunctionality for EPC Interworking Charging | Openet Telecom | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑206405 | Rel-15 CR 32.291 Update OpenAPI version | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
7.4 | Rel-17 Charging |   | ||||||||||
7.4.1 | IMS Charging in 5G System Architecture | S5‑206122 | Rel-17 CR 32.260 Add service based architecture for offline charging | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑206409 | |
S5‑206409 | Rel-17 CR 32.260 Add service based architecture for offline charging | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑206122 | |||
S5‑206123 | Rel-17 CR 32.275 Add service based architecture for offline charging | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑206410 | |||
S5‑206410 | Rel-17 CR 32.275 Add service based architecture for offline charging | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑206123 | |||
S5‑206161 | Rel-17 CR 32.290 Adding IMS nodes as NF consumers | China Mobile | CR | Approval | Yes |
Yes
| revised | No | S5‑206411 | |||
S5‑206411 | Rel-17 CR 32.290 Adding IMS nodes as NF consumers | China Mobile | CR | Approval | Yes |
Yes
| agreed | No | S5‑206161 | |||
S5‑206163 | Rel-17 CR 32.291 Adding IMS nodes as NF consumers | China Mobile | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑206168 | Rel-17 CR 32.298 Adding IMS nodes as NF consumers | China Mobile | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑206198 | Rel-17 CR TS 32.275 Adding converged charging in relevance table | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑206412 | |||
S5‑206412 | Rel-17 CR TS 32.275 Adding converged charging in relevance table | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑206198 | |||
S5‑206199 | Rel-17 CR TS 32.275 Adding converged charging for supplementary service | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑206413 | |||
S5‑206413 | Rel-17 CR TS 32.275 Adding converged charging for supplementary service | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑206199 | |||
S5‑206261 | Rel-16 CR 32.260 Removal of IMS service based charging interface | Matrixx | CR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑206407 | Rel-17 CR 32.260 Update of IMS nodes supporting Nchf | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑205424 | |||
S5‑206414 | Rel-17 CR 32.260 Update of IMS nodes supporting Nchf | Ericsson | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
7.4.2 | Charging enhancement for URLLC | S5‑206100 | Discussion paper on URLLC Charging | Huawei | discussion | Yes |
Yes
| noted | No | |||
S5‑206101 | Rel-17 CR 32.255 Add Triggers for URLLC Charging | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑206420 | |||
S5‑206420 | Rel-17 CR 32.255 Add Triggers for URLLC Charging | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑206101 | |||
S5‑206102 | Rel-17 CR 32.255 Add Message Flow for URLLC Charging | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑206421 | |||
S5‑206421 | Rel-17 CR 32.255 Add Message Flow for URLLC Charging | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑206102 | |||
S5‑206103 | Rel-17 CR 32.255 Add Charging Information for URLLC Charging | Huawei | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
S5‑206104 | Rel-17 CR 32.255 Add Charging Principle for Usage Reporting | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑206422 | |||
S5‑206422 | Rel-17 CR 32.255 Add Charging Principle for Usage Reporting | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑206104 | |||
7.4.3 | N40 Interface Enhancements to Support GERAN and UTRAN | S5‑206247 | Rel-17 CR 32.240 Add PGW in logical ubiquitous charging architecture- service based interface | China Mobile E-Commerce Co. | CR | Approval | Yes |
Yes
| revised | No | S5‑206415 | |
S5‑206415 | Rel-17 CR 32.240 Add PGW in logical ubiquitous charging architecture- service based interface | China Mobile E-Commerce Co. | CR | Approval | Yes |
Yes
| agreed | No | S5‑206247 | |||
S5‑206248 | Rel-17 CR 32.251 Addition of PGW supporting Nchf interface | China Mobile E-Commerce Co. | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑206249 | Rel-17 CR 32.290 Add PGW as consumer of ConvergedCharging service | China Mobile E-Commerce Co. | CR | Approval | Yes |
Yes
| revised | No | S5‑206416 | |||
S5‑206416 | Rel-17 CR 32.290 Add PGW as consumer of ConvergedCharging service | China Mobile E-Commerce Co. | CR | Approval | Yes |
Yes
| agreed | No | S5‑206249 | |||
7.5 | Charging studies |   | ||||||||||
7.5.1 | Study on charging aspects of Edge Computing | S5‑206025 | Rel-17 pCR 28.815 Introduction of the scope | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑206429 | |
S5‑206429 | Rel-17 pCR 28.815 Introduction of the scope | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑206025 | |||
S5‑206083 | pCR 28.815 Add charging scenarios and key issues on charging for edge enabling resources and services | Intel Ireland | pCR | Approval | Yes |
Yes
| revised | No | S5‑206423 | |||
S5‑206423 | pCR 28.815 Add charging scenarios and key issues on charging for edge enabling resources and services | Intel Ireland | pCR | Approval | Yes |
Yes
| approved | No | S5‑206083 | |||
S5‑206084 | pCR 28.815 Add key issue on charging of 5GS capabilities supporting EC based on monitored QoS | Intel Ireland | pCR | Approval | Yes |
Yes
| revised | No | S5‑206424 | |||
S5‑206424 | pCR 28.815 Add key issue on charging of 5GS capabilities supporting EC based on monitored QoS | Intel Ireland | pCR | Approval | Yes |
Yes
| approved | No | S5‑206084 | |||
S5‑206085 | pCR 28.815 Add potenial requirements and key issues on inter-provider charging for 5GS capabilities supporting EC | Intel Ireland | pCR | Approval | Yes |
Yes
| revised | No | S5‑206425 | |||
S5‑206425 | pCR 28.815 Add potenial requirements and key issues on inter-provider charging for 5GS capabilities supporting EC | Intel Ireland | pCR | Approval | Yes |
Yes
| approved | No | S5‑206085 | |||
S5‑206086 | pCR 28.815 Add possible solutions for end-user charging of 5GS capabilities supporting edge computing | Intel Ireland | pCR | Approval | Yes |
Yes
| revised | No | S5‑206426 | |||
S5‑206426 | pCR 28.815 Add possible solutions for end-user charging of 5GS capabilities supporting edge computing | Intel Ireland | pCR | Approval | Yes |
Yes
| approved | No | S5‑206086 | |||
S5‑206174 | Add Scope and References on 5GS charging for edge computing | China Telecomunication Corp. | pCR | Approval | Yes |
Yes
| merged | No | S5‑206429 | |||
S5‑206175 | Add the Service KPIs as charging factors on 5GS charging for edge computing | China Telecomunication Corp. | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑206200 | pCR TR 28.815 Adding topic for charging information | Ericsson | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑206234 | Rel-17 pCR 28.815 Refinements on architectures | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑206427 | |||
S5‑206427 | Rel-17 pCR 28.815 Refinements on architectures | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑206234 | |||
S5‑206269 | Rel-17 pCR 28.815 Introduce use cases and potential requirements | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑206428 | |||
S5‑206428 | Rel-17 pCR 28.815 Introduce use cases and potential requirements | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑206269 | |||
S5‑206430 | Draft TR 28.815 | China Telecomunication Corp | draft TR | Approval | Yes |
Yes
| approved | No | ||||
7.5.2 | Study on charging aspects of 5GS CIoT | S5‑206114 | pCR 28.816 add background for 5GS CIoT | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||
S5‑206115 | pCR 28.816 add background for data connectivity charging | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑206431 | |||
S5‑206431 | pCR 28.816 add background for data connectivity charging | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑206115 | |||
S5‑206116 | pCR 28.816 add background for control plane data transfer charging | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑206432 | |||
S5‑206432 | pCR 28.816 add background for control plane data transfer charging | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑206116 | |||
S5‑206117 | pCR 28.816 add background for monitoring event charging | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑206433 | |||
S5‑206433 | pCR 28.816 add background for monitoring event charging | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑206117 | |||
S5‑206118 | pCR 28.816 add CP optimization for data connectivity charging | Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑206434 | Draft TR 28.816 | Huawei | draft TR | Approval | Yes |
Yes
| approved | No | ||||
7.5.3 | Study on charging aspects of Proximity-based Services in 5GC | S5‑206125 | pCR 32.846 Add terms and abbreviations | CATT | pCR | Approval | Yes |
Yes
| revised | No | S5‑206436 | |
S5‑206436 | pCR 32.846 Add terms and abbreviations | CATT | pCR | Approval | Yes |
Yes
| approved | No | S5‑206125 | |||
S5‑206126 | pCR 32.846 Add concepts and overview of ProSe charing in 5GS | CATT | pCR | Approval | Yes |
Yes
| revised | No | S5‑206437 | |||
S5‑206437 | pCR 32.846 Add concepts and overview of ProSe charing in 5GS | CATT | pCR | Approval | Yes |
Yes
| approved | No | S5‑206126 | |||
S5‑206127 | pCR 32.846 Add architecture considerations for ProSe charing in 5GS | CATT | pCR | Approval | Yes |
Yes
| revised | No | S5‑206438 | |||
S5‑206438 | pCR 32.846 Add architecture considerations for ProSe charing in 5GS | CATT | pCR | Approval | Yes |
Yes
| approved | No | S5‑206127 | |||
S5‑206128 | pCR 32.846 Add general description and assumptions | CATT | pCR | Approval | Yes |
Yes
| revised | No | S5‑206439 | |||
S5‑206439 | pCR 32.846 Add general description and assumptions | CATT | pCR | Approval | Yes |
Yes
| approved | No | S5‑206128 | |||
S5‑206129 | pCR 32.846 Add potential charging requirements | CATT | pCR | Approval | Yes |
Yes
| revised | No | S5‑206440 | |||
S5‑206440 | pCR 32.846 Add potential charging requirements | CATT | pCR | Approval | Yes |
Yes
| approved | No | S5‑206129 | |||
S5‑206130 | pCR 32.846 Add key issues | CATT | pCR | Approval | Yes |
Yes
| revised | No | S5‑206441 | |||
S5‑206441 | pCR 32.846 Add key issues | CATT | pCR | Approval | Yes |
Yes
| approved | No | S5‑206130 | |||
S5‑206201 | pCR TR 32.846 Adding topic on charging information | Ericsson | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑206442 | Draft TR 32.846 | CATT | draft TR | Approval | Yes |
Yes
| approved | No | ||||
8 | Any Other Business |   | ||||||||||
9 | Closing of the meeting |   |