JP2020144580A - Program distribution device and program distribution method - Google Patents

Abstract

To provide a program distribution device and a program distribution method, capable of providing an identical program for terminals having varied execution environments, without deteriorating functionality and performance of the terminals.SOLUTION: A program distribution server (11) comprises: a source code acquisition section (102) for, from a program management server (14) for managing source code using varied programming languages against one program, based on language-in-use information of a terminal (13), identifying a programming language-in-use thereof, and acquiring source code using the programming language-in-use; a code conversion section (103) for, when the programming language-in-use is a compile language, converting the source code into an executable formatted file that is executable in execution environments; and a distribution section (104) for transmitting the source code if the programming language-in-use is a script language, or the executable formatted file if the programming language-in-use is the compile language, to the terminal.SELECTED DRAWING: Figure 2

Description

The present invention relates to a program distribution device and a program distribution method.

Conventionally, a system for providing an application program having the same code to terminals having different platform types is known (see Patent Document 1 and the like).

In this system, the difference in the platform of each terminal is absorbed by the virtual machine layer.

Japanese Unexamined Patent Publication No. 2001-51857

However, the execution of the program on the virtual machine imposes a load on the interpretation of the intermediate language code, which causes a decrease in execution speed and a decrease in I / O access.

The present invention has been made in view of the above points, and an object of the present invention is to provide a program distribution device and a program distribution method capable of providing the same program to terminals having different execution environments without deteriorating the functions and performance of the terminals. Let it be one.

One aspect of the program distribution device according to the present invention can be executed in the execution environment of the terminal based on the language information of the terminal from the management unit that manages the source code using different programming languages for one program. A source code acquisition unit that specifies the programming language to be used and acquires the source code using the programming language from the management unit, and when the programming language used is a compilation language, executes the source code in the execution environment. A conversion unit that converts into a possible executable format file, the source code if the programming language used is a script language, the executable format file if the programming language used is the compilation language, and the terminal. It is characterized by having a transmission unit for transmitting to.

One aspect of the program distribution method according to the present invention is to specify a programming language to be used that can be executed in the execution environment of the terminal based on the language information of the terminal, and source code using a different programming language for one program. The process of acquiring the source code using the programming language used from the management unit that manages the above, and converting the source code into an executable file that can be executed in the execution environment when the programming language used is a compilation language. If the programming language used is a script language, the source code is transmitted to the terminal, and if the programming language used is the compilation language, the executable file is transmitted to the terminal. It is characterized by that.

According to the present invention, it is possible to provide a program distribution device and a program distribution method capable of providing the same program to terminals having different execution environments without deteriorating the functions and performance of the terminals.

It is an overall block diagram which shows the program distribution system which concerns on 1st Embodiment. It is a functional block diagram which shows the program distribution server which concerns on 1st Embodiment. It is a functional block diagram which shows the terminal which concerns on 1st Embodiment. It is explanatory drawing which shows the architecture information of the terminal which concerns on 1st Embodiment. It is a flowchart which shows each process performed by the program distribution server which concerns on 1st Embodiment. It is a flowchart which shows each process of the code conversion process in the program distribution server which concerns on 1st Embodiment. It is a sequence diagram which shows the data transaction between the program distribution server and a terminal which concerns on 1st Embodiment. It is a block diagram which shows the hardware configuration of the computer apparatus for realizing the server which concerns on 1st Embodiment. It is a functional block diagram which shows the program distribution server which concerns on 2nd Embodiment. It is a flowchart which shows each process of the application verification process performed by the program distribution server which concerns on 2nd Embodiment. It is a flowchart which shows each process of the verification environment construction process in the program distribution server which concerns on 2nd Embodiment. It is a schematic diagram which shows the relationship between the target application and related application in 2nd Embodiment. It is a flowchart which shows each process of the verification process in the program distribution server which concerns on 2nd Embodiment. It is a schematic diagram which shows the normality and abnormality in the connection between the target application and the related application in the 2nd Embodiment.

Hereinafter, the program distribution device and the program distribution method according to the present embodiment will be described with reference to the drawings.

<Overview>
There are various execution environments (platforms) in which programs are executed on terminals. One of them is the programming language used in the execution environment (hereinafter referred to as the programming language used).

High-level languages among programming languages are roughly classified into "compiler languages" and "script languages" according to their conversion formats. A "compiler language" is a programming language in which source code is compiled in advance in a format that can be executed on an execution environment, and is, for example, C, C ++, or Java (registered trademark). A "script language" is a programming language that executes while interpreting source code on an execution environment, and is, for example, Python, Perl, PHP, Ruby, and Javascript (registered trademark).

Among the compiler languages, C, C ++, etc. (hereinafter, referred to as "C language, etc.") convert the source code into an executable file (executable file, also simply referred to as "executable format") in advance. More specifically, the source code is compiled into an object file described in machine language or the like, the object file and the library are linked, and an executable file is generated.

Such C language and the like have advantages that the execution speed on the terminal is high and the load is small. However, compilation and linking depends on architecture such as the terminal processor (CPU) and operating system (OS).

