[ZKU-264] Need To Modify The Rule To Parse LIC ID_Huawei Created: 05/Mar/25  Updated: 10/Apr/25  Due: 10/Mar/25

Status: Done
Project: Zain KSA upgradation
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Normal
Reporter: Indrasan Yadav Assignee: Indrasan Yadav
Resolution: Unresolved Votes: 1
Labels: AI_All_incidents, ZAINKSAAUDIT, ZAINKSAUAT
Remaining Estimate: 0 minutes
Time Spent: 3 days, 30 minutes
Original Estimate: Not Specified

Attachments: File Need To Modify The Rule To Parse LIC ID_Huawei __ ZKU-264 __.msg     File license 1.rar    
Customer:
Zain KSA 3.X
Planned Start:
Planned End:
Actual Start:
Date of Baselining:

 Description   

Dear @Bassem Sabbagh,

I would like to request the assignment of an AI development resource to implement the updated rules for parsing licenses for Huawei, as detailed below.

Current Scenario: Currently, all LIC IDs are being parsed in XML according to the provided dump, as described in my previous email in LS-241 (Mail is attaching for reference). This includes instances where the same LIC ID appears multiple times for a node, but with different attribute values such as allocation, configuration, usage, and expiration. The NEP team has indicated that not all licenses are being imported due to conditions related to node ID, LIC ID, and LIC details.

Updated Case: To ensure all licenses can be imported into NEP, we need to add a condition to make each LIC ID unique.

SRAN Controller Case:
1. If the same LIC ID is available for the same node with corresponding LIC details, we should append “_2G” for technology 2G and “_3G” for technology 3G to the LIC ID.

Example:

In the SRAN Controller node DM1MBSCH01, the same LIC ID is currently parsed with the same license details in the XML, but for different technologies. We need to modify the LIC ID as follows:
• LQW1CS01_2G
• LQW1CS01_3G

Current XML:

In NEP, only the 3G license is being imported, while the 2G license is ignored.

NEP Import:

Other Node Case:
If the duplicate LIC ID is available for the same node with identical LIC details, we need to add an underscore and a starting value of “1” after the LIC ID value, incrementing by 1 for subsequent instances of the same LIC ID within the same node and license details. We need to modify the LIC ID as follows:
1. LT1S0000RB00_1
2. LT1S0000RB00_2
Example: Below are the LIC Id of one node type eNodeB (RIYA2U6760B-P3) present in the XML but not imported into NEP, with no relevant errors in the error report.
Current XML:

In this case, there are two licenses with the same LIC ID and LIC details for one node, yet only one is being imported into NEP.

NEP Import:

Note: This rule is needed to add in the existing rule there should no changes in existing data parsing. And it will apply for those cases where duplicate LIC ID/Licences details available for a same node ID.

Thank you for your attention to this matter. I look forward to your prompt response.

Best regards,
Indrasan



 Comments   
Comment by Bassem Sabbagh [ 10/Mar/25 ]

Assigned to Jharna to define the WL

Comment by Jharna Thakur [ 13/Mar/25 ]

wl-1.5 days

Comment by Bassem Sabbagh [ 13/Mar/25 ]

to be started on 17-3-25

Comment by Jharna Thakur [ 17/Mar/25 ]

Kindly share the dumps related to it

Comment by Indrasan Yadav [ 17/Mar/25 ]

Require dump is attached here for your reference.

Comment by Jharna Thakur [ 17/Mar/25 ]

Kindly share the remaining dump data as well, as the provided dumps are not generating any licenses.

Comment by Indrasan Yadav [ 18/Mar/25 ]

Hi Jharna, require dump has been shared to you now.

Comment by Bassem Sabbagh [ 18/Mar/25 ]

to be delivered by latest 19-3 the first half

Comment by Jharna Thakur [ 18/Mar/25 ]

Xml has been shared

Comment by Indrasan Yadav [ 19/Mar/25 ]

Hi Jharna, please commit the code.

Comment by Jharna Thakur [ 19/Mar/25 ]

Code has been committed

Comment by Indrasan Yadav [ 19/Mar/25 ]

Dear @Khaled Khalil,

Could you please generate an AI patch as code commit has been done by @Jharna Thakur for the same.

Thank you

Comment by Indrasan Yadav [ 24/Mar/25 ]

From: Khaled Khalil <Khaled.Khalil@nuiva.com>
Sent: 20 March 2025 14:26
To: Bassem Sabbagh <bassem.sabbagh@mobinets.com>; Indrasan Yadav <Indrasan.Yadav@nuiva.com>; Jharna Thakur <Jharna.thakur@nuiva.com>
Cc: Ahad Siddiqui <Ahad.Siddiqui@mobinets.com>
Subject: Re: Need To Modify The Rule To Parse LIC ID_Huawei || ZKU-264 ||

Dear Bassem, I already created a patch yesterday as below, do you need another new one?

Build 3.7.2.24 (19-Mar-2025 4:03:59 PM)

Comment by Indrasan Yadav [ 24/Mar/25 ]

From: Indrasan Yadav <Indrasan.Yadav@nuiva.com>
Sent: 20 March 2025 16:23
To: ABHINAV PARASHAR <ABHINAV.PARASHAR@mobinets.com>
Cc: Ahad Siddiqui <Ahad.Siddiqui@mobinets.com>; Khaled Khalil <Khaled.Khalil@nuiva.com>; Bassem Sabbagh <bassem.sabbagh@mobinets.com>; Sanju Yadav <Sanju.Yadav@mobinets.com>
Subject: RE: Need To Modify The Rule To Parse LIC ID_Huawei || ZKU-264 ||

Dear @ABHINAV PARASHAR,

Please deploy mentioned patch on production and after successfully deploy it also generate full xml on same platform.

Build 3.7.2.24 (19-Mar-2025 4:03:59 PM)

Thank you
Indrasan

Comment by Indrasan Yadav [ 24/Mar/25 ]

Dear Indrasan,

Build 3.7.2.24 Patch deployed and 2025-03-20-01.31.54_ZainKsa.xml full XML file generated after deployment.

NETWORKS TRANSFORMED

Abhinav Parashar| Sr. System Engineer
Mob: +91 9897473040
1102-1103, Tower C, Unitech Cyber Park, Gurgaon
abhinav.parashar@mobinets.com | www.mobinets.com

Comment by Indrasan Yadav [ 24/Mar/25 ]

Require data is seems parsing correctly in XML on production also.

I need to import full XML (2025-03-20-01.31.54_ZainKsa.xml) on production by today EOD because full xml import is not happening automatically since last few days.

Comment by Indrasan Yadav [ 25/Mar/25 ]

Above mentioned XML imported manually on production and now all data related to LIC are parsing in NEP correctly.

Generated at Wed Jul 09 16:35:52 EEST 2025 using JIRA 6.1.4#6159-sha1:44eaedef2e4a625c6c7183698b2468d4719c20dc.