Dear @Bassem Sabbagh,

As discussed in our earlier meeting, kindly assign an AI DEV resource to implement a rule for parsing nodes as outlined below:

Note: This rule will apply when duplicate child nodes (Role2G/Role3G/Role4G) are found across two different nodes (see example for reference).
Rule: We need to disregard the node containing “MMM,” “VIP,” “DIS,” “Core,” or “Templock” in the NEName, and parse only the second node.

Example: Below are two examples where duplicate child nodes are found across two different nodes, and only one node will be parsed while the other will be ignored:

1- The SRANB nodes MDN2996-P1-VIP_SRAN and MDN2996-MMM-P1-VIP_SRAN contain duplicate child nodes with the same model (NEType="BTS5900"). Both nodes have the same Role2G node, MDN2C2996-MMM-P1-VIP. In this case, we will parse only the node "MDN2996-P1-VIP_SRAN" and ignore the second node, "MDN2996-MMM-P1-VIP_SRAN," which contains "MMM" in the NEName.

2- The SRANB nodes RUM2708-P3_SRAN and RIY2708-VIP-P1_SRAN-DIS contain duplicate child nodes with the same model (NEType="BTS3900"). Both nodes have the same Role2G (RUM2M2708-P3), Role3G (RUM2M4708-P3), and Role4G (RUM2M8708-P3-L800) nodes. In this case, we will parse only the node "RUM2708-P3_SRAN" and ignore the second node, "RIY2708-VIP-P1_SRAN-DIS," which contains "DIS" in the NEName.

Best regards,
Indrasan

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Dear @Sandya Sharma,

As discussed now nodes are parsing correctly as per given rule except below case for which we need to apply an extra condition as described below:

Please apply the following additional conditions during parsing:

1. Disregard Nodes Containing "FWA":
o If the NEName contains "FWA," disregard that node and parse only the second node where a duplicate child node is found across two different parent nodes.
2. Handle Duplicate Child Nodes for "MMM" and "VIP":
o In cases where a duplicate child node is found across nodes with NEName containing "MMM" and "VIP," parse the node with "VIP" in the NEName and disregard the node with "MMM."

For reference, I have attached a snippet where nodes marked in yellow need to be disregarded due to containing "FWA" in the NEName, and the second node should be parsed.

Please let me know if further clarification is required.

Best regards,
Indrasan

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Dear @Sandya Sharma,

As discussed, please add the following rules under the existing ZKU-234 conditions. (Please ensure that the existing conditions are not modified, and only these additional rules are implemented.)

Rules to be Added:
1. Ignore nodes containing “TEMPLOCK” or “TempLocked” in the node name where duplicate child nodes are found in two different nodes. (Ensure case sensitivity is considered for "TEMPLOCK.")
2. Disregard nodes containing only “HUB” and parse the second one if it contains “WDM” along with “HUB.”

Examples:

Sr. No. Node ID Child Node ID Child Node Role Latest Dump Comment Latest XML Comment
1 YBDB2291-P1-HUB_SRAN YBDB2M2291-P1-HUB 2G Issue persists in the dump dated 22-01-2025 Currently, Node is parsing but it shouldn't (new case); rule added as above under ZKU-234
2 HAJ0082-P3_SRAN-TEMPLOCK HAJ2M1082-P3 2G Issue persists in the dump dated 22-01-2025 Currently, Node is parsing but it shouldn't (new case); rule added as above under ZKU-234
3 HAJ0270-P3_SRAN-TempLocked HAJ2M1270-P3 2G Issue persists in the dump dated 22-01-2025 Currently, Node is parsing but it shouldn't (new case); rule added as above under ZKU-234
4 HAJ0270-P3_SRAN HAJ2M1270-P3 2G Issue persists in the dump dated 22-01-2025 Node is parsing i.e., OK
5 HAJ0082-P3_SRAN HAJ2M1082-P3 2G Issue persists in the dump dated 22-01-2025 Node is parsing i.e., OK
6 YBDB2291-P1-WDM-HUB_SRAN YBDB2M2291-P1-HUB 2G Issue persists in the dump dated 22-01-2025 Node is parsing i.e., OK

I have also updated the rule details under JIRA ZKU-234.

Request:

After implementing the above rules, kindly share the final full XML, including Huawei license data, for validation.

Regards,
Indrasan

(Mail is attached for reference with date 28-01-2025).