CN114467325A

CN114467325A - Test methods for verification of RSP processes and active test systems providing the test methods

Info

Publication number: CN114467325A
Application number: CN202080067921.3A
Authority: CN
Inventors: 胡仕成; 戈斯·塔拉加诺夫; 弗拉德·布拉图
Original assignee: Xigaosi Co ltd
Current assignee: Xigaosi Co ltd
Priority date: 2019-09-27
Filing date: 2020-09-11
Publication date: 2022-05-10
Also published as: KR20220071238A; DE102019214919A1; EP4035438A1; AU2020354339B2; JP7413516B2; JP2023501874A; AU2020354339A1; WO2021058305A1

Abstract

In a test method for verification of an eSIM remote provisioning process, an eSIM profile is subscribed (8) from an RSP platform under test (1). Thereafter, downloading of the subscribed eSIM profile from the RSP platform (1) is triggered (9). The triggered eSIM profile is then downloaded (9a) from the RSP platform (1) to the target eSIM or eUICC (5) in the test probe (6) via the air interface. And then verifies whether the subscribed, triggered, and downloaded eSIM configuration file is correct. The test probe (6) may be configured to simulate an M2M device, a smartphone, and/or a consumer IoT device. The testing methods enhance the ability of the testing system to test mobile networks using eSIM remote configuration while continuously providing network connectivity and services through eSIM exchanges.

Description

Test methods for verification of RSP processes and active test systems providing the test methods

The present application claims priority from the german patent application DE 102019214919.7, the contents of which are incorporated herein by reference.

Technical Field

The present invention relates to a test method for verification of an eSIM remote configuration (RSP) procedure. In addition, the invention relates to an active test system providing such test methods.

Background

Test systems for mobile networks are known, for example, from US 10,097,981B 1, US 7,831,249B 2 and from WO 2004/049746 a 1. US 2019/0075448 a1 discloses the monitoring of embedded subscriber identity modules. WO 2016/013827 a1 discloses a method and apparatus for embedded SIM configuration. WO 2017/013127 a1 discloses a method for detecting remote access to a universal integrated circuit card.

Disclosure of Invention

It is an object of the present invention to enhance the ability of such test systems to test mobile networks using eSIM remote configuration.

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

Embedded universal integrated circuit cards (euiccs) or embedded sims (esims) are commonplace and are used for consumer internet of things (IoT) and machine-to-machine (M2M) devices to identify devices for mobile networks. In addition, esims will also be introduced for smart phones. esims are next generation SIM technology intended to replace physical cards with a combination of hardware and software, providing the ability to remotely switch devices between carriers. The techniques allow one device to host multiple connectivity providers (called profiles) and be designed for all classes of mobile devices, including smartphones and IoT modules.

The hardware portion of the eUICC card is manufactured primarily in an embedded form factor (MFF 2). The software components of the eSIM can be downloaded remotely and installed to the eUICC card. This process is referred to as eSIM remote configuration (RSP). The term eUICC or eSIM referred to in this patent refers to a "personalized" eUICC or eSIM as a software part of an eUICC to be downloaded. The eUICC is not easily accessed or replaced, is not intended to be removed or replaced in the device, and enables securely changing subscriptions.

GSMA has specified the following standards for eSIM configuration for M2M devices and consumer devices, respectively:

GSMA sgp.02 v4.2, 07 th 7 month 2020 embedded SIM remote configuration architecture specification

GSMA SGP.22 v2.3, year 2020, 6.05 days-RSP technical Specification

GSMA sgp.02 v4.0, 2019, month 2, day 25-embedded SIM remote configuration architecture.

The testing method and active system according to the present invention covers the testing and verification aspects when esims are provided to those eSIM-capable devices on behalf of a mobile operator or a third party.

Additional criteria specified by GSMA are:

GSMA sgp.23 RSP test specification version 1.7, month 7 and day 07, 2020.

Another standard specified by GSMA is:

GSMA sgp.24 RSP compliance process version 2.2, 9 months and 17 days 2019.