In addition, among compiler languages, Java and the like are different from C, C ++ and the like in that they are executed on a virtual machine. In Java etc., the source code is compiled to generate the intermediate language code. The intermediate language file is interpreted and executed by the virtual machine running on the terminal.

There are two types of virtual machines: an interpreter type that executes while sequentially analyzing the intermediate language code, and a compiler type that compiles and executes the intermediate language code into a machine language when it is read, and both are used in combination. There is also.

This type of high-level language has the advantage that the virtual machine absorbs the difference in the architecture of the terminals, so that the intermediate language code can be shared between terminals with different execution environments. However, it is necessary to execute the virtual machine on the terminal, and the execution of the program on the virtual machine imposes a load on the interpretation of the intermediate language code, which causes a decrease in execution speed and a decrease in I / O access.

On the other hand, since the script language is executed while being sequentially interpreted by the interpreter executed on the terminal, it is not necessary to convert the source code to another format in advance. In addition, since the interpreter absorbs the difference in the architecture of the terminals, there is an advantage that the source code can be shared between terminals having different execution environments. However, the execution speed is slow because the interpreter executes the source code while interpreting it sequentially.

High-level languages such as those mentioned above have advantages and disadvantages depending on their type. Conventionally, many languages that use a compiler and a linker for prior conversion, such as C language, which has a high execution speed, have been used. However, as the speed of CPUs has increased, languages using script languages, interpreters such as Java, or virtual machines have come to be adopted. The reason is that scripting languages, Java, etc. can add interpreters or virtual machines and add and execute programs by distribution via the network even if there are no interpreters and virtual machines in the execution environment of the terminal. Can be mentioned.

Against this background, it is desired that a program distribution system that distributes a program in response to a request from a terminal via a communication network such as the Internet can provide the same program to terminals having different execution environments. However, there is no known one that can provide the same program to terminals having different execution environments without deteriorating the functions and performance of the terminals.

Further, in the program distribution system, since the execution environment differs between the terminal and the server, there is also a problem that the application must be distributed to the terminal and then verified again.

Therefore, as a result of diligent studies to solve the above problems, the present inventors prepare source codes using different programming languages for one program, and execute the terminal based on the language information of the terminal. By specifying the programming language that can be executed in the environment and sending the program to the terminal in a format that can be executed in the execution environment of the terminal according to the programming language used, it contributes to not degrading the functions and performance of the terminal. I found that and completed the present invention.

That is, the program distribution device according to the present embodiment can be executed in the execution environment of the terminal from the management unit that manages the source code using different programming languages for one program based on the language information of the terminal. A source code acquisition unit that specifies a programming language to be used and acquires the source code using the programming language from the management unit, and when the programming language used is a compilation language, the source code is obtained in the execution environment. The conversion unit that converts to an executable executable format file, the source code if the programming language used is a script language, and the executable format file if the programming language used is the compilation language. It is characterized by including a transmission unit for transmitting to a terminal.

That is, in the program distribution method according to the present embodiment, the programming language used that can be executed in the execution environment of the terminal is specified based on the language information used by the terminal, and a source using a different programming language is used for one program. The process of acquiring the source code using the programming language used from the management unit that manages the code, and when the programming language used is a compilation language, the source code is converted into an executable file that can be executed in the execution environment. It includes a step of converting and a step of transmitting the source code when the programming language used is a script language, and the executable format file when the programming language used is the compilation language to the terminal. It is characterized by doing.

In addition, as a result of further studies, the present inventors have constructed a verification environment equivalent to the execution environment of the terminal based on the execution environment information of the terminal, and created the source code or the executable file on the verification environment. By executing and verifying the program, we came up with the idea of distributing the program after verifying it in the same verification environment as the execution environment before distribution.

Hereinafter, the program distribution device and the program distribution method according to the present embodiment will be described in detail with reference to FIGS. 1 to 14. In the following description, an application program will be taken as an example of the program of the present invention, but the program is not particularly limited to this and may be a system program.

<First Embodiment>
(system)
FIG. 1 is an overall configuration diagram showing a program distribution system according to the first embodiment. The program distribution system 1 shown in FIG. 1 is composed of a program distribution server 11, a network 12, and a plurality of terminals 13a to 13n.

The program distribution server 11 is an information processing device that distributes an application program to terminals 13a to 13n via a network 12.

The terminals 13a to 13n are information processing devices that execute application programs distributed from the program distribution server 11. The terminals 13a to 13n may be, for example, a mobile terminal (mobile communication terminal) such as a mobile phone, a smartphone, or a tablet terminal, or a fixed communication terminal such as a personal computer (PC: Personal Computer).

The network 12 includes various networks such as the Internet, a mobile network, a LAN (Local Area Network), and a WAN (Wide Area Network). The network may be composed of wireless, wired, or a combination thereof. For example, as the wireless communication method, Bluetooth (registered trademark), wireless LAN (for example, conforming to the IEEE802.11 standard), LTE (Long Term Evolution), or other wireless communication method can be used.

(Program distribution server)
FIG. 2 is a functional block diagram showing the program distribution server 11 according to the first embodiment. As shown in FIG. 2, the program distribution server 11, which is an example of the program distribution device of the present invention, is composed of an architecture information acquisition unit 101, a source code acquisition unit 102, a code conversion unit 103, and a distribution unit 104. ..

