Intelligent actuation of temple ends

Through the actuator control system of intelligent actuation glasses, the length of the temple end of the glasses is adjusted using pneumatic actuators and machine learning models, solving the problems of difficulty and high cost of adjustment of traditional glasses, and improving the wearer's comfort and use Experience.

CN119032312APending Publication Date: 2024-11-26SNAP INC
View PDF 0 Cites 3 Cited by

Patent Information

Application Number
CN202380033148.2
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-04-11
Filing Date
2023-04-04
Publication Date
2024-11-26

AI Technical Summary

Technical Problem

It is difficult to adjust the traditional glasses frame, especially the length of the end of the temples, which cannot be effectively adjusted, resulting in insufficient comfort for the wearer and the cost of replacing the glasses frame is high.

Method used

The actuator control system of intelligent actuation glasses is adopted. Through pneumatic actuators and machine learning models, the length of the temple end is adjusted in real time according to user feedback and measurement data to achieve a more comfortable adaptation.

Benefits of technology

It enables intelligent adjustment of the length of the end of the glasses temple without completely replacing the parts, improving the wearer's comfort and user experience and reducing replacement costs.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119032312A_ABST
    Figure CN119032312A_ABST
Patent Text Reader

Abstract

Systems and methods herein describe actuator control systems for controlling intelligently actuated temple ends of a pair of eyeglasses. The actuator control system receives a set of measurements corresponding to the length of the temple ends on the pair of eyeglasses, receives user feedback corresponding to the position of the temple ends from a user of the pair of eyeglasses, generates a set of predicted measurements for the length of the temple ends using a machine learning model, and transmits the set of predicted measurements to the pair of eyeglasses. And transmitting the set of predicted measurements to a pneumatic actuator coupled to the ends of the spectacle legs.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] Embodiments herein generally relate to adjusting eyeglass frame size.More specifically, but not by way of limitation, embodiments herein describe an actuator control system for intelligently actuating temple tips. Background Art

[0002] The eyeglass temple is the stem of the frame that connects the front of the eyeglasses to the back of the wearer's head, just behind the wearer's ear. Eyeglass temple measurements contribute to the comfort of the eyeglasses for the wearer. Eyeglass temple tips are the part of the eyeglass temple that rests around the wearer's ear. BRIEF DESCRIPTION OF THE DRAWINGS

[0003] In the drawings, which are not necessarily drawn to scale, similar reference numerals may describe similar components in different views. To easily identify the discussion of any particular element or action, the most significant digit or digits in a reference numeral refer to the figure number in which the element is first introduced. Some non-limiting examples are shown in the accompanying drawings, in which:

[0004] Figure 1 is a block diagram illustrating an example messaging system for exchanging data over a network according to an example implementation.

[0005] Figure 2 A head wearable device according to an example embodiment is shown.

[0006] Figure 3 is a flow chart of a method for remotely adjusting the length of temple ends on a pair of wearable eyeglasses, according to an example implementation.

[0007] Figure 4 is a diagrammatic representation of a machine within which instructions may be executed for causing the machine to perform any one or more of the methodologies discussed herein.

[0008] Figure 5 is a block diagram illustrating a software architecture that may be installed on any one or more of the devices described herein.

[0009] Figure 6 A system in which a head wearable device may be implemented is shown according to an example embodiment. DETAILED DESCRIPTION

[0010] Traditionally, eyeglass frames cannot be changed without completely replacing the parts. Most parts of eyeglass frames are not easily adjustable, and replacing eyeglass frames can be expensive. Specifically, the temple ends on a pair of glasses must typically be adjusted (e.g., bent or straightened) by applying heat. However, bending or straightening the temple ends does not change the length of the temples of the glasses, and only changes how the temple ends fit around the wearer's ears.

[0011] The systems and methods herein describe temple tips for smart actuated eyeglasses. The temple tips for smart actuated eyeglasses are controlled by an actuator control system. The actuator control system adjusts the length of the temple tips of a pair of eyeglasses to provide a more comfortable fit for the wearer of the eyeglasses.

[0012] The pair of glasses may be a device having at least one of augmented reality capability or virtual reality capability. The pair of glasses comprises two actuators at each temple end of the pair of glasses. The actuators may be, for example, pneumatic actuators connected to a tank of compressed air or gas via an air tube.

[0013] The actuator control system receives the current length of the temple end of a pair of glasses and feedback from the user corresponding to the current fit of the glasses. Based on the current length and the received user feedback, the actuator control system generates a predicted length for the temple end. The predicted length is generated using a machine learning model. The machine learning model can be trained based on historical user data. After generating the predicted length for the temple end, the actuator control system transmits the predicted length to the pneumatic actuator. The actuator control system causes the pneumatic actuator to modify the current length of the temple end (e.g., expand or contract the length of the temple end) based on the predicted length. Additional details about the actuator control system are described below.

[0014] Networked computing environment

[0015] Figure 1 1 is a block diagram illustrating an example messaging system 100 for exchanging data (e.g., messages and associated content) over a network. The messaging system 100 includes multiple instances of client devices 102, each of which hosts multiple applications including a messaging client 104 and other applications 106. Each messaging client 104 is communicatively coupled to other instances of the messaging client 104 (e.g., hosted on respective other client devices 102), a messaging server system 108, and a third-party server 110 via a network 112 (e.g., the Internet). The messaging client 104 may also communicate with the local host application 106 using an application program interface (API).

[0016] The messaging clients 104 are able to communicate and exchange data with other messaging clients 104 and messaging server systems 108 via the network 112. The data exchanged between the messaging clients 104 and between the messaging clients 104 and messaging server systems 108 include functions (e.g., commands for activating functions) and payload data (e.g., text, audio, video, or other multimedia data).

[0017] The messaging server system 108 provides server-side functionality to specific messaging clients 104 via the network 112. Although certain functions of the messaging system 100 are described herein as being performed by the messaging client 104 or by the messaging server system 108, the location of certain functions within the messaging client 104 or within the messaging server system 108 may be a design choice. For example, it may be technically preferable to initially deploy certain technologies and functions within the messaging server system 108, but later migrate the technologies and functions to the messaging client 104 where the client device 102 has sufficient processing power.

[0018] The messaging server system 108 supports various services and operations provided to the messaging clients 104. Such operations include transmitting data to the messaging clients 104, receiving data from the messaging clients 104, and processing data generated by the messaging clients 104. As examples, the data may include message content, client device information, geographic location information, media enhancements and overlays, message content persistence conditions, social network information, and live event information. The data exchange within the messaging system 100 is initiated and controlled by functions available via the user interface (UI) of the messaging client 104.

[0019] Turning now specifically to the messaging server system 108, an application program interface (API) server 116 is coupled to the application server 114 and provides a programming interface to the application server 114. The application server 114 is communicatively coupled to a database server 120, which facilitates access to a database 126 that stores data associated with messages processed by the application server 114. Similarly, a web server 128 is coupled to the application server 114 and provides a web-based interface to the application server 114. To this end, the web server 128 handles incoming network requests via the Hypertext Transfer Protocol (HTTP) and several other related protocols.

