EP4609345A1

EP4609345A1 - Management apparatus, management system, management method, and recording medium

Info

Publication number: EP4609345A1
Application number: EP23782282.0A
Authority: EP
Inventors: Shingo Ota; Keisuke Terasaki
Original assignee: Ricoh Co Ltd
Current assignee: Ricoh Co Ltd
Priority date: 2022-10-24
Filing date: 2023-09-19
Publication date: 2025-09-03
Also published as: WO2024089488A1; CN120112931A

Abstract

A management apparatus for managing information related to an introduction object having been introduced to a user device includes a management means, an acquisition means, a generation means, and a transmission means. The management means manages an administrative user and a general user each related to the introduction object. The acquisition means acquires use history information related to the introduction object used by the general user, the generation means generates a notification in a case where a use status based on the use history information matches a predetermined condition, and the transmission means transmits the notification to the administrative user.

Description

[DESCRIPTION]

[Title of Invention]

MANAGEMENT APPARATUS, MANAGEMENT SYSTEM, MANAGEMENT METHOD, AND RECORDING MEDIUM

[Technical Field]

[0001]

The present disclosure relates to a management apparatus, a management system, a management method, and a recording medium.

[Background Art]

[0002]

In recent years, online markets that provide various applications for smart devices have been used. For example, a user using a smart device can download a desirable application recommended in an online market with a charge or no charge to use the recommended application on the smart device. As described above, a system that recommends a useful application to a user is known. For example, a known technology recommends an application based on a tendency of frequency of use of an application by a plurality of users (for example, see Patent Literature (PTL) 1).

[Citation List]

[Patent Literature]

[0003]

[PTL 1]

Japanese Unexamined Patent Application Publication No. 2018-190154

[Summary of Invention]

[Technical Problem]

[0004]

However, in the related art, in a case a user who manages an introduction object such as an application and the like installed on a device is different from a user who uses the application and the like, an administrative user who manages the introduction object faces difficulty in grasping a use status by other users of the introduction object introduced by the administrative user.

[Solution to Problem]

[0005]

In one aspect, a management apparatus for managing information related to an introduction object having been introduced to a user device includes a management means, an acquisition means, a generation means, and a transmission means. The management means manages an administrative user and a general user each related to the introduction object. The acquisition means acquires use history information related to the introduction object used by the general user, the generation means generates a notification in a case where a use status based on the use history information matches a predetermined condition, and the transmission means transmits the notification to the administrative user. Another aspect concerns a management system including a management apparatus and a communication terminal. The management apparatus includes a management means that manages an administrative user and a general user each related to the introduction object, an acquisition means that acquires use history information related to the introduction object used by the general user, a generation means that generates a notification in a case where a use status based on the use history information matches a predetermined condition, and a transmission means that transmits the notification to the administrative user. The communication terminal includes display control means that displays the notification generated by the management apparatus on a display means.

Another aspect concerns a management method executed by a management apparatus configured to manage information related to an introduction object having been introduced to a user device. The method includes managing an administrative user and a general user each related to the introduction object, acquiring use history information related to the introduction object used by the general user, generating a notification in a case where a use status based on the use history information matches a predetermined condition, and transmitting the notification to the administrative user.

Another aspect concerns a recording medium carrying computer readable code for controlling a computer system to carry out a method including managing an administrative user and a general user each related to an introduction object, acquiring use history information related to the introduction object used by the general user, generating a notification in a case where a use status based on the use history information matches a predetermined condition, and transmitting the notification to the administrative user.

[Advantageous Effects of Invention]

[0006]

As described above, according to the embodiments of the present disclosure, even in the case the user who manages the introduction object such as an application and the user who uses the introduction object are different, the administrative user who manages the introduction object is able to grasp the use status by other users of the introduction object introduced by the administrative user.

[Brief Description of Drawings]

[0007]

A more complete appreciation of embodiments of the present disclosure and many of the attendant advantages and features thereof can be readily obtained and understood from the following detailed description with reference to the accompanying drawings.

[FIG. 1]

FIG. 1 is a diagram illustrating history information management on customers according to an embodiment of the present disclosure.

[FIG. 2]

FIG. 2 is a conceptual diagram illustrating acquisition of history information before and after introduction of an introduction object. [FIG. 3]

FIG. 3 is a diagram illustrating an example of an overall configuration of an information processing system.

[FIG. 4]

FIG. 4 is a block diagram illustrating an example of a hardware configuration of a management apparatus, a history management server, and an application distribution server. [FIG. 5]

FIG. 5 is a block diagram illustrating an example of a hardware configuration of a communication terminal.

[FIG. 6]

FIG. 6 is a block diagram illustrating an example of a hardware configuration of a user device.

[FIG. 7]

FIG. 7 is a block diagram illustrating an example of a functional configuration of the information processing system.

[FIG. 8]

FIG. 8 is a diagram illustrating an example of a functional configuration of the information processing system.

[FIG. 9]

FIG. 9 is a table presenting an example of a user information management table.

[FIG. 10]

FIG. 10 is a table presenting an example of a device information management table.

[FIG. 11]

FIG. 11 is a table presenting an example of a use history information management table.

[FIG. 12]

FIG. 12 is a table presenting an example of a transaction history information management table.

[FIG. 13]

FIG. 13 is a table presenting an example of a recommendation condition management table.

[FIG. 14]

FIG. 14 is a table presenting an example of an introduction object management table.

[FIG. 15]

FIG. 15 is a table presenting an example of an introduction information management table.

[FIG. 16]

FIG. 16 is a table presenting an example of a use history information management table.

[FIG. 17]

FIG. 17 is a table presenting an example of a transaction history information management table.

[FIG. 18]

FIG. 18 is a sequence diagram illustrating examples of a user authentication process and a device registration process.

[FIG. 19]

FIG. 19 is a diagram illustrating an example of a screen displayed to execute user authentication in the communication terminal.

[FIG. 20]

FIG. 20 is a diagram illustrating an example of a screen displayed during device registration in the user device.

[FIG. 21]

FIG. 21 is a sequence diagram illustrating an example of a history information acquisition process.

[FIG. 22]

FIG. 22 is a sequence diagram illustrating an example of a recommendation determination process.

[FIG. 23]

FIG. 23 is a flowchart illustrating an example of the recommendation determination process. [FIG. 24]

FIG. 24 is a diagram illustrating an example of a screen displaying notification of recommendation information.

[FIG. 25]

FIG. 25 is a sequence diagram illustrating an example of a various application acquisition process.

[FIG. 26]

FIG. 26 is a sequence diagram illustrating an example of processing according to use.

[FIG. 27]

FIG. 27 is a diagram illustrating an example of a screen displaying notification of an application use status.

[FIG. 28]

FIG. 28 is a sequence diagram illustrating an example of processing using a user device according to another embodiment.

The accompanying drawings are intended to depict embodiments of the present disclosure and should not be interpreted to limit the scope thereof. The accompanying drawings are not to be considered as drawn to scale unless explicitly noted. Also, identical or similar reference numerals designate identical or similar components throughout the several views. [Description of Embodiments] [0008]

In describing embodiments illustrated in the drawings, specific terminology is employed for the sake of clarity. However, the disclosure of this specification is not intended to be limited to the specific terminology so selected and it is to be understood that each specific element includes all technical equivalents that have a similar function, operate in a similar manner, and achieve a similar result. Referring now to the drawings, embodiments of the present disclosure are described below. As used herein, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise.

[0009]

<Customer History Information Management

Management of customer history information according to the present embodiment is described. FIG. 1 is a diagram illustrating the customer history information management. As illustrated in FIG. 1, a management apparatus 3 manages a user device and a user belonging to a customer for each customer identification information. The management apparatus 3 collects log information from each user device and manages the log information as use history information by associating the log information with customer identification information to which the user device belongs. Furthermore, the management apparatus 3 collects purchase information from a history management server 6 that manages the purchase information and the like of each user, and manages the purchase history as transaction history information by associating the purchase history with the customer identification information to which the user belongs. The management apparatus 3 identifies an introduction object based on the use history information and the transaction history information, and recommends introduction of the identified introduction object to the customer. For example, an introduction object recommendation notification is transmitted to a desired destination so that an administrative user who manages a user device 5 can confirm the recommendation, and whether the introduction object has been introduced is managed based on the recommendation notification. Thereafter, the management apparatus 3 associates and manages the customer identification information and the installed introduction object.

[0010]

<Acquisition of History Information Before and After Introduction of Introduction Object> A calculation of difference information before and after introduction of the introduction object is described. FIG. 2 is a conceptual diagram illustrating acquisition of history information before and after introduction of the introduction object. In FIG. 2, the management apparatus 3 calculates the difference information between before and after introduction of a predetermined introduction object by the following method. The management apparatus 3 stores, for example, application identification information of an installed application, the customer identification information, and introduction date and time in association with each other. After that, for example, one month after the introduction, the following processing is performed.

- Extract a recommendation condition based on the application identification information.

- Extract history corresponding to a recommendation condition from the use history information and transaction history information corresponding to the customer identification information.

- Calculate the difference between the history extracted from the use history information and the history extracted from the transaction history information before and after the introduction date and time.

[0011]

Specifically, the use history information and transaction history information before introduction (for example, for one month) is aggregated, the use history information and the transaction history information after introduction (for example, for one month) is aggregated, and the difference information (including the amount of change or ratio) between the use history information and the transaction history information before and after the introduction is calculated, for example, the amount of change in one month or difference information for each day in one month.

[0012]

In the present embodiment, a management system is implemented to provide the administrative user with the difference information calculated based on the method described above.

[0013]

[Overall Configuration of Information Processing System]

FIG. 3 is a diagram illustrating an example of an overall configuration of the information processing system. As illustrated in FIG. 3, the information processing system 1 includes devices and terminals including the management apparatus 3, the communication terminal 4, the user device 5, the history management server 6 and an application distribution server 7. The information processing system 1 also includes a management system 2 including the management apparatus 3, the communication terminal 4, the user device 5 and the history management server 6. In the information processing system 1, the management apparatus 3, the communication terminal 4, the user device 5, the history management server 6 and the application distribution server 7 are connected to each other through a communication network 100. The communication between the management apparatus 3 and the communication terminal 4, the user device 5, and the history management server 6 through the communication network 100, may be done through a firewall provided inside the communication network 100.

[0014]

The communication network 100 described above is a communication network in which an unspecified large amount of communication is performed, and is implemented by the internet, an intranet, a local area network (LAN), and the like. The communication network 100 may include wireless communication networks such as 4th Generation (4G), 5th Generation (5G), Worldwide Interoperability for Microwave Access (WiMAX), and Long Term Evolution (LTE) in addition to wired communication.

[0015]

The management apparatus 3 included in the information processing system 1 is an information processing apparatus (computer system) that manages information related to the introduction object introduced to the user device. The management apparatus 3 is implemented by one or more information processing apparatuses (computer systems) with a general server operating system (OS) or the like installed, and manages the history information related to the introduction object including application recommended for use. The history information is, for example, use history information indicating the use history of a function of the user device 5. The management apparatus 3 performs a recommendation determination process, which is described below, based on the history information. Further, the management apparatus 3 may have an installation management function for managing installation of applications. In addition, the management apparatus 3 stores communication application for communicating with other devices and communication terminals in the storage. The management apparatus 3 may manage the use history of the introduction object in cooperation with another management server that manages the use history. In other words, the management apparatus 3 may separately manage the use history information (log information) as a use history and information for recommending introduction of the introduction object.

[0016]

The management apparatus 3 may be a communication terminal having a communication function, such as a general purpose personal computer (PC), portable notebook PC, mobile phone, smartphone, tablet terminal, or the like. A communication device or a communication terminal capable of operating software such as browser software may also be used as the management apparatus 3. The management apparatus 3 may be implemented by a plurality of computers.

[0017]

The management apparatus 3 may send a notification (transmission) to the communication terminal 4 or the user device 5 (described below) of data (information) by push notification (transmission), such as a recommendation information notification that is a result of the recommendation determination process. In this case, the management apparatus 3 can implement a notification (transmission) of data by push notification using Firebase Cloud Messaging (FCM), which is an example of a push notification server.

[0018]

Communication Terminal>

The communication terminal 4 displays the information related to the introduction object transmitted by the management apparatus 3. The communication terminal 4 is implemented by the information processing apparatus (computer system) with the general-purpose OS or the like installed to perform communication. The communication terminal 4 receives and displays the recommendation information notification and the difference information between before and after introducing the introduction object transmitted by the management apparatus 3. The communication terminal 4 stores, in a storage means, communication application for performing communication with the communication terminal 4 and another device and applications that provide commonly used external services.

[0019] The communication terminal 4 may be a communication terminal having a communication function used by the user, such as the general PC, portable notebook PC, mobile phone, smartphone, tablet terminal, or wearable terminal (sunglass type, wristwatch type, or the like). The communication terminal 4 may be a communication apparatus or a communication terminal that can operate browser software or software of various applications.

[0020]

The user device 5 is managed by the management apparatus 3 in association with a customer identification information. The user device 5 is, for example, a device (apparatus) that is implemented by the information processing apparatus (computer system) with the general- purpose OS or the like installed for performing communication and provides history information related to the introduction object, such as the application recommended to be used. The user device 5 introduces and uses the recommended introduction object (application or the like). In response to using a function of the user device 5, the user device 5 stores log information as an example of the use history and uploads the log information to the management apparatus 3. In the present embodiment, as illustrated in FIG. 1, user devices 5A and 5B are image forming apparatuses which are examples of multi-function peripherals (MFPs). In the present embodiment, the user devices 5A and 5B are referred to as the user device 5 unless otherwise specified. The user device 5 includes a scanner, a facsimile, an electronic whiteboard, a projector, a PC, a smartphone, and an interactive voice operation apparatus (smart speaker or artificial intelligence (Al) speaker). The user device 5 stores, in the storage means, the communication application for performing communication with another apparatus or application that provides an external service that is generally used, or each apparatus or terminal through the communication network 100.

[0021]

The user device 5 may be implemented by the computer, such as the general desktop PC or the portable notebook PC.

[0022]

The history management server 6 is the information processing apparatus (computer system) that manages the history information. The history management server 6 is implemented by one or more information processing apparatuses (computer systems) on which the general server OS or the like is installed. The history management server 6 manages history information including contract history information indicating a contract history related to a contract, purchase history information indicating a purchase history, and research history information indicating a research history of the user device 5 in association with the user device 5 or the customer. The above-described history information, that is, transaction history information is history information different from the use history information managed by the management apparatus 3. Specifically, the transaction history information includes purchase history information representing a purchase history related to a purchase of the user device 5, contract history information representing the contract history related to the contract of the user device 5, and research history information representing the research history related to the research on the user device 5. The history management server 6 stores the communication application for performing communication with another apparatus or communication terminal in a storage means.

[0023]

The history management server 6 may be implemented by the computer, such as the generally used PC or portable notebook PC, or may be implemented by a plurality of computers in which respective units (functions or means) such as a storage are divided and desirably assigned. All or part of the functions of the history management server 6 may be provided by a server computer residing in a cloud environment or a server computer residing in an onpremises environment. In other words, the management system 2 according to the present embodiment may be implemented such that the management apparatus 3 manages the information (data) managed by the history management server 6. The history management server 6 may be a communication apparatus or a communication terminal that can operate software such as the browser software.

[0024]

Application Distribution Server>

The application distribution server 7 is an information processing apparatus (computer system) that provides an application (service) to the user device 5 or the user for a fee or free of charge. The application distribution server 7 is implemented by one or more information processing apparatuses (computer systems) with the general-purpose server OS or the like installed. The application distribution server 7 stores various applications distributed or introduced to the user device 5 in a predetermined storage area and manages the applications. Thereby, the user can download desired application from the application distribution server 7 to the communication terminal 4 or the user device 5 used by the user. The application distribution server 7 further performs authentication in response to a predetermined processing request from the user device 5 and execution of the predetermined processing.

The processing or process includes, for example, providing application data to the user device 5, providing an application function to the user device 5, and providing a service to the user device 5 or the user. The application distribution server 7 stores a communication application for performing communication with another apparatus or the communication terminal in a storage means.

[0025]

The application distribution server 7 may be implemented by a computer such as the general PC or portable notebook PC, or may be implemented by a plurality of computers in which respective units (functions or means) such as a storage are divided and assigned. All or part of the functions of the application distribution server 7 may be provided by a server computer present in a cloud environment or a server computer present in an on-premises environment. The application distribution server 7 may be a communication apparatus or a communication terminal that can operate software such as the browser software.

[0026]

In the present embodiment, a management apparatus capable of grasping whether the introduction object is appropriately used is provided to a user who uses the introduction object, based on the system configuration described above.

[0027]

In the present embodiment, “recommendation” represents recommending the customer to introduce the introduction object.

Examples of the recommendation include recommendation for introducing the introduction object such as an application program (hereinafter, referred to as application) to the user device 5 or the like.

[0028]

