KR101523266B1 - Method, server and computer-readable recording media for managing meta store - Google Patents

Abstract

The present invention relates to a method of managing a meta store, a server, and a computer-readable recording medium. A method for managing a meta store according to the present invention includes the steps of: (a) registering a static resource and metadata for creating a predetermined application using an open device API and an external HTML5 authoring tool in a meta store; (b) Setting a platform, (c) referring to the set build target OS and platform information, checking essential consistency between i) the static resource and metadata, and ii) the parameter information delivered from the build target meta-repository (D) calling the external open build system and the API to generate a target executable file suitable for the OS and platform set in the step (b) and returning to the external open build system and API if the required consistency is satisfied; and (e) And storing and registering the target executable file and the resource and meta data in a meta source repository.

Description

TECHNICAL FIELD [0001] The present invention relates to a meta store management method, a server, and a computer readable recording medium.

The present invention relates to a method of managing a meta store, a server, and a computer-readable recording medium, and more particularly, to a method and apparatus for managing a metadata and a static resource for creating a predetermined application using an open device API and an external HTML5 authoring tool, And checks the essential consistency between i) the static resource and the metadata, and ii) the parameter information received from the build target meta-repository, and then satisfies the required consistency , It creates a target executable file that is suitable for the OS and platform that is set by calling the external open build system and API, and returns the meta-store to return and register resources and metadata with the target executable file in the meta-source repository A management method, a server, and a computer-readable recording medium.

Recently, the spread of smart phones is being activated, and various types of applications are being developed and rapidly spreading in an open environment. In general, the online open market system is divided into a developer portal and a buyer portal. In the developer portal, developers register and price applications, while the buyer portal provides virtual infrastructure that allows buyers to search, Of the market. The online open market provides developers with development support, verification, distribution, and statistics, and provides buyers with search, purchase, and installation procedures for content tailored to their device.

The distribution of various kinds of developed applications through open market is a commerce activity that starts from Apple's App Store and runs on all mobile platforms such as Android Market and Windows Marketplace. Also, not the platform owners such as Amazon and SK Telecom We are entering the 3rd party market operation business.

Korean Patent Laid-Open Publication No. 10-2011-0066274 relates to an open marketplace system, a server, and a method of providing an application using the open marketplace server. The open marketplace server provides a development tool necessary for developing an application, A developer portal that registers an application, a test bed that tests the registered application (Test Bed), and a buyer portal that sells the tested application to the buyer on the testbed. to provide. However, even in Korean Patent Laid-Open Publication No. 10-2011-0066274, since different markets have different OSs and platforms, a developer performs a separate build process for each platform to develop an application, There is a need for registration processing.

In order to solve the above problems, the present invention is characterized in that a static resource and meta data for creating a predetermined application are registered in a meta store, a target execution file is provided corresponding to a target OS and platform set from an external open build system, Management of a target executable file corresponding to an open market, each target OS and platform, and interworking with a plurality of external open markets, not only managing a predetermined application on the meta store but also interworking with various external open markets, It is possible to process a series of processes of registering an application of the application at a time. Therefore, it is possible to eliminate the inconvenience of generating separate executable files according to the OS and platform and separately registering the generated executable files according to the market.

According to a first technical aspect of the present invention, there is provided a method for managing a build target OS, the method comprising: (a) registering a static resource and metadata for creating a predetermined application using an open device API and an external HTML5 authoring tool in a meta store; And setting a platform, (c) referring to the set build target OS and platform information, checking essential consistency between i) the static resource and metadata, and ii) the parameter information received from the target meta-repository (D) calling the external open build system and the API to generate a target executable file suitable for the OS and platform set in the step (b) and returning to the external open build system and API if the required consistency is satisfied; and (e) Storing the target executable file and the resource and meta data in a meta-source repository and registering the meta-store in the meta-source repository; Not getting.

According to a second technical aspect of the present invention, there is provided a method for registering a static resource and metadata for creating a predetermined application using an open device API and an external HTML5 authoring tool in a meta store, And, when the platform is set up, checking the required consistency between i) the static resource and metadata, and ii) the parameter information delivered from the target meta-store, with reference to the set build target OS and platform information, System and an API to generate a target executable file for the set target OS and platform and return the target executable file to the meta source repository together with the resource and meta data, A meta file including an executable file generation unit Thor offers a management server.

