US20050278369A1 - Information processing system, information processing apparatus, method and program - Google Patents

Abstract

The present invention relates to an information processing system, an information processing apparatus and method, and a program in which the purchase of content can be facilitated. When giving content data as a present, a sender giving the content data sends first information for identifying the sender, second information for identifying the destination of the present, and third information for determining the content data to be given. Then, mail querying whether to accept the content data as a present is delivered to the destination of the present based on the second information. Then, only when a response indicating that the content data is to be accepted as a present is returned in response to the mail, the processing concerning the present is executed. The present invention is applicable to a server for executing processing concerning content data.

Description

TECHNICAL FIELD
• The present invention relates to information processing systems, information processing apparatuses and methods, and programs. The invention relates to an information processing system, an information processing apparatus and method, and a program, which are suitable for purchasing content data.
BACKGROUND ART
• Due to the recent widespread use of networks, such as the Internet, the purchasing of various goods (or following certain procedures for purchase) on networks is becoming common. There are various goods that can be purchased on a network, for example, not only tangible goods but also intangible goods. Intangible goods include, for example, music data and video data.
• Some intangible goods can be obtained not only by being purchased, but also by being rented. Regardless of whether the user purchases or rents intangible goods, he/she can purchase desired content data, such as music data or video data, by using a computer at home without the need to go to music stores or rental stores for compact discs storing content data.
• Unlike tangible goods, the intangible goods can be easily copied, and undesirable actions may occur, for example, copies of the intangible goods may be delivered from one purchaser to other persons. Generally, a mechanism for preventing such undesirable actions is contained in intangible goods.
• For example, data concerning licenses (usage rights) is provided (sent) together with content data. By using such license data, the playback operation of content data provided to the user is managed, thereby preventing undesirable actions, such as copying.
• When the user wishes to purchase content data via a network, he/she first accesses a site handling the content data via the network, and performs processing for purchasing the content data, such as inputting predetermined information, according to instructions from the site.
• After completing the processing for purchasing the content data, the content data is downloaded from the site to a user device via the network. The downloaded content data is stored in a recording medium, such as a hard disk drive, in the device, together with license data.
• After being downloaded to the user device, the license data is associated (bound) with ID information unique to the device storing the content data. Because of this association, even if the content data is copied, it can be prevented from being played back in a device other than the device which has downloaded the content data, i.e. a device that cannot associate its ID information with the license data.
• In this manner, content data is downloaded to a device in which purchase processing was performed and is played back by this device. Accordingly, when the user purchases content data by using a device other than a device at home when he/she is away, he/she cannot play back the purchased content data by using the device at home.
• In other words, the user cannot perform processing for storing desired content data in the device at home by using a different device when, for example, the user is away from home. Accordingly, the user cannot purchase content data by using a device different from the device used for playing back the content data.
• This indicates that it is not possible to play back in a device other than a device for purchasing content (license data). For example, it is suggested that a user A cannot give content data (license data) to a user B as a present. In other words, a person paying a fee for purchasing content data and a person obtaining the purchased content data should be the same person.
DISCLOSURE OF INVENTION
• In view of the above background, it is an object of the present invention to enable a user to perform processing for purchasing content data by using a device different from a device to play back the content data and to give the content data to another user as a present.
• A first information processing apparatus of an information processing system of the present invention includes: first management means for managing a first ID for identifying the content; second management means for managing a second ID for identifying the second information processing apparatus and a third ID for identifying the third information processing apparatus; supply means for supplying the first ID managed by the first management means to the second information processing apparatus in response to a request to distribute the content from the second information processing apparatus; specifying means for specifying, when receiving the first ID, information for specifying the second ID, and information for specifying the third ID from the second information processing apparatus, the second ID and the third ID managed by the second management means from the received information; distribution means for distributing the content identified by the first ID to the third information processing apparatus corresponding to the third ID specified by the specifying means. A second information processing apparatus includes: request means for requesting the first information processing apparatus to distribute the content; and sending means for sending the first ID corresponding to the content selected by a user from the first ID supplied from the supply means and for sending information for specifying the second ID and information for specifying the third ID in response to the request from the request means. A third information processing apparatus includes storage means for receiving and storing the content distributed by the distribution means.
• An information processing apparatus of the present invention includes: first management means for managing a first ID for identifying a first apparatus; second management means for managing a second ID for identifying a second apparatus; third management means for managing a third ID for identifying content; supply means for supplying the third ID managed by the third management means to the first apparatus in response to a request to distribute the content from the first apparatus; specifying means for specifying, when receiving information for specifying the first ID, information for specifying the second ID, and the third ID from the first apparatus, the first ID managed by the first management means and the second ID managed by the second management means from the received information; and distribution means for distributing the content identified by the third ID to the second apparatus corresponding to the second ID specified by the specifying means.
• The information processing apparatus may further include billing means for billing the content distributed by the distribution means to a user of the first apparatus identified by the first ID specified by the specifying means.
• The information processing apparatus may further include: query means for querying, after the second ID is specified by the specifying means, a user of the second apparatus identified by the second ID as to whether to accept the distribution of the content; and scheduling means for forming, when receiving a response indicating that the distribution of the content is to be accepted from the user of the second apparatus in response to the query made by the query means, a schedule for distributing the content identified by the third ID to the second apparatus corresponding to the second ID specified by the specify means. The distribution means may distribute the content based on the schedule formed by the scheduling means.
• When the user of the first apparatus or the user of the second apparatus designates a time to distribute the content, the scheduling means may form a schedule for distributing the content at the designated time.
• The information processing apparatus may further include providing means for providing, when the schedule for the second apparatus is formed by the scheduling means, the schedule to the second apparatus in response to a request to provide the schedule from the second apparatus.
• The first management means and the second management means may manage the same table in which IDs including the first ID and the second ID, user IDs for identifying the users, and passwords, and mail addresses are associated with each other. The specifying means may use information indicating at least one of the user ID and the password as the information for specifying the first ID, and may use the mail address as the information for specifying the second ID.
• An information processing method of the present invention includes: a first management step of managing a first ID for identifying a first apparatus; a second management step of managing a second ID for identifying a second apparatus; a third management step of managing a third ID for identifying content; a supply step of supplying the third ID managed by processing of the third management step to the first apparatus in response to a request to distribute the content from the first apparatus; a specifying step of specifying, when receiving information for specifying the first ID, information for specifying the second ID, and the third ID from the first apparatus, the first ID managed by processing of the first management step and the second ID managed by processing of the second management step from the received information; and a distribution control step of controlling the distribution of the content identified by the third ID to the second apparatus corresponding to the second ID specified by processing of the specifying step.
• A program in a recording medium of the present invention includes: a first management step of managing a first ID for identifying a first apparatus; a second management step of managing a second ID for identifying a second apparatus; a third management step of managing a third ID for identifying content; a supply step of supplying the third ID managed by processing of the third management step to the first apparatus in response to a request to distribute the content from the first apparatus; a specifying step of specifying, when receiving information for specifying the first ID, information for specifying the second ID, and the third ID from the first apparatus, the first ID managed by processing of the first management step and the second ID managed by processing of the second management step from the received information; and a distribution control step of controlling the distribution of the content identified by the third ID to the second apparatus corresponding to the second ID specified by processing of the specifying step.
• A program of the present invention allows a computer to execute: a first management step of managing a first ID for identifying a first apparatus; a second management step of managing a second ID for identifying a second apparatus; a third management step of managing a third ID for identifying content; a supply step of supplying the third ID managed by processing of the third management step to the first apparatus in response to a request to distribute the content from the first apparatus; a specifying step of specifying, when receiving information for specifying the first ID, information for specifying the second ID, and the third ID from the first apparatus, the first ID managed by processing of the first management step and the second ID managed by processing of the second management step from the received information; and a distribution control step of controlling the distribution of the content identified by the third ID to the second apparatus corresponding to the second ID specified by processing of the specifying step.
• In the present invention, the ID for determining a device to which content data is distributed is managed, and the ID for identifying content is managed. When there is a request to distribute content from the first apparatus, the ID for identifying the managed content is supplied to the first apparatus. When receiving information from the first apparatus, the device to which the content data is distributed and the device to which a fee for the purchase of the content data is billed are determined from the received information.
BRIEF DESCRIPTION OF THE DRAWINGS
• FIG. 1 is a diagram illustrating the configuration of an embodiment of an information processing system to which the present invention is applied.
• FIG. 2 is a block diagram illustrating an example of the configuration of a service provider.
• FIG. 3 is a block diagram illustrating an example of the configuration of an STB.
• FIG. 4 is a block diagram illustrating an example of the configuration of a PC.
• FIG. 5 is a diagram illustrating an example of the external configuration of a cellular telephone.
• FIG. 6 is a diagram illustrating an example of the internal configuration of the cellular telephone.
• FIG. 7 is a block diagram illustrating the functions of the service provider.
• FIG. 8 is a block diagram illustrating the functions of the STB.
• FIG. 9 is a flowchart illustrating processing for registering a device.
• FIG. 10 illustrates an example of the screen displayed on a television receiver.
• FIG. 11 illustrates the data configuration of a destination table.
• FIG. 12 is a flowchart illustrating another processing for registering a device.
• FIG. 13 illustrates an example of the screen displayed on a display unit.
• FIG. 14 illustrates another configuration of the destination table.
• FIG. 15 is a flowchart illustrating processing for changing registered information.
• FIG. 16 illustrates an example of the screen displayed on a display unit.
• FIG. 17 illustrates an example of the screen displayed on a display unit.
• FIG. 18 illustrates another configuration of the destination table.
• FIG. 19 is a flowchart illustrating purchase processing.
• FIG. 20 illustrates data stored in a content database.
• FIG. 21 illustrates data stored in a license issuer.
• FIG. 22 illustrates schedule data.
• FIG. 23 is a flowchart illustrating another purchase processing.
• FIG. 24 is a flowchart illustrating processing performed by the service provider.
• FIG. 25 illustrates an example of the screen displayed on a display unit.
• FIG. 26 illustrates an example of the screen displayed on a display unit.
• FIG. 27 is a flowchart illustrating processing performed by the service provider.
• FIG. 28 is a flowchart illustrating processing performed by the STB.
• FIG. 29 is a flowchart illustrating processing performed by the service provider.
• FIG. 30 is a flowchart illustrating present processing.
• FIG. 31 illustrates an example of the screen displayed on a display unit.
• FIG. 32 illustrates an example of the screen displayed on a display unit.
• FIG. 33 illustrates an example of the screen displayed on a display unit.
• FIG. 34 illustrates a distribution reservation table for reserving schedules.
• FIG. 35 is a flowchart illustrating scheduling.
• FIG. 36 is a flowchart illustrating processing performed by the service provider.
BEST MODE FOR CARRYING OUT THE INVENTION
• An embodiment of the present invention is described below with reference to the accompanying drawings.FIG. 1 is a schematic diagram illustrating an embodiment of an information processing system integrating an information processing apparatus to which the present invention is applied. Anetwork1 is a network formed of the Internet or a LAN (Local Area Network). Aservice provider2 is connected to thenetwork1.
• In this embodiment, theservice provider2 is a provider for offering services for providing content data to user devices.
• A user A owns a STB (Set Top Box)11, a PC (Personal Computer)12, and acellular telephone13 as devices which can be connected to thenetwork1. Similarly, a user B owns aSTB21, aPC22, and acellular telephone23 as devices which can be connected to thenetwork1. TheSTBs11 and21 and thePCs12 and22 can be connected to thenetwork1 while they are installed in the user A's home and the user B's home, respectively. Thecellular telephones13 and23 can be connected to thenetwork1 even when they are in a place away from the user A's home and the user B's home.
• The basic configuration and functions of theSTB11 owned by the user A are similar to those of theSTB21 owned by the user B. The same applies to thePC12 and thePC22 owned by the user A and the user B, respectively, and thecellular telephone13 and thecellular telephone23 owned by the user A and the user B, respectively. For giving a description of these devices in the following specification, theSTB11, thePC12, and thecellular telephone13 are discussed by way of example, and a description of theSTB21, thePC22, and thecellular telephone23 is omitted, assuming that the same explanation applies to them, unless otherwise stated.
• FIG. 2 is a block diagram illustrating an example of the configuration of theservice provider2. Theservice provider2 is formed of, for example, a computer. A CPU (Central Processing Unit)41 of theservice provider2 executes various types of processing according to a program stored in a ROM (Read Only Memory)42. In a RAM (Random Access Memory)43, data and programs required for executing various types of processing by theCPU41 are stored. Aninput unit46 formed of, for example, a keyboard and a mouse, is connected to an input/output interface45, and outputs a signal input into theinput unit46 to theCPU41. Anoutput unit47 formed of, for example, a display and a speaker, is also connected to the input/output interface45.
• Astorage unit48 formed of, for example, a hard disk, and acommunication unit49 for sending and receiving data to and from another device (for example, the STB11) via thenetwork1, such as the Internet, are also connected to the input/output interface45. Adrive50 is used for reading and writing data from and into recording media, such as amagnetic disk61, anoptical disc62, a magneto-optical disk63, and asemiconductor memory64.
• FIG. 3 illustrates an example of the internal configuration of theSTB11. ACPU81 expands a control program stored in aROM82 into aRAM83 so as to control the entire operation of theSTB11 based on an instruction from a user supplied from aninfrared receiver84.
• For example, in response to an instruction from the user to display an EPG (Electronic Program Guide) on a monitor (not shown) connected to theSTB11, theCPU81 executes processing for displaying an image on the monitor based on EPG data supplied from ademultiplexer87.
• Theinfrared receiver84 receives infrared emitted from a remote controller (not shown) for theSTB11 and outputs a command corresponding to the user's instruction to theCPU81.
• Astorage unit85 stores information concerning programs for which record reservations or viewing reservations are made or information concerning an ID supplied from another device (in this case, the service provider2). Based on an instruction from theCPU81, acommunication unit86 extracts a predetermined channel signal, performs analog-to-digital conversion, QPSK (Quadrature Phase Shift Keying) demodulation, and error correction, and outputs a obtained transport stream to thedemultiplexer87 at the stage subsequent to thecommunication unit86.
• Thecommunication unit86 sends and receives data to and from theservice provider2 via thenetwork1 and also performs processing on the sending data and the received data.
• Thedemultiplexer87 temporarily stores a supplied transport stream in abuffer memory88, and descrambles the transport stream by using a descramble key supplied from an IC card (not shown). Thedemultiplexer87 then extracts packets forming video data of a program specified by theCPU81 from the descrambled data based on the identifiers, and outputs the extracted packets to avideo decoder89. Thedemultiplexer87 also extracts packets in which audio data of the program is stored, and outputs the extracted packets to anaudio decoder90.
• Thevideo decoder89 plays back the supplied packets according to, for example, the MPEG (Moving Picture Experts Group)2 method, and supplies the played back video signal to a monitor (not shown) and displays it on the monitor. Theaudio decoder90 similarly plays back the supplied packets, and supplies the played back audio signal to a speaker (not shown) and outputs it from the speaker.
• FIG. 4 is a block diagram illustrating an example of the internal configuration of thePC12. ACPU101 of thePC12 executes various types of processing according to a program stored in aROM102. In aRAM103, data and programs required for executing various types of processing by theCPU101 are stored. Aninput unit106 formed of, for example, a keyboard and a mouse, is connected to an input/output interface105, and outputs a signal input into theinput unit106 to theCPU101. Anoutput unit107 formed of, for example, a display and a speaker, is also connected to the input/output interface105.
• Astorage unit108 formed of, for example, a hard disk, and acommunication unit109 for sending and receiving data to and from another device (for example, the service provider2) via thenetwork1, such as the Internet, are also connected to the input/output interface105. A drive120 is used for reading and writing data from and into a recording medium, for example, a magnetic disk.
• FIG. 5 illustrates an example of the external configuration of thecellular telephone13.FIG. 5 shows that thecellular telephone13 is divided into adisplay portion122 and amain portion123 across acenter hinge121, and can be folded at thehinge121.
• Atransceiver antenna124 is attached to the top left of thedisplay portion122 in the state in which it can be pulled out of and retracted into thedisplay portion122. Radio waves are transmitted and received via theantenna124 to and from a base station for controlling the connection with thenetwork1. Acamera unit125 rotatable in the angle range of about 180 degrees is disposed at the top center of thedisplay portion122, and a desired image subject can be captured by aCCD camera126 provided for thecamera unit125.
• When thecamera unit125 is rotated, theCCD camera126 disappears and a speaker (not shown) appears, and the user can listen to the voice on the telephone.
• Aliquid crystal display127 is provided at the front side of thedisplay portion122, and displays, not only the reception status of radio waves, the remaining capacity of batteries, the names and telephone numbers registered in the address book, and the calling history, but also email messages, simplified homepages, and images captured by theCCD camera126 of thecamera unit125.
• On the obverse surface of themain portion123,operation keys128, such as numeric keys from 0 to 9, a calling key, a redial key, a hang-up/power key, a clear key, and an email key, are provided, and various instructions can be input by using theoperation keys128.
• Amicrophone129 is provided for themain portion123, and user's voice on the telephone is collected by themicrophone129. Arotatable jog dial130 is disposed above theoperation keys128 such that it slightly projects from the surface of themain portion123. In accordance with the rotating operation on thejog dial130, various operations, for example, scrolling of the address book list and email messages displayed on theliquid crystal display127, page scrolling of simplified homepages, or forwarding of images, can be performed.
• A memorystick® slot131 for inserting a memory stick140 (produced by Sony Corporation) that can be inserted/removed is provided at the top of the left side of themain portion123. Email messages, simplified homepages, and images captured by theCCD camera126 can be recorded in response to the user's operation.
• Since thememory stick140 can be inserted into themain portion123, thecellular telephone13 can share data with other electronic devices via thememory stick140.
• In thecellular telephone13, as shown inFIG. 6, apower supply circuit161, anoperation input controller162, animage encoder163, acamera interface164, an LCD (Liquid Crystal Display)controller165, animage decoder166, ademultiplexer167, a recorder/player168, amodem circuit169, and anaudio codec170 are connected to amain controller160 for centrally controlling the elements of thedisplay portion122 and themain portion123 via amain bus171. Also, theimage encoder163, theimage decoder166, thedemultiplexer167, themodem circuit169, and theaudio codec170 are connected to each other via a synchronizingbus172.
• When the hang-up/power key is turned ON by the user's operation, thepower supply circuit161 supplies power from a battery pack to the individual elements, thereby starting thecellular telephone13.
• Under the control of themain controller160 formed of a CPU, a ROM, and a RAM, thecellular telephone13 converts an audio signal collected by themicrophone129 during the audio conversation mode into digital audio data by theaudio codec170, performs spread spectrum on the digital audio data by using themodem circuit169, performs digital-to-analog conversion and frequency conversion on the digital audio data by using atransceiver circuit173, and then sends the resulting data via theantenna124.
• Thecellular telephone13 also amplifies a signal received by theantenna124 during the audio conversation mode so as to perform frequency conversion and analog-to-digital conversion, performs de-spread spectrum by using themodem circuit169, and converts the digital signal into an analog audio signal by using theaudio codec170, and then outputs the analog audio signal via aspeaker174.
• When receiving data of a moving-picture file linked to a simplified homepage during the data communication mode, thecellular telephone13 performs de-spread spectrum on a signal received from a base station via theantenna124 by using themodem circuit169, and sends the resulting multiplexed data to thedemultiplexer167.
• Thedemultiplexer167 demultiplexes the multiplexed data so as to divide it into coded image data and coded audio data. Thedemultiplexer167 then supplies the coded image data to theimage decoder166 and also supplies the audio data to theaudio codec170 via the synchronizingbus172.
• Theimage decoder166 decodes the coded image data according to a decoding method corresponding to the predetermined coding method, such as MPEG (Moving Picture Experts Group)2 or MPEG4 so as to generate playback moving picture data, and supplies the decoded image data to theliquid crystal display127 via theLCD controller165. Accordingly, moving picture data contained in the moving picture file linked to a simplified homepage can be displayed.
• Simultaneously, theaudio codec170 converts the audio data into an analog audio signal and supplies it to thespeaker174. Accordingly, the audio data contained in the moving picture file linked to the simplified homepage can be played back.
• Thecellular telephone13 can record data linked to a received simplified homepage on thememory stick140 via the recorder/player168 in response to a user's operation.
• In the individual devices having the above-described configurations, the functions for implementing this embodiment are described below.FIG. 7 is a functional block diagram of theservice provider2 illustrating the functions required for executing the processing described below.
• A content-distribution reservation unit201 accepts reservations or purchases for the distribution of content from users. Acontent database202 stores data of the content itself (hereinafter sometimes referred to as “content data”) and data concerning the content data (hereinafter sometimes referred to as “content accompanying data”), for example, the size and the effective period of the content data, so that the content data and the content accompanying data can be associated with each other.
• Adestination database203 stores information concerning users (hereinafter sometimes referred to as “user information”) who have made contract for the purchase of the content data. Upon receiving a request to reserve or purchase content data from a user, the content-distribution reservation unit201 determines whether the request is to be accepted by referring to the content accompanying data stored in thecontent database202 and the user information stored in thedestination database203. If the content-distribution reservation unit201 determines that the request is to be accepted, it outputs predetermined information to ascheduler204.
• The content-distribution reservation unit201 manages data concerning a site (homepage that can be browsed on the network1) which accepts requests to reserve or purchase predetermined content from users, for example, the user A (FIG. 1), and provides such data to a user who has accessed the site. Then, the user can send a request to reserve or purchase content by checking the screen based on the data.
• Thescheduler204 forms a distribution schedule indicating, for example, when content data requested by the user is provided to the user. Based on this schedule, acontent distributor105 reads content data from thecontent database202 and sends it to a user device.
• Alicense issuer206 issues license data (usage right) for allowing the content data to be played back at the user side while preventing the unauthorized use of the content data, and adds the license data to the content data. Acommunication controller207 controls the sending and receiving of data in theservice provider2 via thenetwork1.
• The correlation between theservice provider2 shown inFIG. 2 and theservice provider2 shown inFIG. 7 is as follows. Thecontent data202 and thedistribution database203 are databases stored in thestorage unit48. The portion for storing the data concerning the site managed by the content-distribution reservation unit201 may be disposed in thestorage unit48.
• The content-distribution reservation unit201, thescheduler204, thecontent distributor205, and thelicense issuer206 are functions implemented by starting the corresponding programs stored in theROM42 or thestorage unit48 and by executing the processing by theCPU41 according to the programs. Accordingly, the programs or data are expanded and stored in theRAM43 if necessary.
• Thecommunication controller207 is a function for controlling the sending and receiving of data performed by thecommunication unit49.
• A description is now given of the functions of theSTB11 for sending and receiving data to and from theservice provider2 having the above-described functions.FIG. 8 is a functional block illustrating functions of theSTB11 required for sending and receiving data to and from theservice provider2 and for performing processing described below. Acommunication controller221 controls the sending and receiving of data to and from theservice provider2 via thenetwork1. The data controlled by thecommunication controller221 is supplied to adistribution controller222.
• Thedistribution controller222 controls the sending and receiving of content data or distribution schedule data to and from theservice provider2. Astorage unit223 stores content data supplied from thedistribution controller222. Alicense manager224 stores license data supplied from thedistribution controller222, and also manages the storage of content data in thestorage unit223 or the playback operation of content data in aplayback unit226 based on the stored license data.
• Adevice ID manager225 manages a device ID supplied from theservice provider2 as information for identifying theSTB11.
• The correlation between theSTB11 shown inFIG. 3 and theSTB11 shown inFIG. 8 is as follows. Thecommunication controller221 is a function of controlling the communication in thecommunication unit86. Thestorage unit223, the portion of thelicense manager224 for storing the license data, and the portion of thedevice ID manager225 for storing the device ID are disposed in thestorage unit85.
• Thedistribution controller222, thelicense manager224, and thedevice ID manager225 are functions implemented by starting the corresponding programs stored in theROM82 or thestorage unit85 and by executing processing by theCPU81 according to the programs. Accordingly, the programs or data are expanded and stored in theRAM83 if necessary.
• Theplayback unit226 is a function executed by the portions related to the playback operation, such as thedemultiplexer87, thevideo decoder89, and theaudio decoder90.
• The sending and receiving of data performed by theservice provider2 and theSTB11 is discussed below. To download content data by theSTB11 from theservice provider2, it is necessary that the STB11 (user A) has made contract with the service provider2 (or an agent managing the service provider2). A description is given below, assuming that a device ID for identifying theSTB11 is given from theservice provider2 by making contract with theservice provider2 and that theSTB11 is registered in theservice provider2 by receiving the device ID.
• A process for registering theSTB11 in theservice provider2 is discussed below with reference to the flowchart ofFIG. 9. In step S11, theSTB11 accesses theservice provider2. This access is made via thenetwork1 by performing a predetermined operation on theSTB11 by the user A.
• Upon receiving an access request from theSTB11 in step S21, theservice provider2 sends data concerning a registration form in step S22. Before sending the data concerning the registration form, a determination may be made as to whether theSTB11 which has accessed theservice provider2 has already been registered, and if so, the registration form data may not be sent to theSTB11. To describe the registration processing, it is now assumed that registration form data be sent.
• The processing of step S22 is performed in the content-distribution reservation unit201 (FIG. 7). That is, a request to access from theSTB11, in this case, a registration request, is supplied to the content-distribution reservation unit201 under the control of thecommunication controller207 of theservice provider2. The content-distribution reservation unit201 manages data concerning an initial screen which is always provided when receiving an access request or an initial screen specially used for registration, and sends the data as the registration form data.
• In step S12, the initial screen data sent from theservice provider2 is received by theSTB11. The initial screen data received under the control of thecommunication controller221 of theSTB11 is supplied to thedistribution controller222. When determining that the supplied (sent) data is the initial screen data, thedistribution controller222 supplies the data to theplayback unit226.
• Theplayback unit226 plays back the supplied data. As a result, a screen, such as that shown inFIG. 10, is displayed on the display of, for example, a television receiver, connected to theSTB11. The screen shown inFIG. 10 is the registration initial screen on which a userID input column251 for inputting a user ID, apassword input column252 for inputting a password, and a mailaddress input column253 for inputting a mail address are disposed.
• The user ID is an ID that can be freely assigned by the user, and is a character string having a predetermined number of digits, for example, alphabets, numbers, and kana characters. The password is also a character string having a predetermined number of digits that can be freely assigned by the user. The mail address may be an email address if theSTB11 has the function of sending and receiving email and is assigned with the corresponding email address.
• In order to execute the processing described below, however, it is preferable that a mail address assigned to a device other than theSTB11, for example, a mail address assigned to thePC12 or thecellular telephone13, be input into the mailaddress input column253. Accordingly, the item name above the mailaddress input column253 may be more specifically indicated, for example, “mail address of PC or cellular telephone” rather than “mail address” shown inFIG. 10.
• Although in this example the user ID, password, and mail address are input, information other than these items may be input solely or together with the above-described items of information. The information input into this screen is information that can uniquely identify theSTB11, and in this example, theSTB11 of the user A can be distinguished from other STBs (for example, the STB21 (FIG. 1)) by the user ID.
• Since the user ID can uniquely identify theSTB11, the mail address may be used as the user ID. That is, the mail address may be used for uniquely identifying theSTB11. If the mail address is used as the user ID, it is not necessary to provide both the userID input column251 and the mailaddress input column253 on the screen of atelevision receiver241 shown inFIG. 10, and one of the columns suffices.
• As stated above, the screen, such as that shown inFIG. 10, is displayed on thetelevision receiver241 at the user side, and the time when such a screen is displayed on thetelevision receiver241 may be determined as follows. An item “registration” is disposed on the initial screen provided by theservice provider2, and the screen shown inFIG. 10 may be displayed when the item “registration” is selected. In this case, basically, data concerning the screen is sent and received between theSTB11 and theservice provider2 in a manner similar to that described above.
• It is now assumed that the screen shown inFIG. 10 is displayed on the user television receiver24 and that the user inputs the user ID, password, and mail address.
• Referring back to the description of the flowchart ofFIG. 9, in step S13, the user inputs a desired character string into the screen shown inFIG. 10, and the data is then sent to theservice provider2. Upon receiving the data, such as the user ID, in step S23, theservice provider2 stores the user ID, password, and mail address based on the received data in step S24.
• The storage processing of step S24 is as follows. The data, such as the user ID, from theSTB11 is received by thecommunication controller207 of theservice provider2, and is supplied to the content-distribution reservation unit201. As discussed above, the content-distribution reservation unit201 performs registration processing as part of the processing.
• If the content-distribution reservation unit201 determines that the data supplied from thecommunication controller207 is from the STB11 (user) which has requested to conduct registration for the first time, it writes (stores) the data into thedestination database203.FIG. 11 illustrates an example of the data configuration in thedestination database203. In thedestination database203, as shown inFIG. 11, the device ID, user ID, password, and mail address are stored in association with each other. In this case, data, such as that shown inFIG. 11, stored in thedestination database203 is sometimes referred to as a “destination table”.
• The device ID is prestored in the destination table. In the destination table shown inFIG. 11,numbers 000001 through 999999 are indicated (prepared) as the device IDs in advance. Although in this example the device IDs are prestored in the destination table, they may be generated when registration is conducted.
• The user ID, password, and mail address received in step S23 are written into the corresponding portions of the destination table. It is assumed that “AIU” is received as the user ID, “XXXX” is received as the password, and “ΔΔΔ@z.co.jp” is received as the mail address, and are written into the device ID entry “000001”.
• After finishing writing (storing) data into thedestination database203 in step S24, the device ID is sent in step S25. The device ID sent from theservice provider2 in step S25 is the device ID corresponding to the entry into which the information has been written. That is, in this case, “000001” is read as the device ID and is sent to theSTB11.
• After finishing sending the device ID, theservice provider2 has completed the processing for registering theSTB11. Thus, in step S26, theservice provider2 reports to the user of theSTB11 that registration has completed.
• To report the completion of the registration, a simple message, for example, “registration has completed”, may be displayed on the screen of thetelevision receiver241 connected to theSTB11. Alternatively, another message or an image may be displayed.
• If, for example, the user ID to be registered is already stored in thedestination database203, a message instructing the user to change the user ID may be sent together with a message for reminding the user that registration is not completed before changing the user ID.
• The same user ID is not doubly stored in the destination table in order to uniquely identify theSTB11 by the user ID, as stated above. Accordingly, processing must be performed for avoiding the double storage of the same user ID.
• Meanwhile, theSTB11 receives the device ID in step S14, and then receives a completion message in step S15. In step S16, the device ID received in step S14 is stored in the device ID manager225 (FIG. 8) of theSTB11. Based on the completion message received in step S15, theSTB11 performs processing, for example, finishing registration or changing the user ID. If the user ID is changed, the device ID is stored in step S16 only when the changed user ID is accepted in theservice provider2.
• When inputting character strings into the columns on the screen shown inFIG. 10, a remote controller (not shown) for giving instructions to theSTB11 is used. Normally, however, the remote controller is not suitable for inputting characters. Additionally, theSTB11 may not have a function of inputting character strings.
• Accordingly, as stated above, instead of conducting registration by using theSTB11, another device suitable for inputting character strings may preferably be used for registering theSTB11 in theservice provider2. Then, the user can perform registration processing more easily. Accordingly, processing for registering theSTB11 in theservice provider2 by using thePC12 as an example of the device suitable for inputting characters is described below with reference to the flowchart ofFIG. 12.
• In step S41, theSTB11 accesses theservice provider2. In step S61, theservice provider2 receives an access request from theSTB11. The connection processing between theSTB11 and theservice provider2 is performed in a manner similar to the processing of steps S11 and S21 ofFIG. 9.
• In step S62, theservice provider2 sends a device ID and an alias ID to theSTB11. The device ID is an ID which is not provided to the user while remaining unknown to the user. In contrast, the alias ID is an ID which is provided and is known to the user.
• A description is given below, assuming that the device ID and the alias ID are supplied from theservice provider2. The device ID and the alias ID are prestored in theservice provider2 so that they can be associated with each other. Accordingly, the alias ID can uniquely determine the device ID.
• In step S62, the device ID and the alias ID are sent from theservice provider2 to theSTB11. Then, in step S42, theSTB11 receives the device ID and the alias ID under the control of thecommunication controller221, and supplies the device ID and the alias ID to thedistribution controller222. In step S43, thedistribution controller222 supplies the device ID and the alias ID to thedevice ID manager225 and thedevice ID manager225 manages (stores) them.
• After storing the device ID and the alias ID in thedevice ID manager225, in step S44, the stored alias ID is sent (provided) to thePC12. The provision of the alias ID to thePC12 may be performed directly or indirectly.
• A description is first given of the case where the alias ID is provided directly from theSTB11 to thePC12. When, for example, theSTB11 and thePC12 are connected via a home network, the alias ID is sent and received via this network. The sending and receiving of the alias ID can be performed, for example, when the alias ID is stored in theSTB11 or when thePC12 is started. Alternatively, as stated below, when thePC12 accesses (is connected to) theservice provider2, it may obtain the alias ID stored in theSTB11 via the home network.
• Alternatively, the alias ID may be sent from theSTB11 to thePC11 by email. In whichever manner, the alias ID is sent and received directly from theSTB11 to thePC12.
• A description is now given of the case where the alias ID is provided indirectly from theSTB11 to thePC12. For example, when the alias ID is stored in theSTB11, a message for informing the user that the alias ID is stored, and the stored alias ID are displayed on the screen of the television receiver24 connected to theSTB11. The user writes the alias ID displayed on the television receiver24 on a medium, for example, paper.
• The user then stores the alias ID written on the paper in the PC12 (inputs the alias ID into the predetermined column, as described below). The alias ID can be stored when, for example, thePC12 accesses (is connected to) theservice provider2.
• Methods for providing the alias ID from theSTB11 to thePC12 can be considered as described above. Thus, the timing of receiving the alias ID by thePC12 may be before or after step S52 shown inFIG. 12, and such a timing can be changed according to the provision method for the alias ID.
• Since thePC12 has been taken by way of example to perform the above-described processing, the above methods for providing the alias ID can be considered. If thecellular telephone13 performs the processing, an image of the alias ID may be captured by the CCD camera126 (FIG. 5) of thecellular telephone13, and the captured image of the alias ID is identified and stored by the processing of thecellular telephone13.
• In a device provided with an image capturing unit, such as theCCD camera126, code for providing information, i.e., so-called “two-dimensional barcode”, may be used for providing the alias ID to the user device.
• Regardless of the timing of providing the alias ID from theSTB11 to the PC12 (or cellular telephone13), thePC12 starts accessing theservice provider2 in step S52 after the alias ID is stored in theSTB11. As stated above, theservice provider2 manages a site that can be browsed on thenetwork1. The user operates thePC12 to browse the site.
• When thePC12 is ready to browse the site managed by theservice provider2, theservice provider2 sends registration form data to thePC12 in step S64. ThePC12 receives the registration form data in step S53. Then, the registration screen based on the received data is displayed on the display unit, which serves as theoutput unit107 of the PC12 (FIG. 4).
• FIG. 13 illustrates an example of the registration form displayed on adisplay unit261 of thePC12. In the configuration of the registration form displayed on thedisplay unit261 shown inFIG. 13, an aliasID input column254 for inputting the alias ID is added to the registration form displayed on thetelevision receiver241 shown inFIG. 10.
• The user operates the keyboard (not shown), which serves as theinput unit106 of thePC12, to input information (character strings) into the individual columns of the registration form shown inFIG. 13. If the alias ID of theSTB11 is already obtained, it may be automatically displayed in the aliasID input column254 without the need for the user to input it.
• Normally, thePC12 is provided with a keyboard, which is suitable for inputting character strings, as theinput unit106, and thus, thePC12 is more suitable for inputting character strings required for the registration form than theSTB11. Accordingly, it is advantageous and easy for the user to perform registration processing of theSTB11 in theservice provider2 by using thePC12, which is a different device from theSTB11.
• When various items of information are input into the predetermined columns of the registration screen shown inFIG. 13, in step S54, the information is sent to theservice provider2 from thePC12. Upon receiving the information from thePC12 in step S65, theservice provider2 stores the information in step S66. After the storage of the information, theservice provider2 reports to thePC12 in step S67 that the registration has completed.
• Upon receiving a registration completion report from theservice provider2, thePC12 performs corresponding processing in step S55; for example, it displays a message for informing the user that the registration processing has completed on thedisplay unit261.
• A description has been given, assuming that the processing between theSTB11, thePC12, and theservice provider2 shown inFIG. 12 is performed only once. However, it may be repeated a plurality of times, in which case, user IDs and passwords that are different among family members can be registered in one terminal. In other words, a plurality of users can be registered in theSTB11.
• The registration of a plurality of users in a single device can be implemented by repeatedly performing the processing between theSTB11, thePC12, and theservice provider2 shown inFIG. 12. In this case, the processing may be repeated continuously, and or it may be performed at time intervals. As described below, however, if the alias ID is deleted (changed), the processing must be performed before changing the alias ID. However, if the alias ID is not changed, or if the user registration can be conducted by information other than the alias ID, the above-described restriction can be eliminated.
• Referring back to the description of the flowchart ofFIG. 12, the storage processing in step S66 and the registration completion report in step S67 performed by theservice provider2 are basically similar to steps S24 and S26, respectively, ofFIG. 9, and step S67 executed by thePC12 is basically similar to step S26 executed by theSTB11 inFIG. 9, and an explanation thereof is thus omitted.
• On the other hand, the storage processing conducted in step S66 by theservice provider2 is slightly different from that of step S24 inFIG. 9, and thus, the processing different from that of step S24 is explained below. The destination table of the destination database203 (FIG. 7) in theservice provider2 when the processing is performed according to the flowchart ofFIG. 12 is shown inFIG. 14.
• In the destination table of thedestination database203 shown inFIG. 14, a column into which the “alias ID” is written is added to the destination table shown inFIG. 11. As discussed above, the alias ID is associated with the device ID and thus uniquely determines the device ID. The alias ID is an ID that is provided to the user by being known to the user. Accordingly, in the destination table, the alias ID has been written in association with the device ID.
• Theservice provider2 manages a destination table, such as that shown inFIG. 14, and information sent to theSTB11 in the processing of step S62 (FIG. 12) is only the device ID and the corresponding alias ID in the destination table. That is, a set of the device ID and the alias ID are provided to theSTB11 before thePC12 accesses theservice provider2.
• In this state, theservice provider2 receives information, such as the user ID, password, mail address, and alias ID, from thePC12 of the user under the control of thecommunication controller207, and the received information is then supplied to the content-distribution reservation unit201.
• The content-distribution reservation unit201 reads the alias ID from the supplied information, and then, checks the destination table, which is managed by thedestination database203, to determine the entry of the destination table into which the read alias ID is written.
• The content-distribution reservation unit201 writes the supplied user ID, password, and mail address into the determined entry of the destination table. In this manner, the information of each user that has sent a request to register him/her is written into the corresponding entry of the destination table, such as that shown inFIG. 14.
• As discussed above, by providing an ID, i.e., the alias ID, registration processing can be performed by using a device (in this case, the PC12) other than a device (in this case, the STB11) that has sent a request to register it without the need to make sensitive information, i.e., the device ID, known to the user.
• Basically, the number of device IDs is limited. The flowchart ofFIG. 12 shows that, after the device ID is stored in theSTB11 in step S43, the user does not always register theSTB11 in theservice provider2 by using a device, for example, thePC12. In other words, the destination table may be left for a long period without having the user information written into the entry corresponding to the device ID assigned to theSTB11.
• This means that some device IDs may remain unused. Accordingly, the following function may be provided for theservice provider2. That is, if registration is not conducted within a predetermined period after the device ID is stored in theSTB11, such a device ID is allocated to another device. Then, the device IDs can be efficiently allocated.
• In this case, theservice provider2 first detects device IDs that remain unused for a predetermined period without conducting registration processing (without writing information, such as the user ID, into the corresponding entry even though a set of the device ID and the alias ID are provided). As a result of detection, theservice provider2 changes the alias IDs associated with the device IDs that have expired.
• In this manner, by changing the alias IDs, even if the user of theSTB11 storing the previous alias ID performs registration processing after the predetermined period, the registration is not accepted because the previous alias ID is different from the current alias ID. Also, by changing the alias ID, the changed alias ID can be provided to another STB, thereby achieving the effective use of the device IDs.
• After registering theSTB11 in theservice provider2 according to the flowchart ofFIG. 12, there are two items of information, i.e., the alias ID (information1) and the user ID (information2), as information for uniquely determining the device ID assigned to theSTB11. Accordingly, after registering theSTB11 in theservice provider2, the device ID may be determined by using eitherinformation1 orinformation2.
• By taking this into consideration, if the user ID asinformation2 determines the device ID, the alias ID asinformation1 does not have to be stored (managed) in the destination table (FIG. 14). Accordingly, alias IDs corresponding to user information, such as user IDs, which have already been written into the corresponding entries after conducting registration processing may be deleted. With this arrangement, the deleted alias IDs can be associated with other device IDs, thereby making it possible to reuse the alias IDs.
• Basically, many device IDs must be prepared for conducting contract with many users (devices). In order to avoid the use of the same ID, character strings having many number of digits are used. If the device IDs and alias IDs are associated with each other based on a one-to-one correspondence, the same number of alias IDs as that of the device IDs must be prepared, and character strings having the number of digits similar to that of the device IDs must be used.
• However, the alias ID is provided to the user, and the user himself/herself may have to input the corresponding character string. Considering that the user may have to input the alias ID, the small number of digits of the character string is preferable.
• As stated above, if the alias IDs can be reused, the number of alias IDs that should be prepared can be smaller than the number of device IDs (i.e., the device IDs and the alias IDs do not have to be associated based on one-to-one correspondence). Thus, the number of alias IDs can be reduced. If the number of alias IDs is small, the alias IDs can be allocated while avoiding the use of the same IDs even if the number of digits of the character strings forming the alias IDs is smaller.
• A further description of the alias IDs is given. It can be considered, for example, as shown inFIG. 1, that the user A owns a plurality of devices, such as theSTB11, thePC12, and thecellular telephone13, for receiving content data. That is, it can be considered that one user owns a plurality of devices for receiving content data. In this case, the user performs the above-described registration processing for each device.
• As a result, the user has to register the alias ID, user ID, password, and mail address for each device. When the device ID can be uniquely determined by the user ID, as described above, the same user ID cannot be registered even for the same user. Accordingly, when registering a plurality of devices, the user has to register them with a plurality of user IDs and also to memorize them. Even if the device ID is-uniquely determined by the alias ID, the user also has to memorize a plurality of alias IDs.
• This is not convenient for the user. Accordingly, to improve the ease of use, the following processing is performed. The following processing is not necessary if a condition, for example, that one user can register only one device in theservice provider2, is given.
• As discussed above, after a predetermined device is registered in theservice provider2, the alias ID assigned to the device does not have to be managed by theservice provider2. Accordingly, if the alias ID can be changed by the user side, the ease of use for the user can be enhanced.
• In this case, it is assumed that theSTB11 already stores the device ID and the alias ID and that thePC12 stores (obtains) the alias ID assigned to theSTB11. The process up to the storage (obtaining) processing is performed in a manner similar to the process between theSTB11 and theservice provider2 indicated by the flowchart ofFIG. 12, and an explanation thereof is thus omitted.
• The processing for registering theSTB11 in theservice provider2 by thePC12 is described below with reference to the flowchart ofFIG. 15. Steps S81 through S83 of thePC12 and steps S91 through S93 of theservice provider2 are similar to steps S52 through S54 and steps S63 through S65, respectively, of the flowchart ofFIG. 12, and an explanation thereof is thus omitted.
• Upon receiving the user ID, password, mail address, and also the alias ID assigned to theSTB11 from thePC12 in step S93, theservice provider2 conducts user authentication (password check) in step S94. In this case, such authentication is conducted since the user who has already been registered accesses theservice provider2 to change the alias ID into a terminal name.
• If it is determined in step S94 that the same user ID as the received user ID is stored in the destination table and that the password coincides with the stored password, i.e., if it is determined that user authentication has succeeded, the process proceeds to step S95 in which data concerning a changing form is read. The changing form is a form for changing the alias ID into a terminal name. The terminal name is a name assigned to the device that has been registered (in this case, the STB11) by the user.
• If it is determined in step S94 that the same user ID as the received user ID is not stored in the destination table, and that the password does not coincide with stored password, i.e., if it is determined that user authentication has failed, the process proceeds to step S96 in which data concerning a re-input form is read. The re-input form is a form for instructing the user to re-input the user ID and password by assuming that the user authentication has failed because the user ID or password has been wrongly input.
• In step S97, the read changing form or re-input form data is sent to thePC12. In step S84, the data is received by thePC12. ThePC12 displays a screen, such as that shown inFIG. 16 or17, on thedisplay unit261 as the screen based on the received data. The screen shown inFIG. 16 is for changing the alias ID based on the changing form data. The screen shown inFIG. 17 is for re-inputting information based on the re-input form data.
• On the changing screen shown inFIG. 16, acolumn281 for indicating the alias ID before being changed and acolumn282 for inputting a terminal name after being changed are provided. On the re-input screen shown inFIG. 17, columns for inputting the user ID and password are provided.
• As the alias ID indicated in thecolumn282 on the screen shown inFIG. 16, the alias ID received and stored in step S93 is attached to and sent together with the changing form data sent from theservice provider2 in step S97. With this arrangement, the screen with the input alias ID can be displayed on thedisplay unit261 of theuser PC12.
• The user inputs a desired name into thecolumn282 of the screen shown inFIG. 16. For example, in this case, since theSTB11 is to be registered in theservice provider2, the name “STB” is input into thecolumn282. Characters may be input into thecolumn282 so that the user can input a desired name. Alternatively, the user may select a desired name from a pull-down menu.
• The user inputs (selects) a desired terminal name on the screen, such as that shown inFIG. 16, or inputs other information if necessary, and then, the information is sent to theservice provider2 from thePC12 in step S84. In step S98, theservice provider2 then receives data concerning the above-described change from thePC12.
• If the user ID and password are re-input into the screen, such as that shown inFIG. 17, step S94 and the subsequent steps are repeated in theservice provider2.
• Theservice provider2 performs processing for changing the data in step S99, and stores the changed data in step S100. The changing and storage processing is performed by determining the corresponding entry in the destination table from the received alias ID before being changed and by writing the changed terminal name into the corresponding portion of the column into which the alias ID is written.
• In the above-described description, the alias ID is rewritten into the terminal name. However, the terminal name may be added while the alias ID remains being stored. In this case, the alias ID may be used in the processing described below.
• When storing the information after being changed in theservice provider2, theservice provider2 sends a completion report to thePC12 in step S101. The processing of step S101 and the corresponding processing of step S85 of thePC12 are similar to the processing of step S67 and the corresponding processing of step S55 of thePC12 inFIG. 12, and an explanation thereof is thus omitted.
• The destination table stored in thedestination database203 of theservice provider2 after performing the processing based on the flowchart ofFIG. 15 can be schematically shown inFIG. 18. In the example of the destination table shown inFIG. 18, the user having a user ID “AIU”, a password “XXXX”, and a mail address “ΔΔΔ@z.co.jp” has two devices, such as an “STB” and a “PC”. The device ID “000001” is allocated to the device “STB”, and the device ID “010021” is allocated to the device “PC”.
• The user having a user ID “KAKIKU”, a password “◯◯◯◯”, and a mail address “ΔXΔ@x.co.jp” has three devices, such as a “personal computer”, an “STB”, and a “cellular telephone”. The device ID “001234” is allocated to the device “personal computer”, the device ID “001235” is allocated to the device “STB”, and the device ID “001236” is allocated to the device “cellular telephone”.
• In this manner, a plurality of devices (terminal names) are associated with one user ID, and the device ID is associated with each device. By using such a destination table, a single user can receive (purchase) content data by using a desired device selected from a plurality of devices with the same user ID. A description is given below of the processing for purchasing content data by using the destination table shown inFIG. 18 by way of example.
• The processing for purchasing content data from theservice provider2 by a device storing the device ID therein is first discussed with reference to the flowchart ofFIG. 19. In this description, theSTB11 is taken as an example of the device storing the device ID, and theSTB11 purchases content data from theservice provider2.
• In step S121, theSTB11 starts accessing theservice provider2. The access is made in response to a user instruction. In step S131, theservice provider2 receives an access request from theSTB11.
• If theservice provider2 determines that the access request from theSTB11 is a request to purchase content data, in step S132, it sends information concerning content data to theSTB11 that has made the access request. The data sent in this step is content accompanying data stored in thecontent database202.FIG. 20 illustrates an example of the configuration of the content accompanying data stored in thecontent database202.
• The content accompanying data is information indicating the content ID, which is assigned to each item of content data, for uniquely determining the content data, the size of the content data, the fee for purchasing the content data, and details of the content provided by the content data.
• Upon receiving the data from theservice provider2 in step S122, theSTB11 displays a screen based on the received data on thetelevision receiver241 connected to theSTB11. The user checks the screen displayed on thetelevision receiver241 to determine content data to be purchased.
• When the user determines the content data to be purchased, the content ID assigned to the determined content data is sent to theservice provider2 together with the device ID. The device ID managed by thedevice ID manager225 of theSTB11 is read and is sent together with the content ID.
• In step S133, theservice provider2 receives the data from theSTB11. In step S134, theservice provider2 extracts the device ID contained in the received data. Theservice provider2 then determines based on the extracted device ID whether the device having the device ID is an authorized device for purchasing the requested content data by checking the data stored in thedestination database203 and the content accompanying data stored in thecontent database202.
• If it is determined in step S134 that the purchasing of the content data is permitted, the process proceeds to step S135. If it is determined in step S134 that the purchasing of the content data is not permitted, the process for purchasing content data shown inFIG. 19 is terminated. If it is determined in step S134 that the purchasing of the content data is not permitted, a message indicating that the purchasing of the content data is not permitted is preferably sent to the user.
• In step S135, the content data and the license data are sent to theSTB11 based on a schedule formed by thescheduler204. Although details are given below, thescheduler204 determines the timing of sending the content data to the user, and forms a schedule based on the determination result and controls the content data to be sent based on the schedule.
• When sending the content data, thescheduler204 instructs thelicense issuer206 to issue license data. The license data is data concerning usage conditions containing data for preventing unauthorized copying or playback operation, and is provided to the user together with the content data.
• Thelicense issuer206 stores a table containing data shown inFIG. 21, namely, the license ID, usage conditions identified by the license ID, and content ID subjected to the usage conditions associated with each other. The usage conditions include conditions, such as purchase, rental, one-time copy.
• One license ID is assigned to one usage condition, and a plurality of content IDs can be associated with one license ID. This makes it possible to apply the same usage condition to a plurality of items of content. One license ID may be associated with a plurality of usage conditions. That is, one license data may be generated by a combination of a plurality of usage conditions, and one license ID may be assigned to such license data.
• By using such data, thelicense issuer206 issues license data. The content accompanying data shown inFIG. 20 and the license data shown inFIG. 21 are examples only, and other data may be added and stored, and such added data may be used to perform processing described below.
• Thescheduler204 forms a schedule from the content accompanying data stored in thecontent database202 and the data stored in thelicense issuer206. One example of the schedule formed is shown inFIG. 22.
• Every time a request to send content data is made, a schedule corresponding to the request is formed. The transaction ID for identifying each schedule is disposed at the head of the schedule.
• The content ID for identifying the content requested by the user is read from the content database202 (FIG. 20) and is associated with the transaction ID. The license ID corresponding to the usage condition applied to the content requested by the user is read from thelicense issuer206 and is associated with the transaction ID. The destination ID is the device ID assigned to the device specified by the user as the destination of the content data, and is read from thedestination database203 if necessary.
• The billing user ID is the user ID to which a fee for purchasing the content data is charged. As the distribution time, the time specified by the user is basically set. If the user has not specified the time or if the content data cannot be sent at the time specified by the user, the time specified by theservice provider2 is set. In the distribution status, information concerning the distribution status, for example, “not yet distributed”, “now distributing”, or “distributed”, is written.
• The content data is sent based on such a schedule. In this case, if the request is made from theSTB11 and there is no request (necessity) to send the content data later, theservice provider2 can respond to this request immediately, and thus, the time at which the schedule was formed may be written into the distribution time in the schedule.
• Thecommunication controller207 sends the content data and the license data (usage conditions) to theSTB11 based on the schedule formed by thescheduler204.
• In step S124, theSTB11 receives the data from theservice provider2. In step S125, theSTB11 stores the received data. In this storage processing, the data received under the control of thecommunication controller221 is first supplied to thedistribution controller222. Thedistribution controller222 supplies the content data of the supplied data to thestorage unit223, and supplies the license data to thelicense manager224.
• Thestorage unit223 and thelicense manager224 store the supplied data therein. In this manner, the content data is purchased by theSTB11. Although a description of billing is not given, when the purchase processing is performed, billing processing is also performed by theservice provider2. Also in the following description, when the purchase processing for content data is performed, billing processing is also performed.
• A description is now given, with reference to the flowchart ofFIG. 23, of the processing when thePC12 purchases content data and theSTB11 stores the purchased content data. In this case, the device for purchasing the content data and the device for storing the purchased content data are different. The overall processing is schematically discussed first, and then, details of the processing in each device are given.
• Steps S151 through S153 of thePC12 are basically similar to steps S121 through S123 of theSTB11 ofFIG. 19, and steps S161 through S163 of theservice provider2 corresponding to steps S151 through S153 are basically similar to steps S131 and S132 of theservice provider2 ofFIG. 19, and an explanation thereof is thus omitted.
• In step S153, however, only the content ID for identifying the content data that the user has decided to purchase is sent from thePC12, and the device ID is not sent from thePC12. This is because the device ID is an ID assigned to and managed by theSTB11 and cannot be sent from thePC12.
• Upon receiving the data from thePC12 in step S163, theservice provider2 sends purchase form data to thePC12 in step S164. Since there is no device ID in the received data, theservice provider2 determines that a request to purchase content data has been sent from a device without a device ID. Theservice provider2 then sends purchase form data to request thePC12 to send information for the destination device of the purchased content data and for checking whether the user is an authorized user.
• Upon receiving the purchase form data in step S154, thePC12 displays a purchasing screen based on the data on thedisplay unit261. The user checks the screen to input required items, for example, the user ID and password. In step S155, the input user ID and password data are sent from thePC12 to theservice provider2.
• Upon receiving the data from thePC12 in step S165, theservice provider2 stores the received data and also performs scheduling based on the data in step S166. Although details are given below, password authentication or the checking of the destination device of content data is conducted when performing scheduling, such as that shown inFIG. 22. It is now assumed that such processing has completed and the process proceeds to step S167.
• In step S167, theservice provider2 performs content purchase processing, that is, theservice provider2 reports to the user that the request to purchase content has been accepted. Upon receiving such a report in step S156, theuser PC12 performs processing based on this report, for example, thePC12 displays a message such as “content purchase request has been accepted” on thedisplay unit261.
• Meanwhile, in step S181, theSTB11 queries theservice provider2 as to a schedule. TheSTB11 queries the service provider as to whether a schedule for the STB11 (schedule in which theSTB11 is specified as the destination of the content data) has been formed. Such a query is made, for example, every hour, from theSTB11 to theservice provider2. In this case, it is assumed that, as a result of performing the above-described processing, theSTB11 makes a query to theservice provider2 after a schedule for theSTB11 has been formed and that the query is received by theservice provider2 in step S168.
• If theservice provider2 determines that there is a schedule for theSTB11 in response to the query from theSTB11, it sends the schedule for theSTB11 in step S169. To make the above determination, theSTB11 sends the device ID when making a query, and theservice provider2 determines whether a schedule associated with the device ID has been formed (stored) by thescheduler204.
• The schedule sent from theservice provider2 in step S169 is received by theSTB11 in step S182. The received schedule contains information concerning the sending due time. When the due time reaches, theSTB11 requests theservice provider2 to send the content data. Upon receiving this request in step S170, theservice provider2 responds to the request and starts sending the content data in step S171.
• When the sending of the content data is started, theservice provider2 reports to thePC12 that the sending of the purchased content data to theSTB11 is started in step S172. When the sending of the content data to theSTB11 is finished (step S173), theservice provider2 reports to thePC12 that the sending of the content data is finished. The report from theservice provider2 to thePC12 is conducted by, for example, email.
• TheSTB11 stores the content data in step S185.
• As described above, the content purchasing processing is performed in thePC12, and the purchased content data is stored in theSTB11.
• Then, details of the processing of the flowchart inFIG. 23 are discussed for each device. For the processing of thePC12, thePC12 basically repeats processing for displaying the screen based on the data received from theservice provider2 and sending information input into the screen, and an explanation of such processing is thus omitted. If necessary, however, the processing of thePC12 is discussed together with the processing of theservice provider2.
• The processing for purchasing content (processing for communicating with the PC12) by theservice provider2 is described below with reference to the flowchart ofFIG. 24. In step S201, theservice provider2 determines whether access has been made from another device. Theservice provider2 repeats step S201 in the standby mode until it determines that access has been made from another device.
• If it is determined in step S201 that access has been made from another device, the process proceeds to step S202. In step S202, content accompanying data is read from thecontent database202 and is sent to the device that has made access. After sending the content accompanying data, theservice provider2 remains in the standby mode until the user decides desired content and receives the content ID of the decided content.
• The content accompanying data sent to another device (for example, PC12) from theservice provider2 contains he content IDs. At least the content ID of the content that the user has decided to purchase is sent to theservice provider2 and is received as a request to purchase content from the user. Theservice provider2 determines in step S203 whether such a content purchase request has been received from the user.
• Theservice provider2 remains in the standby mode until it determines that a content purchase request has been received, and when it is received, the process proceeds to step S204. In step S204, it is determined whether the device ID is contained in the received content purchase request.
• As stated above, when a purchase request is made from a device to receive the content data (device that has obtained and stored the device ID), such as theSTB11, the device ID is sent together with the content ID. However, when a purchase request is made from a device that does not receive the content data (device that has not obtained the device ID), such as thePC11 or thecellular telephone13, only the content ID is sent.
• Accordingly, in step S204, it is determined whether the received request (data) contains the device ID. As a result of this determination, it can also be determined whether the device that has sent a content purchase request has already been registered as the device that can receive the content data.
• The process may be modified that step S204 is omitted to always send a purchase form. This is to respond to a user's desire: when thePC12 has obtained and stored the device ID assigned to thePC12, the user performs processing for purchasing the content data by using thePC12 but wishes to store the purchased content data in theSTB11. Alternatively, processing for instructing the user to specify the destination of the purchased content data in another manner may be added.
• If it is determined in step S204 that the received data does not contain the device ID, the process proceeds to step S205 in which purchase form data is sent. The purchase form data is data for displaying a screen, such as that shown inFIG. 25, on a user device, for example, thedisplay unit261 of thePC12.
• On the screen based on the purchase form data, as shown inFIG. 25, a column for inputting a user ID and a column for inputting a password are provided. The reason for inputting the user ID and password is to specify the device ID by the user ID and to conduct user authentication by the password. If the alias ID is still stored in the destination table of theservice provider2, it may also be sent and received.
• When the user inputs the user ID and password by referring to the screen shown inFIG. 25, the information is sent to theservice provider2, and theservice provider2 receives information concerning the user ID and password in step S206. Theservice provider2 specifies the device ID from the received user ID in step S207.
• A destination table, such as that shown inFIG. 18, is stored in thedestination database203 of theservice provider2, and the device ID is specified by referring to this table. For example, if the received user ID is “AIU” and the password is “XXXX”, two device IDs “000001” and “010021” can be specified, as shown inFIG. 18.
• It is then determined in step S208 whether plural device IDs have been specified. Since two device IDs can be specified in the above-described situation, the result of step S208 becomes YES, and the process proceeds to step S209. In step S209, data concerning a destination determination form is sent. The destination determination form data is data for displaying the screen for instructing the user to select (determine) the device by and in which the content data is to be received and stored.
• The data indicating the destination determination form includes at least the terminal names (FIG. 18) corresponding to the device IDs specified in step S207.FIG. 26 is an example of the screen displayed on a device in which purchase processing is currently performed, for example, on thedisplay unit261 of thePC12. If the processing is performed based on the destination table shown inFIG. 18, the terminal names “STB” and “PC” corresponding to the device IDs “000001” and “010021” are displayed on the screen shown inFIG. 26. Radio buttons for selecting the terminal names are provided before the terminal names.
• In this manner, if the user who has sent a content purchase request had registered a plurality of devices as the devices for receiving the content data, the device for storing (downloading) the purchased content data can be selected with the terminal name assigned by the user. Information concerning the terminal name selected by referring to the screen shown inFIG. 26 is sent to theservice provider2.
• As the downloading device, only one device may be selected by the user, or a plurality of devices may be selected by the user. Such setting is made by theservice provider2 according to the billing processing.
• In step S210, theservice provider2 receives information concerning the terminal name selected as the downloading device. By receiving the terminal name information, theservice provider2 can specify the device ID of the device for receiving the purchased content data.
• In step S211, the received data is stored, and scheduling based on the data is conducted. Scheduling is to generate data for the requested content, such as that configured as shown inFIG. 22, by thescheduler204.
• Step S211 is always executed to perform scheduling even when it is determined in step S204 that the device ID is contained in the received request (data) or when it is determined in step S208 that the specified device ID is only one. In any case, when only one device ID of the device for receiving the content data is specified, scheduling is performed.
• When performing scheduling, information concerning the content distribution time must be obtained. Accordingly, for example, as shown inFIG. 26, a message “please input the time and date you wish to receive content” is displayed on the screen of thedisplay unit261 of the user, and a column for allowing the user to input a desired time may be provided under the message. When the time is input into this column, it can be set as the sending due time.
• In this case, if the user does not designate the distribution time, theservice provider2 can set the time and writes it. Alternatively, only theservice provider2 may be able to set the distribution time without allowing the user to specify the time.
• When performing scheduling, it is determined whether the user who has sent a request to purchase content data is an authorized user who can receive the services provided by theservice provider2, and only when the user is an authorized user, scheduling is performed. To determine whether the user is an authorized user, it is determined whether the received password is registered in the destination table in association with the user ID.
• After finishing performing scheduling, in step S212, it is reported to the user device that the purchase request has been accepted. The purchase processing in theservice provider2 has completed.
• A description is now given, with reference to the flowchart ofFIG. 27, of processing (processing with theSTB11 in the above description) for sending content data by theservice provider2. In step S231, theservice provider2 determines whether there is a query concerning schedules or a request to send content data.
• Theservice provider2 remains in the standby mode until it determines in step S231 that there is a query or request from another device. When it is determined that there is a query or request from another device, the process proceeds to step S232. It is determined in step S232 whether the query or request from another device is about schedules. If it is determined in step S232 that the query is about schedules, the process proceeds to step S233.
• It is determined in step S233 whether a schedule corresponding to the device ID of the device that has queried about schedules has been formed and stored by thescheduler204. Another device (for example, the STB11) queries theservice provider2 as to the schedules at regular intervals, and when making a query, the device sends the device ID.
• Accordingly, theservice provider2 determines by using the received device ID whether a schedule for the device ID is stored in thescheduler204. Thescheduler204 stores a plurality of schedules having a data structure, such as that shown inFIG. 22. Theservice provider2 checks the “destination device ID” in the data of the schedule to determine whether there is the “destination device ID” which coincides with the received device ID.
• If it is determined in step S233 that there is no schedule concerning the received device ID (device), the process returns to step S231, and step S231 and the subsequent steps are repeated. If it is determined in step S233 that there is a schedule concerning the received device ID, the process proceeds to step S234. In step S234, the corresponding schedule is read from thescheduler204 and is sent to the device that has made a query.
• The schedule read in step S234 should be a schedule whose “distribution status” (FIG. 22) indicates that the content data has not been sent. Even if the “distribution status” indicates that the content data has not been sent, the schedule itself may have already been sent. In this case, it is not necessary to send the same schedule again, and thus, such a schedule does not have to be read.
• To prevent the same schedule from being re-sent, a flag, for example, indicating whether the schedule has been sent, may be prepared, and this flag may be contained in the schedule shown inFIG. 22 as one item of data, or may be contained in the “distribution status”.
• Upon completing the sending of the schedule in step S234, the process returns to step S231, and step S231 and the subsequent steps are repeated.
• If it is determined in step S232 that the query or request from another device is not about schedules, i.e., that the query or request is about a request to send content data, the process proceeds to step S235. In step S235, the sending of the requested content data is started.
• When sending a request to send content data, the device (for example, the STB11) sends at least information concerning the transaction ID together with the request. By receiving the transaction ID, theservice provider2 can specify which schedule is to be executed among the schedules stored in thescheduler204.
• By specifying the schedule to be executed, the content ID of the content to be sent can be specified. The content data associated with the content ID is read from the content database (FIG. 7) and is sent.
• Upon starting sending the content data in step S235, it is reported to the predetermined device at the user side in step S236 that the sending of the content data is started. The predetermined device is a device to which the mail address (FIG. 18) registered in the destination table of theservice provider2 is assigned.
• It is determined in step S237 whether the whole content data has been sent, i.e., whether the sending has finished. Step S237 is repeated until it is determined that the sending of the content data has finished. When it is determined that the sending of the content data has finished, the process proceeds to step S238.
• When sending content data, license data is also sent. Content data cannot be played back without the license data. For example, when sending content data to the user device, it is encrypted, and data for decrypting the content data is contained in the license data. Accordingly, both the content data and license data must be sent to the user (STB11). The timing of sending the content data does not have to be the same as that of sending the license data. That is, the content data and license data may be sent simultaneously, or may be sent at different times (differently).
• For example, since the data amount of content data is relatively large, it may be sent at a time when transmission lines are not busy, for example, at night, and license data having a relatively small data amount may be sent before or after the time when the content data is sent and before the user views the content data.
• In step S238, the “distribution status” information in the data of the schedule shown inFIG. 18 is overwritten by the information indicating that the sending of the content data has finished. Instead of overwriting the information, the corresponding schedule may be deleted. The reason for overwriting the “distribution status” information by the information indicating that the sending of the content data has finished is to perform billing processing. Thus, when billing processing is finished, the corresponding schedule may be deleted.
• In step S239, it is reported that the sending of the content data has completed. This report processing may be performed in a manner similar to that of step S236.
• As described above, theservice provider2 controls the processing for sending content data. Steps S236 and S239 for report processing are not always necessary. Neither of the steps may be performed, or one of the steps may be executed.
• In response to the processing by theservice provider2, processing for receiving content data is described below with reference to the flowchart ofFIG. 28. This processing is discussed in the context of theSTB11.
• In step S251, theSTB11 determines whether it is time to query theservice provider2 as to schedules. It is set that theSTB11 makes a query at predetermined time intervals, for example, every hour.
• It is determined whether it is time to make a query after the lapse of the predetermined time interval. If it is determined in step S251 that it is time to make a query, the device ID is read from the device ID manager225 (FIG. 8) and is sent to theservice provider2 in step S252. When the device ID is sent, the above-described processing is performed in theservice provider2. When the schedule information is sent as a result of this processing, the schedule is received in step S253.
• The received schedule is stored in, for example, the distribution controller222 (FIG. 8). The schedule stored (sent) includes at least information concerning the transaction ID and the distribution time. In step S254, thedistribution controller222 checks the “distribution time” in the stored schedule to determine whether the distribution time has reached. That is, theSTB11 determines whether it is time to send a request to send content data.
• Step S254 is repeated until it is determined that it is time to send a request to send content data, and if it is determined that it is time to send a request to send content data, the process proceeds to step S255. In step S255, the transaction ID is read and is sent to theservice provider2.
• As a result of sending the transaction ID, the content data is sent from theservice provider2. In step S256, the content data is received by theSTB11 and is stored.
• As discussed above, theSTB11 stores content data for which the purchase processing has been performed by using another device.
• The device (in this case, the STB11) that receives content data can query theservice provider2 as to schedules or can send a request to send content data to theservice provider2. This is because theSTB11 is not always ready to receive schedules or content data.
• In other words, theSTB11 is not always powered ON, but it may be powered OFF. If schedules or content data is sent from theservice provider2 when theSTB11 is powered OFF, theSTB11 cannot receive or store the schedules or content data. By considering this, theSTB11 queries about the schedules or sends a request to send content data.
• If theSTB11 is always powered ON or if it has a function of receiving content data even when it is powered OFF, theservice provider2 may send a schedule to theSTB11 upon creating the schedule. The content data may also be sent from theservice provider2 when the distribution time has reached without the need for theSTB11 to send a request.
• Although in the above-described embodiment thePC12 performs purchase processing and the content data is downloaded to theSTB11, thecellular telephone13 may perform purchase processing, in which case, thecellular telephone13 performs purchase processing in a manner similar to thePC12.
• As described above, purchase processing can be performed in a predetermined device, and another device can store the purchased content data therein. This enables the user to download desired content data to a device at home by using another device when he/she is away. Accordingly, it becomes easier for the user to obtain desired content data.
• In the above-described embodiment, basically, the user who purchases content data and the user who enjoys the content data are the same user. In other words, the user paying a fee for the purchased content data (the user to be charged) and the user obtaining the content data are the same user. Also in other words, the device for performing processing for purchasing the content data and the device for storing the purchased content data are owned by the same user.
• A description is now given of the case where the user A (FIG. 1) performs processing for purchasing content data and the user B enjoys the content data purchased by the user A by using a device owned by the user B. In other words, the user A gives the content data (license data) to the user B as a present.
• As stated above, content data cannot be played back without the license data. For example, content data does not have to be provided via thenetwork1, and may be recorded on a recording medium, such as a CD (Compact Disc) or a DVD (Digital Versatile Disc), and is given as a present. In this case, license data may be provided via thenetwork1 to a device playing back such a recording medium. The following processing can also be applied to such a case.
• By considering the definition of license data, license data is not always necessary, for example, when content data is distributed free of charge, content data can be played back without license data.
• In this sense, there are some cases that license data be preferably given as a present. In the following description, it is indicated that content data is given as a present; however, it actually means that both the content data and license data are offered as a present and that only license data is given as a present.
• Processing for offering content data as a present is discussed below, assuming that the user A performs processing for purchasing content data as a present by using thePC12 and that the user B obtains (stores) the content data offered by the user A in the STB21 (FIG. 1). In other words, theservice provider2 bills the user A and distributes the content data to the user B.
• The overall processing flow (processing flow between thePC12, theservice provider2, and the STB21) is basically similar to that indicated by the flowchart shown inFIG. 23. In the flowchart ofFIG. 23, the processing performed by the PC is the processing performed by thePC12 of the user A, and the processing performed by the STB is the processing performed by theSTB21 of the user B.
• When performing processing concerning presents, theservice provider2 must perform the corresponding processing. Accordingly, a description is given below of the processing by theservice provider2. A description is first given of, with reference to the flowcharts ofFIGS. 29 and 30, content purchase processing including processing concerning presents by theservice provider2.
• In the flowchart ofFIG. 29, steps S307 and S308 are added to the flowchart ofFIG. 24. That is, steps S301 through S306 of the flowchart inFIG. 29 are basically similar to steps S201 through S206 of the flowchart inFIG. 24. Steps S309 through S314 of the flowchart inFIG. 29 are basically similar to steps S207 through S212 of the flowchart inFIG. 24.
• Accordingly, only an explanation of executing processing concerning presents is given by omitting a description of the processing by theservice provider2 discussed with reference to the flowchart ofFIG. 24. When executing present processing by theservice provider2, purchase form data sent in step S305 is different from that in the above-described embodiment.
• In the above-described embodiment, the screen based on the purchase form data is that shown inFIG. 25. When executing present processing, however, purchase form data displayed on a screen, such as that shown inFIG. 31, of the user device (in this case, thedisplay unit261 of thePC12 of the user A) is sent in step S305.
• On the screen shown inFIG. 31, a column for inputting the user ID, a column for inputting the password, and a radio button for checking when giving an affirmative answer in response to a message “Is it for present?” are provided. When the user wishes to give content data to be purchased to another user as a present, he/she checks the radio button corresponding to the message “Is it for present?”.FIG. 31 illustrates the state in which the radio button has been checked.
• When sending purchase form data for displaying such a screen on thedisplay unit261 of the user, theservice provider2 enters in the standby mode to wait for information input by the user by referring to the purchase form. Upon receiving the information filled in the purchase form in step S306, the process proceeds to step S307.
• The received information contains at least the user ID and password, and may contain information indicating that the content data to be purchased is for a present. The processing of step S307 is performed by using the information indicating whether the content data to be purchased is for a present.
• If it is determined in step S307 that the content data to be purchased is for a present (such information is contained), the process proceeds to step S308. If it is determined in step S307 that the content to be purchased is not for a present (such information is not contained), the process proceeds to step S309.
• When the process proceeds to step S309, that is, when the content data to be purchased is not for a present, the subsequent process is performed similarly to that shown inFIG. 24.
• When the process proceeds to step S308, present processing is performed. Before explaining the processing of step S308, the handling of the user ID and password of the information received in step S306 is discussed below.
• When the process proceeds to step S309, as discussed with reference to the flowchart ofFIG. 24, the user ID and password are used for specifying the device for receiving the purchased content data and for conducting user authentication. When the process proceeds to step S308, the user ID and password are used for specifying the user to be charged, which is described below.
• The present processing in step S308 is described below with reference to the flowchart ofFIG. 30. In step S321, data concerning a present form is sent. An example of the screen displayed on the user device, in this case, on thedisplay unit261 of thePC12 of the user A, by performing processing based on the present form data is shown inFIG. 32.
• On the screen shown inFIG. 32, a column for inputting the mail address of the user to receive the present and a column for inputting the time and date when the user wishes to deliver the present are provided. The reason for inputting the mail address of the user to receive the present is to specify the user (device) for receiving the content data as a present.
• The reason for inputting the time and date when the user wishes to deliver the present is to respond to a user's desire to supply the content data as a specific date, for example, a birthday. The input of the time and date for delivering the present is not essential, and even if the user does not input the time and date, the subsequent processing is performed.
• Although the mail address is used for specifying the user to deliver the present, another information may be used. A description has been given, assuming that the information shown inFIG. 18 is contained in the destination table, and among such items of information, the mail address seems to be most suitable for specifying the user to deliver the present. Thus, the mail address is used by way of example.
• When it is controlled that the same user ID is not present in the destination table, as in this embodiment, the user to receive the present can be uniquely determined by the user ID. Accordingly, the user ID can be used as the information for specifying the user to receive the present. In this case, in the screen shown inFIG. 32, instead of the mail address, the user ID of the user to receive the present can be input.
• If the user's real name, telephone number, and address are contained in the destination table (or another table in the service provider2), such information may be used for specifying the user to receive the present. Alternatively, the user can be specified by a combination of the above-described items of information.
• The information input by the user to give the content data as a present by referring to the screen shown inFIG. 32 is received by theservice provider2 in step S322. Theservice provider2 extracts the mail address contained in the information received in step S322. In step S323, it is determined whether the extracted mail address is stored (registered) in the destination table (for example, the destination table shown inFIG. 18).
• If it is determined in step S323 that the extracted mail address is registered in the destination table, the process proceeds to step S324. If it is determined that the extracted mail address is not registered, the present processing based on the flowchart ofFIG. 30 is terminated. If the extracted mail address is not registered in the destination table, the device (user) to receive the content data as a present cannot be specified. Thus, if it is determined that the mail address is not registered, present processing is terminated.
• If it is determined that the extracted mail address is not registered in the destination table, processing for instructing the user to re-input the mail address may be performed. If the present processing is terminated because the destination cannot be specified, a message indicating that the purchase processing has failed may be sent to the user device of the user who has sent a request to purchase the content data in step S314 (FIG. 29).
• If it is determined in step S323 that the extracted mail address is registered in the destination table, the process proceeds to step S324. In step S324, mail is sent to the extracted mail address. It is assumed that the extracted mail address is “ΔXΔ@x.co.jp”. The destination table shown inFIG. 18 shows that this mail address is the mail address of the user having a user ID “KAKIKU”.
• When the extracted mail address coincides with the mail address indicated in the destination table, the outcome of step S323 is YES, and the process proceeds to step S324. When the result of step S323 is determined to be YES, the information indicated in the same entry of the mail address is also read if necessary. In this case, at least information “personal computer”, “STB”, and “cellular telephone” indicated in the terminal name are read. The read information is contained in the mail and is sent.
• The content of the mail is as shown inFIG. 33. It is now assumed that the mail is received by thePC22 of the user B and the content (screen) shown inFIG. 33 is displayed on adisplay unit301 of thePC22.
• On the screen shown inFIG. 33, a message “You have content present from user A”. Do you wish to accept it?” is displayed. In the “user A” in this message, the user ID or the name of the user A registered before (which is managed as one item of information in the destination table in association with another item information) is displayed. When sending mail for displaying such a screen, theservice provider2 specifies the user who has offered the present from the user ID (or the password or the user ID and the password) of the user, and forms a mail message so that the character string indicating the specified user can be displayed in the “user A” in the above-described message.
• On the screen shown inFIG. 33, radio buttons for responding to the message “Do you wish to accept the present?” are provided; one is for “YES”, and the other one is for “NO”. When the radio button corresponding to “YES” is checked, radio buttons for responding to the message “Please select the device by which you wish to receive the present” becomes effective.
• In the example shown inFIG. 33, radio buttons for three terminal names “personal computer”, “STB”, and “cellular telephone” are provided. If the user to receive the present has registered only one device (terminal), only one terminal name is displayed in the portion in which the terminal name is indicated. If only one terminal name is displayed, the device corresponding to the terminal name has to be specified as the destination for the content data. That is, since there is no choice for the device, the terminal name does not have to be displayed or selected. Accordingly, if only one terminal name is to be displayed, it is not necessary to be displayed.
• The information input by the user to receive the present by referring to the screen shown inFIG. 33 is sent to theservice provider2. Theservice provider2 determines in step S325 whether information from the user to receive the present has been received. If it is determined that the information has been received, the process proceeds to step S326.
• In step S326, theservice provider2 extracts the user's response for the query “Do you wish to accept the present?” contained in the received information, and determines whether the extracted response is “YES”. That is, it is determined in step S326 whether the user to receive the present has decided to accept the present.
• If it is determined in step S326 that the user to receive the present has decided not to accept the present, the present processing does not have to be executed, and thus, the processing based on the flowchart inFIG. 30 is terminated. When the user to receive the present (in this case, the user B) has refused to accept the present, a message indicating such information may be sent to the user who has offered the present (in this case, the user A) by email.
• If it is determined in step S326 that the user to receive the present has decided to accept the present, the process proceeds to step S327. In step S327, a schedule is formed to distribute the content data to the destination as a present. The schedule to be formed is basically similar to that shown inFIG. 22.
• Details of the schedule formed in step S327 are given below with reference toFIG. 22, assuming that a present is given from the user A to the user B. In the “content ID”, the ID of the content specified by the user A as a present for the user B is indicated. In the “destination device ID”, the device ID corresponding to the device (terminal name) specified by the user B and received in step S325 is indicated.
• In the “billing user ID”, the user ID of the user A offering the present is indicated. In the “distribution time”, the time designated by the user A as the time to deliver the present to the user B is basically indicated. The reason for indicating “basically” is that there is a possibility of theservice provider2 writing (setting) a time other than the designated time in the subsequent scheduling processing.
• After creating such a schedule, the process proceeds to step S314 (FIG. 29). In step S314, it is reported that the purchase request has been accepted. When the present processing has been executed and the user to receive the present has decided to accept the present, the above-described report is sent to the user to receive the present and the user to offer the present.
• When the user to receive the present has decided not to accept the present after executing the present processing, it is reported to the user that the present processing has been terminated, and it is reported to the user to offer the present that the present has been refused.
• When the present processing is not executed, i.e., when it is determined in step S307 that the content data is not for a present, the subsequent processing is performed. In this case, processing similar to step S212 of the flowchart inFIG. 24 is performed.
• The purchase processing including the present processing has been performed by theservice provider2. A description is now given of the processing for distributing content data by theservice provider2. The processing for distributing content data by theservice provider2 is basically similar to that of the flowchart inFIG. 27, and an explanation thereof is thus omitted. In this case, however, the processing is performed between theservice provider2 and the user device to receive a present, for example, theSTB21.
• When the content data is distributed as a present, a distribution completion report in step S239 may preferably be given not only to the user who has received the present, but also to the user who has offered the present. By sending a report to the user who has offered the present, it is possible to inform the user that the present has been sent and the user is to be billed for it.
• The device to receive a present (in this case, for example, theSTB21 of the user B) performs the processing indicated by the flowchart ofFIG. 28. That is, regardless of whether the user B receives content data purchased by himself/herself or receives content data offered by the user A as a present, processing is similarly performed.
• Accordingly, in this embodiment, content data (license data) can be offered to another user as a present.
• Scheduling performed by theservice provider2 is described below. The scheduling is performed, for example, in step S313 (FIG. 29), when an instruction is given to purchase a new item of content.
• The situations in which scheduling is performed is checked. In one situation, the user A performs purchase processing by using a device owned by the user A, and stores content data in the same device used for purchase processing. In another situation, the user A performs purchase processing by using a device owned by the user A, and stores content data in a device different from the device used for purchase processing.
• In another situation, the user A performs purchase processing by using a device owned by the user A, and stores content data in a device owned by the user B different from the user A.
• In this manner, there are several relationships between the device for performing purchase processing and the device storing the purchased content data. The content data may be distributed at the time designated by the user or set by theservice provider2.
• The data amount of content data to be distributed is not uniform, and some data may be sent in a short time, and for other data, it takes a long time to send.
• By considering such various situations, the timing of sending content data must be determined. The processing for determining the timing of sending data is to perform scheduling.
• Before describing scheduling performed by the scheduler204 (FIG. 7) of theservice provider2 with reference to the flowchart ofFIG. 35, a table to be checked when performing scheduling is discussed with reference toFIG. 34.FIG. 34 illustrates a table to be checked when forming a schedule by thescheduler204, and this table shows the reservation times when predetermined items of content are to be distributed.
• In a distribution reservation table321, reservations can be made every ten minutes, and time spans at 1:00, 1:10, 1:20, and 1:30 are enlarged. InFIG. 34, black dots indicate that reservations have been made, and white dots indicate that no reservations are made (free).
• FIG. 34 illustrates that N reservations can be made from 0 to 10 minutes. A specific number N is determined by the data amount of content data to be distributed and the data amount (transmission capacity) by which theservice provider2 can distribute for 10 minutes. However, since the transmission capacity (processing capacity) is constant, the number N is basically determined by the data amount of content data.
• Accordingly, when many items of content data having a larger amount of data are sent, the number N becomes smaller, and when many items of content data having a smaller amount of data is sent, the number N becomes larger. Thus, N varies according to the time spans. N is determined by considering the amount of content data that have already been reserved.
• The distribution reservation table321 includes a definedportion322 and anundefined portion323. In the definedportion322, the number of reservations that have been determined as schedules is indicated. In theundefined portion323, the number of reservations that cannot be determined as schedules since requests for presents have not been accepted by the users is indicated.
• Thescheduler204 performs scheduling based on the flowchart ofFIG. 35 by referring to the distribution reservation table321 shown inFIG. 34. The processing for determining the distribution time is described below with reference to the flowchart ofFIG. 35 without explaining processing for obtaining other information. The other information has already been obtained and written as stated above.
• In step S351, thescheduler204 determines whether a request to purchase a new item of content has been made and whether it is necessary to form a schedule for distributing the content.
• As discussed above, the processing for purchasing content is performed by the content-distribution reservation unit201. When determining that a content reservation has been made (for example, step S211 ofFIG. 24 is performed), the content-distribution reservation unit201 instructs thescheduler204 to form a new schedule. Thescheduler204 makes a determination in step S351 by determining whether the above instruction has been given.
• If it is determined in step S351 that a new schedule is to be formed, the process proceeds to step S352. In step S352, it is determined whether a schedule to be formed is a schedule concerning a present. The reason for making the determination in step S352 is that a schedule concerning a present (specially, the time to distribute the content data) cannot be determined before the user to receive the present decides to accept the present.
• If it is determined in step S352 that the schedule to be formed is not a schedule concerning a present, it is determined in step S353 whether the time to distribute the content data to be purchased is designated by the user. If it is determined in step S353 that the time to distribute the content data is designated, the process proceeds to step S354. In step S354, it is determined whether it is possible to distribute the content data at the designated time.
• This determination can be made by referring to the distribution reservation table321 shown inFIG. 34. For example, when checking the time span at 1:00, N reservations can be made at 1:00. Reservations have already been made in0-1 through0-3, while there is no reservation in0-4 and0-N. If the content data distribution time is designated at 1:00 by the user, a reservation can be made in0-4. Thus, it can be determined that content data can be distributed at the time designated by the user.
• When checking, for example, the time span at 1:10, N (different from the number N at 1:00) reservations can be made for the time span at 1:10. Reservations have already been made in10-1 through10-N. That is, no reservations can be made at 1:10. If the content data distribution time is designated at 1:10 by the user, no reservations can be made. Thus, it can be determined that it is not possible to distribute the content data at the time designated by the user.
• In this manner, if it is determined in step S354 that the content data can be distributed at the time designated by the user, the process proceeds to step S355. In step S355, the designated time is set to be the content data distribution time. That is, the time specified by the user is written into the “distribution time” inFIG. 22. In this case, information “not distributed” is written into the “distribution status”.
• When the user designates the content data distribution time and when it is determined that content data can be distributed at the time designated by the user, a schedule with the designated time is formed.
• If it is determined in step S354 that the content data cannot be distributed at the time designated by the user, the process proceeds to step S356. In step S356, the time closest to the designated time by the user and at which the content data can be distributed is searched for by checking the distribution reservation table321.
• Reference is again made toFIG. 34. If the time designated by the user is 1:10, the time span at 1:10 is fully reserved, and thus, it is determined that content data cannot be distributed at 1:10 designated by the user. In this case, the time before or after the designated time is checked. It necessary to preset whether to first search the time before or after the designated time, and basically, it is not important which is searched first.
• When the time before the designated time is searched first, the time to be searched (time A) is compared with the time when search is conducted (current time), and unless the time A is after the current time, the time A is not searched. For example, if the designated time is 1:10, the time before the designated time (i.e., time A) is 1:00, and if the time when search is conducted (i.e., the current time) is, for example, 1:05, content data cannot be distributed (reserved) at time A.
• In step S356, by checking the distribution reservation table321, and the time closest to the designated time by the user and at which the content data can be distributed is set to be the distribution time. Then, the set time is written into the “distribution time” of the schedule (FIG. 22).
• As described above, when the user specifies the content data distribution time and when it is determined that the content data cannot be distributed at the designated time, a schedule in which the time closest to the designated time and at which the content data can be distributed is formed.
• The above-described processing is executed when the user has designated the time. If it is determined in step S353 that the user has not designated the content data distribution time, the process proceeds to step S357. In step S357, the time (basically after the current time) closest to the time (current time) when the schedule is formed and at which the content data can be distributed is set to be the distribution time.
• As discussed above, when the user has not specified the content data distribution time, thescheduler204 forms a schedule with the time when the content data can be distributed.
• If it is determined in step S352 that a new schedule to be formed is a schedule concerning a present, the process proceeds to step S358. In step S358, thescheduler204 forms a schedule in which the information “distribution status” inFIG. 22 is set to be “undefined”, i.e., it is not determined whether to distribute the content data.
• In this case, the date (time) designated by the user as the time and date at which the user delivers the content data as a present is written into the information “distribution time” of the schedule shown inFIG. 22. Such a schedule is counted as one reservation in theundefined portion323 of the destination reservation table321.
• The reservation cannot be defined as a schedule even though the time when the content data is distributed is designated. This is because information indicating whether the user to receive the present has decided to accept the present has not been received. It is then determined in step S359 whether information indicating whether the user has decided to accept the present has been received. This processing is similar to the processing in step S325 of the flowchart inFIG. 30.
• Step S359 is performed by determining whether thescheduler204 has received information concerning a response from the user to receive the present. If it is determined in step S359 that information has been received, the process proceeds to step S360.
• It is determined in step S360 whether the received information indicates that the present is to be received (accepted). If the information is found to indicate that the present is to be accepted, the process proceeds to step S353 and the step S353 and the subsequent steps are performed. Step S353 and the subsequent steps have been discussed, and an explanation thereof is omitted, except for processing for a schedule concerning a present.
• It is determined in step S353 by referring to undefined schedules whether the time has been designated. That is, even undefined schedules have already been formed as schedules, such as those shown inFIG. 22, and the “distribution time” is checked to perform step S353.
• If a predetermined time is written as the information “distribution time”, the process proceeds to step S354. In step S354, the time written in the “distribution time” is compared with the current time, and if the written time is after the current time and if the content data can be distributed at the written time, the process proceeds to step S355.
• If it is determined in step S354, as a result of comparing the written time with the current time, that the written time is before the current time, the written time has already elapsed. That is, the time designated as the time to deliver the present has already elapsed.
• In this case, the process proceeds to step S356. In step S356, the earliest possible time is preferably set to be the distribution time rather than the time closest to the designated time and at which the content data can be distributed.
• When the “distribution time” in the schedule is set and written, information indicating the “distribution status” is also changed from “undefined” to “not yet distributed”. Also, the number of reservations written into theundefined portion323 of the distribution table321 is decremented by one, and the number of reservations corresponding to the set time in the definedportion323 is incremented by one.
• A schedule concerning a present can be formed, as described above.
• If it is determined in step S360 that information from the user to receive the present indicates that the user does not accept the present, the process proceeds to step S361. In step S361, the undefined schedule for the content refused is discarded. In this processing, the number of reservations in theundefined portion323 of the destination reservation table321 is decremented by one.
• The schedule formed as described above is provided to theSTB11 in response to queries from theSTB11 at predetermined time intervals as to whether a new schedule has not been formed for theSTB11. TheSTB11 sends a request to distribute content data based on the provided schedule, and the request is sent after the time when the schedule has been received.
• Because of this time lag, it is necessary to consider the possibility that the situation of theSTB11 has changed from the time when it has received the schedule to the time when theSTB11 sends a request to distribute content data.
• More specifically, theSTB11 is provided with the storage unit85 (FIG. 3) having a limited capacity, and content data is stored in thisstorage unit85. Even if thestorage unit85 has a capacity for storing the content data to be distributed when the schedule has been received, the capacity of thestorage unit85 may become short because another content data is received and stored before sending a request to distribute the content data.
• In this manner, even if theSTB11 sends a request to distribute content data based on a schedule and receives the content data, the capacity of thestorage unit85 may not be enough for storing the content data. If such a situation occurs in theSTB11, it is necessary that theservice provider2 perform processing for re-sending the content data.
• Processing for sending content data by theservice provider2 by considering such a situation is described below with reference to the flowchart ofFIG. 36.
• In the flowchart ofFIG. 36, steps S385 and S386 are added to the flowchart ofFIG. 27. That is, steps S381 through S384 and steps S387 through S391 of the flowchart inFIG. 36 are similar to steps S231 through S234 and S235 through S239 of the flowchart inFIG. 27, and an explanation thereof is thus omitted.
• Step S385 is performed when it is determined that the STB11 (by way of example) has sent a request to distribute content data. In step S385, when distributing the requested content data, it is determined whether the device for receiving the content data can reliably store the content data. The information for making this determination must be sent from theSTB11.
• When sending a request to distribute content data, theSTB11 sends information concerning the remaining capacity of thestorage unit85 to theservice provider2. Theservice provider2 compares the remaining capacity of thestorage unit85 with the size of the requested content data, and only when the remaining capacity of the storage unit is greater than the size of the content data, the process proceeds to step S387, and step S387 and the subsequent steps, i.e., processing for distributing the content data, are executed.
• Alternatively, when sending a request to distribute content data, theSTB11 compares the remaining capacity of thestorage unit85 with the size of the content data to request (theSTB11 can obtain this information by referring to the information concerning the schedule received in step S253 ofFIG. 28), and sends information indicating whether there is a capacity for storing the content data in thestorage unit85 to theservice provider2.
• Theservice provider2 receives either of the information indicating that the content data can be received or the information indicating that the content data cannot be received. By using such information, theservice provider2 may perform step S385.
• In any case, theservice provider2 does not execute step S387 unless it determines that theSTB11 can store the content data to be received. Accordingly, it is possible to prevent a situation in which theSTB11 cannot store received content data.
• When it is determined in step S385 that it is not possible to send requested content data, the process proceeds to step S386. In step S386, the schedule is changed. That is, in step S386, it is understood that content data to be distributed cannot be sent, and that it should be distributed another time.
• Accordingly, the “distribution time” of the schedule has to be rewritten (changed). The “distribution time” may be rewritten so that the content data is re-sent after the lapse of a predetermined time, for example, after one hour. In this case, details in the distribution reservation table321 are also rewritten, and the number of reservations at the changed time is incremented by one.
• Alternatively, theservice provider2 may send mail to the user to instruct him/her to change the distribution time, and may change the schedule based on a response from the user. In this case, the “distribution status” of the corresponding schedule is changed to “not defined” until a response from the user is received. Accordingly, the number of reservations of theundefined portion322 of the distribution reservation table321 is incremented by one. Then, when receiving a response, the “distribution time” in the schedule is changed to the time indicated in the response, and the number of reservations at the changed time in the distribution reservation table321 is incremented by one.
• When the schedule is rewritten, the rewritten schedule is re-sent to theSTB11, and theSTB11 performs processing based on the rewritten schedule. The content data is then sent and received.
• Alternatively, when theSTB11 becomes ready to store the content data, it may re-send a request to distribute the content data. In this case, theservice provider2 maintains the “distribution status” in the corresponding schedule to be “not distributed” without deleting the schedule.
• As discussed above, by sending required information from theSTB11 and by performing corresponding processing by theservice provider2, it is possible to prevent a situation in which content data received by theSTB11 cannot be stored. Thus, theservice provider2 does not perform processing for distributing content data in vain.
• In the above-described embodiment, processing for purchasing one item of content is described by way of example. However, processing for purchasing a plurality of items of content data at the same time can be performed, and a plurality of items of content data can be sent and received at the same time.
• The above-described series of processing may be executed by hardware having the corresponding functions or by software. If software is used to execute the series of processing, the software program is installed from a recording medium into a computer built in dedicated hardware or a computer, such as a general-purpose computer, that can execute various functions by installing various programs thereinto.
• The recording medium may be a package medium, for example, the magnetic disk61 (including flexible disk), the optical disc62 (including CD-ROM (Compact Disc-Read Only Memory) and DVD (Digital Versatile Disc))), the magneto-optical disk63 (including MD (Mini-Disc) (registered)), or thesemiconductor memory64, which is distributed for providing the program to the user, separately from the personal computer, such as theservice provider2. The recording medium may also be formed of theROM42 or a hard disk containing thestorage unit48 storing the program therein, which is provided to the user while being integrated in a computer.
• In this specification, the steps forming the program provided by the medium may be executed in chronological order as described in the specification. Alternatively, the steps may be executed concurrently or individually.
• In this specification, the system is the entire apparatus formed of a plurality of devices.
INDUSTRIAL APPLICABILITY
• According to the present invention, content data can be supplied to user devices.
• According to the present invention, content data or license data required for playing back the content data can be given as a present.
• According to the present invention, content data or license data required for playing back the content data can be given as a present by a user at a desired time.

