WO2017201908A1

WO2017201908A1 - Application program security management method and system

Info

Publication number: WO2017201908A1
Application number: PCT/CN2016/097464
Authority: WO
Inventors: 钟焰涛; 傅文治; 蒋罗
Original assignee: 宇龙计算机通信科技(深圳)有限公司
Priority date: 2016-05-25
Filing date: 2016-08-31
Publication date: 2017-11-30
Also published as: CN105827653A

Abstract

An application program security management method, applicable to a mobile terminal. The mobile terminal comprises an eUICC device provided with a security domain. The method comprises: downloading a key application program; and storing key data generated during registration of the key application program in the security domain. The present invention further provides an application program security management system. By means of storing key data of a key application program in a security domain of an eUICC, leakage of the key data caused by coexistence of multiple eSIM cards is avoided, and thus security of the key data is improved.

Description

Application security management method and system

The present application claims priority to Chinese Patent Application No. 201610352945.9, entitled "Application Security Management Method and System", filed on May 25, 2016, the entire contents of .

Technical field

The present invention relates to the field of communications technologies, and in particular, to an application security management method and system.

Background technique

With the rapid development of the mobile communication network, the Subscriber Identity Module (SIM) has been integrated into the mobile terminal during the device production phase. This SIM card is called an embedded SIM card. eSIM card. Different from the current SIM card supporting only one network operator's service, the eSIM card stores multiple network operator profiles, which can support the mobile terminal to switch between different network operator services.

Currently, the eSIM of the Global System for Mobile Communications Alliance (GSMA) is mainly implemented based on an embedded Universal Integrated Circuit Card (eUICC). Usually, an eUICC chip can download and install dozens of eSIM cards. However, when multiple eSIM cards coexist, key data of the user's key applications (for example, electronic wallet, bank certificate, etc.) may leak.

Summary of the invention

In view of the above, it is necessary to provide an application security management method and system, which can store key data of key applications in the security domain of eUICC, avoiding leakage of key data when multiple eSIM cards coexist, and improving security.

An application security management method is applied to a mobile terminal, where the mobile terminal includes an eUICC device, and the eUICC device is provided with a security domain, and the method includes:

Download key applications; and

The key data generated when the key application is registered is stored in the security domain.

According to a preferred embodiment of the present invention, the key application includes an application for associating a bank card The key data includes an encryption and decryption key, a signature key, and a password.

According to a preferred embodiment of the present invention, after the key data is stored in the security domain, the method further includes:

The occupation notification of the security domain is reported to the subscription manager security route.

According to a preferred embodiment of the invention, the method further comprises:

Pre-store data for authenticating critical applications.

According to a preferred embodiment of the present invention, the method further includes:

Uninstall the key applications, including:

Receiving authentication data input by the user;

Determining the occupation of key data in the security domain when determining that the authentication data input by the user matches the data of the pre-stored authentication key application;

Notifying the subscription manager of the secure routing of the application uninstallation of the security domain; and

Complete the uninstallation of the critical application.

According to a preferred embodiment of the invention, the data of the authentication critical application comprises biometric data, behavioral feature data or cryptographic data of the user.

An application security management system is applied to a mobile terminal, where the mobile terminal includes an eUICC device, and the eUICC device is provided with a security domain, and the system includes:

Download module for downloading critical applications; and

a storage module, configured to store key data generated when the key application is registered in the security domain.

According to a preferred embodiment of the invention, the key application comprises an application associated with a bank card, the key data comprising an encryption and decryption key, a signature key, a password.

According to a preferred embodiment of the invention, the system further comprises:

The reporting module is configured to report the occupation notification of the security domain to the subscription manager.

According to a preferred embodiment of the present invention, the storage module is further configured to:

Pre-store data for authenticating critical applications.

a receiving module, configured to receive authentication data input by a user;

a determining module, configured to determine whether the authentication data input by the user is related to the pre-stored authentication key The application's data matches;

And a releasing module, configured to: when the determining module determines that the authentication data input by the user matches the data of the pre-stored authentication key application, disarming the key data in the security domain;

The reporting module is further configured to report the application uninstallation of the security domain to the subscription manager secure route; and

An uninstallation module is used to complete the uninstallation of the critical application.

It can be seen from the above technical solution that the key data of the critical application can be stored in the security domain of the eUICC, and the key data is prevented from being leaked when multiple eSIM cards coexist, thereby improving security.

DRAWINGS

1 is a schematic diagram of a hardware architecture of a preferred embodiment of a mobile terminal for executing an application security management system of the present invention.

