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, ZKU-158, and I have shared the relevant details in a separate email.

Best regards,
Indrasan

Hi Sandya, as discussed please commit code for same JIRA ZKU-136.

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.