Object trading program, object trading system, and object trading method

Abstract

To prevent excessive simplification of object collection.SOLUTION: Means for acquiring a proposal for an object exchange with a second user from objects owned by a first user, the proposal including setting of a second object to be exchanged, means for acquiring acceptance or rejection of the proposal by the second user, and means for acquiring establishment or non-establishment of an exchange between the first object and the second object by the first user when the proposal is accepted. means for acquiring a proposal for an object exchange with a second user from objects owned by a first user, the proposal including setting of a second object to be exchanged, means for acquiring establishment or non-establishment of an exchange between the first object and the second object by the first user when the proposal is accepted. Causing the first user to possess the second object and causing the second user to possess the first object, wherein when the object exchange with the second user is proposed, a first parameter that changes in accordance with a lapse of time associated with the first user is used.SELECTED DRAWING: Figure 7

Description

[Technical Field]

[0001] The present invention relates to an object trading program, an object trading system, and an object trading method. [Background technology]

[0002] There are known object trading systems that allow users to trade objects such as electronic media cards. In some object trading systems, conditions are set, such as requiring that the objects to be traded must have the same rarity. In such cases, users cannot complete a trade unless they know the rarity of the objects.

[0003] Therefore, a technology has been disclosed that aims to stimulate trading by automatically determining tradable objects based on the objects owned by the user and the trade conditions, and presenting the results to the user (Patent Document 1). [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Patent Publication No. 2019-209117 Summary of the Invention [Problem to be solved by the invention]

[0005] However, if unlimited exchange of objects is possible, the desire to collect objects may become excessive. Therefore, a technique for appropriately suppressing the exchange of objects is needed. [Means for solving the problem]

[0006] One aspect of the present invention is a trading program that causes a computer to function as: means for obtaining a proposal for an object exchange with a second user different from the first user, the proposal including settings of a first object to be exchanged from an object owned by a first user; means for obtaining an acceptance or rejection of the proposal by the second user; means for obtaining a proposal for an object exchange with the first user, the proposal including settings of a second object to be exchanged from an object owned by the second user, if the proposal is accepted; means for obtaining whether an exchange of the first object and a second object by the first user has been successful or not; and means for allowing the first user to own the second object and the second user to own the first object, if the exchange is successful; and when the proposal for the object exchange with the second user is made, a first parameter that changes over time and is associated with the first user is used.

[0007] Here, when a proposal to exchange an object with the second user is made, a second parameter associated with the first user in accordance with the first object is preferably used.

[0008] It is also preferable that a second parameter associated with the first user is used depending on the rarity of the first object.

[0009] Furthermore, if the exchange is unsuccessful, it is preferable that the first parameter and the second parameter are returned in association with the first user.

[0010] Furthermore, if the exchange is successful, it is preferable that a reward be given to at least one of the first user and the second user.

[0011] Another aspect of the present invention is a trading system comprising: means for acquiring a proposal for an object exchange with a second user different from the first user, the proposal including settings of a first object to be exchanged from an object owned by a first user; means for acquiring an acceptance or rejection of the proposal by the second user; means for acquiring a proposal for an object exchange with the first user, the proposal including settings of a second object to be exchanged from an object owned by the second user if the proposal is accepted; means for acquiring whether the exchange of the first object and the second object by the first user has been successful or not; and means for allowing the first user to own the second object and the second user to own the first object if the exchange is successful; wherein when the proposal for the object exchange with the second user is made, a first parameter that changes over time and is associated with the first user is used.

[0012] Another aspect of the present invention is a trading method that causes a computer to perform the following steps: acquiring a proposal for an object exchange with a second user different from the first user, the proposal including settings of a first object to be exchanged from an object owned by a first user; acquiring an acceptance or rejection of the proposal by the second user; if the proposal is accepted, acquiring a proposal for an object exchange with the first user, the proposal including settings of a second object to be exchanged from an object owned by the second user; acquiring a result of whether the exchange of the first object and the second object by the first user has been successful; and if the exchange has been successful, allowing the first user to own the second object and allowing the second user to own the first object; and characterized in that when the proposal for the object exchange with the second user is made, a first parameter that changes over time and is associated with the first user is used. [Effects of the Invention]

[0013] According to the present invention, it is possible to prevent oversimplification of object collection. Other objects of the embodiments of the present invention will become apparent by reading the entire specification. [Brief explanation of the drawings]

[0014] [Figure 1] 1 is a diagram showing a configuration of an object trade system according to an embodiment of the present invention. [Figure 2] FIG. 2 is a diagram illustrating a configuration of a server according to an embodiment of the present invention. [Figure 3] FIG. 2 is a diagram illustrating a configuration of a user terminal according to an embodiment of the present invention. [Figure 4] FIG. 3 is a diagram illustrating an example of an object database according to the embodiment of the present invention. [Figure 5] FIG. 3 is a diagram illustrating an example of a user database according to the embodiment of the present invention. [Figure 6] FIG. 2 is a diagram illustrating an example of a management database according to an embodiment of the present invention. [Figure 7] 1 is a flowchart showing a process for object trading according to an embodiment of the present invention. [Figure 8] FIG. 10 is a diagram showing a user selection screen according to the embodiment of the present invention. [Figure 9] FIG. 10 is a diagram showing an object selection screen according to the embodiment of the present invention. [Figure 10] FIG. 10 is a diagram showing an object selection screen in which an object is selected in the embodiment of the present invention. [Figure 11] FIG. 2 is a diagram illustrating an example of a trade database according to an embodiment of the present invention. [Figure 12] FIG. 10 is a diagram showing a trade proposal screen according to an embodiment of the present invention. [Figure 13] FIG. 10 is a diagram showing a trade confirmation screen in the embodiment of the present invention. [Figure 14] FIG. 2 is a diagram illustrating an example of a trade database according to an embodiment of the present invention. [Figure 15]FIG. 2 is a diagram illustrating an example of a trade database according to an embodiment of the present invention. [Figure 16] FIG. 10 is a diagram showing a trade confirmation screen in the embodiment of the present invention. [Figure 17] FIG. 2 is a diagram illustrating an example of a trade database according to an embodiment of the present invention. [Figure 18] FIG. 2 is a diagram illustrating an example of a trade database according to an embodiment of the present invention. [Figure 19] FIG. 10 is a diagram showing an object exchange screen before an object is acquired in the embodiment of the present invention. [Figure 20] FIG. 10 is a diagram showing an object exchange screen for each object acquisition in the embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0015] As shown in Fig. 1, an object trading system 100 according to an embodiment of the present invention includes a server 102 and a user terminal 104. In this embodiment, a first user uses user terminal 104a, and a second user uses user terminal 104b. Server 102 and user terminal 104 are connected to each other via an information and communications network 108 such as the Internet so that they can exchange information with each other.

