RU2791001C1 - Testing method for checking the process of remote initialization of embedded sim cards and an active testing system that provides such a testing method - Google Patents

Abstract

FIELD: wireless networks.

SUBSTANCE: invention relates to wireless networks, namely to testing the process of remote initialization of embedded SIM cards (eSIM), when eSIM cards for eSIM-supporting devices are provided by a mobile operator or a third party. To test the eSIM remote initialization process, an eSIM profile is ordered (8) from the tested RSP platform (1). Then the ordered eSIM profile is downloaded (9) from the RSP platform (1). Then the running eSIM profile is loaded (9a) from the RSP platform (1) via the wireless interface to the target eSIM or eUICC (5) in the test probe (6). Then the correctness of the ordered, launched and loaded eSIM profile is checked. The test probe (6) can be made with the ability to simulate an M2M device, a smartphone and/or an IoT consumer device. This method for testing expands the capabilities of the system for testing mobile networks with remote initialization of eSIM, while network connectivity and services are continuously provided by alternating loading of eSIM.

EFFECT: ensuring the possibility of checking RSP (remote initialization of eSIM) in the testing system and the possibility of connecting to a mobile network using a SIM card provided in a national or international service network.

13 cl, 4 dwg, 2 tbl

Description

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

The invention relates to a testing method for checking the process of remote provisioning of embedded SIM cards (eSIMs). In addition, the invention relates to an active testing system providing such a testing method.

Test systems for mobile networks are known, for example, from the following documents: US 10,097,981 B1, US 7,831,249 B2 and WO 2004/049746 A1. US 2019/0075448 A1 discloses the monitoring of an embedded Subscriber Identity Module (i.e. embedded SIM card, eSIM). WO 2016/013827 A1 discloses a method and apparatus for initializing a Subscriber Identity Module (SIM). WO 2017/013127 A1 discloses a method for remote access detection of a Universal Integrated Circuit Card (UICC).

The aim of the invention is to enhance the capabilities of such a mobile network testing system with eSIM remote provisioning.

This goal is achieved by the testing method with the characteristics of claims. 1 and 2 of the claims, and a testing system, with the features of paragraph 7 of the claims.

Embedded Universal Integrated Circuit Cards (eUICCs) or Embedded Subscriber Identity Modules (eSIMs) are widely used in Internet of Things (IoT) and machine-to-machine (M2M) devices to identify a device in a mobile network. In addition, eSIMs are also being introduced into smartphones. eSIM is the next generation of SIMs designed to replace physical cards with a combination of hardware and software that allows you to switch devices remotely between carriers. This technology allows one device to be the master of many connection providers (known as "profiles") and provides the ability to use the full range of mobile devices, including smartphones and IoT modules.

The eUICC hardware is mostly embedded (MFF2). The eSIM software can be remotely downloaded and installed on the eUICC card. This process is called Remote eSIM Provisioning (RSP). The term eUICC or eSIM as used in this application refers to a "personalized" eUICC, or eSIM as part of an eUICC, to be downloaded. The eUICC is not easily accessible or replaceable, cannot be removed or replaced on the device, and allows for secure change of subscriptions.

The Global System for Mobile Communications Alliance (GSMA) has set the following standards:

- GSMA SGP.02 v4.2, July 07, 2020 - Remote Provisioning Architecture for Embedded SIM Card - Datasheet,

- GSMA SGP.22 v2.3, June 05, 2020 - RSP Technical Specification,

- GSMA SGP.02 v4.0, February 25, 2019 - Embedded SIM Remote Provisioning Architecture

to prepare eSIM for M2M devices and consumer devices, respectively

The proposed method and active system cover testing and verification aspects when eSIM cards for these eSIM-enabled devices are provided by a mobile operator or a third party.

The GSMA standard is also

- GSMA SGP.23 RSP test specification, version 1.7, July 07, 2020

Another GSMA standard is

- GSMA SGP.24 RSP Compliance Process, Version 2.2, September 17, 2019

Several profiles can be downloaded and installed on the eUICC. A carrier associated profile is a combination of file structure, data and applications to be provisioned or presented on the eUICC that, when enabled, provides access to a specific mobile network infrastructure. Only one profile can be activated and work at a time. Each profile on the eUICC can be managed to enable, disable, delete, or switch from one to another using the eSIM RSP platform on behalf of an operator or a third party.

