Test methods for authentication of rsp procedures and active test system providing the same

Abstract

In a test method for verifying the eSIM remote configuration process, an eSIM profile is pre-ordered (8) from an RSP platform (1) under test. Then, a trigger (9) is initiated to download the pre-ordered eSIM profile from the RSP platform (1). 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. The pre-ordered, triggered, and downloaded eSIM profile is then verified to be correct. The test probe (6) can be configured to simulate an M2M device, a smartphone, and / or a consumer IoT device. These test methods enhance the test system's ability to test mobile networks using eSIM remote configuration while continuously providing network connectivity and services via eSIM exchange.

Description

[0001] This application claims priority to German patent application DE 10 2019 214 919.7, the contents of which are incorporated herein by reference. Technical Field

[0002] This invention relates to a test method for verifying the eSIM Remote Configuration (RSP) process. Furthermore, this invention relates to an active test system that provides such test methods. Background Technology

[0003] For example, test systems for mobile networks are known from US 10,097,981 B1, US 7,831,249 B2, and WO 2004 / 049746 A1. US 2019 / 0075448 A1 discloses monitoring of an embedded user identification module. WO 2016 / 013827 A1 discloses a method and apparatus for configuring an embedded SIM. WO 2017 / 013127 A1 discloses a method for detecting remote access to a general-purpose integrated circuit card. Summary of the Invention

[0004] The purpose of this invention is to enhance the ability of such testing systems to test mobile networks using eSIM remote configuration.

[0005] The objective is achieved by a testing method including the features described in the first or second aspect and by an active testing system including the features described in the seventh aspect.

[0006] Embedded Universal Integrated Circuit Cards (eUICCs), or embedded SIMs (eSIMs), are ubiquitous and used in consumer Internet of Things (IoT) and machine-to-machine (M2M) devices to identify devices against mobile networks. Furthermore, eSIMs will also be introduced for smartphones. eSIM is a next-generation SIM technology designed to replace physical cards using a combination of hardware and software, thereby providing the ability to remotely switch devices between operators. This technology allows a single device to host multiple connectivity providers (called profiles) and is designed for use with all types of mobile devices, including smartphones and IoT modules.

[0007] The hardware portion of the eUICC card is primarily manufactured using an embedded form factor (MFF2). The software portion of the eSIM can be remotely downloaded and installed onto the eUICC card. This process is known as eSIM Remote Configuration (RSP). The terms eUICC or eSIM used in this patent refer to a "personalized" eUICC or eSIM that is the software portion of the eUICC to be downloaded. The eUICC is not easily accessible or replaceable, is not intended to be removed or replaced in a device, and enables secure changes to the subscription.

[0008] GSMA has specified the following standards for eSIM configuration for M2M devices and consumer devices respectively:

[0009] -GSMA SGP.02v4.2, July 7, 2020 - Embedded SIM Remote Configuration Architecture - Technical Specification

[0010] -GSMA SGP.22v2.3, June 5, 2020-RSP Technical Specification

[0011] -GSMA SGP.02v4.0, February 25, 2019 - Embedded SIM remote configuration architecture.

[0012] When providing eSIM to devices with eSIM capability on behalf of mobile operators or third parties, the test methods and active system coverage testing and verification aspects according to the present invention are applied.

[0013] Other standards stipulated by GSMA are:

[0014] -GSMA SGP.23RSP Test Specification Version 1.7, July 7, 2020.

[0015] Another standard stipulated by GSMA is:

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

[0017] Multiple profiles can be downloaded and installed on the eUICC. A profile is associated with an operator and 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 profile can be activated and run at a time. An eSIM RSP platform on behalf of the operator or a third party can enable, disable, delete, or switch each profile on the eUICC.

[0018] The aforementioned test method and active test system employ an end-to-end test method, which verifies mobile network connectivity and services within the context of the RSP process. The test method verifies the RSP in the test system and tests mobile network connectivity using a SIM configured in a national or international service network according to the following criteria:

[0019] -GSMA SGP.02RSP for M2M devices;

[0020] - GSMA SGP.22RSP for consumer devices.

