Corresponding to overseas application sales management system

Abstract

The present invention provides an overseas application sales management system (1000) for appropriately managing third-party applications developed by third parties. The overseas application sales management system (1000) manages online store sales of applications running in third countries through edge servers (400), and comprises a store registration server (300) that, when the developer of the application is a third party, receives an export management list containing a compliance / non-compliance determination document and a trade management regulations determination result for the application, and registers the application in correspondence with the export management list containing the compliance / non-compliance determination document and the trade management regulations determination result when it is determined that the application can be sold in stores in the third country.

Description

Technical Field

[0001] The present invention relates to a sales management system corresponding to overseas application programs. Background Art

[0002] Recently, in the field of manufacturing equipment including CNC machine tools, industrial equipment, industrial robots, etc., EC (e-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] On such websites, applications developed by various application developers undergo a prescribed review process and are listed in the app store. Users can then purchase and install these applications on edge servers installed at manufacturing sites. Specifically, at manufacturing sites such as factories, applications on edge servers can collect and effectively utilize data such as the operating status of manufacturing equipment, data on the production status of manufacturing equipment, data on the quality of products produced by manufacturing equipment, and data on the operational status of manufacturing equipment.

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

[0005] When operating and providing such app stores in third countries, the apps listed on these app stores may have various functions for manufacturing equipment, including CNC machine tools, industrial equipment, and industrial robots, and therefore could be used, for example, in weapons development. Therefore, for example, the sale of apps developed in countries other than Japan or third countries through stores in third countries may be subject to restrictions under the export trade control orders of those countries.

[0006] In this case, when operating and providing an application store 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 must 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 must 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 Act

[0008] Here, we briefly explain the export trade control laws and regulations using Japan as an example. In addition, the areas where the export control laws and regulations of each country apply are referred to as regions.

