JP2008022459A - Digital camera and digital camera system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To easily achieve product registration of a digital camera. <P>SOLUTION: A camera cap has a cap memory storing cap information including cap identification information for identifying an individual product, and a light-emitting section for converting the cap information into an optical signal and outputting the signal to a light-receiving section of the camera. A camera body receives the cap information from the camera cap, and transmits the received cap information and camera information in the camera body to a server. The server utilizes the cap identification information included in the cap information in order to identify a user and manages to manage the user. The user connects the camera cap to the camera body and registers a product at the camera body via a network. Thus, the product registration of the digital camera can be easily achieved. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to a digital camera capable of registering a product.

In a digital camera, in order to register a purchased product, a user accesses a home page on a server, which is a computer of the manufacturer of the digital camera, via a network from a personal computer, for example. Then, the user inputs information necessary for product registration according to the menu on the homepage, and registers the product. Product registration can also be performed by connecting a digital camera to a personal computer and transmitting identification information unique to the digital camera from the digital camera to the server via the personal computer. The server manages the received identification information unique to the digital camera in association with the personal information of the user (see, for example, Patent Document 1).
JP 2002-41891 A

With this type of digital camera, the user needs to perform many tasks such as starting up a personal computer, entering a homepage URL (Uniform Resource Locator), entering a product model number, and entering contact information. become. Thus, the work performed by the user for product registration is complicated.
In addition, every time a user replaces a digital camera or purchases an accessory, the user needs to start a personal computer, connect the digital camera to the personal computer, input a home page URL, input user information, and the like.

  An object of the present invention is to easily realize product registration or update of a digital camera.

In the present invention, the camera cap is stored in the memory in which the cap information including cap identification information for identifying the individual is stored, the operation unit operable by the user, and in response to the operation of the operation unit. And a light emitting unit that outputs the cap information as an optical signal.
A camera body includes a light receiving unit that receives cap information as an optical signal, a memory that stores camera information including camera identification information for individually identifying a product, and a computer that connects the cap information and camera information to a network. A communication interface unit for transmitting to the network.

  According to the present invention, the user registers the product of the digital camera by connecting the camera cap and the camera body, and connecting the camera body and the network. This makes it easy to register a digital camera product.

Hereinafter, embodiments of the present invention will be described with reference to the drawings.
FIG. 1 shows a first embodiment of the present invention. In this embodiment, the digital camera includes a camera body 10, a lens unit 12, and a camera cap 14. The digital camera system includes a server 18 that is a manufacturer's computer connected to the network 16 and the above-described digital camera.

  The camera cap 14 includes a cap memory 20, a light emitting unit 22, an operation unit 24, a battery 26, and a lens connection unit 28. The camera cap 14 is connected to the front surface of the lens unit 12 in order to protect the lens. For example, in this embodiment, the lens connecting portion 28 of the camera cap 14 is connected to a cap mount 30 formed on the front surface of the lens portion 12, and the camera cap 14 is attached to the camera body 10.

  The cap memory 20 is formed of, for example, a flash memory or a ROM (Read Only Memory). The cap memory 20 may be formed by a program element such as a fuse. Cap information CAINF is written in the cap memory 20 by the manufacturer of the digital camera before the camera cap 14 is shipped. Here, the cap information CAINF includes, for example, cap identification information for individually identifying the camera caps 14 and URL (Uniform Resource Locator) information indicating a connection destination address of a homepage accessed for product registration. Yes. Details of the cap information CAINF will be described later with reference to FIG. The URL information may be stored in the camera body 10.

  The operation unit 24 is, for example, a push button type switch, and is operated by the user in order to transmit the cap information CAINF to the camera body 10. The light emitting unit 22 includes, for example, a light emitting diode (LED) and a circuit for controlling a light emitting pattern of the light emitting diode. The light emitting unit 22 converts the cap information CAINF stored in the cap memory 20 into an optical signal OPTSIG in response to the user pressing the operation unit 24. Then, the light emitting unit 22 outputs the converted optical signal OPTSIG toward the image sensor 32 of the camera body 10 via the photographing lens LENS. Here, the optical signal OPTSIG is, for example, a light blinking pattern indicating the data of the cap information CAINF.

The battery 26 is, for example, a button battery and is a power source for the light emitting unit 22 and the cap memory 20.
The lens unit 12 includes a photographing lens LENS, a lens memory 34, a cap mount 30, and a body mount 36. The lens memory 34 is formed of, for example, a flash memory or a ROM. In the lens memory 34, lens information LINF including lens identification information for identifying the type and individual of the lens unit 12 is written by the manufacturer of the digital camera before the lens unit 12 is shipped. The lens identification information may be information for identifying only the type of the lens unit 12. Details of the lens information LINF will be described later with reference to FIG. The body mount 36 is connected to the lens mount 38 of the camera body 10. That is, the digital camera of this embodiment is a single-lens reflex camera.

