Skip to content

ASN.1 Editor: tasks with tested values

The hands-on companion to the ASN.1 Editor guide. Results were produced on 4 October 2026, as a principal holding asn1editor: maintain unless a row says otherwise.

Before you start

Addressasn1-editor.rsplab.click
Role neededasn1editor: read to decode; maintain to edit, encode and test on a device
SampleNo profile to hand? Try a sample loads the GSMA TS.48 v5 test profile (TS48v5_SAIP2.3_BERTLV_SUCI.der, 12284 octets)

1. Decode a profile package

Load the sample.

Expected result. 30 profile elements, no findings. The header decodes as:

FieldValue
profileTypeGSMA Generic eUICC Test Profile
iccid89000123456789012341
eUICCMandatoryServicescontactless, usim, isim, csim, milenage, … (34 flags)

The elements include header, mf, pukCodes, five pinCodes, telecom, usim, optUsim, two akaParameter, csim, isim, four rfm, securityDomain and end.

2. Decode an SGP.22 message

SGP.22 message, spec version SGP.22 v2.x (v2, v3.0 and v3.1 are offered; v2 has 126 message types), type ProfileInstallationResult. Paste the profileInstallationResult hex from an install in the SM-DP+ console.

Expected result. The tree:

ProfileInstallationResult
profileInstallationResultData
transactionId
notificationMetadata
seqNumber 1
notificationAddress smdpplus.rsplab.click
iccid 984405000000000075F0
smdpOid 2.23.146.1.2.1.0.0.1.2
finalResult
successResult
aid A0000005591010FFFFFFFF8900001100
euiccSignPIR

3. Edit and re-encode

In the sample’s header, set iccid to 89000123456789012359 and save.

Expected result. A new package is produced (one edit applied) and offered for download.

With only read, the same save answers editing requires the maintain role; this account has read.

4. Test on a device (Consumer)

Test on a device, device type Consumer (SGP.22, SM-DP+ → LPA → eUICC).

StepResult
A phone is prepareda new test phone, product CONSUMER, no profiles
The package is ordereddeclared ICCID 98001032547698103214, 30 elements, an activation code for smdpplus.rsplab.click
InstallInstalled — The card installed the profile.

The Timeline carries the LPA’s six steps — initiateAuthentication, authenticateClient (eUICC chain accepted), getBoundProfilePackage (BPP 12860 bytes), LoadBoundProfilePackage, one notification delivered. Runs lists the run so it can be reopened.

Test phones shows each phone with its last digits, kind, date and profile count. A card another console manages is marked, for example the OTA console manages this SIM, and cannot be scrapped here.

Not yet verified

CapabilityWhy
Test on a device as IoT or M2MNot run in this pass
The AssistantNeeds your own model provider key
Structural edits (insert or delete an element)Not run in this pass