In the present embodiment, an “introduction object” is an object to be introduced. Examples of the introduction object include an application to be introduced (installed) to the user device 5 or the like, a contract action by the user or a contract content related to a contract of the user device 5, a purchase procedure for a purchase, and a research action such as a research. In the following description, the application may be used as the introduction object, but the introduction object is not limited to the application.

[0029]

In the present embodiment, “introduction” refers to making an introduction object available. In the case the introduction object is software such as the application, examples of the introduction include making software available by installation or the like in the user device 5, the communication terminal 4, or the like, purchasing a license, and making a function of the application available from an external server such as the application distribution server 7. In the case the introduction object is hardware or a product such as a peripheral device or an apparatus, the introduction includes installing the hardware, making the hardware available, and purchasing the hardware. In the case the introduction object is a service, the introduction includes a contract and a sign-up for the service.

[0030]

In the present embodiment, a “user” is a person who is managed in the management apparatus 3 in association with the customer identification information. The user refers to, for example, a person who sees and handles various notifications transmitted by the management apparatus 3 using the communication terminal. The user also refers to a person who operates the user device 5 to use a predetermined function, or a person who performs a transaction or a procedure such as a purchase or a contract through a communication terminal. The user includes a general user (an example of a first user) and an administrative user (an example of a second user). The general user is a person who uses the user device 5. The administrative user is a person who manages or owns the user device 5. For example, the administrative user can introduce the introduction object to the user device 5 based on the recommendation information notification. The user includes a department, an organization, a group, a team, of a company or the like in addition to an individual.

[0031]

In the present embodiment, a “customer” is a contractor who uses a service provided by the information processing system 1. The customer is managed by the customer identification information in the management apparatus 3. The customer includes, for example, an entity to which the user and the user device belong, or an account related to the entity. The customer includes, for example, a department, an organization, a group, a team, and a mass of a company. The customer may indicate an individual such as the user. The user or the user device 5 belonging to the customer may be referred to as the customer.

[0032]

In the present embodiment, a “service” is a function that is provided by the information processing system 1. The service includes functions provided by the application. Examples of the service include providing data or a function of an application, and recommending the introduction object. [0033]

In the present embodiment, “use” indicates that the user uses the introduction object. The use includes activation, execution, and the like of the introduced application. Also, “use amount” is the number or amount of use of the introduction object. The use amount includes the number of times the function of the installed application is executed, the number of times the application is started, the use time of the application, the number of files processed by the application, the amount of data or the number of media such as paper, and the frequency of use of the application.

[0034]

[Hardware Configurations]

Hardware configurations of the apparatuses or terminals included in the information processing system according to the present embodiment are described with reference to FIGs. 4 to 6. A component may be added or deleted from the hardware configurations of the apparatuses or terminals illustrated in FIGs. 4 to 6 as appropriate.

[0035]

FIG. 4 is a block diagram illustrating examples of the hardware configurations of the management apparatus, history management server, and application distribution server. As illustrated in FIG. 4, the management apparatus 3 is implemented by, for example, a computer, and includes a central processing unit (CPU) 301, a read-only memory (ROM) 302, a random-access memory (RAM) 303, an electrically erasable programmable ROM (EEPROM) 304, a hard disk (HD) 305, a hard disk drive (HDD) controller 306, a display 307, a short-range communication interface (I/F) 308, a complementary metal-oxide semiconductor (CMOS) sensor 309, and an imaging element PF 310. The management apparatus 3 further includes a network I/F 311, a keyboard 312, a pointing device 313, a medium I/F 315, an external device connection I/F 316, a sound input and output I/F 317, a microphone 318, a speaker 319, and a bus line 320.

[0036]

Among these components, the CPU 301 controls entire operation of the management apparatus 3. The ROM 302 stores programs and the like used to drive the CPU 301. The RAM 303 is used as a work area for the CPU 301. The EEPROM 304 reads or writes various data such as applications under the control of the CPU 301. The HD 305 stores various data such as programs. The HDD controller 306 controls reading or writing of various data to and from the HD 305 according to the control of the CPU 301. The management apparatus 3 may have a hardware configuration including a solid state drive (SSD) instead of the HD 305 and the HDD controller 306. The display 307 displays various information such as a cursor, menu, window, character, or image. In the present embodiment, the display 307 functions as an example of a display means. The short-range communication I/F 308 is a communication circuit for performing data communication with, for example, a communication apparatus or a communication terminal including a wireless communication interface such as near field communication (NFC), BLUETOOTH (registered trademark), or WI-FI (registered trademark). The CMOS sensor 309 is a built-in imaging device for acquiring image data or moving image data by imaging a subject under the control of the CPU 301. The imaging device may be implemented by a charge coupled device (CCD) sensor or the like instead of the CMOS sensor. An imaging element I/F 310 is a circuit that controls driving of the CMOS sensor 309.

[0037]

A network I/F 311 is an interface for data communication using the communication network 100. The keyboard 312 is an example of an input device provided with a plurality of keys for allowing the user to input characters, numerals, or various instructions. In place of or in addition to the keyboard 312, the input device implemented by a touch panel for inputting characters, numerical values, various instructions, and the like may be provided. The pointing device 313 is an example of the input device that allows a user to select or execute a specific instruction, select a target for processing, or move a cursor being displayed. The medium I/F 315 reads or writes (stores) data from or to a recording medium 314 such as a flash memory. The external device connection I/F 316 is an interface for connecting various external devices. The external device in this case is, for example, a Universal Serial Bus (USB) memory or the like. The sound input and output I/F 317 is a circuit for controlling input and output of audio signals between the microphone 318 and the speaker 319 under control of the CPU 301. The microphone 318 is a built-in circuit that converts sound into an electric signal. The microphone 318 acquires voice and sound waves emitted from an external speaker, and the like, and acquires information using electrical signals. The speaker 319 is a built-in circuit that generates the sound such as music or voice by converting an electric signal into physical vibration. The bus line 320 is an address bus, a data bus, or the like for electrically connecting each component such as the CPU 301. [0038]

The history management server 6 is implemented by a computer, for example, and includes a CPU 601, a ROM 602, a RAM 603, an EEPROM 604, an HD 605, an HDD controller 606, a display 607, a short-range communication I/F 608, a CMOS sensor 609, and an imaging element I/F 610. Since these hardware resources are similar to the CPU 301, the ROM 302, the RAM 303, the EEPROM 304, the HD 305, the HDD controller 306, the display 307, the short-range communication PF 308, the CMOS sensor 309, and the imaging element PF 310 of the management apparatus 3, the description thereof is omitted. The history management server 6 further includes a network PF 611, a keyboard 612, a pointing device 613, a medium PF 615, an external device connection PF 616, a sound input and output PF 617, a microphone 618, a speaker 619, and a bus line 620. Since these hardware resources are similar to the network PF 311, the keyboard 312, the pointing devices 313, the medium PF 315, the external device connection PF 316, the sound input and output PF 317, the microphone 318, the speaker 319, and the bus line 320 of the management apparatus 3, the description thereof is omitted.

[0039]

The application distribution server 7 is implemented by, for example, a computer, and includes a CPU 701, a ROM 702, a RAM 703, an EEPROM 704, a HD 705, an HDD controller 706, a display 707, a short-range communication PF 708, a CMOS sensor 709, and an imaging element PF 710. Since these hardware resources are similar to the CPU 301, the ROM 302, the RAM 303, the EEPROM 304, the HD 305, the HDD controller 306, the display 307, the short-range communication PF 308, the CMOS sensor 309, and the imaging element PF 310 of the management apparatus 3, the description thereof is omitted. The application distribution server 7 further includes a network PF 711 , a keyboard 712, a pointing device 713, a medium PF 715, an external device connection PF 716, a sound input and output PF 717, a microphone 718, a speaker 719, and a bus line 720. Since these hardware resources are similar to the network PF 311, the keyboard 312, the pointing devices 313, the medium PF 315, the external device connection PF 316, the sound input and output PF 317, the microphone 318, the speaker 319, and the bus line 320 of the management apparatus 3, the description thereof is omitted. The application distribution server 7 may be implemented by a generally used external server connected through the communication network 100. The hardware resources in this case may comply with hardware specifications of the external server.

[0040]

FIG. 5 is a block diagram illustrating an example of a hardware configuration of the communication terminal. As illustrated in FIG. 5, the communication terminal 4 is implemented by, for example, a computer, and includes a CPU 401, a ROM 402, a RAM 403, an EEPROM 404, a display 407, a short-range communication PF 408, a CMOS sensor 409, and an imaging element PF 410. The communication terminal 4 further includes a network I/F 411, a touch panel 412, a pointing device 413, a medium I/F 415, an external device connection 1/F 416, a sound input and output 1/F 417, a microphone 418, a speaker 419, and a bus line 420.

[0041]

The CPU 401 controls the operation of the entire communication terminal 4. The ROM 402 stores programs used to drive the CPU 401 and the like. The RAM 403 is used as a work area for the CPU 401. The EEPROM 404 reads or writes various data such as applications under the control of the CPU 401. The display 407 displays various information such as a cursor, menu, window, character, or image. In the present embodiment, the display 407 functions as an example of the display means. The short-range communication PF 408 is a communication circuit for performing data communication with, for example, a communication apparatus or a communication terminal including a wireless communication interface such as near field communication (NFC), BLUETOOTH (registered trademark), or WI-FI (registered trademark). The CMOS sensor 409 is a built-in imaging device for acquiring image data or moving image data by imaging a subject under the control of the CPU 401. The imaging device may be implemented by the CCD sensor or the like instead of the CMOS sensor. The imaging element PF 410 is a circuit that controls driving of the CMOS sensor 409.

[0042]

The network PF 411 is an interface for data communication using the communication network 100. The touch panel 412 is an example of an input device for operating the communication terminal 4 by the user pressing, clicking, or tapping predetermined buttons, icons, and the like arranged on the display 407. Note that, instead of or in addition to the touch panel 412, the input device such as a keyboard for inputting characters, numerical values, various instructions, and the like may be provided. The pointing device 413 is an example of the input device that allows a user to select or execute a specific instruction, select a target for processing, or move a cursor being displayed. The medium PF 415 reads or writes (stores) data from or to a recording medium 414 such as a flash memory. The external device connection PF 416 is an interface for connecting various external devices. The external device in this case is, for example, the USB memory or the like. The sound input and output PF 417 is a circuit that processes sound signal input and output between the microphone 418 and the speaker 419 under the control of the CPU 401. The microphone 418 is a built-in circuit that converts sound into electric signal. The microphone 418 acquires voice and sound waves emitted from the external speaker and the like, and acquires information using electrical signals. The speaker 419 is a built-in circuit that generates the sound such as music or voice by converting an electric signal into physical vibration. The bus line 420 is an address bus, a data bus, or the like for electrically connecting each component such as the CPU 401.

[0043]

<Hardware Configuration of User Device> FIG. 6 is a diagram illustrating an example of a hardware configuration of the user device. As illustrated in FIG. 6, the user device 5 is, for example, an image forming apparatus such as the MFP, and includes hardware resources such as a controller 510, a short-range communication circuit 520, an engine controller 530, a control panel 540, and a network I/F 550. [0044]

The controller 510 includes a CPU 501 as a main processor of the computer, a system memory (MEM-P) 502, a north bridge (NB) 503, a south bridge (SB) 504, an application specific integrated circuit (ASIC) 505, a local memory (MEM-C) 506, an HDD controller 507, and an HD 508 as a storage. The NB 503 and the ASIC 505 are connected through an Accelerated Graphics Port (AGP) bus 521.

[0045]

The CPU 501 is a control unit that controls the entire user device 5. The NB 503 connects the CPU 501 with the MEM-P 502, the SB 504, and the AGP bus 521. The NB 503 includes a memory controller for controlling reading or writing of various data with respect to the MEM- P 502, a Peripheral Component Interconnect (PCI) master, and an AGP target. [0046]

The MEM-P 502 includes a ROM 502a as a memory that stores program and data for implementing various functions of the controller 510. The MEM-P 502 further includes a RAM 502b as a memory that deploys the program and data, or as a drawing memory that stores drawing data for printing. The program stored in the RAM 502b may be provided as a file in an installable format or an executable format by recording the program on a computer- readable recording medium such as a compact disc-read only memory (CD-ROM), compact disc-recordable (CD-R), or digital versatile disk (DVD).

[0047]

The SB 504 is a bridge for connecting the NB 503 to PCI devices and peripheral devices. The ASIC 505 is an integrated circuit (IC) for image processing applications including hardware elements for image processing and has a role of a bridge connecting the AGP bus 521, PCI bus 522, HD 508, and MEM-C 506, respectively. The ASIC 505 includes a PCI target and AGP master, an arbiter that arbitrates the driving timing of each signal according to a predetermined priority in the ASIC 505, a memory controller that controls the MEM-C 506, image data rotation, etc. by hardware logic, and a PCI unit that transfers data between a scanner 531 and a printer 532 through the PCI bus 522. A USB interface or an Institute of Electrical and Electronics Engineers 1394 (IEEE 1394) interface may be connected to the ASIC 505.

[0048]

The MEM-C 506 is a local memory used as a buffer for image data to be copied or a code buffer. The HD 508 is a storage for accumulating image data, accumulating font data used for printing, and accumulating forms. The HDD controller 507 controls reading or writing of data to the HD 508 according to the control of the CPU 501. The AGP bus 521 is a bus interface for a graphic accelerator card, which has been proposed to accelerate graphic processing. Through directly accessing the MEM-P 502 by high-throughput, the speed of the graphics accelerator card is increased.

[0049]

The short-range communication circuit 520 includes a short-range communication antenna 520a. The short-range communication circuit 520 is a communication circuit that communicates in compliance with NFC, BLUETOOTH (registered trademark) and the like. [0050]

The engine controller 530 includes the scanner 531, the printer 532 and a facsimile 533. The control panel 540 includes a display panel 540a and an operation panel 540b. The display panel 540a is implemented by, for example, a touch panel that displays current settings or a selection screen and receives a user input. The operation panel 540b includes a numeric keypad that receives set values of various image forming parameters such as image density parameter and a start key that receives an instruction to start copying. In the present embodiment, the display panel 540a functions as an example of the display means. The controller 510 controls the entire user device 5, such as drawing, communication, and input from the control panel 540, for example. The scanner 531 or the printer 532 includes image processing functions such as error diffusion and gamma (y) conversion. Further, the facsimile 533 includes an analog interface, a modem, a speaker, and the like for performing facsimile communication using an analog line (public line) connected with an external device having a facsimile communication function.

[0051]

In response to an instruction to select a specific application through the control panel 540, for example, using an application switch key, the user device 5 selectively performs a document box function, a copy function, a print function, and a facsimile function. The document box mode is selected when the document box function is selected, the copy mode is selected when the copy function is selected, the print mode is selected when the print function is selected, and the facsimile mode is selected when the facsimile function is selected.

[0052]

The network I/F 550 controls communication of data with an external device through the communication network 100. The short-range communication circuit 520 and network I/F 550 are electrically connected to the ASIC 505 through the PCI bus 522.

[0053]

The user device 5 may also be implemented by a computer and includes hardware resources as illustrated in FIG. 4.

[0054]

Each of the programs described above may be recorded as a file in a format installable or executable on a computer-readable recording medium for distribution. Examples of the computer-readable recording medium are a Compact Disc Recordable (CD-R), a Digital Versatile Disc (DVD), a BLU-RAY (registered trademark), a Secure Digital (SD) card, a USB memory, and the like. The recording medium may be provided in the form of a program product to users within a certain country or outside that country. For example, the management apparatus 3 implements the management method according to the present disclosure by executing the program according to the present disclosure.

[0055]

[Functional Configuration of Information Processing System]

With reference to FIGs. 7 to 17, a functional configuration of the present embodiment is described below. FIG. 7 is a diagram illustrating an example of a functional configuration of the information processing system. FIG. 7 illustrates the terminals or devices illustrated in FIG. 3 that are related to processing or operations described below. [0056] <Functional Configurations of Management Apparatus>

With reference to FIGs. 4 and 7, the functional configurations of the management apparatus 3 are described. As illustrated in FIG. 7, the management apparatus 3 includes a data exchange unit 31, an extracting and specifying unit 32, an acquisition unit 33, a display control unit 34, a determination processing unit 35, a calculation unit 36, a generation unit 37, a registration management unit 38, and a storing and reading unit 39. These functional units are functions that are implemented by or means that are caused to function by operating any of the hardware resources illustrated in FIG. 4 in response to a command from the CPU 301 in accordance with a program for the management apparatus 3 developed from at least one of the ROM 302, the EEPROM 304, or the HD 305 to the RAM 303. The management apparatus 3 includes a storage unit 3000 implemented by at least one of the ROM 302, EEPROM 304, or HD 305 illustrated in FIG. 4. Further, the storage unit 3000 stores a communication program (communication application) for performing communication with each apparatus or each terminal through the communication network 100, a browser application, an introduction object management application for transmitting an introduction effect of an introduction object to the communication terminal 4 or the user device 5, and so forth.

[0057]

