Information processing apparatus, contract management method, and program

Abstract

To provide an information processing apparatus which can enhance facility of managing information on contracts of multiple services.SOLUTION: An information processing apparatus for managing information on contracts of a first service and a second service includes: service information storage means which stores information on the second service in association with the first service; contract receiving means which receives a contract for the second service stored in association with the first service; and matching means which adjusts a contract period of the second service for which the contract has been received, so as to be consistent with a contract period of the first service at the time of renewing the contract of the first service stored in association with the second service.SELECTED DRAWING: Figure 4

Description

[Technical Field]

[0001] The present invention relates to an information processing device, a contract management method, and a program. [Background technology]

[0002] A contract (subscription) is known in which a service can be used for a limited period of time by paying a fixed fee. In a subscription, a service user pays a fixed fee to a service provider and can use the service for a limited period of time.

[0003] For example, in an image forming device that comes standard with basic functions such as copying, printing, and scanning, and offers extended functions as options, it has long been known that fees for using the extended functions are paid by subscription (see, for example, Patent Document 1). Summary of the Invention [Problem to be solved by the invention]

[0004] For example, with a device such as an image forming apparatus, it is possible to use multiple services with contract periods by signing up for them separately. However, when multiple services with contract periods are signed up for separately, the contract periods for the multiple services end up being different, making it difficult to manage information related to the contracts. Note that Patent Document 1 does not solve the above problem.

[0005] An object of one embodiment of the present invention is to provide an information processing device that can improve the ease of managing information relating to contracts for a plurality of services. [Means for solving the problem]

[0006] In order to achieve the above-mentioned object, one embodiment of the present invention is an information processing device that manages information regarding contracts for a first service and a second service, and has a service information storage means that stores information about the second service in association with the first service, a contract acceptance means that accepts a contract for the second service stored in association with the first service, and an alignment means that aligns the contract period of the second service for which the contract has been accepted with the contract period of the first service at the time of contract renewal for the first service stored in association with the second service. [Effects of the Invention]

[0007] According to one embodiment of the present invention, it is possible to improve the ease of managing information relating to contracts for multiple services. [Brief explanation of the drawings]

[0008] [Figure 1] 1 is a configuration diagram of an example of an information processing system according to an embodiment of the present invention. [Figure 2] FIG. 2 is a diagram illustrating an example of a hardware configuration of a computer according to the present embodiment. [Figure 3] FIG. 2 is a diagram illustrating a hardware configuration of an example of an MFP according to the present embodiment. [Figure 4] 1 is a functional configuration diagram of an example of an information processing system according to an embodiment of the present invention. [Figure 5] FIG. 10 is a diagram illustrating an example of base product information. [Figure 6] FIG. 10 is a diagram illustrating an example of add-on product information. [Figure 7] FIG. 2 is a diagram illustrating an example of pricing plan information. [Figure 8] FIG. 2 is a diagram illustrating an example of contract information. [Figure 9] FIG. 2 is a diagram illustrating an example of license information. [Figure 10] FIG. 10 is a diagram illustrating an example of usage authority information. [Figure 11] FIG. 10 is a diagram illustrating an example of a data model of contract information when a contract is made for a base product and an add-on product. [Figure 12] 10 is a flowchart illustrating an example of processing of the information processing system according to the present embodiment. [Figure 13] FIG. 10 is an explanatory diagram of an example of a process for aligning the contract period of an add-on product during the contract period with the contract renewal timing of the associated base product. [Figure 14] FIG. 10 is an explanatory diagram of an example of a process for aligning the contract period of an add-on product during the contract period with the contract renewal timing of the associated base product. [Figure 15] FIG. 10 is an explanatory diagram of an example of a process for aligning the contract period of an add-on product during the contract period with the contract renewal timing of the associated base product. DETAILED DESCRIPTION OF THE INVENTION

[0009] Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings.

[0010] [First embodiment] <System configuration> Fig. 1 is a configuration diagram of an example of an information processing system according to this embodiment. The information processing system 1 shown in Fig. 1 has an information processing device 10, an information processing terminal 12, and an electronic device 14, and communicates via a network 18. The network 18 is the Internet, a LAN (Local Area Network), or the like. The information processing terminal 12 and the electronic device 14 are examples of devices 16 that use multiple subscribed services.

