Patent Grant
12153278
This disclosure relates generally to a welded bracket structure for a multi-camera system.
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 devices may include a multi-camera system that includes cameras held in place by a bracket formed of a single piece of material.
Some 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. Furthermore, some 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 AF 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.
Various embodiments described herein relate to a welded bracket structure for use in conjunction with multiple camera modules. In some examples, the welded bracket structure may provide a unitary body structure to which camera modules may be attached or otherwise coupled, e.g., to form a multi-camera system module that may be incorporated into a device, such as a phone or other computing device. The welded bracket structure may comprise at least two brackets that are welded together via one or more weld joints. Each of the brackets may be configured to couple with one or more camera modules. As a non-limiting example, a first bracket may be configured to couple with two camera modules, and a second bracket (that is welded to the first bracket) may be configured to couple with one camera module. The welded bracket structure may be T-shaped in various embodiments, which may enable a reduction in space consumption as compared to, e.g., a rectangular welded bracket structure. According to various embodiments, each of the first bracket and the second bracket may be formed by deep drawing a respective sheet of metal. In some embodiments, the welded bracket structure (and the techniques for forming the same) may not suffer from some manufacturing problems that may arise in other camera bracket structures, e.g., a T-shaped bracket structure formed via stamping a single sheet of metal (which may result in the metal being torn). Furthermore, the techniques described herein may reduce manufacturing costs, e.g., as compared to processes (e.g., CNC machining) used to form some other camera bracket structures.
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.
As mentioned above, various embodiments include a welded bracket structure comprising at least two brackets that are welded together.
According to various embodiments, the first bracket 104 may be configured to couple with one or more camera modules (e.g., camera modules 110 and 112). Similarly, the second bracket 106 may be configured to couple with one or more other camera modules (e.g., camera module 114).
In some embodiments, the first bracket 104 may include a top wall 116 (also referred to herein as the “first top wall 116”) and one or more side walls 118 (e.g., side walls 118a-118d). The side wall(s) 118 may be oriented at a non-zero angle relative to the first top wall 116. As a non-limiting example, one or more of the side walls 118 may be orthogonal to the first top wall 116. In some examples, one or more of the side walls 118 may be oriented at a first angle relative to the first top wall 116, and another one or more of the side walls 118 may be oriented at a different, second angle relative to the first top wall 116.
The first top wall 116 may define one or more apertures, e.g., to receive at least a portion of a first set of one or more camera modules. As indicated in
In some embodiments, the second bracket 106 may include a top wall 128 (also referred to herein as the “second top wall 128”) and one or more side walls 130 (e.g., side walls 130a-130d). The side wall(s) 130 may be oriented at a non-zero angle relative to the second top wall 128. As a non-limiting example, one or more of the side walls 130 may be orthogonal to the second top wall 128. In some examples, one or more of the side walls 130 may be oriented at a first angle relative to the second top wall 128, and another one or more of the side walls 130 may be oriented at a different, second angle relative to the second top wall 128.
The second top wall 128 may define one or more apertures, e.g., to receive at least a portion of a second set of one or more camera modules. As indicated in
According to some embodiments, the first bracket 104 may be formed by deep drawing a first sheet of metal. Additionally, or alternatively, the second bracket 106 may be formed by deep drawing a second sheet of metal. However, the first bracket 104 and/or the second bracket 106 may be formed using any other suitable material and/or process. Example methods/processes for manufacturing a welded bracket structure for camera modules are described in further detail below with reference to
As mentioned above, the welded bracket structure 102 may include a weld joint arrangement 108 that couples the second bracket 106 with the first bracket 104.
In some embodiments, the weld joint arrangement 108 may include one or more weld joints to fixedly attach the first bracket 104 and the second bracket to one another, e.g., such that a first side wall 118a of the first bracket 104 abuts a second side wall 130a of the second bracket 106. According to various embodiments, the weld joint(s) may include one or more spot welds 136, e.g., as indicated in
In some non-limiting examples, the weld joint(s) may include a first set of one or more spot welds 136a (see detail view in
In some non-limiting examples, the weld joint(s) may include a seam weld 138 between a first interior edge of the first side wall 118a (of the first bracket 104) and a second interior edge of the second side wall 130a (of the second bracket 106). The first interior edge may at least partially define the first cutout portion of the first side wall 118a. The second interior edge may at least partially define the second cutout portion of the second side wall 130a. That is, the first interior edge and/or the second interior edge may define the combined cutout portion 144 in some embodiments.
In some non-limiting examples, the weld joint(s) may include side butt welds 140 and a top edge butt weld 142. A first side butt weld 140a may be produced between the first side wall 118a of the first bracket 104 and a first corner portion 146a the second bracket 106, e.g., as indicated in the detail view in
In various embodiments, the weld joint arrangement 108 (e.g., the spot weld(s) 136, the seam weld(s) 138, the side butt weld(s) 140, and/or the top edge butt weld(s) 142) may be configured to counteract forces (e.g., pull, torque, etc.) imposed on the welded bracket structure 102, such that the first bracket 104 and the second bracket 106 are maintained securely attached to one another. In some examples, the spot weld(s) 136 may be used to bring the first bracket 104 and the second bracket 106 together, e.g., such that the respective geometries of the first side wall 118a and the second side wall 130a abut one another. That is, the spot weld(s) 136 may be produced before the other types of weld joints in some non-limiting examples. In various examples, the first bracket 104 and the second bracket 106 may be welded to one another (e.g., via the weld joint arrangement 108) with the target of having no gaps between the first side wall 118a and the second side wall 130a. In some cases, gaps between the first side wall 118a and the second side wall 130a may negatively impact accuracy in the manufacturing and/or assembling of the welded bracket structure 102. Additionally, or alternatively, gaps between the first side wall 118a and the second side wall 130a may negatively impact accuracy of alignment between camera modules coupled to the welded bracket structure 102. As discussed below with reference to
At 306, the process 300 may include forming aperture(s) and/or cutout portion(s) on the first bracket. At 308, the process 300 may include forming aperture(s) and/or cutout portion(s) on the second bracket. In some non-limiting examples, the aperture(s) and/or cutout portion(s) may be formed by performing one or more piercing and/or punching operations on the first bracket and/or the second bracket.
At 310, the process 300 may include performing one or more lapping operations (e.g., rotational grinding) on a first top wall (e.g., the first top wall 116 in
At 312, the process 300 may include aligning the first bracket with the second bracket. For example, each of the first bracket and the second bracket may be positioned in respective attachment orientations so that they may be attached to one another, e.g., via welding. In some examples, a first cutout portion of the first bracket may be aligned with a second cutout portion of the second bracket. The first cutout portion may be defined by a first side wall (e.g., the first side wall 118a in
At 314, the process 300 may include welding the first bracket and the second bracket together. In various examples, the first bracket and the second bracket may be welded together via a weld joint arrangement (e.g., weld joint arrangement 108 described above with reference to
At 316, the process 300 may include performing one or more lapping operations on the first top wall of the first bracket and the second top wall of the second bracket, e.g., after the brackets have been welded together. The lapping operation(s) may be performed to ensure that the first top wall of the first bracket is flush with the second top wall of the second bracket. That is, in some embodiments the first top wall may be coplanar with the second top wall as a result of the lapping operation(s).
At 318, the process 300 may include plating the welded bracket structure. For example, the welded bracket structure may be plated with a material (e.g., nickel) to prevent corrosion, e.g., if the first bracket and/or the second bracket are formed of a material that is susceptible to corrosion (e.g., copper). In some examples, the plating may additionally, or alternatively, be performed on the first bracket and/or the second bracket individually, e.g., before the welding (at 314) as indicated by the dashed arrow in
As mentioned above, in various embodiments a welded bracket structure may include a cutout portion that may allow epoxy to flow from a first bracket to a second bracket, or vice-versa.
The welded bracket structure may include a first bracket 402 and a second bracket 404. While not shown in
In some examples, the multi-camera system may include a first camera module 406, a second camera module 408, and a third camera module 410. The first bracket 402 may at least partially encompass the first camera module 406 and the second camera module 408, e.g., such that they are adjacent to each other. The second bracket 404 may at least partially encompass the third camera module 410. In some embodiments, the multi-camera system of
According to various embodiments, the epoxy arrangement 400 may include a first epoxy 412 and/or a second epoxy 414. The first epoxy 412 and the second epoxy 414 may be different types of epoxies in some embodiments. In some non-limiting examples, the first epoxy 412 (e.g., a silver epoxy) may be used to electrically ground the welded bracket structure to the camera modules, and the second epoxy 414 may comprise a thermal epoxy.
In some examples, the first epoxy 412 may include one or more first portions 412a that provide an electrical connection between the welded bracket structure and the camera modules for the first bracket 402, e.g., to ground the welded bracket structure to those camera modules for electromagnetic interference (EMI) purposes. For example, the first portion(s) 412a may contact the first bracket 402 and a respective component (e.g., a shield can, a stiffener, etc.) of each of the first camera module 406 and the second camera module 408. Furthermore, the first epoxy 412 may include one or more second portions 412b that provide an electrical connection between the welded bracket structure and the camera modules for the second bracket 404, e.g., to ground the welded bracket structure to those camera modules for EMI purposes. For example, the second portion(s) 412b may contact the second bracket 404 and a component (e.g., a shield can, a stiffener, etc.) of the third camera module 410.
In some examples, the second epoxy 414 (e.g., a thermal epoxy) may be dispensed into the multi-camera system, e.g., in an epoxy potting process. A needle may be used to inject the second epoxy 414 into the multi-camera system via one or more injections points, such as the first injection point 414a and the second injection point 414b indicated in
In some embodiments, the first epoxy 412 and the second epoxy 414 may be dispensed into the multi-camera system after one or more of the camera modules are actively aligned. In performing such active alignment, the welded bracket structure may be used as a reference to align camera modules with one another. For example, the first camera module 406 (and/or the second camera module 408) may be placed in the welded bracket structure, and the third camera module 410 may be actively aligned to the first camera module 406 (and/or the second camera module 408). An ultraviolet (UV) flash epoxy (not shown) may be used during the active alignment process to mount the camera modules to the welded bracket structure. In some examples, the first epoxy 412 may be dispensed during a time period after the UV flash epoxy is dispensed and before the second epoxy 414 is dispensed. According to some examples, the second epoxy 414 may be dispensed (e.g., using the first injection point 414a and/or the second injection point 414b for potting) to produce a thermal fill that encompasses the camera modules. The second epoxy 414 may be dispensed until it reaches a particular height of the wall (e.g., the full height), which may increase rigidity and improve reliability of the multi-camera system.
According to some embodiments, each of the camera modules may include a flex circuit board. For example, the first camera module 406 may include a first flex circuit board 416, the second camera module 408 may include a second flex circuit board 418, and the third camera module 410 may include a third flex circuit board 420. The flex circuit boards may convey signals (e.g. power and/or control signals) from the respective camera modules to one or more other components outside of the welded bracket structure. In a non-limiting example, the multi-camera system may be included in a mobile device, and the flex circuit boards may convey signals from the respective camera modules to one or more components (e.g., processor(s), controller(s), etc.) of the mobile device that are external to the welded bracket structure.
At 504, the method 500 may include forming a second bracket of the welded bracket structure. For example, at 504a, forming the second bracket may include deep drawing a second sheet of metal. In some embodiments, forming the second bracket may include removing one or more portions of the second sheet of metal, at 504b. In various examples, one or more portions of the second sheet of metal may be removed to form one or more apertures, one or more cutout portions, and/or one or more reduced wall thicknesses, e.g., as described above with reference to
At 506, the method 500 may include welding the first bracket to the second bracket. In some examples, welding the first bracket to the second bracket may produce one or more weld joints that fixedly attach the first bracket to the second bracket, e.g., such that a first side wall of the first bracket abuts a second side wall of the second bracket. The first side wall may be adjacent a first top wall of the first bracket. The first top wall may define a first set of one or more apertures (e.g., apertures formed at 502b) to receive at least a portion of a first set of one or more camera modules. The second side wall may be adjacent a second top wall of the second bracket. The second top wall may define a second set of one or more apertures (e.g., an aperture formed at 504b) to receive at least a portion of a second set of one or more camera modules.
According to various examples, the welding the first bracket to the second bracket may include producing one or more spot welds, one or more seam welds, and/or one or more butt welds. The spot weld(s) may include a first spot weld and/or a second spot weld produced between the first side wall of the first bracket and the second side wall of the second bracket. The first spot weld may be located to a first side of a first cutout portion of the first bracket. The second spot weld may be located to a second side of the first cutout portion, the second side being opposite the first side. The seam weld(s) may include a seam weld produced between a first edge of the first side wall and a second edge of the second side wall. In some examples, the first edge may at least partially define the first cutout portion, and the second edge may at least partially define a second cutout portion of the second bracket. The butt weld(s) may include a first side butt weld, a second side butt weld, and/or a top edge butt weld. The first side butt weld may be produced between the first side wall of the first bracket and a first corner portion of the second bracket. The first corner portion may comprise a portion of the second side wall and a portion of a third side wall that is orthogonal to the second side wall and the second top wall. The second side butt weld may be produced between the first side wall of the first bracket and a second corner portion of the second bracket. The second corner portion may comprise another portion of the second side wall and a portion of a fourth side wall that is opposite the third side wall. The top edge butt weld may be produced between a first exterior edge of the first side wall and a second exterior edge of the second side wall.
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, California 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 600 is only one example of a portable multifunction device, and that device 600 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 602 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 602 by other components of device 600, such as CPU 620 and the peripherals interface 618, may be controlled by memory controller 622.
Peripherals interface 618 can be used to couple input and output peripherals of the device to CPU 620 and memory 602. The one or more processors 620 run or execute various software programs and/or sets of instructions stored in memory 602 to perform various functions for device 600 and to process data.
In some embodiments, peripherals interface 618, CPU 620, and memory controller 622 may be implemented on a single chip, such as chip 604. In some other embodiments, they may be implemented on separate chips.
RF (radio frequency) circuitry 608 receives and sends RF signals, also called electromagnetic signals. RF circuitry 608 converts electrical signals to/from electromagnetic signals and communicates with communications networks and other communications devices via the electromagnetic signals. RF circuitry 608 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 608 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 (HSUPA), 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 610, speaker 611, and microphone 613 provide an audio interface between a user and device 600. Audio circuitry 610 receives audio data from peripherals interface 618, converts the audio data to an electrical signal, and transmits the electrical signal to speaker 611. Speaker 611 converts the electrical signal to human-audible sound waves. Audio circuitry 610 also receives electrical signals converted by microphone 613 from sound waves. Audio circuitry 610 converts the electrical signal to audio data and transmits the audio data to peripherals interface 618 for processing. Audio data may be retrieved from and/or transmitted to memory 602 and/or RF circuitry 608 by peripherals interface 618. In some embodiments, audio circuitry 610 also includes a headset jack (e.g., 712,
I/O subsystem 606 couples input/output peripherals on device 600, such as touch screen 612 and other input control devices 616, to peripherals interface 618. I/O subsystem 606 may include display controller 656 and one or more input controllers 660 for other input or control devices. The one or more input controllers 660 receive/send electrical signals from/to other input or control devices 616. The other input control devices 616 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) 660 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., 708,
Touch-sensitive display 612 provides an input interface and an output interface between the device and a user. Display controller 656 receives and/or sends electrical signals from/to touch screen 612. Touch screen 612 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 612 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 612 and display controller 656 (along with any associated modules and/or sets of instructions in memory 602) detect contact (and any movement or breaking of the contact) on touch screen 612 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 612. In an example embodiment, a point of contact between touch screen 612 and the user corresponds to a finger of the user.
Touch screen 612 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 612 and display controller 656 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 612. 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, California.
Touch screen 612 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 612 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 600 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 612 or an extension of the touch-sensitive surface formed by the touch screen.
Device 600 also includes power system 662 for powering the various components. Power system 662 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 600 may also include one or more optical sensors or cameras 664.
Device 600 may also include one or more proximity sensors 666.
Device 600 includes one or more orientation sensors 668. In some embodiments, the one or more orientation sensors 668 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 668 include one or more gyroscopes. In some embodiments, the one or more orientation sensors 668 include one or more magnetometers. In some embodiments, the one or more orientation sensors 668 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 600. In some embodiments, the one or more orientation sensors 668 include any combination of orientation/rotation sensors.
In some embodiments, the software components stored in memory 602 include operating system 626, communication module (or set of instructions) 628, contact/motion module (or set of instructions) 630, graphics module (or set of instructions) 632, text input module (or set of instructions) 634, Global Positioning System (GPS) module (or set of instructions) 635, arbiter module 658 and applications (or sets of instructions) 636. Furthermore, in some embodiments memory 602 stores device/global internal state 657. Device/global internal state 657 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 612; sensor state, including information obtained from the device's various sensors and input control devices 616; and location information concerning the device's location and/or attitude.
Operating system 626 (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 628 facilitates communication with other devices over one or more external ports 624 and also includes various software components for handling data received by RF circuitry 608 and/or external port 624. External port 624 (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 630 may detect contact with touch screen 612 (in conjunction with display controller 656) and other touch sensitive devices (e.g., a touchpad or physical click wheel). Contact/motion module 630 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 630 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 630 and display controller 656 detect contact on a touchpad.
Contact/motion module 630 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 632 includes various known software components for rendering and displaying graphics on touch screen 612 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 632 stores data representing graphics to be used. Each graphic may be assigned a corresponding code. Graphics module 632 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 656.
Text input module 634, which may be a component of graphics module 632, provides soft keyboards for entering text in various applications (e.g., contacts 637, e-mail 640, IM 641, browser 647, and any other application that needs text input).
GPS module 635 determines the location of the device and provides this information for use in various applications (e.g., to telephone module 638 for use in location-based dialing, to camera module 643 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 636 may include the following modules (or sets of instructions), or a subset or superset thereof:
Examples of other applications 636 that may be stored in memory 602 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 612, display controller 656, contact module 630, graphics module 632, and text input module 634, contacts module 637 may be used to manage an address book or contact list (e.g., stored in application internal state 657), 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 638, video conference 639, e-mail 640, or IM 641; and so forth.
In conjunction with RF circuitry 608, audio circuitry 610, speaker 611, microphone 613, touch screen 612, display controller 656, contact module 630, graphics module 632, and text input module 634, telephone module 638 may be used to enter a sequence of characters corresponding to a telephone number, access one or more telephone numbers in address book 637, 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 608, audio circuitry 610, speaker 611, microphone 613, touch screen 612, display controller 656, optical sensor 664, optical sensor controller 658, contact module 630, graphics module 632, text input module 634, contact list 637, and telephone module 638, videoconferencing module 639 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 608, touch screen 612, display controller 656, contact module 630, graphics module 632, and text input module 634, e-mail client module 640 includes executable instructions to create, send, receive, and manage e-mail in response to user instructions. In conjunction with image management module 644, e-mail client module 640 makes it very easy to create and send e-mails with still or video images taken with camera module 643.
In conjunction with RF circuitry 608, touch screen 612, display controller 656, contact module 630, graphics module 632, and text input module 634, the instant messaging module 641 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 608, touch screen 612, display controller 656, contact module 630, graphics module 632, text input module 634, GPS module 635, map module 654, and music player module 646, workout support module 642 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 612, display controller 656, optical sensor(s) 664, optical sensor controller 658, contact module 630, graphics module 632, and image management module 644, camera module 643 includes executable instructions to capture still images or video (including a video stream) and store them into memory 602, modify characteristics of a still image or video, or delete a still image or video from memory 602.
In conjunction with touch screen 612, display controller 656, contact module 630, graphics module 632, text input module 634, and camera module 643, image management module 644 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 608, touch screen 612, display system controller 656, contact module 630, graphics module 632, and text input module 634, browser module 647 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 608, touch screen 612, display system controller 656, contact module 630, graphics module 632, text input module 634, e-mail client module 640, and browser module 647, calendar module 648 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 608, touch screen 612, display system controller 656, contact module 630, graphics module 632, text input module 634, and browser module 647, widget modules 649 are mini-applications that may be downloaded and used by a user (e.g., weather widget 549-1, stocks widget 549-2, calculator widget 649-3, alarm clock widget 649-4, and dictionary widget 649-5) or created by the user (e.g., user-created widget 649-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 608, touch screen 612, display system controller 656, contact module 630, graphics module 632, text input module 634, and browser module 647, the widget creator module 650 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 612, display system controller 656, contact module 630, graphics module 632, and text input module 634, search module 651 includes executable instructions to search for text, music, sound, image, video, and/or other files in memory 602 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 612, display system controller 656, contact module 630, graphics module 632, audio circuitry 610, speaker 611, RF circuitry 608, and browser module 647, video and music player module 652 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 612 or on an external, connected display via external port 624). In some embodiments, device 600 may include the functionality of an MP3 player.
In conjunction with touch screen 612, display controller 656, contact module 630, graphics module 632, and text input module 634, notes module 653 includes executable instructions to create and manage notes, to do lists, and the like in accordance with user instructions.
In conjunction with RF circuitry 608, touch screen 612, display system controller 656, contact module 630, graphics module 632, text input module 634, GPS module 635, and browser module 647, map module 654 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 612, display system controller 656, contact module 630, graphics module 632, audio circuitry 610, speaker 611, RF circuitry 608, text input module 634, e-mail client module 640, and browser module 647, online video module 655 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 624), 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 641, rather than e-mail client module 640, 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 602 may store a subset of the modules and data structures identified above. Furthermore, memory 602 may store additional modules and data structures not described above.
In some embodiments, device 600 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 600, the number of physical input control devices (such as push buttons, dials, and the like) on device 600 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 600 to a main, home, or root menu from any user interface that may be displayed on device 600. 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 600 may also include one or more physical buttons, such as “home” or menu button 704. As described previously, menu button 704 may be used to navigate to any application 636 in a set of applications that may be executed on device 600. Alternatively, in some embodiments, the menu button 704 is implemented as a soft key in a GUI displayed on touch screen 612.
In one embodiment, device 600 includes touch screen 612, menu button 704, push button 706 for powering the device on/off and locking the device, volume adjustment button(s) 708, Subscriber Identity Module (SIM) card slot 710, head set jack 712, and docking/charging external port 724. Push button 706 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 600 also may accept verbal input for activation or deactivation of some functions through microphone 613.
It should be noted that, although many of the examples herein are given with reference to optical sensor(s)/camera(s) 664 (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) 664 on the front of a device.
Example Computer System
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 800, which may interact with various other devices. Note that any component, action, or functionality described above with respect to
In various embodiments, computer system 800 may be a uniprocessor system including one processor 810, or a multiprocessor system including several processors 810 (e.g., two, four, eight, or another suitable number). Processors 810 may be any suitable processor capable of executing instructions. For example, in various embodiments processors 810 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 810 may commonly, but not necessarily, implement the same ISA.
System memory 820 may be configured to store camera control program instructions 822 and/or camera control data accessible by processor 810. In various embodiments, system memory 820 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 822 may be configured to implement a lens control application 824 incorporating any of the functionality described above. Additionally, existing camera control data 832 of memory 820 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 820 or computer system 800. While computer system 800 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 830 may be configured to coordinate I/O traffic between processor 810, system memory 820, and any peripheral devices in the device, including network interface 840 or other peripheral interfaces, such as input/output devices 850. In some embodiments, I/O interface 830 may perform any necessary protocol, timing or other data transformations to convert data signals from one component (e.g., system memory 820) into a format suitable for use by another component (e.g., processor 810). In some embodiments, I/O interface 830 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 830 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 830, such as an interface to system memory 820, may be incorporated directly into processor 810.
Network interface 840 may be configured to allow data to be exchanged between computer system 800 and other devices attached to a network 885 (e.g., carrier or agent devices) or between nodes of computer system 800. Network 885 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 840 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 850 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 800. Multiple input/output devices 850 may be present in computer system 800 or may be distributed on various nodes of computer system 800. In some embodiments, similar input/output devices may be separate from computer system 800 and may interact with one or more nodes of computer system 800 through a wired or wireless connection, such as over network interface 840.
As shown in
Those skilled in the art will appreciate that computer system 800 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 800 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 800 may be transmitted to computer system 800 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.
Additional descriptions of embodiments (example clauses):
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 is a continuation of U.S. application Ser. No. 16/825,521, filed Mar. 20, 2020, which claims benefit of priority to U.S. Provisional Application Ser. No. 62/826,657, filed Mar. 29, 2019, which are hereby incorporated by reference herein in their entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 7271511 | Osaka | Sep 2007 | B2 |
| 20120075519 | Blasch | Mar 2012 | A1 |
| 20140267882 | O'Neill et al. | Sep 2014 | A1 |
| 20170263515 | Bolognia et al. | Sep 2017 | A1 |
| 20180348469 | Son et al. | Dec 2018 | A1 |
| 20190250312 | Moon et al. | Aug 2019 | A1 |
| 20200310072 | Hubert et al. | Oct 2020 | A1 |
| 20220151087 | Hillman | May 2022 | A1 |
| Number | Date | Country |
|---|---|---|
| 103095974 | May 2013 | CN |
| 103713447 | Apr 2014 | CN |
| 107561825 | Jan 2018 | CN |
| 207316382 | May 2018 | CN |
| 207316382 | May 2018 | CN |
| 208027061 | Oct 2018 | CN |
| 109076150 | Dec 2018 | CN |
| 208334752 | Jan 2019 | CN |
| 208540011 | Feb 2019 | CN |
| 208540011 | Feb 2019 | CN |
| 2555526 | Feb 2013 | EP |
| 2924501 | Sep 2015 | EP |
| 2924501 | Sep 2016 | EP |
| 2018052228 | Mar 2018 | WO |
| Entry |
|---|
| Office Action and Search Report Mailed Dec. 9, 2023 from Chinese Patent Application No. 202210559420.8, Apple Inc., pp. 1-11. |
| Number | Date | Country | |
|---|---|---|---|
| 20230228965 A1 | Jul 2023 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62826657 | Mar 2019 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16825521 | Mar 2020 | US |
| Child | 18189167 | US |