The camera body 10 includes an image sensor 32, a photometric sensor 40, a camera memory 42, a CPU, a communication interface unit 44, a shutter switch 46, a mirror MIRR, a recording medium 48, a monitor 50, a finder 52, a camera operation unit 54, and a lens mount 38. Have.
The image sensor 32 is, for example, a CCD image sensor or a CMOS image sensor. The image sensor 32 converts an image of a subject incident through the photographing lens LENS into an electric signal, and outputs the converted electric signal to the CPU. Further, the image sensor 32 receives the optical signal OPTSIG output from the camera cap 14, converts the received optical signal OPTSIG into an electrical signal, and outputs the converted electrical signal to the CPU.

The photometric sensor 40 is, for example, a CCD image sensor or a CMOS image sensor. The photometric sensor 40 is an element for measuring the intensity of light in order to determine the exposure time and the like of the image sensor 32.
The camera memory 42 is formed by, for example, a flash memory or a ROM. In the camera memory 42, a program executed by the CPU is written. Further, camera information CBINF including the camera identification information for identifying the model and individual of the camera body 10 is written in the camera memory 42 by the manufacturer of the digital camera before the camera body 10 is shipped. The camera identification information may be information for identifying only the model of the camera body 10. Details of the camera information CBINF will be described later with reference to FIG.

  The CPU performs signal processing such as image processing and control processing such as exposure control. In addition, the CPU receives an electrical signal converted from the optical signal OPTSIG by the image sensor 32 and demodulates the received electrical signal into cap information CAINF. The communication interface unit 44 is connected to the network 16 and communicates with the server 18 using, for example, a USB (Universal Serial Bus) interface or a LAN (Local Area Network) interface.

  The mirror MIRR responds to the depression of the shutter switch 46 in order to allow the optical signal from the photographic lens LENS to reach the image sensor 32, for example, as shown in FIG. Jump up. Further, the mirror MIRR jumps upward in order to receive the optical signal OPTSIG output from the camera cap 14 by the image sensor 32 at the time of product registration. The recording medium 48 stores captured image data. The monitor 50 displays captured images and menu screens. The menu screen includes a pressing display of the operation unit 24 of the camera cap 14 and the like. The camera operation unit 54 is operated by a user in order to set various parameters of the camera body 10.

  The camera body 10 receives the cap information CAINF from the camera cap 14 by the operation of the CPU, and accesses the home page on the server 18 via the network 16 according to the URL information indicating the connection destination address included in the received cap information CAINF. Access automatically. The camera body 10 receives lens information LINF from the lens unit 12. Then, the camera body 10 transmits the cap information CAINF, the lens information LINF, and the camera information CBINF of the camera body 10 to the server 18. The server 18 uses the cap identification information included in the received cap information CAINF for user identification, and performs user management of the digital camera. A detailed flow of digital camera product registration will be described with reference to FIG.

  The user connects the camera cap 14 to the camera body 10 via the lens unit 12 and connects the camera body 10 and the network 16 via a USB cable or the like, thereby registering the product of the digital camera. When possessing a plurality of digital cameras, the user determines one camera cap 14 to be used for product registration. Then, the user only has to connect the camera cap 14 selected for product registration to the camera body 10 desired to register the product, and connect the camera body 10 and the network 16. Thereby, even when a plurality of digital cameras are owned, product registration can be easily realized.

  FIG. 2 shows an example of the outer shape of the camera cap 14 of the digital camera shown in FIG. FIG. 2A shows the front surface of the camera cap 14 (the surface opposite to the lens unit 12 shown in FIG. 1). An operation unit 24 and a knob 56 are respectively formed on the front and side surfaces of the camera cap 14. The operation unit 24 is a push button type switch and is formed at the corner of the camera cap 14. The knob 56 is a knob for mounting and demounting the camera cap 14 and the lens unit 12 shown in FIG. The knob 56 has, for example, a spring-type configuration, and is pressed from the outside to the inside to release the fixation between the lens connecting portion 28 and the cap mount 30 shown in FIG. 1 and returns to the original position when the knob 56 is released. Returning, the lens connecting portion 28 and the cap mount 30 are fixed.

  FIG. 2B shows the back surface of the camera cap 14 (the surface on the lens unit 12 side shown in FIG. 1). An output part EOUT of the light emitting part 22, for example, a light emitting diode and a collimating lens, is provided at the center of the back surface of the camera cap 14. By forming the output unit EOUT at the center of the camera cap 14, when the camera cap 14 and the lens unit 12 are connected, the output unit EOUT is positioned on the optical axis of the photographing lens LENS. Thereby, the optical signal OPTSIG can be efficiently received by the imaging device 32 shown in FIG.

  FIG. 3 shows an example of the configuration of the cap information CAINF, camera information CBINF, and lens information LINF of the digital camera shown in FIG. The cap information CAINF includes an identifier type IDTYP (CapID), cap identification information CAID (1234567), a sales area SAREA (USA), and a connection destination address URL (www.XXX). The identifier type IDTYP (CapID) is information indicating an identifier or a product type. For example, the identifier type IDTYP (CapID) indicates that the data group including the identifier type IDTYP (CapID) is cap information CAINF. The cap identification information CAID (1234567) is information for individually identifying the camera cap 14. A sales area SAARE (USA) indicates an area where the camera cap 14 is sold. The connection destination address URL (www.XXX) indicates the URL of a home page accessed for product registration.

  The camera information CBINF includes camera identification information CBID (D200; for example, camera model) for identifying the model of the camera body 10, a serial number SNO (0123456) set by the manufacturer when the camera body 10 is manufactured, and sales. It includes information on the area SAREA (USA). The lens information LINF includes lens identification information LID (AF-S VR Zoom Nikkor ED 70-200 mmF2.8G; for example, lens type) for identifying the type of the lens unit 12, serial number SNO (0123457), and sales area SAREA. (USA) information is included.

