METHOD AND APPARATUS FOR MOBILE TERMINAL MANAGEMENT SUPPORTING SECURITY POLICY

• US 20180131725A1
• Filed: 07/06/2017
• Published: 05/10/2018
• Est. Priority Date: 11/10/2016
• Status: Abandoned Application

• Current Assignee: Electronics and Telecommunications Research Institute
• Original Assignee: Electronics and Telecommunications Research Institute
• Inventors: KIM, Seung-Hyun, KIM, Seok Hyun, KIM, Soo Hyung, KIM, Youngsam, NOH, Jong-Hyouk, CHO, Sangrae, CHO, Young Seob, CHO, Jin-Man, HUH, Seyoung, HWANG, Jung Yeon, JIN, Seung Hun
• Application Number:
  US15/642,450
• Publication Number:
  US 20180131725A1
• Time in Patent Office: Days
• CPC Class Codes: G06F 8/44 Encoding
• CPC Class Codes: G06F 8/53 Decompilation; Disassembly
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources
• CPC Class Codes: H04L 63/20 for managing network security; network security policies in general filtering policies H04L63/0227
• CPC Class Codes: H04W 12/30 Security of mobile devices; Security of mobile applications
• CPC Class Codes: H04W 12/37 Managing security policies for mobile devices or for controlling mobile applications
• CPC Class Codes: H04W 12/63 Location-dependent; Proximity-dependent

Abstract

Disclosed is a method and apparatus for mobile terminal management supporting security policy. An exemplary embodiment of the present invention provides a terminal management method for installing a mobile device management (MDM) function in which a server supports a security policy for a binary mobile application, including: adding, by the server, an MDM interlocking code for each class-method unit of an original application of the binary mobile application; modifying, by the server, the original application into a modification application; and generating and transmitting, by the server, an MDM policy including at least one MDM function to be applied to the modification application to a mobile terminal.

Claims

1. A terminal management method for installing a mobile device management (MDM) function in which a server supports a security policy for a binary mobile application, comprising:

adding, by the server, an MDM interlocking code for each class-method unit of an original application of the binary mobile application;

modifying, by the server, the original application into a modification application; and

generating and transmitting, by the server, an MDM policy including at least one MDM function to be applied to the modification application to a mobile terminal,

wherein the MDM interlocking code checks the MDM policy, and calls an arbitrary MDM function.

2. The terminal management method of claim 1, wherein

the modifying includes:

decompiling the original application to extract class files;

generating a tag with a class name-method name at a beginning portion of a method of each class; and

adding the MDM interlocking code together with the generated tag to the beginning portion of the method.

3. The terminal management method of claim 2, wherein

the modifying includes recompiling the original application to generate the modification application when it is completed to add the tag and the MDM interlocking code for each of the class files of the original application.

4. The terminal management method of claim 1, wherein

the arbitrary MDM function of the MDM policy is performed while the modification application operates in a mobile terminal and the MDM policy is checked according to the MDM interlocking code.

5. The terminal management method of claim 1, further comprising

performing, by the server, policy management of adding, modifying, or deleting the MDM function to, at, or from a predetermined location of each class-method unit of the binary mobile application according to data inputted through a management user interface (UI).

6. The terminal management method of claim 5, wherein

the performing of the policy management includes:

outputting a history of calling the class-method unit including execution details of the method of the class and a currently executing location when the binary mobile application is executed; and

performing policy management of adding, modifying, or deleting the MDM function to, at, or from a predetermined location of the outputted history calling class-method unit.

7. A terminal management method for a mobile terminal that executes a binary mobile application provided from a server, comprising:

executing, by the mobile terminal, the binary mobile application, an MDM interlocking code being added for each class-method unit of the binary mobile application;

checking an MDM policy related to the MDM interlocking code when the MDM interlocking code is identified in the executed binary mobile application; and

performing an arbitrary MDM function of the MDM policy related to the MDM interlocking code.

