JP2021135588A - Object management system, object management method, and program - Google Patents

Abstract

To provide an object management technique capable of smoothly performing after-care concerning an object.SOLUTION: An object management system 100 for managing an object including a toy imitating a specific object includes: an acquisition unit 51 for acquiring object information including an object image indicating an object, and clothing information including a clothing image showing one or a plurality of pieces of clothing of the object; a screen generation unit 52 for generating a dressing change screen for displaying an object image and a clothing image in association with each other based on the object and the clothing information; and a dressing change management unit 54 for managing dressing change of clothing relative to the object by changing a clothing image displayed in association with an object image on a dressing change screen according to a user input.SELECTED DRAWING: Figure 1

Description

The present invention relates to an object management system, an object management method, and a program.

In recent years, a technique for managing the physical condition of pets such as cats using an information processing system has been known.

In this regard, Patent Document 1 describes a pet management system that manages physical condition information including changes in the weight or the degree of obesity of pets.

Patent No. 65382237

The pet management system as described in Patent Document 1 is only for managing animals, and is not premised on managing an object including a toy that imitates a specific object. Therefore, it is desired to smoothly perform aftercare related to the toy after the user acquires the toy (for example, purchase of clothing of the object, repair of the object, interaction between users who acquire the object, etc.). ..

Therefore, the present invention has been made in view of such circumstances, and an object of the present invention is to provide an object management technique capable of smoothly performing aftercare regarding an object.

The object management system according to one aspect of the present invention is an object management system that manages an object including a toy that imitates a specific object, and is an object information including an object image showing the object and an object. A dress-up screen that displays the object image and the clothing image in association with each other based on the acquisition unit for acquiring the clothing information including the clothing image showing one or more clothing of the object and the object information and the clothing information. And a dress-up management unit that manages the dress-up of clothes for the object by changing the clothing image displayed in association with the object image on the dress-up screen in response to user input. , Equipped with.

The object management method according to one aspect of the present invention is an object management method executed by a computer that manages an object including a toy that imitates a specific object, and includes an object image showing the object. Based on the step of acquiring the information and the clothing information including the clothing image showing one or more clothing of the object, and the object information and the clothing information, the object image and the clothing image are displayed in association with each other. A step of generating a dress-up screen and a step of managing the dress-up of clothes for an object by changing the clothes image displayed in association with the object image on the dress-up screen in response to user input. include.

The program according to one aspect of the present invention uses a computer that manages an object including a toy that imitates a specific object, object information including an image of the object showing the object, and one or more clothing of the object. An acquisition unit that acquires clothing information including the clothing image to be shown, a screen generation unit that generates a dress-up screen that displays the object image and the clothing image in association with each other based on the object information and the clothing information. By changing the clothing image displayed in association with the object image on the dress-up screen in response to the user input, the dress-up management unit that manages the dress-up of the clothing for the object is made to function.

In the present invention, the "part" and "device" do not simply mean a physical means, but also include a case where the functions of the "part" and "device" are realized by software. Further, even if the functions of one "part" or "device" are realized by two or more physical means or devices, the functions of two or more "parts" or "devices" can be realized by one physical means or device. It may be realized by the device.

According to the above aspect of the present invention, aftercare for an object can be smoothly performed.

It is a figure which shows the outline of the function of the object management system which concerns on one Embodiment. It is a figure which showed an example of the birth certificate of the object which concerns on one Embodiment. It is a schematic block diagram of the object management system which concerns on one Embodiment. It is a schematic block diagram of the object management device and the user terminal which concerns on one Embodiment. It is a schematic block diagram which shows an example of the functional structure of the object management apparatus which concerns on one Embodiment. It is a flowchart which shows an example of the dress-up process in the object management process which concerns on one Embodiment. It is a figure which shows an example of the dress-up screen in the output part of the user terminal which concerns on one Embodiment. It is a figure which shows an example of the dress-up screen in the output part of the user terminal which concerns on one Embodiment. It is a figure which shows an example of the dress-up screen in the output part of the user terminal which concerns on one Embodiment. It is a figure which shows an example of the dress-up screen in the output part of the user terminal which concerns on one Embodiment. It is a figure which shows an example of the message notification screen in the output part of the user terminal which concerns on one Embodiment. It is a figure which shows an example of the repair content input screen in the output part of the user terminal which concerns on one Embodiment. It is a figure which shows an example of the repair content of the object which concerns on one Embodiment of this invention. It is a diagram illustrating an example of a SNS (S ocial N etworking S ervice ) screen in the output unit of the user terminal according to an embodiment. It is a figure which shows an example of the SNS screen in the output part of the user terminal which concerns on one Embodiment.