[0020] The application program interface (API) server 116 receives and transmits message data (e.g., commands and message payloads) between the client device 102 and the application server 114. Specifically, the application program interface (API) server 116 provides a set of interfaces (e.g., routines and protocols) that can be called or queried by the messaging client 104 to facilitate activating the functions of the application server 114. An application program interface (API) server 116 exposes various functions supported by application server 114, including: account registration; login functionality; sending messages from a particular messaging client 104 to another messaging client 104 via application server 114; sending media files (e.g., images or videos) from a messaging client 104 to messaging server 118 and for possible access by another messaging client 104; setting of a collection of media data (e.g., a story); retrieving a friend list of a user of client device 102; retrieving such a collection; retrieving messages and content; adding and removing entities (e.g., friends) from an entity graph (e.g., a social graph); locating friends within a social graph; and opening application events (e.g., related to messaging client 104).

[0021] The application server 114 hosts multiple server applications and subsystems, including, for example, a messaging server 118, an image processing server 122, a social network server 124, and an actuator control system 130. The messaging server 118 implements multiple message processing techniques and functions, particularly those related to the aggregation and other processing of content (e.g., text and multimedia content) included in messages received from multiple instances of the messaging client 104. As will be described in further detail, text and media content from multiple sources can be aggregated into collections of content (e.g., called stories or galleries). These collections are then made available to the messaging client 104. Given the hardware requirements for other processor- and memory-intensive data processing, such processing can also be performed on the server side by the messaging server 118.

[0022] The application server 114 also includes an image processing server 122 that is dedicated to performing various image processing operations, typically on images or videos within the payload of messages sent from or received at the messaging server 118 .

[0023] The social network server 124 supports various social networking functions and services and makes these functions and services available to the messaging server 118. Examples of functions and services supported by the social network server 124 include identifying other users with whom a particular user of the messaging system 100 has relationships or that the particular user is "following", and also includes identifying interests and other entities of a particular user.

[0024] The actuator control system 130 generates an adjustment to the length of the temple end of the glasses by remotely controlling a pair of glasses with an AR / VR display system. For example, the actuator control system 130 can use a machine learning model to intelligently predict the length of the temple end of a specific user, and can adjust the length of the temple end by using a series of actuators to contract or extend the temple end.

[0025] Returning to the messaging client 104, the features and functions of the external resource (e.g., application 106 or applet) are available to the user via the interface of the messaging client 104. In this context, "external" refers to the fact that the application 106 or applet is outside the messaging client 104. External resources are usually provided by a third party, but can also be provided by the creator or provider of the messaging client 104. The messaging client 104 receives a user selection of an option for launching or accessing features of such an external source. The external resource can be an application 106 installed on the client device 102 (e.g., a "local app"), or a small-scale version of the application hosted on the client device 102 or away from the client device 102 (e.g., on a third-party server 110) (e.g., a "applet"). The small-scale version of the application includes a subset of the features and functions of the application (e.g., a full-scale, local version of the application) and is implemented using a markup language document. In one example, the small-scale version of the application (e.g., a "applet") is a web-based markup language version of the application and is embedded in the messaging client 104. In addition to using markup language documents (eg, .*ml files), applets may also include scripting languages ​​(eg, .*js files or .json files) and style sheets (eg, .*ss files).

[0026] In response to receiving a user selection of an option for launching or accessing a feature of an external resource, the messaging client 104 determines whether the selected external resource is a web-based external resource or a locally installed application 106. In some cases, an application 106 locally installed on the client device 102 may be launched independently of and separately from the messaging client 104, for example, by selecting an icon corresponding to the application 106 on a home screen of the client device 102. A small-scale version of such an application may be launched or accessed via the messaging client 104, and in some examples, none of the portions of the small-scale application may be accessed outside of the messaging client 104 or limited portions of the small-scale application may be accessed outside of the messaging client 104. The small-scale application may be launched by the messaging client 104 receiving, for example, a markup language document associated with the small-scale application from a third-party server 110 and processing such a document.

[0027] In response to determining that the external resource is a locally installed application 106, the messaging client 104 instructs the client device 102 to launch the external resource by executing locally stored code corresponding to the external resource. In response to determining that the external resource is a web-based resource, the messaging client 104 communicates with the third-party server 110 (for example) to obtain a markup language document corresponding to the selected external resource. The messaging client 104 then processes the obtained markup language document to present the web-based external resource within the user interface of the messaging client 104.

[0028] The messaging client 104 may notify the user of the client device 102 or other users (e.g., "friends") associated with such a user of activities occurring in one or more external resources. For example, the messaging client 104 may provide a notification to a participant in a conversation (e.g., a chat session) in the messaging client 104 about the current or recent use of an external resource by one or more members of a group of users. One or more users may be invited to join an active external resource or to start an external resource that was recently used but is currently inactive (in the friend group). The external resource may provide the participants of the conversation, each using a corresponding messaging client 104, with the ability to share items, conditions, states, or locations in an external resource with one or more members of a group of users in a chat session. The shared item may be an interactive chat card that members of the chat may interact with, for example, to start a corresponding external resource, view specific information within an external resource, or bring members of the chat to a specific location or state within an external resource. Within a given external resource, a response message may be sent to the user on the messaging client 104. The external resource may selectively include different media items in the response based on the current context of the external resource.

[0029] The messaging client 104 may present a list of available external resources (e.g., applications 106 or applets) to the user to launch or access a given external resource. The list may be presented in a context-sensitive menu. For example, icons representing different applications (or applets) of the applications 106 (or applets) may vary based on how the user launches the menu (e.g., from a conversational interface or from a non-conversational interface).

[0030] Figure 2 A head wearable device 200 is shown according to one example embodiment. Figure 2 A perspective view of a head wearable device 200 is shown according to an example implementation. In some examples, a client device 102 can include a head wearable device 200. In some examples, the head wearable device can be part of a messaging server system 108.

[0031] exist Figure 2 , the head wearable device 200 is a pair of glasses. In some embodiments, the head wearable device 200 can be sunglasses or goggles. Some embodiments may include one or more wearable devices, such as a pendant with an integrated camera that is integrated, communicates with, or is coupled to the head wearable device 200 or the client device 102. Any desired wearable device may be used in conjunction with embodiments of the present disclosure, such as a watch, headphones, wristband, earbuds, clothing (such as a hat or jacket with an integrated electronic device), a clip-on electronic device, or any other wearable device. It should be understood that, although not shown, one or more portions of the system included in the head wearable device 200 may be included in a client device 102 that may be used in conjunction with the head wearable device 200.