8. The terminal management method of claim 7, wherein

the MDM interlocking code checks the MDM policy, and calls the arbitrary MDM function.

9. The terminal management method of claim 7, wherein

the checking includes checking the MDM policy related to the MDM interlocking code of the MDM policies when MDM policies including at least one MDM function to be applied to the modification application are provided, stored, and managed from the server.

10. The terminal management method of claim 7, wherein

the MDM policy is represented in a form including an MDM class name, an MDM method name, and a parameter, and

the performing of the MDM function includes calling an MDM class and an MDM method of the MDM policy related to the MDM interlocking code through a JAVA reflection method to perform an MDM function.

11. The terminal management method of claim 10, wherein

the MDM policy includes a tag with a class name-method name, and

the MDM interlocking code is added to a beginning portion of a method of each class together with the tag with the class name-method name.

12. A server provided with an MDM function supporting a security policy for a binary mobile application, comprising:

an input/output portion; and

a processor that is connected to the input/output portion and performs installing of the MDM function,

wherein the processor includes;

an app modification processor configured to add an MDM interlocking code for each class-method unit of an original application of the binary mobile application and to modify the original application into a modification application; and

an MDM policy processor configured to generate an MDM policy including at least one MDM function to be applied to the modification application to transmit it to a mobile terminal through the input/output portion,

wherein the MDM interlocking code checks the MDM policy, and calls the arbitrary MDM function.

13. The server of claim 12, wherein

the app modification processor of the processor includes:

a decompile processing module configured to decompile the original application to extract class files;

an MDM function adding module configured to generate a tag with a class name-method name at a beginning portion of a method of each class and to add the MDM interlocking code together with the generated tag to the beginning portion of the method; and

a recompile processing module configured to recompile the original application to generate the modification application when it is completed to add the tag and the MDM interlocking code for each of the class files of the original application.

14. The server of claim 12, wherein

the input/output portion includes a management UI, and

the MDM policy processor of the processor includes:

a policy management module configured to perform policy management of adding, modifying, or deleting the MDM function to, at, or from a predetermined location of each class-method unit of the binary mobile application according to data inputted through the management UI; and

a policy transmitting module configured to transmit the MDM policy including the MDM function to the mobile terminal through the input/output portion.

15. A mobile terminal that executes a binary mobile application provided from a server, comprising:

an input/output portion; and

a processor that is connected to the input/output portion and executes the binary mobile application,

wherein the processor includes;

an MDM processor configured to receive MDM policies including at least one MDM function to be applied to the modification application through the input/output portion from the server to store and manage it; and

a modification app processor configured to execute the binary mobile application, an MDM interlocking code being added for each class-method unit of the binary mobile application and to load the MDM policy related to the MDM interlocking code from the MDM processor to perform the MDM function,

wherein the MDM interlocking code checks the MDM policy, and calls the arbitrary MDM function.

16. The mobile terminal of claim 15, wherein

the modification app processor of the processor includes:

a code executing module configured to execute the binary mobile application;

a policy checking module configured to check whether the MDM policy related to the MDM interlocking code is present in the MDM processor when the MDM interlocking code is identified in the executed binary mobile application; and

a policy applying module configured to execute the arbitrary MDM function of the MDM policy related to the MDM interlocking code.

17. The mobile terminal of claim 15, wherein

the MDM processor of the processor includes:

a policy database configured to store the MDM policies provided from the server; and

an MDM function processing module configured to perform the MDM function requested by the modification app processor.

18. The mobile terminal of claim 17, wherein

the MDM policy is represented in a form including an MDM class name, an MDM method name, and a parameter, and

the policy applying module is configured to call an MDM class and an MDM method of the MDM policy related to the MDM interlocking code through a JAVA reflection method to perform an MDM function.

19. The mobile terminal of claim 18, wherein

the MDM policy includes a tag with a class name-method name, and

the MDM interlocking code is added to a beginning portion of a method of each class together with the tag with the class name-method name.