Supporting overseas application sales management server system

Abstract

The present invention provides a server system for managing sales of overseas applications, which can quickly and appropriately perform customer checks when a third-party application developed by a third party is requested to be purchased through an application store operated in an overseas country. The management server (100) has: an order processing unit (112) that manages online store sales that can only purchase applications stored in an application BD (250) and registered for online store sales, and determines whether the application requested to be purchased from a user is a third-party application developed by a third party; and a sales approval processing unit (113) that notifies the user that the approval of the third party is being waited for when the application requested to be purchased is a third-party application, and notifies the third party of the customer check request, thereby obtaining sales approval for the third-party application.

Description

Technical Field

[0001] The present invention relates to a server system for managing sales of overseas application programs. Background Art

[0002] Recently, in the field of manufacturing equipment including CNC machine tools, industrial equipment, industrial robots, etc., EC (electronic commerce) websites (also called "application stores", "app stores", or "application sales management systems", or "application sales management systems") are provided to users for online sales (also called "store sales") of server application software (hereinafter referred to as "applications" or "apps") with various functions or purposes for manufacturing sites.

[0003] In such a website, applications developed by various application developers are displayed in the application store after a prescribed review, and users can purchase them and install them in the edge server set up at the manufacturing site for use. Specifically, for example, at a manufacturing site such as a factory, data indicating the operating status of a manufacturing device, data indicating the production status of a manufacturing device, data indicating the quality status of a product manufactured by a manufacturing device, data indicating the operating status of a manufacturing device, and the like can be collected and effectively used through the edge server application.

[0004] By setting up such an application store in a third country overseas (hereinafter also referred to as a "third country") and providing it to users in the third country, it is convenient for users in the third country to use the application store to purchase applications corresponding to their uses and install them on the edge server set up at the manufacturing site in the third country.

[0005] When such an application store is operated and provided in a third country, the applications displayed in the application store have various functions for manufacturing equipment including CNC machine tools, industrial equipment, industrial robots, etc., and therefore, for example, may be used for weapon development. Therefore, when a store sells an application developed in a country other than Japan or a third country in a third country, it may be restricted by the "Export Trade Control Order" of each country.

[0006] In this case, when an application store is operated and provided in a third country, when an application developed in a country other than Japan or a third country is sold in the application store provided by the third country, the application needs to meet the requirements stipulated by the security export control laws of the country other than Japan or the third country, and when the application is sold (for example, distributed) to a customer in a third country who actually wishes to purchase the application, a separate check needs to be conducted to ensure that the customer is not a customer of concern (for example, a company or organization that does not and / or will not develop weapons of mass destruction, etc., or is not listed on a foreign user list).

[0007] <Export Trade Control Law>

[0008] Here, the export trade control laws and regulations of Japan are briefly described. In addition, the area to which the export control laws and regulations of each country are applied is referred to as a region.

[0009] For example, enabling an application developed in Japan to be sold in stores in overseas regions outside Japan (for example, the United States), that is, enabling an application developed in Japan to be published to an application store (such as a publishing server) set up corresponding to an overseas region (hereinafter referred to as "local store sales registration" or "local store registration"), is consistent with the act of exporting the application from Japan to overseas regions (for example, the United States).

[0010] Japan is a whitelist country that strictly implements export control. In Japan, the "Export Trade Control Order" is used to restrict exports related to weapon development. For example, a server application program that is sold in an overseas region outside Japan (hereinafter, also referred to as an "export destination") and is run by the edge server 400 is an application associated with the operation of a machine tool, etc., and is considered to be potentially related to weapon development. Therefore, in order to register the application for local store sales in the export destination (an overseas region outside Japan, such as the United States), the person who makes the application, for example, the developer of the application needs to determine whether the application complies with the Export Trade Control Order (hereinafter also referred to as "conformity / nonconformity judgment"). Therefore, the person who makes the application, that is, the developer of the application, needs to prepare a "conformity / nonconformity judgment note". In addition, regarding the judgment of conformity / nonconformity in the conformity / nonconformity judgment, if the export destination is a whitelist country, it is based on list restrictions, and if the export destination is a non-whitelist country, it is based on catch-all controls.

[0011] In addition, several technologies for efficiently making compliance / non-compliance determinations are provided. For example, Patent Document 1 shows an export management system that displays guidance such as relevant legal texts when making compliance / non-compliance determinations. In addition, Patent Document 2 shows an export management compliance / non-compliance determination chart extraction system that has multiple compliance / non-compliance determination tables, and selects a compliance / non-compliance determination table based on input such as keywords. In addition, Patent Document 3 shows an export management system that allows operators who make compliance / non-compliance determinations to make compliance / non-compliance determinations while referring to past compliance / non-compliance determination results, thereby improving the accuracy of compliance / non-compliance determinations.

[0012] Next, after the developer of the app has prepared a compliance / non-compliance determination certificate, anyone who exports the app to an export destination (an overseas location outside of Japan, such as the United States), for example, when the developer exports the app himself or a person who purchases the app from the developer for export, will need to obtain a compliance / non-compliance determination certificate and, after confirming its contents, will need to obtain export trade management permission from, for example, an economic and industrial official.

[0013] It should be noted that if the app is judged as "non-compliant", it is not necessary to obtain export trade management permission from the Ministry of Economy, Industry and Commerce. In other words, it is possible to apply for local store sales registration from the operating management company of the application store at the export destination.

[0014] When the app is judged as "compliant", when the export destination is a whitelist country, a comprehensive license (such as an unlimited special blanket permission) can be obtained. In addition, when the export destination is not a whitelist country, store sales that comply with the stock sales of the app are basically not allowed (that is, it is not possible to apply for local store sales registration from the operating manager of the application store at the export destination, that is, the operating management company). In this case, in order to sell the app at the export destination, face-to-face sales are required (that is, for each customer who requests to purchase the app, an export license for the app for that customer is obtained from the economic and industrial officials).

[0015] As described above, when it is determined to be compliant in the compliance / non-compliance determination, only when the export destination is a whitelist country, after obtaining a comprehensive license (for example, a special general comprehensive license), you can apply for local store sales registration from the operating manager, that is, the operating management company, of the application store in the export destination (whitelist country). On the other hand, when the export destination is a non-whitelist country, you cannot apply for local store sales registration from the operating manager, that is, the operating management company, of the application store in the export destination (non-whitelist country).

[0016] In summary, when the application is determined to be "non-compliant", for example, for an application developed in Japan, regardless of whether the export destination is a whitelist country or a non-whitelist country, you can apply to the operation manager of the application store in the export destination (whitelist country), that is, the operation management company, for local store sales registration. On the other hand, when the application is determined to be "compliant", for example, for an application developed in Japan, you can apply to the operation manager of the application store in the export destination (whitelist country), that is, the operation management company, for local store sales registration only when the export destination is a whitelist country.

[0017] <Customer Inspection>

[0018] Furthermore, after local store sales registration is completed with the operating manager of the application store at the export destination, i.e., the operating management company, when an order for the application is generated, taking the application developed in Japan as an example, a customer check is required according to the order destination. The customer check is used to determine whether the order destination, i.e., the customer, is a customer of interest.

[0019] For an application developed in Japan, after it has been registered for local store sales with the operating manager of the application store at the export destination, i.e., the operating management company, when there is a purchase request for the application from a customer who resides (also referred to as "belongs to") in the export destination (e.g., the United States), the exporter (e.g., the application developer) needs to conduct a separate check (also referred to as "customer check") on the customer, such as if the customer does not and / or will not develop weapons of mass destruction, etc., or if the customer is not a company or organization listed in the foreign user list. Here, the so-called foreign user list refers to a list of foreign company names and organization names, which are prepared by the Ministry of Economy, Trade and Industry in accordance with the export trade control order, and the exported goods or technologies may be used for the development, manufacture, etc. of weapons of mass destruction, biological weapons, chemical weapons, and carrier missiles.

[0020] As a result of the customer inspection, if the customer qualifies as a customer of concern, the application is not allowed to be sold.

[0021] In this regard, Patent Documents 1 to 3 neither describe nor suggest a technique for efficiently performing the above-described customer inspection.

[0022] Prior art literature

[0023] Patent Literature

[0024] Patent Document 1: Japanese Patent Application Publication No. 2003-36323

[0025] Patent Document 2: Japanese Patent Application Publication No. 2007-140889

[0026] Patent Document 3: Japanese Patent No. 3958264

[0027] As described above, in an application store operated and provided in a third country, that is, in a corresponding overseas application sales management server system, for example, after an application developed by a country other than Japan or a third country (hereinafter also referred to as a "third-party application") is registered for store sales (hereinafter also referred to as "store registration") as an application that can be sold in the application store (specifically, for example, after registering with the publishing server of the application sales management system), when there is a purchase request for the application from a customer residing in a third country, the application developer (hereinafter also referred to as the "third party") who wishes to reside in a country other than Japan or a third country can quickly conduct a customer check and can understand the customer check status involving the third party after the customer makes a purchase request. Summary of the invention

[0028] (1) One method of the present disclosure provides a corresponding overseas application sales management server system, which manages the online store sales of applications run by an edge server in a third country, the edge server being communicatively connected to one or more edge devices, the corresponding overseas application sales management server system corresponding to the third country, and characterized in that the corresponding overseas application sales management server system is communicatively connected to the edge device set up in the third country and the user terminal of the user using the edge server via a communication network, the corresponding overseas application sales management server system having: an application DB, which stores the applications to be registered for online store sales; and a management control unit, which controls the online store that can only purchase the applications stored in the application DB and registered for online store sales. The sales management unit includes: a publishing control unit, which publishes the application to the edge server, and an order processing unit, which determines whether the application requested to be purchased from the user via the user terminal is a third-party application developed by an application developer in a country other than the third country, that is, a third party; and a sales approval processing unit, which, when it is determined by the order processing unit that the application requested to be purchased is a third-party application developed by a third party, notifies the user via the user terminal that the approval of the third party is waiting, and notifies the contact destination of the third party of a customer inspection request, thereby obtaining sales approval of the third-party application performed by the third party from the third party, wherein the customer inspection request is used to determine whether to approve the sale of the third-party application requested to be purchased from the user to the user.

[0029] Effects of the Invention

[0030] According to one method, in an application store operated and provided in a third country, i.e., a corresponding overseas application sales management server system, when there is a purchase request for a third-party application developed by a country other than Japan or a third country from a customer residing in the third country, the application developer, i.e., the third party, can quickly perform a customer check and can understand the status of the customer check performed by the third party after the customer makes a purchase request. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] Figure 1 1 is a schematic diagram showing a basic configuration of an application sales management system 1000 - n installed in a region n according to the present embodiment.

[0032] Figure 2A This is a functional block diagram of the management server 100 included in the sales management server system 10 in the present embodiment.

[0033] Figure 2B This is a functional block diagram of the distribution server 200 included in the sales management server system 10 in the present embodiment.

[0034] Figure 2C This is a diagram showing an example of the storage unit 120 of the management server 100 included in the sales management server system 10 in the present embodiment.

[0035] Figure 2D This is a diagram showing an example of the storage unit 220 of the distribution server 200 included in the sales management server system 10 in the present embodiment.

[0036] Figure 2E This is a diagram showing an example of the application DB 250 included in the sales management server system 10 in the present embodiment.

[0037] Figure 3 This is a diagram showing an example of a browsing screen displayed on the terminal 600 in the present embodiment.

[0038] Figure 4 An example of a screen displayed while waiting for third party approval for an application requested to be purchased by a user in the present embodiment is shown.

[0039] Figure 5A An example of the order status management screen provided to a third party in this embodiment is shown.

[0040] Figure 5B An example of a screen provided to a third party in the present embodiment and presenting information related to a user who requests to purchase a third-party application developed by the third party is shown.

[0041] Figure 5CAn example of a search condition input field included in the order status management screen provided to a third party in the present embodiment is shown.

[0042] Figure 6 1 is a flowchart showing the browsing information providing process of the sales management server system 10 in the present embodiment.

[0043] Figure 7 This is a flowchart showing an example of order processing for a purchase request from a customer by the sales management server system 10 in this embodiment.

[0044] Figure 8 This is a flowchart showing an example of the process related to sales approval of the sales management server system 10 in this embodiment.

[0045] Fig. 9 This is a flowchart showing an example of the process after the sales approval process of the sales management server system 10 in this embodiment.

[0046] Fig.10 This is a flowchart showing an example of the application distribution process of the sales management server system 10 in this embodiment.

[0047] Fig.11 This is a functional block diagram of the store registration server 300 in this embodiment.

[0048] Fig.12 An example of the application registration management screen provided by the store registration server 300 in this embodiment is shown.

[0049] Fig.13 This is a flowchart showing an example of processing related to store sales registration in the store registration server 300 in this embodiment.

