Application publishing method and device

Abstract

The present invention discloses a method and device for application publishing, and relates to the field of computer technology. A specific implementation of the method includes: receiving a user's application publishing request, obtaining a publishing identifier of the application to be published; according to the publishing identifier, obtaining the publishing workflow of the application to be published from a preset publishing workflow library; and publishing the application to be published to a target server according to the publishing workflow. This implementation can automatically publish the application to be published to the target server, realize one-click publishing, and greatly save manpower and time costs.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a method and device for publishing an application. Background Art

[0002] When releasing applications in the prior art, users usually release the applications to be released to the target server. The release process is heavily dependent on the manual operation of the users. The release process is cumbersome and has high manpower and time costs. Summary of the invention

[0003] In view of this, an embodiment of the present invention provides a method and device for application publishing, which can automatically publish the application to be published to the target server, realize one-click publishing, and greatly save manpower and time costs.

[0004] To achieve the above object, according to one aspect of an embodiment of the present invention, a method for publishing an application is provided, comprising:

[0005] Receive the user's application publishing request and obtain the publishing identifier of the application to be published;

[0006] According to the release identifier, obtaining the release workflow of the application to be released from a preset release workflow library;

[0007] The application to be published is published to the target server according to the publishing workflow.

[0008] Optionally, the release identifier includes: an application identifier and a version identifier.

[0009] Optionally, before acquiring the publishing workflow of the to-be-published application from a preset publishing workflow library, the process further includes:

[0010] Obtaining interface parameters of various calling interfaces required for publishing the application to be published;

[0011] The calling interfaces are assembled according to the business logic of the application to be released and the interface parameters of the calling interfaces to obtain the publishing workflow of the application to be released.

[0012] Optionally, obtaining interface parameters of various calling interfaces required for publishing the application to be published includes:

[0013] Obtaining encrypted request information of the target server;

[0014] The target server is logged in according to the encrypted request information to obtain interface parameters of each calling interface required for publishing the application to be published.

[0015] According to a second aspect of an embodiment of the present invention, there is provided a device for publishing an application, including:

[0016] A receiving module receives a user's application publishing request and obtains a publishing identifier of the application to be published;

[0017] An acquisition module, which acquires the publishing workflow of the application to be published from a preset publishing workflow library according to the publishing identifier;

[0018] A publishing module publishes the application to be published to a target server according to the publishing workflow.

[0019] Optionally, the release identifier includes: an application identifier and a version identifier.

[0020] Optionally, the acquisition module is further used to: before acquiring the publishing workflow of the to-be-published application from a preset publishing workflow library,

[0021] Obtaining interface parameters of various calling interfaces required for publishing the application to be published;

[0022] The calling interfaces are assembled according to the business logic of the application to be released and the interface parameters of the calling interfaces to obtain the publishing workflow of the application to be released.

[0023] Optionally, the acquisition module acquires interface parameters of various calling interfaces required for publishing the application to be published, including:

[0024] Obtaining encrypted request information of the target server;

[0025] The target server is logged in according to the encrypted request information to obtain interface parameters of each calling interface required for publishing the application to be published.

[0026] According to a third aspect of an embodiment of the present invention, there is provided an electronic device for publishing an application, including:

[0027] one or more processors;

[0028] a storage device for storing one or more programs,

[0029] When the one or more programs are executed by the one or more processors, the one or more processors implement the method provided in the first aspect of the embodiment of the present invention.

[0030] According to a fourth aspect of an embodiment of the present invention, a computer-readable medium is provided, on which a computer program is stored, and when the program is executed by a processor, the method provided by the first aspect of the embodiment of the present invention is implemented.

[0031] An embodiment of the above invention has the following advantages or beneficial effects: a unified publishing platform is used to realize application publishing and a publishing workflow library is pre-set, and there is no need for each user to directly interact with the target server for data. Each application to be published can be automatically published to the target server, realizing one-click publishing, which greatly saves manpower and time costs.

[0032] The further effects of the above-mentioned non-conventional optional manner will be described below in conjunction with the specific implementation manner. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] The accompanying drawings are used to better understand the present invention and do not constitute an improper limitation of the present invention.

[0034] Figure 1 It is a schematic diagram of the main process of the method for publishing an application according to an embodiment of the present invention;

[0035] Figure 2 is a schematic diagram of a method for application publishing in an optional embodiment of the present invention;

[0036] Figure 3 It is a schematic diagram of a method for publishing a formal version application in an optional embodiment of the present invention;

[0037] Figure 4 This is a schematic diagram of the process of releasing the official version application in an optional embodiment of the present invention;

