CN111372237B

CN111372237B - eSIM card operator file management method and device

Info

Publication number: CN111372237B
Application number: CN202010187353.2A
Authority: CN
Inventors: 崔可; 何碧波; 底明辉
Original assignee: Hengbao Co Ltd
Current assignee: Hengbao Co Ltd
Priority date: 2020-03-17
Filing date: 2020-03-17
Publication date: 2023-05-23
Anticipated expiration: 2040-03-17
Also published as: CN111372237A

Abstract

The application discloses an eSIM card operator file management method, wherein the eSIM card comprises a safety element, a plurality of operator files are stored on the safety element, and a management element, wherein the management element is used for managing the operator files on the eSIM card, and the method comprises the following steps: responding to an operator switching request, and switching the current operator file into a target operator file by the management element; the management element stores rule files according to which some or all of the currently active applications are managed by the destination operator file. By providing the rule file, when the operators switch, the part of the currently running compliance application can continue to run, so that the convenience of using the application in the eSIM card is provided for the users.

Description

eSIM card operator file management method and device

Technical Field

The present invention relates to the field of computers, and in particular, to a method and apparatus for managing files of an eSIM card carrier.

Background

With the development of wearable technology, the use of SIM cards has become a bottleneck limiting their development. The card slot is required to be reserved for the SIM card in the wearable equipment, and meanwhile, a user needs to go to a business hall to purchase the SIM card independently, so that the use of the SIM card brings a lot of inconvenience for manufacturers and users of the wearable equipment.

eSIM (Embedded Subscriber Identification Module, embedded subscriber identity module) technology has become a hotspot for industry development, and communication devices implemented using eSIM technology have been developed in a long-standing manner. eSIM cards are intended to embed a conventional SIM card directly onto a device chip, rather than being added to the device as a separate removable component.

The existing eSIM card stores data of a plurality of mobile operators, and when a user uses the eSIM card, an identity recognition module of the eSIM card allows the user to select the operators according to own needs and allows the user to switch at random at any time. Therefore, the user can select the mobile operator more flexibly, more terminal use cost is saved for the user, and convenience and safety are brought.

At present, how to manage multiple mobile operators on an eSIM card is a focus of attention, and for safety, downloaded multiple operators are isolated from each other, and an existing eSIM card management mode is to manage own application by each operator file, and when a mobile operator is switched, the application on the eSIM card which can be called by a user is changed to an application managed by the switched mobile operator, namely, the content such as address book and the like included in the first operator cannot be used by the second operator, which causes inconvenience in use of the user, and obviously does not meet the demands of people on the application.

Disclosure of Invention

The application requests to protect the file management method and the file management device for the eSIM card operator, which can uniformly manage the application and the data on the eSIM card, thereby providing better mobile service for users.

The application provides an eSIM card operator file management method, wherein the eSIM card comprises a safety element, a plurality of operator files are stored on the safety element, and a management element, and the management element is used for managing the operator files on the eSIM card, and the method comprises the following steps: responding to an operator switching request, and switching the current operator file into a target operator file by the management element; the management element stores rule files according to which some or all of the currently active applications are managed by the destination operator file.

Preferably, the management element receives notification information issued by the operator periodically, and the management element modifies the rule file according to the notification information.

Preferably, the rule file stores therein the application information.

Preferably, the method comprises the following substeps, wherein some or all of the currently activated applications are managed by the destination operator file according to the rule file, wherein the substeps comprise: acquiring a currently running application list and an activated operator identifier; inquiring a rule file according to the application list to obtain identification information of the currently running application; and judging whether the currently activated application is allowed to run or not according to the application identification information.

Preferably, after switching the current operator file to an operator file related to the invoked application, the method further comprises the steps of: connecting to an operator server corresponding to the operator service through a management file stored in the management element; sending a service message to an operator server; and the operator server provides cloud services matched with the eSIM card according to the use condition of the application included in the service message.

The application also provides an eSIM card comprising the following components: a secure element storing a plurality of operator files and applications; the management element receives notification information issued by the operator server and binds the application and the operator file according to the notification information; responding to an application starting request, and acquiring application use information; .

Preferably, the rule file stores therein the application information.

Preferably, the management element manages some or all of the currently activated applications by the destination operator file according to the rule file, comprising the sub-steps of: activating an operator profile; inquiring a rule file to obtain application identification information; and judging whether the currently activated application is allowed to run or not according to the application identification information.

The application also provides an eSIM card operator file management device, which comprises the eSIM card and an operator server for providing cloud service.