Hereinafter, embodiments of the present invention will be described with reference to the drawings. However, the embodiments described below are merely examples, and there is no intention of excluding the application of various modifications and techniques not specified below. That is, the present invention can be implemented with various modifications (combining each embodiment, etc.) within a range that does not deviate from the gist thereof. Further, in the description of the following drawings, the same or similar parts are designated by the same or similar reference numerals. The drawings are schematic and do not necessarily match the actual dimensions and ratios. Even between drawings, parts with different dimensional relationships and ratios may be included.

FIG. 1 is a diagram showing an outline of a function provided in an object management system for managing an object including a toy imitating a specific object according to the present embodiment. The "object" includes, for example, humans and animals, as well as characters appearing in movies, cartoons, or animations. A "toy" is one that helps entertainment or guides an activity. "Toys" include, but are not limited to, children's toys, for example. In this embodiment, as an example, as an "object", a "stuffed animal" imitating a "bear" that is manually produced by one or more users (including minor or adult users) at a workshop or the like is given as an example. I will explain. However, the "object" may include items other than those actually produced by the user, or may include items purchased by the user from a third party.

As shown in FIG. 1, the object management system includes, for example, functions 1 to 4. As function 1, the object management system issues and manages the birth certificate C of the object O for each of the one or more objects produced in the workshop. For example, the object management system may take in and manage the birth certificate produced by the administrator who manages the object management system or the object management device 1 shown in FIGS. 3 and 4 described later as electronic data. The object management system issues a birth certificate on the system based on electronic data (for example, the name, weight, date of manufacture, etc.) that can be written on the birth certificate directly entered by the administrator into the object management system. May be generated by.

FIG. 2 is a diagram showing an example of a birth certificate of the object according to the embodiment. The birth certificate C shown in FIG. 1 is, for example, the birth certificate page shown in FIG. 2 (a), the identification card page shown in FIG. 2 (b), the stamp page shown in FIG. 2 (c), and FIG. The album page shown in (d) is provided. On the birth certificate page shown in FIG. 2 (a), for example, the "name", "type", "weight" (weight), "height" (length), or "date of birth" of the object ( Production date) etc. are included. The birth certificate page may further include place of birth (place of birth), image information obtained by imaging the object from different directions, and the like. According to this function 1, the object owned by the user can be managed on the system for each user.

Returning to FIG. 1, as a function 2, in the object management system, for example, when purchasing clothes to be worn on an object, it is possible to change the clothes. "Clothing" is for the object to wear. "Clothing" includes, for example, shirts, skirts, trousers, hats, necklaces and the like. According to this function 2, it is possible for the user to confirm in advance when purchasing clothing that is more suitable for the object. The function 2 (dress-up process) will be described in detail with reference to FIGS. 6 to 10.

As a function 3, the object management system can request repair of an object owned by a user (order), pay a cost (repair price) according to the repair content, and the like. For example, after making a repair request on the object management system, the user sends the object to a contractor in charge of repairing the object. Then, the user pays the repair price to the contractor via the object management system. The user then receives the repaired object from the vendor. The trader may be the same as the manager who manages the object management system or the object management device 1 shown in FIGS. 3 and 4 described later, or may be a different entity. As mentioned above, the object management system collects various information about the object when issuing the birth certificate. Therefore, the contractor in charge of repairing the object can refer to this information about the object when repairing the object. For example, the vendor can refer to an image of an object (eg, a stuffed animal) and repair it to restore its appearance. In addition, the trader can adjust the batting of the object by referring to the weight of the object. The user may receive the repaired object either before or after the user pays for the repair. The function 3 (repair management process) will be described in detail with reference to FIGS. 11 to 13.

As a function 4, the object management system provides a place where a plurality of users who own the object can interact with each other. Object management system on the object management SNS the system performs (S ocial N etworking S ervice) application may provide a place for each other a plurality of users can interact. In addition, the object management system can send planning information and event notifications to each user (user terminal) so that users can attend a place where they can bring objects and interact with each other in the real world (so-called off-line meeting). good. The function 4 (SNS management process) will be described in detail with reference to FIGS. 14 to 15.

The object management system may send a predetermined message to each user (each user terminal) as a part of after service. The predetermined message includes, for example, a congratulatory message regarding the birthday of the object, a message urging the object to be repaired, or a message regarding the season. The birthday of the object includes, for example, the date when the information of the object is registered in the object management system, the date when the object is actually manufactured, and the like. The predetermined message may be transmitted at any time or periodically.

As described above, the object management system according to the embodiment of the present invention includes at least functions 1 to 4. Therefore, after-care regarding the object after the user has acquired the object (for example, purchase of clothing of the object, repair of the object, interaction between users, notification to the user at an appropriate timing, etc.) is facilitated. It can be carried out. The specific contents of the object management system will be described below.