[0038] Figure 5 is a schematic diagram of main modules of an apparatus for publishing an application according to an embodiment of the present invention;

[0039] Figure 6 is an exemplary system architecture diagram to which embodiments of the present invention may be applied;

[0040] Figure 7 It is a schematic diagram of the structure of a computer system of a terminal device or a server suitable for implementing an embodiment of the present invention. DETAILED DESCRIPTION

[0041] The following is a description of exemplary embodiments of the present invention in conjunction with the accompanying drawings, including various details of the embodiments of the present invention to facilitate understanding, which should be considered as merely exemplary. Therefore, it should be recognized by those of ordinary skill in the art that various changes and modifications may be made to the embodiments described herein without departing from the scope and spirit of the present invention. Similarly, for clarity and conciseness, the description of well-known functions and structures is omitted in the following description.

[0042] According to one aspect of an embodiment of the present invention, a method for publishing an application is provided.

[0043] Figure 1is a schematic diagram of the main process of the method for publishing an application according to an embodiment of the present invention, such as Figure 1 As shown, the method for application publishing includes: step S101, step S102 and step S103.

[0044] In step S101, a user's application publishing request is received, and a publishing identifier of the application to be published is obtained.

[0045] The application identifier is the identifier of the application to be released. Each application identifier uniquely corresponds to a release workflow in the preset release workflow library. An application identifier can uniquely correspond to an application to be released, for example, the application identifier of application A is a, and the application identifier of application B is b; of course, an application identifier can also uniquely correspond to only one version of the application to be released, for example, the application identifier of the gray version of application A is a1, and the application identifier of the official version of application A is a2, etc. Optionally, the release identifier includes: application identifier and version identifier, so as to meet the differentiated requirements of the release process of different applications and different versions.

[0046] In step S102, according to the release identifier, the release workflow of the application to be released is obtained from a preset release workflow library.

[0047] The release workflow is a workflow that connects various business process operation nodes related to the release of the application to be released. In the release workflow, each node presets the operation of the next node, so that the operations of various nodes involved in the release of an application can be connected in series, so as to realize the automation and process operation of application release.

[0048] During the application publishing process, multiple interactive operations with the target server are required, and the corresponding calling interface needs to be called during each interaction. In an optional embodiment of the present invention, before obtaining the publishing workflow of the application to be published from the preset publishing workflow library, it also includes: obtaining the interface parameters of each calling interface required to publish the application to be published; assembling the various calling interfaces according to the business logic of the application to be published and the interface parameters of each calling interface to obtain the publishing workflow of the application to be published. The interface parameters may include the interface name, interface address (i.e., Uniform Resource Locator, URL for short), etc.

[0049] When the publishing process for publishing applications in the target server is open and transparent to the outside, the various calling interfaces and their interface parameters required to publish the application to be published can be directly obtained. When the publishing process for publishing applications in the target server is not open and transparent to the outside, it is impossible to directly obtain the various calling interfaces and their interface parameters required to publish the application to be published. In this case, the interface parameters of each calling interface required to publish the application to be published can be obtained by following the following steps: obtain the request encryption information of the target server; log in to the target server according to the request encryption information, and obtain the interface parameters of each calling interface required to publish the application to be published.

[0050] For example, it is assumed that the target server does not provide the various calling interfaces and interface parameters required for the release of the official version of application C, and that a security check is set for each calling request in the process of releasing the official version of application C. At this time, the network request method, request header (message header), body (message body), cookie (data stored on the user's local terminal to identify the user's identity and track the session) and other information can be analyzed through tools such as crawlers and browser elements-network, and the encrypted key information (service-key) can be obtained, and it can be disguised as a web page (web) to log in through its security access, and then the various calling interfaces (Application Program Interface, API) related to the official version release can be analyzed through crawlers, such as: download, edit, upload metadata interface, review interface, review status query interface, etc. Finally, the various APIs are connected and assembled in series to form an executable program and deployed to the release workflow library.

[0051] In step S103, the application to be published is published to the target server according to the publishing workflow. The target server mentioned in this step refers to various application stores, such as the Apple App Store that supports the iOS system, the Google Play Store that supports the Android system, etc.

[0052] When the prior art releases an application, the user interacts with the target server to directly release the application to be released to the target server. Since the application release process requires multiple interactive operations with the target server, this application release process is heavily dependent on the user's manual operation, and the release process is cumbersome and labor and time costs are high. The method of the embodiment of the present invention provides a unified release platform to realize application release, and pre-sets a release workflow library. There is no need for each user to directly interact with the target server for data. Each application to be released can be automatically released to the target server, realizing one-click release, which greatly saves labor and time costs.

