Technical problems and answers on SIM Editor

1. License Request Generation & Submission Steps:

   1. Launch SIM Editor:

      • Open the License Manager window.

   2. Generate the License Request:

      • Click “Generate License Request Code.”

      • Copy the generated code.

   3. Email the Code:

      • Send the code to order@smartjac.com.

   4. Receive & Validate License:

      • Upon receipt of the license file (from your sales representative), click “Open & Validate License File.”

      • Expected outcome: “Validation successful” indicates proper licensing.

        Follow-up Questions:

        • Is the License Manager showing any error messages during this process?

        • Have you verified that your email client has sent the code correctly?

        
        

        

2. License Transfer Process Steps:

   1. Prepare the New PC:

      • Download and install the latest SIM Editor version from this link.

      • Open License Manager and select “Transfer License.”

      • This generates a transfer request file/number.

   2. Process on the Current PC:

      • On the existing licensed PC, open License Manager.

      • Enter the transfer request from the new PC.

      • A new license will be generated and the old license deactivated.

   3. Activate on New PC:

      • Use the new license file to activate SIM Editor on the new PC.

        Important Note:

        • Always initiate the transfer from the new PC to avoid deactivating the current license prematurely.

          Follow-up Questions:

        • Did you encounter any issues when generating or processing the transfer request?

        • Are you following the “Transfer License” documentation in the Help section?

        
        

        

3. Handling Validation Failures Explanation & Actions:

   • Common Causes:

     • Environment changes (e.g., OS or hardware upgrades), multiple simultaneous license uses, or expired licenses.

   • Steps to Resolve:

     • Verify if any changes have been made since last validation.

     • If the license is being used on a different PC, initiate a proper transfer.

     • Contact support if the license appears expired.

       Follow-up Questions:

   • Can you confirm if any changes were made to the PC environment recently?

   
   

   

4. EF File Not Found on the Card (e.g., 4F06) Scenario:

   • A support request may indicate missing file 4F06 during configuration. Explanation:

   • File 4F06 is used only on 5G SIM cards. 3G/LTE cards do not support 5G files due to the 15-byte UST limit.Action:

   • Inform the customer that a 5G SIM card is required for file 4F06.

     Follow-up Questions:

   • Is the customer attempting to configure a 3G/LTE card for 5G services?

   
   

   

5. Troubleshooting License Issues Steps:

   1. Gather Evidence:

      • Request a full screenshot of the License Manager window.

      • Ask for the License Request Number.

   2. Check for Environment Changes:

      • Confirm if there have been OS or hardware modifications.

   3. Solution:

      • Upgrade to version 3.195 if using an older version.

      • Follow our upgrade guidelines.

        Follow-up Questions:

        • What specific error message is displayed in the License Manager?

        • Have any system changes been reported recently?

        
        

        

6. Resolving 5G SIM Card Detection Problems Steps & Considerations:

   1. Review 5G Service Configuration:

      • Verify that the UST is correctly set.

      • Disable services above 121 initially.

   2. Enabling 5G Security (if needed):

      • Enable services 122 and 123 for basic 5G security.

      • If additional 5G services are required, check the USIM/5GS configurations.

   3. Apple Devices:

      • Refer to Apple’s Private Network Guidelines for iOS 17 and later.

        Follow-up Questions:

        • Which device and OS version is being used?

        • Has the customer already tested with the recommended settings?

        
        

        

7. Access Class Barring (ACC) Configuration Details:

   • File: ACC [6F78] under USIM.

   • Coding:

     • Each ACC is coded as a bit (1 for allocated, 0 for not).

     • Example: Allocating ACC 1 and 4 → “00 12” in HEX.

   • Caution:

     • Never set ACC to “00 00” as it blocks connectivity.

       Follow-up Questions:

   • Do customers need additional guidance on the binary-to-HEX conversion?

   
   

   

8. Setting AMF on SIM Cards Instructions:

   • Default Setting:

     • Typically set to “00 00.”

   • For EPS AKA:

     • Use “80 00” (or “80 01” if issues persist).

   • Note:

     • For cards with TUAK activated (SMAOT500B234FF), follow TUAK-specific guidelines.

       Follow-up Questions:

   • Has there been any confusion regarding the use of AMF between UMTS-AKA and EPS AKA?

   
   

   

9. HPLMNwAct Configuration Steps:

   1. Data Entry:

      • Enter PLMN data with the highest priority access first.

      • Example: “08 00” (NG-RAN) followed by “40 00” (E-UTRAN) and “80 00” (UTRAN).

   2. Service Activation:

      • Ensure UST service 43 is enabled by default.

        Follow-up Questions:

        • Do customers require examples of multiple PLMN configurations?

        
        

        

10. PC/SC Reader / Communication Error Troubleshooting Steps:

    1. Use “Check ATR”:

       • Test communication between SIM Editor and the card reader.

    2. Remote Desktop:

       • Avoid using RDP; try TeamViewer or Webex.

    3. USB Port & Admin Rights:

       • Change USB port and run SIM Editor as Administrator.

    4. Antivirus & Multiple Readers:

       • Check that antivirus software isn’t blocking access and that only one card reader is active.

         Follow-up Questions:

         • Are there any additional error messages besides “Smart Card Resource Manager is not running”?

         
         

         

