JP7413516B2 - Test methods for validation of RSP processes and active test systems providing such test methods - Google Patents

Description

This application claims priority from German patent application DE 10 2019 214 919.7, the contents of which are incorporated herein by reference.

The present invention relates to a test method for validation of remote eSIM provisioning (RSP) processes. The invention also relates to an active test system that provides such a test method.

Test systems for mobile networks are known, for example, from US Pat. US Pat. No. 5,090,000 discloses embedded subscriber identity module (SIM) monitoring. US Pat. No. 5,001,502 discloses a method and device for embedded SIM provisioning. US Pat. No. 6,001,303 discloses a method for detecting remote access of a universal integrated circuit card (UICC).

US 10,097,981 B1 US 7,831,249 B2 WO 2004/049746 A1 US 2019/0075448 A1 WO 2016/013827 A1 WO 2017/013127 A1

The aim of the invention is to improve the capabilities of such a test system for testing mobile networks with remote eSIM provisioning.

This object is met by a test method comprising the features of claim 1 or 2 and an active test system comprising the features of claim 8.

Embedded general purpose integrated circuit cards (eUICCs), or embedded SIMs (eSIMs), are widely used in consumer Internet of Things (IoT) and Machine-to-Machine (M2M) devices, and are used to connect devices to mobile networks. identify. Furthermore, eSIM for smartphones has also been introduced. eSIM is a next-generation SIM technology that aims to replace physical cards with a combination of hardware and software and provide the ability to remotely switch devices between carriers (operators). The technology allows a single device to host multiple connectivity providers (called profiles) and is designed for use across the entire spectrum of mobile devices, including smartphones and IoT modules.

The hardware part of the eUICC card is mainly manufactured in embedded form factor (MFF2). The software portion of the eSIM can be remotely downloaded and installed on the eUICC card. This process is called remote eSIM provisioning (RSP). The term eUICC or eSIM mentioned in this patent specification, as the software part of the eUICC that is downloaded, is referred to as a "personalized" eUICC or eSIM. The eUICC is not easily accessible or replaceable, is not intended to be removed or replaced on the device, and allows secure modification of subscriptions.

GSMA is a standard for eSIM provisioning for M2M devices and consumer devices, respectively.
- GSMA SGP. 02 v4.2, July 7, 2020 - Embedded SIM Remote Provisioning Architecture - Technical Specification,
- GSMA SGP. 22 v2.3, June 5, 2020 - RSP Technical Specifications,
- GSMA SGP. 02 v4.0, February 25, 2019 - Embedded SIM remote provisioning architecture,
stipulates.
The test method and active system according to the invention covers the testing and validation aspects when eSIMs are provisioned on behalf of mobile carriers or their third parties of eSIM-enabled devices.

Further standards defined by the GSMA are:
- GSMA SGP. 23 RSP Test Specification Version 1.7, July 7, 2020.
Another standard defined by the GSMA is
- GSMA SGP. 24 RSP Compliance Process Version 2.2, September 17, 2019.

Multiple profiles can be downloaded and installed on the eUICC. A profile is a combination of file structures, data, and data associated with an operator and provisioned into or residing on the eUICC that, when activated, allows access to a particular mobile network infrastructure. Make it. Only one profile is active and operational at a time. All profiles in the eUICC can be enabled, disabled, deleted, or switched from one to another managed by the eSIM RSP platform on behalf of the operator or a third party.

The test method and active test system apply an end-to-end test method to verify mobile network connectivity and services in the context of the RSP process. This test method verifies the RSP on a test system and meets the following conditions:
- GSMA SGP. for M2M devices. 02 RSP,
- GSMA SGP for consumer devices. 22 RSP,
Test mobile network connectivity using a SIM provisioned in a national or international serving network according to

An eSIM profile is a personalized software portion of an embodied universal integrated circuit card (eUICC), ie, software given to an assigned user. Such software includes at least one user profile. The RSP process may be used for consumer devices such as smartphones, smart watches, wearables, and/or M2M (machine-to-machine) devices, for example. This test method specifically verifies mobile network connectivity and services.

