throbber
PTO/AIA/14 (11-15)
`Approved for use through 04/30/2017. OMB 0651-0032
`U.S. Patent and Trademark Office; U.S. DEPARTMENT OF COMMERCE
`Under the Paperwork Reduction Act of 1995, no persons are required to respond to a collection of information unless it contains a valid OMB control number.
`
`
`Attorney Docket Number|FXT315CONS
`
`Application Data Sheet 37 CFR 1.76
`
`
`
`Application Number
`
`SOFTWARE APPLICATION FOR A MOBILE DEVICE TO WIRELESSLY MANAGE OR WIRELESSLY SETUP
`Title of Invention|an OUTPUT SYSTEM OR OUTPUT DEVICE FOR SERVICE
`
`
`
`
`
`The application data sheetis part of the provisional or nonprovisional application for whichit is being submitted. The following form contains the
`bibliographic data arranged in a format specified by the United States Patent and Trademark Office as outlined in 37 CFR 1.76.
`This document may be completed electronically and submitted to the Office in electronic format using the Electronic Filing System (EFS) or the
`document may be printed and included in a paperfiled application.
`
`Secrecy Order 37 CFR 5.2:
`
`Og Portions or all of the application associated with this Application Data Sheet may fall under a Secrecy Order pursuant to
`37 CFR 5.2 (Paperfilers only. Applications that fall under Secrecy Order may notbe filed electronically.)
`
`Inventor Information:
`
`{1
`
`Remove
`
`Inventor
`Legal Name
`
`
`
`Mailing Addressof Inventor:
`
`
`P.O. Box 87237
`
`|
`
`Address 1
`Address 2
`| A
`State/Province
`| ancouver
`City
`
`Postal Code | 98687|Countryi—_—‘|us
`Inventor
`[2
`Legal Name
`
`
`Prefix| Given Name
`Middle Name
`“I
`
`
`Family Name
`
`
`
`
`
`Address 1
`
`
`
`
`Address 2
`
`State/Province
`
`
`
`Postal Code
`Country i
`| ps
`
`Inventor
`All
`Inventors Must Be Listed - Additional
`Information blocks may be
`generatedwithin this form by selecting the Add button.
`
`CorrespondenceInformation:
`
`Enter either Customer Numberor complete the Correspondence Information section below.
`Forfurther information see 37 CFR 1.33(a).
`
`ROKU EXH. 1003
`
`EFS Web 2.2.12
`
`- 1 -
`
`
`
`
`
`ROKU EXH. 1003
`
`-1-
`
`

`

`PTO/AIA/14 (11-15)
`Approved for use through 04/30/2017. OMB 0651-0032
`U.S. Patent and Trademark Office; U.S. DEPARTMENT OF COMMERCE
`Underthe Paperwork Reduction Act of 1995, no persons are required to respond to a collection of information unless it contains a valid OMB control number.
` Application Data Sheet 37 CFR 1.76
`
`Attorney Docket Number|FXT315CON8
`
`
`
`SOFTWARE APPLICATION FOR A MOBILE DEVICE TO WIRELESSLY MANAGE OR WIRELESSLY SETUP
`
`Title of Invention
`AN OUTPUT SYSTEM OR OUTPUT DEVICE FOR SERVICE
`
`Application Number
`
`[] An Addressis being provided for the correspondence Information of this application.
`
`
`
`
`
`
`
`
`Only complete this section whenfiling an application by reference under 35 U.S.C. 111(c) and 37 CFR 1.57{a). Do not complete this section if
`application papers including a specification and any drawings are beingfiled. Any domestic benefit or foreign priority information must be
`provided in the appropriate section(s) below(i.e., "Domestic Benefit/National Stage Information’ and “Foreign Priority Information”).
`
`i
`
`
`
`Attorney Docket Number|a SmallEntityStatusClaimed
`
`
`
`
`Rowena!
` Application Type
`
`
`
`by
`
`Subject Matter
`
`4|Suggested Figure for Publication (if any) no|
`
`
`
`Total Number of Drawing Sheets (if any)
`
`Filing By Reference:
`
`
`
`
`
`Application numberof the previously
`
`filed application
`
`
`
`
`For the purposesofa filing date under 37 CFR 1.53(b), the description and any drawings of the present application are replaced by this
`reference to the previously filed application, subject to conditions and requirements of 37 CFR 1.57(a}.
`
`
`Filing date (YYYY-MM-DD)
`
`Intellectual Property Authority or Country
`
`Publication Information:
`
`[_] Request Early Publication (Fee required at time of Request 37 CFR 1.219)
`
`Request Not to Publish. | hereby requestthat the attached application not be published under
`35 U.S.C. 122(b) and certify that the invention disclosed in the attached application has not and will not be the
`subject of an application filed in another country, or under a multilateral international agreement, that requires
`publication at eighteen monthsafterfiling.
`
`Representative Information:
`
`Representative information should be provided for all practitioners having a power of attorney in the application. Providing
`this information in the Application Data Sheet does not constitute a powerof attorney in the application (see 37 CFR 1.32).
`Either enter Customer Number or complete the Representative Name section below.If both sections are completed the customer
`Number will be used for the Representative Information during processing.
`
`
`C) Limited Recognition (37 CFR 11.9) CustomerNumber|S
`
`Please Select One:
`
`@ Customer Number
`
`US Patent Practitioner
`
`EFS Web 2.2.12
`
`-2-
`
`ROKU EXH. 1003
`
`ROKU EXH. 1003
`
`-2-
`
`

`

`PTO/AIA/14 (11-15)
`Approved for use through 04/30/2017. OMB 0651-0032
`U.S. Patent and Trademark Office; U.S. DEPARTMENT OF COMMERCE
`Underthe Paperwork Reduction Act of 1995, no persons are required to respond to a collection of information unless it contains a valid OMB control number.
`leat
`Application Data Sheet 37 CFR 1.76
`
`SOFTWARE APPLICATION FOR A MOBILE DEVICE TO WIRELESSLY MANAGE OR WIRELESSLY SETUP
`
`Title of Invention|any QUTPUT SYSTEM OR OUTPUT DEVICE FOR SERVICE
`
`Domestic Benefit/National Stage Information:
`This section allows for the applicant to either claim benefit under 35 U.S.C. 119(e), 120, 121, 365(c), or 386(c) or indicate
`National Stage entry from a PCT application. Providing benefit claim information in the Application Data Sheet constitutes
`the specific reference required by 35 U.S.C. 119(e) or 120, and 37 CFR 1.78.
`Whenreferring to the current application, please leave the “Application Number’field blank.
`
`Application Number
`
`Continuity Type
`
`Filing or 371(c) Date
`(YYYY-MM-DD)
`Prior Application Number
`
`
`Prior Application Status Expired
`Remove
`
`Filing or 371(c) Date
`(YYYY-MM-DD)
`2001-01-19
`
`Application Number
`0053765
`
`Continuity Type
`| laims benefit of provisional
`
`Prior Application Number
`+ 60262764
`
`
`
`
`
`
`
`
`Application Number
`
`Application Number
`
`19992413
`
`Prior Application Status
`
`Application Number
`
`Prior Application Status
`
`Continuity Type
`| continuation in part of
`
`Prior Application Number
`-| 09992413
`
`Filing or 371(c} Date
`(YYYY-MM-DD)
`PO01-11-18
`
`Continuity Type
`
`Prior Application Number
`
`Filing or 371(c) Date
`(YY YY-MM-DD)
`
`| laimsbenefitofprovisional
`
`: 60252682
`
`2000-11-20
`
`Continuity Type
`
`Prior Application Number
`
`Filing or 371(c) Date
`(YYYY-MM-DD)
`
`2012-12-10
`
`Patent Number
`
`4 13710299
`| continuationinpartof
`Issue Date
`_
`Prior—_—
`Filing Date
`Application
`Number
`Continuity Type
`(YYYY-MM-DD)
`Patent Number
`(YYYY-MM-DD)
`
`
`H3710299 | PentinuatonofE][r2s0s0es |poto-10-12 |332621 |po12-12-11
`
`
`Application
`_
`Prior—_
`Filing Date
`Issue Date
`Number
`ContinuityType
`mussMM-DD)
`(YYYY-MM-DD)
`
`Application Number
`0016223
`
`Continuity Type
`| laims benefit of provisional
`
`Prior Application Number
`-| 60245101
`
`EFS Web 2.2.12
`
`-3-
`
`Filing or 371(c) Date
`(YYYY-MM-DD)
`|p‘000-11-01
`ROKU EXH. 1003
`
`ROKU EXH. 1003
`
`-3-
`
`

`