FIG. 3 is a block diagram showing the overall configuration of the object management system according to the present embodiment. As shown in FIG. 3, the object management system 100 is exemplified by an object management device 1 that manages an object including a toy that imitates a specific object, and n units (n is any one or more arbitrary objects). It is configured to include a user terminal 3 (an integer value) and a network N.

The object management system 100 is a so-called client / server system. The object management system 100 is realized by the n user terminals 3 which are clients and the object management device 1 communicating with each other via the network N. The network N is, for example, the Internet, a network such as a cellular phone network, LAN (L ocal A rea N etwork), or is realized by a network of a combination of these.

The object management device 1 is realized by, for example, one or a plurality of server devices. The object management device 1 may be realized by, for example, a smartphone, a game machine, or a personal computer. Further, the user terminal 3 is realized by, for example, a smartphone, a game machine, or a personal computer. In the figure, the user terminals 3a and the user terminals 3n are shown as n user terminals 3. However, in the following description, when these n user terminals 3 are described without distinction, some reference numerals are omitted and they are simply referred to as "user terminals 3".

FIG. 4 is a block diagram showing a hardware configuration of the object management device 1 and a hardware configuration of the user terminal 3 according to the embodiment of the present invention. In the figure, the code corresponding to the hardware of the object management device 1 is described without parentheses, and the code corresponding to the hardware of the user terminal 3 is described with parentheses.

Object management apparatus 1 includes, for example, a CPU (C entral P rocessing U nit ) 11, a ROM (R ead O nly M emory ) and RAM (R andom A ccess M emory ) memory 12 composed of such input A unit 13, an output unit 14, a recording unit 15, a communication unit 16, and a bus 17 are provided.

The CPU 11 executes various processes according to the program recorded in the memory 12 or the program loaded into the memory 12 from the recording unit 15.

Data and the like necessary for the CPU 11 to execute various processes are also appropriately stored in the memory 12. The CPU 11 and the memory 12 are connected to each other via the bus 17. Further, the input unit 13, the output unit 14, the recording unit 15, and the communication unit 16 are connected to the bus 17.

The input unit 13 inputs various information according to an instruction operation by the administrator of the object management device 1. The input unit 13 is composed of, for example, various buttons, a touch panel, a microphone, or the like. The input unit 13 may be realized by an input device such as a keyboard or a mouse, which is independent of the main body accommodating each other unit of the office layout presentation server 1.

The output unit 14 outputs image data and audio data. The output unit 14 is composed of, for example, a display, a speaker, or the like. The image data and audio data output by the output unit 14 are recognizable by the player as images and music from a display, a speaker, or the like.

The recording unit 15 stores various data. Recording unit 15, for example, a semiconductor memory such as a DRAM (D ynamic R andom A ccess M emory).

The communication unit 16 realizes communication with other devices. For example, the communication unit 16 communicates with the user terminal 3 via the network N.

Although not shown, a drive is appropriately provided in the object management device 1 as needed. For example, a removable medium composed of a magnetic disk, an optical disk, a magneto-optical disk, or the like may be appropriately mounted on the drive. Various data such as programs and image data read from the removable media by the drive are installed in the recording unit 15 as needed.

The hardware configuration of the user terminal 3 will be described. As shown in FIG. 3, the user terminal 3 includes, for example, a CPU 31, a memory 32, an input unit 33, an output unit 34, a recording unit 35, a communication unit 36, and a bus 37. There is. Each of these parts has the same function as each part of the same name, which is provided in the above-mentioned object management device 1 and differs only in the code.

FIG. 5 is a block diagram showing an example of the functional configuration of the object management device 1 according to the embodiment of the present invention. The object management device 1 is optionally configured to include an information processing unit 50 that executes management processing of the object, and a recording unit 15 that records information related to the management processing of the object. The recording unit 15 may be configured as another device different from the object management device 1.

The information processing unit 50 functionally includes an acquisition unit 51, a screen generation unit 52, a reception unit 53, a dress-up management unit 54, a repair management unit 55, and an SNS management unit 56. The information processing unit 50 can be realized, for example, by the CPU 11 executing a program stored in the memory 12 and the recording unit 15 shown in FIG.

The acquisition unit 51 acquires information regarding the management process of the object. The acquisition unit 51 acquires, for example, the object information OI including the object image showing the object and the clothing information CI including the clothing image showing one or more clothes of the object from the recording unit 15. The object information OI includes a plurality of object images (see the object images OG10, OG12, and OG14 shown in FIG. 10) acquired when the object is imaged with a camera or the like from a plurality of different directions. That is, the acquisition unit 51 may acquire the object information OI from an external device such as a camera. The object image may include an image acquired by actually capturing the object with a camera or the like. Further, the object image may include an image corresponding to an icon imitating the object, assuming that the object is captured by an imaging device.

