JP7502943B2 - Information processing device, information processing method, and program - Google Patents

Description

The present invention relates to an information processing device, an information processing method, and a program.

A subscription product sales system is known that can sell multiple types of subscription products by associating different contract information with each product (see, for example, Patent Document 1). This subscription product sales system includes a product information management means for managing product information related to multiple types of subscription products that can be sold, a product designation means for designating one of the multiple types of subscription products, and a contract information management means for acquiring product information related to the subscription product designated via the product designation means from the product information management means and managing subscription contract information corresponding to the subscription product in association with the product information.

JP 2020-67777 A

If a user receives a product or service from a specific business in the usual unit provided by that business, the user may end up receiving more products or services than he or she needs, and may not feel that the cost benefit is sufficient.

The purpose of the present invention is to enable a user to receive only the amount of products or services that the user needs from a specific business operator.

To this end, the present invention provides an information processing device that includes a means for identifying a plurality of users who wish to receive a product or service from a specific business operator in a unit different from the normal unit in which the specific business operator provides the product or service, and a means for notifying the specific business operator of information indicating the different unit desired by the plurality of users and each of the plurality of users identified by the means for identifying.

The specific business operator may be one of multiple businesses.

The different units may include units obtained by dividing normal units. In this case, the identification means may identify the multiple users such that the sum of the different units desired by each of the multiple users equals the normal unit. The identification means may also identify the multiple users that are a group of users who satisfy a predetermined condition.

The information processing device may further include a receiving means for receiving a right to receive a product or service from a specific business operator, and a transmitting means for transmitting the right received by the receiving means to a plurality of users. In this case, the receiving means may receive the right from the specific business operator before the identification means identifies the plurality of users, or may receive the right from the specific business operator after the identification means identifies the plurality of users.

The present invention also provides an information processing method including the steps of: a computer identifying a plurality of users who wish to receive a product or service from a specific business in a unit different from the normal unit in which the specific business provides the product or service; and a computer notifying the specific business of information indicating the different unit desired by the identified plurality of users and each of the plurality of users.

The present invention also provides a program for enabling a computer to realize a function of identifying a plurality of users who wish to receive a product or service from a specific business in a unit different from the normal unit in which the specific business provides the product or service, and a function of notifying the specific business of information indicating the different unit desired by the identified plurality of users and each of the plurality of users.

The present invention allows a user to receive only the amount of products or services that the user needs from a specific business.

1 is a diagram showing an example of the overall configuration of a service providing system according to an embodiment of the present invention. FIG. 2 is a diagram illustrating an example of a hardware configuration of an intermediary server according to an embodiment of the present invention. FIG. 2 is a diagram showing an overview of the operation of the service providing system according to the embodiment of the present invention. 4 is a block diagram showing an example of a functional configuration of an intermediary server according to an embodiment of the present invention. FIG. 4 is a diagram showing an example of service information stored in a service information storage unit of the intermediary server in the embodiment of the present invention. FIG. 11 is a flowchart showing a first operation example of an intermediary server in the embodiment of the present invention. 11 is a flowchart showing a first operation example of an intermediary server in the embodiment of the present invention. 13 is a flowchart showing a second operation example of the intermediary server in the embodiment of the present invention. 13 is a flowchart showing a second operation example of the intermediary server in the embodiment of the present invention.

Below, an embodiment of the present invention will be described in detail with reference to the attached drawings. Note that this embodiment can be applied to the provision of goods or services, but in the following, the provision of goods will also be considered as the provision of a service for selling goods, and the embodiment will be described as being applied to the provision of a service.

[Overall configuration of the service provision system]
FIG. 1 is a diagram showing an example of the overall configuration of a service providing system 1 in this embodiment. As shown in the figure, this service providing system 1 is configured by connecting user terminals 10 ₁ to 10 ₃ , service provider servers 20 ₁ to 20 ₃ , and an intermediary server 30 to a communication line 80. In the figure, user terminals 10 ₁ to 10 ₃ are shown, but when there is no need to distinguish between them, they may be referred to as user terminals 10. Although three user terminals 10 are shown, there may be four or more. In the figure, service provider servers 20 ₁ to 20 ₃ are shown, but when there is no need to distinguish between them, they may be referred to as service provider servers 20. Although three service provider servers 20 are shown, there may be four or more.

The user terminal 10 is a terminal device used by a user. For example, a web browser is installed on the user terminal 10. When the user operates this web browser to display services provided by the service provider server 20 and selects a desired service from the displayed services, the user terminal 10 communicates the selected service to the intermediary server 30. The user terminal 10 may be, for example, a personal computer, a tablet terminal, a smartphone, etc. It may also be specific communication software other than a web browser.

The service provider server 20 is a server computer used by a service provider. Here, the service provider is a business that provides a service. The form of the service may be, for example, a subscription service that provides a service for a certain period of time in exchange for a certain fee. The content of the service may be, for example, a service that dispatches a person to the user's location. An example of such a service is a housekeeping service. Furthermore, as described above, the provision of a service also includes the provision of a product, so the content of the service may be, for example, a service that delivers an item to the user. An example of such a service is a home delivery service for picture books, prepared foods, etc. Alternatively, the content of the service may be a service that transmits electronic data to the user terminal 10 via the communication line 80. An example of such a service is a video content distribution service. When the service provider server 20 is notified of the service selected by the user from the intermediary server 30, the service provider server 20 provides the selected service to the user. The service provider server 20 may be, for example, a personal computer.

