WO2018129754A1

WO2018129754A1 - Euicc configuration file management method and related device

Info

Publication number: WO2018129754A1
Application number: PCT/CN2017/071322
Authority: WO
Inventors: 龙水平
Original assignee: 华为技术有限公司
Priority date: 2017-01-16
Filing date: 2017-01-16
Publication date: 2018-07-19
Also published as: CN109792604B; CN109792604A

Abstract

Provided in the embodiments of the present invention are an embedded universal integrated circuit card (eUICC) configuration file management method, comprising: establishing an eUICC management session with an eUICC remote management server; acquiring user intention configuration information from the eUICC remote management server by means of the eUICC management session; verifying the user intention configuration information; performing no user intention confirmation step during the current eUICC management session if the verification on the user intention configuration information is successful, wherein the eUICC management session is used for performing at least one operation of: an eUICC configuration file download and installation operation, an eUICC configuration file activation operation, an eUICC configuration file deactivation operation or an eUICC configuration file deletion operation. By using the present invention, a profile may be efficiently downloaded and installed, and efficient remote profile management may be implemented.

Description

EUICC configuration file management method and related device

Technical field

The present invention relates to the field of eUICC telecommunications smart cards, and in particular, to an eUICC configuration file management method and related apparatus.

Background technique

The eUICC is a removable or non-removable Universal Integrated Circuit Card (UICC) that performs remote profile management in a secure manner or performs local profile management (eg, terminal device user triggered profiles) Activate, deactivate or delete, etc.). The word eUICC is derived from an embedded UICC, which may be embedded in a terminal device in a single chip form, or as part of other single chips in the terminal device, but does not mean that it must be embedded in the terminal device and cannot be moved, or it may be The removable card form is like a SIM card, a Micro SIM card or a Nano SIM card. eUICC is sometimes called eSIM. The eUICC profile is a combination of data and applications. It is configured on the eUICC for the purpose of providing services. The so-called services include calling, sending and receiving text messages, or data services. The Profile can also be regarded as a SIM (Subscriber Identification Module) software module. Like the traditional SIM card, it performs functions such as authentication calculation when the terminal device accesses the mobile network.

The eUICC remote configuration/management system (also known as the remote SIM configuration system) is shown in Figure 1, where the Contract Manager Data Preparation+ (SM-DP+) server is used to prepare the profile and will be ready. The profile is securely sent to the eUICC module of the terminal device, and the profile is remotely managed. The SM-DP+ can be deployed on the server of the operator, the eUICC manufacturer, the original equipment manufacturer (OEM) or other parties; The Subscription Manager Discovery Service (SM-DS) server is used to provide the SM-DP+ address (or one or more) to the terminal device, and the terminal device can communicate with the SM through the SM-DP+ address. -DP+ establishes a connection, or the terminal device further obtains the SM-DP+ address by replacing the SM-DS; the terminal device (Device) includes a local profile assistant (LPA) module for establishing a connection with the SM-DP+. Related management operations for Profile and eUICC, such as download and installation, remote profile management and remote eUICC management, eUICC module for implementing SIM Card functions and profile and eUICC configuration and management functions; Operator BSS is the operator's business support system, which is responsible for ordering profiles to SM-DP+ and requesting management of profiles on eUICC; End User is End device user/user; eUICC Manufacturer (EUM) is a manufacturer of eUICC. SM-DP+, SM-DS are all called eUICC management servers (or remote SIM configuration servers).

In the prior art, the information needs to be downloaded to the eUICC module of the terminal device to enable the terminal device to have a communication function. The download, activation, deactivation, or deletion of the profile requires the terminal device to interact with the user and obtain the user intention confirmation command. Achieved. For enterprise users, before distributing the terminal device to employees, the enterprise needs to purchase a batch of profiles in batches, and then interact with each terminal device separately, downloading the profiles one by one to the terminal device, which wastes time, and the download efficiency of the profile is very high. Low; in addition, if the enterprise asset administrator needs to manage the installed profiles on all terminal devices, when the asset administrator triggers the remote profile management process, The enterprise employee who wants to hold the terminal device can confirm the profile on the terminal device, which is not conducive to unified management of the profile on the terminal device.

Summary of the invention

The technical problem to be solved by the embodiments of the present invention is to provide an eUICC configuration file management method and related devices, which implement efficient downloading and installation of profiles, and efficient remote profile management.

In a first aspect, an embodiment of the present invention provides an eUICC configuration file management method, including: establishing an eUICC management session with an eUICC remote management server;

Obtaining user intent configuration information from the eUICC remote management server through the eUICC management session;

Verifying the user intent configuration information;

In the case that the verification of the user intent configuration information is passed, the user intent confirmation step is not performed during the current eUICC management session, wherein the eUICC management session is used to execute the eUICC configuration file download and installation operation, eUICC At least one of a profile activation operation, an eUICC profile deactivation operation, or an eUICC profile deletion operation.

In a first possible implementation manner of the first aspect, the user intention configuration information is a user intention indication; or the user intention configuration information is a first signature value; or the user intention configuration information is a first signature value and the first The owner name of the digital certificate corresponding to the signature value.

In a second possible implementation manner of the first aspect, the user intention configuration information is a first signature value, where the first signature value includes a signature of the first to-be-signed data by using the first key, where the first key is The public key, the private key, or the symmetric key; after the user intent configuration information is obtained, the local first to-be-signed data is generated, where the local first to-be-signed data includes an operation type, an operator identifier, and an eUICC remote management server object identifier; The second key corresponding to the first key and the local first to-be-signed data verify the first signature value to implement verification of the user intent configuration information.

With the second possible implementation of the first aspect, in a third possible implementation, the second to-be-signed data and the second signature value are obtained from the eUICC remote management server by using the eUICC management session, where the second to-be The signature data includes user intention configuration information, and the second signature value is a signature of the second signature data and the authentication signature value by using the third key, and the authentication signature value is generated during the establishment of the eUICC management session; After the data to be signed and the second signature value, the local first to-be-signed data is generated; the second signature value is verified by the fourth key corresponding to the third key, the second to-be-signed data, and the authentication signature value, and then The first signature value is verified by the second key corresponding to the first key and the local first to-be-signed data, thereby verifying the user intention configuration information.

In a fourth possible implementation manner of the first aspect, the user intention configuration information is a first signature value and an owner name of the digital certificate corresponding to the first signature value, where the first signature value includes using the first key pair The signature of the first data to be signed, the first key is a public key, a private key, or a symmetric key; after the user intent configuration information is obtained, the local first to-be-signed data is generated, where the local first to-be-signed data includes an operation type. The operator identifier and the eUICC remote management server object identifier; the first signature value is verified by the second key corresponding to the first key and the local first to-be-signed data, and the data corresponding to the first signature value is simultaneously The owner name of the certificate is verified to verify the user intent configuration information.

In conjunction with the fourth possible implementation of the first aspect, in a fifth possible implementation, the second to-be-signed data and the second signature value are obtained from the eUICC remote management server by using the eUICC management session, where the second to be The signature data includes user intention configuration information, and the second signature value is a signature of the second signature data and the authentication signature value by using the third key, wherein the authentication signature value is generated during the establishment of the eUICC management session; After the second to-be-signed data and the second signature value, the local first to-be-signed data is generated, where the local first to-be-signed data includes an operation type, an operator identifier, and an eUICC remote management server object identifier; The fourth key, the second to-be-signed data, and the authentication signature value verify the second signature value, and then perform the first signature value by using the second key corresponding to the first key and the local first to-be-signed data. Verification, at the same time, verifying the owner name of the data certificate corresponding to the first signature value, thereby realizing verification of the user intent configuration information.

In a sixth possible implementation manner of the first aspect, the user intention configuration information is a user intention indication, and the third to-be-signed data and the third signature value are obtained from the eUICC remote management server by using the eUICC management session, where the third to be The signature data includes user intention configuration information, and the third signature value is a signature of the third signature data and the authentication signature value by using the third key, wherein the authentication signature value is generated during the establishment of the eUICC management session; After the third to-be-signed data and the third signature value, the third signature value is verified by the fourth key, the third to-be-signed data, and the authentication signature value corresponding to the third key, and then the user intention indication is verified. Validation to achieve verification of user intent configuration information.

In a second aspect, an embodiment of the present invention provides another eUICC configuration file management method, including:

Establish an eUICC management session with the eUICC remote management server;

Sending a user intent verification instruction to the eUICC module, where the user intent verification instruction is used by the eUICC module to verify the user intent configuration information, wherein the user intent verification instruction carries the user intent configuration information;

In a first possible implementation manner of the second aspect, the user intention configuration information is a user intention indication; or the user intention configuration information is a first signature value; or the user intention configuration information is a first signature value and the first The owner name of the digital certificate corresponding to the signature value.

In a second possible implementation manner of the second aspect, the user intention configuration information is a first signature value, where the first signature value includes a signature of the first to-be-signed data by using the first key, where the first key is a public key, a private key, or a symmetric key; generating a local first to-be-signed data before sending the user intent instruction to the eUICC module, where the local first to-be-signed data includes an operation type, an operator identifier, and an eUICC remote management server object identifier; The user intent verification command carries the local first to-be-signed data, and the local first to-be-signed data is used by the eUICC module to verify the first signature value by using the second key corresponding to the first key to verify the user intent configuration information. .

