Dear @Hassan Abdine @Hassan Abdine,

Could you please provide guidance on the following case, where the parent RNC is not parsing against a NodeB?
The current rule in the connector is applicable only for RNC, not for MBSC. However, in this scenario, the NodeB is available in the MBSC dump, and as per the dump, the NodeB is connecting to the MBSC.

Details:

MBSC Type: BSC6910GU (Supports both 2G & 3G technologies)

Huawei BSC6910GU is a Base Station Controller (BSC) designed to support both 2G (GSM) and 3G (UMTS) technologies. The BSC6910GU is part of Huawei's network infrastructure equipment and provides integrated management for both GSM and UMTS base stations in a single platform. This means it can handle traffic and management for both 2G and 3G radio access networks, allowing operators to optimize their networks and provide seamless service across multiple generations of technology.
It can support:

• GSM (2G): The traditional 2G mobile technology for voice and basic data services.
• UMTS (3G): A more advanced standard for mobile communication, providing faster data speeds and additional services compared to 2G.

Observations:

1. The NodeB (DRN2M3106-P3) is present in the dump and is shown as connected to the MBSC (BSC6910GU).
2. The rule in the connector currently applies only for RNC parenting, not MBSC.
3. As per the dump and rule logic, the MBSC should appear as the parent node for this NodeB. However, it is not being reflected in the npsnodeb snippet.

Queries:
1. Will NEP accept the NodeB with a parenting BSC (in this case, MBSC)?
2. If not, should we implement a modification to the connector rule to account for MBSC parenting in similar cases?

Supporting Snippets:

1. Dump Snippet for NodeB (DRN2M3106-P3):

2. MBSC Snippet:

3. XML Snippet:

Best regards,
Indrasan

Dear @Sandya Sharma,

I hope this email finds you well.

We need to parse the following three nodes under the SRAN Controller instead of “nodebsc,” as these nodes support both 2G and 3G technologies.

I have updated the node-matching sheet for the BSC6910GU model and shared it with you in a separate email for your reference.

Once this issue is resolved, we expect to successfully parse the missing parent node, as highlighted in the previous email thread.

Dump Snippet:

XML Snippet:

Br//
Indrasan

will be delivered on 30-11

@ Sandya: Please update

WL is one day.

to be delivered on 2-12

XML shared.

Indrasan : Please confirm

Dear @Sandya Sharma,

Currently, the following nodes are being parsed as SRANController nodes, and their types are also present in the XML:

1. YB1MBSCH01
2. KJ1BSCH01
3. DM1MBSCH01

As per our earlier discussion, these SRANController nodes need to be parsed as parent nodes for the respective NodeB entries where they are missing in npsnodeb. For your reference, I have included an example snippet below.

I have also attached a list of NodeB entries where the corresponding SRANController should populate under the 'rnc' column in npsnodeb. Please review the remarks in the attached list for additional details.

XML Snippet:

Example:

NodeB "DRN2M3106-P3" is linked to the SRANController node "DM1MBSCH01", as indicated under the attribute "UCELL" in the XML.

Please let me know if further clarification is required.

Best regards,
Indrasan

will implement this change by today.

need some clarification on this issue with indrsan but he is unavailable, once he come back will do this.

Hi Sandya, we discussed yesterday regarding this and we suggested @Hassan will give best clarification on this.

And, @Hassan has replied on your mail as below:
_________________________________________________________________________________________________

The model is as following:
• Under the SRANController
o Role2GController
o Role3GController
• NodeB -> the parent is the Role3GController of SRAN
• BTS -> the parent is the Role2GController of SRAN

________________________________________
From: Sandya Sharma <Sandya.Sharma@nuiva.com>
Sent: Thursday, December 5, 2024 12:02 PM
To: Hassan Abdine <Hassan.Abdine@nuiva.com>; Hassan Abdine <hassan.abdine@mobinets.com>
Cc: Bassem Sabbagh <bassem.sabbagh@mobinets.com>; Navneet Kaur <Navneet.Kaur@mobinets.com>; Ahad Siddiqui <Ahad.Siddiqui@mobinets.com>; Indrasan Yadav <Indrasan.Yadav@nuiva.com>
Subject: RE: Clarification Needed on NodeB Parenting to MBSC in Huawei || ZKU-166 ||

Hi sir,

As per below email I have parsed these 3 nodes in srancontroller , now my concern is that how I can parse them as parent rnc in npsnodeb because there is element type mismatch error I can parse only rnc type in parent rnc , for srancontroller type is there any other way to parse them . kindly suggest about this.