Multiple profiles can be downloaded and installed on the eUICC. The profile is associated with the operator, is a combination of file structures, data, and applications to be configured or presented on the eUICC, and, when enabled, allows access to specific mobile network infrastructure. Only one configuration file can be activated and run at a time. An eSIM RSP platform on behalf of an operator or third party can enable, disable, delete, or switch each profile on the eUICC.

The test method and the active test system apply an end-to-end test method, and the end-to-end test method verifies the mobile network connection and service in the context of the RSP process. The test method verifies RSP in a test system and tests mobile network connections using a SIM configured in a national or international service network according to the following standards:

-GSMA sgp.02 RSP for M2M devices;

-GSMA sgp.22 RSP of consumer devices.

An eSIM profile is a personalized software part of an embodied universal integrated circuit card (eUICC) (i.e., software assigned to an assigned user). The software includes at least one user profile. The RSP process may be for consumer devices (e.g., smartphones, smartwatches, wearable devices) and/or may be for machine-to-machine (M2M) devices. Specifically, the test method verifies mobile network connectivity and services. eSIM profiles can be subscribed to from the RSP platform manually or automatically. The sender of the order may be a Mobile Network Operator (MNO). Prior to subscription, RSP procedures may be initiated. During the testing method, a previous working profile or boot profile installed on the eUICC at the beginning may be disabled and the downloaded eSIM profile enabled. The checking may be performed by monitoring for the occurrence of at least one failed criterion. The fail criteria can be satisfied based on RSP platform connection timeouts and/or network attachment timeouts and/or based on subscriptions, triggers, and/or expected structures of downloads, and/or based on reattachment timeouts for devices having downloaded updated eSIM profiles.

Network connectivity and services are continuously provided through eSIM exchanges during the testing method.

The test method of claim 1, the test probe simulating an M2M device.

The test probe can support a large frequency spectrum over licensed bands, including 2G radio frequencies, 3G radio frequencies, 4G radio frequencies, and 5G radio frequencies. Such configurations of the test probe allow for the deployment of Short Message Service (SMS) as an efficient means of communication between a remote RSP platform that provides eSIM profiles that are to be configured by download and the test probe. The test probe may support sms (smsona) over non-access stratum (NAS) for 4G technologies and 5G technologies. The test probe may support sms over internet protocol (smsoip) for IP Multimedia Subsystem (IMS) technology. The test probe may be configured to adapt itself to select the correct communication protocol, i.e., to adapt the communication protocol required for eSIM verification of the respective RSP platform, depending on the communication technology environment. The test probe may be configured to communicate with an industrial IoT application. An example of such industrial IoT applications is machine long term evolution (LTE-M). Another example is narrowband internet of things (NB-IoT). The test probe may be configured to communicate with at least one Low Power Wide Area Network (LPWAN) radio technology standard.

The testing method of claim 2, the test probe emulating a smartphone and/or a consumer IoT device.

The test probe may be configured to test user transaction related test criteria, i.e. to test the RSP validation process at the user level. During such user-plane testing, a test probe may initiate a quality testing step by examining quality parameters, which may be defined by Key Parameter Indicators (KPIs). The KPIs may be access failure rate, access time, cutoff rate, download start duration, download availability rate, etc. The quality parameters can be checked in real time by the test probe. In this regard, the test probe may be configured to simulate real user behavior of a user of the smartphone and/or the consumer IoT device.

Examples of consumer IoT devices are tablets, smart watches, wearable computers (e.g., smart glasses), home voice controllers, doorbell cameras, smart locks, smart light switches, air quality monitors, and the like.

The sending entity of the subscription request of claim 3, being able to use a proxy of the mobile network operator. The subscription request may include a link or code. During the triggering step, the sending entity of the order may confirm the subscription request from the test profile. The confirmation can trigger the test probe to find a download address for downloading the subscribed eSIM configuration file. The trigger option may use a subscription manager data preparation (SM-DP +) default address stored at the target eSIM, may use a root subscription manager discovery server (SM-DS) to discover a Fully Qualified Domain Name (FQDN) for the SM-DP + address, or may use an activation code containing the SM-DP + address.