[0053] In the embodiment of the present invention, in order to facilitate visual viewing and operation, each method step in the embodiment of the present invention may be visually presented in the form of a web page.

[0054] In some optional embodiments, the method for implementing the embodiment of the present invention includes two parts: a pipeline part (Bamboo pipeline, used for pipeline tasks of the automatic publishing system, such as uploading, querying, and reviewing) and a scheduling part (Bamboo service, used to schedule some services and scheduling functions of the automatic publishing system). The pipeline part implements the core functions of the grayscale or formal version application by investigating business logic, underlying API, and tools, connects the core functions in series, and realizes automated process operation. The scheduling part implements the scheduling work between the core functions. Through webcore (a typesetting engine) development, the implemented functions are presented through the web (webpage) to achieve visual viewing and operation. This embodiment may include integrated process operations such as supporting iOS App Store Connect, Android Google Play, and channel package release. The system (i.e., the execution subject for implementing the method of the embodiment of the present invention) provides account management, supports users to select apps (applications), submit apps, query review status, conduct grayscale testing, and release apps on shelves and other core workflows. The above steps preset the release workflow through the scheduling capability of Bamboo service, which is divided into grayscale release and formal release. Each step will pre-set the operation of the next node, so that they can be run in series. Scheduling is for the business process operation of the publisher, not for multiple pipelines. The overall implementation is completed by the cooperation between the server and the pipeline, that is, the Bamboo service is responsible for scheduling, notifying the Bamboo pipeline of an operation that needs to be performed (such as uploading an app), and the Bamboo pipeline performs specific logical processing. After completion, it notifies the Bamboo service of the execution status so that the workflow continues to run. Figure 2 The scheduling process is shown, including: pre-collecting the business logic of releasable applications, building the application release pipeline, and providing the user with a release page. After the user uploads the application to be released on the release page, the system uploads the application to be released uploaded by the user to the target server such as App Store Connect or Google Play, and the user can query the asynchronous effectiveness status through the system. After the upload is successful, the system automatically conducts a grayscale review, and the user can query the grayscale review status through the system. After the grayscale review is passed, the system automatically prepares the materials before the formal review (multi-role collaborative process), and then conducts automated pre-review and formal package review.

[0055] The release workflow of the gray version generally includes the following nodes: upload, effective status, submission for review, and review status. The release workflow of the formal version generally includes the following nodes: upload, effective status, download metadata, edit metadata, upload (pre-review), formal review, and review status. Figure 3 Schematic diagram of a method for publishing a formal version application in an optional embodiment of the present invention. Figure 3 As shown in the figure, after the application to be released is uploaded to the App Store, the system queries the effectiveness status of the upload. If the upload is effective, the metadata is configured; otherwise, the process ends. Configuring metadata means downloading and editing metadata. After configuring metadata, the system automatically performs a pre-examination. If the pre-examination passes, a formal review is conducted; otherwise, the process ends. The status of the formal review is synchronized to the Bamboo service for user query. The target server returns the review status to the Bamboo service. If the review passes, the application to be released is successfully released to the App Store and the release process ends; otherwise, the release process of the application to be released is rejected, that is, it is not successfully released to the App Store.

[0056] When the publishing process for publishing applications in the target server is not open and transparent to the outside, you can first crack the publishing process of the target server and then build a publishing workflow for the application to be published. Figure 4 is a schematic diagram of the process of releasing the official version application in an optional embodiment of the present invention, such as Figure 4 As shown, the network request method, request header / body / cookie and other information of the target server are analyzed through crawlers, browser elements-network tools, etc., and the encrypted key information service-key is obtained, and it is disguised as a web login to gain secure access. Then, the various APIs related to the official version release are analyzed through crawlers, such as: download, edit, upload metadata interfaces, review interfaces, review status query interfaces, etc. Finally, the various APIs are connected and assembled in series to form an executable program, which is deployed to the release workflow library.

[0057] This embodiment can not only automatically publish each application to be released to the target server, realize one-click release, greatly saving manpower and time costs, but also connect with the channel market of target servers such as Apple, Google, Android, etc., to facilitate application development and promotion.

[0058] According to a second aspect of an embodiment of the present invention, a device for implementing the above method is provided.

[0059] Figure 5 is a schematic diagram of the main modules of the device for publishing an application according to an embodiment of the present invention, such as Figure 5 As shown, the device 500 for application publishing includes:

[0060] The receiving module 501 receives a user's application publishing request and obtains a publishing identifier of the application to be published;