Ordering eSIM profiles from the RSP platform can be done manually or automatically. The sender of the order may be a mobile network operator (MNO). The RSP process may be initiated prior to placing the order. During the testing method, the previous working profile or bootstrap profile originally installed on the eUICC may be disabled and the downloaded eSIM profile is enabled. The check may be performed by monitoring the occurrence of at least one failed criterion. Such failed criteria may be downloaded and updated based on RSP platform connection timeouts and/or network attach timeouts, and/or based on the expected structure of orders, triggers, and/or downloads. may be satisfied based on the re-touch timeout of a device with a different eSIM profile.

During the test method, network connectivity and services are continuously provided by eSIM swapping.

According to the test method according to claim 1, the test probe simulates an M2M device.

The test probe may support a large frequency spectrum in licensed bands, including 2G, 3G, 4G and 5G radio frequencies. This configuration of the test probe allows the deployment of SMS (Short Message Service) as an efficient communication method between the remote RSP platform providing the eSIM profile and the test probe where the eSIM profile is provisioned via download. (deploy) possible. The test probe may support SMSoNAS (SMS over NAS) for 4G and 5G technologies. The test probe may support the IMS (IP Multimedia Subsystem) technology SMSoIP (SMS over Internet Protocol). The test probe can be configured to select the correct communication protocol depending on the communication technology environment, ie to adapt the communication protocol required for eSIM verification of the respective RSP platform. The test probe may be configured to communicate with an industrial IoT application. An example of such an industrial IoT application is Long-Term Evolution for Machines (LTE-M). Another example is NB-IoT (Narrow Band Internet of Things). The test probe may be configured to communicate with at least one LPWAN (Low Power Wide Area Network) wireless technology standard.

According to the test method according to claim 2, the test probe simulates a smartphone and/or a consumer IoT device.

The test probe may be configured to test user transaction related test criteria, ie to test the RSP validation process at the user level. During such user-level testing, the test probe may initiate quality testing steps by checking quality parameters that may be defined by key parameter indicators (KPIs). Such KPIs may be access failure rate, access time, cutoff rate, download start time, download availability rate, etc. Such quality parameters can be checked in real time via test probes. In that regard, the test probe may be configured to emulate actual user behavior of a user of a smartphone and/or consumer IoT device.

Examples of consumer IoT devices include tablets, smart watches, wearable computers, such as smart glasses, home voice controllers, doorbell cams, smart locks, smart light switches, air quality monitors, etc.

The sending entity of the subscription request according to claim 3 may use a proxy of a mobile network operator. A subscription request may include a link or code. During the trigger step, the order sending entity may confirm the subscription request from the test profile. The confirmation may trigger a test probe to detect a download address for downloading the ordered eSIM profile. The trigger option may use the SM-DP+ (Subscription Manager Data Preparation) default address stored in the target eSIM, and the root SM-DS to discover the FQDN (Fully Qualified Domain Name) of the SM-DP+ address. (Subscription Manager Discovery Server) or an activation code containing an SM-DP+ address.

The ordering schedule of claim 4 may include an amount of eSIM profiles generated by the RSP platform, and may include an IMSI value, multiple IMSI values, or an IMSI range, an ICCID value, multiple ICCID values, or It may include an ICCID range, it may include a non-personalized profile type or multiple non-personalized profile types, and it may include information about the target eSIM or multiple target eSIMs, such as an EID (eUICC-ID). The EID may be bound to an ordered eSIM profile ID (ICCID).

The test method according to claim 5 has proven its efficiency.

This applies in particular to the test method according to claim 6. The HTTP session may establish an e2e (end-to-end) connection between the target eUICC and the RSP platform via the TLS (Transport Layer Security) protocol. The test probe may establish a BIP (Bearer Independent Protocol) channel for communication between the test probe and the target eUICC. A CAT_TP session may include data for two commands: e2e CAT_TP link re-request and/or BIP channel establishment. Such HTTPs sessions or CAT_TP sessions may be maintained during the test method, in particular via LTE/EPS.

In the test method according to claim 7, the gateway identification may be performed in particular via the APN (Access Point Name) given in the trigger SMS.

The advantages of the active test system according to claim 8 correspond to those mentioned above regarding the test method. The test probe may be embodied as a smartphone.

The active test system according to claim 9 is particularly suitable for M2M applications. The SM-DP (Subscription Manager Data Preparation) module may receive orders and the SM-SR (Subscription Manager Secure Routing) module may manage personalized eSIM profiles.

The ordering module according to claim 10 may communicate with the RSP platform via a web interface or an application program interface (API).

