throbber
(19) United States
`(12) Patent Application Publication (10) Pub. N0.: US 2004/0109066 A1
`
` Inoue et al. (43) Pub. Date: Jun. 10, 2004
`
`
`US 20040109066A1
`
`(54) DIGITAL CAMERA, METHOD OF
`CONTROLLING DIGITAL CAMERA, AND
`FILE SERVER
`
`(30)
`
`Foreign Application Priority Data
`
`Dec. 6, 2002
`
`(JP) .................................. JP2002-356084
`
`(75)
`
`Inventors: Yasuaki Inoue, Saitama-shi (JP);
`“5111“?" Hiranuma> MatuSdO'fihi (1,1));
`KYP‘Chl Takano> TOkYO (JP); H‘mk‘
`M1ura, Kawaguch1-sh1 (JP)
`
`Correspondence Address:
`McDERMOTT, WILL & EMERY
`600 13th Street, NW.
`Washington, DC 20005-3096 (US)
`
`(73) Assignee: SANYO ELECTRIC C0,, LTD,
`
`(21) Appl. N0.:
`
`10/725,385
`
`Publication Classification
`Int. Cl.7 ..................................................... H04N 5/225
`(51)
`(52) us. CI.
`........................................................ 348/207.99
`(57)
`ABSTRACT
`Digital cameras which improve operability in checking,
`storing, and editing shot images have not been satisfactory.
`A digital camera and a user terminal including a file server
`are connected over a network. When the digital camera is
`powered on, it automatically establishes a network connec-
`tion with the file server in an activation process. When the
`digital camera shoots an image, this image is transmitted to
`the file server automatically upon completion of the encod-
`ing and compression of the image. When image reproduc-
`tion is instructed from the digital camera,
`the image is
`downloaded from the file sever over the network and dis-
`
`(22)
`
`Filed:
`
`Dec. 3, 2003
`
`played on the digital camera.
`
`16
`
`'
`
`‘
`48
`REPRODUC-
`TION PRO-
`CIIJSNSINNG
`
`'
`-
`
`..:
`
`I'
`
`' 46 '
`MAIN
`MEMORY
`
`'
`
`I4
`
`44
`26
`IMAGE PICKUP BLOCK
`T
`
`
`
`
`
`.............
`'
`pIIAICAEES-
`
`
`ING UNIT
`
`MECHAN ISM
`
`CONTROL
`
`BLOCK
`
`
`
`
`5o
`
`56
`58
`60
`
`INTERNAL BUFFER AREA
`NETWORK
`CONFIGURATION AREA
`FLASH MEMORY
`
`CARD IDEN-
`BUFFER
`MOSES? | NG TI FICATION
`I
`
`64
`72
`
`COMMUNICATION 66
`CONTROL UNIT
`MEMORY CARD
`
`.
`
`TRANSMISSION
`
`I
`CONTROL UNIT
`‘
`PROCESSING UNIT
`I
`'
`PROCESSING BLOCK
`52
`.
`L_.._____._________......________._l
`
`76 : SYSTEM BUS
`
`20
`
`I
`-
`I
`.
`
`,
`
`68
`
`OPTION
`CAR“
`
`.
`
`‘
`EVENT
`OETUENCITTINS
`
`I
`I
`I
`I
`I
`.
`—-
`
`-—-
`
`REPRODUCTION
`
`'“SBIIITUFJAION
`POWER
`BUTTON
`
`36
`
`SHUTTER
`
`BUTTON
`
`34
`
`38
`
`
`Io
`
`OPERATION BLOCK
`
`18
`
`IPR2017-02056, Petitioner Google Inc.
`
`Ex. 1011, p. 1
`
`IPR2017-02056, Petitioner Google Inc.
`Ex. 1011, p. 1
`
`