The proposed method and system uses end-to-end testing, which verifies mobile network connectivity and services in the context of the RSP process. The test method checks the RSP in the test system and the ability to connect to a mobile network using a SIM card provided in a national or international service network in accordance with

- GSMA SGP.02 RSP for M2M devices,

- GSMA SGP.22 RSP for consumer devices.

An eSIM profile is a personalized piece of software, i.e. software for a designated user of an Embedded Universal Integrated Circuit Card (eUICC). Such software includes at least one user profile. The RSP process can be used for consumer devices, such as smartphones, smart watches, wearable devices, and/or Machine to Machine (M2M) devices. The test method checks, in particular, the connection to the mobile network and services. Ordering an eSIM profile on the RSP platform can be done manually or automatically. The sender of the order can be a mobile network operator (MNO). An RSP process can be initiated before ordering. The test method may disable the previous work profile or boot profile originally installed on the eUICC and enable the downloaded eSIM profile. Verification may be performed by monitoring the occurrence of at least one failure criterion. Such failure criteria may be met based on RSP connection timeout and/or network connection timeout and/or expected ordering, firing, and/or loading pattern and/or retry timeout. connecting a device with an updated eSIM profile loaded.

In the proposed method, network connectivity and services are continuously provided by eSIM switching during testing.

In the method of claim 1, the M2M device is simulated using a test probe.

The test probe can support a wide range of licensed bands, including 2G, 3G, 4G, and 5G radio frequencies. This implementation of the test probe allows the deployment of Short Message Service (SMS) as an efficient way of communication between a remote RSP providing an eSIM profile and a test probe where the eSIM profile is to be initiated by download. The test probe can support SMS over NAS (No Access Layer) (SMSoNAS) for 4G and 5G technologies. The test probe can support SMS over Internet Protocol (SMSoIP) for IP Multimedia Subsystem (IMS) technology. The test probe can be configured to adapt to select the correct communication protocol depending on the communication technology environment, i.e. to adapt the required communication protocol to test the eSIM of the corresponding RSP platform. The test probe can be configured to communicate with industrial IoT applications. An example of such industrial IoT applications is the Long Term Evolution for Machines (LTE-M) standard. Another example is the 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.

In the method of claim 2, the test probe simulates a smartphone and/or consumer IoT device.

The test probe may be configured to test test criteria associated with a user transaction, ie to test a user-level RSP validation process. During such a user-level test, the test probe may initiate quality test stages by checking quality parameters, which may be determined by key parameter indicators (KPIs). These KPIs can be access failure rate, access time, cutoff ratio, download start duration, download availability ratio, etc. Such quality parameters can be tested with a real-time test probe. In this respect, the test probe may be configured to mimic the actual behavior of a smartphone user and/or consumer IoT device.

Examples of consumer IoT device are tablet, smart watch, laptop computer, smart glasses, home voice controller, doorbell camera, smart lock, smart light switch, air quality monitor, etc.

The sender of the subscription request in claim 3 may use the proxy of the mobile network operator. The subscription request may include a link or a code. During the launch phase, the order submitter can approve the subscription request from the test profile. The confirmation may launch a test probe to look for a download address to download the ordered eSIM profile. The launch function can use the Subscription Manager Data Provisioning Address (SM-DP+) stored on the target eSIM by default, can use the Subscription Manager Root Discovery Server (SM-DS ) to discover the FQDN of the SM-DP+ address, or use an activation code, containing the SM-DP+ address.

The order schedule in claim 4 may include a number of eSIM profiles to be generated by the RSP platform, include an IMSI value, or IMSI values, or an IMSI range, include an ICCID value, or ICCID values, or an ICCID range, include an anonymous profile type, or anonymized profile types or include information about the target eSIM or target eSIMs, such as EID (eUICC-ID). The EID can be tied to an ordered eSIM Profile Identifier (ICCID).

The method according to claim 5 of the claims has proved its effectiveness.

This is particularly applicable to the method according to claim 6 of the claims. An HTTP session can establish an end-to-end connection (e2e) over Transport Layer Security (TLS protocol) between the target eUICC and the RSP. The test probe may establish a BIP (Bear Independent Protocol) channel for communication between the test probe and the target eUICC. A CAT_TP session may include two commands, i.e. a request for an e2e CAT_TP link and/or data to open a BIP channel. Such an HTTPs session or a CAT_TP session may be supported in the method, in particular via LTE/EPS.

