Dear @Bassem Sabbagh,

As discussed during yesterday’s Teams call with @Ahad Siddiqui, we will parse data from the current Nokia dump as it stands.

As per your suggestion, if required classes are missing (e.g., ZKU-153, which I have already raised) for node parsing rules:

• We will parse data for BTS, BSC, NodeB, RNC, eNodeB, and all remaining nodes will be categorized under SRAN.
• Without the required classes, we cannot definitively determine whether nodes belong to SRAN or other categories, however I have given rule as detailed in the attached FRS.

Could you please assign an AI resource to generate an XML based on the attached FRS for Nokia?

Best regards,
Indrasan

Will be delivered Eod !! and its license Whose Jira is zku-130 (Will fixed remarks)

WL = 1.5 mday (has been started on 17-11 and to be delivered on 18)

a rule has been changed . Indrasan Yadav to update the FRS. the new change will be accommodated by 20-11

Updated FRS shared to Juned & attached here.

will be delivered on 20-11

to be delivered on 22-11-2024 (First half)

XML AND SV SHARED !!

@indrasan : to shared feedback in 2-3 hrs on 24th

Dear @Juned Ali,

Please find below validation remarks for ZKU-156.

1- The sheet “rnc type” is missing in XML.
2- The sheet “nodeshelf” is missing in XML.
3- All “eNodeB” is also parsing in “npsranbs” which should be come in only “npsenodeb”.
4- The value of cabinet index is showing different in cabinet id & cabinet index.

5- Under nodecabinet, in cabinet type in column "C" & "E" only Flexi Multiradio" should be come"

6- Boards details & serial numbers against them are not matching, sharing one example of node “MRBTS-519380”

Dump Snippet:

XML Snippet:

Please check & fix the issue, let me know if more clarification need.

Best regards,
Indrasan

All 6 points are fixed Xml and csv shared !!!

@Indrasan: Kindly share eta

As discussed, it is to completed today

Dear @Juned Ali,

Please find below validation remarks for ZKU-156:

1- In sheet “nodeshelf” for many nodes model is showing blank, please check & fix this.

2- In sheet “nodeshelf” why RU Index is coming in negative value “-7” which is coming in case of BSC only.

3- In “nodeboards” below boards are missing which are available in dump, it should be parse.

Boards-Previous rule Old XML
FBBA
FSMD
BOC_A
FSME
FSM
FWGP
FWGP_FRGP
FWGL
FWGL_FRGL
BMFU-B
BAFU-A
BCNMB-B
BCNDP-A
HDSAM-A
BMPP2_B
FWGM_FRGM
FWGM
BFAN_A
BCN_A
BJC_A
FRGF
BCNMB_B

4- I will raise another JIRA for antenna data parsing (as JIRA is not working currently) which are coming under boards as I explained you verbally. We need to parse antenna data under “radioantenna” as same as in Huawei (You can take support from Sandya)

Br//
Indrasan

Point 1 and point 2 are resolved and for Point 3 please share all the serial number List which are present but not coming in xml . Through this I can resolve point 3 within 2 hours.

Serial Number which are not coming in node board are due to reason that they don't have boards details for the shelf for example we have three shelf and both three shelf have serial number but that out of three shelf only one shelf have board details so its board will be created and other doesn't shelf doesn't have board details so they will be neglected but and their serial Number.

you have to provide me rule for the sane to parse shelf and cabinet serial number in this case.

Please share list of serial Number not coming in csv !!
I hope these issue you shared are all in one go !!

Thanks !!

PLease share eta both Juned and Indrasan

Indrasan to share the ETA for the FRS .

Dear @Ahad Siddiqui,

As discussed, please review the attached FRS where I made modifications related to inventory and antenna data parsing.

Once you have cross-verified the FRS, @Juned Ali will work on generating the full XML for both inventory and antenna.

Br//
Indrasan

Kindly share me the updated FRS , please if you mentioning to parse Antenna when calssValue =INVUNIT and type = singleAntennaDevice or others as mentioned. Please Provide me in clase of board what if classValue =INVUNIT what to parse in board now on basis of type as not mentioned in Frs .

Please share the updated Frs !! so that i can begin work !

Wl = 1 mday , to be started on 28-11 and delivered on 29-11

Hi Juned, Yesterday it was shared with you on mail and also informed you.

However, now same FRS I have attached here for your reference.

Hi Juned, as discussed, in RNC case please take slot number as it is same where slot is given in dump and for others boards in same class "Unit" where slot is not given increment it by 1 after considering existing slot.

Please the new rule in FRS also for future Reference side by side !!

Thanks !!

xml and csv shared after implementing Radio Antenna Rule !!

Thanks !!

Validation remarks has been shared over the mail.

Hi @Juned,

I have attached here updated FRS as we discussed & validation remarks sheet.

Please let me know if any clarification need.

to be delivered by 2-12 by EOD

@Juned : Kindly update

xml and csv shared !!

Hi Juned, as discussed now data are parsing as per given rule (XML File: 2024-12-05-08.21.07_ZainKsa is OK which you shared me over the teams)

(updated final FRS is attached here with today date, which is final FRS)
____________________________________________________________________________________
As discussed, please proceed with the necessary updates.

We need to add an additional attribute, "nodeId", under the CSV nodecabinet in Nokia_RAN XML.
____________________________________________________________________________________

As we encountered the issue of the missing "nodeId" attribute in Huawei during the XML import into NEP, we need to apply the same rule for Nokia as well to ensure consistency and avoid similar issues.

Please proceed with implementing this update.

Thank you for your support.

Hi Juned, as discussed first commit the code for same JIRA.

then you need to add above mentioned attribute in nodecabinet.

Is it complete now ?

xml ands csv shared

@Indrasan : Please share ETA

Hi Juned, based on the shared XML over the teams (2024-12-09-01.20.37_ZainKsa) data is coming ok please proceed to commit the code for same.

Code has been Committed for All the changes till now !!

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.