Application sales management server system, application sales management system, management control device and release control device

Abstract

The present invention provides an application sales management server system and the like that enables a suitable person to be responsible for the function or trustworthiness of an application. The sales management server system manages the online store sales of applications run by an edge server connected to one or more edge devices, and has an application database storing applications, a management control device, and a release control device. The management control device has: a purchase request sending unit that sends purchase request information of an application that has been commissioned via a communicably connected user terminal to a communicably connected developer terminal; a result sending unit that sends release permission information to the user terminal when the purchase authorization information received from the developer terminal indicates that the purchase is allowed; and a release control device that has: an application publishing unit that publishes the application corresponding to the release permission information of the release request information sent by the user terminal to the determined edge server.

Description

Technical Field

[0001] The invention relates to an application sales management server system, an application sales management system, a management control device and a publishing control device. Background Art

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

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

[0004] As an example, an application sales management server system is known (e.g., Patent Document 1), which manages the sales of applications run by an edge server that is communicatively connected to one or more edge devices, the application sales management server system comprising: a communication unit, a control unit, and a storage unit, the application sales management server system being communicatively connected to a user terminal of an intermediary that mediates the sale of the application and a user terminal of an end user that uses the edge device and the edge server via the communication unit, the control unit comprising: a release permission information issuing unit, which issues release permission information that associates the application and the license associated with the application to the application sales management server system based on a purchase request for the application from the user terminal of the intermediary; and an application publishing unit, which, based on receiving the release permission information from the user terminal of the end user, publishes the application and the license associated with the release permission information to the edge server together, the license associated with the application containing information on the number of edge devices that can be connected to each license, so that the edge server controls the number of connected edge devices associated with the application based on the license.

[0005] The developers of the applications know the contents of the applications sold by such application stores. On the other hand, the operators of the application stores cannot know the contents of the applications unless the developers of the applications make them public. However, the operators of the application stores have excessive responsibility for the functions and reliability of the applications they sell.

[0006] Prior art literature

[0007] Patent Literature

[0008] Patent Document 1: Japanese Patent Application Publication No. 2019-21090 Summary of the invention

[0009] Therefore, it is desirable that a structure be established in which the person in charge has responsibility for the functionality and reliability of the application.

[0010] Technical solution (1): One method of the present disclosure provides an application sales management server system, which manages the online store sales of applications run by an edge server that is communicatively connected to one or more edge devices, the application sales management server system comprising: an application database that stores the applications created by developers and registered for online store sales; a management control device that manages the online store sales of the applications that can be purchased and are registered for online store sales and stored in the application database; and a publishing control device that publishes the applications to the edge server, the application sales management server system being able to communicate with user terminals owned by users who use the edge devices and the edge servers, and developer terminals owned by the developers via a communication network. The management control device is communicatively connected, and comprises: a purchase request sending unit, which sends purchase request information of the application commissioned by the user via the user terminal to the developer terminal of the application; and a result sending unit, which sends purchase permission information including release permission information associated with the application to the user terminal when the permission information related to the purchase commission received from the developer terminal indicates that the application can be purchased, and notifies the user terminal that the application cannot be purchased when the permission information related to the purchase commission indicates that the application cannot be purchased. The release control device comprises: an application release unit, which releases the application corresponding to the release permission information to the edge server based on the receipt of release request information including the release permission information sent by the user terminal.

[0011] Technical solution (2): One method of the present disclosure provides a management control device possessed by an application sales management server system, wherein the application sales management server system manages online store sales of applications run by an edge server that is communicatively connected to one or more edge devices, and the management control device manages online store sales of the applications that can be purchased and are stored in an application database that stores the applications created by the developer and have been logged in for online store sales. The management control device is communicatively connected to a user terminal possessed by a user who uses the edge device and the edge server, and a developer terminal possessed by the developer via a communication network, and the management control device comprises: a purchase request sending unit that sends purchase request information of the application that has been commissioned by the user via the user terminal to the developer terminal of the application; and a result sending unit that, when the permission information related to the purchase commission received from the developer terminal indicates that the purchase is allowed, sends purchase permission information including release permission information associated with the application to the user terminal, and when the permission information related to the purchase commission indicates that the purchase is not allowed, notifies the user terminal that the purchase is not allowed.

[0012] Technical solution (3): One method of the present disclosure provides a publishing control device possessed by an application sales management server system, wherein the application sales management server system manages the online store sales of applications run by an edge server that is communicatively connected to one or more edge devices, wherein the publishing control device publishes the application created by the developer and stored in an application database to the edge server, and the publishing control device is communicatively connected to a user terminal possessed by a user who uses the edge device and the edge server, and a developer terminal possessed by the developer via a communication network, wherein the publishing control device comprises: an application publishing unit, which publishes the application corresponding to publishing permission information to the edge server based on the receipt of a publishing request information from the user terminal, wherein the publishing request information includes the publishing permission information associated with the application contained in the purchase permission information sent by the management control device to the user terminal, wherein the management control device manages the online store sales of the application that can be purchased and is registered for online store sales and stored in the application database.

[0013] Effects of the Invention

[0014] According to one embodiment, it is possible to provide an application sales management server system, an application sales management system, a management control device, and a distribution control device that allow a qualified person to be responsible for the function or trustworthiness of an application. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Figure 1 This is a schematic diagram showing the basic structure of the application sales management system in this embodiment.

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

[0017] Figure 3 It is a diagram showing an example of a storage unit of a management server included in the sales management server system in the present embodiment.

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

[0019] Figure 5A This is a functional block diagram of a distribution server included in the sales management server system in this embodiment.

[0020] Figure 5B This is a diagram showing an example of a storage unit of a distribution server included in the sales management server system in the present embodiment.

[0021] Figure 6 It is a diagram showing an example of an application DB included in the sales management server system in this embodiment.

[0022] Figure 7 This is a flowchart showing the browsing information providing process of the management server in this embodiment.

[0023] Figure 8 This is a flowchart showing the purchase request processing of the management server in this embodiment.

[0024] Fig. 9 This is a flowchart showing the sales permission processing of the sales management server system in this embodiment.