[0032] exist Figure 2 In the embodiment, the head wearable device 200 is a pair of glasses including a frame 210, which includes a frame (or frame) that is respectively coupled to two handles (or temples) via hinges and / or end pieces. The frame of the frame 210 carries or accommodates a pair of lenses (e.g., lens 212 and lens 214). The frame 210 includes a first (e.g., right) side coupled to the first handle and a second (e.g., left) side coupled to the second handle. The first side is opposite to the second side of the frame 210.

[0033] The head wearable device 200 also includes a camera module (not shown), which includes a camera lens (e.g., camera lens 206, camera lens 208) and at least one image sensor. The camera lens 206 and the camera lens 208 can be a perspective camera lens or a non-perspective camera lens. The non-perspective camera lens can be, for example, a fisheye lens, a wide-angle lens, an omnidirectional lens, etc. The image sensor captures digital video through the camera lens 206 and the camera lens 208. The image can also be a still image frame or a video including multiple still image frames. The camera module can be coupled to the frame 210. As shown in FIG. Figure 1 As shown in , frame 210 is coupled to camera lens 206 and camera lens 208 so that the camera lenses (e.g., camera lens 206, camera lens 208) face away from the user (e.g., rear camera). Camera lens 206 and camera lens 208 can be perpendicular to lens 212 and lens 214. The camera module can also include dual front cameras (e.g., cameras facing the user) separated by the width of frame 210 or the width of the head of the user of head wearable device 200.

[0034] exist Figure 2 , two handles (or temples) are coupled to microphone housing 202 and microphone housing 204, respectively. The first handle and the second handle are coupled to opposite sides of the frame 210 of the head wearable device 200. The first handle is coupled to the first microphone housing 202, and the second handle is coupled to the second microphone housing 204. The microphone housing 202 and the microphone housing 204 can be coupled to the handles between the frame 210 and the positions of the temple ends (template end 216 and temple end 218). When the user wears the head wearable device 200, the microphone housing 202 and the microphone housing 204 can be located on the corresponding sides of the temples of the user.

[0035] The temple end 216 includes a first actuator system, and the temple end 218 includes a second actuator system. Each of the first actuator system and the second actuator system includes two pneumatic actuators. The pneumatic actuators of each actuator system are connected to an air tank (not shown) via one or more air tubes. The air tank can be some form of pressurized gas. The first actuator system and the second actuator system expand or contract the temple end 216 and the temple end 218 respectively based on the measurement values ​​provided by the actuator control system 130. The first actuator in the first actuator system moves the temple end 216 in the horizontal direction, while the second actuator in the first actuator system moves the temple end 216 in the vertical direction. Similarly, the first actuator in the second actuator system moves the temple end 218 in the horizontal direction, while the second actuator in the second actuator system moves the temple end 218 in the vertical direction.

[0036] like Figure 2 As shown in FIG. 1 , microphone housing 202 and microphone housing 204 enclose multiple microphones (not shown). A microphone is an air interface sound pickup device that converts sound into an electrical signal. More specifically, a microphone is a transducer that converts sound pressure into an electrical signal (e.g., an acoustic signal). The microphone may be a digital or analog micro-electromechanical system (MEMS) microphone. The acoustic signal generated by the microphone may be a pulse density modulation (PDM) signal.

[0037] Although the flow chart described below can show the operation as a sequential process, many operations in the operation can be performed in parallel or simultaneously. In addition, the order of the operation can be rearranged. When the operation of the process is completed, the process is terminated. The process can correspond to a method, a process, an algorithm, etc. The operation of the method can be performed in whole or in part, can be performed in combination with some or all operations in other methods, and can be performed by any number of different systems (such as the system described herein) or any part thereof (such as a processor included in any system).

[0038] Figure 3 The method 300 for remotely adjusting the length of the temple end on a pair of wearable glasses according to an example implementation. In one example, the operations in the method 300 may be performed by a processor in the client device 102, a processor in the head wearable device 200, a processor in the messaging server system 108, a processor in the actuator control system 130, or any combination thereof.

[0039] At operation 302, the actuator control system 130 receives a set of measurements corresponding to the lengths of temple ends of eyeglasses on a pair of eyeglasses. The set of measurements may include a first length of a first temple end (e.g., temple end 216) and a second length of a second temple end (e.g., temple end 218). The measurements may be received by one or more sensors of the head wearable device 200. In some examples, the actuator control system 130 also captures a first set of images of the wearer using a front-facing camera of the head wearable device.

[0040] At operation 304, the actuator control system 130 receives user feedback corresponding to the position of the end of the temple of the glasses from the user of the pair of glasses. The feedback can be received via input received on the AR / VR display screen of the head wearable device 200. For example, the actuator control system 130 can cause one or more user interface elements (e.g., buttons, check boxes, toggle switches) to be displayed on the AR / VR display screen of the head wearable device 200. In some examples, the feedback is audio feedback received from one or more microphones (e.g., located in the microphone housing 202, within the microphone housing 202). In some examples, the feedback is a gesture or posture (e.g., thumbs up, thumbs down, etc.) received from a camera system (e.g., a rear camera) of the head wearable device 200.

[0041] At operation 306, based on the user feedback and the set of measurements, the actuator control system 130 generates a set of predicted measurements for the length of the eyeglass temple ends. For example, the actuator control system 130 can use a trained machine learning model to generate the set of predicted measurements. The machine learning model can be trained based on historical user data, including, but not limited to: eyeglass temple end length, user facial measurements, eyeglass lens size, and historical user feedback. The machine learning model can use additional data to generate the set of predicted measurements.

[0042] At operation 308, the actuator control system 130 transmits the set of predicted measurements to pneumatic actuators coupled to the ends of the temples of the eyeglasses. The actuator control system 130 causes each set of pneumatic actuators to expand or contract the material of each of the temple ends 216 and temple ends 218 based on the set of predicted measurements. The temple ends 216 and temple ends 218 of the pair of eyeglasses can be made of a material that can be rolled in and out to expand or contract a desired distance. The material can be inside a tubular cover and can be moved in and out of an outer tubular cover to adjust its size. In some examples, the material is plastic or silicon.

[0043] In some examples, the actuator control system 130 captures a second set of images of the wearer via a front-facing camera of the head wearable device. The actuator control system 130 can compare the first set of captured images with the second set of captured images. For example, the actuator control system 130 uses the captured images to determine the heart rate or blood pressure of the wearer. The actuator control system 130 can also receive heart rate or blood pressure information from one or more non-camera sensors (e.g., capacitive sensors) of the head wearable device 200. If the heart rate or blood pressure is above an average threshold, the actuator control system 130 can determine that the temple ends should be extended to reduce the pressure of the temple ends of the glasses on the wearer.

[0044] After comparing the first set of images with the second set of images, the actuator control system 130 generates a set of adjustment measurements based on the comparison of the images. The set of adjustment measurements is a modification of the set of predicted measurements. The actuator control system 130 transmits the set of adjustment measurements to two sets of pneumatic actuators coupled to each of the temple ends of the eyeglasses (e.g., temple end 216, temple end 218). The actuator control system 130 can continue to receive feedback from the wearer of the head wearable device and adjust the length of the temple end 216 and the temple end 218 until the wearer feels comfortable with the fit.