[0061] The acquisition module 502 acquires the publishing workflow of the application to be published from a preset publishing workflow library according to the publishing identifier;

[0062] The publishing module 503 publishes the application to be published to the target server according to the publishing workflow.

[0063] Optionally, the release identifier includes: an application identifier and a version identifier.

[0064] Optionally, the acquisition module is further used to: before acquiring the publishing workflow of the to-be-published application from a preset publishing workflow library,

[0065] Obtaining interface parameters of various calling interfaces required for publishing the application to be published;

[0066] The calling interfaces are assembled according to the business logic of the application to be released and the interface parameters of the calling interfaces to obtain the publishing workflow of the application to be released.

[0067] Optionally, the acquisition module acquires interface parameters of various calling interfaces required for publishing the application to be published, including:

[0068] Obtaining encrypted request information of the target server;

[0069] The target server is logged in according to the encrypted request information to obtain interface parameters of each calling interface required for publishing the application to be published.

[0070] According to a third aspect of an embodiment of the present invention, there is provided an electronic device for publishing an application, including:

[0071] one or more processors;

[0072] a storage device for storing one or more programs,

[0073] When the one or more programs are executed by the one or more processors, the one or more processors implement the method provided in the first aspect of the embodiment of the present invention.

[0074] According to a fourth aspect of an embodiment of the present invention, a computer-readable medium is provided, on which a computer program is stored, and when the program is executed by a processor, the method provided by the first aspect of the embodiment of the present invention is implemented.

[0075] Figure 6 An exemplary system architecture 600 is shown to which the method or apparatus for application publishing according to the embodiment of the present invention may be applied.

[0076] like Figure 6 As shown, system architecture 600 may include terminal devices 601, 602, 603, network 604 and server 605. Network 604 is used to provide a medium for communication links between terminal devices 601, 602, 603 and server 605. Network 604 may include various connection types, such as wired, wireless communication links or optical fiber cables, etc.

[0077] Users can use terminal devices 601, 602, and 603 to interact with server 605 through network 604 to receive or send messages, etc. Various communication client applications can be installed on terminal devices 601, 602, and 603, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social platform software, etc. (only examples).

[0078] The terminal devices 601 , 602 , and 603 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop computers, and desktop computers, etc.

[0079] The server 605 may be a server that provides various services, such as a backend management server (only an example) that provides support for shopping websites browsed by users using the terminal devices 601, 602, and 603. The backend management server may analyze and process the received data such as product information query requests, and feed back the processing results (such as target push information, product information - only an example) to the terminal device.

[0080] It should be noted that the application publishing method provided in the embodiment of the present invention is generally executed by the server 605 , and accordingly, the application publishing device is generally set in the server 605 .

[0081] It should be understood that Figure 6 The number of terminal devices, networks and servers in the embodiment is only for illustration. Any number of terminal devices, networks and servers may be provided according to implementation requirements.

[0082] Reference below Figure 7 , which shows a schematic diagram of the structure of a computer system 700 of a terminal device suitable for implementing an embodiment of the present invention. Figure 7 The terminal device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present invention.

[0083] like Figure 7As shown, the computer system 700 includes a central processing unit (CPU) 701, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 702 or a program loaded from a storage portion 608 into a random access memory (RAM) 703. In the RAM 703, various programs and data required for the operation of the system 700 are also stored. The CPU 701, the ROM 702, and the RAM 703 are connected to each other via a bus 704. An input / output (I / O) interface 705 is also connected to the bus 704.

[0084] The following components are connected to the I / O interface 705: an input section 706 including a keyboard, a mouse, etc.; an output section 707 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 708 including a hard disk, etc.; and a communication section 709 including a network interface card such as a LAN card, a modem, etc. The communication section 709 performs communication processing via a network such as the Internet. A drive 710 is also connected to the I / O interface 705 as needed. A removable medium 711, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 710 as needed, so that a computer program read therefrom is installed into the storage section 708 as needed.

[0085] In particular, according to the embodiments disclosed in the present invention, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present invention include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 709, and / or installed from the removable medium 711. When the computer program is executed by the central processing unit (CPU) 701, the above-mentioned functions defined in the system of the present invention are executed.

[0086] It should be noted that the computer-readable medium shown in the present invention may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present invention, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, device or device. In the present invention, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, which carries a computer-readable program code. This propagated data signal may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. The program code contained on the computer-readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, optical cable, RF, etc., or any suitable combination of the above.