<<Each Functional Configuration of Management Apparatus>>

Configuration of each functional unit of the management apparatus 3 is described below in detail. The data exchange unit 31 of the management apparatus 3 illustrated in FIG. 7 is implemented mainly by processing of the CPU 301 on the network PF 311 and the short- range communication PF 308, and transmits or receives various data (or information) to or from each terminal or each apparatus through the communication network 100. The data exchange unit 31 transmits information related to at least one specified introduction object (recommendation information notification including information on an introduction object) to the communication terminal 4 or the user device 5 that can communicate with the management apparatus 3. Further, the data exchange unit 31 transmits a notification to the administrative user. Further, the data exchange unit 31 transmits notification for the customer generated by the generation unit 37 described below, to a destination associated with the customer identification information that identifies the customer. Further, the data exchange unit 31 transmits to the communication terminal 4 or the user device 5, alternative introduction object information, which is information regarding an alternative introduction object that is an alternative to the introduction object. The alternative introduction object information may include storage location information indicating the storage location of the alternative introduction object. The data exchange unit 31 further transmits a notification to the communication terminal 4 in response to an access from the communication terminal 4 used by the administrative user. In the present embodiment, the data exchange unit 31 functions as an example of at least one of a transmission means or receiving means.

[0058]

The extracting and specifying unit 32 is implemented mainly by the processing of the CPU 301, and extracts and specifies an introduction object in response to a recommendation information notification request transmitted by the communication terminal 4 or the user device 5. The extracting and specifying unit 32 specifies the introduction object for which a predetermined period has passed since the introduction among the introduction objects. Further, the extracting and specifying unit 32 specifies the introduction object that has been introduced to the user device 5 for a fee among the introduction objects. Further, the extracting and specifying unit 32 specifies an introduction object that has been introduced to the user device 5 according to a notification (for example, recommendation notification) transmitted by the management apparatus 3. The extracting and specifying unit 32 specifies an introduction object introduced to the user device 5 for a fee. In the present embodiment, the extracting and specifying unit 32 functions as an example of at least one of an extraction means or specification means.

[0059]

The acquisition unit 33 is implemented mainly by processing of the CPU 301. In the present embodiment, the acquisition unit 33 functions as a first acquisition means that acquires use history information (first history information) indicating a use history related to a function of the user device 5. In addition, in the present embodiment, the acquisition unit 33 functions as a second acquisition means for acquiring transaction history information (second history information) related to the user's transaction history. The transaction history information includes information related to the purchase history, contract history, and research history of the user device 5. The acquisition unit 33 may include a plurality of acquisition means. Further, the acquisition unit 33 acquires use history information related to the introduction objects used by the general users. The acquisition unit 33 acquires history information related to the specified introduction object. The acquisition unit 33 also acquires use history information of the user device 5 as the history information. In addition, the acquisition unit 33 acquires, as the history information, a combination of pieces of use history information in one or more user devices 5 owned by the customer associated with the same customer identification information. In addition to the history information, the acquisition unit 33 also acquires identification information of the introduction object and introduction date and time information. In the present embodiment, the acquisition unit 33 also functions simply as an example of the acquisition means.

[0060]

The display control unit 34 is implemented mainly by the processing of the CPU 301 on the display 307 and controls the display of various screens and information (data) on at least one of the communication terminal 4 or the user device 5. The display control unit 34 displays a display screen generated in compliance with, for example, Hyper Text Markup Language (HTML) on at least one of the display 407 of the communication terminal 4 or the display panel 540a of the user device 5 using a browser. In the present embodiment, the display control unit 34 functions as an example of a display control means. [0061]

The determination processing unit 35 is implemented mainly by processing of the CPU 301 and makes various determinations in the management apparatus 3. In the present embodiment, the determination processing unit 35 functions as an example of determination processing means.

[0062]

The calculation unit 36 is implemented mainly by processing of the CPU 301. The calculation unit 36 calculates the use amount of a specified introduction object by a predetermined user based on the history information. The calculation unit 36 also calculates the number of times the introduction object is used by a user different from the administrative user who introduced the introduction object, as the use amount. In the present embodiment, the calculation unit 36 functions as an example of a calculation means. [0063]

The generation unit 37 is implemented mainly by the processing of the CPU 301, and generates recommendation information notification screen data after the recommendation determination process is executed. Also, the generation unit 37 generates a notification in the case the use status based on the use history information matches a predetermined condition. Specifically, the generation unit 37 generates the notification in the case the use status based on the introduction object use history information specified by the extracting and specifying unit 32 matches the predetermined condition. Further, the generation unit 37 generates a notification indicating alternative introduction object information that indicates alternative introduction object that replaces the introduction object, in the case the use amount for the function or setting related to the specific introduction object calculated by the calculation unit 36 is equal to or less than a predetermined value. The generation unit 37 generates a notification including the fixed phrases and the like in advance, in the case the notification including fixed phrases and the like generated in a predetermined format is to be transmitted. Notifications generated as described above include, for example, notifications sent by email, notifications notified by an application, and the like.

In the present embodiment, the generation unit 37 functions as an example of generation means.

[0064] The registration management unit 38 is implemented mainly by processing of the CPU 301. The registration management unit 38 uses the user identification information and password transmitted by the communication terminal 4 to execute a user authentication process. The registration management unit 38 manages the administrative user and the general user related to the introduction object. The registration management unit 38 manages the user device 5 associated with the customer identification information for identifying the customer, the user associated with the customer identification information, and introduction object identification information for identifying the introduction object introduced in association with the customer identification information. A data table (each database (DB)) for performing the abovedescribed management is described below. In the present embodiment, the registration management unit 38 functions as an example of at least one of a registration means or a management means.

[0065]

The storing and reading unit 39 is implemented mainly by processing of the CPU 301 on at least one of the ROM 302, the EEPROM 304, or the HD 305, and stores various data (or information) in the storage unit 3000 or reads various data (or information) from the storage unit 3000. In the present embodiment, the storing and reading unit 39 functions as an example of a storing and reading means.

[0066]

User Information Management Table

FIG. 9 is a table presenting an example of a user information management table. The configuration of a data table described below is an example, and the configuration is not limited to this example. A user information management DB 3001 including the user information management table illustrated in FIG. 9 is constructed in the storage unit 3000 of the management apparatus 3. In the user information management table, at least one of the customer identification information or a customer name serves as a tab, and a user name, a user type, a password, and an email address are stored and managed in association with each other per user identification information divided in each tab. Among these pieces of information, the customer identification information and the customer name are identification information given to a customer X who uses the user device 5 in the management system 2. Examples of the customer identification information include “C0001”, “C0002”, and the like. The user identification information is information for identifying users included in (belonging to) the customer. Examples of the user identification information include “U0001”, “U0002”, and the like. The user name is the name of a user having user identification information. The user type indicates a type of user as a customer, and includes administrative user, general user, and the like. The password is identification information associated with the user identification information at the time of login when the information processing system 1 including the management system 2 is used, and is input by the user at the time of initial startup (at the time of login) or the like. The email address is an address when the user uses an email given to the user. In the present embodiment, the user information management table (user information management DB 3001) functions as an example of a user history information management means. Further, the user information management DB 3001 may store information indicating whether the management apparatus 3 transmits the recommendation information notification for each piece of user identification information. For example, the user identification information corresponding to the administrative user is stored in association with information indicating that the recommendation information notification is to be transmitted.

[0067]

Device Information Management Table

FIG. 10 is a table presenting an example of a device information management table. The configuration of a data table described below is an example, and the configuration is not limited to this example. A device information management DB 3002 including the device information management table illustrated in FIG. 10 is constructed in the storage unit 3000 of the management apparatus 3. In the device information management table, at least one of the customer identification information or the customer name serves as a tab, and a device type and address information are stored and managed in association with each other per device identification information (terminal identification information) divided in each tab. Among these pieces of information, the device identification information is information for identifying the user device 5 included in (belonging to) the customer. Examples of the device identification information include “D0001”, “D0002”, and the like. The device identification information includes information on the communication terminal 4 in addition to the information on the user device 5. The information on the communication terminal 4 is to be used when the management apparatus 3 notifies the communication terminal 4 of the recommended introduction object, and the calculated information, or the like. When the management apparatus 3 notifies the communication terminal 4 of the recommendation information or the like for recommending the introduction object, the management apparatus 3 specifies the communication terminal 4 from the device identification information based on the customer identification information serving as a notification object, and transmits the notification to the destination indicated by the address information. The user may be specified from the user identification information based on the customer identification information, and the notification may be transmitted to the email address. The device type is a type of apparatus of the user device 5, and examples of the device type include “MFP”, “scanner”, “facsimile”, “electronic whiteboard”, “projector”, “PC”, “smartphone”, and “interactive voice operation apparatus (smart speaker)”. The address information is, for example, an internet protocol (IP) address, and used for specifying and managing the user device 5 in the information processing system 1.

[0068]

In the device information management DB 3002, information indicating whether the management apparatus 3 transmits the recommendation information notification may be stored for each piece of device identification information. For example, the device identification information corresponding to the user device 5 and the communication terminal 4 managed by the administrative user is stored in association with information indicating that the recommendation information notification is to be transmitted.

[0069]

The device information management table is used for the following purpose. For example, in response to receiving log information from a device not managed by a first history information management table described below (for example, a device that has just been installed by the customer and has not yet been logged in the past) the device information management table is used to determine with which customer identification information to associate and store the log information. Alternatively, the device information management table is used when the management apparatus 3 determines to which device the log information is to be requested. In this case, the address information is used when the management apparatus 3 makes an inquiry to the user device 5. In the present embodiment, the device information management table (device information management DB 3002) functions as an example of a device history information management means.

[0070]

Use History Information Management Table

FIG. 11 is a table presenting an example of a use history information management table. The configuration of a data table described below is an example, and the configuration is not limited to this example. A use history information management DB 3003 including the use history information management table illustrated in FIG. 11 is constructed in the storage unit 3000 of the management apparatus 3. In the use history information management table, at least one of the customer identification information or the customer name serves as a tab, and the device type, a use history (item 1), the user identification information, the user name, a setting item, a use date and time, and the number of uses (use amount) are stored and managed in association with each other for each piece of device identification information divided in each tab. Among these information, the device type is information indicating the type of the user device 5, and indicates, for example, an MFP, a facsimile, a projector, and the like. The use history (item 1) is an example of first history information indicating the use history related to the function of the user device 5. Examples of the use history (item 1) include “business card copy”, “slip scan and copy”, “search”, “video viewing” and the like. In other words, the use history (item 1) is information indicating functions or applications executed by the user device 5. The information indicating the function is the name of the function and function identification information, and the information indicating the application is the name of the application and the application identification information. In the case one application includes multiple functions, in addition to the information indicating the application, information indicating the function used in the application may be stored. The user identification information is information that identifies the user who executed the function of the user device 5 or the application. The user name is the name of the user who executed the function of the user device 5 or the application. A setting item indicates a setting item and a setting value corresponding to a predetermined function set when using the function of the user device 5 or the application. Examples of the setting item include, for example, print settings and destinations. The use date and time indicates the date and time when the use history was accumulated (that is, the date and time when the function of the application was executed) or a predetermined period of time. The use amount represents the use amount of the use history (item 1) in the date and time given as the use date and time or in a predetermined period. The use amount may be the number of times the function or the application executes a predetermined process, the number of times execution is accepted, or the number and capacity of media, files, and data that have been processed. The management apparatus 3 is free to set the timing of acquiring the use history information (the number of uses or the use amount) related to the use history from the user device 5. The timing of the acquisition may be, for example, daily, in three-day intervals, or in ten-day intervals. For example, when the management apparatus 3 acquires predetermined use history information (the number of uses or the use amount) in ten-day intervals, use history information (the total number of uses or the total use amount) for ten days is extracted.

[0071]

Examples of the use history (item 1) managed in the use history information management table for the device type MFP include copy and print, scan, facsimile transmission and reception, and authentication. Examples of the use history (item 1) managed in the use history information management table for the device type electronic whiteboard (IWB) include projection, writing, cooperation between bases, and sharing of a result. Examples of the use history (item 1) managed in the use history information management table for the device type projector include projection and writing. The devices described above are devices that the management apparatus 3 transmits information to each user device.

[0072]

Examples of the use history (item 1) managed in the use history information management table for the device type smartphone include search, dithering, information sharing (social networking service (SNS)), call or email, viewing and listening of video, a still image, or music, and navigation (position, action history). In this case, the management apparatus 3 transmits information to the smartphone (PC) instead of the user device. In the present embodiment, the use history information management table (use history information management DB 3003) functions as an example of a use history information management means.

[0073]

Transaction History Information Management Table

FIG. 12 is a table presenting an example of a transaction history information management table. The configuration of data table described below is an example, and the configuration is not limited to this example. A transaction history information management DB 3004 including the transaction history information management table illustrated in FIG. 12 is constructed in the storage unit 3000 of the management apparatus 3. In the transaction history information management table, at least one of the customer identification information or the customer name serves as a tab, and a history type, a transaction history (item 2), a transaction date and time, and the number of transactions (the amount of transaction) are stored and managed in association with each other for each piece of user identification information divided in each tab. The history type is the type of transaction made by the user. Examples of the history type include “purchase”, “research”, “contract”, and the like. The transaction history (item 2) is an example of second history information indicating a transaction history of a transaction by the user. Examples of the transaction history (item 2) include “business card folder purchase”, “slip purchase”, “stamp purchase”, “operation status of sorting prints”, “video editing”, and the like. The transaction date and time indicates the date and time when the transaction history was accumulated or a predetermined period of time. The number of transactions (the amount of transaction) indicates the number of transactions of the transaction history (item 2) on the date and time given as the transaction date and time or in the predetermined period. As described above, the transaction history information includes the purchase history information related to a purchase history of a supply or the like, the contract history information related to a contract history of any of various services or licenses, and the research history information related to a research history of a questionnaire result or a monitoring result of a user environment. Since the history management server 6 does not manage the customer identification information, each transaction information collected by the management apparatus 3 is associated with the customer identification information to generate the transaction history information management DB 3004.

[0074]

In the case the history type is purchase and the purchase object is an office supply, examples of the transaction history (item 2) managed in the transaction history information management table include a business card folder, paper, ink, toner, a peripheral device, office furniture, office ware, and other office supplies. In the case the history type is purchase and the purchase object is a nursing care supply, examples of the transaction history (item 2) managed in the transaction history information management table include a nursing care supply. In the case the history type is purchase and the purchase object is construction or work, examples of the transaction history (item 2) managed in the transaction history information management table include a blackboard, a tool, conveyance, polishing, and a surveying instrument. In the case the history type is purchase and the purchase object is a safety sign, examples of the transaction history (item 2) managed in the transaction history information management table include a safety sign and a safety product. In the case the history type is purchase and the purchase object is crime and disaster prevention, examples of the transaction history (item 2) managed in the transaction history information management table include a crime prevention product and a disaster prevention product. In the case the history type is purchase and the purchase object is a store supply, examples of the transaction history (item 2) managed in the transaction history information management table include a cash register, a sealer, and a banner. In the case the history type is purchase and the purchase object is a packing supply, examples of the transaction history (item 2) managed in the transaction history information management table include a box, a shock absorbing member, and a tape. The above-listed contents serve as the history types managed as the purchase history included in the transaction history by the management apparatus 3.

[0075]

In the case the history type is a seminar, examples of the transaction history (item 2) managed in the transaction history information management table include a sign-up for a webinar. In the case the history type is electric power sales, examples of the transaction history (item 2) managed in the transaction history information management table include an electric power sales service. In the case the history type is a call, examples of the transaction history (item 2) managed in the transaction history information management table include a telephone service. In the case the history type is material for presentation, examples of the transaction history (item 2) managed in the transaction history information management table include an illustration and a template. In the case the history type is an article, examples of the transaction history (item 2) managed in the transaction history information management table include know-how, manner, and trend. The above are the history types managed by the management apparatus 3 as the contract history (contract date and time, contract details, etc.) in the transaction history.

[0076]

In the case the history information is customer information, examples of the transaction history (item 2) managed in the transaction history information management table include the number of devices of the company, the number of devices of another company, a customer attribute, an interest and inconvenience, and a contract period. In the case the history type is research, examples of the transaction history (item 2) managed in the transaction history information management table include monitoring information on network traffic. The above history types are managed by the management apparatus 3 as research histories (questionnaire response results, hearing results, monitoring results, etc.) in the transaction history. [0077]

The number of transactions (the amount of transaction) indicates the number of purchased items or the number of times of purchase when the history type is purchase, indicates a research result when the history type is research, and indicates a contract content, or the number of people or the number of devices subjected to contract objects when the history type is contract. In the present embodiment, the transaction history information management table (transaction history information management DB 3004) functions as an example of a transaction history information management means.

[0078]

Recommendation Condition Management Table