The intermediary server 30 is a server computer used by an intermediary who mediates between the user and the service provider. A web server is installed on the intermediary server 30. The intermediary server 30 accepts a service selected by the user from the user terminal 10 using this web server, and notifies the service provider server 20 of the selected service. The intermediary server 30 may be, for example, a personal computer.

The communication line 80 is a communication means used for information communication between the user terminal 10 and the intermediary server 30, between the intermediary server 30 and the service provider server 20, etc. As the communication line 80, for example, the Internet may be used.

[Hardware configuration of the intermediary server, user terminal, and service provider server]
2 is a diagram showing an example of the hardware configuration of the intermediary server 30. As shown in the figure, the intermediary server 30 includes a control unit 31 that controls the operation of the entire device, a hard disk drive 32 that stores data and the like, a communication interface 33 that realizes communication via a LAN (Local Area Network) cable or the like, an input device 34 into which information is input, and a display device 35 on which information is displayed.

The control unit 31 has a CPU 311, a ROM 312 in which basic software, a BIOS, etc. are stored, and a RAM 313 used as a work area. The CPU 311 may be a multi-core. The ROM 312 may be a rewritable non-volatile semiconductor memory. The control unit 31 is what is known as a computer.

The hard disk drive 32 is a device that reads and writes data to a non-volatile storage medium that has a magnetic material applied to the surface of a disk-shaped substrate. The non-volatile storage medium may be a semiconductor memory or the like. The communication interface 33 is an interface used to connect to other devices. The input device 34 is, for example, a keyboard, a mouse, or a touch panel, and the display device 35 is, for example, a liquid crystal display or an organic EL (Electro Luminescence) display.

The control unit 31, hard disk drive 32, communication interface 33, input device 34, and display device 35 are connected via a bus 39 and signal lines not shown.

The hardware configuration example shown in FIG. 2 can also be regarded as an example of the hardware configuration of the user terminal 10 and the service provider server 20. However, when describing the user terminal 10, the control unit 31, CPU 311, ROM 312, RAM 313, hard disk drive 32, communication interface 33, input device 34, and display device 35 in FIG. 2 will be written as control unit 11, CPU 111, ROM 112, RAM 113, hard disk drive 12, communication interface 13, input device 14, and display device 15, respectively. And, when describing the service provider server 20, the control unit 31, CPU 311, ROM 312, RAM 313, hard disk drive 32, communication interface 33, input device 34, and display device 35 in FIG. 2 will be written as control unit 21, CPU 211, ROM 212, RAM 213, hard disk drive 22, communication interface 23, input device 24, and display device 25, respectively.

[Outline of the present embodiment]
In such a service provision system 1, in this embodiment, the intermediary server 30 identifies a group of users who wish to receive services in units different from the usual units in which the service provider provides services, and notifies the service provider of information indicating the identified users and the unit desired by each user.

Here, units that are different from normal units may include units that are divisions of normal units.

In addition, after the information indicating the identified multiple users and the unit desired by each user is notified to a specific business operator, each user will receive services from the service provider in the unit desired by that user.

Figures 3(a) and (b) are diagrams showing an overview of the operation of such a service providing system 1. In this embodiment, it is assumed that the service provider S prepares a flat-rate plan for providing services at a frequency and amount determined by the service provider S. Hereinafter, such a flat-rate plan prepared by the service provider S will be referred to as the "normal plan."

Figure 3 (a) shows a first example of the outline of the operation of the service providing system 1. This first example is an example in which the normal plan prepared by the service provider S is arranged to a desired plan desired by the users U1 and U2, and the service provider S only has the normal plan prepared. Here, arranging the normal plan means reducing the frequency and amount determined in the normal plan. In this case, the intermediary M divides the normal plan of the service provider S into the desired plans of the users U1 and U2, so that the users U1 and U2 can receive the service from the service provider S in the desired plan, and collects a fee from at least one of the users and the service provider S in return. Note that a profit may be collected in place of the fee, but in this embodiment, the fee from the user will be used as an example for explanation.

Specifically, assume that user U1 wishes to use a% of the regular plan and has paid a service charge of a% of the regular plan's flat rate plus commission to intermediary M. Also assume that user U2 wishes to use b% of the regular plan and has paid a service charge of b% of the regular plan's flat rate plus commission to intermediary M. Intermediary M will then pay a service charge of 100% of the regular plan's flat rate to service provider S, and service provider S will provide a% of the service to user U1 and b% of the service to user U2.

For example, consider the case where service provider S provides housekeeping services four times a month for 20,000 yen. In this case, suppose that two users who want to use this housekeeping service but think that once a month is sufficient, and one user who wants to use this housekeeping service but thinks that twice a month is sufficient, appear. Then, intermediary M receives 5,000 yen plus a fee from each of the former two users, and 10,000 yen plus a fee from the latter user, and pays 20,000 yen to service provider S, allowing all users to receive the service as frequently as they wish.