With the second possible implementation of the second aspect, in a third possible implementation manner, the second to-be-signed data and the second signature value are obtained from the eUICC remote management server by using the eUICC management session, where the second to-be The signature data includes user intention configuration information, and the second signature value is a signature of the second signature data and the authentication signature value by using the third key, wherein the authentication signature value is generated during the establishment of the eUICC management session; user verification In the instruction And carrying the second to-be-signed data and the second signature value, wherein the second to-be-signed data and the authentication signature value are used by the eUICC module to verify the second key value corresponding to the third key. Thereby verifying the user intent configuration information.

In a fourth possible implementation manner of the second aspect, the user intention configuration information is a user intention indication; obtaining the third to-be-signed data and the third signature value from the eUICC remote management server by using the eUICC management session, where the third The data to be signed includes user intention configuration information, and the third signature value is a signature of the third to-be-signed data and the authentication signature value by using the third key, wherein the authentication signature value is generated during the establishment process of the eUICC management session; The verification instruction further carries the third to-be-signed data and the third signature value, wherein the third to-be-signed data and the authentication signature value are used by the eUICC module for the fourth key pair corresponding to the third key to the third signature. The value is verified; the user intent is used by the eUICC to verify whether the validation is valid to enable verification of the user intent configuration information.

In a third aspect, the embodiment of the present invention provides another eUICC configuration file management method, including:

Receiving a user intent verification instruction sent by the local eUICC configuration file auxiliary module, where the user intent verification instruction carries user intent configuration information, where the local intent configuration information is the local eUICC configuration file auxiliary module from the eUICC remote management server The eUICC management session is obtained;

Verifying the user intent configuration information;

In a first possible implementation manner of the third aspect, the user intention configuration information is a user intention indication; or the user intention configuration information is a first signature value; or the user intention configuration information is a first signature value and the first The owner name of the digital certificate corresponding to the signature value.

In a second possible implementation manner of the third aspect, the user intention configuration information is a first signature value, where the first signature value includes a signature of the first to-be-signed data by using the first key, where the first key is The public key, the private key, or the symmetric key; the user intent verification command further carries the local first to-be-signed data, wherein the local first to-be-signed data is generated by the local eUICC configuration file auxiliary module, and the local first to-be-signed data includes the operation type. And the operator identifier and the eUICC remote management server object identifier; verifying the user signature configuration information by verifying the first signature value by using the second key corresponding to the first key and the local first to-be-signed data.

With the second possible implementation of the third aspect, in a third possible implementation manner, the user verification instruction further carries the second to-be-signed data and the second signature value, where the second to-be-signed data includes the User intention configuration information, the second signature value includes a signature of the second signature data and an authentication signature value by using a third key; and a fourth key corresponding to the third key, the second And verifying, by the signature data and the authentication signature value, the second signature value, and verifying the first signature value by using the second key corresponding to the first key and the local first to-be-signed data to implement The user intends to configure the information for verification.

In a fourth possible implementation manner of the third aspect, the user intent configuration information includes a first signature value, where the first signature value includes a signature of the first to-be-signed data by using the first key, The first key includes a public key, a private key, or a symmetric key; the user intent verification instruction further carries a configuration tube that generates a local first to-be-signed data. The first data to be signed is generated after receiving the user intent verification command sent by the local eUICC configuration file auxiliary module, where the local first to-be-signed data is generated by the local eUICC configuration file auxiliary module, The local first to-be-signed data includes an operation type, an operator identifier, and an eUICC remote management server object identifier; and the first signature is obtained by using a second key corresponding to the first key and the local first to-be-signed data The value is verified.

In a fifth possible implementation manner of the third aspect, the user intention configuration information is a user intention indication; the user verification instruction further carries a third to-be-signed data and a third signature value, where the third to-be-signed data includes the User intention configuration information, the third signature value includes a signature of the third signature data and an authentication signature value by using a third key; and a fourth key corresponding to the third key, the third The to-be-signed data and the authentication signature value verify the third signature value and confirm that the verification passes; and then verify whether the user intention indication is effective to verify the user intent configuration information.

In a fourth aspect, an embodiment of the present invention provides an eUICC configuration file management apparatus, including:

a management session establishing module, configured to establish an eUICC management session with the eUICC remote management server;

a configuration information obtaining module, configured to acquire user intent configuration information from the eUICC remote management server by using the eUICC management session;

a verification module, configured to verify the user intent configuration information;

An execution module, configured to perform a user intent confirmation step during the current eUICC management session, where the eUICC management session is used to perform eUICC configuration file downloading, if the verification of the user intent configuration information is passed And at least one of an installation operation, an eUICC profile activation operation, an eUICC profile deactivation operation, or an eUICC profile deletion operation.

In a fifth aspect, an embodiment of the present invention provides a local eUICC configuration file auxiliary module, including:

a management session establishing unit, configured to establish an eUICC management session with the eUICC remote management server;

a configuration information acquiring unit, configured to acquire user intent configuration information from the eUICC remote management server by using the eUICC management session;

a verification instruction sending unit, configured to send a user intention verification instruction to the eUICC module, where the user intention verification instruction is used by the eUICC module to verify the user intent configuration information, where the user intention verification instruction carries User intent configuration information;

a first execution unit, configured to perform a user intent confirmation step during the current eUICC management session, where the eUICC management session is used to perform eUICC configuration, in the case that the verification of the user intent configuration information is passed At least one of a file download and install operation, an eUICC profile activation operation, an eUICC profile deactivation operation, or an eUICC profile delete operation.

In a sixth aspect, an embodiment of the present invention provides an eUICC module, including:

a verification instruction receiving unit, configured to receive a user intent verification instruction sent by the local eUICC configuration file auxiliary module, where the user intent verification instruction carries user intent configuration information, where the user intent configuration information is the local eUICC configuration file auxiliary The module is obtained from an eUICC management session with the eUICC remote management server;

a verification unit, configured to verify the user intent configuration information;

a second execution unit, configured to perform a user intent confirmation step during the current eUICC management session, where the eUICC management session is used to perform eUICC configuration, in the case that the verification of the user intent configuration information is passed At least one of a file download and install operation, an eUICC profile activation operation, an eUICC profile deactivation operation, or an eUICC profile delete operation.

In a seventh aspect, an embodiment of the present invention provides an eUICC configuration file management apparatus, including: a processor, a memory, and a transceiver, wherein the processor, the memory, and the transceiver are connected to each other by a bus, wherein the memory is used for storing Program code, the processor is used to call the program code, and performs the following operations:

Establish an eUICC management session with the eUICC remote management server;

Verifying the user intent configuration information;

In an eighth aspect, an embodiment of the present invention provides a terminal, including: a processor, a memory, and a transceiver, wherein the processor, the memory, and the transceiver are connected to each other by a bus, where the memory is used to store program code, where The processor is configured to invoke the program code and perform the following operations:

Establish an eUICC management session with the eUICC remote management server;

According to a ninth aspect, an embodiment of the present invention provides an eUICC module, including: a processor, a memory, and a transceiver, wherein the processor, the memory, and the communication interface are connected to each other by a bus, wherein the memory is used to store program code. The processor is configured to invoke the program code and perform the following operations:

Verifying the user intent configuration information;

In the case that the verification of the user intent configuration information is passed, during the current eUICC management session, The user intent confirmation step is not performed, wherein the eUICC management session is used to perform at least one of an eUICC profile download and install operation, an eUICC profile activation operation, an eUICC profile deactivation operation, or an eUICC profile deletion operation.

By implementing the embodiment of the present invention, the user intent configuration information is obtained from the eUICC remote management server, and the user intent configuration information is verified. If the verification of the user intent configuration information is passed, the eUICC management session is not executed during the current eUICC management session. The user intent confirms the steps, omitting the interaction process with the user, thereby enabling efficient downloading and installation of the eUICC configuration file, and efficient remote eUICC configuration file management.

DRAWINGS

In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the background art, the drawings to be used in the embodiments of the present invention or the background art will be described below.

Figure 1 is a system architecture diagram of eUICC;

2 is a schematic flowchart of a method for managing an eUICC configuration file according to an embodiment of the present invention;

3 is a schematic flowchart of another eUICC configuration file management method according to an embodiment of the present invention;

4 is a schematic flowchart of a method for initializing an SM-DP+ according to an embodiment of the present invention;

FIG. 5 is a schematic flowchart of generating localuserintentfreeSigned by eUICC according to an embodiment of the present invention;

FIG. 6 is a schematic flowchart of still another eUICC configuration file management method according to an embodiment of the present disclosure;

FIG. 7 is a schematic flowchart of still another eUICC configuration file management method according to an embodiment of the present disclosure;

FIG. 8 is a schematic flowchart of still another eUICC configuration file management method according to an embodiment of the present disclosure;

FIG. 9 is a schematic structural diagram of an eUICC configuration file management apparatus according to an embodiment of the present invention;

FIG. 10 is a schematic structural diagram of another eUICC configuration file management apparatus according to an embodiment of the present disclosure;

11 is a schematic structural diagram of a local eUICC configuration file auxiliary module according to an embodiment of the present invention;

FIG. 12 is a schematic structural diagram of a terminal according to an embodiment of the present disclosure;

FIG. 13 is a schematic structural diagram of an eUICC module according to an embodiment of the present disclosure;

FIG. 14 is a schematic structural diagram of another eUICC module according to an embodiment of the present invention.

detailed description

The embodiments of the present invention are described below in conjunction with the accompanying drawings in the embodiments of the present invention.

