JP2023501874A - Test method for verification of RSP process and active test system providing such test method - Google Patents

Abstract

In a test method for verification of the remote eSIM provisioning process, an eSIM profile from the RSP platform (1) under test is ordered (8). Then the download of the eSIM profile ordered from the RSP platform (1) is triggered (9). The triggered eSIM profile is then downloaded (9a) from the RSP platform (1) over the wireless communication interface to the target eSIM or eUICC (5) of the test probe (6). The ordered, triggered and downloaded eSIM profile is then verified for correctness. The test probe (6) may be configured to simulate M2M devices, smart phones and/or consumer IoT devices. Such a test method improves the test system's ability to test mobile networks with remote eSIM provisioning, while eSIM swapping provides continuous network connectivity and services.

Description

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

The present invention relates to a test method for verification 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,300,000 discloses embedded Subscriber Identity Module (SIM) monitoring. US Pat. No. 5,900,000 discloses a method and device for embedded SIM provisioning. US Pat. No. 6,300,000 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

An object of the present invention is to improve the capabilities of such test systems 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 universal 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. In addition, eSIMs for smartphones have also been introduced. eSIM is a next-generation SIM technology that aims to replace the physical card with a combination of hardware and software to provide the ability to remotely switch devices between carriers (operators). This technology allows one 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 part 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 referred to in this patent specification is referred to as a "personalized" eUICC or eSIM as the software portion of the eUICC is downloaded. The eUICC is not easily accessible or replaceable and is not intended to be removed or replaced on the device, allowing secure changes to subscriptions.

GSMA is a standard for eSIM provisioning for M2M and consumer devices respectively;
- GSMA SGP. 02 v4.2, July 7, 2020 - Embedded SIM Remote Provisioning Architecture - Technical Specification,
- GSMA SGP. 22 v2.3, 5 June 2020 - RSP Technical Specification,
- GSMA SGP. 02 v4.0, February 25, 2019 - Embedded SIM Remote Provisioning Architecture,
stipulates.
The testing method and active system according to the present invention covers testing and verification aspects when eSIMs are provisioned on behalf of mobile operators or third parties of their 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 to or residing on the eUICC that, when activated, allows access to a particular mobile network infrastructure. to Only one profile is active and operational at a time. All profiles of the eUICC can be managed by the eSIM RSP platform to be activated, deactivated, deleted or switched from one to the other on behalf of the operator or 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 validates the RSP on a test system under the following conditions:
- GSMA SGP. 02 RSPs,
- GSMA SGP. 22 RSPs,
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 instantiated 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 order sender may be a mobile network operator (MNO). Prior to ordering, the RSP process may be initiated. During the test method, the previous working profile or bootstrap profile originally installed on the eUICC may be disabled and the downloaded eSIM profile is enabled. A 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 expected structure of orders, triggers, and/or downloads. may be fulfilled based on the reattach timeout of the device with the specified eSIM profile.

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

According to the test method of 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. Such a configuration of test probes deploys 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) can be done. The test probe may support SMSoNAS (SMS over NAS (non-access stratum)) for 4G and 5G technologies. The test probe may support 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 each RSP platform. The test probe may be configured to communicate with industrial IoT applications. An example of such an industrial IoT application is LTE-M (Long-Term Evolution for Machines). 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 of claim 2, the test probe simulates smart phones and/or consumer IoT devices.

A 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, test probes can initiate quality testing steps by checking quality parameters, which can be defined by key parameter indicators (KPIs). Such KPIs may be access failure rate, access time, cutoff rate, download start time, download availability rate, and the like. Such quality parameters can be checked in real time via test probes. In that regard, the test probes may be configured to emulate the actual user behavior of users of smartphones and/or consumer IoT devices.

Examples of consumer IoT devices include tablets, smartwatches, wearable computers, smart glasses, home voice controllers, doorbell cams (cameras), smart locks, smart light switches, air quality monitors, etc.

The subscription request sending entity of claim 3 may use a mobile network operator proxy. 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. Confirmation may trigger a test probe to detect the 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 on finding the FQDN (Fully Qualified Domain Name) of the SM-DP+ address. (Subscription Manager Discovery Server), or an activation code containing the SM-DP+ address.