[0011] The information processing terminal 12 is a PC (Personal Computer), a mobile phone, a smartphone, a tablet terminal, a game console, a PDA (Personal Digital Assistant), a digital camera, a wearable PC, etc. operated by the service user. The electronic device 14 is an image forming device, a PJ (Projector), an IWB (Interactive White Board: an electronic whiteboard with a blackboard function that allows mutual communication), etc. operated by the service user.

[0012] The device 16 may be an output device such as a digital signage, a HUD (Head Up Display) device, industrial machinery, an imaging device, a sound collection device, a medical device, a network home appliance, an automobile (connected car), etc. The device 16 is not limited to the above examples as long as it has a communication function and can use the service under contract.

[0013] In the following, an example will be described in which device 16 is an MFP (Multifunction Peripheral / Product Printer), which is an example of an image forming device. The MFP can perform various functions such as copying, scanning, faxing, and printing. The MFP can use base products and add-on products during the contract period.

[0014] A base product is an example of a first service and is a base service available on device 16. An add-on product is an example of a second service and is a service that adds functions to a base product. An add-on product is associated with one or more base products to which functions can be added. In other words, functions provided as add-on products utilize at least some of the functions provided as the base product. Note that base products and add-on products can be contracted at different times, and each has a defined contract period. The contract periods for base products and add-on products are renewed at renewal times according to the defined contract period. Here, products and services refer to, for example, applications and functions available on device 16. Services include functions provided by native applications installed on device 16 and functions provided to device 16 from an external server via a web application.

[0015] The information processing device 10 manages information related to the contracts for the base product and add-on products of the device 16. For example, as described below, the information processing device 10 performs management to align the contract periods for the base product and the add-on products, which were contracted at different times, with the renewal timing of the contract for the base product. In addition, as described below, the information processing device 10 performs management to prevent a situation in which an add-on product cannot add functions to the base product during the contract period due to cancellation of the base product, etc.

[0016] 1 is an example of the configuration of the information processing system 1. For example, the information processing device 10 may be realized as a cloud service, or may be realized as one or more servers that manage information related to contracts for base products and add-on products of the device 16. Furthermore, the information processing device 10 may be realized as one or more servers that provide programs such as applications required for using the base products and add-on products.

[0017] <Hardware configuration> "computer" The information processing device 10 in Fig. 1 is realized, for example, by a computer 500 having a hardware configuration as shown in Fig. 2. Furthermore, in the case of a PC, the information processing terminal 12 in Fig. 1 is realized, for example, by a computer 500 having a hardware configuration as shown in Fig. 2. Fig. 2 is a diagram showing the hardware configuration of an example of a computer according to this embodiment.

[0018] The computer 500 includes a CPU (Central Processing Unit) 501, a ROM (Read Only Memory) 502, a RAM (Random Access Memory) 503, a HD 504, a HDD (Hard Disk Drive) controller 505, a display 506, an external device connection I / F (Interface) 508, a network I / F 509, a data bus 510, a keyboard 511, a pointing device 512, a DVD-RW (Digital Versatile Disk Rewritable) drive 514, and a media I / F 516.

[0019] Of these, the CPU 501 controls the overall operation of the computer 500 in accordance with a program. The ROM 502 stores programs used to drive the CPU 501, such as the IPL. The RAM 503 is used as a work area for the CPU 501. The HD 504 stores various data such as programs. The HDD controller 505 controls the reading and writing of various data from and to the HD 504 in accordance with the control of the CPU 501.

[0020] The display 506 displays various types of information such as a cursor, menus, windows, characters, or images. The external device connection I / F 508 is an interface for connecting various types of external devices. In this case, the external device is, for example, a USB (Universal Serial Bus) memory. The network I / F 509 is an interface for data communication using the network 18. The data bus 510 is an address bus, data bus, or the like for electrically connecting each component such as the CPU 501.

[0021] The keyboard 511 is a type of input means having multiple keys for inputting characters, numbers, various instructions, etc. The pointing device 512 is a type of input means for selecting and executing various instructions, selecting a processing target, moving a cursor, etc. The DVD-RW drive 514 controls reading and writing of various data from a DVD-RW 513, which is an example of a removable recording medium. Note that this is not limited to a DVD-RW, and may be a DVD-R, etc. The media I / F 516 controls reading and writing (storing) of data from a recording medium 515, such as a flash memory.

