Details

    • Customer:
      Zain KSA 3.X

      Description

      Dear @Bassem Sabbagh,

      I would like to request the assignment of an AI development resource to implement the updated rules for parsing licenses for Huawei, as detailed below.

      Current Scenario: Currently, all LIC IDs are being parsed in XML according to the provided dump, as described in my previous email in LS-241 (Mail is attaching for reference). This includes instances where the same LIC ID appears multiple times for a node, but with different attribute values such as allocation, configuration, usage, and expiration. The NEP team has indicated that not all licenses are being imported due to conditions related to node ID, LIC ID, and LIC details.

      Updated Case: To ensure all licenses can be imported into NEP, we need to add a condition to make each LIC ID unique.

      SRAN Controller Case:
      1. If the same LIC ID is available for the same node with corresponding LIC details, we should append “_2G” for technology 2G and “_3G” for technology 3G to the LIC ID.

      Example:

      In the SRAN Controller node DM1MBSCH01, the same LIC ID is currently parsed with the same license details in the XML, but for different technologies. We need to modify the LIC ID as follows:
      • LQW1CS01_2G
      • LQW1CS01_3G

      Current XML:

      In NEP, only the 3G license is being imported, while the 2G license is ignored.

      NEP Import:

      Other Node Case:
      If the duplicate LIC ID is available for the same node with identical LIC details, we need to add an underscore and a starting value of “1” after the LIC ID value, incrementing by 1 for subsequent instances of the same LIC ID within the same node and license details. We need to modify the LIC ID as follows:
      1. LT1S0000RB00_1
      2. LT1S0000RB00_2
      Example: Below are the LIC Id of one node type eNodeB (RIYA2U6760B-P3) present in the XML but not imported into NEP, with no relevant errors in the error report.
      Current XML:

      In this case, there are two licenses with the same LIC ID and LIC details for one node, yet only one is being imported into NEP.

      NEP Import:

      Note: This rule is needed to add in the existing rule there should no changes in existing data parsing. And it will apply for those cases where duplicate LIC ID/Licences details available for a same node ID.

      Thank you for your attention to this matter. I look forward to your prompt response.

      Best regards,
      Indrasan

        Activity

        Indrasan Yadav logged work - 05/Mar/25 12:00 AM
        • Time Spent:
          1 hour, 30 minutes
           

          Make a rule to parse LIC ID with unique & same is updated in FRS and FRS uploaded on sharepoint. then created this JIRA to @Bassem to fix the same. this JIRA is related to LS-241.

        Indrasan Yadav made changes -
        Field Original Value New Value
        Gantt Options Milestone (set to milestone: having a due date but zero effort)
        Planned Start 2025-03-10 24:00 (milestone: set planned start date to due date)
        Planned End 2025-03-10 24:00 (milestone: set planned end date to due date)
        Indrasan Yadav made changes -
        Indrasan Yadav made changes -
        Description Dear @Bassem Sabbagh,

        I would like to request the assignment of an AI development resource to implement the updated rules for parsing licenses for Huawei, as detailed below.

        Current Scenario: Currently, all LIC IDs are being parsed in XML according to the provided dump, as described in my previous email in LS-241 (Mail is attaching for reference). This includes instances where the same LIC ID appears multiple times for a node, but with different attribute values such as allocation, configuration, usage, and expiration. The NEP team has indicated that not all licenses are being imported due to conditions related to node ID, LIC ID, and LIC details.

        Updated Case: To ensure all licenses can be imported into NEP, we need to add a condition to make each LIC ID unique.

        SRAN Controller Case:
        1. If the same LIC ID is available for the same node with corresponding LIC details, we should append “_2G” for technology 2G and “_3G” for technology 3G to the LIC ID.

        Example:

        In the SRAN Controller node DM1MBSCH01, the same LIC ID is currently parsed with the same license details in the XML, but for different technologies. We need to modify the LIC ID as follows:
        • LQW1CS01_2G
        • LQW1CS01_3G

        Current XML:

         

        In NEP, only the 3G license is being imported, while the 2G license is ignored.

        NEP Import:

         

        Other Node Case:
        If the duplicate LIC ID is available for the same node with identical LIC details, we need to add an underscore and a starting value of “1” after the LIC ID value, incrementing by 1 for subsequent instances of the same LIC ID within the same node and license details. We need to modify the LIC ID as follows:
        1. LT1S0000RB00_1
        2. LT1S0000RB00_2
        Example: Below are the LIC Id of one node type eNodeB (RIYA2U6760B-P3) present in the XML but not imported into NEP, with no relevant errors in the error report.
        Current XML:

        In this case, there are two licenses with the same LIC ID and LIC details for one node, yet only one is being imported into NEP.

         

        NEP Import:


         


        Note: This rule is needed to add in the existing rule there should no changes in existing data parsing. And it will apply for those cases where duplicate LIC ID/Licences details available for a same node ID.


        Thank you for your attention to this matter. I look forward to your prompt response.


        Best regards,
        Indrasan

        Indrasan Yadav made changes -
        Assignee Indrasan Yadav [ iyadav ] Bassem Sabbagh [ bsabbagh ]
        Indrasan Yadav made changes -
        Remaining Estimate 0 minutes [ 0 ]
        Time Spent 1 hour, 30 minutes [ 5400 ]
        Worklog Id 261743 [ 261743 ]
        Indrasan Yadav made changes -
        Baseline Start 2025-03-10 24:00 (set baseline based of initial work logging)
        Baseline End 2025-03-10 24:00 (set baseline based of initial work logging)
        Bassem Sabbagh made changes -
        Assignee Bassem Sabbagh [ bsabbagh ] Jharna Thakur [ jthakur ]
        Hide
        Bassem Sabbagh added a comment -

        Assigned to Jharna to define the WL

        Show
        Bassem Sabbagh added a comment - Assigned to Jharna to define the WL
        Hide
        Jharna Thakur added a comment - - edited

        wl-1.5 days

        Show
        Jharna Thakur added a comment - - edited wl-1.5 days
        Hide
        Bassem Sabbagh added a comment -

        to be started on 17-3-25

        Show
        Bassem Sabbagh added a comment - to be started on 17-3-25
        Indrasan Yadav logged work - 17/Mar/25 12:00 AM
        • Time Spent:
          1 hour
           

          Share the inventory & license dump to @Jharna.

        Jharna Thakur logged work - 17/Mar/25 12:00 AM
        • Time Spent:
          1 day
           

          Requirement review , code change and testing

        Jharna Thakur made changes -
        Status To Do [ 10001 ] In Progress [ 3 ]
        Hide
        Jharna Thakur added a comment -

        Kindly share the dumps related to it

        Show
        Jharna Thakur added a comment - Kindly share the dumps related to it
        Indrasan Yadav made changes -
        Attachment license 1.rar [ 104900 ]
        Hide
        Indrasan Yadav added a comment -

        Require dump is attached here for your reference.

        Show
        Indrasan Yadav added a comment - Require dump is attached here for your reference.
        Hide
        Jharna Thakur added a comment - - edited

        Kindly share the remaining dump data as well, as the provided dumps are not generating any licenses.

        Show
        Jharna Thakur added a comment - - edited Kindly share the remaining dump data as well, as the provided dumps are not generating any licenses.
        Jharna Thakur logged work - 18/Mar/25 12:00 AM
        • Time Spent:
          1 day
           

          Requirement review , code change and testing

        Hide
        Indrasan Yadav added a comment -

        Hi Jharna, require dump has been shared to you now.

        Show
        Indrasan Yadav added a comment - Hi Jharna, require dump has been shared to you now.
        Hide
        Bassem Sabbagh added a comment -

        to be delivered by latest 19-3 the first half

        Show
        Bassem Sabbagh added a comment - to be delivered by latest 19-3 the first half
        Hide
        Jharna Thakur added a comment -

        Xml has been shared

        Show
        Jharna Thakur added a comment - Xml has been shared
        Indrasan Yadav logged work - 19/Mar/25 12:00 AM
        • Time Spent:
          3 hours
           

          XML validation for same and requested to code commit then requested to @Khaleed to release AI patch for same.

        Bassem Sabbagh made changes -
        Assignee Jharna Thakur [ jthakur ] Indrasan Yadav [ iyadav ]
        Hide
        Indrasan Yadav added a comment -

        Hi Jharna, please commit the code.

        Show
        Indrasan Yadav added a comment - Hi Jharna, please commit the code.
        Indrasan Yadav made changes -
        Assignee Indrasan Yadav [ iyadav ] Jharna Thakur [ jthakur ]
        Hide
        Jharna Thakur added a comment -

        Code has been committed

        Show
        Jharna Thakur added a comment - Code has been committed
        Jharna Thakur made changes -
        Assignee Jharna Thakur [ jthakur ] Indrasan Yadav [ iyadav ]
        Hide
        Indrasan Yadav added a comment -

        Dear @Khaled Khalil,

        Could you please generate an AI patch as code commit has been done by @Jharna Thakur for the same.

        Thank you

        Show
        Indrasan Yadav added a comment - Dear @Khaled Khalil, Could you please generate an AI patch as code commit has been done by @Jharna Thakur for the same. Thank you
        Indrasan Yadav made changes -
        Time Spent 1 hour, 30 minutes [ 5400 ] 2 hours, 30 minutes [ 9000 ]
        Worklog Id 262953 [ 262953 ]
        Indrasan Yadav made changes -
        Time Spent 2 hours, 30 minutes [ 9000 ] 5 hours, 30 minutes [ 19800 ]
        Worklog Id 262957 [ 262957 ]
        Indrasan Yadav logged work - 20/Mar/25 12:00 AM
        • Time Spent:
          1 hour
           

          Taken the follows up for release patch ad after received requested to @Integration to deploy it on production.

        Hide
        Indrasan Yadav added a comment -

        From: Khaled Khalil <Khaled.Khalil@nuiva.com>
        Sent: 20 March 2025 14:26
        To: Bassem Sabbagh <bassem.sabbagh@mobinets.com>; Indrasan Yadav <Indrasan.Yadav@nuiva.com>; Jharna Thakur <Jharna.thakur@nuiva.com>
        Cc: Ahad Siddiqui <Ahad.Siddiqui@mobinets.com>
        Subject: Re: Need To Modify The Rule To Parse LIC ID_Huawei || ZKU-264 ||

        Dear Bassem, I already created a patch yesterday as below, do you need another new one?

        Build 3.7.2.24 (19-Mar-2025 4:03:59 PM)

        Show
        Indrasan Yadav added a comment - From: Khaled Khalil <Khaled.Khalil@nuiva.com> Sent: 20 March 2025 14:26 To: Bassem Sabbagh <bassem.sabbagh@mobinets.com>; Indrasan Yadav <Indrasan.Yadav@nuiva.com>; Jharna Thakur <Jharna.thakur@nuiva.com> Cc: Ahad Siddiqui <Ahad.Siddiqui@mobinets.com> Subject: Re: Need To Modify The Rule To Parse LIC ID_Huawei || ZKU-264 || Dear Bassem, I already created a patch yesterday as below, do you need another new one? Build 3.7.2.24 (19-Mar-2025 4:03:59 PM)
        Hide
        Indrasan Yadav added a comment -

        From: Indrasan Yadav <Indrasan.Yadav@nuiva.com>
        Sent: 20 March 2025 16:23
        To: ABHINAV PARASHAR <ABHINAV.PARASHAR@mobinets.com>
        Cc: Ahad Siddiqui <Ahad.Siddiqui@mobinets.com>; Khaled Khalil <Khaled.Khalil@nuiva.com>; Bassem Sabbagh <bassem.sabbagh@mobinets.com>; Sanju Yadav <Sanju.Yadav@mobinets.com>
        Subject: RE: Need To Modify The Rule To Parse LIC ID_Huawei || ZKU-264 ||

        Dear @ABHINAV PARASHAR,

        Please deploy mentioned patch on production and after successfully deploy it also generate full xml on same platform.

        Build 3.7.2.24 (19-Mar-2025 4:03:59 PM)

        Thank you
        Indrasan

        Show
        Indrasan Yadav added a comment - From: Indrasan Yadav <Indrasan.Yadav@nuiva.com> Sent: 20 March 2025 16:23 To: ABHINAV PARASHAR <ABHINAV.PARASHAR@mobinets.com> Cc: Ahad Siddiqui <Ahad.Siddiqui@mobinets.com>; Khaled Khalil <Khaled.Khalil@nuiva.com>; Bassem Sabbagh <bassem.sabbagh@mobinets.com>; Sanju Yadav <Sanju.Yadav@mobinets.com> Subject: RE: Need To Modify The Rule To Parse LIC ID_Huawei || ZKU-264 || Dear @ABHINAV PARASHAR, Please deploy mentioned patch on production and after successfully deploy it also generate full xml on same platform. Build 3.7.2.24 (19-Mar-2025 4:03:59 PM) Thank you Indrasan
        Hide
        Indrasan Yadav added a comment -

        Dear Indrasan,

        Build 3.7.2.24 Patch deployed and 2025-03-20-01.31.54_ZainKsa.xml full XML file generated after deployment.

        NETWORKS TRANSFORMED

        Abhinav Parashar| Sr. System Engineer
        Mob: +91 9897473040
        1102-1103, Tower C, Unitech Cyber Park, Gurgaon
        abhinav.parashar@mobinets.com | www.mobinets.com

        Show
        Indrasan Yadav added a comment - Dear Indrasan, Build 3.7.2.24 Patch deployed and 2025-03-20-01.31.54_ZainKsa.xml full XML file generated after deployment. NETWORKS TRANSFORMED Abhinav Parashar| Sr. System Engineer Mob: +91 9897473040 1102-1103, Tower C, Unitech Cyber Park, Gurgaon abhinav.parashar@mobinets.com | www.mobinets.com
        Hide
        Indrasan Yadav added a comment -

        Require data is seems parsing correctly in XML on production also.

        I need to import full XML (2025-03-20-01.31.54_ZainKsa.xml) on production by today EOD because full xml import is not happening automatically since last few days.

        Show
        Indrasan Yadav added a comment - Require data is seems parsing correctly in XML on production also. I need to import full XML (2025-03-20-01.31.54_ZainKsa.xml) on production by today EOD because full xml import is not happening automatically since last few days.
        Indrasan Yadav logged work - 25/Mar/25 12:00 AM
        • Time Spent:
          2 hours
           

          Validate the data on production and it seems that now all related LIC data are parsing correctly.

        Hide
        Indrasan Yadav added a comment -

        Above mentioned XML imported manually on production and now all data related to LIC are parsing in NEP correctly.

        Show
        Indrasan Yadav added a comment - Above mentioned XML imported manually on production and now all data related to LIC are parsing in NEP correctly.
        Indrasan Yadav made changes -
        Status In Progress [ 3 ] To Do [ 10001 ]
        Indrasan Yadav made changes -
        Status To Do [ 10001 ] Done [ 10000 ]
        Indrasan Yadav made changes -
        Time Spent 5 hours, 30 minutes [ 19800 ] 7 hours, 30 minutes [ 27000 ]
        Worklog Id 263322 [ 263322 ]
        Indrasan Yadav made changes -
        Time Spent 7 hours, 30 minutes [ 27000 ] 1 day, 30 minutes [ 30600 ]
        Worklog Id 263328 [ 263328 ]
        Jharna Thakur made changes -
        Time Spent 1 day, 30 minutes [ 30600 ] 2 days, 30 minutes [ 59400 ]
        Worklog Id 264542 [ 264542 ]
        Jharna Thakur made changes -
        Time Spent 2 days, 30 minutes [ 59400 ] 3 days, 30 minutes [ 88200 ]
        Worklog Id 264543 [ 264543 ]
        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        To Do To Do In Progress In Progress
        11d 20h 23m 1 Jharna Thakur 17/Mar/25 5:09 AM
        In Progress In Progress To Do To Do
        8d 3h 4m 1 Indrasan Yadav 25/Mar/25 8:14 AM
        To Do To Do Done Done
        5s 1 Indrasan Yadav 25/Mar/25 8:14 AM
        Subversion JIRA

        Links Hierarchy

         Documentation

        Invalid license: EXPIRED

          People

          • Assignee:
            Indrasan Yadav
            Reporter:
            Indrasan Yadav
          • Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Due:
              Created:
              Updated:
              Planned Start:
              Planned End:
              Actual Start:
              Date of Baselining:

              Time Tracking

              Estimated:
              Original Estimate - Not Specified
              Not Specified
              Remaining:
              Remaining Estimate - 0 minutes
              0m
              Logged:
              Time Spent - 3 days, 30 minutes
              3d 30m

                Drag and Drop