[0087] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, functions and operations of the system, method and computer program product according to various embodiments of the present invention. In this regard, each box in the flow chart or block diagram can represent a module, a program segment, or a part of a code, and the above-mentioned module, program segment, or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flow chart, and the combination of the boxes in the block diagram or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0088] The modules involved in the embodiments of the present invention may be implemented in software or hardware. The modules described may also be set in a processor. For example, they may be described as: a processor includes: a receiving module, which receives a user's application publishing request and obtains a publishing identifier of the application to be published; an obtaining module, which obtains the publishing workflow of the application to be published from a preset publishing workflow library according to the publishing identifier; and a publishing module, which publishes the application to be published to the target server according to the publishing workflow. Among them, the names of these modules do not constitute a limitation on the module itself in some cases. For example, the receiving module may also be described as "a module that publishes the application to be published to the target server according to the publishing workflow."

[0089] As another aspect, the present invention also provides a computer-readable medium, which may be included in the device described in the above embodiment; or may exist independently without being assembled into the device. The above computer-readable medium carries one or more programs, and when the above one or more programs are executed by a device, the device includes: receiving a user's application publishing request, obtaining a publishing identifier of the application to be published; according to the publishing identifier, obtaining the publishing workflow of the application to be published from a preset publishing workflow library; and publishing the application to be published to the target server according to the publishing workflow.

[0090] According to the technical solution of the embodiment of the present invention, a unified publishing platform is used to realize application publishing and a publishing workflow library is preset. There is no need for each user to directly interact with the target server for data. Each application to be published can be automatically published to the target server, realizing one-click publishing, which greatly saves manpower and time costs.

[0091] The above specific implementations do not constitute a limitation on the protection scope of the present invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may occur depending on design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present invention shall be included in the protection scope of the present invention.

Claims

1. A method for publishing an application, characterized in that: include: Receive the user's application publishing request and obtain the publishing identifier of the application to be published; According to the release identifier, obtaining the release workflow of the application to be released from a preset release workflow library; Publishing the application to be published to the target server according to the publishing workflow; The publishing workflow refers to a workflow formed by connecting in series various business process operation nodes related to publishing the application to be published; the method includes a pipeline part and a scheduling part; The scheduling part is responsible for scheduling according to the publishing workflow, notifying the pipeline part of a certain operation that needs to be performed currently, and the pipeline part performs specific logical processing, and notifies the scheduling part of the execution status after completion.

2. The method according to claim 1, characterized in that The release identifier includes: application identifier and version identifier.

3. The method according to claim 1, characterized in that Before obtaining the publishing workflow of the to-be-published application from the preset publishing workflow library, the method further includes: Obtaining interface parameters of various calling interfaces required for publishing the application to be published; The calling interfaces are assembled according to the business logic of the application to be released and the interface parameters of the calling interfaces to obtain the publishing workflow of the application to be released.

4. The method according to claim 3, characterized in that Obtain the interface parameters of each calling interface required to publish the application to be published, including: Obtaining encrypted request information of the target server; The target server is logged in according to the encrypted request information to obtain interface parameters of each calling interface required for publishing the application to be published.

5. A device for publishing an application, characterized in that: include: A receiving module receives a user's application publishing request and obtains a publishing identifier of the application to be published; An acquisition module, which acquires the publishing workflow of the application to be published from a preset publishing workflow library according to the publishing identifier; A publishing module, which publishes the application to be published to a target server according to the publishing workflow; The publishing workflow refers to a workflow formed by connecting in series various business process operation nodes related to publishing the application to be published; the device includes a pipeline part and a scheduling part; The scheduling part is responsible for scheduling according to the publishing workflow, notifying the pipeline part of a certain operation that needs to be performed currently, and the pipeline part performs specific logical processing, and notifies the scheduling part of the execution status after completion.

6. The device according to claim 5, characterized in that The release identifier includes: application identifier and version identifier.

7. The device according to claim 5, characterized in that The acquisition module is further used to: before acquiring the publishing workflow of the to-be-published application from a preset publishing workflow library, Obtaining interface parameters of various calling interfaces required for publishing the application to be published; The calling interfaces are assembled according to the business logic of the application to be released and the interface parameters of the calling interfaces to obtain the publishing workflow of the application to be released.

8. The device according to claim 7, characterized in that The acquisition module acquires interface parameters of various calling interfaces required for publishing the application to be published, including: Obtaining encrypted request information of the target server; The target server is logged in according to the encrypted request information to obtain interface parameters of each calling interface required for publishing the application to be published.

9. An electronic device for publishing an application, characterized in that: include: one or more processors; a storage device for storing one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors implement the method according to any one of claims 1 to 4.

10. A computer readable medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the method according to any one of claims 1 to 4 is implemented.

Images