`

`Patent Application Publication
`
`Jun. 10, 2004 Sheet 1 of 12
`
`US 2004/0109066 A1
`
`F|C3.1
`
`mamzwpw>moh
`
`me
`
`zo_Hmo
`
`nm<o
`
`p
`
`Ioaoommmm
`
`loamzo_H:
`
`mvz_<z
`.->mosm2
`
`p_z=uz_
`
`mw<z_
`
`
`
`-mwmoomm.:.............
`
`¥o04mmnxo_mmw<:_ow
`
`wz_wmmo
`
`
`
`H_z==w_z<xoms
`
`Aomhzoov_
`
`mummam
`
`
`
`.xoogm
`
`wz_mwmoomm
`
`H_z:
`
`
`
`>mosm2Iw<4mom
`
`owzo_H<o_zzzzoowe
`
`p_z:Aozpzoo
`
`<mm<zo_p<z=o_mzou
`<mz<mwmm=m4<zmmpz_om
`xmoahmzmm
`omwz_pumhmn
`
`Hzm>m
`
`p.23,
`
`
`
`
`
`
`
`H_z=wz_mwmooxm_zophamZOPHDm
`
`zo_ww_:wz<zp_zo_poznommmmguppaxm
`
`
`
`
`
`
`>mozmz-.....-...|h_z=nomhzoo4am<o
`
`...l.|.......|.,,.....I...........I....;.{..II....onHDm
`
`Nmxuonmwz_mwmoomm.4onmmgomwm
`
`
`
`
`
`
`
`o_m_xoonmzo_h<xmmomm
`
`5:853
`
`IPR2017-02056, Petitioner Google Inc.
`
`EX.1011,p.2
`
`IPR2017-02056, Petitioner Google Inc.
`Ex. 1011, p. 2
`
`
`
`
`
`

`

`Patent Application Publication
`
`Jun. 10, 2004 Sheet 2 of 12
`
`US 2004/0109066 A1
`
`FIG.2
`
` CONTROL UNIT
`REPRODUCT | ON
`PROCESSING UNI T
`
`112
`
`
`
`
`
`F I LE MANAGEMENT
`UNI T
`
`FIG.3
`
`
`
`
`TERMINAL
`
`IPR2017-02056, Petitioner Google Inc.
`
`Ex. 1011, p. 3
`
`IPR2017-02056, Petitioner Google Inc.
`Ex. 1011, p. 3
`
`

`

`Patent Application Publication
`
`Jun. 10, 2004 Sheet 3 of 12
`
`US 2004/0109066 A1
`
`FIG.4
`
`
`
` FILE
`
`SERVER
`
`100
`
`120
`
`IPR2017-02056, Petitioner Google Inc.
`
`Ex. 1011, p. 4
`
`IPR2017-02056, Petitioner Google Inc.
`Ex. 1011, p. 4
`
`

`

`Patent Application Publication
`
`Jun. 10, 2004 Sheet 4 of 12
`
`US 2004/0109066 A1
`
`FIG.5
`
`POWER ON ?
`
`512
`Y
`
`314
`IA‘fakbc‘METS'SO" I
`
`$16
`818
`Y |-|
`
`N '
`
`pom OFF?
`
`DOES EVENT “
`OCCUR ?
`
`
`
`
`
`
`320
`322
` SHOOTING
`Y I-I
`INSTRUCTION ?
`
`324
`326
`
`Y I-I
`REPRODUCTION
`INSTRUCTION ?
`
`828
`
`OTHER PROCESSING
`
`IPR2017-02056, Petitioner Google Inc.
`
`Ex. 1011, p. 5
`
`IPR2017-02056, Petitioner Google Inc.
`Ex. 1011, p. 5
`
`

`

`Patent Application Publication
`
`Jun. 10, 2004 Sheet 5 of 12
`
`US 2004/0109066 A1
`
`FIG.6
`
`ACT IVAT ION
`PROCESS
`
`
`
`
`
`N
`
`ANY IMAGE
`IN BUFFER ?
`
`
`
`
`
`
`
`
`
`I STORING PROCESS I
`
`RETURN
`TO MA IN TASK
`
`S38
`
`IPR2017-02056, Petitioner Google Inc.
`
`Ex. 1011, p. 6
`
`IPR2017-02056, Petitioner Google Inc.
`Ex. 1011, p. 6
`
`

`

`Patent Application Publication
`
`Jun. 10, 2004 Sheet 6 of 12
`
`US 2004/0109066 A1
`
`FICSI?
`
`STORING
`PROCESS
`
`
`CARD
`IDENTIFICATION
`
` S40
`
`
`
`
`IMAGE TRANSMISSION
`
`
`TRANSFER
`
`FROM BUFFER
`
`
`TO MEMORY CARD
`
`
`S48
`
`‘
`
`S46
`
`FILE CREATION COMMAND
`
`
`
`
`
`CLOSE COMMAND
`
`IPR2017-02056, Petitioner Google Inc.
`
`Ex. 1011, p. 7
`
`IPR2017-02056, Petitioner Google Inc.
`Ex. 1011, p. 7
`
`

