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 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 logged work - 18/Mar/25 12:00 AM
        • Time Spent:
          1 day
           

          Requirement review , code change and testing

        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.

        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.

        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.

          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