JP2024054342A - OBJECT PROVIDING SYSTEM, OBJECT UTILIZING SYSTEM, INFORMATION PROCESSING APPARATUS, PROGRAM AND OBJECT PROVIDING METHOD - Google Patents

Abstract

[Problem] To provide a system that enhances the interest of users. [Means for solving the problem] An object providing system includes a payment means for making a payment for a first object that is an intangible object and can be used for a predetermined service, and a second object that is a tangible object, a first object providing means for providing the first object to a user on condition that the payment of the price is completed, an association means for associating the first object with the user's user identifier by using the first object, and a delivery procedure means for executing a delivery procedure for delivering the second object to the user on condition that the payment of the price is completed. The delivery procedure means does not execute the delivery procedure for the second object to the user on condition that the association between the user's user identifier and the first object is released. [Selected Figure] Figure 2

Description

The present invention relates to an object provision system, an object usage system, an information processing device, a program, and an object provision method.

Conventionally, there is a technique for reading character information from a barcode or the like printed on a tangible game card using a reader or the like, and playing a game using the read character information (for example, Patent Document 1).

Japanese Patent Application Laid-Open No. 06-154421

However, intangible objects such as digital data and tangible objects such as goods have different utility values, and if these objects could be provided to users, it would be possible to provide a system that is more interesting to users.

The present invention therefore aims to provide an object provision system, an object usage system, an information processing device, a program, and an object provision method that improve the user's interest.

One aspect of the present invention is an object provision system that includes a payment means for making a payment settlement for a first object that is an intangible object and can be used in a specified service, and a second object that is a tangible object, a first object provision means for providing the first object to a user on condition that the payment of the price is completed, and a delivery procedure means for executing a delivery procedure for delivering the second object to the user on condition that the payment of the price is completed.

One aspect of the present invention is an object usage system that includes a payment means for making a payment for a pair of a first object, which is an intangible object and can be used in a plurality of services, and a second object, which is a tangible object; a first object providing means for providing the first object to a user on condition that the payment of the price is completed; a delivery procedure means for executing a delivery procedure for delivering the second object to the user on condition that the payment of the price is completed; an association means for associating the first object with a user identifier that is used in common among a plurality of services and for identifying the user in the plurality of services on condition that the payment of the price is completed; and a plurality of service execution means for executing a service using the first object on condition that the user identifier is authenticated.

One aspect of the present invention is an information processing device that includes a payment means for making a payment settlement for a first object that is an intangible object and that can be used in a specified service, and a second object that is a tangible object, a first object providing means for providing the first object to a user on condition that the payment of the price is completed, and a delivery procedure means for executing a delivery procedure for delivering the second object to the user on condition that the payment of the price is completed.

One aspect of the present invention is a program that causes a computer to function as a payment means for making a payment for a first object that is an intangible object and can be used in a specified service, and a second object that is a tangible object, a first object providing means for providing the first object to a user on condition that the payment of the price is completed, and a delivery procedure means for executing a delivery procedure for delivering the second object to the user on condition that the payment of the price is completed.

One aspect of the present invention is a method of providing objects, in which a computer executes control to effect a payment settlement for a first object, which is an intangible object and can be used in a specified service, and a second object, which is a tangible object, and executes a delivery procedure to provide the first object to a user on condition that the payment settlement for the price is completed, and to deliver the second object to the user on condition that the payment settlement for the price is completed.

The present invention provides technology that enhances the interest of users.

FIG. 1 is a diagram for explaining the first embodiment. FIG. 2 is a diagram showing an example of the overall configuration of an object providing system according to the first embodiment. FIG. 3 is a block diagram showing an example of the functional configuration of the common user ID management server 1. As shown in FIG. FIG. 4 is a diagram showing an example of the common user ID management database 120. As shown in FIG. FIG. 5 is a block diagram showing an example of the functional configuration of the object sales server 2. As shown in FIG. FIG. 6 is a diagram showing an example of the sales object database 220. As shown in FIG. FIG. 7 is a block diagram showing an example of the functional configuration of the service providing server 3. As shown in FIG. FIG. 8 is a diagram showing an example of an object database 320 used in a game. FIG. 9 is a block diagram showing an example of the functional configuration of the terminal 4. As shown in FIG. FIG. 10 is a sequence diagram of the operation of the first embodiment. FIG. 11 is a flowchart of the common user ID registration process (Step 1). FIG. 12 is a flowchart of the object sales process (Step 2). FIG. 13 shows an example of transition of the screen displayed on the terminal 4. In FIG. FIG. 14 is a flowchart of the object registration process (Step 3). FIG. 15 is an example of a login screen for a game. FIG. 16 is a flow chart showing the service execution process (Step 4) and the start of the object management process (Step 5). FIG. 17 is a flowchart of the object list process (Step 6). FIG. 18 is a diagram showing an example of the object list screen. FIG. 19 is a diagram for explaining the second embodiment. FIG. 20 is a diagram showing an example of the overall configuration of an object trading system according to the second embodiment. FIG. 21 is a block diagram showing an example of the functional configuration of the transaction server 5. FIG. 22 is a diagram showing an example of the transaction management database 510. FIG. 23 is a sequence diagram of the operation of the second embodiment. FIG. 24 is a flow chart of the transaction object registration process (Step 10) and the transactionable owned object list process (Step 11). FIG. 25 is a diagram showing an example of a screen displayed on the terminal 4a. FIG. 26 is a flowchart of the transaction process (Step 12). FIG. 27 is an example of a transaction screen displayed on the terminal 4b. FIG. 28 shows an example of a negotiation offer screen displayed on the terminal 4a. FIG. 29 is a flowchart of the transaction authentication process (Step 13). FIG. 30 is a diagram showing an example of the common user ID management table 120 after the transaction. FIG. 31 is a diagram for explaining a first modified example of the second embodiment. FIG. 32 is a diagram showing an example of a transaction conditions screen in the third modification of the second embodiment.

First Embodiment
A first embodiment of the present invention will be described.
With the recent digitalization, attention has been focused on virtual game cards used in game applications, virtual objects that appear in a three-dimensional virtual space constructed online called the metaverse, etc. Hereinafter, such intangible digital data will be referred to as a first object.

On the other hand, game cards, trading cards, figurines, plastic models, etc. associated with characters from anime and the like have traditionally been provided. These items are tangible objects with substance that can be realistically recognized by the user. These tangible items will be referred to as second objects below.

While the first object and the second object differ in that one is intangible and the other is tangible, they have in common the fact that they can be associated (embodied) with characters, etc. Thus, the first object and the second object can be associated with the same character or with characters related to each other. Here, characters related to each other refer to, for example, the relationship between the first object and the second object as characters appearing in a certain story.

If a first object and a second object associated with such a character could be paired (set) and provided to the user, a new form of enjoyment could be provided to the user. This is because the first object associated with the user's favorite character is an intangible object, and therefore various services, such as application games using this first object and virtual spaces such as the metaverse, could be provided to the user. Furthermore, the second object associated with the user's favorite character is a tangible object, and therefore the user's sense of ownership can be satisfied in the real world. In other words, it is possible to provide the user with double value.

Specifically, as shown in FIG. 1, there is a virtual game card (first object) X1 used in a game application and a game card (second object) X2 as an item, and game card X1 and game card X2 correspond to the same character. For example, game card X1 and game card X2 have the same picture. A user can purchase game card X1 and game card X2 as a set.

The service provider provides the game card X1 as digital data to the user who purchased the set. At this time, the user and the game card X1 are associated with each other so that the user can use the game card X1 in multiple services. For example, the game card X1 is associated with a common identifier (hereinafter, may be referred to as a common user ID) that can identify the user in each of multiple services. In this way, the game card X1 can be identified as the user's property, and the user can use the game card X1 in multiple services. For example, the user can use the game card X1 as a game element in a game application, or as a display in the metaverse.

The service provider also delivers the game card X2 as a real item to the user who purchased the set. Here, delivery includes shipping the game card X2 to the user and handing it over to the user at the store. This allows the user to satisfy their desire to own a physical collection, etc.

In the above specific example, the first object and the second object are the same character and have the same picture, but this is not limited to the above. For example, the first object and the second object may be the same character, but the first object may be a figurine of that character and the second object may be a plastic model of that character.

As mentioned above,
A first object and a second object associated with the character are provided to the user as a set,
Associating at least the first object with a common user ID that identifies the user in a plurality of services;
This makes it possible to provide the user with various services that utilize the first object, and the second object allows the user to feel a sense of ownership in the real world.
Detailed embodiments will be described below.