The screen generation unit 52 generates various screens for output on the display or the like in the output unit 14 or the output unit 34 shown in FIG. The screen generation unit 52 generates, for example, a dress-up screen that displays the object image and the clothing image in association with each other based on the object information OI and the clothing information CI.

The reception unit 53 accepts the user's input. Specifically, the reception unit 53 receives the information input by the user in the input unit 33 of the user terminal 3 shown in FIG. 4 from the user terminal 3. For example, the touch panel of the user terminal 3 detects a state in which the user touches the touch panel and accepts the user's desired input.

The dress-up management unit 54 manages the dress-up of clothes for the object by changing the clothing image displayed in association with the object image on the dress-up screen in response to the user input received by the reception unit 53. ..

The repair management unit 55 receives and manages the contents of repair of the object. The repair management unit 55 receives the repair information RI corresponding to the repair content input by the user on the user terminal 3. Details of the "contents of repair" will be described later with reference to FIG. Further, the repair management unit 55 notifies, for example, the user terminal 3 of information for prompting the repair of the object at a predetermined timing after the acquisition unit 51 acquires the object information OI. For example, the repair management unit 55 manages the date when the information of the object is registered in the object management system, the date when the object is actually manufactured, and the like as the repair information RI. The repair management unit 55 determines the object when a predetermined period (for example, 3 years, etc.) elapses from the date when the information of the object is registered in the object management system or the date when the object is actually manufactured. The user terminal 3 may be notified of information for prompting the repair of the above. According to this configuration, it is possible to notify information for prompting repair of the object at an appropriate time when the object may be damaged after a certain period of time has passed from the manufacturing date of the object.

The repair management unit 55 may execute the notification on a regular basis (for example, every six months). According to this configuration, the user can be urged to repair the object on a regular basis.

The repair management unit 55 notifies the user terminal 3 of the object image showing the repaired object and the amount of money corresponding to the repair contents in association with each other. According to this configuration, it is possible to pay the repair cost after confirming whether the repair contents requested by the user have been properly carried out. Therefore, the user can pay the repair cost for the object with confidence.

The SNS management unit 56 (service management unit) manages an SNS (network service) in which a plurality of users who have acquired an object can interact with each other. For example, the SNS management unit 56 manages a plurality of users in association with an object image showing an object acquired by each of the plurality of users. That is, the SNS management unit 56 records the object image indicating the object acquired by each of the plurality of users in the recording unit 15 as the SNS information SI for each of the plurality of users. The SNS information SI may include IDs and passwords for each of a plurality of users who use the SNS. As the SNS information SI, the recording unit 15 may record the comments input by each of the plurality of users on the SNS in association with each of the plurality of users.

The recording unit 15 records, for example, the object information OI, the clothing information CI, the notification information NI for notifying the user terminal 3, the repair information RI, and the SNS information SI. The recording unit 15 may record the object information OI, the clothing information CI, the notification information NI, the repair information RI, and the SNS information SI for each one or a plurality of users in association with each other. The notification information NI includes information indicating the above-mentioned predetermined message (for example, a congratulatory message regarding the birthday of the object, a message urging the repair of the object, a message regarding the season, etc.). The recording unit 15 may record the notification information NI in association with the timing of transmitting the predetermined message for each predetermined message. In addition, the recording unit 15 may further record information about the user, for example, information such as the user's name, age, address, birthday, gender, or contact information (telephone number or e-mail address).

<Object management process>
An example of the object management process according to the embodiment of the present invention will be described with reference to FIGS. 6 to 15. In particular, an example (first example) of the dress-up process in the object management process according to the embodiment will be described with reference to FIGS. 6 to 10. An example (second example) of the repair management process in the object management process according to the embodiment will be described with reference to FIGS. 11 to 13. An example (third example) of the SNS management process in the object management process according to the embodiment will be described with reference to FIGS. 14 and 15. As a premise, the user downloads the application software for object management processing according to one embodiment of the present invention from, for example, a predetermined site on the network, and saves it in the user terminal 3 so that it can be executed. Then, when the user instructs the execution of the application software, the program operation based on the application software starts. Similarly, the object management device 1 also operates a program based on the application software.

(1st example: dress-up process)
FIG. 6 is a flowchart showing an example of the dress-up process according to the embodiment of the present invention.

(Step SP1)
The object management system 100 shown in FIG. 3 acquires the object information OI and the clothing information CI.