[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 (for example, 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 with strict export controls. Exports related to weapons development are restricted in Japan through the Export Trade Control Order. For example, a server application run by edge server 400, sold in overseas regions outside of Japan (hereinafter referred to as the "export destination"), is associated with machine tool operations and is considered potentially related to weapons development. Therefore, in order to register the application for sale in local stores in the export destination (an overseas region outside of Japan, such as the United States), the developer of the application, for example, must determine whether the application complies with the Export Trade Control Order (hereinafter referred to as a "conformity / nonconformity determination"). Therefore, the developer of the application, i.e., the developer of the application, must prepare a "conformity / nonconformity judgment note." Furthermore, the conformity / nonconformity determination within the conformity / nonconformity determination is based on list-based restrictions if the export destination is a whitelist country, and on catch-all controls if the export destination is a non-whitelist country.

[0011] Several technologies for efficiently performing compliance / non-compliance determinations are also provided. For example, Patent Document 1 describes an export management system that displays guidance, such as relevant legal text, during compliance / non-compliance determinations. Furthermore, Patent Document 2 describes an export management compliance / non-compliance determination chart extraction system that includes multiple compliance / non-compliance determination tables, which are selected based on input such as keywords. Furthermore, Patent Document 3 describes an export management system in which operators performing compliance / non-compliance determinations refer to past compliance / non-compliance determination results while performing compliance / non-compliance determinations, thereby improving the accuracy of compliance / non-compliance determinations.

[0012] Next, after the developer of the app creates a certificate of conformity / non-conformity, anyone exporting 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 themselves or purchases the app from the developer for export, will need to obtain a certificate of conformity / non-conformity and, after confirming its contents, obtain export trade management permission from, for example, an economic and industrial official.

[0013] It should be noted that if the app is deemed "non-compliant," it does not need to obtain export trade management permission from the Ministry of Economy, Trade and Industry. Instead, it can apply for local store sales registration from the operating company of the app store at the export destination.

[0014] If the app is determined to be "compliant," a comprehensive license (such as an unlimited special blanket permission) can be obtained when the export destination is a whitelist country. Furthermore, if the export destination is not a whitelist country, stores that qualify for the app's inventory sales are generally not allowed to sell it (i.e., it is not possible to apply for local store sales registration with the operating company that manages the app store at the export destination). In this case, in order to sell the app in the export destination, face-to-face sales are required (i.e., for each customer who requests to purchase the app, an export license for the app must be obtained from the economic and industrial officials for that customer).

[0015] As described above, if a compliance determination is made, only if the export destination is a whitelist country and a comprehensive license (e.g., a special general comprehensive license) is obtained, can local store sales registration be applied for from the operating and management company of the app store in the export destination (whitelist country). On the other hand, if the export destination is not a whitelist country, local store sales registration cannot be applied for from the operating and management company of the app store in the export destination (non-whitelist country).

[0016] To summarize, if an app is determined to be "non-compliant," for example, an app developed in Japan, regardless of whether the export destination is a whitelisted country or a non-whitelisted country, the app can apply for local store sales registration from the operating and management company of the app store in the export destination (whitelisted country). On the other hand, if an app is determined to be "compliant," for example, an app developed in Japan, only if the export destination is a whitelisted country can the app be applied for local store sales registration from the operating and management company of the app store in the export destination (whitelisted country).

[0017] <Customer Inspection>

[0018] In addition, after local store sales registration is completed with the operation manager of the application store at the export destination, that is, the operation 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, that is, the customer, is a customer of interest.

[0019] For apps developed in Japan, after they are registered for local store sales with the operating company of the app store in the export destination, if a customer residing in (also referred to as "belonging to") the export destination (e.g., the United States) receives a purchase request for the app, the exporter (e.g., the app developer) must conduct a separate check (also referred to as "customer check") to verify that the customer does not and / or will not develop weapons of mass destruction, etc., or is not a company or organization listed on the foreign user list. The so-called foreign user list is a list of foreign companies and organizations, compiled by the Ministry of Economy, Trade and Industry pursuant to the Export Trade Control Order, whose exported goods or technologies may be used for the development or manufacture of weapons of mass destruction, biological weapons, chemical weapons, or missile-delivery systems.

[0020] As a result of the customer inspection, if the customer meets the criteria of a concerned customer, the application cannot be sold.

[0021] Prior art literature

[0022] Patent Literature

[0023] Patent Document 1: Japanese Patent Application Laid-Open No. 2003-36323

[0024] Patent Document 2: Japanese Patent Application Laid-Open No. 2007-140889

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

[0026] As described above, in an application store operated and provided in a third country, i.e., in a corresponding overseas application sales management system, when, for example, an application developed in 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 a store through the application store, it is necessary to confirm with the operating and management company of the application store, through the developer of the application (hereinafter also referred to as the "third party"), the following: for example, the compliance / non-compliance determination document and the trade control regulations determination result (completed / not required) prepared by implementing the compliance / non-compliance determination prescribed by the export control laws of Japan or a country other than the third country. Therefore, it is desired that 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 and management company can easily confirm the compliance / non-compliance determination document and trade control regulations determination result related to the application.

[0027] In this way, when a third-party application developed by a third party is registered for sale in a local store through an application from a third party in an application store used and provided in a third country, that is, in a corresponding overseas application sales management system, it is possible to easily confirm the compliance / non-compliance judgment and trade management regulations judgment results related to the application. Summary of the Invention

[0028] (1) One method of the present disclosure provides a corresponding overseas application sales management system, 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 corresponding overseas application sales management system corresponds to the third country, and the corresponding overseas application sales management system has: a communication unit; an application DB, which stores the applications to be registered for online store sales in the third country; and a store registration control unit, the store registration control unit including: an application acceptance unit, which accepts the applications and an export management list, wherein, when the developer of the application is an application developer in a country other than the third country That is, when the developer of the application is a third party, the export management list includes the compliance / non-compliance judgment letter and the trade management regulations judgment result of the application; an application review unit, which reviews the application accepted by the application acceptance unit and the export management list including the compliance / non-compliance judgment letter and the trade management regulations judgment result when the application developer is a third party; and an application registration unit, when the developer of the application is a third party, when the application review unit determines that the application can be sold in stores in the third country, the application registration unit registers the application in correspondence with the export management list including the compliance / non-compliance judgment letter and the trade management regulations judgment result when the application developer is a third party to the application DB.

[0029] Effects of the Invention

[0030] According to one method, in an application store used and provided in a third country, i.e., in a corresponding overseas application sales management system, when a third-party application developed by a third party is registered for sale in a local store through an application from the third party, the compliance / non-compliance judgment document and trade management regulations judgment result related to the application can be easily confirmed. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

[0033] Figure 2B This is a functional block diagram of the distribution server 200 included in the sales management server system 10 in this 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 this embodiment.

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

[0038] Figure 4 This figure shows an example of a screen displayed while waiting for third-party approval for an application that the user has requested to purchase in the present embodiment.

[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 this embodiment is shown.

[0042] Figure 6 This is a flowchart showing the browsing information providing process of the sales management server system 10 in this 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] Figure 9 This is a flowchart showing an example of processing after the sales approval processing of the sales management server system 10 in this embodiment.

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

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

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

[0049] Figure 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] Figure 14 4 is a functional block diagram of the edge server 400 in this embodiment.

[0051] Figure 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 Renewal Processing Department

[0063] 214 Release Processing Department

[0064] 120, 220 Storage Department

[0065] 122 User Storage

[0066] 124 Release Management Storage Department

[0067] 125 Application Developer Information Storage Department

[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 Department

[0078] 400 Edge Server

[0079] 410 Control Department

[0080] 411 Application Execution Department

[0081] 412 License Control Department

[0082] 413 Access Control Department

[0083] 414 Illegal Application Notification Department

[0084] 420 Storage Department

[0085] 430 Ministry of Communications

[0086] 500 edge devices

[0087] 600 Terminal

[0088] N1 and N2 networks DETAILED DESCRIPTION

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

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

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

[0092] Figure 1 This is a schematic diagram showing the basic structure of an application sales management system 1000 - n provided corresponding to an 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 server system for sales management of overseas application programs, 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, or the like. The specific communication method in the network N1 is not particularly limited to whether it is a wired connection or a wireless connection.

[0094] Furthermore, one operation management company 2-n is pre-set in region n to operate and manage the sales management server system 10-n. Typically, the operation management company 2-n is a company (eg, a corporation) residing in (hereinafter also referred to as "belonging to") the region n.

[0095] The sales management server system 10-n and the store registration server 300 are independent, dedicated server systems corresponding to region n. A dedicated server system is not necessarily limited to a physically independent server device. For example, it can also be an independent virtual server contained in a designated server or cloud, etc., in a dedicated area corresponding to region n. In this case, the sales management server system 10-n and the store registration server 300 secured in the dedicated area corresponding to region n are managed and operated by the operating management company 2-n.

[0096] The sales management server system 10-n is, for example, Figure 1 As shown, it 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 DB (also referred to as "application DB") 250-n as an application DB.

[0097] Here, management server 100-n does not necessarily need to be physically located in region n and may be located in a region other than region n (e.g., Japan). In contrast, distribution server 200-n and / or application DB 250-n, described later, which stores at least applications that are set to be available for store sales (also referred to as "store sales registration" or "store registration"), are preferably located in region n. The configuration of servers and other components will be described later.

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

[0099] Edge servers 400-n are limited to being located within region n (hereinafter also referred to as "belonging to region n"). More specifically, edge servers n that are communicatively connected to the sales management server system 10-n via network N1-n are limited to belonging to region n. Edge servers 400-m belonging to regions m (m≠n) other than region n cannot communicate with the sales management server system 10-n. More specifically, edge servers 400-m belonging to regions m (m≠n) other than region n cannot purchase server applications from the sales management server system 10-n.

[0100] Here, examples of server applications running on edge servers 400-n include, for example, servers that collect and process data related to edge devices 500-n, described later, indicating operational status, production status, product quality, and operational status, but are not limited thereto. In the following description, server applications that perform sales management via application sales management system 1000-n are simply referred to as applications or apps.

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

[0102] Edge devices 500-n are devices installed at manufacturing sites such as factories within region n, including manufacturing equipment such as CNC machine tools, industrial equipment, and industrial robots, as well as image sensors and programmable logic controllers (PLCs). For example, one or more edge devices 500-n may constitute a production line or production unit in a factory.

[0103] In this way, the edge device 500-n has a function of delegating to 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 below, user 3-n can, for example, request the purchase of a desired server application from management server 100-n via terminal 600-n. If specified conditions are met, management server 100-n can obtain a serial number associated with the server application. Based on the serial number, user 3-n can then instruct distribution server 200-n to distribute (install) the server application to edge server 400-n.

[0106] Terminal 600-n is, for example, a personal computer (PC). Terminal 600-n is communicatively connected to management server 100-n and is used, for example, by an end user in region n who wishes to purchase a server application running on edge server 400-n. Terminal 600-n for user 3-n can be located within or outside the factory facility, but is located in region n. Furthermore, user 3-n can access sales management server system 10-n via terminal 600-n and browse the content of applications that user 3-n can purchase. Furthermore, user 3-n can order applications via terminal 600-n.

[0107] In addition, only users 3-n who meet pre-set conditions (qualifications, etc.) are given a user ID (IDentification) for accessing the sales management server system 10-n. Details will be described later.

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

[0109] Next, the structure of sales management server system 10-n, which is installed for region n (also referred to as "belonging to region n"), will be described. Sales management server system 10-n described in this embodiment includes a structure that not only sells applications developed by application developers belonging to region n (hereinafter referred to as "application developers") to users 3-n belonging to region n, but also sells (exports) applications developed by application developers belonging to region m (m ≥ 0 and m ≠ n) in Japan, excluding region n, via 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] Furthermore, unless otherwise specified, the description will be made using region 0 (zero), i.e., Japan, as an example of a region other than this region. Specifically, in the following description, unless otherwise specified, a server application developed by an application developer who belongs to (and resides in) Japan is sold (exported) to a user 3-n belonging to region n via a sales management server system 10-n in a region other than Japan (e.g., a foreign country such as the United States).

[0112] However, this embodiment is not limited to Japan and regions n outside of Japan (for example, foreign countries such as the United States). As described above, it can also be applied to the following situation: not only is the application store developed by application developers in region n sold to users 3-n in region n, but also applications developed by application developers in region m (m≠n) outside of region n are 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 These are functional block diagrams of the management server 100 and the publishing server 200 included in the sales management server system 10 in this embodiment. In addition, the user interfaces (UIF) and emails in these servers can be displayed in a switchable 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, operation and 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 UIs shown below as examples are temporarily recorded in Chinese, but in region n, they are displayed in the display language of region n as a default.

[0115] like Figure 2A As shown, 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 respectively execute various programs stored in the storage unit 120 and the storage unit 220 to centrally control the management server 100 and the publishing server 200 .

[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 management server 100, control unit 110 includes a browsing information provision unit 111, an order processing unit 112, a sales approval processing unit 113, a distribution management processing unit 114, and a contract renewal processing unit 115, as functional units based on programs stored in storage unit 120. In addition to the programs executed by control unit 110, storage unit 120 also includes an application management information storage unit 121, a user storage unit 122, a distribution management storage unit 124, an application developer information storage unit 125, and an order status management information storage unit 126.

[0119] Furthermore, in the distribution server 200, the control unit 210 includes a distribution processing unit 214 as a functional unit based on a 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 , the storage unit 120 , the storage unit 220 , and the application DB 250 will be described.

[0121] Figure 2C This is a diagram showing an example of the storage unit 120 of the management server 100 in this embodiment. Figure 2D : is a diagram showing an example of the storage unit 220 of the distribution server 200 in this 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 that stores 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 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 associated with the application ID. For example, this data may include the application name (and / or product name), target device type information, input information, application manual, pricing information, application developer information (including the application developer ID), sales method information, and customer verification information. The sales method information indicates whether store sales are possible or whether face-to-face sales are required. The customer verification information indicates whether the application developer is required to conduct customer verification when selling in stores. The data stored in the application management information storage unit 121 is not limited to this. Some of the data items shown in the examples, as well as other data items, may also be stored.

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

[0126] The target device type information is device type information of the edge device 500 that is the input / output target of the application program, and is, for example, a device 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 .

[0128] The application manual includes information about the license as part of the application's structure. This information includes, for example, whether the license specifies the edge device 500 that will use the application, whether the edge device 500 is specified, and whether a certain number of edge devices 500 must be purchased for simultaneous use, or whether there is no limit on the number of devices. Furthermore, information about contract renewal regarding the use of the application is also included.

[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), and the like.

[0131] Sales method information indicates whether the application can be sold in stores or requires face-to-face sales. Face-to-face sales, in this context, means that the application developer directly sells the application to the user, rather than selling it in stores. Therefore, applications requiring face-to-face sales cannot be ordered via the ordering screen provided by management server 100, described later.

[0132] The customer check information indicates whether the app developer is required to perform a customer check when selling the app in the store. For example, if the app developer is located outside the region, such as a whitelist country that strictly implements export controls (e.g., Japan), and the sale of the app qualifies as an export activity for the app developer, a customer check based on the export trade control order of that country (e.g., Japan) is required.

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

[0134] Export Trade Control Act

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

[0136] In Japan, which strictly enforces export controls, exports related to weapons development are restricted through the "Export Trade Control Order." For example, a server application that is sold within a region (e.g., the United States) and is run through edge server 400 is an application associated with the operation of machine tools, etc., and is considered potentially related to weapons development. Therefore, in order to enable the application to be sold within a region (e.g., the United States) (e.g., registering the application, i.e., the store sales registration, as a state that allows distribution to application DB 250 located within the region), the person who created the application, i.e., the developer of the application, needs to determine whether the application complies with the Export Trade Control Order (compliance / non-compliance determination) when exporting the application to the region. Therefore, the person who created the application, i.e., the developer of the application, needs to prepare a "compliance / non-compliance determination document."

[0137] Next, after the developer of the app creates a compliance / non-compliance certificate, when exporting the app to someone in the region, such as when the developer exports the app themselves or when someone purchases the app from the developer and exports it, they will obtain a compliance / non-compliance certificate and, after confirming its contents, obtain permission for export trade management, for example, from economic and industrial officials.

[0138] In addition, if the application is judged as "non-compliant", there is no need to obtain special permission for export trade management from the Ministry of Economy, Trade and Industry.

[0139] If the app is determined to be "compliant," a comprehensive license (such as a special general comprehensive license) can be obtained if the region is a whitelist country. However, if the region is not a whitelist country, stores that sell compliant apps in stock are not allowed to sell them, and face-to-face sales are required (i.e., obtaining an export license for the app each time).

[0140] The procedures related to the export trade management order are well known to those skilled in the art, and 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 installed 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), which operates the sales management server system 10 in the region.

[0143] In addition, an embodiment of the store registration server 300 for registering an application developed (for example, developed in Japan) for store sales in an overseas region (for example, the United States) by the exporter of the application (that is, 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 app exporter (e.g., app developer) registers an app developed in Japan for sale in a store overseas (e.g., the United States), they must individually confirm whether the order destination is a customer of interest each time an order for the app is placed.

[0146] Specifically, for example, if an application developed in Japan is registered for sale in a store in a region (e.g., the United States) (i.e., the application is registered as being able to be distributed to a distribution server 200 located in that region), and a purchase request for the application is received from a customer in that region (e.g., the United States), the exporter (e.g., the application developer) must separately check whether the customer is engaged in (has engaged in) the development of weapons of mass destruction, etc., or whether the customer is a company or organization listed in the Foreign User List. The Foreign User List is a table created by the Ministry of Economy, Trade and Industry pursuant to the Export Trade Control Order that lists the names of companies and organizations in foreign countries whose goods or technologies are of concern and are used for the development or manufacture of weapons of mass destruction, biological weapons, chemical weapons, or missile launchers.

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

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

[0149] <User Storage Unit 122>

[0150] The user storage unit 122 is a storage area that stores information related to user 3 who has installed an edge server 400 that is communicatively connected to the sales management server system 10. Setting up the edge server 400 requires that user 3 meet pre-set conditions (e.g., qualifications). User 3 who has installed the edge server 400 is permitted to access the sales management server system 10. Specifically, user 3 is assigned a user ID that allows access to the sales management server system 10. User 3 may include not only end users but also intermediaries such as system integrators and specialized businesses such as machine tool manufacturers.

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

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

[0153] As an example, user information may include information related to the user, such as the user's name, agent name, address, phone number, email address, URL, user level, and subscription permissions. User information is not limited to this. It may include some of the data items listed as examples, as well as other data items. Furthermore, this user information is generated, for example, when the edge server is initially configured for the user, and is subsequently updated whenever changes to the user information occur (e.g., when an edge server is added).

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

[0155] Furthermore, subscription authority is information used to identify whether a user identified by a user ID (a professional (intermediary) or an end user) is allowed to directly request the purchase of an application from the sales management server system 10. Only when the user has subscription authority can the user directly request the purchase of an application from the sales management server system 10.

[0156] Edge server information, particularly when the user is an end user, refers to information related to an edge server 400 located in a factory or manufacturing site related to the user. This information identifies the edge server 400 to which the application is to be distributed. As described above, the edge server 400 is located within the region provided by the application sales management system 1000. As an example, the edge server information may include an edge server ID identifying the edge server 400, the location of the edge server, and address information on the communication network, such as the IP address of the edge server 400. Furthermore, if there is one or more edge servers 400 at a location related to the user, such as a factory, the edge server ID is necessary to identify each edge server 400.

[0157] Furthermore, the edge server information may include information related to an edge device 500 that is a candidate for a request from the edge server 400 and that can perform input and output with the edge server 400. Information related to the edge device 500 may include an edge device ID that identifies the edge device 500, a device type name of the edge device 500, and an address of the edge device 500 on the communication network (e.g., an IP address).

[0158] The edge server information is not limited thereto and may include some 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 related to 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 and stores published application information with the publishing destination edge server 400. For example, the publishing management storage unit 124 stores a publishing management record that uses the edge server ID identifying the publishing destination edge server 400 and the application ID identifying the published application as search keywords, respectively. Furthermore, the publishing management record uses data containing the edge server ID of the publishing destination edge server 400 and the application ID of the published application as a search keyword (compound keyword). For example, in addition to the aforementioned search keywords, the publishing management record also stores the product name, order number, order date, serial number (license key), license, purchase date (license acquisition date), and publication date of the published application. Furthermore, although not shown, data used to manage the published application, such as the next contract renewal date, the next contract renewal notification date, the next contract renewal notification destination, and a notification completion flag, may also be stored. The data contained in the publishing management record is not limited to this. It may also include some of the data items shown in the examples, as well as other data items.

[0162] The order number is, for example, a number for managing the processing status (processing state) from the acceptance of a 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 , and is, 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 notifying the purchaser of the application and / or the user of the license recipient of the application whether to extend the current license contract and continue the contract.

[0170] The next contract renewal 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 has been made to the purchaser of the application and / or the user of the license destination of the application regarding whether to extend the current license contract and continue the contract. 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, for each 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 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 the processing status and processing results of a purchase request for an application from the user 3 .

[0177] Order status management information can be associated with the order number and include, for example, the order date and time, the order's application ID, the application name (product name), the user ID of the order's destination (i.e., the person who ordered the application), the approval status, the publishing status, the application developer ID, etc. The approval status and application developer ID are generated when the application developer needs to conduct a customer review when selling the application.

[0178] The approval status is management information used to manage whether the order destination of the application is a customer of interest when the application is sold, if the application developer is located in a region other than the region to which the sales management server system 10 is assigned (e.g., Japan). Examples of the approval status include "approval not required" (a state where customer verification is not required), "unapproved" (i.e., a state where customer verification is in progress), "approved" (a state where the customer is not a customer of interest as a result of the customer verification), and "rejected" (a state where the customer is a customer of interest as a result of the customer verification).

[0179] In addition, if approval is not required or has been approved, the order processing unit 112 can complete the purchase procedure to the user 3 by, for example, email, as described later. In addition, if approval has been denied, the order processing unit 112 can notify the user 3 that the purchase is not possible by, for example, email, as described later.

[0180] Furthermore, for order status management information, for example, an identification mark can be set, and a symbol for identification can be set on part of the order number so that the application developer can distinguish between orders that require customer review and those that do not. This makes it easy to retrieve order status history information related to orders that require (or have undergone) customer review by the application developer.

[0181] Furthermore, order status management information can be generated 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 some of the data items shown as examples 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 includes a publishing data storage unit 224. Publishing data storage unit 224 is a storage unit provided for publishing applications requested by users. Publishing data storage unit 224 can be associated with the serial number (license key) of the published application and contain the published application ID, product name, application program, access declaration list, license, user ID of the user requesting the purchase, and the ID and IP address of the edge server 400 of the publishing destination on the communication network.

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

[0185] <Application of DB250>

[0186] Figure 2EFIG2 is a diagram showing an example of application DB250. Figure 2E As shown, in the application DB 250, applications registered for sale in a certain region (e.g., the United States) are stored in association with their application IDs. Specifically, applications developed by application developers are authenticated as satisfying specified conditions within the operating and management company 2 by the application registration unit 313, described later, and registered along with an access declaration list. Furthermore, the application's product name, application manual, application license-related manual, and application version number may also be registered as appropriate.

[0187] In addition, in order to enable applications (hereinafter also referred to as "third-party applications") developed by application developers (hereinafter also referred to as "third parties") in countries outside the region (such as Japan) to be sold in stores, they are registered in application DB250, and the application developers implement compliance / non-compliance judgments with export control laws of countries outside the region (such as Japan), and a compliance / non-compliance judgment list containing 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, applications that are generally considered non-compliant and compliant are limited to those that have obtained export licenses and trade management approvals for whitelisted countries. Therefore, compliant applications cannot be sold in stores in non-whitelisted 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, it may be included in the storage unit 220. Alternatively, 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 be installed in the region for the following reasons.

[0191] The explanation is based on an example where 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 if application DB 250 is deployed in Japan, then export control regulations apply whenever applications stored in application DB 250 are distributed to users in the United States. In this case, whenever a third party distributes an application to users in the United States, it will be necessary to obtain export permission from the Ministry of Economy, Trade and Industry (METI) every time it determines whether the application complies or does not comply, and whether the determination is "compliant" or "noncompliant." This procedure becomes extremely complex 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 qualifies for export from the United States to Japan. Conversely, when an application stored in Application DB250 is released to users in the United States, it qualifies for export from Japan to the United States. This requires export licenses from both the United States and Japan, making the process extremely complicated. To avoid this, U.S. law requires that the endpoints of applications developed by U.S. developers be encrypted. Therefore, considerable development costs are required to comply with endpoint encryption, which is unpopular. Furthermore, due to endpoint encryption, the extraction of applications through Application DB250 set up 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 endpoint encryption is performed, the extraction of applications through Application DB250 set up in Japan is judged to comply with import and export. Therefore, endpoint encryption has become an extremely exceptional solution that cannot be applied to countries outside the United States, which is unreasonable.

[0194] In contrast, if the application DB 250 is installed in the United States, there will be no import or export issues associated with extracting applications developed by U.S. developers via the application DB 250. Furthermore, even when exporting from Japan, the most appropriate practice is to apply export control regulations (determining compliance / noncompliance and requiring an export license if compliance) only when the application DB 250 installed in the United States is enabled for sale in stores.

[0195] For the reasons described above, it is preferable to locate application DB 250 in the United States, outside of Japan. In this embodiment, at least one configuration in which application DB 250 is located in that region will be described. Furthermore, if publishing server 200 includes application DB 250, publishing server 200 is located in that region. Furthermore, if application DB 250 is a physically separate DB server from publishing server 200, that DB server is located in that 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. The virtual server ensured in the dedicated area corresponding to region n is managed and used by the operating management company. Therefore, not only within the region, but even if it is set up in Japan, for example, 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 in 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 distribution management processing unit 114 as a distribution management processing unit, and a contract renewal processing unit 115 as a contract renewal 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 requires face-to-face sales rather than in-store 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 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 to extract application product information related to applications (general applications 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 provides information to that effect if customer check is required for the application developer when selling the application in a store.

[0208] [View price information]

[0209] Furthermore, the browsing information providing unit 111 can provide pricing information corresponding to the user level pre-assigned to the user 3 in response to an inquiry or browsing request for application pricing information (application sales pricing information) received from the terminal 600. Specifically, only end-user pricing information is provided to end users, while end-user pricing information and wholesale pricing information for specialized vendors (intermediaries) are provided to specialized vendors (intermediaries). Therefore, the browsing information providing unit 111 references the user storage unit 122 to confirm the user level of the user whose user ID is included in the received browsing request.

[0210] The browsing information providing unit 111 then generates a browsing screen 160 containing the extracted application information and price information of the application corresponding to the user's level, and provides it to the terminal 600. Furthermore, when multiple applications have been extracted, the browsing information providing unit 111 may generate an application list screen and transmit it to the terminal 600. Furthermore, when a selection regarding a single application is received from the terminal 600, the browsing information providing unit 111 extracts information regarding 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 this embodiment.

[0212] like Figure 3 As shown, browsing screen 160 may include, for example, an application ID 161a, an application product name 161b, an application developer 162, information 163 indicating whether the application developer is required to conduct a customer review when selling the application in a store, an application manual 165, and a manual 166 regarding the application license. Manual 166 also includes extracted price information 166a, license quantity 166b, license description information 166c, and an edge server ID designator 166d, which are collectively provided as license-related information. The inclusion of license-related manual 166 on browsing screen 160 allows each user to confirm the license-related information they need.

[0213] Furthermore, 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] Furthermore, the browsing information providing unit 111 can display a purchase button or the like on the browsing screen 160 so that users with ordering permission can place an order. Furthermore, when a user selects an application as a purchase candidate while browsing applications, the browsing information providing unit 111 stores the selected application ID and the like in a temporary purchase candidate storage unit (the so-called "shopping cart") (not shown). Furthermore, upon user instruction, the browsing information providing unit 111 can display the browsing screen 160 as an ordering screen, displaying a purchase button or the like for ordering the application IDs (product names) stored in the purchase candidate storage unit (shopping cart) (not shown), either per application or collectively.

[0215] Furthermore, when a purchase button or the like is displayed, it is preferable to also display whether or not the application developer needs to conduct a customer review when selling the application in a 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 a purchase request for an application program received from a user with subscription authority via terminal 600, order processing unit 112 generates an order number for each application program requested for purchase and, for example, creates an order status management information record containing the order date and time, the application ID of the order, the application name (product name), and the user ID of the order recipient (i.e., the user who ordered the application program). Payment for the requested application program is confirmed using known methods (e.g., credit card, automatic account debit, 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 serves as 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 customer inspection when selling the application requested for purchase in the store. If it is determined that the third party (application developer) needs to perform customer inspection for the application requested for purchase, the user is notified via the terminal 600 that the approval of the application developer is awaited. Figure 4 This shows an example of a screen displaying a request for approval from an application developer.

[0221] like Figure 4As shown, an example of the text notifying the user is "The product you ordered requires approval from the developer. Upon approval, you will be issued the serial number necessary to release the purchased product. An email will be sent after approval. Please proceed to complete the purchase (approval confirmation)." However, this is not limiting. Any language that clearly states that the purchase is pending approval but not completed, that we will contact you later after approval, and that the purchase will be completed (approval confirmation) after approval will be sufficient. This allows the order processing unit 112 to pass on the order status management information for 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 for purchase, 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 for purchase 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 for purchase, and passes the order processing data to the publishing server 200 (publishing processing unit 214).

[0223] Furthermore, as information regarding permission to release, the order processing unit 112 can send an email containing, for example, an ID and password for registering on a dedicated screen (not shown) displaying the application's serial number (license key) to the user who requested to purchase the application. This allows the user to display the dedicated screen and then register using the ID and password provided in the email. The order processing unit 112 can then display the serial number (license key) on the dedicated screen. This allows for enhanced security, even if a third party impersonates and uses the terminal 600 of a user with subscription authority.

[0224] A case will be described where it is determined that customer inspection is necessary, and the order matter passed 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 passed to the order processing unit 112.

[0225] As described 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 for purchase 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") to the contact address (e.g., email address) of the user who requested to purchase the application, notifying the application developer that the customer review has been completed (approved). The email is preferably a push email. After confirming payment of the purchase price by the user, the order processing unit 112 generates a serial number (license key) for the application, creates order processing data containing the application ID, the edge server ID of the edge server 400 serving as the publishing destination, and the serial number (license key), and transmits the data to the publishing server 200 (publishing unit 214).

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

[0228] Furthermore, if the sales approval processing unit 113 determines that a customer review is necessary and the application developer rejects an order case that has been forwarded to the sales approval processing unit 113, and the order case is forwarded to the order processing unit 112, the order processing unit 112 sends an email (also referred to as a "rejection email") to the contact address (e.g., email address) of the user who requested the purchase, notifying them that the purchase of the application has been rejected and the purchase procedure has been completed. This completes the processing related to the order case.

[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 in association with the order number of the application created by the order processing unit 112.

[0232] When receiving order status management information from the order processing unit 112, the sales approval processing unit 113 sends an email, etc., to the third-party (application developer) contact address, notifying the third-party (application developer) of the product order and requesting their approval. Specifically, the sales approval processing unit 113 retrieves the contact address, etc., from the application developer ID included in the received order status management information, by referencing the application developer information storage unit 125. The email, etc., can then be sent to that email address. The email is preferably a push email. Furthermore, the application developer or its agent pre-registers the contact address.

[0233] Alternatively, an email containing a URL for displaying the order status management screen described later may be sent. This allows a third party (application developer) or its agent to 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 for the application developed by the application developer (after user authentication).

[0234] In response to a request from a third party (application developer) or its agent, the sales approval processing unit 113 provides a user interface (hereinafter referred to as an "order status management screen") for confirming product orders to a terminal (not shown) owned by the third party (application developer) or its agent. Specifically, the sales approval processing unit 113 retrieves all order status management information related to the application developer ID contained in the order status management information stored in the order status management information storage unit 126, sorts the information by order date, and displays the order status of the application in a list format, including its historical records, for example.

[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, Figure 5AAs shown, by a third party (application developer) user pressing the sequence number of a screen, another screen 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 presented via a pop-up screen. Figure 5B As an example of the user information 1134b presented, the company code 1134b1, company name 1134b2, company representative 1134b3, and address 1134b4 are shown, but the present invention is not limited to this. Any information can be displayed as user information 1134b. Furthermore, if an edge server is installed at the user's manufacturing site, user information registered by the operation and management company 2 can be provided as user information.

[0239] In the approval status column 1135, the third party (application developer) inputs the following status: Not Approved (Under Customer Confirmation), Approved (Customer Confirmation Not of the Customer of Interest), Rejected (Customer Confirmation of the Customer of Interest), and No Approval Required (No Customer Inspection Required). The Not Approved (Under Customer Confirmation), Approved (Customer Confirmation Not of the Customer of Interest), Rejected (Customer Confirmation of the Customer of Interest), and No Approval Required (No Customer Inspection Required) are statuses input by the third party (application developer) based on the progress of the customer inspection.

[0240] To assist the third party (application developer) in inputting operations, an Approve button 1136a and a Reject button 1136b may be displayed in operation bar 1136 when the approval status of the order case is not approved. This allows the third party (application developer) to easily confirm the cases awaiting customer review and, by displaying an Approve or Reject button operation (e.g., a press or click operation, etc.) in operation bar 1136, allows the third party (application developer) to easily input the customer review result. By pressing (or clicking) the Approve button 1136a, the application developer can complete the purchase procedure for the application (product) and obtain the serial number of the application, as described below. Alternatively, when approval is not required, the application developer can complete the purchase procedure for the application (product) and obtain the serial number of the application, as described below.

[0241] On the other hand, if the third party (application developer) presses (or clicks) the reject button 1136b, the person requesting to purchase the application is determined to be a concerned customer, and 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 Approve button 1136a, the sales approval processing unit 113 records "Approved" in the Approval Status column 1135 of the order status management information, and passes the order status management information for the application to the order processing unit 112. Similarly, when the third party (application developer) presses the Reject button 1136b, the sales approval processing unit 113 records "Rejected" in the Approval Status column 1135 of the order status management information, and passes the order status management information for the application 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] Although not shown, the order status management screen 1130 may include a publishing status column. This column displays the status of the publishing progress, for example, as input by the publishing processing unit 214. For example, the column may display "serial number not sent," "serial number sent," "not published," or "published," depending on the publishing progress. Furthermore, the column may include the serial number sending date and the publishing date. This allows a third party (application developer) or their agent to confirm the approved publishing status.

[0245] The search condition input field 1137 can provide a pop-up screen 1137 a for inputting search conditions by, for example, clicking the search condition input field 1137 . Figure 5C An example of a search condition input field is shown. Figure 5CAs shown, a screen for inputting an order destination (ordering company) 1137b, a product name 1137c, an order number 1137d, an order date and time range 1137e, and an approval status 1137f is provided, along with a screen for performing a complex search combining multiple conditions (AND or OR). Furthermore, a company search button 11371 is used to search for a company specified in the ordering company input field, and a search button 11372 is used to perform a complex search.

[0246] Furthermore, the sales approval processing unit 113 can provide, for example, a function for the administrator of the operation and management company 2 to search and query the order status management information stored in the order status management information storage unit 126 via the operation and management terminal (not shown). This allows the administrator of the operation and management company 2 to, for example, confirm (visualize) order cases that are in an unapproved state.

[0247] <Publishing Processing Unit 214>

[0248] The distribution processing unit 214 of the distribution server 200 extracts the corresponding application from the application DB 250 based on the order processing data transmitted from the management server 100 (order processing unit 112), creates distribution data, and stores it in the distribution data storage unit 224. The distribution data is associated with a serial number (license key) and includes the application ID to be distributed, the product name, the license, the user ID of the user who requested the purchase, the ID of the edge server 400 to which the distribution is to be made, and an address on the communication network such as an IP address.

[0249] When the distribution processing unit 214 receives a serial number (license key) and an application distribution request from a user who purchased the application via terminal 600, it references the distribution data storage unit 224 based on the serial number (license key) to determine the application ID to be distributed and the edge server 400 to which it will be distributed, and then distributes the application from the application DB 250 to the edge server 400 to which it will be distributed. More specifically, in response to the application distribution request received from the user via terminal 600, the distribution processing unit 214 determines the application to be distributed, the license, and the edge server 400 to which the application will be distributed based on the serial number (license key). To the identified edge server 400, the distribution processing unit 214 distributes the license and the application obtained from the application DB 250 based on the application ID associated with the serial number (license key). Here, the license refers to, for example, usage permission information associated with the edge device 500 that is the client of the application (i.e., the target of connection and / or input / output). The license may be distributed to the edge server 400 while included in the application. Alternatively, the license may be distributed 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 release processing unit 214 identifies the application and edge server 400 based on the serial number (license key) included in the release request. Therefore, only specific users who know the serial number can make a release request. In other words, even if a third party makes a release request, the application will not be released because they do not know the serial number. Furthermore, the serial number identifies the edge server 400 to which the application is to be released. Therefore, even if a third party knows the serial number, they cannot release the application to a server other than the specified edge server 400.

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

[0253] Furthermore, the posting processing unit 214 can provide, for example, a manager of the operating and managing company 2 with a function of searching and querying 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.

[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 publishing destination edge server 400. As described above, the publishing management processing unit 114 stores, for example, a publishing management record in the publishing management storage unit 124. The publishing management record uses the edge server ID identifying the publishing destination edge server 400 and the application ID identifying the published application as search keys, and also uses data including the edge server ID of the publishing destination edge server 400 and the application ID of the published application as a search key (compound key).

[0257] The distribution management processing unit 114 provides, for example, a function for a manager of the operating and managing enterprise 2 to search and query the distribution management records stored in the distribution management storage unit 124 via an operations management terminal (not shown). This allows for easy retrieval of information such as the edge server 400 to which a distributed application was distributed, and when the contract renewal date for the application is due on the edge server 400.

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

[0259] <Contract Renewal Processing Unit 115>

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

[0261] The contract renewal processing unit 115 refers to the release management storage unit 124 and, for example, notifies the purchaser of the application and / or the user of the application's license that the contract has been downloaded to the edge server 400 of the contract renewal. Furthermore, the terminal notified by the contract renewal processing unit 115 may be the terminal 600 owned by the purchaser of the application and / or the user of the application's license, or may be another terminal (e.g., a portable terminal) owned by the purchaser of the application and / or the user of the application's license. Furthermore, the notification method may be, for example, a menu screen display or an email.

[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 with the notified flag.

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

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

[0265] Furthermore, when the license is renewed, if the application developer needs to conduct a customer check when selling the application in a store, the application developer can conduct a customer check similar to the ordering process.

[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] To view application information, each user operates terminal 600 and registers with the sales management server system 10. Registration is performed using a known method, such as user authentication using the user's personal information or a password management file containing an ID and password, to verify that the user is a legitimate user. The user then selects "View Application" from a menu screen (not shown) displayed on 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) refers to the application management information storage unit 121 and provides a display screen showing application information (application product information) related to the specified application name. The application information (application product information) display screen can include information such as price information, whether a customer review is required for the application developer, and a purchase button.

[0276] In step S14 , the management server 100 (browsing information providing unit 111 ) receives an instruction from the user via 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 provision 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) customer review is required when selling the requested application in the store. If required (Yes), the process proceeds to step S22. If not required (No), the process proceeds 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 passes 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 price from the user. If payment is confirmed (Yes), the process proceeds to step S24. If payment cannot be confirmed (No), the order status management information is recorded as a waiting fee and the process returns to step S23.

[0284] In step S24, the management server 100 (order processing unit 112) generates a serial number (license key) for the application requested for purchase, and creates order processing data including the application ID, the edge server ID of the edge server 400 serving as the distribution destination, 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, passes the processing along with the order processing data to distribution server 200 (distribution processing unit 214), and ends the order processing.

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

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

[0288] In step S30 , the management server 100 (sales approval processing unit 113 ) sends an email or the like to the third party (application developer) to notify the third party (application developer) of the product order and request for customer inspection.

[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 "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. Specifically, Figure 9 In addition, as a modification example, it is possible to directly transfer to step S40. Figure 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. Figure 9 The step S40 described above is transferred. In addition, as a modified example, it is also possible to directly transfer Figure 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] Figure 9 This is a flowchart showing an example of processing after the aforementioned sales approval processing in 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 "rejected," the process proceeds to step S41. If "approved," the process proceeds to step S42.

[0297] In step S41, the management server 100 (order processing unit 112) identifies the user who requested the application as a customer of interest and sends an email ("rejection email") to the user's contact address (e.g., email address) notifying them that the application purchase has been rejected and the purchase procedure has concluded. The management server 100 (order processing unit 112) records the order status management information as rejected and terminates the process. This completes the processing related to the order case.

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

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

[0300] Next, the process flow related to application distribution will be described.

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

[0302] In order to delegate the publication of an application, for example, the user operates the terminal 600, selects the publication of the application from the unillustrated menu screen 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 the 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 identifies 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, indicating that distribution of the application to the edge server 400 has been completed. The distribution server 200 (distribution processing unit 214) then ends this processing.

[0307] As described above, in the application sales management system 1000 , an application running on 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 processing 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, an application developed in a country other than Japan or the overseas country as described in this embodiment, for example, is registered for local store sales through the operating manager of the application store, i.e., 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 in 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 and results of the third party's customer check when a third party needs to conduct a customer check after the user requests to purchase the application, and can achieve "visualization" of the progress of the customer check for all stakeholders.

[0311] As described above, with respect to this embodiment, in an application store provided in a third country (for example, the United States), that is, 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, that is, a user, residing in the third country, is a third-party application developed by a third party, a customer inspection request (whether it is an inspection of a concerned customer) is notified to the contact destination of the third party. The customer inspection 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] As a result, the application developer, that is, 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 third party's contact destination.

[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, 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 awaited.

[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 rejects the sale of the third-party application to the user through the third party, the management server 100 notifies the user of the rejection of the sale of the third-party application.

[0318] Thus, 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 requesting to purchase 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 third-party applications, it issues permission release information, i.e., a serial number, for the user. In response to receiving the permission release information, i.e., the serial number, from the user terminal owned by the user, the publishing server 200 publishes the third-party application corresponding to the permission 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] Furthermore, it is preferable that an application database storing applications registered for sale in an online store in a third country be located in the third country. This allows applications developed by developers residing in the third country to remain circulated within the third country and not be subject to import and export controls. Only third-party applications developed by third parties become subject to import and export controls, facilitating import and export operations.

[0322] In contrast, as described later, the management server 100 can be configured with physical hardware resources (e.g., servers or cloud computing) within Japan. For example, a dedicated region n (n ≥ 1) is set up for these hardware resources. Within this dedicated region n, the management server 100-n corresponding to region n can be configured as, for example, IaaS (Infrastructure as a Service). This allows for centralized maintenance of hardware resources as infrastructure, reducing maintenance costs. Details will be described later.

[0323] Furthermore, if the third country is a whitelist country other than Japan, the third party's country of residence can be set to a whitelist country other than Japan or the third country.

[0324] <Store Registration Server 300>

[0325] Next, the functions of the store registration server 300 as a store registration control unit in the 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 developed by an application developer belonging to a region (e.g., the United States) or a third party for store sales in a region (e.g., the United States) (i.e., registering the application as a state that it can be published to a publishing server 200 set up in the region) is explained.

[0327] As described above, in order to sell an application developed by a third party through the sales management server system 10 in an overseas region (e.g., the United States), the third party must determine (determine compliance / non-compliance) whether the application complies with the Export Trade Control Order when exporting the application to that region. Therefore, the third party must first prepare a "Compliance / Non-Compliance Determination Certificate."

[0328] When the application is judged to be "non-compliant", there is no need to obtain permission from 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 determined to be "compliant", if the region (i.e., the export destination from the third party) is a whitelist country (e.g., the United States), it is necessary to obtain export trade management permission (e.g., a special general comprehensive permission) from the export trade manager (e.g., the Ministry of Economy and Industry). In this way, the third party can submit an export management list, including a compliance / non-compliance determination letter and the third party (application developer)'s nationality, name, export management regulations determination result (in this case, "compliant"), a backup of the export trade management license, etc., to the operation management company 2 belonging to the region, the application, and the access declaration list related to the application described later.

[0330] Furthermore, when the export destination is a non-whitelisted country, store sales (=inventory sales) of the app are generally not permitted, and face-to-face sales (i.e., obtaining export permission for the app each time) are required to sell the app.

[0331] Systems performed by a third party to assist with applications' compliance / non-compliance determination and export license application are well known to those skilled in the art. In this embodiment, the store registration server 300 used to register applications for store sales in the sales management server system 10 does not assist with applications' compliance / non-compliance determination and export license application. The third party utilizes known techniques to appropriately perform application compliance / non-compliance determination and export license 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. Figure 11 FIG. 3 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 accepts applications developed by application developers (both those in the region and third parties outside the region) and access declaration lists for review. Approved applications are then associated with the access declaration lists and registered in the application DB 250. Furthermore, if the application developer is a third party, the store registration server 300 also associates the application with the export management list and registers it in the application DB 250.

[0335] like Figure 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 comprehensively controls the store registration server 300 by executing various programs stored in the storage unit 320 .

[0337] For example, the CPU executes a program for processing the acceptance of applications, access declaration lists, compliance / non-compliance determination forms when the application developer is a third party, and compliance / non-compliance determination lists (hereinafter referred to as "application acceptance processing"). In addition, the CPU also executes a program for reviewing the 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 processing the registration of the application to application DB250 (hereinafter referred to as "application registration processing") based on the results of the application review processing. In addition, the CPU executes a program for processing the query of 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 containing compliance / non-compliance determinations and export management regulations determination results when the application developer is a third party. In addition to this, 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 containing 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] Furthermore, the application accepting unit 311 may also input and accept, via a predetermined input interface, a computer-readable recording medium storing an application, an access declaration list, and, when the application developer is a third party, an export control list including a compliance / non-compliance determination form and export control regulations determination results. Examples of computer-readable recording media include magnetic recording media (e.g., floppy disks, magnetic tapes, hard disk drives), magneto-optical storage media (e.g., magneto-optical disks), optical disks (e.g., CD-ROMs, DVDs, and Blu-Ray Discs (registered trademark)), and other media well known to those skilled in the art.

[0341] In particular, when the application developer is a third party, the application acceptance unit 311 confirms that the received data contains an export control list, including a compliance / non-compliance determination form and export control regulations determination results. If the application developer is a third party and the received data does not contain the export control list, for example, an error message may be returned. Alternatively, the export control list, including the compliance / non-compliance determination form and export control regulations determination results, may be placed in a waiting state. Furthermore, the received data may be rejected and returned as a rejection.

[0342] The access declaration list is used when executing an application on an edge server, indicating whether edge device functions are being used and / or whether access is being made to edge device processed data. Specifically, the access declaration list indicates whether functions related to edge device 500 are being used and / or whether access is being made to edge device 500 processed data. "Manufacturing equipment" refers to equipment that qualifies as edge device 500, with application developers specifying CNC machine tools, industrial equipment, industrial robots, and the like. Furthermore, the access declaration list is in a predetermined format, and application developers configure it accordingly, for example by checking a checkbox to determine whether access is being made.

[0343] More specifically, the processing data of the edge device 500 includes, for example, data indicating the operating status of the edge device 500, data indicating the production status, data indicating the quality status of the product, and data indicating events (historical records) such as the operating status. This processing data is pre-data-modeled (i.e., standardized), and access can be set based on the standardized data model. In this way, application developers can accurately declare whether access has occurred based on the standardized model, and the application review side can standardize the review process by eliminating arbitrary wording by application developers. In addition, a standardized interface for accessing 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 analyze the application's source code to review whether the application's use of edge device 500 functions and / or access to processed data on the edge device 500 is consistent with the access indicated in the access declaration list. Furthermore, the application review unit 312 can also analyze the application-related actions executed by the edge server 400 to review whether the application's use of edge device 500 functions and / or access to processed data on the edge device 500 is consistent with the access indicated in the access declaration list.

[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 access declaration list as needed. 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 access declaration list as needed. In addition, the confirmation result of being able to 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 given of the application acceptance unit 311 accepting applications, access declaration lists, export management lists including compliance / non-compliance determinations and export management regulations determination results, and the application review unit 312 reviewing applications, access declaration lists, export management lists including compliance / non-compliance determinations and export management regulations determination results, etc., when the application developer is a third party, but the present invention is not limited to this.

[0348] For example, if the application developer is a third party, the application review unit 312 first checks the compliance / non-compliance determination form and the export control regulations determination results based on the application, the access declaration list, and the export control regulations determination results. If the compliance is confirmed, the application review unit 312, for example, analyzes the application's metacode to examine whether the application's use of edge device 500 functions and / or the content of access to processed data on the edge device 500 is consistent with the access indicated in the access declaration list. Furthermore, the application review unit 312 can analyze the application-related actions executed by the edge server 400 to examine whether the application's use of edge device 500 functions and / or the content of access to processed data on the edge device 500 is consistent with the access indicated in the access declaration list.

[0349] If the application review unit 312 determines that the application's use of edge device 500 functions and / or access to edge device 500 processed data is consistent with the access indicated in the access declaration list, and if the application developer is a third party and the application is approved for store sales in the region (e.g., the United States), the application registration unit 313 approves the application's distribution management through the sales management server system 10. Furthermore, the application registration unit 313 registers the approved application with the access declaration list, and the export management list (including compliance / non-compliance determinations and export control regulations determinations if the application developer is a third party) in the application DB 250. The application registration unit 313 notifies the user of the application's registration, i.e., the application's registration for store sales in the region (e.g., the United States), via a terminal communicatively connected to the store registration server 300 (e.g., a terminal provided by the application developer or a management terminal communicatively connected to the store registration server 300). Alternatively, the application registration unit 313 may use email for notification.

[0350] The registered application management unit 314 provides an application registration management screen 3140 for querying registration management information on applications registered in a store in the application DB 250 . Figure 12 This shows an example of the application registration management screen. Figure 12As shown, the application registration management screen displays information such as the registration date and time 3141, the application developer's name 3142, the application developer's country of residence 3143, the product name 3144, the export control regulations determination result 3145 for the country of residence, and a copy (link information) of the compliance / non-compliance determination form 3146 for each registered application. The items displayed on the application registration management screen are not limited to these. Additional items may be added as needed.

[0351] This allows the person in charge of the operating and management company 2 to easily confirm the registration status of apps registered with the store. Furthermore, although not shown, arbitrary items can be used as search items, allowing searches to be performed using arbitrary search conditions. For example, by specifying a range of registration dates and times, it is possible to identify apps registered with the store during that period. Furthermore, by specifying the country of residence of the app developer, it is possible to confirm the store registration status of apps developed by third parties residing in the specified country.

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

[0353] Next, the processing flow of the store registration server 300 in the application sales management system 1000 will be described. Figure 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, step S61 illustrates a process in which the application acceptance unit 311 of the store registration server 300 accepts data required for store sales registration from an application developer's terminal (not shown) via a network, but the present invention is not limited to this. As described above, for example, a computer-readable recording medium storing data required for store sales registration can be input (accepted) to the store registration server 300 by the person in charge of the operating and management enterprise 2 via a prescribed input interface. Here, the so-called data required for store sales registration refers to the following data: at least an application program, an access declaration list, and, when the application developer is a third party (application developer), an export control list including a compliance / non-compliance determination form and export control regulations determination results.

[0355] Furthermore, 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 the 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 acceptance 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 ID, product name, and export management list of the application, and also based on the access declaration list as needed, 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 proceeds to step S64. If not, then proceeds to step S67.

[0360] In step S64, the store registration server 300 (application review unit 312) reviews whether the application's use of edge device 500 functions and / or the content of access to processed data on the edge device 500 matches the access indicated in the access report list. If the determination is consistent (Yes), the process proceeds to step S65. If the determination is inconsistent (No), the process proceeds 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 via a terminal or email that the application has been registered for store sales in the region (e.g., the United States). The store registration server 300 (application registration unit 313) then terminates this processing.

[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 has been determined to be unavailable for store sales registration in the region (e.g., the United States). The store registration server 300 (application registration unit 313) then terminates this processing.

[0364] The above describes 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 results related to the application when the operating management enterprise 2 registers the third-party application developed by the third party for local store sales through an application from the third party. The application that has been registered for store sales is reviewed and approved, so high reliability is guaranteed.

[0366] As described above, with respect to this embodiment, in a corresponding overseas application sales management system 1000 in which only the application registered for online store sales can be purchased in a third country (for example, the United States), the store registration server 300 accepts the third-party application, the export management list including the compliance / non-compliance determination document and the trade management regulations determination result of the third-party application when registering the store sales of the third-party application developed by the application developer residing in a country other than the third country, and when it is determined that the third-party application can be sold in the store in the third country, the third-party application, the export management list including the compliance / non-compliance determination document and the trade management regulations determination result of 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 registers a store in a third country, the store registration server 300 notifies a contact destination of the third party that the store registration has been completed.

[0369] This allows the third party to 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 registration management information related to applications registered with the store in the application DB 250 to a terminal (not shown) of the person in charge of the operation and management company 2 that operates the overseas application sales management system 1000. Specifically, the store registration server 300 associates all applications registered for store sales with each other and provides registration management information such as the application registration date and time, the application developer's name, the application developer's country of residence, the application's product name, the determination of export control regulations of the country of residence (completed or not required), and a copy of the determination document (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] Furthermore, it is preferable to locate an application database storing applications registered for sale in third-country online stores. This allows applications developed by developers residing in third countries to remain circulated within the third country and not be subject to import and export controls. Only third-party applications developed by third parties become subject to import and export controls, thereby facilitating import and export operations.

[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. This allows the overseas application sales management server system 10 to be universally compatible with whitelist countries.

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

[0375] Figure 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 comprehensively 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 based on the license associated with the application.

[0381] More specifically, when the application execution unit 411 starts an application stored in the storage unit 420, the license control unit 412 reads the license corresponding to the application. Based on the read license, the license control unit 412 identifies the edge device 500 that is permitted to serve as the input / output destination for the application. More specifically, for example, based on the license, the license control unit 412 determines whether the edge device 500 requesting a connection to the application satisfies the conditions specified in the license.

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

[0383] When the edge device 500 does not meet 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 edge device 500 functions and / or access to processed data of the edge device 500 by the application program executed by the application execution unit 411 based on the contents of the access declaration list. Furthermore, the access control unit 413 permits the use of functions and / or access to processed data of the edge device 500 only for the edge devices 500 that have been declared as having access according to 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 a request to access the processing 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, upon receiving information indicating that an application is unauthorized from the sales management server system 10 , the access control unit 413 forcibly stops the application if the application is already executed.

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

[0389] When detecting an access request from an application 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 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 (eg, 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 functions and / or access to the processed data of the edge device 500 by the executed application based on the access declaration list, thereby making it possible to set a structure that prevents unauthorized access and 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, implementation by software means that a computer reads a program (application program) and executes it.

[0395] Various types of non-transitory computer readable media can be used to store the program used in the present invention and provide it to the computer. Non-transitory computer readable media include various types of tangible storage media. Examples of non-transitory computer readable media include: magnetic storage media (e.g., floppy disks, magnetic tapes, hard disk drives), magneto-optical storage media (e.g., optical magnetic disks), CD-ROMs (Read Only Memory), CD-Rs, CD-R / Ws, semiconductor memories (e.g., mask ROMs, PROMs (Programmable ROMs), EPROMs (Erasable PROMs), flash ROMs, RAMs (random access memory)). In addition, the program can be supplied to the computer via various types of transitory computer readable media. Examples of transitory computer readable media include electrical signals, optical signals, and electromagnetic waves. Transitory computer readable media can supply the program to the computer via wired communication paths such as wires and optical fibers or wireless communication paths.

[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] Furthermore, the management server 100 , the publishing server 200 , and the store registration server 300 may be independent virtual servers included in a predetermined server or a predetermined cloud.

[0400] Figure 15 This is a diagram showing an example of server configuration. Figure 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 for each region n (n≥1), and in this dedicated region n, the management server 100-n corresponding to region n is set up as, for example, IaaS (Infrastructure as a Service).

[0401] This allows for a unified maintenance of hardware resources serving as infrastructure, thereby reducing maintenance costs.

[0402] Furthermore, as described above, the distribution server 200 - n and the application DB 250 - n are preferably installed in each region n in order to simplify import and export management.

[0403] also, Figure 15 Although the store registration server 300 - n is not shown in the figure, the store registration server 300 - n is preferably installed in each area n similarly to the distribution server 200 - n when physically accepting an application for store registration.

[0404] Furthermore, while the hardware configuration is exemplified as a distributed system consisting of a management server 100, a publishing server 200, and a store registration server 300, the present invention is not limited thereto. For example, the various functional units contained in each server may be distributed across the servers so that they are communicatively connected. Distributed systems are well known to those skilled in the art, and those skilled in the art can appropriately implement functional decentralization as needed.

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

[0406] In the above embodiment, various information is stored in the storage unit 120 of the sales management server system 10. However, the various information in the storage unit is merely illustrative and may include other information. Furthermore, the method of storing data is merely an example.

Claims

1. A management system for overseas application sales that 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 management system for overseas application sales corresponding to the third country being characterized by: The corresponding overseas application sales management system has: Ministry of Communications; an application DB storing the application programs registered for online store sales in the third country; and Store Registration Control Department, The store registration control unit includes: an application acceptance unit configured to accept the application, an access declaration list related to the application, and an export management list, wherein, when the application is developed by a third party in a country other than the third country, the export management list includes a compliance / non-compliance determination and a trade management regulations determination result for the application; an application review department, which reviews the applications accepted by the application acceptance department, the access declaration list related to the applications, and the export management list when the application developer is a third party; an application registration unit, which, when the developer of the application is a third party, registers the application, the access declaration list related to the application, and the export management list in the application DB in a manner corresponding to each other, if the application review unit determines that the application can be sold in stores in the third country; and The registered application management department provides the terminal of the person in charge of the operation and management company that operates the corresponding overseas application sales management system with registration management information related to the application registered in the store in the application DB, The registered application management unit further displays the search result by inputting arbitrary search conditions including at least the registration date and time and the country of residence of the application developer as search items into the terminal. The access declaration list is a list in a predetermined format, and is used when executing an application through an edge server to indicate whether a function of an edge device is used and / or whether there is access to processing data of the edge device, wherein the processing data of the edge device includes at least data indicating an action state related to the edge device, data indicating a production status, data indicating a quality status of a product, and / or data indicating an event of an operating status. When the result of the review by the application review department is that the use of the edge device function of the application and / or the access content to the processing data of the edge device are determined to be consistent with whether there is access represented 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 stores in the third country, the application registration department approves the release management of the application through the corresponding overseas application sales management system, and registers the approved application and access declaration list, wherein the review is based on the analysis of the source code of the application to review whether the use of the edge device function of the application and / or the access content to the processing data of the edge device are consistent with whether there is access represented by the access declaration list, or the review is based on the analysis of the action related to the application performed by the edge device to review whether the use of the edge device function of the application and / or the access content to the processing data of the edge device are consistent with whether there is access represented by the access declaration list.

2. The overseas application sales management system according to claim 1, characterized in that: The application registration unit further notifies a contact destination of the third party that the application is registered for store sales in the third country.

3. The overseas application sales management system according to claim 1 or 2, characterized in that: The export control list includes the name and country of residence of the third party in correspondence with the application.

4. The overseas application sales management system according to claim 1 or 2, characterized in that: The application review unit further displays an export management list confirmation screen on the terminal of the application review manager, the export management list confirmation screen displaying the export management list together with the ID and product name of the application whose developer is a third party.

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

6. The overseas application sales management 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.

Images