[ZKU-229] Need To Implement Given Rule To Parse Site Id For Huawei RAN Created: 30/Dec/24 Updated: 09/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 day, 4 hours, 30 minutes | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Customer: |
Zain KSA 3.X
|
||||||||
| Planned Start: | |||||||||
| Planned End: | |||||||||
| Actual Start: | |||||||||
| Date of Baselining: | |||||||||
| 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: The steps for each node type are as follows: A. For Node Type BTS: D. For Node Type SRAN: E. For Node Type BSC: Updated in the "site matching sheet." Priority - 2: Priority - 3: Best regards, |
| Comments |
| Comment by Bassem Sabbagh [ 31/Dec/24 ] |
|
Assigned to Sandya to define the WL and start working on it |
| Comment by Indrasan Yadav [ 31/Dec/24 ] |
|
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. Best regards, Example explained in attached mail whose file name is: |
| Comment by Sandya Sharma [ 02/Jan/25 ] |
|
WL is 2 day. |
| Comment by Bassem Sabbagh [ 02/Jan/25 ] |
|
to be delivered by 2-1 |
| Comment by Sandya Sharma [ 03/Jan/25 ] |
|
xml shared. |
| Comment by Indrasan Yadav [ 07/Jan/25 ] |
|
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 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, |
| Comment by Sandya Sharma [ 08/Jan/25 ] |
|
will fix it by today. |
| Comment by Bassem Sabbagh [ 08/Jan/25 ] |
|
to be delivered by 8-1 |
| Comment by Sandya Sharma [ 09/Jan/25 ] |
|
XML shared. |
| Comment by Indrasan Yadav [ 09/Jan/25 ] |
|
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, |
| Comment by Indrasan Yadav [ 09/Jan/25 ] |
|
Dear @Sandya Sharma, Please commit the code for same. Best regards, |
| Comment by Navneet Kaur [ 09/Jan/25 ] |
|
@Sandya :Please confirm if done |
| Comment by Sandya Sharma [ 09/Jan/25 ] |
|
commit done. |
| Comment by Indrasan Yadav [ 09/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. |