[0022] The hardware configuration shown in FIG. 2 is an example, and it is not necessary to include all of the components shown in FIG. 2, or it may include components other than those shown in FIG.

[0023] <<MFP>> The electronic device 14 shown in Fig. 1 is realized by, for example, an MFP 900 having the hardware configuration shown in Fig. 3. Fig. 3 is a diagram showing the hardware configuration of an example of an MFP according to this embodiment.

[0024] 3 includes a controller 910, a short-range communication circuit 920, an engine control unit 930, an operation panel 940, and a network I / F 950. The controller 910 includes a CPU 901, which is the main part of the computer, a system memory (MEM-P) 902, a north bridge (NB) 903, a south bridge (SB) 904, an ASIC (Application Specific Integrated Circuit) 906, a local memory (MEM-C) 907, which is a storage unit, an HDD controller 908, and an HD 909, which is also a storage unit, and is configured such that the NB 903 and the ASIC 906 are connected by an AGP (Accelerated Graphics Port) bus 921.

[0025] The CPU 901 is a control unit that performs overall control of the MFP 900. The NB 903 is a bridge that connects the CPU 901 with the MEM-P 902, the SB 904, and the AGP bus 921. The NB 903 also has a memory controller that controls reading and writing to the MEM-P 902, a PCI (Peripheral Component Interconnect) master, and an AGP target.

[0026] The MEM-P902 has a ROM 902a, which is memory for storing programs and data that realize the functions of the controller 910, and a RAM 902b, which is used for expanding the programs and data and as a drawing memory during memory printing. The programs stored in the RAM 902b may be provided by being recorded in an installable or executable file format on a computer-readable recording medium such as a CD-ROM, CD-R, or DVD.

[0027] The SB 904 is a bridge for connecting the NB 903 with PCI devices and peripheral devices. The ASIC 906 is an integrated circuit (IC) for image processing purposes that has hardware elements for image processing, and acts as a bridge connecting the AGP bus 921, PCI bus 922, HDD 908, and MEM-C 907.

[0028] The ASIC 906 has a PCI target and AGP master, an arbiter (ARB) that forms the core of the ASIC 906, a memory controller that controls the MEM-C 907, a plurality of DMACs (Direct Memory Access Controllers) that perform image data rotation using hardware logic, and a PCI unit that transfers data between the scanner unit 931 and the printer unit 932 via a PCI bus 922. Note that a USB interface or an IEEE1394 (Institute of Electrical and Electronics Engineers) interface may be connected to the ASIC 906.

[0029] The MEM-C907 is a local memory used as an image buffer for copying and a code buffer. The HD909 is a storage for storing image data, font data used during printing, and forms. The HD909 controls the reading and writing of data from and to the HD909 under the control of the CPU901. The AGP bus 921 is a bus interface for a graphics accelerator card proposed to speed up graphics processing, and direct high-throughput access to the MEM-P902 enables the graphics accelerator card to operate at high speed.

[0030] Further, the short-distance communication circuit 920 includes a short-distance communication circuit 920a. The short-distance communication circuit 920 is a communication circuit such as NFC or Bluetooth (registered trademark).

[0031] Furthermore, the engine control unit 930 is made up of a scanner unit 931 and a printer unit 932. The operation panel 940 is equipped with a panel display unit 940a such as a touch panel that displays current setting values, selection screens, etc. and accepts input from the operator, and an operation panel 940b that includes a numeric keypad that accepts setting values ​​for image formation conditions such as density setting conditions, a start key that accepts a copy start instruction, etc.

[0032] The controller 910 controls the entire MFP 900, for example, drawing, communication, and input from the operation panel 940. The scanner unit 931 or the printer unit 932 includes an image processing unit such as error diffusion and gamma conversion.

[0033] The MFP 900 can sequentially switch among the document box function, copy function, printer function, and fax function using an application switching key on the operation panel 940. When the document box function is selected, the MFP 900 enters document box mode, when the copy function is selected, the MFP 900 enters copy mode, when the printer function is selected, the MFP 900 enters printer mode, and when the fax function is selected, the MFP 900 enters fax mode.