[0050] Fig.14 4 is a functional block diagram of the edge server 400 in this embodiment.

[0051] Fig.15 This is a diagram showing an example of server configuration in this embodiment.

[0052] Explanation of symbols

[0053] 1000 Application Sales Management System

[0054] 10 Sales Management Server System

[0055] 100 Management Server

[0056] 200 Publish Server

[0057] 110, 210 Control Department

[0058] 111 Reading Information Provision Department

[0059] 112 Order Processing Department

[0060] 113 Sales Approval Processing Department

[0061] 114 Release Management Processing Department

[0062] 115 Contract Update Processing Department

[0063] 214 Release Processing Department

[0064] 120, 220 Storage

[0065] 122 User storage unit

[0066] 124 Release Management Storage Department

[0067] 125 Application developer information storage unit

[0068] 126 Order status management information storage department

[0069] 224 Release Data Storage Department

[0070] 250 Application DB

[0071] 300 Store Registration Server

[0072] 310 Control Department

[0073] 311 Application Acceptance Department

[0074] 312 Application Review Department

[0075] 313 Application Registration Department

[0076] 314 Registration Application Management Department

[0077] 320 Storage

[0078] 400 Edge Server

[0079] 410 Control Department

[0080] 411 Application Execution Unit

[0081] 412 License Control Department

[0082] 413 Access Control Department

[0083] 414 Illegal Application Notification Department

[0084] 420 Storage

[0085] 430 Ministry of Communications

[0086] 500 edge devices

[0087] 600 Terminal

[0088] N1, N2 Network DETAILED DESCRIPTION

[0089] In this embodiment, the area to which the export control laws of each country or a community (regional community) between countries apply is called a region. For example, Japan to which the export control laws of Japan apply or the United States to which the export control laws of the United States apply are each one region.

[0090] Here, when Japan is set as region 0 (zero) and n (n ≥ 1) is set as a notation indicating each overseas region, as described later, the application sales management system 1000-n (hereinafter also referred to as "sales management system 1000-n") corresponding to the overseas application sales management system can be set according to the region n (n ≥ 1) as a third country. Hereinafter, n ≥ 1 is assumed unless otherwise specified.

[0091] For example, the application sales management system 1000 (Japan) installed in Japan, the application sales management system 1000 (USA) installed in the United States, etc. are listed.

[0092] Figure 1 1 is a schematic diagram showing a basic configuration of an application sales management system 1000 - n provided for each overseas region n (n≧1) in the present embodiment.

[0093] like Figure 1 As shown, the application sales management system 1000-n includes an application sales management server system 10-n (hereinafter also referred to as "sales management server system 10-n") as a corresponding overseas program application sales management server system, a store registration server 300 as a sales registration control unit, an edge server 400-n, an edge device 500-n, and a terminal 600-n (user terminal). The sales management server system 10-n, the store registration server 300, the edge device 500-n, and the terminal 600-n are communicatively connected via a network N1-n. The network N1-n is, for example, the Internet, a VPN (Virtual Private Network), a public telephone network, etc. There is no particular limitation on the specific communication method in the network N1, such as a wired connection or a wireless connection.

[0094] In addition, one operation management company 2-n that operates and manages the sales management server system 10-n is preset in the region n. Usually, the operation management company 2-n is a company (for example, a legal person) that resides in (hereinafter also referred to as "belongs to") the region n.

[0095] The sales management server system 10-n and the store registration server 300 are dedicated server systems that are independent of each other and correspond to the region n. Here, the dedicated server system is not necessarily limited to a physically independent server device. For example, it can also be an independent virtual server included in a specified server or a specified cloud, etc., which ensures a dedicated region corresponding to the region n. In this case, the sales management server system 10-n and the store registration server 300 ensured in the dedicated region corresponding to the region n are managed and operated by the operation management company 2-n.

[0096] The sales management server system 10-n is, for example, Figure 1 As shown, the system is composed of a management server 100-n as a management control unit, a distribution server 200-n as a distribution control unit, and an application program DB (also referred to as "application DB") 250-n as an application DB.

[0097] Here, the management server 100-n does not necessarily need to be physically installed in the region n, and may be installed in a region other than the region n (for example, Japan, etc.). On the other hand, it is preferable that the distribution server 200-n and / or the application DB 250-n described later, which stores at least the application program set to a state that can be sold in a store (also referred to as "store sales registration" or "store registration"), is installed in the region n. The configuration of the server, etc. will be described later.

[0098] The store registration server 300-n is a server for performing store sales registration in the sales management server system 10-n so as to enable store sales when the application developed by the application developer meets predetermined conditions. The details of the store registration server 300 will be described later.

[0099] The edge server 400-n is limited to being set in the region n (hereinafter also referred to as "belonging to the region n"). More specifically, the edge server n that is communicatively connected to the sales management server system 10-n via the network N1-n is limited to belonging to the region n. The edge server 400-m belonging to another region m (m≠n) other than the region n cannot communicate with the sales management server system 10-n. More specifically, the edge server 400-m belonging to another region m (m≠n) other than the region n cannot purchase the server application from the sales management server system 10-n.

[0100] Here, as a server application running on the edge server 400-n, for example, a server that collects data indicating the operation status of the edge device 500-n described later, data indicating the production status, data indicating the quality status of the product, data indicating the operation status, etc., and performs information processing is listed, but it is not limited to this. In addition, in the following description, the server application that performs sales management through the application sales management system 1000-n is simply referred to as an application or an application.

[0101] In this way, the edge server 400-n is a server that, by executing an application purchased from the sales management server system 10-n, collects data representing the action status related to the edge device 500-n, data representing the production status, data representing the quality status of the product, data representing the operating status, etc. from one or more edge devices 500-n, and performs prescribed information processing related to the application.

[0102] The so-called edge device 500-n refers to a device installed at a manufacturing site such as a factory in region n, including manufacturing devices such as CNC machine tools, industrial equipment, industrial robots, and image sensors, PLCs (programmable logic controllers), etc. For example, one or more edge devices 500-n constitute a production line or production unit of a factory.

[0103] In this case, the edge device 500-n has a function of entrusting the edge server 400-n. The edge server 400-n and one or more edge devices 500-n are installed in, for example, a factory facility of the user 3-n and are communicatively connected via a network such as a LAN (Local Area Network).

[0104] The sales management server system 10 - n is an online store system for assisting in executing sales management processing for a user 3 - n belonging to a region n who wishes to purchase a server application program run by an edge server 400 - n .

[0105] As described later, the user 3-n can, for example, make a purchase request for a desired server application to the management server 100-n via the terminal 600-n, and obtain a serial number related to the server application from the management server 100-n when a predetermined condition is satisfied. In this way, the user 3-n can make the distribution server 200-n distribute (install) the server application to the edge server 400-n based on the serial number.

[0106] The terminal 600-n is, for example, a personal computer (PC). The terminal 600-n is connected to the management server 100-n so as to be communicable, and is, for example, a terminal used by an end user belonging to region n who wishes to purchase a server application that is run through the edge server 400-n. Here, the terminal 600-n used by the user 3-n may be set in a factory facility or outside the factory facility, but belongs to region n. Furthermore, the user 3-n can access the sales management server system 10-n via the terminal 600-n, and can view the content of the application that the user 3-n can purchase. In addition, the user 3-n can order the application via the terminal 600-n.

[0107] In addition, only the user 3-n that meets the pre-set conditions (qualifications, etc.) is given a user ID (IDentification) for accessing the sales management server system 10-n. The details will be described later.

[0108] [Structure of the Sales Management Server System 10-n Belonging to Region n]

[0109] Next, the structure of the sales management server system 10-n set corresponding to the region n (also referred to as "belonging to the region n") is described. The sales management server system 10-n described in this embodiment includes a structure that not only sells the application store developed by the application developer belonging to the region n (hereinafter also referred to as "application developer") to the user 3-n belonging to the region n, but also sells (exports) applications developed by application developers belonging to the region m (m ≥ 0 and m ≠ n) in Japan other than the region n through the sales management server system 10-n.

[0110] For simplicity, n is omitted for description below. Therefore, the region described below represents an overseas region n (n≥1) outside Japan (for example, a foreign country such as the United States), unless otherwise specified. That is, the sales management server system 10 (management server 100, publishing server 200, and application DB250) is set corresponding to the region n (for example, a foreign country such as the United States). In addition, unless otherwise specified, the store registration server 300 is set corresponding to the region (for example, a foreign country such as the United States). In addition, unless otherwise specified, the edge server 400, edge device 500, terminal 600, and user 3 respectively represent parts belonging to the overseas specified region n (n≥1) outside Japan (for example, a foreign country such as the United States).

[0111] In addition, as a region other than the region, unless otherwise specified, the region 0 (zero), that is, Japan, is used as an example for description. That is, in the following description, unless otherwise specified, the configuration is exemplified in which a server application developed by an application developer belonging to (residing in) Japan is sold (exported) to a user 3-n belonging to the region n via a sales management server system 10-n belonging to a region other than Japan (for example, a foreign country such as the United States).

[0112] However, this embodiment is not limited to Japan and regions n outside Japan (for example, foreign countries such as the United States). As described above, it can also be applied to the following situation: not only the application store developed by the application developer belonging to the region n is sold to the user 3-n belonging to the region n, but also the application developed by the application developer belonging to the region m (m≠n) outside the region n is sold (exported) via the sales management server system 10-n.

[0113] Next, functions included in the sales management server system 10 will be described.

[0114] Figure 2A as well as Figure 2B They are functional block diagrams of the management server 100 and the publishing server 200 included in the sales management server system 10 in the present embodiment. In addition, the user interface (UIF) and emails in these servers can be displayed by switching the display language regardless of the corresponding region. Specifically, for example, the default language is set by region. For example, the UI and emails provided to users, application developers, operating management companies (managers, persons in charge) belonging to region n can be provided in the display language of region n. In addition, the UI and emails provided to application developers (also referred to as "third parties") in countries other than region n (such as Japan) can also be provided in the display language of the region (such as Japan). In addition, the UI and the like shown below as examples are temporarily recorded in Chinese, but in region n, as a default, they are displayed in the display language of region n.

[0115] like Figure 2A As shown in FIG. 1 , the management server 100 includes a control unit 110, a storage unit 120, and a communication unit 130. Figure 2B As shown, the distribution server 200 includes a control unit 210 , a storage unit 220 , and a communication unit 230 .

[0116] The control unit 110 and the control unit 210 may be CPUs, and they collectively control the management server 100 and the distribution server 200 by executing various programs stored in the storage unit 120 and the storage unit 220 , respectively.

[0117] The communication unit 130 and the communication unit 230 are communication control elements that transmit and receive data with external devices (for example, the edge server 400 , the terminal 600 , etc.) via a network.

[0118] In the management server 100, the control unit 110 includes a reading information providing unit 111, an order processing unit 112, a sales approval processing unit 113, a release management processing unit 114, and a contract renewal processing unit 115 as functional units based on the programs stored in the storage unit 120. The storage unit 120 includes an application management information storage unit 121, a user storage unit 122, a release management storage unit 124, an application developer information storage unit 125, and an order status management information storage unit 126 in addition to the programs executed by the control unit 110.

[0119] Furthermore, in the distribution server 200, the control unit 210 includes a distribution processing unit 214 as a functional unit based on the program stored in the storage unit 220. The storage unit 220 includes a distribution data storage unit 224 in addition to the program executed by the control unit 210.

[0120] Before describing each functional unit of the control unit 110 and the control unit 210 , first, the storage unit 120 , the storage unit 220 , and the application DB 250 will be described.

[0121] Figure 2C It is a diagram showing an example of the storage unit 120 of the management server 100 in this embodiment. Figure 2D 2 is a diagram showing an example of the storage unit 220 of the distribution server 200 in the present embodiment. Figure 2E This is a diagram showing an example of the application DB 250 .

[0122] <Application Management Information Storage Unit 121>

[0123] like Figure 2C As shown, the application management information storage unit 121 is a storage area for storing management information (metadata) related to applications that can be purchased in the region. In this embodiment, the application management information storage unit 121 does not store the application program itself, but stores it in the application DB 250 described later.

[0124] like Figure 2CAs shown, the application management information storage unit 121 stores data corresponding to the application ID. As an example, the data may include: application name (and / or product name), target machine type information, input information, application manual, price information, application developer information (including application developer ID), sales method information, whether there is customer inspection information, etc., wherein the sales method information indicates whether store sales can be carried out and whether face-to-face sales are required; whether there is customer inspection information indicates whether the application developer needs to conduct customer inspection when performing store sales. In addition, the data stored in the application management information storage unit 121 is not limited to this. It is also possible to store part of the exemplified data items and other data items.