Claims (10)

1. An information processing system comprising a first information processing apparatus for controlling the distribution of content, a second information processing apparatus for making a request to distribute the content, and a third information processing apparatus for receiving the distribution of the content,

said first information processing apparatus comprising:

first management means for managing a first ID for identifying the content;

second management means for managing a second ID for identifying said second information processing apparatus and a third ID for identifying said third information processing apparatus;

supply means for supplying the first ID managed by said first management means to said second information processing apparatus in response to a request to distribute the content from said second information processing apparatus;

specifying means for specifying, when receiving the first ID, information for specifying the second ID, and information for specifying the third ID from said second information processing apparatus, the second ID and the third ID managed by said second management means from the received information;

distribution means for distributing the content identified by the first ID to said third information processing apparatus corresponding to the third ID specified by said specifying means,

said second information processing apparatus comprising:

request means for requesting said first information processing apparatus to distribute the content; and

sending means for sending the first ID corresponding to the content selected by a user from the first ID supplied from said supply means and for sending information for specifying the second ID and information for specifying the third ID in response to the request from said request means,

said third information processing apparatus comprising:

storage means for receiving and storing the content distributed by said distribution means.

2. An information processing apparatus comprising:

first management means for managing a first ID for identifying a first apparatus;

second management means for managing a second ID for identifying a second apparatus;

