Sales assistant server, sales assistant system, and sales assistant program

The sales support server and system address the issue of unpaid creators by tracking and compensating for modified 3D model data usage, ensuring fair compensation and protecting the interests of both creators and users in virtual marketplaces.

WO2024232026A1PCT designated stage expired Publication Date: 2024-11-14POLYGON TAILOR INC
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
PCT/JP2023/017502
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-05-10
Publication Date
2024-11-14

AI Technical Summary

Technical Problem

There is no mechanism to return profits to creators of modified 3D model data used in virtual spaces, such as avatars and decorations, as users who modify these items are not allowed to sell their changes, preventing them from benefiting from their creative work.

Method used

A sales support server and system that tracks and records the association between modified 3D model data products and their parent products, allowing for accurate pricing and compensation to both the creator and the user who modifies the product, ensuring that the creator of the parent product receives credit and compensation when their work is used in the creation of new products.

Benefits of technology

This system enables fair compensation for creators by ensuring that the value of the parent product is reflected in the sales of the modified product, protecting the interests of both the creator and the user who modifies the product, thereby incentivizing creativity and innovation within virtual marketplaces.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure JP2023017502_14112024_PF_FP_ABST
    Figure JP2023017502_14112024_PF_FP_ABST
Patent Text Reader

Abstract

This sales assistant server, in which electronic data of an object to be used in a virtual space is treated as a commodity, involves: associating, with one another, an exhibitor user who desires to exhibit a commodity, an exhibition commodity, and a unit price to be reflected in sales of the exhibitor user when the exhibition commodity has been sold, and storing said association in a storage part; causing the exhibitor user to declare a master commodity used for producing the exhibition commodity; storing information for specifying the master commodity in a storage part in association with the exhibition commodity; determining, when a purchase user for one exhibition commodity (hereinafter, referred to as "specific commodity") having been exhibited has appeared, whether or not the master commodity is associated with the specific commodity; when said association is determined, adding up unit prices of both the specific commodity and the master commodity as a charging amount to the purchase user; when the purchase user has settled the charging amount which is obtained by adding up the unit prices of both the specific commodity and the master commodity, adding up the unit price of the specific commodity as the sales of the exhibitor user of the specific commodity; and adding up the unit price of the master commodity as the sales of the exhibitor user of the master commodity.
Need to check novelty before this filing date? Find Prior Art

Description

Sales support server, sales support system, and sales support program

[0001] The present invention relates to a sales support server that supports user-to-user trading of electronic data (for example, 3D model data) used in a virtual space, a sales support system including the same, and a sales support program.

[0002] An e-marketplace platform (see Patent Document 2, etc.) that sells 3D model data such as avatars that can be introduced into the Metaverse, a type of virtual space (see Patent Document 1, etc.) is known. Users of this platform can upload 3D model data of avatars created on their own devices to the platform and offer them for sale to other users. If other users like a listed avatar, they can purchase the avatar through the platform and be permitted to download the 3D model data from the platform. Users who purchase an avatar (purchasing users) can introduce the 3D model data downloaded to their devices into the Metaverse, allowing them to participate in a community using the avatar as their own avatar avatar.

[0003] On the other hand, the platform operator transfers the amount of currency, minus a specified fee, from the sales of the avatar to the user who put up the avatar (the "seller"). This ensures that the seller receives payment for the service of creating the avatar. The more users who purchase the avatar (the "purchaser"), the more compensation the seller can receive.

[0004] Metaverse "VRChat", VRChat Inc., [Retrieved April 12, 2023], Internet <URL: https: / / hello.vrchat.com / > E-marketplace platform "BOOTH", Pixiv Inc., [Retrieved April 12, 2023], Internet <URL: https: / / booth.pm / ja>

[0005] In recent years, many users have begun to create modified avatars by editing the 3D model data of purchased avatars on their own devices and using them in the Metaverse. For example, some users modify the body shape of pre-made avatars to suit their own preferences by modeling them on their own devices, or by adding pre-made hairstyles and clothing to pre-made avatars to create their own personalized avatars. Although these modified avatars reflect the ideas and tastes of the users who modeled or dressed them, they are not permitted to be sold in principle, and therefore the users who made the modifications were unable to earn profits. This is because there is no mechanism for returning profits to the creators of the products (parent products) used to create the modified avatars.

[0006] The present invention has been made in consideration of the above problems, and aims to provide a sales support server that supports user-to-user trading of electronic data used in a virtual space as a product, and that can protect the interests of both the user who exhibits the product and the user who exhibits the parent product used in the production of that product, as well as a sales support server that includes such a server, a sales support system that includes such a server, and a sales support program.

[0007] In order to solve the above problems, one sales support server according to the present invention is a sales support server that supports user-to-user trading of electronic data used in a virtual space as a product, and includes: a product management unit that executes a process of storing in a storage unit, in association with a user who wishes to put up an item for sale (hereinafter referred to as an "exhibiting user"), an item that the exhibiting user puts up for sale (hereinafter referred to as an "exhibited item"), and a price that should be reflected in the sales of the exhibiting user when the exhibiting item is sold (hereinafter referred to as a "single item price"); a tree management unit that executes a process of having the exhibiting user declare an item used in the production of the exhibiting item (hereinafter referred to as a "parent item"), and storing in the storage unit information for identifying the parent item in association with the exhibiting item; and a user who wishes to purchase any of the exhibiting items that have been put up for sale (hereinafter referred to as a "specific item"). When a purchasing user (hereinafter referred to as a "purchasing user") appears, the billing unit determines whether or not a parent product is associated with the specific product based on the information stored in the storage unit, and if so, executes a process of including the unit prices of both the specific product and the parent product in the billing amount for the purchasing user; and when the purchasing user pays the billing amount including the unit prices of both the specific product and the parent product, executes a process of including the unit price of the specific product in the sales of the exhibiting user of the specific product and the unit price of the parent product in the sales of the exhibiting user of the parent product.