[0016] The information and communication network 108 is not limited to the Internet, but may be anything that can connect the server 102 and the user terminal 104 to each other so that they can communicate with each other. For example, it may be a dedicated line, a public line (telephone line, mobile communication line, etc.), a wired LAN (Local Area Network), a wireless LAN, etc., or it may be a combination of the Internet and these.

[0017] The server 102 receives information about the objects to be exchanged from the user terminal 104a used by the first user and the user terminal 104b used by the second user, and performs processing for exchanging the objects.

[0018] As shown in FIG. 2, the server 102 includes a processing unit 10, a memory unit 12, an input unit 14, an output unit 16, and a communication unit 18. The processing unit 10 includes a means for performing arithmetic processing, such as a CPU. The processing unit 10 executes a server program stored in the memory unit 12 to interconnect multiple user terminals 104 and perform processing related to object exchange in the object trading system 100 of this embodiment. The memory unit 12 includes storage means, such as a semiconductor memory, a hard disk, and a memory object. The memory unit 12 is accessible to the processing unit 10 and stores the server program and information necessary for the processing. The input unit 14 includes a means for inputting information. The input unit 14 includes, for example, a keyboard, a touch panel, buttons, etc. for receiving input from an administrator. The output unit 16 includes a means for outputting processing results of the server 102, such as a user interface screen (UI) for receiving input information from the administrator. The output unit 16 includes, for example, a display for presenting images to the administrator. The communication unit 18 includes an interface for communicating information with the user terminals 104 via the information and communication network 108. The communication by the communication unit 18 may be wired or wireless.

[0019] The user terminal 104 is a terminal used by a user who exchanges objects. As shown in FIG. 3, the user terminal 104 includes a processing unit 20, a memory unit 22, an input unit 24, an output unit 26, and a communication unit 28. The processing unit 20 includes a means for performing arithmetic processing, such as a CPU. The processing unit 20 realizes the function of a user terminal in the object trading system 100 of this embodiment by executing a user terminal program included in an application stored in the memory unit 22. The memory unit 22 includes storage means, such as a semiconductor memory, a hard disk, or a memory object. The memory unit 22 is accessible to the processing unit 20 and stores the user terminal program and information necessary for its processing. The input unit 24 includes a means for inputting information. The input unit 24 includes, for example, a keyboard, a touch panel, buttons, etc., for receiving input from the user. The output unit 26 includes a means for outputting information necessary for processing on the user terminal 104, such as a screen for receiving input information from the user or a display for displaying image information such as a user interface screen (UI). The communication unit 28 is configured to include an interface for communicating information with the server 102 via the information communication network 108. The communication by the communication unit 28 may be wired or wireless.

[0020] The user terminal 104 can be any of a variety of information processing devices capable of executing programs for providing the services of the object trading system 100. For example, the user terminal 104 can be a dedicated stationary or portable device, a personal computer (PC), a tablet computer, a smartphone, a mobile phone terminal, a PHS (Personal Handy-phone System) terminal, a personal digital assistant (PDA), a multi-function television receiver with information processing capabilities (so-called smart TV), etc.

[0021] The user terminal 104 can be realized by installing an application provided by the server 102 or the like in advance on an information processing device. Each user operates the user terminal 104 to start the application, and performs processing for exchanging objects via the server 102.

[0022] [Object Database] In this embodiment, objects treated as electronic data are the subject of exchange (trade). The object may be any exchangeable electronic medium. The object may be, for example, a card, character, item, or the like, which is an electronic medium. When the object is a card, a card pack treated as electronic data has multiple cards associated therewith, and by performing a process of opening the card pack, the card associated with the card pack can be given to the user.

[0023] The method for acquiring the object is not particularly limited, and the object may be acquired by a user free of charge as a reward in an electronic game or the like, or may be acquired by a user for a fee such as by paying a fee. For example, the object may be purchased from an online shop. Furthermore, the object may be awarded by a random lottery, free of charge or for a fee. Furthermore, the object may be awarded by joining a fan club, for example. Furthermore, the object may be awarded by participating in a predetermined SNS event, for example. However, the method for acquiring the object is not limited to these methods, and any method may be used.

[0024] Information on objects owned by each user is stored as an object database in the storage unit 12. Note that the object database does not necessarily have to be stored in the storage unit 12, but may be stored in a storage medium accessible from the server 102 and the user terminal 104.

[0025] As shown in the example of Figure 4, the object database stores user IDs, object IDs, object types, rarity, attributes, and image data in association with each other. A user ID is an identifier uniquely assigned to each user. In the object database, a user ID is used to identify the user who owns an object. An object ID is an identifier uniquely assigned to each type of object. An object type is an identifier uniquely assigned to each type of object. An object type can be, for example, the name of an object. Rarity is information indicating the rarity of an object.

[0026] The rarity of an object refers to the low probability of obtaining the object when the user opens the object pack. In other words, an object with a high rarity has a low probability of appearing, and an object with a low rarity has a high probability of appearing. In this embodiment, an example will be described in which rarities are represented by R1 to R4 in order of decreasing rarity.

[0027] Attributes are information that indicate the attributes of an object, such as a normal object or a special object. For example, the attribute of an object that can be obtained from a normal object pack is "normal," while the attribute of an object that can only be obtained through a special project (promotion) is "PROMO." Image data is data used when displaying an image of an object.

[0028] [User Database] In the object trading system 100, information about users is stored as a user database in the storage unit 12. Note that the user database does not necessarily have to be stored in the storage unit 12, but may be stored in a storage medium accessible from the server 102 and the user terminal 104.

[0029] As shown in Figure 5, the user database stores user IDs, user names, passwords, friend information, trade status, trade power, recovery items, trade medals, and total blocks in association with each other. As mentioned above, the user ID is an identifier uniquely assigned to each user. The user name is the name used by the user. The password is information used as authentication information when the user logs in to the object trading system 100.

[0030] The friend information is information that indicates other users who have a friend relationship with the user. The friend information stores the user IDs of other users who have a friend relationship with the user. In this embodiment, the conditions for users to become friends with each other are not particularly limited, and it is sufficient that the users can become friends when some conditions are met.

[0031] The trade status is information indicating whether the user is currently in an object exchange session. In this embodiment, a user is restricted from participating in multiple object exchange sessions at the same time. Therefore, if the user is currently in an object exchange session, the trade status is set to "in trade," and if not, the trade status is set to "not in trade."

[0032] Trade power is the first parameter consumed when exchanging objects. One trade power must be consumed to perform one trade. When a user requests an object exchange, the user's trade power is reduced by one. However, the amount of trade power required to exchange an object can be set as appropriate.

[0033] Trade power recovers naturally after a certain period of time has passed. The certain period of time can be set as appropriate. For example, trade power can be increased by one every 24 hours. An upper limit can also be set for the natural recovery of trade power. For example, the upper limit for natural recovery of trade power can be set to 5.