In the method according to claim 7, the identification of the gateway can be performed via an access point name (APN) specified, in particular, in the triggering SMS message.

The advantages of the system according to claim 8 correspond to those mentioned above in relation to the testing method. The test probe can be implemented as a smartphone.

The system of claim 9 is particularly suitable for an M2M application. The Subscription Manager Data Preparation Engine (SM-DP) can receive orders and the Subscription Manager Secure Routing Engine (SM-SR) can manage personalized eSIM profiles.

The order module in claim 10 may interact with the RSP platform via a web interface or via an application program interface (API).

The RSP platform in claim 11 is particularly suitable for smartphones and/or consumer IoT devices. The SM-DP+ module can manage personalized eSIM profiles. The SM-DS module can identify the appropriate SM-DP+ address for the test probe.

The signaling connection between the SIM server in claim 12 and the test probe can be established via LAN/WAN. The SIM multiplexer in claim 12 provides for geographic separation of the test probe and target eUICC/eSIM cards.

The cloud system according to claim 13 provides a convenient and cost-effective client connection.

Further, with reference to the attached drawings (drawings), embodiments of the invention are described.

In FIG. 1 schematically depicts the main components of an active test system for implementing a test method for testing an eSIM remote initiation (RSP) process for a Machine to Machine (M2M) device.

In FIG. 2 is schematically illustrated, similarly to FIG. 1, another embodiment of an active testing system that implements an appropriate method for testing an RSP validation process for a consumer device such as a smartphone or various IoT consumer devices.

In FIG. 3 illustrates a test system including a SIM multiplexer.

In FIG. 4. Illustrated is a test system that communicates through the cloud.

A. Test eSIM RSP for M2M

The eUICC remote provisioning and management platform, known as the Remote SIM Provisioning Platform (RSP) 1, is responsible for eSIM remote provisioning. It boils down to two entities, the Subscription Manager Data Preparation Module (SM-DP) 2 and the Subscription Manager Secure Routing Module (SM-SR) 3, which are securely coupled to each other. The SM-DP module 2 acts on behalf of the mobile network operator (MNO) 4 . The SM-SR module 3 establishes a secure and authenticated transport channel to the personalized embedded universal integrated circuit card (eUICC) or embedded SIM card (eSIM) software side. Such a piece of software may be assigned to a dedicated user or connected device, particularly as part of the Internet of Things (IoT). Module 3 SM-SR additionally manages personalized profiles in the eUICC for loading or switching from one to another.

The test probe 6, which simulates an M2M device in one embodiment and a smartphone and/or consumer IoT device in the other, contains an eSIM card 5 of any suitable design. The test probe 6, which may be multivariate, is part of the active test system 7 and is configured to receive at least one required eSIM profile downloaded from the RSP under test 1. The installed 5 eSIM card contains a current work profile that is different from the required profile, which must be ordered and initialized.

The test scenario to be implemented using the proposed test method includes the user side represented by the test probe 6.

In FIG. 1 illustrates the "Order - Run - Download" three steps of the test procedures to verify that the required eSIM profile is loaded.

1. Order an eSIM profile (stage 8, order)

The RSP for the M2M device is initiated by the MNO 4 to order a specific eSIM profile for the identified target eUICC in the RSP 1 SM-DP module 2. Two illustrative test scenario examples are considered:

a) eSIM profile ordered manually on the tested platform 1 RSP

The tester on behalf of MNO 4 connects to the RSP under test 1 and manually sends an 8 eSIM download order to the RSP 1 based on the eSIMs in the test probe 6 and waits for the initialization message from the RSP 1.

b) eSIM profile automatically ordered on tested platform 1 RSP

The active test system 7 on behalf of the MNO 4 interacts with the RSP under test 1 via a web or application programming interface (API) with an order token to order one or more eSIM profiles. The RSP process can be initiated automatically. Test system 7 is waiting for an initialization message from RSP 1. An order token may contain:

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

- value(s) or range of International Mobile Subscriber Identity (IMSI),

- value(s) or range of integrated board identifier (ICCID),

- type(s) of non-personalized profile,

- target eUICC information, eg EID (eUICC-ID).

2. Stage 9, launch

