Now, all sites are correctly parsing as per given rule & confirmed with Ooredoo.

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

commit done, validate the data in SD and confirm.

started on 12-1 and to be delivered today

WL id half day.

Hello Sandya Sharma,

I have corrected the Site ID parsing rules as per the customer requirement and have attached the updated FRS on same JIRA 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 conditions as well.
• Applicable to all node types, though currently observed only in NodeB & 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.

checked and logic is working according to the priority, and the site is coming as defaultsite for the mentioned node in server csv output.

Sandya to check and advise if the priority logic is maintained

All sites related to the MICRO rule are now parsing correctly.

Sandya, please ensure that the priority logic is maintained as follows:

First priority: Site matching

Second priority: Naming convention rule

Currently, the node ID “MRBTS-12999” is added in site matching with a default site, but it is still being parsed with a different site ID. Kindly review and correct this.

code committed.

Now, issue is fixed in 2nd CSV output which was shared for upload on staging-DB, please commit the code for same.

Hi Sandya Sharma attached the list of nodes which should be parse with site but they are coming with "Default site" please check & fix the same, remain nodes are parsing with correct site for which updated rule was shared.

Snippet: Nodes Should Be Parse With Site Instead Of Default Site_30-12-2025

csv output shared with basant for upload in SD.

XML shared.

WIP and to be delivered the first half on 29-12

due to some configuration issue it was not done , will share the xml by today.

WIP and XML to be shared by 26-12

WL is 1 day.

Hello @Sandya Sharma,

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 NodeB and SRAN nodes only.

Example: Attached

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

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

Now sites are parsing correct as per given rule.

XML shared.

WIP ... to be delivered on 3-9

WL is one day.

Dear @Sandya Sharma,

Please find below the XML validation feedback regarding site parsing:

1. The node name is not being parsed for the SRAN node. This must be corrected based on the newly added rule.
2. For NodeB, the given rule regarding the site ID is not applied. If no rule is applicable, the default site should be used.

3. The Site ID is currently parsing correctly for the given two BTS nodes. However, the defined rule should be reviewed and implemented to ensure it works if more than two BTS nodes are found in the future.

4. For Role2G/Role4G nodes, the Site ID is being parsed as the default site. Instead, it should align with the Site ID of the corresponding Role container SRAN nodes.

5. For eNodeB, the name is parsing correctly; however, the Site ID is currently being parsed the same as the name, which is incorrect. The rule to correct this has already been added in the attached FRS and needs to be implemented.

Thank you
Indrasan

XML Shared.

WIP and WL to be added

Sandya to define the WL and to be started on 26-8

Dear @Sandya Sharma,

As discussed, please find the attached FRS where I have described the rule to parse the site id for different node types of Nokia RAN.

Let me confirm if you need any clarification.

Thank you
Indrasan

We need to remove the rule for parsing site Id as we will follow the sheet "Site Matching" (It will be finalizes once full XML generated of 1200 SRAN nodes)

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

Now Site Id are parsign OK but there is an issue in LAT/LONG for Node-B where it is parsing without decimal value in CSV "npssites" and same is available in dump as well. and as per Sandhya it can't be fix so will check & confirm after XML import in NEP.

XML shared.

delivery date is 14-7

to be delivered by 14-7

Hi Sandya, I have validated the site id xml as you shared (2025-07-08-09.53.25_Ooredoo) please find below feedback:

1- Please put decimal value after 2 digit from xml in both Latitude & Longitude.
2- Please generated xml again with using updated "Site data information".

XML shared.

WIP ... to be delivered by 8-7

to be started on 7-7

WL is 1.5 day.

Dear @Sandya Sharma,

As discussed, please find the rule in attached FRS which I have added now to parse site id for sample dump.

Static file related to site matching & info already shared to you.

Note: We will amendment it if needed once get full dump from customer.

Thank you
Indrasan

As checked sample SRAN dump regarding site id naming convention, we can parse site id as lat/long and site id information is available. and for BSC/RNC it is NA in dump.

So, it will be conclude once we will get any clarification from customer end regarding site id naming convention rule as discussed in last meeting on 12-06-2025.