The RSP platform according to claim 11 is particularly suitable for smartphones and/or consumer IoT devices. The SM-DP+ module may manage personalized eSIM profiles. The SM-DS module may identify suitable SM-DP+ addresses for test probes.

The signal connection between the SIM server and the test probe according to claim 12 may be established via a LAN/WAN. A SIM multiplexer according to claim 12 provides geographical separation of test probes and target eUICC/eSIM.

The cloud-based system according to claim 13 enables comfortable and cost-effective client connectivity.

Embodiments of the invention will be described below with reference to the accompanying drawings.

1 is a schematic diagram of the main components of an active test system that provides a test method for validating remote eSIM provisioning (RSP) processes for M2M (machine-to-machine) devices; FIG. 2 shows, in a schematic diagram similar to FIG. 1, a further embodiment of an active testing system providing a respective RSP verification process testing method for consumer devices, such as smartphones or different consumer IoT devices; FIG. 1 is a diagram showing a test system configuration including a SIM multiplexer. FIG. 1 is a diagram showing the configuration of a test system that communicates via the cloud.

A. Testing eSIM RSP for M2M The eUICC Remote Provisioning and Management Platform (known as RSP (Remote SIM Provisioning) Platform 1) is responsible for remote eSIM provisioning. This establishes two entities, an SM-DP (Subscription Manager Data Preparation) module 2 and an SM-SR (Subscription Manager Security Routing) module 3, which are securely connected to each other. The SM-DP module 2 acts on behalf of a mobile network operator (MNO) 4. The SM-SR module 3 establishes a secure and authenticated transport channel to the embedded general purpose integrated circuit card (eUICC) or personalized software part of the embedded SIM (eSIM). Such software parts may be assigned to connected devices by assigned users or in particular as part of the Internet of Things (IoT). The SM-SR module 3 also manages personalized profiles in the eUICC that are downloaded or switched between each other.

An eSIM card 5 of any suitable form factor is inserted into a test probe 6 simulating an M2M device according to one embodiment and a smartphone and/or a consumer IoT device according to another embodiment. Ru. The test probe 6, which may have multiple instances, is part of the active test system 7 and is configured to receive at least one required eSIM profile downloaded from the RSP platform under test 1. The inserted eSIM card 5 contains a currently functioning profile different from the required profile ordered and provisioned.

The test scenario tested with this test method includes the user side represented by the test probe 6.

FIG. 1 shows the three steps "Order-Trigger-Download" of the test procedure to verify the download of the required eSIM profile.

1. Order an eSIM profile (order step 8)
The RSP for M2M devices is initiated by a representative of the MNO 4 to order a specific eSIM profile of the target eUICC identified in the SM-DP module 2 of the RSP platform 1. Two exemplary test scenarios are covered.

a) eSIM profile manually ordered on RSP platform under test 1 A human tester connects to the RSP platform under test 1 on behalf of MNO 4, targets the eSIM card of test probe 6, and orders an eSIM download. 8 to RSP platform 1 and wait for a provisioning message from RSP platform 1.

b) eSIM profiles automatically ordered on the RSP platform under test 1 The active test system 7 uses the ordering token to order one or more eSIM profiles on behalf of the MNO 4 via a web interface or API. (Application Programming Interface) to exchange information with the RSP platform 1 to be tested. The RSP process may be started automatically. The test system 7 is waiting for a provisioning message from the RSP platform 1.

Order tokens can include:
- the quantity of eSIM profiles generated by the SM-DP module 2; - the IMSI value(s) or range (International Mobile Subscriber Identity);
- ICCID value or range (IC card ID)
- Non-personalized profile type(s)
- Information about the target eUICC(s), such as EID (eUICC-ID);

2. Trigger step 9
The SM-SR module 3 of the RSP platform under test 1 triggers the download of the required eSIM profile to the target eSIM card 5 of the test probe 6 via the OTA (over-the-air) interface. The SM-SR module 3 sends a trigger SMS addressing the eSIM card 5. When the test probe 6 with the current profile of the eSIM card 5 is connected to the mobile network (e.g. EPS attach in a 4G/5G network or GPRS attach in a 2G/3G network), the message sent by the SM-SR module 3 The triggered SMS is delivered to the target eSIM card 5 via the test probe 6 and triggers an HTTPs session or a CAT_TP session (Card Application Toolkit Transport Protocol) depending on the eUICC support. Based on the APN (Access Point Name) encapsulated in the trigger SMS, the test probe establishes a PDN (Packet Data Network) connection to the gateway named in the APN.