[0034] The network I / F 950 is an interface for performing data communication using the network 18. The short-range communication circuit 920 and the network I / F 950 are electrically connected to the ASIC 906 via a PCI bus 922.

[0035] When authentication using an IC card is used, the MFP 900 has a built-in or external IC card reader. The MFP 900 wirelessly reads the identification information unique to the IC card from the RF tag embedded in the IC card. The IC card may be built into a smart device such as a smartphone. The MFP 900 may also use a device other than an IC card reader, such as a biometric authentication device (fingerprint, palm print, iris, face, etc.) or a barcode reader.

[0036] The hardware configuration shown in FIG. 3 is an example, and it is not necessary to include all of the components shown in FIG. 3, or it may include components other than those shown in FIG.

[0037] <Functional configuration> The information processing system 1 according to this embodiment is realized by, for example, a functional configuration as shown in Fig. 4. Fig. 4 is a functional configuration diagram of an example of the information processing system according to this embodiment. Note that the functional configuration diagram in Fig. 4 appropriately omits configurations that are not necessary for explaining this embodiment. The information processing device 10 and the device 16 realize, for example, the functional configuration in Fig. 4 by executing programs such as an OS and applications.

[0038] 4 includes a processing unit 20, a service information storage unit 22, a rate plan information storage unit 24, a contract information storage unit 25, a license information storage unit 26, and a usage authority information storage unit 28. The processing unit 20 also includes a screen data generation unit 30, a contract acceptance unit 32, a matching unit 34, a difference billing unit 36, a cancellation acceptance unit 38, a contract unit 40, a cancellation unit 42, and a usage authority management unit 44. The device 16 shown in FIG. 4 includes a display control unit 50, an operation content notification unit 52, a usage authority determination unit 54, and a service use unit 56.

[0039] The service information storage unit 22 stores base product information as shown in Fig. 5 and add-on product information as shown in Fig. 6. Fig. 5 is a structural diagram of an example of base product information. Fig. 6 is a structural diagram of an example of add-on product information.

[0040] The base product information in FIG. 5 has the product name and function of the base product as items. The product name is the name of the base product and is an example of identification information for the base product. The function is the name of a function provided by the base product and is an example of identification information for the function. Note that "Scan2mail," a service that sends data scanned by device 16 to a specified email address, and "Cloud print," a service that prints data stored on cloud storage by device 16, are examples of base products.

[0041] The add-on product information in FIG. 6 includes the product name, base product, and function of the add-on product as items. The product name is the name of the add-on product and is an example of identification information for the add-on product. The base product is the name of the corresponding base product and is an example of identification information for the corresponding base product. The function is the name of a function provided by the add-on product and is an example of identification information for the function. The add-on product information in FIG. 6 is associated with a base product to which the add-on product's (its own) function can be added using the item "Base Product." As shown in the add-on product information in FIG. 6, an add-on product can be associated with multiple base products. Note that "Scan2ocr2mail," a service that performs character recognition processing on data scanned by device 16 and sends the data to a specified email address, is an example of an add-on product. For example, "Product A Expansion Pack," an example of an add-on product, is a service that adds a character authentication function to the scanning function and email sending function provided by "Product A," an example of a base product.

[0042] The fee plan information storage unit 24 stores fee plan information as shown in Fig. 7. Fig. 7 is a diagram showing an example of fee plan information. The fee plan information in Fig. 7 has items such as plan name, product, contract period, license type, and unit price.

[0043] The plan name is the name of the rate plan and is an example of identification information for the rate plan. The product is the name of the base product or add-on product covered by the rate plan and is an example of information that defines the base product or add-on product covered by the rate plan.

[0044] The contract period is the contract period for the fee plan. The contract period represents the unit of the contract period (years, months, etc.) for using the base product or add-on product, and may be the renewal period or billing period. The license type is an example of information that defines the unit of resources, such as the user or device 16, that uses the base product or add-on product. The unit price is an example of information for calculating the fee required for the contract. Note that multiple fee plans may be defined for the same product, such as the base product or add-on product, and the user may select one.