third management means for managing a third ID for identifying content;

supply means for supplying the third ID managed by said third management means to the first apparatus in response to a request to distribute the content from the first apparatus;

specifying means for specifying, when receiving information for specifying the first ID, information for specifying the second ID, and the third ID from the first apparatus, the first ID managed by said first management means and the second ID managed by said second management means from the received information; and

distribution means for distributing the content identified by the third ID to the second apparatus corresponding to the second ID specified by said specifying means.

3. The information processing apparatus, further comprising billing means for billing the content distributed by said distribution means to a user of the first apparatus identified by the first ID specified by said specifying means.

4. The information processing apparatus according toclaim 2, further comprising:

query means for querying, after the second ID is specified by said specifying means, a user of the second apparatus identified by the second ID as to whether to accept the distribution of the content; and

scheduling means for forming, when receiving a response indicating that the distribution of the content is to be accepted from the user of the second apparatus in response to the query made by said query means, a schedule for distributing the content identified by the third ID to the second apparatus corresponding to the second ID specified by said specify means,

wherein said distribution means distributes the content based on the schedule formed by said scheduling means.

5. The information processing apparatus according toclaim 4, wherein, when the user of the first apparatus or the user of the second apparatus designates a time to distribute the content, said scheduling means forms a schedule for distributing the content at the designated time.

