Details

    • Customer:
      Zain KSA 3.X

      Description

      Click to add description

        Activity

        Indrasan Yadav made changes -
        Time Spent 2 days, 6 hours [ 79200 ] 2 days, 7 hours [ 82800 ]
        Worklog Id 261742 [ 261742 ]
        Indrasan Yadav made changes -
        Status QA In Progress [ 10015 ] Closed [ 6 ]
        Resolution Cancelled [ 10100 ]
        Indrasan Yadav made changes -
        Status Ready for QA [ 10023 ] QA In Progress [ 10015 ]
        Khaled Khalil made changes -
        Status To Be Released [ 10400 ] Ready for QA [ 10023 ]
        Assignee Mustapha Al-Hage [ malhage ] Indrasan Yadav [ iyadav ]
        Khaled Khalil made changes -
        Status Implementation in progress [ 10016 ] To Be Released [ 10400 ]
        Khaled Khalil made changes -
        Status Dev Paused [ 10017 ] Implementation in progress [ 10016 ]
        Indrasan Yadav made changes -
        Assignee Bassem Sabbagh [ bsabbagh ] Mustapha Al-Hage [ malhage ]
        Indrasan Yadav made changes -
        Comment [ 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. 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

        same mail is attaching here for reference.
        ]
        Indrasan Yadav made changes -
        Assignee Indrasan Yadav [ iyadav ] Bassem Sabbagh [ bsabbagh ]
        Mustapha Al-Hage made changes -
        Assignee Mustapha Al-Hage [ malhage ] Indrasan Yadav [ iyadav ]
        Mustapha Al-Hage made changes -
        Status Implementation in progress [ 10016 ] Dev Paused [ 10017 ]
        Mustapha Al-Hage made changes -
        Time Spent 2 days, 2 hours [ 64800 ] 2 days, 6 hours [ 79200 ]
        Worklog Id 261168 [ 261168 ]
        Mustapha Al-Hage made changes -
        Time Spent 1 day, 4 hours [ 43200 ] 2 days, 2 hours [ 64800 ]
        Worklog Id 261167 [ 261167 ]
        Mustapha Al-Hage made changes -
        Status Dev Scheduled [ 10014 ] Implementation in progress [ 10016 ]
        Mustapha Al-Hage made changes -
        Status Open Bug [ 10108 ] Dev Scheduled [ 10014 ]
        Indrasan Yadav made changes -
        Time Spent 1 day [ 28800 ] 1 day, 4 hours [ 43200 ]
        Worklog Id 261123 [ 261123 ]
        Mustapha Al-Hage made changes -
        Baseline Start 2025-02-28 24:00 (set baseline based of initial work logging)
        Baseline End 2025-02-28 24:00 (set baseline based of initial work logging)
        Mustapha Al-Hage made changes -
        Remaining Estimate 0 minutes [ 0 ]
        Time Spent 1 day [ 28800 ]
        Worklog Id 261051 [ 261051 ]
        Khaled Khalil made changes -
        Assignee Khaled Khalil [ kkhalil ] Mustapha Al-Hage [ malhage ]
        Indrasan Yadav made changes -
        Attachment 2025-02-18-01.29.34_ZainKsa.rar [ 103878 ]
        Indrasan Yadav made changes -
        Attachment SRAN Controller XML Snap.jpg [ 103872 ]
        Attachment NEP Error Snap2.jpg [ 103873 ]
        Attachment NEP Error Snap.jpg [ 103874 ]
        Attachment eNodeB NEP Snap.jpg [ 103875 ]
        Attachment XML Snap for eNodeB.jpg [ 103876 ]
        Attachment SRAN Controller NEP Snap.jpg [ 103877 ]
        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-02-28 24:00 (milestone: set planned start date to due date)
        Planned End 2025-02-28 24:00 (milestone: set planned end date to due date)

          People

          • Assignee:
            Indrasan Yadav
            Reporter:
            Indrasan Yadav
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Due:
              Created:
              Updated:
              Resolved:
              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 - 2 days, 7 hours
              2d 7h

                Drag and Drop