Patent Grant
11375091
This disclosure relates generally to architecture for a camera with folded optics and a bearing suspension arrangement.
The advent of small, mobile multipurpose devices such as smartphones and tablet or pad devices has resulted in a need for high-resolution, small form factor cameras for integration in the devices. Some small form factor cameras may incorporate optical image stabilization (OIS) mechanisms that may sense and react to external excitation/disturbance by adjusting location of the optical lens on the X and/or Y axis in an attempt to compensate for unwanted motion of the lens. Some small form factor cameras may incorporate an autofocus (AF) mechanism whereby the object focal distance can be adjusted to focus an object plane in front of the camera at an image plane to be captured by the image sensor. In some such autofocus mechanisms, the optical lens is moved as a single rigid body along the optical axis of the camera to refocus the camera.
This specification includes references to “one embodiment” or “an embodiment.” The appearances of the phrases “in one embodiment” or “in an embodiment” do not necessarily refer to the same embodiment. Particular features, structures, or characteristics may be combined in any suitable manner consistent with this disclosure.
“Comprising.” This term is open-ended. As used in the appended claims, this term does not foreclose additional structure or steps. Consider a claim that recites: “An apparatus comprising one or more processor units . . . .” Such a claim does not foreclose the apparatus from including additional components (e.g., a network interface unit, graphics circuitry, etc.).
“Configured To.” Various units, circuits, or other components may be described or claimed as “configured to” perform a task or tasks. In such contexts, “configured to” is used to connote structure by indicating that the units/circuits/components include structure (e.g., circuitry) that performs those task or tasks during operation. As such, the unit/circuit/component can be said to be configured to perform the task even when the specified unit/circuit/component is not currently operational (e.g., is not on). The units/circuits/components used with the “configured to” language include hardware—for example, circuits, memory storing program instructions executable to implement the operation, etc. Reciting that a unit/circuit/component is “configured to” perform one or more tasks is expressly intended not to invoke 35 U.S.C. § 112, sixth paragraph, for that unit/circuit/component. Additionally, “configured to” can include generic structure (e.g., generic circuitry) that is manipulated by software and/or firmware (e.g., an FPGA or a general-purpose processor executing software) to operate in manner that is capable of performing the task(s) at issue. “Configure to” may also include adapting a manufacturing process (e.g., a semiconductor fabrication facility) to fabricate devices (e.g., integrated circuits) that are adapted to implement or perform one or more tasks.
“First,” “Second,” etc. As used herein, these terms are used as labels for nouns that they precede, and do not imply any type of ordering (e.g., spatial, temporal, logical, etc.). For example, a buffer circuit may be described herein as performing write operations for “first” and “second” values. The terms “first” and “second” do not necessarily imply that the first value must be written before the second value.
“Based On.” As used herein, this term is used to describe one or more factors that affect a determination. This term does not foreclose additional factors that may affect a determination. That is, a determination may be solely based on those factors or based, at least in part, on those factors. Consider the phrase “determine A based on B.” While in this case, B is a factor that affects the determination of A, such a phrase does not foreclose the determination of A from also being based on C. In other instances, A may be determined based solely on B.
It will also be understood that, although the terms first, second, etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first contact could be termed a second contact, and, similarly, a second contact could be termed a first contact, without departing from the intended scope. The first contact and the second contact are both contacts, but they are not the same contact.
The terminology used in the description herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used in the description and the appended claims, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term “and/or” as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms “includes,” “including,” “comprises,” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
As used herein, the term “if” may be construed to mean “when” or “upon” or “in response to determining” or “in response to detecting,” depending on the context. Similarly, the phrase “if it is determined” or “if [a stated condition or event] is detected” may be construed to mean “upon determining” or “in response to determining” or “upon detecting [the stated condition or event]” or “in response to detecting [the stated condition or event],” depending on the context.
Some embodiments include camera equipment outfitted with controls, magnets, and voice coil motors to improve the effectiveness of a miniature actuation mechanism for a compact camera module. More specifically, in some embodiments, compact camera modules include actuators to deliver functions such as autofocus (AF) and/or optical image stabilization (OIS). One approach to delivering a very compact actuator for AF and/or OIS is to use a voice coil motor (VCM) actuator.
Reference will now be made in detail to embodiments, examples of which are illustrated in the accompanying drawings. In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the present disclosure. However, it will be apparent to one of ordinary skill in the art that some embodiments may be practiced without these specific details. In other instances, well-known methods, procedures, components, circuits, and networks have not been described in detail so as not to unnecessarily obscure aspects of the embodiments.
Described here are folded optics arrangements for providing a reduced-height imaging system. The arrangements discussed throughout generally comprise one or more lenses positioned between two light path folding elements, which collectively provides a dual-folded light path. The one or more lenses (and/or one or more light path folding elements) may be moveable to provide autofocus and/or image stabilization during imaging.
In various embodiments, the camera 100 may include a lens group 102, a first prism 104, a second prism 106, and an image sensor package 108. The lens group 102 may include one or more lens elements. In some embodiments, the lens group 102 may be located between the first prism 104 and the second prism 106, forming the folded optics arrangement. Light may follow an optical path 110 that is folded by the first prism 104 such that the light is directed towards the lens group 102, passes through the lens group 102, and is folded by the second prism 106 such that the light is directed towards the image sensor package 108. In some examples, light may enter an object side of the first prism 104 along the Z-axis. The first prism 104 may redirect the light to propagate along the X-axis (which may be parallel to an optical axis defined by the lens group 102) towards the lens group 102. The second prism 106 may redirect the light to propagate along the Z-axis (which may be orthogonal to a plane defined by the image sensor package 108), e.g., such that the light exits an image side of the second prism 106 towards the image sensor package 108. The first prism 104, the lens group 102, and/or the second prism 106 may be positioned along a common axis (e.g., the X-axis, the optical axis defined by the lens group 102, etc.). According to some examples, the optical path 110 may be contained within a plane (e.g., the X-Z plane), and the image sensor package 108 may extend along a different plane (e.g., the X-Y plane).
In some embodiments, the object side of the first prism 104 may extend along the X-Y plane. Furthermore, the first prism 104 may include a pair of opposing lateral sides that each extend along the X-Z plane, a lens group facing side that extends along the Y-Z plane, and a reflecting surface side that is angled relative to one or more of the other sides of the first prism 104. For example, the reflecting surface side of the first prism 104 may include a reflective surface that is angled so as to redirect light received from the object side of the first prism 104 towards the lens group 102 (via the lens group facing side of the first prism 104), as discussed above.
In some embodiments, the image side of the second prism 106 may extend along the X-Y plane, e.g., proximate the image sensor package 108. Furthermore, the second prism 106 may include a pair of opposing lateral sides that each extend along the X-Z plane, a lens group facing side that extends along the Y-Z plane, and a reflecting surface side that is angled relative to one or more of the other sides of the second prism 106. For example, the reflecting surface side of the second prism 106 may include a reflective surface that is angled so as to redirect light received from the lens group 102 (via the lens group facing side of the second prism 106) towards the image sensor package (via the image side of the second prism 106), as discussed above.
While the light path folding elements are shown in various figures as comprising prisms (e.g., the first prism 104 and the second prism 106), the camera systems and/or folded optics arrangements described herein may include any suitable light path folding element (e.g., a mirror or the like) or combination of elements. In some embodiments, one or more of the light path folding elements may also act as a lens element (or combination of lens elements). For example, one or more lens elements (e.g., other than those of the lens group 102) may be integrated with the first prism 104 (and/or the second prism 106) such that the prism acts as a lens element. Additionally, or alternatively, the first prism 104 (and/or the second prism 106) may be shaped such that the prism acts as a lens element.
As will be discussed in further detail below, the lens group 102 may be coupled with an actuator structure that is configured to move the lens group 102 along multiple axes, e.g., to provide autofocus (AF) and/or optical image stabilization (OIS) functionality.
In various embodiments, the camera 300 may include a bearing suspension arrangement and/or an actuator module that may be used for controlled movement of the lens group 302 and/or one or more light path folding elements (e.g., the first prism 304). In some embodiments, the bearing suspension arrangement may include a base structure 312, a Z stage 314, an X stage 316, and/or a Y stage 318. The base structure 312 may be in a fixed position relative to movement of the Z stage 314, the X stage 316, and the Y stage 318. The bearing suspension arrangement may be coupled with the lens group 302 and may allow the lens group 302 to move in multiple directions relative to the image sensor 308. For example, the bearing suspension arrangement may enable movement of the lens group 302 in three degrees of freedom (3 DOF).
In some embodiments, the Z stage 314 may rest on (or otherwise be disposed above) the base structure 312, and may be configured to move in the Z-axis direction, e.g., along Z-movement ball bearings 320 (e.g., made of steel, ceramic, etc.) disposed between the Z stage 314 and the base structure 312. In some embodiments, the X stage 316 may rest on (or otherwise be disposed above) the Z stage 314, and may be configured to move in the X-axis direction, e.g., along the X-movement ball bearings 322 (e.g., made of steel, ceramic, etc.) disposed between the X stage 316 and the Z stage 314. In some embodiments, the Y stage 318 may rest on (or otherwise be disposed above) the X stage 316, and may be configured to move in the Y-axis direction, e.g., along the Y-movement ball bearings 324 (e.g., made of steel, ceramic, etc.) disposed between the Y stage 318 and the X stage 316. Furthermore, in some embodiments, the X stage 316 and/or the Y stage 318 may move in the Z-axis direction together with the Z stage 314 (e.g., due to movement of the Z stage 314 in the Z-axis direction). According to various embodiments, the lens group 302 may be coupled to the Y stage 318, e.g., such that the lens group 302 moves together with the Y stage 318. For example, the lens barrel 310 may have one or more protrusions 326 (e.g., extending from opposing sides of the lens barrel 310) configured to be disposed at least partially within one or more corresponding recesses 328 defined by the Y stage 318. In some examples, an adhesive may be used to fixedly attach the protrusion(s) 326 to the corresponding recess(es) 328, and thus fixedly attach the lens group 302 to the Y stage 318. One or more other optical elements may also be attached to the Y stage 318. For example, the first prism 304 may be fixedly attached to the Y stage 318 in some embodiments.
As indicated above, the actuator module may provide for shifting the lens group 302 along multiple axes (e.g., via movement of the Z stage 314, the X stage 316, and/or the Y stage 318, as described herein) to provide AF and/or OIS movement. In some embodiments the actuator module may comprise a voice coil motor (VCM) actuator module that includes one or more VCM actuators. For instance, the actuator module may include one or more magnets and one or more coils. The magnets and coils may magnetically interact (e.g., when electrical current is provided to the coils) to produce Lorentz forces that move the lens group 302.
In some embodiments, the actuator module may include an AF VCM actuator (e.g., to provide AF movement), an OIS-Y VCM actuator (e.g., to provide OIS-Y movement), and an OIS-X VCM actuator (e.g., to provide OIS-X movement). For example, the AF VCM actuator may include an AF magnet 330 and an AF coil 332. The AF magnet 330 may be attached to the Y stage 318. Furthermore, the AF coil 332 may be attached to the base structure 312. In some embodiments, the OIS-Y VCM actuator may include an OIS-Y magnet 334 and an OIS-Y coil 336. The OIS-Y magnet 334 may be attached to the Y stage 318. Furthermore, the OIS-Y coil 336 may be attached to the base structure 312. In some embodiments, the OIS-X VCM actuator may include an OIS-X magnet 338 and an OIS-X coil 340. The OIS-X magnet 338 may be attached to the Z stage 318. Furthermore, the OIS-Y coil 340 may be attached to the base structure 312.
In some embodiments, the camera 300 may include a position sensor arrangement that includes one or more position sensors 342 for position sensing with respect to AF movement, OIS-Y movement, and/or OIS-X movement. The position sensor(s) 342 may be magnetic field sensors (e.g., Hall sensors, tunneling magnetoresistance (TMR) sensors, giant magnetoresistance (GMR) sensors, etc.) in various embodiments. In some embodiments, a respective position sensor may be located proximate each respective coil of the actuator module. For example, each position sensor may be encircled by a respective coil, as indicated in
In some embodiments, the base structure 312 and/or the stages of the bearing suspension arrangement may be configured to be packaged around an optical payload on multiple sides, e.g., three sides (or U-shaped) as indicated in
In some embodiments, the base structure 312 may form vertical corners that define grooves (e.g., extending in the Z-axis direction) within which Z-movement ball bearings 320 may be disposed. For example, each of two sets of four vertically stacked Z-movement ball bearings 320 may be disposed in a respective corner proximate the OIS-X coil 340, e.g., as indicated in
In some embodiments, the Z stage 314 may have corners at which recesses may be formed. One or more X-movement ball bearings 322 may be disposed within each of the recesses. For example, as indicated in
In some embodiments, the X stage 316 may have an upper portion with corners at which grooves may be formed. One or more Y-movement ball bearings 324 may be disposed within each of the grooves. For example, as indicated in
According to some embodiments, the Z stage 314, the X stage 316, and/or the Y stage 318 may be preloaded against ball bearings (e.g., the Z-movement ball bearings 320, the X-movement ball bearings 322, and/or the Y-movement ball bearings 324) of the bearing suspension arrangement. In some examples, a ferritic component 344 (e.g., iron, stainless steel, etc.) may be attached to the Z stage 314 below the AF magnet 330 to preload the X stage 316 and/or the Y stage 318 against one or more of the ball bearings of the bearing suspension system. In some embodiments, the ferritic component 344 may be insert-molded into the Z stage 314. Another ferritic component 346 may be attached to the Z stage 314 below the OIS-Y magnet 334 to preload the X stage 316 and/or the Y stage 318 against one or more of the ball bearings of the bearing suspension system. In some embodiments, the ferritic component 346 may be insert-molded into the Z stage 314. Another ferritic component 348 may be attached to the OIS-X coil 340 and/or to the base structure 312 (e.g., proximate the OIS-X coil 340 and/or the OIS-X magnet 338) to preload the Z stage 314 against one or more of the ball bearings of the bearing suspension system.
In some embodiments, the camera 300 may include a top plate 350 disposed above the Y stage 318. The top plate 650 may have tabs that each extend downwards at a respective corner of the top plate 650. The tabs may be configured to be disposed within corresponding recesses that are each formed at a respective corner of the Z stage 314. The tabs may be attached (e.g., using an adhesive) to the corresponding recesses such that the top plate 350 and the Z stage 314 sandwich the X stage 314 and the Y stage 318.
According to various embodiments, the bearing suspension arrangement may provide for scaling/increasing actuator strokes, which may enable, for example, higher OIS compensation angles. Furthermore, due to high in-plane stiffness, the bearing suspension arrangement may provide for scaling/increasing the moving mass of the optical payload, which may, for example, enable improved optical specifications). For example, in contrast to some other suspension architectures (e.g., some flexure suspension architectures), the bearing suspension arrangement may be used to move an optical payload comprising a lens group and a prism (e.g., an optically powered prism). Such an optical payload is described below with reference to
According to some embodiments, the first prism 404 and/or the second prism 406 may be considered an optically powered prism. For example, as indicated in
According to various embodiments, the camera 400 may include a bearing suspension arrangement. In some embodiments, the bearing suspension arrangement may include a base structure 416, a Z stage 418, an X stage 420, and a Y stage 422. The base structure 416, the Z stage 418, the X stage 420, and/or the Y stage 422 may be similar to, or the same as, the base structure 312, the Z stage 314, the X stage 316, and/or the Y stage 318, respectively, described above with reference to
In some embodiments, camera 400 may include a first prism holder 424 to hold the first prism 404, and a second prism holder 426 to hold the second prism 406. According to some examples, the first prism holder 424 and the lens barrel 412 may be attached to the Y stage 422. For example, each of the first prism holder 424 and the lens barrel 412 may be formed of one or more respective components. Additionally, or alternatively, each of the first prism holder 424 and the lens barrel 412 may be separately attached (e.g., via an adhesive) to the Y stage 422. In some embodiments, the first prism holder 424 and the lens barrel 412 may be formed of a single component that is attached to the Y stage 422.
In some embodiments, the camera 400 may include an actuator module (e.g., the actuator modules described herein with reference to
According to some embodiments, the Z stage 418, the X stage 420, and/or the Y stage 422 may be preloaded against ball bearings (e.g., the Z-movement ball bearings 320, the X-movement ball bearings 322, and/or the Y-movement ball bearings 324 described above with reference to
In some embodiments, the camera 400 may include a substrate 434 that may be coupled to the image sensor 408. In some examples, a filter 436 (e.g., an infrared filter) may also be coupled to the substrate 434. For instance, the filter 436 may be located above the image sensor 408 such that light passes through the filter 436 before reaching the image sensor 408.
According to various embodiments, the camera 500 may include a bearing suspension arrangement. In some embodiments, the bearing suspension arrangement may include a base structure 514, a Z stage 516, an X stage 518, and a Y stage 520. The base structure 514, the Z stage 516, the X stage 518, and/or the Y stage 520 may be similar to, or the same as, the base structure 312, the Z stage 314, the X stage 316, and/or the Y stage 318, respectively, described above with reference to
In some embodiments, camera 500 may include a first prism holder 522 to hold the first prism 504, and a second prism holder 524 to hold the second prism 506. In some examples, the first prism holder 522 and the second prism holder 524 may be attached to a fixed structure of the camera 500, such that the first prim 504 and the second prism 506 are maintained in a fixed position relative to movement of the lens group 502.
According to some examples, the lens barrel 512 may be attached to the Y stage 520, e.g., so that the lens group 502 moves, together with the Y stage 520, in multiple directions relative to the image sensor 508, the first prism 504, the second prism 506, and/or the base structure 514.
In various embodiments, the camera 500 may include an actuator module (e.g., the actuator modules described herein with reference to
According to some embodiments, the Z stage 516, the X stage 518, and/or the Y stage 520 may be preloaded against ball bearings (e.g., the Z-movement ball bearings 320, the X-movement ball bearings 322, and/or the Y-movement ball bearings 324 described above with reference to
In some embodiments, the camera 500 may include a substrate 532 that may be coupled to the image sensor 508. In some examples, a filter 534 (e.g., an infrared filter) may also be coupled to the substrate 532. For instance, the filter 534 may be located above the image sensor 508 such that light passes through the filter 534 before reaching the image sensor 508.
In some embodiments, the camera 600 may include a lens group 602, a first prism 604, a second prism 606, and an image sensor 608. The lens group 602 may include one or more lens elements 610 disposed within a lens barrel 612.
As indicated in
In some embodiments, camera 600 may include a first prism holder 622 to hold the first prism 604, and a second prism holder 624 to hold the second prism 606. In some examples, the first prism holder 622 and the second prism holder 624 may be attached to a fixed structure of the camera 600, such that the first prim 604 and the second prism 606 are maintained in a fixed position relative to movement of the lens group 602.
According to some examples, the lens barrel 612 may be attached to the Y stage 620, e.g., so that the lens group 602 moves, together with the Y stage 620, in multiple directions relative to the image sensor 608, the first prism 604, the second prism 606, and/or the base structure 614.
In various embodiments, the camera 600 may include an actuator module (e.g., the actuator module described herein with reference to
Referring to
Further referring to
According to some embodiments, the Z stage 616, the X stage 618, and/or the Y stage 620 may be preloaded against ball bearings (e.g., the Z-movement ball bearings 320, the X-movement ball bearings 322, and/or the Y-movement ball bearings 324 described above with reference to
In some embodiments, the camera 600 may include a substrate 644 that may be coupled to the image sensor 608. In some examples, a filter 646 (e.g., an infrared filter) may also be coupled to the substrate 644. For instance, the filter 646 may be located above the image sensor 644 such that light passes through the filter 646 before reaching the image sensor 646.
Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communications device, such as a mobile telephone, that also contains other functions, such as PDA and/or music player functions. Example embodiments of portable multifunction devices include, without limitation, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, Calif. Other portable electronic devices, such as laptops, cameras, cell phones, or tablet computers, may also be used. It should also be understood that, in some embodiments, the device is not a portable communications device, but is a desktop computer with a camera. In some embodiments, the device is a gaming computer with orientation sensors (e.g., orientation sensors in a gaming controller). In other embodiments, the device is not a portable communications device, but is a camera.
In the discussion that follows, an electronic device that includes a display and a touch-sensitive surface is described. It should be understood, however, that the electronic device may include one or more other physical user-interface devices, such as a physical keyboard, a mouse and/or a joystick.
The device typically supports a variety of applications, such as one or more of the following: a drawing application, a presentation application, a word processing application, a website creation application, a disk authoring application, a spreadsheet application, a gaming application, a telephone application, a video conferencing application, an e-mail application, an instant messaging application, a workout support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and/or a digital video player application.
The various applications that may be executed on the device may use at least one common physical user-interface device, such as the touch-sensitive surface. One or more functions of the touch-sensitive surface as well as corresponding information displayed on the device may be adjusted and/or varied from one application to the next and/or within a respective application. In this way, a common physical architecture (such as the touch-sensitive surface) of the device may support the variety of applications with user interfaces that are intuitive and transparent to the user.
Attention is now directed toward embodiments of portable devices with cameras.
It should be appreciated that device 700 is only one example of a portable multifunction device, and that device 700 may have more or fewer components than shown, may combine two or more components, or may have a different configuration or arrangement of the components. The various components shown in
Memory 702 may include high-speed random access memory and may also include non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Access to memory 702 by other components of device 700, such as CPU 720 and the peripherals interface 718, may be controlled by memory controller 722.
Peripherals interface 718 can be used to couple input and output peripherals of the device to CPU 720 and memory 702. The one or more processors 720 run or execute various software programs and/or sets of instructions stored in memory 702 to perform various functions for device 700 and to process data.
In some embodiments, peripherals interface 718, CPU 720, and memory controller 722 may be implemented on a single chip, such as chip 704. In some other embodiments, they may be implemented on separate chips.
RF (radio frequency) circuitry 708 receives and sends RF signals, also called electromagnetic signals. RF circuitry 708 converts electrical signals to/from electromagnetic signals and communicates with communications networks and other communications devices via the electromagnetic signals. RF circuitry 708 may include well-known circuitry for performing these functions, including but not limited to an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, and so forth. RF circuitry 708 may communicate with networks, such as the Internet, also referred to as the World Wide Web (WWW), an intranet and/or a wireless network, such as a cellular telephone network, a wireless local area network (LAN) and/or a metropolitan area network (MAN), and other devices by wireless communication. The wireless communication may use any of a variety of communications standards, protocols and technologies, including but not limited to Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSDPA), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g and/or IEEE 802.11n), voice over Internet Protocol (VoIP), Wi-MAX, a protocol for e-mail (e.g., Internet message access protocol (IMAP) and/or post office protocol (POP)), instant messaging (e.g., extensible messaging and presence protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and/or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document.
Audio circuitry 710, speaker 711, and microphone 713 provide an audio interface between a user and device 700. Audio circuitry 710 receives audio data from peripherals interface 718, converts the audio data to an electrical signal, and transmits the electrical signal to speaker 711. Speaker 711 converts the electrical signal to human-audible sound waves. Audio circuitry 710 also receives electrical signals converted by microphone 713 from sound waves. Audio circuitry 710 converts the electrical signal to audio data and transmits the audio data to peripherals interface 718 for processing. Audio data may be retrieved from and/or transmitted to memory 702 and/or RF circuitry 708 by peripherals interface 718. In some embodiments, audio circuitry 710 also includes a headset jack (e.g., 812,
I/O subsystem 706 couples input/output peripherals on device 700, such as touch screen 712 and other input control devices 716, to peripherals interface 718. I/O subsystem 706 may include display controller 756 and one or more input controllers 760 for other input or control devices. The one or more input controllers 760 receive/send electrical signals from/to other input or control devices 716. The other input control devices 716 may include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, and so forth. In some alternate embodiments, input controller(s) 760 may be coupled to any (or none) of the following: a keyboard, infrared port, USB port, and a pointer device such as a mouse. The one or more buttons (e.g., 808,
Touch-sensitive display 712 provides an input interface and an output interface between the device and a user. Display controller 756 receives and/or sends electrical signals from/to touch screen 712. Touch screen 712 displays visual output to the user. The visual output may include graphics, text, icons, video, and any combination thereof (collectively termed “graphics”). In some embodiments, some or all of the visual output may correspond to user-interface objects.
Touch screen 712 has a touch-sensitive surface, sensor or set of sensors that accepts input from the user based on haptic and/or tactile contact. Touch screen 712 and display controller 756 (along with any associated modules and/or sets of instructions in memory 702) detect contact (and any movement or breaking of the contact) on touch screen 712 and converts the detected contact into interaction with user-interface objects (e.g., one or more soft keys, icons, web pages or images) that are displayed on touch screen 712. In an example embodiment, a point of contact between touch screen 712 and the user corresponds to a finger of the user.
Touch screen 712 may use LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies may be used in other embodiments. Touch screen 712 and display controller 756 may detect contact and any movement or breaking thereof using any of a variety of touch sensing technologies now known or later developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with touch screen 712. In an example embodiment, projected mutual capacitance sensing technology is used, such as that found in the iPhone®, iPod Touch®, and iPad® from Apple Inc. of Cupertino, Calif.
Touch screen 712 may have a video resolution in excess of 800 dpi. In some embodiments, the touch screen has a video resolution of approximately 860 dpi. The user may make contact with touch screen 712 using any suitable object or appendage, such as a stylus, a finger, and so forth. In some embodiments, the user interface is designed to work primarily with finger-based contacts and gestures, which can be less precise than stylus-based input due to the larger area of contact of a finger on the touch screen. In some embodiments, the device translates the rough finger-based input into a precise pointer/cursor position or command for performing the actions desired by the user.
In some embodiments, in addition to the touch screen, device 700 may include a touchpad (not shown) for activating or deactivating particular functions. In some embodiments, the touchpad is a touch-sensitive area of the device that, unlike the touch screen, does not display visual output. The touchpad may be a touch-sensitive surface that is separate from touch screen 712 or an extension of the touch-sensitive surface formed by the touch screen.
Device 700 also includes power system 762 for powering the various components. Power system 762 may include a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., a light-emitting diode (LED)) and any other components associated with the generation, management and distribution of power in portable devices.
Device 700 may also include one or more optical sensors or cameras 764.
Device 700 may also include one or more proximity sensors 766.
Device 700 includes one or more orientation sensors 768. In some embodiments, the one or more orientation sensors 768 include one or more accelerometers (e.g., one or more linear accelerometers and/or one or more rotational accelerometers). In some embodiments, the one or more orientation sensors 768 include one or more gyroscopes. In some embodiments, the one or more orientation sensors 768 include one or more magnetometers. In some embodiments, the one or more orientation sensors 768 include one or more of global positioning system (GPS), Global Navigation Satellite System (GLONASS), and/or other global navigation system receivers. The GPS, GLONASS, and/or other global navigation system receivers may be used for obtaining information concerning the location and orientation (e.g., portrait or landscape) of device 700. In some embodiments, the one or more orientation sensors 768 include any combination of orientation/rotation sensors.
In some embodiments, the software components stored in memory 702 include operating system 726, communication module (or set of instructions) 728, contact/motion module (or set of instructions) 730, graphics module (or set of instructions) 732, text input module (or set of instructions) 734, Global Positioning System (GPS) module (or set of instructions) 735, arbiter module 758 and applications (or sets of instructions) 736. Furthermore, in some embodiments memory 702 stores device/global internal state 757. Device/global internal state 757 includes one or more of: active application state, indicating which applications, if any, are currently active; display state, indicating what applications, views or other information occupy various regions of touch screen display 712; sensor state, including information obtained from the device's various sensors and input control devices 716; and location information concerning the device's location and/or attitude.
Operating system 726 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, WINDOWS, or an embedded operating system such as VxWorks) includes various software components and/or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.) and facilitates communication between various hardware and software components.
Communication module 728 facilitates communication with other devices over one or more external ports 724 and also includes various software components for handling data received by RF circuitry 708 and/or external port 724. External port 724 (e.g., Universal Serial Bus (USB), FIREWIRE, etc.) is adapted for coupling directly to other devices or indirectly over a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is a multi-pin (e.g., 30-pin) connector.
Contact/motion module 730 may detect contact with touch screen 712 (in conjunction with display controller 756) and other touch sensitive devices (e.g., a touchpad or physical click wheel). Contact/motion module 730 includes various software components for performing various operations related to detection of contact, such as determining if contact has occurred (e.g., detecting a finger-down event), determining if there is movement of the contact and tracking the movement across the touch-sensitive surface (e.g., detecting one or more finger-dragging events), and determining if the contact has ceased (e.g., detecting a finger-up event or a break in contact). Contact/motion module 730 receives contact data from the touch-sensitive surface. Determining movement of the point of contact, which is represented by a series of contact data, may include determining speed (magnitude), velocity (magnitude and direction), and/or an acceleration (a change in magnitude and/or direction) of the point of contact. These operations may be applied to single contacts (e.g., one finger contacts) or to multiple simultaneous contacts (e.g., “multitouch”/multiple finger contacts). In some embodiments, contact/motion module 730 and display controller 756 detect contact on a touchpad.
Contact/motion module 730 may detect a gesture input by a user. Different gestures on the touch-sensitive surface have different contact patterns. Thus, a gesture may be detected by detecting a particular contact pattern. For example, detecting a finger tap gesture includes detecting a finger-down event followed by detecting a finger-up (lift off) event at the same position (or substantially the same position) as the finger-down event (e.g., at the position of an icon). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger-down event followed by detecting one or more finger-dragging events, and subsequently followed by detecting a finger-up (lift off) event.
Graphics module 732 includes various known software components for rendering and displaying graphics on touch screen 712 or other display, including components for changing the intensity of graphics that are displayed. As used herein, the term “graphics” includes any object that can be displayed to a user, including without limitation text, web pages, icons (such as user-interface objects including soft keys), digital images, videos, animations and the like.
In some embodiments, graphics module 732 stores data representing graphics to be used. Each graphic may be assigned a corresponding code. Graphics module 732 receives, from applications etc., one or more codes specifying graphics to be displayed along with, if necessary, coordinate data and other graphic property data, and then generates screen image data to output to display controller 756.
Text input module 734, which may be a component of graphics module 732, provides soft keyboards for entering text in various applications (e.g., contacts 737, e-mail 740, IM 741, browser 747, and any other application that needs text input).
GPS module 735 determines the location of the device and provides this information for use in various applications (e.g., to telephone 738 for use in location-based dialing, to camera 743 as picture/video metadata, and to applications that provide location-based services such as weather widgets, local yellow page widgets, and map/navigation widgets).
Applications 736 may include the following modules (or sets of instructions), or a subset or superset thereof:
Examples of other applications 736 that may be stored in memory 702 include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice replication.
In conjunction with touch screen 712, display controller 756, contact module 730, graphics module 732, and text input module 734, contacts module 737 may be used to manage an address book or contact list (e.g., stored in application internal state 757), including: adding name(s) to the address book; deleting name(s) from the address book; associating telephone number(s), e-mail address(es), physical address(es) or other information with a name; associating an image with a name; categorizing and sorting names; providing telephone numbers or e-mail addresses to initiate and/or facilitate communications by telephone 738, video conference 739, e-mail 740, or IM 741; and so forth.
In conjunction with RF circuitry 708, audio circuitry 710, speaker 711, microphone 713, touch screen 712, display controller 756, contact module 730, graphics module 732, and text input module 734, telephone module 738 may be used to enter a sequence of characters corresponding to a telephone number, access one or more telephone numbers in address book 737, modify a telephone number that has been entered, dial a respective telephone number, conduct a conversation and disconnect or hang up when the conversation is completed. As noted above, the wireless communication may use any of a variety of communications standards, protocols and technologies.
In conjunction with RF circuitry 708, audio circuitry 710, speaker 711, microphone 713, touch screen 712, display controller 756, optical sensor 764, optical sensor controller 758, contact module 730, graphics module 732, text input module 734, contact list 737, and telephone module 738, videoconferencing module 739 includes executable instructions to initiate, conduct, and terminate a video conference between a user and one or more other participants in accordance with user instructions.
In conjunction with RF circuitry 708, touch screen 712, display controller 756, contact module 730, graphics module 732, and text input module 734, e-mail client module 740 includes executable instructions to create, send, receive, and manage e-mail in response to user instructions. In conjunction with image management module 744, e-mail client module 740 makes it very easy to create and send e-mails with still or video images taken with camera module 743.
In conjunction with RF circuitry 708, touch screen 712, display controller 756, contact module 730, graphics module 732, and text input module 734, the instant messaging module 741 includes executable instructions to enter a sequence of characters corresponding to an instant message, to modify previously entered characters, to transmit a respective instant message (for example, using a Short Message Service (SMS) or Multimedia Message Service (MMS) protocol for telephony-based instant messages or using XMPP, SIMPLE, or IMPS for Internet-based instant messages), to receive instant messages and to view received instant messages. In some embodiments, transmitted and/or received instant messages may include graphics, photos, audio files, video files and/or other attachments as are supported in a MMS and/or an Enhanced Messaging Service (EMS). As used herein, “instant messaging” refers to both telephony-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).
In conjunction with RF circuitry 708, touch screen 712, display controller 756, contact module 730, graphics module 732, text input module 734, GPS module 735, map module 754, and music player module 746, workout support module 742 includes executable instructions to create workouts (e.g., with time, distance, and/or calorie burning goals); communicate with workout sensors (sports devices); receive workout sensor data; calibrate sensors used to monitor a workout; select and play music for a workout; and display, store and transmit workout data.
In conjunction with touch screen 712, display controller 756, optical sensor(s) 764, optical sensor controller 758, contact module 730, graphics module 732, and image management module 744, camera module 743 includes executable instructions to capture still images or video (including a video stream) and store them into memory 702, modify characteristics of a still image or video, or delete a still image or video from memory 702.
In conjunction with touch screen 712, display controller 756, contact module 730, graphics module 732, text input module 734, and camera module 743, image management module 744 includes executable instructions to arrange, modify (e.g., edit), or otherwise manipulate, label, delete, present (e.g., in a digital slide show or album), and store still and/or video images.
In conjunction with RF circuitry 708, touch screen 712, display system controller 756, contact module 730, graphics module 732, and text input module 734, browser module 747 includes executable instructions to browse the Internet in accordance with user instructions, including searching, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.
In conjunction with RF circuitry 708, touch screen 712, display system controller 756, contact module 730, graphics module 732, text input module 734, e-mail client module 740, and browser module 747, calendar module 748 includes executable instructions to create, display, modify, and store calendars and data associated with calendars (e.g., calendar entries, to do lists, etc.) in accordance with user instructions.
In conjunction with RF circuitry 708, touch screen 712, display system controller 756, contact module 730, graphics module 732, text input module 734, and browser module 747, widget modules 749 are mini-applications that may be downloaded and used by a user (e.g., weather widget 549-1, stocks widget 549-2, calculator widget 749-3, alarm clock widget 749-4, and dictionary widget 749-5) or created by the user (e.g., user-created widget 749-6). In some embodiments, a widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some embodiments, a widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g., Yahoo! Widgets).
In conjunction with RF circuitry 708, touch screen 712, display system controller 756, contact module 730, graphics module 732, text input module 734, and browser module 747, the widget creator module 750 may be used by a user to create widgets (e.g., turning a user-specified portion of a web page into a widget).
In conjunction with touch screen 712, display system controller 756, contact module 730, graphics module 732, and text input module 734, search module 751 includes executable instructions to search for text, music, sound, image, video, and/or other files in memory 702 that match one or more search criteria (e.g., one or more user-specified search terms) in accordance with user instructions.
In conjunction with touch screen 712, display system controller 756, contact module 730, graphics module 732, audio circuitry 710, speaker 711, RF circuitry 708, and browser module 747, video and music player module 752 includes executable instructions that allow the user to download and play back recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files, and executable instructions to display, present or otherwise play back videos (e.g., on touch screen 712 or on an external, connected display via external port 724). In some embodiments, device 700 may include the functionality of an MP3 player.
In conjunction with touch screen 712, display controller 756, contact module 730, graphics module 732, and text input module 734, notes module 753 includes executable instructions to create and manage notes, to do lists, and the like in accordance with user instructions.
In conjunction with RF circuitry 708, touch screen 712, display system controller 756, contact module 730, graphics module 732, text input module 734, GPS module 735, and browser module 747, map module 754 may be used to receive, display, modify, and store maps and data associated with maps (e.g., driving directions; data on stores and other points of interest at or near a particular location; and other location-based data) in accordance with user instructions.
In conjunction with touch screen 712, display system controller 756, contact module 730, graphics module 732, audio circuitry 710, speaker 711, RF circuitry 708, text input module 734, e-mail client module 740, and browser module 747, online video module 755 includes instructions that allow the user to access, browse, receive (e.g., by streaming and/or download), play back (e.g., on the touch screen or on an external, connected display via external port 724), send an e-mail with a link to a particular online video, and otherwise manage online videos in one or more file formats, such as H.264. In some embodiments, instant messaging module 741, rather than e-mail client module 740, is used to send a link to a particular online video.
Each of the above identified modules and applications correspond to a set of executable instructions for performing one or more functions described above and the methods described in this application (e.g., the computer-implemented methods and other information processing methods described herein). These modules (i.e., sets of instructions) need not be implemented as separate software programs, procedures or modules, and thus various subsets of these modules may be combined or otherwise re-arranged in various embodiments. In some embodiments, memory 702 may store a subset of the modules and data structures identified above. Furthermore, memory 702 may store additional modules and data structures not described above.
In some embodiments, device 700 is a device where operation of a predefined set of functions on the device is performed exclusively through a touch screen and/or a touchpad. By using a touch screen and/or a touchpad as the primary input control device for operation of device 700, the number of physical input control devices (such as push buttons, dials, and the like) on device 700 may be reduced.
The predefined set of functions that may be performed exclusively through a touch screen and/or a touchpad include navigation between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates device 700 to a main, home, or root menu from any user interface that may be displayed on device 700. In such embodiments, the touchpad may be referred to as a “menu button.” In some other embodiments, the menu button may be a physical push button or other physical input control device instead of a touchpad.
Device 700 may also include one or more physical buttons, such as “home” or menu button 804. As described previously, menu button 804 may be used to navigate to any application 736 in a set of applications that may be executed on device 700. Alternatively, in some embodiments, the menu button 804 is implemented as a soft key in a GUI displayed on touch screen 712.
In one embodiment, device 700 includes touch screen 712, menu button 804, push button 806 for powering the device on/off and locking the device, volume adjustment button(s) 808, Subscriber Identity Module (SIM) card slot 810, head set jack 812, and docking/charging external port 824. Push button 806 may be used to turn the power on/off on the device by depressing the button and holding the button in the depressed state for a predefined time interval; to lock the device by depressing the button and releasing the button before the predefined time interval has elapsed; and/or to unlock the device or initiate an unlock process. In an alternative embodiment, device 700 also may accept verbal input for activation or deactivation of some functions through microphone 713.
It should be noted that, although many of the examples herein are given with reference to optical sensor(s)/camera(s) 764 (on the front of a device), one or more rear-facing cameras or optical sensors that are pointed opposite from the display may be used instead of, or in addition to, an optical sensor(s)/camera(s) 764 on the front of a device.
Various embodiments of a camera motion control system as described herein, including embodiments of magnetic position sensing, as described herein may be executed in one or more computer systems 900, which may interact with various other devices. Note that any component, action, or functionality described above with respect to
In various embodiments, computer system 900 may be a uniprocessor system including one processor 910, or a multiprocessor system including several processors 910 (e.g., two, four, eight, or another suitable number). Processors 910 may be any suitable processor capable of executing instructions. For example, in various embodiments processors 910 may be general-purpose or embedded processors implementing any of a variety of instruction set architectures (ISAs), such as the x86, PowerPC, SPARC, or MIPS ISAs, or any other suitable ISA. In multiprocessor systems, each of processors 910 may commonly, but not necessarily, implement the same ISA.
System memory 920 may be configured to store camera control program instructions 922 and/or camera control data accessible by processor 910. In various embodiments, system memory 920 may be implemented using any suitable memory technology, such as static random access memory (SRAM), synchronous dynamic RAM (SDRAM), nonvolatile/Flash-type memory, or any other type of memory. In the illustrated embodiment, program instructions 922 may be configured to implement a lens control application 924 incorporating any of the functionality described above. Additionally, existing camera control data 932 of memory 920 may include any of the information or data structures described above. In some embodiments, program instructions and/or data may be received, sent or stored upon different types of computer-accessible media or on similar media separate from system memory 920 or computer system 900. While computer system 900 is described as implementing the functionality of functional blocks of previous Figures, any of the functionality described herein may be implemented via such a computer system.
In one embodiment, I/O interface 930 may be configured to coordinate I/O traffic between processor 910, system memory 920, and any peripheral devices in the device, including network interface 940 or other peripheral interfaces, such as input/output devices 950. In some embodiments, I/O interface 930 may perform any necessary protocol, timing or other data transformations to convert data signals from one component (e.g., system memory 920) into a format suitable for use by another component (e.g., processor 910). In some embodiments, I/O interface 930 may include support for devices attached through various types of peripheral buses, such as a variant of the Peripheral Component Interconnect (PCI) bus standard or the Universal Serial Bus (USB) standard, for example. In some embodiments, the function of I/O interface 930 may be split into two or more separate components, such as a north bridge and a south bridge, for example. Also, in some embodiments some or all of the functionality of I/O interface 930, such as an interface to system memory 920, may be incorporated directly into processor 910.
Network interface 940 may be configured to allow data to be exchanged between computer system 900 and other devices attached to a network 985 (e.g., carrier or agent devices) or between nodes of computer system 900. Network 985 may in various embodiments include one or more networks including but not limited to Local Area Networks (LANs) (e.g., an Ethernet or corporate network), Wide Area Networks (WANs) (e.g., the Internet), wireless data networks, some other electronic data network, or some combination thereof. In various embodiments, network interface 940 may support communication via wired or wireless general data networks, such as any suitable type of Ethernet network, for example; via telecommunications/telephony networks such as analog voice networks or digital fiber communications networks; via storage area networks such as Fibre Channel SANs, or via any other suitable type of network and/or protocol.
Input/output devices 950 may, in some embodiments, include one or more display terminals, keyboards, keypads, touchpads, scanning devices, voice or optical recognition devices, or any other devices suitable for entering or accessing data by one or more computer systems 900. Multiple input/output devices 950 may be present in computer system 900 or may be distributed on various nodes of computer system 900. In some embodiments, similar input/output devices may be separate from computer system 900 and may interact with one or more nodes of computer system 900 through a wired or wireless connection, such as over network interface 940.
As shown in
Those skilled in the art will appreciate that computer system 900 is merely illustrative and is not intended to limit the scope of embodiments. In particular, the computer system and devices may include any combination of hardware or software that can perform the indicated functions, including computers, network devices, Internet appliances, PDAs, wireless phones, pagers, etc. Computer system 900 may also be connected to other devices that are not illustrated, or instead may operate as a stand-alone system. In addition, the functionality provided by the illustrated components may in some embodiments be combined in fewer components or distributed in additional components. Similarly, in some embodiments, the functionality of some of the illustrated components may not be provided and/or other additional functionality may be available.
Those skilled in the art will also appreciate that, while various items are illustrated as being stored in memory or on storage while being used, these items or portions of them may be transferred between memory and other storage devices for purposes of memory management and data integrity. Alternatively, in other embodiments some or all of the software components may execute in memory on another device and communicate with the illustrated computer system via inter-computer communication. Some or all of the system components or data structures may also be stored (e.g., as instructions or structured data) on a computer-accessible medium or a portable article to be read by an appropriate drive, various examples of which are described above. In some embodiments, instructions stored on a computer-accessible medium separate from computer system 900 may be transmitted to computer system 900 via transmission media or signals such as electrical, electromagnetic, or digital signals, conveyed via a communication medium such as a network and/or a wireless link. Various embodiments may further include receiving, sending or storing instructions and/or data implemented in accordance with the foregoing description upon a computer-accessible medium. Generally speaking, a computer-accessible medium may include a non-transitory, computer-readable storage medium or memory medium such as magnetic or optical media, e.g., disk or DVD/CD-ROM, volatile or non-volatile media such as RAM (e.g. SDRAM, DDR, RDRAM, SRAM, etc.), ROM, etc. In some embodiments, a computer-accessible medium may include transmission media or signals such as electrical, electromagnetic, or digital signals, conveyed via a communication medium such as network and/or a wireless link.
The methods described herein may be implemented in software, hardware, or a combination thereof, in different embodiments. In addition, the order of the blocks of the methods may be changed, and various elements may be added, reordered, combined, omitted, modified, etc. Various modifications and changes may be made as would be obvious to a person skilled in the art having the benefit of this disclosure. The various embodiments described herein are meant to be illustrative and not limiting. Many variations, modifications, additions, and improvements are possible. Accordingly, plural instances may be provided for components described herein as a single instance. Boundaries between various components, operations and data stores are somewhat arbitrary, and particular operations are illustrated in the context of specific illustrative configurations.
Other allocations of functionality are envisioned and may fall within the scope of claims that follow. Finally, structures and functionality presented as discrete components in the example configurations may be implemented as a combined structure or component. These and other variations, modifications, additions, and improvements may fall within the scope of embodiments as defined in the claims that follow.
This application claims benefit of priority to U.S. Provisional Application No. 62/840,309, filed Apr. 29, 2019, titled “CAMERA WITH FOLDED OPTICS AND BEARING SUSPENSION”, which is hereby incorporated by reference in its entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 20060017834 | Konno | Jan 2006 | A1 |
| 20140009631 | Topliss | Jan 2014 | A1 |
| 20150288865 | Osborne | Oct 2015 | A1 |
| 20170359568 | Georgiev | Dec 2017 | A1 |
| 20180067335 | Chen | Mar 2018 | A1 |
| 20180217475 | Goldenberg | Aug 2018 | A1 |
| 20190121103 | Bachar | Apr 2019 | A1 |
| 20190141248 | Hubert | May 2019 | A1 |
| 20190377155 | Bachar | Dec 2019 | A1 |
| Number | Date | Country |
|---|---|---|
| WO 2018007981 | Jan 2018 | WO |
| Number | Date | Country | |
|---|---|---|---|
| 62840309 | Apr 2019 | US |