Figure 3 (b) shows a second example of the outline of the operation of the service providing system 1. This second example is an example in which the regular plan provided by the service provider S is arranged to a desired plan desired by the users U1 and U2, and the service provider S does not provide the desired plan as a spot plan, but the fee for the spot plan is set. Here, arranging the regular plan is, as in the first example, a reduction in the frequency and amount set in the regular plan. Also, a spot plan is a fee-per-use plan in which a fee is paid each time a service is received with a frequency and amount less than that set in the regular plan. In this case, the intermediary M collects the fee for the spot plan from the users U1 and U2, pays the fee for the regular plan to the service provider S, and uses the difference to enable the users U1 and U2 to receive the service from the service provider S with the desired plan.

Specifically, assume that user U1 wishes to use the spot plan n times and has paid the service fee for n instances of the spot plan to intermediary M. Also assume that user U2 wishes to use the spot plan m times and has paid the service fee for m instances of the spot plan to intermediary M. Then, intermediary M pays the service fee for the regular plan's flat rate to service provider S, and service provider S provides user U1 with n instances of the one-time service and user U2 with m instances of the one-time service.

For example, in the housekeeping service described above, the service provider S may prepare a spot plan for housekeeping services once a month in addition to a regular plan of four housekeeping services per month. In such cases, the fee for the spot plan is generally more expensive than the fixed fee for the regular plan. Therefore, in this second example, the intermediary M does not collect a commission as in the first example, but instead has the service provider S provide the user with the service at the spot plan fee for each use, and pays the regular plan fee to the service provider S, with the difference being sales.

As such, there are two examples of the general operation of the service providing system 1, but the first example will be explained in detail below.

[Functional configuration of the intermediary server]
4 is a block diagram showing an example of the functional configuration of the intermediary server 30 in this embodiment. As shown in the figure, the intermediary server 30 in this embodiment includes a receiving unit 41, a service usage right management unit 42, a service usage right storage unit 43, a service information storage unit 44, a service information management unit 45, and a transmitting unit 46.

The receiving unit 41 receives a service content viewing request from the user terminal 10, indicating that the user is requesting to view the service content of the service provider. Here, the service content viewing request includes a service provider ID and a service ID. The service provider ID is identification information that identifies the service provider, and the service ID is identification information that identifies a service among multiple services provided by the service provider.

The receiving unit 41 also receives from the user terminal 10 a service usage request indicating that the user is requesting to use the service of the service provider under a desired plan different from the normal plan. Here, the service usage request includes a user ID, a service provider ID, a service ID, and an installment plan specification. The user ID is identification information for identifying the user. As described above, the service provider ID is identification information for identifying the service provider, and the service ID is identification information for identifying the service, as described above. The installment plan specification is the installment plan specification selected by the user as the desired plan from among multiple installment plan specifications obtained by dividing the normal plan specification indicating the frequency and amount determined in the normal plan. Note that in this embodiment, when the term "normal plan" is used, it is intended to include the "normal plan" multiplied by the "normal plan unit number" when the "normal plan unit number" (see FIG. 5) is greater than 1.

On the other hand, the receiving unit 41 receives a service usage right for using the service of the service provider from the service provider server 20. Here, the service usage right means electronic data necessary for using the service of the service provider. The service usage right may be linked to a service provider ID and a service ID. The service usage right may be sold by a sales promotion means (not shown) of the intermediary server 30 encouraging the service provider server 20 to sell the service usage right. At that time, the intermediary may pay the purchase price of the service usage right. Alternatively, the purchase price of the service usage right may be paid later. In either case, the service usage right indicates that money has been or will be paid from the intermediary to the service provider. In this case, the service usage right is an example of a right to receive a product or service from a specific business operator, and the receiving unit 41 is an example of a receiving means for receiving the right to receive a product or service.

When the receiving unit 41 receives a service usage right from the service provider server 20, the service usage right management unit 42 divides the service usage right into predetermined units. Here, the predetermined units may be determined, for example, based on information stored in the service information storage unit 44. That is, the service information storage unit 44 stores multiple installment plan specifications obtained by dividing a normal plan specification, and the service usage right management unit 42 divides the service usage right into units equivalent to the smallest installment plan specification found from the multiple installment plan specifications. The service usage right management unit 42 then stores the divided service usage right (hereinafter referred to as "divided service usage right") in the service usage right storage unit 43, linking it to the service provider ID and the service ID.

On the other hand, when the receiving unit 41 receives a service usage request from the user terminal 10, the service usage right management unit 42 extracts the split service usage rights stored in the service usage right storage unit 43. Specifically, the service usage right management unit 42 focuses on the split service usage rights linked to the service provider ID and service ID included in the service usage request, among the split service usage rights stored in the service usage right storage unit 43. Furthermore, if the service usage right management unit 42 has received a user ID and a desired plan from the service information management unit 45, it extracts the focused split service usage rights in groups of a size according to the desired plan for each user ID. The service usage right management unit 42 then passes the split service usage rights grouped together for each user ID to the transmitting unit 46.