[0025] Fig.10 This is a flowchart showing the application publishing process of the publishing server in this embodiment.

[0026] Fig.11 This is a schematic diagram showing the basic structure of an application sales management system in a modified form.

[0027] Description of Reference Numerals

[0028] 1000, 1000-2 application sales management system, 10, 10-2a, 10-2m sales management server system, 100, 100-2a management server, 110, 210 control unit, 111 reading information providing unit, 112 purchase request processing unit, 113 sales permission processing unit, 114 release management processing unit, 120, 220 storage unit, 121 application management information storage unit, 122 user storage unit, 123 release management storage unit, 124 application developer information storage unit, 200, 200-2a, 200-2m release server, 211 matching information receiving unit, 212 application release processing unit, 221 release information storage unit, 250, 250-2a, 250-2m application DB, 300 developer terminal, 400 user terminal, 500 edge server, 600 edge device, N1, N2 network. DETAILED DESCRIPTION

[0029] The configuration of the application sales management system 1000 according to this embodiment will be described.

[0030] Figure 1 The application sales management system 1000 shown includes: an application sales management server system 10 (hereinafter, also referred to as "sales management server system 10"), a developer terminal 300, a user terminal 400, an edge server 500, and an edge device 600. The sales management server system 10, the developer terminal 300, the user terminal 400, and the edge server 500 are connected to each other through a network N1 so as to be able to communicate. The network N1 is, for example, the Internet, a VPN (Virtual Private Network), a public telephone network, etc. There is no particular limitation on the specific communication method in the network N1, such as wired connection or wireless connection.

[0031] like Figure 1 As shown, the sales management server system 10 is composed of, for example, a management server 100 as a management control device, a distribution server 200 as a distribution control device, and an application DB (database) 250 .

[0032] In addition, the sales management server system 10 may be composed of one server having the functions of the management server 100, the publishing server 200, and the application DB250, or may be composed of two servers, namely, one server having the functions of the publishing server 200 and the application DB250, and the management server 100. In addition, the functions of the management server 100, the publishing server 200, and the application DB250 may be composed of a plurality of servers, or the processing may be dispersed among the servers. Furthermore, the sales management server system 10 may be, for example, configured as follows: the management server 100 is connected to the edge server 500 and the like via the network N1, and the publishing server 200 is not connected to the network N1, but communicates with the edge server 500 and the like via the management server 100. In addition, it is preferred that the edge device 600 is configured to be connected to the management server 100 so as to be communicable, but not connected to the publishing server 200 so as to be communicable.

[0033] Furthermore, the management server 100 , the distribution server 200 , and the application DB 250 are not necessarily limited to physically independent server devices, but may be independent virtual servers included in a cloud or the like.

[0034] The developer terminal 300 and the user terminal 400 are, for example, personal computers (PCs) and are connected to the sales management server system 10 so as to be communicable.

[0035] The developer terminal 300 is a terminal of an application developer (hereinafter also referred to as an "application developer"), and is used, for example, when registering an application created by the application developer in the sales management server system 10. The application sent by the developer terminal 300 is registered in the application DB 250 after being reviewed in the sales management server system 10. In addition, when there is a purchase request for an application created by the application developer from a user, the developer terminal 300 sends permission information to the user to determine whether to allow the sale of the application.

[0036] The user terminal 400 is, for example, a terminal used by an end user who wishes to purchase a server application program run by the edge server 500. Here, regarding the user terminal 400, Figure 1 The example is shown as being set outside the factory facility, but it can also be set inside the factory facility. In addition, the user can access the sales management server system 10 through the user terminal 400 and browse the content of the application that the user can purchase. In addition, the user can entrust the purchase of the application through the user terminal 400.

[0037] In addition, a user ID (Identification) for accessing the sales management server system 10 is given only to users who meet preset conditions (qualifications, etc.).

[0038] The edge server 500 is a server that executes the application purchased from the sales management server system 10 and performs the prescribed information processing related to the application. As a server application run by the edge server 500, for example, a server that collects data indicating the action status of the edge device 600 described later, data indicating the production status, data indicating the quality status of the product, data indicating the operation status, etc., and performs information processing is listed, but it is not limited to this.

[0039] The edge device 600 refers to, for example, manufacturing devices such as CNC machine tools, industrial equipment, industrial robots, etc., and devices attached to manufacturing devices such as image sensors and PLCs (programmable logic controllers) installed at a manufacturing site such as a factory. For example, one or more edge devices 600 constitute a production line or production unit of a factory.

[0040] In this way, the edge device 600 can be said to have a client function for the edge server 500. The edge server 500 and one or more edge devices 600 are installed in, for example, a user's factory facility, and are communicatively connected via a network N2 such as a LAN (Local Area Network).

[0041] The sales management server system 10 is an online store system for executing sales management processing for users who wish to purchase a server application program run by the edge server 500 .

[0042] As described later, when the user can, for example, entrust the management server 100 to purchase a desired server application via the user terminal 400, if the user obtains permission from the application developer, the user can obtain the serial number (license key) related to the server application from the management server 100. Then, based on the serial number, the user can cause the publishing server 200 to publish (install) the server application to the edge server 500. Here, the serial number (license key) is uniquely given identification information, and is publishing permission information given when the publishing of the server application is permitted.

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

[0044] [Configuration of Management Server 100]

[0045] Figure 2 The management server 100 shown includes a control unit 110 , a storage unit 120 , and a communication unit 130 .

[0046] The control unit 110 may be a central processing unit (CPU), and performs overall control of the management server 100 by executing various programs stored in the storage unit 120 .

[0047] The communication unit 130 is a communication control device that transmits and receives data to and from external devices (for example, the developer terminal 300 , the user terminal 400 , and the edge server 500 ) via the network N1 .

[0048] In the management server 100, the control unit 110 includes a browsing information providing unit 111, a purchase request processing unit 112, a sales permission processing unit 113, and a publishing management processing unit 114 as functional units based on the programs stored in the storage unit 120. The storage unit 120 includes an application management information storage unit 121, a user storage unit 122, a publishing management storage unit 123, and an application developer information storage unit 124 in addition to the programs executed by the control unit 110.