The architecture information acquisition unit 101 acquires architecture information from a terminal 13 (representing terminals 13a to 13n shown in FIG. 1) via a network 12 (see FIG. 1) (hereinafter, “architecty”). It is configured to perform (described as "Kuqa information acquisition process"). The architecture information is information on the design concept and structure of the computer constituting the terminal 13. Details of the architecture information will be described later.

The source code acquisition unit 102 acquires the source code from the program management server 14 via the network 12.

The program management server 14 is an example of the management unit of the present invention, and stores source code using different programming languages for one application program. More specifically, the program management server 14 includes a database in which a plurality of records including the following items are stored in the storage 1003 (see FIG. 8) as the source code.
・ Source code ID
・ Application program ID
・ Development language ID
-Source code files-Information about compatible interpreters or virtual machines

The source code ID is identification information uniquely assigned to the source code. The application program ID is identification information uniquely given to the application program. The development language ID is identification information uniquely assigned to the programming language used in the source code. These identification information may be a serial number, a code consisting of a combination of alphanumeric characters, or a character string, and is not particularly limited.

A source code file is the body of source code for an application program. Instead of the source code file, the path indicating the storage location of the source code file may be stored.

Information about a compatible interpreter or virtual machine is used when the source code file uses a scripting language or a compiler language that uses the virtual machine, for example, the name and version of the interpreter, or the name of the virtual machine. And the version, but are not particularly limited.

In response to a request from the program distribution server 11, the program management server 14 can refer to a database, search for a source code file, and transmit it to the program distribution server 11 using the application program ID and the development language ID as keys. In addition, if the source code file is searched and there is no corresponding one, a notification to that effect can be sent.

The code conversion unit 103 is an example of a conversion unit of the present invention, and is configured to perform a process of converting a source code file into an executable file (hereinafter, referred to as “code conversion process”). The details of the code conversion process will be described later.

The distribution unit 104 is an example of a transmission unit of the present invention, and is a process of transmitting an executable file or a source code file to the terminal 13 via the network 12 (see FIG. 2) (hereinafter, referred to as “distribution process”). It is configured to do).

(Terminal)
FIG. 3 is a functional block diagram showing the terminal 13 according to the first embodiment. The terminals 13A, 13B, and 13C shown in FIGS. 3A to 3C are different in that the execution environment is different. First, the configuration common to the terminals 13A, 13B, and 13C will be described with reference to FIG. 3A. In FIGS. 3B and 3C, the same reference numerals are given to the same configurations as those of the terminal 13A shown in FIG. 3A, and the description thereof will be omitted.

As shown in FIG. 3A, the terminal 13A includes hardware (HW) 21 and an operating system (OS) 22 as an execution environment for executing an application program. Further, the architecture information 23 is stored in the storage 1003 (see FIG. 8).

The terminal 13A shown in FIG. 3A has an execution environment in which the programming language is C language. The application program (hereinafter, referred to as “C application”) 24 in which the C language is used can be executed on the OS 22.

The terminal 13B shown in FIG. 3B has an execution environment in which the programming language used is Python. The application program (hereinafter, referred to as “Python application”) 25 using the Python language can be executed by the interpreter (hereinafter, referred to as “Python interpreter”) 26 executed by the OS 22.

The terminal 13C shown in FIG. 3C has an execution environment in which the programming language used is Java. The application program (hereinafter, referred to as “Java application”) 27 using the Java language can be executed by the virtual machine (hereinafter, referred to as “Java VM”) 28 executed by the OS 22.

(Architecture information)
FIG. 4 is an explanatory diagram showing the architecture information of the terminals 13A, 13B, and 13C according to the first embodiment.

As shown in FIG. 4, the architecture information includes installation application information and engineering information. The installed application information is an example of the execution environment information of the present invention, and is information about an application program installed in the terminals 13A, 13B, and 13C. For example, processing content information (for example, measurement processing, calculation) performed by the application program. Processing, input processing, output processing), including application program version information.

In addition, the engineering information includes a development language which is an example of the language information used in the present invention, an interpreter information (name and version) which is an example of the execution environment information of the present invention, a compilation condition, and a link condition.

(Program distribution method)
Hereinafter, the program distribution method in the program distribution system 1 having the above-described configuration will be described. FIG. 5 is a flowchart showing each process performed by the program distribution server 11 according to the first embodiment.

As shown in FIG. 5, the architecture information acquisition unit 101 (see FIG. 2) transmits a connection request to the terminal 13 via the network 12 (S1).

Next, the architecture information acquisition unit 101 determines whether or not the architecture information can be received from the terminal 13 (S2). If the determination is No in S2, the process ends as an abnormality (S3). On the other hand, when the determination is Yes in S2, the source code acquisition unit 102 (see FIG. 2) acquires the source code file from the program management server 14 (S4).