The test probe 6 receives and processes the trigger 9 to the eSIM card 5. If HTTPs are used, the trigger SMS includes an HTTP session trigger command, which allows e2e (transport layer security) between the eSIM card 5 and the SM-SR module 3 of the RSP platform 1 to An end-to-end) HTTP session is established. Under the HTTP session, the test probe 6 establishes a TCP/IP transport connection for the session to the RSP platform 1 and uses BIP (Bearer Independent Protocol) for communication between the test probe 6 and the eSIM card 5. Establish a channel.

If CAT_TP is used, the trigger SMS contains two commands.
- a request for an e2e CAT_TP link to be established between the eSIM card 5 and the SM-SR module 3; - data for the opening of the BIP channel between the test probe 6 and the eSIM card 5;

Similarly, under the CAT_TP session, the test probe 6 establishes a UDP/IP connection for the session and establishes a BIP (Bearer Independent Protocol) channel for communication between the test probe 6 and the eSIM card 5. .

3. Download and install step 9a
The operation of the necessary eSIM profile download and installation procedure, carried out between the eSIM card 5 and the test probe 6 on the one hand and the RSP platform under test 1 on the other hand, is carried out in four main steps: can.

- create a secure domain profile entity for each required eSIM profile to be downloaded to the eSIM card 5;
- personalize the entity with a first set of secure keys, called a key establishment;
- Download the necessary eSIM profile from the SM-DP module 2, install the eSIM profile with RAM (remote application management) to the eSIM card 5,
- enabling the newly installed eSIM profile and disabling the previously used working profile on the eSIM card 5 (this is called profile switching);

During operation, the test probe 6 maintains a reliable HTTPs session or CAT_TP session over LTE/EPS (Evolved Package System).

The triggering step and the step of checking whether the ordered and triggered eSIM profile was downloaded correctly is initiated from the user side, ie via the test probe 6.

B. Testing eSIM RSP for Consumer Devices With reference to FIG. 2, a further embodiment of an active testing system is described that provides a testing method for validating the RSP process of a smartphone or consumer IoT device, respectively. Components and functions already discussed with respect to the embodiment of FIG. 1 are given the same reference numerals and will not be discussed in detail again.

The RSP platforms under test 1 for eSIM RSPs of smartphones and/or consumer IoT devices include a Subscription Manager Data Preparation+ (SM-DP+) module 10 and a Subscription Manager Discovery Server (SM-DP+) module 10, respectively. - DS) module 11. The SM-DP+ module 10 prepares profile packages, protects them with profile protection keys, binds each protected profile package to a respective EID, and securely stores these bound profile packages to respective eSIM cards 5. to download. If the SM-DP+ address is unknown to the test probe 6, an SM-DS module 11 is required.

The eSIM card 5 is inserted into a test probe 6 that simulates or represents a consumer device. The test probe 6 is connected to the active test system 7 and configured to receive the required eSIM profile downloaded from the RSP platform 1 under test. The inserted eSIM card 5 contains a currently functioning profile that is different from the ordered and provisioned profile(s). In order to download the required eSIM profile from the SM-DP+ or to discover the SM-DP+ address via the SM-DS module 11, the test probe uses the HTTPs secure protocol.

FIG. 2 shows an exemplary four-step “Request-Order-Trigger-Download” test procedure to verify the download of the required eSIM profile.

1. Subscription request 12
Test system 7 starts the RSP process and requests a subscription.

2. Order eSIM profile 13
MNO 4 orders the requested eSIM profile on SM-DP+ module 10 . The prepared eSIM profile is securely stored in the SM-DP+ module 10. The EID is bound to an eSIM profile ID (ICCID).

3. Trigger 14 - Confirm Subscription The MNO 4 triggers the test probe 6 to confirm the subscription to find the appropriate address to download the required eSIM profile. This procedure is operator dependent and may be performed by accessing a URL, using a Local Profile Assistant (LPA), or by native functionality of the device's firmware. There are, for example, three options for triggering the test probe 6, which is representative of a consumer device or smartphone.

- Use of the default SM-DP+ address stored in the eSIM card 5 - Use of the root SM-DS for detection of the SM-DP+ address (FQDN) - Use of the Activation Code (AC)

The test probe 6 selects one of the procedures in the following order.