[0045] Machine Architecture

[0046] Figure 4400 within which instructions 410 (e.g., software, programs, applications, applet, app, or other executable code) may be executed for causing the machine 400 to perform any one or more of the methods discussed herein. For example, the instructions 410 may cause the machine 400 to perform any one or more of the methods described herein. The instructions 410 convert a general purpose, unprogrammed machine 400 into a specific machine 400 that is programmed to perform the functions described and illustrated in the manner described. The machine 400 may operate as a standalone device or may be coupled (e.g., networked) to other machines. In a networked deployment, the machine 400 may operate in the capacity of a server machine or a client machine in a server-client network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. The machine 400 may include, but is not limited to, a server computer, a client computer, a personal computer (PC), a tablet computer, a laptop computer, a netbook, a set-top box (STB), a personal digital assistant (PDA), an entertainment media system, a cellular phone, a smart phone, a mobile device, a wearable device (e.g., a smart watch), a smart home device (e.g., a smart appliance), other smart devices, a web device, a network router, a network switch, a network bridge, or any machine capable of sequentially or otherwise executing instructions 410 specifying actions to be taken by the machine 400. In addition, although only a single machine 400 is shown, the term "machine" should also be taken to include a collection of machines that individually or jointly execute instructions 410 to perform any one or more of the methods discussed herein. For example, the machine 400 may include any of the client device 102 or a plurality of server devices forming part of the messaging server system 108. In some examples, the machine 400 may also include both a client system and a server system, wherein certain operations of a particular method or algorithm are performed on the server side, and certain operations of the particular method or algorithm are performed on the client side.