[0125] The application ID is identification information for identifying an application program.

[0126] The target machine type information is machine type information of the edge device 500 that is the input / output target of the application, and is, for example, a machine type name such as a CNC machine tool, industrial equipment, or an industrial robot.

[0127] The input information is edge device information including input data information input from the edge device 500 and the like.

[0128] The description of the application includes descriptions related to the structure of the application and descriptions related to the license. The descriptions related to the license include, for example, whether the license specifies the edge device 500 that uses the application, whether there is a designation of the edge device 500, whether it is necessary to purchase a certain number of edge devices 500 that can be used simultaneously, or whether there is no limit on the number of edge devices 500 that can be used simultaneously, and other contents related to the number of devices that can be used simultaneously. In addition, descriptions related to whether the contract is updated are also included regarding the use of the application.

[0129] The price information is information related to the sales price of the application.

[0130] The application developer information is information related to the developer of the application, and may include, for example, the application developer ID, the nationality (or region ID), etc.

[0131] The sales method information is information indicating whether the application can be sold in stores or whether face-to-face sales are required. Here, face-to-face sales means that the application developer does not sell the application in stores to users who wish to purchase the application, but sells the application directly to the user. Therefore, applications that require face-to-face sales cannot be ordered via the ordering screen provided by the management server 100 described later.

[0132] Whether there is customer check information is information indicating whether the developer of the application is required to conduct customer check when selling the application in the store. For example, if the developer of the application belongs to a country outside the region, such as a whitelist country that strictly implements export control (for example, Japan), and the sale of the application is an export behavior for the developer of the application, a customer check based on the export trade control order of the country (for example, Japan) is required.

[0133] Here, we will briefly explain import applications from regions outside this region, such as white-list countries that strictly implement export controls (such as Japan).

[0134] <Export Trade Control Law>

[0135] For example, making an application developed in Japan available for sale in overseas regions (e.g., the United States) (i.e., for example, registering the application for sale in a store as being able to be published to the application DB250 set up in the region) complies with the act of exporting the application from Japan to a region (e.g., the United States).

[0136] In Japan, which strictly implements export control, exports related to weapons development are restricted through the "Export Trade Control Order". For example, a server application that is sold in a region (e.g., the United States) and is run through the edge server 400 is an application related to the operation of a machine tool, etc., and is considered to be potentially related to weapons development. Therefore, in order to set the application to a state in which it can be sold in a region (e.g., the United States) (for example, registering the application, i.e., the store sales registration, as a state in which it can be published to the application DB250 set up in the region), the person who manufactures the application, i.e., the developer of the application, needs to determine whether it complies with the Export Trade Control Order (compliance / non-compliance determination) when exporting the application to the region. Therefore, the person who manufactures the application, i.e., the developer of the application, needs to prepare a "compliance / non-compliance determination sheet".

[0137] Next, after the developer of the app creates a compliance / non-compliance statement, the app is exported to people in the region, such as when the developer exports the app himself or a person who purchases the app from the developer and exports it, etc. After obtaining the compliance / non-compliance statement and confirming its contents, it is necessary to obtain permission for export trade management from, for example, economic and industrial officials.

[0138] In addition, when the application is judged as "non-compliant", there is no need to obtain special permission for export trade management from economic and trade officials.

[0139] When the app is judged as "compliant", if the region is a whitelist country, a comprehensive license (such as a special general comprehensive license) can be obtained. In addition, if the region is a non-whitelist country, stores that sell stocks that comply with the app are not allowed to sell it, and in order to sell the app, face-to-face sales are required (that is, each time an export license for the app is obtained).

[0140] The procedures related to the export trade management order are well known to those skilled in the art, and a detailed description thereof will be omitted.

[0141] After the above procedures, for example, the procedure of registering the application developed in Japan for store sales in an overseas region (eg, the United States) can be started (ie, registering the application so that it can be distributed to the application DB 250 set up in the region).

[0142] Specifically, the exporter of the application can apply for registration of the application to the operation and management enterprise 2 (belonging to the region), and the operation and management enterprise 2 operates the sales management server system 10 in the region.

[0143] In addition, an embodiment of the store registration server 300 for registering a developed application (e.g., developed in Japan) for store sales in an overseas region (e.g., the United States) by the exporter of the application (i.e., setting the application to a state where it can be published to the application DB250 set up in the region) will be described later.

[0144] <Customer Inspection>

[0145] Even if an application exporter (eg, application developer) registers a store for sale of an application developed in Japan in an overseas region (eg, the United States), it is necessary to individually confirm whether the order destination is a customer of interest each time an order for the application is generated.

[0146] Specifically, for example, after an application developed in Japan is registered for store sales in a region (e.g., the United States) (i.e., the application is registered as a state that can be published to the publishing server 200 set up in the region), when there is a purchase request for the application from a customer belonging to the region (e.g., the United States), the exporter (e.g., the application developer) needs to separately check whether the customer is (has been) developing weapons of mass destruction, etc., or whether the customer is a company or organization listed in the foreign user list. Here, the so-called foreign user list is a table that lists the names of foreign companies and organizations of concern, which are prepared by the Ministry of Economy, Trade and Industry in accordance with the export trade control order and whose exported goods or technologies are used for the development and manufacture of weapons of mass destruction, biological weapons, chemical weapons, carrier missiles, etc.

[0147] When the result of the customer check is that the customer qualifies as a concerned customer, the application will not be sold.

[0148] The details of the processing contents of the sales management server system 10 (management server 100 and distribution server 200) when performing customer check whenever an order for the application is generated for the exporter of the application (eg, application developer) will be described later.

[0149] <User storage unit 122>

[0150] The user storage unit 122 is a storage area for storing information related to the user 3 who has set up the edge server 400 that can be communicatively connected to the sales management server system 10. In addition, in order to set up the edge server 400, it is a prerequisite that the user 3 satisfies the predetermined conditions (qualifications, etc.) set in advance. The user 3 who has set up the edge server 400 is a user who is allowed to access the sales management server system 10. In other words, a user ID is given to access the sales management server system 10. In addition, as the user 3, in addition to the end user, an intermediate operator such as a system integrator and a specialized operator such as a machine tool manufacturer may also be included.

[0151] like Figure 2C As shown, the user storage unit 122 stores the user name, user information, edge server information, etc. in correspondence with the user ID.

[0152] The user ID is identification information for identifying a user.

[0153] As an example, user information may include the user's name, agent name, address, telephone number, email address, URL, user level, ordering authority, and other information related to the user. The user information is not limited to this. It may include a part of the exemplified data items and other data items. In addition, such user information is generated, for example, when the edge server is first set up for the user, and is updated thereafter, for example, whenever a situation related to a change in the user information occurs (for example, the addition of an edge server, etc.).

[0154] Here, the user level is determined by the attributes of the user. In the present embodiment, the user level is described in three stages from user level 1 (also referred to as "ch1") to user level 3 (also referred to as "ch3"). More specifically, user level 1 (ch1) indicating an end user, such as a sales store, user level 2 (ch2) indicating a specialized operator (middle operator) including a system integrator, and user level 3 (ch3) indicating a specialized operator (middle operator) including a machine tool manufacturer, an equipment manufacturer, etc. are exemplified. In the following description, user level 2 is referred to as a lower-level middle operator, and user level 3 is referred to as an upper-level middle operator.

[0155] In addition, the ordering authority is information for identifying whether the user (specialized business (intermediary business) or end user) identified by the user ID is allowed to directly make a purchase request for the application to the sales management server system 10. Only when the user has the ordering authority, the user can directly make a purchase request for the application to the sales management server system 10.

[0156] The edge server information is information related to the edge server 400 installed in a factory or manufacturing site related to the user, especially when the user is an end user, and is information that specifies the edge server 400 that is the distribution destination of the application. As described above, the edge server 400 is installed in the area provided by the application sales management system 1000. As an example, the edge server information may include an edge server ID for identifying the edge server 400, the installation location of the edge server, and address information on the communication network such as the IP address of the edge server 400. In addition, when there are more than one edge server 400 in a factory related to the user, for example, the edge server ID is required to identify each edge server 400.

[0157] In addition, the edge server information may include information related to the edge device 500 that may perform input and output with the edge server 400 and become a candidate for entrustment of the edge server 400. The information related to the edge device 500 may include an edge device ID for identifying the edge device 500, a device type name of the edge device 500, an address of the edge device 500 on the communication network (for example, an IP address), and the like.

[0158] In addition, the edge server information is not limited thereto and may include a part of the exemplified data items and other data items.

[0159] <Publishing management storage unit 124>

[0160] The distribution management storage unit 124 included in the storage unit 120 of the management server 100 is a storage area that stores distribution management information on an application distributed to an arbitrary edge server 400 (or an application sold face-to-face) in association with the edge server 400 of the distribution destination.

[0161] like Figure 2CAs shown, the publishing management storage unit 124 associates the published application information with the edge server 400 of the publishing destination and stores it. The publishing management storage unit 124 stores, for example, a publishing management record, which uses the edge server ID of the edge server 400 that identifies the publishing destination and the application ID that identifies the published application as search keywords, and uses data including the edge server ID of the edge server 400 of the publishing destination and the application ID of the published application as search keywords (compound keywords). In the publishing management record, as an example, in addition to the above-mentioned search keywords, the product name, order number, order date and time, serial number (license key), license, purchase date (license acquisition date), and publishing date of the published application are also stored. In addition, although not shown in the figure, data for managing the published application, such as the next contract renewal date, the next contract renewal notification date, the next contract renewal notification destination address, and the notification completion mark, can also be stored. In addition, the data included in the publishing management record is not limited to this. It can also include a part of the data items illustrated and other data items.

[0162] The order number is, for example, a number for managing the processing status (processing state) from the acceptance of the purchase request for the application from the user 3 to the release of the application.

[0163] The order date and time is the date and time when the purchase request for the application is received from the user 3.

[0164] The serial number (license key) is the serial number corresponding to the purchased application.

[0165] The license is related to the license of the application issued to the edge server 400, for example, information related to the edge device 500 that allows connection and / or input and output with the application.

[0166] The purchase date is the date on which the serial number of the application is notified (ie, the date on which the user acquires the license).

[0167] The release date is the date when the application is released to the edge server 400 .

[0168] The next contract renewal date is the next scheduled contract date when the current license contract is extended to continue the contract.

[0169] The next contract renewal notification date is a candidate date for sending a confirmation notification to the purchaser of the application and / or the user of the license destination of the application whether to extend the current license contract and continue the contract.

[0170] The next contract update notification destination address is, for example, the address of the terminal 600 of the purchaser of the application and / or the user of the license destination of the application and / or the email address of the purchaser of the application and / or the user of the license destination of the application.

[0171] The notification completion flag is a flag indicating whether a confirmation notification of whether to extend the current license contract and continue the contract has been made to the purchaser of the application and / or the user of the license destination of the application. If the notification has been made, the flag is set to on, for example, to indicate that the notification has been completed.

[0172] In this way, according to the published application, it is possible to easily retrieve which edge server 400 the application is in, when the purchase request was received, when it was published, and also when the contract renewal date of the application in the edge server 400 is reached.

[0173] <Application developer information storage unit 125>

[0174] The application developer information storage unit 125 stores application developer information including application developer name, nationality (region), address, URL, contact destination email address, etc. in association with the application developer ID. Alternatively, the application developer information may be managed as application developer information included in the application management information storage unit 121 .

[0175] <Order Status Management Information Storage Unit 126>

[0176] The order status management information storage unit 126 stores order status management information for managing, when a purchase request for an application is received from the user 3, a processing status and a processing result related to the purchase request from the time the purchase request for the application is received.

[0177] The order status management information may correspond to the order number, and may include, for example, the order date and time, the application ID of the order, the application name (product name), the user ID of the order destination (i.e., the person who ordered the application), the approval status, the publishing status, the application developer ID, etc. Here, the approval status and the application developer ID are generated when the application developer needs to conduct a customer check when the application is sold.

[0178] The approval status is management information for managing the customer check status of whether the order destination of the application is a customer of interest when selling the application, when the application developer belongs to a region other than the region to which the sales management server system 10 belongs (for example, Japan). Here, the approval status may include, for example, approval not required (a state in which customer check is not required), unapproved (i.e., a state in which customer check is in progress), approved (a state in which the application is determined to be a customer of interest as a result of customer check), rejected (a state in which the application is determined to be a customer of interest as a result of customer check), etc.

[0179] In addition, when approval is not required or has been approved, the order processing unit 112 can complete the purchase procedure for the user 3 through, for example, an email, as described later. In addition, in the case of rejection, the order processing unit 112 can notify the user 3 that the purchase is not allowed through, for example, an email, as described later.