Since the information of the connection destination address URL (www.XXX) is stored in the cap information CAINF, the user can save the trouble of searching the URL of the home page on the server 18 from a manual or the like for product registration. Thus, the user can easily access the home page on the server 18 from the camera body 10 when registering the product of the digital camera.
Note that, by connecting the camera body 10 to a personal computer, the camera body 10 transfers the URL of the home page to the personal computer, and a WWW (World Wide Web) browser displays the home page on the server 18 on the personal computer. Good.

  FIG. 4 shows an example of a product registration database DB managed by the server 18 shown in FIG. The database DB for product registration is composed of a reference number No., registration date / time RDATE, cap identification information CAID, camera identification information CBID, and lens identification information LID. The product registration database DB may be configured by adding the serial number SNO of the camera body 10 and the serial number SNO of the lens unit 12 to the above-described configuration. The cap identification information CAID is used as a user identifier.

  For example, in the reference numbers No. 001 to 003, the cap identification information CAID (1234567) is all the same, so that the same user has the camera bodies D200, D50, D2Hs and two lenses (AF-S VR Zoom Nikkor ED 70- 200mmF2.8G and AF-S DX Zoom Nikkor ED 18-55mmF3.5-5.6G). Reference number No. 004 indicates that one user owns one camera set (camera body D70s and lens AF-S DX Zoom Nikkor ED 18-70mmF3.5-4.5G). With reference numbers No. 005 and 006, the cap identification information CAID (7890xyz, 3334444) is different, so that multiple users have the same camera set (camera body D2x and lens AF-S VR Zoom Nikkor ED 200-400mmF4G). Is shown. As described above, the database DB for product registration does not have an area for storing user personal information. Since the cap identification information CAID is used instead of the personal information of the user, the anonymity of the user can be maintained if necessary. The cap identification information CAID registered in the product registration database DB may be associated with a database (not shown) in which customer information is registered so that user management can be performed using the product registration database DB. .

  FIG. 5 shows an example of the product registration menu of the digital camera shown in FIG. The display on the monitor 50 is performed by the CPU of the camera body 10 in accordance with a program stored in the camera memory 42, for example. For example, when the menu button MB of the camera operation unit 54 is pressed by the user, the CPU displays a main menu screen on the monitor 50.

  The main menu has a lower menu which is a menu in a lower hierarchy such as a product registration menu and a parameter setting menu for setting various parameters of the camera body 10. For example, the user operates the rotary switch RSW of the camera operation unit 54 to select the lower menu. For example, the lower menu selected corresponding to the rotation of the rotary switch RSW is highlighted. The user presses the enter button of the rotary switch RSW when the lower menu to be executed is highlighted.

  The product registration menu is registered from the registration mode for registering the product owned by the user, the reference mode for checking the registration status of the product owned by the user, and the database DB shown in FIG. Has a delete mode for deleting products. For example, on the product registration menu screen (the upper diagram), a message for selecting a registration mode, a reference mode, and a deletion mode is displayed on the monitor 50.

  The selection of any one of the registration mode, the reference mode, and the deletion mode is performed by the same operation as the selection of the lower menu described above, for example. In the registration mode screen (the leftmost figure in the lower row), for example, a message indicating that the operation unit 24 of the camera cap 14 is pressed is displayed on the monitor 50. The reference mode and the deletion mode are also selected by the same operation as in the registration mode. The flow of the registration mode, the reference mode, and the deletion mode will be described with reference to FIGS. 6, 7, and 8 to be described later.

  FIG. 6 shows an example of the registration mode flow of the digital camera shown in FIG. Steps S100 and S110 are mechanically performed by the camera cap 14. Steps S200 to S270 are performed by the CPU of the camera body 10 according to a program stored in the camera memory 42, for example. Steps S300 to S310 are performed according to a program on the server 18.

  Prior to steps S <b> 100 and S <b> 200, the camera cap 14 is connected in advance to the camera body 10 via the lens unit 12. The camera body 10 is connected to the network 16 in advance and is selected in advance as a registration mode for product registration. Since the registration mode is selected, the mirror MIRR of the camera body 10 does not shield the front part of the image sensor 32 so that the optical signal OPTSIG reaches the image sensor 32, for example, as shown in FIG. It is in a state of jumping upward.

First, in step S <b> 200, the CPU of the camera body 10 displays on the monitor 50 a message indicating that the operation unit 24 of the camera cap 14, for example, an operation button is pressed.
In step S100, the camera cap 14 mechanically detects whether or not the operation unit 24 has been pressed. The camera cap 14 waits until the operation unit 24 is pressed. When the pressing of the operation unit 24 is detected, the process proceeds to step S110. In step S110, the light emitting unit 22 of the camera cap 14 reads the cap information CAINF from the cap memory 20, and outputs the read cap information CAINF as the optical signal OPTSIG.

  In step S210, the image sensor 32 of the camera body 10 converts the optical signal OPTSIG into an electrical signal. The CPU demodulates the converted electric signal into cap information CAINF. In step S220, the CPU of the camera body 10 reads lens information LINF stored in the lens memory 34 from the lens unit 12. In step S230, the CPU displays a list of contents of the cap information CAINF, camera information CBINF, and lens information LINF on the monitor 50. In step S240, the CPU displays a confirmation message on the monitor 50 as to whether to register the camera information CBINF and the lens information LINF in the server 18.

  In step S250, the CPU determines whether to register the camera information CBINF and the lens information LINF in the server 18. When the determination result of the CPU is registered, the process proceeds to step S260. When the determination result of the CPU is not registered, the CPU discards the data of the camera information CBINF and the lens information LINF and ends the registration mode. In step S260, the CPU issues a command to the communication interface unit 44 to access the server 18 of the connection destination address URL included in the cap information CAINF. Further, the CPU transmits cap information CAINF to the communication interface unit 44. The communication interface unit 44 accesses the designated server 18 via the network 16 and transmits cap information CAINF to the server 18.

  In step S300, the server 18 authenticates whether the received cap information CAINF is correct. If the cap information CAINF is correct, the server 18 uses the cap identification information CAID included in the cap information CAINF for user identification. Since the cap identification information CAID is used instead of the user's personal information, the user's anonymity can be maintained.

In step S <b> 270, the CPU transmits the camera information CBINF and the lens information LINF to the communication interface unit 44. The communication interface unit 44 transmits camera information CBINF and lens information LINF to the server 18.
In step S310, the server 18 registers the received camera information CBINF and lens information LINF in association with the cap identification information CAID, for example, as shown in FIG. 4 described above. For example, if the cap identification information CAID is not registered in the database DB of the server 18 at the time of the authentication of the cap information CAINF in step S300, it is newly registered as a new user. When the user buys a camera body or the like, the purchased camera body is registered in association with the already registered cap identification information CAID.

  FIG. 7 shows an example of the flow of the reference mode of the digital camera shown in FIG. Steps S100, S110, S200, S210, S260, and S300 are the same as the registration mode flow shown in FIG. Steps S232 to S282 are performed by the CPU of the camera body 10 according to a program stored in the camera memory 42, for example. Step S312 is performed according to a program on the server 18. In the reference mode, the collection of the lens information LINF in step S220 shown in FIG. 6 is not performed.

  In step S232, the CPU displays the contents of the cap information CAINF on the monitor 50. In step S <b> 242, the CPU displays a message on the monitor 50 as to whether to refer to a list of products registered in the server 18. In step S252, the CPU determines whether to refer to a list of registered products. When the determination result of the CPU refers, the process proceeds to step S260. When the determination result of the CPU does not refer, the CPU ends the reference mode. In step S <b> 260, the communication interface unit 44 transmits cap information CAINF to the server 18.

  In step S300, the server 18 authenticates whether the received cap information CAINF is correct. In step S312, the server 18 transmits the camera information CBINF and the database DB of the lens information LINF associated with the cap identification information CAID of the received cap information CAINF to the camera body 10. In step S282, the CPU displays the received database DB on the monitor 50.

As described above, since the cap identification information CAID included in the cap information CAINF is used for user identification, the user can check the registered product list without providing the user's personal information. Since the cap identification information CAID is used instead of the user's personal information, the user's anonymity can be maintained.
FIG. 8 shows an example of the flow of the deletion mode of the digital camera shown in FIG. Steps S100, S110, S200-S230, S260, and S300 are the same as the flow of the registration mode shown in FIG. Steps S244 to S274 are performed by the CPU of the camera body 10 according to a program stored in the camera memory 42, for example. Step S314 is performed according to a program on the server 18.

  In step S244, the CPU displays a message on the monitor 50 to select camera information CBINF or lens information LINF to be deleted. In step S246, the CPU displays a confirmation message on the monitor 50 as to whether to delete the selected camera information CBINF or lens information LINF from the server 18. In step S254, the CPU determines whether to delete the camera information CBINF or the lens information LINF from the server 18. When the determination result of the CPU is deleted, the process proceeds to step S260. If the determination result of the CPU is not deleted, the CPU discards the data of the camera information CBINF and the lens information LINF and ends the deletion mode. In step S <b> 260, the communication interface unit 44 transmits cap information CAINF to the server 18.

  In step S300, the server 18 authenticates whether the received cap information CAINF is correct. In step S274, the CPU transmits the camera information CBINF or lens information LINF to be deleted to the communication interface unit 44. The communication interface unit 44 transmits the received camera information CBINF or lens information LINF to the server 18. In step S314, the server 18 deletes the received camera information CBINF or lens information LINF from, for example, the database DB shown in FIG. 4 described above.

As described above, since the cap identification information CAID included in the cap information CAINF is used for user identification, the user does not provide the user's personal information, and the registered products that are no longer necessary are stored in the database DB. Can be deleted. Since the cap identification information CAID is used instead of the user's personal information, the user's anonymity can be maintained.
As described above, in the first embodiment, the user work to be performed for product registration includes the connection between the camera cap 14 and the camera body 10 via the lens unit 12, the connection between the camera body 10 and the network 16, and the like. It is only necessary to operate the operation unit 24 of the camera cap 14. Moreover, since the cap identification information CAID included in the cap information CAINF is used for user identification, the user's anonymity can be maintained. As a result, in this embodiment, product registration of a digital camera can be easily realized while maintaining anonymity of the user.

  FIG. 9 shows a second embodiment of the present invention. The same elements as those described in the first embodiment are denoted by the same reference numerals, and detailed description thereof will be omitted. In the digital camera of this embodiment, a camera cap 14A is formed instead of the camera cap 14 of the first embodiment. In this embodiment, the camera cap 14 </ b> A is directly attached to the camera body 10. For this reason, the digital camera does not connect the lens unit 12 of the first embodiment to the camera body 10 when performing product registration of the digital camera. Other configurations are the same as those of the first embodiment.

  The camera cap 14A is formed with a body connecting portion 36A instead of the lens connecting portion 28 of the camera cap 14 shown in FIG. Other configurations are the same as those of the camera cap 14 of the first embodiment. The body connecting portion 36A is connected to the lens mount 38 of the camera body 10. In the digital camera of this embodiment, the camera body 10 and the camera cap 14A are connected to register a product.

  Since the camera body 10 is not connected to the lens unit 12 of the first embodiment, the lens information LINF collection (step S220) of the flow shown in FIG. 6 described above is not performed. Therefore, the lens information LINF is collected in advance when the lens unit 12 is attached to the camera body 10. The other flow in the product registration mode is the same as the flow shown in FIG. Regarding the flow in the deletion mode, the difference from the first embodiment is the same as in the registration mode. The flow in the reference mode is the same as that in FIG.

  As mentioned above, also in 2nd Embodiment, the effect similar to 1st Embodiment mentioned above can be acquired. Furthermore, in this embodiment, product registration of a digital camera can be performed without connecting the lens unit 12 shown in FIG. 1 to the camera body 10. Therefore, when the user purchases only the camera body 10, the user can save the trouble of connecting the already registered lens unit 12 to the camera body 10 in order to register the camera body 10 as a product.

FIG. 10 shows a third embodiment of the present invention. The same elements as those described in the first embodiment are denoted by the same reference numerals, and detailed description thereof will be omitted. The digital camera of this embodiment is formed by a camera cap 14B and a camera body 10A.
The camera body 10A incorporates a photographic lens LENS. The camera body 10A does not have the mirror MIRR, the photometric sensor 40, and the finder 52 of the first embodiment. Further, the camera body 10A is formed with a cap mount 30A instead of the lens mount 38 of the first embodiment. Other configurations of the camera body 10A are the same as those in the first embodiment. That is, the digital camera of this embodiment is a so-called compact digital camera.

  The camera cap 14B is formed with a lens connection portion 28A instead of the lens connection portion 28 of the camera cap 14 of the first embodiment. Other configurations of the camera cap 14B are the same as those in the first embodiment. In the digital camera of this embodiment, the lens connector 28A of the camera cap 14B and the cap mount 30A of the camera body 10A are connected to register the product.

  Since the camera body 10A incorporates the taking lens LENS, the lens information LINF collection (step S220) of the flow shown in FIG. 6 is not performed. In addition, since the camera body 10A does not include the mirror MIRR shown in FIG. 1 described above, there is no processing for flipping the mirror MIRR upward. The other flow in the product registration mode is the same as the flow shown in FIG. Regarding the flow in the deletion mode, the difference from the first embodiment is the same as in the registration mode. The flow in the reference mode is the same as that in FIG.

As described above, also in the third embodiment, the same effect as in the first embodiment described above can be obtained.
FIG. 11 shows a fourth embodiment of the present invention. The same elements as those described in the first embodiment are denoted by the same reference numerals, and detailed description thereof will be omitted. The digital camera system of this embodiment is configured by adding an accessory 58 to the digital camera of the first embodiment. In the digital camera system, a camera body 10B is formed instead of the camera body 10 of the first embodiment. Other configurations are the same as those of the first embodiment.

  The camera body 10B is formed by adding an accessory interface unit 60 to the camera body 10 of the first embodiment. The accessory interface unit 60 connects the camera body 10 </ b> B and the accessory 58. The accessory 58 is, for example, a light emitting device (generally called a strobe or a speedlight), a GPS (Global Positioning System) unit, a wireless LAN adapter, or the like. The accessory 58 has an accessory memory 62 formed of, for example, a flash memory or a ROM. In the accessory memory 62, accessory information AINF including accessory identification information for identifying the model of the accessory 58 is written by the manufacturer of the accessory 58 before the accessory 58 is shipped. Details of the accessory information AINF will be described later with reference to FIG.

  Since the camera body 10B has the accessory 58 added to the first embodiment, the lens information LINF collection of the flow shown in FIG. 6 described above (step S220), the camera information CBINF, and the lens information LINF are transmitted to the server 18. In addition to the processing of (Step S260), accessory information AINF collection and accessory information AINF are transmitted to the server 18, respectively. In the accessory information AINF collection, the camera body 10B reads the accessory information AINF stored in the accessory memory 62 from the accessory 58 connected to the camera body 10B, for example, according to a program stored in the camera memory 42.

  In the figure, only one accessory 58 is shown to simplify the block diagram of this embodiment, but a plurality of accessories 58 such as a light emitting device and a GPS unit are simultaneously connected to the camera body 10B. it can. In this case, the camera body 10B can read a plurality of accessory information AINF without changing the accessory 58. For this reason, in order to register a plurality of accessories, it is possible to save the trouble of individually changing the accessories.

  In transmitting the accessory information AINF to the server 18, in step S260 of FIG. 6, the accessory information AINF read in the above-described processing is transmitted to the server 18 together with the camera information CBINF and the lens information LINF. The server 18 registers the received accessory information AINF similarly to the camera information CBINF and the lens information LINF. The other flow in the product registration mode is the same as the flow shown in FIG. Regarding the flow in the deletion mode, the difference from the first embodiment is the same as in the registration mode. The flow in the reference mode is the same as that in FIG.

  FIG. 12 shows an example of a configuration of cap information CAINF, camera information CBINF, lens information LINF, and accessory information AINF of the digital camera system shown in FIG. The same elements as those described in FIG. 3 described above are denoted by the same reference numerals, and detailed description thereof will be omitted. The cap information CAINF, the camera information CBINF, and the lens information LINF have the same configuration as that shown in FIG. The accessory information AINF includes accessory identification information AID (SB-800; for example, the type of the light emitting device) for identifying the type of the accessory 58, serial number SNO (0345678), and sales area SAARE (USA). .

  FIG. 13 shows an example of a database DB2 for product registration managed by the server 18 shown in FIG. The same elements as those described in FIG. 4 described above are denoted by the same reference numerals, and detailed description thereof will be omitted. The product registration database DB2 is configured by adding accessory identification information AID to the product registration database DB shown in FIG. For example, the reference numbers No. 001 to 003 indicate that the same user owns the accessories SB-800, SB23, and WT2. Furthermore, it is shown that the camera body D200, the lens (AF-S VR Zoom Nikkor ED 70-200mmF2.8G), the light emitting device SB-800, and the accessory WT2 (for example, a wireless LAN adapter) are registered.

As described above, also in the fourth embodiment, the same effect as that of the above-described first embodiment can be obtained. Furthermore, in this embodiment, even when one user owns a plurality of accessories 58, the cap identification information CAID used for registration is made common so that the user and the plurality of accessories 58 are associated and registered. it can.
In the above-described embodiment, the example in which the cap information CAINF is configured as shown in FIG. 3 has been described. The present invention is not limited to such an embodiment. For example, as shown in FIG. 14, the key code KEYC may be included in the cap information CAINF. The key code KEYC is information corresponding to a password, for example. Also in this case, the same effect as the above-described embodiment can be obtained. Furthermore, since the information corresponding to the password is added to the cap information CAINF, the reliability of the authentication of the cap information CAINF is improved.

  In the above-described embodiment, the example in which the cap information CAINF is configured as shown in FIG. 3 described above has been described. The present invention is not limited to such an embodiment. For example, the cap identification information CAID or the cap information CAINF may be encrypted by the manufacturer with a public key or a secret key managed by the manufacturer before the camera cap 14 is shipped. When the server 18 authenticates the cap information CAINF, the server 18 decrypts the cap identification information CAID or the cap information CAINF encrypted with the public key, using the secret key managed by the manufacturer. Also in this case, the same effect as the above-described embodiment can be obtained. Furthermore, since the manufacturer manages the public key and the private key, the illegally copied cap information CAINF is not decrypted. Thereby, the security of cap identification information CAID can be strengthened.

  In the above-described embodiment, the example in which the camera cap 14 is directly connected to the lens unit 12 or the camera body 10 has been described. The present invention is not limited to such an embodiment. For example, even if the lens connecting portion 28 and the lens mount 38 are connected via an adapter ring for connecting the lens connecting portion 28 of the camera cap 14 and the lens mount 38 of the camera body 10 shown in FIG. Good. Also in this case, the same effect as the above-described embodiment can be obtained. Furthermore, even when the apertures of the lens connecting portion 28 and the cap mount 30 of the lens portion 12 do not match, the camera cap 14 and the lens portion 12 can be connected by converting the connecting portion using an adapter ring. Thereby, the camera cap 14 can be connected to a large number of lens units 12 or the camera body 10. Therefore, the number of products that can be registered with one camera cap 14 can be increased. As a result, the user can register a large number of products in association with one user.

  In the above-described embodiment, as illustrated in FIG. 7, the example in which the server 18 is accessed using the reference mode and the product registration status is confirmed has been described. The present invention is not limited to such an embodiment. For example, using the reference mode, service information related to a registered product, for example, a firmware update program or introduction of a new product corresponding to a registered product may be sent from the server 18 to the camera body 10. Information created by the user may be sent from the camera body 10 to the server 18 using the reference mode. For example, the user sends a question regarding a registered product created using a soft keyboard displayed on the monitor 50 of the camera body 10 to the server 18 via the camera body 10. The answer from the manufacturer that received the question is sent to the camera body 10 when the server 18 is accessed next time. Also in this case, the same effect as the above-described embodiment can be obtained. Furthermore, since the user transmits / receives information to / from the server 18 using the cap information CAINF, information specific to the registered product can be obtained.

  In the above-described embodiment, as illustrated in FIG. 8, the example in which the product registered in the server 18 is deleted using the deletion mode has been described. The present invention is not limited to such an embodiment. For example, the camera body 10 may receive a registered product list associated with the cap identification information CBID from the server 18 using the reference mode, and select a product to be deleted from the received product list. Also in this case, the same effect as the above-described embodiment can be obtained. Furthermore, in this case, when the user remembers the identification information of the product to be deleted, for example, the lens model number, it is not necessary to connect the lens unit 12 to the camera body 10.

  In the above-described embodiment, as shown in FIG. 6, the example in which the camera information CBINF and the like are sent to the server 18 has been described. The present invention is not limited to such an embodiment. For example, when camera information CBINF or the like is sent to the server 18, information such as a mail address may be sent to the server 18. For example, an e-mail address is input using a soft keyboard displayed on the monitor 50 of the camera body 10. Also in this case, the same effect as the above-described embodiment can be obtained. The server 18 sends to the received e-mail address a registration e-mail in which the connection destination address URL of the product registration home page is described. The user can access the product registration home page from a personal computer or the like using the connection destination address URL described in the registration mail. Further, in order to strengthen the security of the product registration homepage, an authentication password may be included in the registration mail. In this case, the user can access the homepage for product registration from a personal computer or the like using the connection destination address URL and the authentication password.

  In the above-described embodiment, as shown in FIG. 6, the example in which the camera information CBINF and the like are sent to the server 18 has been described. The present invention is not limited to such an embodiment. For example, when the camera information CBINF or the like is sent to the server 18, the image data, for example, image data in which a mail address or the like is captured may be sent to the server 18. The server 18 decodes the received image data using, for example, a character recognition system and registers it in the database DB. Also in this case, the same effect as the above-described embodiment can be obtained. Furthermore, the server 18 can acquire character information from image data obtained by photographing character information by a character recognition system or the like. For this reason, the user does not need to input characters on the camera body 10. Thereby, for example, the user can save the trouble of key input for transmitting an e-mail address.

  In the first embodiment described above, the example in which the cap information CAINF or the like is received by the image sensor 32 of the camera body 10 has been described. The present invention is not limited to such an embodiment. For example, as shown in FIG. 15, the photometric sensor 40 of the camera body 10 may receive cap information CAINF and the like. In this case, the CPU demodulates the electric signal received from the photometric sensor 40 into cap information CAINF or the like. Similarly, in the second and fourth embodiments, the cap information CAINF may be received by the photometric sensor 40 of the camera body 10. Also in this case, the same effects as those of the first, second, and fourth embodiments described above can be obtained. Furthermore, since the photometric sensor 40 receives the cap information CAINF, it is not necessary to flip up the mirror MIRR for product registration. Since it is not necessary to drive the mirror MIRR every time a product is registered, wear of the drive part of the mirror MIRR can be suppressed.

  In the above-described fourth embodiment, the example in which the digital camera is configured by the camera cap 14, the lens unit 12, and the camera body 10B has been described. The present invention is not limited to such an embodiment. For example, at the time of product registration, the camera cap 14A shown in FIG. 9 and the camera body 10B shown in FIG. 11 may be connected. Alternatively, the accessory interface unit 60 may be formed on the camera body 10A shown in FIG. Also in this case, the same effects as those of the second, third, and fourth embodiments described above can be obtained.

  As mentioned above, although this invention was demonstrated in detail, said embodiment and its modification are only examples of this invention, and this invention is not limited to this. Obviously, modifications can be made without departing from the scope of the present invention.

It is a block diagram which shows the 1st Embodiment of this invention. It is an external view of the camera cap of 1st Embodiment. It is explanatory drawing of the structural example of the cap information of 1st Embodiment, camera information, and lens information. It is explanatory drawing of the database of the product registration of 1st Embodiment. It is explanatory drawing of the product registration menu in 1st Embodiment. It is a flowchart of the registration mode of 1st Embodiment. It is a flowchart of the reference mode of 1st Embodiment. It is a flowchart of the deletion mode of 1st Embodiment. It is a block diagram which shows the 2nd Embodiment of this invention. It is a block diagram which shows the 3rd Embodiment of this invention. It is a block diagram which shows the 4th Embodiment of this invention. It is explanatory drawing of the structural example of the cap information of 4th Embodiment, camera information, lens information, and accessory information. It is explanatory drawing of the structural example of the database of the product registration of 4th Embodiment. It is explanatory drawing of the structural example of the cap information containing a key code. It is a block diagram which shows the modification of 1st Embodiment.

Explanation of symbols

10, 10A, 10B ··· Camera body; 12 · · Lens part; 14, 14A, 14B · · Camera cap; 16 · · Network; 18 · · Server; 20, 34, 42, 62 · · Memory; Light emitting part; 24, 54 ... Operation part; 26 Battery: 28, 28A, 30, 30A, 36, 36A, 38 ... Connection part mount; 32 ... Image sensor; 40 ... Photometric sensor; Communication interface unit; 46.Shutter switch; 48.Recording medium; 50.Monitor; 52.Finder; 56..Pick; 58.Accessory; 60.Accessory interface unit

Claims (8)

A memory storing cap identification information for identifying an individual, an operation unit operable by a user, and outputting the cap identification information stored in the memory as an optical signal in response to an operation of the operation unit A camera cap having a light emitting unit to
A light receiving unit that receives the cap identification information as the optical signal, a memory that stores camera identification information for individually identifying products, and a computer connected to the network that stores the cap identification information and the camera identification information. A digital camera comprising a camera body having a communication interface unit for transmitting. The digital camera according to claim 1, wherein
The digital camera characterized in that the cap identification information is encrypted with either a public key or a private key managed by the camera manufacturer. The digital camera according to claim 1, wherein
The digital camera, wherein the light receiving unit is an image sensor for converting an image of a subject into an electrical signal. The digital camera according to claim 1, wherein
The digital camera, wherein the light receiving unit is a photometric sensor for measuring the intensity of light. The digital camera according to claim 1, wherein
The taking lens provided in the camera body includes a cap mount provided in front of the taking lens to connect the camera cap,
The digital camera according to claim 1, wherein the camera cap includes a lens connecting portion connected to the cap mount. The digital camera according to claim 1, wherein
The camera body includes a lens mount provided on the camera body for connecting a photographing lens;
The digital camera is characterized in that the camera cap includes a body connecting portion connected to the lens mount. A memory storing cap identification information for identifying an individual, an operation unit operable by a user, and a camera using the cap identification information stored in the memory as an optical signal in response to an operation of the operation unit A camera cap having a light emitting unit that outputs to the light receiving unit;
At least one accessory having a memory storing accessory identification information for individually identifying the product;
A light receiving unit that receives the cap identification information as the optical signal, a memory that stores camera identification information for individually identifying products, the cap identification information, the camera identification information, and the accessory identification information on a network A digital camera system comprising: a camera body having a communication interface unit for transmitting to a connected computer and an accessory interface unit for connecting the accessory. The digital camera system according to claim 7, wherein
The digital camera system, wherein the communication interface unit transmits and receives data to and from a computer connected to a network.

Images