Tdoc List
2025-10-24 16:46
| TDoc | Title | Source | Type | For | Agenda | Avail | Treated | Decision | Wdrn | Replaced-by | Replaces |
|---|---|---|---|---|---|---|---|---|---|---|---|
| S5‑254200 | Agenda | WG Chair (Huawei) | agenda | Information |
2Approval of the agenda
| Yes |
YesThe SA5 Chair openend the meeting. CCSA welcomed all delegates to the SA5#163 meeting in Wuhan and presented the practicalities.
Then the SA5 Chair reminded:
Reminder for IPR declaration
"The attention of the delegates to the meeting of this Technical Specification Group was drawn to the fact that 3GPP Individual Members have the obligation under the IPR Policies of their respective Organizational Partners to inform their respective Organizational Partners of Essential IPRs they become aware of.
The delegates were asked to take note that they were thereby invited:
to investigate whether their organization or any other organization owns IPRs which were, or were likely to become Essential in respect of the work of 3GPP.
to notify their respective Organizational Partners of all potential IPRs, e.g., for ETSI, by means of the IPR Information Statement and the Licensing declaration forms "
Antitrust Guidance
"The attention of the delegates to the meeting was drawn to the fact that 3GPP activities were subject to all applicable antitrust and competition laws and that compliance with said laws was therefore required by any participant of the meeting, including the Chair and Vice-Chairs and were invited to seek any clarification needed with their legal counsel. The leadership would conduct the present meeting with impartiality and in the interests of 3GPP. Delegates were reminded that timely submission of work items in advance of TSG/WG/SWG meetings was important to allow for full and fair consideration of such matters."
Consensus principle reminder
“The attention of the delegates to the meeting is drawn to the fact that 3GPP endeavours to reach consensus on all decisions and therefore depends on a cooperative spirit of the Individual Members. In particular, Individual Members are encouraged to seek a consensus-based solution and only to sustain objections as a very last resort, and where absolutely necessary and well justified. The leadership will conduct the present meeting in a manner whereby informal methods of reaching consensus are encouraged, whilst ensuring that well justified concerns are taken into account.”
| revised | No | S5‑254622 | |
| S5‑254201 | IPR Antitrust and Consensus principles reminders | WG Chair (Huawei) | other | Information |
3IPR and Antitrust and Consensus principles reminders
| Yes |
YesThen the SA5 Chair reminded:
Reminder for IPR declaration
"The attention of the delegates to the meeting of this Technical Specification Group was drawn to the fact that 3GPP Individual Members have the obligation under the IPR Policies of their respective Organizational Partners to inform their respective Organizational Partners of Essential IPRs they become aware of.
The delegates were asked to take note that they were thereby invited:
to investigate whether their organization or any other organization owns IPRs which were, or were likely to become Essential in respect of the work of 3GPP.
to notify their respective Organizational Partners of all potential IPRs, e.g., for ETSI, by means of the IPR Information Statement and the Licensing declaration forms "
Antitrust Guidance
"The attention of the delegates to the meeting was drawn to the fact that 3GPP activities were subject to all applicable antitrust and competition laws and that compliance with said laws was therefore required by any participant of the meeting, including the Chair and Vice-Chairs and were invited to seek any clarification needed with their legal counsel. The leadership would conduct the present meeting with impartiality and in the interests of 3GPP. Delegates were reminded that timely submission of work items in advance of TSG/WG/SWG meetings was important to allow for full and fair consideration of such matters."
Consensus principle reminder
“The attention of the delegates to the meeting is drawn to the fact that 3GPP endeavours to reach consensus on all decisions and therefore depends on a cooperative spirit of the Individual Members. In particular, Individual Members are encouraged to seek a consensus-based solution and only to sustain objections as a very last resort, and where absolutely necessary and well justified. The leadership will conduct the present meeting in a manner whereby informal methods of reaching consensus are encouraged, whilst ensuring that well justified concerns are taken into account.”
Then new delegates from Nokia India and CICT introduced themselves.
| noted | No | ||
| S5‑254202 | Report from last SA5 meeting | MCC | report | Approval |
4.1Last SA5 meeting report
| Yes |
Yes
| approved | No | ||
| S5‑254203 | SA5#163 Time Plan | WG Chair (Huawei) | agenda | Information |
5.1Administrative issues at SA5 level
| No |
Yes
| noted | No | ||
| S5‑254204 | agenda_with_Tdocs_sequence_Plenary&OAM | WG Chair (Huawei) | agenda | Information |
5.1Administrative issues at SA5 level
| No |
Yes
| noted | No | ||
| S5‑254205 | SA5 working methods | WG Chair (Huawei) | other | Information |
5.1Administrative issues at SA5 level
| Yes |
Yes
| revised | No | S5‑254623 | |
| S5‑254206 | Rel-20 SA5 work plan TU table | WG Chair (Huawei) | other |
5.1Administrative issues at SA5 level
| Yes |
YesPlanned 5GA, consumed 67 TU.
6G
| noted | No | |||
| S5‑254207 | SA5 meeting calendar | WG Chair (Huawei) | other | Information |
5.4SA5 meeting calendar
| Yes |
Yes
| revised | No | S5‑254629 | |
| S5‑254208 | Post email approval status | WG Vice Chair (Ericsson) | other | Information |
5.1Administrative issues at SA5 level
| No |
Yes
| noted | No | ||
| S5‑254209 | OAM&P action list | WG Vice Chair (China Unicom) | other |
6.1OAM Plenary
| Yes |
Yes
| noted | No | |||
| S5‑254210 | OAM Exec Report | WG Vice Chair (China Unicom) | report |
6.1OAM Plenary
| Yes |
Yes
| noted | No | |||
| S5‑254211 | Plenary and OAM Chair notes and conclusions | WG Chair (Huawei) | report | Information |
5.1Administrative issues at SA5 level
| Yes |
Yes30.10. Samsung will not be available fr the Rapp. call
| noted | No | ||
| S5‑254212 | Collection of useful endorsed documents in OAM | WG Vice Chair (China Unicom) | other |
5.4SA5 meeting calendar
| Yes |
Yes
| noted | No | |||
| S5‑254213 | Collection of external communication documents in OAM | WG Chair (Huawei) | other |
6.1OAM Plenary
| Yes |
Yes
| noted | No | |||
| S5‑254214 | Collection of external communication documents in OAM | WG Vice Chair (China Unicom) | other |
6.1OAM Plenary
| No |
Yes
| withdrawn | Yes | |||
| S5‑254215 | agenda_with_Tdocs_sequence_CH | SWG CH Chair (MATRIXX Software) | report | Information |
7.1Charging Plenary
| No |
Yes
| revised | No | S5‑254800 | |
| S5‑254216 | Charging exec report | SWG CH Chair (MATRIXX Software) | other | Information |
7.1Charging Plenary
| Yes |
Yes
| noted | No | ||
| S5‑254217 | Collection of useful contributions and external communication documents in CH | SWG Vice Chair (Huawei Tech.(UK) Co.. Ltd) | other |
7.1Charging Plenary
| Yes |
Yes
| noted | No | |||
| S5‑254218 | Latest SA5 WIs-SIs | WG Chair (Huawei) | other | Information |
5.1Administrative issues at SA5 level
| Yes |
Yes
| noted | No | ||
| S5‑254219 | draft SA5#163 meeting report | ETSI Secretariat | other | Information |
5.1Administrative issues at SA5 level
| No |
Yes
| noted | No | ||
| S5‑254220 | Rel-20 SA5 work planning | WG Chair (Huawei) | other | Information |
5.1Administrative issues at SA5 level
| Yes |
Yesupdate progress
| noted | No | ||
| S5‑254221 | OAM breakout notes | WG Chair (Huawei) | report | Information |
6.1OAM Plenary
| Yes |
Yes
| noted | No | ||
| S5‑254222 | Rel-20 CR TS 28.552 Add UE Address Information Retrieval for UPF event exposure measurement | China Telecom | CR | Agreement |
6.20.125G performance measurements/KPIs and Trace/MDT/QoE
| Yes |
Yes
| revised | No | S5‑254716 | |
| S5‑254223 | Rel-20 CR TS 28.552 Add UPF event exposure related measurements | China Telecom Corporation Ltd. | CR | Agreement |
6.20.125G performance measurements/KPIs and Trace/MDT/QoE
| Yes |
Yes
| revised | No | S5‑254717 | |
| S5‑254224 | Rel-20 CR TS 28.552 Add measurements of UPF related information exposed | China Telecom Corporation Ltd. | CR | Agreement |
6.20.125G performance measurements/KPIs and Trace/MDT/QoE
| Yes |
Yes
| agreed | No | ||
| S5‑254225 | Rel-20 CR 28.554 Add new KPI equivalent RRC connection number for transient overload scenarios | China Unicom | CR | Agreement |
6.20.125G performance measurements/KPIs and Trace/MDT/QoE
| Yes |
YesNokia: no cl. aff.!
| not pursued | No | ||
| S5‑254226 | Rel-20 CR 28.554 Add operator-specific energy consumption and energy efficiency KPIs for network sharing scenario | China Unicom | CR | Agreement |
6.20.125G performance measurements/KPIs and Trace/MDT/QoE
| Yes |
YesNokia: no cl. aff.!
Do not support this.
ETSI MCC: CR v12.1->12.3.
| not pursued | No | ||
| S5‑254227 | Rel-20 CR 28.554 Add energy efficiency KPI of HDLLC network slice for XR | China Unicom | CR | Agreement |
6.20.125G performance measurements/KPIs and Trace/MDT/QoE
| Yes |
YesNokia: KPI is not correct. Should be part of R20 EE.
ETSI MCC: CR v12.1->12.3. No cl. aff.
E///: move to EE. Are we introducing service awareness? Defer to next meeting.
| not pursued | No | ||
| S5‑254228 | pCR TR 28.881 Add new use case for radio service assurance in transient overload scenarios | China Unicom | pCR | Approval |
6.20.1Study on intent driven management services for mobile network phase 4
| Yes |
Yes
| revised | No | S5‑254648 | |
| S5‑254229 | Rel-19 CR 28.541 Correction to X2HOBlockList | Rakuten Mobile, Inc | CR | Agreement |
6.19.135G Advanced NRM features phase 3
| No |
Yes
| withdrawn | Yes | ||
| S5‑254230 | Rel-20 CR TS 28.541 CR Correction to X2HOBlockList | Rakuten Mobile, Inc. | CR | Agreement |
6.20.0OAM Rel-20 small enhancements
| Yes |
Yes
| agreed | No | ||
| S5‑254231 | Reply LS on specification of dataset and model parameters exchange | SA5 | LS out | Approval |
5.3Liaison statements at SA5 level
| Yes |
Yes
| revised | No | S5‑254791 | |
| S5‑254232 | Reply to LS on a new measurement related to the maintainability of a QoS flow | SA5 | LS out | Approval |
5.3Liaison statements at SA5 level
| Yes |
Yes
| revised | No | S5‑254627 | |
| S5‑254233 | Rel-19 CR TS 28.552 performance measurements for QoS flow fulfillment | Ericsson, Verizon | CR | Agreement |
6.19.125G performance measurements and KPIs phase 4
| Yes |
Yes
| agreed | No | ||
| S5‑254234 | Rel-20 CR TS 28.552 performance measurements for QoS flow fulfillment | Ericsson, Verizon | CR | Agreement |
6.19.125G performance measurements and KPIs phase 4
| Yes |
Yes
| agreed | No | ||
| S5‑254235 | Rel-19 CR TS 28.554 performance measurements for QoS flow fulfillment | Ericsson, Verizon | CR | Agreement |
6.19.125G performance measurements and KPIs phase 4
| Yes |
Yes
| agreed | No | ||
| S5‑254236 | Rel-18 CR TS 32.422 Corrections on MDT configurations | Ericsson | CR | Agreement |
6.6.8Management of Trace/MDT phase 2
| Yes |
Yes
| agreed | No | ||
| S5‑254237 | Rel-19 CR TS 32.422 Corrections on MDT configurations | Ericsson | CR | Agreement |
6.6.8Management of Trace/MDT phase 2
| Yes |
Yes
| agreed | No | ||
| S5‑254238 | Rel-18 CR TS 28.622 Corrections on Allowed Data Category | Ericsson | CR | Agreement |
6.6.8Management of Trace/MDT phase 2
| Yes |
YesNokia & Huawei did not agree with this change.
Nokia objected.
| not pursued | No | ||
| S5‑254239 | Rel-19 CR TS 28.622 Corrections on Allowed Data Category | Ericsson | CR | Agreement |
6.6.8Management of Trace/MDT phase 2
| Yes |
YesNokia objected.
| not pursued | No | ||
| S5‑254240 | Rel-20 CR TS 28.622 Corrections on Allowed Data Category | Ericsson | CR | Agreement |
6.6.8Management of Trace/MDT phase 2
| Yes |
YesNokia objected.
| not pursued | No | ||
| S5‑254241 | Rel-18 CR TS 28.623 Corrections on Allowed Data Category | Ericsson | CR | Agreement |
6.6.8Management of Trace/MDT phase 2
| Yes |
YesNokia objected.
| not pursued | No | ||
| S5‑254242 | Rel-19 CR TS 28.623 Corrections on Allowed Data Category | Ericsson | CR | Agreement |
6.6.8Management of Trace/MDT phase 2
| Yes |
YesNokia objected.
| not pursued | No | ||
| S5‑254243 | Rel-20 CR TS 28.623 Corrections on Allowed Data Category | Ericsson | CR | Agreement |
6.6.8Management of Trace/MDT phase 2
| Yes |
YesNokia objected.
| not pursued | No | ||
| S5‑254244 | Rel-19 CR TS 32.422 area scope correction | Ericsson | CR | Agreement |
6.6.8Management of Trace/MDT phase 2
| Yes |
Yes
| agreed | No | ||
| S5‑254245 | Rel-18 CR TS 32.422 area scope correction | Ericsson Japan K.K. | CR | Agreement |
6.6.8Management of Trace/MDT phase 2
| Yes |
Yes
| revised | No | S5‑254580 | |
| S5‑254246 | Rel-18 CR TS 28.622 area scope correction | Ericsson | CR | Agreement |
6.6.8Management of Trace/MDT phase 2
| Yes |
Yes
| agreed | No | ||
| S5‑254247 | Rel-19 CR TS 28.622 area scope correction | Ericsson Japan K.K. | CR | Agreement |
6.6.8Management of Trace/MDT phase 2
| Yes |
Yes
| revised | No | S5‑254582 | |
| S5‑254248 | Rel-19 CR TS 32.423 Corrections on Trace Record Protocol Buffer | Ericsson Japan K.K. | CR | Agreement |
6.19.14Subscriber and Equipment Trace and QoE collection management
| No |
Yes
| withdrawn | Yes | ||
| S5‑254249 | Rel-20 CR TS 28.622 area scope correction | Ericsson | CR | Agreement |
6.6.8Management of Trace/MDT phase 2
| Yes |
Yes
| agreed | No | ||
| S5‑254250 | Rel-19 CR TS 28.623 NTN geographical area scope | Ericsson Japan K.K. | CR | Agreement |
6.19.14Subscriber and Equipment Trace and QoE collection management
| Yes |
Yes
| revised | No | S5‑254585 | |
| S5‑254251 | Rel-20 CR TS 28.623 NTN geographical area scope | Ericsson | CR | Agreement |
6.19.14Subscriber and Equipment Trace and QoE collection management
| Yes |
Yes
| not pursued | No | ||
| S5‑254252 | Rel-20 CR TS 28.554 Corrections on KPI naming | Ericsson | CR | Agreement |
6.20.125G performance measurements/KPIs and Trace/MDT/QoE
| Yes |
YesNokia: does not support this change.
Keep open.
Nokia objected.
| not pursued | No | ||
| S5‑254253 | Rel-20 CR TS 32.423 Additional Trace References | Ericsson Japan K.K. | CR | Agreement |
6.20.125G performance measurements/KPIs and Trace/MDT/QoE
| No |
Yes
| withdrawn | Yes | ||
| S5‑254254 | Rel-20 CR TS 32.423 Trace Record Schema Optimization | Ericsson Japan K.K. | CR | Agreement |
6.20.125G performance measurements/KPIs and Trace/MDT/QoE
| No |
Yes
| withdrawn | Yes | ||
| S5‑254255 | Rel-20 CR TS 32.423 Trace message direction | Ericsson, AT&T | CR | Agreement |
6.20.125G performance measurements/KPIs and Trace/MDT/QoE
| No |
Yes
| withdrawn | Yes | ||
| S5‑254256 | Rel-19 CR TS 28.541 add 5GC and NG-RAN NRM usage introduction in the annex | Huawei | CR | Agreement |
6.19.135G Advanced NRM features phase 3
| Yes |
YesNokia is not supportive of this change.
Ericsson expressed concerns, the list would be too long.
| not pursued | No | ||
| S5‑254257 | Rel-19 CR TS 28.540 add missing concepts and backgrouds of management of NG-RAN and 5GC | Huawei | CR | Agreement |
6.19.135G Advanced NRM features phase 3
| Yes |
Yes
| revised | No | S5‑254880 | |
| S5‑254258 | Revised WID on 5G Advanced NRM features phase 4 | Huawei | WID revised | Approval |
6.2.2Revised OAM SIDs/WIDs proposals
| Yes |
Yes
| revised | No | S5‑254661 | |
| S5‑254259 | Pseudo-CR on TR 28.882 add Management support to Two-Side model training use case | Huawei | pCR | Approval |
6.20.2Study on AI/ML management phase 3
| Yes |
YesNokia provided offline comments
merged into S5-254665
| merged | No | ||
| S5‑254260 | Pseudo-CR on TR 28.882 add Management support to UE-Side model training use case | Huawei | pCR | Approval |
6.20.2Study on AI/ML management phase 3
| Yes |
Yes
| revised | No | S5‑254666 | |
| S5‑254261 | Pseudo-CR on TR 28.882 add Management support to NW-Side model training use case | Huawei | pCR | Approval |
6.20.2Study on AI/ML management phase 3
| Yes |
Yesneed more solutions to reply to RAN2 LS S5-254621.
| revised | No | S5‑254667 | |
| S5‑254262 | Pseudo-CR on TR 28.882 add model registration management use case | Huawei | pCR | Approval |
6.20.2Study on AI/ML management phase 3
| Yes |
Yes
| revised | No | S5‑254749 | |
| S5‑254263 | Rel-20 CR TS 28.541 add LTM control attribute to support conditional LTM | Huawei | CR | Agreement |
6.20.115G Advanced NRM features phase 4
| Yes |
Yes
| revised | No | S5‑254708 | |
| S5‑254264 | Rel-20 CR TS 28.313 update the description of MRO for LTM control to support conditional LTM | Huawei | CR | Agreement |
6.20.115G Advanced NRM features phase 4
| Yes |
YesTS baseline is not ready!
Endorsed in principle.
Bring it back at the next meeting
| endorsed | No | ||
| S5‑254265 | Rel-20 Discussion on the management support for NG-RAN 5GC feature | Huawei | discussion | Endorsement |
6.19.135G Advanced NRM features phase 3
| Yes |
YesNokia is not supportive of this change.
| revised | No | S5‑254881 | |
| S5‑254266 | Rel-20 CR TS 28.541 add 5G femto NRM usage introduction in the annex | Huawei | CR | Agreement |
6.20.115G Advanced NRM features phase 4
| Yes |
YesE///: why new annex?
Huawei: clearly shows the features.
| revised | No | S5‑254710 | |
| S5‑254267 | Pseudo-CR on TR 28.886 Add solution for enhance the mobility performance analysis use case | Huawei | pCR | Approval |
6.20.7Study on Management Data Analytics (MDA) phase 4
| Yes |
YesE///: pls. remove ".. NSA mobility issue.."
| revised | No | S5‑254687 | |
| S5‑254268 | pCR TR 28.881 Add solution for enhancement of radio service delivering and assurance scenarios | Huawei,China Mobile | pCR | Approval |
6.20.1Study on intent driven management services for mobile network phase 4
| Yes |
Yes
| revised | No | S5‑254646 | |
| S5‑254269 | pCR TR 28.881 Add solution for Intent exploration enhancement | Huawei,China Mobile | pCR | Approval |
6.20.1Study on intent driven management services for mobile network phase 4
| Yes |
YesNokia: the solution does not match the requirements.
| revised | No | S5‑254652 | |
| S5‑254270 | pCR TR 28.881 Add solution for enhancement of radio network performance assurance scenarios | Huawei | pCR | Approval |
6.20.1Study on intent driven management services for mobile network phase 4
| Yes |
Yes
| revised | No | S5‑254645 | |
| S5‑254271 | pCR TR 28.881 Add solution for Intent handling capability configuration, registration and discovery | Huawei | pCR | Approval |
6.20.1Study on intent driven management services for mobile network phase 4
| Yes |
YesE///: aspect1 can be merged into.
| revised | No | S5‑254656 | |
| S5‑254272 | pCR TR 28.881 Documentation for the overview of intent driven management functionalities | Huawei | pCR | Approval |
6.20.1Study on intent driven management services for mobile network phase 4
| Yes |
Yes
| revised | No | S5‑254653 | |
| S5‑254273 | pCR TR 28.881 Add use case for the Investigation on the applicability and potential impacts to support natural language intents translation | Huawei | pCR | Approval |
6.20.1Study on intent driven management services for mobile network phase 4
| Yes |
Yes
| revised | No | S5‑254658 | |
| S5‑254274 | Rel-19 CR TS 28.541 correct the NRM definition for RedCap | Huawei | CR | Agreement |
6.19.17Management Aspects of RedCap features
| Yes |
Yes
| revised | No | S5‑254779 | |
| S5‑254275 | Rel-20 CR TS 28.541 correct the NRM definition for RedCap | Huawei | CR | Agreement |
6.19.17Management Aspects of RedCap features
| Yes |
Yes
| revised | No | S5‑254780 | |
| S5‑254276 | Rel-19 CR TS 28.533 Update Annex F to add missing R19 management capabilities | Huawei | CR | Agreement |
6.19.24Rel-19 CAT B/C SA5 internal alignment and other CAT F CR(s)
| Yes |
YesE///: keep open.
| agreed | No | ||
| S5‑254277 | Rel-19 CR TS 28.622 Add Enum values for missing R19 management capabilities | Huawei | CR | Agreement |
6.19.24Rel-19 CAT B/C SA5 internal alignment and other CAT F CR(s)
| Yes |
YesE///: would like to keep the values where they are.
| revised | No | S5‑254796 | |
| S5‑254278 | Rel-20 CR TS 28.622 Add Enum values for missing R19 management capabilities | Huawei | CR | Agreement |
6.19.24Rel-19 CAT B/C SA5 internal alignment and other CAT F CR(s)
| Yes |
Yes
| revised | No | S5‑254797 | |
| S5‑254279 | Rel-19 CR TS 28.623 Add Enum values for missing R19 management capabilities | Huawei | CR | Agreement |
6.19.24Rel-19 CAT B/C SA5 internal alignment and other CAT F CR(s)
| Yes |
Yes
| agreed | No | ||
| S5‑254280 | Rel-19 CR TS 28.537 Add missing functionality and solution description for managing external management data | Huawei | CR | Agreement |
6.19.10Data management phase 2
| Yes |
Yes
| revised | No | S5‑254767 | S5‑253888 |
| S5‑254281 | Rel-20 CR TS 28.622 Correct several issues for the IOCs related to MADCOL | Huawei | CR | Agreement |
6.20.0OAM Rel-20 small enhancements
| Yes |
Yes
| revised | No | S5‑254642 | |
| S5‑254282 | Rel-20 CR TS 28.623 Correct several issues for the IOCs related to MADCOL | Huawei | CR | Agreement |
6.20.0OAM Rel-20 small enhancements
| Yes |
Yes
| revised | No | S5‑254643 | |
| S5‑254283 | Rel-20 CR TS 28.541 Update NTNEntityConf dataType definition | Huawei | CR | Agreement |
6.20.115G Advanced NRM features phase 4
| Yes |
YesE///: some misunderstanding of NTN.
| revised | No | S5‑254711 | |
| S5‑254284 | Correction of PcscfInfo data type | AsiaInfo | CR | Agreement |
6.20.115G Advanced NRM features phase 4
| Yes |
Yes
| revised | No | S5‑254712 | |
| S5‑254285 | Enhancement of PcscfInfo | AsiaInfo | CR | Agreement |
6.20.115G Advanced NRM features phase 4
| Yes |
Yes
| revised | No | S5‑254713 | |
| S5‑254286 | Enhancement of PcfInfo | AsiaInfo | CR | Agreement |
6.20.115G Advanced NRM features phase 4
| Yes |
Yes
| revised | No | S5‑254714 | |
| S5‑254287 | Rel-20 pCR TR 32.801-02 Add TR scope and reference to 6G charging system | CATT | pCR | Approval |
7.6.1Charging Aspects of 6G System
| Yes |
YesIs linked to S5-254359
N: similar as for SID on CAPIF
Chair: merged
| merged | No | ||
| S5‑254288 | New SID on Charging Aspects of satellite access phase 4 | CATT | SID new | Approval |
7.2.1New CH SIDs/WIDs proposals
| Yes |
Yes
| postponed | No | S5‑254802 | |
| S5‑254289 | Rel-20 pCR TR 28.881 Add Use case on intent expectation satisfaction information | Huawei | pCR | Approval |
6.20.1Study on intent driven management services for mobile network phase 4
| Yes |
Yes
| revised | No | S5‑254655 | |
| S5‑254290 | Rel-20 pCR TR 28.883 Add structure proposal | Huawei | pCR | Approval |
6.20.3Study on management aspects of Network Digital Twins phase 2
| Yes |
Yes
| approved | No | ||
| S5‑254291 | Rel-20 pCR TR 28.883 Use case on NDT support intent pre-evaluation | Huawei | pCR | Approval |
6.20.3Study on management aspects of Network Digital Twins phase 2
| Yes |
YesNokia disagreed with the doc.
| revised | No | S5‑254670 | |
| S5‑254292 | Rel-20 pCR TR 28.883 Improvement of data generation | Huawei | pCR | Approval |
6.20.3Study on management aspects of Network Digital Twins phase 2
| Yes |
Yes
| revised | No | S5‑254671 | |
| S5‑254293 | Rel-19 CR TS 28.310 Update UC and requirements of Energy Efficiency as a Service Criteria | Ericsson | CR | Agreement |
6.19.20Energy efficiency and energy saving aspects of 5G networks and services
| Yes |
YesNokia: the existing use cases and req. are aligned.
Huawei: 5.1.6.1 needs rewording
| revised | No | S5‑254793 | |
| S5‑254294 | Study on 6G Management and Orchestration | China Unicom (Moderator) | SID new | Approval |
6.2.1New OAM SIDs/WIDs proposals
| Yes |
YesFiberCop: pls. remove '?'.
endorsed all the rest, only focus on yellow part.
Ericsson: pls use revision marks.
Option 1: E///, Verizon, Rakuten, NEC, AT&T.
Option 2a: Huawei, VIVO, Vodafone, DOCOMO, CATT, CMCC
Option 3a: Samsung, Telecom Italia, FIberCop, Nokia
(3 was proposed as a compromise)
Coordination with SA2.
NTT: Need definition of management data.
+Option 4: not include 1.6D
+Option 5: study the data management framework.
Telecom Italia: we do not want a different framework for collecting data.
Verizon agreed.
Vodafone: starting point should be management data, as it is a management framework.
China Mobile agreed.
Further show of hands on Tue (multiple options possible):
Option 1: E///, Vz, FBC, N, RT, AT&T, NEC, TI
Option 2a: HW, V, VF, ZTE, DCM, CATT, CMCC
Option 3a: SS, N
Option 4: -
Option 5: E///, FBC, NK, SS, V, AT&T, RT, NEC, TI
Single choice:
Option 1: E///, Vz, FBC, N, RT, AT&T, NEC, TI
Option 2a: HW, V, VF, ZTE, DCM, CATT, CMCC
Option 3a: SS
Option 5: -
| revised | No | S5‑254638 | S5‑254112 |
| S5‑254295 | Study on 6G Management and Orchestration Status Report | China Unicom (Moderator) | report | Presentation |
6.2.1New OAM SIDs/WIDs proposals
| Yes |
Yes
| revised | No | S5‑254639 | |
| S5‑254296 | Revised SID on Study on AI/ML management phase 3 | Qualcomm India Pvt Ltd | SID revised | Approval |
6.20.2Study on AI/ML management phase 3
| Yes |
Yeslate doc
ETSI MCC: author SA5? Former author NEC, Intel?
| noted | No | ||
| S5‑254297 | Add informatin elements to support charging aspects of multi-modality service | China Telecom | CR | Agreement |
7.4.1Charging aspects for XRM
| Yes |
Yes
| revised | No | S5‑254805 | |
| S5‑254298 | Add attributes to support charing aspects of multi-modality service | China Telecom | CR | Agreement |
7.4.1Charging aspects for XRM
| Yes |
Yes
| not pursued | No | ||
| S5‑254299 | Add informatin elements to support charing aspects of multi-modality XRM features | China Telecom | CR | Agreement |
7.4.1Charging aspects for XRM
| Yes |
Yes
| not pursued | No | ||
| S5‑254300 | pCR TR 28.881 Add new requirements and solution for enhancement radio service delivering and assurance scenarios | China Mobile, Huawei | pCR | Approval |
6.20.1Study on intent driven management services for mobile network phase 4
| Yes |
Yes
| revised | No | S5‑254647 | |
| S5‑254301 | pCR TR 28.883 Add a use case of NDT data generation | China Mobile | pCR | Approval |
6.20.3Study on management aspects of Network Digital Twins phase 2
| Yes |
Yes
| revised | No | S5‑254672 | |
| S5‑254302 | pCR TR 28.883 Add use case and requirements on enhancement for multiple NDT collaborations | China Mobile | pCR | Approval |
6.20.3Study on management aspects of Network Digital Twins phase 2
| Yes |
Yes
| revised | No | S5‑254673 | |
| S5‑254303 | pCR TR 28.883 Add use case and requirements on enhancement for NDT management and orchestration | China Mobile | pCR | Approval |
6.20.3Study on management aspects of Network Digital Twins phase 2
| Yes |
Yes
| revised | No | S5‑254675 | |
| S5‑254304 | pCR TR 28.885 Add use case and requirements for renewable energy consumption | China Mobile | pCR | Approval |
6.20.5Study on energy efficiency and energy saving aspects of 5G Advanced
| Yes |
YesEricsson sent offline comments
| revised | No | S5‑254736 | |
| S5‑254305 | pCR TR 28.885 Add solution for renewable energy consumption | China Mobile | pCR | Approval |
6.20.5Study on energy efficiency and energy saving aspects of 5G Advanced
| Yes |
Yes
| revised | No | S5‑254737 | |
| S5‑254306 | Proposals to guide the 6G OAM Study | China Mobile, Verizon, SK Telecom, CATT, ZTE, Rakuten Mobile, NEC, Orange | discussion | Endorsement |
6.2.1New OAM SIDs/WIDs proposals
| Yes |
Yes
| revised | No | S5‑254640 | |
| S5‑254307 | DP on scope of data WT in 6G Study.docx" | Nokia | discussion | Endorsement |
6.2.2Revised OAM SIDs/WIDs proposals
| Yes |
Yes
| noted | No | ||
| S5‑254308 | pCR TR28.886 Cell grouping for inference Analytics.docx" | Nokia | pCR | Approval |
6.20.7Study on Management Data Analytics (MDA) phase 4
| Yes |
Yeslate doc
Huawei: there is no definition of cell grouping?
| noted | No | ||
| S5‑254309 | pCR TR28.889 CCL for ES control.docx" | Nokia | pCR | Approval |
6.20.10Study on Closed Control Loop Management phase 2
| Yes |
Yeslate doc
offline comments from E///, NTT, Docomo, Samsung, Huawei, similar for following docs
| noted | No | ||
| S5‑254310 | pCR TR28.889 CCL for Handover optimization.docx" | Nokia | pCR | Approval |
6.20.10Study on Closed Control Loop Management phase 2
| Yes |
Yeslate doc
offline comments
| noted | No | ||
| S5‑254311 | pCR TR28.889 CCL for network slice resource optimization.docx" | Nokia | pCR | Approval |
6.20.10Study on Closed Control Loop Management phase 2
| Yes |
Yeslate doc
offline comments
| revised | No | S5‑254886 | |
| S5‑254312 | pCR TR28.881 Assisting intent decomposition.docx" | Nokia | pCR | Approval |
6.20.1Study on intent driven management services for mobile network phase 4
| Yes |
Yes0.0.0?
| noted | No | ||
| S5‑254313 | pCR TR28.881 Intent Interpretation Assistance Information Solution.docx" | Nokia | pCR | Approval |
6.20.1Study on intent driven management services for mobile network phase 4
| Yes |
Yes0.0.0?
| noted | No | ||
| S5‑254314 | pCR TR28.881 Invariant Guidance in Intent Contexts Solution.docx" | Nokia | pCR | Approval |
6.20.1Study on intent driven management services for mobile network phase 4
| Yes |
Yes0.0.0?
| noted | No | ||
| S5‑254315 | pCR TR28.881 DP on 6G work on autonomous agents.pptx" | Nokia | discussion | Endorsement |
6.20.1Study on intent driven management services for mobile network phase 4
| Yes |
Yeswrong title: "Intents, Goals and Autonomous Agents".
(Is a discussion paper)
| revised | No | S5‑254641 | |
| S5‑254316 | Reply LS on UE type identification for UAS charging requirements | CT3 | LS in | Information |
5.3Liaison statements at SA5 level
| Yes |
Yes
| noted | No | ||
| S5‑254317 | Reply LS on UE type identification for UAS charging requirements | CT4 | LS in | Information |
5.3Liaison statements at SA5 level
| Yes |
Yes
| noted | No | ||
| S5‑254318 | LS on need for modeling isInvariant and SystemCreated in YANG | IETF NETMOD WG | LS in | Action |
5.3Liaison statements at SA5 level
| Yes |
Yespresented by E///
reply in S5-254630
| noted | No | ||
| S5‑254319 | LS on Invitation to update the information in the IMT-2020 and beyond roadmap | JCA-IMT2020 | LS in | Action |
5.3Liaison statements at SA5 level
| Yes |
Yesreply in S5-254625, author CMCC
Will be presented again in the next meeting!
| postponed | No | ||
| S5‑254320 | LS on ""IETF Network Slice Application in 3GPP 5G End-to-End Network Slice"" | IETF Traffic Engineering Architecture and Signaling Working Group (teas) | LS in | Action |
5.3Liaison statements at SA5 level
| Yes |
Yesreply in S5-254626, E///
Matrix: also charging is impacted.
| noted | No | ||
| S5‑254321 | LS on new GSMA OPG PRDs publication and changes to PRD OPG.02 | GSMA OPG | LS in | Information |
5.3Liaison statements at SA5 level
| Yes |
YesSamsung: no need to replay
| noted | No | ||
| S5‑254322 | LS on User consent for Data collection at the UE for NW-side model training | RAN2 | LS in | Information |
6.1OAM Plenary
| Yes |
Yes
| noted | No | ||
| S5‑254323 | Reply LS on Logged Data Handling During Handover | RAN3 | LS in | Information |
5.3Liaison statements at SA5 level
| Yes |
Yes
| noted | No | ||
| S5‑254324 | Reply LS on MBS Communication Service Type | RAN3 | LS in | Information |
5.3Liaison statements at SA5 level
| Yes |
Yesreply in S5-254628, author NEC
| revised | No | ||
| S5‑254325 | LS on geographical area scope MDT | RAN3 | LS in | Action |
5.3Liaison statements at SA5 level
| Yes |
Yes
| noted | No | ||
| S5‑254326 | LS on specification of dataset and model parameters exchange | TSG RAN | LS in | Information |
5.3Liaison statements at SA5 level
| Yes |
Yes
| noted | No | ||
| S5‑254327 | Reply LS on signalling feasibility of dataset and parameter sharing | SA2 | LS in | Information |
5.3Liaison statements at SA5 level
| Yes |
Yes
| noted | No | ||
| S5‑254328 | LS for a new measurement related to the maintainability of a QoS flow | SA2 | LS in | Action |
5.3Liaison statements at SA5 level
| Yes |
Yes
| noted | No | ||
| S5‑254329 | LS on initiation of new work item ITU-T Y.DTNCM “Digital twin network - collaboration and management in IMT-2020 networks and beyond” | ITU-T SG13 | LS in | Information |
5.3Liaison statements at SA5 level
| Yes |
Yes
| noted | No | ||
| S5‑254330 | LS on consent of new Recommendation ITU-T Y.3123 (ex.Y.IMT2020-CEFEC) “Framework of edge computing capability exposure for IMT-2020 networks and beyond” | ITU-T SG13 | LS in | Information |
5.3Liaison statements at SA5 level
| Yes |
Yes
| noted | No | ||
| S5‑254331 | LS on information and call for contributions to the new Focus Group on Artificial Intelligence Native for Telecommunication Networks (FG-AINN) | ITU-T FG-AINN | LS in | Action |
5.3Liaison statements at SA5 level
| Yes |
Yes
| noted | No | ||
| S5‑254332 | LS/r on methodology coordination | ITU-T SG2 | LS in | Information |
5.3Liaison statements at SA5 level
| Yes |
YesSA5 had replied
| noted | No | ||
| S5‑254333 | LS on the consent of draft new Recommendation ITU-T M.3393 (M.rsmca): “Requirements for smart maintenance of cell antenna” | ITU-T SG2 | LS in | Information |
5.3Liaison statements at SA5 level
| Yes |
Yes
| noted | No | ||
| S5‑254334 | LS on Study on Modernization of Specification Format and Procedures for 6G | TSG SA | LS in | Information |
5.3Liaison statements at SA5 level
| Yes |
Yespostponed to next meeting!
Resubmit to next meeting
| postponed | No | ||
| S5‑254335 | LS on Guidance on 6G data related work tasks | TSG SA | LS in | Information |
5.3Liaison statements at SA5 level
| Yes |
Yesno need to reply.
Matrix: the purpose of data colection should also be considered.
| noted | No | ||
| S5‑254336 | LS on unified management interface for multi-RAT support | TSG SA | LS in | Information |
5.3Liaison statements at SA5 level
| Yes |
Yes
| noted | No | ||
| S5‑254337 | Liaison Response to ZSM work on Agent and Autonomy | TM Forum Autonomous Network Project | LS in | Information |
5.3Liaison statements at SA5 level
| Yes |
Yes
| noted | No | ||
| S5‑254338 | pCR TR28.889 CCL interactions with other functionalities | Nokia Americas | pCR | Approval |
6.20.10Study on Closed Control Loop Management phase 2
| Yes |
Yeslate doc
offline comments
| revised | No | S5‑254887 | |
| S5‑254339 | DP Clarify use of choice | Ericsson Hungary Ltd | discussion | Endorsement |
6.20.0OAM Rel-20 small enhancements
| Yes |
Yesis endorsed
| endorsed | No | ||
| S5‑254340 | Rel-20 CR 28.623 Indicate disturbance | Ericsson Hungary Ltd | CR | Agreement |
6.20.0OAM Rel-20 small enhancements
| Yes |
YesApproval->Agreement
+TS
E///: Nokia had asked for more time.
| agreed | No | ||
| S5‑254341 | Rel-18 CR 28.541 Add missing format specifiers to YAML | Ericsson Hungary Ltd | CR | Agreement |
6.6.26Rel-18 CAT B/C SA5 internal alignment and other CAT F CR(s)
| Yes |
Yes
| agreed | No | ||
| S5‑254342 | Rel-19 CR 28.541 Add missing format specifiers to YAML | Ericsson Hungary Ltd | CR | Agreement |
6.6.26Rel-18 CAT B/C SA5 internal alignment and other CAT F CR(s)
| Yes |
Yes
| agreed | No | ||
| S5‑254343 | Rel-20 CR 28.541 Add missing format specifiers to YAML | Ericsson Hungary Ltd | CR | Agreement |
6.6.26Rel-18 CAT B/C SA5 internal alignment and other CAT F CR(s)
| Yes |
Yes
| agreed | No | ||
| S5‑254344 | Rel-20 CR TS 32.423 VS Trace Record Payload | Ericsson Japan K.K. | CR | Agreement |
6.20.125G performance measurements/KPIs and Trace/MDT/QoE
| No |
Yes
| withdrawn | Yes | ||
| S5‑254345 | Rel-19 CR 28.623 YANG stage-3 corrections | Ericsson Hungary Ltd | CR | Agreement |
6.19.24Rel-19 CAT B/C SA5 internal alignment and other CAT F CR(s)
| Yes |
Yes
| agreed | No | ||
| S5‑254346 | Rel-19 CR 28.541 YANG stage-3 corrections | Ericsson Hungary Ltd | CR | Agreement |
6.19.24Rel-19 CAT B/C SA5 internal alignment and other CAT F CR(s)
| Yes |
Yes
| agreed | No | ||
| S5‑254347 | Rel-20 CR 28.541 YANG stage-3 corrections | Ericsson Hungary Ltd | CR | Agreement |
6.19.24Rel-19 CAT B/C SA5 internal alignment and other CAT F CR(s)
| Yes |
Yes
| agreed | No | ||
| S5‑254348 | Reply LS on geographical area scope MDT | CATT, Ericsson | LS out | Approval |
6.1OAM Plenary
| Yes |
Yes
| revised | No | S5‑254790 | |
| S5‑254349 | Rel-19 CR TS 32.422 Enhancement on the geographical area scope for NTN MDT | CATT, Ericsson | CR | Agreement |
6.19.23Rel-19 CAT B/C alignment CR(s) due to the work led by other 3GPP Working Groups
| Yes |
Yes
| revised | No | S5‑254785 | |
| S5‑254350 | Rel-20 CR TS 32.422 Enhancement on the geographical area scope for NTN MDT | CATT, Ericsson | CR | Agreement |
6.19.23Rel-19 CAT B/C alignment CR(s) due to the work led by other 3GPP Working Groups
| Yes |
Yes
| revised | No | S5‑254786 | |
| S5‑254351 | Rel-19 CR TS 28.622 Add Geo area scope for NTN MDT (stage 2) | CATT, Ericsson | CR | Agreement |
6.19.23Rel-19 CAT B/C alignment CR(s) due to the work led by other 3GPP Working Groups
| Yes |
Yes
| revised | No | S5‑254787 | |
| S5‑254352 | Rel-19 CR TS 28.623 Add Geo area scope for NTN MDT (stage 3 Yaml) | CATT | CR | Agreement |
6.19.23Rel-19 CAT B/C alignment CR(s) due to the work led by other 3GPP Working Groups
| Yes |
Yes
| revised | No | S5‑254788 | |
| S5‑254353 | Rel-20 CR TS 28.622 Add Geo area scope for NTN MDT (stage 2) | CATT, Ericsson | CR | Agreement |
6.19.23Rel-19 CAT B/C alignment CR(s) due to the work led by other 3GPP Working Groups
| Yes |
Yes
| revised | No | S5‑254789 | |
| S5‑254354 | Rel-20 CR TS 28.623 Add Geo area scope for NTN MDT (stage 3 Yaml) | CATT | CR | Agreement |
6.19.23Rel-19 CAT B/C alignment CR(s) due to the work led by other 3GPP Working Groups
| Yes |
Yesnot needed now. Maybe in Jan.
| not pursued | No | ||
| S5‑254355 | Rel-20 CR TS 32.260 IMS Call Charging Optimization | CSCN | CR | Agreement |
7.3Charging Maintenance and Rel-20 Charging small enhancements
| Yes |
Yes
| withdrawn | Yes | ||
| S5‑254356 | Rel-20 CR TS 32.291 IMS Call Charging Optimization | CSCN | CR | Agreement |
7.3Charging Maintenance and Rel-20 Charging small enhancements
| Yes |
Yes
| withdrawn | Yes | ||
| S5‑254357 | TR 32.801-02 v0.0.0 skeleton | China Telecom | draft TR | Approval |
7.6.1Charging Aspects of 6G System
| Yes |
Yesdoc type other->draft TR!
| approved | No | ||
| S5‑254358 | Rel-20 pCR TR 32.801-02 Update of the skeleton | China Telecom | pCR | Approval |
7.6.1Charging Aspects of 6G System
| Yes |
Yes
| revised | No | S5‑254818 | |
| S5‑254359 | Rel-20 pCR TR 32.801-02 Update of the Scope | China Telecom | pCR | Approval |
7.6.1Charging Aspects of 6G System
| Yes |
Yes
| revised | No | S5‑254816 | |
| S5‑254360 | Rel-20 pCR TR 32.801-02 Introduce a topic of new charging business models and charging metrics for 6G | China Telecom | pCR | Approval |
7.6.1Charging Aspects of 6G System
| Yes |
Yes
| revised | No | S5‑254819 | |
| S5‑254361 | Rel-19 CR TS 32.260 IMS Call Charging Optimization | CSCN | CR | Agreement |
7.3Charging Maintenance and Rel-20 Charging small enhancements
| Yes |
Yes
| not pursued | No | ||
| S5‑254362 | Rel-19 CR TS 32.291 IMS Call Charging Optimization | CSCN | CR | Agreement |
7.3Charging Maintenance and Rel-20 Charging small enhancements
| Yes |
Yes
| revised | No | S5‑254826 | |
| S5‑254363 | Rel-19 CR TS 32.291 Add a new trigger type in YAML for IMS call charging optimization | CSCN | CR | Agreement |
7.3Charging Maintenance and Rel-20 Charging small enhancements
| Yes |
Yes
| not pursued | No | ||
| S5‑254364 | Rel-20 CR TS 28.541 Management Support for Dynamic Traffic Characteristics Update | ZTE Corporation | CR | Agreement |
6.20.14OAM support for Extended Reality and Media service (XRM) phase 2
| Yes |
YesSA5
E///: referred to 23.503. Cannot check with the backoffice. Objected.
Postponed to next meeting.
| not pursued | No | ||
| S5‑254365 | Rel-20 CR TS 28.541 Management Support for Policy Control Enhancements to Support Multi-modality Flows | ZTE Corporation | CR | Agreement |
6.20.14OAM support for Extended Reality and Media service (XRM) phase 2
| Yes |
YesSA5
| not pursued | No | ||
| S5‑254366 | Rel-20 CR TS 28.541 Management Support for UE Power Saving for XRM Services | ZTE Corporation | CR | Agreement |
6.20.14OAM support for Extended Reality and Media service (XRM) phase 2
| Yes |
YesSA5
| not pursued | No | ||
| S5‑254367 | Rel-20 CR TS 28.541 Management Support to Deliver Media Related Information for Encrypted Traffic Using On-path N6 Signaling Method | ZTE Corporation | CR | Agreement |
6.20.14OAM support for Extended Reality and Media service (XRM) phase 2
| Yes |
YesSA5
MCC; clause numbering fix
| not pursued | No | ||
| S5‑254368 | Rel-20 CR TS 28.541 Stage 3 of Management Support for Policy Control | ZTE Corporation | CR | Agreement |
6.20.14OAM support for Extended Reality and Media service (XRM) phase 2
| Yes |
YesSA5
| not pursued | No | ||
| S5‑254369 | Rel-19 CR 32.291 Addition on NSPA charging information | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-20 Charging small enhancements
| Yes |
Yes
| not pursued | No | ||
| S5‑254370 | Rel-19 CR 32.298 Addition on NSPA charging information | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-20 Charging small enhancements
| Yes |
Yes
| not pursued | No | ||
| S5‑254371 | Rel-19 CR 32.291 Correction on Cardinality and Presence | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-20 Charging small enhancements
| Yes |
Yes
| revised | No | S5‑254824 | |
| S5‑254372 | Pseudo-CR on TR 28.886 Add new use case on domain information for MDAFunction | Huawei, China Mobile | pCR | Approval |
6.20.7Study on Management Data Analytics (MDA) phase 4
| Yes |
Yes
| revised | No | S5‑254684 | |
| S5‑254373 | Rel-20 CR TS 28.552 Add DL data transmission time per SSB | China Unicom | CR | Agreement |
6.20.125G performance measurements/KPIs and Trace/MDT/QoE
| Yes |
YesSamsung: rephrasing is needed.
ETSI MCC: no cl. aff.
| revised | No | S5‑254720 | |
| S5‑254374 | Rel-20 CR TS 28.552 Add Timing Advance distribution for NR Cell per SSB | China Unicom | CR | Agreement |
6.20.125G performance measurements/KPIs and Trace/MDT/QoE
| Yes |
Yes
| revised | No | S5‑254721 | |
| S5‑254375 | Rel-20 pCR TR 28.886 Add new use case on radio resource optimization based on per SSB usage | China Unicom | pCR | Approval |
6.20.7Study on Management Data Analytics (MDA) phase 4
| Yes |
YesE///: what is the MDS type?
| revised | No | S5‑254685 | |
| S5‑254376 | New WID on Charging aspects of next generation real time communication services phase 3 | China Mobile | WID new | Approval |
7.2.1New CH SIDs/WIDs proposals
| Yes |
Yes
| revised | No | S5‑254803 | |
| S5‑254377 | Study on unified management interface for multi-RAT support | Vodafone | draft TR | Approval |
6.20.15Unified Management interface for Multi-RAT support
| Yes |
Yes
| approved | No | ||
| S5‑254378 | pCR on TR 28.892 - Scope | Vodafone | pCR | Approval |
6.20.15Unified Management interface for Multi-RAT support
| Yes |
YesE///: pls. more details
| revised | No | S5‑254730 | |
| S5‑254379 | pCR on TR 28.892 - References | Vodafone | pCR | Approval |
6.20.15Unified Management interface for Multi-RAT support
| Yes |
Yes
| revised | No | S5‑254731 | |
| S5‑254380 | TR 32.872 v0.0.0 Initial skeleton | Huawei | other | Approval |
7.5.25GA Roaming Charging Reliability Enhancement
| Yes |
Yes
| revised | No | S5‑254811 | |
| S5‑254381 | Rel-20 pCR 32.872 Skeleton update | Huawei | pCR | Approval |
7.5.25GA Roaming Charging Reliability Enhancement
| Yes |
Yes
| approved | No | ||
| S5‑254382 | Report from last SA5-SG2 methodology coordination meeting | Ericsson LM | report | Information |
4.2Inter-organizational reports
| Yes |
Yes
| noted | No | ||
| S5‑254383 | DP on reference to other release version | Ericsson LM | discussion | Endorsement |
6.1OAM Plenary
| Yes |
Yesdeferred.
is endorsed
| endorsed | No | ||
| S5‑254384 | Rel-19 CR 28.572 Plan management stage3 updates | Ericsson Hungary Ltd | CR | Agreement |
6.19.9Management of planned configurations
| Yes |
Yes+Nokia
| revised | No | S5‑254766 | |
| S5‑254385 | Rel-20 pCR 28.891 Document Structure Update | Nokia | pCR | Approval |
7.5.1Charging Aspects of CAPIF Phase 3
| Yes |
Yes
| revised | No | S5‑254806 | |
| S5‑254386 | Rel-20 pCR 28.891 Update of the Scope | Nokia | pCR | Approval |
7.5.1Charging Aspects of CAPIF Phase 3
| Yes |
Yes
| revised | No | S5‑254807 | |
| S5‑254387 | Rel-20 CR 28.552 Add a new measurement related to the number of requests of ADRF storage services | China Telecom Corporation Ltd. | CR | Agreement |
6.20.13Management Aspects related to NWDAF phase 3
| Yes |
Yes
| withdrawn | Yes | ||
| S5‑254388 | New WID on cloud aspects of management and orchestration | Moderator (China Mobile), NTT DOCOMO, Rakuten Mobile | WID new | Approval |
6.2.1New OAM SIDs/WIDs proposals
| Yes |
YesE///: WT-3: can be standalone. Disagreed with WT-2 and WT-4.
Nokia confirmed the same.
-> breakout session
| noted | No | ||
| S5‑254389 | Pseudo-CR-TR 28.869 Add evaluation for solution of Observability | China Mobile | pCR | Approval |
6.19.6Study on Cloud Aspects of Management and Orchestration
| Yes |
Yes
| revised | No | S5‑254637 | |
| S5‑254390 | Rel-20 CR 28.552 Add new measurements related to the number of subscriptions and requests of ADRF retrieval services | China Telecom Corporation Ltd. | CR | Agreement |
6.20.13Management Aspects related to NWDAF phase 3
| Yes |
Yes
| withdrawn | Yes | ||
| S5‑254391 | Revised SID on Cloud Aspects of Management and Orchestration | China Mobile | SID revised | Approval |
6.2.2Revised OAM SIDs/WIDs proposals
| Yes |
Yes
| revised | No | S5‑254662 | |
| S5‑254392 | Presentation sheet of TR 28.869 for SA approval | China Mobile | TS or TR cover | Approval |
6.19.6Study on Cloud Aspects of Management and Orchestration
| Yes |
Yesmaybe have a working agreement.
| approved | No | S5‑254849 | |
| S5‑254393 | Rel-20 CR 28.552 Add a new measurement related to the number of requests of ADRF storage services | China Telecom | CR | Agreement |
6.20.13Management Aspects related to NWDAF phase 3
| Yes |
Yes
| revised | No | S5‑254722 | |
| S5‑254394 | Pseudo-CR-TR 28.869 Add Rapporteur clean-up and solve some editor's notes | China Mobile | pCR | Approval |
6.19.6Study on Cloud Aspects of Management and Orchestration
| Yes |
Yes
| revised | No | S5‑254735 | |
| S5‑254395 | Rel-20 CR 28.552 Add new measurements related to the number of subscriptions and requests of ADRF retrieval services | China Telecom | CR | Approval |
6.20.13Management Aspects related to NWDAF phase 3
| Yes |
YesSA5
merged into S5-254722
| merged | No | ||
| S5‑254396 | Rel-20 pCR TR 28.883 Enhancement on NDT reporting method | Huawei | pCR | Approval |
6.20.3Study on management aspects of Network Digital Twins phase 2
| Yes |
Yes
| approved | No | ||
| S5‑254397 | Rel-20 CR 28.541 Add VFL interoperability and client aggregation capability information for NWDAF | China Telecom | CR | Agreement |
6.20.13Management Aspects related to NWDAF phase 3
| Yes |
YesE///: typos
SA5
| revised | No | S5‑254724 | |
| S5‑254398 | New KI on Historical alarms | Nokia | pCR | Approval |
6.20.4Study on Service Based Management Architecture enhancement phase 4
| Yes |
Yes
| revised | No | S5‑254732 | |
| S5‑254399 | CR 28.572 Correct multiple errors in stage 2 | Nokia, Ericsson | CR | Agreement |
6.19.9Management of planned configurations
| Yes |
Yes2 typos
additional modifs at the next meeting
| agreed | No | ||
| S5‑254400 | CR 28.572 Correct multiple errors in stage 3 | Nokia, Ericsson | CR | Agreement |
6.19.9Management of planned configurations
| Yes |
Yes
| agreed | No | ||
| S5‑254401 | Rel-19 CR TS 28.105 Correct Misalignment between Stage 2 and Stage 3 | ZTE Corporation | CR | Agreement |
6.19.1AI/ML management phase 2
| Yes |
Yes
| withdrawn | Yes | ||
| S5‑254402 | Rel-19 CR TS 28.105 Correction on Properties of Attributes | ZTE Corporation | CR | Agreement |
6.19.1AI/ML management phase 2
| Yes |
YesE///: why is SS needed?
SA5
| revised | No | S5‑254750 | |
| S5‑254403 | Rel-19 CR TS 28.561 Correct Inconsistency between Stage 2 and Stage 3 | ZTE Corporation | CR | Agreement |
6.19.5Management aspects of Network Digital Twins
| Yes |
Yes
| revised | No | S5‑254762 | |
| S5‑254404 | Rel-19 CR TS 28.561 Correction on NDT Attributes | ZTE Corporation | CR | Agreement |
6.19.5Management aspects of Network Digital Twins
| Yes |
YesNTT: simulationData and performanceData are not correct
| revised | No | S5‑254763 | |
| S5‑254405 | Rel-20 CR TS 28.541 Configuration Enhancement on MWAB-gNB to Support QoS Related Information for the BH PDU Sessions | ZTE Corporation | CR | Agreement |
6.20.115G Advanced NRM features phase 4
| Yes |
YesE////: how does it fit the MGMT system?
Samsung: if RAN3 doesn't say anything, this can't be agreed.
| revised | No | S5‑254705 | |
| S5‑254406 | Pseudo-CR on TR 28.881 Add Solution to Intent Handling Capability Configuration, Registration and Discovery | ZTE Corporation | pCR | Approval |
6.20.1Study on intent driven management services for mobile network phase 4
| Yes |
Yesmerged into S5-254271
| merged | No | ||
| S5‑254407 | Pseudo-CR on TR 28.881 Add Solution to Support to Express Guarantee Requirements in an Intent | ZTE Corporation | pCR | Approval |
6.20.1Study on intent driven management services for mobile network phase 4
| Yes |
Yes
| revised | No | S5‑254650 | |
| S5‑254408 | Pseudo-CR on TR 28.882 Add New Use Case on Management of Vertical Federated Learning | ZTE Corporation | pCR | Approval |
6.20.2Study on AI/ML management phase 3
| Yes |
Yes
| revised | No | S5‑254744 | |
| S5‑254409 | Rel-19 CR TS 28.105 Correct Inconsistency between Stage 2 and Stage 3 | ZTE Corporation | CR | Agreement |
6.19.1AI/ML management phase 2
| Yes |
YesSA5
| revised | No | S5‑254751 | |
| S5‑254410 | pCR TR 28.869 NRM updates for NF Deployment LCM | Rakuten Mobile, Inc | pCR | Agreement |
6.19.6Study on Cloud Aspects of Management and Orchestration
| Yes |
YesNokia: agreed to the general solution. but it is incomplete.
Close the SI FS_Cloud_OAM in this meeting?
E///: think this pCR is premature.
| revised | No | S5‑254634 | |
| S5‑254411 | Rel-19 CR TS28.567 Clarify CCL-related MnS | Nokia | CR | Agreement |
6.19.4Closed Control Loop Management
| Yes |
Yesis not Cat. D.->F!
| revised | No | S5‑254759 | |
| S5‑254412 | Rel-19 CR TS28.567 Small corrections | Nokia | CR | Agreement |
6.19.4Closed Control Loop Management
| Yes |
YesHuawei: is not a small correction
| revised | No | S5‑254760 | |
| S5‑254413 | pCR on Rel-20 TR 28.881 Add solution for use case#3 | NTT DOCOMO | pCR | Approval |
6.20.1Study on intent driven management services for mobile network phase 4
| Yes |
Yes
| revised | No | S5‑254659 | |
| S5‑254414 | pCR on Rel-20 TR 28.881 Add use-case description, requirement and solution for relation and interaction with AIML | NTT DOCOMO | pCR | Approval |
6.20.1Study on intent driven management services for mobile network phase 4
| Yes |
YesE/// disagreed
Huawei: req.1 needs to reword.
| revised | No | S5‑254657 | |
| S5‑254415 | pCR on Rel-20 TR 28.881 Add use-case description, requirement and solution for enhancing feasibility check | NTT DOCOMO | pCR | Approval |
6.20.1Study on intent driven management services for mobile network phase 4
| Yes |
YesNokia did not agree with Requirement 2.
| revised | No | S5‑254649 | |
| S5‑254416 | pCR on Rel-20 TR 28.889 Add use case description and requirement for Network Maintenance CCL | NTT DOCOMO | pCR | Approval |
6.20.10Study on Closed Control Loop Management phase 2
| Yes |
YesHuawei: does not look like a CL.
Nokia: req. too generic
| revised | No | S5‑254702 | |
| S5‑254417 | Pseudo-CR on TR 28.881 Add new use case for supporting collaborative deployment of intent handling function and CCL | China Mobile E-Commerce Co. | pCR | Approval |
6.20.1Study on intent driven management services for mobile network phase 4
| Yes |
Yes
| withdrawn | Yes | ||
| S5‑254418 | Pseudo-CR on TR 28.881 Add new use case for natural language intents translation and execution | China Mobile E-Commerce Co. | pCR | Approval |
6.20.1Study on intent driven management services for mobile network phase 4
| Yes |
Yes
| withdrawn | Yes | ||
| S5‑254419 | Pseudo-CR TR28.869 Terminology alignment | DOCOMO Beijing Labs | pCR | Approval |
6.19.6Study on Cloud Aspects of Management and Orchestration
| Yes |
YesE///: same comments like last meeting.
NTT: the discussion about the difference between cloud native VNF and VNF deployment already happened one year ago.
E///;: VNF generic functions are defined outside of the model.
| revised | No | S5‑254879 | |
| S5‑254420 | Pseudo-CR TR28.869 Config management updates | DOCOMO Beijing Labs | pCR | Approval |
6.19.6Study on Cloud Aspects of Management and Orchestration
| Yes |
Yes
| revised | No | S5‑254734 | |
| S5‑254421 | Pseudo-CR TR 28.869 Traffic management function updates | DOCOMO Beijing Labs | pCR | Approval |
6.19.6Study on Cloud Aspects of Management and Orchestration
| Yes |
YesNokia objected.
| noted | No | ||
| S5‑254422 | Pseudo-CR TR 28.869 Recommendation for LCM of NF Deployment | DOCOMO Beijing Labs | pCR | Approval |
6.19.6Study on Cloud Aspects of Management and Orchestration
| Yes |
YesEricsson: disagreed to extend the current scope.
merged into S5-254633
| merged | No | ||
| S5‑254423 | Pseudo-CR TR 28.869 Evaluation of VNF generic OAM functions | DOCOMO Beijing Labs | pCR | Approval |
6.19.6Study on Cloud Aspects of Management and Orchestration
| Yes |
Yesmerged with S5-254571
Huawei disagree with 2. paragraph. Nokia agreed.
| merged | No | ||
| S5‑254424 | Pseudo-CR TR 28.869 Conclusions for VNF generic OAM functions | DOCOMO Beijing Labs | pCR | Approval |
6.19.6Study on Cloud Aspects of Management and Orchestration
| Yes |
YesNTT disagreed to remove the last paragraph.
Samsung: why does the consumer need to provide an IP address?
merged into S5-254636
| merged | No | ||
| S5‑254425 | Pseudo-CR on Time Issue of External Management Data | Nokia | pCR | Approval |
6.20.8Study for Data management phase 3
| Yes |
YesSamsung: what is event schedule, UE path?
| revised | No | S5‑254689 | |
| S5‑254426 | Pseudo-CR on Clarification of Mechanisms to Discover Management Data | Nokia | pCR | Approval |
6.20.8Study for Data management phase 3
| Yes |
YesHuawei: we have got 2 mechanisms for discovery
NTT: should align use case title with problem description.
| revised | No | S5‑254690 | |
| S5‑254427 | Pseudo-CR on Clarification of Mechanisms to Request and Retrieve Management Data | Nokia | pCR | Approval |
6.20.8Study for Data management phase 3
| Yes |
YesE///: is not description of use case, looks rather than an inventary.
NTT: use case title should be aligned
| revised | No | S5‑254691 | |
| S5‑254428 | Rel-19 CR TS 28.561 editorial corrections and clarifications | DOCOMO Beijing Labs | CR | Agreement |
6.19.5Management aspects of Network Digital Twins
| Yes |
YesHuawei: keep Brit. ENG.
| revised | No | S5‑254764 | |
| S5‑254429 | Rel-19 TS 28.105 correction to MLTrainingProcess attributes | NEC | CR | Agreement |
6.19.1AI/ML management phase 2
| Yes |
Yes
| revised | No | S5‑254784 | |
| S5‑254430 | Rel-18 TS 28.105 correction to MLTrainingProcess attributes | NEC | CR | Agreement |
6.6.3AI/ML management
| Yes |
Yesadd FORGE link
E/// offline comments
| revised | No | S5‑254783 | |
| S5‑254431 | Rel-20 CR 32.277 CHF CDR closure | Nokia | CR | Agreement |
7.3Charging Maintenance and Rel-20 Charging small enhancements
| Yes |
Yes
| withdrawn | Yes | ||
| S5‑254432 | Rel-20 CR 32.277 Charging Reflection to UE | Nokia | CR | Agreement |
7.3Charging Maintenance and Rel-20 Charging small enhancements
| No |
Yes
| withdrawn | Yes | ||
| S5‑254433 | Rel-19 CR TS 28.541 Correct the issues for MWAB NRM fragment | China Mobile, Huawei | CR | Agreement |
6.19.135G Advanced NRM features phase 3
| Yes |
Yes
| revised | No | S5‑254775 | |
| S5‑254434 | Rel-20 CR TS 28.541 Correct the issues for MWAB NRM fragment | China Mobile, HUAWEI | CR | Approval |
6.20.115G Advanced NRM features phase 4
| Yes |
Yes
| withdrawn | Yes | ||
| S5‑254435 | Rel-20 CR TS 28.541 Correct the issues for MWAB NRM fragment | China Mobile, Huawei | CR | Agreement |
6.19.135G Advanced NRM features phase 3
| Yes |
Yes
| revised | No | S5‑254776 | |
| S5‑254436 | Pseudo-CR on TR 28.881 Add new use case for supporting collaborative deployment of intent handling function and CCL | China Mobile E-Commerce Co. | pCR | Approval |
6.20.1Study on intent driven management services for mobile network phase 4
| Yes |
YesSamsung: reqs. 1-2 are not correct.
Nokia: this pCR is not needed.
| noted | No | ||
| S5‑254437 | Pseudo-CR on TR 28.881 Add new use case for natural language intents translation and execution | China Mobile E-Commerce Co. | pCR | Approval |
6.20.1Study on intent driven management services for mobile network phase 4
| Yes |
Yes
| withdrawn | Yes | ||
| S5‑254438 | Pseudo-CR on TR 28.881 Add new use case for natural language intents translation and execution | China Mobile E-Commerce Co. | pCR | Approval |
6.20.1Study on intent driven management services for mobile network phase 4
| Yes |
Yesmerged into S5-254658
| merged | No | ||
| S5‑254439 | Rel-20 CR TS 28.541 Enhance the NRM fragment for RedCap Access | Huawei | CR | Agreement |
6.20.115G Advanced NRM features phase 4
| Yes |
Yes
| revised | No | S5‑254715 | |
| S5‑254440 | Rel-19 CR TS 28.567 Correction on CCL Purpose | NTT DOCOMO | CR | Agreement |
6.19.4Closed Control Loop Management
| Yes |
Yes
| revised | No | S5‑254761 | |
| S5‑254441 | Rel-19 CR TS 28.567 Correction on Stage-3 Fault Management CCL | NTT DOCOMO | CR | Agreement |
6.19.4Closed Control Loop Management
| Yes |
Yes
| agreed | No | ||
| S5‑254442 | Rel-20 pCR 28.886 RET Analytics | Samsung R&D Institute India | pCR | Approval |
6.20.7Study on Management Data Analytics (MDA) phase 4
| No |
Yes
| withdrawn | Yes | ||
| S5‑254443 | pCR TR 28.882 Add new use case for ML model deployment phase | China Mobile | pCR | Approval |
6.20.2Study on AI/ML management phase 3
| Yes |
Yes
| withdrawn | Yes | ||
| S5‑254444 | pCR TR 28.882 Add new use cases of ML workflow | China Mobile | pCR | Approval |
6.20.2Study on AI/ML management phase 3
| Yes |
Yes
| withdrawn | Yes | ||
| S5‑254445 | pCR TR 28.882 Add new use cases Management of AIML monitoring | China Mobile | pCR | Approval |
6.20.2Study on AI/ML management phase 3
| Yes |
Yes
| withdrawn | Yes | ||
| S5‑254446 | Rel-20 pCR 28.886 RET Analytics | Samsung R&D Institute India | pCR | Approval |
6.20.7Study on Management Data Analytics (MDA) phase 4
| Yes |
Yes
| revised | No | S5‑254686 | |
| S5‑254447 | Rel-20 pCR 28.889 CCL for LCM | Samsung R&D Institute India | pCR | Agreement |
6.20.10Study on Closed Control Loop Management phase 2
| Yes |
YesNokia: use cases should be separate
E///: should be more speific
| revised | No | S5‑254703 | |
| S5‑254448 | Rel-20 CR 28.541 NRM extensions for MWAB Ph2 Stage 2 and Stage 3 | Samsung R&D Institute India | CR | Agreement |
6.20.115G Advanced NRM features phase 4
| Yes |
Yes
| revised | No | S5‑254706 | |
| S5‑254449 | pCR TR 28.888 Add structure for enhanced exposure of management services study report | Huawei | pCR | Approval |
6.20.9Study on Enhanced exposure of management services
| Yes |
Yes
| approved | No | ||
| S5‑254450 | pCR TR 28.888 Add concepts and background | Huawei | pCR | Approval |
6.20.9Study on Enhanced exposure of management services
| Yes |
YesNokia: needs maybe to be merged with S5-254567.
| revised | No | S5‑254694 | |
| S5‑254451 | pCR TR 28.888 Add use case on transformation of MnS information for external MnS consumers | Huawei | pCR | Approval |
6.20.9Study on Enhanced exposure of management services
| Yes |
Yes
| revised | No | S5‑254696 | |
| S5‑254452 | pCR TR 28.884 Add introduction for SBMA study report | Huawei | pCR | Approval |
6.20.4Study on Service Based Management Architecture enhancement phase 4
| Yes |
YesEricsson supports. But don't use normative language.
| revised | No | S5‑254676 | |
| S5‑254453 | pCR TR 28.884 Add scope for SBMA study report | Huawei | pCR | Approval |
6.20.4Study on Service Based Management Architecture enhancement phase 4
| Yes |
YesEricsson: is a 5G study.
| revised | No | S5‑254677 | |
| S5‑254454 | pCR TR 28.884 Add structure for SBMA study report | Huawei | pCR | Approval |
6.20.4Study on Service Based Management Architecture enhancement phase 4
| Yes |
Yes
| approved | No | ||
| S5‑254455 | pCR TR 28.884 Add concepts and background | Huawei | pCR | Approval |
6.20.4Study on Service Based Management Architecture enhancement phase 4
| Yes |
YesE///: 2. paragraph not needed.
| revised | No | S5‑254678 | |
| S5‑254456 | pCR TR 28.884 Use case on software management | Huawei | pCR | Approval |
6.20.4Study on Service Based Management Architecture enhancement phase 4
| Yes |
YesNokia: agreed with Samsung about 4G.
| revised | No | S5‑254679 | |
| S5‑254457 | pCR TR 28.884 Use case on inventory management | Huawei | pCR | Approval |
6.20.4Study on Service Based Management Architecture enhancement phase 4
| Yes |
YesNTT OOMO disagreed.
| revised | No | S5‑254680 | |
| S5‑254458 | pCR TR 28.884 Use case on integration of SBMA with 5GC and 5G Access Network architecture | Huawei | pCR | Approval |
6.20.4Study on Service Based Management Architecture enhancement phase 4
| Yes |
YesE///: determine what is lacking.
NEC: justification for requirements is needed.
| revised | No | S5‑254681 | |
| S5‑254459 | pCR TR 28.884 Management data streaming based on message bus | Huawei | pCR | Approval |
6.20.4Study on Service Based Management Architecture enhancement phase 4
| Yes |
YesRakuten: support this use case.
Nokia: different remarks
E///: we are jumping to conclusions here.
Disadvantages for message bus? Would like to handle with framework in 6G.
| revised | No | S5‑254682 | |
| S5‑254460 | Rel-19 CR 32.298 Correction of userDisasterRoamingInd | Ericsson | CR | Agreement |
7.3Charging Maintenance and Rel-20 Charging small enhancements
| Yes |
Yes
| agreed | No | ||
| S5‑254461 | Rel-19 CR 32.298 Correction of SatelliteID | Ericsson | CR | Agreement |
7.3Charging Maintenance and Rel-20 Charging small enhancements
| Yes |
Yes
| agreed | No | ||
| S5‑254462 | Rel-20 pCR 28.891 Key issue regarding reference points and chargeable events | Ericsson | pCR | Approval |
7.5.1Charging Aspects of CAPIF Phase 3
| Yes |
Yes
| revised | No | S5‑254808 | |
| S5‑254463 | Rel-20 pCR 28.891 Charging architecture considerations for CAPIF reference points | Ericsson | pCR | Approval |
7.5.1Charging Aspects of CAPIF Phase 3
| Yes |
Yes
| withdrawn | Yes | ||
| S5‑254464 | Rel-20 pCR 32.801-02 Study structure 6G business models | Ericsson | pCR | Approval |
7.6.1Charging Aspects of 6G System
| Yes |
YesMerged into S5-254360
| merged | No | ||
| S5‑254465 | Rel-20 pCR 32.801-02 Study structure 6G charging architecture and mechanism | Ericsson | pCR | Approval |
7.6.1Charging Aspects of 6G System
| Yes |
Yes
| revised | No | S5‑254820 | |
| S5‑254466 | Rel-20 pCR 32.801-02 Structuring of OpenAPI | Ericsson | pCR | Approval |
7.6.1Charging Aspects of 6G System
| Yes |
Yes
| withdrawn | Yes | ||
| S5‑254467 | Rel-20 pCR 32.801-02 Structuring of ASN.1 | Ericsson | pCR | Approval |
7.6.1Charging Aspects of 6G System
| Yes |
Yes
| withdrawn | Yes | ||
| S5‑254468 | Rel-20 pCR 32.801-02 Solution structuring of OpenAPI | Ericsson | pCR | Approval |
7.6.1Charging Aspects of 6G System
| Yes |
Yes
| withdrawn | Yes | ||
| S5‑254469 | Rel-20 pCR 32.801-02 Solution structuring of ASN.1 | Ericsson | pCR | Approval |
7.6.1Charging Aspects of 6G System
| Yes |
Yes
| withdrawn | Yes | ||
| S5‑254470 | Pseudo-CR on TR 28.883 Add enhanced evaluation use cases | Huawei Tech. Japan, K.K. | pCR | Approval |
6.20.3Study on management aspects of Network Digital Twins phase 2
| Yes |
YesZTE: can not provide predictions?
Nokia objects, it's analytics, not NDT.
Ericsson agreed, should not bring in intelligence.
| noted | No | ||
| S5‑254471 | Pseudo-CR on TR 28.886 Add requirements and solution for failure resolution | Huawei, China Mobile | pCR | Approval |
6.20.7Study on Management Data Analytics (MDA) phase 4
| Yes |
YesNokia: req. look like traditional FM req.
| revised | No | S5‑254688 | |
| S5‑254472 | Pseudo-CR on TR 28.886 Add solution for MDA scope | Huawei Tech. Japan, K.K. | pCR | Approval |
6.20.7Study on Management Data Analytics (MDA) phase 4
| Yes |
Yes
| revised | No | S5‑254782 | |
| S5‑254473 | Pseudo-CR on TR 28.889 Add status monitoring use case | Huawei Tech. Japan, K.K. | pCR | Approval |
6.20.10Study on Closed Control Loop Management phase 2
| Yes |
YesNokia: CCL should not initiate a new CCL
| revised | No | S5‑254704 | |
| S5‑254474 | Rel-18 CR TS 28.541 Update the reference for YANG Data Models for 'Attachment Circuits'-as-a-Service (ACaaS) to RFC 9834 | Huawei | CR | Agreement |
6.6.11Additional NRM features phase 2
| Yes |
YesE///: we will update FORGE procedures for Yang.
| agreed | No | ||
| S5‑254475 | Rel-19 CR TS 28.541 Update the reference for YANG Data Models for 'Attachment Circuits'-as-a-Service (ACaaS) to RFC 9834 | Huawei | CR | Agreement |
6.6.11Additional NRM features phase 2
| Yes |
Yes
| agreed | No | ||
| S5‑254476 | Rel-20 CR TS 28.541 Update the reference for YANG Data Models for 'Attachment Circuits'-as-a-Service (ACaaS) to RFC 9834 | Huawei | CR | Agreement |
6.6.11Additional NRM features phase 2
| Yes |
Yes
| agreed | No | ||
| S5‑254477 | pCR TR 28.881 Add use case for the investigation on the transition of intent Lifecycle management state | Huawei | pCR | Approval |
6.20.1Study on intent driven management services for mobile network phase 4
| Yes |
Yes
| revised | No | S5‑254654 | |
| S5‑254478 | pCR TR 28.881 Add use case for the investigation on coordination between conflict resolution mechanisms | Huawei | pCR | Approval |
6.20.1Study on intent driven management services for mobile network phase 4
| Yes |
Yes
| noted | No | ||
| S5‑254479 | Rel-19 TS 28.105 corrections related to CR implementation in v19.3.0 | NEC | CR | Agreement |
6.19.1AI/ML management phase 2
| Yes |
YesSA5
ETSI MCC: don't reuse Voided Table number
| revised | No | S5‑254752 | |
| S5‑254480 | pCR TR 28.883 Introduce precision in the execution of network simulation tasks | Huawei | pCR | Approval |
6.20.3Study on management aspects of Network Digital Twins phase 2
| Yes |
Yesdiscussed in breakout
| revised | No | S5‑254882 | |
| S5‑254481 | Rel-19 CR 32.255 Correction of general principles | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-20 Charging small enhancements
| Yes |
Yes
| revised | No | S5‑254825 | |
| S5‑254482 | Rel-19 CR 32.255 Correction on the Charging data response message | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-20 Charging small enhancements
| Yes |
Yes
| agreed | No | ||
| S5‑254483 | Rel-19 CR 32.260 Correction on the Abbreviations | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-20 Charging small enhancements
| Yes |
Yes
| revised | No | S5‑254837 | |
| S5‑254484 | Rel-19 CR 32.290 Corrections to the misalignment and editorial errors of charging scenarios | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-20 Charging small enhancements
| Yes |
Yes
| revised | No | S5‑254838 | |
| S5‑254485 | Rel-19 CR 32.290 Corrections on quota management | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-20 Charging small enhancements
| Yes |
Yes
| revised | No | S5‑254827 | |
| S5‑254486 | Rel-19 CR 32.291 Correction on the re-used data types of Nchf_ConvergedCharging | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-20 Charging small enhancements
| Yes |
Yes
| revised | No | S5‑254828 | |
| S5‑254487 | Rel-19 CR 28.201 Addition on NSPA charging information | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-20 Charging small enhancements
| Yes |
Yes
| revised | No | S5‑254823 | |
| S5‑254488 | Rel-20 pCR 32.872 Add definitions of terms, symbols and abbreviations | Huawei | pCR | Approval |
7.5.25GA Roaming Charging Reliability Enhancement
| Yes |
Yes
| approved | No | ||
| S5‑254489 | Rel-20 pCR 32.872 Add reference | Huawei | pCR | Approval |
7.5.25GA Roaming Charging Reliability Enhancement
| Yes |
Yes
| approved | No | ||
| S5‑254490 | Rel-20 pCR 32.872 Add scope | Huawei | pCR | Approval |
7.5.25GA Roaming Charging Reliability Enhancement
| Yes |
Yes
| approved | No | ||
| S5‑254491 | Rel-20 pCR 32.872 Introduce the background for roaming charging | Huawei | pCR | Approval |
7.5.25GA Roaming Charging Reliability Enhancement
| Yes |
Yes
| approved | No | ||
| S5‑254492 | Rel-20 pCR 32.872 Introduce the usecase1 on Local Breakout Inter CHFs | Huawei | pCR | Approval |
7.5.25GA Roaming Charging Reliability Enhancement
| Yes |
Yes
| revised | No | S5‑254812 | |
| S5‑254493 | Rel-20 pCR 32.872 Introduce the usecase2 on Local Breakout Inter CHFs | Huawei | pCR | Approval |
7.5.25GA Roaming Charging Reliability Enhancement
| Yes |
Yes
| revised | No | S5‑254813 | |
| S5‑254494 | Rel-20 pCR 32.872 Introduce the usecase3 on Local Breakout Inter CHFs | Huawei | pCR | Approval |
7.5.25GA Roaming Charging Reliability Enhancement
| Yes |
Yes
| revised | No | S5‑254814 | |
| S5‑254495 | Rel-20 pCR 32.872 Introduce the usecase on Home Routed scenario | Huawei | pCR | Approval |
7.5.25GA Roaming Charging Reliability Enhancement
| Yes |
Yes
| revised | No | S5‑254815 | |
| S5‑254496 | Mapping with SA1 Charging Requirement | Huawei | discussion | Discussion |
7.1Charging Plenary
| Yes |
Yes
| noted | No | S5‑254801 | |
| S5‑254497 | Rel-19 CR 32.255 Clarify the CHF selection method | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-20 Charging small enhancements
| Yes |
Yes
| revised | No | S5‑254829 | |
| S5‑254498 | Discussion paper on the Charging parameters Categories | Huawei | discussion | Endorsement |
7.3Charging Maintenance and Rel-20 Charging small enhancements
| Yes |
YesM: The historic reason was the unknow content of a attrtibute was possible and caused errors in the BS therefore are Oc and Om were needed.
The issue on inconsistent treatment of categories between different WGs in 3GPP is addressed under the SA topic for TS modernization.
| noted | No | ||
| S5‑254499 | Discussion Paper on the Network Slice Related Spending Limit Control | Huawei | discussion | Endorsement |
7.3Charging Maintenance and Rel-20 Charging small enhancements
| Yes |
Yes
| noted | No | ||
| S5‑254500 | LS on Extending spending limit control Support for network slice | SA5 | LS out | Approval |
7.3Charging Maintenance and Rel-20 Charging small enhancements
| Yes |
Yes
| noted | No | ||
| S5‑254501 | Discussion paper on the CHF Group ID | Huawei | discussion | Endorsement |
7.3Charging Maintenance and Rel-20 Charging small enhancements
| Yes |
YesTS 29.504 clear indicates the providion of CHF Group Id to AMF
M: SA2 didn’t addressed any problem with CT specificationstherefore is SA5 not able to act to CT4
| noted | No | ||
| S5‑254502 | Rel-19 CR 32.255 Clarification on CHF address and Charging Characteristics | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-20 Charging small enhancements
| Yes |
Yes
| revised | No | S5‑254830 | |
| S5‑254503 | Rel-19 CR 32.274 Clarification on CHF address and Charging Characteristics | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-20 Charging small enhancements
| Yes |
Yes
| revised | No | S5‑254831 | |
| S5‑254504 | Rel-19 CR 32.256 Clarification on CHF address and Charging Characteristics | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-20 Charging small enhancements
| Yes |
YesSame request as in S5-254502
| revised | No | S5‑254832 | |
| S5‑254505 | Reply LS on Extending Charging Support in 5GC | SA5 | LS out | Approval |
7.3Charging Maintenance and Rel-20 Charging small enhancements
| Yes |
YesM: The original LS is noted and a new LS is required
| withdrawn | Yes | ||
| S5‑254506 | pCR TR 32.801-02 Add background for the 6G Charging | Huawei | pCR | Approval |
7.6.1Charging Aspects of 6G System
| Yes |
Yes
| revised | No | S5‑254817 | |
| S5‑254507 | pCR TR 32.801-02 Add 6G Charging business model | Huawei | pCR | Approval |
7.6.1Charging Aspects of 6G System
| Yes |
YesThis background has been addressed already by 3GPP for 6G therefore will 5.1 been removed.
E: 6G service should be sufificient without examples
API invoker and developer is not clear – remove it
AI token is also not clear
SMNO was also removed in the past
N: customer and stakeholder are for charged(charging parties
MVNO could be also SAT provider
C: what is the difference between industry partners and vertical partners? -> industry/vertical partners should be used
Merged into S5-254360
| merged | No | ||
| S5‑254508 | pCR TR 32.801-02 Add general description for WT2.1 6G converged charging | Huawei | pCR | Approval |
7.6.1Charging Aspects of 6G System
| Yes |
YesThis pCR covers the Charging architecture topic and merged into S5-254465
Chair: Not pursued
| not pursued | No | ||
| S5‑254509 | pCR TR 32.801-02 Add general description for WT2.1 flexible charging | Huawei | pCR | Approval |
7.6.1Charging Aspects of 6G System
| Yes |
Yes
| revised | No | S5‑254821 | |
| S5‑254510 | Rel-19 CR TS 32.422 Corrections on Trace Failure Notification | Nokia | CR | Agreement |
6.19.11Data management regarding subscriptions and reporting
| Yes |
Yes
| revised | No | S5‑254511 | |
| S5‑254511 | Rel-19 CR TS 32.422 Corrections on Trace Failure Notification | Nokia | CR | Agreement |
6.19.11Data management regarding subscriptions and reporting
| Yes |
Yes
| revised | No | S5‑254772 | S5‑254510 |
| S5‑254512 | Pseudo-CR on TR 28.882 Add New Use Case on Management Support for Dataset and Model Parameters Exchange | ZTE Corporation | pCR | Approval |
6.20.2Study on AI/ML management phase 3
| Yes |
YesVIVO: need more discussion.
| noted | No | ||
| S5‑254513 | Pseudo-CR on Introduction for data management phase-3 | Ericsson Telecomunicazioni SpA | pCR | Approval |
6.20.8Study for Data management phase 3
| Yes |
Yes
| revised | No | S5‑254692 | |
| S5‑254514 | Rel-20 pCR TR 28.882 Add new use case and requirements on AI/ML Model Inference Complexity | Nokia Canada | pCR | Approval |
6.20.2Study on AI/ML management phase 3
| Yes |
Yes
| revised | No | S5‑254747 | |
| S5‑254515 | Pseudo-CR on TR 28.883 Add New Use Case on Capability Discovery of NDT in NDT Collaboration | ZTE Corporation | pCR | Agreement |
6.20.3Study on management aspects of Network Digital Twins phase 2
| Yes |
Yes
| revised | No | S5‑254674 | |
| S5‑254516 | Rel-20 pCR TR 28.882 Add new use case and requirements on Minimum acceptable performance for AI/ML Model Training | Nokia Canada | pCR | Approval |
6.20.2Study on AI/ML management phase 3
| Yes |
Yes
| revised | No | S5‑254748 | |
| S5‑254517 | Rel-20 pCR TR 28.882 Add New Use Case on Enhancement on LCM of Federated Learning | Samsung Electronics France SA | pCR |
6.20.2Study on AI/ML management phase 3
| Yes |
Yes
| withdrawn | Yes | |||
| S5‑254518 | Rel-19 CR TS 28.541 Clarify usage of CESManagementFunction | Nokia | CR | Agreement |
6.19.20Energy efficiency and energy saving aspects of 5G networks and services
| Yes |
YesHuawei: this is not Cat. D, better submit a Rel-20 CR or a pCR.
| revised | No | S5‑254794 | |
| S5‑254519 | Rel-20 CR TS 28.541 Clarify usage of CESManagementFunction | Nokia | CR | Agreement |
6.19.20Energy efficiency and energy saving aspects of 5G networks and services
| Yes |
Yes
| revised | No | S5‑254795 | |
| S5‑254520 | pCR on Rel-20 TR 28.885 Add TR structure | Nokia | pCR | Approval |
6.20.5Study on energy efficiency and energy saving aspects of 5G Advanced
| Yes |
Yes///: overlaps with S5-254612
| revised | No | S5‑254683 | |
| S5‑254521 | pCR on Rel-20 TR 28.885 Add new use case support of energy-related characteristics | Nokia | pCR | Approval |
6.20.5Study on energy efficiency and energy saving aspects of 5G Advanced
| Yes |
YesE///: is it NE or NF? The use case does not specify the purpose.
We should not copy the requirements from SA1.
| revised | No | S5‑254698 | |
| S5‑254522 | pCR on Rel-20 TR 28.885 Add new use case related to service adjustments to adapt to energy-related characteristics | Nokia | pCR | Approval |
6.20.5Study on energy efficiency and energy saving aspects of 5G Advanced
| Yes |
Yesseveral offline comments
| revised | No | S5‑254699 | |
| S5‑254523 | pCR on Rel-20 TR 28.885 Add new use case related to different energy states | Nokia | pCR | Approval |
6.20.5Study on energy efficiency and energy saving aspects of 5G Advanced
| Yes |
YesNokia objected
| noted | No | ||
| S5‑254524 | pCR on Rel-20 TR 28.885 Add new use case to support network energy saving optimizations across operators | Nokia | pCR | Approval |
6.20.5Study on energy efficiency and energy saving aspects of 5G Advanced
| Yes |
Yes
| revised | No | S5‑254701 | |
| S5‑254525 | pCR on Rel-20 TR 28.885 Add new use case for enhancements to reporting EC and EE at per network slice granularity | Nokia | pCR | Approval |
6.20.5Study on energy efficiency and energy saving aspects of 5G Advanced
| Yes |
Yes
| revised | No | S5‑254738 | |
| S5‑254526 | pCR on Rel-20 TR 28.885 Add new use case to study Enhancements to NF Profile to support energy saving and energy efficiency | Nokia | pCR | Approval |
6.20.5Study on energy efficiency and energy saving aspects of 5G Advanced
| Yes |
Yes
| revised | No | S5‑254739 | |
| S5‑254527 | pCR on Rel-20 TR 28.885 Add new use case to study measuring of EC of NE at per Energy Supply granularity | Nokia | pCR | Approval |
6.20.5Study on energy efficiency and energy saving aspects of 5G Advanced
| Yes |
Yes
| revised | No | S5‑254740 | |
| S5‑254528 | pCR on Rel-20 TR 28.885 Add new use case to study EC and EE per PLMNID in Network sharing scenario | Nokia | pCR | Approval |
6.20.5Study on energy efficiency and energy saving aspects of 5G Advanced
| Yes |
Yes
| revised | No | S5‑254741 | |
| S5‑254529 | Pseudo-CR on Scope for data management phase-3 | Ericsson Telecomunicazioni SpA | pCR | Approval |
6.20.8Study for Data management phase 3
| Yes |
Yesdiscussion about UE data collection
| revised | No | S5‑254693 | |
| S5‑254530 | pCR TR 28.882 Add new use cases of ML workflow | China Mobile | pCR | Approval |
6.20.2Study on AI/ML management phase 3
| Yes |
Yes
| revised | No | S5‑254668 | |
| S5‑254531 | pCR TR 28.882 Add new use cases Management of AIML monitoring | China Mobile | pCR | Approval |
6.20.2Study on AI/ML management phase 3
| Yes |
Yes
| revised | No | S5‑254745 | |
| S5‑254532 | New SID on 5GA Charging aspects of ISAC | China Unicom | SID new | Approval |
7.2.1New CH SIDs/WIDs proposals
| Yes |
Yes
| treated | No | S5‑254804 | |
| S5‑254533 | pCR TR 28.882 Add new use case for ML model deployment phase | China Mobile | pCR | Approval |
6.20.2Study on AI/ML management phase 3
| Yes |
Yes
| revised | No | S5‑254746 | |
| S5‑254534 | Rel-19 CR TS 28.541 A-IoT Configurations Stage2 and Stage3 alignment | Samsung Electronics France SA | CR | Agreement |
6.19.135G Advanced NRM features phase 3
| Yes |
Yes
| agreed | No | ||
| S5‑254535 | SA5 Working Methods maintenance of TSs | Ericsson | other |
5.1Administrative issues at SA5 level
| Yes |
Yesmerged into S5-254623
| merged | No | |||
| S5‑254536 | PCR TR 28.822 Rel-20 5GA Sustainability use case and requirements | Ericsson Telecom S.A. de C.V. | pCR | Approval |
6.20.2Study on AI/ML management phase 3
| Yes |
Yes
| revised | No | S5‑254669 | |
| S5‑254537 | Rel-19 CR 28.552 Correct clause title | Ericsson | CR | Agreement |
6.19.125G performance measurements and KPIs phase 4
| Yes |
Yes
| revised | No | S5‑254773 | S5‑253673 |
| S5‑254538 | Rel-20 CR 28.552 Correct clause title | Ericsson | CR | Agreement |
6.19.125G performance measurements and KPIs phase 4
| Yes |
Yes
| revised | No | S5‑254774 | S5‑253673 |
| S5‑254539 | Rel-19 TS 28.105 clarifications on MLModel and MLTrainingRequest attributes | NEC | CR | Agreement |
6.19.1AI/ML management phase 2
| Yes |
YesSA5
Nokia proposed an offline discussion.
| revised | No | S5‑254753 | |
| S5‑254540 | Rel-19 CR 28.552 PM for inter-CU LTM | Ericsson | CR | Agreement |
6.19.125G performance measurements and KPIs phase 4
| Yes |
Yes
| agreed | No | S5‑254108 | |
| S5‑254541 | Rel-20 CR 28.552 PM for inter-CU LTM | Ericsson | CR | Agreement |
6.19.125G performance measurements and KPIs phase 4
| Yes |
Yeserror! same common root CR!!
| agreed | No | S5‑254108 | |
| S5‑254542 | Rel-19 CR 28.552 PM for intra-CU conditional LTM | Ericsson | CR | Agreement |
6.19.125G performance measurements and KPIs phase 4
| Yes |
Yes
| agreed | No | S5‑254109 | |
| S5‑254543 | Rel-20 CR 28.552 PM for intra-CU conditional LTM | Ericsson | CR | Agreement |
6.19.125G performance measurements and KPIs phase 4
| Yes |
Yeserror! same common root CR!!
| agreed | No | S5‑254109 | |
| S5‑254544 | Rel-19 CR 28.554 Update mobility KPI for LTM | Ericsson | CR | Agreement |
6.19.125G performance measurements and KPIs phase 4
| Yes |
Yes
| agreed | No | S5‑253677 | |
| S5‑254545 | Rel-19 TS 28.105 clarifications on the use of mLTrainingType attributes | NEC | CR | Agreement |
6.19.1AI/ML management phase 2
| Yes |
Yes
| revised | No | S5‑254754 | |
| S5‑254546 | New WID on Life Cycle Management (LCM) of NF Deployment | Ericsson Limited, Nokia, AT&T, Verizon | WID new | Approval |
6.2.1New OAM SIDs/WIDs proposals
| Yes |
Yessame like S5-254388.
| revised | No | S5‑254889 | |
| S5‑254547 | pCR TR 28.869 Recommendation for LCM of NF Deployment | Ericsson Limited, Nokia, AT&T, Rakuten | pCR | Approval |
6.19.6Study on Cloud Aspects of Management and Orchestration
| Yes |
Yes
| revised | No | S5‑254633 | |
| S5‑254548 | Rel-18 CR 28.622 Fix inheritance diagram and definitions | Ericsson Canada Inc. | CR | Agreement |
6.6.11Additional NRM features phase 2
| No |
Yes
| withdrawn | Yes | ||
| S5‑254549 | Rel-20 CR 28.622 Fix inheritance diagram and definitions | Ericsson Canada Inc. | CR | Agreement |
6.19.135G Advanced NRM features phase 3
| Yes |
Yes
| agreed | No | ||
| S5‑254550 | Rel-19 CR Update to management of IAB-node for NCI reconfiguration | Ericsson | CR | Agreement |
6.19.16Management of IAB nodes
| Yes |
Yes
| revised | No | S5‑254631 | |
| S5‑254551 | Rel-19 CR TS 28.541 Additional AIoT NRM Configurations | Samsung Electronics France SA | CR | Agreement |
6.19.135G Advanced NRM features phase 3
| Yes |
Yes
| revised | No | S5‑254777 | |
| S5‑254552 | Rel-20 CR Update to management of IAB-node for NCI reconfiguration | Ericsson | CR | Agreement |
6.19.16Management of IAB nodes
| Yes |
Yes
| revised | No | S5‑254632 | |
| S5‑254553 | Pseudo-CR on TR 28.881 Add potential solution for UC#4 intent traceability | Ericsson Canada Inc. | pCR | Agreement |
6.20.1Study on intent driven management services for mobile network phase 4
| Yes |
Yes
| revised | No | S5‑254660 | |
| S5‑254554 | Rel-18 CR TS 28.622 Clarify usage of notifyFileReady | Ericsson Canada Inc. | CR | Agreement |
6.6.95G performance measurements and KPIs phase 3
| Yes |
Yescl. aff.
+TS!
| revised | No | S5‑254872 | |
| S5‑254555 | Rel-19 CR TS 28.622 Clarify usage of notifyFileReady | Ericsson Canada Inc. | CR | Agreement |
6.6.95G performance measurements and KPIs phase 3
| Yes |
Yes
| revised | No | S5‑254873 | |
| S5‑254556 | Rel-20 CR TS 28.622 Clarify usage of notifyFileReady | Ericsson Canada Inc. | CR | Agreement |
6.6.95G performance measurements and KPIs phase 3
| Yes |
Yes
| revised | No | S5‑254874 | |
| S5‑254557 | Rel-20 CR TS 28.540 Add requirements for WAB-gNB management | Ericsson | CR | Agreement |
6.20.115G Advanced NRM features phase 4
| Yes |
Yes
| revised | No | S5‑254707 | |
| S5‑254558 | Rel-19 DP on Initial training | Ericsson España S.A. | discussion | Endorsement |
6.19.1AI/ML management phase 2
| Yes |
YesNokia objected.
| noted | No | ||
| S5‑254559 | Rel-19 CR TS 28.105 Initial training | Ericsson | CR | Agreement |
6.19.1AI/ML management phase 2
| Yes |
Yes
| revised | No | S5‑254755 | |
| S5‑254560 | Rel-18 CR TS 28.623 Clarify usage of notifyFileReady | Ericsson Canada Inc. | CR | Agreement |
6.6.95G performance measurements and KPIs phase 3
| Yes |
Yes
| agreed | No | ||
| S5‑254561 | Rel-19 CR TS 28.105 Training types in Training NRM fragment | Ericsson | CR | Agreement |
6.19.1AI/ML management phase 2
| Yes |
YesCMCC: cannot remove expectedinferencescope
Samsung, NTT, ZTE don't agree with the change.
| revised | No | S5‑254756 | |
| S5‑254562 | Rel-19 CR 28.623 Clarify usage of notifyFileReady | Ericsson Canada Inc. | CR | Agreement |
6.6.95G performance measurements and KPIs phase 3
| Yes |
Yes
| agreed | No | ||
| S5‑254563 | Rel-20 CR 28.623 Clarify usage of notifyFileReady | Ericsson Canada Inc. | CR | Agreement |
6.6.95G performance measurements and KPIs phase 3
| Yes |
Yes
| agreed | No | ||
| S5‑254564 | Rel-19 CR TS 28.105 Correct associations on Training NRM fragment | Ericsson | CR | Agreement |
6.19.1AI/ML management phase 2
| Yes |
Yes
| revised | No | S5‑254757 | |
| S5‑254565 | Rel-19 CR TS 28.105 Correct inference related attributes in MLModel | Ericsson | CR | Agreement |
6.19.1AI/ML management phase 2
| Yes |
YesCMCC: agreed with the problem, not the solution
E///: tried to provide clarification about this attribute
| revised | No | S5‑254758 | |
| S5‑254566 | Rel-20 pCR TR 28.888 Add use case and requirements for authorization of the external MnS consumers at the CCF | Nokia Mexico, Samsung | pCR | Approval |
6.20.9Study on Enhanced exposure of management services
| Yes |
YesE///: offline comments before the meeting. Objected.
| noted | No | ||
| S5‑254567 | Rel-20 pCR TR 28.888 Concepts and background on data sharing permissions | Nokia Mexico | pCR | Approval |
6.20.9Study on Enhanced exposure of management services
| Yes |
Yes///, Huawei: no merging needed, content is different.
| revised | No | S5‑254695 | |
| S5‑254568 | DP on comparison between management services exposure and O-RAN defined SME and DME | Nokia Mexico | discussion | Endorsement |
6.20.9Study on Enhanced exposure of management services
| Yes |
YesZTE: we don't endorse observations
E///: supports the general observations.
| revised | No | S5‑254697 | |
| S5‑254569 | DP on solutions for authorization of the external MnS consumers at the CCF | Nokia Mexico, Samsung | discussion | Endorsement |
6.20.9Study on Enhanced exposure of management services
| Yes |
YesE/// objected.
| noted | No | ||
| S5‑254570 | Modified EnExpo SID | Nokia Mexico | SID revised | Endorsement |
6.2.2Revised OAM SIDs/WIDs proposals
| Yes |
Yes+Samsung
| revised | No | S5‑254883 | |
| S5‑254571 | Rel-19 pCR TR 28.869 Add Evaluation to the use of VNF generic OAM functions | Nokia Mexico, Ericsson | pCR | Approval |
6.19.6Study on Cloud Aspects of Management and Orchestration
| Yes |
YesE///->NTT
| revised | No | S5‑254635 | |
| S5‑254572 | Rel-19 pCR TR 28.869 Add conclusions and recommendations to the use of VNF generic OAM functions | Nokia Mexico | pCR | Approval |
6.19.6Study on Cloud Aspects of Management and Orchestration
| Yes |
Yes+NTT
| revised | No | S5‑254636 | |
| S5‑254573 | Rel-20 pCR TR 28.883 Defining the Lifecycle and Runtime Behaviour of NDT Jobs | L.M. Ericsson Limited | pCR | Agreement |
6.20.3Study on management aspects of Network Digital Twins phase 2
| Yes |
Yes
| revised | No | S5‑254733 | |
| S5‑254574 | Discussion paper on UE data collection | Nokia | discussion | Endorsement |
6.20.8Study for Data management phase 3
| Yes |
YesE///: we need a study first. Prop. 5 & 6 were never discussed before.
NTT: prop. 1 we should study first.
VF: similar to E///, prop. 1 should be management data
Noted.
Can be further discussed.
| noted | No | ||
| S5‑254575 | LS on Clarifications for UE Data Collection | Nokia | LS out | Approval |
6.1OAM Plenary
| Yes |
YesE/// is not supportive of the LS.
Samsung, Huawei, ZTE same.
Vodafone: need more discussion.
| noted | No | ||
| S5‑254576 | Rel-19 CR TS 28.537 Correction for Deployment Scenario Description | Nokia | CR | Agreement |
6.19.10Data management phase 2
| Yes |
Yes
| revised | No | S5‑254768 | |
| S5‑254577 | Rel-19 CR TS 28.622 Corrections for Condition Monitor | Nokia | CR | Agreement |
6.19.10Data management phase 2
| Yes |
Yes
| revised | No | S5‑254769 | |
| S5‑254578 | Rel-20 CR TS 28.622 Corrections for Condition Monitor | Nokia | CR | Agreement |
6.19.10Data management phase 2
| Yes |
Yes
| revised | No | S5‑254770 | |
| S5‑254579 | Rel-19 CR TS 28.623 Corrections for Condition Monitor | Nokia | CR | Agreement |
6.19.10Data management phase 2
| Yes |
Yes
| revised | No | S5‑254771 | |
| S5‑254580 | Rel-18 CR TS 32.422 area scope correction | Ericsson | CR | Agreement |
6.6.8Management of Trace/MDT phase 2
| Yes |
YesNokia: why is the sentence removed?
Checked offline.
| agreed | No | S5‑254245 | |
| S5‑254581 | Rel-19 CR TS 28.561 Make NDTDataValue and NDTScalingFactor as conditional mandatory attributes | L.M. Ericsson Limited | CR | Agreement |
6.19.5Management aspects of Network Digital Twins
| Yes |
Yesno Tdoc#; del. '<'
| revised | No | S5‑254765 | |
| S5‑254582 | Rel-19 CR TS 28.622 area scope correction | Ericsson Japan K.K. | CR | Agreement |
6.6.8Management of Trace/MDT phase 2
| Yes |
Yes
| revised | No | S5‑254583 | S5‑254247 |
| S5‑254583 | Rel-19 CR TS 28.622 area scope correction | Ericsson | CR | Agreement |
6.6.8Management of Trace/MDT phase 2
| Yes |
Yes
| agreed | No | S5‑254582 | |
| S5‑254584 | pCR TR 28.882 initial ToC | NEC | pCR | Approval |
6.20.2Study on AI/ML management phase 3
| Yes |
Yeswrong version, 0.0.0 exists already.
| revised | No | S5‑254664 | |
| S5‑254585 | Rel-19 CR TS 28.623 NTN geographical area scope | Ericsson | CR | Agreement |
6.19.14Subscriber and Equipment Trace and QoE collection management
| Yes |
Yes
| agreed | No | S5‑254250 | |
| S5‑254586 | New WID on 5G Advanced Management Aspects of NTN Phase 3 | China Unicom, CATT | WID new | Approval |
6.2.1New OAM SIDs/WIDs proposals
| Yes |
Yesmaybe resubmit for the next meeting.
Have to get more supporting companies.
| noted | No | ||
| S5‑254587 | Fix attribute definitions with distinct ndtJobRef | L.M. Ericsson Limited | CR | Agreement |
6.19.5Management aspects of Network Digital Twins
| Yes |
YesMCC: no cl. aff.!
Huawei: is a false Cat. F
merged into S5-254762
| merged | No | ||
| S5‑254588 | Rel-19 CR TS 28.561 Add NDT job resume operation | L.M. Ericsson Limited | CR | Agreement |
6.19.5Management aspects of Network Digital Twins
| Yes |
Yes
| not pursued | No | ||
| S5‑254589 | Rel-20 CR TS28.541 Fix multiplicity and isOrdered property for hniList | ZTE Corporation | CR | Agreement |
6.20.0OAM Rel-20 small enhancements
| Yes |
Yes
| revised | No | S5‑254644 | |
| S5‑254590 | Rel-18 CR TS28.552 Fix MOI for VR usage of NF related PMs | ZTE Corporation | CR | Agreement |
6.6.26Rel-18 CAT B/C SA5 internal alignment and other CAT F CR(s)
| Yes |
YesE///: ->CUCPFunction!
| revised | No | S5‑254875 | |
| S5‑254591 | Rel-19 CR TS28.552 Fix MOI for VR usage of NF related PMs | ZTE Corporation | CR | Agreement |
6.6.26Rel-18 CAT B/C SA5 internal alignment and other CAT F CR(s)
| Yes |
Yes
| revised | No | S5‑254876 | |
| S5‑254592 | Rel-20 CR TS28.552 Fix MOI for VR usage of NF related PMs | ZTE Corporation | CR | Agreement |
6.6.26Rel-18 CAT B/C SA5 internal alignment and other CAT F CR(s)
| Yes |
Yes
| revised | No | S5‑254877 | |
| S5‑254593 | Rel-16 CR TS28.554 Add missing formula for InterGNBHOMeanTime and MobilityRegUpdateSR | ZTE Corporation | CR | Agreement |
6.4OAM Rel-16
| Yes |
Yesformat EQ
check formula
| revised | No | S5‑254798 | |
| S5‑254594 | Rel-17 CR TS28.554 Add missing formula for InterGNBHOMeanTime and MobilityRegUpdateSR | ZTE Corporation | CR | Agreement |
6.4OAM Rel-16
| Yes |
Yes
| revised | No | S5‑254799 | |
| S5‑254595 | Rel-18 CR TS28.554 Add missing formula for MobilityRegUpdateSR | ZTE Corporation | CR | Agreement |
6.4OAM Rel-16
| Yes |
Yes
| revised | No | S5‑254870 | |
| S5‑254596 | Rel-19 CR TS28.554 Add missing formula for MobilityRegUpdateSR | ZTE Corporation | CR | Agreement |
6.4OAM Rel-16
| Yes |
Yes
| revised | No | S5‑254871 | |
| S5‑254597 | Rel-20 pCR TR 28.881 Add description and requirements for intent guarantee UC#8 | Ericsson Korea Partners Co Ltd | pCR | Agreement |
6.20.1Study on intent driven management services for mobile network phase 4
| Yes |
YesNokia disagreed with requirements 2-5
| revised | No | S5‑254651 | |
| S5‑254598 | Rel-20 pCR TR 28.881 Add requirements and potential solution for intent handling capability UC#9 | Ericsson Korea Partners Co Ltd | pCR | Agreement |
6.20.1Study on intent driven management services for mobile network phase 4
| Yes |
Yesmerged into S5-254271
| merged | No | ||
| S5‑254599 | DP for Fixing corrupted TS 28.554 spec | ZTE Corporation | discussion | Endorsement |
6.20.125G performance measurements/KPIs and Trace/MDT/QoE
| Yes |
YesAP on MCC
| noted | No | ||
| S5‑254600 | New SID on Management aspects of Integrated Sensing and Communication | ZTE Corporation | SID new | Information |
6.2.1New OAM SIDs/WIDs proposals
| Yes |
Yes
| noted | No | ||
| S5‑254601 | Rel-19 CR 28.622 Fix inheritance diagram and definitions | Ericsson Canada Inc. | CR | Agreement |
6.19.135G Advanced NRM features phase 3
| Yes |
Yes
| agreed | No | ||
| S5‑254602 | R19 pCR TR 28.869 recommendation on observability requirements (Use case 7) | Orange, AT&T | pCR | Approval |
6.19.6Study on Cloud Aspects of Management and Orchestration
| Yes |
YesNokia: it's not clear how telemetric could be used
merged into S5-254367
| merged | No | ||
| S5‑254603 | Reply LS on OAM-centric solution for NW-side data collection | Nokia Japan | LS out | Approval |
6.1OAM Plenary
| Yes |
Yes
| noted | No | ||
| S5‑254604 | DP Multipoint-to-Multipoint Data Reporting in SBMA based on Message Bus | Rakuten Mobile, Inc | discussion | Endorsement |
6.20.4Study on Service Based Management Architecture enhancement phase 4
| Yes |
YesNokia expressed concerns. This exists already.
| noted | No | ||
| S5‑254605 | DP on NES use cases and policy | Rakuten Mobile, Inc | discussion | Endorsement |
6.20.5Study on energy efficiency and energy saving aspects of 5G Advanced
| Yes |
Yes
| noted | No | ||
| S5‑254606 | Rel-20 pCR on TR 28.885 Add New Use Case on Energy Rationing management | Samsung Electronics France SA | pCR | Approval |
6.20.5Study on energy efficiency and energy saving aspects of 5G Advanced
| Yes |
Yes
| withdrawn | Yes | ||
| S5‑254607 | Discussion on the need for prioritisation of work | NEC | discussion | Endorsement |
6.20.2Study on AI/ML management phase 3
| Yes |
Yesoffline discussion needed (NEC).
| revised | No | S5‑254878 | |
| S5‑254608 | Rel-20 pCR TR 28.891 Update of the Scope | Nokia | pCR | Approval |
7.5.1Charging Aspects of CAPIF Phase 3
| Yes |
Yes
| revised | No | S5‑254809 | |
| S5‑254609 | Rel-20 pCR TR 28.885 Add New Use Case on Energy Rationing management | Samsung Electronics France SA | pCR | Approval |
6.20.5Study on energy efficiency and energy saving aspects of 5G Advanced
| Yes |
Yesoffline comments
| revised | No | S5‑254700 | |
| S5‑254610 | DP for Enhancements to ProSe Path Selection | Nokia | discussion | Discussion |
7.2New/Revised Charging Study/Work Item proposals
| Yes |
Yes
| noted | No | ||
| S5‑254611 | pCR TR 28.891 Background | Nokia | pCR | Approval |
7.5.1Charging Aspects of CAPIF Phase 3
| Yes |
Yes
| revised | No | S5‑254810 | |
| S5‑254612 | Rel-20 pCR on TR 28.885 Add TR’s remaining structural clauses | Samsung Electronics France SA | pCR | Approval |
6.20.5Study on energy efficiency and energy saving aspects of 5G Advanced
| Yes |
Yesmerged into S5-254520
| merged | No | ||
| S5‑254613 | Rel-20 pCR on TR 28.882 Add New Use Case on Enhancement on LCM of Federated Learning | Samsung Electronics France SA | pCR | Approval |
6.20.2Study on AI/ML management phase 3
| Yes |
Yes
| revised | No | S5‑254743 | |
| S5‑254614 | Study on AI/ML management phase 3 | NEC | SID revised | Agreement |
6.2.2Revised OAM SIDs/WIDs proposals
| Yes |
Yes
| revised | No | S5‑254615 | |
| S5‑254615 | Revised Study on AI/ML management phase 3 | NEC | SID revised | Agreement |
6.2.2Revised OAM SIDs/WIDs proposals
| Yes |
YesE///: disagreed with the 1. change, there is no consensus in RAN1-2.
| revised | No | S5‑254663 | S5‑254614 |
| S5‑254616 | 25th Anniversary Celebration of SA5 Charging Subgroup 2000 - 2025 | MATRIXX Software | other | Presentation |
7.1Charging Plenary
| Yes |
Yes
| noted | No | ||
| S5‑254617 | Remove the Satellite Backhaul QoS change trigger | China Mobile Com. Corporation | CR | Agreement |
7.3Charging Maintenance and Rel-20 Charging small enhancements
| Yes |
Yes
| revised | No | S5‑254833 | |
| S5‑254618 | Remove the Satellite Backhaul QoS change trigger | China Mobile Com. Corporation | CR | Agreement |
7.3Charging Maintenance and Rel-20 Charging small enhancements
| Yes |
Yes
| revised | No | S5‑254834 | |
| S5‑254619 | Correction of SatelliteBackhaulCategory | China Mobile Com. Corporation | CR | Agreement |
7.3Charging Maintenance and Rel-20 Charging small enhancements
| Yes |
Yes
| revised | No | S5‑254835 | |
| S5‑254620 | Correction of SatelliteBackhaulCategory | China Mobile Com. Corporation | CR | Agreement |
7.3Charging Maintenance and Rel-20 Charging small enhancements
| Yes |
Yes
| revised | No | S5‑254836 | |
| S5‑254621 | Reply LS on OAM-centric solution for NW-side data collection | RAN2 | LS in | Information |
5.3Liaison statements at SA5 level
| No |
Yespostponed to next meeting
Rsubmit to next meeting!
| postponed | No | ||
| S5‑254622 | Agenda | WG Chair (Huawei) | agenda | Information |
2Approval of the agenda
| Yes |
YesEricsson: need code coordinator for YAML
| approved | No | S5‑254200 | |
| S5‑254623 | SA5 working methods | WG Chair (Huawei) | other | Information |
5.1Administrative issues at SA5 level
| Yes |
Yes
| noted | No | S5‑254205 | |
| S5‑254625 | LS on Invitation to update the information in the IMT-2020 and beyond roadmap | SA5 | LS out | Approval |
5.3Liaison statements at SA5 level
| No |
Yesneeded more time. Postponed to next meeting.
| withdrawn | Yes | ||
| S5‑254626 | LS on ""IETF Network Slice Application in 3GPP 5G End-to-End Network Slice"" | SA5 | LS out | Approval |
5.3Liaison statements at SA5 level
| No |
YesRakuten asked to be added. +Nokia
Postponed to next meeting. May send to SA for a coordianted 3GPP reply.
| postponed | No | ||
| S5‑254627 | Reply to LS on a new measurement related to the maintainability of a QoS flow | SA5 | LS out | Approval |
5.3Liaison statements at SA5 level
| Yes |
Yes
| approved | No | S5‑254232 | |
| S5‑254628 | Reply to LS on Study on Modernization of Specification Format and Procedures for 6G | SA5 | LS out | Information |
5.3Liaison statements at SA5 level
| Yes |
Yesmodified the title.
SA5 Chair: check the TR and provide feedback/join conf call if needed.
| noted | No | ||
| S5‑254629 | SA5 meeting calendar | WG Chair (Huawei) | other | Information |
5.4SA5 meeting calendar
| Yes |
Yes
| noted | No | S5‑254207 | |
| S5‑254630 | LS on need for modeling isInvariant and SystemCreated in YANG | SA5 | LS out | Approval |
5.3Liaison statements at SA5 level
| Yes |
Yesd2
SBMA_Ph2?
| approved | No | ||
| S5‑254631 | Rel-19 CR Update to management of IAB-node for NCI reconfiguration | Ericsson | CR | Agreement |
6.19.16Management of IAB nodes
| Yes |
Yes
| agreed | No | S5‑254550 | |
| S5‑254632 | Rel-20 CR Update to management of IAB-node for NCI reconfiguration | Ericsson | CR | Agreement |
6.19.16Management of IAB nodes
| Yes |
Yes
| agreed | No | S5‑254552 | |
| S5‑254633 | pCR TR 28.869 Recommendation for LCM of NF Deployment | Ericsson Limited, Nokia, AT&T, Rakuten Mobile, China Mobile | pCR | Approval |
6.19.6Study on Cloud Aspects of Management and Orchestration
| Yes |
Yesd5
-NTT DOCOMO
| approved | No | S5‑254547 | |
| S5‑254634 | pCR TR 28.869 NRM updates for NF Deployment LCM | Rakuten Mobile, Inc | pCR | Agreement |
6.19.6Study on Cloud Aspects of Management and Orchestration
| Yes |
Yesd4
| noted | No | S5‑254410 | |
| S5‑254635 | Rel-19 pCR TR 28.869 Add Evaluation to the use of VNF generic OAM functions | Nokia Mexico, China Mobile, Ericsson, Samsung | pCR | Approval |
6.19.6Study on Cloud Aspects of Management and Orchestration
| Yes |
Yesd7
Huawei objected to the editor's note.
Conclusion: will be removed.
-NTT DOCOMO
| approved | No | S5‑254571 | |
| S5‑254636 | Rel-19 pCR TR 28.869 Add conclusions and recommendations to the use of VNF generic OAM functions | Nokia Mexico, China Mobile, Ericsson, Samsung | pCR | Approval |
6.19.6Study on Cloud Aspects of Management and Orchestration
| Yes |
Yesd7
Huawei: remove last paragraph and Editor's note.
no d8
-NTT DOCOMO
| approved | No | S5‑254572 | |
| S5‑254637 | Pseudo-CR-TR 28.869 Add evaluation for solution of Observability | China Mobile | pCR | Approval |
6.19.6Study on Cloud Aspects of Management and Orchestration
| Yes |
Yes
| approved | No | S5‑254389 | |
| S5‑254638 | Study on 6G Management and Orchestration | China Unicom (Moderator) | SID new | Approval |
6.2.1New OAM SIDs/WIDs proposals
| Yes |
YesVodafone: option 4 is not an option. Compromise 5 doesn't solve, but gives a future option.
SA5 Chair: in Dec. we need to submit the SID.
Either take out 1.6., or reword.
China Unicom: agree with Vf, opt. 4 is a bad option.
E///: opt. 5 with the note from opt.1 would be the compromise. ->opt. 5a
Huawei: management data & framework is in our scope.
CMCC: need one more meeting to reach consensus.
VIVO: agree with CMCC.
SA5 Vice Chair E///: don't hear any technical argument for or against management data.
SA Chair: pls. progress the other objactives in the study. 1.6. can be brought in Nov.
Maybe also resolve then at plenary level.
Also see what comes out of the SA2 meeting.
| revised | No | S5‑254905 | S5‑254294 |
| S5‑254639 | Study on 6G Management and Orchestration Status Report | China Unicom (Moderator) | report | Presentation |
6.2.1New OAM SIDs/WIDs proposals
| Yes |
Yesfor information
| noted | No | S5‑254295 | |
| S5‑254640 | Proposals to guide the 6G OAM Study | China Mobile, Verizon, SK Telecom, CATT, ZTE, Rakuten Mobile, NEC, Orange | discussion | Endorsement |
6.2.1New OAM SIDs/WIDs proposals
| Yes |
Yesd1
Nokia: needed more time.
d2 added 1 supporting company.
Nokia objected.
| noted | No | S5‑254306 | |
| S5‑254641 | Intents, Goals and Autonomous Agents | Nokia | discussion | Endorsement |
6.20.1Study on intent driven management services for mobile network phase 4
| Yes |
Yes
| noted | No | S5‑254315 | |
| S5‑254642 | Rel-20 CR TS 28.622 Correct several issues for the IOCs related to MADCOL | Huawei | CR | Agreement |
6.20.0OAM Rel-20 small enhancements
| Yes |
Yes
| agreed | No | S5‑254281 | |
| S5‑254643 | Rel-20 CR TS 28.623 Correct several issues for the IOCs related to MADCOL | Huawei | CR | Agreement |
6.20.0OAM Rel-20 small enhancements
| Yes |
Yesfirst agreed, then reopened:
Nokia: misalignment with stage 3
| revised | No | S5‑254890 | S5‑254282 |
| S5‑254644 | Rel-20 CR TS28.541 Fix multiplicity and isOrdered property for hniList | ZTE Corporation | CR | Agreement |
6.20.0OAM Rel-20 small enhancements
| Yes |
Yesd1
no stage 3 needed.
| agreed | No | S5‑254589 | |
| S5‑254645 | pCR TR 28.881 Add solution for enhancement of radio network performance assurance scenarios | Huawei | pCR | Approval |
6.20.1Study on intent driven management services for mobile network phase 4
| Yes |
Yesd2
| approved | No | S5‑254270 | |
| S5‑254646 | pCR TR 28.881 Add solution for enhancement of radio service delivering and assurance scenarios | Huawei,China Mobile | pCR | Approval |
6.20.1Study on intent driven management services for mobile network phase 4
| Yes |
Yesd2
| approved | No | S5‑254268 | |
| S5‑254647 | pCR TR 28.881 Add new requirements and solution for enhancement radio service delivering and assurance scenarios | China Mobile, Huawei | pCR | Approval |
6.20.1Study on intent driven management services for mobile network phase 4
| Yes |
Yesd1
Nokia agreed.
| approved | No | S5‑254300 | |
| S5‑254648 | pCR TR 28.881 Add new use case for radio service assurance in transient overload scenarios | China Unicom | pCR | Approval |
6.20.1Study on intent driven management services for mobile network phase 4
| Yes |
Yesd1
Nokia needs to check.
| approved | No | S5‑254228 | |
| S5‑254649 | pCR on Rel-20 TR 28.881 Add use-case description, requirement and solution for enhancing feasibility check | NTT DOCOMO | pCR | Approval |
6.20.1Study on intent driven management services for mobile network phase 4
| Yes |
Yesd2
| approved | No | S5‑254415 | |
| S5‑254650 | Pseudo-CR on TR 28.881 Add Solution to Support to Express Guarantee Requirements in an Intent | ZTE Corporation | pCR | Approval |
6.20.1Study on intent driven management services for mobile network phase 4
| Yes |
Yesd1
Nokia didn't agree. Revise further.
0.0.0->0.1.0
| approved | No | S5‑254407 | |
| S5‑254651 | Rel-20 pCR TR 28.881 Add description and requirements for intent guarantee UC#8 | Ericsson Korea Partners Co Ltd | pCR | Agreement |
6.20.1Study on intent driven management services for mobile network phase 4
| Yes |
YesNokia needed to check.
Samsung comment was not addressed.
| revised | No | S5‑254884 | S5‑254597 |
| S5‑254652 | pCR TR 28.881 Add solution for Intent exploration enhancement | Huawei,China Mobile | pCR | Approval |
6.20.1Study on intent driven management services for mobile network phase 4
| Yes |
Yesd1
Nokia needs to check.
| approved | No | S5‑254269 | |
| S5‑254653 | pCR TR 28.881 Documentation for the overview of intent driven management functionalities | Huawei, ZTE | pCR | Approval |
6.20.1Study on intent driven management services for mobile network phase 4
| Yes |
Yesd2
ETSI MCC: formats & quoting other specs to be reviewed.
| approved | No | S5‑254272 | |
| S5‑254654 | pCR TR 28.881 Add use case for the investigation on the transition of intent Lifecycle management state | Huawei | pCR | Approval |
6.20.1Study on intent driven management services for mobile network phase 4
| Yes |
YesETSI MCC: pls. fix table format
| approved | No | S5‑254477 | |
| S5‑254655 | Rel-20 pCR TR 28.881 Add Use case on intent expectation satisfaction information | Huawei | pCR | Approval |
6.20.1Study on intent driven management services for mobile network phase 4
| Yes |
Yesd1
ETSI MCC: renumber clauses.
Nokia did not agree.
| approved | No | S5‑254289 | |
| S5‑254656 | pCR TR 28.881 Add solution for Intent handling capability configuration, registration and discovery | Huawei, Ericsson, ZTE | pCR | Approval |
6.20.1Study on intent driven management services for mobile network phase 4
| Yes |
Yes4406 4598 into here
| approved | No | S5‑254271 | |
| S5‑254657 | pCR on Rel-20 TR 28.881 Add use-case description, requirement and solution for relation and interaction with AIML | NTT DOCOMO | pCR | Approval |
6.20.1Study on intent driven management services for mobile network phase 4
| Yes |
Yesd1
| approved | No | S5‑254414 | |
| S5‑254658 | pCR TR 28.881 Add use case for the Investigation on the applicability and potential impacts to support natural language intents translation | Huawei | pCR | Approval |
6.20.1Study on intent driven management services for mobile network phase 4
| Yes |
Yes
| approved | No | S5‑254273 | |
| S5‑254659 | pCR on Rel-20 TR 28.881 Add solution for use case#3 | NTT DOCOMO | pCR | Approval |
6.20.1Study on intent driven management services for mobile network phase 4
| Yes |
Yesd1
ETSI MCC: pls. resolve [z]
| approved | No | S5‑254413 | |
| S5‑254660 | Pseudo-CR on TR 28.881 Add potential solution for UC#4 intent traceability | Ericsson Canada Inc.., Nokia, NTT DOCOMO | pCR | Agreement |
6.20.1Study on intent driven management services for mobile network phase 4
| Yes |
Yes
| approved | No | S5‑254553 | |
| S5‑254661 | Revised WID on 5G Advanced NRM features phase 4 | Huawei | WID revised | Approval |
6.2.2Revised OAM SIDs/WIDs proposals
| Yes |
YesSA5 Chair: Huawei should be primary rapporteur.
Nokia 2.?
| agreed | No | S5‑254258 | |
| S5‑254662 | Revised SID on Cloud Aspects of Management and Orchestration | China Mobile | SID revised | Approval |
6.2.2Revised OAM SIDs/WIDs proposals
| Yes |
Yesd2
Companies who wanted to close CMO discussion in this meeting: E///, Nokia, Samsung, Verizon, Rakuten, China Mobile, China Unicom.
In next meeting: DCM
| agreed | No | S5‑254391 | |
| S5‑254663 | Revised Study on AI/ML management phase 3 | NEC | SID revised | Agreement |
6.2.2Revised OAM SIDs/WIDs proposals
| Yes |
Yesd1 could not converge
E///: take out the RP reference
VIVO: RP LS requirements in Sept. are not captured.
Clarification is needed for WT-1-5 concerning the data collection for the one side/two side model.
NEC: the info is already covered by the existing relevant work task.
OPPO: share same view as ZTE.
| agreed | No | S5‑254615 | |
| S5‑254664 | pCR TR 28.882 initial ToC | NEC | pCR | Approval |
6.20.2Study on AI/ML management phase 3
| Yes |
Yesthis pCR contains the draft TR 28.882 v0.0.1
the TR will be submitted as a new doc
| approved | No | S5‑254584 | |
| S5‑254665 | Pseudo-CR on TR 28.882 add Management support use case and requirement to Two-Side model training | NEC, Huawei, Nokia, Samsung | pCR | Approval |
6.20.2Study on AI/ML management phase 3
| Yes |
Yesd2
VIVO objected. Need more discussion. Some technical issue is not clear.
| noted | No | ||
| S5‑254666 | Pseudo-CR on TR 28.882 add Management support to UE-Side model training use case | Huawei, Nokia, Samsung, NEC | pCR | Approval |
6.20.2Study on AI/ML management phase 3
| Yes |
Yesd4
wrong Tdoc#
| approved | No | S5‑254260 | |
| S5‑254667 | Pseudo-CR on TR 28.882 add Management support to NW-Side model training use case | Huawei, Nokia, NEC | pCR | Approval |
6.20.2Study on AI/ML management phase 3
| Yes |
Yes
| approved | No | S5‑254261 | |
| S5‑254668 | pCR TR 28.882 Add new use cases of ML workflow | China Mobile | pCR | Approval |
6.20.2Study on AI/ML management phase 3
| Yes |
Yesd1
E/// objected
| noted | No | S5‑254530 | |
| S5‑254669 | PCR TR 28.822 Rel-20 5GA Sustainability use case and requirements | Ericsson Telecom S.A. de C.V., Nokia, ZTE, NEC | pCR | Approval |
6.20.2Study on AI/ML management phase 3
| Yes |
Yesd2
ETSI MCC: pls. reorder the numbering
Samsung objected.
| noted | No | S5‑254536 | |
| S5‑254670 | Rel-20 pCR TR 28.883 Use case on NDT support intent pre-evaluation | Huawei | pCR | Approval |
6.20.3Study on management aspects of Network Digital Twins phase 2
| Yes |
Yesd2
| approved | No | S5‑254291 | |
| S5‑254671 | Rel-20 pCR TR 28.883 Improvement of data generation | Huawei | pCR | Approval |
6.20.3Study on management aspects of Network Digital Twins phase 2
| Yes |
Yesd1
Samsung: delete "quantity and real-to-synthetic data ratio"
| revised | No | S5‑254842 | S5‑254292 |
| S5‑254672 | pCR TR 28.883 Add a use case of NDT data generation | China Mobile | pCR | Approval |
6.20.3Study on management aspects of Network Digital Twins phase 2
| Yes |
Yesd3
| approved | No | S5‑254301 | |
| S5‑254673 | pCR TR 28.883 Add use case and requirements on enhancement for multiple NDT collaborations | China Mobile | pCR | Approval |
6.20.3Study on management aspects of Network Digital Twins phase 2
| Yes |
Yes
| revised | No | S5‑254843 | S5‑254302 |
| S5‑254674 | Pseudo-CR on TR 28.883 Add New Use Case on Capability Discovery of NDT in NDT Collaboration | ZTE Corporation | pCR | Agreement |
6.20.3Study on management aspects of Network Digital Twins phase 2
| Yes |
Yesd3
| approved | No | S5‑254515 | |
| S5‑254675 | pCR TR 28.883 Add use case and requirements on enhancement for NDT management and orchestration | China Mobile | pCR | Approval |
6.20.3Study on management aspects of Network Digital Twins phase 2
| Yes |
Yesd2
Nokia objected.
| noted | No | S5‑254303 | |
| S5‑254676 | pCR TR 28.884 Add introduction for SBMA study report | Huawei | pCR | Approval |
6.20.4Study on Service Based Management Architecture enhancement phase 4
| Yes |
Yes
| approved | No | S5‑254452 | |
| S5‑254677 | pCR TR 28.884 Add scope for SBMA study report | Huawei | pCR | Approval |
6.20.4Study on Service Based Management Architecture enhancement phase 4
| Yes |
Yes
| approved | No | S5‑254453 | |
| S5‑254678 | pCR TR 28.884 Add concepts and background | Huawei | pCR | Approval |
6.20.4Study on Service Based Management Architecture enhancement phase 4
| Yes |
Yes
| approved | No | S5‑254455 | |
| S5‑254679 | pCR TR 28.884 Use case on software management | Huawei | pCR | Approval |
6.20.4Study on Service Based Management Architecture enhancement phase 4
| Yes |
YesNokia: remove req. 1-3
ETSI MCC: renumber clauses
| revised | No | S5‑254844 | S5‑254456 |
| S5‑254680 | pCR TR 28.884 Use case on inventory management | Huawei | pCR | Approval |
6.20.4Study on Service Based Management Architecture enhancement phase 4
| Yes |
Yesremove req. 2
| revised | No | S5‑254845 | S5‑254457 |
| S5‑254681 | pCR TR 28.884 Use case on integration of SBMA with 5GC and 5G Access Network architecture | Huawei, NEC | pCR | Approval |
6.20.4Study on Service Based Management Architecture enhancement phase 4
| Yes |
Yes
| approved | No | S5‑254458 | |
| S5‑254682 | pCR TR 28.884 Management data streaming based on message bus | Huawei | pCR | Approval |
6.20.4Study on Service Based Management Architecture enhancement phase 4
| Yes |
Yes
| approved | No | S5‑254459 | |
| S5‑254683 | pCR on Rel-20 TR 28.885 Add TR structure | Nokia | pCR | Approval |
6.20.5Study on energy efficiency and energy saving aspects of 5G Advanced
| Yes |
Yesd1
| agreed | No | S5‑254520 | |
| S5‑254684 | Pseudo-CR on TR 28.886 Add new use case on domain information for MDAFunction | Huawei, China Mobile | pCR | Approval |
6.20.7Study on Management Data Analytics (MDA) phase 4
| Yes |
Yes
| approved | No | S5‑254372 | |
| S5‑254685 | Rel-20 pCR TR 28.886 Add new use case on radio resource optimization based on per SSB usage | China Unicom | pCR | Approval |
6.20.7Study on Management Data Analytics (MDA) phase 4
| Yes |
Yesd1
ETSI MCC: 3GPP styles
| approved | No | S5‑254375 | |
| S5‑254686 | Rel-20 pCR 28.886 RET Analytics | Samsung R&D Institute India | pCR | Approval |
6.20.7Study on Management Data Analytics (MDA) phase 4
| Yes |
Yes
| approved | No | S5‑254446 | |
| S5‑254687 | Pseudo-CR on TR 28.886 Add solution for enhance the mobility performance analysis use case | Huawei | pCR | Approval |
6.20.7Study on Management Data Analytics (MDA) phase 4
| Yes |
Yesd1
| approved | No | S5‑254267 | |
| S5‑254688 | Pseudo-CR on TR 28.886 Add requirements and solution for failure resolution | Huawei, China Mobile, Verizon | pCR | Approval |
6.20.7Study on Management Data Analytics (MDA) phase 4
| Yes |
Yes
| approved | No | S5‑254471 | |
| S5‑254689 | Pseudo-CR on Time Issue of External Management Data | Nokia | pCR | Approval |
6.20.8Study for Data management phase 3
| Yes |
Yes
| approved | No | S5‑254425 | |
| S5‑254690 | Pseudo-CR on Clarification of Mechanisms to Discover Management Data | Nokia | pCR | Approval |
6.20.8Study for Data management phase 3
| Yes |
YesE/// objected
| noted | No | S5‑254426 | |
| S5‑254691 | Pseudo-CR on Clarification of Mechanisms to Request and Retrieve Management Data | Nokia | pCR | Approval |
6.20.8Study for Data management phase 3
| Yes |
YesE/// objected
| noted | No | S5‑254427 | |
| S5‑254692 | Pseudo-CR on Introduction for data management phase-3 | Ericsson Telecomunicazioni SpA | pCR | Approval |
6.20.8Study for Data management phase 3
| Yes |
Yesd2
| revised | No | S5‑254894 | S5‑254513 |
| S5‑254693 | Pseudo-CR on Scope for data management phase-3 | Ericsson Telecomunicazioni SpA | pCR | Approval |
6.20.8Study for Data management phase 3
| Yes |
Yesd2
| revised | No | S5‑254895 | S5‑254529 |
| S5‑254694 | pCR TR 28.888 Add concepts and background | Huawei | pCR | Approval |
6.20.9Study on Enhanced exposure of management services
| Yes |
Yes
| approved | No | S5‑254450 | |
| S5‑254695 | Rel-20 pCR TR 28.888 Concepts and background on data sharing permissions | Nokia Mexico | pCR | Approval |
6.20.9Study on Enhanced exposure of management services
| Yes |
YesVodafone & E/// objected
| noted | No | S5‑254567 | |
| S5‑254696 | pCR TR 28.888 Add use case on transformation of MnS information for external MnS consumers | Huawei | pCR | Approval |
6.20.9Study on Enhanced exposure of management services
| Yes |
YesE/// objected
| noted | No | S5‑254451 | |
| S5‑254697 | DP on comparison between management services exposure and O-RAN defined SME and DME | Nokia Mexico | discussion | Endorsement |
6.20.9Study on Enhanced exposure of management services
| Yes |
Yesd3
Rakuten asked for more time. Share AT&T's opinion seeing the value of the comparison.
Huawei: need more investigation. Postpone to next meeting.
Vodafone agreed with Rakuten.
| noted | No | S5‑254568 | |
| S5‑254698 | pCR on Rel-20 TR 28.885 Add new use case support of energy-related characteristics | Nokia | pCR | Approval |
6.20.5Study on energy efficiency and energy saving aspects of 5G Advanced
| Yes |
Yes
| approved | No | S5‑254521 | |
| S5‑254699 | pCR on Rel-20 TR 28.885 Add new use case related to service adjustments to adapt to energy-related characteristics | Nokia | pCR | Approval |
6.20.5Study on energy efficiency and energy saving aspects of 5G Advanced
| Yes |
Yes4609
| approved | No | S5‑254522 | |
| S5‑254700 | Rel-20 pCR TR 28.885 Add New Use Case on Energy Rationing management | Samsung Electronics France SA, Nokia | pCR | Approval |
6.20.5Study on energy efficiency and energy saving aspects of 5G Advanced
| Yes |
Yes+Nokia
| approved | No | S5‑254609 | |
| S5‑254701 | pCR on Rel-20 TR 28.885 Add new use case to support network energy saving optimizations across operators | Nokia | pCR | Approval |
6.20.5Study on energy efficiency and energy saving aspects of 5G Advanced
| Yes |
YesSamsung objected
| noted | No | S5‑254524 | |
| S5‑254702 | pCR on Rel-20 TR 28.889 Add use case description and requirement for Network Maintenance CCL | NTT DOCOMO | pCR | Approval |
6.20.10Study on Closed Control Loop Management phase 2
| Yes |
Yesd1
wrong ver
| approved | No | S5‑254416 | |
| S5‑254703 | Rel-20 pCR 28.889 CCL for LCM | Samsung R&D Institute India | pCR | Agreement |
6.20.10Study on Closed Control Loop Management phase 2
| Yes |
Yesd2
Author missing, wrong ver
| revised | No | S5‑254885 | S5‑254447 |
| S5‑254704 | Pseudo-CR on TR 28.889 Add status monitoring use case | Huawei Tech. Japan, K.K. | pCR | Approval |
6.20.10Study on Closed Control Loop Management phase 2
| Yes |
Yes
| approved | No | S5‑254473 | |
| S5‑254705 | Rel-20 CR TS 28.541 Configuration Enhancement on MWAB-gNB to Support QoS Related Information for the BH PDU Sessions | ZTE Corporation | CR | Agreement |
6.20.115G Advanced NRM features phase 4
| Yes |
Yesd3
E/// objected
| not pursued | No | S5‑254405 | |
| S5‑254706 | Rel-20 CR 28.541 NRM extensions for MWAB Ph2 Stage 2 and Stage 3 | Samsung R&D Institute India | CR | Agreement |
6.20.115G Advanced NRM features phase 4
| Yes |
YesE/// objected. Can bring a joint contribution at the next meeting.
| not pursued | No | S5‑254448 | |
| S5‑254707 | Rel-20 CR TS 28.540 Add requirements for WAB-gNB management | Ericsson | CR | Agreement |
6.20.115G Advanced NRM features phase 4
| Yes |
Yesd1
Samsung: retain the address
| agreed | No | S5‑254557 | |
| S5‑254708 | Rel-20 CR TS 28.541 add LTM control attribute to support conditional LTM | Huawei | CR | Agreement |
6.20.115G Advanced NRM features phase 4
| Yes |
Yesd1
| agreed | No | S5‑254263 | |
| S5‑254710 | Rel-20 CR TS 28.541 add 5G femto NRM usage introduction in the annex | Huawei, CMCC, ZTE, Rakuten | CR | Agreement |
6.20.115G Advanced NRM features phase 4
| Yes |
Yesd1
AP on Huawei, E///, Nokia, Samsung to propose a better representation of Rel-19 management support.
| not pursued | No | S5‑254266 | |
| S5‑254711 | Rel-20 CR TS 28.541 Update NTNEntityConf dataType definition | Huawei | CR | Agreement |
6.20.115G Advanced NRM features phase 4
| Yes |
Yes
| agreed | No | S5‑254283 | |
| S5‑254712 | Correction of PcscfInfo data type | AsiaInfo | CR | Agreement |
6.20.115G Advanced NRM features phase 4
| Yes |
Yesd2
rev: 1!
E///: fix also in other places.
SA5 Chair: at the next meeting.
| agreed | No | S5‑254284 | |
| S5‑254713 | Enhancement of PcscfInfo | AsiaInfo | CR | Agreement |
6.20.115G Advanced NRM features phase 4
| Yes |
Yesd1
| agreed | No | S5‑254285 | |
| S5‑254714 | Enhancement of PcfInfo | AsiaInfo | CR | Agreement |
6.20.115G Advanced NRM features phase 4
| Yes |
Yesd1
| agreed | No | S5‑254286 | |
| S5‑254715 | Rel-20 CR TS 28.541 Enhance the NRM fragment for RedCap Access | Huawei | CR | Agreement |
6.20.115G Advanced NRM features phase 4
| Yes |
Yesd1
| agreed | No | S5‑254439 | |
| S5‑254716 | Rel-20 CR TS 28.552 Add UE Address Information Retrieval for UPF event exposure measurement | China Telecom | CR | Agreement |
6.20.125G performance measurements/KPIs and Trace/MDT/QoE
| Yes |
Yesd1
| agreed | No | S5‑254222 | |
| S5‑254717 | Rel-20 CR TS 28.552 Add UPF event exposure related measurements | China Telecom Corporation Ltd. | CR | Agreement |
6.20.125G performance measurements/KPIs and Trace/MDT/QoE
| Yes |
Yesd1
| agreed | No | S5‑254223 | |
| S5‑254720 | Rel-20 CR TS 28.552 Add DL data transmission time per SSB | China Unicom | CR | Agreement |
6.20.125G performance measurements/KPIs and Trace/MDT/QoE
| Yes |
Yesd2
cl. aff.
| agreed | No | S5‑254373 | |
| S5‑254721 | Rel-20 CR TS 28.552 Add Timing Advance distribution for NR Cell per SSB | China Unicom | CR | Agreement |
6.20.125G performance measurements/KPIs and Trace/MDT/QoE
| Yes |
Yesd1
| agreed | No | S5‑254374 | |
| S5‑254722 | Rel-20 CR 28.552 Add a new measurement related to the number of requests of ADRF storage services | China Telecom | CR | Agreement |
6.20.13Management Aspects related to NWDAF phase 3
| Yes |
Yesd2
ETSI MCC: changes over changes.
| revised | No | S5‑254393 | |
| S5‑254724 | Rel-20 CR 28.541 Add VFL interoperability and client aggregation capability information for NWDAF | China Telecom | CR | Agreement |
6.20.13Management Aspects related to NWDAF phase 3
| Yes |
Yes
| agreed | No | S5‑254397 | |
| S5‑254730 | pCR on TR 28.892 - Scope | Vodafone | pCR | Approval |
6.20.15Unified Management interface for Multi-RAT support
| Yes |
Yes
| approved | No | S5‑254378 | |
| S5‑254731 | pCR on TR 28.892 - References | Vodafone | pCR | Approval |
6.20.15Unified Management interface for Multi-RAT support
| Yes |
YesTdoc#
| noted | No | S5‑254379 | |
| S5‑254732 | New KI on Historical alarms | Nokia | pCR | Approval |
6.20.4Study on Service Based Management Architecture enhancement phase 4
| Yes |
Yesd2
Samsung: remove AI/ML training.
| approved | No | S5‑254398 | |
| S5‑254733 | Rel-20 pCR TR 28.883 Defining the Lifecycle and Runtime Behaviour of NDT Jobs | L.M. Ericsson Limited | pCR | Agreement |
6.20.3Study on management aspects of Network Digital Twins phase 2
| Yes |
Yesd3
Huawei: may->should
Nokia & Samsung do not support this version.
| approved | No | S5‑254573 | |
| S5‑254734 | Pseudo-CR TR28.869 Config management updates | DOCOMO Beijing Labs | pCR | Approval |
6.19.6Study on Cloud Aspects of Management and Orchestration
| Yes |
Yesd1
| approved | No | S5‑254420 | |
| S5‑254735 | Pseudo-CR-TR 28.869 Add Rapporteur clean-up and solve some editor's notes | China Mobile | pCR | Approval |
6.19.6Study on Cloud Aspects of Management and Orchestration
| Yes |
Yesd2
| approved | No | S5‑254394 | |
| S5‑254736 | pCR TR 28.885 Add use case and requirements for renewable energy consumption | China Mobile | pCR | Approval |
6.20.5Study on energy efficiency and energy saving aspects of 5G Advanced
| Yes |
Yes
| approved | No | S5‑254304 | |
| S5‑254737 | pCR TR 28.885 Add solution for renewable energy consumption | China Mobile | pCR | Approval |
6.20.5Study on energy efficiency and energy saving aspects of 5G Advanced
| Yes |
YesNokia objected
| noted | No | S5‑254305 | |
| S5‑254738 | pCR on Rel-20 TR 28.885 Add new use case for enhancements to reporting EC and EE at per network slice granularity | Nokia | pCR | Approval |
6.20.5Study on energy efficiency and energy saving aspects of 5G Advanced
| Yes |
Yes
| approved | No | S5‑254525 | |
| S5‑254739 | pCR on Rel-20 TR 28.885 Add new use case to study Enhancements to NF Profile to support energy saving and energy efficiency | Nokia | pCR | Approval |
6.20.5Study on energy efficiency and energy saving aspects of 5G Advanced
| Yes |
Yes
| approved | No | S5‑254526 | |
| S5‑254740 | pCR on Rel-20 TR 28.885 Add new use case to study measuring of EC of NE at per Energy Supply granularity | Nokia | pCR | Approval |
6.20.5Study on energy efficiency and energy saving aspects of 5G Advanced
| Yes |
Yes
| approved | No | S5‑254527 | |
| S5‑254741 | pCR on Rel-20 TR 28.885 Add new use case to study EC and EE per PLMNID in Network sharing scenario | Nokia | pCR | Approval |
6.20.5Study on energy efficiency and energy saving aspects of 5G Advanced
| Yes |
Yes
| approved | No | S5‑254528 | |
| S5‑254743 | Rel-20 pCR on TR 28.882 Add New Use Case on Enhancement on LCM of Federated Learning | Samsung Electronics France SA | pCR | Approval |
6.20.2Study on AI/ML management phase 3
| Yes |
YesE/// objected
| noted | No | S5‑254613 | |
| S5‑254744 | Pseudo-CR on TR 28.882 Add New Use Case on Management of Vertical Federated Learning | ZTE Corporation | pCR | Approval |
6.20.2Study on AI/ML management phase 3
| Yes |
Yes
| approved | No | S5‑254408 | |
| S5‑254745 | pCR TR 28.882 Add new use cases Management of AIML monitoring | China Mobile | pCR | Approval |
6.20.2Study on AI/ML management phase 3
| Yes |
YesE/// objected
| noted | No | S5‑254531 | |
| S5‑254746 | pCR TR 28.882 Add new use case for ML model deployment phase | China Mobile | pCR | Approval |
6.20.2Study on AI/ML management phase 3
| Yes |
YesE/// objected
| noted | No | S5‑254533 | |
| S5‑254747 | Rel-20 pCR TR 28.882 Add new use case and requirements on AI/ML Model Inference Complexity | Nokia Canada | pCR | Approval |
6.20.2Study on AI/ML management phase 3
| Yes |
YesE/// objected.
| noted | No | S5‑254514 | |
| S5‑254748 | Rel-20 pCR TR 28.882 Add new use case and requirements on Minimum acceptable performance for AI/ML Model Training | Nokia Canada | pCR | Approval |
6.20.2Study on AI/ML management phase 3
| Yes |
YesE/// objected.
| noted | No | S5‑254516 | |
| S5‑254749 | Pseudo-CR on TR 28.882 add model registration management use case | Huawei | pCR | Approval |
6.20.2Study on AI/ML management phase 3
| Yes |
YesNokia objected
| noted | No | S5‑254262 | |
| S5‑254750 | Rel-19 CR TS 28.105 Correction on Properties of Attributes | ZTE Corporation | CR | Agreement |
6.19.1AI/ML management phase 2
| Yes |
Yes
| agreed | No | S5‑254402 | |
| S5‑254751 | Rel-19 CR TS 28.105 Correct Inconsistency between Stage 2 and Stage 3 | ZTE Corporation | CR | Agreement |
6.19.1AI/ML management phase 2
| Yes |
Yes
| agreed | No | S5‑254409 | |
| S5‑254752 | Rel-19 TS 28.105 corrections related to CR implementation in v19.3.0 | NEC | CR | Agreement |
6.19.1AI/ML management phase 2
| Yes |
Yes
| agreed | No | S5‑254479 | |
| S5‑254753 | Rel-19 TS 28.105 clarifications on MLModel and MLTrainingRequest attributes | NEC | CR | Agreement |
6.19.1AI/ML management phase 2
| Yes |
Yes
| agreed | No | S5‑254539 | |
| S5‑254754 | Rel-19 TS 28.105 clarifications on the use of mLTrainingType attributes | NEC | CR | Agreement |
6.19.1AI/ML management phase 2
| Yes |
YesE/// objects
| not pursued | No | S5‑254545 | |
| S5‑254755 | Rel-19 CR TS 28.105 Initial training | Ericsson | CR | Agreement |
6.19.1AI/ML management phase 2
| Yes |
Yes
| agreed | No | S5‑254559 | |
| S5‑254756 | Rel-19 CR TS 28.105 Training types in Training NRM fragment | Ericsson | CR | Agreement |
6.19.1AI/ML management phase 2
| Yes |
Yes
| agreed | No | S5‑254561 | |
| S5‑254757 | Rel-19 CR TS 28.105 Correct associations on Training NRM fragment | Ericsson | CR | Agreement |
6.19.1AI/ML management phase 2
| Yes |
YesNEC objected
| not pursued | No | S5‑254564 | |
| S5‑254758 | Rel-19 CR TS 28.105 Correct inference related attributes in MLModel | Ericsson | CR | Agreement |
6.19.1AI/ML management phase 2
| Yes |
YesCMCC objected.
| not pursued | No | S5‑254565 | |
| S5‑254759 | Rel-19 CR TS28.567 Clarify CCL-related MnS | Nokia | CR | Agreement |
6.19.4Closed Control Loop Management
| Yes |
YesHuawei objects, unless the example is removed.
| revised | No | S5‑254908 | S5‑254411 |
| S5‑254760 | Rel-19 CR TS28.567 Small corrections | Nokia | CR | Agreement |
6.19.4Closed Control Loop Management
| Yes |
Yes
| agreed | No | S5‑254412 | |
| S5‑254761 | Rel-19 CR TS 28.567 Correction on CCL Purpose | NTT DOCOMO | CR | Agreement |
6.19.4Closed Control Loop Management
| Yes |
Yes
| agreed | No | S5‑254440 | |
| S5‑254762 | Rel-19 CR TS 28.561 Correct Inconsistency between Stage 2 and Stage 3 | ZTE Corporation | CR | Agreement |
6.19.5Management aspects of Network Digital Twins
| Yes |
Yes
| agreed | No | S5‑254403 | |
| S5‑254763 | Rel-19 CR TS 28.561 Correction on NDT Attributes | ZTE Corporation | CR | Agreement |
6.19.5Management aspects of Network Digital Twins
| Yes |
Yes
| agreed | No | S5‑254404 | |
| S5‑254764 | Rel-19 CR TS 28.561 editorial corrections and clarifications | DOCOMO Beijing Labs | CR | Agreement |
6.19.5Management aspects of Network Digital Twins
| Yes |
Yes
| agreed | No | S5‑254428 | |
| S5‑254765 | Rel-19 CR TS 28.561 Make NDTDataValue and NDTScalingFactor as conditional mandatory attributes | L.M. Ericsson Limited | CR | Agreement |
6.19.5Management aspects of Network Digital Twins
| Yes |
YesTdoc#
| revised | No | S5‑254907 | S5‑254581 |
| S5‑254766 | Rel-19 CR 28.572 Plan management stage3 updates | Ericsson Hungary Ltd, Nokia | CR | Agreement |
6.19.9Management of planned configurations
| Yes |
Yes
| agreed | No | S5‑254384 | |
| S5‑254767 | Rel-19 CR TS 28.537 Add missing functionality and solution description for managing external management data | Huawei | CR | Agreement |
6.19.10Data management phase 2
| Yes |
Yes
| agreed | No | S5‑254280 | |
| S5‑254768 | Rel-19 CR TS 28.537 Correction for Deployment Scenario Description | Nokia | CR | Agreement |
6.19.10Data management phase 2
| Yes |
YesE/// objected
| not pursued | No | S5‑254576 | |
| S5‑254769 | Rel-19 CR TS 28.622 Corrections for Condition Monitor | Nokia | CR | Agreement |
6.19.10Data management phase 2
| Yes |
Yes
| agreed | No | S5‑254577 | |
| S5‑254770 | Rel-20 CR TS 28.622 Corrections for Condition Monitor | Nokia | CR | Agreement |
6.19.10Data management phase 2
| Yes |
Yes
| agreed | No | S5‑254578 | |
| S5‑254771 | Rel-19 CR TS 28.623 Corrections for Condition Monitor | Nokia | CR | Agreement |
6.19.10Data management phase 2
| Yes |
Yes
| agreed | No | S5‑254579 | |
| S5‑254772 | Rel-19 CR TS 32.422 Corrections on Trace Failure Notification | Nokia | CR | Agreement |
6.19.11Data management regarding subscriptions and reporting
| Yes |
Yes
| agreed | No | S5‑254511 | |
| S5‑254773 | Rel-19 CR 28.552 Correct clause title | Ericsson | CR | Agreement |
6.19.125G performance measurements and KPIs phase 4
| Yes |
Yes
| agreed | No | S5‑254537 | |
| S5‑254774 | Rel-20 CR 28.552 Correct clause title | Ericsson | CR | Agreement |
6.19.125G performance measurements and KPIs phase 4
| Yes |
Yes
| agreed | No | S5‑254538 | |
| S5‑254775 | Rel-19 CR TS 28.541 Correct the issues for MWAB NRM fragment | China Mobile, Huawei | CR | Agreement |
6.19.135G Advanced NRM features phase 3
| Yes |
Yes
| agreed | No | S5‑254433 | |
| S5‑254776 | Rel-20 CR TS 28.541 Correct the issues for MWAB NRM fragment | China Mobile, Huawei | CR | Agreement |
6.19.135G Advanced NRM features phase 3
| Yes |
Yes
| agreed | No | S5‑254435 | |
| S5‑254777 | Rel-19 CR TS 28.541 Additional AIoT NRM Configurations | Samsung Electronics France SA, Ericsson | CR | Agreement |
6.19.135G Advanced NRM features phase 3
| Yes |
Yes
| agreed | No | S5‑254551 | |
| S5‑254778 | Rel-20 CR TS 28.541 Additional AIoT NRM Configurations | Samsung Electronics France SA, Ericsson | CR | Agreement |
6.19.135G Advanced NRM features phase 3
| Yes |
Yes
| agreed | No | ||
| S5‑254779 | Rel-19 CR TS 28.541 correct the NRM definition for RedCap | Huawei | CR | Agreement |
6.19.17Management Aspects of RedCap features
| Yes |
Yes
| agreed | No | S5‑254274 | |
| S5‑254780 | Rel-20 CR TS 28.541 correct the NRM definition for RedCap | Huawei | CR | Agreement |
6.19.17Management Aspects of RedCap features
| Yes |
Yes
| agreed | No | S5‑254275 | |
| S5‑254781 | draft TR 28.885 v0.0.0 | Samsung | draft TR | Approval |
6.20.5Study on energy efficiency and energy saving aspects of 5G Advanced
| Yes |
Yes
| approved | No | ||
| S5‑254782 | Pseudo-CR on TR 28.886 Add solution for MDA scope | Huawei Tech. Japan, K.K., Ericsson | pCR | Approval |
6.20.7Study on Management Data Analytics (MDA) phase 4
| Yes |
Yes
| approved | No | S5‑254472 | |
| S5‑254783 | Rel-18 TS 28.105 correction to MLTrainingProcess attributes | NEC | CR | Agreement |
6.6.3AI/ML management
| Yes |
YesE/// objected.
| not pursued | No | S5‑254430 | |
| S5‑254784 | Rel-19 TS 28.105 correction to MLTrainingProcess attributes | NEC | CR | Agreement |
6.19.1AI/ML management phase 2
| Yes |
YesE/// objects
| not pursued | No | S5‑254429 | |
| S5‑254785 | Rel-19 CR TS 32.422 Enhancement on the geographical area scope for NTN MDT | CATT, Ericsson | CR | Agreement |
6.19.23Rel-19 CAT B/C alignment CR(s) due to the work led by other 3GPP Working Groups
| Yes |
Yes
| agreed | No | S5‑254349 | |
| S5‑254786 | Rel-20 CR TS 32.422 Enhancement on the geographical area scope for NTN MDT | CATT, Ericsson | CR | Agreement |
6.19.23Rel-19 CAT B/C alignment CR(s) due to the work led by other 3GPP Working Groups
| Yes |
Yes
| agreed | No | S5‑254350 | |
| S5‑254787 | Rel-19 CR TS 28.622 Add Geo area scope for NTN MDT (stage 2) | CATT, Ericsson | CR | Agreement |
6.19.23Rel-19 CAT B/C alignment CR(s) due to the work led by other 3GPP Working Groups
| Yes |
Yes
| agreed | No | S5‑254351 | |
| S5‑254788 | Rel-19 CR TS 28.623 Add Geo area scope for NTN MDT (stage 3 Yaml) | CATT | CR | Agreement |
6.19.23Rel-19 CAT B/C alignment CR(s) due to the work led by other 3GPP Working Groups
| Yes |
Yes
| agreed | No | S5‑254352 | |
| S5‑254789 | Rel-20 CR TS 28.622 Add Geo area scope for NTN MDT (stage 2) | CATT, Ericsson | CR | Agreement |
6.19.23Rel-19 CAT B/C alignment CR(s) due to the work led by other 3GPP Working Groups
| Yes |
Yes
| agreed | No | S5‑254353 | |
| S5‑254790 | Reply LS on geographical area scope MDT | CATT, Ericsson | LS out | Approval |
6.1OAM Plenary
| Yes |
Yes
| approved | No | S5‑254348 | |
| S5‑254791 | Reply LS on specification of dataset and model parameters exchange | SA5 | LS out | Approval |
5.3Liaison statements at SA5 level
| Yes |
YesNEC: remove 'already'
| revised | No | S5‑254846 | S5‑254231 |
| S5‑254793 | Rel-19 CR TS 28.310 Update UC and requirements of Energy Efficiency as a Service Criteria | Ericsson | CR | Agreement |
6.19.20Energy efficiency and energy saving aspects of 5G networks and services
| Yes |
Yes
| agreed | No | S5‑254293 | |
| S5‑254794 | Rel-19 CR TS 28.541 Clarify usage of CESManagementFunction | Nokia | CR | Agreement |
6.19.20Energy efficiency and energy saving aspects of 5G networks and services
| Yes |
Yes
| agreed | No | S5‑254518 | |
| S5‑254795 | Rel-20 CR TS 28.541 Clarify usage of CESManagementFunction | Nokia | CR | Agreement |
6.19.20Energy efficiency and energy saving aspects of 5G networks and services
| Yes |
Yes
| agreed | No | S5‑254519 | |
| S5‑254796 | Rel-19 CR TS 28.622 Add Enum values for missing R19 management capabilities | Huawei | CR | Agreement |
6.19.24Rel-19 CAT B/C SA5 internal alignment and other CAT F CR(s)
| Yes |
Yes
| agreed | No | S5‑254277 | |
| S5‑254797 | Rel-20 CR TS 28.622 Add Enum values for missing R19 management capabilities | Huawei | CR | Agreement |
6.19.24Rel-19 CAT B/C SA5 internal alignment and other CAT F CR(s)
| Yes |
Yes
| agreed | No | S5‑254278 | |
| S5‑254798 | Rel-16 CR TS28.554 Add missing formula for InterGNBHOMeanTime and MobilityRegUpdateSR | ZTE Corporation | CR | Agreement |
6.4OAM Rel-16
| Yes |
Yes
| agreed | No | S5‑254593 | |
| S5‑254799 | Rel-17 CR TS28.554 Add missing formula for InterGNBHOMeanTime and MobilityRegUpdateSR | ZTE Corporation | CR | Agreement |
6.4OAM Rel-16
| Yes |
Yes
| agreed | No | S5‑254594 | |
| S5‑254800 | agenda_with_Tdocs_sequence_CH | SWG CH Chair (MATRIXX Software) | report | Information |
7.1Charging Plenary
| Yes |
Yes
| noted | No | S5‑254215 | |
| S5‑254801 | Mapping with SA1 Charging Requirement | Huawei | discussion | Discussion |
7.1Charging Plenary
| Yes |
Yes
| noted | No | S5‑254496 | |
| S5‑254802 | New SID on Charging Aspects of satellite access phase 4 | CATT | SID new | Approval |
7.2.1New CH SIDs/WIDs proposals
| Yes |
Yes
| postponed | No | S5‑254288 | |
| S5‑254803 | New WID on Charging aspects of next generation real time communication services phase 3 | China Mobile | WID new | Approval |
7.2.1New CH SIDs/WIDs proposals
| Yes |
Yesupdate title?
| revised | No | S5‑254847 | S5‑254376 |
| S5‑254804 | New SID on 5GA Charging aspects of ISAC | China Unicom | SID new | Approval |
7.2.1New CH SIDs/WIDs proposals
| Yes |
YesSA5 Charging Convener: SA2 has no info.
Is endorsed
| endorsed | No | S5‑254532 | |
| S5‑254805 | Add informatin elements to support charging aspects of multi-modality service | China Telecom | CR | Agreement |
7.4.1Charging aspects for XRM
| Yes |
Yes
| agreed | No | S5‑254297 | |
| S5‑254806 | Rel-20 pCR 28.891 Document Structure Update | Nokia | pCR | Approval |
7.5.1Charging Aspects of CAPIF Phase 3
| Yes |
Yes
| approved | No | S5‑254385 | |
| S5‑254807 | Rel-20 pCR 28.891 Update of the Scope | Nokia | pCR | Approval |
7.5.1Charging Aspects of CAPIF Phase 3
| Yes |
Yes
| approved | No | S5‑254386 | |
| S5‑254808 | Rel-20 pCR 28.891 Key issue regarding reference points and chargeable events | Ericsson | pCR | Approval |
7.5.1Charging Aspects of CAPIF Phase 3
| Yes |
Yes
| approved | No | S5‑254462 | |
| S5‑254809 | Rel-20 pCR TR 28.891 Update of the Scope | Nokia | pCR | Approval |
7.5.1Charging Aspects of CAPIF Phase 3
| Yes |
Yes
| approved | No | S5‑254608 | |
| S5‑254810 | pCR TR 28.891 Background | Nokia | pCR | Approval |
7.5.1Charging Aspects of CAPIF Phase 3
| Yes |
Yes
| approved | No | S5‑254611 | |
| S5‑254811 | TR 32.872 v0.0.0 Initial skeleton | Huawei | other | Approval |
7.5.25GA Roaming Charging Reliability Enhancement
| Yes |
Yes
| approved | No | S5‑254380 | |
| S5‑254812 | Rel-20 pCR 32.872 Introduce the usecase1 on Local Breakout Inter CHFs | Huawei | pCR | Approval |
7.5.25GA Roaming Charging Reliability Enhancement
| Yes |
Yes
| approved | No | S5‑254492 | |
| S5‑254813 | Rel-20 pCR 32.872 Introduce the usecase2 on Local Breakout Inter CHFs | Huawei | pCR | Approval |
7.5.25GA Roaming Charging Reliability Enhancement
| Yes |
Yes
| approved | No | S5‑254493 | |
| S5‑254814 | Rel-20 pCR 32.872 Introduce the usecase3 on Local Breakout Inter CHFs | Huawei | pCR | Approval |
7.5.25GA Roaming Charging Reliability Enhancement
| Yes |
Yes
| not pursued | No | S5‑254494 | |
| S5‑254815 | Rel-20 pCR 32.872 Introduce the usecase on Home Routed scenario | Huawei | pCR | Approval |
7.5.25GA Roaming Charging Reliability Enhancement
| Yes |
Yes
| approved | No | S5‑254495 | |
| S5‑254816 | Rel-20 pCR TR 32.801-02 Update of the Scope | China Telecom | pCR | Approval |
7.6.1Charging Aspects of 6G System
| Yes |
YesSimilar as S5-254287 and will consider this pCR as integrated without all details of the SID
H: No need of the link to normative work
Rev1 avaialble
CH Plenary:approved
| approved | No | S5‑254359 | |
| S5‑254817 | pCR TR 32.801-02 Add background for the 6G Charging | Huawei | pCR | Approval |
7.6.1Charging Aspects of 6G System
| Yes |
YesE: what is ‘dynamic offerirng’
H: combination of different services in a package
N: could be achieved with PCF based on PCC rules
E: what is behind ptotection
H: it is related to user consent
References and abbreviation will be added
Chapter 4.2 will be removed
4.1 is for 5G CCS
Rev1 available
CH Plenary: approved
| approved | No | S5‑254506 | |
| S5‑254818 | Rel-20 pCR TR 32.801-02 Update of the skeleton | China Telecom | pCR | Approval |
7.6.1Charging Aspects of 6G System
| Yes |
YesH: How could the mapping be done because it is not clear during the study
H: How is the relationship between our own req and other requirements as in 5.x.2
The structure of the TR should start with Background as ussgested in S5-254506 followed by business model before list to topics
A separate presentation covered two different options for the
The groop agreed to have under High-level description
4.1 Backgroung
4.2 Bisiness Model
Subclause 5.Topics should follow the structure of TR 28.826.
Rev1 available
rev2 available
rev3 available
Rev4 available
rev5 avaialble
CH Plenary:
Add Topic x to topics
Rev6 approved
| approved | No | S5‑254358 | |
| S5‑254819 | Rel-20 pCR TR 32.801-02 Introduce a topic of new charging business models and charging metrics for 6G | China Telecom, Huawei, Ericsson | pCR | Approval |
7.6.1Charging Aspects of 6G System
| Yes |
YesN: Business model and metrics should not be linked
There will be no requirements and key issue content
Will incorporate S5-254507 and S5-254464
Rev1 available
CH Plenary:
Editorials
Rev2 approved
| approved | No | S5‑254360 | |
| S5‑254820 | Rel-20 pCR 32.801-02 Study structure 6G charging architecture and mechanism | Ericsson | pCR | Approval |
7.6.1Charging Aspects of 6G System
| Yes |
YesH: Maybe better to agree on two major topics for architecture and mechanism
The pCR will integrate S5-254508 to cover the architecture aspects.
The interworking will be covered from the SID.
Charging collection part will be merged into S5-254509, failure handling is removed
No agreement has been reached on the sentence to cover the interworking therefore was it proposed to have just the content of the SID 1:1 copied into all pCRs which wasn’t also not accepted.
Final agreement is just to keep the title of the topic.
Rev1 available
CH Plenary:
Add Topic 1: to thew tile
Add Description and delele s in 5.1.7
Rev2 approved
| approved | No | S5‑254465 | |
| S5‑254821 | pCR TR 32.801-02 Add general description for WT2.1 flexible charging | Huawei | pCR | Approval |
7.6.1Charging Aspects of 6G System
| Yes |
YesThis pCR will cover charging mechanism topic 5.2
E: first item should be for configuration
5G charging mechanism…
E: keep just the two for static and dynamic
no need for enhancement at this time
Based on the discussion for S5-254465 for which no agreement reached on the content will just the title for the clause remain.
Rev1 available
CH Plenary:
6.2 - > 5.2
Rev2 approved
| approved | No | S5‑254509 | |
| S5‑254822 | Suggestion for draft TR 32.801-02 skeleton | China Telecom | discussion | discussion |
7.6.1Charging Aspects of 6G System
| Yes |
YesThe group finally agreed on this guidance for the skeleton which should be used for the upcoming pCRs.
D1 available
CH Plenary:
structure is endorsed and will be added to the SA5 CH collection
Noted
| noted | No | ||
| S5‑254823 | Rel-19 CR 28.201 Addition on NSPA charging information | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-20 Charging small enhancements
| Yes |
Yes
| not pursued | No | S5‑254487 | |
| S5‑254824 | Rel-19 CR 32.291 Correction on Cardinality and Presence | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-20 Charging small enhancements
| Yes |
Yes
| not pursued | No | S5‑254371 | |
| S5‑254825 | Rel-19 CR 32.255 Correction of general principles | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-20 Charging small enhancements
| Yes |
Yes
| agreed | No | S5‑254481 | |
| S5‑254826 | Rel-19 CR TS 32.291 IMS Call Charging Optimization | CSCN | CR | Agreement |
7.3Charging Maintenance and Rel-20 Charging small enhancements
| Yes |
Yes
| not pursued | No | S5‑254362 | |
| S5‑254827 | Rel-19 CR 32.290 Corrections on quota management | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-20 Charging small enhancements
| Yes |
Yes
| not pursued | No | S5‑254485 | |
| S5‑254828 | Rel-19 CR 32.291 Correction on the re-used data types of Nchf_ConvergedCharging | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-20 Charging small enhancements
| Yes |
Yes
| not pursued | No | S5‑254486 | |
| S5‑254829 | Rel-19 CR 32.255 Clarify the CHF selection method | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-20 Charging small enhancements
| Yes |
Yes
| agreed | No | S5‑254497 | |
| S5‑254830 | Rel-19 CR 32.255 Clarification on CHF address and Charging Characteristics | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-20 Charging small enhancements
| Yes |
YesC: why is the CHF Group ID not added in PCF, NRF
E: CHF Group ID should be kept in the table
N: all are example and optional
First change will be evaluated based on a reworded sentence in the revision
N: CHF address and the CHF Group ID should be kept together
C: TS 23.501 is clearly referencing CC under the control in TS 32.255
Rev1 available
Rev2 available
CH Plenary:
E: there are ongoing discussion in CT WGs
Second change will be removed
| not pursued | No | S5‑254502 | |
| S5‑254831 | Rel-19 CR 32.274 Clarification on CHF address and Charging Characteristics | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-20 Charging small enhancements
| Yes |
YesSame request as in S5-254502
| not pursued | No | S5‑254503 | |
| S5‑254832 | Rel-19 CR 32.256 Clarification on CHF address and Charging Characteristics | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-20 Charging small enhancements
| Yes |
Yes
| not pursued | No | S5‑254504 | |
| S5‑254833 | Remove the Satellite Backhaul QoS change trigger | China Mobile Com. Corporation | CR | Agreement |
7.3Charging Maintenance and Rel-20 Charging small enhancements
| Yes |
Yes
| agreed | No | S5‑254617 | |
| S5‑254834 | Remove the Satellite Backhaul QoS change trigger | China Mobile Com. Corporation | CR | Agreement |
7.3Charging Maintenance and Rel-20 Charging small enhancements
| Yes |
Yes
| agreed | No | S5‑254618 | |
| S5‑254835 | Correction of SatelliteBackhaulCategory | China Mobile Com. Corporation | CR | Agreement |
7.3Charging Maintenance and Rel-20 Charging small enhancements
| Yes |
Yes
| not pursued | No | S5‑254619 | |
| S5‑254836 | Correction of SatelliteBackhaulCategory | China Mobile Com. Corporation | CR | Agreement |
7.3Charging Maintenance and Rel-20 Charging small enhancements
| Yes |
Yes
| not pursued | No | S5‑254620 | |
| S5‑254837 | Rel-19 CR 32.260 Correction on the Abbreviations | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-20 Charging small enhancements
| Yes |
Yes
| not pursued | No | S5‑254483 | |
| S5‑254838 | Rel-19 CR 32.290 Corrections to the misalignment and editorial errors of charging scenarios | Huawei | CR | Agreement |
7.3Charging Maintenance and Rel-20 Charging small enhancements
| Yes |
Yes
| not pursued | No | S5‑254484 | |
| S5‑254839 | TR 32.872 email approval | Huawei | draft TR | Approval |
7.5.25GA Roaming Charging Reliability Enhancement
| No |
Yes
| for email approval | No | ||
| S5‑254840 | draft TR 28.891 email approval | Ericsson | draft TR | Approval |
7.5.25GA Roaming Charging Reliability Enhancement
| No |
Nofor email approval
| for email approval | No | ||
| S5‑254841 | TR 32.801-02 email approval | China Telecom | draft TR | Approval |
7.6.1Charging Aspects of 6G System
| No |
Yesfor email approval
| for email approval | No | ||
| S5‑254842 | Rel-20 pCR TR 28.883 Improvement of data generation | Huawei | pCR | Approval |
6.20.3Study on management aspects of Network Digital Twins phase 2
| Yes |
Yes
| approved | No | S5‑254671 | |
| S5‑254843 | pCR TR 28.883 Add use case and requirements on enhancement for multiple NDT collaborations | China Mobile | pCR | Approval |
6.20.3Study on management aspects of Network Digital Twins phase 2
| Yes |
Yes
| approved | No | S5‑254673 | |
| S5‑254844 | pCR TR 28.884 Use case on software management | Huawei | pCR | Approval |
6.20.4Study on Service Based Management Architecture enhancement phase 4
| Yes |
Yes
| approved | No | S5‑254679 | |
| S5‑254845 | pCR TR 28.884 Use case on inventory management | Huawei | pCR | Approval |
6.20.4Study on Service Based Management Architecture enhancement phase 4
| Yes |
Yes
| approved | No | S5‑254680 | |
| S5‑254846 | Reply LS on specification of dataset and model parameters exchange | SA5 | LS out | Approval |
5.3Liaison statements at SA5 level
| Yes |
Yes
| approved | No | S5‑254791 | |
| S5‑254847 | New WID on Charging aspects of next generation real time communication services phase 3 | China Mobile | WID new | Approval |
7.2.1New CH SIDs/WIDs proposals
| Yes |
Yesis endorsed
| endorsed | No | S5‑254803 | |
| S5‑254848 | My SA5 – song for SA5 | Ericsson | other | Endorsement |
8Any Other Business
| Yes |
Yesis endorsed
| endorsed | No | ||
| S5‑254849 | Presentation sheet of TR 28.869 for SA approval | China Mobile | TS or TR cover | Approval |
6.19.6Study on Cloud Aspects of Management and Orchestration
| Yes |
Yes
| agreed | No | S5‑254392 | |
| S5‑254850 | draft TR 28.869 v1.7.0 | China Mobile | draft TR | Approval |
6.19.6Study on Cloud Aspects of Management and Orchestration
| No |
No
| reserved | No | ||
| S5‑254851 | draft TR 28.892 v0.0.1 | Vodafone | draft TR | Approval |
6.20.15Unified Management interface for Multi-RAT support
| No |
No
| reserved | No | ||
| S5‑254870 | Rel-18 CR TS28.554 Add missing formula for MobilityRegUpdateSR | ZTE Corporation | CR | Agreement |
6.4OAM Rel-16
| Yes |
Yes
| agreed | No | S5‑254595 | |
| S5‑254871 | Rel-19 CR TS28.554 Add missing formula for MobilityRegUpdateSR | ZTE Corporation | CR | Agreement |
6.4OAM Rel-16
| Yes |
Yes
| agreed | No | S5‑254596 | |
| S5‑254872 | Rel-18 CR TS 28.622 Clarify usage of notifyFileReady | Ericsson Canada Inc. | CR | Agreement |
6.6.95G performance measurements and KPIs phase 3
| Yes |
Yes
| revised | No | S5‑254891 | S5‑254554 |
| S5‑254873 | Rel-19 CR TS 28.622 Clarify usage of notifyFileReady | Ericsson Canada Inc. | CR | Agreement |
6.6.95G performance measurements and KPIs phase 3
| Yes |
Yes
| revised | No | S5‑254892 | S5‑254555 |
| S5‑254874 | Rel-20 CR TS 28.622 Clarify usage of notifyFileReady | Ericsson Canada Inc. | CR | Agreement |
6.6.95G performance measurements and KPIs phase 3
| Yes |
Yes
| revised | No | S5‑254893 | S5‑254556 |
| S5‑254875 | Rel-18 CR TS28.552 Fix MOI for VR usage of NF related PMs | ZTE Corporation | CR | Agreement |
6.6.26Rel-18 CAT B/C SA5 internal alignment and other CAT F CR(s)
| Yes |
Yes
| agreed | No | S5‑254590 | |
| S5‑254876 | Rel-19 CR TS28.552 Fix MOI for VR usage of NF related PMs | ZTE Corporation | CR | Agreement |
6.6.26Rel-18 CAT B/C SA5 internal alignment and other CAT F CR(s)
| Yes |
Yes
| agreed | No | S5‑254591 | |
| S5‑254877 | Rel-20 CR TS28.552 Fix MOI for VR usage of NF related PMs | ZTE Corporation | CR | Agreement |
6.6.26Rel-18 CAT B/C SA5 internal alignment and other CAT F CR(s)
| Yes |
Yes
| agreed | No | S5‑254592 | |
| S5‑254878 | Discussion on the need for prioritisation of work | NEC | discussion | Endorsement |
6.20.2Study on AI/ML management phase 3
| Yes |
Yesd1
E/// objected. Do not see the need to endorse this.
SA5 Chair: would be good to still have some rapporteur's guidance.
E///: could have an email from the rapporteur before every meeting with a reminder about the items we should focus on. Meaning of the note?
NEC: this paper will not be brought in at every meeting.
SA5 Chair: is endorsed as a guidance.
| noted | No | S5‑254607 | |
| S5‑254879 | Pseudo-CR TR28.869 Terminology alignment | DOCOMO Beijing Labs | pCR | Approval |
6.19.6Study on Cloud Aspects of Management and Orchestration
| Yes |
Yesd2
Huawei: pls. remove cloud nw function.
| approved | No | S5‑254419 | |
| S5‑254880 | Rel-19 CR TS 28.540 add missing concepts and backgrouds of management of NG-RAN and 5GC | Huawei | CR | Agreement |
6.19.135G Advanced NRM features phase 3
| Yes |
YesNokia objected.
Will follow up.
| not pursued | No | S5‑254257 | |
| S5‑254881 | Rel-20 Discussion on the management support for NG-RAN 5GC feature | Huawei | discussion | Endorsement |
6.19.135G Advanced NRM features phase 3
| Yes |
Yes
| noted | No | S5‑254265 | |
| S5‑254882 | pCR TR 28.883 Introduce precision in the execution of network simulation tasks | Huawei | pCR | Approval |
6.20.3Study on management aspects of Network Digital Twins phase 2
| Yes |
YesNokia and Samsung objected.
| noted | No | S5‑254480 | |
| S5‑254883 | Modified EnExpo SID | Nokia Mexico | SID revised | Endorsement |
6.2.2Revised OAM SIDs/WIDs proposals
| Yes |
Yes
| agreed | No | S5‑254570 | |
| S5‑254884 | Rel-20 pCR TR 28.881 Add description and requirements for intent guarantee UC#8 | Ericsson Korea Partners Co Ltd | pCR | Agreement |
6.20.1Study on intent driven management services for mobile network phase 4
| Yes |
Yes
| approved | No | S5‑254651 | |
| S5‑254885 | Rel-20 pCR 28.889 CCL for LCM | Samsung R&D Institute India | pCR | Agreement |
6.20.10Study on Closed Control Loop Management phase 2
| Yes |
Yes
| approved | No | S5‑254703 | |
| S5‑254886 | pCR TR28.889 CCL for network slice resource optimization.docx" | Nokia | pCR | Approval |
6.20.10Study on Closed Control Loop Management phase 2
| Yes |
YesE/// objected
| noted | No | S5‑254311 | |
| S5‑254887 | pCR TR28.889 CCL interactions with other functionalities | Nokia Americas | pCR | Approval |
6.20.10Study on Closed Control Loop Management phase 2
| Yes |
YesE/// objected
| noted | No | S5‑254338 | |
| S5‑254889 | New WID on Life Cycle Management (LCM) of NF Deployment | Moderator (China Mobile), Ericsson, Nokia | WID new | Approval |
6.2.1New OAM SIDs/WIDs proposals
| Yes |
Yes+Verizon, +China Unicom
SA5 Chair: pls. use latest template
| revised | No | S5‑254906 | S5‑254546 |
| S5‑254890 | Rel-20 CR TS 28.623 Correct several issues for the IOCs related to MADCOL | Huawei | CR | Agreement |
6.20.0OAM Rel-20 small enhancements
| Yes |
Yes
| agreed | No | S5‑254643 | |
| S5‑254891 | Rel-18 CR TS 28.622 Clarify usage of notifyFileReady | Ericsson Canada Inc. | CR | Agreement |
6.6.95G performance measurements and KPIs phase 3
| Yes |
Yes
| agreed | No | S5‑254872 | |
| S5‑254892 | Rel-19 CR TS 28.622 Clarify usage of notifyFileReady | Ericsson Canada Inc. | CR | Agreement |
6.6.95G performance measurements and KPIs phase 3
| Yes |
Yes
| agreed | No | S5‑254873 | |
| S5‑254893 | Rel-20 CR TS 28.622 Clarify usage of notifyFileReady | Ericsson Canada Inc. | CR | Agreement |
6.6.95G performance measurements and KPIs phase 3
| Yes |
Yes
| agreed | No | S5‑254874 | |
| S5‑254894 | Pseudo-CR on Introduction for data management phase-3 | Ericsson Telecomunicazioni SpA | pCR | Approval |
6.20.8Study for Data management phase 3
| Yes |
Yes
| approved | No | S5‑254692 | |
| S5‑254895 | Pseudo-CR on Scope for data management phase-3 | Ericsson Telecomunicazioni SpA | pCR | Approval |
6.20.8Study for Data management phase 3
| Yes |
Yes
| approved | No | S5‑254693 | |
| S5‑254896 | draft TR 28.881 v0.2.0 | Ericsson | draft TR | Approval |
6.20.1Study on intent driven management services for mobile network phase 4
| Yes |
Yesfor email approval
| for email approval | No | ||
| S5‑254897 | draft TR 28.882 v0.1.0 | Ericsson | draft TR | Approval |
6.20.2Study on AI/ML management phase 3
| No |
Yesfor email approval
| for email approval | No | ||
| S5‑254898 | draft TR 28.883 v0.1.0 | Huawei | draft TR | Approval |
6.20.3Study on management aspects of Network Digital Twins phase 2
| No |
Yesfor email approval
| for email approval | No | ||
| S5‑254899 | draft TR 28.884 v0.1.0 | Ericsson | draft TR | Approval |
6.20.4Study on Service Based Management Architecture enhancement phase 4
| No |
Yesfor email approval
| for email approval | No | ||
| S5‑254900 | draft TR 28.885 v0.1.0 | Samsung | draft TR | Approval |
6.20.5Study on energy efficiency and energy saving aspects of 5G Advanced
| No |
Yesfor email approval
| for email approval | No | ||
| S5‑254901 | draft TR 28.886 v0.2.0 | Ericsson | draft TR | Approval |
6.20.7Study on Management Data Analytics (MDA) phase 4
| No |
Yesfor email approval
| for email approval | No | ||
| S5‑254902 | draft TR 28.887 v0.2.0 | Ericsson | draft TR | Approval |
6.20.8Study for Data management phase 3
| No |
Yesfor email approval
| for email approval | No | ||
| S5‑254903 | draft TR 28.888 v0.1.0 | Nokia | draft TR | Approval |
6.20.9Study on Enhanced exposure of management services
| Yes |
Yesfor email approval
| for email approval | No | ||
| S5‑254904 | draft TR 28.889 v0.1.0 | Nokia | draft TR | Approval |
6.20.10Study on Closed Control Loop Management phase 2
| Yes |
Yesfor email approval
| for email approval | No | ||
| S5‑254905 | Study on 6G Management and Orchestration | China Unicom (Moderator) | SID new | Approval |
6.2.1New OAM SIDs/WIDs proposals
| No |
Yesis endorsed
| endorsed | No | S5‑254638 | |
| S5‑254906 | New WID on Life Cycle Management (LCM) of NF Deployment | Moderator (China Mobile), Ericsson, Nokia | WID new | Approval |
6.2.1New OAM SIDs/WIDs proposals
| Yes |
Yes
| agreed | No | S5‑254889 | |
| S5‑254907 | Rel-19 CR TS 28.561 Make NDTDataValue and NDTScalingFactor as conditional mandatory attributes | L.M. Ericsson Limited | CR | Agreement |
6.19.5Management aspects of Network Digital Twins
| Yes |
Yes
| agreed | No | S5‑254765 | |
| S5‑254908 | Rel-19 CR TS28.567 Clarify CCL-related MnS | Nokia | CR | Agreement |
6.19.4Closed Control Loop Management
| Yes |
Yes
| agreed | No | S5‑254759 |