`

`Patent Application Publication
`
`Jun. 10, 2004 Sheet 7 of 12
`
`US 2004/0109066 A1
`
`FWC3.EB
`
`SHOOTING
`PROCESS
`
`CREATE COMPRESSED
`IMAGE
`
`$60
`
`362
`
`
`IN BUFFER ?
`
`
`ANY IMAGE
`
`Y
`
`I
`
`FIRST STORING
`
`PROCESS
`
`I
`
`S36A
`
`$64
` STORED
`SUCCESSFULLY ?
`
`
`
`
`
`CLEAR BUFFER
`
`I
`
`SECOND STORING
`
`PROCESS
`
`I
`
`3365
`
`SUCCESSFULLY ?
`
`$68
` STORED
`
`
`STORE
`INTO BUFFER
`
`S72
`
`
`
`CLEAR MAIN MEMORY
`
`S70
`
`RETURN
`
`TO MAIN TASK
`
`S74
`
`IPR2017-02056, Petitioner Google Inc.
`
`EX.1011,p.8
`
`IPR2017-02056, Petitioner Google Inc.
`Ex. 1011, p. 8
`
`

`

`Patent Application Publication
`
`Jun. 10, 2004 Sheet 8 of 12
`
`US 2004/0109066 A1
`
`FIG.9
`
`REPRODUCTION
`PROCESSING
`
`N
`
`READ IMAGE
`
`380
`
`
`CARD
`IDENTIFICATION
`
`
`C
`
`882
`
`
`
`see
`
`
`IREIIGII'EII“?
`
`
`S84
`
`N
`
`888
`
`READ IMAGE
`FROM BUFFER
`
`IMAGE RECEPTION
`890
`
`FILE OPEN COMMAND
`
`892
`
`CLOSE COMMAND
`
`REPRODUCTION
`
`“396
`
`RETURN TO
`MAIN TASK
`
`393
`
`IPR2017-02056, Petitioner Google Inc.
`
`Ex. 1011, p. 9
`
`IPR2017-02056, Petitioner Google Inc.
`Ex. 1011, p. 9
`
`

`

`Patent Application Publication
`
`Jun. 10, 2004 Sheet 9 of 12
`
`US 2004/0109066 A1
`
`FIC351O
`
`TERMINATION
`PROCESS
`
`$100
` ANY REMAINING DATA
`YET TO BE STORED ?
`
`Y
`
`N
`
`
`SI()4
`
`
`IS THERE
`
`COMMUNICATION
`
`CARD ?
`
`
`D I SCONNECT
`FROM SERVER
`
`__________
`
`POWER OFF
`
`3108
`
`RETURN
`
`TO MAIN TASK
`
`3110
`
`IPR2017-02056, Petitioner Google Inc.
`
`EX.1011,p.10
`
`IPR2017-02056, Petitioner Google Inc.
`Ex. 1011, p. 10
`
`

`

`Patent Application Publication
`
`Jun. 10, 2004 Sheet 10 of 12
`
`US 2004/0109066 A1
`
`FK311
`
`PARENT THREAD
`
`WAIT FOR CONNECTION
`REQUEST
`
`
`
`
`
`
`
`$150
`
`$152
`
`
`
`3‘ 54
`
`ESTABLISH CONNECTION
`
`ICREATE CHILD THREAD I
`
`
`IPR2017-02056, Petitioner Google Inc.
`
`Ex.1011, p. 11
`
`IPR2017-02056, Petitioner Google Inc.
`Ex. 1011, p. 11
`
`

`

`Patent Application Publication
`
`Jun. 10, 2004 Sheet 11 of 12
`
`US 2004/0109066 A1
`
`FIG.12
`
`CHILD THREAD
`
`D I SPLAY
`SPECIFIC WINDOW
`
`8200
`
`CREATE INDIVIDUAL
`FOLDERS
`
`8202
`
`WAIT FOR COMMAND
`RECEPT I ON
`
`$204
`
`__________________
`
`D I SOONNECT
`
`3207
`
`8206
`
`MUCH COMMAND ?
`
`REPRODUCEO
`
`DIsooIIIIECT FROM
`
`DIGITAL CAMERA
`
`RECEIVE IMAGE
`
`TWEGMEIT
`
`STORE
`
`3210
`
`3216
`
`$208
`
`,
`
`PARENT THREAD
`
`REPRODUGE' STORE
`
`.
`
`DREATE
`DISPLAY Tl-IJMBNAIL
`IMAGE
`
`57-14
`
`
`
`IPR2017-02056, Petitioner Google Inc.
`
`Ex.1011, p. 12
`
`IPR2017-02056, Petitioner Google Inc.
`Ex. 1011, p. 12
`
`

`