[0045] The contract information storage unit 25 stores contract information as shown in Fig. 8. Fig. 8 is a configuration diagram of an example of contract information. The contract information in Fig. 8 has the following items: contract number, plan name, product, contract period, license type, unit price, contractor, billing destination, quantity, and update information.

[0046] The contract number is an example of identification information for contract information. The plan name, product, contract period, license type, and unit price are information copied from the fee plan information in Figure 7. The contractor is the name of the user who has signed the contract, and is an example of identification information for the user who has signed the contract. The billing destination is the account number of the billing destination to which fees are billed according to the contract, and is an example of identification information for identifying the billing destination. The quantity is the number of resources, such as users or devices 16, who have signed up to use the base product or add-on product. The update information defines the timing of contract updates based on the contract period and whether the contract information is to be automatically updated. For example, if the contract information is not to be automatically updated, a manual update is performed.

[0047] The license information storage unit 26 stores license information as shown in Fig. 9. Fig. 9 is a diagram showing an example of the structure of license information. The license information in Fig. 9 has the following items: license ID, contract number, license type, and upper limit number.

[0048] The license ID is an example of information that identifies a license. The contract number is an example of identification information for contract information, and is information for identifying the contract information in FIG. 8. The license type is an example of information that defines a unit of resource, such as a user or device 16, that uses the base product or add-on product. The upper limit number is the upper limit number of resources, such as a user or device 16, that can use the base product or add-on product based on the contract. The license information in FIG. 8 is used to manage the usage rights of the base product or add-on product.

[0049] The usage authority information storage unit 28 also stores usage authority information as shown in Fig. 10. Fig. 10 is a diagram showing an example of usage authority information. The usage authority information in Fig. 10 includes a license ID and a resource as items.

[0050] The license ID is an example of information for identifying a license. The resource defines a user or a device 16 as an example of a unit of resource that uses a base product or an add-on product. The usage authority information defines a license and a user or a device 16 that has the authority to use the base product or the add-on product under that license as a resource.

[0051] The usage authority information in Fig. 10 shows an example in which devices A to C have usage authority for "product A." The usage authority information in Fig. 10 also shows an example in which users A to B have usage authority for "product A expansion pack."

[0052] Returning to FIG. 4 , the screen data generation unit 30 of the processing unit 20 generates image data (screen data) for a screen to be displayed on the device 16 and transmits it to the device 16. The display control unit 50 of the device 16 displays various screens in accordance with the screen data received from the information processing device 10. For example, the display control unit 50 of the device 16 displays a contract screen for accepting a contract for a base product or an add-on product from the user. Also, for example, the display control unit 50 of the device 16 displays a cancellation screen for accepting cancellation of the base product or an add-on product from the user.

[0053] The operation content notifying unit 52 of the device 16 notifies the information processing device 10 of the operation content on the contract screen or cancellation screen displayed by the display control unit 50. Therefore, the contract accepting unit 32 of the processing unit 20 of the information processing device 10 can accept a contract request for a base product or an add-on product from the user based on the operation content of the user on the contract screen notified from the device 16. The contract unit 40 can update the contract information in Fig. 8 based on the accepted contract request.

[0054] Furthermore, the cancellation acceptance unit 38 of the processing unit 20 of the information processing device 10 can accept a request to cancel a base product or an add-on product from the user, based on the content of the user's operation on the cancellation screen notified from the device 16. The cancellation unit 42 can update the contract information in FIG. 8 and the like, based on the request to cancel a base product or an add-on product from the user accepted by the cancellation acceptance unit 38.

[0055] The matching unit 34 matches the contract period of the add-on product with the contract period of the base product when the contract for the base product is renewed, as will be described later. Details of the matching process for matching the contract period of the add-on product with the contract period of the base product will be described later.

[0056] When a difference in the fee required for the add-on product contract occurs as a result of the process of aligning the contract period of the add-on product with the contract period of the base product, the difference billing unit 36 ​​performs a billing process according to the difference in fee. For example, if the fee is paid at the start of the contract for using the add-on product, the difference billing unit 36 ​​performs a refund process for the difference in fee that has occurred. Also, if the fee is paid at the end of the contract for using the add-on product, the difference billing unit 36 ​​performs a billing process for the difference in fee that has occurred.

