JP2007207144A - Equipment management system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To promote user registration of used equipment to facilitate acquisition of a synthetic operation history. <P>SOLUTION: When a certain user performs the user registration of the holding equipment 21, a user record 31 and an equipment record 33 are associated inside a database 13. When the registered user transmits transfer requirement to an equipment management server 11 when desiring to resell the equipment 21 afterward, the equipment management server 11 sets a transfer flag inside the equipment record 33. When the transfer flag is set, the equipment management server 11 complies with requirement of the user registration when a person having taken over the equipment 21 from the registered user requires the user registration about the equipment 21. When the registered user of the equipment 21 is changed, the equipment management server 11 takes operation information inside the equipment record 33 before the registered user change in new operation information after the change to produce synthetic operation information. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a computer system for managing user information and operation information related to devices that can be transferred from one user to another.

  There is a second-hand goods market for various devices such as electronic printers and personal computers. For example, regarding resale of used printers, a system has been proposed that calculates a trade-in price of the printer, a used sales price, and the like from usage information accumulated in the printer (see, for example, Patent Document 1).

JP 2004-66493 A

  A user registration system in which a user who purchases a device registers with the device manufacturer that the user is the device user can receive various support services for the device from the device manufacturer. Adopted by various equipment manufacturers. This user registration system is widely used for equipment sold as new, but currently it is not used much for used equipment sold in the used market. However, there are more opportunities for users to use a used device rather than a new device to receive support services based on user registration. Nevertheless, no special technique has been proposed to promote user registration of used equipment.

  In addition, when a device manufacturer intends to provide support services to users who have purchased second-hand equipment, not only the operation information of the equipment used by the current user but also the operation information of past user use If the integrated operation history from the beginning of the device to the present can be grasped, the state of the device can be analyzed more accurately, and the quality of the support service should be improved. However, no specific technique has been proposed for enabling an integrated operation history to be grasped from the beginning to the present of the devices that are resold in the secondhand market.

  Furthermore, in order to grasp the integrated usage information of equipment that will be resold in the second-hand market, when that equipment is resold from the previous user to the next user, the fact of the resale is timely and timely. It is important that the equipment manufacturer can understand. However, no specific technique has been proposed so far that makes this easy.

  Accordingly, an object of the present invention is to promote user registration for used equipment, facilitate the understanding of an integrated operation history of used equipment, and contribute to improving the quality of support services for used equipment users.

The device management system according to the present invention is:
A plurality of device records respectively corresponding to a plurality of devices and a plurality of user records respectively corresponding to a plurality of users are accumulated, and the device records of each device indicate whether or not each device is a transfer target. A device management database containing transfer information;
A device management server capable of communicating with a plurality of user clients respectively used by a plurality of users and accessing the device management database;
User registration request means that is provided to a user client used by each user and transmits a user registration request for the device owned by each user to the device management server;
Transfer notification means provided to the user client of each user and transmitting a transfer notification for the device owned by each user.

