GENERATION PROGRAM, GENERATION SYSTEM, AND GENERATION METHOD

Abstract

To implement various data on a virtual space.SOLUTION: A generation program makes a computer implement an identifier data acquisition part for acquiring identifier data for allowing a user to identify use data to be used in a virtual space, an implementation part for generating implementation data for implementing the identifier data on the virtual space on the basis of an implementation rule defined in advance and the identifier data, and an implementation data output part for outputting the implementation data to an external information processing system.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a generation program, a generation system, and a generation method. [Background technology]

[0002] Conventionally, there has been known a technique for automatically generating a character (for example, an avatar) of a user to be used in a virtual space.

[0003] For example, the avatar generation device described in Patent Document 1 is an avatar device that generates an avatar associated with a user. The device acquires non-appearance information, which is information that cannot be identified from the user's appearance, and generates the avatar by selecting items to be used for the avatar associated with the user from items stored in association with the non-appearance information. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2011-39570 Summary of the Invention [Problem to be solved by the invention]

[0005] However, in the avatar generation device described in Patent Document 1, non-appearance information, such as information about a user's affiliation and profile, is associated with and stored in advance, and an item is selected that matches the image evoked by the non-appearance information itself. In other words, the non-appearance information described in Patent Document 1 is premised on the fact that the non-appearance information itself evokes some kind of image to the extent that it can be associated with an item. Therefore, no consideration was given to embodying data in a virtual space that does not evoke a specific image, such as data consisting of a string of character strings.

[0006] Therefore, an object of the present invention is to provide a generation program, a generation system, and a generation method that are capable of embodying various data in a virtual space. [Means for solving the problem]

[0007] A generation program according to one aspect of the present invention causes a computer to implement an identifier data acquisition unit that acquires identifier data that identifies usage data used by a user in a virtual space, an embodiment unit that generates embodiment data for embodying the identifier data in the virtual space based on predetermined embodiment rules and the identifier data, and an embodiment data output unit that outputs the embodiment data to an external information processing system.

[0008] A generation system according to one aspect of the present invention includes an identifier data acquisition unit that acquires identifier data that identifies usage data used by a user in a virtual space, an embodiment unit that generates embodiment data for embodying the identifier data in the virtual space based on predetermined embodiment rules and the identifier data, and an embodiment data output unit that outputs the embodiment data to an external information processing system.

[0009] A generation method according to one aspect of the present invention involves a computer acquiring identifier data that identifies usage data used by a user in a virtual space, generating embodiment data for embodying the identifier data in the virtual space based on predetermined embodiment rules and the identifier data, and outputting the embodiment data to an external information processing system.

[0010] In this invention, a "unit" does not simply mean a physical means, but also includes cases where the functions of the "unit" are realized by software. Furthermore, the functions of one "unit" or device may be realized by two or more physical means, devices, or software modules, and the functions of two or more "units" or devices may be realized by one physical means, device, or software module. [Effects of the Invention]

[0011] According to the present invention, it is possible to provide a generation program, a generation system, and a generation method that are capable of embodying various data in a virtual space. [Brief explanation of the drawings]

[0012] [Figure 1] FIG. 1 is a diagram showing an overview of processing in a generation system 100 according to an embodiment of the present invention. [Figure 2] 1 is a diagram showing the configuration of a generation system 100 according to an embodiment of the present invention. [Figure 3] FIG. 2 is a diagram showing an example of identifier data stored in storage unit 110. [Figure 4] 10 is a diagram showing an example of embodied data stored in a storage unit 110. FIG. [Figure 5] 1 is a flowchart illustrating an example of processing in the generation system 100. [Figure 6] 1 is a flowchart illustrating an example of processing in the generation system 100. DETAILED DESCRIPTION OF THE INVENTION

[0013] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Preferred embodiments of the present invention will now be described with reference to the accompanying drawings, in which: Figure 1 is a diagram showing an overview of processing in a generation system 100 according to an embodiment of the present invention;

[0014] The generation system 100 is an information processing system realized by a generation program, which generates embodied data based on the embodied rules and identifier data, and generates the identifier data that is the basis for generating the embodied data based on the identifier rules and the embodied data. The generation system 100 is, so to speak, an information processing system that converts identifier data and embodied data into each other.