Specifically, the source code acquisition unit 102 transmits an acquisition request to the program management server 14. The acquisition request includes the development language ID corresponding to the development language included in the architecture information (see FIG. 4) transmitted from the terminal 13 in response to the connection request of S1, and the application program corresponding to the application program to be distributed. Includes ID. The program management server (see FIG. 2) searches the database using the development language ID and the application program ID included in the acquisition request as keys, and transmits the searched source code file to the source code acquisition unit 102.

The source code acquisition unit 102 can determine whether or not the source code file needs to be acquired based on the installation application information included in the architecture information. Specifically, it can be determined that the source code file is acquired when there is an application program that is not installed in the terminal 13 or when the version of the installed application program is old. Based on such a determination, it is possible to determine whether or not the application program needs to be distributed.

Next, the code conversion unit 103 (see FIG. 2) executes a code conversion process for converting the acquired source code file into an appropriate format as needed (S5).

(Code conversion process)
FIG. 6 is a flowchart showing each step of the code conversion process in the program distribution server 11 according to the first embodiment. As shown in FIG. 6, first, in the code conversion unit 103 (see FIG. 2), the programming language used in the source code file (hereinafter, referred to as “programming language used”) is determined based on the development language ID. , C language or not (S10).

If the determination in S10 is Yes, the code conversion unit 103 performs compile / link processing (S11). Details of compilation / link processing will be described later. Next, the code conversion unit 103 determines whether or not the compilation / link processing can be completed normally (S12). If the determination is No in S12, the process ends as an abnormality (S13). If the determination is Yes in S12, a package for distribution is created from the executable file generated by the compile / link process (S14). After that, the code conversion process ends normally (S15).

On the other hand, when the determination in S10 is No, the code conversion unit 103 determines whether or not the programming language used is Python based on the development language ID (S16).

If the determination in S16 is Yes, the code conversion unit 103 performs a version check process of the Chord interpreter (S17). The details of the version check process will be described later. Next, the code conversion unit 103 determines whether or not the version check process can be completed normally (S18). If the determination is No in S18, the process ends as an abnormality (S19). If the determination is Yes in S18, a package is created from the source code file (S14). After that, the code conversion process ends normally (S15).

On the other hand, when the determination in S16 is No, the code conversion unit 103 determines whether or not the programming language used is Java based on the development language ID (S20).

If the determination in S20 is Yes, the code conversion unit 103 executes the bytecode conversion process (S21). The details of the bytecode conversion process will be described later. Next, the code conversion unit 103 determines whether or not the byte code conversion process can be normally completed (S22). If the determination is No in S22, the process ends as an abnormality (S23). If the determination is Yes in S22, a package is created from the generated bytecode file (S14). After that, the code conversion process ends normally (S15). On the other hand, if the determination in S20 is No, the code conversion unit 103 ends as an abnormality (S23).

Returning to FIG. 5, when the code conversion process (S5) is completed normally, the distribution unit 104 distributes the package to the terminal 13 (see FIG. 2) (S6). Next, the distribution unit 104 receives the result (OK or NG) of activating the distributed application program from the terminal 13 that has received the package, and determines whether or not the application startup is successful (S7). If the determination in S7 is Yes, the distribution unit 104 ends the process normally (S8). If the determination in S7 is No, the distribution unit 104 ends as an abnormality (S9).

(C language compilation / link processing)
The details of the compile / link process (S11) shown in FIG. 6 will be described. The compilation / link processing (S11) is performed by the compiler and linker included in the code conversion unit 103 (see FIG. 2). Compilers and linkers will be easily understood by those skilled in the art by their names.

Compilation by the compiler is performed according to the compilation conditions included in the engineering information of the architecture information. The compilation conditions are, for example, a processor name, a compiler software name, a version, a manufacturer name, and compilation options, but are not particularly limited.

In addition, the link by the linker is performed according to the link condition included in the engineering information of the architecture information. The link conditions are, for example, the linker software name, version, manufacturer name, and link option, but are not particularly limited.

By using the compile condition and the link condition in the engineering information of the architecture information acquired from the terminal 13A (see FIG. 3A) in S11, the executable format binary code file (executable format file) suitable for the terminal 13A is used. ) Can be generated.

More specifically, refer to the compilation conditions, prepare a compiler with the same compiler software name, version, and manufacturer name, specify the processor name and compilation options, and execute compilation.

For the link, refer to the link condition, prepare a linker with the same linker software name and version, specify the link option, and execute the link. Then, in S14 of FIG. 6, the binary-coded executable file after compilation and linking is packaged for distribution.

(Python version check process)
Programs (source code files) that run on the Python language interpreter have additional and abolished libraries and functions that can be used depending on the version of the interpreter, so the programs cannot be run on the terminal unless they are matched. Therefore, it is preferable to confirm whether or not the program written in the Python language in the database of the program management server 14 is a version that operates on the interpreter 26 implemented in the terminal 13B (see FIG. 3B).

Therefore, in the Python version check process (S17), does the interpreter name and interpreter version in the engineering information (see FIG. 4) match those of the source code file acquired by the source code acquisition unit 102 from the program management server 14. Check if it is not.