Overall Configuration of First Embodiment
The object providing system according to this embodiment will be described.
Fig. 2 is a diagram showing an example of the overall configuration of the object provision system in the first embodiment. As shown in Fig. 2, the object provision system is configured to include a common user ID management server 1, an object sales server 2, a service provision server 3, and a terminal 4. The common user ID management server 1, the object sales server 2, the service provision server 3, and the terminal 4 can be connected to a network N and can communicate with each other.

The network N refers to a communication path that allows data communication. In other words, the network N includes a LAN using a dedicated line (dedicated cable) for direct connection or Ethernet (registered trademark) and other communication networks such as telephone communication networks, cable networks, and the Internet, regardless of whether the communication method is wired or wireless.

The common user ID management server 1, the object sales server 2, and the service providing server 3 are a server system that includes one or more server devices, storage devices, etc. Furthermore, the common user ID management server 1, the object sales server 2, and the service providing server 3 do not need to be installed separately, and may be mixed with other servers in a cloud system.

The common user ID management server 1 is a server that manages common user IDs that are used in common in multiple services provided to users. The common user ID is an identifier (identification information) that uniquely identifies a user who uses a service.

The object sales server 2 is a server that sells or provides objects to users.

The service providing server 3 is a server that provides a service using the first object to a user. The service providing server 3 may execute multiple services collectively, or may exist for each service.

The terminal 4 is an information processing device (computer) capable of executing applications, web browsers, etc., and is connected to the network N via a wireless communication base station or the like, and can perform data communication with the common user ID management server 1, the object sales server 2, and the service provision server 3. The terminal 4 is, for example, a smartphone, a mobile phone, a portable game device, a stationary home game device, an arcade game device, a personal computer, a tablet computer, a controller for a stationary home game device, etc. Basically, there are multiple terminals 4, and each is operated by a different user.

<Configurations of the First Embodiment>
The common user ID management server 1 will now be described.

As shown in FIG. 3, the device includes a processing unit 10, a communication unit 11, and a storage unit 12.
The processing unit 10 comprehensively controls the operation of the common user ID management server 1 based on the programs and data stored in the memory unit 12. The functions of the processing unit 10 can be realized by electronic components such as a microprocessor such as a CPU or GPU, an ASIC, an IC memory, etc. The processing unit 10 includes a calculation unit 100, an image generation unit 101, and a communication control unit 102 as main functional units.

The calculation unit 100 includes a common user ID management unit 110 and an owned object presentation unit 111.

The common user ID management unit 110 manages common user IDs using a common user ID management database 120 stored in the memory unit 12. The common user ID is an identifier that is used in common in multiple services provided to users, and is used to identify and authenticate each user.

Figure 4 shows an example of the common user ID management database 120. The common user ID management database 120 includes a common user ID database 121 and a player object management database 122.

The common user ID database 121 is a database that manages the common user IDs of users. One record in the common user ID database 121 includes a field for the user's common user ID, a field for the user's username, a field for the user's password, a field for the user's address, and a field for the currency (coins) that can be used within the services owned by the user.

The player object management database 122 is a table prepared for each common user ID, and is a table that manages objects available to or owned by the user of the common user ID. Each table includes a field for the object name of the object owned by the user, an object ID that identifies the object, a field for the name of the service for which the object is available, a field for whether the object can be used in that service, a field for the scheduled delivery procedure date for the object, and a field for the delivery completion date for the object.

The common user ID management unit 110 uses the common user ID management database 120 to identify and authenticate users and provide various information upon request from the object sales server 2 or the service provision server 3. The common user ID management unit 110 also updates the common user ID management database 120 using information provided by the object sales server 2 or the service provision server 3.

The owned object presentation unit 111 responds to a request from the terminal 4 and presents a list of objects owned by the user.

The image generation unit 101 generates one screen per frame time (e.g., 1/60 seconds) based on the processing results of the calculation unit 100, and outputs an image signal of the generated screen. The functions of the image generation unit 101 can be realized by, for example, a processor such as a GPU or digital signal processor (DSP), a video signal IC, a program such as a video codec, an IC memory for drawing frames such as a frame buffer, an IC memory used for expanding texture data, etc.

The communication control unit 102 performs communication connection and data processing for data communication between the object sales server, the service providing server 3, and the terminal 4.

The communication unit 11 connects to a communication line to realize communication. The functions of the communication unit 11 can be realized, for example, by a wireless communication device, a modem, a TA (terminal adapter), a jack for a wired communication cable, a control circuit, etc.

The storage unit 12 is realized by, for example, a RAM, a ROM, an IC memory such as a flash memory, a magnetic disk such as a hard disk, or an optical disk such as a CD-ROM or a DVD, and stores a system program and a function program. The system program is a program for realizing the basic functions of a computer. The function program is a program for causing the calculation unit 100 to function as a common user ID management unit 110 and an owned object presentation unit 111. In this embodiment, the storage unit 12 also stores a common user ID management database 120.

The object sales server 2 will now be described. FIG.
As shown in FIG. 5, the device includes a processing unit 20, a communication unit 21, and a storage unit 22.

The processing unit 20 performs overall control of the operation of the object sales server 2 based on the programs and data stored in the memory unit 22. The functions of the processing unit 20 can be realized by electronic components such as a microprocessor such as a CPU or GPU, an ASIC, and an IC memory. The processing unit 20 has, as its main functional units, a calculation unit 200, an image generation unit 201, and a communication control unit 202.

The calculation unit 200 includes an object sales unit 210, a settlement unit 211, a first object provision unit 212, and a second object delivery procedure unit 213.

The object selling unit 210 reads out information on objects available for sale from the selling object database 220, and presents an object purchase screen to the terminal 4. In addition, the object selling unit 210 presents a selected object purchase screen to the terminal 4 in response to a selection of an object to be purchased from the terminal 4, and presents a selected object purchase completion screen to the terminal 4 after the settlement is completed. In this embodiment, the object to be sold means a set of a first object which is an intangible object and a second object which is a tangible object. The first object and the second object which is a tangible object are objects corresponding to the same character. For example, the first object is a game card of digital data usable in an application game, and the second object is a real card having the same design as the game card of digital data.
The object sales unit 210 communicates with the terminal 4 mainly by HTTP, and transmits contents of various screens and the like (HTML/XHTML/XML, documents, images, etc.).

The settlement unit 211 settles the payment of the price of the object selected by the user. Here, the price of the object is the price of a set of a first object, which is an intangible object, and a second object, which is a tangible object. In this embodiment, the payment of the price is settled using in-service currency, but electronic payment such as credit card is also possible. The settlement unit 111 transmits payment information regarding the object that the user is about to purchase to the common user ID management server 1. The payment information includes the user's common user ID, password, and information on the price of the object. When the settlement unit 211 receives payment completion information from the common user ID management server 1, it notifies the terminal 4 that the payment has been completed. The payment completion information includes authentication of the user, a notification of the completion of subtraction of the price of the object from the currency (coins) owned by the user, and the user's address (delivery destination).

After the payment unit 211 makes a payment, the first object providing unit 212 provides the first object of the objects to the terminal 4. The method of provision includes, for example, not only a method of providing digital data of the first object for registration in a game application installed on the terminal 4, but also a method of providing usage information for making the first object available to the user, rather than the digital data of the first object itself.

The second object delivery procedure unit 213 manages the delivery procedures for the second object, which is a tangible object among the objects. Specifically, the second object delivery procedure unit 213 creates a delivery slip for delivery to the user's address (delivery destination) so that the second object can be delivered to the user on the scheduled delivery date for each user in the player object management database 122, and manages the procedures required for delivery.

The image generation unit 201 generates one screen per frame time (e.g., 1/60 seconds) based on the processing results of the calculation unit 200, and outputs an image signal of the generated screen. The function of the image generation unit 201 can be realized by, for example, a processor such as a GPU or digital signal processor (DSP), a video signal IC, a program such as a video codec, an IC memory for drawing frames such as a frame buffer, an IC memory used for expanding texture data, etc.

The communication control unit 202 performs communication connection and data processing for data communication between the common user ID management server 1 and the terminal 4.

The communication unit 21 connects to a communication line to realize communication. The functions of the communication unit 11 can be realized, for example, by a wireless communication device, a modem, a TA (terminal adapter), a jack for a wired communication cable, a control circuit, etc.

The storage unit 22 is realized by, for example, a RAM, a ROM, an IC memory such as a flash memory, a magnetic disk such as a hard disk, or an optical disk such as a CD-ROM or a DVD, and stores a system program and a function program. The system program is a program for realizing the basic functions of a computer. The function program is a program for causing the calculation unit 200 to function as an object sales unit 210, a settlement unit 211, a first object provision unit 212, and a second object delivery procedure unit 213. In this embodiment, the storage unit 22 also stores a sales object database 220.

Figure 6 is a diagram showing an example of the sales object database 220. One record in the sales object database 220 includes a field for the name of the object, a field for an object ID that identifies the object, a field for the sales period of the object, a field for available services for the object, a field for information regarding the delivery of the object, and a field for the price of the object.

The contents of the first record in the sales object database 220 in FIG. 6 will be specifically described as follows:
・The application game card X1 (first object) and the real card X2 (second object) corresponding to the character X of the "X Series" are sold as a set.
- The sales period for the set is from February 10, 2022 to March 10, 2022.
- The price of the set is 100 coins,
The application game card X1 (first object) can be used in the game "X Series";
The application game card X1 (first object) was delivered (provided) to the user on March 1, 2022, and the real card X2 (second object) is scheduled to be delivered to the user on March 20, 2022.
It is.

The service providing server 3 will now be described. FIG. 7 is a block diagram showing an example of the functional configuration of the service providing server 3. In the first embodiment, the services using the objects executed by the service providing server 3 are a card game using the first object and a metaverse using the first object.

As shown in FIG. 7, the device includes a processing unit 30, a communication unit 31, and a storage unit 32.
The processing unit 30 comprehensively controls the operation of the service providing server 3 based on the programs and data stored in the memory unit 32. The functions of the processing unit 30 can be realized by electronic components such as a microprocessor such as a CPU or a GPU, an ASIC, and an IC memory. The processing unit 30 includes, as main functional units, a calculation unit 300, an image generation unit 301, and a communication control unit 302.

The calculation unit 300 includes a game execution unit 310 and a metaverse execution unit 311 .
The game execution unit 310 executes a game using the first object in response to a service execution request from the terminal 4. The service execution request from the terminal 4 includes the common user ID and password of the user. The game execution unit 310 transmits an available object request including the common user ID and password included in the service execution request to the common user ID management server 1. The game execution unit 310 also receives available object information including the common user ID of the user and the object ID of a first object available to the user from the common user ID management server 1. The game execution unit 310 then identifies an object (character) to be made to appear in the game from the acquired object ID, and enables the use of the first object (character) in the game executed on the terminal 4.

The metaverse execution unit 311 executes a metaverse service using the first object in response to a service execution request from the terminal 4. The metaverse execution unit 311 sends an available object request, including the common user ID and password included in the service execution request, to the common user ID management server 1. It also receives available object information, including the user's common user ID and the object ID of a first object available to that user, from the common user ID management server 1. The metaverse execution unit 311 then identifies an object (character) to be made to appear in the metaverse from the acquired object ID, and enables the use of the first object (character) in the metaverse service executed on the terminal 4.

The image generation unit 301 generates one screen per frame time (e.g., 1/60 seconds) based on the processing results of the calculation unit 300, and outputs an image signal for the generated screen. The functions of the image generation unit 201 can be realized by, for example, a processor such as a GPU or digital signal processor (DSP), a video signal IC, a program such as a video codec, an IC memory for drawing frames such as a frame buffer, an IC memory used for expanding texture data, etc.

The communication control unit 302 performs communication connection and data processing for data communication between the common user ID management server 1 and the terminal 4.

The communication unit 31 connects to a communication line to realize communication. The functions of the communication unit 31 can be realized, for example, by a wireless communication device, a modem, a TA (terminal adapter), a jack for a wired communication cable, a control circuit, etc.

The storage unit 32 is realized by, for example, a RAM, a ROM, an IC memory such as a flash memory, a magnetic disk such as a hard disk, or an optical disk such as a CD-ROM or a DVD, and stores system programs and function programs. The system programs are programs for realizing the basic functions of a computer. The function programs are programs for causing the calculation unit 300 to function as a game execution unit 310 and a metaverse execution unit 311.

In addition, in this embodiment, the storage unit 32 stores various databases related to first objects (characters) for executing the game and the metaverse. FIG. 8 is a diagram showing an example of an object database 320 used in the game. One record in the object database 320 includes a field for an object ID, a field for image data of the object displayed in the game, a field for character information of the object, and a field for user ownership information indicating whether the user owns the object. A similar database is also stored for the metaverse service.

The terminal 4 will now be described. FIG. 9 is a block diagram showing an example of the functional configuration of the terminal 4.
As shown in FIG. 9 , the terminal 4 includes a processing unit 40 , an operation input unit 41 , a display unit 42 , a sound output unit 44 , a communication unit 44 , and a storage unit 45 .

The processing unit 40 performs overall control of the operation of the terminal 4 based on the programs and data stored in the memory unit 45, various input signals from the operation input unit 41, etc. The functions of the processing unit 40 can be realized by electronic components such as a microprocessor such as a CPU or GPU, an ASIC, and an IC memory. The processing unit 40 includes, as its main functional units, a calculation unit 400, an image generation unit 401, a sound generation unit 402, and a communication control unit 403.

The calculation unit 400 executes various processes for implementing the service of this embodiment, and outputs the results of the processes to the image generation unit 401 , the sound generation unit 402 , or the communication control unit 403 .
The calculation unit 400 includes a browser execution unit 410 and a service execution unit 411 .

The browser execution unit 410 communicates with the server mainly via HTTP, acquires content, and arranges and draws text and images based on the results of syntax analysis of the acquired content according to its type (HTML/XHTML/XML, document, image, etc.). In addition, the browser execution unit 410 can display and execute Flash applications and Java applets if plug-ins compatible with these applications are available.

The service execution unit 411 is a unit that executes the services to be provided. In this embodiment, the service execution unit 411 executes each service by an application that executes a game using objects and a metaverse.

The image generation unit 401 generates one game screen per frame time (e.g., 1/60th of a second) based on the processing results of the calculation unit 400, and outputs an image signal of the generated game screen to the image display unit 103. The functions of the image generation unit 401 can be realized by, for example, a processor such as a GPU or digital signal processor (DSP), a video signal IC, a program such as a video codec, an IC memory for drawing frames such as a frame buffer, an IC memory used for expanding texture data, etc.

The sound generation unit 402 generates sound signals such as game-related sound effects and background music, audio information for operation support information, and various operation sounds based on the processing results of the calculation unit 400, and outputs them to the sound output unit 43. The functions of the sound generation unit 401 can be realized, for example, by a processor such as a digital signal processor (DSP) or a voice synthesis IC, or an audio codec capable of playing audio files.

The communication control unit 403 handles communication connections and data processing for data communication with each server.

The operation input unit 41 allows the player to input various operations related to the service, and outputs an operation input signal corresponding to the operation input to the processing unit 40. The functions of the operation input unit 40 can be realized by elements that are directly operated by the player's fingers, such as a touch pad, a home button, a button switch, a joystick, or a trackball, as well as elements that detect movement or posture, such as an acceleration sensor, an angular velocity sensor, a tilt sensor, or a geomagnetic sensor.

The display unit 42 displays various game screens based on the image signals input from the image generation unit 401. The functions of the display unit 42 can be realized by a display device such as a flat panel display such as a liquid crystal display, a cathode ray tube (CRT), a projector, or a head-mounted display.

The sound output unit 43 outputs sound effects and the like related to the game based on the sound signal input from the sound generation unit 402. For example, the sound output unit 43 is a speaker.

The communication unit 44 connects to a communication line to realize communication. The functions of the communication unit 35 can be realized, for example, by a wireless communication device, a modem, a TA (terminal adapter), a jack for a wired communication cable, a control circuit, etc.

The storage unit 45 stores in advance or temporarily stores each time a process is performed system programs, service applications, and data used during execution of service applications for operating the terminal 4 and realizing various functions of the terminal 4. The storage unit 45 can be realized, for example, by RAM, ROM, a solid state drive using IC memory such as flash memory, a magnetic disk such as a hard disk, or an optical disk such as a CD-ROM or DVD. The system programs are programs for realizing the basic functions of the terminal 4 as a computer. The service applications are, for example, a web browser that causes the calculation unit 400 to function as the browser execution unit 410, a game application that causes the calculation unit 400 to function as the service execution unit 411, a metaverse application, and the like. The storage unit 45 also stores databases necessary for executing services.

<Operation of the First Embodiment>
The operation of the first embodiment will be described with reference to Fig. 10, which is a sequence diagram of the operation of the first embodiment.

First, to obtain a common user ID, the browser execution unit 410 of the terminal 4 sends a common user ID acquisition request to the common user ID management server 1. The common user ID acquisition request includes the user name, the desired password, and the user's address.

Upon receiving the common user ID acquisition request, the common user ID management server 1 performs a common user ID registration process (Step 1). Figure 11 is a flowchart of the common user ID registration process (Step 1).