The service usage right memory unit 43 stores the divided service usage rights obtained by the service usage right management unit 42 by dividing the service usage right.

The service information storage unit 44 stores information about the services provided by the service provider (hereinafter referred to as "service information"). The service information includes a service provider ID, a service ID, service content, information about the regular plan, user conditions, information about the installment plan, and a user ID. Specific examples of service information will be described later.

When the receiving unit 41 receives a service content viewing request from the user terminal 10, the service information management unit 45 extracts the service information corresponding to the service provider ID and service ID included in the service content viewing request from the service information storage unit 44. Then, the service information, regular plan information, installment plan information, etc. included in this service information are passed to the transmitting unit 46.

In addition, when the receiving unit 41 receives a service use request from the user terminal 10, the service information management unit 45 determines whether the user information linked to the user ID included in the service use request satisfies the user conditions included in the service information storage unit 44. Then, when it is determined that the user ID satisfies the user conditions, the service information management unit 45 registers this user ID in the installment plan specification included in the service use request among the multiple installment plan specifications stored in the service information storage unit 44. This is an example of identifying multiple users who bundle together users who satisfy predetermined conditions. However, if the total of the multiple installment plan specifications stored in the service information storage unit 44 in which the user ID is registered exceeds the normal plan specification stored in the service information storage unit 44, there is no need to bundle any more users, so it is not necessary to register the user ID. In addition, the service information management unit 45 determines whether the multiple installment plan specifications stored in the service information storage unit 44 in which the user ID is registered can constitute the normal plan specification stored in the service information storage unit 44. Here, if the sum of the multiple installment plan specifications in which the user ID is registered is equal to the normal plan specification, it may be determined that the normal plan specification can be configured. This is an example of identifying multiple users so that the sum of the different units desired by each of the multiple users is the normal unit. Alternatively, even if the sum of the multiple installment plan specifications in which the user ID is registered is not equal to the normal plan specification, it may be determined that the normal plan specification can be configured if the sum of the multiple installment plan specifications in which the user ID is registered is equal to or greater than a certain percentage of the normal plan specification. If it is determined that the multiple installment plan specifications in which the user ID is registered are able to configure the normal plan, the service information management unit 45 transfers the user ID and the installment plan specification in which the user ID is registered to the service usage right management unit 42 and the transmission unit 46. In this case, the normal plan specification is an example of a normal unit in which a specific business provides a product or service, and the installment plan specification is an example of a unit different from the normal unit. In addition, the service information management unit 45 is an example of a specifying means for specifying multiple users who wish to receive a product or service from a specific business in a unit different from the normal unit.

On the other hand, when the receiving unit 41 receives a service usage right from the service provider server 20, the service information management unit 45 reads out the smallest installment plan spec among the multiple installment plan specs obtained by dividing the normal plan spec from the service information storage unit 44 and passes it to the service usage right management unit 42.

When the receiving unit 41 receives a service content viewing request from the user terminal 10, the transmitting unit 46 transmits the service content, information on the regular plan, information on the installment plan, etc., passed from the service information management unit 45 to the user terminal 10.

When the receiving unit 41 receives a service use request from the user terminal 10, if the service information management unit 45 has passed on the user ID and the installment plan specifications to the service provider server 20, the transmitting unit 46 transmits these pieces of information. In this case, the transmitting unit 46 is an example of a notification means for notifying a specific business operator of information indicating different units desired by multiple users and each of the multiple users. Also, when the receiving unit 41 receives a service use request from the user terminal 10, if the service use right management unit 42 has passed on the split service use right, the transmitting unit 46 transmits the split service use right to the user terminal 10. Specifically, if the service use right management unit 42 has passed on the split service use right summarized by user ID, the transmitting unit 46 transmits the split service use right to the user terminal 10 used by the user of the corresponding user ID. In this case, the transmitting unit 46 is an example of a transmission means for transmitting rights to multiple users.

These functional units are realized by the cooperation of software and hardware resources. Specifically, the CPU 311 (see FIG. 2) loads the programs that realize the receiving unit 41, the service usage right management unit 42, the service information management unit 45, and the transmitting unit 46 from, for example, the hard disk drive 32 (see FIG. 2) into the RAM 313 (see FIG. 2) and executes them, thereby realizing these functional units. The service usage right memory unit 43 and the service information memory unit 44 are realized, for example, by the hard disk drive 32 (see FIG. 2).

Figure 5 is a diagram showing an example of service information stored in the service information storage unit 44. As shown in the figure, the service information associates a service provider ID, a service ID, service content, regular plan specifications, regular plan fee, regular plan unit number, user conditions, installment plan specifications, installment plan fee, installment plan fee, and a user ID.

The service provider ID is identification information that identifies the service provider. The service provider ID is assigned in advance so that multiple service providers that provide services in this service provision system 1 can be distinguished from one another.

The service ID is identification information that identifies a service provided by a service provider identified by the corresponding service provider ID. The service ID is assigned in advance so that it can at least distinguish between multiple services provided by one service provider.