[0049] Before describing each functional unit of the control unit 110 , first, the storage unit 120 will be described.

[0050] <Application Management Information Storage Unit 121>

[0051] The application management information storage unit 121 is a storage area for storing management information (metadata) related to applications that can be purchased in the sales management server system 10. In this embodiment, the application program itself is not stored in the application management information storage unit 121, but is stored in the application DB 250 described later.

[0052] like Figure 3 As shown, as an example, the application management information storage unit 121 can store application name (and / or product name), target model information, input information, application manual, price information, application developer ID, sales area, etc. in correspondence with the application ID. In addition, the data stored in the application management information storage unit 121 is not limited to this. Some of the exemplified data items and other data items may also be stored.

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

[0054] The target model information is model information of the edge device 600 that is the input / output target of the application, and is, for example, the model name of a CNC machine tool, industrial equipment, industrial robot, or the like.

[0055] The input information is edge device information including input data information input from the edge device 600 and the like.

[0056] The description of the application includes, for example, descriptions related to the license as descriptions related to the structure of the application. The descriptions related to the license include, for example, whether it is a license for specifying the edge device 600 that uses the application, whether there is a specification of the edge device 600, whether it is necessary to purchase a certain number of edge devices 600 that can be used simultaneously, or whether there is no limit on the number of edge devices 600 that can be used simultaneously. In addition, descriptions related to whether there is a contract update are also included regarding the use of the application.

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

[0058] The application developer ID is identification information for identifying the application developer of the application.

[0059] The salesable region is information on a region (for example, a country name) in which the application developer is allowed to sell the application.

[0060] <User storage unit 122>

[0061] The user storage unit 122 is a storage area for storing information related to the user who has set up the edge server 500 that can be communicatively connected to the sales management server system 10. In addition, in order to set up the edge server 500, it is a prerequisite that the user satisfies the predetermined conditions (qualifications, etc.) set in advance. The user who has set up the edge server 500 is a user who is allowed to access the sales management server system 10. In other words, a user ID for accessing the sales management server system 10 is given. In addition, as users, in addition to end users, system integrators and specialized businesses such as machine tool manufacturers can also be included.

[0062] like Figure 3 As shown, the user storage unit 122 stores user information, edge server information, etc. in correspondence with the user ID.

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

[0064] As an example, the user information may include information related to the user, such as the user's name, agent name, address including country name (region), telephone number, email address, URL, user level, and rights that can be purchased. Here, the user level is a level determined by the attributes of the user, and is classified into end users, specialized businesses including, for example, sales stores and system integrators, and specialized businesses including, for example, machine tool manufacturers and equipment manufacturers. In addition, the rights that can be purchased are information for identifying whether the user (specialized business or end user) identified by the user ID is allowed to entrust the purchase of the application to the sales management server system 10.

[0065] The user information is not limited thereto. It may also include a portion of the exemplified data items and other data items. In addition, the user information is generated, for example, when the edge server is first set up for the user, and is subsequently updated, for example, whenever a situation involving a change in the user information occurs (for example, the addition of an edge server, etc.).

[0066] In particular, when the user is an end user, the edge server information is information related to the edge server 500 installed in the factory or manufacturing site involved in the user, and is information that specifies the edge server 500 that is the distribution destination of the application. As an example, the edge server information may include an edge server ID for identifying the edge server 500, the location where the edge server is installed, and address information on the communication network such as the IP address of the edge server 500. In addition, when there are more than one edge server 500 in the factory involved in the user, the edge server ID is required to identify each edge server 500.

[0067] In addition, the edge server information may include information related to the edge device 600 that may be a candidate client of the edge server 500 and may perform input and output with the edge server 500. The information related to the edge device 600 may include an edge device ID for identifying the edge device 600, a model name of the edge device 600, an address of the edge device 600 on the communication network (e.g., an IP address), and the like.

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

[0069] <Release management storage unit 123>

[0070] The delivery management storage unit 123 is a storage area that stores delivery management information related to an application delivered to an arbitrary edge server 500 in association with the edge server 500 of the delivery destination.

[0071] The publishing management storage unit 123 associates the published application information with the edge server 500 of the publishing destination and stores it. Figure 3 As shown, the publishing management storage unit 123 stores, for example, publishing management information, which uses the edge server ID of the edge server 500 that identifies the publishing destination and the application ID that identifies the published application as search keywords, respectively, and uses the data including the edge server ID of the edge server 500 of the publishing destination and the application ID of the published application as search keywords (compound keywords). In the publishing management information, as an example, in addition to the above-mentioned search keywords, the order number, order date and time, serial number, license, purchase date (license acquisition date), publishing date, etc. are also stored. In addition, as other items, various data used to manage the published application can also be stored. As other items, for example, there are the next scheduled contract date when the current license contract is extended to continue the contract, the next contract update notification date for the confirmation notification, the next contract update notification destination address used when notifying, and the notification completion mark indicating whether the notification has been made. In addition, the data included in the publishing management information is not limited to this. It can also include a part of the data items illustrated and other data items.

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

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

[0074] The serial number is a number uniquely assigned to a purchased application.

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

[0076] 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).

[0077] The release date is the date when the application is released to the edge server 500 .

[0078] Therefore, for each application that is published, it is possible to easily retrieve information such as in which edge server 500 the application was published, when the purchase request was received, and when.

[0079] <Application developer information storage unit 124>

[0080] The application developer information storage unit 124 stores application developer information including the application developer's name, nationality, address, URL, contact email address, etc. in association with the application developer ID.

[0081] Furthermore, the storage unit 120 may store order management information for managing a processing status related to a purchase request for an application from the time when the purchase request for the application is received from the user.

[0082] The order management information may be associated with the order number, for example, including the order date and time, the application ID of the order, the user ID of the user who ordered the application, etc. Furthermore, when the release of the application is permitted for the order, the information may be stored in the release management storage unit 123. Furthermore, when the release of the application is not permitted for the order, the information may be directly stored in the storage unit 120 as an order history record, or may be deleted.