When the common user ID management server 1 receives a common user ID acquisition request (Step 100), the common user ID management unit 110 determines whether the user name and desired password included in the common user ID acquisition request can be registered (Step 101). If registration is possible, the common user ID management unit 110 assigns the common user ID to the user (Step 102) and registers the common user ID, user name, password, and address in the common user ID management database 121 (Step 103). Then, the common user ID management unit 110 transmits a common user ID registration completion screen on which the common user ID is described to the terminal 4 (Step 105). On the other hand, if the user name and desired password cannot be registered (Step 101), the common user ID management unit 110 transmits a screen requesting a different user name and password to the terminal 4 (Step 105).

By performing the above operations, the user can obtain a common user ID to be used in multiple services. In addition, the user can use the obtained common user ID to obtain currency (coins) to be used in various services. The currency (coins) is obtained by paying for it through electronic payment such as a credit card. The currency (coins) obtained by the user is entered in the currency (coins) field of the user's record in the common user ID management database 121 by the common user ID management unit 110.

Next, the purchase of an object by a user will be described.
To purchase an object, the browser execution unit 410 of the terminal 4 transmits an object purchase screen request to the object sales server 2. The object sales server 2 that receives the object purchase screen request performs object sales processing (Step 2) with the common user ID management server 1. Fig. 12 is a flowchart of the object sales processing (Step 2).

When the object sales server 2 receives an object purchase screen request (Step 200), the object sales unit 210 obtains information on objects available for sale from the sales object database 220 (Step 201) and transmits the object purchase screen to the terminal 4 (Step 202).

Figure 13 is a diagram showing an example of the transition of a screen for purchasing an object displayed on the terminal 4. The object purchase screen shown in Figure 13 displays a list of objects including the name of the object, the sales period of the object, the available services for the object, information on the delivery of the object, and the price of the object, which are read from the sales object database 220 shown in Figure 5. As an example, for character X of the "X series", an application game card X1 (first object) and a real card X2 (second object) are sold as a set, the sales period is from February 10, 2022 to March 10, 2022, and the price is 100 coins. In addition, the application game card X1 (first object) and the real card X2 (second object) are cards associated with character X and include the same image.

When the object sales unit 210 receives a request for a selected object purchase screen selected by the user from the list of object purchase screens from the terminal 4 (Step 203), it transmits the selected object purchase screen (including the selected object ID) to the terminal 4 (Step 204). The selected object purchase screen shown in FIG. 13 is a selected object purchase screen when the user selects the object "X series character X" on the object purchase screen. The selected object purchase screen includes the application game card X1, which is the first object (intangible object) that is a set sale of the object "X series character X", and the real card X2, which is the second object (tangible object), the start date of use of the application game card X1 (intangible object), the scheduled delivery date of the real card X2 (tangible object), and the price of the "X series character X" set (card X1 and real card X2). The selected object purchase screen also includes an input field for the user's common user ID and password, and a purchase button. Additionally, the selected object purchase screen is sent with the object ID "X101" of the first object in the "X series" object and the object ID "X102" of the second object in the "X series" object.

To purchase the object "X Series Character X," the user enters the user's common user ID "10001" and password "25002" into the input fields of the selected object purchase screen displayed on terminal 4, and presses the purchase button. Terminal 4 then sends a selected object purchase request to the object sales server 2. The selected object purchase request includes the user's common user ID "10001" and password "25002," the object ID "X101" of the first object, and the object ID "X102" of the second object.

When the payment unit 211 receives the selected object purchase request (Step 205), it acquires the user's common user ID and password, the object ID of the first object, and the object ID of the second object from the selected object purchase request, and transmits payment information to the common user ID management server 1 (Step 206). The payment information includes the user's common user ID and password, the object ID of the first object and the name of the available service, the object ID of the second object and the scheduled delivery date, and the price of the set of the first object and the second object. In the example of FIG. 10, the payment information includes the user's common user ID "10001" and password "25002", the object ID "X101" of the first object, the available service "Game "X Series"", the object ID "X102" of the second object and the scheduled delivery date "March 20, 2022", and the price of the set "100 coins".

When the settlement unit 211 receives the settlement completion information from the common user ID management server 1 (Step 207), it notifies the object sales unit 210, the first object provision unit 212, and the second object delivery procedure unit 213 that the settlement for the object has been completed, and the object sales unit 210 sends a selected object purchase completion screen to the terminal 4 (Step 208). The selected object purchase completion screen of FIG. 13 displays that the card X1 has become available for use in the application game "X Series" and that the real card X2 is scheduled to be delivered to the user on March 20, 2022.

After the payment unit 211 makes a payment, the first object providing unit 212 provides the terminal 4 with digital data of the first object that can be used by the service execution unit 411 of the terminal 4 (Step 209). In this operation, the digital data of the card X1 to be registered in the game application "X Series" installed on the terminal 4 is transmitted to the terminal 4.

The second object delivery procedure unit 213 refers to the scheduled delivery date in the player object management database 122 and performs delivery procedures for the second object (Step 210). In this operation, the procedure is performed to deliver the real card X2 to the user on March 20, 2022.

Next, the object registration process (Step 3) of the user ID management server 1 will be described. Figure 14 is a flowchart of the object registration process (Step 3).

When the common user ID management server 1 receives the payment information (Step 300), the common user ID management unit 110 authenticates the common user ID and password included in the payment information using the common user ID management database 120 (Step 301). For example, if the payment information includes the user's common user ID "10001" and password "25002", then according to the common user ID database 121 in FIG. 4, the user's common user ID "10001" and password "25002" match, and therefore authentication is possible.

If the common user ID and password can be authenticated (Step 302), the common user ID management unit 110 checks the balance of the currency owned by the user of the common user ID (Step 303). If the balance of the currency owned by the user in the common user ID database 121 is equal to or greater than the price of the object included in the payment information (Step 304), the common user ID management unit 110 subtracts the price of the object to be purchased from the balance of the currency owned by the user (Step 305). Then, the common user ID management unit 110 updates the player object management database 122 with the object ID of the first object, the available service name, and the object ID of the second object and the scheduled delivery date included in the payment information (Step 307), and transmits payment completion information to the object selling server 2 (Step 308). Specifically, if the information included in the payment information is the user's common user ID "10001", the first object's object ID "X101", the available service "Game "X Series"", the second object's object ID "X102", and the scheduled delivery date "March 20, 2022", then the player object management database 122 for the common user ID "10001" is updated as shown in FIG. 4.
This completes the explanation of the object registration process (Step 3).

Next, the use of the first object by the user in the service will be described. Note that in this embodiment, a game will be described as an example of a service that the user uses, but the same applies to other services such as the metaverse.

The game execution unit 411 of the terminal 4 displays a login screen for the game and sends a service execution request to the service providing server 3. The service execution request includes the service name, common user ID, and password. Figure 15 is an example of the login screen for the game. The user enters the common user ID and password on the login screen and presses the login button. In this case, the service execution request includes the game "X Series", the common user ID "10001", and the password "25002".

When the service providing server 3 receives the service execution request, it starts the service execution process (Step 4). Figure 16 is a flowchart of the service execution process (Step 4) and the start of the object management process (Step 5).

When the service providing server 3 receives a service execution request (Step 400), the game execution unit 310 sends a usable object request to the common user ID management server 1 (Step 401). The usable object request includes the service name, common user ID, and password included in the received service execution request. In this example, the usable object request includes the game "X Series", the common user ID "10001", and the password "25002".

When the common user ID management unit 110 of the common user ID management server 1 receives an available object request (Step 500), it authenticates the common user ID and password included in the available object request (Step 501).

The common user ID management unit 110 refers to the common user ID management database 120, and if the common user ID and password can be authenticated (Step 502), it acquires an object ID that can be used for the service (Step 503). The common user ID management unit 110 then transmits usable object information, including the object ID that can be used for the service, to the service providing server 3 (Step 504).

Specifically, the available object request includes the game "X Series", the common user ID "10001", and the password "25002". The common user ID management unit 110 authenticates the common user ID "10001" and the password "25002" using the common user ID database 121. Since the common user ID "10001" and the password "25002" can be authenticated from the common user ID database 121, the common user ID management server 1 obtains the object ID of the object available for the game "X Series" from the player object management database 122 of the common user ID "10001". From the player object management database 122 of the common user ID "10001", the object ID of the object available for the game "X Series" is "X101". The common user ID management unit 110 transmits the available object information including the object ID "X101" to the service providing server 3.