[0034] Furthermore, the use of a specific item may be made to assist in the recovery of trade power. For example, the use of a recovery item may be made to shorten the time until trade power is recovered. As a specific example, the use of one recovery item may be made to shorten the time until trade power is recovered by one hour. In this case, the use of 24 of the recovery items may be made to recover one unit of trade power. Furthermore, for example, the use of a recovery item may be made to recover one unit of trade power. However, the method of assisting the recovery of trade power using recovery items is not limited to these.

[0035] The method for acquiring recovery items is not particularly limited. For example, the user may be able to acquire them free of charge as a reward in an electronic game or the like, or may be able to acquire them for a fee by paying some kind of compensation such as a charge. For example, recovery items may be purchased from an online shop. Furthermore, recovery items may be awarded by random lottery, free of charge or for a fee. Furthermore, recovery items may be awarded by joining a fan club, for example. Furthermore, recovery items may be awarded by participating in a predetermined SNS event, for example.

[0036] Additionally, an upper limit may be set for the recovery of trade power through the use of recovery items. For example, the upper limit for the amount of trade power that can be recovered naturally may be set to 8.

[0037] Furthermore, if a trade is unsuccessful, the trade power that was reduced when the trade was requested is restored. In this case, it is preferable to restore trade power beyond the natural recovery limit and the optional recovery limit. For example, if the user's trade power had already naturally recovered to 4.8 when the trade was unsuccessful, the trade power is restored to 5.8 when the trade was unsuccessful. For example, if the user's trade power had already naturally recovered to 7.8 through the use of a recovery item when the trade was unsuccessful, the trade power is restored to 8.8 when the trade was unsuccessful.

[0038] Trade medals are a second parameter that is consumed along with trade power when exchanging objects. Trade medals are consumed according to at least one of the rarity and attributes of the object being exchanged.

[0039] FIG. 6 shows a management database that indicates the relationship between the rarity of an object and the number of trade medals consumed when exchanging that object. As shown in FIG. 7, it is preferable to increase the number of trade medals consumed when exchanging that object as the rarity of the object increases (R1 → R5). It is also preferable to increase the number of trade medals consumed when exchanging an object with a rarer attribute, depending on the object's attributes. In other words, it is preferable to set it so that more trade medals are required to exchange an object with a rarer value. Note that the number of trade medals is not limited to one type, and multiple types of trade medals may be provided.

[0040] For example, in the example management database of FIG. 6, the number of trade medals required to exchange an object with the attribute "normal" and rarity "R1" is 0, meaning that no trade medals are required. In this way, trade medals may be unnecessary for the exchange of objects with low rarity, allowing for free exchange. In contrast, the number of trade medals required to exchange an object with the attribute "normal" and rarity "R3" is 500. In this way, by setting it so that more trade medals are required to exchange objects with higher rarity, the exchange of higher rarity objects may be suppressed.

[0041] The method for acquiring trade medals is not particularly limited. For example, users may be able to acquire them free of charge as a reward in an electronic game or the like, or may be able to acquire them for a fee by paying some kind of compensation, such as a charge. For example, trade medals may be purchased from an online shop. Furthermore, trade medals may be awarded through a random lottery, free of charge or for a fee. Furthermore, trade medals may be awarded by joining a fan club, for example. Furthermore, trade medals may be awarded by participating in a specified SNS event, for example.

[0042] The overall block is information indicating whether or not a block state is set to prevent the exchange of objects. A user who does not wish to exchange objects in the object trading system 100 can block object exchange by setting the overall block. The overall block setting can be set as appropriate on a user setting screen, etc.

[0043] [Object trade processing] 7, an object trade process for exchanging objects between users in the object trade system 100 will be described. The process for exchanging objects via the server 102 will be described below, in which a first user (user X) uses the user terminal 104a and a second user (user Y) uses the user terminal 104b.

[0044] It is assumed that both the first user and the second user are already logged in to the object trading system 100. In the logged-in state, the user terminal 104a and the user terminal 104b are able to obtain information from the object database, the user database, and the management database stored in the storage unit 12 of the server 102.

[0045] In step S10, the first user selects a user with whom to exchange objects and a first object with which to exchange objects. The first user is a user who proposes an object exchange. Through the processing in this step, the user terminal 104a functions as a first object selection means.

[0046] The first user starts trading objects in the object trading system 100 by operating the user terminal 104a. First, the first user selects a user with whom to trade. In this embodiment, only users who are friends with the first user can be selected as exchange partners for objects. If the first user does not have any friends registered, the first user may be prompted to register a friend.

[0047] The user terminal 104a acquires information about users who are associated as friends with the user ID of the first user from the user database. As shown in Fig. 8, the user terminal 104a displays a user selection screen 210 on the output unit 26. The user selection screen 210 displays a user selection section 212 for selecting each user who is friends with the first user as a trading partner.

[0048] The user selection section 212 includes a user icon 212a, a user name display section 212b, and a trade selection section 212c. The user icon 212a displays an icon image that is registered in advance for each user. The user name display section 212b displays the usernames of users who are friends with the first user. The trade selection section 212c displays a button that is selected (clicked, tapped, etc.) when selecting a partner for exchanging objects.

[0049] Depending on the trade status in the user database, it is preferable to exclude users whose trade status is "Trading" from the user selection section 212 of the user selection screen 210, and display only users whose trade status is "Not Trading" in the user selection section 212. For example, since the trade status of "User Z" with user ID "U03" is "Trading," he is not displayed in the user selection section 212 even if he is in a friend relationship with the first user "User X."

[0050] In addition, it is preferable to display the trade selection section 212d in an unselectable state for users for whom an overall block has been set, depending on the registered contents of the overall block in the user database. For example, since an overall block has been set for "User V" whose user ID is "U05", the user is displayed in the user selection section 212, but the trade selection section 212d is displayed in an unselectable state (shown by a dashed line in FIG. 8).

[0051] The first user selects a user with whom to exchange objects by selecting the trade selection section 212c in the user selection section 212. In this embodiment, the description will be given assuming that the second user is selected as the user with whom to exchange objects.

[0052] The first user operates the user terminal 104a to select an object to be exchanged in the object trading system 100 as a first object.

[0053] The user terminal 104a acquires information about objects associated with the user ID of the first user from the object database. As shown in Fig. 9, the user terminal 104a displays an object selection screen 220 on the output unit 26. The object selection screen 220 includes an object selection section 222, an explanation area 224, a resource display area 226, a search input area 228, a confirmation button 230, and a back button 232.

[0054] The object selection section 222 is an area for the first user to select a first object. The object selection section 222 is displayed for each type of object based on image data of the objects owned by the first user. The first user selects the first object to be exchanged by selecting (clicking, tapping, etc.) the object selection section 222 that displays the object to be exchanged. Note that the selection can be cancelled by selecting (clicking, tapping, etc.) the selected object selection section 222 again.