[0008] In order to solve the above problem, in one sales support server of the present invention, the memory unit pre-stores purchase history information indicating the purchase histories of multiple users, and the billing unit may not include the unit price of the parent product in the billing amount even if a parent product is associated with the specific product, if it determines based on the purchase history information that the purchasing user has already purchased the parent product.

[0009] In order to solve the above problem, in one sales support server of the present invention, when the billing unit determines that a higher-level parent product is associated with the parent product based on the information stored in the memory unit, it also includes the unit price of the higher-level parent product in the billing amount.

[0010] In order to solve the above problem, in one sales support server of the present invention, the tree management unit may require the listing user to declare the parent product even if only a portion of the parent product was used in the production of the listed product.

[0011] In order to solve the above problem, in one sales support server of the present invention, the virtual space may be a metaverse, and the electronic data may include 3D model data of an avatar, which is a type of object that can be used in the metaverse, and 3D model data of items that decorate the avatar.

[0012] In order to solve the above problem, a sales support system according to the present invention is characterized by comprising a sales support server according to the present invention and a data server that stores electronic data of multiple products listed by multiple listing users.

[0013] In order to solve the above-mentioned problems, one computer-readable sales support program according to the present invention is a computer-readable sales support program that causes a computer to function as a sales support server that supports user-to-user trading of electronic data used in a virtual space as a commodity, and includes a product management unit that executes a process of storing in a storage unit, in association with a user who wishes to exhibit an item (hereinafter referred to as an "exhibiting user"), an item that the exhibiting user exhibits (hereinafter referred to as an "exhibited item"), and a price that should be reflected in the sales of the exhibiting user when the exhibited item is sold (hereinafter referred to as a "unit price"); and a process of having the exhibiting user declare an item (hereinafter referred to as a "parent item") used in the production of the exhibited item, and storing information for identifying the parent item in the exhibited item. and storing the information stored in the storage unit in association with the parent product when a user (hereinafter referred to as a "purchasing user") appears who wishes to purchase any of the listed products (hereinafter referred to as a "specific product"), the processing is to determine whether or not a parent product is associated with the specific product based on the information stored in the storage unit, and if so, to include the unit prices of both the specific product and the parent product in the amount charged to the purchasing user; and when the purchasing user pays the amount charged in which the unit prices of both the specific product and the parent product are included, to include the unit price of the specific product in the sales of the listing user of the specific product, and to include the unit price of the parent product in the sales of the listing user of the parent product.

[0014] The sales support server, the sales support system, or the sales support program of the present invention supports user-to-user trading of electronic data used in a virtual space as a commodity, and manages in a memory unit the unit price that should be reflected in one's own sales when an item is sold, and the parent product used to create the item, each associated with the selling user.

[0015] Based on the information stored in the memory unit, the sales support server of the present invention, the sales support system of the present invention, or the sales support program of the present invention can identify the parent product of the specific product, the unit price of the parent product, and the user who has listed the parent product when a purchasing user appears who wishes to purchase the specific product, and can therefore charge the purchasing user the unit price of both the specific product and the parent product, and can include the unit price of the specific product in the sales of the user who has listed the specific product, and can include the sales of the parent product in the sales of the user who has listed the parent product.

[0016] Therefore, the sales support server of the present invention, the sales support system of the present invention, or the sales support program of the present invention has the effect of protecting the interests of both the user who exhibits the product and the user who exhibits the parent product used in the production of that product.

[0017] FIG. 1 is a schematic block diagram illustrating the general configuration of a sales support system according to an embodiment. FIG. 2 is a schematic block diagram illustrating the configuration of a sales support server. FIG. 3 is an explanatory diagram illustrating products 1 to 4. FIG. 4 is an explanatory diagram illustrating the configuration of a user table. FIG. 5 is an explanatory diagram illustrating the configuration of a product table. FIG. 6 is an explanatory diagram illustrating the configuration of a modification tree table. FIG. 7 is an explanatory diagram illustrating the configuration of a purchase history table. FIG. 8 is an explanatory diagram illustrating the configuration of a payment table. FIG. 9 is a flowchart illustrating the flow of procedures when listing an item. FIG. 10 is a flowchart illustrating the flow of procedures when selling an item.

[0018] Hereinafter, embodiments of a sales support server according to the present invention, a sales support system according to the present invention, or a computer-readable sales support program according to the present invention will be described with reference to the drawings.

[0019] 1. Sales Support System First, the schematic configuration of the sales support system of this embodiment will be described. This sales support system provides multiple users with an e-marketplace platform in which objects usable in the metaverse are used as products. FIG. 1 is a schematic block diagram illustrating the schematic configuration of a sales support system according to a preferred embodiment. As shown in FIG. 1, the sales support system 100 includes a sales support server 10, a data server 20, a payment server 30, and the like, and these sales support server 10, data server 20, and payment server 30 are connected to multiple terminals 50-1, 50-2, ... via a network 40 such as the Internet.