Dear @Hassan Abdine@Hassan Abdine,

Thank you for your valuable feedback.

Below are the points for your consideration:
1. We agree on these points.
2. For NodeB: The same NodeB is being parsed as standalone, and with the same standalone NodeB ID, it is also available in the SRANController. Should we parse the parent RNC as the standalone NodeB ID or as the SRANController ID?
3. For BTS: Currently, we have all parent BSCs for the available standalone BTS nodes.

Snippet for Reference:

Standalone NodeB: DAM2M3001-P1-VIP-DIA

SRANController Node: DM1MBSCH01

The same NodeB is present under the SRANController Node.

We propose parsing the parent RNC in the “npsnodeb” sheet for the NodeB DAM2M3001-P1-VIP-DIA as SRANController "DM1MBSCH01".

Based on this, should we parse the SRANController as the parent RNC, or should we retain the NodeB itself as the parent?

Your suggestion would be highly appreciated to proceed further.

Best regards,
Indrasan

XML shared.

@INdrasan : PLease share the ETA

From: Hassan Abdine <Hassan.Abdine@nuiva.com>
Sent: 06 December 2024 13:30
To: Indrasan Yadav <Indrasan.Yadav@nuiva.com>; Sandya Sharma <Sandya.Sharma@nuiva.com>; Hassan Abdine <hassan.abdine@mobinets.com>
Cc: Bassem Sabbagh <bassem.sabbagh@mobinets.com>; Navneet Kaur <Navneet.Kaur@mobinets.com>; Ahad Siddiqui <Ahad.Siddiqui@mobinets.com>
Subject: Re: Clarification Needed on NodeB Parenting to MBSC in Huawei || ZKU-166 ||

Hi Indrasan,
• For SRAN Controller, you need to parse:
o Name/id/site,type, etc. for the SRAN Controller as physical node
o Name/id, etc. for Role2G Controller if the SRAN supports 2G
o Name/id, etc. for Role3G Controller if the SRAN supports 3G
• For the NodeB: if the node has the parent SRAN, you should map the parent RNC of NodeB to the Role2G Controller under the SRAN controller.
Thank you,
Hassan

Dear @Sandya Sharma,

As discussed during the Teams call with @Hassan Abdine and @Ahad Siddiqui, please proceed with the following updates:

1. Parse role2g controller and role3g controller similarly to how it is done in normal SRAN cases.
2. In the npsbts and npsnodeb CSV files, the role2g controller and role3g controller should be parsed under the BSC and RNC columns, respectively.
3. Remove the old BSC and RNC columns from the npsbts and npsnodeb CSV files.

Best regards,
Indrasan

From: Sandya Sharma <Sandya.Sharma@nuiva.com>
Sent: 06 December 2024 18:32
To: Indrasan Yadav <Indrasan.Yadav@nuiva.com>; Hassan Abdine <Hassan.Abdine@nuiva.com>; Hassan Abdine <hassan.abdine@mobinets.com>; Ahad Siddiqui <Ahad.Siddiqui@mobinets.com>
Cc: Bassem Sabbagh <bassem.sabbagh@mobinets.com>; Navneet Kaur <Navneet.Kaur@mobinets.com>
Subject: RE: Clarification Needed on NodeB Parenting to MBSC in Huawei || ZKU-166 ||

Hi indrsan,

What will be the value for umtscapability and gsmcapability in case of srancontroller here , I need this to parse the roles as like we use in sran .

From: Indrasan Yadav <Indrasan.Yadav@nuiva.com>
Sent: Saturday, December 7, 2024 1:57 PM
To: Sandya Sharma <Sandya.Sharma@nuiva.com>; Hassan Abdine <Hassan.Abdine@nuiva.com>; Hassan Abdine <hassan.abdine@mobinets.com>; Ahad Siddiqui <Ahad.Siddiqui@mobinets.com>
Cc: Bassem Sabbagh <bassem.sabbagh@mobinets.com>; Navneet Kaur <Navneet.Kaur@mobinets.com>
Subject: RE: Clarification Needed on NodeB Parenting to MBSC in Huawei || ZKU-166 ||

Dear @Sandya Sharma,

As we discussed including me @Ahad Siddiqui and you, we are having difficulty understanding your requirement. It might be better to consult with Driss or Hassan for further clarification.

Best regards,
Indrasan

From: Sandya Sharma <Sandya.Sharma@nuiva.com>
Sent: 07 December 2024 15:16
To: Indrasan Yadav <Indrasan.Yadav@nuiva.com>
Cc: Bassem Sabbagh <bassem.sabbagh@mobinets.com>; Navneet Kaur <Navneet.Kaur@mobinets.com>; Hassan Abdine <Hassan.Abdine@nuiva.com>; Hassan Abdine <hassan.abdine@mobinets.com>; Ahad Siddiqui <Ahad.Siddiqui@mobinets.com>
Subject: RE: Clarification Needed on NodeB Parenting to MBSC in Huawei || ZKU-166 ||

Hi indrsan,

Please check the xml shared on teams for ZKU-166+ZKU-198.

From: Indrasan Yadav <Indrasan.Yadav@nuiva.com>
Sent: Monday, December 9, 2024 2:22 PM
To: Sandya Sharma <Sandya.Sharma@nuiva.com>
Cc: Bassem Sabbagh <bassem.sabbagh@mobinets.com>; Navneet Kaur <Navneet.Kaur@mobinets.com>; Hassan Abdine <Hassan.Abdine@nuiva.com>; Hassan Abdine <hassan.abdine@mobinets.com>; Ahad Siddiqui <Ahad.Siddiqui@mobinets.com>
Subject: RE: Clarification Needed on NodeB Parenting to MBSC in Huawei || ZKU-166 ||

Dear @Sandya Sharma,

The parent missing case has now been fixed. However, the SRANController node should be parsed under SRANController, not under BSC or RNC.

Currently, the following three SRANController nodes are also being parsed in BSC:

BSC Snippet: SRANController Snippet:

Please review and correct this issue.

Best regards,
Indrasan

From: Sandya Sharma <Sandya.Sharma@nuiva.com>
Sent: Monday, December 9, 2024 1:39 PM
To: Hassan Abdine <Hassan.Abdine@nuiva.com>
Cc: Bassem Sabbagh <bassem.sabbagh@mobinets.com>; Navneet Kaur <Navneet.Kaur@mobinets.com>; Hassan Abdine <Hassan.Abdine@nuiva.com>; Hassan Abdine <hassan.abdine@mobinets.com>; Ahad Siddiqui <Ahad.Siddiqui@mobinets.com>; Indrasan Yadav <Indrasan.Yadav@nuiva.com>
Subject: RE: Clarification Needed on NodeB Parenting to MBSC in Huawei || ZKU-166 ||

Hi sir,

Kindly suggest for below , I have parsed role2gcontroller and role3gcontroller now . in role2gcontroller I have added the same node in bsc and for role3gcontroller I have added the same sran controller nodes in rnc , but in below mail indrasan said that these srancontroller nodes will not come in bsc , just for testing purpose I did exclude theses nodes from bsc and generate the xml , after investigate in this xml now role2gcontroller is not coming because the nodes are not present in bsc .

Kindly suggest that if these nodes will not come in bsc then how I can parse the roles.

From: Hassan Abdine <Hassan.Abdine@nuiva.com>
Sent: Monday, December 9, 2024 4:27 PM
To: Sandya Sharma <Sandya.Sharma@nuiva.com>
Cc: Bassem Sabbagh <bassem.sabbagh@mobinets.com>; Navneet Kaur <Navneet.Kaur@mobinets.com>; Hassan Abdine <hassan.abdine@mobinets.com>; Ahad Siddiqui <Ahad.Siddiqui@mobinets.com>; Indrasan Yadav <Indrasan.Yadav@nuiva.com>
Subject: Re: Clarification Needed on NodeB Parenting to MBSC in Huawei || ZKU-166 ||

Hi Sandya,

You already have a list for each type, so you need to add each type in the correct list: mean you will have list for SRAN Controllers, list for Role2G controllers and a list for Role3G controllers ...

Hi Indrasan,

Please check the xml shared with you on teams and revert me ASAP.

The required data, such as "srancontroller" and "srancontroller type," is now coming correctly. However, the same model, BSC6910GU, is appearing under both "srancontroller type" and "BSC type." I will confirm once the XML (2024-12-09-09.33.09_ZainKsa) import is complete and verify the data.

SRANController nodes are not showing correctly in NEP under SRANController report, for which JIRA ZKU-209 has been raised.

The issue related to ZKU-166 has been fixed 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.

________________________________________________

Sandya, please commit the code for same ZKU-166.

commit done.

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.