2 is a schematic flow chart of an application security management method according to a first embodiment of the present invention.

FIG. 3 is a schematic diagram of information flow of an application security management method according to a first embodiment of the present invention.

4 is a schematic flow chart of an application security management method according to a second embodiment of the present invention.

Figure 5 is a functional block diagram of the application security management system of the present invention.

Main component symbol description

移动终端Mobile terminal	11
应用程序安全管理系统Application security management system	1010
存储设备 Storage device	2020
处理设备 Processing equipment	3030
显示设备 display screen	4040
eUICC设备 eUICC device	5050

下载模块 Download module	500500
存储模块 Storage module	501501
上报模块Reporting module	502502
接收模块 Receiving module	503503
判断模块 Judgment module	504504
退出模块 Exit module	505505
解除模块 Release module	506506
卸载模块 Unload module	507507
提示模块 Prompt module	508508

detailed description

The present invention will be described in detail below with reference to the drawings and specific embodiments.

1 is a schematic diagram of a hardware architecture of a preferred embodiment of a mobile terminal for executing an application security management system of the present invention. As shown in the hardware architecture diagram, the mobile terminal 1 includes, but is not limited to, an application security management system 10, a storage device 20, a processing device 30, a display device 40, and an embedded universal integrated circuit card (eUICC). ) Device 50.

The mobile terminal 1 may be a mobile terminal capable of automatically performing numerical calculation and/or information processing according to an instruction set or stored in advance, and the hardware thereof includes but is not limited to a microprocessor, an application specific integrated circuit, and a programmable gate array. , digital processors, embedded devices, etc. The mobile terminal 1 may comprise a user equipment. The user equipment includes, but is not limited to, any electronic product that can interact with a user through a keyboard, a mouse, a remote controller, a touch pad, or a voice control device, such as a personal computer, a tablet computer, a smart phone, and a personal digital device. Personal digital assistant (PDA), game console, Internet protocol television (IPTV), smart wearable device, etc. The network where the user equipment is located includes, but is not limited to, the Internet, a wide area network, Metropolitan area network, local area network, virtual private network (VPN), etc.

The application security management system 10 is configured to store key data of the critical application in a security domain of the eUICC when the user downloads the critical application, and read the eUICC security domain when running and/or uninstalling the critical application. The critical data and the user-defined authentication can perform related operations, thus improving the security of critical applications. The critical application is an application that requires high security protection, including, but not limited to, any application associated with a bank card, such as an electronic wallet, mobile banking, and other payment software. Key data for critical applications includes, but is not limited to, encryption and decryption keys, signing keys, and passwords.

The storage device 20 is configured to store program codes of respective program segments in the application security management system 10. The storage device 20 can be a storage device such as a smart media card, a secure digital card, or a flash card. The storage device 10 stores user-defined authentication authentication data, for example, biometric data and/or behavior characteristic data of the user. The biometric data includes fingerprint data, face data, hand data, iris data, retina data, pulse data, or auricle data. The behavior characteristic data includes handwriting, sound, key strength, and the like. In other embodiments, the user-defined authentication authentication data stored by the storage device 10 further includes a verification password set by the user, and the password may be a number, a letter, a symbol, or the like, or a combination of numbers, letters, symbols, and the like.

The processing device 30 can be comprised of one or more microprocessors, digital processors. The processing device 30 is communicatively coupled to the application security management system 10, the storage device 20, the display device 40, and the eUICC device 50. The communication can occur over a serial peripheral interface bus or some other communication path and protocol. In other embodiments, in order to ensure the security of communication, some or all of the communication data may also be encrypted by a private key, which may be a dynamic random key string code.

The display device 40 includes, but is not limited to, a display device having a touch function such as a touch display screen.

The eUICC device 50 is an embedded Universal Integrated Circuit Card (eUICC) for remotely managing a plurality of mobile network operators (MNOs) personal management services and conforms to the global mobile communication system. Regulations of the Global System for Mobile Communications Alliance (GSMA).

As shown in FIG. 2, it is a flowchart of an application security management method according to a first embodiment of the present invention. According to The order of the steps in the flowchart may be changed for different requirements, and some steps may be omitted.

In step 210, the key application is downloaded.

In some embodiments, the critical application may be downloaded through the application security management system 10, or the application may be downloaded through the mobile terminal 1 to download the critical application. The key application refers to an application that requires high security protection, such as an application that associates a bank card, such as payment software, banking software, and the like.