[0180] In addition, for order status management information, for example, an identification mark can be set, and a symbol for identification can be set for part of the order number so that the application developer of the application can identify whether a customer inspection is required or not. In this way, order status history information related to orders that require (have been) customer inspection by the application developer can be easily extracted.

[0181] In addition, the order status management information can be created only when the application developer of the application does not belong to the region. In addition, the data included in the order status management information is not limited to this. It can also include part of the exemplified data items and other data items.

[0182] <Published data storage unit 224>

[0183] like Figure 2D As shown, the storage unit 220 of the publishing server 200 has a publishing data storage unit 224. The publishing data storage unit 224 is a storage unit set up to publish applications requested by users to purchase. The publishing data storage unit 224 can correspond to the serial number (license key) of the published application, and includes the published application ID, product name, application program, access declaration list, license, user ID of the user who requested to purchase, ID of the edge server 400 of the publishing destination and the address on the communication network such as the IP address, etc.

[0184] In addition, the distribution data storage unit 224 does not need to include the application program itself, and may be distributed from the application DB 250 by the distribution processing unit 214 described later.

[0185] <Application of DB250>

[0186] Figure 2E2 is a diagram showing an example of application DB 250. Figure 2E As shown, in the application DB 250, applications registered for sale in a store in a region (e.g., the United States) are stored in correspondence with the application ID. Specifically, by the application registration unit 313 described later, applications developed by application developers are registered together with the access declaration list as applications that meet the prescribed conditions in the operation and management enterprise 2. In addition, the product name of the application, the manual of the application, the manual related to the license of the application, and the version number of the application may also be appropriately registered.

[0187] In addition, in order to register applications (hereinafter also referred to as "third-party applications") developed by application developers (hereinafter also referred to as "third-party applications") in countries outside the region (such as Japan) as applications that can be sold in stores in application DB250, and to have the application developers implement compliance / non-compliance judgments with export control laws of countries outside the region (such as Japan), a compliance / non-compliance judgment list including the nationality, name, export control regulations judgment results (completed / not required), etc. of the application developer is registered together with the compliance / non-compliance judgment sheet.

[0188] Regarding third-party applications stored in the application DB 250, the applications that are determined to be non-compliant and the applications that are determined to be compliant are basically limited to applications that have obtained export license trade management approval for whitelist countries. Therefore, applications that are determined to be compliant cannot be sold in stores in non-whitelist countries and cannot be registered in the application DB 250.

[0189] The application DB 250 may be included in the distribution server 200. For example, the application DB 250 may be included in the storage unit 220. In addition, the application DB 250 may be provided as a DB server separately from the distribution server 200.

[0190] In addition, it is preferable that the application DB 250 is installed in the region for the following reason.

[0191] The description is based on an example in which the third party's country of residence is Japan and the region where the app is sold in the store is the United States, but the same applies to situations other than this combination.

[0192] Assume that when the application DB 250 is deployed in Japan, the export control regulations apply to each application stored in the application DB 250 when it is released to a user in the U.S. In this case, each time a third party releases an application to a user in the U.S., it will always be necessary to obtain an export license from the Ministry of Economy, Trade and Industry when determining compliance / noncompliance and compliance / noncompliance, which makes the procedure very complicated for the third party.

[0193] Furthermore, when an application developed by an application developer residing in the United States is stored in application DB250, it complies with export from the United States to Japan. Conversely, when an application stored in application DB250 is released to users in the United States, it complies with export from Japan to the United States. Export licenses from both the United States and Japan are required, which becomes a very complicated process. In order to avoid this, the U.S. law requires that the endpoints of applications developed by developers in the United States be encrypted. Therefore, considerable development funds are required due to the correspondence of endpoint encryption, which is unpopular. Furthermore, due to the correspondence of endpoint encryption, the extraction of applications through application DB250 set in Japan is not applicable to import and export in the United States. For example, in whitelist countries, such as European countries or South Korea, even if the endpoint is encrypted, the extraction of applications through application DB250 set in Japan is judged to comply with import and export. Therefore, the correspondence of endpoint encryption has become an extremely exceptional solution that cannot be applied to countries other than the United States, which is unreasonable.

[0194] On the other hand, when the application DB 250 is set up in the United States, there will be no import or export problem in the United States for extracting applications developed by U.S. developers through the application DB 250. In addition, even in the case of exporting from Japan, it is most appropriate to apply the export control regulations (compliance / non-compliance judgment and the need for export license when compliance) only when the application DB 250 set up in the United States is set to a state that can be sold in stores.

[0195] For the above reasons, it is preferable to set the application DB 250 in the United States outside of Japan. In this embodiment, at least the configuration in which the application DB 250 is set in the region is described as an embodiment. In addition, when the publishing server 200 has the application DB 250, the publishing server 200 is set in the region. In addition, when the application DB 250 is a DB server physically different from the publishing server 200, the DB server is set in the region.

[0196] In addition, as described above, the management server 100 is, for example, an independent virtual server included in a specified server or a specified cloud that ensures a dedicated area corresponding to the region, and the management and operation of the virtual server ensured by the dedicated area corresponding to region n is performed by the operating management enterprise. Therefore, not only within the region, but also even if it is set up in Japan, no import and export related problems will arise.

[0197] In the above, the storage unit 120 of the management server 100 , the storage unit 220 of the distribution server 200 , and the application DB 250 have been described as an example of the present embodiment.

[0198] Next, each functional unit of the control unit 110 and the control unit 210 in the management server 100 and the distribution server 200 will be described.

[0199] First, the functions related to the management server 100 and the publishing server 200 after the application is registered for store sales in a region (e.g., the United States) are explained, regardless of whether the application is developed by an application developer belonging to the region (e.g., the United States) or developed outside the region, such as by Japan.

[0200] like Figure 2A As shown, the management server 100 includes a browsing information providing unit 111 as a browsing information providing unit, an order processing unit 112 as an order processing unit, a sales approval processing unit 113 as a sales approval processing unit, a publishing management processing unit 114 as a publishing management processing unit, and a contract update processing unit 115 as a contract update processing unit.

[0201] In addition, if Figure 2B As shown, the distribution server 200 further includes a distribution processing unit 214 as a distribution processing unit.

[0202] Furthermore, in the case of an application that is not sold in a store but requires face-to-face sales, information to that effect may be provided in the browsing information providing unit 111 as described later.

[0203] <Browsing information providing unit 111>

[0204] The browsing information providing unit 111 has a browsing information providing function and a sales price information providing function.

[0205] More specifically, the browsing information providing unit 111 provides the application information (application product information) that can be browsed by the user 3 in response to a browsing request for application information (application product information) received from the terminal 600 from the user 3 .

[0206] The browsing information providing unit 111 may refer to the application management information storage unit 121 , extract application product information related to the application (general application 171 ) provided to all registered users, and provide the information to the terminal 600 .

[0207] At this time, the browsing information providing unit 111 refers to the customer check information stored in the application management information storage unit 121, and if the application developer needs to perform a customer check when selling the application in a store, provides information to that effect.

[0208] [View price information]

[0209] Furthermore, the reading information providing unit 111 can provide price information corresponding to the user level preset for the user 3 in response to the inquiry or reading of the price information (application sales price information) for the application received from the terminal 600 from the user 3. Specifically, only the end-user price information is provided to the end user, and the end-user price information and the wholesale price information for the specialized operators (intermediary operators) are provided to the specialized operators (intermediary operators). Therefore, the reading information providing unit 111 refers to the user storage unit 122 to confirm the user level of the user for the user ID included in the received reading request.

[0210] Furthermore, the browsing information providing unit 111 generates a browsing screen 160 including the extracted application information and the price information of the application corresponding to the user's level, and provides it to the terminal 600. In addition, when a plurality of applications are extracted, the browsing information providing unit 111 may generate an application list screen and send it to the terminal 600. Furthermore, when a selection related to one application is received from the terminal 600, the browsing information providing unit 111 extracts information related to the selected application from the application management information storage unit 121 and generates the browsing screen 160.

[0211] Figure 3 This is a diagram showing an example of a browsing screen displayed on the terminal in the present embodiment.

[0212] like Figure 3 As shown, the browsing screen 160 may include, for example, an application ID 161a, an application product name 161b, an application developer 162, whether the application developer needs to conduct a customer check 163 when selling the application in a store, an application manual 165, and a manual 166 related to the application license. The manual 166 includes extracted price information 166a, license quantity 166b, license description information 166c, and an edge server ID designation unit 166d, which are summarized and provided as information related to the license. Since the license-related manual 166 is included in the browsing screen 160, each user can confirm the required license-related information.

[0213] The browsing screen 160 may also serve as an ordering screen, and in this case, the license quantity 166b and the edge server ID designation portion 166d may be displayed to facilitate ordering.

[0214] In addition, the reading information providing unit 111 can display a purchase button or the like on the reading screen 160 so that the user with ordering authority can place an order. In addition, when the user selects an application as a purchase candidate during the user's browsing of applications, for example, the reading information providing unit 111 stores the selected application ID or the like in a temporary storage purchase candidate storage unit (so-called "shopping cart") (not shown). Furthermore, the reading information providing unit 111 displays the reading screen 160 as an ordering screen in response to a designation from the user, and the reading screen 160 displays a purchase button or the like for ordering the application ID (product name) stored in the purchase candidate storage unit (shopping cart) (not shown) for each application or in a lump sum.

[0215] In addition, when a purchase button or the like is displayed, it is preferable to display whether or not the application developer needs to conduct a customer check when the application is sold in the store for each application.

[0216] <Order Processing Unit 112>

[0217] The order processing unit 112 has a customer checking function, a distribution permission notification function, and an order screen output function.

[0218] In response to receiving a purchase request for an application from a user with ordering authority from the terminal 600, the order processing unit 112 generates an order number for each application requested for purchase, and for example, generates an order status management information record including the order date and time, the application ID of the order, the application name (product name), the user ID of the order destination (i.e., the person who ordered the application), etc. In addition, the payment of the fee for the application requested for purchase is confirmed by a known method (e.g., credit card, automatic account deduction, etc.).

[0219] When the order case has been approved (or approval is not required), the order processing unit 112 generates a serial number (license key) of the application corresponding to the purchase request, and passes the order processing data including the application ID and the edge server ID of the edge server 400 that becomes the publishing destination, and the serial number (license key) to the publishing processing unit 214 of the publishing server 200 described later.

[0220] Therefore, the order processing unit 112 determines whether the third party (application developer) needs to perform a customer check when the store sells the application requested to be purchased. If it is determined that the third party (application developer) needs to perform a customer check for the application requested to be purchased, the user is notified via the terminal 600 that the approval of the application developer is waiting. Figure 4 An example of a screen displaying the application developer's approval is shown.

[0221] like Figure 4As shown, as an example of the text notified to the user, "The product you ordered requires the approval of the development source company. When approved, the serial number required for publishing the purchased product will be given. After approval, an email will be sent, so please continue to complete the purchase procedure (approval confirmation)", but it is not limited to this. As long as the language is clear that waiting for approval does not complete the purchase, the result of approval will be contacted later, and the purchase procedure will be completed after approval (approval confirmation). In this way, the order processing unit 112 can extend the order status management information of the application to the sales approval processing unit 113 described later.

[0222] When it is determined that customer inspection is not required when the store sells the application requested to be purchased, the order processing unit 112, after confirming the payment of the purchase fee from the user, generates a serial number (license key) of the application requested to be purchased corresponding to the edge server ID of the edge server 400 that is the publishing destination of the application and the number of edge devices 500 that are the entrusted objects, creates order processing data including the application ID and the edge server ID of the edge server 400 that is the publishing destination, and the serial number (license key), notifies the user of the serial number (license key) of the application requested to be purchased, and extends the order processing data to the publishing server 200 (publishing processing unit 214).

[0223] In addition, the order processing unit 112 may send an email containing an ID and a password for registering to a dedicated screen (not shown) displaying the serial number (license key) of the application to the user who has made a purchase request for the application as information related to permission to be released. In this way, after the dedicated screen is displayed, when the user registers using the ID and password recorded in the email, the order processing unit 112 can display the serial number (license key) on the dedicated screen. Thus, even if a third party pretends to be a third party and uses the terminal 600 of a user with ordering authority, the serial number is not notified to the third party, and the structure with improved security can be used.

[0224] A case will be described in which it is determined that customer inspection is necessary, and the order matter transferred to the sales approval processing unit 113 is approved by a third party (application developer) in the sales approval processing unit 113 described later, and then transferred to the order processing unit 112.

[0225] Similar to the above, after confirming the payment of the purchase fee from the user, the order processing unit 112 generates a serial number (license key) of the application requested to be purchased corresponding to the edge server ID of the edge server 400 that is the publishing destination of the application, the number of edge devices 500 that are the entrusted objects, etc., and creates order processing data including the application ID, the edge server ID of the edge server 400 that is the publishing destination, and the serial number (license key).