By providing the rule file, when the operators switch, the part of the currently-running compliant application can continue to run, so that the convenience in use of the application in the eSIM card is provided for the users.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following description will briefly introduce the drawings that are required to be used in the embodiments or the description of the prior art, and it is obvious that the drawings in the following description are only some embodiments described in the present application, and other drawings may also be obtained according to these drawings for a person having ordinary skill in the art.

Fig. 1 is a device block diagram of an eSIM card carrier file management device of the present application;

fig. 2 is a device block diagram of an eSIM card of the present application;

fig. 3 is a method flow diagram of an operator file management method.

Detailed Description

The following description of the embodiments of the present application, taken in conjunction with the accompanying drawings, clearly and completely describes the technical solutions of the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments herein without making any inventive effort, are intended to be within the scope of the present application.

Example 1

The application proposes an eSIM card operator file management device 100, comprising the following components: eSIM card 110, carrier server 120.

eSIM card 110 includes components as shown in fig. 2:

a secure element 210 storing a plurality of operator files and applications;

the management element 220 receives notification information issued by the operator server and binds the application and the operator file according to the notification information; responding to an application starting request, and acquiring application use information; responding to an operator switching request, and switching the current operator file into a target operator file; and according to the rule file, managing some or all of the currently activated applications by the destination operator file.

The operator server 120 obtains cloud services matching the identifier of the eSIM card according to the usage status of the application included in the service message sent by the eSIM card.

Referring to fig. 2, there is a block diagram of the architecture of an eSIM card of the present application, in which a management element 220 is coupled to a security element 210, and a plurality of operator profiles are stored on the security element 210, each of the operator profiles including a corresponding security domain, file system, key, and application. After a certain profile is activated, the corresponding operator security domain (MNO-SD) is managed as a main security domain on the card, and the corresponding file system, key and application under the card can be used.

Further, the present application provides a method for managing files of an eSIM card carrier, as shown in fig. 3, including the following steps:

step S310, responding to an operator switching request, and switching the current operator file into a target operator file by the management element;

for example, the current operator is operator profile1, and the handover request is, for example, to switch to profile2, then operator profile2 is activated, and operator profile1 is deactivated.

Step S320, the management element stores a rule file, and manages some or all currently activated applications by the destination operator file according to the rule file, wherein the method comprises the following sub-steps:

step S3201, obtaining a currently running application list and an activated operator identifier;

to obtain a list of currently operating applications, the eSIM card obtains the AID of the application, which is a string that is used to uniquely identify the application. The AID of the currently operating application forms an application list. Further obtaining an identification of the active operator. Such as the currently active operator profile2.

Step S3202, inquiring a rule file according to the application list to obtain identification information of the currently running application;

the management element periodically receives notification information issued by an operator, wherein the notification information comprises service information provided by an operator server aiming at an application. Such as information such as the mobile operator's department providing projection support for a certain video application.

The management element modifies a rule file according to the notification information, the rule file storing the application information therein. And the management element obtains the service information provided by the application of each operator server according to the issued notification information, selects the optimal service, and binds the application with the operator server providing the corresponding optimal service. And records the binding relationship in the rule information. The operator providing the optimal service is taken as the affiliated operator, and further, other operators which can provide the server are recorded in the application information.

For example, the rule files stored in the eSIM card are shown in table 1:

application AID	Application information	Belonging to the operator
			0x1001	Run in Profile2	profile1
0x1002	Run in Profile1	profile2
			0x1003	Run on profile1 and profile2	Profile3
0x1004	None	profile1

Table 1: rule file

As can be seen from table 1, the application with the application AID of 0x1001 belongs to the operator profile1, and when the operator profile1 is activated, the application 0x1001 may be invoked, and the operator profile2 is stored in the application information, which indicates that when the application 0x1001 is operated, once the action of switching to the operator profile2 occurs, the operation of the application 0x1001 may be continued.

Step S3203, judging whether the currently activated application is allowed to run or not according to the application identification information.

And judging whether the currently activated application is allowed to run or not according to the application information in the rule file. Taking table 1 as an example, when a switch from the operator profile1 to the operator profile2 occurs, the application information indicates that the running application 0x1001 continues to run under the operator profile2.

Where the application can be stored on the eSIM card security element or in a common area of the eSIM card.

Example two

The above describes the application that will be currently running based on the rule file. The second embodiment of the present application is described below.

After the step of storing the rule file by the management element according to the rule file and managing some or all of the currently activated applications by the destination operator file, the management element further includes the following steps:

an application that can be managed by the destination operator is set to an accessible state.

