Details
-
Type:
Bug
-
Status:
Closed
(View Workflow)
-
Priority:
Normal
-
Resolution: Cancelled
-
Component/s: None
-
Labels:
-
Customer:Zain KSA 3.X
Description
Click to add description
Attachments
Activity
|
Links Hierarchy |
 Documentation
|
| Transition | Time In Source Status | Execution Times | Last Executer | Last Execution Date | |||||
|---|---|---|---|---|---|---|---|---|---|
|
4d 37m | 1 | Mustapha Al-Hage | 25/Feb/25 6:29 AM | |||||
|
4s | 1 | Mustapha Al-Hage | 25/Feb/25 6:29 AM | |||||
|
23h 15m | 1 | Mustapha Al-Hage | 26/Feb/25 5:44 AM | |||||
|
7d 3h 20m | 1 | Khaled Khalil | 05/Mar/25 9:05 AM | |||||
|
14s | 1 | Khaled Khalil | 05/Mar/25 9:05 AM | |||||
|
5s | 1 | Khaled Khalil | 05/Mar/25 9:05 AM | |||||
|
5m 3s | 1 | Indrasan Yadav | 05/Mar/25 9:10 AM | |||||
|
6m 5s | 1 | Indrasan Yadav | 05/Mar/25 9:16 AM |
| Time Spent | 2 days, 6 hours [ 79200 ] | 2 days, 7 hours [ 82800 ] |
| Worklog Id | 261742 [ 261742 ] |
| Status | QA In Progress [ 10015 ] | Closed [ 6 ] |
| Resolution | Cancelled [ 10100 ] |
| Status | Ready for QA [ 10023 ] | QA In Progress [ 10015 ] |
| Status | To Be Released [ 10400 ] | Ready for QA [ 10023 ] |
| Assignee | Mustapha Al-Hage [ malhage ] | Indrasan Yadav [ iyadav ] |
| Status | Implementation in progress [ 10016 ] | To Be Released [ 10400 ] |
| Status | Dev Paused [ 10017 ] | Implementation in progress [ 10016 ] |
| Assignee | Bassem Sabbagh [ bsabbagh ] | Mustapha Al-Hage [ malhage ] |
Dear @Mustapha Al-Hage,
Thank you for your clarification.
I noticed that the JIRA status is currently paused. Could you please resume it so we can proceed with closing this JIRA?
Additionally, I will create a separate JIRA to update the rule in FRS to make the LIC ID unique and ensure it will import in NEP accordingly.
Thank you
Indrasan
Show
Indrasan Yadav
added a comment - Dear @Mustapha Al-Hage,
Thank you for your clarification.
I noticed that the JIRA status is currently paused. Could you please resume it so we can proceed with closing this JIRA?
Additionally, I will create a separate JIRA to update the rule in FRS to make the LIC ID unique and ensure it will import in NEP accordingly.
Thank you
Indrasan
| 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. ] |
| Assignee | Indrasan Yadav [ iyadav ] | Bassem Sabbagh [ bsabbagh ] |
| Attachment | Need To Implement Updated Rule In LIC Parsing In XML_Huawei __ LS-241 __.msg [ 104207 ] |
-
- Time Spent:
- 1 hour
-
Worked on same during sanity check on production
| Assignee | Mustapha Al-Hage [ malhage ] | Indrasan Yadav [ iyadav ] |
| Status | Implementation in progress [ 10016 ] | Dev Paused [ 10017 ] |
Dear @Indrasan Yadav,
As per the discussion with @Hassan Abdine :
In NE License Management, the License Identifier Key is used to ensure license uniqueness. This key is a combination of the following attributes:
Object ID + License ID + License Details
Example 1:
The unique identifier key is: "RIYA2U6760B-P3_LT1S0000RB00_RESOURCE BLOCK(FDD)" for both licenses.
Example 2:
The unique identifier key is: "DM1MBSCH01_LQW1CS01_Voice Erlang-Erlang" for both licenses.
Therefore, the uniqueness of the licenses will be lost, making it difficult to update data or detect duplicates.
Regards,
Mustapha Al Hage
Show
Mustapha Al-Hage
added a comment - Dear @Indrasan Yadav,
As per the discussion with @Hassan Abdine :
In NE License Management, the License Identifier Key is used to ensure license uniqueness. This key is a combination of the following attributes:
Object ID + License ID + License Details
Example 1:
The unique identifier key is: "RIYA2U6760B-P3_LT1S0000RB00_RESOURCE BLOCK(FDD)" for both licenses.
Example 2:
The unique identifier key is: "DM1MBSCH01_LQW1CS01_Voice Erlang-Erlang" for both licenses.
Therefore, the uniqueness of the licenses will be lost, making it difficult to update data or detect duplicates.
Regards,
Mustapha Al Hage
| Time Spent | 2 days, 2 hours [ 64800 ] | 2 days, 6 hours [ 79200 ] |
| Worklog Id | 261168 [ 261168 ] |
| Time Spent | 1 day, 4 hours [ 43200 ] | 2 days, 2 hours [ 64800 ] |
| Worklog Id | 261167 [ 261167 ] |
| Status | Dev Scheduled [ 10014 ] | Implementation in progress [ 10016 ] |
| Status | Open Bug [ 10108 ] | Dev Scheduled [ 10014 ] |
-
- Time Spent:
- 4 hours
-
Discussions with Hassan/Nazih/Indrasan + solution
| Time Spent | 1 day [ 28800 ] | 1 day, 4 hours [ 43200 ] |
| Worklog Id | 261123 [ 261123 ] |
-
- Time Spent:
- 6 hours
-
Implementing solution / discussions
| 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) |
| Remaining Estimate | 0 minutes [ 0 ] | |
| Time Spent | 1 day [ 28800 ] | |
| Worklog Id | 261051 [ 261051 ] |
| Assignee | Khaled Khalil [ kkhalil ] | Mustapha Al-Hage [ malhage ] |
| Attachment | 2025-02-18-01.29.34_ZainKsa.rar [ 103878 ] |
| 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 ] |
| 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) |
-
- Time Spent:
- 1 day
-
Found the issue and checking solution
Cancelling this JIRA as I will create a separate JIRA (ZKU-264) to update the rule in FRS to make the LIC ID unique and ensure it will import in NEP accordingly.
As per NEP-DEV current LIC identifier is Node ID_LIC ID_LIC details so if my requested condition will be implement then it's difficult to identify duplicity & related errors.