[0057] The usage authority management unit 44 manages usage authority of resources such as the user or device 16 for the base product or add-on product based on, for example, the license information in Fig. 9 and the usage authority information in Fig. 10. The usage authority determination unit 54 of the device 16 determines whether or not the user has usage authority for the base product or add-on product in accordance with the usage authority managed by the usage authority management unit 44 of the information processing device 10. The service use unit 56 uses the functions of the base product and add-on product in accordance with the determination of the usage authority determination unit 54.

[0058] <Data model of contract information when subscribing to a base product and an add-on product> Fig. 11 is a diagram showing an example of a data model for contract information when a contract is made for a base product and an add-on product. As shown in Fig. 11, separate licenses are issued for the base product and the add-on product, and usage rights are managed for each of the base product and the add-on product.

[0059] For example, in the example of Figure 11, User A can use the base product but cannot use the add-on product, User B can use both the base product and the add-on product, and User C can use the add-on product but cannot use the base product.

[0060] As shown in Figure 11, contract information is created from the pricing plans and licenses of one or more base products and add-on products. The pricing plans in the contract information are set for each base product and add-on product. Therefore, information in the contract information, such as the contract period, license type, unit price, and quantity, will differ for each base product and add-on product.

[0061] <Processing> The processing procedure of the information processing system 1 according to this embodiment will be described below. Fig. 12 is a flowchart showing an example of processing of the information processing system according to this embodiment.

[0062] In step S10, the contract unit 40 of the information processing device 10 reads out the contract information shown in Fig. 8 from the contract information storage unit 25. In step S12, the contract unit 40 determines whether or not there is a contract due for renewal based on the contract information read out in step S10. If there is no contract due for renewal, the contract unit 40 returns to step S10 and continues processing.

[0063] If there is a contract due for renewal, the contract unit 40 determines in step S14 whether the contract information for renewal is a contract for a base product. If it is a contract for a base product, the contract unit 40 proceeds to step S16 and performs processing to update the contract period for the base product. If the contract period update processing for the base product in step S16 is for automatic renewal, for example, the contract period is updated in accordance with the "contract cycle" item of the contract information. If the contract period update processing for the base product in step S16 is for manual renewal, for example, the contract unit 40 requests the "contractor" item of the contract information to update the contract period.

[0064] If it is determined in step S14 that the contract is not for the base product, the contract unit 40 proceeds to step S18 and performs processing to renew the contract period for the add-on product. If the add-on product contract period is automatically renewed, for example, the processing to renew the contract period in step S18 is performed in accordance with the "contract period" item in the contract information. If the add-on product contract period is manually renewed, for example, the processing to renew the contract period in step S18 is performed by requesting the "contractor" item in the contract information to renew the contract period.

[0065] After step S16, the process proceeds to step S20, where the matching unit 34 refers to the add-on product information in Fig. 6, for example, to identify the add-on product associated with the base product whose contract period has been updated in step S16. The matching unit 34 determines whether the identified add-on product is currently in the contract period.

[0066] If the add-on product associated with the base product whose contract period has been renewed has been contracted and is currently in the contract period, the matching unit 34 proceeds to step S22. In step S22, the matching unit 34 performs processing to match the contract period of the add-on product associated with the base product whose contract period has been renewed with the contract renewal timing of the associated base product.

[0067] The process of aligning the contract period of an add-on product currently in the contract period associated with a base product for which the contract period renewal process was performed in step S22 with the contract renewal timing of the associated base product is performed, for example, as follows.

[0068] Figure 13 is an explanatory diagram of an example of a process for aligning the contract period of an add-on product with the contract renewal timing of the associated base product. Figure 13 shows an example in which the contract period of the base product and the contract period of the add-on product are "1 year," and the contract periods of the base product and the add-on product are the same.

[0069] Figure 13 shows an example where the contract period for the base product is from "2021 / 04" to "2022 / 04". Figure 13 also shows an example where the contract period for the add-on product is from "2021 / 10" to "2022 / 10".