5. The order schedule of claim 4 may include a quantity of eSIM profiles generated by the RSP platform, 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, may include a non-personalized profile type, or multiple non-personalized profile types, and may include a target eSIM, or information about multiple target eSIMs, such as an EID (eUICC-ID). An 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 TLS (Transport Layer Security) protocol. The test probe may establish a Bearer Independent Protocol (BIP) channel for communication between the test probe and the target eUICC. A CAT_TP session may contain two commands: re-request the e2e CAT_TP link and/or data for opening a BIP channel. Such HTTPs sessions, or CAT_TP sessions, especially over LTE/EPS, may be maintained during the test method.

In a testing method as claimed in claim 7, gateway identification may be performed via an APN (Access Point Name) specifically given in the triggered SMS.

The advantages of the active test system according to claim 8 correspond to those described above with respect to the test method. A test probe may be embodied as a smart phone.

An 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 of 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 SM-DP+ addresses suitable for test probes.

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

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

Embodiments of the invention are 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 of M2M (Machine to Machine) devices; FIG. 2 shows, in a schematic diagram similar to FIG. 1, a further embodiment of an active test system providing respective RSP validation process test methods for consumer devices, eg smartphones or different consumer IoT devices; FIG. Fig. 2 shows a test system configuration including a SIM multiplexer; It is a figure which shows the test system configuration|structure which communicates via a 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 constitutes two entities securely connected to each other: the SM-DP (Subscription Manager Data Preparation) module 2 and the SM-SR (Subscription Manager Security Routing) module 3 . 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 universal integrated circuit card (eUICC) or personalized software part of the embedded SIM (eSIM). Such software portions may be assigned to connected devices as part of an assigned user or, in particular, the Internet of Things (IoT). The SM-SR module 3 also manages personalized profiles in the eUICC that are downloaded or switched between.

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 consumer IoT device according to another embodiment. be. A test probe 6, which may have multiple instances, is part of an active test system 7 and is configured to receive at least one required eSIM profile downloaded from the RSP platform 1 under test. The inserted eSIM card 5 contains a currently working profile different from the required profile ordered and provisioned.

The test scenarios tested with this test method include the user side represented by the test probes 6 .

FIG. 1 shows the 3-step “order-trigger-download” test procedure for verifying the download of the required eSIM profile.

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

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

b) eSIM profiles automatically ordered on the RSP platform 1 under test The active test system 7 uses an order 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 under test. The RSP process can be started automatically. Test system 7 is waiting for a provisioning message from RSP platform 1 .

An order token can include:
- quantity of eSIM profiles generated by SM-DP module 2 - 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 the EID (eUICC-ID);

2. trigger step 9
The SM-SR module 3 of the RSP platform 1 under test triggers the download of the required eSIM profile to the target eSIM card 5 of the test probe 6 via OTA (over the air) interface. The SM-SR module 3 sends a triggered SMS addressing the eSIM card 5 . Sent by the SM-SR module 3 when a test probe 6 with the current profile of the eSIM card 5 is connected to a mobile network (e.g. EPS attach in 4G/5G networks or GPRS attach in 2G/3G networks) 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.

A test probe 6 receives and processes the trigger 9 to the eSIM card 5 . If HTTPs are used, the trigger SMS contains an HTTP session trigger command, which establishes an e2e (Transport Layer Security) protocol between the eSIM card 5 and the SM-SR module 3 of the RSP platform 1 via the TLS (Transport Layer Security) protocol. end-to-end) An 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 triggered SMS contains two commands.
- request for an e2e CAT_TP link to be established between the eSIM card 5 and the SM-SR module 3; - data for BIP channel opening 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 required eSIM profile download and installation procedure operations are performed between the eSIM card 5 and the test probe 6 on the one hand and the RSP platform 1 under test on the other hand and are performed 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 the Key Establishment;
- Download the required eSIM profile from the SM-DP module 2 and install the eSIM profile with RAM (Remote Application Management) on the eSIM card 5,
- Activate the newly installed eSIM profile and deactivate the working profile previously used 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 checking whether the ordered and triggered eSIM profile has been downloaded correctly is initiated from the user side, ie via the test probe 6 .