11. Communication Error with a Virtual Smart Card Steps:

    1. Identify the ATR:

       • ATR (3B8D0180FBA000000397425446590401CF) suggests a Microsoft Virtual Smartcard.

    2. VMware Settings:

       • Check if the smart card device is connected to the virtual machine.

       • Disconnect the virtual smart card if not needed.

    3. Device Redirection & VMware Tools:

       • Adjust redirection settings and ensure VMware Tools is up to date.

    4. Host Check:

       • Confirm the host system is not sharing the physical smart card reader.

         Follow-up Questions:

         • Is the customer aware of any virtualization in their setup?

         • Would they like guidance on checking for hidden devices in Device Manager?

         
         

         

12. SUCI Data Configuration Overview:

    • Applicability:

      • For SMAOT500A/B 5G cards.

    • Default Values:

      • SUCI data resides in file 4F07 and can be edited if service 124 is enabled.

    • Key Details:

      • Profile A keys are 32 bytes, Profile B can be up to 64 bytes.

    • Configuration Tips:

      • Ensure proper key pair generation (using Curve25519 or Secp256r1).

      • Provision both SUCI files (5FC0/4F07 and 5FD0/4F01) to cover all scenarios.

        Follow-up Questions:

    • Would customers benefit from a tool to generate and format SUCI keys?

    
    

    

13. URSP / NSSAI for 5G SIM Cards Purpose:

    • To manage Route Selection Policies (network slicing). Steps:

    1. Check EFURSP (4F0B):

       • Confirm that service 132 is available in UST.

    2. Review Documentation:

       • Refer to 3GPP TS 24.526 and the Trusted Alliance PDF for details.

         Follow-up Questions:

         • Do customers need examples of URSP rule configurations?

         
         

         

14. ViLTE / ViNR Implementation Explanation:

    • No Additional Card Requirements:

      • Uses the same files as VoLTE/VoNR.

    • Key Action:

      • Ensure that ISIM Auth keys, IMPI, IMPU, and Domain are provisioned during script creation.

        Follow-up Questions:

    • Are customers experiencing any issues with IMS registration that might be related to this configuration?

    
    

    

15. ISIM and IMS APN Information Key Concepts:

    • IMS Registration:

      • Utilizes SIP after LTE Attach.

    • Information Exchange:

      • UE sends “+sip.instance,” IMPU (e.g., tel:+447700900123), and IMPI (e.g., username@realm).

    • Provisioning:

      • Ensure the HSS is correctly provisioned with this data.

        Follow-up Questions:

    • Does the customer require a more detailed explanation of IMS APN flows?

    
    

    

16. ICCID and Related Queries Details:

• ICCID Structure:

  • Format: MM CC II followed by the account ID and a checksum (via the Luhn algorithm).

• Additional SUCI Query:

  • For SUCI calculation (ADF.USIM/DF.5GS/EF.SUCI_CALC_INFO), provision both files (5FC0/4F07 and 5FD0/4F01) to ensure the keys are accessible for both ME and USIM calculations.

    Follow-up Questions:

• Is there any additional ICCID-related information needed?

1. Card Reader & PC/SC Errors (Error 0x000006F7) Steps:

   1. Test Communication:

      • Click “Check ATR” in SIM Editor.

   2. Verify Connections:

      • Ensure a secure connection and update drivers.

   3. Restart Services:

      • Restart the PC/SC service using services.msc.

   4. Advanced Troubleshooting:

      • Check Event Logs for detailed error messages.

   5. Virtual Environment Checks:

      • If using virtualization (VMware/RDP), follow the guidelines in Section 11.

        Follow-up Questions:

        • Would additional guidance on driver updates or service restarts be helpful?

        
        

        

2. Self/Customer Provisioned Cards Not Authenticating Steps:

   1. Provisioning Data Check:

      • Request detailed provisioning data, including Ki and OPc checksums.

   2. EF Provisioning Verification:

      • Confirm all required EFs (IMSI, Ki, OPc, SUCI_Calc_Info, UST, HPLMNwACT, AD) are correctly written.

   3. SUCI Configuration:

      • Ensure SUCI_Calc_Info matches the network’s private key.

   4. Device Considerations:

      • Check if the test device (e.g., iOS requiring IOS17) is compatible.

   5. Log Collection:

      • Ask for logs or diagnostic outputs if available.

        Follow-up Questions:

        • Can the customer provide a sample of the provisioning script or logs?

        • Which UE/phone model is being used?

        
        

        

3. Device Not Sending Registration Requests to gNB Steps:

   1. Device Configuration Check:

      • Confirm that the SIM’s Ki/OPc and PLMN configurations are correct.

   2. Test on Multiple Devices:

      • Verify whether the issue is device-specific.

   3. Collect Communication Traces:

      • If possible, collect traces between the device and the network.

   4. PLMN Verification:

      • Ensure the SIM card PLMN matches the device’s active network settings.

Follow-up Questions:

• Has the customer tried a different device or network?

• Are there any traces or error logs from the device available?