[0226] Specifically, the order processing unit 112 sends an email (also referred to as an "approval email"), etc., to the contact destination (e.g., email address) of the user who requested to purchase the application, for notifying the application developer that the customer inspection is completed (approved). In addition, the email is preferably a PUSH-type email. After confirming the payment of the purchase fee from the user, the order processing unit 112 generates a serial number (license key) for the application, creates order processing data including the application ID, the edge server ID of the edge server 400 that becomes the publishing destination, and the serial number (license key), and transmits it to the publishing server 200 (publishing processing unit 214).

[0227] Furthermore, when the purchase of the application has been approved (or approval is not required), the order processing unit 112 can send the ID and password for registering to the order screen for completing the purchase procedure of the application to the user who requested the purchase of the application, for example, in response to the approval email, in the same manner as described above. In this way, after the dedicated screen is displayed, when the user registers using the ID and password recorded in the email, the order processing unit 112 can display the serial number (license key) on the dedicated screen.

[0228] Furthermore, when the order case that is passed to the sales approval processing unit 113 and rejected by the application developer in the sales approval processing unit 113 as requiring customer inspection is passed to the order processing unit 112, the order processing unit 112 sends an email (also referred to as a "rejection email") or the like to the contact destination (e.g., email address) of the user who requested the purchase, notifying that the purchase of the application is rejected and the purchase procedure is completed. Thus, the processing related to the order case is completed.

[0229] <Sales Approval Processing Department 113>

[0230] The sales approval processing unit 113 provides, for example, an approval status management function (visualization of approval processing status) to application developers.

[0231] The sales approval processing unit 113 provides product order history information and a management screen for product sales approval management to the application developer based on the order status management information generated by the order processing unit 112 in association with the order number of the application.

[0232] When the sales approval processing unit 113 inherits the order status management information from the order processing unit 112, it sends an email or the like notifying the third party (application developer) of the order order and requiring the approval of the third party (application developer) to the contact destination of the third party (application developer). Specifically, the sales approval processing unit 113 obtains the contact destination email address or the like by referring to the application developer information storage unit 125 based on the application developer ID included in the inherited order status management information, and can send the above email or the like to the email address destination. In addition, the email is preferably a PUSH type email. In addition, as the contact destination, the application developer or its agent is registered in advance.

[0233] In addition, an email containing a URL for displaying the order status management screen described later may also be sent. In this way, the third party (application developer) or its agent can access the URL via a terminal (not shown) owned by the third party (application developer) or its agent, thereby quickly displaying the order status management screen related to the application developed by the application developer (after user authentication).

[0234] The sales approval processing unit 113 provides a user interface for confirming a product order (hereinafter also referred to as an "order status management screen") to a terminal (not shown) owned by the third party (application developer) or its agent in response to a request from the third party (application developer) or its agent. Specifically, the sales approval processing unit 113 extracts all order status management information related to the application developer ID based on the application developer ID included in the order status management information stored in the order status management information storage unit 126, and displays the order status of the application in a list format including its history, for example, by sorting the order status in order of order date and time.

[0235] Figure 5A An example of an order status management screen 1130 provided to a third party (application developer) or its agent is shown.

[0236] like Figure 5A As shown, the order status management screen 1130 provided to the third party (application developer) or its agent can include its historical records, for example, it can display the order status of all applications that will need (and have needed) the application developer to conduct customer inspection in a list form. In addition, when it is impossible to display all the order status management information on one screen, such as Figure 5AAs shown, by pressing the sequence number of the screen by a third party (application developer) user, other screens can be displayed. In addition, the pressing operation of the sequence number of the screen can be converted to a scrollable display.

[0237] As an example, the order status management screen 1130 may include the third party (application developer)'s order number 1131, order date and time 1132, product name 1133, order destination (ordering company code) 1134, approval status bar 1135, operation bar 1136, and a search condition input bar 1137 for searching order status management information.

[0238] A company information display button 1134a may be displayed in the order destination (ordering company code) column 1134. In this way, in response to the application developer pressing the company information display button 1134a, the sales approval processing unit 113 can access the user information 1134b related to the user (order destination) stored in the user storage unit 122. Figure 5B This shows an example of user information 1134b related to the user (order destination) being prompted via a pop-up screen. Figure 5B As an example of the user information 1134b presented, an example of displaying the enterprise code 1134b1, enterprise name 1134b2, enterprise representative 1134b3, and address 1134b4 is shown, but it is not limited to this. Any information can be displayed as the user information 1134b. In addition, as the user information, when an edge server is set up at the manufacturing site of the user, user information registered by the operation management enterprise 2 can be provided.

[0239] In the approval status column 1135, the third party (application developer) inputs the following statuses: Not Approved (under customer confirmation), Approved (customer confirmation of a customer other than the customer of interest), Rejected (customer confirmation of the customer of interest), and Approval Not Required (customer inspection not required) are statuses entered by the third party (application developer) based on the progress of the customer inspection.

[0240] In order to assist the input operation of the third party (application developer), when the approval status of the order case is not approved, an approval button 1136a and a rejection button 1136b can be displayed in the operation bar 1136. In this way, the third party (application developer) can easily confirm the case waiting for customer inspection, and by displaying the approval or rejection button operation (such as pressing operation, clicking operation, etc.) in the operation bar 1136, the customer inspection result can be easily input. By the application developer pressing (or clicking) the approval button 1136a, as described later, the person requesting to purchase the application can complete the purchase procedure of the application (commodity) and obtain the serial number of the application. In addition, when approval is not required, the person requesting to purchase the application can also complete the purchase procedure of the application (commodity) as described later, and the serial number of the application can be obtained.

[0241] On the contrary, by the third party (application developer) pressing (or clicking) the rejection button 1136b, the person who requested to purchase the application is determined to be a concerned customer, and it is decided that the application (product) cannot be purchased, and the purchase procedure is terminated.

[0242] More specifically, when the third party (application developer) presses (or clicks) the approval button 1136a, the sales approval processing unit 113 records "approved" in the approval status column 1135 of the order status management information, and the order status management information of the application is transferred to the order processing unit 112. Similarly, when the third party (application developer) presses the rejection button 1136b, the sales approval processing unit 113 records "rejected" in the approval status column 1135 of the order status management information, and the order status management information of the application is transferred to the order processing unit 112.

[0243] By doing so, as described above, the order processing unit 112 can restart the order processing corresponding to the order number.

[0244] In addition, although not shown in the figure, the order status management screen 1130 may include a publishing status column. The publishing status column is a status input by the publishing processing unit 214 according to the publishing progress status. For example, according to the publishing progress status, the serial number may be input as not sent, the serial number may be sent, not published, published, etc. In addition, the serial number sending date and the publishing date may be included. In this way, a third party (application developer) or its agent can confirm the approved publishing status.

[0245] The search condition input field 1137 can provide a pop-up screen 1137a for inputting search conditions by, for example, performing a click operation. Figure 5C This shows an example of a search condition input field. Figure 5CAs shown, an input column 1137b for the order destination (ordering company), an input column 1137c for the product name, an input column 1137d for the order number, an input column 1137e for the order date and time range, an input column 1137f for the approval status, and a screen for performing a compound search combining multiple conditions (AND or OR) based on these conditions can be provided. In addition, a company search button 11371 is a button for searching for a designated company in the input column of the ordering company, and a search button 11372 is a button for performing a compound search.

[0246] In addition, the sales approval processing unit 113 can provide, for example, a function of searching / inquiring the order status management information stored in the order status management information storage unit 126 via the operation management terminal (not shown) for the manager of the operation management company 2. In this way, the manager of the operation management company 2 can also confirm (visualize) order cases in an unapproved state, for example.

[0247] <Publishing Processing Unit 214>

[0248] The publishing processing unit 214 of the publishing server 200 extracts the corresponding application from the application DB 250 based on the order processing data inherited from the management server 100 (order processing unit 112), creates publishing data, and stores it in the publishing data storage unit 224. Here, the publishing data corresponds to the serial number (license key), and includes the application ID to be published, the product name, the license, the user ID of the user who requested the purchase, the ID of the edge server 400 of the publishing destination, and the address on the communication network such as the IP address, etc.

[0249] When the publishing processing unit 214 receives the serial number (license key) and the application publishing request from the user who purchased the application via the terminal 600, it determines the application ID to be published and the edge server 400 of the publishing destination based on the serial number (license key) and refers to the publishing data storage unit 224, and publishes the application from the application DB 250 to the edge server 400 of the publishing destination. More specifically, in response to the application publishing request from the user received from the terminal 600, the publishing processing unit 214 determines the application to be published, the license, and the edge server 400 that publishes the application from the serial number (license key), and publishes the license and the application obtained from the application DB 250 based on the application ID corresponding to the serial number (license key) to the determined edge server 400. Here, the so-called license is, for example, the use permission information related to the edge device 500 that becomes the client of the application (i.e., the connection and / or input / output object). The license can also be included in the application and published to the edge server 400. In addition, the license can also be published to the edge server 400 separately from the application.

[0250] In this way, the user can download the purchased application to the determined edge server 400 .

[0251] In this way, the publishing processing unit 214 determines the application and the edge server 400 based on the serial number (license key) included in the publishing request, so only a specific user who can know the serial number can make a publishing request. In other words, even if a third party makes a publishing request, the application will not be published because the serial number is unknown. In addition, the serial number determines the edge server 400 that becomes the publishing destination of the application, so even if the third party knows the serial number, it cannot publish the application to a server other than the determined edge server 400.

[0252] The publishing processing unit 214 associates the published application information with the edge server 400 of the publishing destination, generates publishing management information related to the published application, and transmits it to the management server 100 (publishing management processing unit 114). Here, the publishing management information includes the edge server ID of the edge server 400 of the publishing destination and the application ID of the published application as a search keyword (compound keyword), for example, the product name, order number, serial number (license key), license, purchase date (license acquisition date), and publishing date of the published application.

[0253] In addition, the posting processing unit 214 can provide, for example, a manager of the operating and managing company 2 with a function of searching / inquiring the posting data stored in the posting data storage unit 224 via an operation management terminal (not shown).

[0254] <Publishing Management Processing Unit 114>

[0255] The release management processing unit 114 manages the release management information of the application program.

[0256] The publishing management processing unit 114 inherits the publishing management information from the publishing processing unit 214, and stores the published application information in association with the edge server 400 of the publishing destination. As described above, the publishing management processing unit 114 stores, for example, a publishing management record in the publishing management storage unit 124, wherein the publishing management record uses the edge server ID of the edge server 400 of the publishing destination and the application ID of the published application as search keywords, respectively, and uses data including the edge server ID of the edge server 400 of the publishing destination and the application ID of the published application as a search keyword (compound keyword).

[0257] The publishing management processing unit 114 provides, for example, a function of searching / inquiring the publishing management records stored in the publishing management storage unit 124, for the administrator of the operating and managing enterprise 2, via the operation management terminal (not shown). In this way, it is possible to easily search for the edge server 400 to which the application is published, and also for information such as when the contract renewal date of the application is in the edge server 400, for each published application.

[0258] Furthermore, information such as which application has a contract renewal date and when among the applications published to the edge server 400 can be easily retrieved for each edge server 400. Furthermore, a confirmation notification of the contract renewal of the application can be made for each application and / or each edge server 400 with respect to the next contract renewal notification destination address (e.g., terminal 600 and / or email address, etc.) on the next contract renewal notification date before the next contract renewal date.

[0259] <Contract update processing unit 115>

[0260] The contract update processing unit 115 has a function corresponding to a contract update notification unit.

[0261] The contract update processing unit 115 refers to the release management storage unit 124, and notifies the purchaser of the application and / or the user of the license destination of the application, for example, for contract update of the application downloaded to the edge server 400. In addition, the terminal notified by the contract update processing unit 115 may be the terminal 600 owned by the purchaser of the application and / or the user of the license destination of the application, or may be another terminal (for example, a portable terminal, etc.) owned by the purchaser of the application and / or the user of the license destination of the application. In addition, the notification method may be, for example, displayed on a menu screen, or may be performed by e-mail, etc.

[0262] More specifically, the contract renewal processing unit 115 refers to the release management storage unit 124 at a predetermined time (e.g., once a week or once a month) to extract the edge server ID and application ID of the edge server 400 whose next contract renewal notification date has arrived and which has not been notified by the notified flag.

[0263] The contract renewal processing unit 115 notifies the purchaser of the application and / or the user of the license recipient of the application that the contract renewal of the application corresponding to the application ID is required.

[0264] Therefore, the contract renewal processing unit 115 can prevent the user's contract renewal from being leaked, and can make the user not forget to renew the contract.

