Content delivery system, delivery server, receiving terminal, and content delivery method

Abstract

A transmitting terminal can transmit a content held by itself to a specific receiving terminal having no email software as if using a mailer. The transmitting terminal (10) and the receiving terminal (20) are connected to a delivery server (30) via a network (4). The delivery server (30) comprises: a database (36) for registering the device ID that specifies the receiving terminal (20); a content storage (39) for temporarily storing a content transmitted from the transmitting terminal (10); and table (33, 37) for managing contents separately on a per device ID basis of the receiving terminal. The delivery server (30), when receiving a request from the receiving terminal (20), refers to the tables (33, 27) and transmits to the receiving terminal (20) a content, the transmission destination of which corresponds to the device ID of the receiving terminal (20).

Claims

1. A content delivery system comprising a transmitting terminal, a plurality of receiving terminals, and a delivery server, wherein the delivery server comprises a database which registers a user ID of a sender who transmits a picture content and a user ID of each of a plurality of receivers who receives the picture content in association with each other, and a content storage which stores the picture content transmitted from the sender, wherein, in a case that the transmitting terminal transmits a new picture content to the delivery server, each of the plurality of receiving terminals receives a first notice indicating that the new picture content is stored in the content storage, wherein each of the plurality of receiving terminals displays a list of the picture contents which are transmitted from the transmitting terminal and stored in the content storage, information about a sender who transmitted the listed picture contents, and a comment inputted by the transmitted terminal, and wherein, in case that one of the plurality of receiving terminals sends a request of rejecting the receiving of the picture contents to the delivery server, the list of the picture contents are not displayed on the receiving terminal which sent the request.

2. The content delivery system according to claim 1, wherein each of the plurality of receiving terminals further displays a group of picture contents.

3. A method for delivering picture contents among a transmitting terminal, a plurality of receiving terminals and a delivery server including a database which registers a user ID of a sender who transmits a picture content and a user ID of each of a plurality of receivers who receives the picture content in association with each other, and a content storage which stores the picture content transmitted from the sender, the method comprising the steps of: transmitting from a transmitting terminal a new picture content to the delivery server, wherein each of the plurality of receiving terminals receives a first notice indicating that the new picture content is stored in the content storage, and displaying, by each of the plurality of receiving terminals, a list of the picture contents which are transmitted from the transmitting terminal and stored in the content storage, information about a sender who transmitted the listed picture contents, and a comment inputted by the transmitted terminal, wherein, in a case of sending a request of rejecting the receiving of the picture contents to the delivery server by one of the plurality of receiving terminals, the list of the picture contents are not displayed on the receiving terminal which sent the request.

4. The method for delivering picture contents according to claim 3, further comprising the step of displaying, by each of the plurality of receiving terminals, a group of picture contents.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

(1) FIG. 1 is an overall architectural diagram showing an exemplary embodiment of a content delivery system.

(2) FIG. 2 is a diagram showing an exemplary internal structure of a server 30.

(3) FIG. 3 is a diagram showing an exemplary internal structure of a TV set 20.

(4) FIG. 4 is a flowchart illustrating a process flow of a content delivery service.

(5) FIG. 5 shows an example of an unread e-mail check table.

(6) FIG. 6 shows an example of a sender DB.

(7) FIG. 7 shows an example of a receiver DB.

(8) FIG. 8 snows an example of a content management table.

(9) FIG. 9 shows an example of a login/user registration screen at a sending side.

(10) FIG. 10 shows an example of a user registration screen (to very the terms).

(11) FIG. 11 shows an example of a user registration screen (to specify a destination).

(12) FIG. 12 shows an example of a user registration screen (to enter member information).

(13) FIG. 13 shows an example of a user registration screen (to confirm the entry).

(14) FIG. 14 shows an example of a user registration screen (tentative registration completed).

(15) FIG. 15 shows an example of an initial screen for connecting to the server at a receiving end.

(16) FIG. 16 shows an example of a screen to accept a sender.

(17) FIG. 17 shows an example of a screen for a definite user registration.

(18) FIG. 18 shows an example of a screen to create an e-mail.

(19) FIG. 19 shows an example of a created e-mail.

(20) FIG. 20 shows an example of a screen to acid/edit destinations.

(21) FIG. 21 shows an example of a screen to register/edit mobile phones.

(22) FIG. 22 shows an example of a screen to access from a mobile phone.

