Checked sample dump eNodeB for site id parsing rule and it is founded in dump but will conclude once other sample damp received from customer and also waiting for any clarification regarding site data information from customer end as discussed in last meeting on 12-06-2025.

As discussed with Bassem Sabbagh we need to parse site id based on sample and parse the same in NEP.

Once customer will share full dump & any information regarding site data then we will amendment the same accordingly.

Now, site id is parsing correctly in XML based on given data in static sheet SM, and imported the same XML in NEP and also site id is coming correctly there.

Checked the site naming convention rule which is shared by customer on 16-07-2025 over the sharepoint.

Which need to be raised to Ooredoo for Huawei_RAN.

1- There are 22 site Ids which are available in file "CM_RAN_july" but has incorrect/missing Lat/Long.
2- There are 129 nodes whose site id are not available in file "CM_RAN_july"

Final sheet is attached which need to be raised to Ooredoo for missing site id & Lat-Long.

File name: Require Site ID & Lat-Long_Huawei_19-08-2025

Hi Jharna Thakur,

Please find the attached FRS: (OT_Huawei_RAN All Nodes_Physical_20-08-2025), which details the rules to parse the Site ID for all node types for Huawei RAN.

I’ve also shared the same via email for your reference.

Please implement the parsing logic as specified in the FRS.

Share back the XML along with the CSV output generated from the parsed Site IDs.

If you have any queries or need clarifications, let me know.

WIP with OT-17 and both might be delivered by 22-8

delayed and to be delivered on 25-8 the first half

XML to be shared shortly on 25-8

xml shared

Site Ids are parsing based on naming convention rule in given xml. (2025-08-25-02.33.48_Ooredoo)

Dear Jharna Thakur,

As discussed please parse the site id for BSC/RNC as same node name of them. and share the revised XML with using of updated sheet "Site Data Information".

WIP and to be delivered by today EOD

will be delivered by today EOD

xml shared

Now, sites are parsing for BSC/RNC as per given rule.

Hello @Jharna Thakur,

Please review and implement the following updated rule to parse the Site ID, as per the customer requirement for micro site.

Rule:
If the value extracted from the node name (before or after the special characters _ or -) has 2 as the 4th character, and the next three digits after 2 are greater than 600, then subtract 600 from those last three digits.

This rule is applicable to all node types; however, it is currently observed in SRAN nodes only.

Example: Attached

• Node Name: SFX2612
• Rule Applied: After the 4th character 2, the next three digits are 611 (>600), so subtract 600 → 012
• Derived Site ID: SFX2012

Please let me know once this is implemented or if any clarification is required.

WIP and XML to be shared on 26-12

xml shared

XML validated locally but CSV output was not uploaded due to latest AI patch deployment pending, now it is deployed and CSV output is shared by Jharna to Basant for upload it on staging-DB. Once upload done I will check & validate it on staging-DB.

Jharna Thakur please commit the code for same.

code committed

Dear @Jharna Thakur,

Please find the validation feedback below based on staging-DB and csv output generated on server & uploaded by Basant:

Importer ID: "20251231015405_2025-12-31-01.54.05"

The site ID is now parsing correctly based on the defined micro site rule. Kindly review and confirm the following priority order:

1. First priority: Site matching
2. Second priority: Naming convention rule

Please confirm if this priority logic is correctly implemented.

As I can see, for the below nodes that fall under “site matching”, the parsing is still being done based on the naming convention rule, which should not be the case:

(I) BSC HW TB
(II) BSCSOS51 TEST BED
(III) RNCTBMGH

Kindly review and correct this so that these nodes follow the site matching logic as intended.

WIP and WL to be be defined by Jharna

Hi Jharna Thakur,

I have corrected the Site ID parsing rules as per the customer requirement and have attached the updated FRS for your reference.

Updated Site ID Parsing Rules

1- If the value extracted from the node name (before or after the special characters _ or -) has the 4th character as 2, and the next three digits are greater than or equal to 600, then subtract 600 from the last three digits.
(This logic is already implemented for values greater than 600; please extend it to cover the equal to 600 condition as well) (Applicable to all node types, though currently observed only in SRAN)

2- If the value extracted from the node name (before or after the special characters _ or -) has the 4th character as 2, and the next three digits are greater than or equal to 500, then subtract 50 from the last three digits.
(Applicable only to NodeB)

3- In all cases, if the value extracted after the special character has the 4th digit as 2 and the next three digits are less than 600, the extracted value itself should be considered as the Site ID (This is finding in SRAN: Example-MBTS-Ste_SOPAT_MAH2010)

csv output shared to upload it in db. Indrasan Yadav sir can check in db after upload

Hi Jharna,

Now the sites are parsing correctly as per the given rule.
Please go ahead and commit the code for the same.

code committed

Latest patch deployed on server, to be check data on staging-DB.

Now, all site ids are correctly parsing as per given rule & confirmed by Ooredoo.