[0020] The multiple terminals 50-1, 50-2, etc. are terminal devices used individually by multiple users 1, 2, 3, 4, etc. who are pre-registered in the sales support server 10 (note that "user 1," "user 2," "user 3," "user 4," etc. are user IDs for distinguishing between users). Each of the terminals 50-1, 50-2, etc. is configured as a desktop PC, laptop PC, tablet PC, smartphone, home game console, etc., and each of the terminals 50-1, 50-2, etc. is pre-installed with, for example, an application program (including a web browser, a game program, etc.) provided by the sales support server 10 or pre-installed. This application program uses a display, input device, etc. mounted on the terminal devices 50-1, 50-2, etc. to cause the terminals 50-1, 50-2, etc. to function as a user interface required for user registration, listing products for sale, purchasing products, etc.

[0021] The sales support server 10 is a server device that supports user-to-user trading of 3D model data of objects used in virtual space. The products traded include 3D model data of avatars, which are character objects used as users' avatars in the metaverse, and 3D model data of items (clothes, hairstyles, etc.), which are objects that decorate the avatars. Details of the sales support server 10 will be described later.

[0022] Under instructions from the sales support server 10, the data server 20 stores a file of 3D model data of an exhibited item uploaded from a terminal 50-i of an exhibiting user i who is one of the multiple users 1, 2, ..., and also executes a process of downloading the file of 3D model data of a purchased item to a terminal 50-j of a purchasing user j who is one of the multiple users 1, 2, .... The operator of the data server 20 may be the same person as the operator of the sales support server 10, or may be a different person (such as a file storage company).

[0023] The payment server 30 is a server device that executes the processes required when a purchasing user j pays (settles) the purchase price of a product via the terminal 50-j to the operator of the sales support server 10. The operator of the payment server 30 may be the same person as the operator of the sales support server 10, or may be a different person (such as a payment agent).

[0024] 2. Sales Support Server Next, the general configuration of the sales support server of this embodiment will be described. Figure 2 is a general block diagram illustrating the configuration of the sales support server. As shown in Figure 2, the sales support server 10 includes a communication unit 11, a control unit 12, and a storage unit 13.

[0025] The communication unit 11 is a communication interface that enables the sales support server 10 to send and receive data via the network 40 between the data server 20, the settlement server 30, and the terminals 50-1, 50-2, . . .

[0026] The memory unit 13 is a storage device that stores programs and data necessary for processing by the sales support server 10, and is a storage device that is located inside or outside the sales support server 10. The memory unit 13 stores a sales support program 131, a user table 132, a product table 133, a modification tree table 134, a purchase history table 135, a payment table 136, and the like.

[0027] The control unit 12 is a processor (CPU) that executes various processes by running the sales support program 131, and functions as a product management unit 121, a tree management unit 122, a billing unit 123, and a distribution unit 124 as appropriate.

[0028] The product management unit 121 executes a process in which the seller user i inputs the single item price that should be reflected in his or her sales when the exhibited product is sold, and stores the single item price information in the product table 133 (Figure 5) of the memory unit 13 in association with the exhibited product and the exhibited user i.

[0029] The tree management unit 122 executes a process of having the seller user i declare the parent product used in the production of the listed product, and storing information for identifying the parent product (the modified tree described below) in association with the listed product in the modified tree table 134 ( FIG. 6 ) of the storage unit 13. The tree management unit 122 requires the seller user i to declare the parent product even if only a portion of the parent product was used in the production of the listed product. For example, the tree management unit 122 displays a list of the listed products that have been listed to date on the display of the seller user's terminal 50-i, and adds a note such as, "If one or more products were used in the production of the product you are about to list, please declare all of them without omission, even if only a portion of those products was used." This prevents seller user i from failing to declare the parent product. This is to protect the interests of the user who listed the parent product.

[0030] When a purchasing user j appears who wishes to purchase one of the listed products (specific products), the billing unit 123 determines whether a parent product is associated with the specific product based on the information in the modified tree table 134 stored in the memory unit 13. If a parent product is associated with the specific product, the billing unit 123 executes a process of adding the unit prices of both the specific product and the parent product to the billing amount for the purchasing user j based on the information in the product table 133 stored in the memory unit 13. Note that if the billing unit 123 determines based on the information stored in the modified tree table 134 that a higher-level parent product is associated with the parent product, the billing unit 123 further adds (adds) the unit price of the higher-level parent product to the billing amount for the purchasing user j. However, even if a parent product is associated with the specific product, if the billing unit 123 determines based on the purchase history table 135 that the purchasing user j has already purchased at least one parent product, the billing unit 123 does not add (add) the unit price of the parent product to the billing amount for the purchasing user j.

[0031] When the purchasing user j pays the billing amount including the unit prices of both the specific product and at least one parent product, the distribution unit 124 executes a process of recording the unit price of the specific product in the sales of the exhibiting user of the specific product and recording the unit price of the at least one parent product in the sales of the exhibiting user of the parent product. Specifically, the distribution unit 124 refers to the product table 133 for all products related to the charge, adds 1 to the number of sales of the corresponding product, and records (adds) the value obtained by multiplying the number of sales of the corresponding product by the unit price of the corresponding product in the sales of the corresponding user in the user table 133.