B. Testing eSIM RSPs for Consumer Devices With reference to FIG. 2, we describe further embodiments of active test systems that provide test methods for validating the RSP process of smartphones or consumer IoT devices, respectively. Components and functions already discussed with respect to the embodiment of FIG. 1 are labeled with the same reference numerals and will not be discussed in detail again.

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

An 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 working profile that is different from the ordered and provisioned profile(s). To download the required eSIM profile from the SM-DP+ or detect the SM-DP+ address via the SM-DS module 11, the test probe uses HTTPs secure protocol.

FIG. 2 shows an exemplary four-step “request-order-trigger-download” test procedure for verifying download of the required eSIM profile.

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

2. Ordering an eSIM profile 13
MNO 4 orders the requested eSIM profile at SM-DP+ module 10 . Prepared eSIM profiles are securely stored in the SM-DP+ module 10 . The EID is bound to the eSIM Profile ID (ICCID).

3. Trigger 14 - Subscription Confirmation 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 the Local Profile Assistant (LPA), or by native features of the device's firmware. There are, for example, three options for triggering the test probe 6, which is representative of consumer devices or smartphones.

- use of default SM-DP+ address stored in eSIM card 5 - use of root SM-DS for finding SM-DP+ address (FQDN) - use of activation code (AC)

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

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

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

- Use of AC.
The active test system 7 has received an Activation Code (AC) from the MNO 4 via any means, e.g. 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.

4. Download and install step 15
An eSIM profile download procedure 15 operation is performed between the test probe 6 and the SM-DP+ module 10 of the RSP platform 1 under test. In operation, test probe 6 maintains a reliable e2eHTTPs session over TCP/IP over LTE/EPS or fixed cable. Using the parameters EID and matching ID, the test probe 6 initiates the download of the required eSIM profile and identifies the bound profile package. The matching ID is empty if the profile is downloaded from the default SM-DP+ address.

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

In a further embodiment a smart phone may be used as test probe 6 .

The smartphone's eSIM RSP is performed similarly to the eSIM download procedure described above with respect to the eSIM card 5 of the test probe 6 . A smartphone is considered as a specific embodiment of the test probe 6, ie it acts as a test mobile device with the same user access interface to mobile applications.

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

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

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

The SIM multiplexer 16 provides geographical separation between 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 a SIM multiplexer 16 to either eSIM card 5 (eUICC) and SM-SR module 3 (for M2M devices, compare FIG. 1 above), or test probe environment 19 of test probe 6. The provided mobile connectivity will be used to bridge messages between SM-DP+ modules 10 (for smartphones and/or consumer IoT devices, compare FIG. 2 above). Each embodiment is described below with reference to FIG.

Verification of the eSIM RSP consists of two test sequence parts.
(a) The eSIM profile is provisioned and swapped from bootstrap to the target operator by confirming that the test probe has successfully reconnected to the network and comparing the new IMSI value with the previous value in the eSIM RSP. verify that
(b) Testing post-RSP network service assurance by using eSIMs 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 tests will not be described in further detail.

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

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

Such a cloud-based test system 7 is applied for eSIM RSP process verification (see Fig. 4) and also SMS over HTTP(s) over LTE/EPS and/or RAM (remote application management) to support

In FIG. 4 different embodiments of the test probe 6 are depicted, communicating via the core network interface or via the radio 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, the main 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 receipt of provisioning SMS-MT or SM-DP+ address in 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 a successful network reconnection with the newly provisioned eSIM profile,
- Disconnect from the network.

The triggering step and checking whether the ordered and triggered eSIM profile has been 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 the 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.

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

- No SMS (within a user-configured timeout period) or no Subscription Confirmation (AC) from SM-SR.
- HTTPs sessions are 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 automatically triggered RSP (compare with the embodiment described with respect to FIG. 2 above), the active test system 7 according to FIG. 4 preferably uses two interfaces for 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 should be customized according to the platform under test used by the customer.

The mobile interface part should behave the same as 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.

A 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 As with the manual scenario, a timeout parameter should be included, allowing the user to set a timeout for waiting for a provisioning trigger-SMS from the SM-SR module 3.