[0265] Furthermore, when the license is updated, if the application developer is required to perform a customer check when selling the application in a store, the application developer may perform a customer check process similar to the process at the time of ordering.

[0266] The above describes the functions related to the management server 100 and the publishing server 200 after the application is registered for store sales in a region (e.g., the United States), regardless of whether the application is developed by an application developer belonging to the region (e.g., the United States) or developed outside the region, such as Japan.

[0267] The above describes the functional blocks included in the sales management server system 10 corresponding to a region (e.g., the United States) after the application is registered for store sales in the region, regardless of whether the application is developed by an application developer belonging to the region (e.g., the United States) or developed outside the region, such as Japan.

[0268] Next, the processing flow of the sales management server system 10 will be described.

[0269] First, the flow of processing related to browsing of the application program will be described.

[0270] Figure 6 This is a flowchart showing an example of browsing information providing processing of the sales management server system 10 in this embodiment.

[0271] In order to browse the application information, each user operates the terminal 600 and registers with the sales management server system 10. Here, the registration is performed using a known method, for example, using the user's personal information or a password management file including an ID, password, etc., to perform user authentication and confirm that the user is a legitimate user. Then, the user selects browsing of the application from a menu screen (not shown) displayed on the terminal 600.

[0272] In step S10 , the management server 100 (browsing information providing unit 111 ) receives a browsing request transmitted from the terminal 600 .

[0273] In step S11 , the management server 100 (browsing information providing unit 111 ) provides the terminal 600 with a screen listing applications that the user 3 can browse.

[0274] In step S12, the application name (product name) designated by the terminal 600 is received.

[0275] In step S13, the management server 100 (browsing information providing unit 111) provides a display screen of application information (application product information) related to the specified application name with reference to the application management information storage unit 121. Here, the display screen of the application information (application product information) may display price information, whether a customer check is required for the application developer, a purchase button, etc.

[0276] In step S14 , the management server 100 (browsing information providing unit 111 ) receives an instruction from the user through the terminal 600 .

[0277] In step S15, the management server 100 (browsing information providing unit 111) determines the content of the instruction from the user. Figure 7 The process moves to step S20 shown. When a return instruction is given, the process returns to step S10. When an end instruction is given, the browsing information providing process ends.

[0278] Next, the process flow related to the purchase request of the application is described.

[0279] Figure 7 This is a flowchart showing an example of order processing for a purchase request from a customer by the sales management server system 10 in this embodiment.

[0280] In step S20, the management server 100 (order processing unit 112) generates an order number for the application requested for purchase based on the purchase request from the user, and creates an order status management information record.

[0281] In step S21, the management server 100 (order processing unit 112) determines whether a third party (application developer) needs to perform a customer check when the store sells the application requested for purchase. If necessary (yes), the process moves to step S22. If not necessary (no), the process moves to step S23.

[0282] In step S22, the management server 100 (order processing unit 112) guides the user via the terminal 600 to wait for the approval of the application developer, and continues the processing to the sales approval processing unit 113 ( Figure 8 Step S30 shown).

[0283] In step S23, the management server 100 (order processing unit 112) confirms the payment status of the purchase fee from the user. If the payment is confirmed (Yes), the process proceeds to step S24. If the payment cannot be confirmed (No), the order status management information is recorded as the waiting fee, and the process returns to step S23.

[0284] In step S24, management server 100 (order processing unit 112) generates a serial number (license key) for the application program requested for purchase, and creates order processing data including the application ID, the edge server ID of edge server 400 to be distributed, and the serial number (license key).

[0285] In step S25, management server 100 (order processing unit 112) notifies the user of the serial number (license key) of the application requested for purchase, and passes the processing along with the order processing data to distribution server 200 (distribution processing unit 214), thereby completing the order processing.

[0286] Next, for those that are determined to require customer inspection (from Figure 7 The processing flow related to sales approval of the order item which is continued to the sales approval processing unit 113 in step S22) described above will be described.

[0287] Figure 8 This is a flowchart showing an example of sales approval-related processing of the sales management server system 10 in this embodiment. In addition, in the following processing flow, the processing of prompting information related to the user (order destination) in response to pressing the company information display button and the query processing in response to the input of the search condition are omitted.

[0288] In step S30 , the management server 100 (sales approval processing unit 113 ) transmits an email or the like to notify the third party (application developer) of the product order and the need for the third party (application developer) to conduct a customer check, to the contact destination of the third party (application developer).

[0289] In step S31, in response to a request from a third party (application developer), the management server 100 (sales approval processing unit 113) provides a user interface (order status management screen) for confirming a product order to a terminal (not shown) owned by the third party (application developer) or its agent.

[0290] In step S32 , the management server 100 (sales approval processing unit 113 ) obtains the customer inspection result from a terminal (not shown) owned by a third party (application developer) or its agent via a user interface (order status management screen).

[0291] In step S33, the management server 100 (sales approval processing unit 113) determines the content of the customer's inspection result based on the pressed operation button. If the reject button is pressed, the process proceeds to step S34. If the approve button is pressed, the process proceeds to step S35.

[0292] In step S34, the management server 100 (sales approval processing unit 113) records the person who requested to purchase the application as a customer of interest, records "rejected" in the approval status column of the order status management information, and passes the order status management information of the application to the order processing unit 112. Fig. 9 In addition, as a modified example, the step S40 described above can be directly transferred to Fig. 9 The described step S41 is transferred.

[0293] In step S35, the management server 100 (sales approval processing unit 113) records "approved" in the approval status column of the order status management information, and passes the order status management information of the application to the order processing unit 112. Fig. 9 In addition, as a modified example, it is also possible to directly transfer to step S40. Fig. 9 The described step S42 is transferred.

[0294] Next, the flow of processing related to the continuation processing from the sales approval processing unit 113 of the application will be described.

[0295] Fig. 9 This is a flowchart showing an example of the process after the above-mentioned sales approval process of the sales management server system 10 in this embodiment.

[0296] In step S40, the management server 100 (order processing unit 112) determines whether the approval status column of the order status management information record inherited from the sales approval processing unit 113 is "approved" or "rejected". If it is "rejected", the process proceeds to step S41. If it is "approved", the process proceeds to step S42.

[0297] In step S41, the management server 100 (order processing unit 112) regards the user who requested to purchase the application as a customer of interest, and sends an email ("rejection email") or the like to the contact destination (e.g., email address) of the user who requested to purchase, notifying that the purchase of the application has been rejected and the purchase procedure has ended. The management server 100 (order processing unit 112) records the order status management information as rejected and ends the process. Thus, the process related to the order case ends.

[0298] In step S42, management server 100 (order processing unit 112) sends an email (also referred to as "approval email") or the like to notify the application developer that the customer review is complete (approved) to the contact destination (eg, email address) of the user who requested to purchase the application.

[0299] In step S43, the management server 100 (order processing unit 112) confirms the purchase procedure completion request from the user. If there is a purchase procedure completion request, Figure 7 The described step S24 is transferred.

[0300] Next, the process flow related to the distribution of the application is described.

[0301] Fig.10 This is a flowchart showing an example of the application distribution process of the sales management server system 10 in this embodiment.

[0302] In order to commission the publication of an application, for example, the user operates the terminal 600, selects the publication of the application from a menu screen (not shown) displayed on the terminal 600, enters the serial number of the application to be published to the edge server 400 on the transferred publication screen (not shown), and sends the publication request to the sales management server system 10.

[0303] In step S50 , the distribution server 200 (distribution processing unit 214 ) receives a distribution request for an application from the terminal 600 .

[0304] In step S51, the distribution server 200 (distribution processing unit 214) refers to the distribution data storage unit 224 based on the serial number included in the distribution request, and specifies the application and the edge server 400 that distributes the application.

[0305] In step S52 , the distribution server 200 (distribution processing unit 214 ) distributes the specified application to the specified edge server 400 .

[0306] In step S53, the distribution server 200 (distribution processing unit 214) sends a distribution completion message to the terminal 600 that sent the distribution request in response to the completion of distribution of the application to the edge server 400. Thereafter, the distribution server 200 (distribution processing unit 214) ends the processing of this part.

[0307] As described above, in the application sales management system 1000 , an application that is run by the edge server 400 can be purchased from the sales management server system 10 and downloaded.

[0308] At this time, when there is a purchase request for a third-party application from a customer, if the customer is not a focused customer, the developer of the application, ie, the third party, can quickly perform a customer check.

[0309] The process flow of the sales management server system 10 has been described above.

[0310] As described above, according to the sales management server system 10 as a corresponding overseas application sales management server system, which is an application store operated in an overseas country as a third country as recorded in this embodiment, after an application developed by a country other than Japan or the overseas country is registered for local store sales through the operating manager of the application store, that is, the operating management company 2 (specifically, for example, after being registered with the publishing server of the application sales management system), when there is a purchase request for the application from a customer, the application developer of the country other than Japan or the overseas country can quickly conduct a customer check. In addition, the user (customer) who purchases the application and the person in charge of the operating management company 2 can also grasp the progress status and results of the customer check conducted by the third party when the user requests to purchase the application and the customer check is required by the third party, and can realize the "visualization" of the progress status of the customer check for all related parties.

[0311] As described above, with respect to the present embodiment, in an application store provided in a third country (e.g., the United States), i.e., in the corresponding overseas application sales management server system 10, when it is determined through the management server 100 that an application requested to be purchased by a customer, i.e., a user residing in the third country, is a third-party application developed by a third party, a customer check request (whether it is a check of the customer of interest) is notified to the contact destination of the third party, and the customer check request is used to determine to the third party whether to approve the sale of the third-party application requested to be purchased by the user to the user.

[0312] Thus, the application developer, ie, the third party, who resides in a country other than Japan or a third country of the third-party application can quickly know the order of the third-party application.

[0313] Furthermore, the management server 100 may provide the order status management information to a terminal of a contact destination of the third party.

[0314] As a result, the third party can easily perform customer inspection management through its own responsibilities.

[0315] Furthermore, when the management server 100 determines that the application program requested to be purchased by the user who is a client residing in a third country is a third-party application developed by a third party, the management server 100 notifies the user via the user terminal that the approval of the third party is being waited for.

[0316] When the management server 100 obtains approval from the third party for the sale of the third-party application, it may notify the user that the sale of the third-party application has been approved.

[0317] When the management server 100 refuses the sale of the third-party application to the user through the third party, the management server 100 notifies the user of the refusal of the sale of the third-party application.

[0318] As a result, a customer or user residing in a third country can easily understand the customer review status (awaiting approval, approved, or rejected) performed by the third party after making a purchase request for a third-party application developed by the third party.

[0319] In addition, when the management server 100 obtains approval from a third party for the sale of a third-party application, it issues permission-to-release information, i.e., a serial number, for the user. The publishing server 200 responds to receiving the permission-to-release information, i.e., the serial number, from a user terminal owned by the user, and releases the third-party application corresponding to the permission-to-release information together with the license to the edge server.

[0320] Thus, a third-party application developed by a third party can be quickly installed on a customer edge server that does not correspond to the customer of interest.

[0321] In addition, it is preferable that the application DB storing the application registered for sale in the online store in the third country is set in the third country. As a result, the application developed by the developer living in the third country remains in the third country and is not subject to import and export management. Only the third-party application developed by the third party becomes subject to import and export management, and the operation related to import and export becomes easy.

[0322] On the other hand, the management server 100 is provided with physical hardware resources (e.g., servers or cloud) in Japan, as described later, and a dedicated region n is provided for each region n (n≥1) for the hardware resources. In the dedicated region n, the management server 100-n corresponding to the region n can be set as IaaS (Infrastructure as a Service). In this way, the maintenance work of the hardware resources as the infrastructure can be included, and the maintenance cost can be reduced. The details will be described later.

[0323] In addition, the third country is a whitelist country other than Japan, and the third party's country of residence can be set to a whitelist country other than Japan or the third country. Thus, the overseas application sales management server system 10 corresponding to the whitelist country can be universalized.

[0324] <Store registration server 300>

[0325] Next, the functions of the store registration server 300 as a store registration control unit in one embodiment of the application sales management system 1000 for registering applications for store sales in the sales management server system 10 will be described.

[0326] Specifically, the functional part (store registration server 300) of the application sales management system 1000 when registering an application developer belonging to a region (e.g., the United States) or an application developed by a third party for store sales in a region (e.g., the United States) (i.e., registering the application as being able to be published to a publishing server 200 set up in the region) is described.

[0327] As described above, in order to sell an application developed by a third party in a store through the sales management server system 10 in an overseas region (e.g., the United States), the third party needs to determine (compliance / noncompliance determination) whether the application complies with the export trade management order when exporting the application to the region. Therefore, the third party first needs to prepare a "compliance / noncompliance determination sheet".