[0032] 3. Specific examples of listed products To make the explanation easier to understand, an example will be given in which users 1 to 4 individually list products A to D shown in FIG. 3. FIG. 3 is an explanatory diagram illustrating products 1 to 4. "Product 1," "Product 2," "Product 3," and "Product 4" are the product IDs of each product. Product 1: Avatar A created by user 1 without using any other products. Product 2: Long hair hairstyle B created by user 2 without using any other products. Product 3: Short hair hairstyle C created by user 3 by modeling the 3D model data of long hair hairstyle B. Product 4: Avatar D created by user 4 by attaching short hair hairstyle C to avatar A.

[0033] 4. User Table Next, the user table will be described. FIG. 4 is an explanatory diagram illustrating the configuration of the user table. As shown in FIG. 4, the user table 132 stores information such as user registration details and user sales for each user. Of these, user registration details are user-specific information such as email address, password, and remittance destination. On the other hand, a user's sales are sales of products (listed products) that the user has put up for sale. The breakdown of sales is specifically as follows: Sales of User 1: This is ¥20,000, obtained by multiplying the number of sales of product 1 (= avatar A) "4" by the unit price of product 1 (= avatar A) of ¥5,000 (note that the number of sales and unit price of product 1 are stored in the product table 133, which will be described later). Sales for User 2: ¥8,000 obtained by multiplying the number of sales of product 2 (= hairstyle B) "4" by the unit price of product 2 (= hairstyle B) of ¥2,000 (note that the number of sales and unit price of product 2 are stored in product table 133, which will be described later). Sales for User 3: ¥3,000 obtained by multiplying the number of sales of product 3 (= hairstyle C) "3" by the unit price of product 3 (= hairstyle C) of ¥1,000 (note that the number of sales and unit price of product 3 are stored in product table 133, which will be described later). Sales for User 4: ¥1,000 obtained by multiplying the number of sales of product 4 (= avatar D) "2" by the unit price of product 4 (= avatar D) of ¥500 (note that the number of sales and unit price of product 3 are stored in product table 133, which will be described later). The user table 132 is updated when a user is registered, when the user registration details are changed, when a product is sold (when the price of the product is settled), etc. For simplicity of explanation, the sales information stored in the user table 132 is the sales amount from the previous closing date to the present time, and when a predetermined closing date such as the end of the month arrives and the amount of the sales amount minus the fee is remitted to the remittance destination designated by the user (settlement is completed), the sales amount in the user table 132 is reset to zero.

[0034] 5. Product Table Next, the product table will be described. FIG. 5 is an explanatory diagram illustrating the configuration of the product table. As shown in FIG. 5, the product table 133 stores information for each listed item, such as the listing user, the unit price, the storage location of the 3D model data, and the number of sales. In the example shown in FIG. 5, the unit price of product 1 (= avatar A) is ¥5,000, the unit price of product 2 (= hairstyle B) is ¥2,000, the unit price of product 3 (= hairstyle C) is ¥1,000, and the unit price of product 4 (= avatar D) is ¥500. This product table 133 is updated, for example, when a product is listed or sold. For simplicity's sake, the sales count information stored in the product table 133 represents the number of sales from the previous closing date to the present time. When a predetermined closing date, such as the end of the month, arrives and the above settlement is completed, the sales count in the product table 133 is reset to zero.

[0035] 6. Modification Tree Table Next, the modification tree table will be described. FIG. 6 is an explanatory diagram illustrating the configuration of the modification tree table. As shown in FIG. 6, the modification tree table 134 stores a modification tree for each exhibited item. The modification tree in this modification tree table 134 is updated, for example, when the item is exhibited. Here, the "modification tree" refers to a tree structure that links an exhibited item with one or more parent items that were used to create the exhibited item.

[0036] 6-1. When Avatar A is put up for sale If the put up for sale is Product 1 (= Avatar A), no other products were used in the production of Product 1 (= Avatar A), so the alteration tree for Product 1 (= Avatar A) is not stored in the alteration tree table 134.

[0037] When Hairstyle B is put up for sale, if the put up product is product 2 (= hairstyle B), no other products were used in the production of this product 2 (= hairstyle B), so the alteration tree for product 2 (= hairstyle B) is not stored in the alteration tree table 134.

[0038] 6-3. When Hairstyle C is put up for sale If the product being put up for sale is product 3 (= hairstyle C), product 2 (= hairstyle B) was used to create this product 3 (= hairstyle C), and so the following modification tree is stored in the modification tree table 134 as the modification tree for product 3 (= hairstyle C). Modification tree 1: A modification tree linking product 3 (= hairstyle C) with its parent product, product 2 (= hairstyle B) (note that "modification tree 1" is the modification tree ID).

[0039] 6-4. When Avatar D is put up for sale If the put up for sale is Product 4 (= Avatar D), Product 3 (= Hairstyle C) and Product 1 (= Avatar A) were used to create Product 4 (= Avatar D), so the following two modification trees are stored in the modification tree table 134 as modification trees for Product 4 (= Avatar D).Modification tree 2: A modification tree linking Product 4 (= Avatar D) with Product 3 (= Hairstyle C) (Note: "Modification tree 2" is the modification tree ID).Modification tree 3: A modification tree linking Product 4 (= Avatar D) with Product 1 (= Avatar A) (Note: "Modification tree 3" is the modification tree ID).