Additional parameters for interacting with the API (operation type, authentication to API, eSIM/eUICC ID (EID) - ID of requested eSIM profile for which provisioning is required, IMSI) should be included. A complete list of parameters can be specified based on a particular RSP Platform API document.

Key Parameter Indicators The following KPIs should be provided.
- the IMSI at the start of the test;
- the IMSI at the end of the test;
- IP session lifetime from PCAP file - IP session lifetime between eSIM card 5 and SM-SR module 3 - This is the time taken to complete RSP operations such as profile download, enable, disable etc. reflect.
- IP address of SM-SR module 3 or SM-DP+ module 10 from the PCAP file.
- IP session initiation lifetime - if possible - between receipt of provisioning SMS or receipt of AC and initiation of IP session (TCP SYN from mobile to RSP Platform 1 (SM-SR or SM-DP+)) Measured as lifetime.
- total provisioning lifetime - time from sending API1 trigger to completion of IP session.
- SMS Receiving Lifetime - Lifetime after sending the API trigger until the provisioning SMS is received.
- subscription lifetime - 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.

- No SMS (within a user-configured timeout period) or no Subscription Confirmation (AC) from SM-SR.
- HTTPs sessions are 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;
- The 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, to automatically order the required sequence of eSIM profiles according to an 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 install 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 verification of a remote eSIM provisioning (RSP) process, comprising:
ordering (8; 13) an eSIM profile from the RSP platform (1) under test;
triggering (9; 14) the download of the eSIM profile ordered from the RSP platform (1);
downloading (9a; 15) the triggered eSIM profile from the RSP platform (1) to the target eSIM of the test probe (6) or eUICC (5) via an over-the-air (OTA) interface;
confirming whether the order and the triggered eSIM profile were downloaded correctly;
A test method, wherein said test probe (6) is configured to simulate an M2M (Machine to Machine) device. A test method for verification of a remote eSIM provisioning (RSP) process, comprising:
ordering (8; 13) an eSIM profile from the RSP platform (1) under test;
triggering (9; 14) the download of the eSIM profile ordered from the RSP platform (1);
downloading (9a; 15) the triggered eSIM profile from the RSP platform (1) to the target eSIM of the test probe (6) or eUICC (5) via an over-the-air (OTA) interface;
confirming whether the order and the triggered eSIM profile were downloaded correctly;
said test probe (6) is configured to simulate smart phones and/or consumer IoT devices,
a test scenario to be tested using the test method includes a user side represented by the test probe (6);
A testing method, wherein said triggering (9; 14) and said confirming steps are initiated from said user side. 3. A testing method according to claim 1 or 2, characterized in that, prior to ordering, a subscription request (12) is sent from the test probe (6) to the order sending entity (4). 4. A testing method as claimed in any preceding claim, comprising automatically ordering a set of eSIM profiles according to an ordering schedule. 5. Any one of claims 1 to 4, characterized in that during triggering, the RSP platform (1) addresses the target eUICC (5) and sends a trigger SMS to the test probe (6). Test method described in section. The testing method according to claim 5, characterized in that the trigger SMS triggers an HTTPs session or a CAT_TP (Card Application Toolkit Transport Protocol) session. 7. The method according to any one of claims 1 to 6, characterized in that during triggering the test probe (6) establishes a PDN (Packet Data Network) connection to the gateway specified in the trigger SMS. test method. An active test system (7) for providing a test method according to any one of claims 1 to 7, comprising:
at least one test probe (6) containing at least one target eSIM or eUICC (5) with an initial working profile installed;
an interface to the RSP platform (1) for remotely providing an eSIM profile different from said initial working profile;
an OTA interface for providing communication between said RSP platform (1) and said test probe (6);
An active test system (7), characterized in that it comprises: Said RSP platform (1) comprises:
a subscription manager data preparation (SM-DP) module (2);
9. 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. Said RSP platform (1) comprises:
a Subscription Manager Data Preparation+ (SM-DP+) module (10);
The active test 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). Claim 8, characterized in that it comprises a SIM multiplexer (16) containing a SIM server (17) and a number of eUICCs (5), said SIM server (17) being in signal connection with said test probes (6). 12. An active test system according to any one of claims 1-11. Active test system according to any one of claims 8 to 11, characterized in that it comprises a cloud-based server (20).

Images