The order schedule of claim 4, can comprise a number of eSIM profiles to be generated by the RSP platform, can comprise one or more IMSI values or IMSI ranges, can comprise one or more ICCID values or ICCID ranges, can comprise one or more non-personalized profile types, or can comprise information about one target eSIM or about multiple target esims, such as eUICC-id (eid). The EID may be bound to a predetermined eSIM profile id (iccid).

The test method of claim 5 has demonstrated its efficiency.

This applies in particular to the test method according to claim 6. The HTTP session may establish an end-to-end (e2e) connection between the target eUICC and the RSP platform through a Transport Layer Security (TLS) protocol. The test probe may establish a Bearer Independent Protocol (BIP) channel for communication between the test probe and the target eUICC. The CAT _ TP session may include two commands, i.e., a request for e2e CAT _ TP link and/or data open to the BIP channel. These HTTP sessions or CAT _ TP sessions can be maintained during the test method, especially over LTE/EPS.

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

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

The active test system of claim 9 is particularly suitable for M2M applications. A subscription manager data preparation (SM-DP) module can receive the order, and a subscription manager secure routing (SM-SR) module can manage the personalized eSIM profile.

The order module of claim 10 may communicate with the RSP platform through a network interface or through 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 the appropriate SM-DP + address of the test probe.

The signal connection between the SIM server and the test probe according to claim 12 can be established over a LAN/WAN. The SIM multiplexer of claim 12, providing geographic separation of a test probe from a target eUICC/eSIM.

The cloud-based system of claim 13 enables comfortable and cost-effective client connections.

Drawings

Embodiments of the present invention will be described hereinafter with reference to the accompanying drawings. These drawings show:

fig. 1 schematically illustrates the main components of an active test system for providing a test method of validation of an eSIM remote configuration (RSP) process for a machine-to-machine (M2M) device;

FIG. 2 is a schematic diagram of another embodiment of an active test system similar to FIG. 1 that provides a corresponding RSP verification process test method for a consumer device (e.g., a smartphone or a different consumer IoT device);

FIG. 3 is a test system configuration including a SIM multiplexer; and is

FIG. 4 is a test system configuration communicating through the cloud.

Detailed Description

A. Testing eSIM RSP for M2M

The eUICC remote provisioning and management platform (or called SIM remote provisioning (RSP) platform 1) is responsible for eSIM remote provisioning. The eUICC remote configuration and management platform comprises two entities, a subscription manager data preparation (SM-DP) module 2 and a subscription manager secure routing (SM-SR) module 3, which are securely connected to each other. The SM-DP module 2 represents a Mobile Network Operator (MNO) 4. The SM-SR module 3 establishes a secure and authenticated transmission channel to the personalized software part of the embedded universal integrated circuit card (eUICC) or embedded sim (esim). The software portions may be assigned to assigned users or connected devices, particularly as part of the internet of things (IoT). The SM-SR module 3 further manages at the eUICC the personalized profiles to be downloaded or switched over to each other.

The eSIM card 5 of any suitable form factor is inserted into a test probe 6, the test probe 6 emulating an M2M device according to one embodiment, and the test probe 6 emulating a smartphone and/or consumer IoT device according to another embodiment. 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 configuration file to be downloaded from the RSP platform under test 1. The inserted eSIM card 5 contains a currently working profile that is different from the desired profile to be subscribed and configured.

The test scenario to be tested with the test method comprises a user side represented by the test probe 6.

Fig. 1 shows three steps of "subscribe-trigger-download" of a test program to verify the eSIM configuration file required for download.

1. Subscription eSIM configuration file (subscription step 8)

RSP for M2M devices is initiated by a representative of MNO 4 (representational) to subscribe to a particular eSIM profile for an identified target eUICC at SM-DP module 2 of RSP platform 1. Two exemplary test scenarios are presented:

a) eSIM configuration files manually subscribed to at RSP platform 1 under test

A tester on behalf of MNO 4 will connect to the RSP platform 1 under test and manually send an eSIM download command 8 to the RSP platform 1, targeting the eSIM card in the test probe 6, and waiting for a configuration message from the RSP platform 1.

b) eSIM configuration file automatically subscribed at RSP platform 1 under test