Service content is information that describes what kind of service is identified by the corresponding service ID.

The regular plan specs are the frequency and amount specified in the regular plan for the service identified by the corresponding service ID.

The regular plan fee is the fee required to use the service identified by the corresponding service ID under the regular plan.

The number of units of the regular plan is a number that indicates how many times the frequency and amount specified in the regular plan the service identified by the corresponding service ID can be used. In other words, the number of units of the regular plan is a number that indicates how many people's worth of service are provided in the regular plan, assuming that one unit of the regular plan is for one person.

The user conditions are conditions that must be met by a user when a service provider identified by the corresponding service provider ID provides the user with a service identified by the corresponding service ID.

The installment plan specs are the frequency and amount determined by the installment plan when the corresponding regular plan is divided into multiple types of installment plans. As the installment plan specs, multiple installment plan specs that the user can select are stored.

The installment plan fee is the fee required to use the service identified by the corresponding service ID under the corresponding installment plan.

The installment plan fee is a fee that the intermediary collects from the user to enable the service provider to provide the user with the service identified by the corresponding service ID under the corresponding installment plan.

The user ID is identification information that identifies a user who wishes to use the service identified by the corresponding service ID of the service provider identified by the corresponding service provider ID with the corresponding installment plan.

Here, we will explain the meaning of each piece of service information shown in Figure 5.

The service information for service provider ID "S1" and service ID "S11" indicates that the regular plan for the service provides four housekeeping services per month for 20,000 yen. Furthermore, the number of units for the regular plan is generally a large number indicating a large number of people, such as 100 people, but in this service information, the number of units for the regular plan is set to "1" to simplify the explanation. Furthermore, this service information indicates that, for the sake of temporary staffing, a condition for users who can receive the service is that they "reside in a certain ward." This service information also indicates that the regular plan is divided into four installment plans. The first installment plan provides four housekeeping services per month for 20,000 yen plus 0 yen fee, the second installment plan provides three housekeeping services per month for 15,000 yen plus 500 yen fee, the third installment plan provides two housekeeping services per month for 10,000 yen plus 1,000 yen fee, and the fourth installment plan provides one housekeeping service per month for 5,000 yen plus 1,500 yen fee. Furthermore, this service information indicates that the user with user ID "U1" and the user with user ID "U2" want the fourth installment plan, and the user with user ID "U3" wants the third installment plan.

The service information for service provider ID "S2" and service ID "S21" indicates that the regular plan for the service provides a home delivery service of two picture books once a month for 1,000 yen. The number of units for the regular plan is set to "1" for the same reasons as above. This service information also indicates that the regular plan is divided into two installment plans. The first installment plan provides a home delivery service of two picture books once a month for 1,000 yen plus a fee of 0 yen, and the second installment plan provides a home delivery service of two picture books once every two months for 500 yen plus a fee of 50 yen. This service information further indicates that the user with user ID "U4" and the user with user ID "U5" desire the second installment plan.

The service information for service provider ID "S3" and service ID "S31" indicates that the regular plan for the service provides home delivery of five prepared meals per month for 2,000 yen. The number of units for the regular plan is set to "1" for the same reasons as above. Furthermore, this service information indicates that a condition for users who can receive the service is that they "reside in XX ward," in order to maintain the freshness of the food. This service information also indicates that the regular plan is divided into five installment plans. The first installment plan provides a monthly delivery service of 5 prepared dishes for 2000 yen plus 0 yen handling fee, the second installment plan provides a monthly delivery service of 4 prepared dishes for 1600 yen plus 5 yen handling fee, the third installment plan provides a monthly delivery service of 3 prepared dishes for 1200 yen plus 10 yen handling fee, the fourth installment plan provides a monthly delivery service of 2 prepared dishes for 800 yen plus 15 yen handling fee, and the fifth installment plan provides a monthly delivery service of 1 prepared dish for 400 yen plus 20 yen handling fee. Furthermore, this service information indicates that the user with user ID "U6" desires the fourth installment plan, and the user with user ID "U7" desires the third installment plan.

[Operation of the intermediary server]
6-1 and 6-2 are flow charts showing a first operation example of the intermediary server 30 in the present embodiment. The operation of this flow chart is executed, for example, at regular intervals.

This first operation example is an operation example in which a service content viewing request and a service usage request are received from the user terminal 10 after a service usage right is received from the service provider server 20. In other words, it is assumed that the service usage right is purchased from the service provider before a service usage request is received from the user. This first operation example is an example of a case in which rights are received from a specific business operator prior to identifying multiple users.

Prior to this operation, the intermediary server 30 acquires the portion of the service information other than the user ID from the service provider server 20 and stores it in the service information storage unit 44. In this case, in this first operation example, as described above, a service usage right is purchased from the service provider before receiving a service usage request from the user, so the number of regular plan units in the service information is determined according to the purchase price of the service usage right.

As shown in FIG. 6-1, in the intermediary server 30, the receiving unit 41 first determines whether the service usage right has been received from the service provider server 20 (step 301).