When the game execution unit 310 of the service providing server 3 receives the available object information from the common user ID management server 1 (Step 402), it permits the use of the object with the object ID included in the available object information in the game (Step 403). Then, the game execution unit 310 of the service providing server 3 executes a game (service) using the object on the terminal 4 (Step 404).

Specifically, the game execution unit 310 receives the available object information including the object ID "X101", and makes the card X1 specified by the object ID "X101" available in the "X Series" game.
This concludes the explanation of the services provided to users.

Next, we will explain the object list process, which allows users to view a list of objects they currently own.

The browser execution unit 410 of the terminal 4 sends a request for a list of owned objects to the common user ID management server 1. The request for a list of owned objects includes a common user ID and a password. The common user ID management server 1 that receives the request for a list of owned objects executes object listing processing (Step 6). Figure 17 is a flowchart of the object listing processing (Step 6).

When the common user ID management unit 110 of the common user ID management server 1 receives the owned object list request (Step 600), it authenticates the common user ID and password included in the owned object list request (Step 601). The common user ID management unit 110 refers to the common user ID management database 120, and if it is able to authenticate the common user ID and password (Step 602), it acquires information on objects registered in the player object management database 122 of the common user ID (Step 603). The common user ID management unit 110 then generates an object list screen from the acquired information and transmits the object list screen to the terminal 4 (Step 604).

Figure 18 is a diagram showing an example of an object list screen. Figure 18 shows a list screen of objects owned by a user (user name: XYZ) with a common user ID "10001". The object list screen displays the object name, the name of a service available for the first object and whether the service is available, and the scheduled delivery date and completion date for the second object.

In the first embodiment, a first object and a second object associated with a character are provided to the user as a set. This allows the user to acquire assets as intangible digital data and assets as tangible goods. Furthermore, by associating at least the first object with a common user ID that identifies the user across multiple services, various services that utilize the first object can be provided to the user, and further, the first object can be used not only in existing services but also in new services that are added.

<Modification of the First Embodiment>
In the first embodiment described above, the use of the service of the first object is immediately possible after purchase, but this is not limited to this. The availability of the service of the first object can be freely set. For example, the use of the service of the first object may be possible on the scheduled delivery date of the second object. In this way, the value of the first object and the value of the second object can be generated on the same day. Furthermore, when a new service using the first object is introduced, the introduction date of the service can be set as the availability date of the first object.

Second Embodiment
Tangible objects such as goods have long had asset value and have been traded. Intangible objects such as digital data have also recently gained asset value, for example, rare cards in application games. These intangible objects can also be traded.

On the other hand, while intangible digital data does not deteriorate through trading, tangible items may lose their asset value through trading. For example, once an item has been handed over by a seller, it is no longer considered new, but is treated as a used item.

Considering this social reality, the period during which a transaction can be made for a set of an intangible object and a tangible object must take into account the time of delivery of the tangible object.

The second embodiment therefore describes an example of trading objects by setting a tradable period to a period that can prevent a decline in the asset value of tangible objects while ensuring the tradability of intangible objects. The second embodiment can also be considered an example of adding a service called object trading.

Fig. 19 is a diagram for explaining the second embodiment. Fig. 19 shows an example in which an intangible game card X1 used in an application game and a tangible real card X2 are sold as a set. A first user can acquire a set of the game card X1 and the real card X2 by paying the price for the set of the game card X1 and the real card X2. In this case, the form of the object to be traded by the first user is as follows:
- Only the first object is the subject of trading.
A set of a first object and a second object is the subject of a transaction.
- Only the second object is the subject of trading.

As described above, since the second object may be included in the subject of the transaction, it is necessary to take into consideration the asset value of the second object. Therefore, in this embodiment, the tradable period during which the first object and/or the second object can be traded is the period from the settlement of the payment of the price of the set to the scheduled delivery date of the second object to the first user (hereinafter, referred to as the delivery grace period). In the example of Fig. 19, the delivery grace period from the settlement of the payment of the price of the set of the game card X1 and the real card X2 by the first user to the scheduled delivery date of the real card X2 to the first user is the tradable period during which the game card X1 and the real card X2 can be traded with the second user as the subject of the transaction.
The embodiment will be described in detail below. In the following description, the same components as those in the first embodiment are designated by the same reference numerals, and detailed description thereof will be omitted.

Overall Configuration of Second Embodiment
The object trading system in the second embodiment will be described. FIG. 20 is a diagram showing an example of the overall configuration of the object trading system in the second embodiment. As shown in FIG. 20, the object trading system includes a trading server 5 in addition to the first embodiment. The trading server 5 can be connected to the common user ID management server 1, the object sales server 2, the service providing server 3, and the terminals 4a and 4b via a network N and can communicate with each other. The trading server 5 is a server system including one or more server devices and storage devices. The trading server 5 does not need to be installed separately, as with the common user ID management server 1, the object sales server 2, and the service providing server 3, and may be mixed with other servers in a cloud system. The terminal 4a is a terminal operated by a first user, and the terminal 4b is a terminal operated by a second user.

<Configurations of the Second Embodiment>
The transaction server 5 will now be described. FIG. 21 is a block diagram showing an example of the functional configuration of the transaction server 5.
As shown in FIG. 21, the device includes a processing unit 50, a communication unit 51, and a storage unit 52.

The processing unit 50 performs overall control of the operation of the common user ID management server 1 based on the programs and data stored in the memory unit 52. The functions of the processing unit 50 can be realized by electronic components such as a microprocessor such as a CPU or GPU, an ASIC, and an IC memory. The processing unit 50 includes, as its main functional units, a calculation unit 500, an image generation unit 501, and a communication control unit 502.

The calculation unit 500 includes a transaction control unit 510 .
The transaction control unit 510 controls transactions of objects between users in cooperation with the common user ID management server 1. Specifically, the transaction control unit 510 performs processes such as registering objects to be traded by users, managing the tradable period, accepting trade applications from other users, and managing whether or not a transaction has been concluded.

The transaction control unit 510 can handle any of the following transactions: only the first object, only the second object, or a set of the first object and the second object; however, only one of these may be handled. In addition, the transaction mode handled by the transaction control unit 510 can be either an exchange of an object for currency (coins), or an exchange of objects for each other.

The period during which an object can be traded between users is from the settlement of payment for the second object to the scheduled delivery date of the second object (delivery grace period), but it is thought that in many cases a user will not start a transaction immediately after settling the payment for the object. Therefore, the transaction control unit 510 sets the transaction period from the date on which the user applies for a request to trade an object to the scheduled delivery date of the second object. These processes are performed using the transaction management database 510 stored in the memory unit 52.

Figure 22 is a diagram showing an example of a transaction management database 510. The transaction management database 510 is a database in which objects to be traded are registered. One record in the transaction management database 510 includes a field for the name of the object to be traded, a field for an object ID that identifies the object, a field for the transaction period of the object, a field for information on the object's available services and transaction conditions (currency, exchange with other objects), and a field for the common user ID of the user who registered the object to be traded.

The transaction control unit 510 deletes records of objects for which a transaction was concluded during the transaction period. The transaction control unit 510 also references the transaction period field in the transaction management database 510 and deletes records of objects for which the transaction period has passed without a transaction being concluded.

The image generation unit 501 generates one screen per frame time (e.g., 1/60 seconds) based on the processing results of the calculation unit 500, and outputs an image signal of the generated screen. The functions of the image generation unit 101 can be realized by, for example, a processor such as a GPU or digital signal processor (DSP), a video signal IC, a program such as a video codec, an IC memory for drawing frames such as a frame buffer, an IC memory used for expanding texture data, etc.

The communication control unit 502 performs communication connection and data processing for data communication between the common user ID management server 1 and the terminal 4.

The communication unit 51 connects to a communication line to realize communication. The functions of the communication unit 11 can be realized, for example, by a wireless communication device, a modem, a TA (terminal adapter), a jack for a wired communication cable, a control circuit, etc.

The memory unit 52 is realized by, for example, a RAM, a ROM, an IC memory such as a flash memory, a magnetic disk such as a hard disk, or an optical disk such as a CD-ROM or a DVD, and stores a system program and a function program. The system program is a program for realizing the basic functions of a computer. The function program is a program for causing the calculation unit 500 to function as a transaction control unit 510. In this embodiment, the memory unit 12 also stores a transaction management database 510.

<Operation of the second embodiment>
The operation of the second embodiment will be described. Fig. 23 is a sequence diagram of the operation of the second embodiment. The terminal 4a is the terminal of the first user, and the first user is the seller of the object (the exchange source in the case of an exchange). The terminal 4b is the terminal of the second user, and the second user is the buyer of the object (the exchange destination in the case of an exchange).