(Step SP3 and Step SP5)
The object management system 100 generates a dress-up screen based on the object information OI and the clothing information CI. The object management system 100 manages the dressing of clothes for the object by changing the clothing image displayed in association with the object image on the dressing screen in response to the received user input. In particular, steps S3 and S5 will be specifically described with reference to a plurality of examples of the dress-up screens shown in FIGS. 7 to 10.

FIG. 7 is a diagram showing an example of a dress-up screen in the output unit 34 (for example, a touch panel display) of the user terminal 3 shown in FIG. As shown in FIG. 7, on the dress-up screen S50 (home screen), at least a button B1 for trying on an object (dress-up) and a button B2 for displaying a clothing list screen are displayed. Will be done. For example, when a specific user presses the button B2 on the dress-up screen S50, the dress-up screen S9 shown in FIG. 8 to be described later is displayed. When a specific user presses the button B1 on the dress-up screen S50, the dress-up screen S52 (object selection screen) is displayed. On the dress-up screen S52, one or a plurality of object images corresponding to the one or a plurality of objects acquired by the user are displayed. When the user presses the button B3 on the dress-up screen S52, the dress-up screen S1 including the object image OG of the object corresponding to the button B3 is displayed. The screen generation unit 52 shown in FIG. 5 generates the dress-up screen S1 so as to include the category selection area R1 (type selection area) in which the category (type) of the clothing image to be displayed on the dress-up screen S1 can be selected. According to this configuration, the user can easily select a clothing category suitable for the object while checking the object image OG on the dress-up screen S1.

When the user presses (selects) the skirt button SB of the category selection area R1 on the dress-up screen S1 (touch panel display), the screen generation unit 52 causes at least a part of the plurality of clothing images corresponding to the selected category. A dress-up screen S5 is generated so as to include a clothing image display area R3 for displaying a clothing image (for example, a skirt image). According to this configuration, the user can easily select a specific clothing suitable for the object while checking the object image OG on the dress-up screen S1. In the clothing image display area R3, for example, by moving a plurality of skirt images in the horizontal direction (horizontal direction), other skirt images not displayed in the example of FIG. 7 may be displayed.

When the user presses the list button LB of the clothing image display area R3 on the dress-up screen S3, the screen generation unit 52 corresponds to the selected skirt (type) based on the pressing of the list button LB (user input). Generate a list screen S7 that executes a list display of a plurality of skirt images. According to this configuration, a list of skirt images corresponding to the selected skirt (type) can be easily confirmed, and a user can select a desired skirt image from the list of these skirt images. For example, when the user presses (selects) a specific skirt icon SIC on the list screen S7, the screen generation unit 52 generates a dress-up screen S5, which will be described later.

When the user presses (selects) a specific skirt icon SIC in the clothing image display area R3 on the dress-up screen S3, the screen generation unit 52 presses (selects) the selected specific skirt icon SIC. A dress-up screen S5 for displaying the skirt image SG corresponding to the skirt icon SIC and the object image OG in association with each other is generated. For example, a dress-up screen is generated in which a skirt image SG of a specific skirt is superimposed on an object image OG of a specific object. As shown in the dress-up screen S5, the skirt image SG may be superimposed on the object image OG as if the object were to try on a specific skirt. According to this configuration, the user can try on the object on the system with clothing that may be worn on the object.
When the "change stuffed animal" button B20 shown at the top of the dress-up screens S1, S3 and S5 shown in FIG. 7 is pressed, the dress-up screen S52 (object selection screen) is displayed on the output unit 34 of the user terminal 3. It will be displayed again. For example, when the "change stuffed animal" button B20 on the dress-up screen S5 is pressed, the dress-up screen S52 is displayed. Then, when the user selects another object (for example, the object corresponding to the "original 2") on the dress-up screen S52, the dress-up is made by superimposing the skirt image SG on the object image corresponding to the "original 2". A screen may be generated. That is, the skirt image SG superimposed on the object image OG on the dress-up screen S5 is temporarily stored, and the skirt image SG is superimposed on the object image corresponding to the new object.

FIG. 8 is a diagram showing an example of a dress-up screen in the output unit 34 of the user terminal 3 shown in FIG. As shown in FIG. 8, for example, on the dress-up screen S9 (home screen), a list of shirt images (clothing images) corresponding to shirts (clothes) for a specific user to wear on an object is displayed. Has been done. Then, when the user presses (selects) the skirt button SB of the category selection area R5 on the dress-up screen S9, the screen generation unit 52 displays a list of a plurality of skirt images corresponding to the selected category. To generate. Next, when the user presses a specific skirt icon SIC on the dress-up screen S11, the screen generation unit 52 displays the details of the specific skirt corresponding to the specific skirt icon SIC (for example, "product name", "product". Generate a dress-up screen S13 that displays "details" or "size"). When the user presses the fitting button FB on the dress-up screen S13, the dress-up screen S14 (object selection screen) is generated. Further, when the user presses B5 on the dress-up screen S13, a purchase screen for purchasing a skirt corresponding to the specific skirt image SG is generated. When the user presses the button B7 on the dress-up screen S14, the dress-up screen S5 (for example, the dress-up screen S5 shown in FIG. 7) including the object image OG of the object corresponding to the button B7 is displayed.