- Use of default SM-DP+ address.
This option is often used for power-on profile detection. The test probe 6 obtains a default SM-DP+ address that is preconfigured and stored in the eSIM card 5.

- Use of root SM-DS for profile discovery.
The test probe 6 obtains the SM-DC address configured in advance and stored in the eSIM card 5, establishes a TLS connection with the SM-DC server, establishes mutual authentication with the SM-DC via HTTPs, Send an event request without an event ID. The SM-DC replies to the test probe 6 with an event request using the AC (=SM-DP+address+matching ID), that is, the activation code.

- Use of AC.
The active test system 7 receives an activation code (AC) from the MNO 4 via any means, such as email or API. The AC is at least
- SM-DP+address,
- AC token (matching ID),
including.

The AC can be entered into the test probe 6 manually or by scanning a QR code (registered trademark).

4. Download and install step 15
The operation of the eSIM profile download procedure 15 is performed between the test probe 6 and the SM-DP+ module 10 of the RSP platform under test 1. During operation, the test probe 6 maintains a reliable e2eHTTPs session over TCP/IP via LTE/EPS or fixed cable. The test probe 6 uses the parameter EID and the matching ID to initiate the download of the required eSIM profile and identify the bound profile package. If the profile is downloaded from the default SM-DP+ address, the matching ID is empty.

After receiving the entire bound profile package, the test probe 6 starts installing the required eSIM profile onto the eSIM card 5 in a safe and secure manner.

In further embodiments, a smartphone may be used as the test probe 6.

The eSIM RSP of the smartphone is executed in the same manner as the eSIM download procedure described above regarding the eSIM card 5 of the test probe 6. A smartphone is considered as a specific embodiment of the test probe 6, ie, serves as a test mobile device with the same user access interface to the mobile application.

For enterprise smartphones, the EID list is used to order the required eSIM profile. The above approach of using the root SM-DS for address detection is applied in the triggering step 14.

In a further embodiment shown in FIG. 3, the active test system includes a SIM multiplexer 16. SIM multiplexer 16 includes a SIM server 17 and a number of eSIM cards 5. The SIM server 17 is in signal connection with the test probe 6, which includes a SIM emulation module 18, which in this embodiment is in signal connection with a test probe environment 19, which may be embodied as a mobile phone or a smart phone.

The SIM emulation of the SIM emulation module 18 represents and operates as a target eSIM, or eUICC, of the eSIM card 5.

The SIM multiplexer 16 can geographically separate the test probe 6 and the eSIM card 5 (eUICC) to provision multiple eSIMs and subsequently dispatch the provisioned eSIMs. The test system 7 uses the SIM multiplexer 16 to connect the eSIM card 5 (eUICC) and the SM-SR module 3 (for M2M devices, compare with FIG. 1 above) or the test probe environment 19 of the test probe 6. The provided mobile connectivity will be used to bridge messages between the SM-DP+ modules 10 (for smartphones and/or consumer IoT devices, compare FIG. 2 above). Each embodiment will be described below with reference to FIG. 4.

Verification of the eSIM RSP consists of two test sequence parts.
(a) The eSIM profile is provisioned and swapped from the bootstrap to the target operator by verifying that the test probe is successfully reconnected to the network and comparing the new IMSI value with the previous value of the eSIM RSP. Verify that the
(b) Testing of network service guarantees after RSP by using eSIM provisioned with test probes for basic mobile services (such as HTTPs download, Ping, SMS MO MT, and voice MO MT). Such post-RSP network service assurance testing will not be described in further detail.

The test system can be a traditional server/client model based distributed test system. Nowadays, cloud-based testing systems are mainly deployed. Test probes can be connected to either type of test system.

Communication between the main components of the test system 7 may be performed via a cloud-based test server 20. (See Figure 4)

Such a cloud-enabled test system 7 is applied to the validation of the eSIM RSP process (see Figure 4) and also to the verification of SMS and/or RAM (remote application management) via HTTP(s) via LTE/EPS. support.

In FIG. 4, different embodiments of the test probe 6 are depicted, communicating via a core network interface or via a wireless interface.

The RSP test procedure using the clouded test system 7 is the same as described above. A standard test sequence consisting of EPS ATTACH and Trigger-SMS may be performed.

In the following, key aspects regarding validation of manually triggered RSP processes are described.