The browser execution unit 410 of the terminal 4a sends a tradable owned object list request to the trading server 5, requesting a list of tradable objects among the objects owned by the first user. The tradable owned object list request includes the first user's common user ID and password. In this example, the first user's common user ID and password are the common user ID "10001" and the password "25002".

Here, the trading server 5 executes the trading object registration process (Step 10), and the common user ID management server 1 executes the trading-possessed object list process (Step 11). Figure 24 is a flowchart of the trading object registration process (Step 10) and the trading-possessed object list process (Step 11).

When the transaction control unit 510 of the transaction server 5 receives the request for a list of tradable objects (Step 700), it sends tradable ownership object information, including the common user ID and password included in the request for a list of tradable ownership objects, to the common user ID management server 1 (Step 701). In this example, it sends tradable ownership object information, including the common user ID "10001" and password "25002", to the common user ID management server 1.

When the common user ID management unit 101 of the common user ID management server 1 receives the tradable ownership object information (Step 800), it authenticates the common user ID and password included in the tradable ownership object information using the common user ID database 121 (Steps 801 and 802). In this example, the authentication target is the common user ID "10001" and password "25002", so authentication is possible by referring to the common user ID database 121 shown in FIG. 4.

The common user ID management unit 101 acquires information on tradable objects from the player object management database 122 corresponding to the common user ID (Step 803). A tradable object is one in which the second object is in the delivery grace period. That is, the second object is an object before the scheduled delivery date. For example, if the date on which the tradable owned object information was received is March 15, 2022, referring to the player object management database 122 of the common user ID "10001" in FIG. 4, the objects whose scheduled delivery date is before March 15, 2022 are "X series character X" and character Y. Therefore, the common user ID management unit 101 acquires the object name, object ID, available service name, availability, scheduled delivery date, and delivery completion date for "X series character X" and character Y. Then, this information is regarded as available owned object information.
The common user ID management unit 101 transmits the available owned object information to the trading server 5 (Step 804).

The transaction control unit 510 of the transaction server 5 receives the available ownership object information (Step 702). Using the available ownership object information, the transaction control unit 510 generates a tradable ownership object list screen corresponding to the common user ID and transmits it to the terminal 4a (Step 703). At this time, the transaction control unit 510 sets the period from the date of reception of the available ownership object information to the scheduled delivery date of the second object as the transaction period during which the transaction is possible.

The browser execution unit 410 of the terminal 4 receives the tradable owned object list screen and displays the tradable owned object list screen. FIG. 25 is a diagram showing an example of a screen displayed on the terminal 4a. According to FIG. 25, a list of objects that the first user can trade as of March 15, 2022 is displayed.

The first user selects the object he or she wishes to trade from the list of owned objects that can be traded. In this example, it is assumed that the first user selects "X Series Character X" and presses a button on the trading conditions screen. When the button on the trading conditions screen is pressed, the browser execution unit 410 of the terminal 4a sends a request for the trading conditions screen.

When the transaction control unit 510 of the transaction server 5 receives the transaction conditions screen request (Step 704), it sends the transaction conditions screen to the terminal 4a (Step 705).

The browser execution unit 410 of the terminal 4 receives the transaction conditions screen and displays the transaction conditions screen. As shown in FIG. 25, the user can select the type of object to be traded (only the first object, only the second object, or the first and second objects) and input the transaction conditions (exchange with currency or object). In this example, the first user selects the first object and the second object (application game card X1 and real card X2) as the objects to be traded, sets 150 coins as the object to be exchanged as the transaction conditions, and presses the transaction conditions registration button. When the transaction conditions registration button is pressed, the browser execution unit 410 of the terminal 4a transmits the transaction conditions to the transaction server 5.

When the transaction control unit 510 of the transaction server 5 receives the transaction conditions (Step 706), the transaction control unit 510 registers the transaction conditions in the transaction management database 510 (Step 707). In this example, as shown in the transaction management database 510 of Fig. 22, information on the object "X Series Character X" is registered.
This allows the first user to register the object to be traded in the trading server 5.

Next, a transaction offer by a second user will be described.
The browser execution unit 410 of the terminal 4 b sends a request for a list of transaction target objects to the transaction server 5 .

The trading server 5 that receives the request for the list of trading objects executes the trading process (Step 12). Figure 26 is a flowchart of the trading process (Step 12).

When the transaction control unit 510 of the transaction server 5 receives the transaction object list request (Step 900), it obtains information on currently tradable objects from the transaction management database 510 and generates a transaction object list (Step 901). Then, the transaction control unit 510 transmits the transaction object list screen to the terminal 4b.

The browser execution unit 410 of terminal 4b receives the transaction object list screen and displays the transaction object list screen. Figure 27 is an example of a transaction screen displayed on terminal 4b. The transaction object list screen in Figure 27 displays a list of two transaction object objects currently registered in the transaction management database 510.

The second user selects an object for which he/she wishes to make a trade offer from the trade target objects displayed on the trade target object list screen, and presses a button on the trade offer screen. The browser execution unit 410 of terminal 4b sends a trade offer screen request including identification information for identifying the selected object to the trade server 5. Here, it is assumed that the second user has selected "X Series" character A.

When the transaction control unit 510 of the transaction server 5 receives the transaction application screen request (Step 903), it transmits the transaction application screen for the selected object to the terminal 4b (Step 904).

Terminal 4b receives the trade application screen and displays the trade application screen. The trade application screen in FIG. 27 displays input fields for the second user's common user ID and password. When the second user applies for a trade, the second user inputs the second user's common user ID and password and presses the trade application button. When the trade application button is pressed, terminal 4b sends the trade application to the trade server 5. The trade application includes the second user's common user ID and password. In this example, the second user's common user ID and password are the common user ID "10002" and the password "avn51".

When the transaction control unit 510 of the transaction server 5 receives the transaction request (Step 905), it transmits a negotiation request screen for the object for which a transaction request has been made to the terminal 4a (Step 906).

The browser execution unit 410 of the terminal 4a receives the negotiation offer screen and displays the negotiation offer screen. FIG. 28 is an example of the negotiation offer screen displayed on the terminal 4a. The negotiation offer screen in FIG. 28 displays the user name of the negotiating partner, object information of the transaction target, and buttons for accepting and rejecting the offer.

The first user decides whether to accept or reject the transaction for the transaction object displayed on the negotiation offer screen. If the first user accepts the transaction for the transaction object, he/she presses the accept button. If the first user does not accept the transaction for the transaction object, he/she presses the reject button. The browser execution unit 410 of the terminal 4a sends information on transaction acceptance or rejection corresponding to the selected button to the transaction server 5.

When the transaction control unit 510 of the transaction server 5 receives the transaction approval information (Step 907), it transmits the transaction information to the common user ID management server 1 (Step 908). The transaction information includes the common user ID and password of the first user, the common user ID and password of the second user, the object ID to be traded, and the exchange conditions. In this example, the transaction information includes the common user ID "10001" and password "25002" of the first user, the common user ID "10002" and password "avn51" of the second user, the object ID "X101" and "X102", and the exchange condition "150 coins".

The common user ID management server 1 that receives the transaction information executes the transaction authentication process (Step 13). Figure 29 is a flowchart of the transaction authentication process (Step 13).

When the common user ID management unit 101 of the common user ID management server 1 receives the transaction information (Step 1000), it authenticates the common user ID and password (Step 1001). In this example, the common user ID and password to be authenticated are the common user ID "10001" and password "25002" of the first user, and the common user ID "10002" and password "avn51" of the second user. These common user IDs and passwords are authenticated by referring to the common user ID database 121. In this example, referring to the common user ID database 121 in FIG. 4, the common user ID "10001" and password "25002" of the first user, and the common user ID "10002" and password "avn51" of the second user can be authenticated.

If the common user ID and password have been authenticated (Step 1002), the common user ID management unit 101 checks the exchange conditions for the transaction objects (Step 1003). In this example, the exchange conditions for the transaction objects are a payment of "150 coins" from the second user to the first user. Therefore, the common user ID management unit 101 checks whether the balance of the number of owned coins for the second user's common user ID "10002" in the common user ID database 121 is "150 coins" or more.

If the exchange conditions for the transaction object are met (Step 1004), the common user ID management unit 101 updates the player object management database 122 (Step 1005).

The update of the player object management database 122 will be specifically described. FIG. 30 is a diagram showing an example of the common user ID management table 120 after the transaction. The common user ID management unit 101 subtracts the exchange condition of "150 coins" from the coins owned by the second user (common user ID "10002"), "500 coins", in the common user ID database 121, and updates the coins owned by the second user to "350 coins". In addition, the common user ID management unit 101 sets the service use of the application game card X1 of the object "X series character X" in the player object management database 122 of the first user (common user ID "10001") as "not available" (impossible), and deletes the scheduled delivery date of the real card X2. In addition, the common user ID management unit 101 adds records of the application game card X1 and real card X2 of the object "X series character X" to the player object management database 122 of the second user (common user ID "10002"), sets the service use of the application game card X1 to "available", and enters "March 20, 2022" as the scheduled delivery date of the real card X2. This completes a transaction of the object "X series character X" between the first user and the second user.