[0021] An eSIM profile is a personalized software portion of an embodied universal integrated circuit card (eUICC) (i.e., software assigned to the assigned user). This software includes at least one user profile. The RSP process can be used for consumer devices (e.g., smartphones, smartwatches, wearable devices) and / or for machine-to-machine (M2M) devices. Specifically, the testing method verifies mobile network connectivity and services. An eSIM profile can be ordered manually or automatically from the RSP platform. The order sender can be a mobile network operator (MNO). The RSP process can be initiated before ordering. During the testing method, the previously working profile or boot profile installed on the eUICC at the start may be disabled, and the downloaded eSIM profile is enabled. Checks can be performed by monitoring for the occurrence of at least one "failed criterion." These failure criteria can be met based on RSP platform connection timeouts and / or network attachment timeouts and / or based on the expected structure of the ordered, triggered, and / or downloaded profile, and / or based on reattachment timeouts of the device with the downloaded updated eSIM profile.

[0022] During the testing phase, network connectivity and services were continuously provided via eSIM exchange.

[0023] According to the test method described in the first aspect, the test probe simulates an M2M device.

[0024] The test probe supports a wide range of frequency spectrums in licensed bands, including 2G, 3G, 4G, and 5G radio frequencies. This configuration allows for efficient communication between the test probe and a remote RSP platform providing eSIM profiles, which are configured via download. The test probe supports SMS over Non-Access Stratum (NAS) for 4G and 5G technologies (SMSoNAS). It also supports SMS over Internet Protocol (SMSoIP) for IP Multimedia Subsystem (IMS) technology. The test probe can be configured to adapt to the communication environment, selecting the correct communication protocol required for eSIM verification on the corresponding RSP platform. The test probe can be configured to communicate with industrial IoT applications. Examples of such industrial IoT applications include Machine Long Term Evolution (LTE-M) and Narrowband Internet of Things (NB-IoT). The test probe can also be configured to communicate with at least one Low Power Wide Area Network (LPWAN) radio technology standard.

[0025] According to the test method described in the second aspect, the test probe simulates a smartphone and / or a consumer IoT device.

[0026] The test probe can be configured to test user transaction-related test standards, i.e., to test the RSP verification process at the user level. During such user-level testing, the test probe can initiate quality test steps by checking quality parameters that can be defined by Key Performance Indicators (KPIs). These KPIs can be access failure rate, access time, cutoff rate, download start duration, download availability ratio, etc. These quality parameters can be checked in real time by the test probe. In this regard, the test probe can be configured to simulate real user behavior of smartphone and / or consumer IoT device users.

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

[0028] The entity sending the subscription request as described in the third aspect may use a mobile network operator's agent. The subscription request may include a link or code. During the triggering step, the entity sending the order may confirm the subscription request from a test profile. This confirmation may trigger a test probe to find a download address for the eSIM profile used to download the subscription. Triggering options may use the default address of the Subscription Manager Data Preparation (SM-DP+) stored at the target eSIM, the Fully Qualified Domain Name (FQDN) of the SM-DP+ address to be discovered using the Root Subscription Manager Discovery Server (SM-DS), or an activation code containing the SM-DP+ address.

[0029] The order schedule described in the fourth aspect may include the number of eSIM profiles generated by the RSP platform, may include one or more IMSI values ​​or IMSI ranges, may include one or more ICCID values ​​or ICCID ranges, may include one or more non-personalized profile types, or may include information about one or more target eSIMs, such as eUICC-ID (EID). The EID may be bound to a pre-defined eSIM profile ID (ICCID).

[0030] The efficiency of the testing method described in the fifth aspect has been proven.

[0031] This is particularly applicable to the test method described in aspect six. An HTTP session can establish an end-to-end (e2e) connection between the target eUICC and the RSP platform via the Transport Layer Security (TLS) protocol. The test probe can 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: a request for an e2e CAT_TP link and / or data open to the BIP channel. Such HTTP or CAT_TP sessions can be maintained during the test method, especially via LTE / EPS.

[0032] In the test method described in the seventh aspect, gateway identification can be performed by using the Access Point Name (APN) specifically given in the triggered SMS.

[0033] The advantages of the active testing system described in aspect eight correspond to the advantages mentioned above for the testing method. The test probe can be implemented as a smartphone.

[0034] The proactive testing system described in aspect nine is particularly suitable for M2M applications. The Reservation Manager Data Preparation (SM-DP) module receives orders, and the Reservation Manager Secure Routing (SM-SR) module manages personalized eSIM profiles.