[0015] First, the generation system 100 acquires identifier data from the information processing system (S101). The generation system 100 generates embodied data based on the embodied rules and the identifier data, and outputs the embodied data to the information processing system (S102).

[0016] Furthermore, the generation system 100 acquires embodied data from the information processing system (S103). The generation system 100 generates identifier data based on the identifier rule and the embodied data, and outputs the identifier data to the information processing system (S104).

[0017] 2 is a diagram showing the configuration of a generation system 100 according to one embodiment of the present invention. The generation system 100 is communicably connected to an information processing system 200 via a network such as the Internet. The information processing system 200 is further communicably connected to a user terminal 300 via a network such as the Internet. Details of the generation system 100 will be described later.

[0018] The generation system 100 may be communicably connected to the user terminal 300 via a network such as the Internet. In this case, the generation system 100 may transmit and receive data to and from the information processing system 200 to and from the user terminal 300.

[0019] The information processing system 200 is, for example, an information processing system of a business operator. The business operator may be, for example, an operator that manages and operates a virtual space. Here, the virtual space is not particularly limited, and may be, for example, a metaverse, virtual reality, augmented reality, or mixed reality.

[0020] The information processing system 200 can request identification and materialization from the generation system 100. That is, the information processing system 200 can provide the user's identifier data and materialization data to the generation system 100, and can also obtain the materialization data and identifier data generated in the generation system 100 from the generation system 100.

[0021] The user terminal 300 is a computer used by a user of the information processing system 200, and is a smartphone, a tablet terminal, a personal computer, etc. The user is, for example, a user of a virtual space provided by the information processing system 200.

[0022] A user accesses the information processing system 200 through, for example, a user terminal 300, and uses the virtual space provided by the information processing system 200. The user then requests identification and realization in the virtual space. At this time, the user terminal 300 outputs the user's identifier data to the information processing system 200.

[0023] Subsequently, the identifier data and embodied data are input and output between the generation system 100 and the information processing system 200. The information processing system 200 embodies the identifier data in a virtual space using the embodied data acquired from the generation system 100, making it available for use by the user. The information processing system 200 also outputs the identifier data acquired from the generation system 100 to the user terminal 300. This allows the user to use the embodied data in the virtual space and acquire the identifier data.

[0024] In this case, the user terminal 300 that outputs the identifier data to the information processing system 200 and the user terminal 300 that acquires the identifier data generated by the identifier conversion may be the user terminal 300 of a different user. That is, a first user terminal of a first user may output identifier data to the information processing system 200 and request materialization, and a second user of a second user may request identifier conversion and acquire the generated identifier data from the information processing system 200. In this way, the generation system 100 can convert identifier data and materialized data to each other and support the exchange of identifier data between users.

[0025] Although one information processing system 200 and one user terminal 300 are shown in FIG. 2, there may be a plurality of information processing systems 200 and a plurality of user terminals 300.

[0026] Next, the details of the generation system 100 will be described. The generation system 100 includes a storage unit 110, an identifier data acquisition unit 120, a preprocessing unit 130, an embodiment unit 140, an embodiment data output unit 150, an embodiment data acquisition unit 160, an identifier unit 170, and an identifier data output unit 180. Each unit shown in Fig. 2 can be realized, for example, by using a storage area or by having a processor execute a program stored in the storage area.

[0027] The storage unit 110 stores information to be processed in the generation system 100. The storage unit 110 can store, for example, identifier data and embodiment data, which will be described later.

[0028] The identifier data acquisition unit 120 acquires identifier data that identifies the usage data that the user uses in the virtual space, and stores the identifier data in the storage unit 110 .

[0029] Here, the usage data is, for example, data used by a user in a virtual space, and includes, for example, contact data indicating the user's contact information, payment method data relating to the payment method used by the user at the time of payment, usage item data relating to usage items used in the virtual space, or benefit data relating to benefits exchangeable in the real space.

[0030] Identifier data is data that identifies usage data. If the usage data is contact data, the identifier data may be, for example, data indicating an address, a telephone number, or an email address. If the usage data is payment method data, the identifier data may be, for example, a credit card number, an account number, or a token ID (e.g., an EMV (Europay International, MasterCard, Visa) standard token provided by a payment brand). If the usage data is usage item data, the identifier data may be, for example, a JAN (Japanese Article Number) code, a GTIN (Global Trade Item Number) code, or a serial number. If the usage data is benefit data, the identifier data may be, for example, a benefit code corresponding to the benefit.

