Method for managing at least one EUICC Information Set (EIS) of the EUICC and an intermediate buffer proxy

Abstract

The invention relates to a method for managing at least one eUICC Information Set (EIS) of an eUICC, the method comprising the steps of: generating (110) a first request to register an eUICC Information Set (EIS) with an eUICC Manufacturer (EUM), the first request including a first Function Invocation Identifier (FCI), sending (120) the first request from the eUICC Manufacturer (EUM) to an intermediate buffer proxy (20), generating (130) a response to the first request in the intermediate buffer proxy (20), and sending (140) the response to the request to the eUICC Manufacturer (EUM).

Description

[Technical field]

[0001] TECHNICAL FIELD OF THEINVENTION The present invention relates to a method for managing at least one eUICC Information Set (EIS) of an eUICC and to an intermediate buffer proxy.

[0002] The use of embedded Universal Integrated Circuit Cards (eUICC), also called embedded Subscriber Identity Modules (eSIM), is becoming increasingly popular in the consumer and machine-to-machine (M2M) communications sector. Unlike traditional UICCs or SIMs, which exist as removable smart cards that can be transported between multiple devices, eUICCs are integrated circuits that are not designed to be user removable, i.e., they are typically embedded or soldered into other electronic components of the device. eUICCs are typically issued by Electronic Manufacturers (EUMs), often referred to as Original Equipment Manufacturers (OEMs). [Background technology]

[0003] Technology background Traditionally, for a telecommunications device to be able to connect to a particular mobile network, a SIM card issued by a mobile network operator (MNO) needs to be inserted into the device. In this manner, to switch the mobile connection to a different MNO, the SIM card for the current MNO is removed from the device and replaced with another SIM card associated with the new MNO. The requirement to replace SIM cards whenever a connection to a different mobile network is required is a major drawback, especially in the context of M2M communications. It would be highly efficient and desirable to have a single SIM card installed when manufacturing a device, and then that SIM card be able to support connection to the MNO of the user's choice.

[0004] To address this issue, the Global System for Mobile Association (GSMA) defines a remote provisioning architecture for embedded SIMs as a guide for mobile operators. eSIMs are embedded in IoT devices, providing a secure interoperability architecture to facilitate commercial deployment of systems that allow remote provisioning of target MNO profiles into the eSIM. GSMA specifies methods and protocols for MNOs to set up profile information on the eSIM using wireless communication channels. This method is called Over-the-Air (OTA) provisioning. OTA provisioning of entirely new SIM profiles can be used for devices moving through an operator network.

[0005] In the document GSMA SGP.01 "Embedded SIM Remote Provisioning Architecture", version 4.0, 23 February 2019, the GSMA provides an architectural approach for provisioning and subscription management of M2M devices. The document includes a description of eUICC registration in the SM-SR. To achieve this, the eUICC manufacturer sends a registration request to the SM-SR, and after performing the registration, the SM-SR returns a registration confirmation.

[0006] The eSIM supports multiple subscription profiles. These profiles can be added, enabled, disabled and removed as required. The GSMA is standardizing an OTA architecture for eSIM profile introduction and switching. Profile introduction and switching is compliant with the Global Platform Card standard (v2.2.1), which is incorporated herein by reference. The Subscription Manager Data Preparation (SM-DP) function is used to create SIM profiles, while the Subscription Manager Secure Routing (SM-SR) function is used to communicate with the eUICC to introduce, enable, disable and remove profiles. The Certificate Issuer (CI) is used for authentication and integrity protection.

[0007] One or more eSIM profiles are set up on the eUICC, each of which includes a unique International Mobile Subscriber Identity (IMSI) number that authenticates the subscriber to a wireless communication carrier. Other data stored in the eSIM profile may include carrier network information, security authentication information, a list of accessible network services, and / or others. The wireless communication carrier may transfer the eSIM profile to the eUICC of a user device in the form of a consumer device or M2M device via an over-the-air (OTA) update.

[0008] Consumer devices are network-enabled devices typically sold to individual consumers. For example, these devices may include smartphones, tablet computers, smart watches, gaming consoles, and / or others. M2M devices are network machines that use telecommunication services provided by wireless carriers to communicate with other network machines. For example, an M2M monitoring device embedded in a vehicle may automatically transmit vehicle tracking and driving information to a remote assistance device at a management center. In another example, an M2M device in the form of a smart home appliance may automatically transmit diagnostic information to a monitoring device at a service center in the event of a device failure.