Referring to FIG. 2, FIG. 2 is a schematic flowchart of a method for managing an eUICC configuration file according to an embodiment of the present invention. The method of the embodiment of the present invention may be implemented in the system architecture shown in FIG. 1, including but not limited to The following steps:

Step S101: The terminal device establishes an eUICC management session with the eUICC remote management server.

Specifically, as shown in FIG. 1 , the terminal device may include an LPA module and an eUICC module, where the LPA module and the eUICC module may be two modules that are separated from each other and have a physical or logical connection relationship, for example, the LPA module exists on the baseband chip. On the application processor or other hardware modules of the terminal device; the LPA module can also be saved directly It is on the eUICC module. Specifically, the LPA module can be a software module or a plurality of software modules that are distributed and associated.

Specifically, the eUICC management session may be a Remote SIM Provisioning (RSP) session.

Specifically, the eUICC management session may be initiated by the LPA module, and the LPA assists the two-way authentication authentication between the eUICC module and the eUICC remote management server to establish an eUICC management session.

Step S102: The terminal device acquires user intent configuration information from the eUICC remote management server by using the eUICC management session.

Specifically, the eUICC remote management server may be an SM-DP+, or may be another server capable of providing an eUICC configuration file and capable of remotely managing the eUICC configuration file.

Specifically, the user intent configuration information may be a first signature value; or may be a user intention indication; or may be a first signature value and an owner name of the digital certificate corresponding to the first signature value.

Step S103: The terminal device verifies the user intent configuration information.

The user intent configuration information is used to indicate that the terminal saves, deactivates, or skips the step of interacting with the user during the current eUICC management session.

Specifically, in the case where the verification of the user's intention configuration information is passed, step S105 is performed.

Specifically, the content or type of the user's intentional configuration information is different, and the specific process for the terminal device to verify the user's intended configuration information is different. In the specific process, the terminal may not only verify the user's intention configuration information, but also configure the information with the user's intention. Relevant information is verified.

Step S104: In the case where the verification of the user's intention configuration information fails, the terminal device performs a user intention confirmation step.

Specifically, when the verification of the user intent configuration information fails, the terminal device may display, on the interface, “whether or not to agree to download”, “please input a confirmation code”, and obtain a confirmation operation of the user, and obtain the confirmation of the user. The subsequent steps are performed after the operation.

Step S105: The terminal device performs at least one of an eUICC configuration file download and install operation, an eUICC configuration file activation operation, an eUICC configuration file deactivation operation, or an eUICC configuration file deletion operation.

Specifically, the eUICC configuration file can be a profile.

The implementation of the foregoing embodiment is specifically described in the following with reference to the system architecture of FIG. 1. The second embodiment to the fifth embodiment of the present invention mainly introduce the LPA module and the eUICC module. In the case where the modules of the above-mentioned embodiments are implemented in the case where the LPA modules are directly present in the eUICC module, it is considered that only the steps performed by the LPA module and the eUICC module are combined to form a solution. Do the discussion. The following embodiment is described in detail by using the LPA module of the LPA on behalf of the terminal device, the eUICC module of the eUICC on behalf of the terminal device, the SM-DP+ on behalf of the eUICC remote management server, and the profile on behalf of the eUICC configuration file.

Referring to FIG. 3, FIG. 3 is a schematic flowchart of a method for managing an eUICC configuration file according to a second embodiment of the present invention. In the embodiment of the present invention, the eUICC management session is used to perform an eUICC configuration file download and installation operation, The specific implementation process is as follows:

Step S201: The LPA acquires the SM-DP+ address.

Specifically, under the conditions of user operation, power-on, timing trigger, or eUICC triggering, the LPA can obtain an SM-DP+ address and an event identifier (Event ID) from the SM-DS. The EventID can identify the profile to be downloaded event, or can identify Profile or eUICC remote management events, download or management events can be targeted to single or multiple terminals/eUICC. The LPA can send the EventID to the SM-DP+ through the Matching ID parameter.

Optionally, the LPA may also obtain a default SM-DP+ address from the eUICC. For example, the terminal device is custom-produced by the operator A, the operator A specifies an SM-DP+ address preset in the eUICC, or the OEM terminal. The vendor presets an SM-DP+ address shared by multiple operators in the eUICC.

Step S202: The LPA establishes a Transport Layer Security (TLS) connection with the SM-DP+.

Specifically, for example, the LPA performs one-way certificate authentication on the SM-DP+, and establishes a TLS connection after the authentication is passed.

Step S203: The eUICC and the SM-DP+ perform two-way authentication based on the HyperText Transfer Protocol Secure (HTTPS).

Specifically, HTTPS runs on top of a TLS connection.

Specifically, the LPA obtains the eUICC challenge value and the like from the eUICC, sends an HTTPS request (including the eUICC challenge value) to the SM-DP+, triggers the eUICC and the SM-DP+ to perform bidirectional authentication, and the bidirectional authentication data exchange passes the HTTPS request and response. Message and interface implementation of LPA and eUICC. In the two-way authentication process, the eUICC generates its own authentication signature value (euiccSignature1) and sends eucicSignature1 to SM-DP+, SM-DP+ and eUICC both store eucicSignature1; meanwhile, SM-DP+ will authenticate the certificate (CERT. DPauth.ECDSA) is sent to eUICC, eUICC saves CERT.DPauth.ECDSA; after two-way authentication is passed, SM-DP+ generates session identification (TransactionID).

At this point, after the two-way authentication, the RSP session between the terminal device and the SM-DP+ is successfully established.

Step S204: The SM-DP+ obtains a Profile download pending order or a Batch Profile download pending order by searching.

Specifically, in the two-way authentication process, the terminal device sends a MatchingID or an eUICC identifier (EID) to the SM-DP+.

Specifically, SM-DP+ can find a Profile download pending order or a Batch Profile download pending order by using MatchingID or EID.

Specifically, the Profile download pending order or the Batch Profile download pending order may be generated during the profile download initialization process of the SM-DP+, and FIG. 4 is a schematic diagram of the profile download initialization process of the SM-DP+.

Before downloading the profile to the eUICC of the terminal device, the individual or enterprise user needs to sign a contract with the operator to complete the account opening process, and then the operator business support system (Operator BSS) instructs the SM-DP+ as the user. A single or batch of profiles is prepared for the user's terminal device to download. After the eUICC downloads and installs the profile successfully and the profile is activated, the Operator mobile network can provide various services for the terminal device users, including calling, receiving short messages, and data services. In the process of signing the user and the Operator, optionally, the Operator BSS can obtain the international mobile device identity of the user terminal device (International Mobile Equipment Identity, IMEI), capability information, and eUICC Identification (EID). In the process of preparing the profile, the operator BSS sends the EID to the SM-DP+. The SM-DP+ generates a profile pending event according to the Operator BSS indication, and waits for the user terminal device to perform the profile download. If the enterprise user is contracted with the operator, the Operator BSS optionally sends the batch eUICC identifier (ie, EIDs) to the SM-DP+, and the SM-DP+ generates a batch profile to be downloaded event or for each terminal device/eUICC. Generate a single profile to be downloaded event. The following takes the enterprise user as an example to introduce the SM-DP+ profile download initialization process:

Step S1: The Operator BSS sends a download command (DownloadOrder) to the SM-DP+, where the DownloadOrder can carry the batch eUICC identifier (EIDs), the profile type (Profile Type), or the batch profile ID (Integrated Circuit Card ID, ICCIDs).

Among them, the EIDs are optional, that is, the DownloadOrder may also not carry the EIDs.

Step S2: SM-DP+ saves the ICCIDs, EIDs and sends a reply command to the Operator BSS.

Specifically, the reply instruction is a response message.

Optionally, the Operator BSS may generate a batch matching identifier (MatchingIDs) after receiving the reply instruction, and the MatchingID may match the profile to be downloaded event generated by the SM-DP+.

Optionally, Operator BSS can also be configured in the background.

Step S3: Optionally, the Operator BSS obtains the terminal device from the user intent to authorize the userintentfreeSignature.

The userintentfreeSignature may indicate that the LPA omits, deactivates, or skips the step of user intent confirmation in the current RSP session. For example, let the user confirm the steps of accepting the operator Profile Policy Rules (PPR), let the user confirm the steps of downloading and installing the profile, let the user enter the verification code, and the steps can be merged.

Alternatively, userintentfreeSignature can also be defined with other names.

Specifically, the userintentfreeSignature can be sent to the LPA through the SM-DP+ included in the user intent configuration information (userintentConfiguration).

Specifically, Operator BSS can obtain userintentfreeSignature from Enterprise, OEM, or EUM.

Specifically, the userintentConfiguration may be a userintentfreeSignature or a {Signer, userintentfreeSignature}, where the userintentfreeSignature is a signature of the first to-be-signed data by using the first key (ie, a first signature value), and the first to-be-signed data may be {euicc Operation Type, Operatorid, SM-DP+OID}, optionally, the first to-be-signed data may further include EIDs, that is, the first to-be-signed data is {euicc Operation Type, Operatorid, SM-DP+OID, EIDs}, where the eucic Operation Type is an eUICC management operation type, the Operatorid is an operator identifier, the SM-DP+OID is an SM-DP+Object Identifications (OID), and the Signer is a digital certificate corresponding to the first key. The owner name, for example, may be the Distinguished Name (DN) of the OEM digital certificate, the EUM digital certificate or the Enterprise digital certificate. For example, the Operator BSS obtains the userintentfreeSignature from the OEM, and the Signer is the DN name of the OEM digital certificate.