(23) FIG. 23 shows an example of a screen to transmit an e-mail from a mobile phone.

(24) FIG. 24 shows an example of a received e-mail list display screen.

(25) FIG. 25 shows an example of a still picture list display screen.

(26) FIG. 26 shows an example of a screen reproducing a motion and/or still picture.

(27) FIG. 27 shows an example of a screen to select and download an e-mail.

(28) FIG. 28 shows an example of a screen to confirm the execution of downloading.

(29) FIG. 29 shows an example of a screen indicating a download in process.

(30) FIG. 30 shows an example of a screen indicating a download completed.

(31) FIG. 31 shows an example of a sender list display screen.

(32) FIG. 32 shows an example of a screen to accept a sender.

(33) FIG. 33 shows an example of a screen to accept/reject reception.

(34) FIG. 34 is an overall architectural diagram showing an exemplary embodiment of a content delivery system.

(35) FIG. 35 is a diagram showing an exemplary internal structure an authentication server 70.

(36) FIG. 36 shows an example of TV device DB.

(37) FIG. 37 shows an example of a one-time ID management table.

(38) FIG. 38 is a flowchart illustrating a process flow of authentication.

(39) FIG. 39 shows an example of a TV device DB for management using device identifying ID.

(40) FIG. 40 shows an example of a one-time ID management table for management using device identifying ID.

(41) FIG. 41 is a flowchart illustrating a process flow regarding device identifying ID.

(42) FIG. 42 shows an example of a screen to acquire and confirm a device identifying ID.

(43) FIG. 43 shows an example of a screen to acquire and confirm a device identifying ID, when the user has no device identifying ID.

(44) FIG. 44 shows an example of a screen to delete the device identifying ID.

(45) FIG. 45 shows an example of an unread e-mail check table for management using device identifying ID.

(46) FIG. 46 shows an example of a sender DB for management using device identifying ID.

(47) FIG. 47 shows an example of a receiver DB for management using device identifying ID.

(48) FIG. 48 shows an example of a content management table for management using device identifying ID.

(49) FIG. 49 is a diagram showing an exemplary internal structure of an authentication server 80.

(50) FIG. 50 shows an example of a member DB.

(51) FIG. 51 shows an example of a TV device DB for management using member ID.

(52) FIG. 52 shows an example of a one-time ID management table for management using member ID.

(53) FIG. 53 is a flowchart illustrating a process flow regarding member ID.

(54) FIG. 54 shows an example of a screen to register and confirm a member ID.

(55) FIG. 55 shows an example of a screen to newly register a member ID.

(56) FIG. 56 shows an example of a screen to delete a member ID.

(57) FIG. 57 shows an example of a user registration screen (to specify a destination for management using member ID).

(58) FIG. 58 is a flowchart illustrating a process flow to transmit a message by “memo messaging service”.

(59) FIG. 59 shows an example of a message input screen to enter a device identifying ID and a member ID.

(60) FIG. 60 shows an example of a screen to confirm message transmission.

(61) FIG. 61 shows an example of a TV device DB for management using member ID.

(62) FIG. 62 is a flowchart illustrating a process flow to receive a message by “memo messaging service”.

(63) FIG. 63 shows an example of a “memo messaging” message list screen.

(64) FIG. 64 shows an example of a “memo messaging” message display screen.

(65) FIG. 65 shows an example of a screen to enter a password of a “memo messaging” member.

LIST OF REFERENCE NUMERALS

(66) 4 . . . Network 10 . . . Transmitting terminal (PC) 20 . . . Receiving terminal (TV set) 21 . . . Network transceiver 22 . . . Browser 23 . . . Picture reproducer 27 . . . Display 24 . . . Device ID sender 25 . . . Device ID storage 26 . . . Content storage 30 . . . Delivery server 31 . . . Network transceiver 32 . . . Member information manager 33 . . . Unread e-mail check table 34 . . . Sender DB 35 . . . Receiver DB 36 . . . TV device DB 37 . . . Content management table 38 . . . Content transceiver 39 . . . Content storage 50 . . . Mobile phone 70 . . . Authentication server 72 . . . Member information manager 76 . . . TV device DB 77 . . . One-time ID management table 80 . . . Authentication server 82 . . . Member information manager 85 . . . Member DR 86 . . . TV device DB 87 . . . One-time ID management table