[0040] 7. Purchase History Table Next, the purchase history table will be described. FIG. 7 is an explanatory diagram illustrating the configuration of a purchase history table showing purchase history information for multiple users. As shown in FIG. 7, the purchase history table 135 records information for each payment, such as the purchasing user, purchase date and time, and the product for which a charge was made (charged product). This purchase history table 135 makes it possible to check the details of each payment (charged product / purchasing user) as needed, and also to identify the products currently owned by each of users 1, 2, etc. (products previously purchased). This purchase history table 135 is updated when the purchase price of the product is paid. Note that "Payment 1," "Payment 2," ..., "Payment 7" in FIG. 7 are payment IDs.

[0041] 7-1. Regarding Payment 5 For example, "Payment 5" in Figure 7 is the payment when User 5, who had never purchased any products before, purchased Product 1 (= Avatar A) for the first time (note that "Payment 5" is the payment ID). Since Product 1 (= Avatar A), the purchased product related to Payment 5, does not have a parent product (see Figure 5), User 5 should have been charged only the unit price of Product 1 (= Avatar A). Therefore, only Product 1 (= Avatar A) is recorded as the charged product in Payment 5.

[0042] 7-2. Regarding Payment 6 For example, "Payment 6" in Figure 7 is a payment when user 5, who has already purchased product 1 (avatar), purchases product 4 (avatar D). Product 4 (avatar D), the purchased product related to this payment 6, has products 1, 3, and 2 as parent products (see Figure 5), of which product 1 has already been purchased by user 5. Therefore, products 4, 3, and 2, excluding product 1, are recorded in "Payment 6" as billable products.

[0043] 7-3. Regarding Payment 7 For example, "Payment 7" in Figure 7 is a payment when user 6, who had never purchased any products before, purchases product 4 (= avatar D) for the first time. Product 4 (= avatar D), the purchased product related to this payment 7, has products 1, 3, and 2 as parent products (see Figure 5), none of which have been purchased by user 6. Therefore, products 4, 1, 3, and 2 are all recorded in "Payment 7" as billable products.

[0044] 8. Payment Table Next, the payment table will be described. FIG. 8 is an explanatory diagram illustrating the configuration of the payment table. As shown in FIG. 8, the payment table 136 records information for each payment, such as the user who made the payment, the payment amount, and the date and time of payment. This information is mainly information notified from the payment server 30 to the sales support server 10. The payment table 136 is updated, for example, after the user has paid the billing amount.

[0045] 9. Listing Flow The following describes the listing flow, assuming that the user (listing user) wishing to list an item is User 4 and the item being listed (listed item) is Item 4. Figure 9 is a flowchart illustrating the procedure for listing an item. As shown in Figure 9, the control unit 12 of the sales support server 10 executes the following steps S11 to S17 when listing an item. Note that reference numeral S121 in Figure 9 mainly corresponds to the processing of the item management unit 121, and reference numeral S122 in Figure 9 mainly corresponds to the processing of the tree management unit 122.

[0046] Step S11: The control unit 12 determines whether or not an exhibition request has been received from the terminal (terminal 50-4) of the exhibition user (user 4), and if it has been received (step S11 YES), proceeds to the next step S12, and if it has not been received (step S11 NO), waits.

[0047] Step S12: The control unit 12 determines whether or not information on the unit price (¥500) of the exhibiting item (item 4) has been received from the terminal (terminal 50-4) of the exhibiting user (user 4). If the information has been received (step S12 YES), the control unit 12 proceeds to the next step S13; if the information has not been received (step S12 NO), the control unit 12 waits.

[0048] Step S13: The control unit 12 determines whether or not it has received information on all parent products (products 3 and 1) from the terminal (terminal 50-4) of the exhibiting user (user 4), and if it has received information (step S13 YES), it proceeds to the next step S14, and if it has not received information (step S13 NO), it waits.

[0049] Step S14: The control unit 12 determines whether or not a request to upload a file of 3D model data of the exhibited item (item 4) has been received from the terminal (terminal 50-4) of the exhibiting user (user 4). If a request has been received (step S14 YES), the control unit 12 proceeds to the next step S15; if a request has not been received (step S14 NO), the control unit 12 waits.

[0050] Step S15: The control unit 12 uploads the 3D model data file of the auction item (item 4) from the terminal (terminal 50-4) of the auction item user (user 4) to the data server 20. The uploaded 3D model data file is stored in the data server 20.

[0051] Step S16: The control unit 12 associates information such as the exhibiting user (user 4), the single item price (500 yen), and the storage location of the 3D model data of the exhibited item (item 4) with the exhibited item (item 4) and stores the information in the item table 133. As a result, the exhibited item (item 4) is registered in the item table 133.

[0052] Step S17: The control unit 12 stores the information on the parent product (products 3 and 1) received from the terminal (terminal 50-4) of the exhibiting user (user 4) in association with the exhibited product (product 4) in the alteration tree table 134. As a result, the alteration trees (alteration trees 2 and 3) for the exhibited product (product 4) are registered in the alteration tree table 134.

[0053] The order of steps S11 to S17 can be changed as appropriate. For example, the order of steps S12 and S13 can be reversed, or the order of steps S15, S16, and S17 can be changed.

