CN111372237A

CN111372237A - eSIM card operator file management method and device

Info

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

Abstract

The application discloses an eSIM card operator file management method, wherein the eSIM card comprises a secure element and a management element, the secure element stores a plurality of operator files, and the management element is used for managing the operator files on the eSIM card, and the method comprises the following steps: responding to the 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 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 operator switches, part of the compliance application currently running can continue to run, so that the convenience in use of the application in the eSIM card is provided for the user.

Description

eSIM card operator file management method and device

Technical Field

The present application relates to the field of computers, and in particular, to a method and an apparatus for managing an eSIM card operator file.

Background

With the development of wearable technology, the use of SIM cards has become a bottleneck limiting its development. The wearable equipment needs to reserve a card slot for the SIM card, and meanwhile, a user needs to go to a business hall to buy the SIM card independently, so that the use of the SIM card brings inconvenience for manufacturers and users of the wearable equipment.

An eSIM (Embedded Subscriber identity Module) technology has become a hot spot of industry development, and communication equipment implemented by using the eSIM technology has been developed greatly. eSIM cards are devices that embed a traditional 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 therein, and when a user uses the eSIM card, an identity module of the eSIM card allows the user to select an operator according to own needs and allows the user to switch at will 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 data of multiple mobile operators on an eSIM card is a focus of attention, for the sake of security, downloaded data of multiple operators are isolated from each other, an existing eSIM card management method manages own applications by files of each operator, and when a mobile operator is switched, an application on the eSIM card that can be called by a user is changed into an application managed by the switched mobile operator, that is, contents such as an address book included in a first operator cannot be used by a second operator, which causes inconvenience in use of the user, and obviously does not meet requirements of people for the application.

Disclosure of Invention

The application requests to protect an eSIM card operator file management method and device, which can uniformly manage application and data on an 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 secure element and a management element, the secure element stores a plurality of operator files, and the management element is used for managing the operator files on the eSIM card, and the method comprises the following steps: responding to the 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 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 an operator periodically, and the management element modifies the rule file according to the notification information.

Preferably, the rule file stores therein application information.

Preferably, wherein some or all of the currently active applications are managed by the destination operator file according to the rule file, the method comprises the sub-steps of: obtaining a currently running application list and an activated operator identifier; inquiring the rule file according to the application list to obtain the 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 the operator file related to the invoked application, the method further includes the following steps: connecting to an operator server corresponding to an operator service through a management file saved in the management element; sending a service message to an operator server; and the operator server provides the cloud service 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, which comprises 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 application information.

Preferably, the management element manages some or all of the currently active applications from the destination operator file according to the rule file, comprising the sub-steps of: activating operator profile; inquiring the 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 operator switches, part of currently-running compliance applications can continue to run, so that convenience in use of applications in the eSIM card is provided for users.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments described in the present application, and other drawings can be obtained by those skilled in the art according to the drawings.

Fig. 1 is a device configuration diagram of an eSIM card operator file management device according to the present application;

fig. 2 is a device configuration 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 technical solutions in the embodiments of the present application are clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some, but not all, embodiments of the present application. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

Example one

The application provides an eSIM card operator file management apparatus 100, which includes the following components: eSIM card 110, operator server 120.

An eSIM card 110, comprising the components shown in fig. 2:

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

the management element 220 receives the 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; according to the rule file, some or all of the currently active applications are managed by the destination operator file.

The operator server 120 obtains a cloud service matching the identity 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, the structural block diagram of the eSIM card of the present application is shown, where a management element 220 is connected to a secure element 210, and the secure element 210 stores thereon a plurality of operator profiles, each of which includes a corresponding security domain, a file system, a key, and an application. After a certain profile is activated, a corresponding operator security domain (MNO-SD) is managed as a main security domain on the card, and a corresponding file system, a corresponding key and a corresponding application can be used.

Further, the present application provides an eSIM card operator file management method, as shown in fig. 3, including the following steps:

step S310, responding to the 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 profile2, operator profile2 is activated and operator profile1 is deactivated.

Step S320, the management component stores the rule file, and manages some or all currently activated applications by the destination operator file according to the rule file, including the following sub-steps:

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

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

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

the management element regularly receives notification information issued by an operator, wherein the notification information comprises service information provided by an operator server aiming at the application. For example, the mobile operator department provides presentation support for a certain video application.