`PTO/AIA/14 (11-15)
`Approved for use through 04/30/2017. OMB 0651-0032
`U.S. Patent and Trademark Office; U.S. DEPARTMENT OF COMMERCE
`Underthe Paperwork Reduction Act of 1995, no persons are required to respond to a collection of information unless it contains a valid OMB control number.
`
`ee Attorney Docket Number|FXT315CON8
`
`Application Data Sheet 37 CFR 1.76
`
`— Title of Invention
`
`SOFTWARE APPLICATION FOR A MOBILE DEVICE TO WIRELESSLY MANAGE OR WIRELESSLY SETUP
`AN OUTPUT SYSTEM OR OUTPUT DEVICE FOR SERVICE
`
`Additional Domestic Benefit/National Stage Data may be generated within this form
`by selecting the Add button.
`
`Foreign Priority Information:
`
`
`
`This section allows for the applicant to claim priority to a foreign application. Providing this information in the application data sheet
`constitutes the claim for priority as required by 35 U.S.C. 119(b) and 37 CFR 1.55. Whenpriority is claimed to a foreign application
`thatis eligible for retrieval under the priority document exchange program (PDX)! the information will be used by the Office to
`automatically attempt retrieval pursuant to 37 CFR 1.55(i)(1) and (2). Under the PDX program, applicant bears the ultimate
`responsibility for ensuring that a copy of the foreign application is received by the Office from the participating foreign intellectual
`
`property office, or a certified copy of the foreign priority application is filed, within the time period specified in 37 CFR 1.55(g)}{1).
`
`Filing Date (YYYY-MM-DD)
`Country!
`Application Number
`
`
`Additional Foreign Priority Data may be generated within this form by selecting the
`Add button.
`
`Remove
`Access Codel (if applicable)
`
`
`
`Statement under 37 CFR 1.55 or 1.78 for AIA (First Inventor to File) Transition
`Applications
`
`This application (1) claims priority to or the benefit of an application filed before March 16, 2013 and (2) also
`contains, or contained at any time, a claim to a claimed invention that has an effective filing date on or after March
`[|16, 2013.
`NOTE: Byproviding this statement under 37 CFR 1.55 or 1.78, this application, with a filing date on or after March
`
`16, 2013, will be examined underthefirst inventor to file provisions of the AIA.
`
`EFS Web 2.2.12
`
`-4-
`
`ROKU EXH. 1003
`
`ROKU EXH. 1003
`
`-4-
`
`

`

`PTO/AIA/14 (11-15)
`Approved for use through 04/30/2017. OMB 0651-0032
`U.S. Patent and Trademark Office; U.S. DEPARTMENT OF COMMERCE
`Underthe Paperwork Reduction Act of 1995, no persons are required to respond to a collection of information unless it contains a valid OMB control number.
`leat
`Application Data Sheet 37 CFR 1.76
`
`Title of Invention
`
`SOFTWARE APPLICATION FOR A MOBILE DEVICE TO WIRELESSLY MANAGE OR WIRELESSLY SETUP
`AN OUTPUT SYSTEM OR OUTPUT DEVICE FOR SERVICE
`
`
`
`Authorization or Opt-Out of Authorization to Permit Access:
`
`Whenthis Application Data Sheet is properly signed and filed with the application, applicant has provided written
`authority to permit a participating foreign intellectual property (IP) office access to the instant application-as-filed (see
`paragraph A in subsection 1 below) and the European Patent Office (EPO) access to any search results from the instant
`application (see paragraph B in subsection 1 below).
`
`Should applicant choose not to provide an authorization identified in subsection 1 below, applicant must opt-out of the
`authorization by checking the corresponding box A or B or both in subsection 2 below.
`
`NOTE: This section of the Application Data Sheet is ONLY reviewed and processed with the INITIALfiling of an
`application. After the initial filing of an application, an Application Data Sheet cannot be used to provide or rescind
`authorization for access by a foreign IP office(s).
`Instead, Form PTO/SB/39 or PTO/SB/69 must be used as appropriate.
`
`
`
`
`
`1. Authorization to Permit Access by a ForeignIntellectual Property Office(s)
`
`A. Priority Document Exchange (PDX)- Unless box A in subsection 2 (opt-out of authorization) is checked, the
`undersigned hereby grants the USPTO authority to provide the European Patent Office (EPO), the Japan Patent Office
`(JPO), the Korean Intellectual Property Office (KIPO), the State Intellectual Property Office of the People’s Republic of
`China (SIPO), the World Intellectual Property Organization (WIPO), and any other foreign intellectual property office
`participating with the USPTOin a bilateral or multilateral priority document exchange agreementin which a foreign
`application claiming priority to the instant patent application is filed, access to: (1) the instant patent application-as-filed
`andits related bibliographic data, (2) any foreign or domestic application to which priority or benefit is claimed by the
`instant application and its related bibliographic data, and (3) the date offiling of this Authorization. See 37 CFR 1.14(h)
`(1).
`
`B. Search Results from U.S. Application to EPO - Unless box B in subsection 2 (opt-out of authorization) is checked,
`the undersigned hereby grants the USPTO authority to provide the EPO accessto the bibliographic data and search
`results from the instant patent application when a European patent application claiming priority to the instant patent
`applicationis filed. See 37 CFR 1.14(h)(2).
`
`The applicant is reminded that the EPO’s Rule 141(1) EPC (European Patent Convention) requires applicants to submit a
`copy of search results from the instant application without delay in a European patent application that claims priority to
`the instant application.
`
`2. Opt-Out of Authorizations to Permit Access by a Foreign Intellectual Property Office(s}
`
`[|
`
`A. Applicant DOES NOT authorize the USPTO to permit a participating foreign IP office access to the instant
`application-as-filed.
`If this box is checked, the USPTOwill not be providing a participating foreign IP office with
`any documents andinformation identified in subsection 1A above.
`
`B. Applicant DOES NOTauthorize the USPTOto transmit to the EPO any search results from the instant patent
`[|application. If this box is checked, the USPTO will not be providing the EPO with search results from the instant
`application.
`NOTE: Oncethe application has published or is otherwise publicly available, the USPTO may provide accessto the
`application in accordance with 37 CFR 1.14.
`
`EFS Web 2.2.12
`
`-5-
`
`ROKU EXH. 1003
`
`ROKU EXH. 1003
`
`-5-
`
`

`

`PTO/AIA/14 (11-15)
`Approved for use through 04/30/2017. OMB 0651-0032
`U.S. Patent and Trademark Office; U.S. DEPARTMENT OF COMMERCE
`Underthe Paperwork Reduction Act of 1995, no persons are required to respond to a collection of information unless it contains a valid OMB control number.
`
`ee Attorney Docket Number|FXT315CON8
`
`Application Data Sheet 37 CFR 1.76
`—
`
`Title of Invention
`
`SOFTWARE APPLICATION FOR A MOBILE DEVICE TO WIRELESSLY MANAGE OR WIRELESSLY SETUP
`AN OUTPUT SYSTEM OR OUTPUT DEVICE FOR SERVICE
`
`
`
`Applicant Information:
`
`Providing assignmentinformation in this section does not substitute for compliance with any requirementof part 3 of Title 37 of CFR
`to have an assignment recorded by the Office.
`
`{1
`Applicant
`If the applicant is the inventor (or the remaining joint inventor or inventors under 37 CFR 1.45), this section should not be completed.
`The information to be provided in this section is the name and addressof the legal representative whois the applicant under 37 CFR
`1.43; or the name and addressof the assignee, person to whom the inventor is under an obligation to assign the invention, or person
`who otherwise shows sufficient proprietary interest in the matter whois the applicant under 37 CFR 1.46. If the applicantis an
`applicant under 37 CFR 1.46 (assignee, person to whem theinventoris obligated to assign, or person who otherwise showssufficient
`proprietary interest) together with one or morejoint inventors, then the joint inventor or inventors who are also the applicant should be
`identified in this section.
`
`
`Clear
`
`@ Assignee
`
`
`
`Legal Representative under 35 U.S.C. 117
`
`Joint Inventor
`
`Person who showssufficient proprietary interest
`Person to whom theinventor is obligated to assign.
`
`lf applicant is the legal representative, indicate the authority to file the patent application, the inventor is:
`
`Nameof the Deceased or Legally Incapacitated Inventor:Po
`If the Applicant is an Organization checkhere.
`xX]
`
`Organization Name
`
`i lexiworld Technologies,Inc.
`
`Mailing Address Information For Applicant:
`
`
`
`
`
`|
`Address 2
`
`City [Fencouer=iStateProvince|[wa
`
`PhoneNumber]anNumber|
`J
`
`Email Address
`
`
`Additional Applicant Data may be generated within this form by selecting the Add button.
`
`Add
`
`Assignee Information including Non-Applicant Assignee Information:
`
`Providing assignmentinformation in this section does not substitute for compliance with any requirement of part 3 of Title
`
`37 of CFR to have an assignment recorded by the Office.
`
`EFS Web 2.2.12
`
`-6-
`
`ROKU EXH. 1003
`
`ROKU EXH. 1003
`
`-6-
`
`

`

`PTO/AIA/14 (11-15)
`Approved for use through 04/30/2017. OMB 0651-0032
`U.S. Patent and Trademark Office; U.S. DEPARTMENT OF COMMERCE
`Underthe Paperwork Reduction Act of 1995, no persons are required to respond to a collection of information unless it contains a valid OMB control number.
`
`
`Attorney Docket Number|FXT315CON8
`
`
`Application Data Sheet 37 CFR 1.76
`
`
`
`SOFTWARE APPLICATION FOR A MOBILE DEVICE TO WIRELESSLY MANAGE OR WIRELESSLY SETUP
`
`Title of Invention
`AN OUTPUT SYSTEM OR OUTPUT DEVICE FOR SERVICE
`
`Application Number
`
`Assignee
`
`(1
`
`Complete this section if assignee information, including non-applicant assignee information, is desired to be included on the patent
`application publication. An assignee-applicant identified in the "Applicant Information” section will appear on the patent application
`publication as an applicant. For an assignee-applicant, complete this section onlyif identification as an assigneeis also desired on the
`patent application publication.
`
`Remove
`
`
`If the Assignee or Non-Applicant Assignee is an Organization check here.
`xX]
`
`Organization Name
`lexiworld Technologies,Inc.
`
`
`Address 2
`
`Postal Code
`
`
`
`
`Mailing Address Information For Assignee including Non-Applicant Assignee:
`
` Address 1
`P.O. Box 87237
`
`
`State/Province
`
`
`
`
`a
`Phone Number
`
`
`
`Email Address
`
`
`Additional Assignee or Non-Applicant Assignee Data may be generatedwithin this form by
`Add
`:
`selecting the Add button.
`
`
`
`
`
`
`
`Signature:
`NOTE: This Application Data Sheet must be signed in accordance with 37 CFR 1.33(b). However,if this Application
`Data Sheet is submitted with the INITIALfiling of the application and either box A or B is not checked in
`subsection 2 of the “Authorization or Opt-Out of Authorization to Permit Access”section, then this form must
`also be signed in accordance with 37 CFR 1.14(c).
`
`This Application Data Sheet must be signed by a patent practitioner if one or more of the applicants is a juristic
`entity (e.g., corporation or association). If the applicant is two or morejoint inventors, this form must be signed by a
`
`patent practitioner, all joint inventors who are the applicant, or one or morejoint inventor-applicants who have been given
`powerof attorney (e.g., see USPTO Form PTO/AIA/81) on behalf ofall joint inventor-applicants.
`See 37 CFR 1.4(d) for the manner of making signatures andcertifications.
`
`Date corto)
`|/PeterD.Sabido/
`Signature
`
`
`
`
`
`2017-05-12
`
`Additional Signature may be generated within this form by selecting the Add button.
`
`EFS Web 2.2.12
`
`-/-
`
`ROKU EXH. 1003
`
`ROKU EXH. 1003
`
`-7-
`
`

`

`PTO/AIA/14 (11-15)
`Approved for use through 04/30/2017. OMB 0651-0032
`U.S. Patent and Trademark Office; U.S. DEPARTMENT OF COMMERCE
`Underthe Paperwork Reduction Act of 1995, no persons are required to respond to a collection of information unless it contains a valid OMB control number.
`
`ee Attorney Docket Number|FXT315CON8
`
`Application Data Sheet 37 CFR 1.76
`
`— Title of Invention
`
`SOFTWARE APPLICATION FOR A MOBILE DEVICE TO WIRELESSLY MANAGE OR WIRELESSLY SETUP
`AN OUTPUT SYSTEM OR OUTPUT DEVICE FOR SERVICE
`
`This collection of information is required by 37 CFR 1.76. The information is required to obtain or retain a benefit by the public which
`is to file (and by the USPTOto process) an application. Confidentiality is governed by 35 U.S.C. 122 and 37 CFR 1.14. This
`collection is estimated to take 23 minutes to complete, including gathering, preparing, and submitting the completed application data
`sheet form to the USPTO. Time will vary depending upon theindividual case. Any comments on the amount of time you require to
`complete this form and/or suggestions for reducing this burden, should be sentto the Chief Information Officer, U.S. Patent and
`Trademark Office, U.S. Department of Commerce, P.O. Box 1450, Alexandria, VA 22313-1450. DO NOT SEND FEES OR
`COMPLETED FORMSTO THIS ADDRESS. SEND TO: Commissioner for Patents, P.O. Box 1450, Alexandria, VA 22313-1450.
`
`EFS Web 2.2.12
`
`-8-
`
`ROKU EXH. 1003
`
`ROKU EXH. 1003
`
`-8-
`
`

`

`
`
`Privacy Act Statement
`
`The Privacy Act of 1974 (P.L. 93-579) requires that you be given certain information in connection with your submission of the attached form related to a patent
`application or patent. Accordingly, pursuant to the requirements of the Act, please be advised that: (1) the general authority for the collection of this information
`is 35 U.S.C. 2(b) (2); (2) furnishing of the information solicited is voluntary; and (3) the principal purpose for which the information is used by the U.S. Patent and
`Trademark Office is ta process and/or examine your submission related to a patent application or patent. If you do not furnish the requested information, the U.S.
`Patent and Trademark Office may not be able to process and/or examine your submission, which mayresult in termination of proceedings or abandonment of
`the application or expiration of the patent.
`
`The information provided by you in this form will be subject to the following routine uses:
`
`1
`
`The information on this form will be treated confidentially to the extent allowed under the Freedom of Information Act (5 U.S.C. 552) and the Privacy
`Act (5 U.S.C. 552a). Records from this system of records may be disclosed to the Departmentof Justice to determine whether the Freedom of
`Information Act requires disclosure of these records.
`
`Arecord from this system of records may be disclosed, as a routine use, in the course of presenting evidence to a court, magistrate, or administrative
`tribunal, including disclosures to opposing counselin the course of settlement negotiations.
`
`Arecordin this system of records maybe disclosed,as a routine use, to a Member of Congress submitting a request involving an individual, to whom
`the record pertains, when the individual has requested assistance from the Member with respect to the subject matter of the record.
`
`A record in this system of records may be disclosed, as a routine use, to a contractor of the Agency having need for the information in order to perform
`a contract. Recipients of information shall be required to comply with the requirements of the Privacy Act of 1974, as amended, pursuant to 5 U.S.C.
`552a(m).
`
`Arecord related to an International Application filed under the Patent Cooperation Treaty in this system of records may be disclosed, as a routine use,
`to the International Bureau of the World Intellectual Property Organization, pursuant to the Patent CooperationTreaty.
`
`A record in this system of records may be disclosed, as a routine use, to another federal agency for purposes of National Security review (35 U.S.C. 181}
`and for review pursuant to the Atomic Energy Act (42 U.S.C. 218(c)).
`
`Arecord from this system of records may be disclosed,as a routine use, to the Administrator, General Services, or his/her designee, during an
`inspection of records conducted by GSAas part of that agency's responsibility to recommend improvements in records managementpractices and
`programs, under autherity of 44 U.S.C. 2904 and 2906. Such disclosure shall be made in accordance with the GSA regulations governing inspection of
`recordsfor this purpose, and any other relevant(i.e., GSA or Commerce) directive. Such disclosure shall not be used to make determinations about
`individuals.
`
`A record from this system of records may be disclosed,as a routine use, to the public after either publication of the application pursuant to 35 U.S.C.
`122(b) or issuance of a patent pursuant to 35 U.S.C 151. Further, a record may be disclosed, subject to the limitations of 37 CFR 1.14, as a routine use,
`to the public if the record wasfiled in an application which became abandoned orin which the proceedings were terminated and which application is
`referenced by either a published application, an application open to public inspections or an issued patent.
`
`A record from this system of records may be disclosed,as a routine use, to a Federal, State, or local law enforcement agency,if the USPTO becomes
`awareof a violation or potential violation of law or regulation.
`
`EFS Web 2.2.12
`
`-J-
`
`ROKU EXH. 1003
`
`
`
`ROKU EXH. 1003
`
`-9-
`
`

`

`SOFTWAREAPPLICATION FOR A MOBILE DEVICE TO
`WIRELESSLY MANAGE OR WIRELESSLY SETUP AN
`OUTPUT SYSTEM OR OUTPUT DEVICE FOR SERVICE
`
`Cross-Reference to Related Applications
`
`[0001]
`
`This application is a continuation of U.S. Patent Application Serial No.
`
`10/053,765 filed January 18, 2002, which claims priority to U.S. Provisional Patent
`
`Application Serial No. 60/262, 764, filed January 19, 2001. Additionally, this application is
`
`a continuation-in-part of U.S. Patent Application Serial No. 09/992,413 filed November
`
`18, 2001, which claims benefit of U.S. Provisional Patent Application Serial No.
`
`60/252,682 filed November 20, 2000. Moreover, this application is a continuation-in-part
`
`of U.S. Patent Application Serial No. 13/710,299 filed December 10, 2012, whichis a
`
`continuation of U.S. Patent Application Serial 12/903,048 filed October 12, 2010 and now
`
`issued as U.S. Patent No. 8,332,521, which is a continuation of U.S. Patent Application
`
`Serial No. 10/016,223 filed November 1, 2001 and now issued as U.S. Patent No.
`
`7,941,541, and which claims benefit of U.S. Provisional Patent Application Serial No.
`
`60/245,101, filed November 1, 2000. The complete disclosures of the above patent
`
`applications are hereby incorporated by referencefor all purposes.
`
`Technical Field of the Invention
`
`[0002]
`
`Present invention relates to providing content to an output device and,
`
`in
`
`particular, to providing universal output in which an information apparatus can pervasively
`
`output content to an output device without the need to install a dedicated device
`
`dependentdriver or applications for each output device.
`
`Background of the Disclosure
`
`[0003]
`
`The present invention relates to universal data output and,
`
`in particular,
`
`to
`
`providing a new data output method and a new raster image process for information
`
`apparatuses and output devices.
`
`[0004]
`
`As described herein,
`
`information apparatuses refer generally to computing
`
`devices, which include both stationary computers and mobile computing devices
`
`(pervasive devices). Examples of such information apparatuses include, without
`
`limitation, desktop computers,
`
`laptop computers, networked computers, palmtop
`
`computers (hand-held computers), personal digital assistants (PDAs), Internet enabled
`
`Page 1 of 73 - CONTINUATION APPLICATION
`
`Kolisch Docket No. FXT315CON8
`
`-10-
`
`ROKU EXH. 1003
`
`ROKU EXH. 1003
`
`-10-
`
`

`

`mobile phones, smart phones, pagers, digital capturing devices (e.g., digital cameras and
`
`video cameras), Internet appliances, e-books, information pads, and digital or web pads.
`
`Output devices may include, without limitation, fax machines, printers, copiers,
`
`image
`
`and/or video display devices (e.g., televisions, monitors and projectors), and audio output
`
`devices.
`
`[0005]
`
`For simplicity and convenience, hereafter, the following descriptions may refer
`
`to an output device as a printer and an output processasprinting. However, it should be
`
`understood that the term printer and printing used in the discussion of present invention
`
`refer to one embodiment used as a specific example to simplify the description of the
`
`invention. The referencesto printer and printing used here are intended to be applied or
`
`extended to the larger scope and definition of output devices and should not be construed
`
`as restricting the scope and practice of present invention.
`
`[0006]
`
`Fueled by an ever-increasing bandwidth, processing power, wireless mobile
`
`devices, and wireless software applications, millions of users are or will be creating,
`
`downloading, and transmitting content and information using their pervasive or mobile
`
`computing devices. As a result, there is a need to allow users to conveniently output
`
`content and information from their pervasive computing devices to any output device. As
`
`an example, people need to directly and conveniently output from their pervasive
`
`information apparatus, without depending on synchronizing with a stationary computer
`
`(e.g., desktop personal computer) for printing.
`
`[0007]
`
`Toillustrate, a mobile worker at an airport receiving e-mail in his hand-held
`
`computer may want to walk up to a nearby printer or fax machine to have his e-mail
`
`printed.
`
`In addition, the mobile worker may also want to print a copy of his to-do list,
`
`appointment book, business card, and his flight schedule from his mobile device. As
`
`another example, a user visiting an e-commerce site using his mobile device may want
`
`to print out transaction confirmation. In still another example, a user who takesa picture
`
`with a digital camera may wantto easily print it out to a nearby printer. In any of the above
`
`cases, the mobile user may want to simply walk up to a printer and conveniently print a
`
`file (word processing document, PDF, HTML etc) that is stored on the mobile device or
`
`downloaded from a network (e.g., Internet, corporate network).
`
`[0008]
`
`Conventionally, an output device (e.g., a printer) is connected to an information
`
`Page 2 of 73 - CONTINUATION APPLICATION
`
`Kolisch Docket No. FXT315CON8
`
`-11-
`
`ROKU EXH. 1003
`
`ROKU EXH. 1003
`
`-11-
`
`

`

`apparatus via a wired connection such as a cable line. A wireless connection is also
`
`possible by using,
`
`for example,
`
`radio communication or
`
`infrared communication.
`
`Regardless of wired or wireless connection, a user mustfirst install in the information
`
`apparatus an output device driver (e.g., printer driver in the case the output device is a
`
`printer) corresponding to a particular output device model and make. Using a device-
`
`dependent or specific driver, the information apparatus may process output content or
`
`digital document into a specific output device's input requirements (e.g., printer input
`
`requirements). The output device's input requirements correspond to the type of input that
`
`the output device (e.g., a printer) understands. For example, a printer's input requirement
`
`mayinclude printer specific input format (e.g., one or more of an image, graphics or text
`
`formator language). Therefore, an output data (or print data in the case the output device
`
`is a printer) herein refers to data that is acceptable for input to an associated output
`
`device. Examples of input requirements may include, without limitation, audio format,
`
`video format,
`
`file format, data format, encoding,
`
`language (e.g., page description
`
`language, markup language etc), instructions, protocols or data that can be understood
`
`or used by a particular output device make and model.
`
`[0009]
`
`Input requirements may be based on proprietary or published standards or a
`
`combination of the two. An output device's input requirements are, therefore, in general,
`
`device dependent. Different output device models may havetheir own input requirements
`
`specified, designed or adopted by the output device manufacturer (e.g.,
`
`the printer
`
`manufacturer) according to a specification for optimal operation. Consequently, different
`
`output devices usually require use of specific output device drivers (e.g., printer drivers)
`
`for accurate output (e.g., printing). Sometimes,
`
`instead of using a device driver (e.g.,
`
`printer driver),
`
`the device driving feature may be included as part of an application
`
`software.
`
`[0010]
`
`Installation of a device driver (e.g., printer driver) or application may be
`
`accomplished by, for example, manual installation using a CD or floppy disk supplied by
`
`the printer manufacturer. Or alternatively, a user may be able to download a particular
`
`driver or application from a network. For a home or office user, this installation process
`
`may take anywhere from several minutes to several hours depending on the type of driver
`
`and user's sophistication level with computing devices and networks. Even with plug-and-
`
`Page 3 of 73 - CONTINUATION APPLICATION
`
`Kolisch Docket No. FXT315CON8
`
`-12-
`
`ROKU EXH. 1003
`
`ROKU EXH. 1003
`
`-12-
`
`

`

`play driver installation, the user is still required to execute a multi-step process for each
`
`printer or output device.
`
`[0011]
`
`This installation and configuration process adds a degree of complexity and
`
`work to end-users who may otherwise spend their time doing other productive or
`
`enjoyable work. Moreover, many unsophisticated users may be discouraged from adding
`
`new peripherals (e.g., printers, scanners, etc.) to their home computers or networks to
`
`avoid the inconvenience ofinstallation and configuration. It is therefore desirable that an
`
`information apparatus can output
`
`to more than one output device without
`
`the
`
`inconvenience ofinstalling multiple dedicated device dependentdrivers.
`
`[0012]
`
`In addition, conventional output or printing methods may pose significantly
`
`higher challenges and difficultie

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