[0054] 10. Flow at the Time of Purchase The flow at the time of purchase will be explained below, assuming that the user wishing to make a purchase (purchasing user) is User 5, and the product (specific product) being purchased is Product 4. Figure 10 is a flowchart explaining the flow of procedures at the time of sale. As shown in Figure 10, the control unit 12 of the sales support server 10 executes the following steps S21 to S35 when purchasing a product. Note that reference numeral S123 in Figure 10 mainly corresponds to the processing of the billing unit 123, and reference numeral S124 in Figure 10 mainly corresponds to the processing of the distribution unit 124.

[0055] Step S21: The control unit 12 determines whether a purchase request for a specific product (product 4) has been received from the terminal (terminal 50-5) of the purchasing user (user 5), and if so (step S21 YES), proceeds to the next step S22; if not (step S21 NO), proceeds to step S34 described below.

[0056] Step S22: The control unit 12 identifies all parent products associated with the specific product (product 4) by referring to the modification tree table 134. If at least one parent product exists (step S22 YES), the control unit 12 proceeds to step S23. If no parent product exists (step S22 NO), the control unit 12 proceeds to step S25. Here, the specific product 4 has parent products (products 3, 1, and 2), so the control unit 12 proceeds to step S23.

[0057] Step S23: The control unit 12 refers to the purchase history table 135 and determines whether the purchasing user (user 5) has previously purchased each of the parent products (products 3, 1, and 2). If there is at least one unpurchased parent product (YES in step S23), the control unit 12 proceeds to step S24. If there is no unpurchased parent product (NO in step S23), the control unit 12 proceeds to step S25. Here, since the purchasing user 5 had not purchased the parent products (products 3 and 2) before purchasing the specific product (product 4), the control unit 12 proceeds to step S24.

[0058] Step S24: The control unit 12 references the product table 133 and identifies the unit price (¥500) of the specific product (product 4) and the unit prices (¥1,000, ¥2,000) of the unpurchased (all) parent products (products 3 and 2). The control unit 12 then adds the unit price (¥500) of the specific product (product 4) and the unit prices (¥1,000, ¥2,000) of the unpurchased (all) parent products (products 3 and 2) to the amount charged to the purchasing user (user 5), and then proceeds to step S26. The amount charged to user 5 is ¥3,500.

[0059] Step S25: The control unit 12 refers to the product table 133, identifies the unit price of the specific product, and then includes only the unit price in the amount charged to the purchasing user, before proceeding to step S26.

[0060] Step S26: The control unit 12 presents the charge amount (3,500 yen) to the terminal (terminal 50-5) of the purchasing user (user 5).

[0061] Step S27: The control unit 12 determines whether or not a payment request has been received from the terminal (terminal 50-5) of the purchasing user (user 5), and if it has been received (step S27 YES), proceeds to the next step S28, and if it has not been received (step S27 NO), waits.

[0062] Step S28: The control unit 12 transmits the purchasing user (user 5), the billing amount (3,500 yen), and a payment request to the payment server 30. For simplicity, it is assumed that no coupons, points, discounts, etc. are used.

[0063] Step S29: If the control unit 12 receives a payment completion notice from the payment server 30 (step S29 YES), it proceeds to the next step S30. If the control unit 12 does not receive a payment completion notice (step S29 NO), it waits. When the control unit 12 receives a payment completion notice, it updates the payment table 136 by recording the purchasing user (user 5), payment amount (3,500 yen), and payment date and time related to the most recent payment (payment 6 in this case) in the payment table 136.

[0064] Step S30: If the determination result of step S22 is YES (step S30 YES), the control unit 12 proceeds to step S31, and if the determination result of step S22 is NO (step S30 NO), the control unit 12 proceeds to step S33. In this example, the specific product (product 4) has parent products (products 3, 1, and 2), so the control unit 12 proceeds to step S32.

[0065] Step S31: If the determination result of step S23 is YES (step S31 YES), the control unit 12 proceeds to step S32, and if the determination result of step S23 is NO (step S31 NO), the control unit 12 proceeds to step S33. In this case, since the user 5 before payment has not purchased the parent product (products 3 and 2), the control unit 12 proceeds to step S32.

[0066] Step S32: The control unit 12 references the product table 133 to identify the seller (User 4) and the unit price (¥500) of the specific product (Product 4), as well as the sellers (Users 3 and 2) of the unpurchased (all) parent products (Products 3 and 2) and the unit prices (¥1,000 and ¥2,000) of those parent products (Products 3 and 2). The control unit 12 then records the unit price (¥500) of the specific product (Product 4) in the sales of the seller (User 4) of the specific product (Product 4), and records the unit prices (¥1,000 and ¥2,000) of the unpurchased (all) parent products (Products 3 and 2) in the sales of the sellers (Users 3 and 2) of the unpurchased (all) parent products (Products 3 and 2), respectively, before proceeding to step S34. ¥1,000 is recorded in User 3's sales, and ¥2,000 is recorded in User 2's sales.

[0067] Step S33: The control unit 12 refers to the product table 133, identifies the seller and the unit price of the specific product, and then includes the unit price in the sales of the seller user, before proceeding to step S34.

[0068] Step S34: The control unit 12 determines whether or not a predetermined closing date has arrived. If the closing date has arrived (step S34 YES), the control unit 12 proceeds to the next step S35. If the closing date has not arrived (step S34 NO), the control unit 12 returns to the initial step S21.