And the management element modifies the rule file according to the notification information, and the rule file stores the application information. And the management element acquires various service information provided by each operator server for the application 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. That is, the operator providing the optimal service is regarded as the affiliated operator, and further, other operators who can provide the server are recorded in the application information.

For example, the rule file stored in the eSIM card is as shown in table 1:

application AID	Application information	Affiliated operator
			0x1001	Run in profile2	profile1
0x1002	Run in profile1	profile2
			0x1003	Run in 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 called, and the application information of the application stores the operator profile2, which indicates that when the application 0x1001 is run, once the behavior of switching to the operator profile2 occurs, the application 0x1001 may continue to run.

Step S3203, determining whether to allow the currently activated application to run 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 handover occurs from the carrier profile1 to the carrier profile2, the application information indicates that the running application 0x1001 continues to run under the carrier profile 2.

Wherein the application can be stored on the eSIM card secure element or in an eSIM card public area.

Example two

The above describes the application that will be currently running according to the rule file. Example two of the present application is described below.

In an embodiment, after the step of storing a rule file by a management element and managing some or all currently activated applications by a destination operator file according to the rule file, the method further includes the following steps:

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

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

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

EXAMPLE III

On the basis of the second embodiment, the application further includes one or more cloud servers, and the one or more cloud servers are connected with the operator server 120 to provide cloud services matched with the eSIM card.

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

The operator server may also obtain, from the cloud service providers that provide the cloud services, 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;

wherein the eSIM card is connected to an operator server corresponding to an operator service through a management file saved 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 the cloud service matched with the ESIM card.

Corresponding to the method in fig. 3, the present application further provides a computer-readable storage medium, on which a computer program is stored, and the computer program is executed by a processor to perform the steps of the above-mentioned method for controlling security.

Specifically, the storage medium can be a general-purpose storage medium, such as a removable disk, a hard disk, or the like, and when a computer program on the storage medium is executed, the method for issuing an eSIM certificate online can be performed.

In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. The above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only one logical division, and there may be other divisions when actually implemented, and for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection of devices or units through some communication interfaces, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed 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 can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments provided in the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into 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 or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to 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), a magnetic disk or an optical disk, and other various media capable of storing program codes.

It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus once an item is defined in one figure, it need not be further defined and explained in subsequent figures, and moreover, 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 above-mentioned embodiments are only specific embodiments of the present application, and are used for illustrating the technical solutions of the present application, but not limiting the same, and the scope of the present application is not limited thereto, and although the present application is described in detail with reference to the foregoing embodiments, those skilled in the art should understand that: any person skilled in the art can modify or easily conceive the technical solutions described in the foregoing embodiments or equivalent substitutes for some technical features within the technical scope disclosed in the present application; such modifications, changes or substitutions do not depart from the spirit and scope of the present disclosure, which should be construed in light of the above teachings. Are intended to be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. An eSIM card operator file management method, wherein an eSIM card includes a secure element on which a plurality of operator files are stored, and a management element for managing the operator files on the eSIM card, the method comprising the steps of:

responding to the 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 according to which some or all of the currently active applications are managed by the destination operator file.

2. The eSIM card operator file management method of claim 1, wherein the management element periodically receives notification information issued by an operator, and the management element modifies the rule file according to the notification information.

3. The eSIM card operator file management method of claim 2, wherein the rule file stores therein application information.

4. The eSIM card operator file management method of claim 1 wherein some or all of the currently active applications are managed by the destination operator file according to a rule file, comprising the substeps of:

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

inquiring the rule file according to the application list to obtain the 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.

5. The eSIM card operator file management method of claim 1, further comprising, after switching the current operator file to an operator file related to the invoked application, the steps of:

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

sending a service message to an operator server;

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

6. 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; and acquiring application use information in response to the application starting request.

7. The eSIM card of claim 6, wherein the management element periodically receives notification information issued by an operator, and the management element modifies the rule file according to the notification information.

8. The eSIM card of claim 6 wherein the rule file stores application information therein.

9. The eSIM card of claim 6 wherein the administrative component manages some or all of the currently active applications from the destination carrier file according to a rules file, comprising the substeps of:

10. An eSIM card operator file management apparatus comprising the eSIM card of one of claims 6-9, and an operator server that provides a cloud service.