[0055] Furthermore, a remaining object number display area 222a is displayed in the object selection section 222. The remaining object number display area 222a displays the number of owned objects of the objects displayed in the object selection section 222. By checking the remaining object number display area 222a, the first user can confirm the current number of owned objects and then determine whether or not to select the object as a target for exchange.

[0056] It is preferable that non-exchangeable objects among the objects owned by the first user are displayed in a manner that allows them to be distinguished from the object selection section 222 for exchangeable objects, as shown as object selection section 234 in Fig. 10. A distinguishable manner includes, for example, displaying the object selection section 222 for exchangeable objects and the object selection section 234 for non-exchangeable objects with different brightness, colors, shapes, etc. Objects displayed as non-exchangeable object selection section 234 are processed so that they cannot be selected as the first object on the object selection screen 220.

[0057] An object that cannot be exchanged can be an object for which the first user does not currently have enough trade medals to exchange. In this way, an object that cannot be exchanged is displayed in the object selection section 234.

[0058] Information regarding the exchange of objects is displayed in the explanation area 224. For example, in this embodiment, only objects of the same rarity can be exchanged, so the explanation area 224 displays a description such as "You will receive an object of the same rarity as the object you are sending."

[0059] The resource display area 226 is an area where the value of the trade diamonds owned by the first user is displayed, i.e., the amount of resources that can be used to exchange for objects is displayed in the resource display area 226.

[0060] The search input area 228 is an area for searching for an object. By inputting search information related to an object into the search input area 228, only objects owned by the first user that match or are related to the search information are displayed on the object selection screen 220. The search information may be, for example, information such as the object type (object name), rarity value, attributes, etc.

[0061] Confirm button 230 is a button selected when deciding that the object selected on object selection screen 220 is to be exchanged. When the first user selects (clicks, taps, etc.) confirmation button 230 while selecting object selection section 222 displaying the object to be exchanged, the object corresponding to the selected object selection section 222 is set as the object to be exchanged.

[0062] The back button 232 is a button for returning to the screen before transition from the object selection screen 220. If the first user wants to end the trade without selecting an object, the first user ends the trade by selecting (clicking, tapping, etc.) the back button 232.

[0063] FIG. 10 shows the object selection screen 220 when an object of the object type "Object B" (upper center) (the description will be given assuming that "Object B" has been selected as the first object) is selected as the first object to be exchanged. When an object is selected as the first object, the object is displayed as an object selection section 236. It is preferable that the object selection section 236 is displayed in a display manner that allows it to be distinguished from the object selection sections 222 of other objects that have not been selected. In FIG. 10, the object selection section 236 is displayed with shading, showing a display manner that is different from the other object selection sections 222. A distinguishable manner includes, for example, displaying the object selection section 236 of the first object and the object selection sections 222 of the other objects in different brightness, different colors, different shapes, etc.

[0064] It is also preferable to display a required resource display section 236a in conjunction with the object selection section 236. The object selection section 236 is an area that displays the resources required to exchange the selected object, i.e., the amount of trade diamonds. For example, when "Card B" owned by "User X," a first user, is selected, the object database is referenced to read out the attribute "normal" and rarity "R3" of "Card B." The management database is then referenced to read out the amount of trade diamonds "500" required for the combination of the attribute "normal" and rarity "R3" of "Card B." The required resource display section 236a then displays "500" as the amount of trade diamonds required to exchange "Card B."

[0065] As described above, trading power is required to exchange objects. For example, if the trading power required to exchange one object is 1, it is preferable to prevent the first user (user X) from selecting an object on the object selection screen 220 when his / her trading power is less than 1. In this case, it is preferable to display a message such as "You do not have enough trading power to exchange the object." The first user can wait until his / her trading power recovers naturally by selecting the back button 232, or by using a recovery item to recover his / her trading power at will, thereby becoming able to exchange objects.

[0066] Furthermore, when selecting an object selection section 222, if the number of trade medals required to exchange for the object corresponding to that object selection section 222 exceeds the number of trade medals owned by the first user, it is preferable to make that object selection section 222 unselectable. In this case, it is preferable to display a message such as "There are not enough trade medals required to exchange for the object [Number required: MMM (Number owned: NNN)]." The first user can perform a process to acquire trade medals by selecting the back button 232, for example.

[0067] When the object to be exchanged is selected in the object selection section 222 and the confirmation button 230 is selected, the object is selected as the first object to be exchanged.

[0068] A confirmation screen may be displayed on which the information of the object selected in the above selection process can be confirmed. Also, the user may be allowed to return to the selection of the exchange partner user and the selection of the first object to be exchanged and redo the selection.

[0069] As described above, the selection process of the object exchange partner and the first object to be exchanged is performed. When the selection process is completed, the user terminal 104a transmits to the server 102 information indicating the user ID of the user with whom the object is to be exchanged, the object type and object ID of the first object to be exchanged, in association with the user ID of the first user.

[0070] If an object has other attributes such as language, a process for selecting those attributes may be provided. For example, if there are language attributes such as a Japanese object and an English object, it may be possible to select which object attribute to use as the first object to be exchanged.

[0071] In step S12, a process for receiving the user and the first object is performed. Through the process in this step, server 102 functions as a first object receiving means. Server 102 receives the information transmitted from user terminal 104a in step S10. As a result, server 102 receives information indicating the user ID of the user with whom the object is to be exchanged, the object type and object ID of the first object to be exchanged, in association with the user ID of the first user.

[0072] 11, the server 102 assigns a unique trade ID to the trade, and stores the received information associated with the trade ID as a trade database in the storage unit 12. The server 102 also stores the date and time when the trade request was received from the user terminal 104a as the trade start date and time, associated with the trade ID.

[0073] In this embodiment, the trade database stores a trade ID "T01", a first user ID "U01", a first user name "User X", a second user ID "U02", a second user name "User Y", a first object ID "C002", and a first object type "Object B" in association with each other. In addition, the start date and time of the trade, "2024 / 1 / 1 12:00", is stored in association with each other.

[0074] The server 102 also performs a process to reduce the trade power and trade medals required to exchange the object in the user database. In this embodiment, the trade power associated with the first user, "User X," is reduced by 1, and the trade medals are reduced by 500, which are required to exchange "Object B" with the attribute "normal" and rarity "R3."

[0075] Furthermore, server 102 references the user ID of the user with whom the object is to be exchanged, and transmits information about the first object to be exchanged to user terminal 104 used by that user. In this embodiment, server 102 transmits to user terminal 104b used by a second user information indicating the trade ID, the username and user ID of the first user, the object type and object ID of the first object to be exchanged, and the start date and time of the trade.

[0076] In step S14, information about the first object is received by the user terminal 104b of the second user. Through the processing in this step, the user terminal 104b used by the second user functions as first object receiving means. The user terminal 104b of the second user receives the information transmitted from the server 102 in step S12. As a result, the user terminal 104b accepts, in association with the user ID of the first user, information indicating the user ID of the user with whom the object is to be exchanged, the object type and object ID of the first object to be exchanged, and the start date and time of the trade.

[0077] The user terminal 104b displays information indicating that a trade proposal has been made to the second user. For example, as shown in FIG. 12, a trade proposal screen 280 is displayed on the output unit 26 of the user terminal 104b.

[0078] As shown in FIG. 12, the trade proposal screen 280 includes a trade image area 282, a remaining trade time display area 284, a trade partner display area 286, a confirmation button 288, and an end button 290.

[0079] The trade image area 282 is an area that displays an image that visualizes the trade of objects. The remaining trade time display area 284 is an area that displays the time remaining until the deadline for the second user, who is the object exchange partner, to respond whether or not to accept the exchange. The trade deadline is set, for example, to a predetermined time from the trade start date and time set in step S12. The predetermined time can be, for example, three days from the trade start date and time.

[0080] The trade partner display area 286 is an area where information about the user who proposed the trade is displayed. For example, the trade partner display area 286 displays the username of the first user, such as "User X," along with the explanation, "You have received a trade request."

[0081] The confirmation button 288 is a button for confirming the details of the proposed trade. When the second user selects (clicks, taps, etc.) the confirmation button 288, the process proceeds to display a trade confirmation screen 300, which allows the second user to confirm the details of the trade proposed by the first user. The exit button 290 is a button for returning from the trade proposal screen 280 to the screen before transition. When the second user selects (clicks, taps, etc.) the exit button 290, the process returns to the screen immediately before transitioning to the trade proposal screen 280.

[0082] In step S16, the user terminal 104b of the second user accepts or rejects the trade with the first object and selects the object to be exchanged. Through the processing in this step, the user terminal 104b used by the second user functions as trade acceptance / rejection selection means and second object selection means.

[0083] In step S14, when the confirmation button 288 is selected, a trade confirmation screen 300 is displayed on the output unit 26 of the user terminal 104b. As shown in FIG. 13 , the trade confirmation screen 300 includes a trade partner display area 302, an object display area 304, a remaining trade time display area 306, a trade reject button 308, a trade accept button 310, and an end button 312.

[0084] The trade partner display area 302 displays information about the user who proposed the trade. For example, the trade partner display area 286 displays the username of the first user, such as "User X." The object display area 304 is an area that displays information about the first object that the first user is proposing to exchange. For example, an image of the first object is displayed in the object display area 304.

[0085] Furthermore, when the object database is referenced and the type of the first object corresponds to a type of object that the second user does not own, a NIW mark 304a may be displayed in the object display area 304. This allows the second user to easily understand by checking the trade confirmation screen 300 that the type of first object proposed for exchange by the first user is a type of object that the second user does not currently own.

[0086] The remaining trade time display area 306 is an area that displays the time remaining until the deadline for the second user, with whom the object is being exchanged, to respond as to whether or not to accept the exchange. The remaining trade time display area 306 is displayed in the same manner as the remaining trade time display area 284 on the trade proposal screen 280.

[0087] The trade reject button 308 is a button that is selected when the second user wishes to reject the exchange of an object. The second user can reject the exchange of an object by selecting (clicking, tapping, etc.) the trade reject button 308. When the trade reject button 308 is selected, the user terminal 104b transmits to the server 102 the trade ID and information indicating that the exchange of the object has been rejected.

[0088] The trade acceptance button 310 is a button that is selected when accepting the exchange of an object. The second user can accept the exchange of an object by selecting (clicking, tapping, etc.) the trade acceptance button 310. When the trade acceptance button 310 is selected, the user terminal 104b proceeds to a process in which the second user selects a second object to be exchanged.

[0089] The exit button 312 is a button for returning to the screen prior to the transition from the trade confirmation screen 300. When the second user selects (clicks, taps, etc.) the exit button 312, the process returns to the screen immediately prior to the transition to the trade confirmation screen 300.

[0090] When the trade accept button 310 is selected, the second user selects an object to be exchanged from the objects owned by the second user as the second object. The user terminal 104b acquires information about the object associated with the second user's user ID from the object database. The user terminal 104b displays a screen similar to the object selection screen 220 shown in FIG. 9 based on the acquired information about the object owned by the second user.

[0091] In this embodiment, since only objects having the same rarity as the first object can be exchanged, it is preferable that only objects of the same rarity as the first object among those owned by the second user are displayed in the object selection unit 222. At this time, an explanation indicating the conditions of the trade, such as "Please send me an object of the same rarity," is displayed in the explanation area 224. Note that if the second user does not own an object of the same rarity as the first object, a message to that effect is displayed and then a process of forcibly returning to the previous screen is performed.

[0092] The second user selects an object to be exchanged with the first object as the second object on the object selection screen 220 displayed on the user terminal 104b. When the object selection section 222 of the object to be exchanged is selected and the confirmation button 230 is selected, the object is selected as the second object to be exchanged. The selection process of the second object by the second user on the object selection screen 220 can be performed in the same manner as the selection process of the first object by the first user in step S10.

[0093] Note that trading power is required to exchange objects. For example, if the trading power required to exchange one object is 1, it is preferable to prevent the second user (user Y) from selecting an object on the object selection screen 220 if his / her trading power is less than 1. In this case, it is preferable to display a message such as "You do not have enough trading power to exchange the object." The second user can then exchange objects by selecting the back button 232 or other means to wait until his / her trading power recovers naturally, or by using a recovery item to recover his / her trading power at will.

[0094] Furthermore, when selecting an object selection section 222, if the amount of trade medals required to exchange for the object corresponding to that object selection section 222 exceeds the amount of trade medals owned by the second user, it is preferable to make that object selection section 222 unselectable. In this case, it is preferable to display a message such as "There are not enough trade medals required to exchange for the object [Number required: MMM (Number owned: NNN)]." The second user can perform a process to acquire trade medals by selecting the back button 232, for example.

[0095] A confirmation screen may be displayed that allows the user to confirm information about the object selected in the above selection process. Also, the user may be allowed to return to the process of selecting the user with whom to exchange and the second object to be exchanged and redo the selection.

[0096] As described above, the selection process for the second object to be exchanged is performed. When the selection process is completed, the user terminal 104b transmits to the server 102 information indicating the trade ID, the user ID of the first user with whom the object is to be exchanged, and the object type and object ID of the second object to be exchanged, in association with the user ID of the second user.

[0097] If an object has other attributes such as language, a process for selecting those attributes may be provided. For example, if there are language attributes such as a Japanese object and an English object, it may be possible to select which object attribute to use as the first object to be exchanged.