Specifically, in the embodiment of the present invention, the eucic Operation Type is Profile Download.

Optionally, the first key may be a public key (PK), a private key (Secret Key, SK), or a symmetric key.

Specifically, the EIDs may be represented in various forms, for example, may be represented as any one of EID _start | EID _end , EID _start | Count, or EID list, and combinations thereof.

Step S4: The Operator BSS sends a confirmation command (ConfirmOrder) to the SM-DP+, wherein the ConfirmOrder carries {Signer, userintentfreeSignature}.

Among them, Signer is optional. When userintentConfiguration is userintentfreeSignature, ConfirmOrder only carries userintentfreeSignature.

Optionally, the ConfirmOrder may further carry ICCIDs, EIDs, Confirmation Codes, MatchingIDs, wherein the Confirmation Codes are a batch of Confirmation Codes for enhancing the security of the profile download.

Step S5: SM-DP+ generates a Batch Profile download pending order.

Optionally, SM-DP+ can also generate a single Profile to be downloaded event for each terminal device/eUICC.

Specifically, the Batch Profile download pending order may include Signer, userintentfreeSignature, eventID, MatchingIDs, EIDs, and a batch of profiles generated by SM-DP+.

At this point, the SM-DP+ profile download initialization process is completed, and the SM-DP+ prepares a batch of profiles for the enterprise user. Optionally, the name of the batch pending download event is not limited to the description of the Batch Profile download pending order in the embodiment of the present invention. It can also be described by other names, mainly used to distinguish existing single profile pending download events.

Specifically, the SM-DP+ can find a Profile download pending order or a Batch Profile download pending order according to the MatchingID or EID sent by the terminal device.

Step S205: The SM-DP+ performs the validity check using the terminal device information (Device Info) and the eUICC information (euicc Info2).

Specifically, the SM-DP+ checks, for example, whether the firmware information, version information, and the like of the terminal device and the eUICC match the profile in the download pending order.

Step S206: SM-DP+ generates Profile metadata (Metadata), checks whether it is a download retry, generates second to-be-signed data (for example, smdpSigned2), smdpSigned2={TransactionID, and confirmation code Required Flag ), temporary key pair public key (bppEuiccOtpk)}.

Specifically, the TransactionID is generated by SM-DP+ during the establishment of the RSP session, and the Confirmation Code Required Flag is set to 'True' or "False' (depending on whether the SM-DP+ receives the Confirmation Code during the profile download initialization process, bppEuiccOtpk is The abruptly terminated profile downloads the public key portion of the temporary public-private key pair generated by the eUICC in the RSP session.

Step S207: SM-DP+ performs a signature calculation on smdpSigned2 and eucicSignature1 by using a third key (SK.DPpb.ECDSA) to generate a second signature value (for example, smdpSignature2), where SK.DPpb.ECDSA is a configuration file of SM-DP+ Bind the private key of the ProfileBinding digital certificate (CERT.DPpb.ECDSA).

Specifically, SM-DP+ may generate a digest of smdpSigned2|euiccSignature1 (the "|" symbol is used to concatenate the two data before and after), and then encrypt the digest with SK.DPpb.ECDSA to generate smdpSignature2. For example, A={smdpSigned2, eucicSignature1}, the abstract is obtained by summing A, and the result of encrypting the digest a by SK.DPpb.ECDSA is the second signature value smdpSignature2.

Step S208: SM-DP+ sends Profile Metadata, smdpSigned2, smdpSignature2, CERT.DPpb.ECDSA, userintentConfiguration, and EIDs to the LPA.

Among them, EIDs are optional.

Step S209: The LPA confirms receipt of the userintentConfiguration, and generates local first to-be-signed data (localuserintentfreeSigned), localuserintentfreeSigned={euicc Operation Type, Operatorid, SM-DP+OID}.

In another embodiment, localuserintentfreeSigned={euicc Operation Type, Operatorid, SM-DP+OID, EIDs}.

Specifically, the LPA identifies the eUICC Operation Type as Profile download by Profile Metadata, assigns the Profileowner in the Profile Metadata to the Operatorid, and obtains the SM-DP+OID from the CERT.DPpb.ECDSA certificate.

Step S210: The LPA verifies that the EID of the local eUICC is within the EIDs.

Step S211: The LPA sends localuserintentfreeSigned, userintentConfiguration, TransactionID, and CERT.DPpb.ECDSA to the eUICC.

Specifically, the LPA reads the Transaction ID from smdpSigned2.

In another implementation manner, the localuserintentfreeSigned may be generated by the eUICC. In this case, the steps S209 to S211 are as shown in FIG. 5, and may be replaced by:

Step S209-1: The LPA confirms receipt of the userintentConfiguration, and generates the eucic Operation Type and the Operatorid.

The manner in which the LPA generates the eucic Operation Type and the Operatorid is the same as that in the step S209, and will not be described again.

Step S210-1: Optionally, the LPA verifies that the EID of the local eUICC is within the EIDs.

Step S211-1: The LPA sends the eucic Operation Type, Operatorid, userintentConfiguration, TransactionID, and CERT.DPpb.ECDSA to the eUICC.

Optionally, if the first to-be-signed data is {euicc Operation Type, Operatorid, SM-DP+OID, EIDs}, the LPA may also send the EIDs to the eUICC.

Step S211-2: eUICC generates localuserintentfreeSigned.

Step S212: The eUICC verifies that CERT.DPpb.ECDSA is legal and belongs to the same SM-DP+ as CERT.DPauth.ECDSA, and verifies that the TransactionID matches the current RSP session.

Specifically, the eUICC compares the two SM-DP+OIDs obtained by acquiring the SM-DP+OIDs from CERT.DPpb.ECDSA and CERT.DPauth.ECDSA respectively, if the two SM-DP+OIDs are the same. Then it is determined that CERT.DPpb.ECDSA belongs to the same SM-DP+ as CERT.DPauth.ECDSA.

Step S213: The eUICC verifies the userintentConfiguration.

Specifically, the eUICC verifies the userintentfreeSignature by using a second key corresponding to the first key and localuserintentfreeSigned.

Optionally, the second key and the first key may be mutually symmetric keys or asymmetric keys, for example, the first key and the second key are mutually asymmetric keys, and then When the key is PK, the second key is SK, when the first key is SK, the second key is PK; and if the second key and the first key are symmetric keys with each other, the first Key and second secret The keys are the same.

Specifically, the eUICC generates the local first digest of the localuserintentfreeSigned, and decrypts the userintentfreeSignature with the second key to obtain a decrypted result. When the local first digest and the decrypted result are the same, the verification of the userintentfreeSignature is passed.

Optionally, when the LPA receives both the userintentfreeSignature and the Signer, the eUICC also needs to verify whether the DN name in the Signer and the CERT.EUM/Enterprise/OEM.ESCDA is the same, and the verification is passed. The verification order of Signer and userintentfreeSignature is not limited.

Step S214: The eUICC sends a verification completion instruction to the LPA.

The verification completion instruction includes a verification pass instruction or a verification non-pass instruction, which is used to indicate whether to perform a user verification step, and if the verification completion instruction is a verification pass instruction, the user intention confirmation step is not performed; if the verification complete instruction is a verification failure instruction Then, the user intent confirmation step is performed, or the LPA is instructed to terminate the current RSP session.

Specifically, the verification completion instruction may be, for example, an OK or Error response message.

Step S215: The LPA determines whether to perform the user intention confirmation step according to the verification completion instruction.

In a possible implementation manner, a flag bit may be set for whether to perform a user intent confirmation step, for example, when the verification pass instruction is received, the mark position is set to '1', indicating that the step should be skipped when running to the user intention confirmation step. When the verification fails the instruction, the flag is set to '0', indicating that this step should be performed when running to the user intent confirmation step.

Specifically, when the verification completion instruction is the verification pass instruction, step S217 is performed.

Step S216: The verification completion instruction is a verification failure instruction, and the LPA performs a user intention confirmation step.

Step S217: The LPA continues to perform the profile download and installation process.

In the method described in FIG. 3, the user intends to configure the information userintentConfiguration as userintentfreeSignature or {Signer, userintentfreeSignature}, and the operator obtains the userintentfreeSignature from Enterprise, OEM or EUM and carries the userintentfreeSignature in the ConfirmOrder and sends it to the SM-DP+, when the user terminal device wants When performing the profile download operation, SM-DP+ sends the userintentfreeSignature (and Signer) to the LPA of the terminal. LPA and eUICC cooperate to complete the verification of userintentfreeSignature (and Signer), and skip the user intent confirmation step when the verification is passed, which is helpful to achieve Efficient downloading of profiles is especially beneficial for scenarios of batch enterprise user terminal devices.

Referring to FIG. 6, FIG. 6 is a schematic flowchart of a method for downloading an eUICC configuration file according to a third embodiment of the present invention. In the embodiment of the present invention, the eUICC management session user is configured to perform an eUICC configuration file download and installation operation, and the specific implementation process is as follows:

Step S301: The LPA acquires the SM-DP+ address.

Step S302: The LPA establishes a TLS connection with the SM-DP+.

Step S303: The SM-DP+ and the eUICC perform mutual authentication based on the HTTPS.

Step S304: The SM-DP+ search obtains a Profile download pending order or a Batch Profile download pending order.

Step S305: The SM-DP+ performs the validity check by using Device Info and eucic Info2.