[0035] The order module described in aspect ten can communicate with the RSP platform via a network interface or an application programming interface (API).

[0036] The RSP platform described in aspect eleven is particularly suitable for smartphones and / or consumer IoT devices. The SM-DP+ module manages personalized eSIM profiles. The SM-DS module identifies the appropriate SM-DP+ address for the test probe.

[0037] The signal connection between the SIM server and the test probe, as described in the twelfth aspect, can be established via LAN / WAN. The SIM multiplexer, as described in the twelfth aspect, provides geographical separation between the test probe and the target eUICC / eSIM.

[0038] The cloud-based system described in aspect thirteen enables comfortable and cost-effective client connections. Attached Figure Description

[0039] Embodiments of the invention will be described below with reference to the accompanying drawings. These drawings illustrate:

[0040] Figure 1 The main components of an active test system are schematically shown for a test method used to verify the eSIM remote configuration (RSP) process for machine-to-machine (M2M) devices.

[0041] Figure 2 Is with Figure 1 A schematic diagram of another embodiment of a similar active testing system, which provides a corresponding RSP verification process testing method for consumer devices (e.g., smartphones or various consumer IoT devices);

[0042] Figure 3 It includes a test system configuration for SIM multiplexers; and

[0043] Figure 4 This is a test system configuration for communication via the cloud. Detailed Implementation

[0044] A. Testing eSIM RSP for M2M

[0045] The eUICC remote configuration and management platform (or SIM remote configuration (RSP) platform 1) is responsible for eSIM remote configuration. 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, securely connected to each other. SM-DP module 2 represents the Mobile Network Operator (MNO) 4. SM-SR module 3 establishes a secure and authenticated transport channel to the personalized software portion of the embedded universal integrated circuit card (eUICC) or embedded SIM (eSIM). This software portion can be assigned to the assigned user or connected device, especially as part of the Internet of Things (IoT). SM-SR module 3 further manages personalized profiles to be downloaded or switched between at the eUICC.

[0046] An eSIM card 5 of any suitable form factor is inserted into a test probe 6, which, according to one embodiment, simulates an M2M device, and according to another embodiment, simulates a smartphone and / or a consumer IoT device. Multiple instances of the test probe 6 are part of an active testing system 7 and are configured to receive at least one required eSIM profile to be downloaded from the RSP platform 1 under test. The inserted eSIM card 5 contains a currently active profile, which differs from the required profile to be ordered and configured.

[0047] The test scenario to be tested using the aforementioned test method includes the user side, represented by test probe 6.

[0048] Figure 1 The test procedure is shown in three steps: "booking-triggering-downloading" to verify the eSIM profile required for downloading.

[0049] 1. Reserve an eSIM profile (Reservation Step 8)

[0050] The RSP for M2M devices is initiated by the representative of MNO 4 to subscribe to a specific eSIM profile for the identified target eUICC at the SM-DP module 2 of the RSP platform 1. Two exemplary test scenarios are presented:

[0051] a) Manually pre-ordered eSIM profile at RSP platform 1 during testing

[0052] The tester representing MNO 4 will connect to the RSP platform 1 under test and manually send eSIM download command 8 to RSP platform 1, targeting the eSIM card in test probe 6, and wait for configuration messages from RSP platform 1.

[0053] b) The eSIM profile automatically reserved at RSP platform 1 during testing

[0054] The active test system 7, representing MNO 4, interacts with the RSP platform 1 under test via a web interface or application programming interface (API), which has a reservation token for reserving one or more eSIM profiles. The RSP process can be initiated automatically. Test system 7 is awaiting a configuration message from RSP platform 1. The reservation token may contain:

[0055] - The number of eSIM profiles generated by SM-DP module 2;

[0056] - Values ​​or ranges for the International Mobile Subscriber Identity (IMSI);

[0057] - The value or range of the Integrated Circuit Card ID (ICCID);

[0058] -Non-personalized configuration file type;

[0059] - Information about the target eUICC, such as eUICC-ID (EID).

[0060] 2. Trigger step 9

[0061] In the test, the SM-SR module 3 in the RSP platform 1 triggers the download of the required eSIM profile to the target eSIM card 5 in the test probe 6 via an over-the-air (OTA) interface. The SM-SR module 3 sends a trigger SMS to address the eSIM card 5. When the test probe 6, which has the current profile on the eSIM card 5, is attached to a mobile network (e.g., EPS attachment over a 4G / 5G network or GPRS attachment over a 2G / 3G network), the trigger SMS sent by the SM-SR module 3 is delivered to the target eSIM card 5 via the test probe 6, triggering an HTTP session or a Card Application Kit 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 the gateway specified in the APN.

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

[0063] If CAT_TP is used, triggering the SMS includes the following two commands:

[0064] - A request to establish an e2e CAT_TP link between eSIM card 5 and SM-SR module 3;

[0065] - Data is opened in the BIP channel between test probe 6 and eSIM card 5.

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

[0067] 3. Download and installation steps 9a

[0068] On the one hand, the required eSIM profile download and installation process is performed between the eSIM card 5 and the test probe 6, and on the other hand, between the eSIM card 5 and the RSP platform 1 under test. This process can be performed in four main steps:

[0069] - Create a security domain profile entity for each required eSIM profile to be downloaded to the eSIM card 5.

[0070] - Personalizing the entity using a first set of secure keys is known as key establishment.

[0071] - Download the required eSIM profile from SM-DP module 2 and install the eSIM profile with remote application management (RAM) onto eSIM card 5.

[0072] - Enabling the newly installed eSIM profile and disabling the previously used working profile on the eSIM 5 is called profile switching.

[0073] During operation, test probe 6 maintains a reliable HTTP session or CAT_TP session via the evolved packet system (LTE / EPS).

[0074] The triggering process, including checking whether the pre-booked and triggered eSIM profile has been correctly downloaded, is initiated from the user side (i.e. via test probe 6).

[0075] B. Testing eSIM RSP on consumer devices

[0076] against Figure 2 Further embodiments of an active test system are described, which provide test methods for verifying the RSP process for smartphones or consumer IoT devices. (This has been addressed in...) Figure 1 The components and functions described in the illustrated embodiments have the same reference numerals and will not be discussed in detail thereafter.

[0077] The RSP platform 1 used for testing eSIM RSP in smartphones and / or consumer IoT devices consists of two parts: the Subscription Manager Data Preparation+ (SM-DP+) module 10 and the Subscription Manager Discovery Server (SM-DS) module 11. The SM-DP+ module 10 prepares configuration file packages, protects them using configuration file protection keys, binds each protected configuration file package to a corresponding EID, and securely downloads these bound configuration file 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.

[0078] 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 the required eSIM profile to be downloaded from the RSP platform 1 under test. The inserted eSIM card 5 contains a currently active profile, which is different from the profile to be ordered and configured. The test probe uses the HTTP secure protocol to download the required eSIM profile from SM-DP+ or to discover the SM-DP+ address via the SM-DS module 11.

[0079] Figure 2 The test process for verifying the download of the required eSIM profile involves four steps: "Request - Reservation - Trigger - Download".

[0080] 1. Request 12 subscriptions

[0081] Test system 7 initiates an RSP process and requests subscription.

[0082] 2. Pre-order 13eSIM profile

[0083] MNO 4 pre-orders the requested eSIM profile at SM-DP+ module 10.

[0084] The prepared eSIM profile is securely stored at SM-DP+ module 10. The EID is bound to the eSIM profile ID (ICCID).

[0085] 3. Trigger 14-Subscription Confirmation

[0086] MNO 4 confirms its subscription with test probe 6, which triggers test probe 6 to find the appropriate address to download the required eSIM profile. This process is carrier-dependent and can be accomplished by accessing a URL, using a Local Profile Assistant (LPA), or through a local function in the device firmware. For example, there are three options for triggering test probe 6, representing a consumer device or smartphone.

[0087] - Use the default SM-DP+ address stored in the eSIM card 5

[0088] - Use root SM-DS to discover SM-DP+ addresses (FQDNs)

[0089] - Use activation code (AC)

[0090] Test probe 6 selects one of the procedures in the following order.

[0091] - Use the default SM-DP+ address

[0092] This option is typically used for boot profile discovery. Test probe 6 retrieves the pre-configured default SM-DP+ address stored in the eSIM 5.

[0093] - Use root SM-DS for configuration file discovery

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

[0095] -Use AC

[0096] The Active Test System 6 has received the activation code from MNO 4 by any means, such as email or API. The AC must include at least:

[0097] -SM-DP+address

[0098] -AC token (matching ID)