[0031] The identifier data may be data automatically generated in a predetermined information processing system (for example, information processing system 200 or another information processing system). The identifier data may also be data arbitrarily set by a user. The identifier data may also be data arbitrarily set by a user under certain constraints. Here, the certain constraints may be, for example, constraints regarding an upper or lower limit on the number of digits, or constraints regarding the type of character string.

[0032] The identifier data may be, for example, data that does not evoke a specific image in the user. Furthermore, the identifier data may be, for example, character string data consisting of at least one of alphanumeric characters and kana characters. Furthermore, the identifier data may be character string data consisting only of numbers.

[0033] 3 is a diagram showing an example of identifier data stored in storage unit 110. The identifier data stored in storage unit 110 includes, for example, an identifier data ID and identifier content data. The identifier data ID is information that identifies the identifier data stored in storage unit 110. The identifier content data is information that indicates the content of the identifier (for example, a character string).

[0034] The pre-processing unit 130 performs predetermined arithmetic processing on the identifier data to generate processed identifier data, which is stored in the storage unit 110 .

[0035] The preprocessing unit 130 may, for example, perform encryption processing on the identifier data using predetermined key information corresponding to the user to generate processed identifier data. In this case, the processed identifier data is data encrypted using the predetermined key information.

[0036] The encryption process is not particularly limited, but may be, for example, encryption process using a common key cryptosystem or encryption process using a public key cryptosystem.

[0037] Furthermore, preprocessing unit 130 may generate processed identifier data by processing the identifier data into a format that can be materialized by materialization unit 140, which will be described later. Specifically, for example, when materialization unit 140, which will be described later, performs materialization processing based on data of a predetermined number of digits, and the identifier data acquired by identifier data acquisition unit 120 is not in a format with the predetermined number of digits, preprocessing unit 130 processes the identifier data to generate processed identifier data with the predetermined number of digits.

[0038] The realization unit 140 generates realization data for realizing the usage data in a virtual space based on predetermined realization rules and identifier data, and stores the realization data in the storage unit 110.

[0039] The embodiment unit 140 can generate the embodied data based on the embodiment rules and the processed identifier data. The embodiment unit 140 can also generate the embodied data based on the embodiment rules and the processed identifier data generated by the encryption process.

[0040] Here, the embodied data is data in which the identifier data is embodied in a virtual space, and may be any data that can be perceived by a user in a virtual space.

[0041] The embodied data may be, for example, data that can be visually recognized by a user in a virtual space. Specifically, the embodied data may be, for example, data representing an object or creature that exists or has existed in real space, data representing an imaginary object or creature, or data representing a photographed image or an illustrated image (e.g., a character).

[0042] The embodied data may be, for example, data that can be perceived by the user auditorily, olfactoryly, gustatoryly, or tactilely in the virtual space. Specifically, the embodied data may be, for example, sound data related to sounds, smell data related to smells, taste data related to tastes, or tactile data related to sensations.

[0043] Identifier data may be a list of numbers, or may be data that is not set by the user but is automatically generated by a specific information processing system. Even if identifier data can be set by the user, it may be set under certain constraints due to the nature of the data. For this reason, identifier data may be, so to speak, impersonal data, and users may find it difficult to develop an attachment or sentiment to it.

[0044] Therefore, the generation system 100 (particularly the materialization unit 140) generates materialized data for materialization in a virtual space based on the identifier data, which is so-called impersonal data. This allows the user to recognize the identifier data, which is so-called impersonal data, as materialized materialized data in the virtual space, and to develop an attachment or fondness for the identifier data. Furthermore, the user can interact with other users in the virtual space through the materialized data.

[0045] More specifically, consider a case where the identifier data of a credit card number is embodied in the embodied data of a bird character. In the real world, a user makes a payment by presenting a credit card. Meanwhile, in the virtual world, the credit card number is embodied in the bird character. Therefore, when making a payment in the virtual world, the user can make the payment by presenting the bird character to the payment counterparty in the virtual world. This allows the user to enjoy a higher quality user experience when making a payment in the virtual world compared to when presenting a credit card number.