[0009] Furthermore, the eUICC may include an eUICC Information Set (EIS), which represents the eUICC and may include an eUICC identifier, an identifier of the manufacturer of the eUICC, and further information (e.g., a list of profiles associated with the eUICC). A description and application of the eUICC Information Set (EIS) can be found in the GSMA SGP.02 standard "Remote Provisioning Architecture for Embedded UICC", version 4.0, 25 February 2019.

[0010] To enable the subscription management procedure, the eUICC is registered in the Subscription Manager Secure Routing (SM-SR) database. The registration is performed using the EIS. The procedure is defined in the SGP.01 standard.

[0011] For some OEMs, EUMs or service providers (SPs), it is necessary to decide under what conditions and / or when to push the eUICC information set (EIS) to the subscription manager secure routing (SM-SR) function. For example, the condition for pushing the eUICC information set (EIS) to the subscription manager secure routing (SM-SR) function can be a registered and valid subscription of the eUICC in the Home Location Register (HLR) or the knowledge of the MNO that installs the eUICC in the device that is about to be powered on. Furthermore, the MNO may need to control multiple EUM providers and need to decide which eUICC information set (EIS) to load to the subscription manager secure routing (SM-SR) function, from whom to load the eUICC information set (EIS) to the subscription manager secure routing (SM-SR) function, and when to load the eUICC information set (EIS) to the subscription manager secure routing (SM-SR) function. Furthermore, the ES1 interface between the EUM and the SM-SR as defined in the current GSMA SGP.02 standard may need to be outsourced to a third party integrator. The ES1 interface serves as an interface between the two entities fulfilling the EUM and SM-SR functions.

[0012] An EIS is loaded by using a request-response function as described in the SGP.02 standard. The EUM as a requester sends a request message to the SM-SR which receives the request, processes it and finally returns a message accordingly. The request function is identified based on a Function Requester Identifier (FRI) and a Function Invocation Identifier (FCI). For request-response functions, a validity period may be set.

[0013] However, the current GSMA SGP.02 standard does not provide the possibility to outsource the ES1 interface, since all interactions between the EUM or OEM and the SM-SR function need to be synchronous. Furthermore, the GSMA SGP.02 standard does not provide a mechanism to delay the load on the Subscription Manager Secure Routing (SM-SR) function.

[0014] To partially meet the above-mentioned needs of the OEM, EUM or SP, it is known from the prior art to provide a transparent proxy. A transparent proxy intercepts standard application layer communications without requiring any special client configuration. A transparent proxy is a proxy that does not modify requests or responses beyond what is necessary for proxy authentication and identification. The client does not need to be aware of the presence of the proxy. A transparent proxy can be provided between the EUM or OEM and the SM-SR functionality. Although such a transparent proxy can act as a broker between the EUM or OEM and the SM-SR functionality, it cannot delay the load on the Subscription Manager Secure Routing (SM-SR) functionality.

[0015] Alternatively, it is also known from the prior art to provide a stop-and-go proxy to partially meet the above-mentioned needs of the OEM, EUM or SP. Although a stop-and-go proxy between the EUM or OEM and the SM-SR function can delay the loading to the Subscription Manager Secure Routing (SM-SR) function, it jeopardizes the integrity of the chain between the EUM or OEM and the SM-SR function and represents a risk if it duplicates data of the SM-SR function or the EUM or OEM.

[0016] WO 2020 / 071975 A1 discloses a system for registering an eUICC of an autonomous vehicle with a legal party. The system connects the eUICC manufacturer to an autonomous vehicle manufacturer connected to a specialized SM-SR device. The eUICC manufacturer provides the eUICC to the vehicle manufacturer who forwards the eUICC to the specialized SM-SR to handle provisioning. After registering ownership with the legal party, the specialized SM-SR sends a message indicating a change in the state of the eUICC to the eUICC manufacturer.

