throbber
Case 1:20-cv-02878-DDD Document 1-1 Filed 09/22/20 USDC Colorado Page 1 of 15
`Case 1:20-cv-02878—DDD Document 1-1 Filed 09/22/20 USDC Colorado Page 1 of 15
`
`Exhibit A
`
`

`

`Case 1:20-cv-02878-DDD Document 1-1 Filed 09/22/20 USDC Colorado Page 2 of 15
`Case 1:20-cv-02878-DDD Document 1—1 Filed 09/22/20 USDC Colorado Page 2 of 15
`
`USOO8856221B2
`
`(12) United States Patent
`US 8,856,221 B2
`(10) Patent N0.:
`Rothschild
`
`(45) Date of Patent: Oct. 7, 2014
`
`(54)
`
`SYSTEM AND METHOD FOR STORING
`BROADCAST CONTENT IN A CLOUD-BASED
`COMPUTING ENVIRONMENT
`
`(56)
`
`References Cited
`
`U.S. PATENT DOCUMENTS
`
`(71) Applicant: Leigh M. Rothschild, Sunny Isles
`Beach, FL (US)
`
`(72)
`
`Inventor: Leigh M. Rothschild, Sunny Isles
`Beach, FL (US)
`
`(*)
`
`Notice:
`
`Subject to any disclaimer, the term of this
`patent is extended or adjusted under 35
`U.S.C. 154(b) by 0 days.
`
`(21)
`
`App1.No.: 13/652,034
`
`(22)
`
`Filed:
`
`Oct. 15, 2012
`
`(65)
`
`(63)
`
`(60)
`
`(51)
`
`(52)
`
`Prior Publication Data
`
`US 2013/0054683 A1
`
`Feb. 28, 2013
`
`Related US. Application Data
`
`Continuation of application No. 13/300,798, filed on
`Nov. 21, 2011, now Pat. No. 8,307,089.
`
`Provisional application No. 61/528,543, filed on Aug.
`29, 2011.
`
`Int. Cl.
`G06F 15/16
`US. Cl.
`
`(2006.01)
`
`USPC ........... 709/203; 709/204; 709/231; 709/226;
`709/249
`
`(58)
`
`Field of Classification Search
`USPC .......................................................... 709/203
`
`6,822,639 B1
`7,496,608 B2
`8,108,441 B2
`2002/0069252 A1
`2003/0014630 A1
`2003/0060264 A1
`2003/0061281 A1
`2005/0021869 A1
`2005/0076220 A1
`2006/0080452 A1
`2010/0217759 A1
`2010/0223385 A1
`2010/0268736 A1
`2010/0332456 A1
`2011/0066687 A1
`
`11/2004 Silverbrook et a],
`2/2009 Wilbrink et 31.
`1/2012 Ruhlen
`6/2002 Jones et a1.
`1/2003 Spencer et al.
`3/2003 Chilton et al.
`3/2003 Miyazaki
`1/2005 Aultman et al.
`4/2005 Zhang et al.
`4/2006 Julia et al.
`8/2010 Ma. et a1.
`9/2010 Gulley et al.
`10/2010 Ruhlen
`12/2010 Prahlad et a1.
`3/2011 Chen et al.
`
`Primary Examiner 7 Hua Fan
`(74) Attorney, Agent, or Firm 7 Atanu Das; Techlaw LLP
`
`ABSTRACT
`(57)
`A system, method and device for media content storage and
`delivery. A server has a receiver in communication with a
`processor. The receiver receives a request message. The
`request message includes media data indicating requested
`media content and a consumer device identifier correspond-
`ing to a consumer device. The processor determines whether
`the consumer device identifier corresponds to a registered
`consumer device. If the processor determines that the con-
`sumer device identifier corresponds to the registered con-
`sumer device, then the processor determines Whether the
`request message is one of a storage request message and a
`content request message. Ifthe request message is the storage
`request message, then the processor is further configured to
`determine whether the requested media content is available
`for storage. If the request message is the content request
`message, then the processor initiates delivery ofthe requested
`media content to the consumer device.
`
`See application file for complete search history.
`
`13 Claims, 7 Drawing Sheets
`
`
`
`Step 5162
`
`Content
`advisory message
`received?
`
`
`Determme available
`content corresponding to
`content advisory message
`
`
`
`
`
`
`Available
`
`Download content
`
`tostoreuaxltenl
`,
`
`. 7
`.
`.
`.-
`
`
`YES
`
`
`
`
`
`$170
`
`St
`
`Sp
`
`Receive
`content request
`"16552992 .
`YES
`
`'
`
`Step 8172
`
`Transmil requested contenl
`
`