[0083] Next, each functional unit of the control unit 110 of the management server 100 will be described.

[0084] like Figure 2 As shown, the management server 100 has: a browsing information providing unit 111, a purchase request processing unit 112 as a purchase request sending unit and a result sending unit, a sales permission processing unit 113 as an issuing unit and a matching information sending unit, and a publishing management processing unit 114 as a publishing request sending unit.

[0085] <Browsing information providing unit 111>

[0086] In response to a request for browsing application information from a user received from the user terminal 400 , the browsing information providing unit 111 provides application information that can be browsed by the user.

[0087] The browsing information providing unit 111 refers to the application management information storage unit 121 and the user storage unit 122 , extracts application information related to applications that can be provided to the registered user, and provides the information to the user terminal 400 .

[0088] The browsing information providing unit 111 generates a browsing screen 160 including the extracted application information and provides it to the user terminal 400. In addition, when a plurality of applications are extracted, the browsing information providing unit 111 may generate an application list screen and transmit it to the user terminal 400. Furthermore, when a selection related to one application is received from the user terminal 400, the browsing information providing unit 111 may extract information related to the selected application from the application management information storage unit 121 and generate the browsing screen 160.

[0089] Figure 4The browsing screen 160 shown includes, for example, an application manual 165 and a manual 166 related to the application license. The application manual 165 includes, for example, an application ID 165a, an application product name 165b, an application developer 165c, and a manual 165d related to the content of the application. In addition, the manual 166 related to the license includes, for example, price information 166a, a license quantity 166b, license description information 166c, and an edge server ID designation unit 166d. Since the browsing screen 160 includes the manual 166 related to the license, each user can confirm the required license-related information.

[0090] In addition, the browsing screen 160 can also be used as a purchase entrustment screen. In this case, the browsing screen 160 can be made to display a purchase button, etc. in a manner that enables purchase entrustment, so that users with the authority to purchase can make a purchase entrustment. In addition, when making a purchase entrustment, the user can enter the purpose of use of the application. In addition, when the user selects an application as a purchase candidate while browsing the application, the browsing information providing unit 111 stores the selected application ID, etc. in a temporary storage purchase candidate storage unit (so-called "shopping cart") (not shown). In addition, the browsing information providing unit 111 can display the browsing screen 160 as a purchase entrustment screen by designation from the user, and the browsing screen 160 displays a purchase button, etc. for purchasing the application ID (product name) stored in the purchase candidate storage unit (shopping cart) (not shown) for each application or in general.

[0091] <Purchase Request Processing Unit 112>

[0092] Figure 2 The purchase request processing unit 112 shown in response to receiving a purchase request for an application from the user terminal 400, sends a purchase request message to the developer terminal 300 of the application developer who created the application. The purchase request message includes an address and an application name, and the address includes the name and nationality of the user determined by the user ID. In addition, the purchase request message may also include the number of licenses, the purpose of use of the application, etc.

[0093] In addition, the purchase request processing unit 112 obtains the order number for each application with a purchase request, and stores the order management information including the order date and time, the application ID of the order, the user ID, etc. in the storage unit 120. In addition, the payment of the fee for the application with a purchase request is confirmed by a known method (for example, credit card, automatic account deduction, etc.) before downloading the application.

[0094] The application developer of the developer terminal 300 that has received the purchase request information refers to the user-related information included in the purchase request information through the processing performed by the purchase request processing unit 112, and determines whether to allow the sale of the application program to the user. Furthermore, the developer terminal 300 sends the sales-related determination result based on the application developer, that is, the approval information related to the purchase request, to the management server 100.

[0095] The purchase request processing unit 112 receives permission information related to the purchase request from the developer terminal 300. And, when the permission information indicates that the purchase is allowed, the purchase request processing unit 112 performs the processing related to the sales permission processing unit 113 to be described below. On the other hand, when the permission information indicates that the purchase is not allowed, the purchase request processing unit 112 sends a message to the user terminal 400 that the application cannot be purchased with respect to the purchase entrustment. In this case, the purchase request processing unit 112 sends an email ("rejection email") or the like to notify that the purchase of the application has been rejected and the purchase procedure has been completed to the contact information (e.g., email address) of the user who has made the purchase entrustment. As a result, the processing related to the order case is completed.

[0096] <Sales permission processing unit 113>

[0097] The sales permission processing unit 113 is a process performed when the permission information related to the purchase request is changed to purchase permission through the processing of the purchase request processing unit 112.

[0098] The sales permission processing unit 113 generates a serial number (license key) of the application corresponding to the purchase request information, and transmits purchase permission information including the generated serial number to the user terminal 400 .

[0099] In addition, the purchase request processing unit 112 may send an email containing an ID and a password as purchase permission information to the user who has requested the purchase of the application, and the ID and password are used to register on a dedicated screen (not shown) displaying the serial number of the application. Then, after the dedicated screen is displayed, when the user registers using the ID and password recorded in the email, the purchase request processing unit 112 may display the serial number on the dedicated screen. Thus, even if a user pretends to be a third party and uses the user terminal 400 of a user who has the purchase authority, the serial number is not notified to the third party, and the structure with improved security can be used.

[0100] Then, the sales permission processing unit 113 sends matching information including the generated serial number to the distribution server 200. The matching information includes, in addition to the serial number, a user ID, an application ID, a license, an edge server ID of the edge server 500 to be the distribution destination, and a distribution destination address.

[0101] <Publishing Management Processing Unit 114>

[0102] The distribution management processing unit 114 manages the distribution management information of the application.

[0103] The publishing management processing unit 114 receives publishing management information from the application publishing processing unit 212 (described later), and stores the published application information in association with the edge server 500 of the publishing destination. As described above, for example, the publishing management processing unit 114 stores the publishing management information in the publishing management storage unit 123, wherein the publishing management information uses the edge server ID of the edge server 500 of the publishing destination and the application ID of the published application as search keywords, respectively, and uses data including the edge server ID of the edge server 500 of the publishing destination and the application ID of the published application as a search keyword (compound keyword).

[0104] The release management processing unit 114 provides a function of searching / matching the release management information stored in the release management storage unit 123 via an operation management terminal (not shown), for example, for a manager of an operation management company that operates and manages the sales management server system 10. Thus, for each released application, it is possible to easily search for information such as to which edge server 500 the application is released to, and when the contract renewal date of the application is in the edge server 500.

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

[0106] [Structure of Distribution Server 200]

[0107] like Figure 5A As shown, the distribution server 200 includes a control unit 210 , a storage unit 220 , and a communication unit 230 .

[0108] The control unit 210 may be a CPU, and controls the publishing server 200 in a centralized manner by executing various programs stored in the storage unit 220 .

[0109] The communication unit 230 is a communication control device that transmits and receives data to and from external devices (for example, the user terminal 400 and the edge server 500 ) via a network.

[0110] The control unit 210 includes a matching information receiving unit 211 and an application distribution processing unit 212 as functional units based on the program stored in the storage unit 220. The storage unit 220 includes a distribution information storage unit 221 in addition to the program executed by the control unit 210.

[0111] Before describing each functional unit of the control unit 210 , the storage unit 220 will be described.

[0112] <Published information storage unit 221>

[0113] The release information storage unit 221 is a storage unit provided for releasing applications that are purchased by users and permitted by application developers. Figure 5B As shown, the publishing information storage unit 221 can correspond to the serial number (license key) of the published application, including the application ID of the published application, the license, the user ID of the user who made the purchase commission, the ID of the edge server 500 of the publishing destination, and the address on the communication network such as the IP address, etc.

[0114] Next, each functional unit of the control unit 210 of the distribution server 200 will be described.

[0115] <Matching Information Receiving Unit 211>

[0116] The matching information receiving unit 211 receives the matching information transmitted from the sales permission processing unit 113 of the management server 100. Then, the matching information receiving unit 211 stores the received matching information in the release information storage unit 221.

[0117] <Application Distribution Processing Unit 212>

[0118] When receiving a serial number (license key) and an application distribution request from a user who has purchased the application via the user terminal 400 , the application distribution processing unit 212 refers to the distribution information storage unit 221 based on the serial number.

[0119] Furthermore, the application publishing processing unit 212 determines the record of the publishing information storage unit 221 with the same serial number, confirms the application ID to be published and the edge server 500 of the publishing destination, and publishes the application from the application DB 250 to the edge server 500 of the publishing destination. More specifically, the application publishing processing unit 212 first determines the application to be published, the license, and the edge server 500 that publishes the application based on the serial number included in the publishing request of the application from the user received from the user terminal 400. Furthermore, the application publishing processing unit 212 publishes the license and the application obtained from the application DB 250 based on the application ID associated with the serial number to the determined edge server 500. Here, the so-called license is, for example, the use permission information related to the edge device 600 that becomes the client (i.e., the connection and / or input and output object) of the application. The license can also be published to the edge server 500 by being included in the application. In addition, the license can also be published to the edge server 500 separately from the application.

[0120] Then, the user can download the purchased application to the determined edge server 500 .

[0121] In this way, the application publishing processing unit 212 determines the application and the edge server 500 according to the serial number included in the publishing request, so only a specific user who knows the serial number can make a publishing request. In other words, even if a third party makes a publishing request, the application will not be published because the serial number is unknown. In addition, the serial number determines the edge server 500 that becomes the publishing destination of the application, so even if the third party knows the serial number, it cannot publish the application to a server other than the determined edge server 500.

[0122] In addition, the application publishing processing unit 212 associates the published application information with the edge server 500 of the publishing destination, generates publishing management information related to the published application, and transmits it to the management server 100 (publishing management processing unit 114). Here, the publishing management information includes the edge server ID of the edge server 500 of the publishing destination and the application ID of the published application as a search keyword (compound keyword), for example, the product name, order number, serial number, license, purchase date, publishing date, etc. of the published application.

[0123] In addition, the control unit 210 may provide, for example, a manager of an operation management company with a function of searching and matching the posted data stored in the posted information storage unit 221 via an operation management terminal (not shown).

[0124] [Apply DB250]

[0125] The application DB 250 is a database for storing application programs created by developers. As described above, for example, application programs transmitted from the developer terminal 300 and reviewed are registered in the application DB 250 .

[0126] Figure 6 2 is a diagram showing an example of application DB 250. Figure 6 As shown, the main body of the application is stored in correspondence with the application ID in the application DB 250. In addition, in the application DB 250, appropriate items such as the product name of the application, target model information, price information, version number of the application, application developer ID, etc. can also be registered.

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

[0128] [Browsing information provision processing]

[0129] First, according to Figure 7 The process related to the browsing of the application will be described with reference to the flowchart showing the browsing information providing process of the management server 100 shown.

[0130] In order to browse the application information, each user operates the user terminal 400 and registers with the sales management server system 10. Here, the registration is performed using a known method, for example, using the user's personal information or a password management file including an ID and password to perform user authentication and confirm that the user is a legitimate user.

[0131] Then, the user selects to browse the application from a menu screen (not shown) displayed on the user terminal 400. Then, in step S11, the control unit 110 (browsing information providing unit 111) receives the browsing request sent by the user terminal 400.

[0132] In S12 , the control unit 110 (browsing information providing unit 111 ) transmits a screen listing applications that can be browsed by the user on the user terminal 400 to the user terminal 400 .

[0133] In S13 , the control unit 110 (browsing information providing unit 111 ) receives, from the user terminal 400 , selection of an application program for which details are to be checked.

[0134] In S14, control unit 110 (browsing information providing unit 111) provides a browsing screen 160 of application information related to the received one application by referring to application management information storage unit 121. Here, browsing screen 160 may display price information or a purchase button related to one application.

[0135] In S15, the control unit 110 determines whether a purchase request for an application is received from the user terminal 400. For example, when the user selects a purchase button on the browsing screen, the user terminal 400 sends a purchase request for an application. When a purchase request is received (S15: Yes), the control unit 110 transfers the process to S16. On the other hand, when no purchase request is received (S15: No), the control unit 110 transfers the process to S17.

[0136] In S16, the control unit 110 (purchase request processing unit 112) generates order management information based on the received purchase request, temporarily stores it in the storage unit 120, and then performs the purchase request processing to be described next. Thereafter, the control unit 110 ends this processing.

[0137] In S17, the control unit 110 determines whether to terminate the reading information provision process. For example, when receiving an instruction to terminate the reading from the user terminal 400, the control unit 110 determines that the reading information provision process is terminated. In addition, for example, when the user terminal 400 selects to return to the overview screen, the control unit 110 determines that the reading information provision process is not terminated. When the reading information provision process is terminated (S17: Yes), the control unit 110 terminates the present process. On the other hand, when the reading information provision process is not terminated (S17: No), the control unit 110 transfers the process to S12.

[0138] [Purchase request processing]

[0139] Next, according to Figure 8 The process related to the purchase request of the application will be described with reference to the flowchart showing the purchase request process of the management server 100 shown in FIG.

[0140] In S21 , the control unit 110 (purchase request processing unit 112 ) of the management server 100 refers to the application management information storage unit 121 and the application developer information storage unit 124 based on the purchase request from the user to identify the application developer of the application that has made the purchase request.

[0141] In S22, the control unit 110 (purchase request processing unit 112) sends the purchase request information to the developer terminal 300 of the determined application developer. The purchase request information includes the name of the user and the user's address including nationality in addition to the name of the application. The control unit 110 may also send the purchase request information to the developer terminal 300 via an email or the like.

[0142] Through this process, the purchase request information is transmitted to the developer terminal 300 , and therefore the application developer refers to the purchase request information to determine whether to sell the application program to the user.

[0143] Furthermore, the control unit 110 (purchase request processing unit 112) may send a message to the user terminal 400 to wait for confirmation from the application developer while performing the purchase request processing.

[0144] In S23 , the control unit 110 (purchase request processing unit 112 ) receives permission information regarding the purchase request from the developer terminal 300 .

[0145] In S24, the control unit 110 (purchase request processing unit 112) determines whether the availability information related to the purchase request received from the developer terminal 300 indicates that the purchase is possible. If the purchase is possible (S24: Yes), the control unit 110 transfers the process to S25. On the other hand, if the purchase is not possible (S24: No), the control unit 110 transfers the process to S27.

[0146] In S25 , the control unit 110 (purchase request processing unit 112 ) updates the order management information stored in the storage unit 120 .

[0147] In S26, the control unit 110 (purchase request processing unit 112) performs a sales permission process described later and then terminates the present process.

[0148] On the other hand, in S27, the control unit 110 (purchase request processing unit 112) sends a message to the user terminal 400 that the purchase is not allowed, and the present process is terminated. The control unit 110 may send an email ("rejection email") or the like to the contact information (e.g., email address) of the user who has made the purchase request, notifying that the purchase of the application has been rejected and the purchase procedure has been terminated, etc. The management server 100 (purchase request processing unit 112) deletes the order management information from the storage unit 120, and the process is terminated.

[0149] [Sales permission processing]

[0150] Next, Fig. 9 The following will describe a flowchart showing the sales permission process of the sales management server system 10 shown in FIG.

[0151] In S31, the control unit 110 (sales permission processing unit 113) of the management server 100 generates a serial number of the application program that is permitted to be purchased.

[0152] In S32 , the control unit 110 (sales permission processing unit 113 ) transmits purchase permission information including the generated serial number to the user terminal 400 .

[0153] In S33, the control unit 110 (sales permission processing unit 113) sends matching information including the generated serial number to the distribution server 200. The matching information includes the application ID and the edge server ID of the distribution destination edge server 500 in addition to the serial number. Then, the control unit 110 ends this process.

[0154] In addition, the control unit 110 may perform the process of S32 and the process of S33 simultaneously, or may perform the process of S32 after the process of S33.

[0155] In S34 , the control unit 210 (matching information receiving unit 211 ) of the distribution server 200 receives the matching information transmitted from the management server 100 .

[0156] In S35, the control unit 210 (matching information receiving unit 211) stores the received matching information in the posted information storage unit 221. Thereafter, the control unit 210 ends the present process.

[0157] [Application release processing]

[0158] Next, according to Fig.10 The processing related to the distribution of the application will be described with reference to the flowchart showing the application distribution processing of the distribution server 200 shown in FIG.

[0159] For example, a request for publishing an application is made by selecting, for example, publishing of an application from a menu screen (not shown) displayed on the user terminal 400. The serial number of the application to be published to the edge server 500 is input into the publishing screen (not shown) transferred by selecting publishing of the application, and the user terminal 400 transmits publishing request information to the publishing server 200 by selecting a send button. The publishing request information includes at least the serial number.

[0160] In S51 , the control unit 210 (application distribution processing unit 212 ) of the distribution server 200 receives distribution request information of the application program from the user terminal 400 .

[0161] In S52 , the control unit 210 (application distribution processing unit 212 ) refers to the distribution information storage unit 221 based on the serial number included in the distribution request information to identify the application and the edge server 500 that distributes the application.

[0162] In S53 , the control unit 210 (application distribution processing unit 212 ) obtains the main body of the identified application from the application DB 250 , and distributes the obtained application to the identified edge server 500 .

[0163] In S54 , the control unit 210 (application distribution processing unit 212 ) transmits a distribution completion message to the user terminal 400 that has transmitted the distribution request information, corresponding to the completion of distribution of the application program to the edge server 500 .

[0164] In S55, the control unit 210 (application distribution processing unit 212) generates distribution management information and transmits it to the management server 100. Thereafter, the control unit 210 ends the present process.

[0165] Furthermore, the control unit 110 of the management server 100 which has received the publishing management information from the publishing server 200 updates the publishing management storage unit 123 based on the received publishing management information.

[0166] Through the above, in the application sales management system 1000, the user can purchase the application run by the edge server 500 from the sales management server system 10 and download it.

[0167] At this time, the developer of the application that the user has entrusted to purchase can be sent information related to the user who has entrusted to purchase, so that the application developer can determine whether to allow the sale of the application. Therefore, the application developer can bear the responsibility related to the sale of the application to the user.

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

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

[0170] 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.

[0171] The above-mentioned embodiment is an explanation of the case where the entire structure of the application sales management system is located in a certain country, but the present invention is not limited to this. For example, the present invention can also be applied to the case where the application sales management system is used in multiple countries.

[0172] Fig.11 This is a schematic diagram showing the basic structure of an application sales management system 1000-2 according to a modified embodiment.

[0173] The application sales management system 1000-2 has a sales management server system 10-2a in country A, and a sales management server system 10-2m in country M which is different from country A. As shown in the application sales management system 1000-2, the management server 100-2a is, for example, set in the country (region) of the operating management enterprise, and the publishing server 200-2 (200-2a, 200-2m, etc.) and the application DB250-2 (250-2a, 250-2m, etc.) are also set in the country (country M) having the edge server 500. At this time, the same application can be stored in the application DB250-2 (250-2a, 250-2m, etc.) in a manner common to all countries. In addition, the application DB250-2a can be used as the main database to store all applications, and the application DB250-2 (250-2m, etc.) of each country can store applications that are only allowed to be sold in that country.

[0174] In addition, although the developer terminal 300 is installed in country A in this example, it may be installed in the nationality of the application developer, and a plurality of developer terminals 300 may be located in a plurality of countries.

[0175] When the application sales management system 1000-2 has such a structure, the user terminal 400 of the user in country M sends a purchase commission to the management server 100-2a. When the application developer determines that the purchase is possible, the management server 100-2a determines country M based on the purchase request information and sends purchase permission information including access information to the publishing server 200-2m to the user terminal 400.

[0176] In this way, the user terminal 400 sends a publishing request message to the publishing server 200-2m, and the publishing server 200-2m sends the application stored in the application DB 250-2m to the edge server 500. Therefore, the operation and management enterprise can publish the application to the desired edge server 500 without any special regulations only when the application is stored in the application DB 250-2m and the relevant management regulations are applied.

[0177] In the above embodiment, an example using a serial number as the release permission information or matching information is described, but the invention is not limited thereto. The release permission information or matching information is information that cannot be recalled by a third party, and therefore, it is sufficient that it is information that permits the release of an application.

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

[0179] As described above, according to this embodiment, for example, the following effects are obtained.

[0180] Technical solution (1): The sales management server system 10 manages the online store sales of applications run by edge servers 500 that are communicatively connected to one or more edge devices 600, and comprises: an application DB 250 that stores applications created by developers and registered for online store sales; a management server 100 that manages online store sales that can purchase applications that are registered for online store sales and stored in the application DB 250; and a publishing server 200 that publishes applications to the edge servers 500. The sales management server system 10 is communicatively connected to a user terminal 400 owned by a user using the edge device 600 and the edge server 500, and a developer terminal 300 owned by a developer via a network N1. Next, the management server 100 has: a purchase request processing unit 112, which sends the purchase request information of the application that the user has entrusted to purchase via the user terminal 400 to the developer terminal 300 of the application; when the permission information related to the purchase entrustment received from the developer terminal 300 indicates that the purchase is allowed, the purchase permission information including the publishing permission information corresponding to the application is sent to the user terminal 400; when the permission information related to the purchase entrustment indicates that the purchase is not allowed, the user terminal 400 is notified that the purchase is not allowed; the publishing server 200 has: an application publishing processing unit 212, which publishes the application corresponding to the publishing permission information to the edge server 500 according to the situation that the publishing request information including the publishing permission information sent by the user terminal 400 is received.

[0181] Thus, it is possible to configure the application developer who is responsible for the application's functionality and reliability to determine whether to entrust the purchase of the application. Therefore, the functionality and reliability of the application can be handled by a suitable person, rather than by the company that manages the system.

[0182] Furthermore, when the availability information related to the purchase request of the application indicates that the application can be purchased, the publishing permission information is provided to the user terminal 400, and the application corresponding to the publishing permission information is published to the edge server 500. Therefore, the application can be published to the edge server 500 only for the user who has made the purchase request.

[0183] Technical Solution (2): In the sales management server system 10 described in Technical Solution (1), the management server 100 has: a sales permission processing unit 113, which, when the permission information related to the purchase commission received from the developer terminal 300 indicates that the purchase is allowed, issues release permission information and matching information corresponding to the release permission information, and sends the issued matching information to the publishing server 200. When the release permission information contained in the publishing request information matches the matching information, the application publishing processing unit 212 of the publishing server 200 publishes the application corresponding to the release permission information to the edge server 500.

[0184] Thus, a structure that allows the application to be published can be constructed only when the matching information corresponding to the publishing permission information directly sent by the management server 100 to the publishing server 200 matches the publishing permission information included in the publishing request information sent by the user terminal 400. Therefore, the application can be published only when it is a publishing server 200 permitted by the management server 100.

[0185] Technical Solution (3): In the sales management server system 10 described in Technical Solution (2), the management server 100 can simultaneously send matching information based on the sales permission processing unit 113 and send purchase permission information based on the purchase request processing unit 112.

[0186] Thus, when the publishing request information is sent from the user terminal 400, the publishing server 200 can be in a state of receiving the matching information and storing it as a matching object.

[0187] Technical Solution (4): In the sales management server system 10 described in Technical Solution (2) or Technical Solution (3), the release permission information and the matching information may include the same information.

[0188] This makes matching easy because matching can be performed based on the same information.

[0189] Technical Solution (5): In the sales management server system 10 described in any one of Technical Solutions (1) to (4), the purchase request information may include a user's name and an address including at least an area name, and a name of an application.

[0190] Thus, the purchase request information can provide the application developer with materials for determining whether to entrust the purchase of the application program.