When the receiving unit 41 determines that the service usage right has been received from the service provider server 20, the service usage right management unit 42 divides the service usage right (step 302). Specifically, the service usage right management unit 42 acquires the smallest installment plan specification among the multiple installment plan specifications stored in the service information storage unit 44 from the service information management unit 45. Then, the service usage right received in step 301 is divided into multiple split service usage rights of a size equivalent to this smallest installment plan specification. The multiple split service usage rights are linked to the service provider ID and the service ID and stored in the service usage right storage unit 43. The service usage right management unit 42 then advances the process to step 303.

On the other hand, if the receiving unit 41 does not determine that the service usage right has been received from the service provider server 20, it proceeds to step 303 without performing step 302.

Next, in the intermediary server 30, the receiving unit 41 determines whether a request to view the service contents has been received from the user terminal 10 (step 303).

If the receiving unit 41 determines that a service content viewing request has been received from the user terminal 10, the service information management unit 45 extracts the service content, etc., contained in the service information stored in the service information storage unit 44 (step 304). Specifically, the service information management unit 45 extracts the service content, etc., from the service information storage unit 44 using the service provider ID and service ID contained in the service content viewing request received in step 303 as keys. The transmitting unit 46 then transmits the service content, etc., extracted in step 304 to the user terminal 10 (step 305). The transmitting unit 46 then advances the process to step 311 in FIG. 6-2.

On the other hand, if the receiving unit 41 does not determine that a service content viewing request has been received from the user terminal 10, it proceeds to step 311 in FIG. 6-2 without performing steps 304 and 305.

Next, as shown in FIG. 6-2, in the intermediary server 30, the receiving unit 41 determines whether a service usage request has been received from the user terminal 10 (step 311).

If the receiving unit 41 determines that a service use request has been received from the user terminal 10, the service information management unit 45 determines whether the service use request satisfies the user conditions (step 312). Specifically, the service information management unit 45 determines whether the user information linked to the user ID included in the service use request received in step 311 satisfies the user conditions stored in the service information storage unit 44. Note that if the user conditions are not stored in the service information storage unit 44, the service information management unit 45 may determine that the service use request satisfies the user conditions.

If it is determined that the service usage request satisfies the user conditions, the service information management unit 45 determines whether the total of the installment plan specifications requested for use so far by the service usage request will exceed the normal plan specifications (step 313). Specifically, the service information management unit 45 registers the user ID included in the service usage request received in step 311 to the installment plan specifications included in the service usage request received in step 311, thereby determining whether the total of the installment plan specifications for which the user ID is registered will exceed the normal plan specifications.

If it is determined that the total of the installment plan specifications requested for use up to this point will not exceed the normal plan specifications, the service information management unit 45 registers the user ID in the installment plan specifications (step 314). Specifically, the service information management unit 45 registers the user ID included in the service usage request received in step 311 to the installment plan specifications included in the service usage request received in step 311.

When the user ID is registered in the installment plan spec in this way, the service information management unit 45 determines whether a regular plan spec can be constructed using the installment plan spec in which the user ID is registered (step 315). Specifically, the service information management unit 45 determines whether the sum of the installment plan specs in which the user ID is registered is equal to the regular plan spec. Alternatively, it may determine whether the sum of the installment plan specs in which the user ID is registered is equal to or greater than a certain percentage of the regular plan spec.

If it is determined that a normal plan specification can be configured using the installment plan specification in which the user ID is registered, the service information management unit 45 extracts the user ID and the desired plan from the service information storage unit 44 (step 316). Specifically, the service information management unit 45 extracts from the service information storage unit 44 a plurality of installment plan specifications corresponding to the service provider ID and service ID included in the service usage request received in step 311. Next, the service information management unit 45 extracts the user ID registered in one of the extracted plurality of installment plan specifications. Next, the service information management unit 45 extracts the installment plan specification in which the extracted user ID is registered as the desired plan desired by the user of this user ID.

As a result, the transmission unit 46 transmits the user ID and desired plan extracted in step 316 to the service provider server 20 (step 317).

Next, the service usage right management unit 42 extracts split service usage rights from the service usage right storage unit 43 (step 318). Specifically, the service usage right management unit 42 focuses on multiple split service usage rights stored in association with the service provider ID and service ID included in the service usage request received in step 311. Next, the service usage right management unit 42 extracts an amount of split service usage rights equivalent to the desired plan extracted in step 316, in association with the user ID extracted in step 316.

As a result, the transmission unit 46 transmits the split service usage right extracted in step 318 to the user terminal 10 corresponding to the user ID with which the split service usage right is associated (step 319).

On the other hand, if the receiving unit 41 does not determine in step 311 that a service usage request has been received from the user terminal 10, the receiving unit 41 terminates the process without performing steps 312 to 319.

If it is not determined in step 312 that the service usage request satisfies the user conditions, the service information management unit 45 ends the process without performing steps 314 to 319. In this case, in response to an instruction from the service information management unit 45, the transmission unit 46 may suggest to the user of the user ID that the user information linked to the user ID satisfies the user conditions for the use of another service.