In the present embodiment, if they do not match (No in the determination in S18), the process ends as an abnormality (S19), but the present invention is not limited to this. For example, an interpreter matching the source code file acquired by the source code acquisition unit 102 may be packaged together with the source code file and distributed to the terminal 13B.

(Java language bytecode conversion process)
Programs (bytecode files or intermediate language files) that use bytecode that runs on the Java language virtual machine (Java VM) match because the libraries and functions that can be used are added or abolished depending on the virtual machine version. If you do not, you will not be able to run the program on the terminal. Therefore, it is preferable to confirm whether or not the source code file described in the Java language in the database of the program management server 14 is a version that operates on the Java VM28 implemented in the terminal 13C (see FIG. 3C).

Therefore, in the bytecode conversion process (see S21), the virtual machine name and version in the engineering information (see FIG. 4) match those of the source code file acquired by the source code acquisition unit 102 from the program management server 14. Check if it is.

In the present embodiment, if they do not match (No in the determination in S22), the process ends as an abnormality (S23), but the present invention is not limited to this. For example, a virtual machine matching the source code file acquired by the source code acquisition unit 102 may be packaged together with the source code file and distributed to the terminal 13C.

When the version check is completed, the code conversion unit 103 compiles the source code file using the Java language and generates bytecode.

(Data transaction between program distribution server and terminal)
FIG. 7 is a sequence diagram showing a data transaction between the program distribution server 11 and the terminal 13 according to the first embodiment. As shown in FIG. 7, first, the architecture information acquisition unit 101 of the program distribution server 11 (see FIG. 2) transmits a “connection request” to the terminal 13 (S101). When the terminal 13 makes it possible to accept the application program, the terminal 13 returns a response "OK" to the program distribution server 11 (S102). Here, "acceptable" means a state in which communication is used only for program distribution and no other communication is performed. For example, the terminal 13 includes a state in which an application unrelated to program distribution is not communicating.

Next, the terminal 13 transmits the "architecture information" stored in the storage unit (not shown) to the program distribution server 11 (S103). On the other hand, the architecture information acquisition unit 101 of the program distribution server 11 transmits a response “OK” to the terminal 13 when the reception of the architecture information is completed (S104). Further, if the program distribution server 11 cannot receive the architecture information or receives an unknown response, the program distribution server 11 terminates abnormally with a timeout.

Next, the distribution unit 104 of the program distribution server 11 distributes the package to the terminal 13 (S105). When the terminal 13 receives the package and completes the rewriting of the program, the terminal 13 returns a response "OK" (S106). Rewriting the program means that the terminal 13 that has received the program reads the package, checks whether it has been correctly received by the check code, and records the new application in the storage unit (for example, ROM) of the device.

Next, the distribution unit 104 of the program distribution server 11 transmits "application activation" to the terminal 13 in order to activate the distributed application program (S107). If the terminal 13 normally starts the application program, the terminal 13 returns a response "OK" (S108).

The data transaction between the program distribution server 11 and the terminal 13 described with reference to FIG. 7 is only an example, and the order and the like can be changed as appropriate.

(Server configuration)
Next, with reference to FIG. 8, the hardware configuration of the computer device for realizing a server such as the program distribution server 11 (see FIG. 2) and the program management server 14 (hereinafter, simply referred to as “server”). Will be described. FIG. 8 is a block diagram showing a hardware configuration of a computer device for realizing the server according to the first embodiment.

FIG. 2 used in the description of the first embodiment shows a block of functional units. These functional blocks (components) are realized by any combination of hardware and / or software. Further, the means for realizing each functional block is not particularly limited. That is, each functional block may be realized by one physically connected device, or may be realized by connecting two or more physically separated devices by wire or wirelessly and these plurality of devices. Good.

For example, the server in the first embodiment may function as a computer that implements each step of the program distribution method of the present invention. The server 1000 shown in FIG. 8 may be physically configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1008, and the like.

In the following description, the word "device" can be read as a circuit, a device, a unit, or the like. The hardware configuration of the server 1000 or the like may be configured to include one or more of the devices shown in the figure, or may be configured not to include some of the devices.

For example, although only one processor 1001 is shown, there may be multiple processors. Further, the processing may be executed by one processor, or the processing may be executed simultaneously, sequentially, or by other methods on one or more processors.

For each function of the program distribution server 11, the program management server 14, and the like, the processor 1001 performs calculations by loading predetermined software (programs) on hardware such as the processor 1001 and the memory 1002, and the communication device 1004 communicates. It is realized by controlling the reading and / or writing of data in the memory 1002 and the storage 1003.

Processor 1001 operates, for example, an operating system to control the entire computer. The processor 1001 may be composed of a central processing unit (CPU) including an interface with a peripheral device, a control device, an arithmetic unit, a register, and the like. Each unit such as the above-mentioned architecture information acquisition unit 101, source code acquisition unit 102, code conversion unit 103, and distribution unit 104 may be realized by the processor 1001. Processor 1001 may be mounted on one or more chips.

Further, the processor 1001 reads a program (program code), a software module, and data from the storage 1003 and / or the communication device 1004 into the memory 1002, and executes various processes according to these. As the program, a program that causes a computer to execute at least a part of the operations described in the above-described embodiment is used. For example, the architecture information acquisition unit 101, the source code acquisition unit 102, the code conversion unit 103, and the distribution unit 104 may be stored in the memory 1002 and realized by a control program that operates in the processor 1001, and other functional blocks. May be realized in the same manner.