The device management server
User registration request receiving means for receiving the user registration request from any user client;
Transfer request receiving means for receiving the transfer request from any user client;
When a user registration request for a certain device held by a certain user is received, the transfer information in a device record corresponding to the certain device is checked, and the checked transfer information is determined to be the certain device. Indicates that it is a transfer target, the checked transfer information is reset so as to indicate that the certain device is no longer a transfer target, and a device record corresponding to the certain device User registration means for setting a first association between the user record corresponding to the certain user and indicating that the certain user is a registered user of the certain device;
After the first association is set between the device record corresponding to the certain device and the user record corresponding to the certain user, a transfer notification for the certain device held by the certain user is issued. And a transfer notification registration unit for resetting the transfer information in the device record corresponding to the certain device so as to indicate that the certain device is a transfer target.

  According to the device management system of the present invention having the above configuration, when a certain user transmits a user registration request for a certain device owned by the user from the user client used by the user to the device management server, the device management server Refers to the transfer information in the device record of the device in the device management database to check whether the device is currently targeted for transfer, and as a result, the device is currently targeted for transfer. Then, the device management server registers the user as a registered user of the device in the device management database by forming a first association between the user record of the user and the device record of the device. At the same time, the device management server resets the transfer information in the device record of the device to indicate that the device is no longer the target of transfer. In this way, the user registration of the user for the device is completed.

  Thereafter, if the user intends to transfer the device to another person, the user can transmit a transfer notification about the device from his user client to the device management server. When the device management server receives the transfer notification, the device management server resets the transfer information in the device record of the device to indicate that the device has been transferred. As a result, another person can register as a user for the device. Therefore, if another user who has transferred the device from the user transmits a user registration request for the device to the device management server, the transferred user is registered as a registered user of the device.

  In this way, when a certain device is transferred from one user to another, the user can use the device database as a registered user of the device when he / she owns the device. Can be registered. In the device management database, status information indicating whether the device is currently targeted for transfer (that is, whether it is on the market) and registered user information indicating who is the registered user of the device. Can be clearly managed.

  In a preferred embodiment, each of the user registration request unit and the transfer notification unit is a computer program, which is stored in advance in a storage device built in or attached to each device, and from the storage device, It can be installed in a user client used by a user who acquires each device. Therefore, the procedure for user registration and transfer notification for a certain device is performed only by the user who obtains the device by installing the program from the storage device built in or attached to the device into his user client. A person who does not have the equipment can do it. Thereby, user registration and transfer notification by a fake user are prevented. In addition, when the user transfers the device to another user, the program attached to the device is also transferred to the transferee user. User registration and transfer notification procedures.

  In a preferred embodiment, the device record corresponding to each device in the device management database includes operation information indicating a state relating to the operation of each device. The device management server continuously and repeatedly acquires the operation data of each device, and integrates the acquired operation data of each device and the operation information in the device record corresponding to each device. In addition, the system further includes an operation information update unit that creates new operation information and updates the operation information in the device record corresponding to each device to the new operation information. When the registered user of each device is changed, the operation information update unit supports not only the operation data acquired after the registered user is changed, but also each device before the registered user is changed. The old operation information set in the device record is also taken in, and the new operation information is created.

  Therefore, when a certain device is transferred from one user to another, the operation information in the device record of the device includes not only the operation information from the last user but also the operation information from the previous user. However, integrated operation information will be recorded. Therefore, each user can receive a better quality support service that is more appropriate to the actual state of the device, based on integrated operation information that reflects the usage results of all the users so far.

  In a preferred embodiment, the device management server sets the first user association between the device record corresponding to the certain device and the user record corresponding to the certain user, and then the certain user. When a transfer notification for the certain device is received, a customer key is created, the created customer key is assigned to the certain user, and the created customer key is used by the certain user. It further has a means to transmit to a user client. When a user client used by each user receives a customer key assigned to each user from the device management server, the user client stores the received customer key in a predetermined storage device inside or outside each user client. Means for searching for a customer key assigned to each user from the predetermined storage device when the user registration request is transmitted, and if the customer key assigned to each user is found, the user registration Means for transmitting the found customer key together with the request to the device management server. In addition, the device management server may be owned by the certain user when the first association exists between a device record corresponding to the certain device and a user record corresponding to the certain user. When a customer key assigned to the certain user is received together with a user registration request for another device, between the device record corresponding to the certain device and the user record corresponding to the certain user. The first association existing in the device is deleted, and between the device record corresponding to the device and the user record corresponding to the user, the user Means for setting a second association indicating that the user is a user.

  According to this preferred embodiment, when a user who is currently a registered user of a certain device transmits a transfer notification about the device to the device management server, the device management server, as described above, The transfer information in the record is reset and the device is changed to the transfer target. In addition, a new customer key is assigned to the user, and the customer key is stored in the user record of the user. Register and send to the user client of the user. The user client that has received the customer key stores the customer key in a predetermined storage device inside or outside the user client. Thereafter, when the user transfers the device to another person and obtains another device, a user registration request for the other device is transmitted from his user client to the device management server. Can do. At that time, the user client transmits the stored customer key to the device management server together with a user registration request for the newly acquired device. Then, the device management server finds out the user record of the user based on the customer key, and erases the first association existing between the found user record of the user and the device record of the previous device. Instead, by setting a second association between both records, it is registered that the user is no longer a registered user of the device but a past user.

  As a result, when a user buys a new device, the device management database manages the history of the device possession so far. By utilizing this equipment possession history, for example, equipment manufacturers can provide more advantageous support services to users who love more of their products, and what kind of equipment is popular. Information useful for sales and product development can be obtained, which is advantageous for both equipment users and equipment manufacturers.

  Further, in the preferred embodiment, the customer key can be used as a one-time key that can be used only once, so that the fact of product replacement can be accurately grasped.

  According to the present invention, it is possible to facilitate user registration for used equipment and to easily grasp the integrated usage history of used equipment, and thus contribute to improving the quality of support services for used equipment users. can do.

  FIG. 1 shows the overall configuration of a device user information management system according to an embodiment of the present invention.

  As shown in FIG. 1, there is a device management server 11 operated by a device manufacturer, for example, for managing information on each device to be managed and information on users of each device. The device management server 11 has a device management database 13. The device management database 13 includes a user database 15 for storing user information that is information unique to each user, and a device that is information unique to each device. A device database 17 for storing information is included.

  Although there is no particular limitation on the type of device managed by the device management server 11, in this embodiment, the type of device to be managed is assumed to be a computer peripheral device (for example, an electronic printer) as an example. Although the number of devices managed by the device management server 11 is not limited, FIG. 1 typically shows only one certain device (hereinafter referred to as the first device) 21, Illustration of managed devices is omitted.

  A person who owns the first device 21 (hereinafter referred to as “first user”) sends a certain client computer (hereinafter referred to as “first user”) in order to send the device information of the first device 21 and the user information of the user to the device management server 11. 19) (referred to as “first user client”). The first user client 19 can communicate with the device management server 11 through a communication network (not shown) such as the Internet. The first device 21 and the first user client 19 are interconnected and can communicate with each other in this embodiment (although not necessarily).

  The first device 21 generates operation data 25 representing information on occurrence and change of various states related to its operation (for example, use start date, operation amount, consumable usage amount, failure / deterioration history, etc.) at a predetermined timing. I remember it. The first device 21 has a device management program 23 for transmitting the latest operation data 25 to the device management server 11, and can automatically execute this at a predetermined timing. In this embodiment, the device management program 23 transmits the operation data 25 to the device management server 11 through the first user client 19 (although this is not necessarily the case). Since the first device 21 and the first user client 19 can communicate with each other, the device management program 83 may be executed not in the first device 21 but in the first user client 19.

  The first device 21 also has a user registration program (or a user registration program installed on an arbitrary user client) that is a computer program for transmitting a user registration request for the first device 21 to the device management server 11. The installer program 27) is attached. The user registration program (or installer program) 27 may be stored in a storage device built in the first device 21 or stored in a storage device such as a CD-ROM attached to the first device 21. It may be. In any case, the first user obtains the first device 21 to obtain the user registration program (or installer program) 27 attached thereto, and the user registration program (or installer program) 27. Can be used to install the user registration program 29 for the first device 21 in the first user client 19 and execute the user registration program 29 installed in the first user client 19 to manage the device. By communicating with the server 11, user registration for the first device 21 can be performed with respect to the device management server 11.

  When the first user performs user registration for the first device 21 with respect to the device management server 11, the device management server 11 has a user record unique to the first user (hereinafter referred to as “user record”) that records the user information of the first user. , “First user record”) 31, and the first user record 31 is registered in the user database 31. On the other hand, a device record 33 (hereinafter referred to as “first device record”) unique to the first device 21 in which device information of the first device 21 is recorded is stored in the device database 33. Here, the first device record 33 is already registered in the device database 33 by, for example, a device manufacturer or another predetermined authority when the first device 21 first enters the market. The first user record 31 and the first device record 33 are associated with each other.

  The device management server 11 uses the first device record 33 and the first user record 31 that are associated with each other, and the device information of the first device 21 and the user information of the first user who is the user of the first device 21. Manage. In addition, when the first device 21 is transferred (for example, resold) from the first user to another person (hereinafter referred to as “second user”), the device management server 11 determines the second user's The user record 77 (see FIG. 4) and the first device record 33 are managed in association with each other. In the first device record 33, the operation information during the usage period of the first user and the trial period of the second user are used. It is possible to manage integrated operation information combined with other operation information. These management functions will be described in detail later.

  FIG. 2 illustrates the user record structure of each user and the device record structure of each device.

  As shown in FIG. 2, the user record 35 of each user stored in the user database 15 includes a user ID 37, a possessed device ID 39, a customer key 41, transmission source data 43, user detailed information 45, a reward score 47, and A device history 49 and the like are included.

  The user ID 37 is a user identification code corresponding to the user record 35. The possessed device ID 39 is identification information of a device currently owned by the user. In FIG. 2, only one owned device ID 39 is shown, but a plurality of owned device IDs 39 may be included in the user record 35, and the plurality of owned device IDs 39 respectively correspond to a plurality of corresponding devices of the same user. Means that you currently own.

  The customer key 41 is a code assigned to the user indicating that the user has owned the product of the device manufacturer in the past (that is, the customer is already a customer of the device manufacturer). In this embodiment, the customer key 41 is issued to the user from the device management server 11 when the user tries to transfer the owned device to another person (although this is not necessarily the case). A one-time key that can be used and stored in the user client used by the user.

  The transmission source data 43 transmits information such as a user registration request from the client computer of the user (for example, the first user client 19 shown in FIG. 1 in the case of the first user) to the device management server 11. Address data used as a transmission source of the user or the client computer is sometimes used.

  The user detailed information 45 is detailed personal information such as the address and name of the user. The reward point 47 indicates the degree or type of various rewards that can be provided to the user by the device manufacturer (for example, a discount service for purchasing devices or consumables, a gift of a special product or a special support service). It is a score to decide. In general, the higher the reward score 47, the more expensive the reward that can be provided.

  The device history 49 is a history of devices that the user has held in the past (for example, device IDs and usage periods of devices that have been held in the past).

  On the other hand, the device record 51 of each device stored in the device database 17 includes a device ID 55, a registered user ID 57, a transfer flag 59, operation information 61, a user history 63, and the like.

  The device ID 55 is an identification code unique to the device. The registered user ID 57 is a user ID for identifying a user who is a registered user of the device.

  The transfer flag 59 is a flag that indicates whether or not the device is currently being transferred (resold) (that is, whether or not the user of the device wants to transfer the device to another person). As will be described later, when the current user of the device registers the transfer notification in the device management server 11, the transfer flag 59 is set to indicate that the device is a transfer target, and then the device is transferred to another person. Is transferred (ie, when the transferee has registered as a user for the device), the transfer flag 59 is reset to indicate that the device is not to be transferred. Note that the transfer flag 59 is set at the initial stage when the device is first put on the market as a new product.

  The operation information 61 is information (for example, a use start date, an operation amount, a consumable usage amount, a failure / deterioration history, etc.) indicating the occurrence or change of various states related to the operation of the device. The operation information 61 is operation data transmitted repeatedly at a predetermined timing from a device management program of the device (for example, in the case of the first device 21 shown in FIG. 1, the device management program 83 in the first device 21). Is created by the device management server 11. In accordance with the principles of the present invention, when a device is transferred from one user to another, it is not only the operation data acquired during the subsequent user's use period, but also the device at the end of use of the previous user. The old operation information 61 recorded in the record 51 is also taken in, new device information is created, and this is recorded again in the device record 51, so that the previous user's usage period and the subsequent user's usage period Integrated operation information over the entire use period including the above is held in the operation information 61 in the device record 51.

  The user history 63 is a history of a user who has owned the device in the past (for example, a user ID or a usage period of a past user).

  As shown in FIG. 2, each user's user record 35 is a device record 51 having the same device ID 55 as the possessed device ID 39 by the possessed device ID 39 (that is, the device record of the device currently owned by the user) 51. Are logically associated with each other. Further, the user record 35 of each user is a device record having the same device ID as the device ID in the device history 49 (that is, the device record of the device that the user has held in the past) 53 by the device history 49 in the user record 35. Are logically associated with each other. On the other hand, the device record 51 of each device is logically converted into a user record 35 (that is, a user record of the user who currently owns the device) having the same user ID 37 as the registered user ID 57 by the registered user ID 57 therein. Associated. In addition, the device record 51 of each device includes a user record 65 having the same user ID as the user ID in the user history (that is, a user record of a user who has held the device in the past) 65 based on the user history 63 therein. , Logically related.

  In this manner, the device record 51 of the device currently owned by the user is associated with the user record 35 of each user. If the device is a second-hand product that has been transferred, the device record 51 captures not only the operation information of the device for the current user's use period but also the operation information of the past user's use period. Integrated operating information is recorded. Therefore, the device manufacturer can provide the user with a higher quality support service based on the integrated operation information of the device.

  The user record 35 of each user is also associated with the device record 53 of the device that the user has held in the past. Therefore, the device manufacturer can grasp the history of its products used by the user so far, and the service provided to the user can be obtained only by the information of the device currently owned by the user. In addition, it is possible to make adjustments by taking into account the information of the devices held in the past. For example, among a plurality of users who currently have the same device, adjustments can be made such that a user who owns more products in the past provides more reward points. Such service coordination can be an incentive for the user to facilitate user registration.

  In addition, the device record 51 of each device is associated not only with the user record 35 of the current user but also with the user record 65 of the past user. The user records 35 and 65 of the respective users record the detailed user information of the respective users, and are associated with the device records of the devices owned by the respective users at present and in the past. By analyzing this information, device manufacturers can purchase a variety of market information (for example, which devices are popular in the used goods market, which devices are purchased by which users, what devices are purchased) The user can obtain what kind of equipment to purchase next, etc.), and can use it for future product development, for example.

  Next, the operation of the device management system according to the embodiment of the present invention will be described. In this description, the above-mentioned first user purchases the above-mentioned first device, then resells the first device to the above-mentioned second user, and then the first user makes another device (hereinafter referred to as “the first device”). It is assumed that the user has purchased 2 devices).

  1 and 3 to 5 show a data communication procedure in the present system in the above case. In particular, FIG. 1 shows a data communication procedure when a first user registers as a first device. FIG. 3 shows a data communication procedure when the first user intends to resell the first device to another person. FIG. 4 shows a data communication procedure when the second user registers as the first device. Further, FIG. 5 shows a procedure of data communication when the first user performs user registration for the second device.

  FIG. 6 shows the flow of information processing of the device management program for each device to be managed. FIG. 7 shows the flow of information processing of the user registration program of each user client. 8 and 9 show the information processing flow of the device management server by connecting the two diagrams.

  Hereinafter, the operation of the system according to the present embodiment in the above case will be described with reference to these drawings.

  First, the operation when the first user who purchased the first device 21 performs user registration of the first device 21 will be described. As shown in step (1) in FIG. 1, a user registration program 19 for the first device 21 is stored in the first user client 19 by using a user registration program (its installer program) 27 attached to the first device 21. Is installed. The user registration program 19 for the first device 21 has the device ID of the first device 21 or can communicate with the first device 21 to obtain the device ID of the first device 21. Note that the installation procedure of the user registration program 29 may be performed accompanying the installation of a device driver (not shown) of the first device 21 to the first user client 19, or , It may be performed independently.

  Thereafter, the first device 21 and the first user client 19 are connected, their power is turned on, and the device management program 23 in the first device 21 communicates with the device management server 11 (in this embodiment, this communication is Once it is possible to do this through the first user client 19 (which is not necessarily the case), it will be shown in the first device 21 as shown in steps (2) and (3) in FIG. The device management program 23 is activated at a predetermined intermittent timing (for example, periodically) to obtain the latest operating data 25 held in the first device 21, and step (3) and FIG. As shown in step S1 in FIG. 6, a connection request including the device ID of the first device 21 is transmitted to the device management server 11, and if connection to the device management server 11 is established, step (3) in FIG. As shown in and Figure 6 at step S2, and transmits the acquired operation data 25, the device management server 11 via the first user client 19.

  The device management server 11 receives the connection request and operation data 25 from the device management program 23 as shown in step (4) in FIG. 1 and step S31 in FIG. 8, and as shown in step S32 in FIG. The device record 33 (that is, the device record of the first device 21) having the device ID included in the received connection request is read, and the current contents of the operation information 61 in the device record 33 are read. The contents of the received operation data 25 are integrated to create new contents of the operation information 61, and the contents of the device record 33 in the device database 17 are updated so as to be the new contents. Further, the device management server 11 checks whether or not the transfer flag 59 in the device record 33 of the first device 21 is set as shown in step S33 in FIG.

  Here, the first device 21 is new and sold to the first user, or it is resold to the first user as a second-hand product, but before the resale is performed, the previous user is the first device. It is assumed that the transfer notification registration described later for 21 has been performed. In this case, the transfer flag 59 in the device record 33 of the first device 21 is set at this stage (this state is that the first device 21 is currently a transfer target and is assigned by the transferee. Meaning that the user registration has not been done yet). Therefore, the check result shown in step S34 in FIG. 8 is NO, and the control in the device server 11 proceeds to step S35 in FIG. 8 and step (5) in FIG. 6, where the device server 11 sends the above connection request. The user registration program 29 is sent to the first user client 19 that is the transmission source of the user registration program 29 to automatically start the user registration program 29 in the first user client 19. As shown in step (6) in FIG. 1, the user can manually start the user registration program 29 in the first user client 19.

  As shown in step S11 in FIG. 7, when the user registration program 29 is activated in the first user client 19, the user registration program 29 prompts the user to select an action to be performed. Here, the actions that can be selected by the user in the user registration program 29 include user registration and assignment notification registration as shown in steps S12 and S20 in FIG. Transfer notification registration will be described later. The user registration is to register the user information of the device to be managed in the device management server 11. In this stage of the description, the information of the first user as the user of the first device 21 is registered in the device management server 11. It is to be. There are two user registration methods: new user registration and continuous user registration. The continuous user registration is a user registration method performed when the user has a customer key, which will be described later. New user registration is a user registration method when the user does not have a customer key. In this embodiment, if the user has a customer key, the customer key is stored in the user client by the user registration program 29 in the user client (but not necessarily). The customer key may be stored by the user himself or may be stored in a storage device outside the user client). In this explanation, it is assumed that the first user does not have a customer key at this stage when the first user is going to register the user of the first device 21, that is, in the first user client 19. It is assumed that the user registration program 29 does not store the customer key, and therefore only new user registration can be performed at this stage.

  Accordingly, the first user selects user registration for the user registration program 29, and then, as shown in steps S13 and S14 in FIG. 7, the user registration program 29 determines whether or not the first user has a customer key. (That is, whether or not the customer key is stored in the first user client 19) (or whether or not the customer key has been input to the user registration program 29 by the first user, or the customer key is the first key Whether or not it exists in the user client 19 specified by the user or in an external storage location). As a result, there is no customer key, so the user registration program 29 selects new registration as the user registration method. And new user registration data for the first user (for example, user details such as the first user's address and name) Information). Then, as shown in step (7) in FIG. 1 and step S14 in FIG. 8, when the first user performs an input operation on the new user registration data, the user registration program 29 inputs the new user registration data. To do. Then, as indicated by step (8) in FIG. 1 and steps S15 and S16 in FIG. 7, the user registration program 29 is connected to the device management server 11 and the input new user registration data of the first user and A new user registration request including the device ID of the first device 21 is transmitted to the device management server 11.

  Then, as shown in step (9) in FIG. 1 and steps S36 to S38 in FIG. 8, the device management server 11 receives the user registration request from the user registration program 29, and the received request is a new user registration. Identifies whether the request is a request or a continuous user registration request. As a result, since the received request is a new user registration request, a new user ID is assigned to the first user, and based on the first user's new user registration data included in the new user registration request, A user record 31 for one user is newly created, and this user record 31 is registered in the user database 31. At this time, as shown in step S39 in FIG. 7, the device management server 11 includes the first device included in the received new user registration request in the possessed device ID 39 in the user record 31 of the first user. 21, the user record 31 of the first user in the user database 15 is associated with the device record 33 of the first device in the device database 17. Further, the device management server 11 resets the transfer flag 59 in the device record 33 of the first device in the device database 17 in step 39 of FIG. In this way, the new user registration for the first device 21 by the first user is completed.

  Thereafter, in the first device 21, as shown by steps (2) and (3) in FIG. 1 and steps S1 and S2 in FIG. 1 The latest operation data 25 of the device 21 is transmitted to the device management server 11. In each case, the device management server 11 updates the latest operation data 25 received from the first device 21 and the first data in the device database 17 as shown in Step (4) in FIG. 1 and Steps S31 to S33 in FIG. The operation information 61 of the device record 33 of one device is integrated to create a new content of the operation information 61, and the operation information 61 of the device record 33 is updated so as to be the new content.

  Thereafter, when the first user desires to resell the first device 21 as a second-hand product to another person, an operation for registering a transfer notification as shown in FIG. 3 is performed.

  That is, as shown in step (11) in FIG. 3, the first user activates the user registration program 29 in the first user client 19, and transfers it to the user registration program 29 in step S20 of FIG. Select notification registration. Then, as shown in step (12) in FIG. 3 and steps S21 and S22 in FIG. 7, the user registration program 29 transmits a transfer notification including the device ID of the first device 21 to the device management server 11.

  Then, as indicated by steps S31, S33 and S34 in FIG. 8, the device management server 11 receives the transfer notification from the user registration program 29, and stores the device record having the device ID included in the transfer notification (that is, the first record). The status of the transfer flag 59 in the (device record of 1 device 21) 33 is checked. As a result, since the transfer flag 59 is in a reset state (reset in step (9) in FIG. 1), the control of the device management server 11 proceeds to step S42 in FIG. 9, where the device management server 11 It is checked whether the request received from the user registration program 29 is a transfer notice. As a result, it is recognized that the received request is a transfer notification. Therefore, as shown in step S43 in FIG. 9 and step (13) in FIG. 3, the transfer flag in the device record 33 of the first device 21 is shown. 59 is set. As a result, the transfer notification for the first device 21 is registered in the device management database 13. At this time, as shown in steps S44 and S45 in FIG. 9 and steps (14) and (15) in FIG. 3, the device management server 11 sends the source address of the received transfer notification and / or the transfer notification thereof. From the registered user ID 57 in the device record 33 of the first device 21 that is the target of the identification, it is specified that the requester of the transfer notification is the first user, and a new customer key 71 is created. The customer key 41 is registered in the user record 31 having the same user ID 37 as the registered user ID 57 in the device record 33 of the first device 21 (that is, the user record of the first user). Assigned to the first user), and the customer key 71 is assigned to the user client (that is, the first user class used by the first user) that sent the transfer notice. To send to the user registration program 29 of the ant) 19.

  Then, the user registration program 29 in the first user client 19 reads the customer key 71 for the first user issued from the device management server 11 as shown in step (16) in FIG. 3 and step S23 in FIG. Are stored in a predetermined storage location in the first user client 19 (or in a storage location in or outside the first user client 19 designated by the first user). This completes the transfer notification registration procedure for the first device 21 by the first user.

  By the way, the above-mentioned customer key indicates that the user having the customer key is that the management target device registered as the user's possession in the device database 13 is currently the transfer target (that is, the user Indicates that the device is currently being transferred to another person, or has already been transferred). As will be described later, this customer key is registered by the method of continuous user registration when the user obtains this customer key and then acquires another managed device and tries to register the user for that device. Make it possible to do. Then, when the user is registered for the device obtained later by the method of continuous user registration, the information of the device previously held is registered as the device history in the user record of the user. As a result, the device manufacturer can obtain information on which device the user has used habitually so far, and based on that information, the user is more preferential than other users. It is also possible to provide such a service.

  Next, an operation in the case where the second user purchases the first device 21 as a mid-size product after the first user has performed transfer notification registration for the first device 21 and performs the user registration will be described. This operation is illustrated in FIG.

  That is, in the user registration operation by the second user shown in FIG. 4, it is assumed that the second user does not have a customer key. Therefore, the second user performs user registration for the first device 21 by the new user registration method. The operation of new user registration by the second user is basically the same as the operation of new registration by the first user already described with reference to FIG. 1 and FIGS. Therefore, in this specification, in the above description already given with reference to FIG. 1 and FIGS. 6 to 8, “first user” is read as “second user”, and “first user client 19” is referred to as “first user”. “User registration program 29” is read as “user registration program 75”, and “user record 31 of the first user” is read as “user record 77 of the second user”. It replaces with description of the operation | movement shown by FIG.

  When the user registration shown in FIG. 4 is performed, the device record 79 of the first device in the device database 17 includes the operation information through the usage period of the first user who is the previous owner as the operation information 61. Already recorded. Then, after the user registration shown in FIG. 4 is completed, the operation information through the use period of the first user already registered and the operation information during the use period of the second user after that are integrated. The operation information 61 of the device record 79 of the first device 21 is updated in the content. For this reason, the device manufacturer not only affects the second user who has purchased the first device 21 that is a second-hand product, but also affects the state of the first device 21 due to the use of the previous user as well as the influence of the second user himself / herself. It is possible to provide a better quality support service based on integrated operation information that incorporates

  Next, an operation when the first user purchases another device (second device) after reselling the first device 21 and performs user registration for the second device will be described. The operation in this case is shown in FIG.

  That is, as shown in step (31) in FIG. 5, the first user uses a user registration program (or an installer program for installing it in an arbitrary user client) 87 attached to the second device 81. Then, the user registration program 89 for the second device 81 is installed in the first user client 19. Thereafter, as shown in steps (32) to (35) in FIG. 5, when the device management program 83 in the second device 81 first transmits the operation data 85 in the second device 81 to the device management server 11. The user registration program 89 in the first user client 19 is automatically started by the start command from the device management server 11. Alternatively, as shown in step (36) in FIG. 5, the user 1 manually starts the user registration program 89 in the first user client 19 automatically. In any case, when activated, the user registration program 89 first prompts the first user to select either user registration or transfer notification registration. The details of the operation so far are basically the same as the case of user registration for the first device 21 already described with reference to FIG.

  Thereafter, as shown in step (37) in FIG. 5, the first user selects user registration for the first user client 19. Then, as shown in step (38) in FIG. 5 and steps S12 and S13 in FIG. 8, the user registration program 89 determines whether or not the first user has a customer key in response to the user registration selection. 89 is whether or not the first user has a customer key (that is, whether or not the customer key is stored in the first user client 19) (or the customer key is sent from the first user to the user registration program 89). Whether the customer key has been entered or whether or not the customer key exists in the storage location inside or outside the one-user client 19 designated by the first user is checked. As a result, since the customer key 71 (which is issued and stored when the procedure for registering notification of transfer of the first device shown in FIG. 3 is performed) is found, the user registration program 89 performs step ( 39) and (40) and steps S17 to S19 in FIG. 7, the user registration method is selected as the user registration method, connected to the device management server 11, and the found customer key 71 and the second device 81 are detected. A continuous user registration request including the ID is transmitted to the device management server 11, and the found customer key 71 is deleted.

  On the other hand, as indicated by steps S34 to S34 in FIG. 8, in response to the connection request from the user registration program 89, the device management server 11 has a device record (that is, the second record) having the device ID included in the connection request. The transfer flag 59 in the device record 79 of the device 81 is checked. Here, since the second device 81 is new and sold to the second user or sold as a second-hand product, the transfer flag in the device record 79 has been registered because the previous user has performed the transfer notification registration described above. It is assumed that 59 is set. Therefore, as a result of the check, the control of the device management server 11 proceeds to step S36 in FIG. 8, and the device management server 11 receives the continuous user registration request transmitted from the user registration program 89 described above.

  Then, as shown in steps S40 and S41 in FIG. 8 and step (40) in FIG. 5, the device management server 11 has an existing customer key 41 that matches the customer key 71 included in the continuous user registration request. The user record (that is, the user record of the first user) 31 is searched from the user database 15, and the current value of the possessed device ID 39 in the found user record 31 (that is, the first user previously owned by the first user). The device history information indicating that the first device 21 has been held in the past is created using the device ID of the one device 21, and is additionally recorded in the device history 49 in the user record 31. Furthermore, the device management server 11 rewrites the retained device ID 39 in the user record 31 with the device ID included in the continuous user registration request (that is, the device ID of the second device 81). As a result, the association indicating that the first user is a registered user of the first device 21 that has existed until now between the user record 31 of the first user and the device record 33 of the first device 21 is deleted. Instead, another association indicating that the first user was a past user of the first device 21 is set between the records 31 and 33, and the user record 31 of the first user and the first record A new association indicating that the first user is a registered user of the second device 81 is set with the device record 79 of the second device 81. Furthermore, the device management server 11 deletes the customer key 41 in the user record 31. Further, the device management server 11 resets the transfer flag 59 in the device record 79 having the device ID included in the continuous user registration request (that is, the device record of the second device 81).

  This completes user registration related to the second device 81 by the first user. By performing user registration for the second device 81 using the customer key acquired by performing the transfer notification registration of the first device 21 previously, the first user is stored in the database 13 by the user registration. It is recorded that the user is not only the current user of the second device 81 but also the user of the first device 21 in the past. Therefore, as a device manufacturer, it is possible to provide a thicker support service to the first user in consideration of the past usage history of the first device 21.

  According to the embodiment of the present invention described above, it is possible and facilitated for each user to perform user registration for devices that are transferred from one user to another. Then, when both the transferring user and the transferring user perform user registration, an integrated operation information record is formed by combining the results of use by both users. It is possible to provide a better quality support service to the user on the side. Furthermore, when a certain user purchases different devices sequentially, a record of the usage history of those devices is also created, and if this is utilized, a higher-quality support service is provided to that user as well. It becomes possible. Further, by analyzing these records, device manufacturers can obtain useful information for future device development and device sales. In this way, there are advantages for the transfer side user, the transfer side user, and the device manufacturer.

  As mentioned above, although embodiment of this invention was described, this embodiment is only the illustration for description of this invention, and is not the meaning which limits the scope of the present invention only to this embodiment. The present invention can be implemented in various other modes without departing from the gist thereof.

  For example, an executable program having a user registration function or a transfer notification registration function can be used as the user registration program in the above-described embodiment, but instead of or in combination with a predetermined application such as a general-purpose web browser. Non-executable programs such as opened HTML files can also be used. Such a non-executable program is provided to the user client from the managed device or the device management server, and is opened on a predetermined application in the user client and operated by the user. The device management server 11 can be configured to request processing such as user registration and transfer notification registration through a predetermined application.

  Also, the program for performing user registration and the program for performing transfer notification registration are not necessarily the same program, and may be different programs. For example, user registration may be performed using a dedicated program, and transfer notification registration may be performed using an HTML file displayed on a web browser, or vice versa.