By updating the player object management database 122 in this way, the second user can use the application game card X1, which is the first object, in the game "X Series." In addition, the object delivery procedure unit 213 executes the delivery procedure for the real card X2, which is the second object, to the second user on "March 20, 2022."

The common user ID management unit 101 updates the player object management database 122, and when the transaction is completed, transmits the transaction authentication information to the transaction server 5 (Step 1006).

On the other hand, if the common user ID management unit 101 cannot authenticate the common user ID and password (Step 1002) or does not satisfy the exchange conditions of the transaction object (Step 1004), it sends transaction non-authentication information to the transaction server 5 (Step 1007).

When the transaction control unit 510 of the transaction server 5 receives the transaction authentication information (Step 909), it transmits transaction completion information to the terminals 4a and 4b (Step 910). On the other hand, when the transaction control unit 510 of the transaction server 5 receives the transaction non-authentication information (Step 909), it transmits transaction non-completion information to the terminals 4a and 4b (Step 910).

In this way, the first user can exchange the acquired object for currency or another object. Meanwhile, the second user can acquire an object from the first user, use the acquired first object for a service, and also own the second object.

In the second embodiment, the tradable period for the object is set within the period from the settlement of payment for the object to the scheduled delivery date of the second object, so that the object can be traded without causing a decrease in the asset value of the object. In addition, since the trade is carried out before the second object is delivered to the user, there is no risk of default in the transaction not delivering the second object from the trading partner after the transaction is concluded.

<First Modification of the Second Embodiment>
In the second embodiment, when an object including a second object is the subject of a transaction and the transaction conditions are an exchange of objects including the second object, it is necessary to take into consideration the transaction period during which the transaction can be performed, in consideration of the decrease in value of the second object and the safety of the transaction. Therefore, in a modified example of the second embodiment, when the transaction conditions are an exchange of objects including the second object, the transaction period is set to the period from the latest settlement date among the users' settlement completion dates to the earliest settlement date among the users' scheduled delivery dates.

Figure 31 is a diagram for explaining a modified example of the second embodiment. As shown in Figure 31, the first user purchases an X set consisting of a game card X1 of the first object and a game card X2 of the second object on March 10, 2022 (payment completion date), and the scheduled delivery date of the game card X2 of the second object is April 20, 2022. On the other hand, the second user purchases a Y set consisting of a figure Y1 of the first object and a figure Y2 of the second object on March 20, 2022 (payment completion date), and the scheduled delivery date of the figure Y2 of the second object is April 30, 2022. In such a case, when considering a transaction in which the X set and the Y set are exchanged between the first user and the second user, the transactionable period is the period from March 20, 2022, which is the payment completion date of the second user, to April 20, 2022, which is the scheduled delivery date of the game card X2 of the second object.

In setting such a trading period, it is considered that in many cases, the seller selling the set will have previously set the scheduled delivery date for each set, such as a scheduled simultaneous delivery date for product A. Therefore, when the user's trading condition is an exchange of objects including a second object, the trading control unit 510 of the trading server 5 acquires the scheduled delivery dates of each of the second objects to be exchanged from the sales object data 220 and determines whether a trading period can be set. For example, when a first user wishes to trade set X acquired by the first user for exchange with set Y, if the date on which the first user registers the trading request is before the scheduled delivery date of the second object of set Y, the period from the date on which the first user registers the trading request to the scheduled delivery date of the second object of set Y is set as the trading period.

By setting the transaction period in this manner, transactions involving the exchange of objects that include a tangible second object can be carried out safely without reducing the value of the tangible second object and preventing accidents in which the second object is not delivered to both users.

<Modification 2 of the second embodiment>
When a transaction is concluded and the first object is transferred to another user, it is possible that the original user may have used the first object in a game service or the like before the transfer. When the first object is used in a game or the like, character information (e.g., level) associated with the first object in the game increases. Therefore, at the time of transfer, the character information (e.g., level) associated with the first object in the game may be higher than the initial value, and the value of the first object in the game may have increased.

Therefore, when a transaction is concluded and the first object is transferred to another user, the value acquired by the first object up to the time of the transfer (e.g., character information in a game, etc.) may be inherited by the other user. In this case, information on the first object held by the service providing server 3, for example, information recorded in the object database 320, is applied to the first object at the transfer destination.
By configuring in this way, the trading value of the first object increases.

<Modification 3 of the second embodiment>
Value information may be attached to an object. For example, the rarity of a game card. The higher the rarity, the higher the value of the game card. Therefore, a user will want to exchange an acquired object for an object that is equivalent in value (the same or equivalent) to the acquired object. It is also necessary to prevent a user from suffering a disadvantage caused by a mistaken selection of an exchange target. Therefore, in a transaction in which an object is exchanged, a third modification of the second embodiment is configured so that only objects having equivalent value information can be exchanged. That is, an example of an equivalent exchange of objects will be described.

When the transaction control unit 510 of the transaction server 5 receives a transaction conditions screen request, it acquires value information of the object to be traded (trade object). The value information of each object is registered in advance in the sales object database 220 of the object sales server 2. The transaction control unit 510 of the transaction server 5 then acquires the value information of the trade object from the sales object database 220. Furthermore, the transaction control unit 510 acquires from the sales object database 220 the name and object ID of an object having value information equivalent (the same or similar) to the acquired value information of the trade object. The transaction control unit 510 then transmits the transaction conditions screen of the trade object, including the acquired name and object ID of the object, to the terminal 4a of the first user. Note that the transaction server 5 may have a database similar to the sales object database 220.

The browser execution unit 410 of the terminal 4a receives the transaction conditions screen and displays the transaction conditions screen. FIG. 32 is a diagram showing an example of the transaction conditions screen in the third modified example of the second embodiment. The transaction screen in FIG. 32 displays a combo box when selecting exchange with an object as the transaction condition. When the combo box is selected, a list of objects with the same value as the object to be traded is displayed. For example, the rarity of the object to be traded, "X Series Character X", is "rare", and the objects that can be exchanged for this object set are Card X3 (rare) set, Card X15 (rare) set, Card X25 (rare) set, and Card X32 (rare) set.

In the example of FIG. 32, the trading conditions are the same for rarities, but this is not necessarily limited to the same, and the conditions may be expanded to a range that can be considered equivalent to the rarity of the object being traded, for example, to a higher or lower rarity. In addition, when the value information of the first object and the value information of the second object are different, exchangeable objects may be selected based on the respective value information. In addition, when value information is set for a pair of a first object and a second object, exchangeable objects may be selected based on the value information of the pair.

The first user can select the object to be exchanged by selecting the object to be exchanged from the list in the combo box. When the transaction condition registration button is pressed, the browser execution unit 410 of the terminal 4a transmits the transaction conditions, including the object ID of the object to be exchanged, to the transaction server 5.

When the transaction control unit 510 of the transaction server 5 receives the transaction conditions, it registers the transaction conditions in the transaction management database 510. As a result, the transaction conditions registered in the transaction management database 510 will be an equivalent exchange with an object that is equivalent (the same or equivalent) to the value of the transaction target object, and an object that is significantly different in value from the transaction target object will not be the subject of exchange.

This configuration allows the user to exchange the acquired object for an object of equivalent (the same or similar) value, preventing transactions that cause the user disadvantage.

A part or all of the above-described embodiments may also be described as follows, but are not limited to the following:

[Appendix 1]
a payment means for making a payment for a first object which is an intangible object and which can be used for a predetermined service, and a second object which is a tangible object;
a first object providing means for providing the first object to a user on condition that the payment of the price is completed;
a delivery procedure means for executing a delivery procedure for delivering the second object to the user on condition that the payment of the price is completed;
An object providing system comprising:

[Appendix 2]
The first object and the second object are provided as a pair;
The price includes the first object and the second object.
2. The object provision system of claim 1.

[Appendix 3]
The first object and the second object are objects relating to the same character or characters related to each other.
3. The object provision system of claim 2.

[Appendix 4]
The first object and the second object include the same picture information.
4. The object provision system of claim 3.

[Appendix 5]
an associating means for associating a user identifier of the user with the first object on condition that the payment of the price is completed;
5. An object provision system according to any one of claims 1 to 4.