FIG. 13 is a table presenting an example of a recommendation condition management table. The configuration of data table described below is an example, and the configuration is not limited to this example. A recommendation condition management DB 3005 including the recommendation condition management table illustrated in FIG. 13 is constructed in the storage unit 3000 of the management apparatus 3. In the recommendation condition management table, items including a use item name (use history), recommendation condition 1, transaction item name (transaction history), and recommendation condition 2 are stored and managed in association with each piece of recommendation condition identification information. The recommendation condition identification information is identification information for identifying recommendation condition for recommending the introduction object such as an application. Examples of the recommendation condition identification information include “RC0001”, “RC0002”, and the like. The use item name (use history) indicates an item name used in the user device 5. Examples of the use item name include “business card copy” and “slip scan”. As the recommendation condition 1, a threshold value for recommending an item listed as a use item name is indicated. The transaction item name (transaction history) indicates an item name as a transaction history different from the use history in the user device 5. Examples of the transaction item name include an item name such as “business card folder purchase” or “slip purchase”. The recommendation condition 2 is a threshold value for recommending the item indicated by the transaction item name. The recommendation condition indicated by “RC0001” is described in the following. In the case the use item indicated as “business card copy”, which is a function of the user device 5, is used for 700 or more copies during a period indicated by the period a, and the number of “business card folder purchases” is 200 or more during the period indicated by the period a, the recommendation condition indicated by “RC0001” is determined to be satisfied. As a result, when the introduction object satisfies the above-described predetermined recommendation conditions for the use history and transaction history, an introduction is recommended to the predetermined customer. In the present embodiment, the recommendation condition management table (recommendation condition management DB 3005) functions as an example of a recommendation condition management means.

[0079]

Introduction Object Management Table FIG. 14 is a table presenting an example of an introduction object management table. The configuration of data table described below is an example, and the configuration is not limited to this example. An introduction object management DB 3006 including the introduction object management table illustrated in FIG. 14 is constructed in the storage unit 3000 of the management apparatus 3. In the introduction object management table, items including recommendation condition identification information, introduction object identification information, introduction object, and introduction object storage destination (purchase destination) are stored and managed in association with each piece of recommendation condition identification information. Among these items of information, the introduction object identification information is identification information for identifying the introduction object such as the application. Examples of the introduction object identification information include “RS0001” and “RS0002”. The introduction object indicates an entity such as an application recommended for the user device 5. Examples of the introduction object include “business card management application” or “billing management software”. The introduction object storage destination (purchase destination) is the location where the introduction object is stored, and is indicated by a uniform resource locator (URL), company name, or the like. In the present embodiment, the introduction object management table (introduction object management DB 3006) functions as an example of an introduction object management means. Further, the introduction object management table may include information indicating whether each introduction object is with or without charge. For example, in the case the introduction object is an application, the application may be with or without charge. Flag information indicating whether the application is with or without charge may be stored in association with the introduction object identification information.

[0080]

Introduction Information Management Table

FIG. 15 is a table presenting an example of an introduction information management table. The configuration of data table described below is an example, and the configuration is not limited to this example. An introduction information management DB 3007 including the introduction information management table illustrated in FIG. 15 is constructed in the storage unit 3000 of the management apparatus 3. In the introduction information management table, at least one of the customer identification information or the customer name is set as a tab, and items including the date and time of introduction, the user identification information, and the name of the user in charge of introduction are associated, stored, and managed for each piece of the introduction object identification information separated by each tab.

The date and time of introduction indicates the date and time when the introduction object was introduced, or the date and time when the introduction object was purchased or contracted. The user identification information is identification information that identifies the user who introduced the introduction object. The user in charge of introduction indicates the name of the user who introduced the recommended introduction object to the user device 5. In addition, the introduction information management table may store information indicating a contract form of the introduction object. For example, in a case where the introduction object is an application, a free contract form such as a trial license may be available, so in the case of a paid contract, flag information indicating that the contract is with charge may be stored in association with the introduction object identification information.

[0081]

In the present embodiment, the introduction information management table (introduction information management DB 3007) functions as an example of an introduction information management means. The introduction information management table stores all introduction objects installed by the user. The introduction information management table can store flag information indicating an introduction object introduced by the user based on the recommendation by the management apparatus 3 in association with the introduction object identification information. However, the introduction information management table may store just the introduction object introduced by the user based on the recommendation by the management apparatus 3, and may exclude the introduction object voluntarily introduced by the user regardless of the recommendation.

[0082] functional Configurations of Communication Terminal

With reference to FIGs. 5 and 7, functional configurations of the communication terminal 4 are described below. As illustrated in FIG. 7, the communication terminal 4 includes a data exchange unit 41, an operation reception unit 42, an acquisition unit 43, a display control unit 44 and a storing and reading unit 49. Each of these functional units is implemented by the instruction from the CPU 401 according to a program for the communication terminal 4 developed in the RAM 403 from at least one of the ROM 402, EEPROM 404, or the recording medium 414 to any of the hardware resources illustrated in FIG. 5. The communication terminal 4 further includes a storage unit 4000 implemented by at least one of the ROM 402, the EEPROM 404, or the recording medium 414 illustrated in FIG. 5. The storage unit 4000 stores a communication program (communication application) for communicating with each device and each terminal through the communication network 100, a browser application, a use status management application for displaying the use status of the introduction object, and the like.

[0083]

<<Each Functional Configuration of Communication Terminal>>

Configuration of each functional unit of the communication terminal 4 is described below in detail. The data exchange unit 41 of the communication terminal 4 illustrated in FIG. 7 is implemented mainly by processing of the CPU 401 on the network PF 411 and the short- range communication PF 408, and transmits or receives various data (or information) to and from each terminal or each apparatus through the communication network 100. In the present embodiment, the data exchange unit 41 functions as an example of at least one of the transmission means or the receiving means. [0084]

The operation reception unit 42 is implemented mainly by the CPU 401 processing signals generated through various operations received by at least one of the touch panel 412 or the pointing device 413. In the present embodiment, the operation reception unit 42 functions as an example of a reception means. [0085]

The acquisition unit 43 is implemented mainly by processing of the CPU 401 and acquires various types of information transmitted by the management apparatus 3. The acquisition unit 43 acquires, for example, the recommendation information included in the recommendation information notification response transmitted by the management apparatus 3. In the present embodiment, the acquisition unit 43 functions as an example of the acquisition means. [0086]

The display control unit 44 is implemented mainly by processing of the CPU 401 on the display 407, and controls displaying of various screens and information (data) in the communication terminal 4. The display control unit 44 uses, for example, a browser to display a display screen generated in HTML or the like on the display 407 of the communication terminal 4 (hereinafter, referred to simply as the display 407). The display control unit 44 controls the display 407 to display, for example, the acquired recommendation information. In the present embodiment, the display control unit 44 functions as an example of the display control means. [0087]

The storing and reading unit 49 is implemented mainly by processing of the CPU 401 on at least one of the ROM 402, the EEPROM 404, or the recording medium 414, and stores various data (or information) in the storage unit 4000 or reads various data (or information) from the storage unit 4000. In the present embodiment, the storing and reading unit 49 functions as an example of the storing and reading means. [0088]

With reference to FIGs. 6 and 7, functional configurations of the user device is described. As illustrated in FIG. 7, the user device 5 includes a data exchange unit 51, an operation reception unit 52, an acquisition unit 53, a display control unit 54, a control unit 55, an execution unit 56, a generation unit 57, and a storing and reading unit 59. These functional units are functions that are implemented by or means that are caused to function by operating any of the hardware resources illustrated in FIG. 6 in response to a command from the CPU 501 in accordance with a program for the user device 5 developed from at least one of the ROM 502a or the HD 508 to the RAM 502b. The user device 5 includes a storage unit 5000 implemented by at least one of the ROM 502a or the HD 508 illustrated in FIG. 6. [0089]

<<Each Functional Configuration of User Device>>

Configuration of each function unit of the user device 5 is described below in detail. The data exchange unit 51 of the user device 5 illustrated in FIG. 7 is implemented mainly by processing of the CPU 501 on the network I/F 550 and the short-range communication circuit 520, and transmits or receives various data (or information) to and from each terminal or each apparatus through the communication network 100. The data exchange unit 51 transmits the first history information indicating the use history related to a function of the user device that provides history information to the management apparatus 3. In the present embodiment, the data exchange unit 51 functions as an example of at least one of the transmission means or the receiving means.

[0090]

The operation reception unit 52 is implemented mainly by the CPU 501 processing signals generated through various operations received by at least one of the display panel 540a or the operation panel 540b of the control panel 540. In the present embodiment, the operation reception unit 52 functions as an example of the reception means. [0091]

The acquisition unit 53 is implemented mainly by processing of the CPU 501 and acquires various types of information transmitted by the management apparatus 3. The acquisition unit 53 acquires, for example, recommendation information included in the recommendation information notification response transmitted by the management apparatus 3, and application data (program or the like) related to any of various applications which are examples of the introduction object. In the present embodiment, the acquisition unit 53 functions as an example of the acquisition means.

[0092]

The display control unit 54 is implemented mainly by processing of the CPU 501 on the display panel 540a of the control panel 540, and controls displaying of various screens and information (data) in the user device 5. The display control unit 54 uses, for example, a browser to display a display screen created in HTML or the like on the control panel 540. In the present embodiment, an MFP is illustrated as an example of the user device 5, but the present disclosure is not limited to this example. Thus, the hardware resource of each functional unit of the user device 5 can be appropriately changed in accordance with the hardware resource included in each user device 5. In the present embodiment, the display control unit 54 functions as an example of the display control means.

[0093]

The control unit 55 is implemented mainly by processing of the CPU 501 and performs various types of control in the user device 5. In the present embodiment, the control unit 55 functions as an example of a control means.

[0094]

The execution unit 56 is implemented mainly by processing of the CPU 501, and starts various applications or the like, starts a print engine, executes a print process, and executes a projection process in the user device 5. In the present embodiment, the execution unit 56 functions as an example of an execution means.

[0095]

The generation unit 57 is implemented mainly by processing of the CPU 501, and generates various types of notification for transmitting to and displaying on the user device 5. In the present embodiment, the generation unit 57 functions as an example of a generation means. [0096]

The storing and reading unit 59 is implemented mainly by processing of the CPU 501 on at least one of the ROM 502a or the HD 508, and stores various data (or information) in the storage unit 5000 or reads various data (or information) from the storage unit 5000. In the present embodiment, the storing and reading unit 59 functions as an example of the storing and reading means.

[0097]

Use History Information Management Table

FIG. 16 is a table presenting an example of a use history information management table. The configuration of data table described below is an example, and the configuration is not limited to this example. A use history information management DB 5001 including the use history information management table illustrated in FIG. 16 is constructed in the storage unit 5000 of the user device 5. The use history information management DB 5001 includes items similar to those of the use history information management table forming the use history information management DB 3003 described above. Therefore, the description of each item is omitted here. Each user device 5 stores the use history information management table in the storage unit 5000 of the respective user device 5. In the present embodiment, the use history information management table (use history information management DB 5001) functions as an example of a use history information management means. [0098]

<Functional Configurations of History Management Server> With reference to FIGs. 4 and 7, functional configurations of the history management server are described in the following. As illustrated in FIG. 7, the history management server 6 includes a data exchange unit 61, an acquisition unit 63, a registration unit 68 and a storing and reading unit 69. These functional units are functions that are implemented by or means that are caused to function by operating any of the hardware resources illustrated in FIG. 4 in response to a command from the CPU 601 in accordance with a program for the history management server 6 developed from at least one of the ROM 602, the EEPROM 604, or the HD 605 to the RAM 603. The history management server 6 includes a storage unit 6000 implemented by at least one of the ROM 602, the EEPROM 604, or the HD 605 illustrated in FIG. 4. Further, the storage unit 6000 stores a communication program (communication application) for performing communication with each apparatus or each terminal through the communication network 100, a browser application, a history management application for managing transaction history information transmitted by the user device, and so forth.

[0099]

<<Each Functional Configuration of History Management Server>> Configuration of each functional unit of the history management server 6 is described below in detail. The data exchange unit 61 of the history management server 6 illustrated in FIG. 7 is implemented mainly by processing of the CPU 601 on the network I/F 611 and the short- range communication PF 608, and transmits or receives various data (or information) to or from each terminal or each apparatus through the communication network 100. In the present embodiment, the data exchange unit 61 functions as an example of at least one of the transmission means or the receiving means.

[0100]

The acquisition unit 63 is implemented mainly by processing of the CPU 601 and acquires transaction history information transmitted by the user device 5, the communication terminal 4, a computer of a person in charge of sales, or the like. In the present embodiment, the acquisition unit 63 functions as an example of the acquisition means. [0101] The registration unit 68 is implemented by processing of the CPU 601 and registers the transaction history information transmitted by the user device 5, the communication terminal 4, the computer of the person in charge of sales, or the like in a transaction history information management DB 6001. In the present embodiment, the registration unit 66 functions as an example of the generation means. [0102]

The storing and reading unit 69 is implemented mainly by processing of the CPU 601 on at least one of the ROM 602, the EEPROM 604 or the HD 605, and stores various data (or information) in the storage unit 6000, or reads various data (or information) from the storage unit 6000. In the present embodiment, the storing and reading unit 69 functions as an example of the storing and reading means. [0103]

Transaction History Information Management Table

FIG. 17 is a table presenting an example of a transaction history information management table. The configuration of data table described below is an example, and the configuration is not limited to this example. A transaction history information management DB 6001 including the transaction history information management table illustrated in FIG. 17 is constructed in the storage unit 6000 of the history management server 6. In the transaction history information management table, items including the history type, a transaction history (item 2), a transaction date and time, and the number of transactions (the amount of transaction) are stored and managed in association with each piece of user identification information. These items correspond to the respective items of the transaction history information management table managed by the management apparatus 3. In other words, the content of each item of the transaction history information management table related to a particular customer, transmitted by the history management server 6 that manages the transaction history information per customer is reflected in the corresponding item of the transaction history information management table managed by the management apparatus 3. In the present embodiment, the transaction history information management table (transaction history information management DB 6001) functions as an example of a transaction history information management means.

[0104]

With reference to FIGs. 4 and 8, functional configurations of the application distribution server are described in the following. As illustrated in FIG. 8, the application distribution server 7 includes a data exchange unit 71, an acquisition unit 73, an execution unit 76, and a storing and reading unit 79. These functional units are functions that are implemented by or means that are caused to function by operating any of the hardware resources illustrated in FIG. 4 in response to a command from the CPU 701 in accordance with a program for the application distribution server 7 developed from at least one of the ROM 702, the EEPROM 704, or the HD 705 to the RAM 703. The application distribution server 7 includes a storage unit 7000 implemented by at least one of the ROM 702, the EEPROM 704, or the HD 705 illustrated in FIG. 4. Further, the storage unit 7000 stores a communication program (communication application) for performing communication with each apparatus or each terminal through the communication network 100, a browser application, various data included in an application group, a function execution application for executing a predetermined function transmitted by the user device 5, an application as an introduction object to be installed in the user device 5, and so forth. As described above, the application distribution server 7 may use a generally used external server that is connected through the communication network 100. The functional configuration in that case may correspond to the hardware specifications of the external server.

[0105]

<<Each Functional Configuration of Application Distribution Server>> Configuration of each functional unit of the application distribution server 7 is described below in detail. The data exchange unit 71 of the application distribution server 7 illustrated in FIG. 8 is implemented mainly by processing of the CPU 701 on the network I/F 711 and the short-range communication I/F 708, and transmits and receives various data (or information) to and from each terminal or each apparatus through the communication network 100. In the present embodiment, the data exchange unit 71 functions as an example of at least one of the transmission means or the receiving means. For example, the data exchange unit 71 receives a request for an application of an introduction object from the user device 5, and distribute the application of the introduction object to the user device 5.

[0106]

The acquisition unit 73 is implemented mainly by processing of the CPU 701, and acquires an application distribution request transmitted by the user device 5, a processing request related to the user device 5 and transmitted by the management apparatus 3, and so forth. In the present embodiment, the acquisition unit 73 functions as an example of the acquisition means. [0107]

The execution unit 76 is implemented mainly by processing of the CPU 701, and in the present embodiment, the execution unit 76 functions as an example of the execution means. For example, in response to a request to execute a predetermined function received from the user device 5, the execution unit 76 provides the predetermined function to the user device 5. [0108]

The storing and reading unit 79 is implemented mainly by processing of the CPU 701 on at least one of the ROM 702, the EEPROM 704, or the HD 705, and stores various data (or information) in the storage unit 7000 or reads various data (or information) included in the application group from the storage unit 7000. In the present embodiment, the storing and reading unit 79 functions as an example of the storing and reading means.

[0109]

Various Application Data

Various application data managed by the application distribution server 7 or managed by an external server or the like that can communicate with the application distribution server 7 may comply with a management method, a specification, or the like in the server that manages the various application data. Furthermore, the data structure of various application data is not limited to any particular data structure.

[0110]

[Processes or Operations of Embodiment]

With reference to FIGs.18 to 28, processes or operations of the information processing system according to the present embodiment are described below.

[0111]

< Authentication Process >