SM-SR module 3 on RSP under test 1 initiates the download of the required eSIM profile via wireless interface to target eSIM card 5 in test probe 6. SM-SR module 3 sends a trigger SMS addressing eSIM card 5. When the test probe 6 with the current profile on the eSIM card 5 is connected to a mobile network (for example, an EPS connection in a 4G/5G network or a GPRS connection in a 2G/3G network), the triggering SMS message sent by the SM-SR module 3 is delivered via the test probe 6 to the target eSIM card 5 and initiates an HTTPs session or a CAT_TP (Card Application Toolkit Transport Protocol) session, depending on eUICC support. Based on the access point name (APN) encapsulated in the triggering SMS message, the test probe establishes a packet data network (PDN) connection to the gateway specified in the APN.

Test probe 6 receives and processes trigger 9 for eSIM card 5. If HTTPs is used, the triggering SMS contains an HTTP session start command that causes an end-to-end (e2e) HTTP session over TLS (Transport Layer Security) between eSIM card 5 and SM-SR module 3 on RSP platform 1. Under the HTTP session, the test probe 6 establishes a TCP/IP transport connection for the session with the RSP platform 1 and establishes a BIP (media independent protocol) channel for communication between the test probe and the eSIM card 5.

If CAT_TP is used, the triggering SMS contains two commands:

- request to establish an e2e CAT_TP link between eSIM card 5 and SM-SR module 3,

- data for opening a BIP channel between test probe 6 and eSIM card 5.

Similarly, within a CAT_TP session, test probe 6 establishes a UDP/IP connection for the session and establishes a BIP channel for communication between test probe 6 and eSIM card 5.

3. Download and install step 9a

Between the eSIM card 5 and the test probe 6 on the one hand and the RSP under test 1 on the other, a download and installation procedure for the required eSIM profile is carried out, which can be performed in four main steps:

- creation of a secure domain profile entity for each required eSIM profile loaded onto a 5 eSIM card,

- personalization of an entity with a first secure set of keys, called key generation,

- downloading the required eSIM profile from the 2 SM-DP module and installing the eSIM profile managed via Remote Application Management (RAM) on the 5 eSIM card,

- Enabling the newly installed eSIM profile and deactivating the previously used work profile on the 5 eSIM card, called profile switching.

During operation, test probe 6 supports a reliable HTTPs session or a CAT_TP session via the evolved software package (LTE/EPS).

The startup phase and the validation phase of the ordered and launched eSIM profile are initiated by the user, i.e. via test probe 6.

B. eSIM RSP Testing for Consumer Devices

With reference to FIG. 2 describes another embodiment of an active test system that provides a test method for validating an RSP process for smartphones or IoT consumer devices. The components and functions already discussed in connection with the embodiment illustrated in FIG. 1 have the same reference designations and are not discussed in detail again.

The RSP under test 1 for the eSIM RSP of smartphones and/or consumer IoT devices consists of two parts: a Subscription Manager Data Provisioning+ (SM-DP+) module 10 and a Subscription Manager Discovery Server (SM-DS) module 11 . The SM-DP+ module 10 prepares the profile packages, secures them with the profile security key, associates each secure profile package with the corresponding EID, and securely downloads these associated profile packages to the corresponding eSIM 5 card. SM-DS module 11 is required if the SM-DP+ address is unknown to test probe 6.

The eSIM card 5 is installed in the test probe 6 which simulates or is a consumer device. The test probe 6 is connected to the active test system 7 and configured to receive the required eSIM profile to be downloaded from the RSP under test 1 . The installed eSIM 5 contains the current work profile, which is different from the profiles that need to be ordered and initiated. The Test Probe uses secure HTTPs to download the required eSIM profiles from the SM-DP+ or discover the SM-DP+ address via the SM-DS Module 11.

In FIG. 2 illustrates an example of the "Request - Order - Run - Download" four step test procedures to verify that the required eSIM profile is loaded.

1. Subscription request, stage 12

Test System 7 initiates the RSP process and requests a subscription.

2. Order eSIM profiles, stage 13

MNO 4 orders the requested eSIM profile on SM-DP+ module 10.

The prepared eSIM profile is securely stored in the 10 SM-DP+ module. The EID is linked to the eSIM Profile Identifier (ICCID).

3. Launch, stage 14 - Subscription confirmation