The active test system 7, on behalf of MNO 4, interacts with the RSP platform under test 1 through a Web interface or Application Programming Interface (API) with a subscription token for subscribing to one or more eSIM profiles. The RSP process may be initiated automatically. The test system 7 is waiting for a configuration message from the RSP platform 1. The order token may include:

the number of eSIM profiles to be generated by SM-DP module 2;

-a value or range of International Mobile Subscriber Identity (IMSI);

-a value or range of integrated circuit card id (iccid);

-a non-personalized profile type;

information about the target eUICC, e.g. eUICC-id (eid).

2. Triggering step 9

The SM-SR module 3 in the RSP platform under test 1 triggers the download of the required eSIM configuration file via the over-the-air (OTA) interface to the target eSIM card 5 in the test probe 6. The SM-SR module 3 sends a trigger SMs addressing the eSIM card 5. When a test probe 6 with a current profile on the eSIM card 5 attaches to a mobile network (e.g., EPS attach with a 4G/5G network or GPRS attach with a 2G/3G network), a trigger SMs sent by the SM-SR module 3 is delivered to the target eSIM card 5 via the test probe 6 and triggers an HTTP session or a card application toolkit transport protocol (CAT _ TP) session depending on eUICC support. Based on the Access Point Name (APN) encapsulated in the trigger SMS, the test probe establishes a Packet Data Network (PDN) connection to a specified gateway in the APN.

The test probe 6 receives and processes the trigger 9 for the eSIM card 5. If HTTP is used, the trigger SMS contains an HTTP session trigger command that causes an end-to-end (e2e) HTTP session based on the Transport Layer Security (TLS) protocol to be established between the eSIM card 5 and the SM-SR module 3 in the RSP platform 1. Under the HTTP session, the test probe 6 establishes a TCP/IP transport connection for the session towards the RSP platform 1 and a Bearer Independent Protocol (BIP) channel for communication between the test probe and the eSIM card 5.

If CAT _ TP is used, the trigger SMS contains the following two commands:

a request to establish an e2e CAT _ TP link between the eSIM card 5 and the SM-SR module 3;

data of the BIP channel opened 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 a Bearer Independent Protocol (BIP) channel for communication between the test probe 6 and the eSIM card 5.

3. Download and install step 9a

The operations of the required eSIM profile download and installation process are performed between the eSIM card 5 and the test probe 6 on the one hand and the eSIM card 5 and the RSP platform under test 1 on the other hand, and can be performed in four main steps:

a profile entity that creates a security domain for each required eSIM profile to be downloaded onto the eSIM card 5,

personalizing the entity with a first set of secure keys, referred to as key establishment,

download a required eSIM profile from the SM-DP module 2 and install the eSIM profile with Remote Application Management (RAM) onto the eSIM card 5,

enabling newly installed eSIM profiles and disabling working profiles previously used on the eSIM card 5, referred to as profile switching.

During operation, the test probe 6 maintains a reliable HTTP session or CAT _ TP session over the evolved packet system (LTE/EPS).

The triggering step and the step of checking whether the subscribed and triggered eSIM configuration file has been correctly downloaded are initiated from the user side (i.e., via the test probe 6).

B. Testing eSIM RSP for consumer devices

Further embodiments of active test systems are described with respect to fig. 2, which provide test methods for verification of RSP processes for smartphones or consumer IoT devices, respectively. The components and functions that have been discussed with respect to the embodiment shown in fig. 1 have the same reference numerals and are not discussed in detail.

The RSP platform 1 used in the testing of eSIM RSP for smart phones and/or consumer IoT devices consists of two parts: a subscription manager data preparation + (SM-DP +) module 10 and a subscription manager discovery server (SM-DS) module 11. The SM-DP + module 10 prepares a profile package, protects the profile package using a profile protection key, binds each protected profile package to a corresponding EID, and securely downloads the bound profile packages to the corresponding eSIM card 5. If the test probe 6 does not know the SM-DP + address, the SM-DS module 11 is required.