[0047] Machine 400 may include processor 404, memory 406, and input / output I / O components 402 that may be configured to communicate with each other via bus 440. In an example, processor 404 (e.g., a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a radio frequency integrated circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, processor 408 and processor 412 that execute instructions 410. The term "processor" is intended to include multi-core processors, which may include two or more independent processors (sometimes referred to as "cores") that may execute instructions simultaneously. Although Figure 4 Multiple processors 404 are shown, but machine 400 may include a single processor with a single core, a single processor with multiple cores (e.g., a multi-core processor), multiple processors with a single core, multiple processors with multiple cores, or any combination thereof.

[0048] The memory 406 includes a main memory 414, a static memory 416, and a storage unit 418, all of which are accessible by the processor 404 via the bus 440. The main memory 406, the static memory 416, and the storage unit 418 store instructions 410 that implement any one or more of the methods or functions described herein. The instructions 410 may also reside, completely or partially, within the main memory 414, within the static memory 416, within the machine-readable medium 420 within the storage unit 418, within at least one of the processors 404 (e.g., within a cache memory of a processor), or within any suitable combination thereof during execution thereof by the machine 400.

[0049] I / O components 402 may include various components for receiving input, providing output, generating output, transmitting information, exchanging information, capturing measurements, etc. The specific I / O components 402 included in a particular machine will depend on the type of machine. For example, a portable machine such as a mobile phone may include a touch input device or other such input mechanism, while a headless server machine will be less likely to include such a touch input device. It will be appreciated that I / O components 402 may include Figure 44. In various examples, the I / O components 402 may include a user output component 426 and a user input component 428. The user output component 426 may include a visual component (e.g., a display such as a plasma display panel (PDP), a light emitting diode (LED) display, a liquid crystal display (LCD), a projector, or a cathode ray tube (CRT)), an acoustic component (e.g., a speaker), a tactile component (e.g., a vibration motor, a resistance mechanism), other signal generators, etc. The user input component 428 may include an alphanumeric input component (e.g., a keyboard, a touch screen configured to receive alphanumeric input, an optical keyboard, or other alphanumeric input component), a pointing-based input component (e.g., a mouse, a touch pad, a trackball, a joystick, a motion sensor, or another pointing instrument), a tactile input component (e.g., a physical button, a touch screen that provides the location and force of a touch or touch gesture, or other tactile input component), an audio input component (e.g., a microphone), etc.

[0050] In other examples, the I / O component 402 may include a biometric component 430, a motion component 432, an environmental component 434, or a positioning component 436, as well as various other components. For example, the biometric component 430 includes components for detecting expressions (e.g., hand expressions, facial expressions, voice expressions, body postures, or eye tracking), measuring biosignals (e.g., blood pressure, heart rate, body temperature, perspiration, or brain waves), identifying people (e.g., voice recognition, retinal recognition, facial recognition, fingerprint recognition, or EEG-based recognition), etc. The motion component 432 includes an acceleration sensor component (e.g., an accelerometer), a gravity sensor component, and a rotation sensor component (e.g., a gyroscope).

[0051] Environmental components 434 include, for example, one or more cameras (with still image / photo and video capabilities), lighting sensor components (e.g., a photometer), temperature sensor components (e.g., one or more thermometers that detect ambient temperature), humidity sensor components, pressure sensor components (e.g., a barometer), acoustic sensor components (e.g., one or more microphones that detect background noise), proximity sensor components (e.g., an infrared sensor that detects nearby objects), gas sensors (e.g., a gas detection sensor that detects concentrations of hazardous gases for safety or measures pollutants in the atmosphere), or other components that can provide indications, measurements, or signals corresponding to the surrounding physical environment.

[0052] With respect to cameras, client device 102 may have a camera system including, for example, a front-facing camera on the front surface of client device 102 and a rear-facing camera on the rear surface of client device 102. The front-facing camera may, for example, be used to capture still images and videos of a user of client device 102 (e.g., a "selfie"), which may then be enhanced using the enhancement data (e.g., filters) described above. The rear-facing camera may, for example, be used to capture still images and videos in a more traditional camera mode, where the images are similarly enhanced using the enhancement data. In addition to the front-facing camera and the rear-facing camera, client device 102 may also include a 360° camera for capturing 360° photos and videos.

[0053] Additionally, the camera system of the client device 102 may include dual rear cameras (e.g., a main camera and a depth sensing camera), or even a triple, quad, or penta rear camera configuration on the front and back sides of the client device 102. For example, these multiple camera systems may include a wide-angle camera, an ultra-wide-angle camera, a telephoto camera, a macro camera, and a depth sensor.

[0054] The positioning component 436 includes a position sensor component (e.g., a GPS receiver component), an altitude sensor component (e.g., an altimeter or a barometer that detects air pressure, from which the altitude can be obtained), an orientation sensor component (e.g., a magnetometer), etc.

[0055] Various technologies may be used to achieve communication. I / O component 402 also includes a communication component 438 that is operable to couple machine 400 to network 422 or device 424 via a corresponding coupling or connection. For example, communication component 438 may include a network interface component or another suitable device that interfaces with network 422. In other examples, communication component 438 may include a wired communication component, a wireless communication component, a cellular communication component, a near field communication (NFC) component, Parts (e.g. Low energy consumption), Device 424 may be another machine or any of a variety of peripheral devices (eg, a peripheral device coupled via USB).

[0056] In addition, the communication component 438 can detect the identifier, or include a component that is operable to detect the identifier. For example, the communication component 438 can include a radio frequency identification (RFID) tag reader component, an NFC smart tag detection component, an optical reader component (e.g., an optical sensor for detecting one-dimensional bar codes such as universal product codes (UPC) bar codes, multi-dimensional bar codes such as quick response (QR) codes, Aztec codes, data matrix, data symbols (Dataglyph), MaxiCode, PDF417, Ultra Code, UCC RSS-2D bar codes and other optical codes) or an acoustic detection component (e.g., a microphone for identifying an audio signal of a tag). In addition, various information can be obtained via the communication component 438, such as location via Internet Protocol (IP) geolocation, ... Signal triangulation to obtain location, location obtained via detection of NFC beacon signals that can indicate a specific location, etc.

[0057] Various memories (e.g., main memory 414, static memory 416, and memory of processor 404) and storage unit 418 may store one or more sets of instructions and data structures (e.g., software) implemented or used by any one or more of the methods or functions described herein. These instructions (e.g., instructions 410) when executed by processor 404 cause various operations to implement the disclosed examples.

[0058] Instructions 410 may be transmitted or received via a network interface device (e.g., a network interface component included in communications component 438) using a transmission medium and using any of several well-known transmission protocols (e.g., Hypertext Transfer Protocol (HTTP)) over network 422. Similarly, instructions 410 may be transmitted or received via a coupling (e.g., a peer-to-peer coupling) with device 424 using a transmission medium.

[0059] Software Architecture

[0060] Figure 5 500 is a block diagram illustrating a software architecture 504 that may be installed on any one or more of the devices described herein. The software architecture 504 is supported by hardware, such as a machine 502 including a processor 520, a memory 526, and an I / O component 538. In this example, the software architecture 504 may be conceptualized as a stack of layers, where each layer provides specific functionality. The software architecture 504 includes layers such as an operating system 512, a library 510, a framework 508, and an application 506. In operation, the application 506 invokes an API call 550 through the software stack and receives a message 552 in response to the API call 550.

[0061] The operating system 512 manages hardware resources and provides public services. The operating system 512 includes, for example, a kernel 514, services 516, and drivers 522. The kernel 514 acts as an abstraction layer between the hardware and other software layers. For example, the kernel 514 provides functions such as memory management, processor management (e.g., scheduling), component management, networking, and security settings. Services 516 can provide other public services to other software layers. Drivers 522 are responsible for controlling or interfacing with the underlying hardware. For example, drivers 522 may include display drivers, camera drivers, or Low-power drivers, Flash drivers, Serial communication drivers (e.g., USB drivers), Drivers, audio drivers, power management drivers, etc.

[0062] The library 510 provides a common low-level infrastructure used by the application 506. The library 510 may include a system library 518 (e.g., a C standard library) that provides functions such as memory allocation functions, string manipulation functions, mathematical functions, etc. In addition, the library 510 may include an API library 524, such as a media library (e.g., a library for supporting the presentation and manipulation of various media formats, such as Moving Picture Experts Group-4 (MPEG4), Advanced Video Coding (H.264 or AVC), Moving Picture Experts Group Layer-3 (MP3), Advanced Audio Coding (AAC), Adaptive Multi-Rate (AMR) audio codec, Joint Photographic Experts Group (JPEG or JPG), or Portable Network Graphics (PNG)), a graphics library (e.g., an OpenGL framework for rendering in two dimensions (2D) and three dimensions (3D) in graphics content on a display), a database library (e.g., SQLite providing various relational database functions), a web library (e.g., WebKit providing web browsing functions), etc. The library 510 may also include various other libraries 528 to provide many other APIs to the application 506.

[0063] The framework 508 provides a common high-level infrastructure used by the applications 506. For example, the framework 508 provides various graphical user interface (GUI) functions, advanced resource management, and advanced location services. The framework 508 can provide a wide range of other APIs that can be used by the applications 506, some of which can be specific to a specific operating system or platform.

[0064] In an example, applications 506 may include home applications 536, contact applications 530, browser applications 532, book reader applications 534, location applications 542, media applications 544, messaging applications 546, game applications 548, and a variety of other applications such as third-party applications 540. Applications 506 are programs that execute functions defined in the program. Various programming languages ​​may be used to create one or more of the applications 506 constructed in various ways, such as object-oriented programming languages ​​(e.g., Objective-C, Java, or C++) or procedural programming languages ​​(e.g., C language or assembly language). In a specific example, third-party applications 540 (e.g., applications created by entities other than the vendor of a particular platform using ANDROID TM or IOS TM Software Development Kit (SDK) can be used to develop applications on platforms such as IOS TM ANDROID TM , Mobile software running on the mobile operating system of the phone or another mobile operating system. In this example, third-party application 540 can activate API call 550 provided by operating system 512 to facilitate the functions described in this article.

[0065] System with head wearable device

[0066] Figure 6 A system in which a head wearable device 200 may be implemented is shown according to one example embodiment. Figure 6 is a high-level functional block diagram of an example head wearable device 200 communicatively coupling a mobile client device 102 (or client device 604 ) and a server system 632 via various networks 638 .

[0067] The head wearable device 200 includes a camera device, such as at least one of a visible light camera device 612, an infrared transmitter 614, and an infrared camera device 616. The camera device may include Figure 1 A camera module having a camera lens 206 and a camera lens 208.

[0068] The client device 102 may be able to connect with the head wearable device 200 using both a low power wireless connection 634 and a high speed wireless connection 636. The client device 102 connects to the server system 632 and a network 638. The network 638 may include any combination of wired and wireless connections.

[0069] The head wearable device 200 also includes two image displays in the optical assembly's image display 602. The two image displays in the optical assembly's image display 602 include one image display associated with the left lateral side of the head wearable device 200 and one image display associated with the right lateral side of the head wearable device 200. The head wearable device 200 also includes an image display driver 608, an image processor 610, low power circuitry 626 for low power consumption, and high speed circuitry 618. The optical assembly's image display 602 is used to present images and videos to a user of the head wearable device 200, including images that may include a graphical user interface.

[0070] The image display driver 608 commands and controls the image display of the image display 602 of the optical assembly. The image display driver 608 can deliver the image data directly to the image display in the image display 602 of the optical assembly for presentation, or can convert the image data into a signal or data format suitable for delivery to the image display device. For example, the image data can be video data formatted according to a compression format such as H.264 (MPEG-4 Part 10), HEVC, Theora, Dirac, RealVideoRV40, VP8, VP9, ​​etc., and the still image data can be formatted according to a compression format such as Portable Network Graphics (PNG), Joint Photographic Experts Group (JPEG), Tagged Image File Format (TIFF) or Exchangeable Image File Format (Exif), etc.

[0071] As described above, the head wearable device 200 includes a frame 210 and a handle (or temple) extending from a lateral side of the frame 210. The head wearable device 200 also includes a user input device 606 (e.g., a touch sensor or a push button) that includes an input surface on the head wearable device 200. The user input device 606 (e.g., a touch sensor or a push button) is used to receive input selections from a user to manipulate a graphical user interface of a presented image.

[0072] Figure 6 The components for the head wearable device 200 shown in are located on one or more circuit boards (e.g., PCBs or flexible PCBs) in the frame or temples. Alternatively or additionally, the depicted components can be located in a block, frame, hinge, or beam of the head wearable device 200. The left visible light camera and the right visible light camera 612 can include digital camera elements such as complementary metal oxide semiconductor (CMOS) image sensors, charge coupled devices, camera lenses 206 and camera lenses 208, or any other corresponding visible light or light capturing elements that can be used to capture data including images of scenes with unknown objects.

[0073] The head wearable device 200 includes a memory 622 that stores instructions for performing a subset or all of the functions described herein. The memory 622 may also include a storage device.

[0074] like Figure 6 As shown, the high-speed circuit system 618 includes a high-speed processor 620, a memory 622, and a high-speed wireless circuit system 624. In an example, the image display driver 608 is coupled to the high-speed circuit system 618 and is operated by the high-speed processor 620 to drive the left image display and the right image display in the image display 602 of the optical assembly. The high-speed processor 620 can be any processor capable of managing high-speed communications and operations of any general computing system required for the head wearable device 200. The high-speed processor 620 includes the processing resources required to manage high-speed data transmission on the high-speed wireless connection 636 to the wireless local area network (WLAN) using the high-speed wireless circuit system 624. In some examples, the high-speed processor 620 executes an operating system (e.g., a LINUX operating system) or other such operating system of the head wearable device 200, and the operating system is stored in the memory 622 for execution. In addition to any other duties, the high-speed processor 620 that executes the software architecture for the head wearable device 200 is used to manage data transmission with the high-speed wireless circuit system 624. In some examples, high-speed wireless circuit system 624 is configured to implement the Institute of Electrical and Electronics Engineers (IEEE) 802.11 communication standard, also referred to herein as Wi-Fi. In other examples, other high-speed communication standards can be implemented by high-speed wireless circuit system 624.

[0075] The low-power wireless circuit system 630 and the high-speed wireless circuit system 624 of the head wearable device 200 may include a short-range transceiver (Bluetooth TM ) and a wireless wide area network transceiver, a wireless local area network transceiver, or a wide area network transceiver (e.g., cellular or WiFi). The client device 102 including a transceiver for communicating via a low power wireless connection 634 and a high speed wireless connection 636 can be implemented using details of the architecture of the head wearable device 200, as can other elements of the network 638.

[0076] The memory 622 includes any storage device capable of storing various data and applications, including camera data generated by the left and right visible light cameras 612, the infrared camera 616, and the image processor 610, and images generated to be displayed on the image display in the image display 602 of the optical assembly through the image display driver 608, etc. Although the memory 622 is shown as being integrated with the high-speed circuit system 618, in other examples, the memory 622 can be an independent separate element of the head wearable device 200. In some such examples, electrical wiring can provide a connection from the image processor 610 or the low-power processor 628 to the memory 622 through a chip including the high-speed processor 620. In other examples, the high-speed processor 620 can manage the addressing of the memory 622 so that the low-power processor 628 will start the high-speed processor 620 at any time when a read or write operation involving the memory 622 is required.

[0077] like Figure 6 As shown, the low-power processor 628 or the high-speed processor 620 of the head wearable device 200 can be coupled to a camera device (a visible light camera device 612, an infrared emitter 614 or an infrared camera device 616), an image display driver 608, a user input device 606 (for example, a touch sensor or a push button), and a memory 622.

[0078] The head wearable device 200 is connected to the host. For example, the head wearable device 200 is paired with the client device 102 via a high-speed wireless connection 636, or is connected to a server system 632 via a network 638. The server system 632 can be one or more computing devices as part of a service or network computing system, for example, the one or more computing devices include a processor, a memory, and a network communication interface for communicating with the client device 102 and the head wearable device 200 through the network 638.

[0079] The client device 102 includes a processor and a network communication interface coupled to the processor. The network communication interface allows communication over a network 638, a low-power wireless connection 634, or a high-speed wireless connection 636. The client device 102 may also store at least a portion of the instructions for generating binaural audio content in a memory of the client device 102 to implement the functionality described herein.

[0080] The output components of the head wearable device 200 include visual components, such as a display such as a liquid crystal display (LCD), a plasma display panel (PDP), a light emitting diode (LED) display, a projector, or a waveguide. The image display of the optical component is driven by the image display driver 608. The output components of the head wearable device 200 also include acoustic components (e.g., speakers), tactile components (e.g., vibration motors), other signal generators, etc. The input components of the head wearable device 200, the client device 102, and the server system 632, such as the user input device 606, may include alphanumeric input components (e.g., keyboards, touch screens configured to receive alphanumeric input, optical keyboards, or other alphanumeric input components), pointing-based input components (e.g., mice, touch pads, trackballs, joysticks, motion sensors, or other pointing instruments), tactile input components (e.g., physical buttons, touch screens that provide the location and force of touch or touch gestures, or other tactile input components), audio input components (e.g., microphones), etc.

[0081] The head wearable device 200 may optionally include additional peripheral elements. Such peripheral elements may include biometric sensors, additional sensors, or display elements integrated with the head wearable device 200. For example, the peripheral elements may include any I / O components including output components, motion components, positioning components, or any other such components described herein.

[0082] For example, the biometric component includes a component for detecting expressions (e.g., hand expressions, facial expressions, voice expressions, body postures, or eye tracking), measuring biological signals (e.g., blood pressure, heart rate, body temperature, perspiration, or brain waves), identifying people (e.g., voice recognition, retinal recognition, facial recognition, fingerprint recognition, or electroencephalogram-based recognition), etc. The motion component includes an acceleration sensor component (e.g., an accelerometer), a gravity sensor component, a rotation sensor component (e.g., a gyroscope), etc. The positioning component includes a position sensor component for generating position coordinates (e.g., a global positioning system (GPS) receiver component), a WiFi or Bluetooth receiver for generating positioning system coordinates, etc. TM transceiver, altitude sensor components (e.g., an altimeter or barometer that detects air pressure from which altitude can be derived), orientation sensor components (e.g., a magnetometer), etc. Such positioning system coordinates may also be received from the client device 102 via the low power wireless circuitry 630 or the high speed wireless circuitry 624 through the low power wireless connection 634 and the high speed wireless connection 636.

[0083] When phrases similar to "at least one of A, B, or C," "at least one of A, B and C," "one or more A, B, or C," or "one or more of A, B, and C" are used, it is intended that the phrase be interpreted to mean that A can be present alone in an embodiment, B can be present alone in an embodiment, C can be present alone in an embodiment, or any combination of elements A, B, and C can be present in a single embodiment; for example, A and B, A and C, B and C, or A and B and C.

[0084] Changes and modifications may be made to the disclosed embodiments without departing from the scope of the present disclosure. These and other changes or modifications are intended to be included within the scope of the present disclosure as expressed in the appended claims.

[0085] Glossary

[0086] "Carrier signal" refers to any intangible medium that can store, encode or carry instructions for execution by a machine and includes digital or analog communications signals or other intangible media to facilitate communication of such instructions. Instructions may be transmitted or received over a network using a transmission medium via a network interface device.

[0087] "Client device" refers to any machine that interfaces with a communications network to obtain resources from one or more server systems or other client devices. A client device may be, but is not limited to, a mobile phone, a desktop computer, a laptop computer, a portable digital assistant (PDA), a smart phone, a tablet computer, an ultrabook, a netbook, a laptop computer, a multiprocessor system, a microprocessor-based or programmable consumer electronics product, a game console, a set-top box, or any other communications device that a user may use to access a network.

[0088] "Communications network" means one or more parts of a network, which may be an ad hoc network, an intranet, an extranet, a virtual private network (VPN), a local area network (LAN), a wireless LAN (WLAN), a wide area network (WAN), a wireless WAN (WWAN), a metropolitan area network (MAN), the Internet, a part of the Internet, a part of the public switched telephone network (PSTN), a plain old telephone service (POTS) network, a cellular telephone network, a wireless network, The coupling may be a network, another type of network, or a combination of two or more such networks. For example, the network or a portion of the network may include a wireless network or a cellular network, and the coupling may be a code division multiple access (CDMA) connection, a global system for mobile communications (GSM) connection, or other type of cellular or wireless coupling. In this example, the coupling may implement any of various types of data transmission technologies, such as single carrier radio transmission technology (1xRTT), evolution data optimized (EVDO) technology, general packet radio service (GPRS) technology, enhanced data rate for GSM evolution (EDGE) technology, including the third generation partnership project (3GPP) of 3G, fourth generation wireless (4G) network, universal mobile telecommunications system (UMTS), high speed packet access (HSPA), world wide interoperability for microwave access (WiMAX), long term evolution (LTE) standards, other data transmission technologies defined by various standard setting organizations, other long distance protocols, or other data transmission technologies.

[0089] "Component" refers to a logic, device or physical entity with boundaries defined by function or subroutine calls, branch points, APIs or other technical definitions that provide partitioning or modularization for specific processing or control functions. Components can be combined with other components via their interfaces to perform machine processing. Components can be packaged functional hardware units designed for use with other components, and part of a program that generally performs specific functions in related functions. Components can constitute software components (e.g., codes implemented on machine-readable media) or hardware components. "Hardware components" are tangible units that can perform certain operations and can be configured or arranged in a certain physical manner. In various examples, one or more computer systems (e.g., separate computer systems, client computer systems or server computer systems) or one or more hardware components (e.g., processors or processor groups) of a computer system can be configured by software (e.g., applications or application parts) to operate to perform certain operations described herein. Hardware components can also be implemented mechanically, electronically or in any suitable combination thereof. For example, a hardware component may include a dedicated circuit system or logic that is permanently configured to perform certain operations. The hardware component may be a dedicated processor, such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC). The hardware component may also include a programmable logic or circuit system that is temporarily configured to perform certain operations by software. For example, the hardware component may include software executed by a general-purpose processor or other programmable processor. Once configured by such software, the hardware component becomes a specific machine (or a specific component of a machine) that is uniquely customized to perform the configured function and is no longer a general-purpose processor. It will be recognized that it can be determined for cost and time considerations whether to mechanically implement the hardware component in a dedicated and permanently configured circuit system or in a temporarily configured (e.g., configured by software) circuit system to implement the hardware component. Therefore, the phrase "hardware component" (or "hardware-implemented component") should be understood to include a tangible entity, that is, an entity that is physically constructed, permanently configured (e.g., hardwired) or temporarily configured (e.g., programmed) to operate in some way or perform certain operations described herein. Considering an example where a hardware component is temporarily configured (e.g., programmed), each of the hardware components does not need to be configured or instantiated at any time. For example, in the case where a hardware component includes a general-purpose processor that is configured by software to become a special-purpose processor, the general-purpose processor can be configured as different special-purpose processors (e.g., including different hardware components) at different times. Software accordingly configures one or more specific processors to, for example, constitute a specific hardware component at one time and constitute different hardware components at different times. Hardware components can provide information to other hardware components and receive information from other hardware components. Therefore, the described hardware components can be considered to be communicatively coupled.In the case of multiple hardware components being present at the same time, communication can be achieved by signal transmission (e.g., by appropriate circuits and buses) between or among two or more hardware components in the hardware components. In examples where multiple hardware components are configured or instantiated at different times, communication between such hardware components can be achieved, for example, by storing information in a memory structure accessible to multiple hardware components and retrieving information in the memory structure. For example, a hardware component can perform an operation, and the output of the operation is stored in a memory device coupled to it in communication. Then, other hardware components can access the memory device at a subsequent time to retrieve and process the stored output. The hardware component can also initiate communication with an input device or an output device, and can operate on resources (e.g., a collection of information). The various operations of the example methods described herein can be performed at least in part by a temporary configuration (e.g., by software) or one or more processors that are permanently configured to perform related operations. Whether it is temporarily configured or permanently configured, such a processor can constitute a processor-implemented component that operates to perform one or more operations or functions described herein. As used herein, "processor-implemented components" refer to hardware components implemented using one or more processors. Similarly, the method described herein can be implemented at least in part by a processor, wherein one or more specific processors are examples of hardware. For example, at least some operations in the operation of the method can be performed by one or more processors 1004 or the parts implemented by the processor. In addition, one or more processors can also operate to support the execution of related operations in a "cloud computing" environment or as a "software as a service" (SaaS) operation. For example, at least some operations in the operation can be performed by a computer group (as an example of a machine including a processor), wherein these operations can be accessed via a network (e.g., the Internet) and via one or more appropriate interfaces (e.g., API). The execution of some operations in the operation can be distributed between processors, not only resident in a single machine, but deployed across multiple machines. In some examples, a processor or a part implemented by a processor can be located in a single geographical location (e.g., in a home environment, an office environment, or a server cluster). In other examples, a processor or a part implemented by a processor can be distributed across multiple geographical locations.

[0090] "Computer-readable storage media" refers to both machine storage media and transmission media. Thus, the term includes both storage devices / medium and carrier / modulated data signals. The terms "machine-readable medium," "computer-readable medium," and "device-readable medium" mean the same thing and may be used interchangeably in this disclosure.

[0091] "Ephemeral messages" are messages that are accessible for a limited duration in time. Ephemeral messages can be text, images, videos, etc. The access time for ephemeral messages can be set by the message sender. Alternatively, the access time can be a default setting or a setting specified by the recipient. Regardless of the setting technique, the message is ephemeral.

[0092] "Machine storage media" refers to a single or multiple storage devices and media (e.g., centralized or distributed databases, and associated caches and servers) that store executable instructions, routines, and data. Thus, the term should be considered to include, but is not limited to, solid-state memory and optical and magnetic media, including memory internal or external to the processor. Specific examples of machine storage media, computer storage media, and device storage media include: non-volatile memory, including, for example, semiconductor memory devices, such as erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), FPGA, and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The terms "machine storage media," "device storage media," and "computer storage media" mean the same thing and may be used interchangeably in this disclosure. The terms "machine storage media," "computer storage media," and "device storage media" expressly exclude carrier waves, modulated data signals, and other such media, at least some of which are encompassed by the term "signal media."

