Details
-
Type:
Task
-
Status:
Done
(View Workflow)
-
Priority:
Normal
-
Resolution: Unresolved
-
Labels:
-
Customer:Zain KSA 3.X
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
Attachments
Issue Links
- blocks
-
ZKU-95
Nokia RAN_Dumps , XML and NEP data Validation_Sub Parent
-
Activity
| Field | Original Value | New Value |
|---|---|---|
| Gantt Options | Milestone (set to milestone: having a due date but zero effort) | |
| Planned Start | 2025-01-06 24:00 (milestone: set planned start date to due date) | |
| Planned End | 2025-01-06 24:00 (milestone: set planned end date to due date) |
| 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 |
| Attachment | INFO 3.csv [ 103510 ] | |
| Attachment | On Air Sheets V13.rar [ 103511 ] | |
| Attachment | Sites_Matching 3.xlsx [ 103512 ] |
| Assignee | Indrasan Yadav [ iyadav ] | Bassem Sabbagh [ bsabbagh ] |
| Assignee | Bassem Sabbagh [ bsabbagh ] | Juned Ali [ jali ] |
| Attachment | FRS_Physical_NSN_ZAIN-KSA.docx [ 103523 ] |
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
WL = 1.5 mdays to be started on 7-1 and delivered by 8-1
it is on hold till Sandya commit the code
code committed and to be started on 9-1
| Remaining Estimate | 0 minutes [ 0 ] | |
| Time Spent | 5 hours [ 18000 ] | |
| Worklog Id | 258726 [ 258726 ] |
| Baseline Start | 2025-01-06 24:00 (set baseline based of initial work logging) | |
| Baseline End | 2025-01-06 24:00 (set baseline based of initial work logging) |
| Time Spent | 5 hours [ 18000 ] | 1 day, 3 hours [ 39600 ] |
| Worklog Id | 258727 [ 258727 ] |
| Time Spent | 1 day, 3 hours [ 39600 ] | 2 days, 3 hours [ 68400 ] |
| Worklog Id | 258854 [ 258854 ] |
to be delivered by 10-1
rule to be correct for bts node , waiting for indrasan call !!
| Assignee | Juned Ali [ jali ] | Indrasan Yadav [ iyadav ] |
-
- Time Spent:
- 2 hours
-
XML Validation, where i found that still site id is not appearing for BSC & RNC. & 416 NodeBs are not parsing due to this related physical data also not parsing.
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
| Assignee | Indrasan Yadav [ iyadav ] | Juned Ali [ jali ] |
| Assignee | Juned Ali [ jali ] | Indrasan Yadav [ iyadav ] |
| Time Spent | 2 days, 3 hours [ 68400 ] | 2 days, 4 hours [ 72000 ] |
| Worklog Id | 258891 [ 258891 ] |
| Time Spent | 2 days, 4 hours [ 72000 ] | 2 days, 4 hours, 30 minutes [ 73800 ] |
| Worklog Id | 258891 [ 258891 ] |
| Time Spent | 2 days, 4 hours, 30 minutes [ 73800 ] | 2 days, 5 hours [ 75600 ] |
| Worklog Id | 258891 [ 258891 ] |
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
| Assignee | Indrasan Yadav [ iyadav ] | Juned Ali [ jali ] |
-
- Time Spent:
- 2 hours
-
Validate the XML for site id shared by @Juned, there is still issue with RNC shared feedback to him.
He again shared me XML and I validated the same and now issue has been fixed.
| Assignee | Juned Ali [ jali ] | Indrasan Yadav [ iyadav ] |
| Time Spent | 2 days, 5 hours [ 75600 ] | 3 days, 5 hours [ 104400 ] |
| Worklog Id | 258942 [ 258942 ] |
| Time Spent | 3 days, 5 hours [ 104400 ] | 4 days [ 115200 ] |
| Worklog Id | 258943 [ 258943 ] |
| Time Spent | 4 days [ 115200 ] | 4 days, 2 hours [ 122400 ] |
| Worklog Id | 258956 [ 258956 ] |
| Status | To Do [ 10001 ] | In Progress [ 3 ] |
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
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 !!
Hi @Juned,
Please commit the code for same.
| Assignee | Indrasan Yadav [ iyadav ] | Juned Ali [ jali ] |
@Juned: Has the code been committed?
| Assignee | Juned Ali [ jali ] | Indrasan Yadav [ iyadav ] |
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.
| Status | In Progress [ 3 ] | Done [ 10000 ] |
| Time Spent | 4 days, 2 hours [ 122400 ] | 1 week, 1 hour [ 147600 ] |
| Worklog Id | 259597 [ 259597 ] |
| Time Spent | 1 week, 1 hour [ 147600 ] | 1 week, 7 hours [ 169200 ] |
| Worklog Id | 259598 [ 259598 ] |
| Transition | Time In Source Status | Execution Times | Last Executer | Last Execution Date | |||||
|---|---|---|---|---|---|---|---|---|---|
|
15d 2h 56m | 1 | Indrasan Yadav | 14/Jan/25 1:11 PM | |||||
|
1d 54m | 1 | Indrasan Yadav | 15/Jan/25 2:05 PM |
|
Links Hierarchy |
 Documentation
|
Assigned to Juned to define the Wl