A one-way active test is performed. In this scenario, the user initiates the test and manually triggers the RSP process from the provisioning platform (client 21). The test sequence is as follows.

- Connect to the network (MNO4, compare Figures 1 and 2 above),
- Wait for reception of provisioning SMS-MT or SM-DP+ address with AC token,
- wait until the eSIM provisioning HTTPs session between the eSIM card 5 and the RSP platform 1 (including the SM-SR module 3 or SM-DP+ 10) is completed;
- Wait for successful network reconnection with the newly provisioned eSIM profile;
- Disconnect from the network.

The triggering step and the step of checking whether the ordered and triggered eSIM profile was downloaded correctly is initiated from the user side, ie via the test probe 6.

Input Parameters Should include standard test parameters. It should also include a timeout parameter, which allows the user to set a timeout for waiting for a provisioning trigger SMS from the SM-SR module 3. Examples are shown in the table below.

Key parameter indicators (KPI)
The following KPIs should be provided:

The verification results may be recorded in a results file. Such files may be in PCAP (packet capture) format.

The following fail criteria may be set during RSP verification:

- Not receiving an SMS (during a user-configured timeout period) or not receiving a Subscription Confirmation (AC) from the SM-SR.
- An HTTPs session is not opened between the eSIM card 5 or the SIM emulation of the SIM emulation module 18 and the RSP platform (SM-SR or SM-DP+).
- The ending IMSI is the same as the starting IMSI.
- Network reconnection to new APN after IMSI change is not successful.

In the case of an automatically triggered RSP (compare the embodiment described with respect to FIG. 2 above), the active test system 7 according to FIG. 4 preferably uses two interfaces for the RSP.

- One mobile interface for the RSP process itself.
- One LAN interface for interacting with the API of the RSP Platform 1 under test.

This test sequence must be customized depending on the platform being tested that the customer is using.

The mobile interface part needs to behave the same as in the manually triggered scenario above.

- Connect to the network (MNO4, compare Figures 1 and 2 above).
- Provisioning trigger - wait for SMS.
- Wait until the HTTPs session between the eSIM card 5 and the RSP platform 1 (SM-SR module 3 or SM-DP+ 10) is completed.
- Disconnect from the network.

The LAN interface is preferably used to send API commands to the provisioning platform 21. The command should be user configurable, eg, download profile, delete profile, or activate profile.

Input Parameters Similar to the manual scenario, a timeout parameter should be included, allowing the user to set the timeout for the time to wait for the provisioning trigger-SMS from the SM-SR module 3.

Additional parameters for interacting with the API need to be included (operation type, authentication to the API, eSIM/eUICC ID (EID) - ID of the requested eSIM profile that requires provisioning, IMSI). The complete list of parameters can be specified based on the specific RSP platform API documentation.

Key Parameter Indicators The following KPIs should be provided:
- IMSI at the start of the test.
- IMSI at the end of the test.
- IP session lifetime from the PCAP file - IP session lifetime between the eSIM card 5 and the SM-SR module 3 - This is the time taken to complete RSP operations such as profile download, activation, and deactivation. reflect.
- IP address of the SM-SR module 3 or SM-DP+ module 10 from the PCAP file.
- duration of IP session initiation - if possible - between reception of the provisioning SMS or AC and the initiation of the IP session (TCP SYN from mobile to RSP platform 1 (SM-SR or SM-DP+)); Measured as lifetime.
- Total Provisioning Lifetime - The time from sending the API1 trigger until the IP session is completed.
- SMS Reception Duration - Duration from sending the API trigger until the Provisioning SMS is received.
- Subscription duration - duration from subscription request to subscription confirmation

A PCAP file may be provided as the result file.

During RSP verification, the following fail criteria may be set:

- Not receiving an SMS (during a user-configured timeout period) or not receiving a Subscription Confirmation (AC) from the SM-SR.
- An HTTPs session is not opened between the eSIM card 5 or the SIM emulation of the SIM emulation module 18 and the RSP platform (SM-SR or SM-DP+).
- The ending IMSI is the same as the starting IMSI.
- RSP platform is not reachable via API.

The active test system may also include an ordering module, which may be part of the test probe 6, in order to automatically order the required sequence of eSIM profiles according to the ordering schedule.