[0098] In addition, during the period when the first user is waiting for a response from the second user, the user terminal 104a used by the first user may be configured to display a standby screen indicating that the first user is waiting for a response from the second user, who is the exchange partner.

[0099] In step S18, a process of receiving the second object is performed. Through the process in this step, the server 102 functions as a second object receiving means. The server 102 receives the information transmitted from the user terminal 104b in step S16.

[0100] If the trade is rejected by the second user in step S16, the server 102 receives information indicating that the trade has been rejected along with the trade ID. In this case, as shown in Figure 14, the "Acceptance or Rejection by Exchange Partner" field for the trade proposal stored in the trade database in step S12 in association with the received trade ID is set to "Rejected." Furthermore, the server 102 transmits information indicating that the trade has been rejected to the user terminal 104a used by the first user.

[0101] Furthermore, if no acceptance or rejection response is received from the second user by the deadline for the second user to respond as to whether or not to accept the exchange, the trade will be deemed unsuccessful and will be handled in the same manner as if the trade had been rejected.

[0102] If the trade is not successful, the server 102 performs a process to return the trade power and trade medals of the first user that were subtracted from the user database in step S12 as necessary for the exchange of the object. In this embodiment, the process returns 1 to the trade power associated with the first user, "User X," and returns 500 trade medals, which are necessary for the exchange of "Object B" with the attribute "normal" and rarity "R3."

[0103] In step S16, if the trade is accepted by the second user, the server 102 accepts information indicating the trade ID, the user ID of the first user with whom the object is to be exchanged, and the object type and object ID of the second object to be exchanged, in association with the user ID of the second user.

[0104] As shown in FIG. 15, the server 102 stores the received information in the storage unit 12 as a trade database in association with the received trade ID. First, the "Acceptance or Rejection by Exchange Partner" field for the trade proposal stored in the trade database in step S12 in association with the received trade ID is set to "Accepted." Furthermore, the server 102 newly stores information indicating the trade ID, the user ID and user name of the first user, the user ID and user name of the second user, and the object type and object ID of the second object to be exchanged. The server 102 also stores the date and time when the trade acceptance was accepted from the user terminal 104b as the trade acceptance date and time in association with the trade ID.

[0105] In this embodiment, the trade database stores a trade ID "T01", a first user ID "U01", a first user name "User X", a second user ID "U02", a second user name "User Y", a second object ID "C003", and a second object type "Object C" in association with each other. In addition, the trade acceptance date and time "2024 / 1 / 2 13:20" is stored in association with each other.

[0106] The server 102 also performs a process to reduce the trade power and trade medals required to exchange the object in the user database. In this embodiment, the server 102 reduces the trade power associated with the second user, "User Y," by 1, and reduces the trade medals by 500, which are required to exchange "Object C" with the attribute "normal" and rarity "R3."

[0107] Furthermore, the server 102 references the user ID of the first user and transmits information about the second object to be exchanged to the user terminal 104a used by the first user. The server 102 transmits information indicating the trade ID, the username and user ID of the second user, and the object type and object ID of the second object to be exchanged to the user terminal 104a used by the first user.

[0108] In step S20, information about the second object is received by the user terminal 104a of the first user. Through the processing in this step, the user terminal 104a used by the first user functions as second object receiving means. The user terminal 104a of the first user receives the information transmitted from the server 102 in step S18.

[0109] If the trade is rejected by the second user, the user terminal 104a receives information indicating that the trade has been rejected from the server 102. The user terminal 104a displays a screen indicating that the trade has been rejected on the output unit 26, and ends the trade.

[0110] If the trade is accepted by the second user, the user terminal 104a receives information indicating the trade ID, the username and user ID of the second user, and the object type and object ID of the second object to be exchanged.

[0111] The user terminal 104a displays information indicating that the trade has been accepted for the first user. For example, the output unit 26 of the user terminal 104a displays a trade proposal screen 280. As shown in FIG. 12 , the trade proposal screen 280 includes a trade image area 282, a remaining trade time display area 284, a trade partner display area 286, a confirmation button 288, and an end button 290.

[0112] The trade image area 282 is an area that displays an image that visualizes the trade of objects. The remaining trade time display area 284 is an area that displays the time remaining until the deadline for the first user to respond as to whether or not to accept the exchange. The trade deadline is set, for example, to a predetermined time from the trade acceptance date and time set in step S18. The predetermined time can be, for example, three days from the trade acceptance date and time.

[0113] Information about the user who proposed the trade is displayed in the trade partner display area 286. For example, the trade partner display area 286 displays the username of the second user, "User Y," along with the explanation, "Your reply has arrived."

[0114] Confirm button 288 is a button for confirming the details of the proposed trade. When the first user selects (clicks, taps, etc.) confirm button 288, the process proceeds to display trade confirmation screen 320, which allows the first user to confirm the details of the trade proposed by the second user. Exit button 290 is a button for returning from trade proposal screen 280 to the screen before transition. When the first user selects (clicks, taps, etc.) exit button 290, the process returns to the screen immediately before transitioning to trade proposal screen 280.

[0115] In step S22, the user terminal 104a of the first user performs a selection process to accept or reject the trade with the second object. Through the process in this step, the user terminal 104a used by the first user functions as a trade acceptance / rejection selection means.

[0116] In step S20, when the confirmation button 288 is selected, a trade confirmation screen 320 is displayed on the output unit 26 of the user terminal 104a. As shown in FIG. 16 , the trade confirmation screen 320 includes a trade partner display area 322, a second object display area 324, a first object display area 326, a remaining trade time display area 328, a trade reject button 330, a trade accept button 332, and an end button 334.

[0117] The trade partner display area 322 displays information about the second user. For example, the trade partner display area 322 displays the username of the second user, such as "User Y." The second object display area 324 is an area that displays information about the second object that the second user proposes to exchange. For example, the second object display area 324 displays an image of the second object.

[0118] Furthermore, when the object database is referenced and the type of the second object corresponds to a type of object that the first user does not currently own, a NIW mark 324a may be displayed in the second object display area 324. This allows the first user to easily understand by checking the trade confirmation screen 320 that the type of second object proposed for exchange by the second user is a type of object that the first user does not currently own.

[0119] The first object display area 326 is an area that displays information about the first object selected by the first user. In the first object display area 326, for example, an image of the first object is displayed.

[0120] The remaining trade time display area 328 is an area that displays the time remaining until the deadline for the first user to respond as to whether or not to accept the exchange.

[0121] The trade reject button 330 is a button that is selected when rejecting the exchange of an object. The first user can reject the exchange of an object by selecting (clicking, tapping, etc.) the trade reject button 330. When the trade reject button 330 is selected, the user terminal 104a transmits to the server 102 the trade ID and information indicating that the exchange of the object has been rejected.

[0122] The trade accept button 332 is a button that is selected when accepting the exchange of an object. The first user can accept the exchange of an object by selecting (clicking, tapping, etc.) the trade accept button 332. When the trade accept button 332 is selected, the user terminal 104a transmits to the server 102 the trade ID and information indicating that the exchange of the object has been accepted.

[0123] Note that when the trade acceptance button 332 is selected, a process may be performed to further confirm acceptance of the trade. For example, a process may be performed to display an explanation such as "Do you want to confirm the trade and exchange the objects between the two parties? (You cannot undo the trade before it is made)" and have the first user confirm the decision.

[0124] The exit button 334 is a button for returning to the screen prior to the transition from the trade confirmation screen 320. When the first user selects (clicks, taps, etc.) the exit button 334, the process returns to the screen immediately prior to the transition to the trade confirmation screen 320.

[0125] In step S24, a process of receiving an acceptance or refusal of the second object is performed. Through the process in this step, the server 102 functions as a second object acceptance / refusal receiving means. The server 102 receives the information transmitted from the user terminal 104a in step S22.

[0126] If the trade is rejected by the first user in step S22, server 102 receives information indicating that the trade has been rejected along with the trade ID. In this case, as shown in Figure 17, in the trade database, the "Acceptance or Rejection by Exchange Partner" field for the trade proposal stored in step S18 in association with the received trade ID is set to "Rejected." Furthermore, server 102 transmits information indicating that the trade has been rejected to user terminal 104b used by the second user.

[0127] Furthermore, if no acceptance or rejection response is received from the first user by the deadline for the first user to respond as to whether or not to accept the exchange, the trade will be deemed unsuccessful and will be handled in the same manner as if the trade were rejected.

[0128] If the trade is not successful, the server 102 performs a process to return the trade power and trade medals of the first user that were subtracted from the user database in step S12 as necessary for the exchange of the object. In this embodiment, the process returns 1 to the trade power associated with the first user, "User X," and returns 500 trade medals, which are necessary for the exchange of "Object B" with the attribute "normal" and rarity "R3."

[0129] Furthermore, if the trade is not successful, the server 102 performs a process to return the trade power and trade medals of the second user that were subtracted from the user database in step S18 as necessary for the exchange of the object. In this embodiment, the process returns 1 to the trade power associated with the second user, "User Y," and returns 500 trade medals necessary for the exchange of "Object C" with the attribute "normal" and rarity "R3."

[0130] If the trade is accepted by the second user in step S22, the server 102 sets the "Acceptance or Rejection by Exchange Partner" item for the trade proposal stored in the trade database in step S18 to "Accepted," as shown in Figure 18. Furthermore, the server 102 transmits information indicating that the trade has been accepted to the user terminal 104b used by the second user.

[0131] In step S26, the first user performs processing to acquire the second object associated with the exchange. Through the processing in this step, the user terminal 104a used by the first user functions as second object acquisition means.

[0132] In step S22, when the trade is accepted by the first user, the user terminal 104a displays an object exchange screen 340 on the output unit 26. As shown in FIG. 19, the object exchange screen 340 includes an explanation area 342, a sending object display area 344, and an end button 346.

[0133] Explanation area 342 is an area that explains the operations for sending the first object and acquiring the second object. For example, explanation area 342 displays an explanation such as "Swipe the object to send it to the other person."

[0134] The sending object display area 344 is an area where information about an object to be sent to the other party is displayed. In the sending object display area 344, for example, an image of a first object that the first user will exchange with the second user is displayed.

[0135] When the first user swipes the image of the object displayed in the sending object display area 344, a process of acquiring a second object is performed. When the first user swipes the image of the first object displayed in the sending object display area 344, the image of the first object is erased and an image of the second object to be exchanged is displayed on the object exchange screen 340 as shown in Fig. 20. In addition, information indicating that the first user has executed the process of acquiring the second object is transmitted from the user terminal 104a to the server 102.

[0136] The end button 346 is a button for returning to the screen before transition from the object exchange screen 340. When the first user selects (clicks, taps, etc.) the end button 346, the process returns to the screen immediately before transition to the object exchange screen 340.

[0137] In step S28, the second user performs a process of acquiring the first object associated with the exchange. Through the process in this step, the user terminal 104b used by the second user functions as a first object acquisition means.

[0138] In step S24, when server 102 transmits information indicating that the trade has been accepted by the first user to user terminal 104b used by the second user, user terminal 104b receives the information. When user terminal 104b receives the information indicating that the trade has been accepted by the first user, output unit 26 displays object exchange screen 340. Similar to FIG. 19 , object exchange screen 340 includes an explanation area 342, a sending object display area 344, and an end button 346.

[0139] The explanation area 342 is an area that explains the operations for sending the second object and acquiring the first object. For example, the explanation area 342 displays an explanation such as "Swipe the object to send it to the other party." The sending object display area 344 displays, for example, an image of the second object that the second user will exchange with the first user. When the second user swipes the image of the object displayed in the sending object display area 344, a process for acquiring the first object is performed. When the second user swipes the image of the second object displayed in the sending object display area 344, the image of the second object is erased, and an image of the first object to be exchanged is displayed on the object exchange screen 340. In addition, information indicating that the second user has executed the process for acquiring the first object is transmitted from the user terminal 104b to the server 102.

[0140] In step S30, post-processing is performed in association with the exchange of the first object and the second object. By the processing in this step, the server 102 functions as a post-processing means.

[0141] In step S26, when the first user executes the process of acquiring the second object, server 102 receives information indicating that the first user has executed the process of acquiring the second object. Server 102 decreases the number of owned second objects associated with the user ID of the second user in the object database by one. Server 102 also increases the number of owned object types associated with the user ID of the first user and corresponding to the second object acquired from the second user by one in the object database.

[0142] In step S28, when the second user executes the process of acquiring the first object, server 102 receives information indicating that the second user has executed the process of acquiring the first object. Server 102 decreases the number of owned first objects associated with the user ID of the first user in the object database by one. Server 102 also increases the number of owned objects of the type corresponding to the first object acquired from the first user, associated with the user ID of the second user, in the object database by one.

[0143] It should be noted that the process of acquiring the second object by the first user in step S26 and the process of acquiring the first object by the second user in step S28 do not need to be performed simultaneously.

[0144] Furthermore, when an object exchange is successful, a reward may be given to the user involved in the exchange. The reward is not particularly limited, and for example, some kind of item may be given to the user who exchanged the object. The item may be, for example, an item that can be used in an electronic game that uses the object. Furthermore, for example, a trade medal may be given to the user who exchanged the object. Furthermore, the reward may be an object related to the object sent or the object acquired in the exchange. For example, an evolved or evolved version of the object, a different design of the same object, an object that is compatible with the object, etc. are conceivable.