[0093] “Non-transitory computer-readable storage medium” refers to a tangible medium capable of storing, encoding, or carrying instructions for execution by a machine.

[0094] "Signal medium" refers to any intangible medium that can store, encode or carry instructions executed by a machine and includes digital or analog communication signals or other intangible media that facilitate the communication of software or data. The term "signal medium" should be deemed to include any form of modulated data signals, carrier waves, etc. The term "modulated data signal" means a signal that has one or more of its characteristics set or changed in such a way as to encode information in the signal. The terms "transmission medium" and "signal medium" mean the same thing and may be used interchangeably in this disclosure.

Claims

1. A method comprising: receiving a set of measurements corresponding to the lengths of ends of eyeglass temples on a pair of eyeglasses; receiving user feedback from a user of the pair of glasses corresponding to the position of the ends of the temples of the glasses; generating a set of predicted measurements for the lengths of the temple ends of the eyeglasses based on the user feedback and the set of measurements; as well as The set of predicted measurements is transmitted to a pneumatic actuator coupled to a distal end of a temple of the eyeglasses.

2. The method according to claim 1, wherein: The set of predicted measurements is generated using a machine learning model trained on historical user data, the historical user data comprising at least one of: eyeglass temple tip length, user facial measurements, and user feedback.

3. The method according to claim 1, further comprising: A first set of images is received from a first camera coupled to the pair of glasses, the first set of images including a first view of the user wearing the pair of glasses.