The memory 1002 is a computer-readable recording medium, such as at least a ROM (Read Only Memory), an EPROM (Erasable Programmable ROM), an EEPROM (Electrically EPROM), a RAM (Random Access Memory), or any other suitable storage medium. It may be composed of one. The memory 1002 may be referred to as a register, a cache, a main memory (main storage device), or the like. The memory 1002 can store a program (program code), a software module, or the like that can be executed to implement the program distribution method according to the embodiment of the present invention.

The storage 1003 is a computer-readable recording medium, for example, a flexible disk, a floppy (registered trademark) disk, a magneto-optical disk (for example, a compact disc (CD-ROM (Compact Disc ROM)), etc.), a digital versatile disk, and the like. At least one of Blu-ray® disks, removable disks, hard disk drives, smart cards, flash memory devices (eg cards, sticks, key drives), magnetic stripes, databases, servers, and other suitable storage media. It may be composed of. The storage 1003 may be referred to as an auxiliary storage device.

The communication device 1004 is hardware (transmission / reception device) for performing communication between computers via a wired and / or wireless network, and is also referred to as, for example, a network device, a network controller, a network card, a communication module, or the like.

The input device 1005 is an input device (for example, a keyboard, a mouse, etc.) that receives an input from the outside. The output device 1006 is an output device (for example, a display, a speaker, etc.) that outputs to the outside. The input device 1005 and the output device 1006 may have an integrated configuration (for example, a touch panel). The server 1000 may not include the input device 1005 and the output device 1006.

Further, each device such as the processor 1001 and the memory 1002 is connected by a bus 1008 for communicating information. Bus 1008 may be composed of a single bus, or may be composed of different buses between devices.

Further, the server 1000 is configured to include hardware such as a microprocessor, a digital signal processor (DSP: Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), and an FPGA (Field Programmable Gate Array). The hardware may implement some or all of each functional block. For example, processor 1001 may be implemented on at least one of these hardware.

The terminal 13 (see FIG. 2) can also be realized by a computer device having the hardware configuration as described above.

As described above, according to the first embodiment, source code files using different programming languages are prepared in the program management server 14 (see FIG. 2) for one application program, and the program distribution server 11 Acquires a source code file based on the development language (language information used) included in the architecture information acquired from the terminal 13, converts it into an executable file so as to match the development language, or sources. The code file is delivered to the terminal 13 as it is. As a result, the same program can be provided to terminals having different execution environments without deteriorating the functions and performance of the terminal 13.

<Second embodiment>
The program distribution system including the verification process according to the second embodiment will be described with reference to FIGS. 9 to 14. In the following description, the differences from the first embodiment will be described, and the same points will be omitted. Further, the reference numerals used in FIGS. 1 to 8 are designated by the same reference numerals for the same configuration or process, and the description thereof will be omitted.

In the program distribution system 1 according to the first embodiment, as shown in FIG. 7, after the application program is distributed from the program distribution server 11 to the terminal 13 (see FIG. 2), the application program is started on the terminal 13 and the application program is started. The application program is verified by receiving the response "OK" indicating that the application was successful. Therefore, if there is an event in which the application program cannot be started due to interference with other application programs that have been installed and are running in the verification of the application program on the terminal 13, the program distribution server 11 side. Can be detected as an abnormal termination. However, verification of the application program on the terminal 13 may cause inconveniences such as abnormally stopping the terminal 13 or requiring a restart.

Therefore, in the second embodiment, before distribution of the application program, an evaluation environment equivalent to the execution environment of the terminal 13 is constructed on the program distribution server, and the application program is verified.

<Application verification process>
FIG. 9 is a functional block diagram showing a program distribution server according to the second embodiment. As shown in FIG. 9, the program distribution server 201 further includes a verification environment construction unit 202 and a verification unit 203.

FIG. 10 is a flowchart showing each step of the application verification process performed by the program distribution server 201 according to the second embodiment. The program distribution server 201 (see FIG. 9) performs the same processing as the program distribution server 11 according to the first embodiment described with reference to FIGS. 5 to 7. However, before delivering the package (see S6 in FIG. 5), verification under the application program verification environment (hereinafter referred to as "application verification process") is performed based on the architecture information of the terminal 13. It differs in that.

(Verification environment construction process)
As shown in FIG. 10, first, the verification environment construction unit 202 executes the verification environment construction process (S61). In the verification environment construction process (S61), a verification environment, which is an execution environment equivalent to that of the terminal 13 (see FIG. 9), is virtually constructed on the program distribution server 201 based on the architecture information.

FIG. 11 is a flowchart showing each process of the verification environment construction process in the program distribution server 201 according to the second embodiment. As shown in FIG. 11, among the terminals 13 (see FIG. 9), the architecture information acquired in advance for the evaluation target terminal (hereinafter referred to as the target terminal) is analyzed (S81), and the target. It is determined whether or not a verification environment equivalent to the terminal can be constructed (S82).