[0145] By providing rewards in this way, motivation for exchanging objects can be increased.

[0146] While the preferred embodiments of the present invention have been described above, the present invention is not limited to the specific embodiments, and includes the inventions set forth in the claims and their equivalents. Furthermore, the device configurations described in the above embodiments and modifications can be combined as appropriate as long as no technical contradiction occurs.

[0147] [Configuration of the invention] [Configuration 1] Computer, means for acquiring a proposal for an object exchange with a second user different from the first user, the proposal including a setting of a first object to be exchanged from an object owned by the first user; means for obtaining an acceptance or rejection of the proposal by the second user; means for obtaining, if the proposal is accepted, a proposal for an object exchange with the first user, including a setting of a second object to be exchanged from an object owned by the second user; means for acquiring whether or not the exchange of the first object and the second object by the first user has been successful; means for allowing the first user to own the second object and allowing the second user to own the first object when the exchange is successful; and make it work, A trading program characterized in that a first parameter that changes over time and is associated with the first user is used when proposing an object exchange with the second user. [Configuration 2] The trading program according to configuration 1, A trading program characterized in that when a proposal to exchange an object with the second user is made, a second parameter associated with the first user is used depending on the first object. [Configuration 3] The trading program according to configuration 2, A trading program characterized in that a second parameter associated with the first user is used depending on the rarity of the first object. [Configuration 4] The trading program according to any one of configurations 1 to 3, A trading program characterized in that, if the exchange is not successful, the first parameter and the second parameter are returned in association with the first user. [Configuration 5] The trading program according to any one of configurations 1 to 4, A trading program characterized in that, if the exchange is successful, a reward is given to at least one of the first user and the second user. [Configuration 6] means for acquiring a proposal for an object exchange with a second user different from the first user, the proposal including a setting of a first object to be exchanged from an object owned by the first user; means for obtaining an acceptance or rejection of the proposal by the second user; means for obtaining, if the proposal is accepted, a proposal for an object exchange with the first user, including a setting of a second object to be exchanged from an object owned by the second user; means for acquiring whether or not the exchange of the first object and the second object by the first user has been successful; means for allowing the first user to own the second object and allowing the second user to own the first object when the exchange is successful; Equipped with A trading system characterized in that a first parameter that changes over time and is associated with the first user is used when a proposal to exchange an object with the second user is made. [Configuration 7] On the computer, obtaining a proposal for an object exchange with a second user different from the first user, the proposal including a setting of a first object to be exchanged from an object owned by the first user; obtaining an acceptance or rejection of the proposal by the second user; If the proposal is accepted, obtaining a proposal for an object exchange with the first user from an object owned by the second user, the proposal including a setting of a second object to be exchanged; obtaining whether or not the exchange of the first object and the second object by the first user has been successful; If the exchange is successful, allowing the first user to own the second object and allowing the second user to own the first object; Execute A trading method characterized in that a first parameter that changes over time and is associated with the first user is used when proposing an object exchange with the second user. [Explanation of symbols]

[0148] 10 Processing unit, 12 Memory unit, 14 Input unit, 16 Output unit, 18 Communication unit, 20 Processing unit, 22 Memory unit, 24 Input unit, 26 Output unit, 28 Communication unit, 100 Object trading system, 102 Server, 104 (104a, 104b) User terminal, 108 Information and communication network, 210 User selection screen, 212 User selection unit, 212a User icon, 212b User name display unit, 212c Trade selection unit, 212d Trade selection unit, 220 Object selection screen, 222 Object selection unit, 222a Remaining object number display area, 224 Description area, 226 Resource display area, 228 Search input area, 230 Confirm button, 232 Back button, 234 Object selection unit, 236 Object selection unit, 236a Required resource display unit, 280 Trade proposal screen, 282 Trade image area, 284 remaining trade time display area, 286 trade partner display area, 288 confirmation button, 290 exit button, 300 trade confirmation screen, 302 trade partner display area, 304 object display area, 304a NIW mark, 306 remaining trade time display area, 308 trade reject button, 310 trade accept button, 312 exit button, 320 trade confirmation screen, 322 trade partner display area, 324a NIW mark, 328 remaining trade time display area, 330 trade reject button, 332 trade accept button, 334 exit button, 340 object exchange screen, 342 description area, 344 sending object display area, 346 exit button.

Claims

1. Computer, means for acquiring a proposal for an object exchange with a second user different from the first user, the proposal including a setting of a first object to be exchanged from an object owned by the first user; means for obtaining an acceptance or rejection of the proposal by the second user; means for acquiring, if the proposal is accepted, a proposal for an object exchange with the first user, including a setting of a second object to be exchanged from an object owned by the second user; means for acquiring whether or not the exchange of the first object and the second object by the first user has been successful; means for allowing the first user to own the second object and allowing the second user to own the first object when the exchange is successful; and make it work, A trading program characterized in that a first parameter that changes over time and is associated with the first user is used when proposing an object exchange with the second user.

2. 2. The trading program of claim 1, A trading program characterized in that when a proposal to exchange an object with the second user is made, a second parameter associated with the first user is used depending on the first object.

3. 3. The trading program according to claim 2, A trading program characterized in that a second parameter associated with the first user is used depending on the rarity of the first object.

4. The trading program according to any one of claims 1 to 3, A trading program characterized in that, if the exchange is not successful, the first parameter and the second parameter are returned in association with the first user.

5. The trading program according to any one of claims 1 to 4, A trading program characterized in that, if the exchange is successful, a reward is given to at least one of the first user and the second user.

6. means for acquiring a proposal for an object exchange with a second user different from the first user, the proposal including a setting of a first object to be exchanged from an object owned by the first user; means for obtaining an acceptance or rejection of the proposal by the second user; means for acquiring, if the proposal is accepted, a proposal for an object exchange with the first user, including a setting of a second object to be exchanged from an object owned by the second user; means for acquiring whether or not the exchange of the first object and the second object by the first user has been successful; means for allowing the first user to own the second object and allowing the second user to own the first object when the exchange is successful; Equipped with A trading system characterized in that a first parameter that changes over time and is associated with the first user is used when a proposal to exchange an object with the second user is made.

7. On the computer, obtaining a proposal for an object exchange with a second user different from the first user, the proposal including a setting of a first object to be exchanged from an object owned by the first user; obtaining an acceptance or rejection of the proposal by the second user; If the proposal is accepted, obtaining a proposal for an object exchange with the first user from an object owned by the second user, the proposal including a setting of a second object to be exchanged; obtaining whether or not the exchange of the first object and the second object by the first user has been successful; If the exchange is successful, allowing the first user to own the second object and allowing the second user to own the first object; Execute A trading method characterized in that a first parameter that changes over time and is associated with the first user is used when a proposal to exchange an object with the second user is made.

Images