The MNO 4 confirms the subscription to the test probe 6, which launches the test probe 6 to find a suitable address to download the desired eSIM profile. This procedure is carrier dependent and can be performed by accessing a URL, using the Local Profile Assistant (LPA) utility, or using the device's flashing feature. There are, for example, three options for launching test probe 6 representing consumer devices or a smartphone.

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

- Using Root SM-DS to Discover SM-DP+ Address (FQDN)

- Using an activation code (AC)

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

- Using default SM-DP+ address

This setting is often used to detect a profile on power up. The test probe 6 retrieves the default SM-DP+ address pre-configured and stored on the eSIM card 5.

- Using root SM-DS for profile discovery

Test probe 6 retrieves the SM-DC address pre-configured and stored on the eSIM card 5, establishes a TLS connection with the SM-DC server, establishes mutual authentication with the SM-DC over HTTPs, and sends an event request without an event ID. The SM-DC responds to an AC event request (= SM-DP+ address + corresponding ID), i.e. activation code to test probe 6.

- Using an activation code (AC)

The active test system 6 received an activation code in any way from the mobile operator 4, for example. via email or API. AS contains at least

- SM-DP+ address

- AC marker (corresponding identifier)

AC can be entered into test probe 6 by typing manually or by scanning a QR code (quick response).

4. Download and installation, stage 15

The eSIM profile loading step 15 procedure is performed between the test probe 6 and the SM-DP+ module 10 of the RSP under test 1 . During operation, test probe 6 maintains a reliable e2e HTTPs session over TCP/IP over LTE/EPS or fixed cables. The test probe 6 initiates the download of the desired eSIM profile with the parameters EID and match ID to identify the associated profile package. The match ID is empty if the profile is loaded from the default SM-DP+ address.

After receiving the entire associated profile package, the test probe 6 initiates the installation of the required eSIM profile on the eSIM card 5 in a safe and secure manner.

In another embodiment, a smartphone is used as test probe 6.

The eSIM RSP in the smartphone is performed in a similar manner to the eSIM boot procedure described above for the eSIM card 5 in the test probe 6. The smartphone is considered as a specific variant of the test probe 6, i.e. it acts as a test mobile device with the same user access interface to mobile applications.

For corporate smartphones, the EID list is used to order the required eSIM profile. The approach described above for using the root SM-DS for address discovery is applied in the startup step 14 .

In yet another embodiment, illustrated in FIG. 3, the active test system includes 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, which in this embodiment includes a SIM emulation module 18, which is in signal connection with the test probe environment 19, which can be in the form of a mobile phone or smartphone.

The SIM card emulation in the SIM card emulation module 18 presents and behaves as the target eSIM or eUICC of the eSIM 5 .

The SIM multiplexer 16 provides geographic separation of the test probe 6 and eSIM cards 5 (eUICC) to provide multiple eSIMs and then dispatch the prepared eSIMs. Test system 7 using SIM multiplexer 16 will relay messages between eSIM card 5 (eUICC) and SM-SR module 3 (for M2M device, compare Fig. 1 above) or SM-DP+ module 10 (for smartphones and/or consumer devices). IoT, compare Fig. 2 above) using the mobile connection provided by the test environment 19 of the test probe 6. A corresponding embodiment is described below with reference to Figs. 4.

The eSIM RSP check consists of two successive test parts.

a) Verify that the eSIM profile is provisioned and switched from bootstrap to target carrier by verifying that the test probe was successfully reconnected to the network and comparing the new IMSI value with the value prior to the eSIM RSP.

b) Post-RSP network service testing with a provisioned eSIM in a test probe for basic mobile services, such as HTTPs download, ping, SMS MO MT and Voice MO MT. Such network service tests after RSP are not further described in detail.

The test system may be a traditional distributed test system based on a server/client model. Recently, cloud-based testing systems have been mainly deployed. The test probe can be connected to any type of test system.

Communication between the main components of the test system 7 can be carried out through the cloud test server 20 (see Fig. 4).

This cloud-based test system 7 is used to test the eSIM RSP process (see FIG. 4) and also supports SMS and/or remote application control (RAM) over HTTP(s) over LTE/EPS.

In FIG. 4 illustrates various embodiments of test probes 6 communicating via core network interfaces or via radio interfaces.

The procedure for testing RSP using the test system 7 brought to the cloud is similar to that described above. You can run a standard test sequence consisting of an EPS ATTACH and a trigger SMS message.