[0017] US Patent Application Publication No. 2019 / 0159016A1 discloses a system for eSIM deployment that includes a subscription manager proxy positioned as an intermediate gateway between the SM-DP of a target MNO and the SM-SR of a current MNO. The subscription manager proxy enables the creation, download, activation and deactivation of target MNO profiles for existing subscriptions. Summary of the Invention [Problem to be solved by the invention]

[0018] Summary of the Invention The problem to be solved by the invention is to provide the possibility to delay the loading to the SM-SR function without jeopardizing the integrity of the chain between the EUM or OEM and the SM-SR function.

[0019] The problem is solved by a method for managing at least one eUICC Information Set (EIS) of an eUICC according to claim 1 and by an intermediate buffer proxy according to claim 6. Further preferred embodiments of the invention are the subject of the dependent claims.

[0020] A method for managing at least one eUICC Information Set (EIS) of an eUICC according to the present invention comprises the steps of: - generating a first request for registering an eUICC Information Set (EIS) with an eUICC Manufacturer (EUM), the first request including a first Function Invocation Identifier (FCI); - sending a first request from an eUICC manufacturer (EUM) to an intermediate buffer proxy; - generating a response to the first request in the intermediate buffer proxy; - sending a response to the request to the eUICC Manufacturer (EUM); Includes.

[0021] According to an aspect of the invention, a method comprises the steps of: - generating a registration result response in the eUICC manufacturer (EUM) after receiving a response to the request to the eUICC manufacturer (EUM) at the eUICC manufacturer (EUM); - sending a registration result response to a Mobile Network Operator (MNO); Further includes:

[0022] According to a further aspect of the invention, the method comprises the steps of: - generating, at the intermediate buffer proxy, a second request to register an eUICC information set (EIS) based on the first request received at the intermediate buffer proxy, the second request including a second Function Invocation Identifier (FCI); - sending a second request from the intermediate buffer proxy to a subscription manager secure routing (SM-SR) function; Further includes:

[0023] According to a further aspect of the invention, the method comprises the steps of: - receiving a second request from the intermediate buffer proxy at a subscription manager secure routing (SM-SR) function; - checking by the Subscription Manager Secure Routing (SM-SR) function that the eUICC Information Set (EIS) is present in an eUICC Information Set (EIS) directory stored in the Subscription Manager Secure Routing (SM-SR) function; Further includes:

[0024] According to a further aspect of the invention, the method comprises the steps of: - storing the eUICC Information Set (EIS) in a database of valid eUICC Information Sets (EIS) present in a Subscription Manager Secure Routing (SM-SR) function; - generating a response to the second request in a Subscription Manager Secure Routing (SM-SR) function; - sending a response from the subscription manager-secure routing (SM-SR) function to the second request to the intermediate buffer proxy; Further includes:

[0025] Furthermore, the present invention relates to an intermediate buffer proxy configured to receive a first request from an eUICC manufacturer (EUM) to register an eUICC Information Set (EIS), where the first request includes a first Function Invocation Identifier (FCI), generate a response to the first request, and send the response to the request to the eUICC manufacturer (EUM).

[0026] According to an aspect of the invention, the intermediate buffer proxy is further configured to generate a second request to register the eUICC information set (EIS) and send the second request to a Subscription Manager Secure Routing (SM-SR) function.

[0027] According to a further aspect of the invention, the intermediate buffer proxy is further configured to receive a response to the second request from a subscription manager secure routing (SM-SR) function.

[0028] According to a further aspect of the present invention, the intermediate buffer proxy further includes a unique object identifier (OID).

[0029] According to a further aspect of the present invention, the intermediate buffer proxy further includes a Functional Requestor Identifier (FRI).

[0030] The method and intermediate buffer proxy provide the possibility to delay the load to the SM-SR function without jeopardizing the integrity of the chain between the EUM or OEM and the SM-SR function.

[0031] BRIEF DESCRIPTION OF THE DRAWINGS Further embodiments of the invention and its advantages will be explained in more detail with reference to the drawings, which merely illustrate examples of embodiments of the invention. Identical components in the drawings are given the same reference numerals. The drawings are not to be considered precisely to scale, in particular individual elements of the drawings may be shown in exaggerated or simplified form. [Brief description of the drawings]