`Patent Application Publication
`
`Jun. 10, 2004 Sheet 12 of 12
`
`US 2004/0109066 A1
`
`FIG.13
`
`USER ID: abc
`
`‘34
`
`132
`
`136
`
`130
`
`IPR2017-02056, Petitioner Google Inc.
`
`Ex.1011, p. 13
`
`IPR2017-02056, Petitioner Google Inc.
`Ex. 1011, p. 13
`
`

`

`US 2004/0109066 A1
`
`Jun. 10, 2004
`
`DIGITAL CAMERA, METHOD OF CONTROLLING
`DIGITAL CAMERA, AND FILE SERVER
`
`BACKGROUND OF THE INVENTION
`
`a user operation; and a processing block which applies
`processing to an image. For example, the processing block
`includes any one of the following configurations:
`
`[0001]
`
`1. Field of the Invention
`
`[0002] The present invention relates to a digital camera, a
`technology of controlling the same, and a file server. In
`particular, the invention relates to a digital camera having a
`processing block which applies processing to an image, a
`method of controlling the same, and a file server
`for
`exchanging images with the digital camera.
`
`[0003]
`
`2. Description of the Related Art
`
`[0004] Digital cameras are hot sellers in recent years
`which have created a big market. The volume of shipments
`of digital cameras in Japanese market in 2001 exceeded that
`of film cameras. In 2002, the total volume of shipments
`worldwide is expected to reach 20 million or so. Among the
`factors behind this is handiness which includes the absence
`
`of need for film loading, easy storing of image data, and easy
`photoprint available at home when needed. These are privi-
`leges of digital technology. For an application of the digital
`technology, Japanese Patent Laid-Open Publication No. Hei
`10-276391 proposes a technique for transmitting images
`from an electronic still camera to a plurality of destinations
`easily.
`
`[0005] Digital cameras do show high convenience in
`actual use, though with room for improvement obviously.
`For example, shot images are typically reproduced on the
`LCDs of the digital cameras for checking. Nevertheless, the
`LCDs are limited in size due to the digital camera casings,
`and thus are far from being an environment optimum for
`checking.
`
`[0006] Since digital cameras require no film and thus are
`free of care for misshots, users often take a number of shots
`in an identical scene for the sake of choice later. Displaying
`a plurality of images on the LCD of a digital camera,
`however, shrinks the individual images, in which case the
`pictures are hard to compare and choose. On the other hand,
`printing all the pictures without choice leads to higher cost.
`Not printing but storing alone also raises the cost of the
`recording media. Moreover, greater accumulation of images
`makes it difficult to search for desired images. Despite being
`freed from films, digital cameras eventually leave some to be
`desired in terms of image checking, storing, search, repro-
`duction, printing, etc.
`
`[0007] These problems are essentially ascribable to the
`fact that digital cameras have not yet maximized the advan-
`tages of the digital technology, including simplicity, quick
`operation, and low costs.
`
`SUMMARY OF THE INVENTION
`
`[0008] The present invention has been achieved in view of
`the current circumstances. It is thus an object of the present
`invention to provide a digital camera for maximizing the
`advantages of the digital technology, a method of controlling
`the same, and a file server intended for the digital camera.
`
`[0009] One of the aspects of the present invention relates
`to a digital camera, which comprises: an image pickup
`block; a mechanism control block which controls the image
`pickup block mechanically; an operation block which inputs
`
`(1) A detecting unit which detects an activa-
`[0010]
`tion request for the digital camera, and a communi-
`cation control unit which performs processing for
`establishing a network connection with a file server
`upon detection of the activation request;
`
`(2) A detecting unit which detects an image
`[0011]
`pickup request, and a communication control unit
`which performs processing for transmitting an image
`obtained by image pickup to a file server over a
`network upon obtainment of the image;
`
`(3) A detecting unit which detects an image
`[0012]
`reproduction request, and a communication control
`unit which performs processing for receiving an
`image to be reproduced from a file server over a
`network when the image reproduction request
`is
`detected; and
`
`(4) Any two or more of the configurations (1)
`[0013]
`to (3) in combination.
`
`the detecting units as well as the
`In this case,
`[0014]
`communication units may be integrated with or separated
`from each other. Similarly, any members having the same
`name in this specification may hereinafter be configured
`integrally or separately.
`
`[0015] The “activation request” is one by which the digital
`camera is activated in one way or another, such as by turning
`on the power and by recovery from standby. The “network”
`may be either wireless or wired. Nor does matter whether the
`network uses such facilities as an access point as if on a
`wireless LAN in infrastructure mode, or is of so-called
`peer-to-peer as if in ad-hoc mode. The “file server” may be
`a network node of any architecture as long as it exchanges
`images with the digital camera. The “communication control
`unit” shall apply to both the cases where it performs com-
`munication by itself and where it controls a communication
`unit such as an additional communication card and makes no
`
`communication by itself. The “image obtained by image
`pickup” shall cover both an intact image just picked up and
`an image obtained through compression or the like after
`picked up.
`
`[0016] The various types of processing by the communi-
`cation control unit are activated automatically without
`explicit user instructions at least in some operation mode.
`Even without particular user operations, the file server can
`thus be used to store images into the file server and to
`acquire images from the file server for display on the digital
`camera, or as if it is a recording medium built in the digital
`camera. This enhances user convenience or allows a reduc-
`
`tion in the capacity of the recording apparatus to be built in
`the digital camera.
`
`[0017] Another aspect of the present invention relates to a
`method of controlling a digital camera, which comprises:
`detecting an activation request for a digital camera; and
`establishing a network connection between the digital cam-
`era and a file server upon detection of the activation request.
`
`includes: detecting an image
`[0018] Another aspect
`pickup request for a digital camera; and performing pro-
`
`IPR2017-02056, Petitioner Google Inc.
`
`Ex.1011, p. 14
`
`IPR2017-02056, Petitioner Google Inc.
`Ex. 1011, p. 14
`
`