[0069] Step S35: The control unit 12 transfers the amount obtained by deducting a predetermined fee from the amount of sales (sales) of each user in the user table 143 to the destination specified by each user, then resets the sales in the user table 132 to zero, and returns to the initial step S21. Note that the process related to remittance is well known, so a description thereof will be omitted here.

[0070] 11. Effects of the Embodiment As described above, the sales support server 10, sales support system 100, and sales support program 131 according to the present embodiment support user-to-user trading of 3D model data such as avatars used in the metaverse as products, and allow the seller to specify the unit price that should be reflected in his or her sales when selling the product and the parent product used to create the product. Therefore, the unit price, parent product, and seller can be managed in the storage unit 13 in association with the product.

[0071] Then, based on the information (various tables) stored in the memory unit 13, the sales support server 10, sales support system 100, and sales support program 131 according to this embodiment can, when a purchasing user appears who wishes to purchase a specific product, identify the parent product of the specific product, the unit price of the parent product, and the exhibitor of the parent product. Therefore, the purchasing user can be charged the unit price of both the specific product and the parent product, the unit price of the specific product can be included in the sales of the exhibitor of the specific product, and the sales of the parent product can be included in the sales of the exhibitor of the parent product.

[0072] Therefore, according to the sales support server 10, sales support system 100, and sales support program 131 of this embodiment, it is possible to protect the interests of both the user who exhibits the product and the user who exhibits the parent product used in the production of that product.

[0073] 12. Modifications Related to Resale Permission (for All Users) In order to avoid unnecessary disputes, it is desirable for the control unit 12 of the sales support server 10 (or the operator of the server 10) in the above-described embodiment to obtain a resale permission from the registered user in advance (for example, when the user registers). The "resale permission" here refers to permission for other users (all users) to list other products using the user's listed product as a parent product.

[0074] 13. Modifications Regarding Resale Permission (for Each User) Furthermore, the control unit 12 of the sales support server 10 in the above-described embodiment or modification may allow each user to select whether or not to grant resale permission. In this case, the control unit 12 stores information indicating whether or not the user has granted resale permission in the user registration details in the user table 132 of FIG. 4 . When step S13 of FIG. 9 returns YES, the control unit 12 determines whether or not the users who have listed the declared parent product (and higher-level parent products) include users who have not granted resale permission. If no such users are found, the control unit 12 proceeds to step S14. If any such users are found, the control unit 12 notifies the user terminal that the listing is not permitted and then returns to step S11. Furthermore, the control unit 12 may grant a special benefit (a resale permission special benefit) to users who have granted resale permission. The resale permission special benefit may be granted, for example, by one of the following processes: (1) A process for lowering the commission fee when a user who has been granted permission to resell sells a product compared to the commission fee when a user who has not been granted permission to resell sells a product. (2) A process for granting points, coupons, etc. that can be used to purchase products to users who have been granted permission to resell.

[0075] 14. Modifications Related to Resale Permission (for Each Product) In the above embodiment and modifications, the resale permission can be set for each user. However, each user may also be able to set the resale permission for each listed product. In this case, the control unit 12 stores information indicating whether a product is resold in the product registration details in the product table 133 of FIG. 5, for example. When step S13 of FIG. 9 returns YES, the control unit 12 determines whether the declared parent products (and higher-level parent products) include any products that are not resold. If no products are not resold, the control unit 12 proceeds to step S14. If any products are not resold, the control unit 12 notifies the user terminal that the product cannot be listed and then returns to step S11. The control unit 12 may also perform processing to increase the competitiveness of listed products that are resold. For example, the control unit 12 may perform any of the following processing: (1) A process for keeping the commission fee for selling a product licensed for resale lower than the commission fee for selling a product not licensed for resale. (2) A process (weighting process, etc.) for placing search results for products licensed for resale higher than search results for products not licensed for resale when a purchasing user attempts to view products currently on sale (a list of products on sale) on their own device. (3) A process (increasing the display size, etc.) for displaying products licensed for resale more prominently than products not licensed for resale when a purchasing user attempts to view products currently on sale (a list of products on sale) on their own device.

[0076] 15. Modifications of Currency In the above embodiment and modifications, currency is used as a means of exchanging goods, but it goes without saying that currency that can only be used on the platform (platform-exclusive currency), points, coupons, etc. may be used instead of or in addition to currency.

[0077] 16. Modified Examples of Functional Allocation In the sales support system 100 of the above-described embodiment or modified example, the information stored in the memory unit 13 may be divided and stored in multiple storage devices, or some or all of the information stored in the memory unit 13 may be stored on the data server 20 side. In the sales support system 100 of the above-described embodiment or modified example, at least some of the functions of the data server 10 or the payment server 30 may be mounted on the sales support server 10 side. In the sales support system 100 of the above-described embodiment or modified example, at least some of the functions of the sales support server 10 may be mounted on the data server 10 or the payment server 30 side, or may be mounted on a separate server. In the sales support system 100 of the above-described embodiment or modified example, some of the functions of the sales support server 10 may be mounted on the terminals 50-1, 50-1, ...