[0032] [Figure 1] An example of a method known from the prior art using a transparent proxy is given below. [Diagram 2] An example of a method known from the prior art using a stop-and-go proxy is given below. [Diagram 3] 13 shows an example of a method according to a preferred embodiment using an intermediate buffer proxy. [Figure 4] 1 illustrates an example of a mobile communications network including an intermediate buffer proxy according to a preferred embodiment; DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0033] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS The present application relates to a method for managing at least one eUICC Information Set (EIS) of an eUICC, and to an intermediate buffer proxy 20. An eUICC is typically issued by an Equipment Manufacturer (EUM), often also called an Original Equipment Manufacturer (OEM).

[0034] Traditionally, for a telecommunications device to be able to connect to a particular mobile network, a SIM card issued by a mobile network operator (MNO) needs to be inserted into the device. In this manner, to switch the mobile connection to a different MNO, the SIM card for the current MNO is removed from the device and replaced with another SIM card associated with the new MNO. The requirement to replace SIM cards whenever a connection to a different mobile network is required is a major drawback, especially in the context of M2M communications. It would be highly efficient and desirable to have a single SIM card installed when manufacturing a device, and then that SIM card be able to support connection to the MNO of the user's choice.

[0035] To address this issue, the Global System for Mobile Association (GSMA) defines a remote provisioning architecture for embedded SIMs as a guide for mobile operators. eSIMs are embedded in IoT devices, providing a secure interoperability architecture to facilitate commercial deployment of systems that allow remote provisioning of target MNO profiles into the eSIM. GSMA specifies methods and protocols for MNOs to set up profile information on the eSIM using wireless communication channels. This method is called Over-the-Air (OTA) provisioning. OTA provisioning of entirely new SIM profiles can be used for devices moving through an operator network.

[0036] The eSIM supports multiple subscription profiles. These profiles can be added, enabled, disabled and removed as required. The GSMA is standardizing an OTA architecture for eSIM profile introduction and switching. Profile introduction and switching is compliant with the Global Platform Card standard (v2.2.1), which is incorporated herein by reference. The Subscription Manager Data Preparation (SM-DP) function is used to create SIM profiles, while the Subscription Manager Secure Routing (SM-SR) function is used to communicate with the eUICC to introduce, enable, disable and remove profiles. The Certificate Issuer (CI) is used for authentication and integrity protection.

[0037] One or more eSIM profiles may be set up on the eUICC, with each eSIM profile including a unique International Mobile Subscriber Identity (IMSI) number that authenticates the subscriber to a wireless communication carrier. Other data stored in the eSIM profile may include carrier network information, security authentication information, a list of accessible network services, and / or others. The wireless communication carrier may transfer the eSIM profile to the eUICC of a user device in the form of a consumer device or M2M device via an over-the-air (OTA) update.

[0038] Furthermore, the eUICC may include an eUICC Information Set (EIS), which represents the eUICC and may include an eUICC identifier, an identifier of the manufacturer of the eUICC, and further information (e.g. a list of profiles associated with the eUICC). The eUICC Information Set (EIS) is defined in the SGP.02 standard.

[0039] For example, the eUICC may have a file system as described in 3GPP TS 11.11 or 3GPP TS 11.14. An eUICC in the sense of the present invention can be an electronic module of reduced size and resources, for example having a control unit (microcontroller) and at least one interface (data interface) for communication with devices. Preferably, this communication takes place via a connection protocol, in particular a protocol conforming to the ETSI TS 102 221 or ISO-7816 standard.

[0040] The eUICC can be an integral part in a device, e.g. a hardwired electronic component. These eUICCs are not intended to be removed from the device and in principle cannot be easily replaced. Furthermore, such eUICCs can be designed as embedded secure elements and are secure hardware components in the device.

[0041] The eUICC can be used for remote monitoring, control and maintenance of equipment (machines, plants and systems). The eUICC can be used for metering units (e.g. electricity meters, hot water meters, etc.). For example, the eUICC is part of the technology of IoT.

[0042] A device in the sense of the present invention is in principle a device or a device component having means for communication with a communication network in order to be able to use the services of the communication network or to use the services of a server via a gateway of the communication network. For example, mobile devices (e.g. smartphones, tablet computers, notebooks, personal digital assistants) can be included under the term. Multimedia devices (e.g. digital picture frames, audio devices, televisions, e-book readers) further having means for communication with a communication network can also be understood as devices.