`

`US 2004/0109066 A1
`
`Jun. 10, 2004
`
`cessing for transmitting an image obtained by image pickup
`to a file server over a network upon obtainment of the image.
`
`the communication unit but
`(2) When not
`[0027]
`recording device and the buffer memory are present:
`
`the
`
`[0019] Still another aspect includes: detecting an image
`reproduction request for a digital camera; and performing
`processing for receiving an image to be reproduced from a
`file server over a network when the image reproduction
`request is detected.
`
`[0020] Of the foregoing three aspects, any two or more
`may be performed in combination.
`
`[0021] Still another aspect includes: checking a digital
`camera for the presence or absence of at least one among a
`buffer memory intended for temporarily image retention, a
`recording device intended for more permanent image reten-
`tion, and a communication unit which makes a file server
`retain an image over a network; designating a storing
`destination of an image obtained by image pickup depending
`on the check result; and storing the image obtained by image
`pickup into the storing destination designated. The buffer
`memory, the recording device, and the communication unit
`are each mounted on the digital camera fixedly or detach-
`ably. For example, the buffer memory is a fixed memory, the
`recording device a memory card, and the communication
`unit a communication card. The “more permanent” refers to
`having properties suited to data storage with greater capac-
`ity, lower price per bit, and higher storage security in terms
`of volatility and the like.
`
`In this aspect, for example, images are stored in the
`[0022]
`following order of priority.
`
`(1) When the communication unit, the recording
`[0023]
`device, and the buffer memory are all present:
`
`[0024] Case 1: the communication unit is given the
`first priority, the recording device the second, and the
`buffer memory the third. In this case, since images
`can be stored into the file server over the network, it
`is possible to eliminate the recording apparatus
`inside the digital camera or reduce the capacity
`thereof.
`
`[0025] Case 2: the recording device is given the first
`priority, the communication unit the second, and the
`buffer memory the third. In this case, the processing
`time can be reduced due to the storing to the local
`recording device. When the recording device is
`detected to be full, remaining images may be stored
`into the file server. Idling time and the like of the
`digital camera may be used to transfer the images
`stored in the recording device to the file server via
`the communication unit so that the recording device
`has greater free space.
`
`[0026] Case 3: the buffer memory is given the first
`priority, either one of the communication unit and the
`recording device the second, and the other the third.
`In this case, images can be accumulated easily even
`in continuous shooting since the images can be
`stored into the buffer memory which is typically high
`in writing speed. As in the case 2, idling time and the
`like may be used to transfer the images stored in the
`buffer memory to the file server or the recording
`device so that the buffer memory has greater free
`space.
`
`If priority is given to the recording device, it is
`[0028]
`possible to store a greater number of images since the
`recording device typically has a capacity greater than that of
`the buffer memory. On the other hand, giving priority to the
`buffer memory facilitates writing and reading images at high
`speed.
`
`(3) When not the recording device but the com-
`[0029]
`munication unit and the buffer memory are present:
`
`If priority is given to the communication unit, it is
`[0030]
`possible to store a greater number of images since the file
`server typically has a capacity greater than that of the buffer
`memory. On the other hand, giving priority to the buffer
`memory facilitates writing and reading images at high
`speed.
`
`(4) When not the buffer memory but the commu-
`[0031]
`nication unit and the recording device are present:
`
`[0032] The same effects as those of the cases 1 and 2
`in (1) are obtained.
`
`invention
`the present
`[0033] Still another aspect of
`includes: detecting a predetermined operation not directly
`intended for image storing, such as an activation operation
`and shooting operation of a digital camera; and transferring
`an image saved in a buffer memory of the digital camera to
`a recording apparatus more permanent
`than the buffer
`memory, such as a memory card loaded in the digital camera
`and a file server, when the predetermined operation is
`detected. According to this aspect, images can be stored
`permanently through background processing without delib-
`erate user instructions for image storing.
`
`[0034] Still another aspect of the present invention is a file
`server available to store images of a digital camera. The file
`server comprises a communication unit and a control unit,
`the control unit including: a file management unit which
`stores an image file when the communication unit receives
`the image file over a network; and a reproduction processing
`unit which reproduces the image file for screen display upon
`reception of the image file. Since this file server not only
`stores but also reproduces the image file upon reception, the
`image can be checked quickly.
`
`Incidentally, any combinations of the foregoing
`[0035]
`components, and the expressions of the present invention
`converted among methods, apparatuses, systems, computer
`programs, recording media, and the like are also intended to
`constitute applicable aspects of the present invention.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`[0036] FIG. 1 is a block diagram of a digital camera
`according to an embodiment;
`
`[0037] FIG. 2 is a block diagram of a file server according
`to the embodiment;
`
`[0038] FIG. 3 is a block diagram of a file management
`system which is composed of the digital camera and the file
`server according to the embodiment;
`
`[0039] FIG. 4 is a block diagram showing another con-
`figuration of the file management system;
`
`IPR2017-02056, Petitioner Google Inc.
`
`Ex.1011, p. 15
`
`IPR2017-02056, Petitioner Google Inc.
`Ex. 1011, p. 15
`
`