Step 212: Store key data generated when the key application is registered in a security domain of the eUICC device 50.

The key data of the key application includes, but is not limited to, an encryption and decryption key, a signature key, and a password.

The eUICC device 50 can download multiple eSIM cards, and different eSIM cards can use different mobile network operators. Each eSIM card stores information such as user identity, user authentication parameters (eg, encryption and decryption keys, etc.) and algorithms, user's phone book and short message data, and customized parameters of the mobile network operator.

In this embodiment, the eUICC device 50 has a plurality of unassigned security domains in the storage space, and each of the unassigned security domains may be subsequently assigned to the eSIM card. Each unassigned security domain in the eUICC device 50 has a permanent and unique identifier ID. The security domain is used for secure storage of security values such as cryptographic keys, critical data for critical applications. In different embodiments, the storage space of the eUICC device 50 may be preset with a security domain, and the preset security domain may be allocated to the newly downloaded eSIM card, or may be used only for storing the security value without Assigned to the newly downloaded eSIM card. In other embodiments, the security domain may also provide access to security information through one or more standardized protocols as known to those skilled in the art.

Step 214: Report the occupation notification of the security domain to the subscription manager security route.

In this embodiment, the application security management system 10 reports the occupation notification of the security domain to the subscription manager through the network.

The Subscription Manager Secure Routing (SM-SR) is mainly responsible for secure routing and transmission of eUICC remote profile data. The specific process of the application security management system 10 reporting the occupation notification of the security domain to the SM-SR is shown in FIG. 3 and the corresponding description.

In other embodiments, the application security management method may further include: the application The security management system 10 pre-stores data for authenticating critical applications.

In this embodiment, the application security management system 10 receives data of one or more authentication critical applications preset by the user and stores data of the authentication critical application. The data of the authentication critical application may be biometric data of the user, and the biometric data of the user includes fingerprint data, face data, hand data, iris data, retina data, pulse data or auricle data. The data of the authentication critical application may also be behavior characteristic data of the user, and the behavior characteristic data of the user includes handwriting, sound, key strength, and the like. The data of the authentication critical application may also be password data, and the password may be a number, a letter, a symbol, or the like or a combination of numbers, letters, symbols, and the like. In other embodiments, the data of the authentication critical application may also be a combination of two or all of the user's biometric data, behavioral feature data, and password data.

Referring to FIG. 3, the application security management system 10 reports the information flow of the occupation information of the security domain to the SM-SR. The order of the steps in the flowchart may be changed according to different requirements, and some steps may be omitted.

S310: The mobile terminal 1 sends an application installation occupation notice of the security domain to the mobile network operator MNO.

In this embodiment, the application security management system 10 of the mobile terminal 1 sends an application installation occupation notification of the security domain to the mobile network operator MNO through the network. The application installation occupation notification of the security domain carries an identifier of the security domain, an identifier of the eUICC, and remaining space information of the security domain.

S312: MNO and SM-SR mutually authenticate.

The MNO and the SM-SR first perform mutual authentication: the MNO confirms that the SM-SR is legal and reliable, and the SM-SR also confirms that the identity information announced by the MNO is authentic. After the two-way authentication succeeds, the MNO and SM-SR establish a secure IP connection (to prevent remote configuration information from leaking).

S314: The MNO sends an application installation occupation notification of the security domain to the SM-SR.

S316: The SM-SR records the occupation information of the security domain in a database.

The invention stores the key data of the key application in a secure domain of the eUICC, and can effectively improve the security of the key data when a plurality of eSIM cards coexist.

When running the critical application, it is necessary to read the key data stored in the eUICC. In other embodiments, it is also required to determine whether the data input by the user matches the data of the pre-stored authentication critical application, only in determining the data input by the user and the pre-stored authentication critical application. The critical application can be run when the program's data matches.

When the critical application is uninstalled, the SM-SR is required to report the application uninstallation of the security domain to meet the SM-SR management of the eUICC. For details, see Figure 4. The order of the steps in the flowchart may be changed according to different requirements, and some steps may be omitted.

Step 410: Receive authentication data input by a user.

In some embodiments, the application security management system 10 may receive fingerprint data input by the user by touching the display device 40, hand shape data, and may also receive key velocity data input by the user by pressing the display device 40. Handwriting data input by the user by writing characters on the display device 40 or input password data or the like can be received. In some embodiments, the mobile terminal 1 further includes a voice device, and the application security management system 10 can receive sound data input by the user through the voice device. In some embodiments, the mobile terminal 1 further includes an image collection device, and the application security management system 10 can receive facial data, iris data, retina data, and auricle data input by the user through the image collection device. .

