[{"name":"S5-254209","title":"OAM&P action list","source":"WG Vice Chair (China Unicom)","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"other","for":"","abstract":"","secretary_remarks":"","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"OAM Plenary","tdoc_agenda_sort_order":42090,"status":"noted","reservation_date":"2025-09-29 17:24:55","uploaded":"2025-10-22 02:42:24","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG5_TM\/TSGS5_163\/Docs\/S5-254209.zip","group":"S5","meeting":"S5-163","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S5-254210","title":"OAM Exec Report","source":"WG Vice Chair (China Unicom)","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"report","for":"","abstract":"","secretary_remarks":"","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"OAM Plenary","tdoc_agenda_sort_order":42100,"status":"noted","reservation_date":"2025-09-29 17:24:55","uploaded":"2025-10-22 02:42:24","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG5_TM\/TSGS5_163\/Docs\/S5-254210.zip","group":"S5","meeting":"S5-163","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S5-254213","title":"Collection of external communication documents in OAM","source":"WG Chair (Huawei)","contact":"Lan Zou","contact-id":35534,"tdoctype":"other","for":"","abstract":"","secretary_remarks":"","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"OAM Plenary","tdoc_agenda_sort_order":42130,"status":"noted","reservation_date":"2025-09-29 17:24:55","uploaded":"2025-10-22 02:42:24","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG5_TM\/TSGS5_163\/Docs\/S5-254213.zip","group":"S5","meeting":"S5-163","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S5-254214","title":"Collection of external communication documents in OAM","source":"WG Vice Chair (China Unicom)","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"other","for":"","abstract":"","secretary_remarks":"","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"OAM Plenary","tdoc_agenda_sort_order":42140,"status":"withdrawn","reservation_date":"2025-09-29 17:24:55","uploaded":null,"revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S5","meeting":"S5-163","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S5-254221","title":"OAM breakout notes","source":"WG Chair (Huawei)","contact":"Lan Zou","contact-id":35534,"tdoctype":"report","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"OAM Plenary","tdoc_agenda_sort_order":42210,"status":"noted","reservation_date":"2025-09-30 13:15:08","uploaded":"2025-10-17 17:01:07","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG5_TM\/TSGS5_163\/Docs\/S5-254221.zip","group":"S5","meeting":"S5-163","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S5-254322","title":"LS on User consent for Data collection at the UE for NW-side model training","source":"RAN2","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS in","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"OAM Plenary","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2025-10-01 15:34:44","uploaded":"2025-10-01 16:20:27","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"NR_AIML_air-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"R2-2506541","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/ftp\/tsg_sa\/WG5_TM\/TSGS5_163\/Docs\/S5-254322.zip","group":"S5","meeting":"S5-163","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S5-254348","title":"Reply LS on geographical area scope MDT","source":"CATT, Ericsson","contact":"Min Shu","contact-id":83568,"tdoctype":"LS out","for":"Approval","abstract":"SA5 thanks RAN3 for the incoming LS on geographical area scope MDT (R3-255960). SA5 has been requested to update SA5 specifications based on the RAN3 agreed geographical area scope for MDT and optionally a PLMN ID list. \nSA5 has discussed and agreed on the proposed changes related to Geographical Area.\n\u2022\tGeographical Area is agreed and added as a new choice for area scope.\n\u2022\tReuse PLMN ID list in configuration parameters which are specific for MDT.\nAgreed contributions are attached for reference.\n2\tActions\nTo RAN3\nACTION: \tSA5 kindly asks RAN3 to assess whether these proposed changes could meet the requirements.","secretary_remarks":"","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"OAM Plenary","tdoc_agenda_sort_order":43480,"status":"revised","reservation_date":"2025-10-02 03:54:27","uploaded":"2025-10-03 14:38:40","revisionof":"","revisedto":"S5-254790","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"NR_ENDC_SON_MDT_Ph4-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN3, RAN2","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG5_TM\/TSGS5_163\/Docs\/S5-254348.zip","group":"S5","meeting":"S5-163","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S5-254383","title":"DP on reference to other release version","source":"Ericsson LM","contact":"Thomas Tovinger","contact-id":3654,"tdoctype":"discussion","for":"Endorsement","abstract":"The CR S5-253652 [1] \u201cRel-16 CR 32.312 Wrong reference\u201d, and related Rel-17\/18 mirror CRs, was agreed at SA5#162 and approved by SA#109.\nThe Reason for change of this CR explains the background: \u201cTS 32.312 imports entities from the referred TS 32.622.  The last release of 32.622 was Rel-11. The correct reference should be to 28.622, which is the continuation of 32.622 since Rel-11 and exists in the same release as the current version of 32.312\u201d.\nThe Summary of change (as well as the actual change in the TS) was to \u201cUpdate the reference of 32.622 to 28.622\u201d, meaning that the reference will point to the latest version on 28.622 in the same release as the Rel-16\/17\/18 TS 32.312. \u201cSo far so good\u201d.\nHowever, after SA5#162 we have also discovered that several of the other 4G Interface IRP IS TSs have the same issue with a reference to 32.622 (e.g. 32.572, 32.122, 32.322). When preparing similar CRs as [1] for those TSs, we identified an alternative way of solving this error which may be a better solution and perhaps preferred by SA5. Therefore we would like SA5 to consider the pros and cons of both options and take a decision on the recommended option before we prepare those CRs.\nThe alternative option (let\u2019s call it option 2) is this: Instead of updating the reference to 28.622 (same version as the referencing TS), keep the reference to 32.622 but make it a specific reference to the latest Rel-11 version of 32.622 which is 11.1.0. This was the reference that was intended when 32.312 (and the other Interface IRP specifications) were created in Rel-11, thus there will be no impact on the inherited attributes from Top.\nSummary of the options:\n1.\tSame solution as in [1], i.e. updating the reference from 32.622 to 28.622 (same version as the referencing TS).\na.\tPros: All references are kept within the same release, i.e. keeping a \u201ccoherent and consistent\u201d set of TSs in the same release, with less risk of inconsistencies e.g. when new features are added or existing features modified in the future.\nb.\tCons: 1) The inherited attributes from Top IOC are changed compared to the Rel-11 version of 32.622: Top in 28.622 inherits from Top_ and TopX which contain the attributes id, objectClass and objectInstance, while 32.622 v11.1.0 (which does not inherit from any IOC) contains only objectClass and objectInstance. 2) Potential impacts on the SS and interface implementations (although the Top attributes are not explicitly defined in the SS, e.g. 32.316).\n2.\tInstead of updating the reference to 28.622 (same version as the referencing TS), keep the reference to 32.622 but make it a specific reference to the latest Rel-11 version of 32.622 which is 11.1.0.\na.\tPros: No impact on inherited attributes from Top. No impact on the SS and interface implementations.\nb.\tCons: The TS would contain a specific reference to a very old TS (which may not even be maintained in the future), causing potential risk for inconsistent set of TSs in the same release in the future.\n4\tDetailed proposal\nWe recommend endorsing option 2.","secretary_remarks":"","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"OAM Plenary","tdoc_agenda_sort_order":43830,"status":"endorsed","reservation_date":"2025-10-02 11:45:06","uploaded":"2025-10-02 11:52:00","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG5_TM\/TSGS5_163\/Docs\/S5-254383.zip","group":"S5","meeting":"S5-163","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S5-254575","title":"LS on Clarifications for UE Data Collection","source":"Nokia","contact":"Sreekumar Pothera Kalloor","contact-id":103772,"tdoctype":"LS out","for":"Approval","abstract":"","secretary_remarks":"","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"OAM Plenary","tdoc_agenda_sort_order":45750,"status":"noted","reservation_date":"2025-10-03 15:45:49","uploaded":"2025-10-03 16:14:30","revisionof":"","revisedto":"","release":"Rel-20","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN2, RAN3, SA3","Cc":"SA2","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG5_TM\/TSGS5_163\/Docs\/S5-254575.zip","group":"S5","meeting":"S5-163","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S5-254603","title":"Reply LS on OAM-centric solution for NW-side data collection","source":"Nokia Japan","contact":"Sreekumar Pothera Kalloor","contact-id":103772,"tdoctype":"LS out","for":"Approval","abstract":"SA5 would like to thank RAN2 for their LS in R2-2506543 on OAM-centric solution for NW-side data collection and considering the input provided by SA5. \nSA5 acknowledges the following details and further request for clarification received RAN2:\n==========Start R2-2506543==================\nRAN2#131 discussed it and concluded the following:\nRAN2 measurements \n1\tFor network-side data collection for beam prediction, measurement reports include the following:\n?\tCell identity: CGI or PCI of the cell to which the measurement results are related to.\n?\tLogged L1 radio measurement results including the beam identifiers associated to CSI-RS resources or SSBs (CSI-RS IDs or SSB IDs) and the corresponding measured L1-RSRPs.\n-\t[CB after OI discussion] Information to indicate a gap that is longer than the configured logging periodicity in the logged measurements which can happen due to event-based logging. FFS the details.\n2: The required L1 measurements (i.e. L1-RSRP of CSI-RS(s) or SSBs) are defined in TS 38.215 which is referenced in the definition of M1 measurement in TS 37.320.\n3: RAN2 needs to ask SA5 how to transfer the measurement report with the above content and whether the M1 measurement defined in clause 5.4.1.1 of TS 37.320 can be used to transfer the measurement reports with the above content or not.\n4: The gNB will configure the UE to log the above content via the NW-side data collection configuration, which is different from legacy immediate MDT configuration.\n\nFor the 1st agreement above, the last information is updated into: the presence of a gap that is longer than the configured logging periodicity in the logged measurements.\nRAN2 notes that the required L1 measurements (i.e. L1-RSRP of CSI-RS(s) or SSBs) are defined in TS 38.215, which is referenced in the definition of M1 measurement in TS 37.320. However, RAN2 is not sure whether this measurement can be used to transfer the measurement reports with the current content mentioned above from gNB to OAM or not. On this aspect, RAN2 expects inputs from SA5.\n==========End R2-2506543==================\nSA5 would like to confirm that the Rel-20 study item \u201cData Management Phase 3\u201d (FS_MADCOL_Ph3) intents to bring support for collection of UE generated data not supported by the exiting Trace \/ MDT mechanisms. We will evaluate the requirements from RAN2 as part of the study in Rel-20.\n\n2\tActions\nTo RAN2\nACTION: SA5 kindly asks RAN2 to consider the above information in to account and contact us for further updates on the work status.","secretary_remarks":"","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"OAM Plenary","tdoc_agenda_sort_order":46030,"status":"noted","reservation_date":"2025-10-03 18:23:41","uploaded":"2025-10-03 18:27:30","revisionof":"","revisedto":"","release":"Rel-20","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN2","Cc":"RAN3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG5_TM\/TSGS5_163\/Docs\/S5-254603.zip","group":"S5","meeting":"S5-163","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S5-254790","title":"Reply LS on geographical area scope MDT","source":"CATT, Ericsson","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS out","for":"Approval","abstract":"","secretary_remarks":"","agenda_item_sort_order":13,"ainumber":"6.1","ainame":"OAM Plenary","tdoc_agenda_sort_order":43481,"status":"approved","reservation_date":"2025-10-21 05:55:08","uploaded":"2025-10-21 06:01:08","revisionof":"S5-254348","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"NR_ENDC_SON_MDT_Ph4-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN3, RAN2","Cc":"","lsoriginalls":"","lsreply":"R3-258321","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG5_TM\/TSGS5_163\/Docs\/S5-254790.zip","group":"S5","meeting":"S5-163","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]