FIG. 9 is a diagram showing an example of a dress-up screen in the output unit 34 of the user terminal 3 shown in FIG. As shown in FIG. 9, when the user presses, for example, the shirt button SHB of the category selection area R7 on the dress-up screen S15 in which the skirt image SG is superimposed on the object image OG, the screen generation unit 52 is selected. The dress-up screen S15 is generated (updated) so as to include the clothing image display area R9 for displaying at least a part of the shirt images corresponding to the category (shirt).

When the user presses a specific shirt icon SHIC in the clothing image display area R9 on the dress-up screen S15, the screen generation unit 52 presses the specific shirt icon SHIC to display the shirt image corresponding to the specific shirt icon SHIC. A dress-up screen S17 for displaying the SHG and the object image OG in association with each other is generated. According to this configuration, the user can try on the object on the system a plurality of different types of clothing (shirt and skirt in the example of FIG. 9) that may be worn on the object. In addition, a plurality of clothes of the same type may be displayed in association with the object image.

The dress-up management unit 54 shown in FIG. 5 is, for example, when one or a plurality of clothing images (for example, shirt image SHG and skirt image SG) are displayed in association with the object image OG on the dress-up screen S17. When the user presses the favorite button FVB (user input), the one or more clothing images are associated with the object image OG and registered as favorites. According to this configuration, it is possible to register one or a plurality of types of one or a plurality of clothing (clothing images) desired by the user.

When the user presses the coordination button CB of the category selection area R7 on the dress-up screen S17, the screen generation unit 52 coordinates the coordination registered by the user in the past, that is, one or a plurality of types desired by the user. A screen displaying a list of combinations of a plurality of clothes (clothes images) may be generated. According to this configuration, it is possible to easily confirm the coordination registered as a favorite by the user in the past.

The favorite registration may be managed for each clothing category. For example, the screen generation unit 52 may generate a list screen that displays a list of only clothes (clothes images) registered as favorites, for example, shirts (shirt images). According to this configuration, it is possible to easily confirm the coordination registered as a favorite by the user in the past, that is, a specific single clothing (clothing image).

Based on the user input, the screen generation unit 52 is a specific clothing image among one or a plurality of clothing images (for example, shirt image SHG and skirt image SG) displayed in association with the object image OG on the dress-up screen S17. When an image (for example, shirt image SHG) is selected, a purchase screen for purchasing a shirt corresponding to the shirt image SHG is generated. For example, as a user input, the dress-up is performed by maintaining the state in which the user's finger is in contact with the area where the shirt image SHG is displayed on the dress-up screen S17 for a predetermined period (so-called “long press”). The screen S17 may be changed to the shirt purchase screen. The user input is not limited to "long press" and may include other screen operations. According to this configuration, the desired clothing grasped on the dress-up screen can be purchased with a relatively simple operation. The object management system 100 may execute clothing purchase processing (for example, clothing ordering processing, user billing processing, clothing shipping processing, etc.). Further, the object management system 100 may delegate the clothing purchase process to another system.

Further, when the user presses the detail button DB on the dress-up screen S17, the screen generation unit 52 displays the detailed information of the clothes corresponding to the shirt image SHG and the skirt image SG displayed on the dress-up screen S17. The screen S19 may be generated. The user can proceed to the respective purchase screens of the shirt and the skirt from the detail screen S19. For example, when the user presses the button B11 on the detail screen S19, the purchase screen for purchasing the skirt corresponding to the skirt image SG may be displayed. Further, when the user presses the button B9 on the detail screen S19, the dress-up screen S13 shown in FIG. 8 may be displayed.

FIG. 10 is a diagram showing an example of a dress-up screen in the output unit 34 of the user terminal 3 shown in FIG. As shown in FIG. 10, the screen generation unit generates confirmation screens S23, S25, and S27 for confirming the dressing status of the objects from a plurality of different directions based on the images of the plurality of objects. Specifically, when the user presses the button B10 on the confirmation screen S23 including the front object image OG10, the confirmation screen S25 including the side object image OG12 is displayed. When the user presses the button B12 on the confirmation screen S25, the confirmation screen S27 including the back object image OG14 is displayed. When the user presses the button B14 on the confirmation screen S27, although not shown, a confirmation screen including the side object image when the image is taken from the side opposite to the side object image OG12 may be displayed. According to this configuration, it is possible to easily confirm the dressing status of the object from a plurality of different directions.