Step 412: Determine whether the authentication data input by the user matches the authentication data of the pre-stored key application.

When the application security management system 10 determines that the authentication data input by the user matches the authentication data of the pre-stored key application, step 414 is performed. When the application security management system 10 determines that the authentication data input by the user does not match the authentication data of the pre-stored critical application, step 413 is performed.

In step 413, the uninstallation of the key application is exited.

In some embodiments, the step 413 may further include the application security management system 10 displaying a prompt for user authentication failure on the display device 40, or outputting the unsuccessful voice information through the voice device.

In step 414, the occupation of key data in the security domain is released.

In this embodiment, the application security management system 10 deletes key data in the security domain to release the occupation of key data in the security domain.

Step 416: Report the application uninstallation of the security domain to the SM-SR.

In this embodiment, the application security management system 10 reports the application uninstallation of the security domain to the SM-SR through the network.

The application security management system 10 reports the application uninstallation of the security domain to the SM-SR. The specific process of the notification is reported to the application security management system 10 to report the occupation notification of the security domain to the subscription manager. This article will not go into details here.

Step 418, completing the uninstallation of the key application.

As shown in FIG. 5, the application security management system 10 includes a downloading module 500, a storage module 501, a reporting module 502, a receiving module 503, a determining module 504, an exiting module 505, a releasing module 506, an uninstalling module 507, and a prompting module 508. . A module referred to in the present invention refers to a series of computer program segments that can be executed by processing device 30 and that are capable of performing fixed functions, which are stored in storage device 20. In the present embodiment, the functions of the respective modules will be described in detail in the subsequent embodiments.

The download module 500 is configured to download a critical application.

In some embodiments, the download module 500 can log in to the application mall through the mobile terminal 1 to download a key application. The key application refers to an application that requires high security protection, such as an application that associates a bank card, such as payment software, banking software, and the like.

The storage module 501 is configured to store key data generated when the key application is registered in a security domain of the eUICC device 50.

The eUICC device 50 can download multiple eSIM cards, and different eSIM cards can use different mobile network operators. Each eSIM card stores information such as a user identity, a user authentication parameter (addition and decryption key, etc.) and an algorithm, a user's phone book and short message data, and a customized parameter of the mobile network operator.

The reporting module 502 is configured to report the occupation notification of the security domain to the subscription manager.

In this embodiment, the reporting module 502 reports the occupation notification of the security domain to the subscription manager through the network.

The storage module 501 is further configured to pre-store data of the authentication critical application.

In this embodiment, the storage module 501 receives data of one or more authentication critical applications preset by the user and stores the data. The data of the authentication critical application may be biometric data of the user, and the biometric data of the user includes fingerprint data, face data, hand data, iris data, retina data, pulse data or auricle data. The data of the authentication critical application may also be behavior characteristic data of the user, and the behavior characteristic data of the user includes handwriting, sound, key strength, and the like. The data of the authentication critical application may also be password data, and the password may be a number, a letter, a symbol, or the like or a combination of numbers, letters, symbols, and the like. In other embodiments, the data of the authentication critical application may also be a combination of two or all of the user's biometric data, behavioral feature data, and password data.

When running the critical application, it is necessary to read the key data stored in the eUICC. In other embodiments, it is also required to determine whether the data input by the user matches the data of the pre-stored authentication critical application, and only determines the data input by the user and the data of the pre-stored authentication critical application. The critical application can be run when it matches.

When the critical application is uninstalled, the application release release notification of the security domain needs to be reported to the SM-SR to meet the SM-SR management of the eUICC.

The receiving module 503 is configured to receive authentication data input by a user.

In this embodiment, the receiving module 503 can receive the fingerprint data and the hand shape data input by the user by touching the display device 40, and can also receive the button strength data input by the user by pressing the display device 40, and can also receive the user pass. The handwriting data or the input password data or the like is written on the display device 40. In some embodiments, the mobile terminal 1 further includes a voice device, and the receiving module 503 can receive the number of voices input by the user through the voice device. according to. In some embodiments, the mobile terminal 1 further includes an image acquisition device, and the receiving module 503 can receive facial data, iris data, retina data, and auricle data input by the user through the image acquisition device.

The determining module 504 is configured to determine whether the authentication data input by the user matches the authentication data of the pre-stored key application.

The exiting module 505 is configured to exit the uninstallation of the critical application when the authentication data input by the user does not match the authentication data of the pre-stored critical application.