[0099] The AC input can be entered into test probe 6 by manually typing or scanning the Quick Response (QR) code.

[0100] 4. Download and Installation Steps 15

[0101] The eSIM profile download procedure 15 is performed between test probe 6 of the RSP platform 1 and SM-DP+ module 10 during testing. During operation, test probe 6 maintains a reliable e2eHTTP session over TCP / IP via LTE / EPS or a fixed cable. Test probe 6 initiates the required eSIM profile download using the EID parameter and the matching ID to identify the bound profile packet. If the profile is downloaded from the default SM-DP+ address, the matching ID is empty.

[0102] After receiving the entire binding profile package, test probe 6 initiates the installation of the required eSIM profile on eSIM card 5 in a secure and protected manner.

[0103] In another embodiment, a smartphone can be used as test probe 6.

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

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

[0106] exist Figure 3 In another embodiment shown, the active testing system includes a SIM multiplexer 16. The SIM multiplexer 16 includes a SIM server 17 and multiple eSIM cards 5. The SIM server 17 is signal-connected to a test probe 6. In this embodiment, the test probe 6 includes a SIM emulation module 18, which is signal-connected to a test probe environment 19, which can be implemented as a mobile phone or smartphone.

[0107] The SIM emulation in SIM emulation module 18 represents and manifests as the target eSIM or eUICC of eSIM card 5.

[0108] SIM multiplexer 16 allows for geographical separation of test probe 6 from eSIM card 5 (eUICC) for multiple eSIM configurations and subsequent eSIM scheduling. Test system 7 using SIM multiplexer 16 will utilize the mobile connectivity provided by test probe environment 19 of test probe 6 between eSIM card 5 (eUICC) and SM-SR module 3 (for M2M devices, compare above). Figure 1 ) or SM-DP+ module 10 (for smartphones and / or consumer IoT devices, compare the above) Figure 2 Bridge messages between them. See below for reference. Figure 4 The corresponding implementation examples are described.

[0109] eSIM RSP verification consists of two consecutive test parts.

[0110] a) Verify the configured eSIM profile from bootstrapping to the target operator by checking whether the test probe has successfully reattached to the network and by comparing the new IMSI value with the previous value of the eSIM RSP.

[0111] b) Perform post-RSP network service guarantee tests using the configured eSIM in the basic mobile service test probe, such as HTTP download, Ping, SMS MO MT, and voice MO MT. These post-RSP network service guarantee tests will not be described in further detail.

[0112] The testing system can be a traditional distributed testing system based on a server / client model. Recently, cloud-based testing systems have been deployed extensively. Test probes can connect to any type of testing system.

[0113] Communication between the main components of test system 7 can be achieved via cloud-based test server 20 (see...) Figure 4 ) to execute.

[0114] These cloudified test systems 7 are used for verification of the eSIM RSP process (see reference). Figure 4 It also supports SMS and / or remote application management (RAM) over HTTP via LTE / EPS.

[0115] exist Figure 4 Different embodiments of test probe 6 are illustrated, which communicates via a core network interface or via a radio interface.

[0116] The RSP test procedure using the cloud-based test system 7 is the same as described above. It can execute a standard test sequence consisting of EPS attachment and trigger SMS.

[0117] The main aspects of verifying a manually triggered RSP process are discussed below.

[0118] Perform a one-sided active test. In this case, the user starts the test and then manually triggers the RSP process from their configuration platform (client 21). The test sequence is as follows:

[0119] - Attached to network (MNO 4, compared to the above) Figure 1 and Figure 2 ),

[0120] -Waiting to receive a configured SMS-MT or SM-DP+ address with an AC token.

[0121] - Wait until the eSIM configuration HTTP session between eSIM card 5 and RSP platform 1 (including SM-SR module 3 or SM-DP+10) is complete.

[0122] - Waiting for successful reattachment to the network using the newly configured eSIM profile.

[0123] - Disconnect the network attachment.

[0124] The triggering process and the steps to check whether the "pre-ordered and triggered eSIM profile has been correctly downloaded" begin on the user side, i.e., via test probe 6.

[0125] Input parameters

[0126] Standard test parameters should be included. Additionally, timeout parameters should be included, allowing users to set a timeout for waiting for a configuration trigger SMS from the SM-SR module 3. An example is given in the table below:

[0127]