`

`US 2004/0109066 A1
`
`Jun. 10, 2004
`
`[0040] FIG. 5 is a flowchart showing the processing of a
`main task of the digital camera;
`
`[0041] FIG. 6 is a flowchart of an activation process of the
`digital camera;
`
`[0042] FIG. 7 is a flowchart of a storing process of the
`digital camera;
`
`[0043] FIG. 8 is a flowchart of a shooting process of the
`digital camera;
`
`[0044] FIG. 9 is a flowchart of a reproduction process of
`the digital camera;
`
`[0045] FIG. 10 is a flowchart of a termination process of
`the digital camera;
`
`[0046]
`SCIVCI;
`
`FIG. 11 is a flowchart of a parent thread on the file
`
`[0047] FIG. 12 is a flowchart of a child thread on the file
`server; and
`
`[0048] FIG. 13 is a diagram showing an example of
`display on a screen of the display on the file-server side.
`
`DETAILED DESCRIPTION OF THE
`PREFERRED EMBODIMENT
`
`[0049] FIG. 1 shows the configuration of a digital camera
`10 according to an embodiment. The digital camera 10
`includes an image pickup block 12, a mechanism control
`block 14, a processing block 16, an operation block 18, an
`LCD 22, and a card slot 20. The image pickup block 12
`shoots a subject under user instructions. The mechanism
`control block 14 exercises mechanical controls over the
`
`image pickup block 12, including zooming, focusing, and
`aperture setting. The processing block 16 applies various
`types of processing to an image shot by the image pickup
`block 12. The operation block 18 inputs user instructions
`and transmits the same to the processing block 16. The LCD
`22 reproduces and displays an image. The card slot 20
`retains an option card 68 detachably. These components
`exchange data and commands with one another via a system
`bus 76.
`
`[0050] Of these components, the processing block 16 in
`particular is realized, in terms of hardware, by a CPU, an
`image processing LSI, various memory devices, etc. In
`terms of software, the processing block 16 is achieved by an
`image processing program, a memory or buffer control
`program, an option card control program, a user interface
`program, and the like. The foregoing blocks are in units of
`functions to be achieved by the cooperation of the hardware
`and software, but not necessarily in one-to-one correspon-
`dence with actual devices.
`
`it will be readily understood by those
`[0051] Besides,
`skilled in the art that the configuration of FIG. 1 has a
`considerably high degree of flexibility as to which part is
`realized in hardware or software, and various modifications
`are covered by the present
`invention.
`Incidentally,
`the
`mechanism control block 14 may be realized by a dedicated
`CPU or achieved by sharing the CPU of the processing block
`16.
`
`image to the A/D converter 30 as an analog image signal.
`The A/D converter 30 subjects this signal to A/D conversion
`to output digital image data to the processing block 16. A
`not-shown diaphragm, and a mechanical shutter in some
`cases, is/are placed between the lens 26 and the CCD 28. In
`addition, a not-shown signal processing unit is interposed
`between the CCD 28 and the A/D converter 30 so that such
`processing as a white balance adjustment is performed on
`each of R, G, and B signals.
`
`[0053] The processing block 16 comprises an image pro-
`cessing unit 44, a main memory 46, a reproduction process-
`ing unit 48, an event detecting unit 50, a transmission
`processing unit 52, and a flash memory 60. The image
`processing unit 44 inputs the image data output from the
`image pickup block 12, and encodes and compresses the
`same according to a JPEG (Joint Photographic Experts
`Group) scheme or the like. The reproduction processing unit
`48 decompresses the image under user instructions, and
`outputs the resultant to the LCD 22. The main memory 46
`is used as a work area in compressing and decompressing
`images, as well as a resident area for a variety of control
`programs. The event detecting unit 50 detects user instruc-
`tions input from the operation block 18 as events. The
`transmission processing unit 52 stores images that are shot
`and compressed,
`to a designated storing destination. The
`transmission processing unit 52 also reads images to be
`reproduced from the destination. The flash memory 60
`includes an internal buffer area 56 (hereinafter, referred to as
`“buffer 56”) for functioning as an internal buffer, and a
`network configuration area 58 for storing network configu-
`ration information such as the IP addresses of the digital
`camera 10 and a file server to be described later. A network
`connection will be established on the basis of the network
`
`configuration information. The event detecting unit 50
`detects the user instructions to the operation block 18 by
`such means as software polling, hardware-based button
`press signals, and interruption processing resulting from the
`signals.
`
`[0054] The transmission processing unit 52 includes a
`buffer processing unit 64, a card identification unit 66, a
`communication control unit 72, and a memory card control
`unit 74. The buffer processing unit 64 reads and writes image
`data from/to the buffer 56. It also determines whether or not
`any image is saved in the buffer 50. For the sake of read and
`write, the buffer processing unit 64 has a memory control
`circuit intended for the buffer 56. Whether an image is saved
`or not can be indicated by such means as flagging the
`presence or absence of significant data in each of small
`image-storing subareas of the buffer 56, or storing an image
`in an image file formant with the presence or absence of the
`image shown in its header region. The buffer processing unit
`64 thus determines, by software, whether an image is saved
`or not;
`
`[0055] The card identification unit 66 identifies the type of
`the option card 68 loaded in the card slot 20. The identifi-
`cation can be effected by reading a card ID stored in the
`system register inside the option card 68, or by determining
`the card ID from the combination of pins powered or
`grounded inside the option card 68.
`
`[0052] The image pickup block 12 includes a lens 26, a
`CCD 28, and an A/D converter 30. The lens 26 forms the
`image of a subject on the CCD 28. The CCD 28 outputs the
`
`[0056] The communication control unit 72 exercises con-
`trol necessary to communicate with the file server by using
`the option card 68 loaded in the card slot 20 if the option
`
`IPR2017-02056, Petitioner Google Inc.
`
`Ex.1011, p. 16
`
`IPR2017-02056, Petitioner Google Inc.
`Ex. 1011, p. 16
`
`