[0043] The device can be installed in a machine, a vending machine and / or a vehicle. When the device is placed in a car, the device typically has an integrated eUICC. The eUICC establishes a data connection to a server via a communication network through the device, for example by means of the device's modem. The device can be used to contact a server of the device manufacturer (EUM), for example to handle a control unit, for example an ECU (ECU = Electronic Control Unit), for the device's functionality. The eUICC can be used to contact a server in the background system of the mobile network operator MNO, for example a server that loads updates for the eUICC's software, firmware or / and operating system into the eUICC.

[0044] For example, setting up an eUICC and establishing a data connection to a server of a communication network in order to use the services of the server or another server or to exchange data. Establishing such a data connection from the eUICC to a server requires connection parameters (e.g. a unique server address and a data connection protocol to be used). For example, a Card Application Toolkit (CAT) for Subscriber Identity Modules conforming to ETSI standard TS 102 223 is used to establish, terminate and operate the data connection.

[0045] A communication network is a technical facility in which the transmission of signals takes place with identification and / or authentication of subscribers. A communication network provides specific services (specific voice and data services) and / or allows the use of services from external entities. Preferably, the communication network is a mobile network, by which communication between devices under the supervision of the communication network is possible. In particular, a mobile communication network here is to be, for example, the "Global System for Mobile communications" GSM as an example of the second generation, or the "General Packet Radio Service" GPRS, or the "Universal Mobile Telecommunications System" UMTS as an example of the third generation, or the "Long Term Evolution" LTE as an example of the fourth generation as a mobile communication network, or the fifth generation mobile communication network with the currently working name "5G" as a communication network. Communication in a communication network can take place, for example, via a secure channel (for example SCP80, SCP81 or Transport Layer Security TLS) as defined in the technical standards ETSI TS 102 225 and / or ETSI TS 102 226.

[0046] In the sense of the present invention, the server is an entity spatially separate from the device. The server may be part of the communication network. Alternatively or additionally, the server is an external instance (i.e. not an instance of the communication network). Preferably, the server is a server of the device manufacturer for handling a control unit for the functionality of the device, e.g. an electronic control unit (ECU). Alternatively or additionally, the server is a server for remote management of the eUICC, e.g. a so-called OTA server which loads updates for the software, firmware or / and operating system of the eUICC into the eUICC.

[0047] Subscriber identity data, for example as stored in a non-volatile memory area of ​​the eUICC, are for example data that uniquely identify a subscriber (person or device) in a communication network. This data includes for example a subscriber identifier, also known as the International Mobile Subscriber Identity or IMSI, and / or subscriber specific data. The IMSI is a subscriber identity file that is unique in a mobile communication network. The IMSI is composed of the country code MCC (Mobile Country Code), the network code MNC (Mobile Network Code) and a sequence number assigned by the network operator. Furthermore, subscriber identity data are for example data that uniquely authenticate a subscriber to a communication network (for example an authentication algorithm, specific algorithm parameters, a cryptographic authentication key Ki, and / or a cryptographic over-the-air or OTA key). Furthermore, subscriber identity data are for example data that uniquely authenticate a subscriber to a service (for example a unique identifier or a signature). The service is in particular a voice service or a data service of a server that transmits information and / or data over the communication network.

[0048] The eUICC may be operationally integrated into a device. The communication between the UICC and the device is based on a connection protocol. Furthermore, the device may be set up to also use the services of a remote server and independently establish a data connection to the remote server in order to exchange data with this server.

[0049] Profile management can be achieved by OTA communication between a server of the communication network (e.g. a subscription server conforming to the GSMA standard SGP.02 or a data provisioning server SM-DP, SM-DP+), e.g. using SMS, CAT_TP or HTTPS for over-the-air OTA communication with the eUICC. This profile management, which is not part of this specification, includes "Create", "Load", "Enable", "Disable", "Delete" and "Update". For further details, reference is made to the mentioned GSMA standard.