A user authentication process and a device registration process in the information processing system 1 are described. FIG. 18 is a sequence diagram illustrating an example of the user authentication process and the device registration process. In step Sil, the display control unit 44 of the communication terminal 4 controls the display 407 of the communication terminal 4 to display an authentication screen.

[0112]

Example Display Screen

FIG. 19 is a diagram illustrating an example of a screen displayed to execute user authentication in the communication terminal. As illustrated in FIG. 19, the display control unit 44 controls the display 407 of the communication terminal 4 to display a login authentication screen 4001. The login authentication screen 4001 displays an input area for entering a user identification information and a password, and a login button. A user can input the user identification information and the password in these input areas and operate a login button.

[0113]

Referring back to FIG. 18, the operation reception unit 42 receives an authentication operation in step S12.

[0114]

In step S 13, the data exchange unit 41 transmits a user authentication request to the management apparatus 3. Accordingly, the data exchange unit 31 of the management apparatus 3 receives the user authentication request transmitted by the communication terminal 4. The user authentication request includes user identification information and password.

[0115]

In step S14, the registration management unit 38 of the management apparatus 3 executes the user authentication process. Specifically, the registration management unit 38 uses the user identification information and password received in step S13 as search keys, and uses the user information management DB 3001 (see FIG. 9) associated in advance with the customer identification information indicating the customer to which the user belongs to retrieve the corresponding login information. Then, the registration management unit 38 confirms whether the received user identification information and password match the read user identification information and password. When matching is verified, the input user identification information and password are considered to be correct.

[0116]

In step S 15, the data exchange unit 31 transmits a user authentication response for the user authentication request received in step S13 to the communication terminal 4. Accordingly, the data exchange unit 41 of the communication terminal 4 receives the user authentication response transmitted by the management apparatus 3. The user authentication response includes information indicating a user authentication result (for example, authentication OK). [0117]

Through the above-described processing, the communication terminal 4 and the management apparatus 3 succeed in a login authentication process and a session establishment process for establishing a session, which are performed in general, and communication with each other becomes available.

[0118]

In step S21, the display control unit 54 of the user device 5 causes the display panel 540a to display a device registration screen. A predetermined login authentication process and a session establishment process for establishing the session are supposed to be successful between the user device 5 and the management apparatus 3, and the user device 5 and the management apparatus 3 are communicable with each other.

[0119]

Example Display Screen

FIG. 20 is a diagram illustrating an example of a screen displayed during device registration in the user device. As illustrated in FIG. 20, a device registration screen 5011 is displayed on the display panel 540a of the user device 5 by the display control unit 54. On the device registration screen 5011, an input area 5012 for inputting the device type and device name, and a registration button 5051 are displayed. The user inputs the device type and device name in the input area 5012 and operate the registration button 5051. The device registration process may be performed without user input through communication between the user device 5 and the management apparatus 3 instead of the user input on the device registration screen illustrated in FIG. 20.

[0120]

Referring back to FIG. 18, the operation reception unit 52 receives a device registration operation in step S22.

[0121]

In step S23, the data exchange unit 51 transmits a device registration request to the management apparatus 3. Accordingly, the data exchange unit 31 of the management apparatus 3 receives the device registration request transmitted by the user device 5. The device registration request includes device identification information, device type information, and address information indicating a destination of the user device 5. [0122]

In step S24, the registration management unit 38 of the management apparatus 3 performs the device registration process.

Specifically, the registration management unit 38 registers the device identification information, the device type information, and the address information indicating the destination of the user device 5 included in the device registration request received in step S23 in the device information management DB 3002 (see FIG. 10), in association with the customer identification information indicating the customer to which the user belongs in advance. Accordingly, the management apparatus 3 is associated with the user device 5 in the information processing system 1 (management system 2).

[0123]

In step S25, the data exchange unit 31 transmits a device registration response as a response to the device registration request received in step S23 to the user device 5. Accordingly, the data exchange unit 51 of the user device 5 receives the device registration response transmitted by the management apparatus 3. The device registration response may include a message indicating completion of device registration, a registration completion flag, and the like.

[0124]

As described above, the user device 5 may perform a login process to the management apparatus 3 before the processing of step S21. In the login process, the user device 5 transmits a login request including the user name and the password to the management apparatus 3, and the management apparatus 3 authenticates the user based on the information included in the login request and the information stored in the user information management DB 3001 (see FIG. 9). Accordingly, the management apparatus 3 is able to identify the user identification information or the customer identification information corresponding to the user.

[0125]

Further, the processes of steps SI 1 to S15 and the processes of steps S21 to S25 described above may be performed asynchronously with each other.

[0126]

In the information processing system 1, the history management server 6 and the application distribution server 7 that are connected to each other through the communication network 100 are communicable also with the management apparatus 3 and the user device 5.

[0127]

In the management system according to the present embodiment, for example, in executing the processes of steps S 13 and S15 described above, another device or the like may reside between the communication terminal 4 and the management apparatus 3. In other word, information (data) transmitted or received between the communication terminal 4 and the management apparatus 3 may be transmitted or received through another device or the like. The above-described configuration can be applied even when another processing step is present between the communication terminal 4 and the management apparatus 3. [0128]

Further, in the management system according to the present embodiment, for example, in executing the processes of steps S23 and S25 described above, another device or the like may reside between the management apparatus 3 and the user device 5. In other words, each information (data) transmitted or received between the management apparatus 3 and the user device 5 may be transmitted or received through another device or the like. The abovedescribed configuration can be applied even when another processing step is present between the communication terminal 4 and the management apparatus 3.

[0129]

Registration Process of History Information>

A registration process of history information is described in the following. FIG. 21 is a sequence diagram illustrating an example of a history information acquisition process. In step S31, the data exchange unit 31 of the management apparatus 3 transmits a use history information acquisition request to the user device 5. Accordingly, the data exchange unit 51 of the user device 5 receives the use history information acquisition request transmitted by the management apparatus 3. At this time, the use history information acquisition request includes device identification information for identifying the user device 5.

The user device 5 may periodically transmit history information to the management apparatus 3. In this case, the management apparatus 3 can omit the process of step S31.

[0130]

In the example illustrated in FIG. 21, the management apparatus 3 acquires the use history information for each customer identified by the customer identification information. At this time, the management apparatus 3 specifies at least one user device 5 associated with the customer identification information based on information on management of customer (such as the customer identification information), and transmits the use history information acquisition request to each of the specified user device 5 sequentially or collectively. Accordingly, the management apparatus 3 transmits the use history information acquisition request to each of the plurality of user devices 5 owned by the customer. As a result, the management apparatus 3 can manage the acquired use history information in association with the customer identification information managed in the use history information management DB 3003 (see FIG. 11).

[0131]

In step S32, the storing and reading unit 59 of the user device 5 reads the use history information. Specifically, the storing and reading unit 59 searches the use history information management DB 5001 (see FIG. 16) using the device identification information received in step S31 as a search key to read the use history information related to the corresponding use history. The use history information read at this time is an example of first history information.

[0132] In step S33, the data exchange unit 51 transmits a use history information acquisition response as a response to the use history information acquisition request received in step S31 to the management apparatus 3. Accordingly, the data exchange unit 31 of the management apparatus 3 receives the use history information acquisition response transmitted by the user device 5, and the acquisition unit 33 acquires the use history information acquisition response. At this time, the use history information acquisition response includes the device identification information for identifying the user device 5 and the read use history information. The use history information further includes the device type, information corresponding to the use history (item 1), date and time of use (or period), and use amount. In other words, the acquisition unit 33 acquires information including information corresponding to the use history (item 1), use date and time (or period), and use amount as the first history information indicating the use history related to the function of the user device 5. The process of step S32 can be performed by each of the user devices 5 that have received the use history information acquisition request.

[0133]

In step S34, the registration management unit 38 of the management apparatus 3 registers the use history information received in step S33. Specifically, the registration management unit 38 registers items of information including the device identification information, the device type, the use history (item 1), the use date and time, and the number of uses (the use amount) received in step S33 in the corresponding items managed in the use history information management DB 3003 (see FIG. 11). The registration management unit 38 performs registration so that use histories are not duplicated. The management apparatus 3 identifies the customer identification information corresponding to the device identification information based on the received device identification information. As a result, the management apparatus 3 can manage the use history information for each user device 5 in association with the customer identification information.

[0134]

In step S35, the data exchange unit 31 transmits a transaction history information acquisition request to the history management server 6. Accordingly, the data exchange unit 61 of the history management server 6 receives the transaction history information acquisition request transmitted by the management apparatus 3. At this time, the transaction history information acquisition request includes the user identification information for identifying the user. In the case the history management server 6 manages the transaction history information in association with the customer identification information, the customer identification information may be included in the transaction history information acquisition request instead of the user identification information.

[0135]

In step S36, the storing and reading unit 69 of the history management server 6 reads the transaction history information. Specifically, the storing and reading unit 69 searches the transaction history information management DB 6001 (see FIG. 17) using the user identification information received in step S35 as a search key to read the transaction history information related to a transaction history as an example of corresponding second history information.

[0136]

In step S37, the data exchange unit 61 transmits a transaction history information acquisition response as a response to the transaction history information acquisition request received in step S35 to the management apparatus 3.

Accordingly, the data exchange unit 31 of the management apparatus 3 receives the transaction history information acquisition response transmitted by the history management server 6, and the acquisition unit 33 acquires the transaction history information acquisition response. At this time, the transaction history information acquisition response includes the user identification information and the read transaction history information.

The transaction history information further includes history type, information corresponding to transaction history (item 2), transaction date and time (or period), and number of transactions (amount of transaction). In other words, the acquisition unit 33 acquires information including the history type, the transaction date and time (or period), and the number of transactions (the amount of transaction) related to the transaction history (item 2) indicating a history different from the use history (item 1) managed by the user device 5. [0137]

In step S38, the registration management unit 38 of the management apparatus 3 registers the transaction history information included in the transaction history information acquisition response received in step S37 of registering the transaction history information. Specifically, the registration management unit 38 registers the transaction history information corresponding to the user identification information received in step S37 in the items of the history type and the transaction history (item 2) stored in the transaction history information management DB 3004 (see FIG. 12). The registration management unit 38 registers respective items of information in the corresponding items including, for example, the history type, the transaction history (item 2), the transaction date and time, and the number of transactions (the amount of transaction) as the transaction history information transmitted by the history management server 6 and having the user identification information “U0001”. In this case, the extracting and specifying unit 32 of the management apparatus 3 searches the transaction history information management DB 3004 (see FIG. 12) using the received user identification information as a search key to specify corresponding customer identification information. Accordingly, the management apparatus 3 can manage the transaction history information for each user in association with the customer identification information.

[0138]

Among the use history information received in step S33, the device type may be registered in advance in each data table by the management apparatus 3 in association with the device identification information. In this case, the use history information transmitted by the user device 5 does not have to include the device type. As described above, the data exchange unit 41 of the communication terminal 4 may transmit a procedure request regarding website purchase or contract to the history management server 6. The user makes the procedure request after performing the login process. In the login process, the user enters the user name, password, and the like, and refers to the additional drawing (user management information) to authenticate the user. As a result, the history management server is able to identify the user identification information and customer identification information of the user, and to manage the procedure request and history information in association with the user identification information or the customer identification information. In this case, the history management server 6 may register the transaction history information corresponding to the procedure request in the transaction history information management DB 6001 (see FIG. 17), and the data exchange unit 61 may transmit a response to the communication terminal 4.

[0140]

Further, the data exchange unit 41 of the communication terminal 4 may transmit a procedure request regarding website purchase or contract to the history management server 6 through a purchase site separately provided in the information processing system 1. In this case, history management server 6 may acquire transaction information corresponding to the procedure request from an external server that provides a purchase site. After that, the data exchange unit 61 of the history management server 6 may transmit a procedure response regarding website purchase or contract to the communication terminal 4.

[0141]

For the procedure request related to the purchase or the contract through the web site, an access may be made using a telephone or a facsimile. In this case, an operator of the history management server 6 may manually input information to the history management server 6 using a PC or the like additionally provided for the information processing system 1. In this case, the operator also inputs the user identification information or the customer identification information. Then, the history management server 6 may register corresponding transaction information in the transaction history information management DB 6001 (see FIG. 17), and the data exchange unit 61 may transmit a response to the PC.

[0142]

In the management system according to the present embodiment, for example, another device or the like may reside between the management apparatus 3 and the history management server 6 in executing the processes of steps S35 and S37 described above. In other words, each information (data) transmitted or received between the management apparatus 3 and the history management server 6 may be transmitted or received through another device or the like. The above-described configuration can be applied even when another processing step is present between the management apparatus 3 and the history management server 6. [0143]

Each processing described with reference to FIG. 21 may be periodically executed, or may be executed in response to receiving a notification request for an introduction object by the management apparatus 3 from the communication terminal 4 or the user device 5.

[0144]

A recommendation determination process executed by the management apparatus 3 is described in the following. FIG. 22 is a sequence diagram illustrating an example of the recommendation determination process. As illustrated in FIG. 22, the functional units including the determination processing unit 35 of the management apparatus 3 perform the recommendation determination process in step S41. The management apparatus 3 may perform the recommendation determination process in response to a request from the communication terminal 4 or the user device 5, or may periodically perform the recommendation determination process. Specifically, the management apparatus 3 makes various determinations related to recommendation of the introduction object, which is an example of an introduction object to be recommended to the user device 5.

[0145]

<<Details of Recommendation Determination Process>>

Details of the recommendation determination process are described in the following. FIG. 23 is a flowchart presenting an example of the recommendation determination process. The flowchart described below is an example of the present embodiment, and the present embodiment is not limited to this example.

[0146]

In step S41-1, the extracting and specifying unit 32 of the management apparatus 3 specifies the customer identification information. Specifically, the extracting and specifying unit 32 specifies the customer identification information from the customer identification information stored in the user information management DB 3001 or the device information management DB 3002. When the recommendation determination process is performed in response to a recommendation information notification request transmitted by the communication terminal 4 or the user device 5, the device information management DB 3002 (see FIG. 10) is searched using the device identification information included in the recommendation information notification request as a search key, or the user information management DB 3001 (see FIG. 9) is searched using the user identification information included in the recommendation information notification request as a search key to specify corresponding customer identification information.

[0147]

In step S41-2, the extracting and specifying unit 32 extracts the use history information corresponding to the customer identification information. Specifically, the extracting and specifying unit 32 searches the use history information management DB 3003 (see FIG. 11) using the customer identification information specified in step S41-1 as a search key to extract corresponding use history information. The use history information management DB 3003 stores history information of one or more devices for each customer identification information. Note that even in the case the use history information and the customer identification information are not associated in the use history information management DB 3003, the extracting and specifying unit 32 is able to extract the history information corresponding to the customer identification information. At this time, based on the device management information in the use history information management DB 3003, the extracting and specifying unit 32 identifies all device identification information corresponding to the customer identification information specified in step S41-1. For example, in the case the customer identification information specified in step S41-1 is “C0001”, the extracting and specifying unit 32 extracts “D0001”, “D0002”, “D0003”, and “D0004” as the device identification information. Subsequently, the extracting and specifying unit 32 extracts history information corresponding to each of the extracted device identification information. Specifically, the extracting and specifying unit 32 extracts history information corresponding to the identified device identification information from the use history information management DB 3003. The history information to be extracted is, for example, respective pieces of use history information corresponding to the device identification information “D0001”, “D0002”, “D0003”, and “D0004”, among the plurality of pieces of use history information stored in the use history information management DB 3003.

[0148]

In step S41-3, the extracting and specifying unit 32 extracts the transaction history information corresponding to the customer identification information. Specifically, the extracting and specifying unit 32 searches the transaction history information management DB 3004 (see FIG. 12) using the customer identification information specified in step S41-1 as a search key to extract corresponding transaction history information. The transaction history information management DB 3004 stores one or more pieces of transaction history information for each customer identification information. Even in a case the transaction history information and the customer identification information are not associated in the transaction history information management DB 3004, the extracting and specifying unit 32 is able to extract history information corresponding to the customer identification information. At this time, based on the user identification information in the transaction history information management DB 3004, the extracting and specifying unit 32 specifies the user identification information corresponding to the customer identification information specified in step S41-1. For example, in the case the customer identification information specified in step S41-1 is “C0001”, the user identification information “U0001” and “U0002” are extracted. Subsequently, the extracting and specifying unit 32 extracts history information corresponding to each of the extracted user identification information. Specifically, the extracting and specifying unit 32 extracts history information corresponding to all the identified user identification information from the transaction history information management DB 3004. The history information to be extracted is, for example, the transaction history information corresponding to the user identification information “U0001” and “U0002” among a plurality of pieces of transaction history information stored in the transaction history information management DB 3004.

[0149]

