throbber

`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`
`UNITED STATES DEPARTMENT OF COMMERCE
`United States Patent and Trademark Office
`Address: COMMISSIONER FOR PATENTS
`PO. Box 1450
`Alexandria1 Virginia 22313- 1450
`www.uspto.gov
`
`APPLICATION NO.
`
`
`
`
`
` F ING DATE
`
`FIRST NAMED INVENTOR
`
`ATTORNEY DOCKET NO.
`
`
`
`
`
`CONF {MATION NO.
`
`13/ 147,463
`
`08/02/201 1
`
`Fumihiko Taguchi
`
`MAT—10478US
`
`3516
`
`EXAMINER
`RATNERPRESTIA —
`05’0”“ —
`7590
`52473
`PO. BOX 980
`SUN, LIP
`VALLEY FORGE, PA 19482-0980
`
`PAPER NUMBER
`
`ART UNIT
`
`2176
`
`
`
` NOT *ICATION DATE
`
`DELIVERY MODE
`
`05/09/2013
`
`ELECTRONIC
`
`Please find below and/or attached an Office communication concerning this application or proceeding.
`
`The time period for reply, if any, is set in the attached communication.
`
`Notice of the Office communication was sent electronically on above—indicated "Notification Date" to the
`following e—mail address(es):
`
`ptocorrespondence @ratnerprestia.c0m
`sparodi @ ratnerprestia.c0m
`
`PTOL—90A (Rev. 04/07)
`
`

`

`
`
`Applicant(s)
`Application No.
` 13/147,463 TAGUCHI, FUMIHIKO
`
`
`AIA (First Inventorto File)
`Art Unit
`Examiner
`Office Action Summary
`
`
`Li Sun its“ 2176
`-- The MAILING DA TE of this communication appears on the cover sheet with the correspondence address --
`Period for Reply
`
`
`
`A SHORTENED STATUTORY PERIOD FOR REPLY IS SET TO EXPIRE 3 MONTH(S) OR THIRTY (30) DAYS,
`WHICHEVER IS LONGER, FROM THE MAILING DATE OF THIS COMMUNICATION.
`Extensions of time may be available under the provisions of 37 CFR 1.136(a).
`In no event however may a reply be timely filed
`after SIX () MONTHS from the mailing date of this communication.
`If NO period for reply is specified above, the maximum statutory period will apply and will expire SIX (6) MONTHS from the mailing date of this communication.
`Failure to reply within the set or extended period for reply will, by statute, cause the application to become ABANDONED (35 U.S.C. § 133).
`Any reply received by the Office later than three months after the mailing date of this communication, even if timely filed, may reduce any
`earned patent term adjustment. See 37 CFR 1.704(b).
`
`-
`-
`
`Status
`
`1)IXI Responsive to communication(s) filed on 1 March 2013.
`[I A declaration(s)/affidavit(s) under 37 CFR 1.130(b) was/were filed on
`
`2b)|:| This action is non-final.
`a)IXl This action is FINAL.
`3)I:I An election was made by the applicant in response to a restriction requirement set forth during the interview on
`
`
`; the restriction requirement and election have been incorporated into this action.
`
`4)|:I Since this application is in condition for allowance except for formal matters, prosecution as to the merits is
`closed in accordance with the practice under EX parte Quay/e, 1935 CD. 11, 453 O.G. 213.
`
`Disposition of Claims
`5)|XI Claim(s) His/are pending in the application.
`5a) Of the above claim(s)
`is/are withdrawn from consideration.
`6)|:l Claim(s) _ is/are allowed.
`7)IZ| Claim(s)_1-7is/are rejected.
`8)I:I Claim(s) _ is/are objected to.
`
`9)|:l Claim((s)
`are subject to restriction and/or election requirement.
`* If any claims have been determined allowable, you may be eligible to benefit from the Patent Prosecution Highway program at a
`
`participating intellectual property office for the corresponding application. For more information, please see
`htt
`://www.usoto. ov/ atents/init events"
`
`
`
`h/inciex.‘s or send an inquiry to PF"I-iieedback{<‘buspto.qov.
`
`Application Papers
`
`10)I:I The specification is objected to by the Examiner.
`11)|:I The drawing(s) filed on _ is/are: a)I:I accepted or b)I:I objected to by the Examiner.
`Applicant may not request that any objection to the drawing(s) be held in abeyance. See 37 CFR 1.85(a).
`
`Replacement drawing sheet(s) including the correction is required if the drawing(s) is objected to. See 37 CFR 1.121 (d).
`
`Priority under 35 U.S.C. § 119
`12)I:I Acknowledgment is made of a claim for foreign priority under 35 U.S.C. § 119(a)-(d) or (f).
`Certified copies:
`
`b)I:I Some * c)I:I None of the:
`a)I:I AII
`1.I:I Certified copies of the priority documents have been received.
`2.I:I Certified copies of the priority documents have been received in Application No.
`3.|:I Copies of the certified copies of the priority documents have been received in this National Stage
`
`application from the International Bureau (PCT Rule 17.2(a)).
`* See the attached detailed Office action for a list of the certified copies not received.
`
`Interim copies:
`
`a)|:l AII
`
`b)I:I Some
`
`c)I:I None of the:
`
`Interim copies of the priority documents have been received.
`
`Attachment(s)
`
`1) E Notice of References Cited (PTO-892)
`
`3) I] Interview Summary (PTO-413)
`
`Paper NOISIIMa” Date —
`PTO/SB/08
`t
`St t
`I
`D'
`t'
`f
`2 I:l I
`)
`4) I:I Other:
`a emen (s)(
`Isc osure
`n orma Ion
`)
`Paper No(s)/Mai| Date
`US. Patent and Trademark Office
`PTOL-326 (Rev. 03-13)
`
`Part of Paper No./Mai| Date 20130423
`
`Office Action Summary
`
`

`

`Application/Control Number: 13/147,463
`
`Page 2
`
`Art Unit: 2176
`
`DETAILED ACTION
`
`This action is responsive to the Amendment filed on 03/01/2013. Claims 1-7 are
`
`pending in the case.
`
`This action is FINAL.
`
`Applicant’s Response
`
`In Applicant’s response dated 03/01/2013, Applicant amended Claims 1, 2 and 6;
`
`added new Claim 7; amended the Title of the Invention; and argued against all
`
`objections and rejections previously set forth in the Office Action dated 12/04/2012.
`
`Claim Rejections - 35 USC § 1 12
`
`The following is a quotation of 35 U.S.C. 112(b):
`
`(B) CONCLUSION—The specification shall conclude with one or more claims particularly pointing out
`and distinctly claiming the subject matter which the inventor or a joint inventor regards as the invention.
`
`The following is a quotation of 35 U.S.C. 112 (pre-AIA), second paragraph:
`
`The specification shall conclude with one or more claims particularly pointing out and distinctly
`claiming the subject matter which the applicant regards as his invention.
`
`Claim 1 is rejected under 35 U.S.C. 112(b) or 35 U.S.C. 112 (pre-AIA), second
`
`paragraph, as being indefinite for failing to particularly point out and distinctly claim the
`
`subject matter which the inventor or a joint inventor, or for pre-AlA the applicant regards
`
`as the invention.
`
`

`

`Application/Control Number: 13/147,463
`
`Page 3
`
`Art Unit: 2176
`
`Claim 1:
`
`The amended Claim 1 recites “attribute data corresponding at least to a plurality
`
`of functions which the objective device is capable of performing” in line 7-8. This
`
`limitation is indefinite because the Specification expressly describes the “attribute data”
`
`as: “The attribute data contains the presence or absence of an objective device to be
`
`controlled connected to network 102, and the type of the objective device to be
`
`controlled” (see Specification, page 7, line 23-25). It is unclear to Examiner how and in
`
`what way the recited “attribute data” corresponds to a plurality of functions. Thus, the
`
`intended scope of the recited limitation is indefinite. For the purpose of the examination,
`
`Examiner will interpret the recited "attribute data" as any data/information related to or
`
`describes the objective device.
`
`Further, Claim 1 recites “a plurality of functions which the control the objective
`
`device is capable of performing” in line 8, and “an other plurality of functions which the
`
`control device is capable of performing” in line 11. This limitation in indefinite because
`
`some device can only perform a single function, thus, the recited “a plurality of
`
`functions”, which requires two or more functions, does not appear to be a valid
`
`requirement. For the purpose of the examination, Examiner will interpret the recited “a
`
`plurality of functions” as one or more functions.
`
`Examiner’s Comments Concerning the Recited Claims and 35 USC § 101
`
`Claim 7 recites a “control device”. (see Claim 7).
`
`

`

`Application/Control Number: 13/147,463
`
`Page 4
`
`Art Unit: 2176
`
`Based upon the description of the recited “control device” in the Specification and
`
`the Drawings, the examiner interprets the “control device” to necessarily comprise
`
`hardware components. For example, see Fig. 2; page 7, line 4-page 9, line 3.
`
`If the recited “control device” is intended to include an embodiment that includes
`
`only computer software components, then Applicant should expressly state that in the
`
`Response to this Office Action.
`
`In that instance, Claim 7 will be interpreted as being
`
`non-statutory and rejections under 35 U.S.C. 101 will be forthcoming.
`
`Claim Rejections - 35 USC § 102
`
`The following is a quotation of the appropriate paragraphs of 35 U.S.C. 102 that
`
`form the basis for the rejections under this section made in this Office action:
`
`A person shall be entitled to a patent unless —
`
`(b) the invention was patented or described in a printed publication in this or a foreign country or in
`public use or on sale in this country, more than one year prior to the date of application for patent in
`the United States.
`
`Claims 1, 2, 6 are rejected under 35 U.S.C. 102(b) as being anticipated by
`
`Mortensen, US Publication 2009/0154933 A1 (hereinafter Mortensen).
`
`Claim 1:
`
`Mortensen discloses a control device (see DTV 12 in Fig. 1) connected to an
`
`objective device (see IR controlled (IRC) devices 30 and 1394 devices 40 in Fig. 1) to
`
`be controlled via a network (see [0045], Mortensen discloses this limitation in that the
`
`home theater network system (HTNS) 10, as depicted in Fig. 1, includes a plurality of IR
`
`

`

`Application/Control Number: 13/147,463
`
`Page 5
`
`Art Unit: 2176
`
`controlled (IRC) devices 30 and 1394 devices 40 interconnected to the DTV 12 and one
`
`another), the control device comprising:
`
`an operation control unit (see IR detector/receiver 103 in Fig. 5) for
`
`acquiring a request input by a user to display a device list screen (see
`
`[0063]; [0049], Mortensen discloses this limitation in that as shown in Fig.
`
`5, the IR detector 103 receives and amplifies the IR signal sent from a
`
`remote control device 20 to show a device selection menu 52 as illustrated
`
`in Figs. 2A-2F);
`
`a communication control unit (see AV connection module (AVCM) 112 in
`
`Fig. 5) for acquiring attribute data of the objective device to be controlled
`
`via the network (see [0068], line 1-6, Mortensen discloses this limitation in
`
`that the function of the AVCM 112 is to determine the current state of the
`
`HTNS 10 by querying the device management system (DMS) 116, TV
`
`control module (TVCM) 140 and the TV micro 105 as to devices
`
`connected to the system, active “in-use” device connections, active AV
`
`switching within devices and current TV operating parameters);
`
`a first holding unit (see device container list (DCL) 117, and device
`
`interconnect list (DIL) in Fig. 5) for holding the attribute data corresponding
`
`at least to a plurality of functions which the objective device is capable of
`
`performing (see [0070], line 9-22; [0075], line 1-2, Mortensen discloses
`
`this limitation in that the DCL 117 is a list, or database, of all the supported
`
`devices that make up the HTNS 10; information about each device is
`
`

`

`Application/Control Number: 13/147,463
`
`Page 6
`
`Art Unit: 2176
`
`placed into a device container object (DCO); the DIL 118 is a list, or
`
`database, of all the physical device connections in the HTNS 10);
`
`.
`
`a second holding unit (see TVCM 140 in Fig. 5) for holding function
`
`information corresponding at least to an other plurality of functions which
`
`the control device is capable of performing (see [0068], line 1-6,
`
`Mortensen discloses this limitation in that AVCM 112 queries the device
`
`management system (DMS) 116, TV control module (TVCM) 140 and the
`
`TV micro 105 as to devices connected to the system, active “in-use”
`
`device connections, active AV switching within devices and current TV
`
`operating parameters);
`
`.
`
`a determination unit for detecting a presence of at least one function (e.g.,
`
`audio output) from the plurality of functions of the objective device (e.g.,
`
`AVR 1082 in Fig. 2F) that is executable by at least the control device (e.g.,
`
`DTV) independent of the objective device, based on the attribute data held
`
`by the first holding unit and the function information held by the second
`
`holding unit (see window 80 in Fig. 2A, and 1801 in Fig. 2F; [0051], line
`
`12-15; [0052], line 1-9; [0054]-[0055], Mortensen discloses this limitation in
`
`that in the device selection menu 52, icons corresponding to the audio
`
`sink or audio output devices, such as the TV audio icon 82, an IRC AVR
`
`icon 84 and a 1394 AVR icon 86 are displayed in the audio window, as
`
`shown in Fig. 2A, and the TV audio icon and AVR icon displayed in audio
`
`selection window 1080, as shown in Fig. 2F; this intuitive, on-screen,
`
`

`

`Application/Control Number: 13/147,463
`
`Page 7
`
`Art Unit: 2176
`
`head-up, real-time visual recognition system visually communicates to the
`
`user U the current system state including active "in-use" connections,
`
`input device options, audio output options, and etc.. Playing audio through
`
`either the TV audio or AVR is considered executing a function
`
`independent of the other device, e.g., if user selects to play audio through
`
`AVR, it would not interfere with the function of the TV, and vice versa);
`
`.
`
`a display control unit (see graphical Ul 114 in Fig. 5) for displaying the
`
`device list screen (see window 80 in Fig. 2A, and 1801 in Fig. 2F)
`
`provided with information indicating the presence of the at least one
`
`function determined by the determination unit (see [0051], line 12-15;
`
`[0052], line 1-9, Mortensen discloses this limitation in that in the device
`
`selection menu 52, icons corresponding to the audio sink or audio output
`
`devices, such as the TV audio icon 82, an IRC AVR icon 84 and a 1394
`
`AVR icon 86, are displayed in the audio window; this intuitive, on-screen,
`
`head-up, real-time visual recognition system visually communicates to the
`
`user U the current system state including active "in-use" connections,
`
`input device options, audio output options, and etc.); and
`
`.
`
`a control unit (see inter-processor communication module (IPC) 107 in
`
`Fig. 5) for, when the operation control unit has acquired the request to
`
`display the device list screen, making the communication control unit
`
`acquire the attribute data, making the determination unit detect the at least
`
`one functions that is executable by the control device independent of the
`
`

`

`Application/Control Number: 13/147,463
`
`Page 8
`
`Art Unit: 2176
`
`objective device, and making the display control unit display the device list
`
`screen (see [0067], line 2-8, Mortensen discloses this limitation in that an
`
`inter-processor communication module (IPC) 107 enables
`
`communications between the DM 110 and the software or other
`
`programmable logic of the TV micro 105, a user interface module (UIM)
`
`111, a 1394 control module 120, a 1394 driver module 124, a IR control
`
`module 130, an IR blaster control module 134, and a TV control (TVC)
`
`module 140).
`
`Claim 2:
`
`Mortensen discloses the control device according to claim 1, wherein the
`
`determination unit detects the presence of the at least one function based on a plurality
`
`of pieces of the attribute data held by the first holding unit (see window 80 in Fig. 2A,
`
`and 1801 in Fig. 2F; [0051], line 12-15; [0052], line 1-9, Mortensen discloses this
`
`limitation in that in the device selection menu 52, icons corresponding to the audio sink
`
`or audio output devices, such as the TV audio icon 82, an IRC AVR icon 84 and a 1394
`
`AVR icon 86, are displayed in the audio window; this intuitive, on-screen, head-up, real-
`
`time visual recognition system visually communicates to the user U the current system
`
`state including active "in-use" connections, input device options, audio output options,
`
`and etc.; audio output information for TV, IRC AVR, and 1394 AVR is considered a
`
`plurality of pieces of attribute data).
`
`

`

`Application/Control Number: 13/147,463
`
`Page 9
`
`Art Unit: 2176
`
`Claim 6:
`
`Claim 6 merely recites a control method of using the control device recited in
`
`Claim 1. Mortensen discloses a control method (see Claim 1). Thus, Mortensen
`
`discloses every limitation of Claim 6, as indicated in the above rejection for Claim 1.
`
`Claim Rejections - 35 USC § 103
`
`The following is a quotation of 35 U.S.C. 103(a) which forms the basis for all
`
`obviousness rejections set forth in this Office action:
`
`(a) A patent may not be obtained though the invention is not identically disclosed or described as set
`forth in section 102 of this title, if the differences between the subject matter sought to be patented and
`the prior art are such that the subject matter as a whole would have been obvious at the time the
`invention was made to a person having ordinary skill in the art to which said subject matter pertains.
`Patentability shall not be negatived by the manner in which the invention was made.
`
`Claim 3 is rejected under 35 U.S.C. 103(a) as being unpatentable over
`
`Mortensen in view of Yui et al., US Patent No. 7,613,922 B2 (hereinafter Yui).
`
`Claim 3:
`
`Mortensen discloses every element of Claim 1. Additionally, Mortensen teaches
`
`that the device selection menu 52 is customizable and can include any number of
`
`windows (see Figs. 2A-2F; [0050], e.g., in Fig. 2E, the audio window is not displayed).
`
`Mortensen fails to expressly disclose/teach: further comprising:
`
`.
`
`a third holding unit for storing a usage history of a predetermined function
`
`contained in the function information of the control device; and
`
`

`

`Application/Control Number: 13/147,463
`
`Page 10
`
`Art Unit: 2176
`
`.
`
`a suppression unit for outputting a suppression request to suppress the
`
`predetermined function based on the usage history held by the third
`
`holding unit,
`
`wherein upon receiving the suppression request from the suppression unit, the
`
`display control unit displays the device list screen not containing the information
`
`indicating the presence of the different functions detected by the determination unit.
`
`Yui teaches an electronic device controlling system for controlling electronic
`
`devices without requiring tedious operations (see Col. 1, line 36-41), further comprising:
`
`.
`
`a third holding unit (see personal profile information in Fig. 27) for storing
`
`a usage history of a predetermined function (see electronic device usage
`
`history information in Fig. 27) contained in the function information of the
`
`control device (see Col. 28, line 25-40, Yui discloses this limitation in that
`
`as shown in Fig. 27, electronic device usage history information is
`
`recorded as part of personal profile information in the family information
`
`memory 105; the electronic device usage history information may be
`
`constituted by the history of remote controller operations performed
`
`illustratively during the past month; the monitor control unit 1 derives each
`
`user's tastes and preferences from that history of remote controller
`
`operations); and
`
`.
`
`a suppression unit for outputting a suppression request to suppress the
`
`predetermined function based on the usage history held by the third
`
`

`

`Application/Control Number: 13/147,463
`
`Page 11
`
`Art Unit: 2176
`
`holding unit (see Col. 28, line 35-42, Yui discloses this limitation in that the
`
`historical information allows the monitor control unit 1 to determine that a
`
`particular user likes watching TV or listening to audio program and control
`
`the electronic devices accordingly, e.g., turn on TV directly instead of
`
`other audio program based on user preference. In this example, other
`
`audio program is considered suppressed based on preference),
`
`wherein upon receiving the suppression request from the suppression unit, the
`
`display control unit displays the device list screen not containing the information
`
`indicating the presence of the different functions detected by the determination unit (see
`
`Col. 28, line 35-42, Yui discloses this limitation in that the historical information allows
`
`the monitor control unit 1 to determine that a particular user likes watching TV or
`
`listening to audio program and control the electronic devices accordingly, e.g., turn on
`
`TV directly instead of other audio program based on user preference. In this example,
`
`the TV is turned on directly for user to watching TV programs without the need to
`
`display additional option menus asking user to manually turn on the TV or other
`
`devices),
`
`for the purpose of controlling electronic devices without requiring tedious
`
`operation to save time (see Col. 1, line 36-41).
`
`Accordingly, it would have been obvious to one having ordinary skill in the art at
`
`the time of the invention was made to modify the control device, disclosed in Mortensen,
`
`to include:
`
`

`

`Application/Control Number: 13/147,463
`
`Page 12
`
`Art Unit: 2176
`
`.
`
`a third holding unit for storing a usage history of a predetermined function
`
`contained in the function information of the control device; and
`
`.
`
`a suppression unit for outputting a suppression request to suppress the
`
`predetermined function based on the usage history held by the third
`
`holding unit,
`
`wherein upon receiving the suppression request from the suppression unit, the
`
`display control unit displays the device list screen not containing the information
`
`indicating the presence of the different functions detected by the determination unit,
`
`for the purpose of controlling electronic devices without requiring tedious
`
`operation to save time, as taught by Yui.
`
`Claim 4 is rejected under 35 U.S.C. 103(a) as being unpatentable over
`
`Mortensen in view of Kang et al., US Publication 2006l0140499 A1 (hereinafter Kang).
`
`Claim 4:
`
`Mortensen discloses every element of Claim 1.
`
`Mortensen fails to expressly disclose/teach: wherein the network uses HDMI
`
`(High-Definition Multimedia Interface); and the communication control unit acquires the
`
`attribute data as a response to an HDMI extension command.
`
`

`

`Application/Control Number: 13/147,463
`
`Page 13
`
`Art Unit: 2176
`
`Kang teaches apparatuses and methods for data processing which enables input
`
`data to be processed in an optimum data processing environment by making data
`
`processing apparatus share information (see [0003]), wherein the network uses HDMI
`
`(High-Definition Multimedia Interface); and the communication control unit acquires the
`
`attribute data as a response to an HDMI extension command (see Figs. 5, and 8; [049];
`
`[0084], Kang discloses this limitation in that as shown in Fig. 5, attributes for electronic
`
`devices, e.g., a DVD player, a set-top box, and a TV set are retrieved; as shown in Fig.
`
`8, the interface units 820 and 850 corresponding to DVDP 810 and TV set 840 are
`
`connected using DVl/HDMI; the control unit 846 set as the master control unit
`
`determines an optimum condition for enhancing image quality bases on attribute
`
`information stored in the lookup table 818 of the DVDP 810).
`
`It would have been obvious to one of ordinary skill in the art to use the known
`
`technique of HDMI to connect electronic devices in a network, as taught by Kang, to
`
`improve a similar electronic device network, disclosed in Mortensen, to increase
`
`efficiency for sharing data/information among electronic devices in the same manner as
`
`set forth in Kang.
`
`Claim 5 is rejected under 35 U.S.C. 103(a) as being unpatentable over
`
`Mortensen in view of Doumuki et al., US Publication 2007/0101024 A1 (hereinafter
`
`Doumuki).
`
`

`

`Application/Control Number: 13/147,463
`
`Page 14
`
`Art Unit: 2176
`
`Claim 5:
`
`Mortensen discloses every element of Claim 1.
`
`Mortensen fails to expressly disclose/teach: wherein the network uses DLNA
`
`(Digital Living Network Alliance); and the communication control unit acquires the
`
`attribute data contained in DDD (Device Description Document) information of DLNA.
`
`Doumuki teaches system and method providing interoperability between IEEE
`
`1394 network devices and universal plug-and-play (UPnP) network devices in a home
`
`network (see [0007]), wherein the network uses DLNA (Digital Living Network Alliance)
`
`(see [0004], Doumuki discloses this limitation in that lP-based network protocols are
`
`increasingly adopted by consumer electronics in light of the direction of the Digital Living
`
`Network Alliance (DLNA)); and the communication control unit acquires the attribute
`
`data contained in DDD (Device Description Document) information of DLNA (see
`
`[0039], Doumuki discloses this limitation in that when a control point (CP) is added to
`
`network, it sends a “ssdp:search” message to search other devices; a “ssdp:alive” or a
`
`response to “ssdp:search” includes a URL to the device description document which
`
`includes detailed information of the device and a URL of the service description
`
`document).
`
`It would have been obvious to one of ordinary skill in the art to use the known
`
`technique of utilize DLNA in a home network, as taught by Doumuki, to improve a
`
`

`

`Application/Control Number: 13/147,463
`
`Page 15
`
`Art Unit: 2176
`
`similar electronic device network, disclosed in Mortensen, to achieve interoperability in a
`
`home network in the same manner as set forth in Doumuki.
`
`Claim 7 is rejected under 35 U.S.C. 103(a) as being unpatentable over
`
`“Transfering photos from your digital camera”, HP, 12/30/2008 (hereinafter HP) in view
`
`of “Autopay in Windows XP: Automatically Detect and React to New Devices on a
`
`System”, Stephane St-Michel and Brian Aust, MSDN Magzine, 11/2001 (hereinafter
`
`Autoplay).
`
`Claim 7:
`
`HP discloses a control device (computer) connected to an objective device
`
`(digital camera) to be controlled via a network (see page 1-2, under heading “Connect
`
`your digital camera directly to a computer with a USB cable”, HP discloses this limitation
`
`in that when connecting a digital camera to a computer with a USB cable, user can see
`
`the digital camera as a hard drive on the computer and moving photos from camera to
`
`computer), wherein the function (e.g., view photos) is executable by the control device
`
`(computer) independent of the objective device (digital camera) upon transferring the
`
`physical medium (memory card) from the objective device to the control device (see
`
`page 4, under heading “Copy or print digital photos from a memory card”, HP discloses
`
`this limitation in that digital photos are stored on camera's memory card, user can
`
`remove the card and insert it into a card reader slot on the front of the computer, so the
`
`photos can be viewed on the computer without the camera).
`
`

`

`Application/Control Number: 13/147,463
`
`Page 16
`
`Art Unit: 2176
`
`HP fails to expressly disclose/teach: wherein the control device detects a function
`
`common to both the control and the objective device according to a physical medium
`
`holding a content.
`
`Autoplay teaches providing a software response to hardware actions initiated by
`
`user on computer (see page 1, 2nd paragraph), wherein the control device (computer
`
`running Windows XP) detects a function (e.g., function to play media content) common
`
`to both the control and the objective device according to a physical medium holding a
`
`content (see Figure 2; heading "Autoplay V2 on Volume-based Devices", Autoplay
`
`discloses this limitation in that Volume Autoplay V2 relies on sniffing the content of
`
`volumes as they arrive (e.g., a camera contains photos is plugged in), whether they're
`
`media for removable media drives or removable hard disks; the sniffing consists of
`
`scanning the first four levels of folders from the root of the volume and looking for
`
`multimedia content types: music, graphics, and video; when an event occurs (e.g., a
`
`camera contains photos is plugged in), Windows determines which action to perform
`
`based on the intersection of the applications registered on a per-content type basis and
`
`the content types found on the volume through sniffing; if user did not yet specify any
`
`preferences, Windows prompts the user to choose one of the applications, as illustrated
`
`in Figure 2. The Autoplay event prompt when a volume-based device, e.g., digital
`
`camera, is connected, as shown in Figure 2, is considered detecting a function (e.g.
`
`view photo using a computer application) common to both the control and objective
`
`

`

`Application/Control Number: 13/147,463
`
`Page 17
`
`Art Unit: 2176
`
`device (both computer and digital camera can be used to view photos) according to a
`
`physical medium (memory of digital camera) holding a content (photos)), for the
`
`purpose of enhancing the Autoplay feature of Windows to handle the dramatic growth in
`
`digital multimedia content and an increasing number of devices generating such content
`
`(see heading “SUMMARY”).
`
`Accordingly, it would have been obvious to one of ordinary skill in the art at the
`
`time of the invention to modify the control device, disclosed in HP, to include: wherein
`
`the control device detects a function common to both the control and the objective
`
`device according to a physical medium holding a content, for the purpose of enhancing
`
`the Autoplay feature of Windows to handle the dramatic growth in digital multimedia
`
`content and an increasing number of devices generating such content, as taught by
`
`Autoplay.
`
`Response to Arguments
`
`Examiner acknowledges Applicant’s amendment to the Title of the Invention to
`
`cure minor informalities.
`
`In response to this amendment, the objection to the Title of the
`
`Invention is respectfully withdrawn.
`
`Applicant’s prior art arguments with respect to the pending claims have been
`
`considered but they are not persuasive.
`
`

`

`Application/Control Number: 13/147,463
`
`Page 18
`
`Art Unit: 2176
`
`Arguments for Claim 1:
`
`Regarding the amended Claim 1, Applicant argues that Mortensen does not
`
`disclose “a determination unit for detecting a presence of at least one function from the
`
`plurality of functions of the objective device that is executable by at least the control
`
`device independent of the objective device”, because Mortensen discloses different
`
`audio output devices among other lR controlled devices, connected to a digital
`
`television DTV 12, are displayed (and navigated) in the audio window (included in the UI
`
`50) of the DTV. Particularly, Mortensen's Ul 50 and digital module (DM) 110 are
`
`responsible for directing AV signals from external devices and internal devices to the
`
`DTV 12 or to other devices connected within the HTNS 10; Mortensen fails to disclose a
`
`determination unit that can detect a function that is common to both the control device
`
`and the objective device, and particularly, the detected function can be executed by the
`
`control device independent of the objective device. (See Applicant’s REMARKS, page
`
`7, 3rd paragraph)
`
`Examiner respectfully disagrees.
`
`Examiner would like to note that the limitation “functions of the objective device
`
`that is executable by. . .the control device independent of the objective device”, as
`
`claimed, is very broad. Based on the broadest reasonable interpretation, as long as a
`
`function, e.g., play music, can be performed on one device without interfering with the
`
`other device, it meets the recited limitation. As indicated in the above office action,
`
`

`

`Application/Control Number: 13/147,463
`
`Page 19
`
`Art Unit: 2176
`
`Mortensen clearly teaches a determination unit for detecting a presence of at least one
`
`function (e.g., audio output) from the plurality of functions of the objective device (e.g.,
`
`AVR 1082 in Fig. 2F) that is executable by at least the control device (e.g., DTV)
`
`independent of the objective device (see window 80 in Fig. 2A, and 1801 in Fig. 2F;
`
`[0051], line 12-15; [0052], line 1-9; [0054]-[0055], Mortensen discloses this limitation in
`
`that in the device selection menu 52, icons corresponding to the audio sink or audio
`
`output devices, such as the TV audio icon 82, an IRC AVR icon 84 and a 1394 AVR
`
`icon 86 are displayed in the audio window, as shown in Fig. 2A, and the TV audio icon
`
`and AVR icon displayed in audio selection window 1080, as shown in Fig. 2F; this
`
`intuitive, on-screen, head-up, real-time visual recognition system visually communicates
`
`to the user U the current system state including active "in-use" connections, input
`
`device options, audio output options, and etc.. Playing audio through either the TV
`
`audio or AVR is considered executing a function independent of the other device, e.g., if
`
`user selects to play audio through AVR, it would not interfere with the function of the TV,
`
`and vice versa).
`
`Accordingly, Mortensen teaches this limitation.
`
`For new Claim 7, please see above office action for details.
`
`

`

`Application/Control Number: 13/147,463
`
`Page 20
`
`Art Unit: 2176
`
`Conclusion
`
`THIS ACTION IS MADE FINAL. Applicant is reminded of the extension of time
`
`policy as set forth in 37 CFR1.136(a).
`
`A shortened statutory period for reply to this final action is set to expire THREE
`
`MONTHS from the mailing date of this action.
`
`In the event a first reply is filed within
`
`TWO MONTHS of the mailing dat

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