`

`US 2004/0109066 A1
`
`Jun. 10, 2004
`
`card 68 is a communication card. The communication con-
`trol unit 72 includes a communication driver IC and a driver
`
`program, for example. The memory card control unit 74
`controls the read and write of image data from/to the option
`card 68 loaded in the card slot 20 if the option card 68 is a
`memory card. For example, the memory card control unit 74
`includes a data transmission circuit conforming to the gen-
`eral-purpose bus specification of the card slot 20.
`
`[0057] The operation block 18 includes a shutter button
`34, a reproduction instruction button 36, and a power button
`38. When the shutter button 34 is pressed, the instruction is
`transmitted through the event detecting unit 50 and the
`mechanism control block 14 to the image pickup block 12
`for image shooting. When the reproduction instruction but-
`ton 36 is pressed, the instruction is issued to the reproduction
`processing unit 48 through the event detecting unit 50. The
`reproduction processing unit 48 decompresses an image
`which has been compressed at
`the time of storing, and
`outputs the resultant to the LCD 22. Hereinafter, an image
`compressed by the image processing unit 44 will be referred
`to as “compressed image” when distinction is necessary. The
`compressed image is read from the buffer 56, a memory card
`which is the option card 68, or the file server. Before a
`compressed image in the main memory 46 is stored into any
`of those three locations, the compressed image is read from
`the main memory 46 for reproduction.
`
`[0058] The power button 38 is one for switching on/off the
`power of the entire digital camera 10. When the digital
`camera 10 is off, pressing the power button 38 is detected by
`the event detecting unit 50 as an activation request, which is
`followed by an activation process. When the digital camera
`10 is on, pressing the power button 38 is detected by the
`event detecting unit 50 as a termination request, which is
`followed by the processing for turning off the digital camera
`10.
`
`[0059] FIG. 2 shows the configuration of a file server 100
`which exchanges image data with the digital camera 10. The
`file server 100 comprises a communication unit 102 for
`communicating with the digital camera 10 over a network,
`and a control unit 104 for controlling the entire file server
`100. The control unit 104 has a reproduction processing unit
`106 and a file management unit 108. When a compressed
`image sent from the digital camera 10 is received by the
`communication unit 102, the receiving operation triggers the
`reproduction processing unit 106 to decompress the com-
`pressed image and display the resultant image on a display
`112. The receiving operation also triggers the file manage-
`ment unit 108 to store the compressed image into an image
`storing apparatus 110. The reproduction processing unit 106
`and the file management unit 108 both operate automatically
`without any manual operation. In order for compressed
`images transmitted from a plurality of digital cameras 10, or
`a plurality of users, to be displayed and managed separately,
`the reproduction processing unit 106 creates user-specific
`display windows by known methods, so that images of the
`users are displayed on the respective display windows.
`Similarly, to store the images of the users separately, the file
`management unit 108 creates user-specific folders in the
`image storing apparatus 110 by known methods, so that the
`images are classified and stored in the folders.
`
`and the file server 100. Here, an access point 122 for the
`digital camera 10 to use for communication is connected
`with the file server 100 and an user terminal 124 over the
`
`Internet 126. The digital camera 10 and the access point 122
`communicate with each other over a wireless LAN. Accord-
`
`ing to this configuration, images shot by the user with the
`digital camera 10 are accumulated into the file server 100 via
`the access point 122 and the Internet 126. The user terminal
`124 can download necessary images from the file server 100
`when required. Note that the file server 100 may be con-
`structed inside the user terminal 124. In this case, the images
`shot by the user with the digital camera 10 are displayed on
`the user terminal 124 through operations to be described
`later successively with greater convenience.
`
`[0061] FIG. 4 shows another configuration the file man-
`agement system 120. Here, the digital camera 10 and the file
`server 100 are connected with each other over a wireless
`LAN in ad-hoc mode. The file server 100 is constructed
`
`inside the user terminal 124. This configuration makes the
`access point 122 and the Internet 126 in FIG. 3 unnecessary.
`Thus, for example, the user can carry the digital camera 10
`and the user terminal 124, a note PC, together so that images
`shot by the digital camera 10 are checked on the user
`terminal 124 through operations to be described later suc-
`cessively.
`
`[0062] Description will now be given of the operations
`according to the foregoing configurations. The present
`embodiment is characterized in that the images shot by the
`digital camera 10 are transmitted to the file server 100 in
`succession, and are stored therein and displayed succes-
`sively. For example, when the user uses the file management
`system 120 of FIG. 3, the shot images can thus be checked
`on the display 112 of FIG. 2 efficiently, not necessarily on
`the LCD 22 of the digital camera 10, a display of relatively
`small screen. That is,
`the file server 100 is used as the
`recording medium of the digital camera 10 to fully utilize the
`abundant
`storage capacity and greater display screen
`thereof. When the user wishes to view an image on the
`digital camera 10, the necessary image is downloaded from
`the file server 100 to the digital camera 10 according to the
`reproduction instruction, and reproduced on the LCD 22 of
`the digital camera 10. This leads to cost advantage since the
`digital camera 10 need not incorporate large memories for
`storing a number of images.
`
`[0063] Now, if the option card 68 loaded in the card slot
`20 of the digital camera 10 is not the communication card,
`the communication with the file server 100 is impossible. In
`this case,
`the digital camera 10 stores shot images to a
`memory card if the memory card is loaded as the option card
`68. Moreover, images to be reproduced are also loaded from
`this memory card and displayed on the LCD 22. When
`neither the memory card nor the communication card is
`loaded as the option card 68, the digital camera 10 stores an
`image into the buffer 56 which is temporary saving means.
`Hence, the buffer 56 has only to have a minimum memory
`capacity

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