[0328] When the application is judged as "non-compliant", there is no need to obtain permission for export trade management. The third party can submit an export management list, application, and access declaration list related to the application described later, which includes a compliance / non-compliance judgment letter and the nationality, name, and export management regulations judgment result (in this case, "non-compliant") of the third party (application developer) to the operating management enterprise 2.

[0329] When the application is judged as "compliant", when the region (i.e., the export destination from the third party) is a whitelist country (such as the United States), it is necessary to obtain export trade management permission (such as a special general comprehensive license in particular) from the export trade manager (e.g., economic and industrial officials). In this way, the third party can submit an export management list, application, and the access declaration list related to the application described later, which includes a compliance / non-compliance judgment letter and the nationality, name, export management regulations judgment result (in this case, "compliant") of the third party (application developer), and a backup of the export trade management license, etc., to the operation management company 2 belonging to the region.

[0330] In addition, when the export destination is a non-whitelist country, store sales (= inventory sales) of the application are generally not allowed, and face-to-face sales are required to sell the application (that is, obtaining export permission for the application each time).

[0331] The system that assists the operation of determining compliance / non-compliance of an application and applying for an export license of the application by a third party is well known to those skilled in the art. The store registration server 300 for registering the application for store sales in the sales management server system 10 in this embodiment is not an operation that assists the operation of determining compliance / non-compliance of an application and applying for an export license of the application by a third party. The third party applies well-known technology to appropriately determine compliance / non-compliance of an application and apply for an export license of the application.

[0332] Based on the above, the functional units of the store registration server 300 in the application sales management system 1000 will be described. Fig.11 It is a functional block diagram of the store registration server 300.

[0333] <Store registration server 300>

[0334] The store registration server 300 is a server that receives applications developed by application developers (application developers belonging to the region and third parties not belonging to the region) and access declaration lists for review, matches the approved applications with the access declaration lists, and registers them in the application DB 250. In addition, when the application developer is a third party, the store registration server 300 also matches the export management list with the application and registers it in the application DB 250.

[0335] like Fig.11 As shown, the store registration server 300 includes a control unit 310 , a storage unit 320 , and a communication unit 330 .

[0336] The control unit 310 is, for example, a CPU, and controls the store registration server 300 in a centralized manner by executing various programs stored in the storage unit 320 .

[0337] For example, the CPU executes a program for accepting applications, access declaration lists, compliance / non-compliance determination forms when the application developer is a third party, and processing of compliance / non-compliance determination lists (hereinafter referred to as "application acceptance processing"). In addition, the CPU also executes a program for reviewing accepted applications, access declaration lists, export management lists containing compliance / non-compliance determination forms and export management regulations determination results when the application developer is a third party (hereinafter referred to as "application review processing"). In addition, the CPU executes a program for registering the application to application DB250 based on the results of the application review processing (hereinafter referred to as "application registration processing"). In addition, the CPU executes a program for querying the registered application management information registered to application DB250 (hereinafter referred to as "registered application management processing").

[0338] In this way, by executing programs for application acceptance processing, application review processing, application registration processing, and registered application management processing, the CPU forms an application acceptance unit 311 as an application acceptance unit, an application review unit 312 as an application review unit, an application registration unit 313 as an application registration unit, and a registered application management unit 314 as a registered application management unit as a functional structure.

[0339] The application acceptance unit 311 accepts applications developed by application developers, access declaration lists related to the applications, and export management lists including compliance / non-compliance determinations and export management regulations determination results when the application developer is a third party. In addition, the application developer's country of residence and its name, the application's instructions, and the instructions related to the application's license can also be accepted. Here, the application acceptance unit 311 accepts applications, access declaration lists, and export management lists including compliance / non-compliance determinations and export management regulations determination results when the application developer is a third party via the network from a terminal that can be communicatively connected to the store registration server 300 (for example, a terminal set on the application developer or its agent side, or a management terminal that can be communicatively connected to the store registration server 300).

[0340] In addition, the application accepting unit 311 may also input and accept, via a predetermined input interface, a computer-readable recording medium storing an application program, an access declaration list, and an export control list including a compliance / non-compliance determination form and export control regulations determination results when the application developer is a third party. Here, the computer-readable recording medium includes, for example, a magnetic recording medium (e.g., a floppy disk, a magnetic tape, a hard disk drive), a magneto-optical storage medium (e.g., a magneto-optical disk), an optical disk (e.g., a CD-ROM, a DVD, a Blu-Ray Disc (registered trademark)), and other media known to those skilled in the art.

[0341] In particular, when the application developer is a third party, the application accepting unit 311 confirms that the accepted data contains an export management list, which includes a compliance / non-compliance determination form and an export management regulations determination result. When the application developer is a third party and the accepted data does not contain an export management list, for example, an error message may be returned, wherein the export management list includes a compliance / non-compliance determination form and an export management regulations determination result. In addition, the export management list including the compliance / non-compliance determination form and the export management regulations determination result may be set to a waiting acceptance state. In addition, the accepted data may not be accepted and a non-acceptance penalty may be imposed and returned.

[0342] The access declaration list is a list used when executing an application through an edge server, indicating whether the functions of the edge device are used and / or whether there is access to the processing data of the edge device. Specifically, the access declaration list indicates whether the functions related to the edge device 500 are used and / or whether there is access related to the processing data of the edge device 500. In addition, the so-called "manufacturing device" is a device that conforms to the edge device 500, and the application developer specifies CNC machine tools, industrial equipment, industrial robots, etc. In addition, the access declaration list is in a predetermined format, and the application developer sets it according to the format, for example, by checking whether there is access in a check box.

[0343] More specifically, as the processing data of the edge device 500, for example, there are data indicating the action status related to the edge device 500, data indicating the production status, data indicating the quality status of the product, data indicating events (history records) such as the operation status, etc. These processing data are pre-data-modeled (i.e., standardized), and it is possible to set whether there is access based on the data model obtained by such standardization. In this way, the application developer can accurately declare whether there is access based on the standardized model, and the application review side can standardize the review process by eliminating the arbitrary wording of the application developer. In addition, a standardized interface for accessing the processing data related to the edge device 500 can be provided.

[0344] The application review unit 312 reviews the application program received by the application reception unit 311 , the access declaration list, and the export control list including the compliance / non-compliance determination form and the export control regulations determination result when the application developer is a third party.

[0345] When reviewing the access declaration list, for example, the application review unit 312 can review the use of the edge device 500 function of the application and / or the access content of the processed data of the edge device 500, and whether the access is consistent with the access declaration list based on the analysis of the source code of the application. In addition, the application review unit 312 can also review the use of the edge device 500 function of the application and / or the access content of the processed data of the edge device 500, and whether the access is consistent with the access declaration list based on the analysis of the action related to the application executed by the edge server 400.

[0346] In addition, when the application developer is a third party, the application review unit 312 confirms that the application can be sold in stores in the region (for example, the United States) based on the export management list that includes the compliance / non-compliance determination form and the export management regulations determination result, and based on the need, the access declaration list. Specifically, for example, when the application developer is a third party, the application review unit 312 can display the export management list confirmation screen (not shown) on the terminal (not shown) of the manager (or person in charge) of the application review for the ID and product name of the application and the export management list, and based on the need, the access declaration list. In addition, the confirmation result that the application can be sold in stores can also be input to the manager (or person in charge). In this way, it is confirmed that the application can be sold in stores in the region (for example, the United States).

[0347] In the above description, an example is described in which, when the application developer is a third party, the application acceptance unit 311 accepts an application, an access declaration list, an export management list including a compliance / non-compliance determination form and export management regulations determination results, and the application review unit 312 reviews the application, the access declaration list, the export management list including a compliance / non-compliance determination form and export management regulations determination results, but the example is not limited to this.

[0348] For example, in the case where the application developer is a third party, the application review unit 312 first confirms whether the compliance / non-compliance determination form and the export control regulations determination result are suitable based on the application, the access declaration list, and the export control list including the compliance / non-compliance determination form and the export control regulations determination result. When it is confirmed to be suitable, the application review unit 312, for example, based on the analysis of the meta code of the application, examines whether the use of the edge device 500 function of the application and / or the access content to the processed data of the edge device 500 and whether there is any access consistent with the access indicated in the access declaration list. In addition, the application review unit 312 can examine whether the use of the edge device 500 function of the application and / or the access content to the processed data of the edge device 500 and whether there is any access consistent with the access indicated in the access declaration list based on the analysis of the action related to the application executed by the edge server 400.

[0349] When the result of the review by the application review unit 312 is that the use of the function of the edge device 500 and / or the access content to the processing data of the edge device 500 of the application is consistent with the access indicated by the access declaration list, and when it is determined that the application developer is a third party and the application can be sold in the store in the region (for example, the United States), the application registration unit 313 approves the release management of the application through the sales management server system 10. In addition, the application registration unit 313 associates the approved application, the access declaration list, and the export management list containing the compliance / non-compliance judgment form and the export management regulations judgment result when the application developer is a third party, and registers them in the application DB 250. The application registration unit 313 notifies the following content: the registration is performed via a terminal (for example, a terminal provided on the application developer side, or a management terminal connected to the store registration server 300) that can communicate with the store registration server 300, that is, the application is registered for store sales in the region (for example, the United States). In addition, the application registration unit 313 can use an email for notification.

[0350] The registered application management unit 314 provides an application registration management screen 3140 for searching registration management information on applications registered in a store in the application DB 250 . Fig.12 This shows an example of the application registration management screen. Fig.12As shown, on the application registration management screen, for a registered application, the registration date and time 3141, the name of the application developer 3142, the country of residence of the application developer 3143, the product name 3144, the export control regulations determination result of the country of residence 3145, the backup (link information) of the compliance / non-compliance determination sheet 3146, etc. are displayed. In addition, the items displayed on the application registration management screen are not limited to these. It is also possible to appropriately add items as needed.

[0351] In this way, the person in charge of the operation and management company 2 can easily confirm the registration status of the application registered in the store. In addition, although not shown in the figure, any item can be used as a search item, and the search can be performed by any search condition. For example, by specifying the range of registration date and time for search, it is possible to confirm the application registered in the store during that period. In addition, by specifying the country of residence of the application developer for search, it is possible to confirm the store registration status of the application developed by a third party residing in the specified country.

[0352] In the above, the functional blocks included in the store registration server 300 in the application sales management system 1000 have been described.

[0353] Next, the processing flow of the store registration server 300 in the application sales management system 1000 will be described. Fig.13 This is a flowchart showing an example of processing related to store sales registration by the store registration server 300 in this embodiment.

[0354] In the processing flow described below, in step S61, the application acceptance unit 311 of the store registration server 300 is exemplified as a process in which the data required for store sales registration is accepted from the terminal (not shown) of the application developer via the network, but the present invention is not limited thereto. As described above, for example, a computer-readable recording medium storing the data required for store sales registration can be input (accepted) to the store registration server 300 via a prescribed input interface by the person in charge of the operation and management enterprise 2. Here, the data required for store sales registration refers to the following data: at least including an application program, an access declaration list, and when the application developer is a third party (application developer), an export management list including a compliance / non-compliance determination form and an export management regulations determination result.

[0355] In addition, the application receiving unit 311 may receive (input) data from a computer-readable recording medium storing data required for store sales registration via a predetermined input interface instead of a network.

[0356] In step S60 , the store registration server 300 (application reception unit 311 ) receives (or inputs) data required for store sales registration from the application developer.

[0357] In step S61, the store registration server 300 (application receiving unit 311) determines whether the application developer is a third party. If the application developer is a third party (yes), the process proceeds to step S62. If the application developer is not a third party (i.e., resides in the region), the process proceeds to step S67.

[0358] In step S62, the store registration server 300 (application review unit 312) creates an export management list confirmation screen (not shown) based on the application ID, product name, export management list, and, if necessary, the access declaration list, and displays it on the terminal (not shown) of the administrator (or person in charge) of the application review.

[0359] In step S63, the store registration server 300 (application review unit 312) determines that the export management list is "compatible" via the terminal (not shown), and then moves to step S64. If it is determined that the export management list is "incompatible", the process moves to step S67.

[0360] In step S64, the store registration server 300 (application review unit 312) reviews whether the use of the edge device 500 function of the application and / or the access content to the processing data of the edge device 500 is consistent with the access indicated in the access report list. If it is determined to be consistent (yes), the process moves to step S65. If it is determined to be inconsistent (no), the process moves to step S67.

[0361] In step S65, the store registration server 300 (application registration unit 313) associates the application, the access declaration list, and the export management list including the compliance / non-compliance judgment form and the export management regulations judgment result when the application developer is a third party, and registers them in the application DB250.

