Details
-
Type:
Task
-
Status:
Done
(View Workflow)
-
Priority:
Normal
-
Resolution: Unresolved
-
Labels:
-
Customer:Zain KSA 3.X
Description
Please assign an AI DEV resource to implement the following rules for parsing the site ID for Huawei 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 (As described below). 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 Huawei" tab.
• (II) If not found, search in the "2G MMM" tab.
• (III) If still not found, search in the "On Air Summary" tab.
• (IV) If not found, search in the "Dismantled Sites" tab.
B. For Node Type NodeB:
• (I) Search first in the "3G Huawei" tab.
• (II) If not found, search in the "3G MMM" tab.
• (III) If still not found, search in the "On Air Summary" tab.
• (IV) If not found, search in the "Dismantled Sites" tab.
C. For Node Type eNodeB:
• (I) Search first in the "LTE Huawei" tab.
• (II) If not found, search in the "LTE MMM" tab.
• (III) If still not found, search in the "On Air Summary" tab.
• (IV) If not found, search in the "Dismantled Sites" tab.
D. For Node Type SRAN:
• (I) Search first in the "2G Huawei / 3G Huawei / LTE Huawei / 5G Huawei" tabs.
• (II) If not found, search in the "2G MMM / 3G MMM / LTE MMM / 5G MMM" tabs.
• (III) If still not found, search in the "On Air Summary" tab.
• (IV) If not found, search in the "Dismantled Sites" tab.
E. For Node Type BSC: Updated in the "site matching sheet."
F. For Node Type RNC: Updated in the "site matching sheet."
G. For Node Type SRANController: Updated in 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 from the naming convention.
Best regards,
Indrasan
Attachments
Issue Links
- blocks
-
ZKU-94
Huawei RAN_Dumps , XML and NEP data Validation
-
Activity
|
Links Hierarchy |
 Documentation
