PeterCxy
/
OpenEUICC
4
6
Fork 8
Code Issues 8 Pull Requests Actions Projects Releases 4 Wiki Activity

[Suggestion] Adding Profile Size Under ICCID & Approximately eSIM Profiles Left #5

New Issue
Open
opened 2023-12-20 03:07:18 +01:00 by rapdodge · 5 comments
rapdodge commented 2023-12-20 03:07:18 +01:00
Copy Link

Hello there!

Is that possible to adding profile size under ICCID?
So, it would be like this:

[Name of the profile]
[Status of the profile]
Provider: [Name of the provider]
ICCID: [ICCID]
Size: [Profile size]

And the size has smaller font like Space remaining: xxx kB on New eSIM window.

And talking about Space remaining: xxx kB on New eSIM window, it's nicer to have like profile left that you can add into the smartcard like:

Space remaining: xxx kB (~x profiles left)

Why I'm proposing this suggestion, because it'll be great to adding it more information about every profile and can estimate how many profile that user can add.

Hello there! Is that possible to adding profile size under ICCID? So, it would be like this: ``` [Name of the profile] [Status of the profile] Provider: [Name of the provider] ICCID: [ICCID] Size: [Profile size] ``` And the size has smaller font like `Space remaining: xxx kB` on `New eSIM` window. And talking about `Space remaining: xxx kB` on `New eSIM` window, it's nicer to have like profile left that you can add into the smartcard like: ``` Space remaining: xxx kB (~x profiles left) ``` Why I'm proposing this suggestion, because it'll be great to adding it more information about every profile and can estimate how many profile that user can add.
PeterCxy commented 2023-12-20 22:04:17 +01:00
Owner
Copy Link

I don't think estimating the number of profiles left is really responsible, because there is really no limit on how big a profile can be. I'd rather implement a failsafe during the download process where it rejects the new profile if the base64 encoded BPP is estimated to extract to something larger than the remaining space.

I don't think estimating the number of profiles left is really responsible, because there is really no limit on how big a profile can be. I'd rather implement a failsafe during the download process where it rejects the new profile if the base64 encoded BPP is estimated to extract to something larger than the remaining space.
rapdodge commented 2023-12-21 02:36:29 +01:00
Author
Copy Link

I don't think estimating the number of profiles left is really responsible, because there is really no limit on how big a profile can be. I'd rather implement a failsafe during the download process where it rejects the new profile if the base64 encoded BPP is estimated to extract to something larger than the remaining space.

Hmmm... Okay... So, what about adding more information about how much space that some profile takes? Is that possible or not to getting it from the smartcard?

> I don't think estimating the number of profiles left is really responsible, because there is really no limit on how big a profile can be. I'd rather implement a failsafe during the download process where it rejects the new profile if the base64 encoded BPP is estimated to extract to something larger than the remaining space. Hmmm... Okay... So, what about adding more information about how much space that some profile takes? Is that possible or not to getting it from the smartcard?
laf0rge commented 2024-01-27 17:38:16 +01:00
Copy Link

I really like the idea of displaying the size of existing/installed profiles as well as the total remaining space.

Hoever, I also agree with @PeterCxy that ther is no way to estimate the number of remaining profiles due to their unknown size. Also, many eUICC have a hard-coded limit on the number of profiles, which is unrelated to the memory size. I've seen eUICC with a limit of 10 or 20, for example.

I really like the idea of displaying the size of existing/installed profiles as well as the total remaining space. Hoever, I also agree with @PeterCxy that ther is no way to estimate the number of remaining profiles due to their unknown size. Also, many eUICC have a hard-coded limit on the number of profiles, which is unrelated to the memory size. I've seen eUICC with a limit of 10 or 20, for example.
moon-cacke commented 2024-02-29 11:27:06 +01:00
Copy Link

I really like the idea of displaying the size of existing/installed profiles as well as the total remaining space.

Hoever, I also agree with @PeterCxy that ther is no way to estimate the number of remaining profiles due to their unknown size. Also, many eUICC have a hard-coded limit on the number of profiles, which is unrelated to the memory size. I've seen eUICC with a limit of 10 or 20, for example.

100% agree :) 👍... may be a progress bar at the top with the filled percentage will be nice in addition to size information for each profile...