[0050] For some OEMs, EUMs or service providers (SPs), it is necessary to decide under what conditions and / or when to push the eUICC information set (EIS) to the subscription manager secure routing (SM-SR) function. For example, the condition for pushing the eUICC information set (EIS) to the subscription manager secure routing (SM-SR) function can be the registration and valid subscription of the eUICC in the Home Location Register (HLR), or the knowledge of the MNO that incorporates the eUICC into the device that is about to be powered on. Furthermore, the MNO needs to control multiple EUM providers and may need to decide which eUICC information set (EIS) to load to the subscription manager secure routing (SM-SR) function, from whom to load the eUICC information set (EIS) to the subscription manager secure routing (SM-SR) function, and when to load the eUICC information set (EIS) to the subscription manager secure routing (SM-SR) function. Furthermore, it may be necessary to outsource the ES1 interface as defined in the current GSMA SGP.02 standard to a third-party integrator. The ES1 interface serves as the interface between the two entities fulfilling the EUM and SM-SR functions.

[0051] However, the current GSMA SGP.02 standard does not provide such a possibility, since all interactions between the EUM or OEM and the SM-SR function need to be synchronous. Furthermore, the GSMA SGP.02 standard does not provide a mechanism for delaying the load on the Subscription Manager Secure Routing (SM-SR) function.

[0052] To partially meet the above mentioned needs of an OEM, EUM or SP, it is known from the prior art to provide a transparent proxy. A method known from the prior art using such a transparent proxy is shown in Figure 1. A transparent proxy intercepts standard application layer communications without requiring any special client configuration. A transparent proxy is a proxy that does not modify requests or responses beyond what is necessary for proxy authentication and identification. The client does not need to be aware of the presence of the proxy. A transparent proxy can be provided between the EUM or OEM and the SM-SR functionality.

[0053] Such a transparent proxy can be a single point of provisioning of EIS data where MNO data destined for the SM-SR function can be generated by the EUM or OEM and passed seamlessly to the SM-SR function via the BSS of the mobile communication network in a secure and standardized manner. When using a transparent proxy between the EUM or OEM and the SM-SR function, the transparent proxy must use the same Function Requestor Identifier (FRI) and Function Invocation Identifier (FCI) as the EUM or OEM. Optionally, a validity period of the request can be set.

[0054] All parameters used by the EUM or OEM in the request sent to the transparent proxy are passed unmodified to the SM-SR function. The EUM or OEM and the transparent proxy use the ES1 interface as defined by the GSMA SGP.02 standard. The request can be the request "ES1.RegiseterEISRequest" as defined in the GSMA SGP.02 standard.

[0055] Such a transparent proxy can act as a broker between the EUM or OEM and the SM-SR functionality, but cannot slow down the load on the Subscription Manager Secure Routing (SM-SR) functionality.

[0056] Alternatively, it is also known from the prior art to provide a stop-and-go proxy to partially meet the above-mentioned needs of an OEM, an EUM or a SP. A method known from the prior art using such a stop-and-go proxy is illustrated in FIG.

[0057] With such an approach, different FCIs can be used by the proxy and the EUM or OEM. However, this may break the trust on the chain from the EUM or OEM to the SM-SR function. Furthermore, the expiration of the validity period of the request may cause unknown behavior with respect to the EUM or OEM, the proxy and / or the SM-SR function. For example, if a retry mechanism starts to work, an endless loop may occur for a single EIS that may or may not be registered. With this approach, it is not possible to inform back from the EUM or OEM to the MNO if the request "RegisterEIS" is successful. Any change on the stop-and-go proxy side or on the EUM or OEM side affects all MNOs and all SM-Sr functions supported by the EUM or OEM.

[0058] A stop-and-go proxy between the EUM or OEM and the SM-SR function can delay the load on the Subscription Manager Secure Routing (SM-SR) function, but presents a risk if it compromises the integrity of the chain between the EUM or OEM and the SM-SR function and duplicates data in the SM-SR function or the EUM or OEM.

[0059] FIG. 3 illustrates an example of a method according to a preferred embodiment using an intermediate buffer proxy, and FIG. 4 illustrates an example of a mobile communications network including an intermediate buffer proxy according to a preferred embodiment.