By setting the state of the application, the destination operator can manage the application.

Further, this step may be to migrate the application to the destination operator in the case where the application can be managed by the destination operator but the operator to which the application belongs is not the destination operator.

Example III

On the basis of the second embodiment, the application further comprises one or more cloud servers, wherein the one or more cloud servers are connected with the operator server 120, and cloud services matched with the eSIM cards are provided for the eSIM cards.

The carrier server can query the service list according to the identification of the eSIM card, and cloud services matched with the eSIM card can be provided for the eSIM card by the carrier server.

The operator server may also obtain, from a cloud service provider that provides the cloud service, a cloud service server address that matches the usage status of the application and has the highest priority, according to the usage status of the application included in the service message;

the eSIM card is connected to an operator server corresponding to the operator service through a management file stored in the management element; sending a service message to an operator server; and the operator server sends an instruction to a cloud server service address according to the use condition of the application included in the service message, so that a server corresponding to the cloud server address provides cloud service matched with the eSIM card.

Corresponding to the method in fig. 3, the embodiment of the present application further provides a computer readable storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of the above-described method of safety control.

In particular, the storage medium can be a general-purpose storage medium, such as a mobile disk, a hard disk, or the like, and the computer program on the storage medium, when executed, can perform the method for online issuing of eSIM certificates.

In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other manners. The above-described apparatus embodiments are merely illustrative, for example, the division of the units is merely a logical function division, and there may be other manners of division in actual implementation, and for example, multiple units or components may be combined or integrated into another system, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be through some communication interface, device or unit indirect coupling or communication connection, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in the embodiments provided in the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

It should be noted that: like reference numerals and letters in the following figures denote like items, and thus once an item is defined in one figure, no further definition or explanation of it is required in the following figures, and furthermore, the terms "first," "second," "third," etc. are used merely to distinguish one description from another and are not to be construed as indicating or implying relative importance.

Finally, it should be noted that: the foregoing examples are merely specific embodiments of the present application, and are not intended to limit the scope of the present application, but the present application is not limited thereto, and those skilled in the art will appreciate that while the foregoing examples are described in detail, the present application is not limited thereto. Any person skilled in the art may modify or easily conceive of the technical solution described in the foregoing embodiments, or make equivalent substitutions for some of the technical features within the technical scope of the disclosure of the present application; such modifications, changes or substitutions do not depart from the spirit and scope of the corresponding technical solutions. Are intended to be encompassed within the scope of this application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method of managing carrier files of an eSIM card, wherein the eSIM card includes a secure element having a plurality of carrier files stored thereon, and a management element for managing the carrier files on the eSIM card, the method comprising the steps of:

responding to an operator switching request, and switching the current operator file into a target operator file by the management element;

the management element stores a rule file, and manages some or all currently activated applications by the destination operator file according to the rule file; the management element receives notification information issued by an operator at regular intervals, and modifies the rule file according to the notification information; the rule file includes at least: application AID, application information and affiliated operators;

wherein, according to the rule file, some or all of the currently activated applications are managed by the destination operator file, comprising the following sub-steps:

acquiring a currently running application list and an activated operator identifier;

inquiring a rule file according to the application list to obtain identification information of the currently running application;

judging whether the currently activated application is allowed to run or not according to the application identification information;

the method comprises the following steps of managing some or all currently activated applications by a target operator file according to a rule file, wherein the method further comprises the following steps:

setting an application that can be managed by a destination operator to an accessible state;

by setting the state of the application, the destination operator can manage the application;

wherein in case of an application that can be managed by the destination operator but that the belonging operator is not the destination operator, the application is migrated under the destination operator.

2. The eSIM card carrier file management method of claim 1, further comprising the steps of, after switching the current carrier file to a carrier file associated with the invoked application:

connecting to an operator server corresponding to the operator service through a management file stored in the management element;

sending a service message to an operator server;

and the operator server provides cloud services matched with the eSIM card according to the use condition of the application included in the service message.

3. An eSIM card comprising the following components:

a secure element storing a plurality of operator files and applications;

the management element receives notification information issued by the operator server and binds the application and the operator file according to the notification information; responding to an application starting request, and acquiring application use information;

the management element receives notification information issued by an operator at regular intervals, and modifies the rule file according to the notification information; the rule file includes at least: application AID, application information and affiliated operators;

the management element manages some or all of the currently activated applications by the destination operator file according to the rule file, comprising the following sub-steps:

4. An eSIM card carrier file management apparatus comprising the eSIM card of claim 3, and an carrier server providing cloud services.