According to the first example, the object management system 100 changes the clothes image displayed in association with the object image on the dress-up screen in response to the received user input, thereby changing the clothes on the object. To manage. In this way, aftercare related to the object can be smoothly executed.

(Second example: repair management process)
FIG. 11 is a diagram showing an example of a message notification screen in the output unit 34 of the user terminal 3 shown in FIG. After the acquisition unit 51 acquires the object information OI, the repair management unit 55 shown in FIG. 5 notifies the user terminal 3 of a message (information) for prompting the repair of the object at a predetermined timing. As shown in FIG. 11, in the output unit 34 of the user terminal 3, "Happy 3rd birthday, Izumi-chan" including the object "Name: Izumi-chan" shown in FIG. 2. Three years have passed since the birth. The message notification screen S31 including the message "Why don't you come to the examination once?" Is displayed. The output unit 34 of the user terminal 3 may output a message for urging the repair of the object as voice.

FIG. 12 is a diagram showing an example of a repair content input screen in the output unit 34 of the user terminal 3 shown in FIG. As shown in FIG. 12, when the user operates the user terminal 3 to input the repair content, the repair content information corresponding to the repair content is transmitted to the object management device 1 shown in FIG. In this way, the repair management unit 55 receives and manages the contents of repair of the object.

FIG. 13 is a diagram showing an example of the contents of repair of the object according to the embodiment of the present invention. As shown in FIG. 13, the content of the repair includes the repair of the eyes and nose of the object as "ophthalmology / otolaryngology". As an example, "ophthalmology / otolaryngology" was mentioned, but in the case of a teddy bear, "internal medicine" is the repair of the bead bag inside the stuffed animal, and "surgery" is the repair of the damaged part of the stuffed animal. Alternatively, "dermatology" includes repairing the hair loss portion of the stuffed animal. In addition to the above, the repair contents may include cleaning of the object, brushing, and the like.

The object management system 100 may execute a billing process for repairing the object. For example, the object management system 100 may send a quotation created based on the received repair contents to the user terminal 3. Further, the object management system 100 may notify the user terminal 3 of the amount of money for the repair of the object and receive the payment for the repair.

According to the second example, the object management system 100 executes various processes related to the repair of the object. Therefore, aftercare related to the object can be smoothly executed.

(Third example: SNS management process)
14 and 15 are diagrams showing an example of an SNS screen in the output unit 34 of the user terminal 3 shown in FIG. The SNS management unit 56 records and manages a plurality of users and an object image indicating an object acquired by each of the plurality of users as SNS information in the recording unit 15. As shown in FIG. 14A, the screen generation unit 52 may generate a friend application screen S37 for a specific user to connect with another user as a friend on the SNS based on the SNS information. For example, it is possible for a specific user to apply for a friend on SNS to find another user who has a favorite profile. On the friend application screen S37, it is possible to input a self-introduction comment, and it is also possible to display an object image OG of an object acquired by oneself.

The screen generation unit 52 is an exchange screen for a plurality of users who have acquired an object to interact with each other, and includes an object image associated with each of the plurality of users, comments of each of the plurality of users, and a comment of each of the plurality of users. Generate an exchange screen that is displayed in association with. For example, as an exchange screen, the screen generation unit 52 has an exchange screen S39 for exchanging comments between two users shown in FIG. 14 (b), and three or more users shown in FIG. 15 (a). An exchange screen S41 for exchanging comments between them may be generated. According to this configuration, it is possible to easily interact with each other among a plurality of users.

As shown in FIG. 15B, the SNS management unit 56 can also guide various events to a plurality of users participating in the SNS via the event notification screen S43.

According to the third example, the object management system 100 manages an SNS in which a plurality of users who have acquired an object can interact with each other. Therefore, aftercare related to the object can be smoothly executed.

(Other embodiments)
Each of the above embodiments is for facilitating the understanding of the present invention, and does not limit the interpretation of the present invention. The present invention can be modified / improved (for example, combining each embodiment, omitting a part of the configuration of each embodiment) without departing from the spirit thereof, and the present invention also includes an equivalent thereof. Is done.

For example, as described above, the object management device 1 has, as a functional configuration, an acquisition unit 51, a screen generation unit 52, a reception unit 53, a dress-up management unit 54, a repair management unit 55, and an SNS management unit. 56 and. However, at least some of these functions may be provided by the user terminal 3 shown in FIG. That is, the "object management system" may include only the object management device 1, the user terminal 3, or the object management device 1 and the user device as shown in FIG. In some cases, both of 3 are included.