[0046] The realization rule is a rule for converting identifier data through a predetermined calculation process to generate realization data.

[0047] The realization rule may be, for example, correspondence data indicating a correspondence between identifier data and realization data. Alternatively, the realization rule may be, for example, a computation model that outputs realization data when identifier data is input. Alternatively, the realization rule may be a rule that combines multiple pieces of correspondence data, a rule that combines multiple computation models, or a rule that combines at least one piece of correspondence data and at least one computation model.

[0048] When the embodiment rule is correspondence data, the embodiment unit 140 may, for example, refer to the correspondence data to extract embodiment data corresponding to the identifier data, and generate the extracted embodiment data.

[0049] When the embodiment rule is a computational model, the embodiment rule may, for example, generate embodiment data in which a predetermined part corresponding to a predetermined digit of the identifier data is given a predetermined shape (which may include color or transparency) corresponding to the predetermined number, based on the predetermined number of the predetermined digit. Specifically, when the identifier data is 12-digit numerical data and a humanoid character is generated as the embodiment data, the embodiment rule may, for example, be a rule in which the first and second digits correspond to the head of the embodiment data and the third and fourth digits correspond to the arms of the embodiment data, or a rule in which the first and second digits correspond to the shape of the head of the embodiment data.

[0050] In particular, when the embodiment rule is a computational model, the generation system 100 does not need to store all of the correspondences between the identifier data and the embodiment data, and therefore the storage capacity of the generation system 100 can be reduced.

[0051] The materialization rule may be different for each type of identifier data. That is, if the identifier data is data indicating an email address, the materialization unit 140 may generate materialized data from the identifier data indicating the email address based on a first materialization rule. If the identifier data is a credit card number, the materialization unit 140 may generate materialized data from the identifier data indicating the credit card number based on a second materialization rule. This allows the generation system 100 to generate materialized data based on a materialization rule appropriate for the type of identifier data (e.g., an materialization rule appropriate for the number of digits or the type of character string of the identifier data).

[0052] The embodiment rule may also be a rule that does not generate the same embodied data from different identifier data. This allows the generation system 100 to generate unique embodied data for each identifier data. Note that the uniqueness of the embodied data may be satisfied within the range of the same identifier data type.

[0053] Furthermore, the embodiment rule may generate only one piece of embodiment data, or may generate multiple candidates for embodiment data. When the embodiment rule generates multiple candidates for embodiment data, the embodiment unit 140 may, for example, provide the generated multiple candidates for embodiment data to the user terminal 300, and the user may select one piece of embodiment data from the multiple pieces of embodiment data through the user terminal 300, thereby processing the selected piece of embodiment data as the piece of embodiment data generated based on the identifier data.

[0054] The embodiment unit 140 may generate the embodied data further based on usage status data relating to the usage status of the usage data corresponding to the identifier data. Specifically, for example, if the usage data is payment method data, the embodiment unit 140 may generate the embodied data further based on the number of times the payment method has been used indicated by the payment method data. In this case, the embodiment unit 140 may generate more attractive embodied data (e.g., a character with stronger attack power or a more popular character) as the number of times the payment method has been used increases.

[0055] Furthermore, the embodiment unit 140 may accept processing by the user on the generated embodied data. That is, the generation system 100 may process the embodied data processed by the user as embodied data generated based on the identifier data. In this way, the generation system 100 allows the user to process the embodied data to their liking, and can make the user feel a stronger attachment to the embodied data.

[0056] At this time, the generation system 100 may also store processing history information relating to the history of processing by the user. This allows the identifier generating unit 170, which will be described later, to generate identifier data further based on the processing history information.

[0057] 4 is a diagram showing an example of embodied data stored in storage unit 110. The embodied data stored in storage unit 110 includes, for example, an embodied data ID and embodied content data. The embodied data ID is information that identifies the embodied data stored in storage unit 110. The embodied content data is information that indicates the content of the embodied data (for example, the shape of a character).

[0058] The embodied data output unit 150 outputs the embodied data to an external information processing system.

[0059] The embodied data output unit 150 can output the embodied data to, for example, the information processing system 200 .

[0060] The information processing system 200 acquires the embodied data and displays the embodied data in a virtual space, for example. A user can recognize the embodied data by using the virtual space of the information processing system 200 through the user terminal 300.