[0191] Technical Solution (6): In an application sales management system 1000-2 having a sales management server system 10-2a as described in any one of Technical Solutions (1) to (5), other sales management server systems 10-2m different from the sales management server system 10-2a are set in one or more areas where the developer allows sales. The other sales management server system 10-2m has an application DB 250-2m and a publishing server 200-2m. When the permission information related to the purchase commission received from the developer terminal 300 indicates that the purchase is allowed, the purchase request processing unit 112 of the management server 100 determines a publishing server 200-2m of the sales management server system 10-2m based on the purchase request information, and sends purchase permission information including access information for the determined publishing server 200-2m to the user terminal 400.

[0192] Thus, the user terminal 400 sends a publishing request message to the publishing server 200-2m in the user's country, and sends the application stored in the application DB 250-2m to the edge server 500. Therefore, the operating management company does not need to input the application when publishing to the desired edge server 500.

[0193] Technical Solution (7): A sales management server system 10 has a management server 100, the sales management server system 10 manages online store sales of applications run by an edge server 500 that is communicatively connected to one or more edge devices 600, the management server 100 manages online store sales of applications that can be purchased and are stored in an application DB 250 that stores applications created by developers and has been logged in for online store sales, and the management server 100 communicates with a user interface of a user who uses the edge device 600 and the edge server 500 via a network N1. The management server 100 is communicatively connected to a user terminal 400 and a developer terminal 300 owned by a developer, and the management server 100 comprises: a purchase request processing unit 112, which sends purchase request information of an application that is entrusted by a user to purchase via the user terminal 400 to the developer terminal 300 of the application; when the permission information related to the purchase entrustment received from the developer terminal 300 indicates that the purchase is allowed, purchase permission information including release permission information associated with the application is sent to the user terminal 400; when the permission information related to the purchase entrustment indicates that the purchase is not allowed, the user terminal 400 is notified that the purchase is not allowed.

[0194] Thus, the effects of the management server 100 of the technical solution (1) can be obtained.

[0195] Technical solution (8): A sales management server system 10 has a publishing server 200, the sales management server system 10 manages the online store sales of applications run by an edge server 500 that is communicatively connected to one or more edge devices 600, the publishing server 200 publishes applications created by developers and stored in an application DB 250 to the edge server 500, the publishing server 200 is communicatively connected to a user terminal 400 owned by a user using the edge device 600 and the edge server 500, and a developer terminal 300 owned by the developer via a network N1, the publishing server 200 has: an application publishing processing unit 212, which publishes an application corresponding to publishing permission information to the edge server 500 based on the situation of receiving a publishing request information from the user terminal 400, the publishing request information including the publishing permission information associated with the application included in the purchase permission information sent by the management server 100 to the user terminal 400, the management server 100 manages the online store sales of applications that can be purchased and registered for online store sales and stored in the application DB 250.

[0196] Thus, the effect of the publishing server 200 of technical solution (1) can be obtained.

Claims

1. An application sales management server system that manages online store sales of applications run by an edge server that is communicatively connected to one or more edge devices, characterized in that: The application sales management server system has: An application database storing the applications produced by developers and registered for sale in the online store; A management control device that manages online store sales that enable purchase of the application programs stored in the application database and registered for online store sales; as well as a publishing control device, which publishes the application to the edge server, The application sales management server system is connected to a user terminal of a user who uses the edge device and the edge server and a developer terminal of the developer via a communication network so as to be communicable. The management control device has: a purchase request sending unit configured to send purchase request information of the application program entrusted by the user via the user terminal to the developer terminal of the application program; as well as a result sending unit which, when the application developer having the function or trustworthiness of the application received from the developer terminal determines that the purchase is allowed according to the purchase request information, sends purchase permission information including release permission information associated with the application to the user terminal, and when the purchase is not allowed according to the purchase permission information, notifies the user terminal that the purchase is not allowed, The release control device comprises: The application publishing unit publishes the application corresponding to the publishing permission information to the edge server in response to receiving publishing request information including the publishing permission information sent by the user terminal.

2. The application sales management server system according to claim 1, characterized in that: The management control device has: an issuing unit that, when the availability information related to the purchase request received from the developer terminal indicates that the purchase is available, issues the issuance permission information and matching information corresponding to the issuance permission information; as well as a matching information sending unit that sends the matching information issued by the issuing unit to the issuance control device, When the distribution permission information included in the distribution request information matches the matching information, the application distribution unit of the distribution control device distributes the application corresponding to the distribution permission information to the edge server.

3. The application sales management server system according to claim 2, characterized in that: The management control device simultaneously performs transmission of the matching information by the matching information transmission unit and transmission of the purchase permission information by the result transmission unit.

4. The application sales management server system according to claim 2 or 3, characterized in that: The release permission information and the matching information contain the same information.

5. The application sales management server system according to claim 2 or 3, characterized in that: The purchase request information includes the name of the user and an address including at least an area name, and the name of the application.

6. An application sales management system, comprising the application sales management server system according to any one of claims 1 to 5, characterized in that: Another application sales management server system different from the application sales management server system is set in one or more areas where the developer is allowed to sell, and the other application sales management server system has the application database and the distribution control device, When the permission information related to the purchase commission received from the developer terminal indicates that the purchase is allowed, the result sending unit of the management control device determines a publishing control device of the application sales management server system based on the purchase request information, and sends the purchase permission information including access information for the determined publishing control device to the user terminal.

7. A management control device of an application sales management server system, wherein the application sales management server system manages online store sales of applications run by an edge server that is communicatively connected to one or more edge devices, and the management control device manages online store sales of applications that can be purchased and are stored in an application database storing the applications created by developers and have been logged in for online store sales, characterized in that: The management control device is connected to a user terminal of a user who uses the edge device and the edge server and a developer terminal of the developer via a communication network so as to be communicable therewith. The management control device comprises: a purchase request sending unit which sends purchase request information of the application program entrusted by the user via the user terminal to the developer terminal of the application program; as well as A result sending unit, which sends purchase permission information including release permission information associated with the application to the user terminal when the application developer having the function or trustworthiness responsibility for the application received from the developer terminal judges based on the purchase request information that the purchase is allowed according to the permission information related to the purchase entrustment, and notifies the user terminal that the purchase is not allowed when the permission information related to the purchase entrustment is that the purchase is not allowed.

Images