The eSIM card 5 is inserted into a test probe 6 that simulates or represents a user device. The test probe 6 is connected to an active test system 7 and is configured to receive a desired eSIM configuration file to be downloaded from the RSP platform under test 1. The inserted eSIM card 5 contains a currently working profile that is different from the profile to be subscribed and configured. To download the required eSIM configuration file from SM-DP + or discover the SM-DP + address through SM-DS module 11, the test probe uses the HTTP security protocol.

Fig. 2 shows four steps "request-subscribe-trigger-download" of a test procedure to verify the eSIM profile required for download.

1. Requesting 12 subscriptions

The test system 7 initiates the RSP procedure and requests a subscription.

2. Subscribing to 13eSIM profiles

MNO 4 subscribes to the requested eSIM profile at SM-DP + module 10.

The prepared eSIM configuration file is securely stored at the SM-DP + module 10. The EID is bound to an eSIM profile id (iccid).

3. Triggering 14-subscription confirmation

The MNO 4 confirms the subscription to the test probe 6, which triggers the test probe 6 to find the appropriate address to download the required eSIM profile. The process is operator dependent and can be done by accessing a URL, by using a Local Profile Assistant (LPA), or by a local function in the device firmware. For example, there are three options to trigger the test probe 6 representing a consumer device or smartphone.

Using the default SM-DP + address stored in the eSIM card 5

Discovery of SM-DP + Address (FQDN) Using root SM-DS

Using the Activation Code (AC)

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

-using a default SM-DP + address

This option is typically used as a power-on profile discovery. The test probe 6 retrieves the default SM-DP + address that is pre-configured and stored in the eSIM card 5.

Using root SM-DS for profile discovery

The test probe 6 retrieves the SM-DC address previously configured and stored in the eSIM card 5, establishes a TLS connection with the SM-DC server, establishes mutual authentication with the SM-DC over HTTP, and transmits an event request without an event Id. The SM-DC replies to the test probe 6 with an AC (SM-DP + address + matching ID), i.e. an activation code, with an event request.

Using AC

The active test system 6 has received the activation code from the MNO 4 by any means, for example by email or API. The AC comprises at least:

-SM-DP + Address

AC token (match Id)

The AC may be entered into the test probe 6 by manually typing or scanning a Quick Response (QR) code.

4. Download and install step 15

The operation of the eSIM configuration file download program 15 is performed between the test probe 6 of the RSP platform 1 under test and the SM-DP + module 10. During operation, the test probe 6 maintains a reliable e2e HTTP session over TCP/IP via LTE/EPS or fixed cable. The test probe 6 initiates the required eSIM profile download using the parameter EID and the matching ID to identify the bound profile package. If the configuration file is downloaded from the default SM-DP + address, the matching ID is null.

After receiving the entire bundle of binding profiles, the test probe 6 initiates installation of the required eSIM profiles on the eSIM card 5 in a secure and protected manner.

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

The execution of the eSIM RSP in the smartphone is similar to the eSIM download process described above for the eSIM card 5 in the test probe 6. The smartphone is considered to be a specific embodiment of the test probe 6, i.e. to act as a test mobile device with the same user access interface to the mobile application.

In the case of an enterprise smartphone, the EID list is used for the required eSIM profile order. The above-described method of address discovery using the root SM-DS is applied in the triggering step 14.

In a further embodiment shown in fig. 3, the active test system comprises a SIM multiplexer 16. The SIM multiplexer 16 includes a SIM server 17 and a plurality of eSIM cards 5. The SIM server 17 is in signal connection with the test probe 6, in this embodiment the test probe 6 comprises a SIM emulation module 18, said SIM emulation module 18 being in signal connection with a test probe environment 19, said test probe environment 19 may be implemented as a mobile handset or a smartphone.

The SIM emulation in the SIM emulation module 18 represents and behaves as a target eSIM or eUICC for the eSIM card 5.

The SIM multiplexer 16 allows for geographic separation of the test probe 6 from the eSIM card 5(eUICC) for multiple eSIM deployments and eSIM scheduling for subsequent deployments. The test system 7 using the SIM multiplexer 16 will bridge messages between the e-SIM card 5(eUICC) and either the SM-SR module 3 (compare fig. 1 above for M2M devices) or the SM-DP + module 10 (compare fig. 2 above for smartphones and/or consumer IoT devices) using the mobile connection provided by the test probe environment 19 of the test probe 6. A corresponding embodiment is described below with reference to fig. 4.