[Appendix 6]
The user identifier is an identifier commonly used among a plurality of predetermined services.
6. The object provision system according to claim 5.

[Appendix 7]
a first service execution means capable of executing a service that does not involve releasing an association between the user identifier and the first object by using the first object;
7. The object providing system according to claim 5 or 6.

[Appendix 8]
the first service execution means executes a game utilizing the first object.
8. The object provision system of claim 7.

[Appendix 9]
a second service execution means capable of executing a service involving the release of an association between the user identifier and the first object by using the first object;
6. The object provision system according to claim 5.

[Appendix 10]
the second service execution means executes a service in which the first object is a trading target;
When the first object is transferred from the user to another user, the associating means releases the association between the user identifier of the user and the first object, and associates the first object with the user identifier of the other user.
10. The object provision system of claim 9.

[Appendix 11]
the delivery procedure means does not execute a procedure for delivering the second object to the user on condition that the association between the user identifier of the user and the first object has been released;
11. The object providing system according to claim 9 or 10.

[Appendix 12]
the delivery procedure means executes a procedure for delivering the second object after the first object is provided by the first object providing means;
12. An object provision system according to any one of claims 1 to 11.

[Appendix 13]
the delivery procedure means executes a delivery procedure for delivering the second object to the user.
13. An object provision system according to any one of claims 1 to 12.

[Appendix 14]
the first object providing means controls the use of the predetermined service of the first object to be enabled on condition that the delivery procedure of the second object is completed by the delivery procedure means;
14. An object provision system according to any one of claims 1 to 13.

[Appendix 15]
an object presenting means capable of presenting at least one pair of the first object and the second object;
the object presenting means controls to select any one of the presented sets;
15. An object provision system according to any one of claims 2 to 14.

[Appendix 16]
a list presenting means capable of presenting a list of the first objects associated with a user identifier of the user;
16. An object provision system according to any one of appendix 5 to appendix 15.

[Appendix 17]
The list includes status information of a delivery procedure of the second object paired with the first object.
17. The object provision system of claim 16.

[Appendix 18]
a payment means for making a payment for a set of a first object, which is an intangible object and can be used in a plurality of services, and a second object, which is a tangible object;
a first object providing means for providing the first object to a user on condition that the payment of the price is completed;
a delivery procedure means for executing a delivery procedure for delivering the second object to the user on condition that the payment of the price is completed;
an associating means for associating a user identifier, which is used in common among the plurality of services and is for identifying the user in the plurality of services, with the first object on the condition that the payment of the price is completed;
a plurality of service execution means for executing a service using the first object on condition that the user identifier is authenticated;
An object utilization system comprising:

[Appendix 19]
a payment means for making a payment for a first object which is an intangible object and which can be used for a predetermined service, and a second object which is a tangible object;
a first object providing means for providing the first object to a user on condition that the payment of the price is completed;
a delivery procedure means for executing a delivery procedure for delivering the second object to the user on condition that the payment of the price is completed;
An information processing device comprising:

[Appendix 20]
a payment means for making a payment for a first object which is an intangible object and which can be used for a predetermined service, and a second object which is a tangible object;
a first object providing means for providing the first object to a user on condition that the payment of the price is completed;
a delivery procedure means for executing a delivery procedure for delivering the second object to the user on condition that the payment of the price is completed;
A program that makes a computer function as a

[Appendix 21]
The computer
A payment settlement is made for a first object which is an intangible property and which can be used for a predetermined service, and a second object which is a tangible property;
providing the first object to the user on condition that the payment of the price is completed;
and controlling a delivery procedure for delivering the second object to the user on condition that the payment of the price is completed.
Object provision method.

The present invention has been described above with reference to preferred embodiments, but the present invention is not necessarily limited to the above embodiments and can be modified and implemented in various ways within the scope of its technical concept.

1 Common user ID management server 2 Object sales server 3 Service provision server 4 Terminal 5 Transaction server

Claims (21)

a payment means for making a payment for a first object which is an intangible object and which can be used for a predetermined service, and a second object which is a tangible object;
a first object providing means for providing the first object to a user on condition that the payment of the price is completed;
an associating means for associating a user identifier of the user with the first object on condition that the payment of the price is completed;
a first service execution means capable of executing a service involving the release of an association between the user identifier and the first object by using the first object;
a delivery procedure means for executing a delivery procedure for delivering the second object to the user on condition that the payment of the price is completed;
Equipped with
the delivery procedure means does not execute a procedure for delivering the second object to the user on condition that the association between the user identifier of the user and the first object has been released;
Object provision system. The first object and the second object are provided as a pair;
The price includes the first object and the second object.
The object providing system according to claim 1 . The first object and the second object are objects relating to the same character or characters related to each other.
The object providing system according to claim 2 . The first object and the second object include the same picture information.
The object providing system according to claim 3 . the first service execution means executes a service in which the first object and the second object are traded;
When the first object and the second object are transferred from the user to another user, the associating means releases the association between the user identifier of the user and the first object, and associates the first object with the user identifier of the other user.
5. The object providing system according to claim 1. the delivery procedure means, when the first object and the second object are transferred from the user to another user, executes a procedure for delivering the second object to the other user.
The object providing system according to claim 5 . the first service execution means sets a tradable period of the first object and the second object to a period from a date on which the user applies for a request to trade the first object and the second object to a scheduled date of delivery of the second object to the user;
7. The object providing system according to claim 5 or 6. The user identifier is an identifier commonly used among a plurality of predetermined services.
The object providing system according to any one of claims 1 to 7. a second service execution means capable of executing a service that does not involve releasing the association between the user identifier and the first object by using the first object;
The object providing system according to claim 8. the second service execution means executes a game utilizing the first object.
The object provision system according to claim 9. the delivery procedure means executes a procedure for delivering the second object after the first object is provided by the first object providing means;
The object providing system according to any one of claims 1 to 10. the delivery procedure is a delivery procedure for delivering the second object;
The object providing system according to any one of claims 1 to 11. an object presenting means capable of presenting at least one pair of the first object and the second object;
the object presenting means controls to select any one of the presented sets;
The object providing system according to claim 2 . a list presenting means capable of presenting a list of the first objects associated with a user identifier of the user;
The object providing system according to any one of claims 1 to 13. The list includes status information of a delivery procedure of the second object that is a pair with the first object.
The object provision system according to claim 14. a payment means for making a payment for a first object which is an intangible object and which can be used for a predetermined service, and a second object which is a tangible object;
a first object providing means for providing the first object to a user on condition that the payment of the price is completed;
an associating means for associating a user identifier of the user with the first object on condition that the payment of the price is completed;
a service execution means capable of executing a service involving the release of an association between the user identifier and the first object by using the first object;
a delivery procedure means for executing a delivery procedure for delivering the second object to the user on condition that the payment of the price is completed;
Equipped with
the delivery procedure means does not execute a procedure for delivering the second object to the user on condition that the association between the user identifier of the user and the first object has been released;
Information processing device. the service execution means executes a service in which the first object and the second object are traded;
When the first object and the second object are transferred from the user to another user, the associating means releases the association between the user identifier of the user and the first object, and associates the first object with the user identifier of the other user.
The information processing device according to claim 16. the delivery procedure means, when the first object and the second object are transferred from the user to another user, executes a procedure for delivering the second object to the other user.
The information processing device according to claim 17. the service execution means sets a tradable period for the first object and the second object to a period from a date on which a user applies for a trade of the first object and the second object to a scheduled delivery date of the second object to the user;
19. The information processing device according to claim 17 or 18. a payment means for making a payment for a first object which is an intangible object and which can be used for a predetermined service, and a second object which is a tangible object;
a first object providing means for providing the first object to a user on condition that the payment of the price is completed;
an associating means for associating a user identifier of the user with the first object on condition that the payment of the price is completed;
a service execution means capable of executing a service involving the release of an association between the user identifier and the first object by using the first object;
a delivery procedure means for executing a delivery procedure for delivering the second object to the user on condition that the payment of the price is completed;
The computer functions as
the delivery procedure means does not execute a procedure for delivering the second object to the user on condition that the association between the user identifier of the user and the first object has been released;
program. The computer
A payment settlement is made for a first object which is an intangible property and which can be used for a predetermined service, and a second object which is a tangible property;
providing the first object to the user on condition that the payment of the price is completed;
Associating a user identifier of the user with the first object on the condition that the payment of the price is completed;
controlling a delivery procedure for delivering the second object to the user on condition that the payment of the price is completed;
Executing a service involving disassociation of the user identifier from the first object by using the first object;
not executing a procedure for delivering the second object to the user on condition that the association between the user identifier of the user and the first object has been released;
Object provision method.

Images