[0070] When the contract renewal timing for the base product arrives at "2022 / 04," the contract period for the base product will be renewed to "2022 / 04" to "2023 / 04." The contract period for the add-on product corresponding to the base product whose contract period has been renewed will also be renewed to match the contract period for the base product, "2022 / 04" to "2023 / 04," at the contract renewal timing for the associated base product, "2022 / 04." Note that in the example of FIG. 13, the payment of the fee for the add-on product contract is made at the start of the contract, and therefore renewal of the contract period for the add-on product will result in a difference (amount difference) in the fee required for the add-on product contract. Therefore, in this embodiment, when the contract period for the add-on product is renewed, a billing process according to the difference, such as a refund of the difference (fee rebate), is performed.

[0071] Figure 14 is an explanatory diagram of an example of the process of aligning the contract period of an add-on product with the contract renewal timing of the associated base product during the contract period. Figure 14 shows an example where the contract period of the base product is "one year" and the contract period of the add-on product is "six months", and the contract period of the add-on product is shorter than the contract period of the base product and is divisible.

[0072] Figure 14 shows an example where the contract period for the base product is from "2021 / 04" to "2022 / 04". Figure 14 also shows an example where the contract period for the add-on product is from "2021 / 8" to "2022 / 2".

[0073] When the contract renewal timing for the base product arrives at "2022 / 04," the contract period for the base product will be renewed to "2022 / 04" to "2023 / 04." Furthermore, the contract period for the add-on product corresponding to the base product whose contract period has been renewed will be renewed to "2022 / 04" to "2022 / 10" when the contract renewal timing for the associated base product arrives at "2022 / 04." Note that in the example of FIG. 14, the payment of the contract fee for the add-on product is made at the start of the contract, so renewal of the contract period for the add-on product will result in a difference in the fee required for the add-on product contract. Therefore, in this embodiment, when the contract period for the add-on product is renewed, a billing process according to the difference, such as a refund of the difference, is performed.

[0074] Figure 15 is an explanatory diagram of an example of a process for aligning the contract period of an add-on product with the contract renewal timing of the associated base product during the contract period. Figure 15 shows an example in which the contract period of the base product is "1 year" and the contract period of the add-on product is "5 months", and the contract period of the add-on product is shorter than the contract period of the base product and cannot be divided evenly.

[0075] Figure 15 shows an example where the contract period for the base product is from "2021 / 04" to "2022 / 04". Figure 15 also shows an example where the contract period for the add-on product started from "2021 / 4" and was updated to "2021 / 9" and "2022 / 2".

[0076] When the contract renewal timing for the base product arrives at "2022 / 04," the contract period for the base product will be renewed to "2022 / 04" to "2023 / 04." Furthermore, the contract period for the add-on product corresponding to the base product whose contract period has been renewed will be renewed to "2022 / 04" to "2022 / 9" when the contract renewal timing for the associated base product arrives at "2022 / 04." Note that in the example of FIG. 15, the payment of the contract fee for the add-on product is made at the start of the contract, so renewal of the contract period for the add-on product will result in a difference in the fee required for the add-on product contract. Therefore, in this embodiment, when the contract period for the add-on product is renewed, a billing process according to the difference, such as a refund of the difference, is performed.

[0077] In the example of Figure 15, each time the contract for the base product is renewed, the difference in the contract fee for the add-on product is charged, and the contract period for the add-on product is updated to match the start date of the contract period for the base product.

[0078] As shown in FIGS. 13 to 15, add-on products that can be associated with base products are add-on products whose contract period is the same as that of the base product or shorter than that of the base product.

[0079] In this embodiment, the contract screen displayed on device 16 displays an add-on product associated with a base product in such a manner that the add-on product can be accepted as a contract object if the base product associated with the add-on product has already been contracted or is selected as a contract object.

[0080] By displaying such a contract screen, in this embodiment, an add-on product cannot be contracted when the associated base product is not currently in its contract period, or when functions cannot be added to the base product.

[0081] In this embodiment, the cancellation screen displayed on device 16 accepts cancellation of an add-on product when a request to cancel the add-on product associated with the base product is received. Also, the cancellation screen displayed on device 16 is displayed so as not to accept cancellation of the base product associated with the add-on product unless the add-on product is included.

[0082] In this embodiment, by displaying such a cancellation screen, the associated base product is canceled, and a contract for an add-on product that does not allow functions to be added to the base product is not left uncancelled.