|
| Transition | Time In Source Status | Execution Times | Last Executer | Last Execution Date | |||||
|---|---|---|---|---|---|---|---|---|---|
|
8d 18h 39m | 1 | Sandya Sharma | 08/Jan/25 4:25 AM | |||||
|
1d 2h 19m | 1 | Indrasan Yadav | 09/Jan/25 6:44 AM |
| Status | In Progress [ 3 ] | Done [ 10000 ] |
commit done.
@Sandya :Please confirm if done
| Time Spent | 1 day, 2 hours, 30 minutes [ 37800 ] | 1 day, 4 hours, 30 minutes [ 45000 ] |
| Worklog Id | 258770 [ 258770 ] |
Dear @Sandya Sharma,
Please commit the code for same.
Best regards,
Indrasan
| Attachment | RE_ Need To Implement Given Rule To Parse Site Id For Huawei RAN __ ZKU-229 __.msg [ 103598 ] |
Dear @Sandya Sharma,
As discussed, all site IDs are now parsing correctly as per the given rule, except for 571 nodes for which the rule is not applicable. These 571 nodes are listed under additional information against 'Actual Site.' Upon reviewing sample cases, I found that these nodes are either not present in the "On Air Sheet V13" or are missing in "INFO."
For reference, I have attached the list of these nodes. The count excludes MBTS nodes, which need to be ignored as per ZKU-233.
Note:
Request to AI-DEV to please take updated code from connector before starting any new task because the issue is appearing in XML which has been already fixed & code committed.
Best regards,
Indrasan
| Assignee | Sandya Sharma [ ssharma ] | Indrasan Yadav [ iyadav ] |
XML shared.
| Time Spent | 2 hours, 30 minutes [ 9000 ] | 1 day, 2 hours, 30 minutes [ 37800 ] |
| Worklog Id | 258735 [ 258735 ] |
| Time Spent | 30 minutes [ 1800 ] | 2 hours, 30 minutes [ 9000 ] |
| Worklog Id | 258716 [ 258716 ] |
| 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) |
| Remaining Estimate | 0 minutes [ 0 ] | |
| Time Spent | 30 minutes [ 1800 ] | |
| Worklog Id | 258706 [ 258706 ] |
to be delivered by 8-1
| Status | To Do [ 10001 ] | In Progress [ 3 ] |
will fix it by today.
-
- Time Spent:
- 2 hours
-
XML validation:
Dear @Sandya Sharma,
As discussed, all site IDs are now parsing correctly as per the given rule, except for 571 nodes for which the rule is not applicable. These 571 nodes are listed under additional information against 'Actual Site.' Upon reviewing sample cases, I found that these nodes are either not present in the "On Air Sheet V13" or are missing in "INFO."
For reference, I have attached the list of these nodes. The count excludes MBTS nodes, which need to be ignored as per ZKU-233.
Note:
Request to AI-DEV to please take updated code from connector before starting any new task because the issue is appearing in XML which has been already fixed & code committed.
Best regards,
Indrasan
| Assignee | Indrasan Yadav [ iyadav ] | Sandya Sharma [ ssharma ] |
Dear @Sandya Sharma,
I hope you are doing well. Please find below the validation remarks:
1. Almost all site IDs are parsing correctly. However, there are below exception where the site ID should be parsed but is not. These have been checked on a sample basis.
objectId site Remarks
BTS KBR2U6132-P3-MMM Auto_Site available in "On Air Sheet V13" & in INFO/Should be parse
BTS RIYC2U6177A-P2 Auto_Site available in "On Air Sheet V13" & in INFO/Should be parse
BTS RIYC2U6177B-P2 Auto_Site available in "On Air Sheet V13" & in INFO/Should be parse
2- In Addinfo, nodes that are not found in the required sheet should still be available with the actual site. However, they are showing inconsistently as per the example below:
3- Around 528 nodes are being displayed with the "Auto_Site" designation in the NPS node list, but only around 66 nodes are available in Addinfo. Kindly check and confirm this discrepancy.
Looking forward to your confirmation and further guidance on these matters.
Best regards,
Indrasan
| Attachment | ZKU-229_XML Validation.xlsx [ 103574 ] |
xml shared.
| Assignee | Sandya Sharma [ ssharma ] | Indrasan Yadav [ iyadav ] |
to be delivered by 2-1
WL is 2 day.
-
- Time Spent:
- 30 minutes
-
Explained rule to @Sandya over the teams call to implement this given rule.
| Attachment | RE_ Need To Implement Given Rule To Parse Site Id For Huawei RAN __ ZKU-229 __.msg [ 103524 ] |
Dear @Bassem Sabbagh,
We currently don’t have any FRS regarding Huawei RAN. However, I am providing an example below for reference on how to parse the site ID as per the rule mentioned in the previous email. This email will also be attached on JIRA.
Consider the following node “MDN2U6996-P1-HRMCST” as an example, which is of the node type eNodeB.
1- Extract the first string from the node name before the special character ‘-’, i.e., MDN2U6996.
2- Next, search for this value (MDN2U6996) in the sheet “On Air Sheets V13” under the tab LTE Huawei.
3- The value corresponding to MDN2U6996 will be found in column ‘B’, which will be the site ID for the node “MDN2U6996-P1-HRMCST”. i.e., MDN6096 in this case.
Best regards,
Indrasan
Example explained in attached mail whose file name is:
"RE_ Need To Implement Given Rule To Parse Site Id For Huawei RAN __ ZKU-229 __"
Assigned to Sandya to define the WL and start working on it
| Assignee | Bassem Sabbagh [ bsabbagh ] | Sandya Sharma [ ssharma ] |
| Assignee | Indrasan Yadav [ iyadav ] | Bassem Sabbagh [ bsabbagh ] |
| Attachment | INFO 3.csv [ 103507 ] | |
| Attachment | On Air Sheets V13.rar [ 103508 ] | |
| Attachment | Sites_Matching 3.xlsx [ 103509 ] |
| Description |
Please assign an AI DEV resource to implement the following rules for parsing the site ID for Huawei 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 (As described below). 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 Huawei" tab. • (II) If not found, search in the "2G MMM" tab. • (III) If still not found, search in the "On Air Summary" tab. • (IV) If not found, search in the "Dismantled Sites" tab. B. For Node Type NodeB: • (I) Search first in the "3G Huawei" tab. • (II) If not found, search in the "3G MMM" tab. • (III) If still not found, search in the "On Air Summary" tab. • (IV) If not found, search in the "Dismantled Sites" tab. C. For Node Type eNodeB: • (I) Search first in the "LTE Huawei" tab. • (II) If not found, search in the "LTE MMM" tab. • (III) If still not found, search in the "On Air Summary" tab. • (IV) If not found, search in the "Dismantled Sites" tab. D. For Node Type SRAN: • (I) Search first in the "2G Huawei / 3G Huawei / LTE Huawei / 5G Huawei" tabs. • (II) If not found, search in the "2G MMM / 3G MMM / LTE MMM / 5G MMM" tabs. • (III) If still not found, search in the "On Air Summary" tab. • (IV) If not found, search in the "Dismantled Sites" tab. E. For Node Type BSC: Updated in the "site matching sheet." F. For Node Type RNC: Updated in the "site matching sheet." G. For Node Type SRANController: Updated in 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 from the naming convention. Best regards, Indrasan |
| 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) |
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.