[0362] In step S66, the store registration server 300 (application registration unit 313) notifies the application developer that the application has been registered for store sales in the region (eg, the United States) via a terminal or email, etc. After that, the store registration server 300 (application registration unit 313) ends the processing of this part.

[0363] In step S67, the store registration server 300 (application registration unit 313) notifies the application developer via a terminal or email that the application is determined to be not allowed to register for store sales in the region (e.g., the United States). After that, the store registration server 300 (application registration unit 313) ends the processing of this part.

[0364] The above is a description of the processing flow of the store registration server 300 in the application sales management system 1000.

[0365] As described above, the store registration server 300 in the overseas application sales management system recorded in this embodiment can easily confirm the compliance / non-compliance judgment form and trade management regulations judgment result related to the application when the operating management enterprise 2 performs local store sales registration for a third-party application developed by a third party through an application from a third party. The application that has been registered for store sales has been reviewed and approved, so high reliability is guaranteed.

[0366] As described above, with respect to the present embodiment, in the corresponding overseas application sales management system 1000 in which only the application registered for online store sales can be purchased in a third country (e.g., the United States), the store registration server 300, when registering for store sales a third-party application developed by an application developer residing in a country other than the third country, accepts the third-party application and an export management list including a compliance / non-compliance determination sheet and a result of a determination on trade management regulations for the third-party application; and when it is determined that the third-party application can be sold in stores in the third country, the third-party application and the export management list including a compliance / non-compliance determination sheet and a result of a determination on trade management regulations for the third-party application are matched and registered in the application DB 250.

[0367] Therefore, in the corresponding overseas application sales management system 1000 used and provided in a third country, when a third-party application developed by a third party is registered for local store sales through an application from the third party, the operating management enterprise 2 can easily confirm the compliance / non-compliance judgment and trade management regulations judgment results related to the third-party application.

[0368] When a third-party application performs store registration in a third country, the store registration server 300 notifies a contact destination of the third party that the store registration has been performed.

[0369] Thereby, the third party can easily grasp the store sales registration status of the third-party application that has applied for store sales registration.

[0370] The store registration server 300 provides the terminal (not shown) of the person in charge of the operation and management company 2 that operates the corresponding overseas application sales management system 1000 with registration management information related to the application registered in the store in the application DB 250. Specifically, the store registration server 300 matches all the applications registered for store sales, and provides registration management information such as the registration date and time of the application, the name of the application developer, the country of residence of the application developer, the product name of the application, the determination information of the export control regulations of the country of residence (completed or not required), and the backup of the determination book (link destination).

[0371] This allows the person in charge of the operation and management company 2 to easily grasp document information related to any application registered with the store.

[0372] In addition, the application DB storing the application registered for sale in the online store in the third country is preferably set up in the third country. As a result, the application developed by the developer living in the third country remains in the third country and is not subject to the import and export management. Only the third-party application developed by the third party becomes the subject of the import and export management, thereby facilitating the operation related to import and export.

[0373] The third country is a whitelist country other than Japan, and the third party's country of residence can be set to a whitelist country other than Japan or the third country. Thus, the overseas application sales management server system 10 corresponding to the whitelist country can be universalized.

[0374] Finally, the structure of the edge server 400 is briefly described.

[0375] Fig.14 4 is a functional block diagram of the edge server 400 in this embodiment.

[0376] The edge server 400 includes a control unit 410 , a storage unit 420 , and a communication unit 430 .

[0377] The control unit 410 is, for example, a CPU, and centrally controls the edge server 400 by executing various programs stored in the storage unit 420 and application programs downloaded from the sales management server system 10 .

[0378] In this embodiment, the control unit 410 includes an application execution unit 411 , a license control unit 412 , an access control unit 413 , and an illegal application notification unit 414 as functional units based on the application program stored in the storage unit 420 .

[0379] The application execution unit 411 executes the application program stored in the storage unit 420 in response to a request to start the application program.

[0380] The license control unit 412 controls the connection and / or input / output between the application and the edge device 500 according to the license associated with the application.

[0381] More specifically, when the application stored in the storage unit 420 is started by the application execution unit 411, the license control unit 412 reads the license corresponding to the application. The license control unit 412 determines the edge device 500 that is allowed to be entrusted as the input / output destination of the application based on the read license. More specifically, for example, the license control unit 412 determines whether the edge device 500 that makes a connection request to the application is a device that satisfies the conditions specified in the license based on the license.

[0382] When the edge device 500 satisfies the conditions specified in the license, the license control unit 412 permits a connection request to the application and controls input and output with the application.

[0383] When the edge device 500 does not satisfy the conditions specified in the license (for example, when the license is exceeded), the license control unit 412 rejects the connection request to the application and prohibits input and output with the application.

[0384] In this way, the license control unit 412 can control the connection and / or input / output between the application program issued to the edge server 400 and the edge device 500 according to the issued license.

[0385] The access control unit 413 monitors the use of the functions of the edge device 500 and / or the access to the processed data of the edge device 500 by the application program according to the contents of the access declaration list corresponding to the application program executed by the application execution unit 411. Furthermore, the access control unit 413 only permits the use of the functions related to the edge device 500 and / or the access to the processed data of the edge device 500 that are declared as having access through the access declaration list.

[0386] In addition, when the access control unit 413 detects a request to use the function of the edge device 500 that is declared as having no access through the access declaration list and / or an access request to process data of the edge device 500, it detects an illegal access request, displays an error message, an alarm, etc., and forcibly stops the application.

[0387] Furthermore, when receiving illegal information of an application from the sales management server system 10 , the access control unit 413 forcibly stops the application if the application is executed.

[0388] Furthermore, when the access control unit 413 detects an illegal access request or receives illegal information from an application, it is preferred that the application is not started thereafter.

[0389] When detecting an access request from an application program that violates the report in the access report list, the illegal application notification unit 414 notifies the sales management server system 10 that illegal access related to the application program has been detected.

[0390] The storage unit 420 stores the application program executed by the control unit 410. The storage unit 420 stores the application program itself distributed from the sales management server system 10 and the license related to the application program.

[0391] The communication unit 430 is a communication control element that transmits and receives data with an external device (for example, the sales management server system 10 ) via the network N1 , and transmits and receives data with the edge device 500 , etc. via the network N2 .

[0392] In this way, the edge server 400 monitors the use of the edge device 500's functions and / or the access to the processed data of the edge device 500 by the executed application according to the access declaration list, so that a structure that prevents illegal access can be set, which can further improve security.

[0393] The edge server 400 in the application sales management system 1000 has been described above.

[0394] Each of the devices included in the application sales management system 1000 can be implemented by hardware, software, or a combination thereof. Here, the term "implemented by software" means that a computer reads a program (application program) and executes it to implement it.

[0395] Various types of non-transitory computer readable medium can be used to store the program used in the present invention and provide it to the computer. Non-transitory computer readable medium includes various types of tangible storage medium. Examples of non-transitory computer readable medium include: magnetic storage medium (e.g., floppy disk, magnetic tape, hard disk drive), magneto-optical storage medium (e.g., optical magnetic disk), CD-ROM (Read Only Memory), CD-R, CD-R / W, semiconductor memory (e.g., mask ROM, PROM (Programmable ROM), EPROM (Erasable PROM), flash ROM, RAM (random access memory)). In addition, the program can be supplied to the computer via various types of transitory computer readable medium. Examples of transitory computer readable medium include electrical signals, optical signals, and electromagnetic waves. The transitory computer readable medium can supply the program to the computer via a wired communication path such as an electric wire and an optical fiber or a wireless communication path.

[0396] The above-described embodiment is a preferred embodiment of the present invention, but the scope of the present invention is not limited to the above-described embodiment, and the present invention can be implemented in various modified forms without departing from the spirit of the present invention.

[0397] [System Structure]

[0398] As a specific example, the management server 100, the distribution server 200, the store registration server 300, and the edge server 400 can be realized by incorporating a program (application program) for realizing the present embodiment into a general server.

[0399] In addition, the management server 100, the publishing server 200, and the store registration server 300 may be independent virtual servers included in a prescribed server or a prescribed cloud, etc.

[0400] Fig.15 is a diagram showing an example of server configuration. Fig.15 As shown, physical hardware resources (for example, servers or cloud) are set up in region 0 (zero), i.e., Japan. For hardware resources, a dedicated region n is set up according to region n (n≥1), and in the dedicated region n, the management server 100-n corresponding to region n is set as, for example, IaaS (Infrastructure as a Service).

[0401] This makes it possible to consolidate maintenance work using hardware resources as infrastructure, thereby reducing maintenance costs and the like.

[0402] In addition, it is preferable that the distribution server 200-n and the application DB 250-n are respectively installed in the region n in order to simplify the import and export management as described above.

[0403] also, Fig.15 Although the store registration server 300 - n is not shown in the figure, when the store registration server 300 - n physically receives an application for store registration, it is preferable that the store registration server 300 - n is respectively installed in the area n, similarly to the distribution server 200 - n.

[0404] In addition, as a hardware structure, a distributed system composed of the management server 100, the publishing server 200, and the store registration server 300 is exemplified, but it is not limited to this. For example, each functional unit included in each server can be distributed to the server in a manner that can communicate with each other. Distributed systems are well-known technologies to those skilled in the art, and those skilled in the art can appropriately implement decentralized functions as needed.

[0405] In the above-mentioned embodiment, an example in which a serial number (license key) is used as the issuance permission information is described, but the invention is not limited thereto. The issuance permission information may be information that permits the issuance of an application.

[0406] In the above-mentioned embodiment, various information is stored in the storage unit 120 of the sales management server system 10, but the various information in the storage unit is only an example and other information may be included. In addition, the method of storing data is only an example.

Claims

1. A server system for managing sales of overseas applications, which manages online store sales of applications run by an edge server in a third country, wherein the edge server is communicatively connected to one or more edge devices, the server system for managing sales of overseas applications corresponding to the third country, and characterized in that: The overseas application sales management server system is communicatively connected to the edge device installed in the third country and a user terminal owned by a user in the third country who uses the edge server via a communication network. The corresponding overseas application sales management server system has: An application DB storing the application program to be registered for online store sales; a management control unit that manages online store sales in which only the application programs stored in the application DB and registered for online store sales can be purchased; as well as a publishing control unit, which publishes the application to the edge server, The management control unit has: an order processing unit for determining whether the application requested to be purchased by the user in the third country via the user terminal is a third-party application developed by an application developer in a country other than the third country, that is, a third party; as well as A sales approval processing unit which, when it is determined by the order processing unit that the application requested for purchase is a third-party application developed by a third party, notifies the user in the third country via the user terminal that approval of the third party is being waited for, and notifies a contact destination of the third party of a customer check request, thereby obtaining a determination result of approval or rejection of the sale of the third-party application requested for purchase by the user in the third country to the user in the third country from the third party, and when the determination result is approval, enables the user in the third country to obtain approval of the sale of the third-party application, and when the determination result is rejection, enables the user in the third country to obtain rejection of the sale, wherein the customer check request is used to determine approval or rejection of the sale of the third-party application requested for purchase from the user in the third country to the user in the third country, and checks whether the user is included in a foreign user list, the foreign user list listing the names of foreign companies and organizations that are concerned that the exported goods or technologies will be used for the development and manufacture of weapons of mass destruction, biological weapons, chemical weapons, and carrier missiles.

2. The overseas application sales management server system according to claim 1, characterized in that: When the sales approval processing unit obtains the sales approval of the third party application by the third party, the order processing unit notifies a contact destination of the user in the third country that the sales of the third party application has been approved, When the sales approval processing unit obtains a rejection of the sales of the third-party application by the third party, the order processing unit notifies a contact destination of the user in the third country of the rejection of the sales of the third-party application.

3. The overseas application sales management server system according to claim 1 or 2, characterized in that: The sales approval processing unit further provides order status management information to a terminal that is a contact destination of the third party.

4. The overseas application sales management server system according to claim 3, characterized in that: The order status management information includes information related to a user in the third country who requests to purchase the third-party application developed by the third party.

5. The overseas application sales management server system according to claim 1 or 2, characterized in that: When the sales approval processing unit obtains the sales approval of the third party application by the third party, the order processing unit further issues a serial number, which is the release permission information of the third party application, to the user. The distribution control unit distributes the third-party application associated with the distribution permission information together with the license to the edge server based on the serial number received from the user terminal of the user in the third country.

6. The overseas application sales management server system according to claim 1 or 2, characterized in that: The application DB is provided in the third country.

7. The overseas application sales management server system according to claim 1 or 2, characterized in that: The third country is a white-list country other than Japan, and the country of residence of the third party is Japan or a white-list country other than the third country.

8. The overseas application sales management server system according to claim 1 or 2, characterized in that: The management control unit is provided in a dedicated area corresponding to the third country, and the dedicated area is provided in a hardware resource provided in Japan.

Images