[0061] The embodied data acquisition unit 160 acquires the embodied data.

[0062] The embodied data acquisition unit 160 may acquire the embodied data from the information processing system 200, for example.

[0063] The identifier generating unit 170 generates identifier data that is the basis for generating the embodied data, based on a predetermined identifier generating rule and the acquired embodied data.

[0064] The identifier rule is a rule for converting embodied data through a predetermined calculation process to generate identifier data.

[0065] The identifier rule may be, for example, correspondence data indicating the correspondence between embodied data and identifier data. The identifier rule may also be, for example, a computation model that outputs identifier data when embodied data is input. The identifier rule may also be a rule that combines multiple pieces of correspondence data, a rule that combines multiple computation models, or a rule that combines at least one piece of correspondence data and at least one computation model.

[0066] In particular, when the identifier rule is a calculation model, the generation system 100 does not need to store all of the correspondences between the identifier data and the embodied data, so the storage capacity of the generation system 100 can be reduced.

[0067] The identifier rule may be a rule that performs an operation opposite to that of the realization rule, or may be a rule that performs an operation different from that of the rule that performs the opposite operation.

[0068] In this way, the generation system 100 not only processes the materialization of identifier data, but also converts the materialized data generated by the materialization process into an identifier, so to speak, and returns the materialized data to identifier data. This makes it possible to execute computer processing using identifier data while allowing the user to recognize that they are handling materialized data in a virtual space.

[0069] Furthermore, when the embodiment unit 140 generates embodied data based on processed identifier data, the identifier generation unit 170 generates the processed identifier data that was the basis for generating the embodied data based on predetermined identifier rules and the acquired embodied data, and can further generate identifier data. In this case, the identifier generation unit 170 may generate identifier data from the processed identifier data by, for example, performing an arithmetic operation opposite to the predetermined arithmetic operation performed by the preprocessing unit 130.

[0070] Furthermore, when the materialization unit 140 generates embodied data based on processed identifier data encrypted with predetermined key information, the identifier generation unit 170 generates the processed identifier data that was the basis for generating the embodied data based on a predetermined identifier generation rule and the acquired embodied data, and can further decrypt the processed identifier data to generate identifier data. At this time, the identifier generation unit 170 can decrypt the processed identifier data using, for example, key information corresponding to the predetermined key information used by the preprocessing unit 130.

[0071] In this case, the generation system 100 may obtain key information for decryption from the user terminal 300 via the information processing system 200, and the identifier generating unit 170 may use the key information for decryption to decrypt the processed identifier data and generate identifier data. This allows the generation system 100 to prevent identifier data from being output to a user without proper authority.

[0072] Furthermore, when the information processing system 200 includes a plurality of information processing systems 200, the generation system 100 may set whether or not the identifier generation unit 170 is to perform the identifier generation process for each of the plurality of information processing systems 200. That is, the identifier generation unit 170 may perform the identifier generation process only when the information processing system 200 that is the source of the embodied data acquired by the embodied data acquisition unit 160 is an information processing system that is permitted to perform the identifier generation process. This allows the generation system 100 to prevent the leakage of identifier data.

[0073] The setting of whether or not to perform the identifier generation process may be set for each information processing system 200 or for each type of identifier data. This allows the generation system 100 to take measures to prevent the leakage of identifier data for each information processing system 200 or for each type of identifier data.

[0074] The identifier data output unit 180 outputs the generated identifier data to an external information processing system.

[0075] The identifier data output unit 180 may output the identifier data to the information processing system 200, or may output the identifier data to the user terminal 300, for example.

[0076] Here, the identifier data output unit 180 may output the identifier data to a second user terminal of a second user different from the first user corresponding to the identifier data. This allows the first user to use the generation system 100 to exchange identifier data with the second user in the virtual space while handling embodied data in the virtual space through the generation system 100.

[0077] The exchange of identifier data between a first user and a second user will be described using a first specific example in which the first user's credit card number is used as identifier data.

[0078] First, a first user provides identifier data of a credit card number to information processing system 200 through a first user terminal. Identifier data acquisition unit 120 acquires the identifier data from information processing system 200, materialization unit 140 generates materialized data based on the identifier data, and materialized data output unit 150 outputs the materialized data to information processing system 200. Information processing system 200 materializes the materialized data in a virtual space, and a user recognizes the materialized data in the virtual space through the first user terminal. The user uses the virtual space through the first user terminal and makes a payment request to a second user in the virtual space.