6. The information processing apparatus according toclaim 4, further comprising providing means for providing, when the schedule for the second apparatus is formed by said scheduling means, the schedule to the second apparatus in response to a request to provide the schedule from the second apparatus.

7. The information processing apparatus according toclaim 2, wherein:

said first management means and said second management means manage the same table in which IDs including the first ID and the second ID, user IDs for identifying the users, and passwords, and mail addresses are associated with each other; and

said specifying means uses information indicating at least one of the user ID and the password as the information for specifying the first ID, and uses the mail address as the information for specifying the second ID.

8. An information processing method comprising:

a first management step of managing a first ID for identifying a first apparatus;

a second management step of managing a second ID for identifying a second apparatus;

a third management step of managing a third ID for identifying content;

a supply step of supplying the third ID managed by processing of said third management step to the first apparatus in response to a request to distribute the content from the first apparatus;

a specifying step of specifying, when receiving information for specifying the first ID, information for specifying the second ID, and the third ID from the first apparatus, the first ID managed by processing of said first management step and the second ID managed by processing of said second management step from the received information; and

a distribution control step of controlling the distribution of the content identified by the third ID to the second apparatus corresponding to the second ID specified by processing of said specifying step.

9. A recording medium in which a computer-readable program is recorded, said computer-readable program comprising:

a first management step of managing a first ID for identifying a first apparatus;

a second management step of managing a second ID for identifying a second apparatus;

a third management step of managing a third ID for identifying content;

a supply step of supplying the third ID managed by processing of said third management step to the first apparatus in response to a request to distribute the content from the first apparatus;

a specifying step of specifying, when receiving information for specifying the first ID, information for specifying the second ID, and the third ID from the first apparatus, the first ID managed by processing of said first management step and the second ID managed by processing of said second management step from the received information; and

a distribution control step of controlling the distribution of the content identified by the third ID to the second apparatus corresponding to the second ID specified by processing of said specifying step.

10. A program for allowing a computer to execute:

a first management step of managing a first ID for identifying a first apparatus;

a second management step of managing a second ID for identifying a second apparatus;

a third management step of managing a third ID for identifying content;

a supply step of supplying the third ID managed by processing of said third management step to the first apparatus in response to a request to distribute the content from the first apparatus;

a specifying step of specifying, when receiving information for specifying the first ID, information for specifying the second ID, and the third ID from the first apparatus, the first ID managed by processing of said first management step and the second ID managed by processing of said second management step from the received information; and

a distribution control step of controlling the distribution of the content identified by the third ID to the second apparatus corresponding to the second ID specified by processing of said specifying step.

Images