4. The method according to claim 3, wherein: The set of predicted measurements is also generated based on the first set of images.

5. The method according to claim 3, wherein: The first camera device is a front camera device facing the wearer of the pair of glasses.

6. The method according to claim 3, wherein: The first set of images is captured prior to transmitting the set of predicted measurements to a pair of pneumatic actuators, the method further comprising: receiving a second set of images from the first camera, the second set of images captured after transmitting the set of predicted measurements to the pair of pneumatic actuators; comparing the first set of images to the second set of images; generating a set of adjusted measurements based on the comparison, the set of adjusted measurements comprising adjustments to the set of predicted measurements; and The set of adjustment measurements are communicated to the pneumatic actuator.

7. The method according to claim 1, wherein: The eyeglass temple end is a pair of eyeglass temple ends, and wherein a first eyeglass temple end of the pair of eyeglass temples comprises a first actuator system, and a second eyeglass temple end of the pair of eyeglass temples comprises a second actuator system.

8. The method according to claim 7, wherein: The first actuator system and the second actuator system are physically coupled to an air tank via an air tube.

9. The method according to claim 7, wherein: The first actuator system includes a first pair of pneumatic actuators and the second actuator system includes a second pair of pneumatic actuators.

10. The method according to claim 1, wherein: Transmitting the set of predicted measurements to the pneumatic actuator coupled to the eyeglass temple end causes the pneumatic actuator to expand or retract the eyeglass temple end.

