Mobinets-JIRA

Mobinets-JIRA http://jira.mobinets.com/jira This file is an XML representation of an issue en-us

6.1.4

6159

19-11-2013

[ZKU-136] Node Type Parsing Rule for ZAIN-KSA To Be Update_Huawei http://jira.mobinets.com/jira/browse/ZKU-136 Zain KSA upgradation ZKU-136

Node Type Parsing Rule for ZAIN-KSA To Be Update_Huawei

Task Normal Done Unresolved Indrasan Yadav Indrasan Yadav AI_All_incidents ZAINKSAAUDIT ZAINKSAUAT Tue, 12 Nov 2024 07:11:08 +0200 Tue, 26 Nov 2024 04:32:46 +0200 Fri, 29 Nov 2024 00:00:00 +0200 0 3 0 minutes 5 hours, 30 minutes Dear @Bassem & Ahad, As we know, the current node parsing rule for ZAIN-KSA covers only three types of nodes: BSC, RNC, and SRAN. Notably, SRAN includes all standalone nodes, such as BTS, NodeB, eNodeB, and SRAN itself. I would like to confirm if this rule is satisfactory or if we should implement parsing based on each specific node type, as we did in other projects like OmanTel (i.e., parsing BTS, BSC, RNC, NodeB, eNodeB, and SRAN individually). Thank you for your guidance. Best regards, Indrasan we need to parse correctly all nodes Dear @Sandya Sharma, As discussed, please generate an XML for Huawei using the details we covered during our Teams call. The existing rule can be retained with some modifications as outlined below: 1. Node Parsing Update: Currently, we are parsing only three node types: BSC, RNC, and SRAN. We need to expand this to parse all possible node types separately, including BTS, BSC, RNC, NodeB, eNodeB, and SRAN. This approach will follow the same methodology as we implemented for OmanTel. The node type will be parsed based on the NEType= attribute as specified in the table below: NEType Node BSC6900GSM BSC BSC6910GSM BSC BSC6910GU BSC BSC6900UMTS RNC BSC6910UMTS RNC NodeB NodeB eNodeB eNodeB GSMBTS BTS BTS BTS DBS3900IBS BTS MBTS SRAN BTS3900 SRAN BTS5900 SRAN MICROBTS3900 SRAN BTS59005G SRAN 2. Technology Confirmation: The technology will be determined as follows: o BTS/BSC: 2G o NodeB/RNC: 3G o eNodeB: 4G For SRAN, the technology may vary depending on the dump already available in the current connector. However, the following table will help define the technology: Attributes Technology GbtsFunctionName= 2G NodeBFunctionName= 3G ENodeBFunctionName= 4G attrname="GCELL"> 2G attrname="UCELL"> 3G attrname="LCELL"> 4G attrname="NodeBCell"> 3G attrname="eNodeBCell"> 4G attrname="MBTS2GCell"> 2G attrname="MBTS3GCell"> 3G attrname="MBTS4GCell"> 4G Please let me know if you need further clarification or additional inputs. Best regards, Indrasan Dear @Sandya Sharma, Please find the updated node matching sheet attached. I have included all possible node types in the sheet. Kindly use this updated sheet when generating the Huawei XML. Let me know if you need any further details. Best regards, Indrasan XML shared. Dear @Sandya Sharma, The issue for which this JIRA was raised has now been resolved. Now, separate CSV files are being generated for each node type, including BTS, BSC, NodeB, RNC, eNodeB, and SRAN. Please note that there is a separate JIRA for Huawei_XML validation, <a href="http://jira.mobinets.com/jira/browse/ZKU-158" title="Huawei RAN Inventory_Boards Not Parsing Issue In XML Validation" class="issue-link" data-issue-key="ZKU-158">ZKU-158</a>, and I have shared the relevant details in a separate email. Best regards, Indrasan Hi Sandya, as discussed please commit code for same JIRA <a href="http://jira.mobinets.com/jira/browse/ZKU-136" title="Node Type Parsing Rule for ZAIN-KSA To Be Update_Huawei" class="issue-link" data-issue-key="ZKU-136">ZKU-136</a>. commit done. We are now closing this child JIRA as it pertains to an individual issue. As suggested by @Ahad, all code commit JIRAs will be covered under the parent JIRA. Blocks ZKU-94 Actual Start Tue, 12 Nov 2024 00:00:00 +0200 Baseline End Fri, 29 Nov 2024 00:00:00 +0200 Baseline Start Fri, 29 Nov 2024 00:00:00 +0200 Customer Date of Baselining Wed, 13 Nov 2024 11:50:55 +0200 Dev. Actual Duration Gantt Options Last Comment Evaluation License Error: EXPIRED Original Estimate PDM Actual Duration Planned End Fri, 29 Nov 2024 00:00:00 +0200 Planned Start Fri, 29 Nov 2024 00:00:00 +0200 Rank 0|xtihdl: Rank (Obsolete) 9223372036854775807 VTDirections