The following discussion discusses the main aspects of validating a manually started RSP process.

A one-sided active test is performed. In this scenario, the user starts the test and then manually starts the RSP process from their provisioning platform (21 clients). The test sequence is as follows:

- connect to the network (MNO 4, compare Fig. 1 and Fig. 2 above),

- wait for initializing SMS-MT or SM-DP+ address with AC marker,

- wait for eSIM initialization HTTPs session between eSIM card 5 and RSP platform 1 (including SM-SR 3 or SM-DP+ 10 module),

- wait for a successful reconnection to the network with a new prepared eSIM profile,

- disconnect from the network.

The startup phase and the validation phase of the ordered and launched eSIM profile are initiated by the user, i.e. via test probe 6.

Input parameters

Standard test parameters should be included. In addition, the timeout option must be enabled so that the user can set a timeout during which to wait for a trigger SMS message from the SM-SR 3 module. Examples are shown in the table below:

Parameter Type Default Description RSP timeout Whole 90 Timeout(s) to detect IMSI change during initialization. If there is an excess, then the module will return err_failed. Reconnect Timeout Whole 90 Timeout(s) from disconnecting the network after updating an eSIM profile before successfully re-joining a new APN SMS_DCS (Dial Code Scheme) Line F6 Space-separated list of expected DCS values for RSP SMS. Can be used to determine the initialization of an SMS for evaluation results and stop waiting for a further trigger SMS message; 8-bit data, class 2 (SIM specific) APN to reconnect Line According to APN to reconnect after eSIM profile update

Key Parameter Indicators (KPIs)

The following KPIs should be provided:

Name Type Description Initialization successful INT If an IMSI change is detected, then this flag is set to "1", otherwise to "0". Empty if the eSIM_Provisioning module has not been started Initialization duration DURATION_MSEC The period from the time of the open packet channel to the closed packet channel from the decoded T0 trace IMSI launch varchar(100) eSIM IMSI before SIM profile update End of IMSI varchar(100) eSIM card IMSI after successful SIM profile update SMSR_IPAddress (or SM-DP+_IP address) varchar(100) SM-SR IP address extracted from decoded T0 log SMS reception duration DURATION_MSEC Duration from launch of eSIM provisioning module to SMS with expected DCS value (for M2M device) Subscription duration DURATION_MSEC Duration from launching the eSIM provisioning module to request a subscription to confirming the subscription (for a consumer device)

The test results can be written to a result file. Such a file may be in PCAP ("packet capture") format.

During RSP validation, the following failure criteria can be set:

- no SMS is received from SM-SR (during a user-defined timeout period) or subscription confirmation (AC) is not received,

- HTTPs session is not open between 5 eSIM card or SIM emulation in 18 SIM emulation module and RSP platform (SM-SR or SM-DP+),

- IMSI at the end is the same as IMSI at the beginning,

- the network reconnects to a new APN after an unsuccessful IMSI change.