According to the present invention, after a static resource and metadata for producing a predetermined application are registered in a meta store, a target executable file corresponding to a target OS and a platform set from an external open build system is received, Managing a target executable file corresponding to an OS and a platform and interworking with a plurality of external open markets to manage a predetermined application on a metastore and registering a predetermined application by linking with various external open markets Therefore, it is possible to eliminate the inconvenience of generating separate executable files according to the OS and platform and registering the generated executable files separately according to the market.

1 is a diagram for explaining an overall system for creating and managing an application corresponding to each OS and platform using a meta store according to an embodiment of the present invention and registering the application in an external open market.
2 is a diagram illustrating a configuration of a management server of a meta store according to an embodiment of the present invention.

The following detailed description of the invention refers to the accompanying drawings, which illustrate, by way of illustration, specific embodiments in which the invention may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the invention. It should be understood that the various embodiments of the present invention are different, but need not be mutually exclusive. For example, certain features, structures, and characteristics described herein may be implemented in other embodiments without departing from the spirit and scope of the invention in connection with an embodiment. It is also to be understood that the position or arrangement of the individual components within each disclosed embodiment may be varied without departing from the spirit and scope of the invention. The following detailed description is, therefore, not to be taken in a limiting sense, and the scope of the present invention is to be limited only by the appended claims, along with the full scope of equivalents to which such claims are entitled, if properly explained. In the drawings, like reference numerals refer to the same or similar functions throughout the several views.

Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings, so that those skilled in the art can easily carry out the present invention.

1 is a diagram for explaining an overall system for creating and managing an application corresponding to each OS and platform using a meta store according to an embodiment of the present invention and registering the application in an external open market.

The overall system includes a metastore 100, an external open build system 110, and a plurality of external open markets 120. The meta store 100 can communicate with an external open build system 110 and a plurality of open markets 120 using a communication network. The communication network according to an exemplary embodiment of the present invention may be configured as a wired or wireless communication mode and may include various communication networks such as a wide area network (WAN), a local area network (LAN), a mobile communication network, and a satellite communication network. More specifically, the communication network according to the present invention can be implemented by a technique such as IEEE 802.11, Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Global System for Mobile communications (GSM), Long Term Evolution And may include a wireless communication network to be implemented. However, the communication network may include, at least in part, a known wire / wireless data communication network, a known telephone network, or a known wire / wireless television communication network, without being limited thereto.

The external open build system 110 according to an exemplary embodiment of the present invention stores and manages APIs (application programming interfaces) suitable for a plurality of target operating systems (OS) and platforms, If so, it performs the function of providing a predetermined API. The meta store 100 calls the external open build system 110 to build a static resource and metadata and generate a target executable file.

Next, the external open market 120 according to an embodiment of the present invention develops and discloses various services such as a game based on a platform and a service infrastructure, which are open to outside developers, Space, for example, an app store, openappmkt, or oleMarket. The target executable file generated by the meta store 100 can be interlocked with the external open market 120. [

The meta store 100 according to an embodiment of the present invention includes a build target meta store 10, a meta source repository 20, a build meta database 30, an open market meta store 40, And the functions of the respective components included in the meta store 100 may be controlled by the management server of the meta store 100. [ Hereinafter, the meta store 100 will be described in detail with reference to FIG.

2 is a diagram showing a configuration of a management server of the meta store 100 according to an embodiment of the present invention. 2, the management server of the meta store 100 includes a static resource and metadata registration unit 210, a target execution file generation unit 220, a store metadata generation unit 230, a linkage processing unit 240, And a control unit 250. According to an embodiment of the present invention, the static resource and metadata registration unit 210, the target execution file generation unit 220, the store metadata generation unit 230, the interworking processing unit 240, At least some of which communicate with the outside. Such program modules may be included in the server in the form of an operating system, an application program module, and other program modules, and may be physically stored on various known memory devices. Such program modules may also be stored in a remote storage device capable of communicating with the server. These program modules include, but are not limited to, routines, subroutines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types as described below in accordance with the present invention.

The static resource and metadata registration unit 210 registers a static resource and metadata for creating a predetermined application using an open device API and an external HTML5 authoring tool. At this time, the static resource may be at least one of HTML (Hypertext Markup Language), Image, or Js, and the metadata may be at least one of XML (Extensible Markup Language) and Json (JavaScript Standard Object Notation). At this time, the external HTML5 authoring tool can automatically provide a restful API that can be used by a predetermined application developer to process information about the metadata to be registered.

Next, the target executable file generating unit 220 generates a target executable file using the static resources and the metadata and the static resources registered in the meta store 100 by the metadata registering unit 210. [

First, when a target OS and platform to be built among a plurality of OSs and platforms are set, the target execution file generating unit 220 generates i) a static resource and metadata and ii) a build target And checks the required consistency between the parameter information received from the meta storage (10). At this time, since the parameter information required for each platform is different for each platform, parameter information corresponding to the target OS and platform set from the build target meta-repository 10 can be provided. The target executable file generation unit 220 can check the required consistency by checking whether an error has occurred between i) static resources and metadata and ii) parameter information received from the build target meta-repository 10. [ In addition, in checking the required consistency when the meta data is the metadata of the combined application, it is possible to check only the essential consistency between i) static resources and metadata and ii) parameter information received from the build target meta storage 10 Checking the consistency through the association between the combined application and the seeded application that is a part of the combined application, or checking the information such as the seed application, the seed application number, the combination application number, and the version You can do more.