The release module 506 is configured to delete key data in the security domain to release the occupation of key data in the security domain.

The reporting module 502 is further configured to report the notification of application uninstallation of the security domain to the SM-SR.

In this embodiment, the reporting module 502 reports the application uninstallation of the security domain to the SM-SR through the network.

The uninstalling module 507 is configured to complete the uninstallation of the critical application when the authentication data input by the user matches the authentication data of the pre-stored critical application.

The prompting module 508 is configured to prompt the user to fail the authentication on the display device 40, or output the unsuccessful voice information through the voice device.

In the several embodiments provided by the present invention, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the device embodiments described above are merely illustrative. For example, the division of the modules is only a logical function division, and the actual implementation may have another division manner.

The modules described as separate components may or may not be physically separated, and the components displayed as modules may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, each functional module in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above integrated unit can be implemented in the form of hardware or in the form of hardware plus software function modules.

The above-described integrated unit implemented in the form of a software function module can be stored in a computer readable storage medium. The above software function modules are stored in a storage medium, including several instructions. Part of the steps of the method of the various embodiments of the present invention are performed by a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor.

It is apparent to those skilled in the art that the present invention is not limited to the details of the above-described exemplary embodiments, and the present invention can be embodied in other specific forms without departing from the spirit or essential characteristics of the invention. Therefore, the present embodiments are to be considered as illustrative and not restrictive, and the scope of the invention is defined by the appended claims instead All changes in the meaning and scope of equivalent elements are included in the present invention. Any reference signs in the claims should not be construed as limiting the claim. In addition, it is to be understood that the word "comprising" does not exclude other elements or steps. A plurality of units or devices recited in the system claims can also be implemented by a unit or device by software or hardware. The first, second, etc. words are used to denote names and do not denote any particular order.

It should be noted that the above embodiments are only for explaining the technical solutions of the present invention and are not intended to be limiting, and the present invention will be described in detail with reference to the preferred embodiments. Modifications or equivalents are made without departing from the spirit and scope of the invention.

Claims

An application security management method is applied to a mobile terminal, where the mobile terminal includes an eUICC device, and the eUICC device is provided with a security domain, and the method includes:

Download key applications; and

The key data generated when the key application is registered is stored in the security domain.
The application security management method according to claim 1, wherein the key application comprises an application associated with a bank card, and the key data comprises an encryption and decryption key, a signature key, and a password.
The application security management method according to claim 1, wherein after the key data is stored in the security domain, the method further comprises:

The occupation notification of the security domain is reported to the subscription manager security route.
The application security management method according to claim 1, wherein the method further comprises:

Pre-store data for authenticating critical applications.
The application security management method according to claim 4, wherein the method further comprises:

Uninstall the key applications, including:

Receiving authentication data input by the user;

Determining the occupation of key data in the security domain when determining that the authentication data input by the user matches the data of the pre-stored authentication key application;

Notifying the subscription manager of the secure routing of the application uninstallation of the security domain; and

Complete the uninstallation of the critical application.
The application security management method according to any one of claims 4 to 5, wherein the data of the authentication critical application includes biometric data, behavior characteristic data or password data of the user.
An application security management system is applied to a mobile terminal, where the mobile terminal includes an eUICC device, and the eUICC device is provided with a security domain, wherein the system includes:

Download module for downloading critical applications; and

a storage module, configured to store key data generated when the key application is registered in the security domain.
The application security management system according to claim 7, wherein said key application comprises an application associated with a bank card, said key data comprising an encryption and decryption key, a signature key, and a password.
The application security management system of claim 7, wherein the system further comprises:

The reporting module is configured to report the occupation notification of the security domain to the subscription security router after the critical data is stored in the security domain.
The application security management system according to claim 7, wherein the storage module is further configured to pre-store data of the authentication critical application.
The application security management system of claim 10, wherein the system further comprises:

a receiving module, configured to receive authentication data input by a user;

a determining module, configured to determine whether the authentication data input by the user matches the data of the pre-stored authentication critical application;

And a releasing module, configured to: when the determining module determines that the authentication data input by the user matches the data of the pre-stored authentication key application, disarming the key data in the security domain;

The reporting module is further configured to report the application uninstallation of the security domain to the subscription manager secure route; and

An uninstallation module is used to complete the uninstallation of the critical application.
The application security management system according to any one of claims 10 to 11, wherein the data of the authentication critical application includes biometric data, behavior characteristic data or password data of the user.