11. A device comprising: A pair of eyeglasses comprising a frame including a pair of lenses, a pair of temples, and a pair of actuated temple tips; a first actuator system coupled to a first actuated temple end of the pair of actuated temple ends; a second actuator system coupled to a second actuated temple end of the pair of actuated temple ends; as well as A camera system is coupled to the frame of the pair of glasses, the camera system comprising a front camera and a rear camera.

12. The device according to claim 11, wherein The first actuator system includes a first pair of pneumatic actuators and the second actuator system includes a second pair of pneumatic actuators.

13. A non-transitory computer-readable storage medium comprising instructions that, when executed by a computer, cause the computer to: receiving a set of measurements corresponding to the lengths of ends of eyeglass temples on a pair of eyeglasses; receiving user feedback from a user of the pair of glasses corresponding to the position of the ends of the temples of the glasses; generating a set of predicted measurements for the lengths of the temple ends of the eyeglasses based on the user feedback and the set of measurements; as well as The set of predicted measurements is transmitted to a pneumatic actuator coupled to a distal end of a temple of the eyeglasses.

14. The computer-readable storage medium of claim 13, wherein: The set of predicted measurements is generated using a machine learning model trained on historical user data, the historical user data comprising at least one of: eyeglass temple tip length, user facial measurements, and user feedback.

15. The computer-readable storage medium of claim 13, wherein: The instructions further configure the computer to: A first set of images is received from a first camera coupled to the pair of glasses, the first set of images including a first view of the user wearing the pair of glasses.

16. The computer-readable storage medium of claim 15, wherein: The set of predicted measurements is also generated based on the first set of images.

17. The computer-readable storage medium of claim 15, wherein: The first camera device is a front camera device facing the user of the pair of glasses.

18. The computer-readable storage medium of claim 15, wherein: The first set of images is captured prior to transmitting the set of predicted measurements to a pair of pneumatic actuators, wherein the instructions further configure the computer to: receiving a second set of images from the first camera, the second set of images captured after transmitting the set of predicted measurements to the pair of pneumatic actuators; comparing the first set of images to the second set of images; generating a set of adjusted measurements based on the comparison, the set of adjusted measurements comprising adjustments to the set of predicted measurements; and The set of adjustment measurements are communicated to the pneumatic actuator.

19. The computer-readable storage medium of claim 13, wherein: The eyeglass temple end is a pair of eyeglass temple ends, and wherein a first eyeglass temple end of the pair of eyeglass temples comprises a first actuator system, and a second eyeglass temple end of the pair of eyeglass temples comprises a second actuator system.

20. The computer-readable storage medium of claim 19, wherein: The first actuator system and the second actuator system are physically coupled to an air tank via an air tube.

Citation Information

Cited By

  • Intelligent actuated nose bridge

    US12313914B2

  • Intelligent actuated temple tips

    US12399382B2

  • Intelligent actuated and adjustable glasses nose pad arms

    US12561824B2