[0079] The second user receives a payment request using the embodied data from the first user in the virtual space through the second user terminal. The second user requests the information processing system 200 to provide identifier data corresponding to the embodied data through the second user terminal. The information processing system 200 requests the generation system 100 to provide identifier data corresponding to the embodied data. The embodied data acquisition unit 160 acquires the embodied data from the information processing system 200, the identifier generation unit 170 generates identifier data (i.e., the first user's credit card number in this case) that was the basis for generating the embodied data based on the embodied data, and the identifier data output unit 180 outputs the generated identifier data to the information processing system 200. The information processing system 200 provides the generated identifier data to the second user terminal. The second user performs payment processing for payment with the first user based on the acquired identifier data (i.e., the first user's credit card number in this case).

[0080] Next, the exchange of identifier data between a first user and a second user will be described using a first specific example in which the identifier data is bonus data related to an exchangeable bonus. Here, the bonus data is, for example, bonus data related to a bonus that allows a user who possesses the bonus data to receive a predetermined bonus (e.g., a product) in exchange for the bonus data.

[0081] First, a first user provides identifier data of bonus data to the information processing system 200 through a first user terminal. The identifier data acquisition unit 120 acquires the identifier data from the information processing system 200, the materialization unit 140 generates embodied data based on the identifier data, and the embodied data output unit 150 outputs the embodied data to the information processing system 200. The information processing system 200 materializes the embodied data in a virtual space, and the user recognizes the embodied data in the virtual space through the first user terminal. The user uses the virtual space through the first user terminal and provides the embodied data to a second user in the virtual space. At this time, the first user may provide the embodied data, for example, as a bonus for payment with the second user.

[0082] The second user acquires embodied data from the first user in the virtual space through the second user terminal. The second user requests the information processing system 200 to provide identifier data corresponding to the embodied data through the second user terminal. The information processing system 200 requests the generation system 100 to provide identifier data corresponding to the embodied data. The embodied data acquisition unit 160 acquires the embodied data from the information processing system 200, the identifier generation unit 170 generates identifier data (i.e., bonus data in this case) that was the basis for generating the embodied data based on the embodied data, and the identifier data output unit 180 outputs the generated identifier data to the information processing system 200. The information processing system 200 provides the generated identifier data to the second user terminal. The second user enjoys a bonus based on the acquired identifier data (i.e., bonus data in this case).

[0083] In this way, through the materialization process and identification process by the generation system 100, the first user and the second user can recognize and handle the identifier data, which is so-called inorganic data, as materialized data materialized by a character, etc. in the virtual space, and the first user and the second user can also process the identifier data that was the basis for generating the materialized data.

[0084] Fig. 5 is a flowchart showing an example of processing in the generation system 100. The flowchart shown in Fig. 5 is a flowchart showing an example of processing related to generation of embodied data.

[0085] First, the identifier data acquisition unit 120 acquires identifier data (S501). The pre-processing unit 130 performs predetermined arithmetic processing on the identifier data to generate processed identifier data (S502). Note that the processing by the pre-processing unit 130 does not necessarily have to be performed.

[0086] Next, the embodied data output unit 150 generates embodied data based on the embodied rules and the identifier data or the processed identifier data (S503). The embodied data output unit 150 outputs the embodied data to an external information processing system, for example, the information processing system 200 (S504).

[0087] Fig. 6 is a flowchart showing an example of processing in the generation system 100. The flowchart shown in Fig. 6 is a flowchart showing an example of processing related to the generation of identifier data.

[0088] The embodied data acquisition unit 160 acquires embodied data (S601). The identifier generation unit 170 generates identifier data based on the identifier generation rule and the embodied data (S602). The identifier data output unit 180 outputs the identifier data to an external information processing system, for example, the information processing system 200 (S603).

[0089] The above describes one embodiment of the present invention. The generation system 100 can acquire identifier data that identifies usage data used by a user in a virtual space, generate embodied data based on the embodiment rules and the identifier data, and output the embodied data to an external information processing system. This allows the generation system 100 to embody various data in a virtual space.