The implementation logic and implementation manner of steps S301-S305 are the same as steps S201-S205 of the second embodiment. The consistency of the introduction is not repeated here.

Step S306: SM-DP+ generates Profile Metadata, checks whether it is download retry, generates smdpSigned2, smdpSigned2={TransactionID, Confirmation Code Required Flag, bppEuiccOtpk, userintentConfiguration, EIDs}.

Among them, EIDs are optional. Specifically, in the embodiment of the present invention, the userintentConfiguration may be {Signer, userintentfreeSignature}, userintentfreeSignature, or User Intent Free Required Flag.

It should be noted that if the userintentConfiguration is the User Intent Free Required Flag, the Operator BSS does not perform the step of acquiring the user device to authorize the userintentfreeSignature, and directly downloads the scenario according to the profile (for example, the enterprise user batch download, or the elderly user/helper user) Download) Instructs SM-DP+ to generate user intent configuration information (eg, indicating that the user intent flag is set to 'True' or 'False').

It should be noted that, in the embodiment of the present invention, if the userintentConfiguration is {Signer, userintentfreeSignature} or userintentfreeSignature, smdpSigned2 is the second data to be signed, and if the userintentConfiguration is the User Intent Free Required Flag, the smdpSigned2 is the third data to be signed.

Step S307: SM-DP+ performs signature calculation on smdpSigned2|euiccSignature1 by using SK.DPpb.ECDSA to generate smdpSignature2, where SK.DPpb.ECDSA is the private key of the ProfileBinding certificate of SM-DP+.

It should be noted that, in the embodiment of the present invention, if the userintentConfiguration is {Signer, userintentfreeSignature} or userintentfreeSignature, smdpSignature2 is the second signature value, and if the userintentConfiguration is the User Intent Free Ruired Flag, the smdpSignature2 is the third signature value.

Step S308: SM-DP+ sends Profile Metadata, smdpSigned2, smdpSignature2, CERT.DPpb.ECDSA to the LPA.

Step S309: The LPA confirms receipt of the userintentConfiguration.

Specifically, the LPA parses smdpSigned2 to confirm receipt of the user intent configuration information userintentConfiguration.

In a possible implementation manner, if the user intends to configure the information to be {Signer, userintentfreeSignature} or userintentfreeSignature, the LPA may generate localuserintentfreeSigned, and the generated manner and content thereof are consistent with those described in step S209 in the second embodiment, and no longer Narration.

Step S310: Optionally, the LPA verifies that the EID of the local eUICC is within the EIDs.

Step S311: The LPA sends smdpSigned2, smdpSignature2, and CERT.DPpb.ECDSA to the eUICC.

Optionally, if the LPA generates localuserintentfreeSigned, the LPA also sends the generated localuserintentfreeSigned to the eUICC.

In another implementation, userintentfreeSigned may be generated by the eUICC. In this case, the LPA also needs to send the Operation Type, Operatorid, and EIDs (optional) to the eUICC.

Step S312: The eUICC verifies that CERT.DPpb.ECDSA is legal and belongs to the same SM-DP+ as CERT.DPauth.ECDSA, and verifies that the TransactionID matches the current RSP session.

The manner in which the eUICC verifies the CERT.DPpb.ECDSA is the same as that described in step S212 of the second embodiment, and details are not described herein.

Step S313: The eUICC verifies the smdpSignature2.

Specifically, the eUICC verifies the smdpSignature2 by using the fourth key (PK.DPpb.ECDSA), smdpSigned2, and eucicsignature1 corresponding to the SK.DPpb.ECDSA, wherein the eucicSignature1 is the authentication generated and saved by the eUICC during the establishment of the RSP session. Signature value.

Specifically, the eUICC generates a third digest of smdpSigned2|euiccSignature1, and then decrypts smdpSignature2 with PK.DPpb.ECDSA to generate a fourth digest. When the third digest is the same as the fourth digest, the verification of smdpSignature2 is passed. For example, in SM-DP+, A={smdpSigned2, eucicSignature1}, the summary is obtained for A, and smdpSignature2 is the signature value obtained by encrypting the summary a with SK.DPpb.ECDSA; when smdpSigned2 and smdpSignature2 are transmitted to In eUICC, the abstract is obtained by summarizing smdpSigned2|euiccSignature1 to obtain a digest a1, and smdpSignature2 is decrypted by PK.DPpb.ECDSA to generate a new digest b. When the digest a1 and the digest b are the same, the verification of smdpSignature2 is passed.

Step S314: The eUICC verifies the userintentConfiguration.

Specifically, when the userintentConfiguration is {Signer, userintentfreeSignature} or userintentfreeSignature, the steps of verifying the userintentfreeSignature and the signer may refer to step S213 of the second embodiment, and details are not described herein.

Specifically, when the userintentConfiguration is the User Intent Free Required Flag, the eUICC determines whether the User Intent Free Required Flag is valid for verification. For example, the value of the User Intent Free Required Flag is 'True' (or '1'), and the userintentConfiguration is determined to be valid. The verification is passed; the value of User Intent Free Required Flag is 'False' (or '0'), it is invalid, and the verification of userintentConfiguration is not passed. Alternatively, when the userintentConfiguration is the User Intent Free Required Flag, the eUICC does not verify it, but returns the verification result to the LPA after the smdpSignature2 is verified in step S313, and the User Intent Free Required Flag is verified by the LPA.

Step S315: The eUICC sends a verification completion instruction to the LPA.

Step S316: The LPA determines whether to perform the user intention confirmation step according to the verification completion instruction.

Step S317: The verification completion instruction is a verification failure instruction, and the LPA performs a user intention confirmation step.

Step S318: The LPA continues to perform the profile download and installation process.

The implementation logics and manners of the steps S315 to S318 are the same as those of the foregoing steps S214 to S217 in the second embodiment, and are not described again.

In the method described in FIG. 6, the user intends to configure the information userintentConfiguration to be {Signer, userintentfreeSignature}, userintentfreeSignature, or User Intent Free Required Flag, and the Operator BSS obtains the userintentfreeSignature from Enterprise, OEM, or EUM and carries the userintentfreeSignature (and Signer) in the ConfirmOrder. When sent to SM-DP+ (userintentConfiguration is User Intent Free Required Flag, Operator BSS does not perform the procedure of obtaining userintentfreeSignature). When the terminal device wants to perform profile download operation, SM-DP+ puts userintentConfiguration into smdpSigned2 for signature protection and sends it to the terminal device. LPA, LPA and eUICC cooperate to complete the verification of smdpSignature2 and userintentConfiguration. When the smdpSignature2 signature verification is passed and the userintentConfiguration is verified, the user intent confirmation step is skipped, which helps to achieve efficient download of the profile, especially for batch enterprises. The scenario of the user terminal device.

Referring to FIG. 7, FIG. 7 is a schematic flowchart diagram of a method for remotely managing an eUICC configuration file according to a fourth embodiment of the present invention. In the embodiment of the present invention, the eUICC management operation performed by the terminal device is an RPM operation, and the specific implementation process is as follows:

Step S401: The LPA acquires the SM-DP+ address.

Step S402: The LPA establishes a TLS connection with the SM-DP+.

Step S403: The SM-DP+ and the eUICC perform mutual authentication based on the HTTPS.

At this point, the RSP session between the terminal device and the SM-DP+ is successfully established, and the logic and process of the establishment are the same as those described in steps S201 to S203 of the second embodiment, and details are not described herein.

Step S404: The SM-DP+ search obtains a profile remote management pending event (pending RPM order) or a batch profile remote management pending event (pending batch RPM order).

Specifically, the pending RPM order or the pending Batch RPM order may be generated after the SM-DP+ receives the Remote Profile Management Order (RPMOrder) of the Operator BSS. The specific process is described below.

Step S11: The Operator BSS obtains the user-intention-free authorization userintentfreeSignature.

The manner in which the operator BSS obtains the userintentfreeSignature is the same as that described in the step S3 of the profile download initialization process of the SM-DP+ described in conjunction with FIG. 3. It should be noted that in the embodiment of the present invention, the eucic Operation Type is various profiles. Remote management operations (for example, deactivate Disable, activate Enable, delete Delete, update Update, query Query).

Step S12: The Operator sends an RPMorder to the SM-DP+, where the RPMorder carries the userintentfreeSignature, RPM Command.

Optionally, ICDRDs, Signer, and EIDs may also be carried in the RPMOrder.

Step S13: The SM-DP+ performs a legality check.

Specifically, SM-DP+ checks EIDs or ICCIDs to see if they belong to their management scope.

Step S14: SM-DP+ generates one or more pending RPM orders or generates a pending Batch RPM order.

Optionally, the SM-DP+ also performs event registration at the SM-DS.

Specifically, each RPM Oder event has an eventID identifier.

Specifically, SM-DP+ finds a pending RPM order or a pending Batch RPM order through eventID or EID.

Step S405: SM-DP+ generates second to-be-signed data (for example, smdpSigned3), smdpSigned3={TransactionID, RPM Command}.

