System and method of error reporting in a video distribution network
Summary by NHIP
IP TV error reporting system
The method detects network errors in internet protocol television networks and sends an interface with selectable options to a video display. It prioritizes repairs based on weighted user reports, recording selections, and automatic reports before notifying the set top box of corrections.
Claim Score by NHIP
Abstract
Method, systems and devices for error reporting in a video distribution network are disclosed. A method may include determining that a network communication error has occurred in a video distribution network. The method may also include sending an error reporting interface to a video display. The method may also include receiving a send error report selection via the error reporting interface. In response to receiving the send error report selection, the method may perform at least one action.

Term
Projected expiry 26 September 2029.
- Priority and filed
- Granted
- Today
- Projected expiry
14 claims: 4 independent, 10 dependent
- 1Broadest claimClaim Score 31, narrow(NHIP)A method of error reporting in a video distribution network, the method comprising:determining that a network communication error occurred in an internet protocol television network while distributing video content to a set top box device;sending an error reporting interface to a video display device associated with the set top box device, wherein the error reporting interface includes selectable additional information options comprising a watching television option and a recording a program option;receiving, via the error reporting interface, a selection of one of the additional information options;prioritizing the network communication error for repair based at least in part on a number of user reports of the network communication error, a number of automatically generated reports of the network communication error, and the selected additional information option, wherein the user reports and the automatically generated reports are given different weights when prioritizing the network communication error;sending priority information associated with the network communication error for display via the error reporting interface;after receiving a receive notice of correction selection option via the error reporting interface, sending a notice of correction to the set top box device when the network communication error has been corrected;and instructing a content server to resume distribution of the video content to the set top box device.
- 9A non-transitory computer-readable medium tangibly embodying instructions that when executed by a content server cause the content server to:determine that a network communication error occurred in an internet protocol television network while sending video content to a set top box device;receive one or more user reports of the network communication error;receive a plurality of selections of additional information options from a plurality of users, wherein each selected additional information option indicates an activity of a corresponding user when the network communication error occurred, and wherein the selections of additional information options include at least one watching television option and at least one recording a program option;receive one or more automatically generated reports of the network communication error;prioritize the network communication error for repair based at least in part on a number of the user reports of the network communication error, a number of the automatically generated reports of the network communication error, and the selections of additional information options, wherein the user reports and the automatically generated reports are given different weights when prioritizing the network communication error;receive a receive notice of correction selection at the content server from the set top box device;send a notice of correction from the content server to the set top box device when the network communication error has been corrected;and resume sending the video content from the content server to the set top box device.
- 11A method of error reporting in a video distribution network, the method comprising:receiving one or more automatically generated reports of a first network communication error occurring in an internet protocol television network while distributing video content to a plurality of set top box devices;receiving a plurality of user reports of the first network communication error, at least one of the user reports including a selection of an additional information option received from a user, wherein the selected additional information option indicates an activity of the user when the first network communication error occurred, and wherein the selected additional information option includes at least one of a watching television option and a recording a program option;receiving one or more automatically generated reports of a second network communication error;receiving one or more user reports of the second network communication error;determining a repair priority associated with the first network communication error based on a number of the user reports of the first network communication error, a number of the automatically generated reports of the first network communication error, and the selected additional information option associated with the first network communication error, wherein the user reports of the first network communication error and the automatically generated reports of the first network communication error are given different weights when determining the repair priority associated with the first network communication error;determining a repair priority associated with the second network communication error based on a number of user reports of the second network communication error, a number of automatically generated reports of the second network communication error, and a selected additional information option associated with the second network communication error, wherein the user reports of the second network communication error and the automatically generated reports of the second network communication error are given different weights when determining the repair priority associated with the second network communication error;prioritizing the first network communication error and the second network communication error for repair based at least in part on the repair priority associated with the first network communication error and the repair priority associated with the second network communication error;and instructing a content server to resume distribution of the video content to the plurality of set top box devices.
- 13An error tracking server, comprising:a memory to store: user reports associated with a plurality of network communication errors, at least one of the user reports including a selection of an additional information option received from a user, wherein the selected additional information option indicates an activity of the user when a network communication error occurred, and wherein the selected additional information option comprises at least one of a watching television option and a recording a program option;and reports associated with the plurality of network communication errors that are automatically generated by one or more set top box devices when at least one of the one or more set top box devices is unable to receive video content that is distributed to the one or more set top box devices via an internet protocol television network;and a processor to: prioritize each network communication error of the plurality of network communication errors for repair based at least in part on a number of user reports of a particular network communication error, a number of automatically generated reports of the particular network communication error, and the selected additional information option, wherein the user reports and the automatically generated reports are given different weights when prioritizing the particular network communication error;send a notice of correction to the one or more set top box devices when the particular network communication error has been corrected;and instruct a content server to resume distribution of the video content to the one or more set top box devices.
Independent claims4
77 paragraphs in 4 sections, as filed
FIELD OF THE DISCLOSURE
The present disclosure is generally related to network communications.
BACKGROUND
In a video distribution network, video content is typically sent via a network to a display. For example, video content may be delivered from a source, for example a super hub office, to set-top boxes in viewers' homes. Occasionally, the video distribution network may experience a communication error. Such network communication errors can have a negative impact on user satisfaction with a service provider. Hence, there is a need for an improved system and method of error handling in a video distribution network.
BRIEF DESCRIPTION OF THE DRAWINGS
<figref idrefs="DRAWINGS">FIG. 1</figref> is a block diagram of an embodiment of a video distribution network;
<figref idrefs="DRAWINGS">FIG. 2</figref> is a block diagram of a second embodiment of a video distribution network;
<figref idrefs="DRAWINGS">FIG. 3</figref> is a flow chart of a first exemplary embodiment of a method of error reporting in a video distribution network;
<figref idrefs="DRAWINGS">FIG. 4</figref> is a flow chart of a second exemplary embodiment of a method of error reporting in a video distribution network;
<figref idrefs="DRAWINGS">FIG. 5</figref> is a flow chart of a third exemplary embodiment of a method of error reporting in a video distribution network;
<figref idrefs="DRAWINGS">FIG. 6</figref> is an illustration of a first exemplary embodiment of a graphical user interface to report errors in a video distribution network;
<figref idrefs="DRAWINGS">FIG. 7</figref> is an illustration of a second exemplary embodiment of a graphical user interface to report errors in a video distribution network;
<figref idrefs="DRAWINGS">FIG. 8</figref> is an illustration of a third exemplary embodiment of a graphical user interface to report errors in a video distribution network;
<figref idrefs="DRAWINGS">FIG. 9</figref> is an illustration of a fourth exemplary embodiment of a graphical user interface to report errors in a video distribution network;
<figref idrefs="DRAWINGS">FIG. 10</figref> is a block diagram of an illustrative video distribution system; and
<figref idrefs="DRAWINGS">FIG. 11</figref> is a block diagram of an illustrative general computer system.
DETAILED DESCRIPTION OF THE DRAWINGS
A video device is disclosed that includes a network interface to communicate with a video distribution network. The video device also includes an error report module to send an error report to a remote network device when a network communication error is detected. The video device may also include a user interface module to send a user interface including a send error report option to a video display and to receive a user selection of the send error report option.
A method of error reporting in a video distribution network is also disclosed. The method includes determining that a network communication error has occurred in a video distribution network. The method may also include sending an error report interface to a video display device. The method may also include receiving a send error report selection and performing at least one action in response to receiving the send error report selection.
A method of error reporting in a video distribution network is disclosed that includes receiving at least one first automatically sent error report. The at least one first automatically sent error report may be associated with at least one first network communication error. The method also includes receiving at least one second automatically sent error report. The at least one second automatically sent error report may be associated with at least one second network communication error. The method may also include receiving at least one first user initiated error report. The at least one first user initiated error report may be associated with the at least one first network communication error. The method also includes prioritizing the at least one first network communication error and the at least one second network communication error based on the at least one first automatically sent error report, the at least one second automatically sent error report, and the at least one first user initiated error report.
Referring now to <figref idrefs="DRAWINGS">FIG. 1</figref>, a particular illustrative embodiment of a video distribution network <b>100</b> is shown. The video distribution network <b>100</b> includes a content server <b>102</b> at a super hub office <b>104</b>. In general, a server may include a computing device adapted to execute software applications. Such software applications may include, for example, communication functions, data processing functions, security functions, such as authentication and authorization functions, other functions, or any combination thereof. As used herein, the term “server” is used broadly to refers to a hardware device or software application providing services to another hardware device or software application. The term “server” is not intended to be limited to a single, dedicated hardware device. Rather, a server may include a plurality of hardware devices or software applications operating in parallel or in series to provide the services. Additionally, a server may include or be coupled to a controller, for example, a load-balancer, to control the provision of services.
The content server <b>102</b> communicates with a display <b>120</b> via a communications path <b>108</b>. The communications path <b>108</b> may pass through one or more networks, such as, for example, internet <b>106</b> or a local network <b>112</b>. The video distribution network <b>100</b> may also pass through a video hub office <b>110</b>. In a particular embodiment, the local network <b>112</b> may be a private access network of an internet protocol television (IPTV) network. The video distribution network <b>100</b> may also include a customer premises device, such as set top box (STB) <b>118</b>. The STB <b>118</b> may communicate with one or more displays <b>120</b> of a user <b>122</b>.
While communicating video content from the content server <b>102</b> to the display <b>120</b>, one or more devices of the video content distribution system may undergo a communication error. In a particular embodiment, the video distribution network <b>100</b> may be adapted to report network communication errors. In an illustrative embodiment, the video distribution network <b>100</b> may report network communication errors in response to a user command. For example, after determining that a network communication error has occurred in the video distribution network <b>100</b>, an error reporting interface may be displayed at the display <b>120</b> by the STB <b>118</b>. The STB <b>118</b> may receive a send error report selection from the user <b>122</b>. For example, the user may select an indicator of a send error report option displayed on display <b>120</b>, by using a remote control to communicate with the STB <b>118</b> via the error reporting interface. An example of an error reporting interface is illustrated in <figref idrefs="DRAWINGS">FIG. 6</figref>. In response to receiving the selection, the STB <b>118</b> may perform at least one action, such as closing the send error report selection option window, sending an error report via the video distribution network, sending a notice via the video distribution network that the user has selected the send error report option, presenting a receive notice of correction option on video display <b>120</b>, other actions, or any combination thereof.
<figref idrefs="DRAWINGS">FIG. 2</figref> depicts a particular embodiment of a system to report errors in a video distribution network. The system <b>200</b> includes a video device <b>202</b> in communication with a network <b>226</b>. The network <b>226</b> may include an error tracking server <b>224</b>. The system <b>200</b> also includes a display <b>120</b> and a remote control device <b>220</b> in communication with the video device <b>202</b>.
In a particular embodiment, the video device <b>202</b> may include a network interface <b>204</b>, an error report module <b>206</b>, an error detection module <b>208</b>, logic <b>210</b>, and a user interface module <b>214</b>. The video device <b>202</b> may also include other modules or components to provide other functions provided by the video device. Additionally, the modules may be implemented in hardware or software stored in a memory <b>212</b> of the video device and executable by the logic <b>210</b>. For example, the network interface <b>204</b>, the error report module <b>206</b>, the error detection module <b>208</b>, and/or the user interface module <b>214</b> may include program instructions of one or more application programs executable by the logic <b>210</b>.
In a particular embodiment, the network interface <b>204</b> is configured to communicate with a video distribution network, such as the network <b>226</b>. The network interface <b>204</b> may receive a data stream <b>228</b> that includes video content from the network <b>226</b>. The network interface <b>204</b> may communicate data from the data stream <b>228</b> to the logic <b>210</b> for processing. The logic <b>210</b> may process the video content data and communicate the video content data to the user interface module <b>214</b>.
In a particular embodiment, the error detection module <b>208</b> may be configured to detect when a network communication error has occurred. For example, the error detection module <b>208</b> may determine when the network interface <b>204</b> has lost communications with one or more devices on the network <b>226</b>. Upon detecting a network communication error, the error detection module <b>208</b> may report the network communication error to the logic <b>210</b>. The logic <b>210</b> may initiate the error report module <b>206</b> in response to the error detection module <b>208</b> detecting that a network communication error has occurred.
In a particular embodiment, the error report module <b>206</b> may generate an error report after a network communication error is detected. The error report module <b>206</b> may communicate the error report to the logic <b>210</b>. The logic <b>210</b> may instruct the user interface module <b>214</b> to display an error reporting interface at the display <b>120</b>. The user interface module <b>214</b> may display the error reporting interface at the display <b>120</b> and receive a user selection of an indicator of a send error report option. In response to viewing the error report, a user may interact with the video device <b>202</b> using the remote control device <b>220</b> to send one or more commands to the user interface module <b>214</b>.
In an illustrative embodiment, in response to receiving a user selection of the send error report option, the video device <b>202</b> may take at least one action. For example, the video device <b>202</b> may: end the display of the error reporting interface, send an error report to the error tracking server <b>224</b> via the network <b>226</b>, send a notice of the user selection of the send error report option to the error tracking server <b>224</b>, send a request for a notice of correction to the error tracking server <b>224</b>, take some other action, or any combination thereof.
In a particular embodiment, the video device <b>202</b> may automatically send a network communication error report when a network communication error is detected. For example, the error report module <b>206</b> may be configured to automatically generate and send a network communication error report to the error tracking server <b>224</b> after the error detection module <b>206</b> detects that a network communication error has occurred. In an illustrative embodiment, the video device <b>202</b> may also send a user initiated error report upon receipt of a send error report option selection from a user. In a particular illustrative embodiment, the user initiated error report may include the same contents as the automatic generated and sent error report. In another particular illustrative embodiment, the user initiated error report may include additional information acquired from the user, such as the context surrounding the detection of the network communication error. In another particular illustrative embodiment, the user initiated network communication error report may include an indication that the user has selected the send error report option. In this embodiment, the user initiated network communication error report may not include details about the network communication error. For example, the user initiated network communication error report may include an indication that the user requested that a network communication error report be sent.
<figref idrefs="DRAWINGS">FIG. 3</figref> is a flow chart depicting a first exemplary embodiment of a method of error reporting in a video distribution network. The method <b>300</b> includes determining that a network communication error has occurred, at block <b>302</b>. The method also includes sending an error reporting interface to a display, at block <b>304</b>. For example, the error reporting interface may be displayed to a user on a television display. At block <b>306</b>, the method includes receiving a send error report selection. The method also includes performing at least one action in response to receiving a send error report selection, at block <b>308</b>.
<figref idrefs="DRAWINGS">FIG. 4</figref> is a flow chart depicting a second exemplary embodiment of a method <b>400</b> of error reporting in a video distribution network. The method <b>400</b> includes receiving at least one first automatically sent error report, at block <b>402</b>. The at least one first automatically sent error report may be associated with at least one first network communication error. The method <b>400</b> also includes receiving at least one second automatically sent error report, at block <b>404</b>. The at least one second automatically sent error report may be associated with at least one second network communication error.
The method <b>400</b> also includes receiving at least one user initiated error report, at block <b>406</b>. The at least one user initiated error report may also be associated with the at least one first network communication error. The method <b>400</b> also includes prioritizing the at least one first network communication error and at least one second network communication error for repair, at block <b>408</b>. For example, the at least one first network communication error and the at least one second network communication error may be prioritized for repair based on the at least one first automatically sent error report, the at least one second automatically sent error report, the at least one user initiated error report, or any combination thereof. In an illustrative embodiment, the at least one first network communication error may be assigned a higher priority in response to receiving the at least one user initiated error report.
In a particular embodiment, the at least one user initiated error report may include a plurality of user initiated error reports from a plurality of users. In this embodiment, the at least one first network communication error and the at least one second network communication error may be prioritized for repair based on an aggregation of the plurality of user initiated error reports. In an illustrative embodiment, the network communication errors detected in a video content distribution system may be prioritized for repair based at least in part on the number of users reporting or attempting to report each error.
In another particular illustrative embodiment, the network communication errors detected in a video distribution network may be prioritized for repair based at least in part on both the number of users reporting or attempting to report each error and the number of automatically sent reports. For example, communication errors perceived by users as most urgent and more commonly occurring communication errors to be prioritized higher than other communication errors. In a particular illustrative embodiment, the network communication problem that has generated the most total error reports, including automatically sent error reports and user initiated error reports, may be prioritized highest for repair. In another particular illustrative embodiment, a different weighting may be applied to user initiated error reports than to automatically sent error reports. For example, user initiated error reports may be given a higher weight in prioritizing network communication problems for repair.
<figref idrefs="DRAWINGS">FIG. 5</figref> is a flow chart depicting a third exemplary embodiment of a method of error reporting in a video distribution network. The method <b>500</b> includes determining that a network communication error has occurred, at block <b>502</b>. In a particular embodiment, determining that a network communication error has occurred may include receiving a notice that a remote network device has ceased a requested download, at block <b>504</b>. For example, if a user requests access to video content, a remote network device may determine whether the user is authorized to access the requested video content. If the remote network device determines that the user is not authorized to access the requested video content, the remote network device may issue a notice that the download of the requested video content has been terminated.
In a particular embodiment, the method <b>500</b> may also include automatically generating an error report and sending the error report to a remote network device in response to determining that the network communication error has occurred, at block <b>506</b>. For example, the automatically generated error report may be sent to an error tracking server via a video distribution network <b>536</b>. The error tracking server may keep a record of error reports. In a particular embodiment, the record of error reports may distinguish between error reports that are automatically initiated, and error reports that are user initiated. In an illustrative embodiment, the record of error reports may be used to prioritize network communication problems for repair.
In a particular embodiment, at block <b>508</b>, the method <b>500</b> may also include displaying an error reporting interface at a video display <b>512</b>. The video display <b>512</b> may be in communication with the video distribution network <b>536</b>. In an illustrative embodiment, the error reporting interface may include a selectable option in an error report window, at block <b>510</b>.
In a particular embodiment, the method <b>500</b> may also include receiving a send error report selection, at block <b>514</b>. In a particular illustrative embodiment, the send error report selection may include a command received from a user via a remote control device, at block <b>516</b>.
The method <b>500</b> may also include performing at least one action in response to receiving the send error report selection, at block <b>518</b>. In an illustrative embodiment, the at least one action may include closing the error report window, at block <b>520</b>. In another illustrative embodiment, the at least one action may include generating an error report and sending the error report to a remote network device, at block <b>522</b>. In another illustrative embodiment, the at least one action may include sending data to a remote network device indicating that the user has selected the send error report selection, at block <b>524</b>. In another illustrative embodiment, the method may include automatically generating and sending an error report, as discussed with reference to block <b>506</b>, and the at least one action may include re-sending the automatically generated and sent error report, at block <b>526</b>. In another illustrative embodiment, the at least one action does not include sending an error report to the video distribution network. In another illustrative embodiment, the at least one action may include displaying a receive notice of correction option, at block <b>528</b>. In another illustrative embodiment, the at least one action may include a combination of one or more actions discussed above, or other actions.
In a particular embodiment where the at least one action includes displaying a receive notice of correction option, at block <b>528</b>, the method <b>500</b> may also include receiving a selection of a notice of correction option, at block <b>530</b>. In response to receiving the selection, the network <b>536</b> may send a notice when the network communication error has been corrected. For example, the receive notice of the correction option selection may be received by a STB in communication with the display <b>512</b>. The STB may communicate the selection to a remote network device via network <b>536</b>. The remote network device may store a record of the notice of correction selection, and generate a notice of correction after the network communication error has been corrected. In a particular embodiment, the method <b>500</b> may include receiving the notice of correction at block <b>532</b>, and displaying the notice of correction, at block <b>534</b>.
In a particular embodiment, the steps of the methods described herein may be executed in the order shown by the figures. In alternative embodiments, the steps may be executed in alternative sequences.
<figref idrefs="DRAWINGS">FIG. 6</figref> depicts a first illustrative embodiment of a graphical user interface <b>600</b> to report errors in a video distribution network. The graphical user interface <b>600</b> may include, for example, a display window or screen presented on a television <b>604</b>. The graphical user interface <b>600</b> may also include a do not send error report option <b>606</b>. In a particular embodiment, a send error report option <b>602</b> may be accompanied by an explanation of the error. For example, the graphical user interface <b>600</b> includes an explanation stating that “An error has occurred during transmission of your video content.” In an exemplary embodiment, dotted lines surrounding send error report option <b>602</b> may indicate that the send error report option <b>602</b> has been selected. In response to selection of the send error report option <b>602</b>, a send error report option selection may be generated. For example, referring briefly to <figref idrefs="DRAWINGS">FIG. 2</figref>, the user interface module <b>214</b> of the video device <b>202</b> may generate a send error report selection and communicate the send error report selection to the logic <b>210</b> in response to selection of the send error report option <b>602</b>.
<figref idrefs="DRAWINGS">FIG. 7</figref> depicts a second illustrative embodiment of a graphical user interface <b>700</b> to report errors in a video distribution network. The graphical user interface <b>700</b> may include a user interface screen for gathering additional information from a user. The graphical user interface <b>700</b> may, for example, include a display window or screen presented on the television <b>604</b>. A user may interface with the display via a remote control device in communication with the television or a STB to provide input. In a particular embodiment, the additional information user interface screen may be displayed in response to user selection of a send error report option. The additional information screen may allow the user to provide information that may be sent to a remote network device. In a particular illustrative embodiment, the information may be useful for troubleshooting or prioritizing the network communication error for repair. Information provided through the additional information user interface screen may include, for example, information regarding the context of the network communication error. For example, of the context may include what the user was doing when the network communication error occurred. In an illustrative embodiment, the additional information user interface screen may include a plurality of selectable options, such as a watching television option <b>702</b>, a recording a program option <b>704</b>, an other option <b>706</b> or other options or any combination thereof. The user may select one or more of the selectable options to indicate the context of the network communication error. Selection of the other option <b>706</b> may cause one or more additional selectable options to be displayed.
<figref idrefs="DRAWINGS">FIG. 8</figref> depicts a third illustrative embodiment of a graphical user interface <b>800</b> to report errors in a video distribution network. The graphical user interface <b>800</b> includes a receive notice of correction option <b>802</b>. In response to user selection of the receive notice of correction option <b>802</b>, a message indicating the user's desire to be notified when the network communication error is corrected may be sent to a remote network device. The remote network device may maintain a record of requests for notification of correction of network communication errors, and may send a notification when the network communication error has been corrected.
<figref idrefs="DRAWINGS">FIG. 9</figref> depicts a fourth illustrative embodiment of a graphical user interface <b>900</b> to report errors in a video distribution network. The graphical user interface <b>900</b> includes a confirmation that a service provider, e.g., an IPTV service provider, has been notified of the network communication error. The display <b>900</b> also includes a confirmation that the service provider has been provided with additional details provided by the user.
Referring to <figref idrefs="DRAWINGS">FIG. 10</figref>, an illustrative embodiment of an Internet Protocol Television (IPTV) system generally designated <b>1000</b>. In a particular illustrative embodiment, a video distribution network as discussed above with reference to <figref idrefs="DRAWINGS">FIGS. 1-9</figref>, may include a system such as IPTV system <b>1000</b>. As shown, the system <b>1000</b> can include a client facing tier <b>1002</b>, an application tier <b>1004</b>, an acquisition tier <b>1006</b>, and an operations and management tier <b>1008</b>. Each tier <b>1002</b>, <b>1004</b>, <b>1006</b>, <b>1008</b> is coupled to a private network <b>1010</b>; to a public network <b>1012</b>, such as the Internet; or to both the private network <b>1010</b> and the public network <b>1012</b>. For example, the client-facing tier <b>1002</b> can be coupled to the private network <b>1010</b>. Further, the application tier <b>1004</b> can be coupled to the private network <b>1010</b> and to the public network <b>1012</b>. The acquisition tier <b>1006</b> can also be coupled to the private network <b>1010</b> and to the public network <b>1012</b>. Additionally, the operations and management tier <b>1008</b> can be coupled to the public network <b>1012</b>.
As illustrated in <figref idrefs="DRAWINGS">FIG. 10</figref>, the various tiers <b>1002</b>, <b>1004</b>, <b>1006</b>, <b>1008</b> communicate with each other via the private network <b>1010</b> and the public network <b>1012</b>. For instance, the client-facing tier <b>1002</b> may communicate with the application tier <b>1004</b> and the acquisition tier <b>1006</b> via the private network <b>1010</b>. The application tier <b>1004</b> may communicate with the acquisition tier <b>1006</b> via the private network <b>1010</b>. Further, the application tier <b>1004</b> may communicate with the acquisition tier <b>1006</b> and the operations and management tier <b>1008</b> via the public network <b>1012</b>. Moreover, the acquisition tier <b>1006</b> may communicate with the operations and management tier <b>1008</b> via the public network <b>1012</b>. In a particular embodiment, elements of the application tier <b>1004</b>, including, but not limited to, a client gateway <b>1050</b>, may communicate directly with the client-facing tier <b>1002</b>.
The client-facing tier <b>1002</b> may communicate with user equipment via an access network <b>1066</b>, such as an Internet Protocol Television (IPTV) access network. In an illustrative embodiment, customer premises equipment (CPE) <b>1014</b>, <b>1022</b> can be coupled to a local switch, router, or other device of the access network <b>1066</b>. The client-facing tier <b>1002</b> may communicate with a first representative set-top box device <b>1016</b> via the first CPE <b>1014</b> and with a second representative set-top box device <b>1024</b> via the second CPE <b>1022</b>. In a particular embodiment, the first representative set-top box device <b>1016</b> and the first CPE <b>1014</b> may be located at a first customer premise, and the second representative set-top box device <b>1024</b> and the second CPE <b>1022</b> may be located at a second customer premise. In another particular embodiment, the first representative set-top box device <b>1016</b> and the second representative set-top box device <b>1024</b> may be located at a single customer premise, both coupled to one of the CPE <b>1014</b>, <b>1022</b>. The CPE <b>1014</b>, <b>1022</b> may include routers, local area network devices, modems, such as digital subscriber line (DSL) modems, any other suitable devices for facilitating communication between a set-top box device and the access network <b>1066</b>, or any combination thereof.
In an exemplary embodiment, the client-facing tier <b>1002</b> may be coupled to the CPE <b>1014</b>, <b>1022</b> via fiber optic cables. In another exemplary embodiment, the CPE <b>1014</b>, <b>1022</b> may be digital subscriber line (DSL) modems that are coupled to one or more network nodes via twisted pairs, and the client-facing tier <b>1002</b> may be coupled to the network nodes via fiber-optic cables. Each set-top box device <b>1016</b>, <b>1024</b> may process data received via the access network <b>1066</b>, via an IPTV software platform, such as Microsoft® TV IPTV Edition.
The first set-top box device <b>1016</b> may be coupled to a first external display device, such as a first television monitor <b>1018</b>, and the second set-top box device <b>1024</b> may be coupled to a second external display device, such as a second television monitor <b>1026</b>. Moreover, the first set-top box device <b>1016</b> may communicate with a first remote control <b>1020</b>, and the second set-top box device <b>1024</b> may communicate with a second remote control <b>1028</b>. The set-top box devices <b>1016</b>, <b>1024</b> may include IPTV set-top box devices; video gaming devices or consoles that are adapted to receive IPTV content; personal computers or other computing devices that are adapted to emulate set-top box device functionalities; any other device adapted to receive IPTV content and transmit data to an IPTV system via an access network; or any combination thereof.
In an exemplary, non-limiting embodiment, each set-top box device <b>1016</b>, <b>1024</b> can receive data, video, or any combination thereof, from the client-facing tier <b>1002</b> via the access network <b>1066</b> and render or display the data, video, or any combination thereof, at the display device <b>1018</b>, <b>1026</b> to which it is coupled. In an illustrative embodiment, the set-top box devices <b>1016</b>, <b>1024</b> can include tuners that receive and decode television programming signals or packet streams for transmission to the display devices <b>1018</b>, <b>1026</b>. Further, the set-top box devices <b>1016</b>, <b>1024</b> can include a STB processor <b>1070</b> and a STB memory device <b>1072</b> that is accessible to the STB processor <b>1070</b>. In one embodiment, a computer program, such as the STB computer program <b>1074</b>, can be embedded within the STB memory device <b>1072</b>.
In an illustrative embodiment, the STB computer program <b>1074</b> may include instructions that enable the set-top box devices <b>1024</b> to send a menu of network communication error reporting functions to the display device <b>1026</b>. For example, the set-top box devices <b>1024</b> may present a user with an error reporting interface in response to detecting a network communication error. The error reporting interface may include a menu of stored messages and notifications that the user may select or execute by issuing a command from the remote control device <b>1028</b> to the set-top box devices <b>1024</b>. The STB computer program <b>1074</b> may also include instructions to receive a report of a network communication error, or a report of correction of a network communication error. In response to receiving a report of correction of a network communication error, the set-top box device <b>1024</b> may to transmit a stored notification message or the received notification to the display device <b>1026</b>.
In an illustrative embodiment, the STB computer program <b>1074</b> may also include instructions which enable the set-top box device <b>1024</b> to communicate a network communication error report or an indication of user selection of a report network communication error report option from the set-top box device <b>1024</b> to a remote network device of the IPTV network, such as SNMP monitor server <b>1066</b>.
In an illustrative embodiment, the client-facing tier <b>1002</b> can include a client-facing tier (CFT) switch <b>1030</b> that manages communication between the client-facing tier <b>1002</b> and the access network <b>1066</b> and between the client-facing tier <b>1002</b> and the private network <b>1010</b>. As illustrated, the CFT switch <b>1030</b> is coupled to one or more data servers, such as D-servers <b>1032</b>, that store, format, encode, replicate, or otherwise manipulate or prepare video content for communication from the client-facing tier <b>1002</b> to the set-top box devices <b>1016</b>, <b>1024</b>. The CFT switch <b>1030</b> can also be coupled to a terminal server <b>1034</b> that provides terminal devices with a connection point to the private network <b>1010</b>. In a particular embodiment, the CFT switch <b>1030</b> can be coupled to a video-on-demand (VOD) server <b>1036</b> that stores or provides VOD content imported by the IPTV system <b>1000</b>. Further, the CFT switch <b>1030</b> is coupled to one or more video servers <b>1080</b> that receive video content and transmit the content to the set-top boxes <b>1016</b>, <b>1024</b> via the access network <b>1066</b>.
In an illustrative embodiment, the client-facing tier <b>1002</b> can communicate with a large number of set-top boxes, such as the representative set-top boxes <b>1016</b>, <b>1024</b> over a wide geographic area, such as a metropolitan area, a viewing area, a statewide area, a regional area, a nationwide area or any other suitable geographic area, market area, or subscriber or customer group that can be supported by networking the client-facing tier <b>1002</b> to numerous set-top box devices. In a particular embodiment, the CFT switch <b>1030</b>, or any portion thereof, can include a multicast router or switch that communicates with multiple set-top box devices via a multicast-enabled network.
As illustrated in <figref idrefs="DRAWINGS">FIG. 10</figref>, the application tier <b>1004</b> can communicate with both the private network <b>1010</b> and the public network <b>1012</b>. The application tier <b>1004</b> can include a first application tier (APP) switch <b>1038</b> and a second APP switch <b>1040</b>. In a particular embodiment, the first APP switch <b>1038</b> can be coupled to the second APP switch <b>1040</b>. The first APP switch <b>1038</b> can be coupled to an application server <b>1042</b> and to an OSS/BSS gateway <b>1044</b>. In a particular embodiment, the application server <b>1042</b> can provide applications to the set-top box devices <b>1016</b>, <b>1024</b> via the access network <b>1066</b>, which enable the set-top box devices <b>1016</b>, <b>1024</b> to provide functions, such as interactive program guides, video gaming, display, messaging, processing of VOD material and other IPTV content, etc. In an illustrative embodiment, the application server <b>1042</b> can provide location information to the set-top box devices <b>1016</b>, <b>1024</b>. In a particular embodiment, the OSS/BSS gateway <b>1044</b> includes operation systems and support (OSS) data, as well as billing systems and support (BSS) data. In one embodiment, the OSS/BSS gateway <b>1044</b> can provide or restrict access to an OSS/BSS server <b>1064</b> that stores operations and billing systems data.
The second APP switch <b>1040</b> can be coupled to a domain controller <b>1046</b> that provides Internet access, for example, to users at their computers <b>1068</b> via the public network <b>1012</b>. For example, the domain controller <b>1046</b> can provide remote Internet access to IPTV account information, e-mail, personalized Internet services, messaging services or other online services via the public network <b>1012</b>. In addition, the second APP switch <b>1040</b> can be coupled to a subscriber and system store <b>1048</b> that includes account information, such as account information that is associated with users who access the IPTV system <b>1000</b> via the private network <b>1010</b> or the public network <b>1012</b>. In an illustrative embodiment, the subscriber and system store <b>1048</b> can store subscriber or customer data and create subscriber or customer profiles that are associated with IP addresses, stock-keeping unit (SKU) numbers, other identifiers, or any combination thereof, of corresponding set-top box devices <b>1016</b>, <b>1024</b>. In another illustrative embodiment, the subscriber and system store can store data associated with capabilities of set-top box devices associated with particular customers.
In a particular embodiment, the application tier <b>1004</b> can include a client gateway <b>1050</b> that communicates data directly to the client-facing tier <b>1002</b>. In this embodiment, the client gateway <b>1050</b> can be coupled directly to the CFT switch <b>1030</b>. The client gateway <b>1050</b> can provide user access to the private network <b>1010</b> and the tiers coupled thereto. In an illustrative embodiment, the set-top box devices <b>1016</b>, <b>1024</b> can access the IPTV system <b>1000</b> via the access network <b>1066</b>, using information received from the client gateway <b>1050</b>. User devices can access the client gateway <b>1050</b> via the access network <b>1066</b>, and the client gateway <b>1050</b> can allow such devices to access the private network <b>1010</b> once the devices are authenticated or verified. Similarly, the client gateway <b>1050</b> can prevent unauthorized devices, such as hacker computers or stolen set-top box devices from accessing the private network <b>1010</b>, by denying access to these devices beyond the access network <b>1066</b>.
For example, when the first representative set-top box device <b>1016</b> accesses the client-facing tier <b>1002</b> via the access network <b>1066</b>, the client gateway <b>1050</b> can verify subscriber information by communicating with the subscriber and system store <b>1048</b> via the private network <b>1010</b>. Further, the client gateway <b>1050</b> can verify billing information and status by communicating with the OSS/BSS gateway <b>1044</b> via the private network <b>1010</b>. In one embodiment, the OSS/BSS gateway <b>1044</b> can transmit a query via the public network <b>1012</b> to the OSS/BSS server <b>1064</b>. After the client gateway <b>1050</b> confirms subscriber and/or billing information, the client gateway <b>1050</b> can allow the set-top box device <b>1016</b> to access IPTV content and VOD content at the client-facing tier <b>1002</b>. If the client gateway <b>1050</b> cannot verify subscriber information for the set-top box device <b>1016</b>, e.g., because it is connected to an unauthorized twisted pair, the client gateway <b>1050</b> can block transmissions to and from the set-top box device <b>1016</b> beyond the access network <b>1066</b>.
As indicated in <figref idrefs="DRAWINGS">FIG. 10</figref>, the acquisition tier <b>1006</b> includes an acquisition tier (AQT) switch <b>1052</b> that communicates with the private network <b>1010</b>. The AQT switch <b>1052</b> can also communicate with the operations and management tier <b>1008</b> via the public network <b>1012</b>. In a particular embodiment, the AQT switch <b>1052</b> can be coupled to a live acquisition server <b>1054</b> that receives or acquires television content, movie content, advertisement content, other video content, or any combination thereof, from a broadcast service <b>1056</b>, such as a satellite acquisition system or satellite head-end office. In a particular embodiment, the live acquisition server <b>1054</b> can transmit content to the AQT switch <b>1052</b>, and the AQT switch <b>1052</b> can transmit the content to the CFT switch <b>1030</b> via the private network <b>1010</b>.
In an illustrative embodiment, content can be transmitted to the D-servers <b>1032</b>, where it can be encoded, formatted, stored, replicated, or otherwise manipulated and prepared for communication from the video server(s) <b>1080</b> to the set-top box devices <b>1016</b>, <b>1024</b>. The CFT switch <b>1030</b> can receive content from the video server(s) <b>1080</b> and communicate the content to the CPE <b>1014</b>, <b>1022</b> via the access network <b>1066</b>. The set-top box devices <b>1016</b>, <b>1024</b> can receive the content via the CPE <b>1014</b>, <b>1022</b>, and can transmit the content to the television monitors <b>1018</b>, <b>1026</b>. In an illustrative embodiment, video or audio portions of the content can be streamed to the set-top box devices <b>1016</b>, <b>1024</b>.
Further, the AQT switch <b>1052</b> can be coupled to a video-on-demand importer server <b>1058</b> that receives and stores television or movie content received at the acquisition tier <b>1006</b> and communicates the stored content to the VOD server <b>1036</b> at the client-facing tier <b>1002</b> via the private network <b>1010</b>. Additionally, at the acquisition tier <b>1006</b>, the video-on-demand (VOD) importer server <b>1058</b> can receive content from one or more VOD sources outside the IPTV system <b>1000</b>, such as movie studios and programmers of non-live content. The VOD importer server <b>1058</b> can transmit the VOD content to the AQT switch <b>1052</b>, and the AQT switch <b>1052</b>, in turn, can communicate the material to the CFT switch <b>1030</b> via the private network <b>1010</b>. The VOD content can be stored at one or more servers, such as the VOD server <b>1036</b>.
When users issue requests for VOD content via the set-top box devices <b>1016</b>, <b>1024</b>, the requests can be transmitted over the access network <b>1066</b> to the VOD server <b>1036</b>, via the CFT switch <b>1030</b>. Upon receiving such requests, the VOD server <b>1036</b> can retrieve the requested VOD content and transmit the content to the set-top box devices <b>1016</b>, <b>1024</b> across the access network <b>1066</b>, via the CFT switch <b>1030</b>. The set-top box devices <b>1016</b>, <b>1024</b> can transmit the VOD content to the television monitors <b>1018</b>, <b>1026</b>. In an illustrative embodiment, video or audio portions of VOD content can be streamed to the set-top box devices <b>1016</b>, <b>1024</b>.
<figref idrefs="DRAWINGS">FIG. 10</figref> further illustrates that the operations and management tier <b>1008</b> can include an operations and management tier (OMT) switch <b>1060</b> that conducts communication between the operations and management tier <b>1008</b> and the public network <b>1012</b>. In the embodiment illustrated by <figref idrefs="DRAWINGS">FIG. 10</figref>, the OMT switch <b>1060</b> is coupled to a TV<b>2</b> server <b>1062</b>. Additionally, the OMT switch <b>1060</b> can be coupled to an OSS/BSS server <b>1064</b> and to a simple network management protocol (SNMP) monitor <b>1086</b> that monitors network devices within or coupled to the IPTV system <b>1000</b>. In a particular embodiment, the OMT switch <b>1060</b> can communicate with the AQT switch <b>1052</b> via the public network <b>1012</b>.
In an illustrative embodiment, the live acquisition server <b>1054</b> can transmit content to the AQT switch <b>1052</b>, and the AQT switch <b>1052</b>, in turn, can transmit the content to the OMT switch <b>1060</b> via the public network <b>1012</b>. In this embodiment, the OMT switch <b>1060</b> can transmit the content to the TV<b>2</b> server <b>1062</b> for display to users accessing the user interface at the TV<b>2</b> server <b>1062</b>. For example, a user can access the TV<b>2</b> server <b>1062</b> using a personal computer <b>1068</b> coupled to the public network <b>1012</b>.
In conjunction with the configuration of structure described herein, the system and method disclosed provide error reporting in a video distribution network. In a particular embodiment, a video device detects a communication error. The video device presents a send error report option to a user via a video display. If the user selects the send error report option, the video device receives the send error report selection, and performs at least one action in response to receiving the selection.
Referring to <figref idrefs="DRAWINGS">FIG. 11</figref>, an illustrative embodiment of a general computer system is shown and is designated <b>1100</b>. The computer system <b>1100</b> can include a set of instructions that can be executed to cause the computer system <b>1100</b> to perform any one or more of the methods or computer based functions disclosed herein. The computer system <b>1100</b> may operate as a standalone device or may be connected, e.g., using a network, to other computer systems or peripheral devices, such as a STB, or network server, as illustrated in <figref idrefs="DRAWINGS">FIGS. 1</figref>, <b>2</b>, and <b>10</b>.
In a networked deployment, the computer system may operate in the capacity of a server or as a client user computer in a server-client user network environment, or as a peer computer system in a peer-to-peer (or distributed) network environment. The computer system <b>1100</b> can also be implemented as or incorporated into various devices, such as a personal computer (PC), a tablet PC, a set-top box (STB), a personal digital assistant (PDA), a mobile device, a palmtop computer, a laptop computer, a desktop computer, a communications device, a wireless telephone, a land-line telephone, a control system, a camera, a scanner, a facsimile machine, a printer, a pager, a personal trusted device, a web appliance, a network router, switch or bridge, or any other machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine. In a particular embodiment, the computer system <b>1100</b> can be implemented using electronic devices that provide voice, video or data communication. Further, while a single computer system <b>1100</b> is illustrated, the term “system” shall also be taken to include any collection of systems or sub-systems that individually or jointly execute a set, or multiple sets, of instructions to perform one or more computer functions.
As illustrated in <figref idrefs="DRAWINGS">FIG. 11</figref>, the computer system <b>1100</b> may include a processor <b>1102</b>, e.g., a central processing unit (CPU), a graphics processing unit (GPU), or both. Moreover, the computer system <b>1100</b> can include a main memory <b>1104</b> and a static memory <b>1106</b>, that can communicate with each other via a bus <b>1108</b>. As shown, the computer system <b>1100</b> may further include a video display unit <b>1110</b>, such as a liquid crystal display (LCD), an organic light emitting diode (OLED), a flat panel display, a solid state display, or a cathode ray tube (CRT). Additionally, the computer system <b>1100</b> may include an input device <b>1112</b>, such as a keyboard, and a cursor control device <b>1114</b>, such as a mouse. The computer system <b>1100</b> can also include a disk drive unit <b>1116</b>, a signal generation device <b>1118</b>, such as a speaker or remote control, and a network interface device <b>1120</b>.
In a particular embodiment, as depicted in <figref idrefs="DRAWINGS">FIG. 11</figref>, the disk drive unit <b>1116</b> may include a computer-readable medium <b>1122</b> in which one or more sets of instructions <b>1124</b>, e.g. software, can be embedded. Further, the instructions <b>1124</b> may embody one or more of the methods or logic as described herein. In a particular embodiment, the instructions <b>1124</b> may reside completely, or at least partially, within the main memory <b>1104</b>, the static memory <b>1106</b>, and/or within the processor <b>1102</b> during execution by the computer system <b>1100</b>. The main memory <b>1104</b> and the processor <b>1102</b> also may include computer-readable media.
In an alternative embodiment, dedicated hardware implementations, such as application specific integrated circuits, programmable logic arrays and other hardware devices, can be constructed to implement one or more of the methods described herein. Applications that may include the apparatus and systems of various embodiments can broadly include a variety of electronic and computer systems. One or more embodiments described herein may implement functions using two or more specific interconnected hardware modules or devices with related control and data signals that can be communicated between and through the modules, or as portions of an application-specific integrated circuit. Accordingly, the present system encompasses software, firmware, and hardware implementations.
In accordance with various embodiments of the present disclosure, the methods described herein may be implemented by software programs executable by a computer system. Further, in an exemplary, non-limited embodiment, implementations can include distributed processing, component/object distributed processing, and parallel processing. Alternatively, virtual computer system processing can be constructed to implement one or more of the methods or functionality as described herein.
The present disclosure contemplates a computer-readable medium that includes instructions <b>1124</b> or receives and executes instructions <b>1124</b> responsive to a propagated signal, so that a device connected to a network <b>1126</b> can communicate voice, video or data over the network <b>1126</b>. Further, the instructions <b>1124</b> may be transmitted or received over the network <b>1126</b> via the network interface device <b>1120</b>.
While the computer-readable medium is shown to be a single medium, the term “computer-readable medium” includes a single medium or multiple media, such as a centralized or distributed database, and/or associated caches and servers that store one or more sets of instructions. The term “computer-readable medium” shall also include any medium that is capable of storing, encoding or carrying a set of instructions for execution by a processor or that cause a computer system to perform any one or more of the methods or operations disclosed herein.
In a particular non-limiting, exemplary embodiment, the computer-readable medium can include a solid-state memory such as a memory card or other package that houses one or more non-volatile read-only memories. Further, the computer-readable medium can be a random access memory or other volatile re-writable memory. Additionally, the computer-readable medium can include a magneto-optical or optical medium, such as a disk or tapes or other storage device to capture carrier wave signals such as a signal communicated over a transmission medium. A digital file attachment to an e-mail or other self-contained information archive or set of archives may be considered a distribution medium that is equivalent to a tangible storage medium. Accordingly, the disclosure is considered to include any one or more of a computer-readable medium or a distribution medium and other equivalents and successor media, in which data or instructions may be stored.
Although the present specification describes components and functions that may be implemented in particular embodiments with reference to particular standards and protocols, the invention is not limited to such standards and protocols. For example, standards for Internet and other packet switched network transmission (e.g., TCP/IP, UDP/IP, HTML, HTTP) represent examples of the state of the art. Such standards are periodically superseded by faster or more efficient equivalents having essentially the same functions. Accordingly, replacement standards and protocols having the same or similar functions as those disclosed herein are considered equivalents thereof.
The illustrations of the embodiments described herein are intended to provide a general understanding of the structure of the various embodiments. The illustrations are not intended to serve as a complete description of all of the elements and features of apparatus and systems that utilize the structures or methods described herein. Many other embodiments may be apparent to those of skill in the art upon reviewing the disclosure. Other embodiments may be utilized and derived from the disclosure, such that structural and logical substitutions and changes may be made without departing from the scope of the disclosure. Additionally, the illustrations are merely representational and may not be drawn to scale. Certain proportions within the illustrations may be exaggerated, while other proportions may be minimized. Accordingly, the disclosure and the figures are to be regarded as illustrative rather than restrictive.
One or more embodiments of the disclosure may be referred to herein, individually and/or collectively, by the term “invention” merely for convenience and without intending to voluntarily limit the scope of this application to any particular invention or inventive concept. Moreover, although specific embodiments have been illustrated and described herein, it should be appreciated that any subsequent arrangement designed to achieve the same or similar purpose may be substituted for the specific embodiments shown. This disclosure is intended to cover any and all subsequent adaptations or variations of various embodiments. Combinations of the above embodiments, and other embodiments not specifically described herein, will be apparent to those of skill in the art upon reviewing the description.
The Abstract of the Disclosure is provided to comply with 37 C.F.R. §1.72(b) and is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the foregoing Detailed Description, various features may be grouped together or described in a single embodiment for the purpose of streamlining the disclosure. This disclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter may be directed to less than all of the features of any of the disclosed embodiments. Thus, the following claims are incorporated into the Detailed Description, with each claim standing on its own as defining separately claimed subject matter.
The above disclosed subject matter is to be considered illustrative, and not restrictive, and the appended claims are intended to cover all such modifications, enhancements, and other embodiments which fall within the true spirit and scope of the present invention. Thus, to the maximum extent allowed by law, the scope of the present invention is to be determined by the broadest permissible interpretation of the following claims and their equivalents, and shall not be restricted or limited by the foregoing detailed description.
Contents4
10 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8 Sheet 9 Sheet 10
Every citation, both waysCites: the store holds 15 of 16
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US11082323B2 | Cited by | United States of America | Applicant |
| US10548036B2 | Cited by | United States of America | Search report |
| US2012322367A1 | Cited by | United States of America | Pre-grant |
| US2017230850A1 | Cited by | United States of America | Search report |
| US9325378B2 | Cited by | United States of America | Search report |
| US2017230850A1 | Cited by | United States of America | Pre-grant |
| US2006030316A1 | Cites | United States of America | Search report |
| US2006253760A1 | Cites | United States of America | Search report |
| US2007058043A1 | Cites | United States of America | Search report |
| US2008005281A1 | Cites | United States of America | Search report |
| US2008046786A1 | Cites | United States of America | Search report |
| US2008066128A1 | Cites | United States of America | Search report |
| US2008069002A1 | Cites | United States of America | Search report |
| US2008320338A1 | Cites | United States of America | Search report |
| US5818440A | Cites | United States of America | Search report |
| US5984178A | Cites | United States of America | Search report |
| US6983362B1 | Cites | United States of America | Applicant |
| US7036052B2 | Cites | United States of America | Applicant |
| US7444551B1 | Cites | United States of America | Search report |
| US7610296B2 | Cites | United States of America | Search report |
| US7634797B2 | Cites | United States of America | Search report |
| Tony Northrup, "Using Microsoft Online Crash Analysis," Oct. 6, 2003, pp. 1-4. | Non-patent | – | Applicant |
| Microsoft, "Microsoft Online Crash Analysis" 2006 https://oca.microsoft.com/en/welcome.aspx. | Non-patent | – | Applicant |
2 members in 1 office
Priority claims2
| Document | Office | Kind | Date |
|---|---|---|---|
| 58883606 | United States of America | A | |
| US20060588836 | – | – | – |
Members2
| Document | Office | Kind | |
|---|---|---|---|
| US2008104454A1 | United States of America | A1 | |
| US8713621B2This record | United States of America | B2 |
62 transactions on the USPTO file
Allowed after 3 non-final rejections, 3 final rejections and 3 RCEs.
- Non-final rejections
- 3
- Final rejections
- 3
- RCEs
- 3
- Appeals
- 0
Over time
Point at a mark for the transactionTransactions
| Event | Code | |
|---|---|---|
| Expire PatentEXP. | EXP. | |
| Maintenance Fee Reminder MailedREM. | REM. | |
| Recordation of Patent Grant MailedPGM/ | PGM/ | |
| Patent Issue Date Used in PTA CalculationAllowedPTAC | PTAC | |
| Issue Notification MailedAllowedWPIR | WPIR | |
| Dispatch to FDCD1935 | D1935 | |
| Application Is Considered Ready for IssuePILS | PILS | |
| Issue Fee Payment VerifiedN084 | N084 | |
| Issue Fee Payment ReceivedIFEE | IFEE | |
| Mail Notice of AllowanceAllowedMN/=. | MN/=. | |
| Notice of Allowance Data Verification CompletedAllowedN/=. | N/=. | |
| Reasons for AllowanceEX.R | EX.R | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Disposal for a RCE / CPA / R129AbandonedABN9 | ABN9 | |
| Request for Continued Examination (RCE)RCEX | RCEX | |
| Workflow - Request for RCE - BeginBRCE | BRCE | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Disposal for a RCE / CPA / R129AbandonedABN9 | ABN9 | |
| Request for Continued Examination (RCE)RCEX | RCEX | |
| Workflow - Request for RCE - BeginBRCE | BRCE | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Disposal for a RCE / CPA / R129AbandonedABN9 | ABN9 | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Request for Continued Examination (RCE)RCEX | RCEX | |
| Workflow - Request for RCE - BeginBRCE | BRCE | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Correspondence Address ChangeC.ADB | C.ADB | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| PG-Pub Issue NotificationPG-ISSUE | PG-ISSUE | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Transfer Inquiry to GAUTI1050 | TI1050 | |
| Transfer Inquiry to GAUTI1050 | TI1050 | |
| IFW TSS Processing by Tech Center CompleteTSSCOMP | TSSCOMP | |
| Application Dispatched from OIPEOIPE | OIPE | |
| Application Is Now CompleteCOMP | COMP | |
| Payment of additional filing fee/PreexamFLFEE | FLFEE | |
| A statement by one or more inventors satisfying the requirement under 35 USC 115, Oath of the ApplicOATHDECL | OATHDECL | |
| Notice Mailed--Application Incomplete--Filing Date AssignedINCD | INCD | |
| Cleared by OIPE CSRL194 | L194 | |
| IFW Scan & PACR Auto Security ReviewSCAN | SCAN | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Initial Exam Team nnIEXX | IEXX |
6 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Lapsed due to failure to pay maintenance feeLapsedFP | FP | |
| Lapse for failure to pay maintenance feesLapsedPATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.)LAPS | LAPS | |
| Information on status: patent discontinuationPATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362STCH | STCH | |
| Fee payment procedureMAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.)FEPP | FEPP | |
| Fee payment procedurePAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP | FEPP | |
| AssignmentAS | AS |
Numbers
- Publication
- 08713621
- Publication, DOCDB
- 8713621
- Publication, EPODOC
- US8713621
- Application
- 11588836
- Application, DOCDB
- 58883606
- Application, EPODOC
- US20060588836
Titles
- English
- System and method of error reporting in a video distribution network
Patent term adjustment
- A delay
- +1,065 daysthe office missed an examination deadline
- Net adjustment
- 1,065 days
Classification
- CPC, 10
- H04N21/443
- H04L1/0061
- H04L2001/0093
- H04N21/2225
- H04N21/2404
- H04N21/44209
- H04N21/4425
- H04N21/6371
- H04N21/64322
- H04N21/6473
- IPC, 2
- G06F11 00
- H04N7 173
- USPC, 3
- 725107000
- 714027000
- 714047100