In step S41-4, the extracting and specifying unit 32 extracts the recommendation condition. Specifically, by searching the recommendation condition management DB 3005 (see FIG. 13), a recommendation condition (recommendation condition 1, recommendation condition 2) associated with any one of the recommendation condition identification information from among a plurality of recommendation conditions is extracted. For example, the extracting and specifying unit 32 extracts “business card copy” as the use item name corresponding to the recommendation condition identification information “RC0001”, “700 sheets > period a” as the recommendation condition 1, “purchase business card folder” as the transaction item name, and as the recommendation condition 2, “200 pieces > period a” is extracted. [0150]

In step S41-5, the determination processing unit 35 determines whether the extracted history information satisfies the recommendation condition. Specifically, the determination processing unit 35 and the calculation unit 36 aggregate the history information corresponding to the use item names specified in the recommendation condition 1 during the period specified in the recommendation condition 1. For example, the determination processing unit 35, together with the calculation unit 36, identifies the history information whose use item name is “business card copy” and whose use date and time is included in the period a, among the history information stored in the use history information management DB 3003, and calculates the total value of the use amount. The start point or end point of the period a may be set according to the recommendation condition, or may be determined based on the date and time when the recommendation determination process is executed. In addition, the determination processing unit 35 and the calculation unit 36 aggregate history information corresponding to the transaction item name specified in the recommendation condition 2 during the period specified in the recommendation condition 2. For example, the determination processing unit 35, together with the calculation unit 36, extracts history information in which the transaction item name is “business card folder purchase” and the transaction date and time is included in the period a, among the history information stored in the transaction history information management DB 3004 and specifies and calculates the total value of the number of transactions (amount of transaction).

[0151]

Then, the determination processing unit 35 determines whether the calculated total value satisfies the recommendation condition.

For example, the determination processing unit 35 determines that the recommendation condition 1 is satisfied when the total value calculated based on the use history information management DB 3003 is 700 or more. Further, the determination processing unit 35 determines that the recommendation condition 2 is satisfied when the total value calculated based on the transaction history information management DB 3004 is 200 or more. [0152] Based on determination that the extracted history information matches both the recommendation condition 1 and recommendation condition 2 (step S41-5: YES), the extracting and specifying unit 32 extracts an introduction object corresponding to the recommendation condition determined to be matching in step S41-6. Specifically, the extracting and specifying unit 32 searches the introduction object management DB 3006 (see FIG. 14) using the recommendation condition identification information corresponding to the recommendation condition determined to be matching the recommendation condition in step S41-5 as a search key and extracts the corresponding introduction object. [0153]

In step S41-7, the determination processing unit 35 determines whether all recommendation conditions have been confirmed. Based on determination that all recommendation conditions have been confirmed (step S41-7: YES), the process proceeds to step S41-8.

[0154]

On the other hand, based on determination that all the recommendation conditions have not been confirmed (step S41-7: NO), the determination processing unit 35 extracts other recommendation conditions (step S41-9), and then returns to the process of step S41-5. [0155]

In step S41-8, the determination processing unit 35 determines whether history information of all customer identification information has been confirmed. Based on determination that the history information of all customer identification information has been confirmed (step S41-8: YES), the determination processing unit 35 completes this workflow. [0156]

Based on determination that the history information of all the customer identification information has not been confirmed (step S41-8: NO), the determination processing unit 35 identifies other customer identification information (step S41-10), and then returns to processing in step S41-2.

[0157]

The management apparatus 3 repeats the above-described processes from steps S41-1 to S41- 5 by the number of extracted pieces of customer identification information. In executing the recommendation determination process in response to the recommendation information notification request sent by the communication terminal 4 or the user device 5, since the management apparatus 3 checks the history information for the user corresponding to the device identification information or customer identification information included in the request, the processing described in steps S41-8 and S41-10 is omitted.

[0158]

Referring back to FIG. 22, in step S42, the generation unit 37 of the management apparatus 3 generates recommendation information notification screen data. Specifically, the generation unit 37 generates the recommendation information notification screen data for recommending the recommended introduction object (for example, the “business card management application” determined in step S41) to the user device 5. The management apparatus 3 may store the recommendation information notification screen generated in step S42 or information on the introduction object determined in step S41 in association with the customer identification information. Accordingly, in response to receiving a request from the communication terminal 4 or the user device 5 to transmit the recommendation information notification, the management apparatus 3 transmits the recommendation information notification screen based on the recommendation information notification screen generated in advance or the information on the introduction object.

[0159]

In step S43, the data exchange unit 31 transmits a recommendation information notification to the communication terminal 4. For example, when the recommendation determination process is performed in response to a recommendation information notification request transmitted by the communication terminal 4 or the user device 5, the recommendation information notification is transmitted to the communication terminal 4 or the user device 5 that transmitted the recommendation information notification request. The data exchange unit 31 may transmit the recommendation information notification based on the address information stored in the device information management DB 3002 or the email address stored in the user information management DB 3001. In this case, the data exchange unit 31 may transmit the recommendation information notification to the email address of the administrative user among a plurality of email addresses stored in the user information management DB 3001 or to the user device 5 or the communication terminal 4 managed by the administrative user among a plurality of pieces of address information stored in the device information management DB 3002. Accordingly, the data exchange unit 41 of the communication terminal 4 receives the recommendation information notification transmitted by the management apparatus 3. Further, the communication terminal may acquire the recommendation information notification from an external server such as a mail server. The recommendation information notification includes recommendation information notification screen data, introduction object (application name) as the recommendation information, comments, link information (for example, URL of a web page) in which the introduction object is stored, and the like.

[0160]

In step S44, the display control unit 44 of the communication terminal 4 causes the display 407 to display the recommendation information notification screen included in the recommendation information notification received in step S43. The communication terminal 4 may display the recommendation information notification screen by accessing a web page provided by the management apparatus 3. For example, the management apparatus 3 performs a user authentication process in response to a user authentication request received from the communication terminal 4, and identifies the customer identification information to which the authenticated user belongs. Then, the communication terminal 4 is provided with the recommendation information notification screen related to the identified customer identification information. In this case, step S43 can be omitted.

[0161]

Example Display Screen

FIG. 24 is a diagram illustrating an example of a screen displaying the recommendation information notification. As illustrated in FIG. 24, the display control unit 44 controls the display 407 of the communication terminal 4 to display a recommendation information notification screen 4011. On the recommendation information notification screen 4011, the name of the introduction object extracted by the management apparatus 3 corresponding to the user device 5 (for example, “business card management application”), a comment to the recommendation, a link display field 4012 indicating a URL of a storage destination of the introduction object, and the like are displayed. The URL of the storage destination of the introduction object is information stored in the introduction object management DB 3006 (see FIG. 14) and stored as the introduction object storage destination (purchase destination) associated with the introduction object identification information. The user confirms the recommendation information notification screen 4011 and by performing operations such as accessing the URL of the storage location of the introduction object in the link display field 4012, the user is enabled to introduce the introduction object (in this case, business card management application). This is also the case when the management apparatus 3 transmits the recommendation information notification to each user device 5. The storage destination URL of the introduction object may be the URL of the application distribution server 7, or may be the URL of an application registration dedicated server that is connected to the application distribution server 7 and registers the application. When the user checks the recommendation information notification screen 4011 and then operates a confirmation button 4051, the screen can be transitioned to another screen. Since such a screen is displayed on the communication terminal 4, the user using the communication terminal 4 recognizes what kind of introduction object is available for the user device 5. Further, the user can acquire information related to the introduction object by making an access to the management apparatus 3, an external server, or the like based on link information included in the recommendation information notification.

[0162]

Purchase or contract of an introduction object based on the recommendation information performed by the user is described. As described in step S41, the recommendation information included in the recommendation information notification includes, for example, the storage destination of the introduction object, or the URL of the web page for purchasing or contracting the introduction object. Referring back to FIG. 22, processing including a procedure registration process is described below.

[0163]

In step S45, the operation reception unit 42 receives an operation on a link. Specifically, the operation reception unit 42 receives an access to the URL or the like of the web page indicated by predetermined link information displayed in the link display field 4012 illustrated in FIG. 24.

[0164]

In step S46, the data exchange unit 41 transmits a procedure request to the management apparatus 3.

For example, in the case the user confirms the recommendation information and wishes to install the introduction object, the user accesses the web page and transmits the procedure request for purchasing or contracting the introduction object. Accordingly, the data exchange unit 31 of the management apparatus 3 receives the procedure request transmitted by the communication terminal 4. At this time, the procedure request includes the user identification information, the customer identification information, and the introduction object identification information in addition to the URL information of the web page as the link information for which access was received in step S45.

[0165]

In step S47, the registration management unit 38 of the management apparatus 3 performs a procedure registration. Specifically, the registration management unit 38 executes processing related to the procedure registration for introducing the introduction object, such as purchase or contract of the introduction object, based on the procedure request received in step S46. The procedure registration process includes storing the procedure request and notifying predetermined personnel to proceed with a purchase or contract process based on the procedure request. The processing related to the procedure registration also includes a process of registering the customer identification information, the introduction object identification information on the introduction object related to the purchase or the contract, and date and time information indicating the date and time of receiving the procedure request or the date and time of executing the procedure registration in association with each other. At this time, the management apparatus 3 identifies the customer identification information related to the user identification information included in the procedure request. As a result, the generation unit 37 can generate the introduction information as illustrated in the introduction information management DB 3007 (see FIG. 15). Consequently, the management apparatus 3 can manage an introduction object that is recommended to a predetermined user by the management apparatus 3 and that is purchased or contracted by the recommended predetermined user, instead of an object that is purchased or contracted regardless of the recommendation by the management apparatus 3. Note that when the generation unit 37 generates introduction information through the recommendation information notification screen, flag information indicating that the software is an introduction object introduced by the user based on the recommendation by the management apparatus 3, in association with the introduction object identification information may be stored.

[0166]

An example of a case where the introduction object is a native application (an application that is to be installed in the user device 5) is described below. In the case the introduction object is the native application, the management apparatus 3 performs a license assignment process on the user device 5 or the user belonging to the customer of the application in the procedure registration. At this time, the application distribution server 7 may perform processing such as serial number confirmation and licensing.

[0167]

In step S48, the data exchange unit 51 of the user device 5 transmits the application serial number to the management apparatus 3. Accordingly, the data exchange unit 31 of the management apparatus 3 receives the application serial number transmitted by the user device 5. At this time, the data exchange unit 51 may transmit the device identification information of the user device 5. Accordingly, the management apparatus 3 stores the device identification information of the user device 5 in which the application has been introduced in the introduction information management DB 3007 in association with the introduction object identification information.

[0168]

In step S49, the management apparatus 3 confirms the application serial number received in step S48.

[0169]

In step S50, the data exchange unit 31 transmits an application serial number input response as a response to the application serial number received in step S48. Accordingly, the data exchange unit 51 of the user device 5 receives the application serial number input response transmitted by the management apparatus 3.

[0170]

In step S51, the data exchange unit 31 of the management apparatus 3 transmits a procedure response as a response to the procedure request received in step S46 to the communication terminal 4. Accordingly, the data exchange unit 41 of the communication terminal 4 receives the procedure response transmitted by the management apparatus 3.

[0171]

In step S52, the execution unit 56 of the user device 5 that has received the application number input response in step S50 installs the application indicated by the application serial number in a predetermined area of the storage unit 5000. The application may be downloaded to the user device 5 through the network, or the application may be downloaded to the user device 5 by attaching a recording medium storing the application to the user device 5. Furthermore, in response to a completion of the installation of the application, the user device 5 may transmit the introduction object identification information and the device identification information indicating the installed application. Accordingly, the management apparatus 3 updates the introduction information management DB 3007. The processing of steps S46 to S51 and the processing of steps S48 to S52 described above may be performed asynchronously with each other, and the processing order does not matter.

[0172] In another embodiment of the processing illustrated in FIG. 22, the recommendation information notification request may be transmitted from the communication terminal 4 to the management apparatus 3 as described above. [0173]

The installation of the application is an example of an introduction process for enabling the user device 5 to use the application. For example, in the case of a native application that becomes available by being installed on the user device 5, the user device 5 installs the application as an introduction process. On the other hand, in the case of a web application whose functions are provided in cooperation with an external server such as the application distribution server 7, the following processing is performed as the introduction process. The user device 5 displays a shortcut to a browser application or the like on a home screen displayed on the display panel 540a of the user device 5, and performs setting for making an access to the external server when the browser application is started. [0174]

When the introduction object is an application, the management apparatus 3 performs processing so that the user or the user device 5 belonging to the customer whose procedure registration has been completed can use the application by procedure registration. For example, for a web application, the user device 5 accesses an external server such as the application distribution server 7 to use the functions of the application. The management apparatus 3 can transmit permission information for permitting the application distribution server 7 to provide the application function to the user device 5 belonging to the customer whose procedure registration has been completed, directly or indirectly through the user device 5 or the like.

[0175]

In the above description, the user device 5 transmits the application serial number as the processing for the user device 5 to introduce the introduction object, however, the present embodiment is not limited to this example. For example, the communication terminal 4 may access the management apparatus to specify the introduction destination or target of the introduction object from the communication terminal 4. For example, by receiving designation of an application that is made available by a customer through procedure registration among a plurality of applications and designation of a user device 5 desired as an introduction destination of the application among a plurality of user devices 5 belonging to the customer, the designated application can be installed in the designated user device 5. As a result, the management apparatus 3 stores the introduction identification information of the introduction object and the device identification information of the user device 5 to be introduced in association with each other in the introduction information management DB 3007.

[0176]

An acquisition process of recommendation information in the user device 5 is described in the following. FIG. 25 is a sequence diagram illustrating an example of a various application acquisition process. In the sequence diagram illustrated in FIG. 25, a recommendation information notification transmitted by the management apparatus 3 is displayed using an operation unit or the like provided in the user device 5, and then an acquisition and installation process of an application that is an example of an introduction object is performed. The processing from step S61 to step S65 corresponds to the processing from step S41 to step S45 illustrated in FIG. 22, and the description is omitted. In response to receiving the recommendation information notification, the user device 5 displays a banner display or a pop-up display on the screen of the operation unit to indicate that the recommendation information notification has been received. Then, the recommendation information notification screen is displayed on the user device 5 by the user operating the banner display or the pop-up display. The display indicating that the recommendation information notification has been received or the recommendation information notification screen may be displayed in the case the user having logged in to the user device 5 is the administrative user. In this case, an administrative user who manages each user device 5 is set in advance in each user device 5.

[0177]

In step S66, the data exchange unit 51 of the user device 5 transmits an application distribution request to the application distribution server 7 based on the recommendation information received in step S63. Accordingly, the data exchange unit 71 of the application distribution server 7 receives the application distribution request transmitted by the user device 5. At this time, the application distribution request includes, for example, URL information on a web page whose operation has been received in step S65, and the introduction object identification information as information for identifying the application of the introduction object, that is, the application to be installed. In step S66, the user can purchase or make a contract for the application that is the introduction object based on the received recommendation information. The application distribution request may include the device identification information.

[0178]

In step S67, the storing and reading unit 79 of the application distribution server 7 reads the application data. Specifically, the storing and reading unit 79 reads, among various applications stored in a predetermined area of the storage unit 7000, an application associated with the introduction object identification information. The application distribution server 7 registers the introduction object identification information and the application in association with each other in advance. The application distribution server 7 may inquire of the management apparatus 3 about the application corresponding to the introduction object identification information. Along with this process, the acquisition unit 73 acquires the application data read from the storage unit 7000.

[0179]

In step S68, the data exchange unit 71 transmits an application distribution response as a response to the application distribution request received in step S66 to the user device 5. Accordingly, the data exchange unit 51 of the user device 5 receives the application distribution response transmitted by the application distribution server 7. At this time, the application distribution response includes the application identification information and the application data read in step S67 (in the case of a plurality of application distribution responses, respective pieces of application identification information and various corresponding application data).

[0180]

In step S69, the execution unit 56 of the user device 5 installs the application received in step S68 in a predetermined area of the storage unit 5000. Accordingly, the user device 5 can use the predetermined application on which the user has performed the introduction operation in accordance with the recommendation information notification transmitted by the management apparatus 3. The installation of the application is an example of an introduction process for enabling the user device 5 to use the application. For example, in the case of a native application that becomes available by being installed on the user device 5, the user device 5 installs the application as the introduction process. On the other hand, in the case of the web application whose functions are provided in cooperation with an external server such as the application distribution server 7, the following processing is performed as the introduction process. The user device 5 displays a shortcut to a browser application or the like on a home screen displayed on the display panel 540a of the user device 5, and performs settings for making an access to the external server when the browser application is started.

[0181]

In step S70, the data exchange unit 51 transmits an installation completion notification to the management apparatus 3. Accordingly, the data exchange unit 31 of the management apparatus 3 receives the installation completion notification transmitted by the user device 5. The installation completion notification may include a comment indicating that the installation has been completed, flag information indicating the completion of installation, device identification information, introduction object identification information, and the like. [0182]