Here, the parameter information necessary for the build, that is, the parameter information received from the build target meta-repository 10 used in checking the required consistency, includes an app title, an app creation method, an app build environment platform, Information about a version, a description, keys to be used in each platform, an application package, a debug mode decision, and a download publicity (private) .

Next, the target executable file generation unit 220 calls the external open build system 110 and the API when the required consistency is satisfied. After the target executable file that has been built to be suitable for the external open build system 110 and the build target OS and platform set by the API is generated, the target executable file is returned to the meta source repository 20). ≪ / RTI >

At this time, when the target execution file generation unit 220 acquires the target execution file by setting a target OS and platform other than the target OS and platform set first, the target execution file generation unit 220 acquires the static resource and the metadata from the meta source repository 20 And the target executable file corresponding to the newly set target OS and platform can be returned and stored in the meta-source repository 20 through the above-described process. That is, according to an embodiment of the present invention, a static resource and meta data for creating a predetermined application are stored, and then a target executable file corresponding to the target OS and platform set through the external open build system 110 is returned The executable file according to various OS and platform can be easily managed.

Next, the store metadata generator 230 according to an embodiment of the present invention performs a function of generating store metadata in order to register the target executable file stored in the meta-source repository 20 in the external open market do. At this time, when a market for registering the target executable file is selected from a plurality of external open markets, information corresponding to the external open market to be registered is received from the build meta database unit 30 and the open market meta store 40, And store metadata corresponding to the market to be registered can be generated by matching with each other. At this time, the open market meta-store 40 stores information on a plurality of OSs, platforms, browsers, markets, market registration / meta information properties as well as developer information of a predetermined application, And the generated metadata for the store may be stored in the metadata application database 50. [ In addition, although the metadata for storing the target executable file created on the meta store 100 according to an embodiment of the present invention has been described in the present specification, it is not limited to this, but the metadata for store may be generated according to an embodiment of the present invention In addition to the target executable file generated on the meta store 100, an externally generated executable file may be received and the store metadata may be generated.

Next, when the store metadata is generated from the store metadata generator 230, the interworking processor 240 calls the external open market registration / management API from the external open market 120. [ The metadata for store and the target executable file can be processed to be linked with the external open market 120 by using the external open market registration / management API. Accordingly, a predetermined application can be registered in a plurality of external open markets 120 as well as the metastore 100. That is, according to an embodiment of the present invention, a target executable file that is built according to a plurality of OSs and platforms is managed, an application is registered and managed directly on the meta store 100, A series of functions for registering an application in various external open markets 120 through an interlocking process can be processed using one system.

The control unit 250 includes a static resource and metadata registration unit 210, a target execution file generation unit 220, a store metadata generation unit 230, a linkage processing unit 240, And the control unit 250 controls the static resource and metadata registration unit 210, the target execution file generation unit 220, the store metadata generation unit 230, and the interworking unit 240 to perform functions Can be performed. In addition, when a sales record, review, or registered developer information of an application registered in a plurality of external open markets 120 is processed using a predetermined API after a predetermined application is registered in the external open market 120 Can be managed.

The embodiments of the present invention described above can be implemented in the form of program instructions that can be executed through various computer components and recorded on a computer-readable recording medium. The computer-readable recording medium may include program commands, data files, data structures, and the like, alone or in combination. The program instructions recorded on the computer-readable recording medium may be those specially designed and constructed for the present invention or may be those known and used by those skilled in the computer software arts. Examples of computer-readable recording media include magnetic media such as hard disks, floppy disks and magnetic tape, optical recording media such as CD-ROMs and DVDs, magneto-optical media such as floptical disks, media, and hardware devices specifically configured to store and execute program instructions such as ROM, RAM, flash memory, and the like. Examples of program instructions include machine language code such as those generated by a compiler, as well as high-level language code that can be executed by a computer using an interpreter or the like. The hardware device may be configured to operate as one or more software modules for performing the processing according to the present invention, and vice versa.

While the present invention has been particularly shown and described with reference to exemplary embodiments thereof, it is to be understood that the invention is not limited to the disclosed exemplary embodiments, but, on the contrary, Those skilled in the art will appreciate that various modifications, additions and substitutions are possible, without departing from the scope and spirit of the invention as disclosed in the accompanying claims.

Therefore, the spirit of the present invention should not be construed as being limited to the above-described embodiments, and all of the equivalents or equivalents of the claims, as well as the following claims, I will say.

100: Metastore
110: External open build system
120: External open market
210: static resource and metadata register
220: Target Executable File Generation Unit
230: Metadata generation unit for store
240: interlocking processor

Claims (19)

(a) a step of registering, in a meta store, a static resource and metadata for creating a predetermined application using an open device API and an external HTML5 authoring tool;
(b) the meta store management server setting a build target OS and a platform;
(c) The meta store management server refers to the set build target OS and platform information, and compiles the necessary consistency between i) the static resource and meta data, and ii) the parameter information received from the build target meta store Checking;
(d) if the required consistency is satisfied, the meta store management server calls an external open build system and an API to generate a target executable file suitable for the OS and platform set in the step (b), and then return; And
(e) the meta store management server stores and registers the target executable file and the static resource and meta data in a meta source repository;
And managing the meta store. The method according to claim 1,
The step (c)
by checking whether an error has occurred between i) the static resource and meta data, and ii) parameter information received from the build target meta-repository. The method according to claim 1,
If the metadata is metadata of a combination application, the step (c)
Further comprising the step of checking consistency between the combination application and the seed application of the combination application. The method according to claim 1,
When the build target OS and platform are set in addition to the build target OS and platform set in the step (b)
And the step (c) to (e) are performed after acquiring the static resource and the metadata from the meta-source repository. The method according to claim 1,
Wherein the static resource is at least one of HTML, Image, and Js. The method according to claim 1,
Wherein the meta data is at least one of XML and Json. The method according to claim 1,
The parameter information includes at least one of an app title, an app creation method, an app build environment classification, an app version, a description, a key to be used in each platform, an app package, a determination of a debug mode, A meta store management method. The method according to claim 1,
(f) selecting a market for registering the target executable file among a plurality of open markets, and then matching necessary information from the build meta database and an open market meta store to check conditions for registering in the market to be registered, Further comprising the step of generating metadata for a store corresponding to a desired market. 9. The method of claim 8,
The open metadata registration / management API is called, and the store metadata and the target executable file generated from the step (f) are linked with the open market to be registered. A static resource and metadata registering unit for registering static resources and metadata for creating a predetermined application in the meta store using an open device API and an external HTML5 authoring tool; And
When the build target OS and the platform are set, it checks the required consistency between i) the static resource and the metadata, and ii) the parameter information transferred from the build target meta-repository, with reference to the set build target OS and platform information , An external open build system and an API are called to return the target executable file to the meta source repository together with the static resource and the meta data when the target executable file is generated so as to be suitable for the set build target OS and platform A target executable file generation unit for registering the target executable file;
And a meta store management server. 11. The method of claim 10,
Wherein the target executable file generating unit comprises:
wherein the essential metrics are checked by checking whether an error has occurred between i) the static resource and meta data, and ii) parameter information received from the build target meta-repository. 11. The method of claim 10,
If the meta data is metadata of a combination application,
And checks the consistency between the combination application and the seed application of the combination application. 11. The method of claim 10,
Wherein the target execution file generation unit acquires the static resource and the metadata from the meta-source repository when a different build target OS and platform are set in addition to the set build target OS and platform. 11. The method of claim 10,
Wherein the static resource is at least one of HTML, Image, and Js. 11. The method of claim 10,
Wherein the meta data is at least one of XML and Json. 11. The method of claim 10,
The parameter information includes at least one of an app title, an app creation method, an app build environment classification, an app version, a description, a key to be used in each platform, an app package, a determination of a debug mode, Meta store management server. 11. The method of claim 10,
If a market for registering the target executable file is selected from among a plurality of open markets, a necessary information is matched from a build meta database and an open market meta store to check a condition for registering in the market to be registered, Store metadata corresponding to the meta-store management server and the meta-store management server. 18. The method of claim 17,
Further comprising an interworking processor for invoking the external open market registration / management API to interoperate with the open market to register the meta data for store and the target executable file. A computer program for executing the method according to any one of claims 1 to 9.

Images