Furthermore, even if it is determined in step 313 that the total of the installment plan specifications requested for use up to this point will exceed the normal plan specifications, the service information management unit 45 ends the process without performing steps 314 to 319. In this case, the service information management unit 45 may discard the user ID that was not registered in step 314, or may retain it for registration in the installment plan specifications to be prepared later.

Furthermore, if it is not determined in step 315 that a normal plan specification can be configured based on the installment plan specification in which the user ID is registered, the service information management unit 45 also ends the process without performing steps 316 to 319. In this case, the service information management unit 45 may temporarily reserve or delete the user ID for which it is not determined in step 315 that a normal plan specification can be configured.

Figures 7-1 and 7-2 are flowcharts showing a second operation example of the intermediary server 30 in this embodiment. The operation of this flowchart is executed, for example, at regular intervals.

This second operation example is an operation example in which a service usage right is received from the service provider server 20 after a service content viewing request and a service usage request are received from the user terminal 10. In other words, it is assumed that a service usage right is purchased from the service provider after a service usage request is received from a user. This second operation example is an example of a case in which rights are received from a specific business operator after multiple users are identified.

Prior to this operation, the intermediary server 30 acquires the portion of the service information other than the user ID from the service provider server 20 and stores it in the service information storage unit 44. In this case, in this second operation example, as described above, a service usage right is purchased from the service provider after a service usage request is received from the user, so the number of regular plan units in the service information may be determined, for example, according to the upper limit of the service usage right that can be purchased at one time, as determined by the intermediary.

As shown in FIG. 7-1, in the intermediary server 30, the receiving unit 41 first determines whether a service content viewing request has been received from the user terminal 10 (step 351).

If the receiving unit 41 determines that a service content viewing request has been received from the user terminal 10, the service information management unit 45 extracts the service content, etc., contained in the service information stored in the service information storage unit 44 (step 352). Specifically, the service information management unit 45 extracts the service content, etc., from the service information storage unit 44 using the service provider ID and service ID contained in the service content viewing request received in step 351 as keys. The transmitting unit 46 then transmits the service content, etc., extracted in step 352 to the user terminal 10 (step 353). The transmitting unit 46 then advances the process to step 361 in FIG. 7-2.

On the other hand, if the receiving unit 41 does not determine that a service content viewing request has been received from the user terminal 10, it proceeds to step 361 in FIG. 7-2 without performing steps 352 and 353.

Next, as shown in FIG. 7-2, in the intermediary server 30, the receiving unit 41 determines whether a service usage request has been received from the user terminal 10 (step 361).

If the receiving unit 41 determines that a service use request has been received from the user terminal 10, the service information management unit 45 determines whether the service use request satisfies the user conditions (step 362). Specifically, the service information management unit 45 determines whether the user information linked to the user ID included in the service use request received in step 361 satisfies the user conditions stored in the service information storage unit 44. Note that if the user conditions are not stored in the service information storage unit 44, the service information management unit 45 may determine that the service use request satisfies the user conditions.

If it is determined that the service usage request satisfies the user conditions, the service information management unit 45 determines whether the total of the installment plan specifications requested for use so far by the service usage request will exceed the normal plan specifications (step 363). Specifically, the service information management unit 45 registers the user ID included in the service usage request received in step 361 to the installment plan specifications included in the service usage request received in step 361, thereby determining whether the total of the installment plan specifications for which the user ID is registered will exceed the normal plan specifications.

If it is determined that the total of the installment plan specifications requested for use up to this point will not exceed the normal plan specification, the service information management unit 45 registers the user ID in the installment plan specification (step 364). Specifically, the service information management unit 45 registers the user ID included in the service usage request received in step 361 to the installment plan specification included in the service usage request received in step 361.

When the user ID is registered in the installment plan spec in this way, the service information management unit 45 determines whether a regular plan spec can be constructed using the installment plan spec in which the user ID is registered (step 365). Specifically, the service information management unit 45 determines whether the sum of the installment plan specs in which the user ID is registered is equal to the regular plan spec. Alternatively, it may determine whether the sum of the installment plan specs in which the user ID is registered is equal to or greater than a certain percentage of the regular plan spec.

If it is determined that a normal plan specification can be configured using the installment plan specification in which the user ID is registered, the service information management unit 45 extracts the user ID and the desired plan from the service information storage unit 44 (step 366). Specifically, the service information management unit 45 extracts from the service information storage unit 44 a plurality of installment plan specifications corresponding to the service provider ID and service ID included in the service usage request received in step 361. Next, the service information management unit 45 extracts the user ID registered in one of the extracted plurality of installment plan specifications. Next, the service information management unit 45 extracts the installment plan specification in which the extracted user ID is registered as the desired plan desired by the user of this user ID.

As a result, the transmission unit 46 transmits the user ID and desired plan extracted in step 366 to the service provider server 20 (step 367).

Next, in the intermediary server 30, the receiving unit 41 determines whether a service usage right has been received from the service provider server 20 (step 368). Here, it is expected that a service usage right corresponding to the total amount of the fees for the desired plan transmitted in step 367 will be transmitted from the service provider server 20, so the receiving unit 41 waits for this.