In step S71, the registration management unit 38 of the management apparatus 3 performs the procedure registration. The procedure registration process includes registering in association with each other, the customer identification information, the introduction object identification information for identifying the introduction object installed in the user device 5, an introduction date and time indicating the date and time of completion of the installation, and the device identification information indicating the user device 5 with the application installed. At this time, the extracting and specifying unit 32 searches the device information management DB 3002 (see FIG. 10) using the device identification information included in the installation completion notification received in step S70 as a search key to specify the corresponding customer identification information. Accordingly, the registration management unit 38 registers the introduction management information (introduction date and time, etc.) associated with the identified customer identification information in the corresponding items of the introduction information management DB 3007 (see FIG. 15). [0183]

Through the above-described processing, the management apparatus 3 can manage an introduction object that has been purchased or contracted based on the recommendation by the management apparatus 3, instead of an object that has been purchased or contracted regardless of the recommendation by the management apparatus 3. The timing at which the procedure registration process is executed is not limited to this example. For example, the user device 5 may request the management apparatus 3 to execute the procedure registration process at the timing of transmitting the application distribution request. Further, when the application distribution server 7 receives the application distribution request, the application distribution server 7 may request the management apparatus 3 to execute the procedure registration process.

[0184]

In the management system according to the present embodiment, for example, another device or the like may reside between the user device 5 and the application distribution server 7 when the processes of steps S66 and S68 described above are executed. In other words, information (data) transmitted or received between the user device 5 and the application distribution server 7 may be transmitted or received through another apparatus or the like. The above-described configuration can be applied even when another processing step is present between the user device 5 and the application distribution server 7.

[0185]

Notification Process for Unused Function>

A notification process for an unused function is described in the following. FIG. 26 is a sequence diagram illustrating an example of processing according to use amount. As illustrated in FIG. 26, in step S81, the extracting and specifying unit 32 of the management apparatus 3 identifies an application for which a predetermined period of time has elapsed since introduction. Specifically, the extracting and specifying unit 32 searches for the introduction date and time stored in the introduction information management DB 3007 (see FIG. 15) using the current date and time information as a search key and specifies the introduction object identification information corresponding to the application for which the predetermined period (for example, one month) has passed since the introduction. At this time, the extracting and specifying unit 32 may further specify an introduction object introduced to the user device 5 with charge. For example, the extracting and specifying unit 32 can determine whether the introduction object is charged by searching the introduction object management DB 3006 based on the introduction object identification information. Further, the extracting and specifying unit 32 can determine whether the introduction object is introduced under a paid contract by searching the introduction information management DB 3007 based on the introduction object identification information. In this manner, the extracting and specifying unit 32 can identify the introduction object that have been introduced with charge, and exclude the introduction objects that have been introduced without charge. As a result, the administrative user is able to identify an introduction object that has been installed with charge but has not been used by the user, and confirm the effect of the introduction on introduction cost. At this time, an application that the customer X has not installed after being recommended, that is, an application that has been installed in the user device 5 from the beginning or an application that has been automatically installed can be excluded from the identification targets. For example, among the introduction objects stored in the introduction information management DB 3007, the introduction object identification information with flag information indicating that the introduction object is introduced by the user based on the recommendation by the management apparatus 3 can be specified. Accordingly, the application recommended by the management apparatus 3 can be specified. However, instead of the process of step S81 described above, all applications introduced by the customer X may be specified. In the case a plurality of applications are specified in step S81, the processing described below can be executed for each of the plurality of applications specified.

[0186]

In step S82, the acquisition unit 33 acquires use history information related to the specified application. Specifically, at a predetermined timing, the acquisition unit 33 searches the use history information management DB 3003 (see FIG. 11) using the introduction object identification information corresponding to the application specified in step S81 as a search key, and acquires the use history information related to the corresponding introduction object. At this time, the use history information includes the use history (item 1), the setting item, and the use amount of the function executed by the setting item. The acquisition unit 33 further searches the transaction history information management DB 3004 (see FIG. 12) using the user identification information corresponding to the introduction object identification information as a search key, and acquires the transaction history information including corresponding transaction history (item 2).

[0187]

In step S82, for example, in the case there are one or more user devices managed by the same customer, acquisition processing of use history information combining both use history information may be performed, based on the use history information of one or more user device 5A and the user device 5B belonging to the customer. For example, the use history information table of the user device 5A and the use history information table of the user device 5B can be combined to generate one table of use history information.

[0188]

In step S83, the calculation unit 36 calculates the use amount. Specifically, for the use history information acquired in step S82, the calculation unit 36 calculates the use amount related to the application used by the “general user” among the user identification information managed by the user information management DB 3001 (see FIG. 9). In other words, the calculation unit 36 does not calculate the use amount related to the application used by the “administrative user”. As a result, in all user devices 5 corresponding to the customer identification information of the administrative user who introduced the introduction object, the total value of the number or amount of usage of a specific application by all general users corresponding to the customer identification information of the administrative user who introduced the introduction object is calculated as the use amount.

[0189]

Further, the calculation unit 36 calculates the use amount for each application. For example, in the case a plurality of applications is installed, the use amount is calculated as the total value of the number of times or the use amount that the general user has used the application, for each application. The calculation unit 36 may calculate the number of times the application is activated as the use amount. In this case, one item in the use history information management table illustrated in FIG. 11 can be counted as one application activation count.

[0190]

Further, the calculation unit 36 may calculate the use amount for each function of the application. For example, in the case one application has multiple functions, for each function of the application, the use amount is calculated as the total value of the number of times and use amount of the specific function of the application by the general user. As an example, for a printer application, multiple functions such as a print function and a scan function are included. In this case, the number of times the print function is used or the number of sheets printed and the number of times the scan function is used or the number of sheets scanned can be calculated as the use amount. Accordingly, in the case some functions of the application are paid functions, the administrative user can determine whether to continue using the paid function by confirming whether the paid function is being used by the general users. [0191]

Further, the calculation unit 36 may calculate the use amount for each setting item or setting value that is set when using the application. For example, in the case the user is free to set the setting value for the function when using the function of the application, the use amount can be calculated as the total value of the number of times or the amount that the general user sets the specific setting value of the application for each setting item or setting value of the application. As an example, for a scan application, the user is able to select an internal storage of the user device 5 or a cloud storage as scan data save destination setting. In this case, the number of times the storage destination is set to the internal storage and the number of times the cloud storage is set can be calculated as the use amount. As a result, when an administrative user installs an application with the expectation that the general users will use specific setting of the application, the administrative user can determine whether to continue to use the application by confirming whether the specific setting has been used by the general user.

[0192] In addition, as described above, in step S83, the case where the use amount related to the application (function) being used by the administrative user having administrative authority is not calculated has been described. Without being limited to this case, the application use amount by the administrative user who introduced the application may be excluded. In other words, although the administrative user has administrative authority, the use of the application by the user other than the user who introduced the corresponding application may be calculated as the use amount. The reason for excluding the use amount of application by the administrative user who introduced the application is that, for example, in the customer X, in the case the administrative user with administrator authority introduces an application to the user device 5 according to the recommendation information, the general user may not notice that the application has been introduced. In other words, this is the case where only the administrative user who has decided to introduce the application knows the availability of the application. In such a case, an administrative user with administrator authority can actively use the application after installation, but the general user who have not been informed of the introduction may not actively use the application. As a result, the use amount of the corresponding application may not increase. Therefore, from a viewpoint of fairness, the management apparatus 3 calculates the use amount by the general user instead of the use amount by the administrative user with administrator authority, and based on the calculation result, the use status of the introduced application is considered. In this case, the management apparatus 3 may acquire the purchase information, contract information, and the like of the customer X from an external server or the like, and acquires the user identification information and user name for each application introduced by the customer X. [0193]

Then, the calculation unit 36 compares the calculated use amount with a predetermined threshold. In other words, the calculation unit 36 determines whether the use status based on the use history information satisfies a predetermined condition. The comparison target may be the use amount of the application, the use amount of a specific function in the application, or the use amount of a specific setting item or setting value in the function of the application. Which use amount of the application, function, setting item, or setting value is to be compared is to be decided freely. Also, the threshold can be set freely. In step S84, the generation unit 37 generates a notification related to the specified application when the use situation matches the predetermined condition, that is, when the calculated use amount is below the predetermined threshold. In other words, the predetermined condition is that any of the use amount of the application, the use amount of the specific function in the application, and the use amount of the specific setting item or setting value in the function of the application falls below the predetermined threshold. [0194]

In addition, the generation unit 37, together with the extracting and specifying unit 32, selects, among applications managed by the application distribution server 7 or a dedicated external server and the like, searches and identifies an application that is related to the identified application and that satisfies either or both of an application that is more specialized in function than the identified application, or an application that is cheaper than the identified application, and generates a notification with information related to the application. However, the notification generated by the generation unit 37 is not limited to this example. For example, the generation unit 37 may generate a notification made up of fixed phrases, and in this case, information related to the application may be omitted.

[0195]

In step S85, the data exchange unit 31 transmits the generated notification to the communication terminal 4 or the user device 5. The data exchange unit 31 identifies the user identification information of the administrative user who introduced the identified application based on the introduction information management DB 3007, identifies the email address linked to the identified user identification information based on the user information management DB 3001, and transmits the notification to the identified email address. Alternatively, the data exchange unit 31 identifies customer identification information corresponding to the identified user identification information based on the user information management DB 3001, identifies address information linked to the identified customer identification information based on the device information management DB 3002, and transmits the notification to the identified address information. Accordingly, the data exchange unit 41 of the communication terminal 4 receives the notification transmitted by the management apparatus 3. [0196]

In this notification, various notification information may be included. In step S85, notification that include, as an example of notification information, information indicating that the application or specific functions and settings within the application are not being used by the general users, may be sent to the administrative user with administrative authority. The notification information may include the date and time of introduction of the corresponding application (or the number of days that have passed since the introduction), the use amount by the general users, and alternative application information. The use amount included in the notification may be the use amount of the application, the use amount of the specific function in the application, or the use amount of the specific setting item or setting value in the function of the application. The alternative application information may be, for example, an application similar in function to an applicable application but different from the applicable application. For example, an application that is less expensive than the applicable application is recommended as an alternative application. The alternative application information further includes alternative introduction object information indicating alternative introduction object information that is a substitute for the introduction object. The data exchange unit 31 may transmit the notification in response to a request from the communication terminal 4. For example, the data exchange unit 31 can display the notification through the browser of the communication terminal 4 by transmitting the notification in response to receiving an access from the communication terminal 4. In the case a plurality of applications is identified in step S81, a notification including the introduction date (or the number of days elapsed since the introduction) of each of the identified plurality of applications, the use amount by general users, and the alternative application information may be generated. In addition, in the notification, the application that was not identified in step S81, or the application that was determined not to match the predetermined condition in the use status among the applications identified in step S81, the date and time of introduction (or the number of days that have passed since the introduction), the use amount by the general users, and the alternative application information may be included.

[0197]

Further, instead of or in addition to the process of step S85 described above, the management apparatus 3 may similarly transmit a notification to the general user. The notification method at this time may be displayed on the screen of the communication terminal 4 used by the general user, or may be sent by email to the email address of each general user. In other words, the data exchange unit 31 identifies the user identification information of a general user or another administrative user associated with the customer identification information of the administrative user who introduced the identified application, and transmits a notification to the email address associated with the identified user identification information.

[0198]

In step S86, the display control unit 44 of the communication terminal 4 displays the notification. Specifically, the display control unit 44 causes the display 407 to display a screen such as an example of notification screen described below.

[0199]

Example Display Screen

FIG. 27 is an example of a display screen for notifying application use status. As illustrated in FIG. 27, an application use status notification screen 4021 is displayed on the display 407 of the communication terminal 4 by the display control unit 44. The application use status notification screen 4021 is an example of notification generated by the generation unit 37 and transmitted by the data exchange unit 31. On the application use status notification screen 4021, a screen including the introduction date and time (or the number of days that have passed since the introduction) of the applicable application, the use amount by the general user, and the recommended alternative application information is displayed. In the recommended alternative application information, the display control unit 44 further displays an alternative introduction object link display field 4022. The recommended alternative introduction object link (storage destination URL) may include information such as function available by the alternative introduction object, contact information for making an introduction contract for the alternative introduction object, and access information to the contract site. Further, contents of the link may be newly stored in the introduction object management DB 3006 (see FIG. 14). In this case, the recommended alternative introduction object is information newly managed in the item of the introduction object storage destination (purchaser) associated with the introduction object identification information. Accordingly, the user is able to introduce an alternative introduction object (in this case, a low-priced business card management application) by performing an operation such as tapping the save destination URL of the introduction object in the alternative introduction object link display field 4022, after confirming the information on the recommendation information notification screen 4011.

[0200]

Referring back to FIG. 26, in the case the calculated use amount is equal to or greater than the predetermined threshold value, the management apparatus 3 exits the notification processing for unused functions and executes other processing in step S87. The data exchange unit 31 notifies the administrative user with administrator authority that the application is being used by the general user by transmitting the application use notification screen to the administrative user who installed the application. In this case, the recommended alternative application information may be omitted from the application use notification screen. The management apparatus 3 may terminate the process without transmitting the application status notification screen.

[0201]

Further, in the processing of steps S84 to S87, the management apparatus 3 and the communication terminal 4 may execute the processing of steps S84 to S86, in the case the number of uses is equal to or less than a predetermined threshold, and may execute the processing of step S87 in the case the number of uses exceeds the predetermined threshold value. In other words, the conditional branching of the process for the predetermined threshold value is not limited to the example illustrated in FIG. 26.

[0202]

Regarding steps S84 to S86 described above, the management apparatus 3 may notify the communication terminal 4 according to the application use pattern. For example, the administrative user may introduce a scan application for a purpose of saving scan data to a cloud storage. However, some applications include multiple functions. The general user may use the application in a manner different from intention of the administrative user. Therefore, the application use history may include functions and setting values executed by the application. In this case, in the process of step S83, the calculation unit 36 may calculate the use amount for each function or setting value of the application. In step S84, the determination processing unit 35 determines whether the use amount of function or setting value preset by the administrator is below a predetermined threshold, and in step S85, the generation unit 37 may generate a notification related to the function or setting value, and the data exchange unit 31 may transmit the notification to a predetermined destination.

[0203]

[Processing Using User Device According to Another Embodiment]

An example of processing using a user device according to another embodiment is described in the following. FIG. 28 is a sequence diagram illustrating an example of processing using the user device according to another embodiment. In the example illustrated in FIG. 28, a case where the user device 5 uses an interactive voice operation apparatus, for example, a smart speaker or an artificial intelligence (Al) speaker (hereinafter, referred to as smart speaker) is described. The introduction object in this case is, for example, an application for the smart speaker to execute a predetermined function. The application includes a native application that executes a function by being installed in the smart speaker, and a web application in which the smart speaker executes a function in cooperation with the application distribution server 7. An extension function for extending the function provided by the application distribution server 7, a program for extending the function, and so forth, may be referred to as an application. The introduction of the application that is an introduction object includes a sign-up for use of the application from the communication terminal 4 to the application distribution server 7.

[0204]

In the case of FIG. 28, the data exchange unit 51 of the smart speaker serving as an example of the user device 5 transmits a processing request to the management apparatus 3 in step S 101. Accordingly, the data exchange unit 31 of the management apparatus 3 receives the processing request transmitted by the smart speaker. The processing request includes device identification information for identifying the smart speaker and audio information input to the smart speaker.

[0205]

In step S102, the determination processing unit 35 of the management apparatus 3 performs authentication processing. Specifically, the determination processing unit 35 compares the device identification information included in the audio information received in step S101 with the device identification information registered in the management apparatus 3 in advance. Based on determination that the device identification information included in the audio information received in step S101 matches with the device identification information registered in the management apparatus 3, the management apparatus 3 determines that the authentication is successful. At this time, the determination processing unit 35 identifies the customer identification information corresponding to the device identification information. [0206]

In step S103, the determination processing unit 35 performs a voice recognition process based on the voice information, and then performs an availability determination process in step S104. Specifically, the determination processing unit 35 determines an available service based on a device permission DB associated with the device identification information or a customer permission DB corresponding to the customer identification information associated with the device identification information.

[0207]

The management apparatus 3 may specify an available service based on contract identification information and service identification information associated with tenant identification information and group identification information that are separately specified. The determination processing unit 35 of the management apparatus 3 compares the service identification information corresponding to the service information specified from the voice information uttered by the user with the service identification information corresponding to the service specified as the available service. As a result of the comparison, the determination processing unit 35 determines that the service is available when the service identification information matches, and determines that the service is not available when the service identification information does not match.

[0208]

When there is no available service (when the service is not available), the data exchange unit 31 of the management apparatus 3 transmits a processing response including non-availability information indicating that the service is not available to the smart speaker in step S105. Accordingly, the data exchange unit 51 of the smart speaker receives the processing response transmitted by the management apparatus 3.

[0209]

In step S 106, the display control unit 54 of the smart speaker causes the display unit of the smart speaker to display a notice indicating that the service is not available.

[0210]

