U.S. patent application number 10/692920 was filed with the patent office on 2004-05-13 for pickup and delivery of data files.
Invention is credited to Bullock, David Lynn, Fell, Gail Hegarty, McClure, John Joseph, Tabor, Walter Randall, Yang, Jie.
Application Number | 20040092251 10/692920 |
Document ID | / |
Family ID | 23798420 |
Filed Date | 2004-05-13 |
United States Patent
Application |
20040092251 |
Kind Code |
A1 |
Fell, Gail Hegarty ; et
al. |
May 13, 2004 |
Pickup and delivery of data files
Abstract
A data file is regarded as a digital package. A convenient
interface is provided for scheduling pickup and delivery of the
data file via one or more satellite communication links. The data
file may represent various types of information, such as text,
images, audio or video. A centralized system receives the
scheduling order and arranges for the data file to be automatically
picked up from one or more locations and delivered to one or more
destinations. The delivery service may include buffering the data
file for a predetermined time period to comply with the scheduled
delivery time. The centralized system provides a scheduling
confirmation notice for the scheduled pickup and delivery, and also
provides notice that the data file was actually delivered. The
centralized system maintains an activity log useful for status
inquiry and billing. In short, the centralized system functions as
a "dispatcher" for bits, within an infrastructure for receiving,
tracking, delivering and billing based on bits.
Inventors: |
Fell, Gail Hegarty; (Rye,
NY) ; Yang, Jie; (Stamford, CT) ; Tabor,
Walter Randall; (Lithonia, GA) ; Bullock, David
Lynn; (Conyers, GA) ; McClure, John Joseph;
(Stone Mountain, GA) |
Correspondence
Address: |
DAVID LOEWENSTEIN
802 KING ST.
RYE BROOK
NY
10573
US
|
Family ID: |
23798420 |
Appl. No.: |
10/692920 |
Filed: |
October 24, 2003 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
10692920 |
Oct 24, 2003 |
|
|
|
09452900 |
Dec 1, 1999 |
|
|
|
6564064 |
|
|
|
|
Current U.S.
Class: |
455/412.1 ;
455/427; 455/428 |
Current CPC
Class: |
G01S 19/11 20130101;
H04W 52/0216 20130101; G01S 19/258 20130101; G01S 19/256 20130101;
H04W 74/08 20130101; G01S 19/46 20130101; H04W 64/00 20130101; G01S
19/37 20130101; Y02D 30/70 20200801; G01S 5/0027 20130101; H04W
84/06 20130101; H04W 52/0229 20130101; H04W 88/02 20130101 |
Class at
Publication: |
455/412.1 ;
455/427; 455/428 |
International
Class: |
H04Q 007/20 |
Claims
1. A method for file transfer, comprising: transmitting a file
using a satellite communications link in accordance with a
scheduling order created by a sender using a screen-based interface
specifying pickup and delivery instructions for the file.
2. The method of claim 1, further comprising confirming that the
file has been transmitted to a provider of the file.
3. The method of claim 1, wherein the transmitting is
simultaneously performed to selected destinations that are part of
a predefined group excluding some destinations in a geographic
area.
4. The method of claim 1, further comprising receiving the
scheduling order from a user, the scheduling order also specifying
at least one location and time for retrieval of the file.
5. The method of claim 1, further comprising checking facility
availability in response to receiving the scheduling order.
6. The method of claim 1, further comprising sending a confirmation
notice to the user after checking facility availability.
7. The method of claim 1, further comprising converting the format
of the file.
8. The method of claim 1, further comprising storing the file for a
predetermined amount of time.
9. A system for file transfer, comprising: a transmitter for
transmitting a file using a satellite communications link in
accordance with a scheduling order created by a sender using a
screen-based interface specifying pickup and delivery instructions
for the file.
10. The system of claim 9, further comprising means for confirming
that the file has been transmitted to a provider of the file.
11. The system of claim 9, wherein the transmitting is
simultaneously performed to selected destinations that are part of
a predefined group excluding some destinations in a geographic
area.
12. The system of claim 9, further comprising a processor for
receiving the scheduling order from a user, the scheduling order
also specifying at least one location and time for retrieval of the
file.
13. The system of claim 9, wherein the processor is also for
checking facility availability in response to receiving the
scheduling order.
14. The system of claim 9, wherein the processor is also for
sending a delivery notice to a destination for the file before
transmitting the file.
15. The system of claim 9, further comprising a processor for
converting the format of the file.
16. The system of claim 9, further comprising a data storage for
storing the file for a predetermined amount of time.
17. A user interface for scheduling a file transfer, via a
satellite communications system comprising: a terminal for
displaying a data screen to a sender, the data screen including two
or more of the following fields specifying a file location, size,
pickup time, payment type, confirmation type and delivery time, and
means for sending information entered through the data screen to a
central system.
18. A method for file reception, comprising: receiving a file that
has been transmitted using a satellite communications link in
accordance with a scheduling order created by a sender using a
screen-based interface specifying pickup and delivery instructions
for the file.
19. The method of claim 18, further comprising confirming that the
file has been received to a provider of the file.
20. The method of claim 18, wherein the file has been transmitted
by multicasting.
21. The method of claim 18, further comprising confirming
availability of delivery according to a scheduling order, and
wherein the confirming of availability occurs before the receiving
of the file.
22. A system for file reception, comprising: a receiver for
receiving a file that has been transmitted using a satellite
communications link in accordance with a scheduling order created
by a sender using a screen-based interface specifying pickup and
delivery time for the file
23. The system of claim 22, further comprising means for confirming
that the file has been received to a provider of the file.
24. The system of claim 22, wherein the file has been transmitted
by multicasting.
25. The system of claim 22, further comprising means for confirming
availability for delivery according to the scheduling order.
Description
BACKGROUND OF THE INVENTION
[0001] The present invention relates to a method and system for
data file pickup and delivery, and, more particularly, is directed
to a centralized system including a satellite link for delivering
data files in accordance with instructions by a user through a
screen-based interface.
[0002] As the popularity of the Internet increases, there is a
commensurate increase in the need to deliver content over large
distances, bypassing clogged communication channels. Sometimes
content must be delivered according to a specified schedule that
may be one-time or recurring. This need is particularly critical
for files which must be delivered in a real time or near real time
sequence, such as audio and video files, and for files which must
be delivered at the same time to a multiplicity of places. A
similar situation exists for data streamed during delivery.
[0003] There is also a need for an automated interface by which a
user can schedule and manage transfer of data files, so that file
transfer services can be provided in a highly cost-effective
manner.
SUMMARY OF THE INVENTION
[0004] In accordance with an aspect of this invention, there are
provided a method of and a system for transmitting a file using a
satellite communications link in accordance with a scheduling order
specifying pickup and delivery instructions for the file.
[0005] According to a further aspect of the invention, the
scheduling order is received from a user, the scheduling order also
specifying at least one location and time for retrieval of the
file.
[0006] In accordance with another aspect of this invention, there
is provided a user interface for scheduling a file transfer,
comprising a terminal for displaying a data screen to the a user,
the data screen including fields for specifying a file location,
size, pickup time and delivery time, and means for sending
information entered through the data screen to a central
system.
[0007] In accordance with another aspect of this invention, there
are provided a method and a system for receiving a file that has
been transmitted using a satellite communications link in
accordance with a scheduling order specifying pickup and delivery
instructions for the file.
[0008] According to a further aspect of the invention, this file is
transmitted by multicasting, and delivery availability according to
the scheduling order is confirmed before the file is received.
[0009] It is not intended that the invention be summarized here in
its entirety. Rather, further features, aspects and advantages of
the invention are set forth in or are apparent from the following
description and drawings.
BRIEF DESCRIPTION OF THE DRAWINGS
[0010] FIG. 1 is a block diagram illustrating an environment in
which the present invention is applied;
[0011] FIG. 2 is a flowchart illustrating data file pickup and
delivery according to the present invention;
[0012] FIG. 3 is a chart showing a screen for customer
registration; and
[0013] FIG. 4 is a chart showing a screen for scheduling data file
pickup and delivery.
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0014] The present technique regards a data file as a digital
package, and provides a convenient interface for scheduling pickup
and delivery of the data file via one or more satellite
communication links. The data file may represent various types of
information, such as text, images, audio or video. A centralized
system receives the scheduling order and arranges for the data file
to be automatically picked up from one or more locations and
delivered to one or more destinations. The delivery service may
include buffering the data file for a predetermined time period to
comply with the scheduled delivery time. The centralized system
provides a scheduling confirmation notice for the scheduled pickup
and delivery, and also provides notice that the data file was
actually delivered. The centralized system maintains an activity
log useful for status inquiry and billing. In short, the
centralized system functions as a "dispatcher" for bits, within an
infrastructure for receiving, tracking, delivering and billing
based on bits.
[0015] The centralized system provides comprehensive management of
communication channel capacity, particularly in the space segment.
Multiple satellites may provide capacity on an ongoing basis, with
capacity available on additional satellites during peak demand. The
centralized system also efficiently manages capacity on
inter-satellite links, if any.
[0016] The present technique also provides a user with an easy to
use screen-based interface for scheduling data file pickup and
delivery without the burden of managing communications capacity.
The user interface also allows the user to track the progress of
the data file from its source(s) to its destination(s).
[0017] Referring now to the drawings, and in particular to FIG. 1,
there is illustrated an environment in which the present invention
is applied. FIG. 1 shows communication satellites 10, 11,
inter-satellite link 14, satellite links 15, 16, 17, 18, 19,
terrestrial network 20, earth stations 30, 31, 35A, 35B, 35C,
controllers 40, 45, data buses 42, 47, transmitter 50, receiver 55,
data storage units 60, 65, gateway 70, client 75, sending customer
terminal 80, service provider premises 90 and customer premises 92,
95.
[0018] Generally, terrestrial links are assumed to operate in a
duplex handshaking manner. Satellite links typically operate in
simplex mode although a return link is sometimes configured via a
terrestrial or other satellite link.
[0019] Communications satellites 10 and 11 are preferably in
geostationary orbit. Other orbits may be used, and those of
ordinary skill in the art will understand the additional
communications overhead needed to communicate with satellites in
other than geostationary orbit. Satellite 10 is adapted to receive
information on uplink 15 from earth station 30 and to transmit the
received information on downlink 16 covering earth station 35A.
This is referred to as a forward channel. In some embodiments,
satellite 10 is also adapted to receive information from earth
station 35A on a second uplink and to transmit the received
information on a second downlink to earth station 30. This is
referred to as a reverse channel. It will be appreciated that the
actual communication channel may be the same for the first and
second uplinks and downlinks, respectively, and can be re-used.
[0020] Satellite 11 is adapted to receive information on uplink 17
from earth station 31 and to transmit the received information on a
downlink covering earth stations 35B, 35C. For clarity, the
downlink from satellite 11 is depicted as downlinks 18, 19,
although it will be understood that the information on each of
these downlinks is identical. In some embodiments, satellite 11 is
also adapted to transmit from earth stations 35B, 35C to earth
station 31.
[0021] In the embodiment shown in FIG. 1, satellites 10 and 11
communicate directly with each other via inter-satellite link 14.
For example, to transmit from earth station 30 to earth station
35C, the best path may be via uplink 15, inter-satellite link 14
and downlink 19.
[0022] Earth stations 30, 31 and 35A-35C each include an antenna
for communicating with one of satellites 10 and 11 and appropriate
electronics for converting between a baseband electrical signal and
a radio frequency signal, such as in Ka, Ku or C band.
[0023] Terrestrial network 20 encompasses the public switched
telephone network (PSTN) including wireline and wireless links, the
Internet and any private wireline and wireless terrestrial
communication channels established for communication between
controllers 40 and 45.
[0024] For brevity, only the configurations coupled to earth
stations 30 and 35A will be discussed. In practice, many earth
stations communicate with many satellites in the manner discussed
below.
[0025] The transmitting configuration for an earth station will now
be discussed. Earth station 30 is an example of a transmitting
earth station.
[0026] Sending customer terminal 80 is a general purpose processor,
such as a personal computer, personal digital assistant or the
like. Customer terminal 80 is coupled to controller 40 via an
appropriate communication channel, such as a dedicated
communication line, a local area network, a dial-up communication
line, an Internet packet switched channel and so on. Sending
customer terminal 80 is adapted to provide a screen-based interface
for entering scheduling orders for data file pickup and delivery,
to receive notices from the central system relating to the
scheduled pickup and delivery services, and to provide a data file
for pickup. The data file may represent various types of
information, such as text, images, audio or video. The data files
may be delivered via Internet file transfer protocol (FTP),
transmission control protocol (TCP), user datagram protocol (UDP)
and so on.
[0027] In one embodiment, the screen-based interface is provided
via access to an Internet web site. In another embodiment,
additional software for practicing the present technique is
operative in customer terminal 80 for providing the screen-based
interface. In some embodiments, the web site or additional software
is activated by clicking on an icon on a virtual desktop.
[0028] Gateway 70 is a general purpose processor is coupled to
controller 40 and data storage unit 60 via data bus 42. In some
embodiments, gateway 70 is controlled by the sending customer
although it is physically at the service provider's premises.
Gateway 70 functions to receive a data file from data storage unit
60 in response to an instruction from controller 40, to convert the
format of the received data file to a different format in response
to another instruction from controller 40, and to provide the
retrieved data file, as selectively converted, to transmitter
50.
[0029] In one embodiment, gateway 70 acts as a digital video
broadcast (DVB)/internet protocol (IP) gateway, handling the
conversion from IP packets to DVB/MPEG II packets. Standards
defining these conversions include "DVB Specification for Data
Broadcasting" (EN 301 192), "Digital Video Broadcasting:
Specification for Service Information in DVB systems" (EN 300 468),
"DVB Guidelines on Implementation and Usage of Service Information"
(ETR 211), "Extension for Digital Storage Media Command and Control
(DSM-CC)--International Standard (IS)" (ISO/IEC 13818-6), and so
on. All of these standards are available at www.dvb.org.
[0030] Compliance with the DVB data broadcast standard requires an
ability to perform Multiprotocol Encapsulation (MPE). MPE defines
how communication protocols in the form of datagrams are
encapsulated in DSM-CC sections that comply with, for example, the
MPEG-II Transport Stream packet format (ISO/IEC 13818-1).
Compliance with EN 300 468 requires insertion of service
information data for self configuration as specified by ETS 300 468
so that program information allowing receivers to automatically
tune themselves to the correct parameters can be placed into MPEG
transponder streams.
[0031] Although use of DVB is described herein, it will be
understood that other protocols may be used such as asynchronous
transfer mode (ATM).
[0032] Gateway 70 is adapted to output multiple program IDs
simultaneously, so that the central system can put multiple
services into a single uplink stream and segment bandwidth for each
customer and service. Gateway 70 supports IP unicasting, IP
multicasting and broadcasting. It also supports IP static and
dynamic routing.
[0033] Data storage unit 60 is a magnetic, optical, transistor,
magneto-optical or other high capacity storage medium, and is
coupled to gateway 70 and controller 40 via data bus 42. Data
storage unit 60 functions to store data files supplied thereto from
controller 40 and to provide the stored files to gateway 70 in
accordance with control commands from controller 40.
[0034] Transmitter 50 is a communication device such as a modem,
and is coupled to earth station 30, controller 40 and gateway 70.
Transmitter 50 is adapted to receive files from gateway 70 and to
provide these files to earth station 30 for transmission on uplink
15 to satellite 10, in accordance with instructions from controller
40. In practice, many transmitters may be used for each satellite,
depending on the frequencies of the uplinks and downlinks on the
satellite. The specific transmitter details are known to those of
ordinary skill in the art and are omitted here for brevity.
[0035] Controller 40 is a general purpose computer programmed
according to the present technique, and is coupled to sending
customer terminal 80, gateway 70, data storage unit 60, transmitter
50 and terrestrial network 20 via appropriate communication
channels. Controller 40 is adapted to receive scheduling orders for
data file pickup and delivery from customer terminal 80 and to send
status notices to customer terminal 80. Controller 40 is further
adapted to retrieve a data file from customer terminal 80 and
transfer it to data storage unit 60; to instruct data storage unit
60 to receive and provide information; and to instruct data storage
unit to 60 supply a data file to gateway 70. Controller 40 is
additionally adapted to communicate with controller 45 to schedule
data file delivery and receive notices from controller 45 relating
to delivered data files. When retrieving a data file from customer
terminal 80, controller 40 serves as a firewall.
[0036] The receiving configuration for an earth station will now be
discussed. Earth station 35A is an example of a receiving earth
station.
[0037] Receiver 55 functions as a standalone DVB/IP receiver,
including a channel interface, a demodulator, a forward error
detection/correction unit and a DVB demultiplexer. The multiplexed
DVB signal may contain multiple program IDs, for carrying unicast,
multicast and broadcast traffic. Receiver 55 performs program ID
filtering, and router-type filtering, that is, receiver 55 only
forwards multicast IP subnetwork traffic for destinations coupled
thereto and discards the remainder, in accordance with Internet
Group Management Protocol (IGMP). In other embodiments, receiver 55
operates according to a format other than DVB.
[0038] Data storage unit 65 functions in a similar manner as data
storage unit 60, and will not be described further for brevity.
[0039] Client 75 is a general purpose computer coupled to receiver
55, data storage unit 65 and controller 45. Client 75 is the
destination for a data file transmitted from customer terminal 80.
Client 75 is adapted to receive data files from data storage unit
65. In some embodiments, client 75 receives data files directly
from receiver 55.
[0040] FIG. 1 shows client 75 and earth station 35A co-located at
customer premises 95. In another embodiment, earth station 35A is
located at service provider destination premises while the
functionality of client 75 is split between the service provider
destination premises and the customer destination premises.
[0041] Controller 45 is coupled to client 75, data storage unit 65,
receiver 55 and terrestrial network 20 via appropriate
communication channels. Controller 45 is adapted to receive
scheduling requests for data file delivery from controller 40 via
terrestrial network 20, to respond thereto based on facilities
availability, to notify receiving customer terminal of a scheduled
delivery, to receive confirmation from client 75 that a data file
has been delivered thereto, and to send notices to controller 40
confirming data file delivery. Controller 45 is further adapted to
instruct receiver 55 to receive a data file from earth station 35A
that has been transmitted on downlink 16 from satellite 10 and
convert the format of the data file, to instruct data storage unit
65 to receive and provide information, and to instruct client 75 to
receive a data file from data storage unit 65.
[0042] FIG. 2 is a flowchart illustrating data file pickup and
delivery. FIG. 2 shows activity occurring at four places: "SEND
CUST"--meaning sending customer terminal 80, "NET XMT"--also
referred to as the system transmitter--meaning earth station 30,
controller 40, data storage unit 60 and gateway 70, "NET RCV"--also
referred to as the system receiver--meaning earth station 35A,
controller 45, receiver 55 and data storage unit 65, and "RCV
CUST"-meaning client 75. In FIG. 2, horizontal arrows indicate
transmission of information between locations, and the vertical
direction indicates time.
[0043] It is assumed that a user has already registered with the
central system. FIG. 3, discussed 11 below, is an example of a
screen-based interface used for registration.
[0044] The process of file pick up and delivery is discussed in
detail below. As an overview, at the scheduled pickup time, the
data file is sent from customer terminal 80 to controller 40. If
necessary, other portions of the data file are sent from other
customer locations to controller 40. Controller 40 stores the data
file in data storage unit 60. When it is time for the data file to
be transmitted, controller 40 retrieves the data file from data
storage unit 60 and transfers the data file to gateway 70 that
converts the file format, for example, to DVB/MPEG II format, and
delivers the converted data file to transmitter 50.
[0045] At the receiving side, receiver 55 receives the data file
via downlink 16, converts its format in accordance with the
scheduled delivery instructions as applied by controller 45, and
delivers the converted data file to client 75. Appropriate
acknowledgement and reporting to controller 40 occurs through the
path of the data file so that its progress can be readily
monitored.
[0046] At step 100, a user at sending customer terminal 80 submits
a scheduling order for file pickup and delivery. FIG. 4, discussed
below, is an example of a screen-based interface for creation of a
scheduling order.
[0047] At step 102, controller 40 of the system transmitter
receives the scheduling order. At step 104, controller 40 checks
whether facilities are available to transmit the data file by
contacting the appropriate ones of gateway 70 and controller 45.
Together, controllers 40 and 45 schedule transmission capacity and
storage capacity at the transmitting and receiving sides of
satellite 10. Generally, storage and conversion of a data file, as
needed, occurs as the transmitting side. In some situations,
depending on facilities availability, it may be preferable to store
and/or convert the data file at the receiving side.
[0048] At step 103, controller 45 receives the availability check
and determines whether it can comply with the requested data file
transfer. Generally, the determination is positive, and at step
105, controller 45 confirms availability, and at step 107 prepares
and sends a delivery notice to client 75 providing notice of a
future data file delivery. If the determination is negative, then
controller 45 replies with what it can accomplish, and controller
40 may send a new availability check. In some embodiments, a
delivery notice is not sent to receiving client 75.
[0049] At step 106, controller 40 receives a positive availability
reply from controller 45, enqueues the file pickup and delivery
order, and, at step 108, prepares and sends an order confirmation
notice to customer terminal 80. At step 110, customer terminal 80
receives the confirmation notice.
[0050] In some embodiments, customer terminal 80 is coupled to
controller 40 via an Internet connection, and the confirmation
notice is received while the user is still at the web site in
communication with controller 40. In one case, controller 40 is
also operative as a web server. In another case, controller 40 is
contacted by one or more web servers and provides hypertext
transfer protocol (HTTP) responses to the web server. In a further
case, the confirmation notice is sent as an electronic mail
(e-mail) message to an e-mail account specified during
registration.
[0051] In other embodiments, customer terminal 80 is coupled to
controller 40 via a circuit switched connection, and the
confirmation notice is received while the user is still at
controller 40, or is sent to an e-mail account specified during
registration.
[0052] When it is time for the file to be picked up, at step 120,
controller 40 obtains the data file from customer terminal 80 via
an appropriate communication channel such as the Internet. At step
122, customer terminal 80 receives the file pickup request, and at
step 124, provides the requested file. At step 126, controller 40
receives the retrieved data file and stores the retrieved file in
data storage unit 60.
[0053] In some embodiments, instead of picking up the file
electronically, the user, also referred to as the customer, may
send the file to controller 40 on a disk or other portable media in
advance of the scheduled pickup time. In some cases, the data file
to be picked up is at a customer location (not shown) other than
customer terminal 80, such as at a transmitting video camera. In
cases where portions of the data file are obtained from different
locations, a different pick up method may be used at each
location.
[0054] In some embodiments, the customer can schedule a file
pickup, and then schedule delivery of the file at a later time such
as after the file has been picked up.
[0055] At step 130, controller 40 instructs gateway 70 to convert
the format of the stored data file, as needed, such as by
separating it into datagram sized packets, separating it into
multicast formatted packets or converting a file into a DVB/MPEG
format file. Format conversion may be required to comply with the
pickup and delivery instructions. Format conversion may be required
by internal service provider transmission format requirements.
Other format conversions will be apparent to those of ordinary
skill.
[0056] At step 132, controller 40 instructs transmitter 50 to
transmit the data file, as converted, on uplink 15 to satellite 10.
The transmission time is selected in view of facility availability,
as scheduled at steps 103-106, and can be substantially before the
scheduled data file delivery time. That is, file buffering can be
performed in the transmit side or the receive side due to the
presence of data storage units 60 and 65. When data storage unit 65
is used as a temporal file buffer, it is akin to a cache.
[0057] At step 133, receiver 55 receives the transmitted data file.
In response to instructions from controller 45, at step 135,
receiver 55 converts the format of the data file and stores the
data file in data storage unit 65.
[0058] When it is time for the file to be delivered, at step 137,
server 45 instructs data storage unit 65 to provide the data file
to client 75. At the completion of the file delivery, client 75
provides a delivery confirmation notice to controller 45.
[0059] At step 141, controller 45 provides a delivery confirmation
notice to controller 40. In one embodiment, the delivery
confirmation notice is sent via terrestrial network 20. In another
embodiment, the delivery confirmation notice is sent via a second
uplink (not shown) from earth station 35A to satellite 10 and then
on a second downlink (not shown) to earth station 30.
[0060] At step 142, controller 40 forwards the delivery
confirmation notice to customer terminal 80, such as by e-mail or
facsimile transmission. At step 144, customer terminal 80 receives
the delivery confirmation notice. At step 146, controller 40
records the successful file delivery in a log for management and
accounting purposes.
[0061] In some embodiments, controller 40 also logs the progress of
the file through the central system at other points so that a user
can check the location and status of the file using, for example, a
screen-based interface (not shown).
[0062] In some embodiments, client 75 employs a screen-based
interface, provided in a similar manner as the screen-based
interface of sending customer terminal 80, that enables client 75
to request inclusion in a multicast group from controller 40 via
controller 45 and terrestrial network 20 or other suitable
communications channel.
[0063] FIG. 3 is a chart showing registration screen 150 for
customer registration. This screen is provided to terminal 80, for
example, when terminal 80 is in communication with an Internet web
site, or has otherwise established a connection with controller 40.
In some embodiments, a separate registration processor is used
instead of controller 40.
[0064] Registration screen 150 contains fields for entry of the
customer's account name, password, e-mail address, billing
information and default file pickup and delivery instructions.
Billing information includes a physical address and payment means,
such as a credit card or authorized credit account. The chart in
FIG. 3 is merely an illustrative example of registration screen
150; other designs and fields will be apparent to those of ordinary
skill in the art.
[0065] Some customers may wish to schedule a regular file pickup
and delivery, for example, a daily corporate news broadcast.
Registration screen 150 allows the customer to specify the file
pickup place or places, such as a directory on customer terminal
80, the format and size of the file to be picked up, the time of
pick up, the frequency of pick up and the priority of the pick up.
For example, a news video file has real-time priority, while low
priority may be appropriate for a financial log or historical video
file. The frequency may be daily, once a week, once a hour and so
on.
[0066] Customers who do not wish to have a regular file pickup and
delivery simply omit default shipping instructions.
[0067] FIG. 4 is a chart showing scheduling order screen 170 for
scheduling data file pickup and delivery, either on a recurring
basis or as a one-time event. Scheduling order screen 170 includes
data entry fields for the customer's account name and password, for
specification of payment information if other than the default
payment method specified at registration is to be used, for
identifying the characteristics of the data file to be picked up,
and its pickup time and frequency, and for identifying the
destination(s) of the data file. The chart in FIG. 4 is merely an
illustrative example of scheduling order screen 170; other designs
and fields will be apparent to those of ordinary skill in the
art.
[0068] As mentioned above, in some embodiments, within a short time
after clicking on submit button 171, a user may get a scheduling
confirmation for the data file pickup. In other embodiments, the
scheduling confirmation is e-mailed to the user.
[0069] Screens (not shown) are also provided for checking on the
status of a scheduled data file pickup, and for modifying a
scheduled data file pickup.
[0070] The screen-based interface described herein allows a user to
manage pick up and delivery of their files without concern for
managing the communication facilities that actually transmit and
receive the data files. Accordingly, the user's network management
burden is reduced.
[0071] The present technique has been described with reference to a
screen-based interface. In a modification, the user device may be
based on audible presentation of information instead of visual,
such as a telephone or terminal providing voice synthesis.
[0072] The system of FIG. 1 is useful for multicasting, distributed
hosting and network caching.
[0073] Multicasting is a session layer protocol built on top of
User Datagram Protocol (UDP). It uses Class D address space, from
224.0.0.0 through 239.255.255.255, to send data from one host to
multiple hosts. A receive host sends an IGMP join message to
routers, or equivalent devices, so that the routers will forward
the traffic to the receiving host. Multicast software for
delivering content reliably in a satellite environment includes
OMNICAST (TM) available from StarBurst Communications in Concord,
MA, and FAZZT (TM), available from KenCast Software in Stamford,
Conn. Additional information on these products is available at
www.starburstcom.com and www.kencast.com. OMNICAST uses a StarBurst
proprietary Multicast File Transfer Protocol (MFTP) to deliver
files to multiple locations. Distributed hosting refers to storing
content from a web site at multiple sites so that the content is
closer to a requesting end user, and thus can be delivered faster.
The system receivers of FIG. 1 are appropriate for supporting
distributed hosting.
[0074] Network caching refers to a configuration wherein data is
stored in caches at various locations, and provided directly from
these locations, thereby eliminating the need to go back to a
central source. Network caching conserves network bandwidth and
reduces the processing load on the central host. More recent
Internet applications are employing cache processing, wherein the
cache performs functions based on the content stored therein, such
as "playing" streaming video from the cache, providing billing
information for pay per view content, modifying file identifiers
for ad insertion, and sending run-time commands to a user for
streaming software. The system receivers of FIG. 1 are appropriate
for supporting distributed hosting.
[0075] The system of FIG. 1 allows a user to create new files,
update existing files or delete files at a master site, and have
these changes automatically reflected at updates to a set of child
sites. Controllers 40 and 45 cooperate to provide version control
and backup at all sites, automatic restoration of damaged files,
priority updating, tailoring data at remote sites, support of
multiple operating systems and hardware configurations and remote
verification.
[0076] Although the present technique has been described with
regard to data files, one of ordinary skill in the art will
appreciate that the system configuration may also be used for
streaming video with suitable modifications to the software
described above.
[0077] Streaming video refers to separating a video signal into
packets which are then sent over the Internet, for example, and
reassembled and displayed at the destination in real time.
Protocols relevant to streaming video include the Internet
Engineering Task Force (IETF) Real Time Transfer Protocol (RTP)
(available as Request for Comments (RFC) 1889), Real Time Control
Protocol (RTCP) (available as RFC 1890) and Real Time Streaming
Protocol (RTSP) (available as RFC 2326). All RFCs are available at
www.ietf.org.
[0078] Although an illustrative embodiment of the present
invention, and various modifications thereof, have been described
in detail herein with reference to the accompanying drawings, it is
to be understood that the invention is not limited to this precise
embodiment and the described modifications, and that various
changes and further modifications may be effected therein by one
skilled in the art without departing from the scope or spirit of
the invention as defined in the appended claims.
* * * * *
References