If the receiving unit 41 does not determine that the service usage right has been received from the service provider server 20, it repeats step 368.

On the other hand, if the receiving unit 41 determines that the service usage right has been received from the service provider server 20, the service usage right management unit 42 divides the service usage right (step 369). Specifically, the service usage right management unit 42 acquires the smallest installment plan specification among the multiple installment plan specifications stored in the service information storage unit 44 from the service information management unit 45. Then, the service usage right received in step 368 is divided into multiple split service usage rights of a size equivalent to this smallest installment plan specification. The multiple split service usage rights are linked to the service provider ID and the service ID and stored in the service usage right storage unit 43.

Next, the service usage right management unit 42 extracts split service usage rights from the service usage right storage unit 43 (step 370). Specifically, the service usage right management unit 42 focuses on multiple split service usage rights stored in association with the service provider ID and service ID included in the service usage request received in step 361. Next, the service usage right management unit 42 extracts an amount of split service usage rights equivalent to the desired plan extracted in step 366, in association with the user ID extracted in step 366.

As a result, the transmission unit 46 transmits the split service usage right extracted in step 370 to the user terminal 10 corresponding to the user ID with which the split service usage right is associated (step 371).

On the other hand, if the receiving unit 41 does not determine in step 361 that a service usage request has been received from the user terminal 10, the receiving unit 41 ends the processing without performing steps 362 to 371.

If it is not determined in step 362 that the service usage request satisfies the user conditions, the service information management unit 45 ends the process without performing steps 364 to 371. In this case, in response to an instruction from the service information management unit 45, the transmission unit 46 may suggest to the user of the user ID that the user information linked to the user ID satisfies the user conditions for the use of another service.

Furthermore, if it is determined in step 363 that the total of the installment plan specifications requested for use up to this point will exceed the normal plan specifications, the service information management unit 45 also ends the process without performing steps 364 to 371. In this case, the service information management unit 45 may discard the user ID that was not registered in step 364, or may retain it for registration in the installment plan specifications to be prepared later.

Furthermore, if it is not determined in step 365 that a normal plan specification can be configured based on the installment plan specification in which the user ID is registered, the service information management unit 45 ends the process without performing steps 366 to 371. In this case, the service information management unit 45 may temporarily reserve or delete the user ID for which it was not determined in step 315 that a normal plan specification can be configured.

[Modification]
In the above embodiment, a plurality of users who receive services from one service provider are mainly bundled together, but as shown in Fig. 1 with a plurality of service provider servers 20, a plurality of users who receive services from a plurality of service providers may be bundled together. In this case, the above embodiment is also applicable to bundling a plurality of users who receive services from each of the plurality of service providers. In this case, the plurality of service providers is an example of a plurality of businesses, and one service provider in the above embodiment is an example of one of the plurality of businesses.

In this case, the intermediary server 30 may be provided with a means for aggregating the user's usage status and a means for promoting use of an appropriate service from among the services provided by multiple service providers based on the user's usage status. Here, the services used and their frequency may be used as the user's usage status.

[Effects of this embodiment]
As described above, in this embodiment, the intermediary server 30 identifies a group of users who wish to receive services in a unit different from the normal unit in which the service provider provides the service, and notifies the service provider of information indicating the identified users and the unit desired by each user. This allows the user to receive products or services from the service provider in the amount required by that user.

1...service providing system, 10...user terminal, 20...service provider server, 30...intermediary server, 41...receiving unit, 42...service usage right management unit, 43...service usage right storage unit, 44...service information storage unit, 45...service information management unit, 46...transmitting unit

Claims (5)

A means for identifying a plurality of users who wish to receive a product or service from a specific business operator in a unit different from a normal unit in which the specific business operator provides the product or service;
a notification means for notifying the specific business entity of information indicating the plurality of users identified by the identification means and the different units desired by each of the plurality of users;
a receiving means for receiving the right to receive the product or service from the specific business entity;
a transmission means for transmitting the rights received by the receiving means to the plurality of users. 2. The information processing apparatus according to claim 1 , wherein said receiving means receives said right from said specific business operator before said identifying means identifies said plurality of users. 2 . The information processing apparatus according to claim 1 , wherein the receiving means receives the right from the specified business operator after the specifying means specifies the plurality of users. A step of identifying a plurality of users, which is a group of users who wish to receive a product or service from a specific business operator in a unit different from a normal unit in which the specific business operator provides the product or service, by the computer;
a step of notifying the specific business entity of information indicating the identified plurality of users and the different units desired by each of the identified plurality of users ;
A step in which a computer receives a right to receive the provision of the product or the service from the specific business operator;
a computer transmitting the received rights to the plurality of users;
13. An information processing method comprising: On the computer,
A function for identifying a plurality of users who wish to receive a product or service from a specific business operator in a unit different from the normal unit in which the specific business operator provides the product or service;
a function of notifying the specific business entity of information indicating the different units desired by the identified plurality of users and each of the plurality of users ;
A function of receiving a right to receive the provision of the product or the service from the specific business operator;
transmitting the received rights to the plurality of users;
A program to achieve this.