[0060] According to this embodiment, a method for managing at least one eUICC information set (EIS) of an eUICC includes: - a step 110 of generating a first request for registering an eUICC Information Set (EIS) with an eUICC Manufacturer (EUM), the first request including a first Function Invocation Identifier (FCI); - a step 120 of sending a first request from the eUICC manufacturer (EUM) to the intermediate buffer proxy 20; - a step 130 of generating a response to the first request in the intermediate buffer proxy (20); - a step 140 of sending a response to the request to the eUICC manufacturer (EUM); Includes.

[0061] The intermediate buffer proxy according to the present application is configured to receive a first request from an eUICC manufacturer (EUM), generate a response to the first request, and send the response to the request to the eUICC manufacturer (EUM).

[0062] The method and intermediate buffer proxy 20 according to the present embodiment provide the possibility to delay the loading to the SM-SR function without jeopardizing the integrity of the chain between the EUM or OEM and the SM-SR function.

[0063] In other words, the intermediate buffer proxy 20 simulates the response of the SM-SR function to the EUM or OEM, or responds with a fake response to avoid the request becoming invalid after the expiration of the validity period of the request. Thus, the intermediate buffer proxy 20 acts as a SM-SR to the EUM or OEM.

[0064] The term MNO may be used synonymously with an MNO server communicating over a mobile network, the term EUM may be used synonymously with an EUM server communicating over a mobile network, and the term SM-SR function may be used synonymously with an SM-SR server performing SM-SR functions and communicating over a mobile network.

[0065] Before generating (110) and sending (120) the first request, the EUM or OEM may receive input data from the MNO. When sending (120) the first request to the intermediate buffer proxy 20, the EUM may simultaneously send a response file for HLR registration to the MNO. After the EUM receives the response to the request, the EUM may send an "ES1 registration result response" to the MNO.

[0066] The intermediate buffer proxy 20 may need to generate a new FCI for communication with the SM-SR function, especially if the FCI originating from the EUM or OEM is expired. Data validation can be performed in the intermediate buffer proxy 20 until the request is validated by the SM-SR.

[0067] The intermediate buffer proxy 20 may be identified by a unique object identifier (OID) and may include a unique FRI.

[0068] EIS data manipulation may be performed in the intermediate buffer proxy 20, for example, instead of being performed in the EUM or OEM.

[0069] The correlation between the FCI from the EUM or OEM and the FCI used by the intermediate buffer proxy 20 can be tracked by the intermediate buffer proxy 20. This makes it possible to ensure the integrity of the end-to-end communication between the EUM or OEM and the intermediate buffer proxy 20.

[0070] The method is: - a step 150 of generating a registration result response in the eUICC Manufacturer (EUM) after receiving a response to the request to the eUICC Manufacturer (EUM) at the eUICC Manufacturer (EUM); - step 160 of sending a registration result response to the Mobile Network Operator (MNO); It may further include.

[0071] Preferably, the method comprises: - a step 170 of generating at the intermediate buffer proxy 20 a second request to register an eUICC information set (EIS) based on the first request received at the intermediate buffer proxy, the second request including a second Function Invocation Identifier (FCI); - a step 180 of sending a second request from the intermediate buffer proxy 20 to a Subscription Manager Secure Routing (SM-SR) function; It may further include.

[0072] The intermediate buffer proxy 20 may be further configured to generate a second request to register the eUICC information set (EIS) and send the second request to a Subscription Manager Secure Routing (SM-SR) function.

[0073] Further, the method comprises: - a step 190 of receiving a second request from the intermediate buffer proxy 20 at a subscription manager secure routing (SM-SR) function; - step 200 of checking in the Subscription Manager Secure Routing (SM-SR) function that the eUICC Information Set (EIS) is present in an eUICC Information Set (EIS) directory stored in the Subscription Manager Secure Routing (SM-SR) function; It may further include.

[0074] Further, the method comprises: - storing 210 the eUICC Information Set (EIS) in a database of valid eUICC Information Sets (EIS) present in the Subscription Manager Secure Routing (SM-SR) function; - generating 220 a response to the second request in a Subscription Manager Secure Routing (SM-SR) function; - a step 230 of sending a response from the Subscription Manager Secure Routing (SM-SR) function to the second request to the intermediate buffer proxy 20; It may further include.

[0075] The intermediate buffer proxy 20 may be further configured to receive a response to the second request from a subscription manager secure routing (SM-SR) function.