1 RSP platform 2 SM-DP module 3 SM-SR module 4 Mobile network operator (MNO)
5 eSIM card 6 test probe 7 active test system 8, 13 order step 9, 14 trigger step 9a download and installation step 10 SM-DP+ module 11 SM-DS module 12 request step 15 eSIM profile download procedure 16 SIM multiplexer 17 SIM server 18 SIM emulation module 19 Test probe environment 20 Cloud-based test server 21 Provisioning platform (client)

Claims (13)

A test method for validation of a remote eSIM provisioning (RSP) process, the method comprising:
the RSP platform under test (1) receives (8; 13) an order for downloading an eSIM profile;
the RSP platform (1) triggering (9; 14) a download of the ordered eSIM profile;
downloading (9a; 15) the triggered eSIM profile from the RSP platform (1) to a target eSIM or eUICC (5) of a test probe (6) via an over-the-air (OTA) interface;
the test probe (6) checking whether the order and the triggered eSIM profile were downloaded correctly ;
said test probe (6) validating said downloaded eSIM profile and verifying mobile network connectivity and services;
The test method, wherein the test probe (6) is configured to simulate an M2M (machine-to-machine) device. A test method for validation of a remote eSIM provisioning (RSP) process, the method comprising:
the RSP platform under test (1) receives (8; 13) an order for downloading an eSIM profile;
the RSP platform (1) triggering (9; 14) a download of the ordered eSIM profile;
downloading (9a; 15) the triggered eSIM profile from the RSP platform (1) to a target eSIM or eUICC (5) of a test probe (6) via an over-the-air (OTA) interface;
the test probe (6) checking whether the order and the triggered eSIM profile were downloaded correctly ;
said test probe (6) validating said downloaded eSIM profile and verifying mobile network connectivity and services;
The test probe (6) is configured to simulate a smartphone and/or a consumer IoT device;
a test scenario to be tested using the test method includes a user side represented by the test probe (6);
The testing method, wherein the triggering step (9; 14) and the confirming step are initiated from the user side. 3. Testing method according to claim 2 , characterized in that, before an order, a subscription request (12) is sent from the test probe (6) to the order sending entity (4). 4. A testing method according to any one of claims 1 to 3, characterized in that the testing method comprises automatically ordering a series of eSIM profiles according to an ordering schedule. When said RSP platform (1) triggers (9; 14) the download of said ordered eSIM profile, said RSP platform (1) addresses said target eUICC (5) and sends a test probe (6) to said target eUICC (5). 5. Test method according to any one of claims 1 to 4, characterized in that the method comprises sending a trigger SMS to: ). The trigger SMS triggers an HTTPs session or a CAT_TP (Card Application Toolkit Transport Protocol) session established between the RSP platform (1) and the target eSIM or eUICC (5) of the test probe (6). The test method according to claim 5, characterized in that: When the RSP platform (1) triggers (9; 14) the download of the ordered eSIM profile, the test probe (6) connects to the gateway specified in the APN encapsulated in the trigger SMS. Test method according to claim 5 or 6 , characterized in that a PDN (Packet Data Network) connection is established. An active test system (7) providing a test method according to any one of claims 1 to 7, comprising:
at least one test probe (6) comprising at least one target eSIM or eUICC (5) with an initial working profile installed;
an interface to an RSP platform (1) for remotely providing an eSIM profile different from said initial working profile;
an OTA interface for providing communication between the RSP platform (1) and the test probe (6);
An active test system (7) characterized in that it has: The RSP platform (1) is
a subscription manager data preparation (SM-DP) module (2);
Active test system according to claim 8, characterized in that it comprises a Subscription Manager Security Routing (SM-SR) module (3). Active test system according to claim 8 or 9, characterized in that it comprises an ordering module for automatically ordering a series of eSIM profiles according to an ordering schedule. The RSP platform (1) is
Subscription Manager Data Preparation+ (SM-DP+) module (10);
Active testing system according to any one of claims 8 to 10, characterized in that it comprises a Subscription Manager and Discovery Server (SM-DS) module (11). comprising a SIM multiplexer (16) geographically separated from the test probe (6);
Claim characterized in that said SIM multiplexer (16) comprises a SIM server (17) and a number of eUICCs (5), said SIM server (17) being in signal connection with said test probe (6). 12. The active test system according to any one of 8 to 11. Equipped with a cloud-based server (20),
Active test system according to any one of claims 8 to 11, characterized in that communication between main components of the active test system (7) is carried out via the cloud-based server (20). .

Images