[0128] Key performance indicators (KPIs)

[0129] The following KPIs should be provided:

[0130]

[0131] The verification results can be logged in a results file. This file can be in Packet Capture (PCAP) format.

[0132] During RSP verification, the following failure criteria can be established:

[0133] - No SMS received from SM-SR (during the user-configured timeout period) or no subscription confirmation (AC) received.

[0134] - An HTTP session is not open between the SIM emulation in eSIM card 5 or SIM emulation module 18 and the RSP platform (SM-SR or SM-DP+).

[0135] - The IMSI at the end is the same as the IMSI at the beginning.

[0136] - The network reattached to the new APN after the IMSI change failed.

[0137] In the case of automatic RSP triggering (compared to the above for) Figure 2 The described embodiments, according to Figure 4 The active test system 7 should use two interfaces for RSP:

[0138] - A mobile interface of the RSP process itself

[0139] - A LAN interface for interacting with the API of RSP platform 1 under test.

[0140] This test sequence needs to be customized based on the testing platform used by the client.

[0141] The mobile interface should exhibit the same behavior as the manually triggered scenarios discussed above:

[0142] - Attached to network (MNO 4, compared to the above) Figure 1 and Figure 2 )

[0143] -Waiting for configuration to trigger SMS

[0144] -Wait until the HTTP session between eSIM card 5 and RSP platform 1 (SM-SR module 3 or SM-DP+10) is complete.

[0145] - Disconnect the network attachment.

[0146] The LAN interface is used to send API commands to the configuration platform 21. These commands should be user-configurable, such as downloading, deleting, or activating configuration files.

[0147] Input parameters

[0148] Similar to manual scenarios, a timeout parameter should be included so that users can set a timeout for waiting for a configuration-triggered SMS from the SM-SR module 3.

[0149] Additional parameters for interacting with the API are required, such as operation type, API authentication, eSIM / eUICC ID (EID) – the ID of the required eSIM profile that needs to be configured, and IMSI. A complete list of parameters can be specified based on the specific RSP platform API documentation.

[0150] Key parameters and indicators

[0151] The following KPIs should be provided:

[0152] -IMSI at the start of the test

[0153] -IMSI at the end of the test

[0154] - IP session duration from the PCAP file - Duration of the IP session between eSIM card 5 and SM-SR module 3 - This will reflect the time spent completing RSP operations, such as configuration file download, enabling, and disabling.

[0155] -IP address of SM-SR module 3 or SM-DP+ module 10- From PCAP file

[0156] -IP Session Start Duration-If possible-Measure the duration between receiving the configured SMS or receiving the AC and the start of the IP session (from the mobile device to RSP platform 1 TCP SYN (SM-SR or SM-DP+)).

[0157] -Total Configuration Duration-The duration from when API 1 is triggered to when the IP session is complete.

[0158] -SMS Receive Duration- The duration from when the send API is triggered to when the configured SMS is received.

[0159] -Subscription Duration- The duration from subscription request to subscription confirmation.

[0160] A PCAP file can be provided as the result file.

[0161] During RSP verification, the following failure criteria can be established:

[0162] - No SMS received from SM-SR (during the user-configured timeout period) or no subscription confirmation (AC) received.

[0163] - An HTTP session is not open between the SIM emulation in eSIM card 5 or SIM emulation module 18 and the RSP platform (SM-SR or SM-DP+).

[0164] - The IMSI at the end is the same as the IMSI at the beginning.

[0165] - Unable to access the RSP platform via API

[0166] To automatically reserve the required eSIM profile sequence according to the reservation schedule, the active testing system may also include a reservation module, which may be part of the test probe 6.

Claims

1. A test method for verifying the eSIM remote configuration "RSP" process, the test method comprising the following steps: - Reserve (8; 13) eSIM profiles from the RSP platform (1) under test, the eSIM profiles being associated with a mobile network operator (MNO) among multiple mobile network operators; - Trigger (9; 14) to download the eSIM configuration file from the RSP platform (1); - Download the eSIM profile from the RSP platform (1) (9a; 15) to the test probe (6) via the over-the-air "OTA" interface; - The triggered eSIM profile is transmitted from the test probe (6) to the SIM multiplexer via the network, the SIM multiplexer including a SIM server and multiple eUICC / eSIMs, wherein the SIM multiplexer is configured to allow geographical separation of the test probe and the multiple eUICC / eSIMs; - Check whether the pre-ordered and triggered eSIM profile has been correctly downloaded, wherein checking whether the eSIM profile has been correctly downloaded includes verifying the configured eSIM profile from bootstrapping to the target operator by checking whether the test probe has successfully reattached to the network and by comparing the new IMSI value with the value before the eSIM RSP, and performing a post-RSP network service guarantee test by using the configured eSIM in the basic mobile service test probe; and -The test probe (6) is configured to simulate a machine-to-machine "M2M" device.

