KR101425397B1 - Method of Converting Android Application for Registration to the Second Market - Google Patents
Method of Converting Android Application for Registration to the Second Market Download PDFInfo
- Publication number
- KR101425397B1 KR101425397B1 KR1020130013821A KR20130013821A KR101425397B1 KR 101425397 B1 KR101425397 B1 KR 101425397B1 KR 1020130013821 A KR1020130013821 A KR 1020130013821A KR 20130013821 A KR20130013821 A KR 20130013821A KR 101425397 B1 KR101425397 B1 KR 101425397B1
- Authority
- KR
- South Korea
- Prior art keywords
- market
- code
- payment
- authentication
- application
- Prior art date
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/20—Software design
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q50/00—Systems or methods specially adapted for specific business sectors, e.g. utilities or tourism
- G06Q50/10—Services
Abstract
The present invention relates to a method of converting an Android application for a second market registration, and more particularly, to a method of converting an Android application developed for a first market into an application of a form and a structure that can be registered and used in a second market To a method of converting an Android application for a second market registration.
The method for converting an Android application for second market registration of the present invention is a method for converting an application to an authentication module or a payment module in various markets without having to newly develop an application according to an authentication module or a payment module of each market There are advantages to be able to.
The method of converting an Android application for the second market registration of the present invention is advantageous in that it is convenient to convert an application according to various market conditions so that a market operator can induce many applications to be registered in the market, There are advantages that can be useful.
Description
The present invention relates to a method of converting an Android application for a second market registration, and more particularly, to a method of converting an Android application developed for a first market into an application of a form and a structure that can be registered and used in a second market To a method of converting an Android application for a second market registration.
With the spread of smartphones and tablets, various applications are being developed and used. Because applications developed for the iPhone or iPad are sold in a single market run by Apple, application developers can register their applications only in those markets.
Android apps developed by Google are different from applications for iOS. There is a PlayStore, a typical Android application market run by Google, but there are also a number of other markets for Android applications. A typical example is a market operated by each communication company providing a wireless communication service of a cellular phone.
These various applications market for Android have different authentication modules and payment modules for each market. Therefore, from the perspective of the application developer, it is troublesome to prepare the application by newly preparing the authentication code and the payment code that can operate in accordance with the authentication module and the payment module of each market in each market.
From the viewpoint of the operator who operates the market, various kinds of applications must be registered in the market so that consumers can visit the market and actively operate the market. Due to the developer hassle mentioned above, There is a problem in that it is reluctant to register.
The present invention has been conceived to solve the problems as described above, and it is an object of the present invention to provide a method and system for converting an application into a form that can be automatically sold in a market without having to newly develop an application in accordance with an authentication module and a payment module of each market The purpose of this article is to provide a method of converting an Android application for second market registration.
In order to solve the above problems, a method of converting an Android application for a second market registration of the present invention is a method of automatically registering an application registered in a first market and provided to users in a second market A method of converting an Android application for a second market registration, the method comprising: (a) separating an application created for a first market into an executable file portion and a resource file portion; (b) retrieving an authentication code or a payment code associated with authentication or payment of an application from the executable file separated in the step (a); (c) converting the authentication code or the payment code retrieved in step (b) into an authentication code or a payment code usable in the second market; And (d) reconfiguring an executable file of the application using the authentication code or the payment code converted in the step (c) and combining the executable file with the resource file to generate a conversion application file. .
The method for converting an Android application for second market registration of the present invention is a method for converting an application to an authentication module or a payment module in various markets without having to newly develop an application according to an authentication module or a payment module of each market There are advantages to be able to.
The method of converting an Android application for the second market registration of the present invention is advantageous in that it is convenient to convert an application according to various market conditions so that a market operator can induce many applications to be registered in the market, There are advantages that can be useful.
The method for converting the Android application for the second market registration of the present invention converts an apk file that has been compiled to a form that can be used in a desired market automatically when an application developer provides the compiled apk file without providing the source code of the application There is an advantage that application developers can use without worrying about leakage of trade secrets.
1 is a flowchart illustrating an example of a method of converting an Android application for a second market registration according to the present invention.
Hereinafter, a method of converting an Android application for second market registration according to the present invention will be described in detail with reference to the accompanying drawings.
1 is a flowchart illustrating an example of a method of converting an Android application for a second market registration according to the present invention.
Applications for Android are registered in each market in the form of an apk file. The apk file contains a resource file containing various images, text, audio, and a .dex file, which is an executable file of the application. Such a .dex file contains code related to authentication or settlement of the application as well as the actual operation of the application.
The authentication code calls the authentication module of the market and confirms whether or not the application is a normal application by receiving a response from the authentication module of the market, if necessary, to confirm whether or not the application is acquired in a normal path and installed in the smart device. In the case of a paid application, it calls the authentication module of the market as necessary to confirm whether the application is normally purchased, receives a response from the market, and authenticates whether or not the application is normal.
The billing code generates a query signal for calling the payment module of the market through the payment code when it is necessary to settle the fee for the same reason as purchasing an item in the process of using the application, receives the response of the payment module of the market, To pay the cost.
Some applications include both an authentication module and a payment module depending on the type of application, and some applications include only an authentication module and a payment module.
The method for converting an Android application for second market registration of the present invention is for converting an application having any one of an authentication module and a payment module into a form that can be registered and used in another market.
Hereinafter, a process of converting an application registered and used in the first market into a form that can be registered and used in the second market will be described.
First, an application for the first market is prepared. The application may be provided by the developer of the first market, or may be downloaded from the first market.
In this state, the application prepared for the first market is divided into an executable file (.dex) part and a resource file part (step (a), step S100).
Next, in step (a), an authentication code or a payment code associated with authentication or payment of the application is retrieved from the executable file (step (b), step S200). As described above, only one of the authentication code and the payment code may be provided depending on the application, or both the authentication code and the payment code may be provided.
The following four examples are specific methods of retrieving the authentication code and the payment code from the executable file. Depending on the situation, use one of four methods or use them in combination to retrieve the authorization code and the payment code.
The first way is to search for a string pattern. Since there is a pattern of strings commonly used in authentication codes or payment codes, it is searched in the executable file to retrieve the authentication code and the payment code. If there is a verification code and a payment code used only in the first market, the authentication code and the payment code are searched by searching the pattern of the string. Signature-based pattern checking can also be used as a method of retrieving authentication codes and payment codes. Similar to how to scan for malicious code in virus scanning, you can search the authentication code and the payment code by comparing the pattern of the payment code with the predefined stored authentication code.
The second method is to analyze the function pattern inside the executable file. When a function is called from within an executable file, it traces back the number and type of arguments passed to the function to determine whether the function is an authorization code or a payment code.
The third way is to analyze the number of member variables and the pattern of the class. The number of the member variables and the pattern of the class that the authentication class or the payment class of the first market necessarily possesses are analyzed and it is searched whether the corresponding code is the authentication code or the settlement code.
The fourth method is to use superclass or interface. The authentication code or the settlement code is traced by searching for a class having an upper class or an interface among the classes in the executable file. Since the authentication code or the payment code class has a superclass or an interface, the authentication code or the payment code is searched using this feature.
If the authentication code and the payment code are found by the above-described method, the authentication code or the payment code retrieved in step (b) is converted into an authentication code or a payment code that can be used in the second market (step (c) ).
The method (c) can be carried out by the following three methods.
The first method is to replace the authentication code with the payment code. The code for calling the authentication module in the first market is replaced with the code for replacing the authentication module in the second market and the code for calling the payment module in the first market is replaced with the code for calling the payment module in the second market .
The second method is not a substitution of an authentication code or a payment code but a method of converting a value called by an authentication code and a payment code into a value for calling an authentication module and a payment module of the second market.
The authentication code and the payment code generate a value for calling the authentication module and the payment module of the market, respectively, and the authentication module and the payment module of the market generate a response to the value to be called. The application's authorization code and payment code receive the market's response and verify the authorization and payment. The response to the invocation of the authentication code and billing code is generated by different protocols for each market. Therefore, in each market, the values for calling the authentication module and the payment module of the market, and the response format and contents thereof are set differently.
A method may be used to translate the authentication code and the value invoked in the billing code to make the authentication code and billing code configured to receive a response and to make a call to the authentication module and billing module of the first market to operate in the second market have. That is, a value for calling the authentication module or the payment module of the first market in the authentication code or the payment code is converted into a value for calling the authentication module or the payment module of the second market, and the value of the authentication module or the payment module And converts it into the response format of the authentication module of the first market or the settlement module of the first market to convert the authentication code or the payment code retrieved in the step (b).
When the conversion of the authentication code and the payment code is completed as described above, the application executable file is reconfigured using the converted authentication code and the payment code, and the application file is combined with the resource file to create a new application file (Step (d), step S400).
When the creation of the conversion application file is completed, the developer can provide the application developer to register directly in the second market, or the person who is requested to convert can register in the second market on behalf of the application developer. In some cases, the operator of the second market may register the converted application directly in the second market.
As described above, the method for converting the Android application for the second market registration according to the present invention does not require the developer of the application to grasp the authentication and settlement method of the new market every time and newly develop an application corresponding thereto, There is an advantage of reducing.
Further, it is also necessary to provide the source code of the application when requesting the conversion of the application to the person who performs the task of converting the application according to each market by using the conversion method of the Android application for the second market registration according to the present invention There is an advantage in that it only provides the compiled apk file. In the case of providing the source code, there is a concern that the developer secrets trade secrets such as the technology and the knowledge, so that it is reluctant to provide the source code. However, this is not a concern when providing the same apk file to the user. Therefore, there is an advantage that the developer can actively request the conversion of the application without concern about the trade secret infringement.
For the operators of the second market, it is also possible for the application's developers to convert the application into a form that can be used in the second market without much difficulty and register it in the second market, thereby increasing the number of applications registered in the second market, Is easily activated.
The case where the application in which authentication and settlement are performed in the first market is converted into the authentication and settlement in the second market has been described as an example. However, in some cases, the authentication is performed in the second market, You can also convert the application to be in a separate payment server from the two markets.
In this case, the step (c) described above is carried out as follows.
(b), the code for calling the authentication module of the first market is replaced with the code for calling the authentication module of the second market, and the code for receiving the response of the authentication module of the first market Is replaced with a code for receiving the response of the authentication module of the second market, and the authentication code conversion is performed in the same manner as described above.
(b), the code for calling the payment module of the first market is replaced with the code for calling the payment server, and the code for receiving the response of the payment module of the first market is transmitted to the payment server To the receiving code.
When the application is converted in this manner, the settlement is made in the settlement server even if it is registered in the second market. In the case of the conventional market, the market for purchasing or downloading the application and the market for the item in the application were the same. However, using the same method as described above, the payment of the application can be processed in the payment server designated by the user, regardless of the market in which the application is provided to the user. Using this method, you can also effectively use a point-based payment method. Most of the conventional markets use a method of paying cash basically regardless of a payment method such as a card or a cellular phone charge. However, when the payment server using method is used, the payment server gives the user points by various marketing methods, and the user can pay for the application by using the points.
Claims (8)
(a) separating an application made for a first market into an executable file part and a resource file part;
(b) retrieving an authentication code or a payment code associated with authentication or payment of an application from the executable file separated in the step (a);
(c) converting the authentication code or the payment code retrieved in step (b) into an authentication code or a payment code usable in the second market; And
(d) reconstructing an executable file of the application using the authentication code or the payment code converted in the step (c), and combining the executable file with the resource file to generate a converted application file,
Wherein the step (b) is performed by searching a string pattern related to authentication or settlement in the executable file.
(a) separating an application made for a first market into an executable file part and a resource file part;
(b) retrieving an authentication code or a payment code associated with authentication or payment of an application from the executable file separated in the step (a);
(c) converting the authentication code or the payment code retrieved in step (b) into an authentication code or a payment code usable in the second market; And
(d) reconstructing an executable file of the application using the authentication code or the payment code converted in the step (c), and combining the executable file with the resource file to generate a converted application file,
Wherein the step (b) is performed by a method of analyzing a function pattern in the executable file by using a number of arguments and a class type to be passed to the function when calling a function in the executable file. 2 How to convert Android applications for market registration.
(a) separating an application made for a first market into an executable file part and a resource file part;
(b) retrieving an authentication code or a payment code associated with authentication or payment of an application from the executable file separated in the step (a);
(c) converting the authentication code or the payment code retrieved in step (b) into an authentication code or a payment code usable in the second market; And
(d) reconstructing an executable file of the application using the authentication code or the payment code converted in the step (c), and combining the executable file with the resource file to generate a converted application file,
Wherein the step (b) is performed by a method of analyzing a number of member variables and a class pattern that are essentially required by the authentication class or the payment class of the first market. Conversion method.
(a) separating an application made for a first market into an executable file part and a resource file part;
(b) retrieving an authentication code or a payment code associated with authentication or payment of an application from the executable file separated in the step (a);
(c) converting the authentication code or the payment code retrieved in step (b) into an authentication code or a payment code usable in the second market; And
(d) reconstructing an executable file of the application using the authentication code or the payment code converted in the step (c), and combining the executable file with the resource file to generate a converted application file,
Wherein the step (b) is performed by searching for an upper class or a class having an interface among the classes in the executable file.
Wherein the step (c) comprises: replacing the code for calling the payment module of the first market with the code for calling the payment module of the second market in the authentication code or the payment code retrieved in the step (b) And a code for receiving a response of the payment module of the first market is replaced with a code for receiving a response of the payment module of the second market.
The step (c)
Wherein in the authentication code retrieved in step (b), a code for calling the authentication module of the first market is replaced with a code for calling the authentication module of the second market, and a response of the authentication module of the first market Replacing the received code with a code for receiving a response from the authentication module of the second market,
In the billing code retrieved in the step (b), a code for calling the payment module of the first market is replaced with a code for calling a payment server that is provided separately from the first and second markets and is configured to take charge of payment only , A code for receiving a response from the payment module of the first market is replaced with a code for receiving a response from the payment server,
Wherein the payment server is configured to process the payment of the application separately from the first market and the second market.
In the step (c), a value for calling the authentication module or the payment module of the first market in the authentication code or the payment code found in the step (b) is a value for calling the authentication module or the payment module of the second market And converts the authentication code or the payment code retrieved in step (b) so as to use a response format of the authentication module or the payment module of the second market and convert it into a response format of the authentication module or the payment module of the first market, The method comprising the steps of:
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| KR1020130013821A KR101425397B1 (en) | 2013-02-07 | 2013-02-07 | Method of Converting Android Application for Registration to the Second Market |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| KR1020130013821A KR101425397B1 (en) | 2013-02-07 | 2013-02-07 | Method of Converting Android Application for Registration to the Second Market |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| KR101425397B1 true KR101425397B1 (en) | 2014-08-01 |
Family
ID=51749198
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| KR1020130013821A KR101425397B1 (en) | 2013-02-07 | 2013-02-07 | Method of Converting Android Application for Registration to the Second Market |
Country Status (1)
| Country | Link |
|---|---|
| KR (1) | KR101425397B1 (en) |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20130012288A (en) * | 2011-07-25 | 2013-02-04 | 삼성전자주식회사 | Apparatus and method for changing theme of application in portable terminal |
-
2013
- 2013-02-07 KR KR1020130013821A patent/KR101425397B1/en active IP Right Grant
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20130012288A (en) * | 2011-07-25 | 2013-02-04 | 삼성전자주식회사 | Apparatus and method for changing theme of application in portable terminal |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| KR102249262B1 (en) | Cloud service custom execution environment | |
| CN106030528B (en) | Agent data service | |
| KR102288858B1 (en) | Mobile cloud service architecture | |
| CN105531670A (en) | Smart mobile application development platform | |
| CN103744686B (en) | Control method and the system of installation is applied in intelligent terminal | |
| KR101171321B1 (en) | A system and method for car service management using mobile augmented reality in smart phone | |
| CN103713902B (en) | A kind of BOA Compilation Methods and system based on android system | |
| JP5905489B2 (en) | Software activation system | |
| CN109716331A (en) | Meet the shared application deployment with decision service platform mode of application data | |
| CN110262777B (en) | Block chain application framework | |
| CN105630518A (en) | Method and device for updating resources of Android application software | |
| AU2015206386B2 (en) | Privacy setting metadata for application developers | |
| KR20130116409A (en) | Method and apparatus to evaluate required permissions for application | |
| Santoro et al. | Web Application Programming Interfaces (APIs): General-Purpose Standards, Terms and European Commission Initiatives | |
| CN106055375A (en) | Application program installation method and device | |
| CN107402792B (en) | Integration method, device, equipment and storage medium of application software installation package | |
| CN102685122A (en) | Software protection method based on cloud server | |
| CN103885784B (en) | Method for establishing Android platform with security module and plugging function | |
| AU2014412020B2 (en) | Techniques to transform network resource requests to zero rated network requests | |
| KR20150087723A (en) | System and method for ordering food | |
| CN105930713A (en) | Method and terminal for generating identifying codes | |
| CN110908666B (en) | Source code sharing management method, device, equipment and computer storage medium | |
| KR101425397B1 (en) | Method of Converting Android Application for Registration to the Second Market | |
| US11803786B2 (en) | Enterprise integration platform | |
| CN112613063B (en) | Data verification system construction method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| E701 | Decision to grant or registration of patent right | ||
| GRNT | Written decision to grant | ||
| FPAY | Annual fee payment |
Payment date: 20170623 Year of fee payment: 4 |
|
| FPAY | Annual fee payment |
Payment date: 20190627 Year of fee payment: 6 |