[0090] Furthermore, the generation system 100 can acquire embodied data, generate identifier data that is the basis for generating the embodied data based on the identification rules and the embodied data, and output the generated identifier data to an external information processing system. This allows the generation system 100 to convert identifier data to embodied data and vice versa, allowing users to handle the identifier data as embodied data in a virtual space.

[0091] Furthermore, the generation system 100 can generate processed identifier data by performing predetermined arithmetic processing on the identifier data, and generate embodied data based on the embodiment rules and the processed identifier data. This allows the generation system 100 to embody various data in a virtual space based on appropriate processed identifier data that conforms to the embodiment rules.

[0092] Furthermore, the generation system 100 can perform an encryption process to encrypt the identifier data using predetermined key information to generate processed identifier data, and generate embodied data based on the embodiment rules and the processed identifier data generated by the encryption process. This allows the generation system 100 to embody various data in a virtual space based on the processed identifier data obtained by encrypting the identifier data.

[0093] The generation system 100 generates embodied data based on the embodied rules and processed identifier data generated by the encryption process, and can generate identifier data by decrypting the processed identifier data generated based on the embodied rules and the embodied data. This allows identifier data to be generated again from the embodied data generated based on the processed identifier data that has been encrypted.

[0094] It should be noted that the present embodiment is provided to facilitate understanding of the present invention and is not intended to limit the present invention. The present invention may be modified or improved without departing from the spirit thereof, and equivalents thereof are also included in the present invention. [Explanation of symbols]

[0095] 100 Generation system, 110 Storage unit, 120 Identifier data acquisition unit, 130 Preprocessing unit, 140 Materialization unit, 150 Materialized data output unit, 160 Materialized data acquisition unit, 170 Identification unit, 180 Identifier data output unit, 200 Information processing system, 300 User terminal

Claims

1. A computer, an identifier data acquisition unit that acquires identifier data of the user, the identifier data identifying usage data used by the user in the virtual space; an embodiment unit that generates embodiment data for embodying the identifier data in the virtual space based on predetermined embodiment rules and the identifier data; an embodied data output unit that outputs the embodied data to an external information processing system; an embodied data acquisition unit that acquires the embodied data; an identifier generating unit that generates the identifier data that is the basis for generating the embodied data based on a predetermined identification rule and the acquired embodied data; an identifier data output unit that outputs the generated identifier data to an external information processing system; A generation program to achieve this.

2. causing the computer to further realize a pre-processing unit that performs predetermined arithmetic processing on the identifier data to generate processed identifier data; the instantiation unit generates the instantiation data based on the instantiation rules and the processed identifier data. The generating program according to claim 1 .

3. the preprocessing unit performs encryption processing on the identifier data using predetermined key information corresponding to the user to generate the processed identifier data; the materialization unit generates the materialization data based on the materialization rule and the processed identifier data generated by the encryption process. The generating program according to claim 2 .

4. The computer, a pre-processing unit that performs encryption processing on the identifier data using predetermined key information corresponding to the user, and generates processed identifier data; the instantiation unit generates the instantiation data based on the instantiation rule and the processed identifier data generated by the encryption process; the identifier generation unit decodes the processed identifier data generated based on the identifier generation rule and the embodied data to generate the identifier data. The generating program according to claim 1 .

5. an identifier data acquisition unit that acquires identifier data of the user, the identifier data identifying usage data used by the user in the virtual space; an embodiment unit that generates embodiment data for embodying the identifier data in the virtual space based on predetermined embodiment rules and the identifier data; an embodied data output unit that outputs the embodied data to an external information processing system; an embodied data acquisition unit that acquires the embodied data; an identifier generating unit that generates the identifier data that is the basis for generating the embodied data based on a predetermined identification rule and the acquired embodied data; an identifier data output unit that outputs the generated identifier data to an external information processing system; A generating system comprising:

6. The computer Acquire user identifier data that identifies usage data used by the user in the virtual space; generating materialization data for materializing the identifier data in the virtual space based on predetermined materialization rules and the identifier data; outputting the embodied data to an external information processing system; obtaining the embodiment data; generating the identifier data that is the basis for generating the embodied data based on a predetermined identification rule and the acquired embodied data; outputting the generated identifier data to an external information processing system; Generation method.

Images