On the other hand, when there is an available service (when the service is available), the data exchange unit 31 of the management apparatus 3 transfers (transmits) the smart speaker processing request received in step S101 to the application distribution server 7 in step S107. Accordingly, the data exchange unit 71 of the application distribution server 7 receives the processing request transmitted by the management apparatus 3. The processing request includes job information to be processed and parameter information regarding the job. Depending on the service information, the management apparatus 3 may execute processing based on the job information and the parameter information. In this case, identification of the application distribution server 7 and transmission of the processing request can be omitted. [0211]

In step S108, the execution unit 76 of the application distribution server 7 performs authentication process based on the received processing request.

[0212]

In step S 109, the data exchange unit 71 transmits a processing response to the processing request received in step S107 to the management apparatus 3. Accordingly, the data exchange unit 31 of the management apparatus 3 receives the processing response transmitted by the application distribution server 7. The processing response includes processing result information.

[0213]

In step SI 10, the data exchange unit 31 of the management apparatus 3 transmits a processing response including processing result information executed by the application distribution server 7 to the smart speaker. Accordingly, the data exchange unit 51 of the smart speaker receives the processing response transmitted by the management apparatus 3. [0214]

In step Sill, the display control unit 54 of the smart speaker displays the processing result. Specifically, the display control unit 54 displays the processing result information included in the received processing response on the display unit or outputs the processing result information through the speaker. With the above processing, the user using the smart speaker can cause the application distribution server 7 to execute desired processing and confirm the result by display or voice.

[0215]

In the case of the smart speaker described above, the functions provided by the application are implemented in the management apparatus 3 or the external server 7. To introduce an application, the user accesses the management apparatus 3 or an external server (application distribution server 7) from the user device 5 or another communication terminal, and concludes a contract for using the application. As a result, the user who has concluded the contract, or the account or the user device 5 corresponding to the user, is authorized to use the function of the application from the user device 5 by setting the authority to provide the functions of the application in the management apparatus 3 or the external server 7.

[0216]

In the management system according to the present embodiment, for example, when the processes of steps S107 and S109 described above are executed, another device or the like may reside between the management apparatus 3 and the application distribution server 7. In other words, each information (data) transmitted or received between the management apparatus 3 and the application distribution server 7 may be transmitted or received through another device or the like. The above-described configuration can be applied even when another processing step is present between the management apparatus 3 and the application distribution server 7.

[0217]

As described above, according to the present embodiment, the management apparatus 3 acquires the history information of the introduction object related to the general user (step S82), generates a notification in the case the use status based on the use history information matches the predetermined condition (step S84), and transmits the generated notification to the administrative user (step S85). As a result, even in the case the user who manages the introduction object such as an application and the user who uses the introduction object are different, the administrative user who manages the introduction object is able to grasp the use status by other users of the introduction object introduced by the administrative user. [0218]

Further, according to the present embodiment, the notification generated for the specified application is transmitted to the destination of the administrative user having administrator authority or the destination of the general user. As a result, in addition to the effects described above, the user can visually and objectively grasp the use status of the introduction object, and also, there is an effect that the introduction of an inexpensive application that is more suitable for the function actually used than the introduction object that has been introduced becomes possible.

[0219]

[Supplement to the embodiment]

Each of the functions of the above-described embodiments may be implemented by one or more processing circuits or circuitry. Processing circuitry includes a programmed processor, as a processor includes circuitry. A processing circuit also includes devices such as an application specific integrated circuit (ASIC), digital signal processor (DSP), field programmable gate array (FPGA), system on a chip (SOC), graphics processing unit (GPU), and conventional circuit components arranged to perform the recited functions. [0220]

In the above-described embodiment, for example, a system may be provided in which the processing up to steps S81 to S83 described above is learned by machine learning, artificial intelligence (Al), deep learning, or the like. Further, the management system may provide a system that can notify the user of the comment text when notifying the application use status by using the result of learning by machine learning, Al, deep learning, or the like. [0221]

Although the management apparatus, the management system, the management method, and the recording medium according to embodiments of the present invention are described above, the above-described embodiments are illustrative and do not limit the present invention. Thus, numerous additional modifications and variations are possible in light of the above teachings. For example, elements and/or features of different illustrative embodiments may be combined with each other and/or substituted for each other within the scope of the present invention. Any one of the above-described operations may be performed in various other ways, for example, in an order different from the one described above.

[0222]

Aspects of the present disclosure are, for example, as follows. [0223]

According to a first aspect, a management apparatus 3 (an example of a management apparatus) for managing information related to an introduction object introduced to a user device 5 (an example of a user device) includes, a registration management unit 38 (an example of a management means) to manage an administrative user and a general user each related to the introduction object, an acquisition unit 33 (an example of an acquisition means) to acquire use history information related to the introduction object used by the general user, a generation unit 37 (an example of a generation means) to generate a notification when a use status based on the use history information matches a predetermined condition, and a data exchange unit 31 (an example of a transmission means) to transmit a notification to the administrative user.

[0224]

According to the first aspect, even in the case the user who manages the introduction object such as an application and the like is different from the user who uses the introduction object, the administrative user who manages the introduction object is able to grasp the use status of the introduction object introduced by the administrative user by other users.

[0225]

According to a second aspect, an extracting and specifying unit 32 (an example of a specification means) of the user device 5 specifies an introduction object introduced with charge to the user device 5 in the first aspect, and a generation unit 37 generates a notification in a case where the use status based on the use history information of the introduction object specified by the extracting and specifying unit 32 matches a predetermined condition.

[0226]

According to the second aspect, in addition to effect of the first aspect, the administrative user is able to manage introduction cost, maintenance cost, and the like of the introduction object. [0227]

According to a third aspect, the extracting and specifying unit 32 of the management apparatus 3 specifies the introduction object introduced to the user device 5 in response to the notification transmitted by the management apparatus 3 in the second aspect.

[0228]

According to the third aspect, in addition to effect of the second aspect, the administrative user is able to grasp introduction history of the introduction object. Further, in addition to the effect of the second aspect, the management apparatus 3 is able to specify the introduction object introduced to the user device 5 in response to the notification.

[0229]

According to a fourth aspect, the extracting and specifying unit 32 of the user device 5 of the first aspect or the second aspect acquires information combining the use history information on one or more user devices associated with the same customer identification information as history information.

[0230]

According to the fourth aspect, by acquiring various history information in the user device 5 used by the same customer by the management apparatus 3, the administrative user is able to grasp a use trend of the introduction object by general users managed by the same customer identification information.

[0231]

According to a fifth aspect, the extracting and specifying unit 32 of the user device 5 in the first aspect or the second aspect, acquires identification information of the introduced introduction object and a date and time of introduction.

[0232]

According to the fifth aspect, by the management apparatus 3 acquiring more detailed information related to the introduction object, the administrative user is able to receive more detailed notification.

[0233] According to a sixth aspect, in any one of the first aspect to the fifth aspect, the data exchange unit 31 of the user device 5 transmits a notification to the communication terminal 4 in response to an access from the communication terminal 4 used by the administrative user. [0234]

According to the sixth aspect, the administrative user is able to receive the notification in response to an inquiry, request, or the like transmitted at a timing desired by the administrative user.

[0235]

According to a seventh aspect, in any one of the first aspect to the sixth aspect, in a case the calculated use amount for at least one of a function or setting related to the specific introduction object is less than or equal to a predetermined value, the generation unit 37 of the user device 5 generates a notification including alternative introduction object information indicating an alternative introduction object.

[0236]

According to the seventh aspect, the administrative user is able to introduce the alternative introduction object that is more suitable for the user than the introduction object used in the user device 5, and the alternative introduction objects can be used by users including the general user.

[0237]

According to an eighth aspect, the data exchange unit 31 of the user device 5 of the seventh aspect transmits the generated notification to a destination associated with the customer identification information that identifies the customer.

[0238]

According to the eighth aspect, the administrative user who manages the introduction object and has the destination associated with the customer identification information is able to grasp the use status by other users of the introduction object introduced by the administrative user. [0239]

According to a ninth aspect, in any one of the first aspect to the ninth aspect, the user device 5 includes at least one of a multifunction peripheral, a scanner, a facsimile, an electronic whiteboard, a projector, a personal computer, a smartphone, or an interactive voice-operated device.

[0240]

According to the ninth aspect, even in a case the user device 5 is a device of various types, the administrative user who manages the introduction object is able to grasp the use status of the introduction object introduced by the administrative user by other users as in the first aspect. [0241]

According to a tenth aspect, a management system 2 (an example of a management system;) includes a management apparatus 3 for managing information related to an introduction object introduced to a user device 5, a communication terminal 4 for displaying information related to the introduction object transmitted by the management apparatus 3, and the management apparatus 3 includes a registration management unit 38 (an example of a management means) to manage an administrative user and a general user related to the introduction object, an acquisition unit 33 (an example of an acquisition means) to acquire use history information related to the introduction object used by the general user, a generation unit (an example of a generation means) to generate a notification when the use status based on the use history information matches a predetermined condition, a data exchange unit 31 (an example of a transmission means) to transmit a notification to the administrative user, and the communication terminal 4 includes a display control unit 44 (an example of a display control means) to display the notification generated by the management apparatus 3 on the display means.

[0242]

According to the tenth aspect, similar to the first aspect, even in a case the user who manages the introduction object such as the application and the user who uses the introduction object such as the application are different, the administrative user who manages the introduction object is able to grasp the use status by other users of the introduction object introduced by the administrative user.

[0243]

According to an eleventh aspect a management method executed by a management apparatus 3 that manages information related to an introduction object introduced to a user device 5 (an example of a user device) includes, a management step (steps S 14, S34) for managing an administrative user and a general user related to the introduction object, an acquisition step (step S82) for acquiring use history information related to the introduction object used by the general user, a generation step (step S84) for generating a notification when the use status based on the use history information matches a predetermined condition, and a transmission step (step S85) for transmitting the notification to the administrative user.

[0244]

According to the eleventh aspect, similar to the first aspect, even in the case the user who manages the introduction object such as the application and the user who uses the introduction object such as the application are different, the administrative user who manages the introduction object is able to grasp the use status by other users of the introduction object introduced by the administrative user.

[0245]

According to a twelfth aspect, a program for controlling the management apparatus 3 for managing information related to the introduction object introduced in the user device 5 (an example of the device), to carry out a method including, a management step (steps S 14, S34) for managing an administrative user and a general user related to the introduction object, an acquisition step (step S82) for acquiring use history information related to the introduction object used by the general user, a generation step (step S84) for generating a notification when the use status based on the use history information matches a predetermined condition, and a transmission step (step S85) for transmitting the notification to the administrative user. [0246]

According to the twelfth aspect, similar to the first aspect, even in the case the user who manages the introduction object such as the application and the user who uses the introduction object such as the application are different, the administrative user who manages the introduction object is able to grasp the use status of the introduction object introduced by the administrative user by other users.

[0247]

The above-described embodiments are illustrative and do not limit the present invention. Thus, numerous additional modifications and variations are possible in light of the above teachings. For example, elements and/or features of different illustrative embodiments may be combined with each other and/or substituted for each other within the scope of the present invention. Any one of the above-described operations may be performed in various other ways, for example, in an order different from the one described above.

[0248]

The present invention can be implemented in any convenient form, for example using dedicated hardware, or a mixture of dedicated hardware and software. The present invention may be implemented as computer software implemented by one or more networked processing apparatuses. The processing apparatuses include any suitably programmed apparatuses such as a general purpose computer, a personal digital assistant, a Wireless Application Protocol (WAP) or third-generation (3G)-compliant mobile telephone, and so on. Since the present invention can be implemented as software, each and every aspect of the present invention thus encompasses computer software implementable on a programmable device. The computer software can be provided to the programmable device using any conventional carrier medium (carrier means). The carrier medium includes a transient carrier medium such as an electrical, optical, microwave, acoustic or radio frequency signal carrying the computer code. An example of such a transient medium is a Transmission Control Protocol/Intemet Protocol (TCP/IP) signal carrying computer code over an IP network, such as the Internet. The carrier medium may also include a storage medium for storing processor readable code such as a floppy disk, a hard disk, a compact disc read-only memory (CD- ROM), a magnetic tape device, or a solid state memory device.

[0249]

The functionality of the elements disclosed herein may be implemented using circuitry or processing circuitry which includes general purpose processors, special purpose processors, integrated circuits, application specific integrated circuits (ASICs), digital signal processors (DSPs), field programmable gate arrays (FPGAs), conventional circuitry and/or combinations thereof which are configured or programmed to perform the disclosed functionality. Processors are considered processing circuitry or circuitry as they include transistors and other circuitry therein. In the disclosure, the circuitry, units, or means are hardware that carry out or are programmed to perform the recited functionality. The hardware may be any hardware disclosed herein or otherwise known which is programmed or configured to carry out the recited functionality. When the hardware is a processor which may be considered a type of circuitry, the circuitry, means, or units are a combination of hardware and software, the software being used to configure the hardware and/or processor.

[0250]

This patent application is based on and claims priority to Japanese Patent Application Nos. 2022-169783, filed on October 24, 2022, and 2023-024537 filed on February 20, 2023, in the Japan Patent Office, the entire disclosure of which is hereby incorporated by reference herein. [Reference Signs List] [0251]

1 Information processing system

2 Management system

3 Management apparatus

4 Communication terminal

5 User device

6 History management server

7 Application distribution server

31 Data exchange unit (example of transmission means, example of receiving means)

32 Extracting and specifying unit (example of extraction means, example of specification means)

33 Acquisition unit (example of first acquisition means, example of second acquisition means, example of acquisition means)

36 Calculation unit (example of calculation means)

37 Generation unit (example of generation means)

38 Registration management unit (example of management means)

407 Display (example of the display means)

540a Display panel (example of display means)

Claims

[CLAIMS]

[Claim 1]

A management apparatus for managing information related to an introduction object having been introduced to a user device, the management apparatus comprising: management means configured to manage an administrative user and a general user each related to the introduction object; acquisition means configured to acquire use history information related to the introduction object used by the general user; generation means configured to generate a notification in a case where a use status based on the use history information matches a predetermined condition; and transmission means configured to transmit the notification to the administrative user.

[Claim 2]

The management apparatus according to claim 1, wherein the introduction object includes a plurality of instruction objects, the management apparatus further comprising specification means configured to specify at least one introduction object having been introduced to the user device with a charge from among the plurality of introduction objects, and wherein the generation means is configured to generate the notification in a case where the use status based on the use history information of the introduction object specified by the specification means matches the predetermined condition.

[Claim 3]

The management apparatus according to claim 2, wherein the specification means is configured to specify the introduction object having been introduced to the user device further according to recommendation information transmitted by the management apparatus.

[Claim 4]

The management apparatus according to claim 1 or 2, wherein the acquisition means is configured to acquire information combining use history information on one or more user devices including the user device, each user device being associated with the same customer identification information, as the use history information related to the introduction object.

[Claim 5]

The management apparatus according to claim 1 or 2, wherein the acquisition means is further configured to acquire identification information and introduction date and time information of the introduction object having been introduced.

[Claim 6]

The management apparatus according to claim 1, wherein the transmission means is further configured to transmit the notification to a communication terminal in response to an access from the communication terminal used by the administrative user.

[Claim 7] The management apparatus according to claim 1, wherein in a case where a calculated use amount for at least one of a function or a setting related to the introduction object is equal to or less than the predetermined condition, the generation means is further configured to generate a notification including alternative introduction object information indicating an alternative to the introduction object.

[Claim 8]

The management apparatus according to claim 7, further comprising a transmission means configured to transmit the generated notification to a destination associated with customer identification information that identifies a customer.

[Claim 9]

The management apparatus according to claim 1, wherein the user device includes at least one of a multifunction peripheral, a scanner, a facsimile, an electronic whiteboard, a projector, a personal computer, a smartphone, or an interactive voice-operated device.

[Claim 10]

A management system comprising: a management apparatus for managing information related to an introduction object having been introduced to a user device; and a communication terminal for displaying information related to the introduction object transmitted by the management apparatus, the management apparatus including: management means configured to manage an administrative user and a general user each related to the introduction object; acquisition means configured to acquire use history information related to the introduction object used by the general user; generation means configured to generate a notification in a case where a use status based on the use history information matches a predetermined condition; and transmission means configured to transmit the notification to the administrative user, and the communication terminal including display control means configured to display the notification generated by the management apparatus on a display means.

[Claim 11]

A management method executed by a management apparatus configured to manage information related to an introduction object having been introduced to a user device, the method comprising: managing an administrative user and a general user each related to the introduction object; acquiring use history information related to the introduction object used by the general user; generating a notification in a case where a use status based on the use history information matches a predetermined condition; and transmitting the notification to the administrative user.

[Claim 12]

A recording medium carrying computer readable code for controlling a computer system to carry out a method comprising: managing an administrative user and a general user each related to an introduction object having been introduced to a user device; acquiring use history information related to the introduction object used by the general user; generating a notification in a case where a use status based on the use history information matches a predetermined condition; and transmitting the notification to the administrative user.

[Claim 13]

The management apparatus according to claim 1, wherein the introduction object is a computer program installable on the user device.