The determination method of S82 is not particularly limited, but it can be determined that the environment indicated in the architecture information of the target terminal cannot be constructed, and that it can be constructed if it is not. Specifically, for example, there are cases where recompilation cannot be performed due to the expiration of the license of the compiler, and there are cases where there is a version difference in the development language (example: Java, Python version difference), but the present invention is not particularly limited. ..

If the determination is No in S82, the process ends as abnormal (S83). If the determination is Yes in S82, a verification environment is constructed (S84). Specifically, the verification environment can be constructed as follows.

The construction of the verification environment can be realized by using virtualization technology (container type virtualization technology, etc.) and automation environment by batch processing. CPU architecture (x86, ARM, etc.), OS (Debian, Ubuntu, CentOS, etc.), development language (Java, Python, etc.), etc. stored in the program distribution server 201 based on the architecture information of the target terminal. Acquire an image for building a virtual environment of, and automatically build a verification environment similar to the target terminal based on each image.

After constructing the verification environment, it is determined whether or not the construction has been completed (S85). If the determination in S85 is No, the process ends as abnormal (S86). On the other hand, if the determination in S85 is Yes, the process proceeds to S62 shown in FIG.

In S62, the verification unit 203 determines whether or not the related application (described as “related application” in FIG. 10) can be acquired from the program management server 14.

(Related application)
The related application means, when the application program to be distributed (hereinafter referred to as a target application) is a part of an application group composed of a plurality of applications, other application programs constituting the application group.

FIG. 12 is a schematic diagram showing the relationship between the target application and the related application in the second embodiment. In FIG. 12, the “processing application” is referred to as a “processing application” and the “analysis application” is referred to as an “analysis application”. Specifically, as shown in FIG. 12, it is assumed that there are a "processing application" for processing a certain data (processing data) and an "analysis application" for analyzing the target terminal. Furthermore, it is assumed that the "processing application" and the "analysis application" share a data format. Since the "analysis application" executes the analysis processing of the processing data based on the shared data format, a dependency with the "processing application" occurs. Further, the "machining application" sends the machining data to the "analysis application" and then receives a reception completion response from the "analysis application".

In this way, of the two dependent applications, one is defined as the target application and the other is defined as the related application.

In the determination in S62, for example, the source code file of the related application is searched from the database of the program management server 14 using the installation application information which is an example of the execution environment information of the present invention in the architecture information of the target terminal. , It can be done depending on whether or not the search result is obtained.

If the determination is No in S62, the process ends as abnormal (S63). If the determination is Yes in S62, the source code acquisition unit 102 (see FIG. 9) acquires the source code file of the related application from the program management server 14 (S64).

Next, the code conversion unit 103 (see FIG. 9) performs a code conversion process on the source code file of the related application in the same manner as in the first embodiment (S65). After that, it is determined whether or not the code conversion process is normally completed (S66).

If the determination is No in S66, the process ends as an abnormality (S67). If the determination is Yes in S66, the verification unit 203 (see FIG. 9) deploys the related application to the verification environment (S68). Here, deploying means arranging the related application in a state in which it can be executed on the verification environment.

(Verification process)
Next, the verification unit 203 performs a verification process (S69). FIG. 13 is a flowchart showing each step of the verification process in the program distribution server 201 according to the second embodiment. As shown in FIG. 13, first, the verification unit 203 (see FIG. 9) performs unit verification of the target application (S91).

Specifically, in the unit verification, the compatibility (CPU architecture, OS, development language, etc.) of the target application alone with the terminal to be distributed is confirmed. More specifically, in the same execution environment (CPU architecture, OS, development language, etc.) as the target terminal constructed by the verification environment construction process, the target application is executed and the log analysis of the execution result is performed. If this output log matches the normal value defined in advance in the program distribution server 201, it is determined that the response is normal. In addition, in the case of an abnormality, an error code is output and the cause of nonconformity (CPU architecture, OS, development language, etc.) is determined by comparing it with the error code table defined in the program distribution server 201 before distribution. It is possible to confirm to. As a result, it can be confirmed that the target application to be distributed can be executed in the same environment as the execution environment of the target terminal.

Next, it is determined whether or not the result of the unit verification of the target application is normal (S92). If the determination in S92 is No, it is abnormal, an error is output, and the process ends (S93). If the determination in S92 is Yes, it is normal and the next connection verification (S94) is performed.

(Connection verification)
In connection verification (S94), the target application and the related application are connected, and verification between the applications is performed.

As described above, there is a dependency between the target application and the related application. In the connection verification, if there is an abnormality such as a mismatch in the dependent items, the abnormality is determined.

Specific examples include differences in protocols or settings for connection / communication between applications.

FIG. 14 is a schematic diagram showing normality and abnormality in the connection between the target application and the related application in the second embodiment. A specific example will be described with reference to FIG. 14, where the target application is a “machining application” and the related application is an “analysis application”. When communicating between applications, it is necessary to use the same communication protocol and mutual recognition of communication settings (eg, port number, etc.) between applications. In addition, even if the data format shared by the "processing application" and the "analysis application" is not followed, an abnormality (NG) will occur at the time of verification. As shown in FIG. 14, the determination at the time of connection verification between the "processing application" and the "analysis application" is, for example, a match or mismatch of communication protocols (HTTP and MQTT), and a match or mismatch of data formats (text, JSON). Can be done on the basis.