eSIM RSP validation consists of two sequential test parts.

a) The eSIM profile that has been configured and switched from bootstrap to the target operator is verified by checking whether the test probe successfully re-attaches to the network and by comparing the new IMSI value with the previous value of the eSIM RSP.

b) post-RSP web services assurance tests, such as HTTP download, Ping, SMS MO MT, and voice MO MT, are performed by using the configured eSIM in a test probe for basic mobile services. The post RSP web services assurance test is not described in further detail.

The test system may be a conventional server/client model based distributed test system. Recently, cloud-based test systems have been deployed in large numbers. The test probe may be connected to any 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 fig. 4).

The clouded test systems 7 are used for authentication of eSIM RSP processes (refer to fig. 4) and support SMS over HTTP and/or Remote Application Management (RAM) via LTE/EPS.

In fig. 4, different embodiments of a test probe 6 are depicted, said test probe 6 communicating via a core network interface or via a radio interface.

The RSP test program using the clouded test system 7 is the same as described above. A standard test sequence consisting of EPS attach and trigger SMS can be performed.

The main aspects regarding the verification of the manually triggered RSP procedure are discussed below.

A single-sided active test is performed. For such cases, the user starts the test and then manually triggers the RSP procedure from their configuration platform (client 21). The test sequence is as follows:

attach to the network (MNO 4, compare figures 1 and 2 above),

-waiting to receive a configured SMS-MT or SM-DP + address with an AC token,

wait until the eSIM configuration HTTP session between the eSIM card 5 and the RSP platform 1 (including the SM-SR module 3 or SM-DP +10) is completed,

waiting for a successful network re-attachment with the newly configured eSIM profile,

-disconnecting the network attachment.

The triggering step and the step of checking that the subscribed and triggered eSIM profile has been correctly downloaded start from the user side, i.e., via the test probe 6.

Inputting parameters

Standard test parameters should be included. In addition, a timeout parameter should be included so that the user can set a timeout for the time to wait for the configuration trigger SMs from the SM-SR module 3. The following table gives examples:

key Parameter Indicator (KPI)

The following KPIs should be provided:

the verification results may be recorded in a results file. The files may be in a Packet Capture (PCAP) format.

During RSP validation, the following fault criteria may be established:

no reception of SMs from SM-SR (during user-configured timeout period) or no reception of subscription confirmation (AC)

Unopened HTTP session between SIM emulation in eSIM card 5 or SIM emulation module 18 and RSP platform (SM-SR or SM-DP +)

The IMSI at the end is the same as the IMSI at the beginning

Network re-attach to new APN after unsuccessful IMSI change

In case of automatic triggering of RSP (compare the embodiment described above for fig. 2), the active test system 7 according to fig. 4 should use two interfaces for RSP:

a mobile interface to the RSP process itself

-a LAN interface for interacting with the API of the RSP platform 1 under test

This test sequence needs to be customized according to the platform under test used by the customer.

The mobile interface part should have the same behavior as the manual trigger scenario discussed above:

attached to the network (MNO 4, compare figures 1 and 2 above)

-waiting for configuration trigger SMS

Wait until the HTTP session between the eSIM card 5 and the RSP platform 1(SM-SR module 3 or SM-DP +10) is completed,

-disconnecting the network attachment.

The LAN interface is used to send API commands to the configuration platform 21. These commands should be user configurable, such as downloading a configuration file, deleting a configuration file, or activating a configuration file.

Inputting parameters

As with the manual scenario, a timeout parameter should be included so that the user can set a timeout for the time to wait for the configuration trigger SMs from the SM-SR module 3.

Additional parameters for interacting with the API need to be included, such as operation type, API authentication, eSIM/EUICC ID (EID) -the ID, IMSI of the desired eSIM profile that needs to be provisioned. The complete parameter list may be specified based on the specific RSP platform API document.

Index of key parameter

The following KPIs should be provided:

IMSI at the beginning of the test

IMSI at the end of the test