`

`r
`Case 1:20-cv-02878-DDD Document 1-1 Filed 09/22/20 USDC Colorado Page 3 of 1551f
`C
`0
`e
`SaC
`0CCDSU0Q
`1..1t
`2
`DDD.m
`9
`
`muP2o1SeU
`
`0e_tVa
`
`8m
`
`n4emm2m7,Dm
`
`0ndebm._HS
`
`270M
`
`mm
`
`d8.,a00
`
`gna2PIIx
`
`023B
`
`
`
`
`H565mm
`mm: :953mmBoEmm53mmEoEmm
`
`....w1n..mwmmwwmmi
`leEEEmcmfi
`mm1960mm
`
`
`
`
`
`m105mm
`
`58805
`
`ow
`
`
`
`Mm30822HBEEmcmt.
`
`mwmnflmol
` m22:8........V.m...1....»_wwm.....
`
`I..............mm103805
`
`
`
`
`
`x
`
`z.....1,,
`
`
`
`\\\\;,,z\\\>//Hx\\\\
`,x.
`
`A{9562
`
`7/_\_\x.H
`
`\AV_\\\
`
`4/
`
`K
`
`
`
`
`
`//\\,/A/_\11l/,,//._
`
`FGE
`
`x
`
`,///,,K.\u\\
`
`\\\w\
`
`
`
`m353mm58385
`
`
`
`@250.mEzwcoo
`
`mm«
`
`
` mm2.622
`oEEEmcmfi.
`mBmwwooi
`am3898
`NNEZmomm
`LmEsmcoO
`52801
`
`
`
`83mm58380
`
`
`
`@25058.350
`
`cm?
`
`
`
`
`
`

`

`Case 1:20-cv-02878-DDD Document 1-1 Filed 09/22/20 USDC Colorado Page 4 of 15
`Case 1:20-cv-02878—DDD Document 1-1 Filed 09/22/20 USDC Colorado Page 4 of 15
`
`U.S. Patent
`
`Oct. 7, 2014
`
`Sheet 2 0”
`
`Us 8’856’221 B2
`
`START
`
`Step S100
`
`Determine Request
`Received
`
`Step
`8104
`Transmit
`registration
`message
`
`
`
`
`“$23522:
`
`from Registered
`User?
`
`Step 3102
`
`Step 8108
`
`Step 8110
`
`Determine Media
`
`Content information
`
`Step S112
`
`Step $114
`
`Step SILLEtsify
`
`Step
`8116
`
`Notify
`Administrator
`
`
`
`
`Step 3124
`Storage
`Content
`
`
`Request Message
`Request Message
`N0
`
`Received?
`Received?
`
`
`
`
`
`
`YES
`Step 8126
`Process Storage
`Search Database for
`
`Stored Content
`Request Message for
`
`Media Data
`Corresponding to
`
`Request
`
`
`
`Determine Media
`Stored Content
`
`Content Characteristics
`Found?
`
`
`Requested
`.
`
`
`Media’Content
`Transmit Stored
`
`Verified?
`Content to Consumer
`Device Corresponding
`
`to Content Request
`Downioad Content
`
`Corresponding to
`
`Storage Request
`Message
`
`
`
`
`
`Store Downloaded
`Content
`
`
`Transmit Confirmation
`
`Message indicating
`Content was Stored
`
`END
`
`FIG. 2
`
`

`

`Case 1:20-cv-02878-DDD Document 1-1 Filed 09/22/20 USDC Colorado Page 5 of 15
`Case 1:20-cv-02878—DDD Document 1-1 Filed 09/22/20 USDC Colorado Page 5 of 15
`
`U.S. Patent
`
`Oct. 7, 2014
`
`Sheet 3 of7
`
`US 8,856,221 B2
`
`Step 8132
`
`
`Transmit
`Transmit
`
`
`Content Request
`Storage Request
`
`
`Message?
`
`
`Step 8136
`
`
`
`Content Received?
` Message
`
`Received?
`
`
`Step 5134
`
`Step 8138
`
`
`
`
`Display Received
`Content
`
`Step 8140
`
`FIG. 3
`
`

`

`Case 1:20-cv-02878-DDD Document 1-1 Filed 09/22/20 USDC Colorado Page 6 of 15
`Case 1:20-cv-02878—DDD Document 1-1 Filed 09/22/20 USDC Colorado Page 6 of 15
`
`U.S. Patent
`
`Oct. 7, 2014
`
`Sheet 4 of7
`
`US 8,856,221 B2
`
`Step S142
`
`Determine Media
`Content Characteristics
`
`Corresponding to
`Requested Content
`
`Step S144
`
`Determine Length of
`Time the Requested
`Content is to be Stored
`
`Step 8146
`
`Apply Charge
`Reduction Factors
`
`Amount Step 8148
`
`Determine a Cost
`
`FIG. 4
`
`

`

`gHmm26am%
`
`02_/B
`
`S$8.5520mUu.
`
`mm
`
`m8n.GE
`
`Case 1:20-cv-02878-DDD Document 1-1 Filed 09/22/20 USDC Colorado Page 7 of 15
`eS
`C
`e
`0Cm
`2
`02
`51f
`C
`
`aU
`
`muP2.1s
`
`0e_tVa
`
`
`
`00$8305“82605Wma
`
`m2m7,DdODcl:flW.528atom
`
`.oEsmcooHBoEwmMn4ml6MW41/oo_>on_.mhgzwcoo
` a1..a$thwlvx83628300
`
`
`._HS
`
`Z7:9.5330M28.3.9_.0”w.....flBaum/7L:INVMm3.50Lossmcoo
`
`
`

`

`Case 1:20-cv-02878-DDD Document 1-1 Filed 09/22/20 USDC Colorado Page 8 of 15
`Case 1:20-cv-02878—DDD Document 1-1 Filed 09/22/20 USDC Colorado Page 8 of 15
`
`U.S. Patent
`
`Oct. 7, 2014
`
`Sheet 6 of7
`
`US 8,856,221 B2
`
`
`
`START
`
`
`
`
`
`Step 8150
`
`Check whether content is
`available
`
`available?
`
`
`
` Content
`Step $152
`
`
`
`
`,
`Available
`
`content corresponds
`
`to content stored in
`server farm?
`
`
`Step 81 54
`
`Step 8156
`
`
`
`Download Content
`
`
`
`Step S158
`
` Content
`
`request message
`received?“ ,
`"
`
`
`
`Transmit requested content
`
`Step 8160
`
`FIG. 6
`
`

`

`Case 1:20-cv-02878-DDD Document 1-1 Filed 09/22/20 USDC Colorado Page 9 of 15
`Case 1:20-cv-02878—DDD Document 1-1 Filed 09/22/20 USDC Colorado Page 9 of 15
`
`U.S. Patent
`
`Oct. 7, 2014
`
`Sheet 7 of7
`
`US 8,856,221 B2
`
`
`
`
` Content
`advisory message
`
`_NO
`
`Step 8162
`
`
` Step 8164
`Determine available
`
`content corresponding to
`
`content advisory message
`
`
`
`
`Available
`
` Step S166
`
`content corresponds
`
`to stored content
`
`I?
`,
`
`
`
`Download content
`
`
`,VuStep 8168
`
`
`
`
`
` Step S170 Receive
`
`content request
`
`
`
`Step S’l 72
`
`messagefl,
`
`Transmit requested content
`
` ’ "’vES
`
`
`FIG. 7
`
`

`

`Case 1:20-cv-02878-DDD Document 1-1 Filed 09/22/20 USDC Colorado Page 10 of 15
`Case 1:20-cv-02878-DDD Document 1-1 Filed 09/22/20 USDC Colorado Page 10 of 15
`
`US 8,856,221 B2
`
`1
`SYSTEM AND METHOD FOR STORING
`BROADCAST CONTENT IN A CLOUD-BASED
`COMPUTING ENVIRONMENT
`
`CROSS-REFERENCE TO RELATED
`APPLICATION
`
`This application is a continuation of US. patent applica-
`tion Ser. No. 13/300,798, filed Nov. 21, 2011, entitled SYS-
`TEM AND METHOD FOR STORING BROADCAST
`CONTENT IN A CLOUD-BASED COMPUTING ENVI-
`
`RONMENT, which is related to and claims priority to US.
`Provisional Patent Application Ser. No. 61/528,543, filed
`Aug. 29, 2011, entitled SYSTEM AND METHOD FOR
`STORING BROADCAST CONTENT AT A REMOTE
`
`SERVER LOCATION the entirety of all of which is incorpo-
`rated herein by reference
`
`STATEMENT REGARDING FEDERALLY
`SPONSORED RESEARCH OR DEVELOPMENT
`
`n/a
`
`FIELD OF THE INVENTION
`
`The present invention relates to a method and system for
`on-demand storage and delivery of media content.
`
`BACKGROUND OF THE INVENTION
`
`The widespread growth of communication networks and
`internet enabled consumer devices allow consumers to stream
`on-demand Videos and music. The on-demand video and
`
`music service is typically provided by large companies or
`second party distributors that store the media content for
`streaming to the consumer devices. For example, a television
`company may maintain a television server that stores all
`television shows that are broadcast by the television company
`such that the consumer may stream the stored television show
`on the consumer device. This requires the television company
`to store all or substantially all the shows broadcast by the
`television company, which requires a great deal of data stor-
`age and often comes at a significant cost to the television
`company. The cost of storing all the broadcast shows is typi-
`cally passed on to the consumer using the on-demand service
`such that the consumer ends up paying for storage of videos
`and music that the consumer has no interest in streaming.
`In particular, the consumer may be charged a flat rate
`monthly subscription fee by the television company. For
`example, the consumer may be charged a ten dollar fee per
`month for streaming videos from the television server. The
`flat rate subscription fee may not change irrespective of
`whether the consumer streams hundreds ofvideos a month or
`
`one Video a month. Consumers that vary the amount of con-
`tent that is streamed monthly may end up paying more money
`for the service than ifthey simply bought the video content on
`digital versatile disk (DVD).
`Some television companies and second party video and
`music distributors offer a flat rate per video or show that is
`streamed. In particular, a consumer may be charged a set fee
`for streaming a specific episode of a television program. For
`example,
`the consumer may be charged five dollars for
`streaming a two hour long episode of a television show to
`their consumer device. However, another consumer will be
`charged the same five dollar flat rate for streaming a fifteen
`minute episode of another television show. The flat rate fee
`associated with a specific video or show that a consumer
`
`10
`
`15
`
`20
`
`25
`
`30
`
`35
`
`4O
`
`45
`
`50
`
`55
`
`60
`
`65
`
`2
`
`wants to stream may end up detracting consumers who do not
`always stream long running episodes of television shows.
`Moreover, consumers may want to stream videos of a par-
`ticular program that may not be currently stored in the tele-
`vision server. The consumer may request the program in order
`for the television server to be updated to store the particular
`program but such a request may take weeks to months to
`fulfill. As such, the consumer may end up losing interest in the
`particular program, and the television server may eventually
`end up being updated with a particular Video that no consum-
`ers stream, thereby unnecessarily expending data resources
`and driving up the cost of the streaming service.
`There is a need in the art for an on-demand media storage
`and streaming system that tailors cost to each consumerbased
`on the requested media content and each consumer’s needs.
`
`SUMMARY OF THE INVENTION
`
`The present invention advantageously provides a method
`and system for on-demand storage and delivery of media
`content.
`
`According to one embodiment, a system for media content
`storage and delivery is provided. The system includes a server
`that has a receiver and a processor. The receiver receives
`media data that indicates media content to be stored. The
`
`processor is in communication with the receiver. The proces-
`sor determines media content characteristics that correspond
`to the media content to be stored. The processor determines a
`length of time to store the media content based on the media
`data and determines a cost amount based at least in part on the
`determined media content characteristics and length of time
`to store the media content.
`
`According to another embodiment, a consumer device is
`provided. The consumer device includes a transmitter that
`transmits a storage request message. The storage request mes-
`sage indicates media content to be stored and the length of
`time the media content is to be stored. The consumer device
`
`includes a receiver that receives a confirmation message. The
`confirmation message indicates the media content is stored at
`the server based at least in part on the storage request mes-
`sage.
`According to yet another embodiment, a method is pro-
`vided for storing and delivering on—demand media content.
`The method includes receiving media data indicating media
`content to be stored. The method includes determining media
`content characteristics that corresponds to the media content
`to be stored. The method includes determining a length of
`time to store the media content based on the media data. The
`
`method includes determining a cost amount based at least in
`part on the determined media content characteristics and
`length of time.
`According to yet another embodiment, a system is pro-
`vided for storing and delivering media content. The system
`includes at least one server. The at least one server includes a
`
`memory that stores media content and a processor. The pro-
`cessor determines media content is available for download,
`determines the media content is not stored in memory and
`initiates download of the media content. The at least one
`server includes a receiver that receives the media content. The
`
`memory stores the received media content.
`According to yet another embodiment, a method is pro-
`vided for storing and delivering media content. A determina-
`tion is made that media content is available for download. A
`determination is made that content is not stored. Download of
`
`

`

`Case 1:20-cv-02878-DDD Document 1-1 Filed 09/22/20 USDC Colorado Page 11 of 15
`Case 1:20-cv-02878-DDD Document 1—1 Filed 09/22/20 USDC Colorado Page 11 of 15
`
`US 8,856,221 B2
`
`3
`the media content is initiated. The media content is received.
`The received media content is stored.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`A more complete understanding of the present invention,
`and the attendant advantages and features thereof, will be
`more readily understood by reference to the following
`detailed description when considered in conjunction with the
`accompanying drawings wherein:
`FIG. 1 is a block diagram of media content on—demand
`storage system constructed in accordance with the principles
`of the present invention;
`FIG. 2 is a flow chart of an exemplary process for process-
`ing a request message for initiating storing and streaming of
`media content;
`FIG. 3 is a flow chart of an exemplary process for initiating
`media content storage and streaming;
`FIG. 4 is a flow chart of an exemplary process for deter-
`mining a cost amount for storing media content;
`FIG. 5 is a block diagram of media content storage for
`on-demand delivery constructed in accordance with the prin-
`ciples of the present invention;
`FIG. 6 is a flow chart of an exemplary process for storing
`and delivering content; and
`FIG. 7 is a flow chart of an exemplary process for storing
`and delivering content.
`
`10
`
`15
`
`20
`
`25
`
`DETAILED DESCRIPTION OF THE INVENTION
`
`30
`
`4
`
`Memory 26 may include non-volatile and volatile memory.
`For example, non-volatile memory may include a hard drive,
`memory stick, flash memory and the like. Also, volatile
`memory may include random access memory and others
`known in the art. Memory 26 may also include request mod-
`ule 28 and consumer database 30. Request module 28
`includes instructions, which when executed by processor 24,
`causes processor 24 to perform the processes described
`herein, such as the request process for consumer device 12,
`discussed in detail with reference to FIG. 3.
`
`Consumer database 30 may store consumer device data,
`consumer data and subscription data, among other data. Con-
`sumer device data may include a device identification num-
`ber, model number and operating system, among other device
`information corresponding to the user of the consumer
`device. Consumer data may include consumer information
`such as addresses, phone numbers, financial institution infor-
`mation and credit/debit card information, among other con-
`sumer information. Subscription data may include subscrip-
`tion identification number and content storage and retrieval
`cost, as discussed in detail with respect to FIG. 4, among other
`subscription information.
`Broadcast server 14 may include a transmitter 32, receiver
`34, processor 36 and memory 38 as with the corresponding
`consumer device 12 components, with size and performance
`being adjusted based on design needs. Processor 36 performs
`functions described herein with respect to broadcast server
`14. Broadcast server 14 may communicate with consumer
`device 12 and/or remote server 16, via network 18. Memory
`38 may include content database 40 that stores/records media
`content, media content characteristics, among other data. For
`example, the stored media content may be video, audio,
`graphical images and the like, and the media content charac-
`teri stics may be media runtime (playback time) of the media
`content, data size of media content, media content availabil-
`ity, media content existence and the like. Media content avail-
`ability may indicate whether the media content is available
`for download, e.g., due to restrictions on the media content.
`Media content existence may indicate whether the media
`content exist, e. g., media content not found because user input
`the wrong movie title.
`Remote server 16 may include transmitter 42, receiver 44,
`processor 46 and memory 48 as with the corresponding con-
`sumer device 12 components, with size and performance
`being adjusted based on design needs. Processor 46 may
`perform functions described herein with respect to remote
`server 16. Memory 48 may include media module 50, media
`database 52 and registration database 54. In particular, media
`module 50 may be computer program instructions, which
`when executed by processor 46, perform the storage and
`streaming processes as discussed with respect to FIG. 2.
`Media database 52 may store media content and media con-
`tent characteristics sirnilar to that stored in content database
`
`40. The media database may store the media content for a
`specific length of time, as discussed with reference to FIG. 2.
`Registration database 54 may store account data correspond-
`ing to one or more consumer devices 12 such as user regis-
`tration data, account
`information, number of consumer
`devices registered to a particular user, user account prefer-
`ences, among other user account data. Alternatively, remote
`server 16 may be part ofa server farm in which the server farm
`stores all available media content, as is discussed in detail
`with respect to FIGS. 5-6.
`An exemplary process for processing a request message to
`initiating storing and/or streaming is described with reference
`to FIG. 2. A list of media content may be provided to the
`consumer and displayed on consumer device display, e.g., via
`
`35
`
`4O
`
`45
`
`The present invention advantageously provides a system
`and method for on—demand storage and streaming of media
`content. Accordingly, the system and method components
`have been represented where appropriate by conventional
`symbols in the drawings, showing only those specific details
`that are pertinent to understanding the embodiments of the
`present invention so as not to obscure the disclosure with
`details that will be readily apparent to those of ordinary skill
`in the art having the benefit of the description herein.
`Referring now to the drawing figures in which like refer-
`ence designators refer to like elements there is shown in FIG.
`1 an exemplary storage and streaming system constructed in
`accordance with the principles of the present invention and
`designated generally as “10.” In particular, system 10 may
`include one or more consumer devices 12a to 1212 (collec-
`tively referred to as “consumer device 12”), one or more
`broadcast servers 14a to Mr: (collectively referred to as
`“broadcast server 14”) and one or more remote servers 16a to
`1611 (collectively referred to as “remote server 16”), commu-
`nicating via network 18 using communication protocols
`known in the art, e.g., Internet Protocol. Also, broadcast
`server 14 and/or remote server 16 may be part of network 18,
`a second network, among other network, e.g., each may form
`or be part of a cloud computing environment (not shown).
`Consumer device 12 may include wired or wireless devices
`such as mobile phones, personal digital assistant devices,
`personal computers,
`laptop computers,
`tablet computers,
`digital video recorders, televisions, digital versatile disc play-
`ers, among other devices that may communicate via network
`18. Consumer device 12 may communicate with network 18
`using communication protocols known in the art. In particu-
`lar, consumer device 12 may include transmitter 20 and
`receiver 22 for transmission and reception of data communi-
`cations over network 18. Processor 24 may include a central 65
`processing unit (CPU) for executing computer program
`instructions stored in memory 26, as is well known in the art.
`
`50
`
`55
`
`60
`
`

`

`Case 1:20-cv-02878-DDD Document 1-1 Filed 09/22/20 USDC Colorado Page 12 of 15
`Case 1:20-cv-02878—DDD Document 1—1 Filed 09/22/20 USDC Colorado Page 12 of 15
`
`US 8,856,221 B2
`
`5
`a website displayed in a web browser. The list of media may
`include content stored in media database 52 and content not
`
`stored in media database 52. Consumer device may request
`content from the list or may request non-listed media content.
`Consumer device 12 initiates the process by transmitting a
`request message to remote server 16 such that remote server
`16 determines that a request message is received (Step S100).
`Remote server 16 determines whether the request message is
`received from a registered user, e.g., received from registered
`consumer device (Step $102). For example, the request mes-
`sage may include consumer data, device identification num-
`ber(s), media data, among other data stored in consumer
`database 30 that corresponds to the specific user and/or con-
`sumer device. Ifthe request message is determined to be from
`a non-registered consumer device, a registration message
`may be sent to the consumer device to prompt the user to
`register the consumer device 12 with remote server 16 (Step
`8104). Once the consumer device is registered, the process
`may continue to Step $106.
`Ifthe request message is determined to be from a registered
`consumer device, remote server 16 processes the request
`message to determine whether the request message is a stor-
`age request message (Step 8106). In particular, the storage
`request message may include media data indicating the con-
`sumer device is requesting that remote server 16 store specific
`media content for an amount of time, e.g., the storage request
`message may have a triggering flag. If the request message is
`a storage request message, the media data in the storage
`request message is processed (Step $108). For example, the
`storage request message may contain media data identifying
`to the requested media content to be stored. The media data
`may include time data that indicates the length of time the
`user wants the media content to be stored. The time data may
`include a start-end date, period of time (e. g., one month, one
`week), end date, among other values and/or characters that
`may indicate a length of time. Remote server 16 may deter-
`mine media content information based on the processed stor-
`age request message, e.g., based on the media data (Step
`$110). The media content information may include a media
`title, media content serial number, or other media identifying
`characters corresponding to the requested media content.
`Remote server 16 may determine the media content char-
`acteristics corresponding to the requested content based on
`the media content information, e.g., based on media data
`(Step $112). For example, the media content information may
`be used to search media database 52 for corresponding media
`content characteristics, e.g., determine media content charac-
`teristics. Alternatively, remote sever 16 may transmit the
`media content information to broadcast server 14. The broad-
`
`cast server 14 may search database 40 for media content
`characteristics corresponding to the received media content
`information. Broadcast server 14 may transmit the media
`content characteristics to remote server 16. Remote server 16
`
`may verify the requested media content based at least in part
`on the media content characteristics, e.g., remote server 16
`verifies the requested media content is available based at least
`in part on the media content characteristics (Step $114). For
`example,
`the media content characteristics may indicate
`whether the requested media content is available for down-
`load and/or whether the requested media content exists. If the
`requested content is not verified, a network administrator may
`be notified (Step $116).
`If the requested media content is verified, remote server 16
`may download the verified media content, e.g., download
`media content corresponding to media data in storage request
`message (Step $118). In particular, remote server 16 may
`download the content from broadcast server 14 via network
`
`6
`18 for storage in media database 52, e.g., broadcast server 14
`delivers media content to remote server 16. For example,
`remote server 1 6 may transmit a download request message to
`broadcast server 14 indicating remote server 16 requests to
`download the verified media content from broadcast server
`14.
`
`Alternatively, remote server 16 may download content
`from consumer device 12 such that consumer device 12 acts
`
`10
`
`as a proxy server, e.g., consumer device 12 serves as an
`intermediary between remote server 16 and broadcast server
`14 or another content server. Broadcast server 14 and remote
`
`15
`
`20
`
`25
`
`30
`
`35
`
`4O
`
`45
`
`50
`
`55
`
`60
`
`65
`
`server 16 may obtain media content from other lntemet con-
`nected devices, community antenna cable television systems
`(CATV), satellite-based systems, and the like. In other words,
`it is contemplated that servers 14 and 16 have access to media
`content that is requested by the consumer. Remote server 16
`may store the downloaded media content in media database
`52 for a length of time determined from the media data, e. g.,
`media data indicates the length of time to store the media
`content (Step 8120). Also, remote server 16 may tag the
`downloaded content to the consumer. For example, the tag
`may link the downloaded content to the specific consumer
`account that requested the downloaded content.
`Remote server 12 may transmit a confirmation message to
`consumer device 12 indicating the content corresponding to
`the storage request message has been stored in media data-
`base 52 (Step $122). The confirmation message may include
`confirmation data indicating the length of time the media
`content is to be stored, size of stored media content, cost
`amount, cost reduction, consumer account number, among
`other data.
`
`Referring back to Step $106, if the request message is
`determined not to be a storage request message, remote server
`16 determines whether the request message is a content
`request message (Step $124).
`In particular,
`the content
`request message may include content request data indicating
`that the consumer wants to stream or download media content
`
`to consumer device 12. For example, the content request
`message data may include the media content title, a triggered
`message flag, consumer account number, mobile identifica-
`tion number, among other data that may be used by remote
`server 16 to identify the requested content. Remote server 16
`may search media database 52 for stored media content cor-
`responding to the content request message (Step $126). In
`particular, the requested media content may include media
`content previously stored in response to a storage request
`message, other stored media content not linked (e. g., tagged)
`to the requesting consumer, among other media content. For
`example, remote server 16 may store media content other
`consumers have requested and may also store premium con-
`tent such as new programming, pay-per view events, and the
`like. In other words, consumer device 12 may transmit a
`content request message corresponding to any content stored
`on media database 52, absent predefined media restrictions
`set by the network administrator or account administrator.
`If no corresponding media content is found in media data-
`base 52 (Step $128), a network administrator and/or the con-
`sumer may be notified (Step 8116). Alternatively, if no cor-
`responding media content
`is found,
`the content request
`message may be processed as a storage request message. For
`example, the content request message may be processed
`according to the storage request message Steps of 8108-8122.
`Continuing the example, after transmitting the confirmation
`message (Step $122), the content request message may then
`be processed as a content request message, e. g., according to
`Steps 8124-8130. If remote server 16 finds the stored media
`content corresponding to the content request message in
`
`

`

`Case 1:20-cv-02878-DDD Document 1-1 Filed 09/22/20 USDC Colorado Page 13 of 15
`Case 1:20-cv-02878—DDD Document 1—1 Filed 09/22/20 USDC Colorado Page 13 of 15
`
`US 8,856,221 B2
`
`7
`media database 52 (Step $128), the corresponding media
`content may be transmitted to consumer device 12 for display
`(Step S130). For example, consumer device 12 may stream
`media content such as digital Video from remote server 16
`and/or may download the requested content.
`An exemplary process for consumer device 12 to initiate
`media content
`storage, download and/or streaming is
`described with reference to FIG. 3. In particular, request
`module 28 determines whether the consumer is requesting to
`store media content, e.g., whether to transmit a storage
`request message (Step S132). The determination may be
`based on a triggering event on consumer device 12 that is
`initiated by the consumer. For example, the triggering event
`may be pushing a record/storage button, voice activated
`record button, selecting media from a media database, among
`other types oftriggering events that cause consumer device 12
`to transmit a storage request message. If the storage request
`message is transmitted via transmitter 20, a determination is
`made as to whether a confirmation message is received (Step
`S134). If no confirmation message has been received, the
`determination of Step S134 is made again. Alternatively, a
`network administrator and/or consumer may be notified that
`no confirmation message has been received (not shown). A
`received confirmation message indicates the transmitted stor-
`age request message was successfully received and processed
`at remote server 16 such that media content corresponding to
`the storage request message is stored in media database 52.
`The confirmation may also include information for display at
`consumer device 12 such as receipt, cost amount, among
`other displayable data.
`Referring back to Step S132, if the determination is made
`not to transmit a storage request message, a determination is
`made as to whether to transmit a content request message
`(Step S136). In particular, the determination of Step $136 is
`made based on a triggering event on consumer device 12
`caused by the consumer. For example, the triggering event
`may be pushing a content request button, voice activated
`content button, among other types of triggering events that
`cause the consumer device 12 to transmit the content request
`message. If the content request message is transmitted via
`transmitter 20, a determination is made as to whether the
`requested media content has been received, e.g., whether the
`consumer device is storing or downloading the requested
`media content (Step $138). Ifthe requested media content has
`not been received, the determination of Step S138 is made
`again. Alternatively, the network administrator and/or con-
`sumer may be notified that the requested content has not been
`received. If it is determined that the requested media content
`has bee

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket