TW202331469A - Smart rejection of false solid-state button presses on smart glasses - Google Patents

Abstract

A method, for detecting a press button action in a headset and assessing the user intention thereof is provided. The method includes receiving a force data from a force sensor in a headset, a capacitive data from a capacitive sensor in the headset, an inertial data from an inertial sensor in the headset, and a location data from a face sensor in the headset; combining the force data, the capacitive data, the inertial data, and the location data to assess a user intention; and determining whether to accept or reject a button press action on the headset based on the user intention. A headset including a memory storing instructions to cause a processor to cause the headset to perform the above method are also provided.

Description

Smart rejection of wrong solid state button presses on smart glasses

The present invention generally relates to the control and evaluation of user input for smart glasses for mixed reality applications. More particularly, the present invention relates to sensors and methods for assessing user intent when pressing buttons in smart glasses for mixed reality applications. Cross References to Related Applications

This invention relates to U.S. Provisional Patent Application No. 63/287,944 filed December 9, 2021 and U.S. Nonprovisional Patent Application No. 18/052,717 filed November 4, 2022 by Kai T. McKernney et al. Its title is SMART REJECTION OF FALSE SOLID-STATE BUTTON PRESSES ON SMART GLASSES, and asserts its priority under 35 U.S.C. §119(e), for all purposes The contents of these applications are hereby incorporated by reference in their entirety.

Smart glasses for mixed reality applications include a plurality of buttons and hot spots that work as a user interface to receive input from the user. However, when the user unintentionally presses a button in the headset, it is very inconvenient for the user to trigger unnecessary actions in the headset, causing the user to scramble to undo settings, configurations, and the like. unnecessary changes.

In a first embodiment, a computer-implemented method includes receiving force data from a force sensor in a headset, capacitance data from a capacitive sensor in the headset, an inertial data from an inertial sensor in the headset and a positional data from a face sensor in the headset; combining the force data, the capacitance data, the inertial data and the positional data to evaluate a user intention; and determine whether to accept or reject a button press action of the head-mounted device based on the user intention.

In a second embodiment, a system includes one or more processors and memory configured to store instructions. The instructions, when executed by the one or more processors, cause the system to: receive force data from a force sensor in a headset, from a capacitive sensor in the headset Capacitance data from the headset, inertial data from an inertial sensor in the headset, and position data from a face sensor in the headset; combining the force data, the capacitance data, the Inertial data and the location data are used to evaluate a user intent; and to determine whether to accept or reject a button press action of the headset based on the user intent.

In a third embodiment, a computer-implemented method includes: receiving force data, capacitance data, inertial data, and position data from a head-mounted device; Correlating at least two of them to look for a resonance event; identifying a user intent for the headset based on the resonance event; and determining whether to accept or reject a button press on the headset based on the user intent.

In a fourth embodiment, a system includes first means for storing instructions and second means for executing the instructions to cause the system to perform a method. The method includes: receiving force data from a force sensor in a headset, capacitance data from a capacitive sensor in the headset, an inertial sensor in the headset an inertial data from a sensor and a positional data from a face sensor in the headset; combining the force data, the capacitance data, the inertial data and the positional data to evaluate a user intent; and based on the The user intends to determine whether to accept or reject a button press on the headset.

In another embodiment, a non-transitory computer-readable memory stores instructions that, when executed by one or more processors, cause a computer to perform a method. The method includes: receiving force data from a force sensor in a headset, capacitance data from a capacitive sensor in the headset, an inertial sensor in the headset an inertial data from a sensor and a positional data from a face sensor in the headset; combining the force data, the capacitance data, the inertial data and the positional data to evaluate a user intent; and based on the The user intends to determine whether to accept or reject a button press on the headset.

These and other specific examples will become apparent from this disclosure.

The implementations set forth below describe various configurations of the present technology and are not intended to represent the only configurations in which the present technology may be practiced. The embodiments include specific details for the purpose of providing a thorough understanding of the present technology. Accordingly, dimensions may be provided with respect to certain aspects as non-limiting examples. It will be apparent, however, to one of ordinary skill in the art, that the present technique may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form in order to avoid obscuring the concepts of the present technology.

It should be understood that the present invention includes examples of the technology of the present invention and does not limit the scope of the included claims. Various aspects of the present technology will now be disclosed according to specific but non-limiting examples. The various embodiments described in this disclosure can be carried out in different ways and variations and depending on the desired application or implementation.

In the following embodiments, numerous specific details are set forth in order to provide a thorough understanding of the present invention. It will be apparent, however, to one of ordinary skill in the art that specific examples of the invention may be practiced without some of the specific details. In other instances, well-known structures and techniques have not been shown in detail so as not to obscure the disclosure.

By way of example, the present technology is illustrated in terms of various aspects described below. Various examples of aspects of the inventive technology are described as numbered claims (claims 1, 2, etc.) for convenience. These claims are provided as examples and do not limit the inventive technology. general notes

In order to achieve reliable solid state buttons (eg, no physical tactile switches), it is necessary to distinguish an intentional button press from many other signals/phenomena that may appear to a single sensor as a button press. As the user adjusts the frame on his face, the primary force sensor can interpret the flexing of the smart glasses arm as a button press. Also, only capacitive touch sensors can interpret wet hair or a passing finger as a button press.

Aspects of the invention are directed at combining information from various sensors to narrow the definition of a successful solid-state button press to only pressing a certain force directly on the button feature on the smart glasses, and rejecting all others in and near the area Methods of pressing, flexing, and other phenomena.

Depending on the aspect, the smart glasses will combine information from a series of sensors (e.g., strain gauges/force sensors, capacitive touch, inertial measurement unit (IMU), capacitive face detection) to Accurately accept and reject action button presses.

According to an aspect, a strain gauge/force sensor can define an amount of force that can be applied at the button location, helping to reject light inputs like passing fingers and hair.

According to aspects, the capacitive touch area directly under the button feature can ensure that the finger is on the button feature and resists flexing or pressing by other arms near the button feature that may still exert the required force on the force sensor.

According to aspects, the IMU helps to correlate intentional button presses with expected motion of the glasses when the user presses the button to reject other accidental presses.

According to aspects, capacitive face detection sensors help determine whether the glasses are on the user's face, and thus prevent button presses when the user holds the glasses in their hands (and not on their face).

Exemplary scenarios include:

The user extends a finger and presses/squeezes the button area. The system detects this as a successful button press and reacts accordingly.

The user adjusts the glasses on their face - this creates a force on the glasses near the button area, not directly on the button area. The force sensor detects this as a button press, but the capacitive touch signal does not indicate that the finger is directly on the button feature, and therefore the event is not detected as a button press.

The user collides with another person while exercising. Another person's arm or hand contacts the user's smart glasses during the collision. This occurs to generate signals at force sensors like button presses and capacitive touch sensors. The activity seen by the IMU does not indicate a normal button press, and therefore the event is not detected as a button press.

The user squeezes the button area while holding the glasses in his hand and is ready to put on the glasses. Signals at force sensors (eg, force sensor pre-sense), touch sensors, and IMU are similar to normal button presses. A face detection sensor (eg, a face detection/over head detection sensor) detects that the glasses are not currently on the user's face, and thus the event is not detected as a button press. Exemplary network architecture

1 illustrates an architecture 10 that includes a user 101 wearing a headset 100 (eg, smart glasses or VR/AR goggles) that communicates via a network 150 with a mobile device 110, remote The server 130 is coupled to the database 152 . The mobile device 110 can be a smart phone, and can communicate with the smart glasses 100 via wireless communication to exchange the first data set 103-1. In some specific examples, the mobile device 110 can also belong to the user 101 . Data set 103-1 may include recorded video, audio, or some other file or streaming medium. The mobile device 110 can be communicatively coupled with the remote server 130 and the database 152 via the network 150, and can transmit/share information, files, and the like (eg, the dataset 103-2 and the dataset 103-3) with each other. Headset 100 may include button 127 configured to receive input from user 101 (eg, via a pressing motion with a finger).

In some embodiments, the head-mounted device 100 may include a plurality of sensors 121 - 1 , 121 - 2 and 121 - 3 (collectively referred to as “sensors 121 hereinafter”). The sensors 121 may include an inertial measurement unit (IMU), a gyroscope, a microphone, a camera, and the like mounted within the frame of the head mounted device 100 . Other sensors 121 that may be included in the headset 100 may include magnetometers, contact microphones, optical devices such as photodiodes and cameras, touch sensors, pressure sensors, force sensors, and other electromagnetic sensors. devices such as capacitive sensors, pressure sensors, and the like. Sensors 121 may include face sensor 121-3, which may be positioned on the frame of headset 100 such that its signal is indicative of the position of headset 100 (e.g., resting on or away from user 101's face). face) capacitive sensor. The sensor 121 may also include an acoustic microphone and/or a contact microphone. Acoustic microphones receive airborne acoustic signals as pressure waves. Contact microphones may be mechanically coupled to the user's skin and bones, such as in the nose pad or arms of the headset 100, in contact with the user's temples, and the like. The data set 103-1 may include force data, capacitance data, inertial data, and position data transmitted from the head mounted device 100 to the mobile device 110 and/or the remote server 130 for processing.

Additionally, headset 100 or mobile device 110 may include memory circuitry 120 storing instructions and configured to execute the instructions such that headset 100 at least partially performs some of the steps in a method consistent with the present invention. processor circuit 112 . In some embodiments, the memory circuit 120 may include instructions for executing an immersive reality application hosted by the remote server 130 . Therefore, the processor 112 in the headset 100 or one or more processors in the mobile device 110 or in the remote server 130 can use force data, capacitance data, inertial data, and position data to evaluate the pressure on the headset 100. The user intent of the button 127.

Input from the user 101 after pressing the button 127 may be associated with a specific action in the headset 100, such as "wake up", or "turn on/off the camera" (e.g., the camera 123 mounted on the headset 100) . In some embodiments, the input from the user 101 may include actions within an immersive application running on the headset 100 .

In some embodiments, the headset 100 may further include a communication module 118 , which enables the device to communicate wirelessly with the mobile device 110 , with the remote server 130 and/or the database 152 via the network 150 . In some embodiments, the communication module 118 may include, for example, radio frequency hardware (eg, antennas, filters, analog-to-digital converters, and the like) and software (eg, signal processing software). The headset 100 may thus download multimedia online content (eg, data set 103 - 1 ) from the remote server 130 to at least partially perform some of the operations in the methods disclosed herein. The network 150 may include, for example, any one or more of an area network (local area network; LAN), a wide area network (wide area network; WAN), the Internet, and the like. Additionally, a network may include, but is not limited to, any one or more of the following network topologies, including bus, star, ring, mesh, star-bus, tree Or hierarchical networks and the like.

2 is a flowchart illustrating steps in a method 200 for accepting or rejecting button presses in a headset running an immersive reality application, according to some embodiments. In some embodiments, the method 200 may be at least partially executed in a head-mounted device, a mobile device or a remote server as disclosed herein (see head-mounted device 100 , mobile device 110 and remote server 130 ). Accordingly, at least one or more steps in method 200 may be executed by a processing circuit or a communication module as disclosed herein (see processing circuit 112, memory circuit 120, and communication module 118) executing instructions stored in a memory circuit. implement. Additionally, in some embodiments, method 200 may include deriving from any of a force sensor, a capacitive sensor, an inertial sensor, or a face sensor in the headset (eg, sensor 121 ). Collect, receive and transmit sensor data. In some embodiments, methods consistent with this disclosure may include performing any of the steps in method 200 in a different order, simultaneously, semi-simultaneously, or overlapping in time.

Step 202 includes receiving force data from force sensors in the headset, capacitance data from capacitive sensors in the headset, inertial data from inertial sensors in the headset, and Location data of the face sensor in the device.

Step 204 includes combining force data, capacitance data, inertial data, and position data to assess user intent. In some embodiments, the capacitance data indicates the presence of the user's finger, the force data indicates the button press action, and step 204 may include evaluating the user's intent to perform the button press action. In some embodiments, the inertial data indicates that the movement of the headset coincides with the button press, the force data indicates the button press, and step 204 includes evaluating the user's intent to perform the button press. In some embodiments, the face sensor is a capacitive sensor and the location data indicates the presence of the headset on the user's face, and step 204 includes evaluating the user's intention to perform a button press action. In some embodiments, the force data and capacitance data are indicative of a button press, the inertial data are indicative of an involuntary collision of the user with an obstacle, and step 204 includes evaluating the user's intent not to perform the button press.

Step 206 includes determining whether to accept or reject the button press action on the headset based on the user's intention. In some embodiments, the headset is configured to run an immersive reality application hosted by a remote server, and step 206 includes performing an action in the immersive reality application when the button press action is accepted , stopping the immersive reality application when the location data indicates that the headset is not over the user's face, or stopping the immersive reality application when the inertial data indicates free fall of the headset. In some embodiments, the force sensor is a strain gauge, and step 206 includes identifying the force data as a passing finger or hair touch, and discarding the force data to assess user intent. In some embodiments, step 206 includes evaluating the user's intention not to perform the button pressing action when the location data indicates that the headset is not in contact with the user's face.

3 is a flowchart illustrating steps in a method 300 for evaluating user intent to accept a button press in a headset running an immersive reality application, according to some embodiments. In some embodiments, the method 300 may be at least partially executed in a head-mounted device, a mobile device or a remote server as disclosed herein (see head-mounted device 100 , mobile device 110 and remote server 130 ). Accordingly, at least one or more steps in method 300 may be executed by a processing circuit or a communication module as disclosed herein (see processing circuit 112, memory circuit 120, and communication module 118) executing instructions stored in memory circuits. implement. Additionally, in some embodiments, the method 300 may include deriving from any of a force sensor, a capacitive sensor, an inertial sensor, or a face sensor in the headset (eg, sensor 121 ). Collect, receive and transmit sensor data. In some embodiments, methods consistent with this disclosure may include any of the steps in method 300 being performed in a different order, simultaneously, semi-simultaneously, or overlapping in time.

Step 302 includes receiving force data, capacitance data, inertial data, and position data from the headset.

Step 304 includes correlating at least two of force data, capacitance data, and inertial data to find resonance events.

Step 306 includes identifying user intent for the headset based on the resonance event.

Step 308 includes determining whether to accept or reject the button press action of the headset based on the user's intention.

In one aspect, a method can be an operation, instruction or function and vice versa. In one aspect, a claim may be modified to include one or more claim terms, one or more word groups, one or more sentences, one or more phrases, one or more paragraphs, and/or Some or all of the words (eg, instructions, operations, functions, or components) recited in one or more claim items. hardware overview

4 is a block diagram illustrating a computer system for implementing a headset and methods of use thereof, according to some embodiments. In some aspects, computer system 400 may be implemented using hardware, or a combination of software and hardware, in a dedicated server, integrated into another entity, or distributed across multiple entities. The computer system 400 may include a desktop computer, a laptop computer, a tablet computer, a phablet phone, a smart phone, a feature phone, a server computer, or others. Server computers can be located remotely in a data center or stored locally.

Computer system 400 includes a bus 408 or other communication mechanism for communicating information, and a processor 402 (eg, processor 112 ) coupled with bus 408 for processing information. By way of example, computer system 400 may be implemented by one or more processors 402 . The processor 402 can be a general-purpose microprocessor, a microcontroller, a digital signal processor (Digital Signal Processor; DSP), a special application integrated circuit (Application Specific Integrated Circuit; ASIC), a field programmable gate array (Field Programmable Gate Array; FPGA), Programmable Logic Device (PLD), controller, state machine, gating logic, discrete hardware component, or any other suitable entity that can perform calculations or other manipulations of information.

In addition to hardware, computer system 400 may also include code that creates an execution environment for the computer program in question, for example, making up processor firmware, a protocol stack, a database management system, an operating system, or stored in included memory 404 ( For example, the program code of a combination of one or more of the foregoing in the memory 120), including memory such as random access memory (Random Access Memory; RAM), flash memory, read-only memory (Read-Only Memory; ROM), Programmable Read-Only Memory (Programmable Read-Only Memory; PROM), Erasable PROM (Erasable PROM; EPROM), scratchpad, hard disk, removable disk, CD - ROM, DVD, or any other suitable storage device coupled to bus 408 for storing information and instructions to be executed by processor 402. Processor 402 and memory 404 may be supplemented by or incorporated in special purpose logic circuitry.

Instructions may be stored in memory 404, and one or more computer programs of one or more modules of computer program instructions encoded, for example, on a computer readable medium according to any method known to those of ordinary skill in the art Implemented in the product for the computer system 400 to execute or control the operation of the computer system, such instructions include but are not limited to computer languages such as: data-oriented languages (such as SQL, dBase), system languages (such as C, Objective- C, C++, Assembly), architectural languages (eg, Java, .NET), and application languages (eg, PHP, Ruby, Perl, Python). Instructions can also be implemented in computer languages such as array languages, feature-oriented languages, assembly languages, production languages, command-line interface languages, compiled languages, parallel languages, curly bracket languages, dataflow languages, data-structured languages, declarative languages, esoteric language, extended language, fourth-generation language, functional language, interactive pattern language, interpreted language, iterative language, list-based language, small language, logic-based language, machine language, macro language, metaprogramming language , multiparadigm language (multiparadigm language), numerical analysis, non-English language, object-oriented taxonomic language, object-oriented prototype-based language, off-site rule language, procedural language, reflection language, rule-based language, script processing language, stack-based languages, synchronous languages, syntactically processed languages, visual languages, wirth languages, and xml-based languages. Memory 404 may also be used to store temporary variables or other intermediate information during execution of instructions to be executed by processor 402 .

Computer programs as discussed herein do not necessarily correspond to files in a file system. A program may be stored in a section of a file that holds other programs or data (for example, one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple In a coordinated file (for example, a file that stores one or more modules, subroutines, or portions of code). A computer program can be deployed to be executed on one computer or on multiple computers that are located at one site or distributed across multiple sites and interconnected by a communication network. The processes and logic flows described in this specification can be performed by one or more programmable processors executing one or more computer programs to operate on input data and generate output to perform the function.

Computer system 400 further includes a data storage device 406, such as a magnetic or optical disk, coupled to bus 408 for storing information and instructions. The computer system 400 can be coupled to various devices via the input/output module 410 . The I/O module 410 can be any I/O module. Exemplary input/output modules 410 include data ports such as USB ports. The input/output module 410 is configured to connect to the communication module 412 . Exemplary communication modules 412 include network connection interface cards, such as Ethernet cards and modems. In some aspects, input/output module 410 is configured to connect to a plurality of devices, such as input device 414 and/or output device 416 . Exemplary input devices 414 include a keyboard and pointing devices, such as a mouse or trackball, by which a consumer can provide input to computer system 400 . Other types of input devices 414 may also be used to provide interaction with consumers, such as tactile input devices, visual input devices, audio input devices, or brain-computer interface devices. For example, the feedback provided to the consumer can be any form of sensory feedback, such as visual feedback, auditory feedback, or tactile feedback; and any form of input can be received from the consumer, including acoustic input, voice input, tactile input, or Brainwave input. Exemplary output devices 416 include display devices, such as liquid crystal display (LCD) monitors, for displaying information to a consumer.

According to an aspect of the present disclosure, smart glasses 100 may be at least partially implemented using computer system 400 in response to processor 402 executing one or more sequences of one or more instructions contained in memory 404 . Such instructions may be read into memory 404 from another machine-readable medium, such as data storage device 406 . Execution of the sequences of instructions contained in main memory 404 causes processor 402 to perform the process steps described herein. One or more processors in a multi-processing configuration may also be employed to execute the sequences of instructions contained in memory 404 . In alternative aspects, hard-wired circuitry may be used in place of or in combination with software instructions to implement various aspects of the invention. Thus, aspects of the invention are not limited to any specific combination of hardware circuitry and software.

Various aspects of the subject matter described in this specification can be implemented in computing systems that include back-end components, such as data servers, or that include intermediate software components, such as application servers, or that include front-end components, such as with A client computer through which a consumer may interact with an implementation of the subject matter described in this specification through a graphical consumer interface or web browser, or any combination of one or more such back-end components, middleware components, or front-end components . The components of the system can be interconnected by any form or medium of digital data communication (eg, a communication network). A communication network (eg, network 150 ) may include, for example, any one or more of a LAN, WAN, the Internet, and the like. In addition, the communication network may include, but is not limited to, any one or more of the following network topologies, including bus network, star network, ring network, mesh network, star bus network , tree or hierarchical network or similar. The communication module can be, for example, a modem or an Ethernet card.

The computer system 400 may include a client and a server. A client and server are generally remote from each other and usually interact through a communication network. The relationship between client and server arises by means of computer programs running on the respective computers and having a master-slave relationship with each other. Computer system 400 may be, for example but not limited to, a desktop computer, a laptop computer, or a tablet computer. The computer system 400 may also be embedded in another device, such as but not limited to a mobile phone, PDA, mobile audio player, Global Positioning System (GPS) receiver, video game console, and/or television set-top box .

The term "machine-readable storage medium" or "computer-readable medium" as used herein refers to any one or more media that participates in providing instructions to processor 402 for execution. This medium can take many forms, including but not limited to, non-volatile media, volatile media, and transmission media. Non-volatile media include, for example, optical or magnetic disks, such as data storage device 406 . Volatile media includes dynamic memory, such as memory 404 . Transmission media includes coaxial cables, copper wire and fiber optics, including the wires forming bus 408 . Common forms of machine-readable media include, for example, floppy disks, floppy disks, hard disks, magnetic tape, any other magnetic media, CD-ROMs, DVDs, any other optical media, punched cards, paper tape, any Other physical media, RAM, PROM, EPROM, FLASH EPROM, any other memory chips or cartridges, or any other media that can be read by a computer. The machine-readable storage medium can be a machine-readable storage device, a machine-readable storage substrate, a memory device, a composition of matter affecting a machine-readable propagating signal, or a combination of one or more of them.

Many of the features and applications described above can be implemented as instructions intended to be recorded on a computer-readable storage medium (alternatively referred to as a computer-readable medium, a machine-readable medium, or a machine-readable storage medium) Set of software processing. These instructions, when executed by one or more processing units (eg, one or more processors, processor cores, or other processing units), cause the processing units to perform the actions indicated in the instructions. Examples of computer-readable media include, but are not limited to, RAM, ROM, compact disc read-only (CD-ROM), compact disc recordable (CD-R), compact disc rewritable (CD-RW), digital audio-visual read-only Optical discs (e.g., DVD-ROM, dual-layer DVD-ROM), various recordable/rewritable DVDs (e.g., DVD-RAM, DVD-RW, DVD+RW, etc.), flash memory (e.g., SD card , mini SD card, micro SD card, etc.), magnetic and/or solid state drives, ultra-density optical discs, any other optical or magnetic media, and floppy disks. In one or more embodiments, a computer-readable medium excludes carrier waves and electronic signals transmitted wirelessly or via a wired connection or any other transitory signal. For example, a computer-readable medium may be limited entirely to tangible, physical objects that store information in a form that can be read by a computer. In one or more embodiments, the computer readable medium is a non-transitory computer readable medium, a computer readable storage medium, or a non-transitory computer readable storage medium.

In one or more embodiments, a computer program product (also known as a program, software, software application, script code, or code) can be written in any programming language, including compiled or interpreted languages, declarative or programming language and which may be deployed in any form, including as a stand-alone program or as a module, component, subroutine, object or other unit suitable for use in a computing environment. A computer program may, but need not, correspond to a file in a file system. A program may be stored in part of a file that holds other programs or data (for example, one or more scripts stored in a markup language file), in a single file dedicated to the program in question, or in multiple in a reconciled file (for example, a file that stores one or more modules, subroutines, or portions of code). A computer program can be deployed to be executed on one computer or on multiple computers that are located at one site or distributed across multiple sites and interconnected by a communication network.

Although the above discussion primarily refers to microprocessors or multi-core processors that execute software, one or more specific instances are implemented by one or multiple integrated circuits to perform. In one or more embodiments, these integrated circuits execute instructions stored on the circuits themselves.

Those of ordinary skill in the art will appreciate that the various illustrative blocks, modules, elements, components, methods and algorithms described herein may be implemented as electronic hardware, computer software, or a combination of both. To illustrate this interchangeability of hardware and software, various illustrative blocks, modules, elements, components, methods, and algorithms have been described above generally in terms of their functionality. Whether to implement such functionality as hardware or software depends upon the particular application and design constraints imposed on the overall system. Those skilled in the art may implement the described functionality in varying ways for each particular application. Various components and blocks can be arranged in different ways (for example, arranged in different orders, or divided in different ways), all without departing from the technical scope of the present invention.

It is understood that any specific order or hierarchy of blocks in the disclosed programs is an illustration of the sample approach. Based upon implementation preference, it is understood that the specific order or hierarchy of blocks in the program may be rearranged, or not all illustrated blocks implemented. Any of these blocks may be executed concurrently. In one or more embodiments, multitasking and parallel processing can be advantageous. Furthermore, the separation of various system components in the embodiments described above should not be construed as requiring such separation in all embodiments, and it should be understood that the described program components and systems may generally be integrated together in a single software product or packaged to multiple software products.

For example, the present technology is illustrated according to various aspects described above. The present invention is provided to enable any person of ordinary skill in the art to practice the various aspects described herein. This disclosure provides various examples of the inventive technology, and the inventive technology is not limited to these examples. Various modifications to these aspects will be readily apparent to those of ordinary skill in the art, and the generic principles defined herein may be applied to other aspects.

Reference to an element in the singular is not intended to mean "one and only one" unless specifically so stated, but rather "one or more". Unless specifically stated otherwise, the term "some" refers to one or more. A masculine pronoun (eg, his) includes the feminine and neuter genders (eg, her and its) and vice versa. Headings and subheadings, if present, are used for convenience only and do not limit the invention.

The word "exemplary" is used herein to mean "serving as an example or illustration". Any aspect or design described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other aspects or designs. In one aspect, the various alternative configurations and operations described herein may be considered at least equivalent.

As used herein, the phrase "at least one of" preceding a list of items by separating any of those items with the term "or" modifies the list as a whole and not the individual items in the list. The phrase "at least one of" does not require selection of at least one of the items; rather, the phrase allows the inclusion of at least one of any of those items and/or at least one of any combination of those items or and/or at least one of each of these items. By way of example, the phrase "at least one of A, B, or C" may refer to: only A, only B, or only C; or any combination of A, B, and C.

Phrases such as "aspects" do not imply that such aspects are essential to the present technology or that such aspects apply to all configurations of the present technology. A disclosure related to an aspect may apply to all configurations or to one or more configurations. Aspects may provide one or more instances. A phrase such as an aspect may refer to one or more aspects and vice versa. Phrases such as "an embodiment" do not imply that such embodiments are essential to the present technology or that such embodiments are applicable to all configurations of the present technology. A disclosure related to an embodiment may apply to all embodiments or to one or more embodiments. Specific examples may provide one or more examples. A phrase such as an embodiment may refer to one or more embodiments and vice versa. Phrases such as "configuration" do not imply that such configurations are essential to the present technology or that such configurations apply to all configurations of the present technology. A disclosure related to such configurations may apply to all configurations or one or more configurations. A configuration may provide one or more instances. A phrase of such a configuration may refer to one or more configurations and vice versa.

In one aspect, unless otherwise stated, all measurements, values, ratings, positions, magnitudes, sizes and other specifications stated in this specification (including in the claims that follow) are approximate and imprecise. In one aspect, it is intended to have a reasonable range consistent with its relevant function and usage in the art to which it pertains.

It should be understood that some or all of the steps, operations or procedures may be performed automatically without user intervention. The method claims may be presented to present elements of the various steps, operations, or procedures in a sample order, and are not meant to be limited to the specific order or hierarchy presented.

All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be used by all. Including patent application coverage. Furthermore, nothing disclosed herein is intended to be dedicated to the public, whether or not such disclosure is explicitly recited in the claims. A claimed element should not be construed under 35 U.S.C. §112 (f) unless the element is expressly described using the phrase "means for" or, in the case of a method, the element is a Described in terms of "steps for...". Furthermore, to the extent that the term "includes," "has," or the like is used, such term is intended to be inclusive in a manner similar to how the term "comprises" is interpreted when "comprises" is used as a transition word in a claim of.

The title, background and drawings of the present disclosure are hereby incorporated into the present disclosure and provided as illustrative examples rather than limiting descriptions of the present disclosure. It is with the understanding that it will not be used to limit the scope or meaning of claims. In addition, in the embodiments, it can be seen that this specification provides illustrative examples and groups various features together in various specific examples for the purpose of streamlining the disclosure. This method of disclosure should not be interpreted as reflecting an intention that covered subject matter requires more features than are expressly recited in any claim. Rather, as the claims reflect, inventive subject matter lies in less than all features of a single disclosed configuration or operation. The patent claims are hereby incorporated into the Detailed Description, with each claim in its own right representing separately patentable subject matter.

Claims are not intended to be limited to the aspects described herein, but are to be accorded the full scope consistent with the language of the claims and encompass all legal equivalents. Nonetheless, nothing claimed to be patentable is intended to cover subject matter that fails to satisfy the requirements of the patent laws, nor should it be construed in this manner.

10: Architecture 100: Headsets/Smart Glasses 101: user 103-1: Data sets 103-2: Data sets 103-3: Data sets 110:Mobile device 112: Processor 118: Communication module 120: Memory circuit 121: sensor 121-1: Sensor 121-2: Sensor 121-3: Sensor 123: camera 127: button 130: remote server 150: Network 152: Database 200: method 202: Step 204: step 206: Step 300: method 302: Step 304: step 306: Step 308: Step 400: Computer system 402: Processor 404: memory 406: data storage device 408: Bus 410: Input/Output Module 412:Communication module 414: input device 416: output device

[FIG. 1] illustrates a network architecture including a headset running an immersive reality application hosted by a remote server according to some embodiments. [ FIG. 2 ] is a flowchart illustrating steps in a method for accepting or rejecting button presses in a headset running an immersive reality application, according to some embodiments. [ FIG. 3 ] is a flowchart illustrating steps in a method for evaluating user intent to accept a button press in a headset running an immersive reality application, according to some embodiments. [ FIG. 4 ] is a block diagram of a system in the architecture of FIG. 1 configured to at least partially perform one or more of the steps in the methods of FIGS. 2 and 3 , according to some embodiments.

In the figures, elements with the same or similar reference numbers are associated with the same or similar properties and features, unless explicitly stated otherwise.

200: method

202: Step

204: step

206: Step

Claims (20)

A computer-implemented method comprising: Receive force data from force sensors in the headset, capacitance data from capacitive sensors in the headset, inertial data from inertial sensors in the headset, and Location data of the face sensor in the device; combining the force data, the capacitance data, the inertial data, and the position data to assess user intent; and It is determined whether to accept or reject the button pressing action of the headset based on the user intention. The computer-implemented method of claim 1, wherein the head-mounted device is configured to run an immersive reality application hosted by a remote server, and the computer-implemented method further includes when the button press action is accepted Perform actions in this immersive reality application. The computer-implemented method of claim 1, wherein the head-mounted device is configured to run an immersive reality application hosted by a remote server, and the computer-implemented method further includes indicating the head-mounted device in the location data Stops the immersive reality application when not on the user's face. The computer-implemented method of claim 1, wherein the head-mounted device is configured to run an immersive reality application hosted by a remote server, and the computer-implemented method further comprises when the inertial data indicates the head-mounted device Stop the immersive reality application during free fall. The computer-implemented method of claim 1, wherein the force sensor is a strain gauge, and the computer-implemented method further comprises identifying the force data as a passing finger or hair touch, and discarding the force data to assess the user's intent . The computer-implemented method of claim 1, wherein the capacitance data indicates the presence of a user's finger, and the force data indicates the button press, and combining the force data and the capacitance data includes evaluating the user's intent to perform the button press action. The computer-implemented method of claim 1, wherein the inertial data indicates movement of the headset coincident with the button press, and the force data indicates the button press, and combining the force data and the inertial data includes evaluating the use of or intended to perform the button press action. The computer-implemented method of claim 1, wherein the face sensor is a capacitive sensor, and the location data indicates the presence of the headset on the user's face, and combining the force data and the capacitance data includes evaluating The user intends to perform the button press action. The computer-implemented method of claim 1, wherein combining the force data and the position data includes evaluating the user's intention not to perform the button press action when the position data indicates that the headset is not in contact with the user's face. The computer-implemented method of claim 1, wherein the force data and the capacitance data are indicative of the button press action, and the inertial data is indicative of an involuntary collision of the user with an obstacle, and combining the force data and the capacitance data includes evaluating the use of Or the intention is not to perform the button press action. A system comprising: one or more processors; and memory configured to store instructions that, when executed by the one or more processors, cause the system to: Receive force data from force sensors in the headset, capacitance data from capacitive sensors in the headset, inertial data from inertial sensors in the headset, and Location data of the face sensor in the device; combining the force data, the capacitance data, the inertial data, and the position data to assess user intent; and Determine whether to accept or reject the button pressing action of the headset based on the user intention. The system of claim 11, wherein the headset is configured to run an immersive reality application hosted by a remote server, and when the button press is accepted in the immersive reality application Perform an action. The system of claim 11, wherein the headset is configured to run an immersive reality application hosted by a remote server and stop when the location data indicates that the headset is not over the user's face The immersive reality app. The system of claim 11, wherein the headset is configured to run an immersive reality application hosted by a remote server, and the immersion is stopped when the inertial data indicates free fall of the headset Real-world applications. The system of claim 11, wherein the force sensor is a strain gauge, and the one or more processors further execute instructions to identify the force data as a passing finger or hair touch, and discard the force data to evaluate the user intent. A computer-implemented method comprising: Receive force data, capacitance data, inertia data and position data from the headset; correlating at least two of the force data, the capacitance data, and the inertial data to find resonance events; identifying user intent for the headset based on the resonance event; and Determine whether to accept or reject the button pressing action of the headset based on the user intention. The computer-implemented method of claim 16, wherein the head-mounted device is configured to run an immersive reality application hosted by a remote server, and the computer-implemented method further comprises when the button press action is accepted Perform actions in this immersive reality application. The computer-implemented method of claim 16, wherein the head-mounted device is configured to run an immersive reality application hosted by a remote server, and the computer-implemented method further comprises indicating the head-mounted device in the location data Stops the immersive reality application when not on the user's face. The computer-implemented method of claim 16, wherein the head-mounted device is configured to run an immersive reality application hosted by a remote server, and the computer-implemented method further comprises when the inertial data indicates the head-mounted device Stop the immersive reality application during free fall. The computer-implemented method of claim 16, wherein the force data and the capacitance data are indicative of the button press action, and the inertial data is indicative of an involuntary collision of the user with an obstacle, and combining the force data and the capacitance data includes evaluating the use of Or the intention is not to perform the button press action.