The block diagram which shows the structure of the apparatus management system concerning one Embodiment of this invention, and the procedure of the data communication when a 1st user performs user registration about a 1st apparatus in the system. The block diagram which shows the structure of the user record and apparatus record in the database in the same system. The block diagram which shows the procedure of data communication when the 1st user intends to resell the 1st apparatus to others in the system. The block diagram which shows the procedure of the data communication when a 2nd user performs user registration about the 1st apparatus in the same system. The block diagram which shows the procedure of the data communication when a 1st user performs user registration about a 2nd apparatus in the system. The flowchart which showed the flow of the information processing of the device management program of each management object apparatus in the system. The flowchart which showed the flow of the information processing of the user registration program of each user client in the same system. The flowchart which showed the flow of the information processing of the apparatus management server in the same system in connection with FIG. Fig. 8 shows the flow of information processing by the device management server in the same system.

Explanation of symbols

DESCRIPTION OF SYMBOLS 11 ... Device management server, 13 ... Device management database, 19 ... 1st user client, 21 ... 1st device, 23 ... Device management program, 25 ... Operation data, 27 ... User registration program for 1st device (or its) Installer program), 29 ... user registration program for the first device, 31 ... user record of the first user, 33 ... device record of the first device, 35, 65 ... user record, 41 ... customer key, 49 ... device history, 51, 53 ... Device record, 59 ... Transfer flag, 61 ... Operation information, 71 ... Customer key, 73 ... Second user client, 75 ... User registration program for the first device, 77 ... User record for the second user, 79 ... Device record of second device, 81 ... Second device, 23 ... Device management program, 85 ... Operation data, 87 ... Second device User registration program (or its installer program), 89 ... user registration program for the first device.