[0083] As described above, according to this embodiment, it is possible to improve the ease of managing information relating to contracts for multiple services such as base products and add-on products.

[0084] Each function of the above-described embodiments can be realized by one or more processing circuits. Here, the term "processing circuit" in this specification includes a processor programmed to perform each function by software, such as a processor implemented by an electronic circuit, as well as devices such as an ASIC (Application Specific Integrated Circuit), a DSP (Digital Signal Processor), an FPGA (Field Programmable Gate Array), or a conventional circuit module designed to perform each function described above.

[0085] The devices described in the examples merely represent one of multiple computing environments for implementing the embodiments disclosed herein. The present invention is not limited to these embodiments, and the components in these embodiments include those that would be easily conceived by a person skilled in the art, those that are substantially identical, and those that are within the scope of what is called equivalents. Furthermore, various omissions, substitutions, modifications, and combinations of the components can be made without departing from the spirit of the present embodiments. [Explanation of symbols]

[0086] 1. Information Processing Systems 10. Information processing equipment 12 Information processing terminal 14 Electronic equipment 16 devices 18 Network 20 Processing section 22 Service information storage unit 24. Price plan information storage unit 25 Contract information storage unit 26 License information storage unit 28 Usage authority information storage unit 30 Screen data generation unit 32 Contract Reception Department 34 Matching section 36 Differential Billing Department 38 Cancellation Reception Department 40 Contract Department 42 Cancellation Section 44 User Rights Management Department 50 Display control unit 52 Operation content notification section 54 Usage authority determination unit 56 Service User Department [Prior art documents] [Patent documents]

[0087] [Patent Document 1] Japanese Patent Application Laid-Open No. 2018-112990

Claims

1. An information processing device that manages information relating to a contract for a first service and a second service, a service information storage means for storing information on the second service in association with the first service; a contract acceptance means for accepting a contract for the second service stored in association with the first service; a matching means for matching the contract period of the second service for which the contract has been accepted with the contract period of the first service at the timing of renewal of the contract of the first service stored in association with the second service; An information processing device having the above.

2. the service information storage means stores information on the second service, the contract renewal period of which is the same as or shorter than the contract renewal period of the first service, in association with the first service; 2. The information processing device according to claim 1,

3. a difference billing means for billing the user for a difference in fee for the second service resulting from the matching when the contract period of the second service is matched with the contract period of the first service by the matching means; 3. The information processing apparatus according to claim 1, further comprising:

4. The matching means causes a contract for the second service to be renewed at a contract renewal timing for the first service stored in association with the second service, thereby changing the contract period for the second service.

4. The information processing device according to claim 1, wherein:

5. The contract acceptance means displays the second service stored in association with the first service for which a contract has already been made or the first service selected as a contract target in a manner that allows acceptance as a contract target.

5. The information processing device according to claim 1, wherein:

6. a cancellation acceptance means for accepting cancellation of the first service or the second service stored in association with each other; a cancellation means for canceling the second service when the cancellation acceptance means accepts cancellation of the second service, and for canceling the first service and the second service stored in association with the first service when the cancellation acceptance means accepts cancellation of the first service; The information processing device according to claim 1 , further comprising:

7. a usage authority management means for managing users or devices to which usage authority for the first service is assigned by the contract and which can use the first service, and users or devices to which usage authority for the second service is assigned by the contract and which can use the second service, respectively; The information processing device according to claim 1 , further comprising:

8. 1. A contract management method executed by an information processing device that manages information relating to a contract for a first service and a second service, a contract acceptance step of accepting a contract for the second service stored in association with the first service in a service information storage means that stores information on the second service in association with the first service; a matching step of matching a contract period of the second service for which the contract has been accepted with a contract period of the first service at a contract renewal timing of the first service stored in association with the second service; A contract management method having the following features:

9. an information processing device that manages information relating to a contract for the first service and the second service; a service information storage means for storing information on the second service in association with the first service; a contract acceptance means for accepting a contract for the second service stored in association with the first service; a matching means for matching the contract period of the second service, for which the contract has been accepted, with the contract period of the first service at the timing of renewal of the contract of the first service, which is stored in association with the second service; A program to function as a

Images