[0076] The intermediate buffer proxy 20 may further include a unique object identifier (OID) and / or a unique functional requester identifier (FRI).

[0077] In other words, the intermediate buffer proxy 20 acts as a SM-SR function with respect to the EUM and as an EUM with respect to the SM-SR function. The intermediate buffer proxy 20 may send a provisional response to the EUM in response to a request to register a new EIS with the SM-SR function. The provisional response received in the EUM may trigger a registration response in the EUM that is sent to the MNO for confirmation. Redirection of the request received by the intermediate buffer proxy 20 to the SM-SR function may then be initiated at a later time and selected by the MNO, EUM, OEM or SP.

[0078] Thus, the intermediate buffer proxy 20 may act as a bridge for determining and coordinating the data exchanged between the EUM or OEM and the SM-SR functions.

[0079] The intermediate buffer proxy 20 may send fake responses to avoid expiration of the validity period in the EUM.

[0080] The intermediate buffer proxy 20 may "spoof", ie act as a SM-SR, to respond immediately to EUMs and avoid expiration.

[0081] Within the scope of the present invention, any of the elements described and / or illustrated and / or claimed may be combined in any manner.

Claims

1. 1. A method for managing at least one eUICC Information Set (EIS) of an eUICC, comprising the following successive steps: generating (110) a first request to register the eUICC Information Set (EIS) with an eUICC Manufacturer (EUM), the first request including a first Function Invocation Identifier (FCI); Sending (120) the first request from the eUICC manufacturer (EUM) to an intermediate buffer proxy (20); generating (130) a response to said first request within said intermediate buffer proxy (20); sending (140) the response to the request to the eUICC manufacturer (EUM); A method comprising:

2. The following sequential steps: generating (150) a registration result response within the eUICC Manufacturer (EUM) after receiving the response to the request to the eUICC Manufacturer (EUM) at the eUICC Manufacturer (EUM); sending (160) said registration result response to a Mobile Network Operator (MNO); The method of claim 1 further comprising:

3. The following sequential steps: generating (170) a second request to register the eUICC Information Set (EIS) at the intermediate buffer proxy (20) based on the first request received at the intermediate buffer proxy (20), the second request including a second Function Invocation Identifier (FCI); sending (180) said second request from said intermediate buffer proxy (20) to a Subscription Manager Secure Routing (SM-SR) function; 3. The method of claim 1 or 2, further comprising:

4. The following sequential steps: receiving (190) said second request from said intermediate buffer proxy (20) at said Subscription Manager Secure Routing (SM-SR) function; verifying (200) in the Subscription Manager Secure Routing (SM-SR) function that the eUICC Information Set (EIS) exists in an eUICC Information Set (EIS) directory stored in the Subscription Manager Secure Routing (SM-SR) function; The method of claim 3 further comprising:

5. storing (210) said eUICC Information Set (EIS) in a database of valid eUICC Information Sets (EIS) present in said Subscription Manager Secure Routing (SM-SR) function; generating (220) a response to the second request at the Subscription Manager Secure Routing (SM-SR) function; sending (230) the response from the Subscription Manager Secure Routing (SM-SR) function to the second request to the intermediate buffer proxy (20); The method of claim 4 further comprising:

6. An intermediate buffer proxy configured to receive a first request from an eUICC manufacturer (EUM) to register an eUICC information set (EIS), the first request including a first function call identifier (FCI), generate a response to the first request, and send the response to the request to the eUICC manufacturer (EUM).

7. 7. The intermediate buffer proxy of claim 6, further configured to generate a second request to register the eUICC Information Set (EIS) and send the second request to a Subscription Manager Secure Routing (SM-SR) function.

8. 8. The intermediate buffer proxy of claim 7, further configured to receive a response to the second request from the Subscription Manager Secure Routing (SM-SR) function.

9. An intermediate buffer proxy according to any one of claims 6 to 8, characterized in that it comprises a unique object identifier (OID).

10. An intermediate buffer proxy according to any one of claims 6 to 8, characterized in that it includes a unique Functional Requestor Identifier (FRI).

11. An intermediate buffer proxy according to any one of claims 6 to 8, characterized in that it is configured to generate a new Function Call Identifier (FCI) for communication with the Subscription Manager Secure Routing (SM-SR) function.

Images