In the case of an automatically started RSP (compare the case described with references to Fig. 2 above, the active test system 7 illustrated in Fig. 4 should use two interfaces for the RSP:

- one mobile interface for the RSP process itself,

- one LAN interface for interacting with the API of the tested platform 1 RSP.

This test sequence must be customized depending on the platform under test that the client is using.

The mobile interface part should behave in the same way as in the manual launch script above:

- connect to the network (MNO 4, compare Fig. 1 and Fig. 2 above),

- wait for the initialization of the triggering SMS,

- wait for the end of HTTPs session between eSIM card 5 and RSP platform 1 (SM-SR 3 or SM-DP+ 10 module),

- disconnect from the network.

The LAN interface should be used to send API commands to the provisioning platform 21 . Commands must be user-configurable, such as boot profile, uninstall profile, or activation profile.

Input parameters

As in the manual scenario, the timeout setting must be enabled so that the user can set a timeout that determines how long to wait for a trigger SMS message from the SM-SR 3.

You will need to specify additional parameters for interacting with the API, such as the type of operation, API authentication, eSIM / eUICC ID (EID) - the identifier of the required eSIM profile that needs to be configured, IMSI. A complete list of options can be specified based on the API documentation for the specific RSP platform.

Key parameters indicators

The following KPIs should be provided:

- IMSI at the beginning of the test,

- IMSI at the end of the test,

- duration of the IP session from the PCAP file - duration of the IP session between the 5 eSIM card and the SM-SR 3 module - this will reflect the time it took for the RSP to complete its work, such as loading a profile, turning it on, turning it off,

- IP address of SM-SR module 3 or SM-DP+ module 10 - from the PCAP file,

- IP session start duration - if possible - measured as the length of time between the receipt of the initialization SMS message or the receipt of the AC and the start of the IP session (TCP SYN from mobile device to RSP platform 1 (SM-SR or SM-DP+)),

- total preparation time - the time from sending an API 1 trigger to the end of the IP session,

- SMS reception duration - time from sending an API trigger to receiving an SMS with initialization,

- subscription duration - the length of time from the subscription request to the subscription confirmation.

A PCAP file can be provided as a result file.

During RSP validation, the following failure criteria can be set:

- SMS message not received from SM-SR (within user-defined timeout period) or subscription confirmation (AC) not received,

- the HTTPs session is not open between the eSIM card 5 or the SIM emulation in the SIM emulation module 18 and the RSP platform (SM-SR or SM-DP+),

- IMSI at the end is the same as IMSI at the beginning,

- RSP platform is not available via API.

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

Claims (32)

1. A test method for checking the eSIM Remote Provisioning (RSP) process, including the following steps: - order (8; 13) eSIM profile on the tested platform (1) RSP, - start (9; 14) download of the ordered eSIM profile from the platform (1) RSP, - uploading (9a; 15) the running eSIM profile from the platform (1) RSP via wireless interface to the target eSIM or eUICC (5) in the test probe (6), - checking the correct loading of the ordered and launched eSIM profile, - in this case, the test probe (6) is configured to simulate M2M devices (machine-to-machine communication). 2. A test method for checking the eSIM remote provisioning process, including the following steps: - order (8; 13) eSIM profile on the tested platform (1) RSP, - start (9; 14) download of the ordered eSIM profile from the platform (1) RSP, - downloading (9a; 15) the activated eSIM profile from the platform (1) RSP via wireless interface to the target eSIM or eUICC (5) in the test probe (6), - checking the correct loading of the ordered and activated eSIM profile, - wherein the test probe (6) is configured to simulate a smartphone and/or consumer IoT device, wherein the test script to be tested by the testing method includes the user side, which is represented by the test probe (6), - in this case, the launch stage (9; 14) and the verification stage are initiated by the user. 3. The method according to any one of paragraphs. 1 or 2, in which before placing an order, a subscription request (12) is sent from the test probe (6) to the sender (4) of the order. 4. The method according to any one of paragraphs. 1-3, including automatic sequencing of the eSIM profile sequence according to the order schedule. 5. The method according to any one of paragraphs. 1-4, in which during startup, the RSP platform (1) sends to the test probe (6) a trigger SMS message addressed to the target eUICC (5). 6. The method of claim 5, wherein the triggering SMS message initiates an HTTPs session or a CAT_TP (Card Application Toolkit Transport Protocol) session. 7. Testing method according to any one of paragraphs. 1-6, in which, during startup, the test probe (6) establishes a packet data network (PDN) connection to the gateway specified in the triggering SMS. 8. Active testing system (7), providing a testing method according to any one of paragraphs. 1-7, having - at least one test probe (6) including at least one target eSIM or eUICC (5) with the initial work profile set, - an interface to the (1) RSP platform for remotely provisioning an eSIM profile different from the original work profile, - a wireless interface for communication between the RSP platform (1) and the test probe (6). 9. The system of claim. 8, in which the platform (1) RSP includes - subscription manager data preparation module (SM-DP) (2), - Subscription Manager Secure Routing Module (SM-SR) (3). 10. The system according to any one of paragraphs. 8 or 9, characterized in that it contains an order module for automatically ordering a sequence of eSIM profiles in accordance with an order schedule. 11. The system according to any one of paragraphs. 8-10, in which the platform (1) RSP includes - subscription manager data preparation module+ (SM-DP+) (10), - Subscription Manager Discovery Server (SM-DS) module (11). 12. The system according to any one of paragraphs. 8-11, characterized in that the SIM multiplexer (16) includes a SIM server (17) and a plurality of eUICCs (5), wherein the SIM server (17) is in signal communication with the test probe (6). 13. The system according to any one of paragraphs. 8-11, characterized by the presence of a cloud server (20).

Images