> I really like the idea of displaying the size of existing/installed profiles as well as the total remaining space. > > Hoever, I also agree with @PeterCxy that ther is no way to estimate the number of remaining profiles due to their unknown size. Also, many eUICC have a hard-coded limit on the number of profiles, which is unrelated to the memory size. I've seen eUICC with a limit of 10 or 20, for example. 100% agree :) 👍... may be a progress bar at the top with the filled percentage will be nice in addition to size information for each profile...
moon-cacke commented 2024-03-10 16:49:08 +01:00
Copy Link

Bringing some information about the memory feature... (@PeterCxy you probably know already...)
Had been playing with PySim and other softs.... (python pySim-shell.py -p0 to start pysim after install on reader 0)

The main remaining memory is requested with the function GetEuiccInfo2Request - APDU Commands:

  1. Entering ADF.ISD-R
    apdu 00A4040010A0000005591010FFFFFFFF8900000100
  2. Executing GetEuiccInfo2Request (BF 22)
    apdu 00E2910002BF22

The size of each profile can be requested with the function GetProfilesInfo- APDU Commands:

BUT "Profile Size, tag '9F25'" has been introduced only lately by GSMA standards it was not present on the specifications v2.3 (page 198) but is on the specifications v3.0 draft (page 336) I have two card from eSim.me, a classic one and a one with a custom latest firmware none of the cards send back the value "Profile Size, tag '9F25'" I guess I will have to wait for an update if any... but at least the function had been introduced :)

  1. Entering ADF.ISD-R
    apdu 00A4040010A0000005591010FFFFFFFF8900000100
  2. Executing GetProfilesInfo (BF 2D)
    apdu 00E2910003BF2D00

Note:

  • The answers can be breakdown here https://amenitypj.in/tlvPlay and with the help of https://www.gsma.com/esim/wp-content/uploads/2022/10/SGP.22-v3.0-1.pdf
  • The functions are already programmed on the LPAC/PySim etc. but I am indicating how to request the raw value in case a section is not programmed/ignored
  • Other than those two function I did not find any official way to do so... we may be limited to the first function as the second one is new and thus we could not request a profile size but just request the free memory before and after adding the profile, but this data won't be saved
Bringing some information about the memory feature... (@PeterCxy you probably know already...) Had been playing with PySim and other softs.... (`python pySim-shell.py -p0` to start pysim after install on reader 0) **The main remaining memory is requested with the function GetEuiccInfo2Request - APDU Commands:** 1. Entering ADF.ISD-R `apdu 00A4040010A0000005591010FFFFFFFF8900000100` 2. Executing GetEuiccInfo2Request (BF 22) `apdu 00E2910002BF22` **The size of each profile can be requested with the function GetProfilesInfo- APDU Commands:** BUT "Profile Size, tag '9F25'" has been introduced only lately by GSMA standards it was not present on the [specifications v2.3 (page 198) ](https://www.gsma.com/esim/wp-content/uploads/2021/07/SGP.22-v2.3.pdf) but is on the [specifications v3.0 draft (page 336)](https://www..gsma.com/esim/wp-content/uploads/2022/10/SGP.22-v3.0-1.pdf) I have two card from eSim.me, a classic one and a one with a custom latest firmware none of the cards send back the value "Profile Size, tag '9F25'" I guess I will have to wait for an update if any... but at least the function had been introduced :) 1. Entering ADF.ISD-R `apdu 00A4040010A0000005591010FFFFFFFF8900000100` 2. Executing GetProfilesInfo (BF 2D) `apdu 00E2910003BF2D00` **Note:** - The answers can be breakdown here https://amenitypj.in/tlvPlay and with the help of https://www.gsma.com/esim/wp-content/uploads/2022/10/SGP.22-v3.0-1.pdf - The functions are already programmed on the LPAC/PySim etc. but I am indicating how to request the raw value in case a section is not programmed/ignored - Other than those two function I did not find any official way to do so... we may be limited to the first function as the second one is new and thus we could not request a profile size but just request the free memory before and after adding the profile, but this data won't be saved
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
master
mep
unpriv-decouple
lpac
unpriv-beta01
unpriv-alpha03
unpriv-alpha02
unpriv-alpha01
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
4 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#5
No description provided.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?