automatically process + delete notifications #41

Closed
opened 2024-08-01 17:01:38 +02:00 by laf0rge · 1 comment

For a R&D tool it is nice to have low-level control over processing and deleting individual notifications.

But for the average end-user, they simply want "it to work" and that means that a LPA is expected to

  • periodically poll the eUICC for pending notifications
  • automatically proocess them (send them to the respective SM-DP+
  • delete any notification that was successfully sent to a SM-DP+

So let's have this issue here as a reminder that this part of normal LPA logic should be added at some point. For R&D/testing purposes, there could always be a preference disabling automatic processing of notifications. But the default, for Joe Random User, should IMHO be the automatic behavior as speciifed for a LPA.

For a R&D tool it is nice to have low-level control over processing and deleting individual notifications. But for the average end-user, they simply want "it to work" and that means that a LPA is expected to * periodically poll the eUICC for pending notifications * automatically proocess them (send them to the respective SM-DP+ * delete any notification that was successfully sent to a SM-DP+ So let's have this issue here as a reminder that this part of normal LPA logic should be added at some point. For R&D/testing purposes, there could always be a preference disabling automatic processing of notifications. But the default, for Joe Random User, should IMHO be the automatic behavior as speciifed for a LPA.
Owner

OpenEUICC already processes download notifications by default. Enabling switching notifications (activation / deactivation) by default is not planned as it does not seem necessary for normal operations and I do not see why RSPs need to know about this information by default.

Deletion of notifications is not planned either since all eUICCs we have tested with seem to be able to purge old notifications automatically.

OpenEUICC already processes download notifications by default. Enabling switching notifications (activation / deactivation) by default is not planned as it does not seem necessary for normal operations and I do not see why RSPs need to know about this information by default. Deletion of notifications is not planned either since all eUICCs we have tested with seem to be able to purge old notifications automatically.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: PeterCxy/OpenEUICC#41
No description provided.