For example, the size of one or more clothing images displayed in association with the object image on each of the various screens S5, S15, S17, S23, S25 and S27 of FIGS. 7, 9 and 10 is enlarged or reduced. It is possible. For example, the user reduces the display size of the clothing image by bringing the user's two fingers in contact with the dress-up screen on the output unit 34 (for example, the touch panel display) of the user terminal 3 while keeping the two fingers in contact with the screen. Alternatively, the display size of the clothing image can be enlarged by moving the two fingers away from the screen while keeping them in contact with the screen. According to this configuration, it is possible to easily confirm the feeling of size (for example, large or small) of the clothing to be worn on the object.

1 ... Object management device, 3 ... User terminal, 11 (31) ... CPU, 12 (32) ... Memory, 13 (33) ... Input unit, 14 (34) ... Output unit, 15 (35) ... Recording unit, 16 (36) ... Communication Department, 17 (37) ... Bus, 51 ... Acquisition Department, 52 ... Screen Generation Department, 53 ... Reception Department, 54 ... Dress-up Management Department, 55 ... Repair Management Department, 56 ... SNS Management Department, 100 ... Object management system

Claims (13)

An object management system that manages objects including toys that imitate specific objects.
An acquisition unit for acquiring object information including an object image showing the object and clothing information including a clothing image showing one or more clothes of the object.
A screen generation unit that generates a dress-up screen for displaying the object image and the clothing image in association with each other based on the object information and the clothing information.
It is provided with a dress-up management unit that manages the dress-up of the clothing for the object by changing the clothing image displayed in association with the object image on the dress-up screen in response to user input. ,
Object management system. The screen generation unit generates the dress-up screen so as to include a type selection area in which the type of the clothing image to be displayed on the dress-up screen can be selected.
The object management system according to claim 1. The screen generation unit generates the dress-up screen so as to include a clothing image display area for displaying at least a part of the clothing images corresponding to the selected type.
The object management system according to claim 2. The screen generation unit generates a list screen that executes a list display of a plurality of the clothing images corresponding to the selected type based on the user input.
The object management system according to claim 2 or 3. When the dress-up management unit detects the user input when one or more of the clothing images are displayed in association with the object image on the dress-up screen, the dress-up management unit displays the one or more clothing images. Register in association with the object image,
The object management system according to any one of claims 1 to 4. When a specific clothing image is selected from the one or a plurality of the clothing images displayed in association with the object image on the dress-up screen based on the user input, the screen generation unit specifies the specific clothing image. Generate a screen to purchase clothing corresponding to the clothing image of
The object management system according to any one of claims 1 to 5. The object image includes a plurality of object images acquired when the object is imaged from a plurality of different directions.
The screen generation unit generates a screen for confirming the dressing status of the object from a plurality of different directions based on the images of the plurality of objects.
The object management system according to any one of claims 1 to 6. It also has a repair management department that accepts and manages the repair contents of the object.
After the acquisition unit acquires the object information, the repair management unit notifies the information for prompting the repair of the object at a predetermined timing.
The object management system according to any one of claims 1 to 7. The repair management unit notifies the image of the object showing the object after the repair in association with the amount of money corresponding to the content of the repair.
The object management system according to claim 8. It also has a service management unit that manages network services that allow multiple users who have acquired the object to interact with each other.
The service management unit manages the plurality of users in association with the object image showing the object acquired by each of the plurality of users.
The object management system according to any one of claims 1 to 9. The screen generation unit is an exchange screen for a plurality of users who have acquired the object to interact with each other, and the object image associated with each of the plurality of users and each of the plurality of users. Generate an exchange screen that is displayed in association with the comment of
The object management system according to claim 10. An object management method executed by a computer that manages an object including a toy that imitates a specific object.
A step of acquiring object information including an object image showing the object and clothing information including a clothing image showing one or more clothes of the object.
A step of generating a dress-up screen for displaying the object image and the clothing image in association with each other based on the object information and the clothing information.
Including a step of managing the dressing of the clothing with respect to the object by changing the clothing image displayed in association with the object image on the dressing screen in response to user input.
Object management method. A computer that manages objects, including toys that imitate specific objects
An acquisition unit for acquiring object information including an object image showing the object and clothing information including a clothing image showing one or more clothes of the object.
A screen generation unit that generates a dress-up screen for displaying the object image and the clothing image in association with each other based on the object information and the clothing information.
A dress-up management unit that manages the dress-up of the clothing for the object by changing the clothing image displayed in association with the object image on the dress-up screen in response to user input.
A program that works.

Images