Next, it is determined whether or not the result of the connection verification is normal (S95). If the determination in S95 is No, it is abnormal, an error output is performed, and the process ends (S96). If the determination in S95 is Yes, it is normal, the verification process is completed, and the process proceeds to S70 in FIG.

In S70, it is determined whether or not the result of the verification process is normal. If the determination in S70 is No, the process ends as an abnormality (S71). If the determination in S70 is Yes, it is normal, the application verification process is terminated, and the package is distributed to the target terminal (S6 in FIG. 5).

In the present embodiment, verification by starting the application program on the target terminal is not necessary, but it may be performed.

As described above, according to the second embodiment, in addition to the same effect of the first embodiment, execution of the target terminal based on the execution environment information (for example, installation application information) of the target terminal. Build a verification environment equivalent to the environment, execute the source code or executable file on the verification environment, and verify the program. As a result, the application program used in the target terminal can be managed, verified, and distributed by the program distribution server 201, and the development and deployment of the application program can be appropriately performed in a short period of time. In addition, since it is possible to distribute an application program suitable for the execution environment of the target terminal after verifying it under the same verification environment as the execution environment up to the binary level before distribution, a high-quality application program is provided. The target terminal can execute the application program without degrading the application execution time and function.

The present invention is not limited to the above embodiment, and can be modified in various ways. In the above embodiment, the size, shape, function, and the like of the components shown in the accompanying drawings are not limited to this, and can be appropriately changed within the range in which the effects of the present invention are exhibited. In addition, it can be appropriately modified and implemented as long as it does not deviate from the scope of the object of the present invention.

For example, in the first and second embodiments, the application program (package) is distributed by the request from the program distribution servers 11 and 201 (see FIGS. 2 and 9), but the request from the terminal 13. May be done by.

Further, in the first and second embodiments, the source code file is managed by the database of the program management server 14, but the program distribution servers 11 and 201 (see FIGS. 2 and 9) use the database, for example. In preparation for the storage 1003 (see FIG. 8), the source code file may be managed in the same manner as the program management server 14. That is, the management unit of the present invention may be provided by the program distribution servers 11, 201 (see FIGS. 2 and 9).

Further, in the second embodiment, the source code acquisition unit (see FIGS. 2 and 9) acquires the source code file and then checks the version of the source code file. However, the source code file is acquired. Before, the information about the matching interpreter or virtual machine may be acquired from the program management server 14 and the version check may be performed.

The present invention has an effect that the same program can be provided to terminals having different execution environments without deteriorating the functions and performance of the terminals, and is suitable for application to, for example, a system for distribution and verification of an application program. ..

1 Program distribution system 11,201 Program distribution server (program distribution device)
12 Network 13 (13a to 13c, 13n, 13A to 13C) Terminal 14 Program management server (Management Department)
23 Architecture Information 26 Interpreter 28 Java VM (Virtual Machine)
101 Architecture Information Acquisition Department 102 Source Code Acquisition Department (Acquisition Department)
103 Code conversion unit (conversion unit)
104 Distribution section (transmitter section)
202 Verification environment construction unit 203 Verification unit 1000 Server 1001 Processor 1002 Memory 1003 Storage 1004 Communication device 1005 Input device 1006 Output device 1008 Bus

Claims (5)

From the management unit that manages the source code using different programming languages for one program, the programming language used that can be executed in the execution environment of the terminal is specified based on the language information used by the terminal, and the programming language used is defined. A source code acquisition unit that acquires the used source code from the management unit, and
When the programming language used is a compilation language, a conversion unit that converts the source code into an executable file that can be executed in the execution environment, and a conversion unit.
When the programming language used is a script language, the source code is transmitted, and when the programming language used is the compilation language, the executable file is transmitted to the terminal.
A program distribution device characterized by comprising. A verification environment construction unit that builds a verification environment equivalent to the execution environment of the terminal based on the execution environment information of the terminal, and
A verification unit that executes the source code or the executable file in the verification environment and verifies the program.
The program distribution device according to claim 1, further comprising. The conversion unit includes a compiler and a linker.
The program distribution device according to claim 1 or 2, wherein a binary code file is generated as the executable file from the source code based on the compilation condition and the link condition of the terminal. The method according to any one of claims 1 to 3, wherein the conversion unit generates an intermediate language file that can be executed by a virtual machine on the terminal as the executable file from the source code. Program distribution device. Based on the language information of the terminal, the programming language that can be executed in the execution environment of the terminal is specified, and the programming language used is used from the management unit that manages the source code using different programming languages for one program. The process of acquiring the source code
When the programming language used is a compilation language, the process of converting the source code into an executable file that can be executed in the execution environment, and
When the programming language used is a script language, the source code is transmitted, and when the programming language used is the compilation language, the executable format file is transmitted to the terminal.
A program distribution method characterized by comprising.

Images