[ZKU-230] Need To Implement Given Rule To Parse Site Id For Nokia RAN Created: 30/Dec/24  Updated: 28/Jan/25  Due: 06/Jan/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: 0
Labels: AI_All_incidents, ZAINKSAAUDIT, ZAINKSAUAT
Remaining Estimate: 0 minutes
Time Spent: 1 week, 7 hours
Original Estimate: Not Specified

Attachments: Microsoft Word FRS_Physical_NSN_ZAIN-KSA.docx     File INFO 3.csv     File On Air Sheets V13.rar     Microsoft Excel Sites_Matching 3.xlsx    
Issue Links:
Blocks
blocks ZKU-95 Nokia RAN_Dumps , XML and NEP data Va... Done
Customer:
Zain KSA 3.X
Planned Start:
Planned End:
Actual Start:
Date of Baselining:

 Description   

Dear @Bassem Sabbagh,

Please assign an AI DEV resource to implement the following rule for parsing the site ID for Nokia RAN, as outlined below:

Priority - 1:
1. Extract the first string before any special characters (such as ‘-’, ‘_’, or ‘/’) from the node name.
2. Search for this extracted value in column ‘C’ of the relevant tab in the “On Air Sheets V13” file, based on the node type. Retrieve the corresponding value from column “B,” which will be the site ID for the node.
The steps for each node type are as follows:

A. For Node Type BTS:
• (I) Search first in the "2G_NSN" tab.
• (II) If not found, search in the "On Air Summary" tab.
• (III) If still not found, search in the "Dismantled Sites" tab.
B. For Node Type NodeB:
• (I) Search first in the "3G_NSN" tab.
• (II) If not found, search in the "On Air Summary" tab.
• (III) If still not found, search in the "Dismantled Sites" tab.
C. For Node Type eNodeB:
• (I) Search first in the "LTE_NSN" tab.
• (II) If not found, search in the "On Air Summary" tab.
• (III) If still not found, search in the "Dismantled Sites" tab.
D. For Node Type SRAN:
• (I) Search first in the "2G_NSN / 3G_NSN / LTE_NSN / 5G_NSN" tabs.
• (II) If not found, search in the "On Air Summary" tab.
• (III) If still not found, search in the "Dismantled Sites" tab.

E. For Node Type BSC: Follow the "site matching sheet."
F. For Node Type RNC: Follow the "site matching sheet."

Priority - 2:
We will prioritize using the “Site matching sheet” for the site ID.

Priority - 3:
The existing rule should be followed for the site ID.

Best regards,
Indrasan



 Comments   
Comment by Bassem Sabbagh [ 31/Dec/24 ]

Assigned to Juned to define the Wl

Comment by Indrasan Yadav [ 31/Dec/24 ]

Dear @Bassem Sabbagh,

Please find the updated FRS attached, which includes the rule added to parse the site ID.

An example is explained in the FRS, and the same FRS has also been attached on JIRA.

Best regards,
Indrasan

Comment by Bassem Sabbagh [ 06/Jan/25 ]

WL = 1.5 mdays to be started on 7-1 and delivered by 8-1

Comment by Bassem Sabbagh [ 07/Jan/25 ]

it is on hold till Sandya commit the code

Comment by Bassem Sabbagh [ 08/Jan/25 ]

code committed and to be started on 9-1

Comment by Juned Ali [ 09/Jan/25 ]

will be delivered by tommorrow first half !!

Comment by Bassem Sabbagh [ 10/Jan/25 ]

to be delivered by 10-1

Comment by Juned Ali [ 12/Jan/25 ]

rule to be correct for bts node , waiting for indrasan call !!

Comment by Indrasan Yadav [ 13/Jan/25 ]

Dear @Juned,

As discussed yesterday over the phone call, please proceed to apply the given rule where it is applicable:

Applicable Nodes:

NodeB
SRAN
Already Updated:

For BSC and RNC, the site matching sheet has already been updated.
Not Applicable Nodes:

eNodeB
BTS
You can ignore applying the rule for eNodeB and BTS for now. Once we receive any feedback from the customer, we will modify and implement the rule accordingly.

Best regards,
Indrasan

Comment by Juned Ali [ 13/Jan/25 ]

xml and csv shared on mail

Comment by Indrasan Yadav [ 13/Jan/25 ]

Dear @Juned Ali,

Please find below validation remarks:

1- 416 NodeB are not parsing in XML/CSV and related physical also, please find below snippet out of them for your reference.

2- Still site id is not appearing against BSC/RNC as I think you didn’t used updated site matching sheet which I have also attached on mail & same JIRA.

Best regards,
Indrasan

Comment by Juned Ali [ 14/Jan/25 ]

xml and csv Shared !!

Comment by Indrasan Yadav [ 14/Jan/25 ]

Hello @Juned Ali,

Still below nodes are coming on “Auto Site” while site id is available in “site matching sheet” against these nodes (BSC & RNC), please check & fix the same.

Here, I am sharing one example for RNC “JZN1RNC1” whis is available in “site matching sheet”

And please ensure all those nodes which are coming with “Auto Site” should be appear in add info under Actual Site.

Best regards,
Indrasan

Comment by Indrasan Yadav [ 14/Jan/25 ]

Hi @Indrasan Yadav,

1. Site ID COMING As Auto site because it doesn’t meant that if it is present in site matching sheet then it will definitely came although before that we have to check that in info.csv and there it is not present so it coming as Autosite in npsbsc and same has been available in addinfo as actual site. (It was not a issue )

2. Now All Rnc SiteId are Coming in npsRnc !! (fixed)

Point 1 was not an issue and 2 point has been resolved !!

Thank you !!

Comment by Indrasan Yadav [ 14/Jan/25 ]

Hi @Juned,

Please commit the code for same.

Comment by Navneet Kaur [ 15/Jan/25 ]

@Juned: Has the code been committed?

Comment by Juned Ali [ 15/Jan/25 ]

CODE COMMITTED ++

Comment by Indrasan Yadav [ 15/Jan/25 ]

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.

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