Claims (4)

A plurality of device records respectively corresponding to a plurality of devices and a plurality of user records respectively corresponding to a plurality of users are accumulated, and the device records of each device indicate whether or not each device is a transfer target. A device management database containing transfer information;
A device management server capable of communicating with a plurality of user clients respectively used by a plurality of users and accessing the device management database;
User registration request means that is provided to a user client used by each user and transmits a user registration request for the device owned by each user to the device management server;
A transfer notification means that is provided to a user client of each user, and that transmits a transfer notification for a device owned by each user;
The device management server
User registration request receiving means for receiving the user registration request from any user client;
Transfer request receiving means for receiving the transfer request from any user client;
When a user registration request for a certain device held by a certain user is received, the transfer information in a device record corresponding to the certain device is checked, and the checked transfer information is determined to be the certain device. Indicates that it is a transfer target, the checked transfer information is reset so as to indicate that the certain device is no longer a transfer target, and a device record corresponding to the certain device User registration means for setting a first association between the user record corresponding to the certain user and indicating that the certain user is a registered user of the certain device;
After the first association is set between the device record corresponding to the certain device and the user record corresponding to the certain user, a transfer notification for the certain device held by the certain user is issued. A device management system comprising transfer notice registration means for resetting the transfer information in a device record corresponding to the certain device so as to indicate that the certain device is a transfer target when received. The system of claim 1, wherein
The user registration request unit and the transfer notification unit are both stored in advance in a storage device built in or attached to each device, and from the storage device to a user client used by a user who has acquired each device. And a device management system, which is a computer program that can be installed. The system of claim 1, wherein
The device record corresponding to each device in the device management database includes operation information indicating a state related to the operation of each device,
The device management server
The operation data of each device is continuously and repeatedly acquired, and the operation data acquired for each device is integrated with the operation information in the device record corresponding to each device to create new operation information. The operation information update means for updating the operation information in the device record corresponding to each device to the new operation information,
When the registered user of each device is changed, the operation information update unit supports not only the operation data acquired after the registered user is changed, but also each device before the registered user is changed. A device management system that takes in the old operation information set in the device record to be created and creates the new operation information. The system of claim 1, wherein
The device management server
After the first association is set between a device record corresponding to the certain device and a user record corresponding to the certain user, a transfer notification for the certain device of the certain user is received. And a means for creating a customer key, assigning the created customer key to the certain user, and transmitting the created customer key to a user client used by the certain user,
The user client that each user uses is
Means for storing the received customer key in a predetermined storage device inside or outside each user client when the customer key assigned to each user is received from the device management server;
When the user registration request is transmitted, the customer key assigned to each user is searched from the predetermined storage device, and when the customer key assigned to each user is found, together with the user registration request Means for transmitting the found customer key to the device management server;
The device management server
User registration for another device held by the certain user when the first association exists between the device record corresponding to the certain device and the user record corresponding to the certain user When a customer key assigned to the certain user is received together with the request, the first existing between a device record corresponding to the certain device and a user record corresponding to the certain user. And indicating that the certain user is a past user of the certain device between a device record corresponding to the certain device and a user record corresponding to the certain user. A device management system further comprising means for setting two associations.

Images