IP session duration from PCAP file-duration of IP session between eSIM card 5 and SM-SR module 3-this will reflect the time taken to complete RSP operation, e.g. profile download, enable, disable

IP Address of SM-SR Module 3 or SM-DP + Module 10-from PCAP File

IP session start duration-if possible-measured as the duration between receiving the configuration SMS or receiving the AC and the IP session start (TCP SYN (SM-SR or SM-DP +) from the mobile device to the RSP platform 1)

Total configuration duration-duration from sending API 1 trigger to completion of IP session.

SMS receive duration-duration from sending API trigger to receiving configuration SMS

Subscription duration-duration from subscription request to subscription confirmation

A PCAP file may be provided as a result file.

During RSP validation, the following fault criteria may be established:

no reception of SMs from SM-SR (during user configured timeout) or no reception of subscription confirmation (AC)

The IMSI at the end is the same as the IMSI at the beginning

Inability to access the RSP platform through API

To automatically subscribe to a desired sequence of eSIM profiles according to a subscription schedule, the active test system may further include a subscription module, which may be part of the test probe 6.

Claims

1. A testing method for verification of an eSIM remote configuration "RSP" procedure, the testing method comprising the steps of:

-subscribing (8; 13) to an eSIM profile from the RSP platform under test (1);

-triggering (9; 14) a download of the subscribed eSIM profile from the RSP platform (1);

-downloading (9 a; 15) the triggered eSIM profile from the RSP platform (1) to a target eSIM or eUICC (5) in a test probe (6) via an over-the-air "OTA" interface;

-checking whether the subscribed and triggered eSIM profile has been downloaded correctly,

-wherein the test probe (6) is configured to simulate a machine-to-machine "M2M" arrangement.

2. A testing method for verification of an eSIM remote configuration "RSP" process, the testing method comprising the steps of:

-subscribing (8; 13) to an eSIM profile from the RSP platform under test (1);

-wherein the test probe (6) is configured to emulate a smartphone and/or a consumer IoT device,

-wherein a test scenario to be tested with the test method comprises a user side represented by the test probe (6),

-wherein the triggering step (9; 14) and the checking step are initiated from the user side.

3. A testing method according to claim 1 or claim 2, wherein a subscription request (12) is sent from the testing probe (6) to a sending entity (4) of the order prior to the subscription.

4. A testing method according to claim 1-3, wherein the method comprises automatically subscribing to a sequence of eSIM profiles according to an order schedule.

5. The test method according to one of claims 1 to 4, wherein during the triggering, the RSP platform (1) sends a trigger SMS to the test probe (6) addressing the target eUICC (5).

6. The test method according to claim 5, wherein the trigger SMS triggers an HTTP session or a card application toolkit transport protocol "CAT _ TP" session.

7. Test method according to one of claims 1 to 6, wherein during a trigger the test probe (6) establishes a packet data network "PDN" connection to a designated gateway in the trigger SMS.

8. An active test system (7) providing a test method according to one of claims 1 to 7, the active test system having:

-at least one test probe (6) comprising at least one target eSIM or eUICC (5) having an installed initial working profile;

-an interface to an RSP platform (1) for remotely configuring an eSIM profile different from the initial working profile;

-an OTA interface for providing communication between the RSP platform (1) and the test probe (6).

9. The active test system according to claim 8, wherein the RSP platform (1) comprises:

-a subscription manager data preparation "SM-DP" module (2);

-a subscription manager secure routing "SM-SR" module (3).

10. The active testing system of claim 8 or claim 9, characterized by a subscription module for automatically subscribing to a sequence of eSIM profiles according to an order schedule.

11. The active test system according to one of claims 8 to 10, wherein the RSP platform (1) comprises:

-a subscription manager data preparation + "SM-DP +" module (10);

-a subscription manager discovery server "SM-DS" module (11).

12. Active test system according to one of the claims 8 to 11, further comprising a SIM multiplexer (16), said SIM multiplexer (16) comprising a SIM server (17) and a plurality of euiccs (5), said SIM server (17) being in signal connection with said test probes (6).

13. The active test system according to one of the claims 8 to 11, further comprising a cloud-based server (20).