2. A test method for verifying the eSIM remote configuration "RSP" process, the test method comprising the following steps: - Reserve (8; 13) eSIM profiles from the RSP platform (1) under test, the eSIM profiles being associated with a mobile network operator (MNO) among multiple mobile network operators; - Trigger (9; 14) to download the eSIM configuration file from the RSP platform (1); - The triggered eSIM profile will be downloaded (9a; 15) from the RSP platform (1) to the test probe (6) via the over-the-air "OTA" interface. - The triggered eSIM profile is transmitted from the test probe (6) to the SIM multiplexer via the network. The SIM multiplexer includes a SIM server and multiple eUICC / eSIMs and is configured to allow geographical separation of the test probe and the multiple eUICC / eSIMs. - Check whether the pre-ordered and triggered eSIM profile has been downloaded correctly, wherein checking whether the eSIM profile has been downloaded correctly includes verifying the configured eSIM profile from the bootstrap exchange to the target operator by checking whether the test probe has successfully reattached to the network and by comparing the new IMSI value with the value before the eSIM RSP, and performing a post-RSP network service guarantee test by using the configured eSIM in the test probe of basic mobile services. -The test probe (6) is configured to simulate a smartphone and / or a consumer IoT device. -The test scenario to be tested using the test method includes the user side represented by the test probe (6), -The triggering step (9; 14) and the checking step are initiated from the user side.

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

4. The testing method according to any one of claims 1 to 3, wherein the testing method includes automatically reserving a sequence of eSIM profiles according to an order schedule, each eSIM profile being associated with a corresponding MNO among the plurality of mobile network operators.

5. The test method according to any one of claims 1 to 4, wherein during the triggering period, the RSP platform (1) sends a trigger SMS to the test probe (6) to address one of the plurality of eUICCs (5).

6. The test method according to claim 5, wherein the triggering SMS triggers an HTTP session or a Card Application Toolkit Transport Protocol "CAT_TP" session.

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

8. An active testing system (7) providing a testing method according to any one of claims 1 to 7, the active testing system comprising: - At least one test probe (6), the at least one test probe comprising at least one target eSIM or eUICC (5), the at least one target eSIM or eUICC having an initial working profile installed; - An interface to the RSP platform (1), the interface being used for remote configuration of an eSIM profile that is different from the initial working profile; -OTA interface, the OTA interface is used to provide communication between the RSP platform (1) and the test probe (6); - SIM multiplexer (16), the SIM multiplexer (16) including SIM server (17) and multiple eUICC / eSIM (5), the SIM multiplexer (16) being configured to allow geographical separation of the test probe and the multiple eUICC / eSIM, The eSIM profile triggered therein is transmitted from the test probe (6) to the SIM multiplexer (16) via the network, and The test probe (6) verifies the configured eSIM profile from the bootstrap exchange to the target operator by checking whether the test probe has successfully reattached to the network and by comparing the new IMSI value with the previous value of the eSIM RSP. The test probe (6) also checks whether the pre-booked and triggered eSIM profile has been correctly downloaded by performing a post-RSP network service guarantee test using the configured eSIM in the test probe for basic mobile services.

9. The active testing system according to claim 8, wherein the RSP platform (1) comprises: -Subscription Manager Data Preparation "SM-DP" Module (2); -Subscription Manager Security Router "SM-SR" module (3).

10. The active test system of claim 8 or claim 9, wherein A reservation module used to automatically reserve eSIM profile sequences based on order schedules.

11. The active testing system according to any one of claims 8 to 10, wherein the RSP platform (1) comprises: -Subscription Manager Data Preparation + "SM-DP+" Module (10); - The subscription manager discovers the server "SM-DS" module (11).

12. The active testing system according to any one of claims 8 to 11, characterized in that... It also includes cloud-based servers (20).

Images