Step S406: SM-DP+ performs a signature calculation on smdpSigned3|euiccSignature1 by using a third key (SK.DPrpm.ECDSA) to generate a second signature value (smdpSignature3), wherein SK.DPrpm.ECDSA is a remote profile management of SM-DP+ ( The private key of the Remote Profile Management (RPM) certificate (CERT.DPrpm.ECDSA).

Specifically, the RPM certificate can be distinguished or multiplexed from the authentication certificate.

Specifically, SM-DP+ can generate a summary of smdpSigned3|euiccSignature1 and then utilize SK.DPrpm.ECDSA encrypts the digest to generate smdpSignature3. For example, C={smdpSigned3, eucicsignature1}, the C is digested to obtain c, and the result of encrypting the digest c by SK.DPrpm.ECDSA is the second signature value smdpSignature3.

Step S407: SM-DP+ sends smdpSigned3, smdpSignature3, CERT.DPrpm.ECDSA, userintentConfiguration, EIDs and Operatorid to the LPA.

Among them, EIDs are optional; Operatorid can be included in RPM Command.

Step S408: The LPA confirms receipt of the userintentConfiguration, and generates localuserintentfreeSigned, localuserintentfreeSigned={euicc Operation Type, Operatorid, SM-DP+OID}.

Specifically, the LPA identifies the eucic Operation Type through the RPM Command, reads the Operatorid from the smdpSigned3 or the RPM Command, and obtains the SM-DP+OID from the CERT.DPrpm.ECDSA certificate.

Specifically, the eucic Operation Type includes, for example, a Disable, an Enable, a Delete, an Update, or a Query.

Step S409: The LPA verifies that the EID of the local eUICC is within the EIDs.

Step S410: The LPA sends localuserintentfreeSigned, userintentConfiguration, TransactionID, and CERT.DPrpm.ECDSA to the eUICC.

Specifically, the TransactionID is read from smdpSigned3.

In another implementation, localuserintentfreeSigned may be generated by eUICC, which sends eucic Operation Type, Operatorid, userintentConfiguration, TransactionID, and CERT.DPrpm.ECDSA to eUICC. Optionally, the LPA also sends EIDs to the eUICC.

Step S411: The eUICC verifies that CERT.DPrpm.ECDSA is legal and belongs to the same SM-DP+ as CERT.DPauth.ECDSA, and verifies that the TransactionID matches the current RSP session.

Specifically, the eUICC compares the two SM-DP+OIDs obtained by acquiring the SM-DP+OIDs from CERT.DPrpm.ECDSA and CERT.DPauth.ECDSA respectively, if the two SM-DP+OIDs are the same. Then it is determined that CERT.DPrpm.ECDSA belongs to the same SM-DP+ as CERT.DPauth.ECDSA.

Step S412: The eUICC verifies the userintentConfiguration.

Specifically, the method for verifying the userintentConfiguration by the eUICC is the same as that in the foregoing second embodiment, and details are not described herein again.

Step S413: The eUICC sends a verification completion instruction to the LPA.

Step S414: The LPA determines whether to perform the user intention confirmation step according to the verification completion instruction.

Step S415: The verification completion instruction is a verification failure instruction, and the LPA performs a user intention confirmation step.

Step S416: The LPA continues to execute the profile remote management process.

For the implementation logic and the specific manner of the steps S413 to S416, refer to steps S214 to S217 in the foregoing second embodiment, and details are not described herein.

In the method described in FIG. 7, userintentConfiguration is {Signer, userintentfreeSignature}, userintentfreeSignature, and Operator BSS is obtained from Enterprise, OEM, or EUM. UserintentfreeSignature (and Signer) and userintentConfiguration are carried in RPMOrder and sent to SM-DP+. When the terminal device wants to perform profile remote management operation, SM-DP+ sends userintentConfiguration to the LPA of the terminal, and LPA and eUICC cooperate to complete the verification of userintentConfiguration. The user intent confirmation step is not performed when the verification is passed, which facilitates efficient remote management of the profile.

Referring to FIG. 8, FIG. 8 is a schematic flowchart diagram of a method for remotely managing an eUICC configuration file according to a fifth embodiment of the present invention. In the embodiment of the present invention, the eUICC management operation performed by the terminal device is an RPM operation, and the specific implementation process is as follows:

Step S501: The LPA acquires the SM-DP+ address.

Step S502: The LPA establishes a TLS connection with the SM-DP+.

Step S503: SM-DP+ and eUICC perform mutual authentication based on HTTPS.

At this point, after the two-way authentication, the session between the terminal device and the SM-DP+ is successfully established, and the logic and the process of the establishment are the same as those described in steps S201 to S203 of the second embodiment, and details are not described herein.

Step S504: The SM-DP+ search finds a pending RPM order or a pending Batch RPM order.

The implementation logic and mode of the step S504 are the same as those of the step S404 in the fourth embodiment, and details are not described herein.

Step S505: SM-DP+ generates smdpSigned3, smdpSigned3={TransactionID, RPM Command, userintentConfiguration, EIDs, Operatorid}.

Among them, EIDs are optional; Operatorid can also be included in RPM Command.

It should be noted that, in the embodiment of the present invention, if the userintentConfiguration is {Signer, userintentfreeeSignature} or userintentfreeSignature, smdpSigned3 is the second data to be signed, and if the userintentfreeSignature is the User Intent Free Ruired Flag, smdpSigned3 is the third data to be signed.

Step S506: SM-DP+ performs signature calculation on smdpSigned3|euiccSignature1 by using SK.DPrpm.ECDSA to generate smdpSignature3.

The generation manner of smdpSignature3 is mentioned in step S406 of the fourth embodiment described above, and will not be described again.

It should be noted that, in the embodiment of the present invention, if the userintentConfiguration is {Signer, userintentfreeSignature} or userintentfreeSignature, the smdpSignature3 is the second signature value, and if the userintentConfiguration is the User Itent Free Ruired Flag, the smdpSignature3 is the third signature value.

Step S507: SM-DP+ sends smdpSigned3, smdpSignature3, CERT.DPrpm.ECDSA to the LPA.

Step S508: The LPA confirms receipt of the userintentConfiguration.

Specifically, the LPA parses the data in smdpSigned3 to confirm receipt of the userintentConfiguration.

In a possible implementation, if the userintentConfiguration is {Signer, userintentfreeSignature} or userintentfreeSignature, the LPA can generate localuserintentfreeSigned, and the manner and content of the LPA are consistent with those described in step S408 in the fourth embodiment, and details are not described herein.

Step S509: The LPA verifies that the EID of the local eUICC is within the EIDs.

Step S510: The LPA sends smdpSigned3, smdpSignature3, and CERT.DPrpm.ECDSA to the eUICC.

Optionally, if the LPA generates localuserintentfreeSigned, the LPA will send localuserintentfreeSigned Send it to eUICC.

In another implementation manner, localuserintentfreeSigned may be generated by the eUICC, and the LPA also needs to send the eucic Operation Type, the Operatorid, and the optional EIDs to the eUICC.

Step S511: The eUICC verifies that CERT.DPrpm.ECDSA is legal and belongs to the same SM-DP+ as CERT.DPauth.ECDSA, and verifies that the TransactionID matches the current RSP session.

Step S512: The eUICC verifies the smdpSignature3.

Specifically, the eUICC verifies the smdpSignature3 using the fourth key (PK.DPrpm.ECDSA), smdpSigned3, and eucicSignature1 corresponding to SK.DPrpm.ECDSA.

Specifically, the eUICC generates a fifth digest for smdpSigned3 and the locally saved eucicSignature1, and then decrypts smdpSignature3 with PK.DPrpm.ECDSA. When the fifth digest and the decrypted result are the same, the verification of smdpSignature3 is passed.

Step S513: The eUICC verifies the userintentConfiguration

Specifically, when the userintentConfiguration is {Signer, userintentfreeSignature} or userintentfreeSignature, the step of verifying the userintentConfiguration may refer to step S213 of the second embodiment, and details are not described herein.

Specifically, when the userintentConfiguration is the User Intent Free Required Flag, the verification of the userintentConfiguration may refer to step S314 of the third embodiment, and details are not described herein.

Step S514: The eUICC sends a verification completion instruction to the LPA.

Step S515: The LPA determines whether to perform the user intention confirmation step according to the verification completion instruction.

Step S516: The verification completion instruction is a verification failure instruction, and the LPA performs a user intention confirmation step.

Step S517: The LPA continues to execute the profile remote management process.

For the implementation of the logic and the specific manners of the steps S514 to S517, reference may be made to the steps S214 to S217 in the foregoing second embodiment, and details are not described herein.

In the method described in FIG. 8, userintentConfiguration is {Signer, userintentfreeSignature}, userintentfreeSignature, or User Intent Free Required Flag, and Operator BSS obtains userintentfreeSignature (and Signer) from Enterprise, OEM, or EUM, and userintentfreeSignature (and Signer) in RPMorder. Sended to SM-DP+, when the terminal wants to perform profile remote management operation, SM-DP+ puts userintentConfiguration into smdpSigned3 for signature protection and sends it to the LPA of the terminal. LPA and eUICC cooperate to complete verification of smdpSigned3 and userintentConfiguration. The user intent confirmation step is not performed, which facilitates efficient remote management of the profile.

The above describes the method of the embodiment of the present invention in detail, and the apparatus of the embodiment of the present invention is provided below.

Referring to FIG. 9, FIG. 9 is a schematic structural diagram of an eUICC configuration file management apparatus according to an embodiment of the present invention. The eUICC configuration file management apparatus may include a management session establishment module 610, a configuration information acquisition module 620, a verification module 630, and an implementation. Module 640, wherein the detailed description of each module is as follows:

a management session establishing module 610, configured to establish an eUICC management session with the eUICC remote management server;

The configuration information obtaining module 620 is configured to remotely manage the service from the eUICC through the eUICC management session. Obtaining user intent configuration information;

The verification module 630 is configured to verify the user intent configuration information.

The execution module 640 is configured to: during the current eUICC management session, perform a user intent confirmation step, where the eUICC management session is used to execute the eUICC configuration file, if the verification of the user intent configuration information is passed. At least one of a download and install operation, an eUICC profile activation operation, an eUICC profile deactivation operation, or an eUICC profile deletion operation.

It should be noted that the implementation of each module may also correspond to the corresponding description of the method embodiment shown in FIG. 1 , FIG. 3 , FIG. 6 , FIG. 7 or FIG. 8 .

Referring to FIG. 10, FIG. 10 is an eUICC configuration file management apparatus 70 according to an embodiment of the present invention. The eUICC configuration file management apparatus 70 includes a processor 701, a memory 702, and a transceiver 703. The processor 701 and the memory 702 are provided. And the transceiver 403 are connected to each other through a bus.

The memory 702 includes, but is not limited to, a random access memory (English: Random Access Memory, RAM for short), a read-only memory (English: Read-Only Memory, abbreviated as: ROM), and an erasable programmable read-only memory (English: Erasable Programmable Read Only Memory (EPROM) or Portable Read-Only Memory (CD-ROM) is used to store related commands and data. The transceiver 703 is configured to receive and transmit data.

The processor 701 may be one or more central processing units (English: Central Processing Unit, CPU for short). In the case that the processor 701 is a CPU, the CPU may be a single core CPU or a multi-core CPU.

The processor 701 in the eUICC profile management device 70 is configured to read the program code stored in the memory 702, and perform the following operations:

Establish an eUICC management session with the eUICC remote management server;

Verifying the user intent configuration information;

It should be noted that the implementation of each operation may also correspond to the corresponding description of the method embodiment shown in FIG. 1 , FIG. 1 , FIG. 3 , FIG. 6 , FIG. 7 or FIG. 8 .

Referring to FIG. 11, FIG. 11 is a schematic structural diagram of a local eUICC configuration file auxiliary module according to an embodiment of the present invention. The local eUICC configuration file auxiliary module includes a management session establishing unit 810, a configuration information acquiring unit 820, and a verification instruction sending unit. 830 and a first execution unit 840, wherein the detailed description of each unit is as follows:

a management session establishing unit 810, configured to establish an eUICC management session with the eUICC remote management server;

The configuration information obtaining unit 820 is configured to acquire user intent configuration information from the eUICC remote management server by using the eUICC management session;

a verification instruction sending unit 830, configured to send a user intention verification instruction to the eUICC module, where the user intention The verification instruction is used by the eUICC module to verify the user intent configuration information, where the user intent verification instruction carries the user intent configuration information;

The first execution unit 840 is configured to: during the current eUICC management session, perform a user intent confirmation step, where the eUICC management session is used to execute the eUICC, if the verification of the user intent configuration information is passed. At least one of a configuration file download and install operation, an eUICC configuration file activation operation, an eUICC configuration file deactivation operation, or an eUICC configuration file deletion operation.

It should be noted that the implementation of each unit may also correspond to the corresponding description of the LPA in the method embodiment shown in FIG. 1 , FIG. 3 , FIG. 6 , FIG. 7 or FIG. 8 .

Referring to FIG. 12, FIG. 12 is a terminal 90 according to an embodiment of the present invention. The terminal 90 includes a processor 901, a memory 902, and a transceiver 903. The processor 901, the memory 902, and the transceiver 903 are connected to each other through a bus. .

The memory 902 includes, but is not limited to, a random access memory (English: Random Access Memory, RAM for short), a read-only memory (English: Read-Only Memory, ROM for short), and an erasable programmable read-only memory (English: Erasable Programmable Read Only Memory (EPROM) or Portable Read-Only Memory (CD-ROM) is used to store related commands and data. The transceiver 903 is configured to receive and transmit data.

The processor 901 may be one or more central processing units (English: Central Processing Unit, CPU for short). In the case that the processor 901 is a CPU, the CPU may be a single core CPU or a multi-core CPU.

The processor 901 in the terminal 90 is configured to read the program code stored in the memory 902, and perform the following operations:

Establish an eUICC management session with the eUICC remote management server;

Referring to FIG. 13, FIG. 13 is a schematic structural diagram of an eUICC module according to an embodiment of the present invention. The eUICC module includes a verification instruction receiving unit 1010, a verification unit 1020, and a second execution unit 1030, wherein a detailed description of each unit is provided. as follows:

The verification instruction receiving unit 1010 is configured to receive a user intent verification instruction sent by the local eUICC configuration file auxiliary module, where the user intent verification instruction carries user intent configuration information, where the user intent configuration information is the local eUICC configuration file. The auxiliary module is obtained from an eUICC management session with the eUICC remote management server;

a verification unit 1020, configured to verify the user intent configuration information;

The second execution unit 1030 is configured to: during the current eUICC management session, perform a user intent confirmation step, where the eUICC management session is used to execute the eUICC, if the verification of the user intent configuration information is passed. At least one of a configuration file download and install operation, an eUICC configuration file activation operation, an eUICC configuration file deactivation operation, or an eUICC configuration file deletion operation.

It should be noted that the implementation of each unit may also correspond to the corresponding description of the eUICC in the method embodiment shown in FIG. 1 , FIG. 3 , FIG. 6 , FIG. 7 or FIG. 8 .

Referring to FIG. 14, FIG. 14 is an eUICC module 110 according to an embodiment of the present invention. The eUICC module 110 includes a processor 1101, a memory 1102, and a communication interface 1103. The processor 1101, the memory 1102, and the communication interface 1103 pass through a bus. Connected to each other.

The memory 1102 includes, but is not limited to, a random access memory (English: Random Access Memory, RAM for short), a read-only memory (English: Read-Only Memory, ROM for short), and an erasable programmable read-only memory (English: Erasable Programmable Read Only Memory (EPROM) or Portable Read-Only Memory (CD-ROM) is used to store related commands and data. The communication interface 1103 is for receiving and transmitting data.

The processor 1101 may be one or more central processing units (English: Central Processing Unit, CPU for short). In the case where the processor 1101 is a CPU, the CPU may be a single core CPU or a multi-core CPU.

The processor 1101 in the eUICC module 110 is configured to read the program code stored in the memory 1102, and perform the following operations:

Verifying the user intent configuration information;

In summary, by implementing the embodiments of the present invention, efficient downloading and installation of profiles and efficient remote profile management can be realized.

One of ordinary skill in the art can understand all or part of the process of implementing the above embodiments, which can be completed by a computer program to instruct related hardware, the program can be stored in a computer readable storage medium, when the program is executed The flow of the method embodiments as described above may be included. The foregoing storage medium includes various media that can store program codes, such as a ROM or a random access memory RAM, a magnetic disk, or an optical disk.

Claims

An eUICC configuration file management method, comprising:

Establish an eUICC management session with the eUICC remote management server;

Obtaining user intent configuration information from the eUICC remote management server through the eUICC management session;

Verifying the user intent configuration information;

In the case that the verification of the user intent configuration information is passed, the user intent confirmation step is not performed during the current eUICC management session, wherein the eUICC management session is used to execute the eUICC configuration file download and installation operation, eUICC At least one of a profile activation operation, an eUICC profile deactivation operation, or an eUICC profile deletion operation.
The method of claim 1 wherein said user intent configuration information comprises a user intent indication; or

The user intent configuration information includes a first signature value; or

The user intent configuration information includes the first signature value and an owner name of a digital certificate corresponding to the first signature value.
The method of claim 1, wherein the user intent configuration information comprises a first signature value, wherein the first signature value comprises a signature of the first to-be-signed data using the first key, The first key includes a public key, a private key, or a symmetric key;

The verifying the user intent configuration information includes:

Generating a local first to-be-signed data, where the local first to-be-signed data includes an operation type, an operator identifier, and an eUICC remote management server object identifier;

The first signature value is verified by a second key corresponding to the first key and the local first to-be-signed data.
The method of claim 3, wherein the obtaining the user intent configuration information from the eUICC remote management server by using the eUICC management session comprises:

Acquiring the second to-be-signed data and the second signature value from the eUICC remote management server by using the eUICC management session, where the second to-be-signed data includes the user intent configuration information, and the second signature value includes a signature of the second key to the second signature data and the authentication signature value, the authentication signature value being generated during the establishment of the eUICC management session;

The method further includes: before verifying the first signature value by using the second key corresponding to the first key and the local first to-be-signed data:

The second signature value is verified by the fourth key corresponding to the third key, the second signature to be signed data, and the authentication signature value, and the verification is confirmed to pass.
The method of claim 1 wherein said user intent configuration information comprises a user icon The obtaining the user intent configuration information from the eUICC remote management server by using the eUICC management session includes:

Acquiring the third to-be-signed data and the third signature value from the eUICC remote management server by using the eUICC management session, where the third to-be-signed data includes the user intent configuration information, and the third signature value includes a signature of the third key to the third signature data and the authentication signature value, where the authentication signature value is generated during the establishment of the eUICC management session;

The verifying the user intent configuration information includes:

And verifying the third signature value by using a fourth key corresponding to the third key, the third to-be-signed data, and the authentication signature value, and confirming that the verification is passed;

Verify that the user intent flag is valid.
An eUICC configuration file management method, comprising:

Establish an eUICC management session with the eUICC remote management server;

Obtaining user intent configuration information from the eUICC remote management server through the eUICC management session;

Sending a user intent verification instruction to the eUICC module, where the user intent verification instruction is used by the eUICC module to verify the user intent configuration information, wherein the user intent verification instruction carries the user intent configuration information;

In the case that the verification of the user intent configuration information is passed, the user intent confirmation step is not performed during the current eUICC management session, wherein the eUICC management session is used to execute the eUICC configuration file download and installation operation, eUICC At least one of a profile activation operation, an eUICC profile deactivation operation, or an eUICC profile deletion operation.
The method of claim 6 wherein said user intent configuration information comprises a user intent indication; or

The user intent configuration information includes a first signature value; or

The user intent configuration information includes the first signature value and an owner name of a digital certificate corresponding to the first signature value.
The method of claim 6, wherein the user intent configuration information comprises a first signature value, wherein the first signature value comprises a signature of the first to-be-signed data using the first key, The first key includes a public key, a private key, or a symmetric key;

Before the sending the user intent verification instruction to the eUICC module, the method includes:

Generating a local first to-be-signed data, where the local first to-be-signed data includes an operation type, an operator identifier, and an eUICC remote management server object identifier;

The user intent verification command further carries the local first to-be-signed data, and the local first to-be-signed data is used by the eUICC module to use a second key pair corresponding to the first key. A signature value is verified.
The method of claim 8 wherein said managing said session through said eUICC The eUICC remote management server obtains user intent configuration information including:

Acquiring the second to-be-signed data and the second signature value from the eUICC remote management server by using the eUICC management session, where the second to-be-signed data includes the user intent configuration information, and the second signature value includes Signing of the second to-be-signed data and the authentication signature value by the third key, the authentication signature value being generated during the eUICC management session;

The second verification data and the second signature value are further carried in the user verification instruction, where the second to-be-signed data and the authentication signature value are used by the eUICC module and the first The fourth key corresponding to the three keys verifies the second signature value.
The method of claim 6 wherein said user intent configuration information comprises a user intent indication;

The obtaining the user intent configuration information from the eUICC remote management server by using the eUICC management session includes:

Acquiring the third to-be-signed data and the third signature value from the eUICC remote management server by using the eUICC management session, where the third to-be-signed data includes the user intent configuration information, and the third signature value includes Signing the third to-be-signed data and the authentication signature value by the third key, the authentication signature value being generated during the eUICC management session;

The third verification data and the third signature value are further carried in the user verification instruction, where the third to-be-signed data and the authentication signature value are used by the eUICC module and the first The fourth key corresponding to the three keys verifies the third signature value;

The user intent indication is used by the eUICC for verification to be valid.
An eUICC remote configuration file management method, comprising:

Receiving a user intent verification instruction sent by the local eUICC configuration file auxiliary module, where the user intent verification instruction carries user intent configuration information, where the local intent configuration information is the local eUICC configuration file auxiliary module from the eUICC remote management server The eUICC management session is obtained;

Verifying the user intent configuration information;

In the case that the verification of the user intent configuration information is passed, the user intent confirmation step is not performed during the current eUICC management session, wherein the eUICC management session is used to execute the eUICC configuration file download and installation operation, eUICC At least one of a profile activation operation, an eUICC profile deactivation operation, or an eUICC profile deletion operation.
The method of claim 11 wherein said user intent configuration information comprises a user intent indication; or

The user intent configuration information includes a first signature value; or

The user intent configuration information includes the first signature value and an owner name of a digital certificate corresponding to the first signature value.
The method of claim 11, wherein the user intent configuration information comprises a first signature value, wherein the first signature value comprises a signature of the first to-be-signed data using the first key, The first key includes a public key, a private key, or a symmetric key;

The user intent verification command further includes a local first to-be-signed data, where the local first to-be-signed data is generated by the local eUICC configuration file auxiliary module, where the local first to-be-signed data includes an operation type and an operation. Vendor ID and eUICC remote management server object identifier;

The verifying the user intent configuration information includes:

The first signature value is verified by a second key corresponding to the first key and the local first to-be-signed data.
The method of claim 13, wherein the user verification instruction further carries a second to-be-signed data and a second signature value, wherein the second to-be-signed data includes the user intent configuration information, The second signature value includes a signature of the second to-be-signed data and an authentication signature value by using a third key;

The method further includes: before verifying the first signature value by using the second key corresponding to the first key and the local first to-be-signed data:

The second signature value is verified by the fourth key corresponding to the third key, the second signature to be signed data, and the authentication signature value, and the verification is confirmed to pass.
The method of claim 11, wherein the user intent configuration information comprises a user intent indication; the user verification instruction further carries a third to-be-signed data and a third signature value, wherein the third to-be-checked The signature data includes the user intent configuration information, and the third signature value includes a signature of the third to-be-signed data and an authentication signature value by using a third key, the authentication signature value being in the eUICC management session Produced during the process;

The verifying the information about the user intent configuration information includes:

And verifying the third signature value by using a fourth key corresponding to the third key, the third to-be-signed data, and the authentication signature value, and confirming that the verification is passed;

Verify that the user intent flag is valid.
An eUICC configuration file management apparatus, comprising:

a management session establishing module, configured to establish an eUICC management session with the eUICC remote management server;

a configuration information obtaining module, configured to acquire user intent configuration information from the eUICC remote management server by using the eUICC management session;

a verification module, configured to verify the user intent configuration information;

An execution module, configured to perform a user intent confirmation step during the current eUICC management session, where the eUICC management session is used to perform eUICC configuration file downloading, if the verification of the user intent configuration information is passed And at least one of an installation operation, an eUICC profile activation operation, an eUICC profile deactivation operation, or an eUICC profile deletion operation.
A local eUICC configuration file auxiliary module, comprising:

a management session establishing unit, configured to establish an eUICC management session with the eUICC remote management server;

a configuration information acquiring unit, configured to acquire user intent configuration information from the eUICC remote management server by using the eUICC management session;

a verification instruction sending unit, configured to send a user intention verification instruction to the eUICC module, where the user intention verification instruction is used by the eUICC module to verify the user intent configuration information, where the user intention verification instruction carries User intent configuration information;

a first execution unit, configured to perform a user intent confirmation step during the current eUICC management session, where the eUICC management session is used to perform eUICC configuration, in the case that the verification of the user intent configuration information is passed At least one of a file download and install operation, an eUICC profile activation operation, an eUICC profile deactivation operation, or an eUICC profile delete operation.
An eUICC module, comprising:

a verification instruction receiving unit, configured to receive a user intent verification instruction sent by the local eUICC configuration file auxiliary module, where the user intent verification instruction carries user intent configuration information, where the user intent configuration information is the local eUICC configuration file auxiliary The module is obtained from an eUICC management session with the eUICC remote management server;

a verification unit, configured to verify the user intent configuration information;

a second execution unit, configured to perform a user intent confirmation step during the current eUICC management session, where the eUICC management session is used to perform eUICC configuration, in the case that the verification of the user intent configuration information is passed At least one of a file download and install operation, an eUICC profile activation operation, an eUICC profile deactivation operation, or an eUICC profile delete operation.
An eUICC configuration file management apparatus, comprising: a processor, a memory, and a transceiver, wherein the processor, the memory, and the transceiver are connected to each other by a bus, wherein the memory is configured to store program code, and the processing The program is used to call the program code, and performs the following operations:

Establish an eUICC management session with the eUICC remote management server;

Obtaining user intent configuration information from the eUICC remote management server through the eUICC management session;

Verifying the user intent configuration information;

In the case that the verification of the user intent configuration information is passed, the user intent confirmation step is not performed during the current eUICC management session, wherein the eUICC management session is used to execute the eUICC configuration file download and installation operation, eUICC At least one of a profile activation operation, an eUICC profile deactivation operation, or an eUICC profile deletion operation.
A terminal, comprising: a processor, a memory and a transceiver, wherein the processor, the memory and the transceiver are connected to each other by a bus, wherein the memory is used to store program code, and the processor is used to call the The program code, do the following:

Establish an eUICC management session with the eUICC remote management server;

Obtaining user intent configuration information from the eUICC remote management server through the eUICC management session;

Sending a user intent verification instruction to the eUICC module, the user intent verification instruction being used by the eUICC module And verifying the user intent configuration information, where the user intent verification instruction carries the user intent configuration information;

In the case that the verification of the user intent configuration information is passed, the user intent confirmation step is not performed during the current eUICC management session, wherein the eUICC management session is used to execute the eUICC configuration file download and installation operation, eUICC At least one of a profile activation operation, an eUICC profile deactivation operation, or an eUICC profile deletion operation.
An eUICC module, comprising: a processor, a memory, and a communication interface, wherein the processor, the memory, and the communication interface are connected to each other by a bus, wherein the memory is used to store program code, and the processor is used to call The program code performs the following operations:

Receiving a user intent verification instruction sent by the local eUICC configuration file auxiliary module, where the user intent verification instruction carries user intent configuration information, where the local intent configuration information is the local eUICC configuration file auxiliary module from the eUICC remote management server The eUICC management session is obtained;

Verifying the user intent configuration information;

In the case that the verification of the user intent configuration information is passed, the user intent confirmation step is not performed during the current eUICC management session, wherein the eUICC management session is used to execute the eUICC configuration file download and installation operation, eUICC At least one of a profile activation operation, an eUICC profile deactivation operation, or an eUICC profile deletion operation.