[0078] 17. Modifications of Products In addition, in the sales support system 100 of the above-described embodiment or modification, the products are avatars used in the Metaverse, a type of virtual space, and items for decorating the avatars (e.g., hairstyles, costumes, accessories, etc.). However, the products may also be 3D model data of other objects used in a virtual space such as the Metaverse (e.g., terrain objects, flora and fauna objects, architectural objects, vehicle objects, small objects, etc.), or electronic data of other copyrighted works used in a virtual space such as the Metaverse (e.g., audio data, image data, video data, animation data, text data, program data, etc.). Because all copyrighted works are traded as electronic data and may be processed or modified, it is desirable for the sales support system 100 of the above-described embodiment or modification to protect the interests of both the user who exhibits the product and the user who exhibits the parent product used in the creation of that product.

[0079] 18. Regarding accounting processing In the above-described embodiment and variations, the server operator collects a fee from users who put up products, but the operator may also collect a fee from users who purchase products. In this way, in the above-described embodiment and variations, any known method can be used as the accounting method.

[0080] 19. Others The present invention is not limited to the above-described embodiments or modifications, and can be embodied by appropriately modifying the components without departing from the spirit of the invention. Furthermore, various inventions can be created by appropriately combining the multiple components disclosed in each embodiment.

[0081] 100 Sales support system 1 User 2 User 3 User 4 User 10 Sales support server 20 Data server 30 Settlement server 40 Network 50-1 Terminal 50-2 Terminal 11 Communication unit 12 Control unit 121 Product management unit 122 Tree management unit 123 Charging unit 124 Distribution unit 13 Storage unit 131 Sales support program 132 User table 133 Product table 134 Modified tree table 135 Purchase history table 136 Settlement table

Claims

1. A sales support server that supports user-to-user trading of electronic data used in a virtual space as a commodity, comprising: a product management unit that executes a process of storing in a memory unit a user who wishes to sell an item (hereinafter referred to as an "exhibiting user"), a product that the exhibiting user is selling (hereinafter referred to as an "exhibited item"), and a price that should be reflected in the exhibiting user's sales when the exhibited item is sold (hereinafter referred to as an "unit price") in association with each other; a tree management unit that executes a process of having the exhibiting user declare a product (hereinafter referred to as a "parent product") used in the production of the exhibited item, and storing information for identifying the parent product in association with the exhibited item in the memory unit; a billing unit that, when a user (hereinafter referred to as a "purchasing user") who wishes to purchase any exhibited item (hereinafter referred to as a "specific product") that has been put up for sale appears, determines whether or not the specific product is associated with a parent product based on the information stored in the memory unit, and if so, executes a process of including the unit prices of both the specific product and the parent product in the billing amount for the purchasing user; a distribution unit that, when the purchasing user pays the charged amount including the unit prices of both the specific product and the parent product, executes a process of including the unit price of the specific product in the sales of the exhibiting user of the specific product and the unit price of the parent product in the sales of the exhibiting user of the parent product.

2. A sales support server as described in claim 1, wherein the memory unit pre-stores purchase history information indicating the purchase history of a plurality of users, and the billing unit, even if a parent product is associated with the specific product, does not include the unit price of the parent product in the billing amount if it determines based on the purchase history information that the purchasing user has already purchased the parent product.

3. A sales support server as described in claim 1, characterized in that when the billing unit determines that a higher-level parent product is associated with the parent product based on the information stored in the memory unit, the billing unit also includes the unit price of the higher-level parent product in the billing amount.

4. A sales support server as described in claim 1, characterized in that the tree management unit allows the listing user to declare the parent product even if only a portion of the parent product was used in the production of the listed product.

5. A sales support server as described in claim 1, characterized in that the virtual space is a metaverse, and the electronic data includes 3D model data of an avatar, which is a type of object that can be used in the metaverse, and 3D model data of items that decorate the avatar.

6. A sales support system comprising: a sales support server according to any one of claims 1 to 5; and a data server that stores electronic data of a plurality of items exhibited by a plurality of said exhibiting users.

7. A computer-readable sales support program that causes a computer to function as a sales support server that supports user-to-user trading of electronic data used in a virtual space as a commodity, comprising: a product management unit that executes a process of storing in a memory unit, in association with a user who wishes to exhibit an item (hereinafter referred to as an "exhibiting user"), an item exhibited by the exhibiting user (hereinafter referred to as an "exhibited item"), and a price that should be reflected in the exhibiting user's sales when the exhibited item is sold (hereinafter referred to as the "unit price"); a process of having the exhibiting user declare an item used in the production of the exhibited item (hereinafter referred to as a "parent item"), and storing information for identifying the parent item in association with the exhibited item in the memory unit; a process of determining, when a user (hereinafter referred to as a "purchasing user") appears who wishes to purchase any exhibited item (hereinafter referred to as a "specific item") that has been exhibited, whether or not the specific item is associated with a parent item based on the information stored in the memory unit, and if so, including the unit prices of both the specific item and the parent item in the amount charged to the purchasing user; When the purchasing user pays the charged amount including the unit prices of both the specific product and the parent product, the unit price of the specific product is included in the sales of the exhibitor user of the specific product, and the unit price of the parent product is included in the sales of the exhibitor user of the parent product.

Citation Information

Patent Citations

  • Media content management system and media content management method

    JP2009157565A

  • Information processing device, information processing method, and program

    JP2009296159A

  • Computer system and digital work trading control method

    JP2021189475A

  • Information processing apparatus

    JP2022062975A