KR100524134B1 - Method and apparatus for controlling electronic device according to detected condition - Google Patents

Abstract

A system 200 is disclosed that senses physical characteristics of an electronic device 214. System 200 controls electronic device 214 in response to the sensed physical characteristics. This system 200 includes a control subsystem. This control subsystem includes a time trigger 206 and an expected / latency reduction subsystem 207. Prediction / latency reduction subsystem 207 includes additional subsystems such as time trigger 206, position trigger 208, and attitude trigger 209. Various triggers can be implemented using a processor running software. The control subsystem receives signals from the sensing devices 204 and 205. Physical property information obtained from this signal is provided to various triggers 206, 208, 209, 211, 212, 213. In response to this physical characteristic information, various triggers 206, 208, 209, 211, 212, 213 process the physical characteristic information, such that system 200 controls electronic device 214.

Description

Method and apparatus for controlling an electrical device in accordance with a detected condition

Related Applications

This application is a patent application entitled "User Operation Expectation System and Method for Improving Performance of Electrical Device" and a patent application filed on May 22, 1996 (inventors John Ellenby, Peter Malcolm Ellenby and Thomas William Ellenby). It claims the priority of 60 / 018,405, which is incorporated herein by reference.

The present invention relates to a method and apparatus for improving the performance of an electrical device, and more particularly to a method and apparatus for sensing various conditions and controlling the electrical device according to the sensed conditions.

Electronic devices are typically designed to accomplish certain functions. From the moment it is turned on, the electronic device is fully functional to complete the task designed for it. This works well for simple devices. However, for complex systems this approach can present disadvantages. For example, a complex system can consume a relatively large amount of power. If a complex system is always fully functional, power consumption is typically kept high even when the system is not actually used. This relatively high power consumption is a significant problem for battery-powered systems, which results in shorter operating life at higher power consumption.

Another feature of conventional electronic devices is that they have several modes of operation and are designed to initiate operation in one of these modes of operation when turned on. Such a device can only switch modes in response to physical interaction with the user, for example by pressing a predetermined button. This design works well for simple devices. However, in a complex system, switching from one mode of operation to another can take a relatively long time. In addition, it may be inconvenient for the user to manually switch the system between the plurality of modes. If a complex system is started to operate in one mode at all times when it is turned on, or if it is designed to switch to another mode only when manually selected, then the length of that transition time and the user's ability to let the system initiate the transition. The time required can hinder the performance of the electronic system.

Accordingly, what is needed is a method and apparatus for extending the battery life of an electrical device by enabling the device to power up or power down its components at an appropriate timing. There is also a need for a method and apparatus that reduces the waiting time (i.e., delay time) between the time that a user determines which mode the device will operate in and the actual mode switch. The wait time also refers to the wait time between the time when the user decides to turn on or turn off the device and the actual switching on or off of the device.

These and other features and advantages of the present invention will become apparent to those skilled in the art from the following detailed description, which is set forth in conjunction with the accompanying drawings.

1 illustrates a system 100 that is one embodiment of the present invention.

2 illustrates a system 200 that is an alternative embodiment of the present invention.

3 illustrates a main flow diagram of the operation of system 100.

4 illustrates a main flow diagram of the operation of the system 200.

5 illustrates the operation of a time trigger that may be used by embodiments of the present invention.

6 illustrates the operation of an operational profile subsystem that may be used by embodiments of the present invention.

7 illustrates the operation of an operation interval trigger that may be used by embodiments of the present invention.

8 illustrates the operation of a repeat action trigger that may be used by embodiments of the present invention.

9 illustrates the operation of a repeat distance trigger that may be used by embodiments of the present invention.

10 illustrates the operation of an attitude trigger that may be used by embodiments of the present invention.

11 illustrates the operation of a position trigger that may be used by embodiments of the present invention.

12 illustrates a time trigger that may be used by embodiments of the present invention.

13 illustrates a posture trigger that may be used by embodiments of the present invention.

14 illustrates a position trigger that may be used by embodiments of the present invention.

15 illustrates a system 1500 that is another embodiment of the present invention.

16 illustrates a main flow diagram of the operation of system 1500.

17 and 18 illustrate the operation of the graphics limiter due to the unit motion subsystem that may be used by embodiments of the present invention.

19 illustrates the operation of a display usage subsystem that may be used by embodiments of the present invention.

20 illustrates a sleep subsystem that may be used by embodiments of the present invention.

2L illustrates the graphics limitations due to unit motion subsystems that may be utilized by one embodiment of the present invention.

FIG. 22 illustrates the hardware of the operation interval trigger of FIGS. 2 and 7.

FIG. 23 illustrates the hardware of the repetitive action trigger of FIGS. 2 and 8.

FIG. 24 illustrates the hardware of the repeat distance trigger of FIGS. 2 and 9.

25 illustrates hard control of the graphics limiter due to the unit motion subsystem.

26 illustrates hardware of display usage subsystem 1517.

[Overview of invention]

One aspect of the present invention is to provide a method and / or apparatus for controlling an electrical device by detecting whether a user is currently or just about to use the device. Such a method and / or apparatus may allow an electrical device to operate a component that consumes a lot of power only when needed. Such a method and / or apparatus may also cause the electrical device to be inoperative when not in need of a large power consuming component.

One aspect of the present invention provides a method and / or apparatus for controlling an electrical device by sensing when a user desires to switch to a desired mode of operation of the electrical device and in response when wants to switch mode of the device. will be. One aspect of the present invention is to activate and / or deactivate a component, or to provide various events such as, for example, a change in the device's position, a target object or the device's distance to, from, or from a target location, a time event or a recurring event. And / or to switch between modes of the electrical device in response to the condition. Alternative embodiments of the present invention observe other types of conditions, such as acceleration of the device or change in acceleration rate. Embodiments of the present invention can progressively operate components of an electrical device when the electrical device is more likely to require components. In particular, if, according to the sensed condition, the electrical device is going to enter a desired mode and certain components of the electrical device are deemed to be needed in that desired mode, it is more likely that the electrical device is likely to require components. Embodiments of the invention may enable timely operation of individual components of an electrical device at different points in time. This gradual operation is such that if more indications are detected that certain components will be needed (e.g., the user's intention to switch the electronic device to a particular mode) is detected, for example, dedicated resources for the desired mode may be created. It may be done in an increasing manner. Likewise, embodiments of the present invention can cause components of an electrical device to be progressively inactive when the likelihood that components are needed becomes smaller.

One embodiment of the invention includes a novel system and associated method for improving the performance of an electronic device. The following description is set forth to enable those skilled in the art to make and use the invention. Descriptions of specific applications are provided only as examples. Various modifications to the preferred embodiments will be apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments and applications without departing from the spirit and scope of the invention. Accordingly, the present invention is not intended to be limited to the disclosed embodiments, but should be construed to the broadest scope that does not contradict the principles and features disclosed herein.

1 illustrates a block diagram of a system 100 that is a first embodiment of the present invention. The system 100 is a device usage detection system that monitors the physical characteristics of the electronic device 110, monitors certain other conditions for operating the electronic device 110, or otherwise controls the device. Upon detecting an indication or other predetermined condition of intention to use the device, the system 100 operates or controls the device 110. The system 100 includes a clock 101, a user input 102, a system output 103, a position sensing device 104, a posture sensing device 105, a time trigger 106 and an expected / latency reduction sub. System 107. Click 101, time trigger 106, and predicted / latency reduction subsystem 107 form a control subsystem. Alternative embodiments are not limited to this particular control system or to a control system that is structurally equivalent to this particular control system. The user input 102 may be any type of input mechanism, including but not limited to, for example, a keyboard, a mouse, scroll keys, and a graphical user interface, or for example any form of magnetic, optical Or an electronic memory device. The system output 103 may be any form of output that allows the system 100 to communicate with an external user or other type of electronic device, for example. Thus, the system output 103 can be any type of communication port, such as a display or a network port. For example, both input and output may be achieved using remote transmission techniques such as wireless and / or infrared transmission. Communication between the sensing device and the control subsystem can also be accomplished using various techniques, including remote transmission. Typically, the position sensing device 104 is a satellite based position determination system such as GPS or GLONAS, but may also use other position sensing devices such as, for example, an inertial navigation system. Typically, the attitude sensing device 105 is a flux sensing device 105, such as a flux gate compass or a triaxial magnetometer, but other attitude sensing devices such as inclinometers or laser ring gyro may be used. The predicted / latency reduction subsystem 107 further includes a position trigger 108 and an attitude trigger 109. Embodiments of the time trigger 106, the posture trigger 109, and the position trigger 108 are shown in FIGS. 12, 13, and 14, respectively.

As shown in FIG. 1, the output of clock 101 and user input 102 is coupled to time trigger 106. The user input 102, the output of the time trigger 106, the position sensing device 104 and the attitude sensing device 105 are coupled to the anticipated / latency reduction subsystem 107 and thus the position trigger 108 And posture trigger 109. The output of the predicted / latency subsystem 107 is coupled to the electronic device 110.

3 is a flow chart 300 illustrating the general operation of the system 100. In step 301, the user activates the system monitor mode. In this mode, the system 100 monitors the time trigger 106 (step 302) and periodically monitors the expected / waiting time subsystem 107 for any defined condition (step 303). If any defined condition is met, the system 100 operates the electronic device 110 (step 304). For example, a signal used to control the electronic device in response to the sensed physical condition of the electronic device is called a control signal. In an embodiment of the invention, these defined conditions are such that the electronic device 110 is within or outside of a certain distance range of an object or location, and the user is in a predetermined vicinity of the electronic device 110. Falling into or out of the range, vibration of the electronic device 110, or posture of the electronic device. Alternative embodiments may sense other physical characteristics of the electronic device 110, including but not limited to, for example, acceleration of the electronic device 110, changes in acceleration, and the like. The actuation or non-operation of the electronic device can be thought of as the switching mode of the electronic device. Such mode switching may include actuation and / or deactivation of the entire device, or actuation and / or deactivation of only a portion of the device.

5 is a flowchart 500 illustrating the operation of the time trigger 106. This trigger 106 implements a delay between the periods in which the system 100 monitors its expected / latency reduction subsystem. It also executes a time acting routine. For a time actuation routine, the user may indicate that he or she would like to activate or deactivate the device 110 within a specified time period from the time the actuation routine is initiated. The user may use this activation routine to instruct the trigger 106 to activate the device 110 every 10 minutes. In alternative embodiments of the present invention, a time actuation routine may be used to gradually operate a portion of device 110 at multiple user specified times. Such a system may be used where it is desirable to turn on different components of the device 110 at different times. Thus, such a system can turn on the first components that take time to power up or turn on the last components that consume the most power. Such a system can also be used to provide a sense level. In particular, such a system may utilize a sensing device that obtains a coarse position estimate until the electronic device falls within a certain range of the target position. Once within that range, the system can power up other sensing devices (eg, devices that are more precise than the first sensing device but consume more power).

In step 501, the monitor threshold W is defined by software used by the trigger 106. The threshold W stored by the trigger 106 is the delay between monitoring periods in which the system 100 monitors the subsystem 107. For example, for W = 50 ms, system 100 operates on time trigger 106 for 50 ms. After 50 ms, the system 100 branches to monitor the expected / latency reduction subsystem 107. The threshold W may be adjusted depending on how long the user wants to activate the time trigger 106 before the trigger 106 branches and monitors the subsystem 107. Alternate embodiments may use similar delays in other triggers.

In step 502 of FIG. 5, system 100 transmits a current time signal from clock 101 to time trigger 106. The triggers 108 and 109 described below allow the system 100 to determine various subsystems (eg, triggers 108 and 109) and a sensing device (eg, devices 104 and 105). An example of how to monitor the condition is provided. Steps 503 to 509 of FIG. 5 process the time actuation routine used by the time trigger 106 to activate the electronic device 110 or a portion of the electronic device 110 in a user defined time period. . At step 503, the trigger 106 determines whether this actuation routine is active. If this routine is not active, flow chart 500 branches to step 510. If this routine is active, flow chart 500 branches to step 504. In step 504, the trigger 106 determines whether or not a time actuation routine has been initiated. Once the time actuation routine has been initiated, the trigger 106 stores the current time as the "last check" time Y (step 506), prompts the user to enter the desired actuation time interval X (step 507), The interval X is then stored (step 508). This interval X is the time for which the trigger 106 waits from the "last check" time Y to operate the device 110 (ie, the time when the time actuation routine is started). In step 504, if trigger 106 determines that the time actuation routine is already active, the trigger 106 branches to step 505. In step 505, the trigger 106 calculates the time that elapses from the last check time (Y) to the current time, and then compares this elapsed time with the operating interval (X) in step (509). If the resulting time is greater than or equal to X, the flowchart branches to step 304 of FIG. 3, and the system 100 fully operates the device 110. If the elapsed time is less than X in step 509, the flowchart 500 branches to step 510 of FIG. 5. In step 510, the trigger 106 receives a new current time signal and calculates a time difference between the last received time signal received in step 502 and the new current time time received in step 510. Trigger 106 adds the elapsed time Z to the calculated time difference. The trigger 106 then compares the elapsed time Z and the monitor threshold W in step 512. If Z is greater than or equal to W, then trigger 106 sets Z to zero (step 514) and then proceeds to step 1001 of FIG. 10 to check anticipation / latency reduction subsystem 107. Thus, step 512 limits the amount of time that time trigger 106 operates before system 100 branches and monitors anticipation / latency reduction subsystem 107. If Z is less than W in step 512, the trigger 106 checks whether the user has turned off device 110 (step 513), and then returns to step 502 to receive the next current time time signal. do. Step 513 may also be used to determine whether the system 100 itself has turned off device 110 or which other device has turned off device 110.

10 is a flowchart 1000 illustrating the operation of the posture trigger 109. The physical characteristics of the electronic device sensed by the posture sensing device are referred to as posture characteristics. This posture trigger receives posture information indicative of such posture characteristics. This attitude information is obtained from the attitude signal coming from the attitude sensing device. In this embodiment, the attitude trigger 109 is implemented using hardware executing software.

This hardware will be described with reference to FIG. Flowchart 1000 illustrates the soft control operation of posture trigger 109. The posture trigger checks to determine whether the posture of the electronic device 110 is changing higher than the specified rate, or whether the posture of the electronic device 110 has changed from a normal posture to more than a specified amount. If the posture is changing above the specified rate or changed above the specified amount, the system 100 activates the electronic device 110. Step 1001 of the flowchart 1000 defines the "angle / second" operating limit C, the "angle from normal" operating limit (and the "recording of a new steady state A" threshold E). 109 receives the current attitude signal from the attitude sensing device 105 in step 1002, and the values for the "normal state" attitude A and the "last received" attitude B are transferred in step 1003. A check is made to see if it has been stored in. If values for A and B are not stored, the trigger 109 stores the current pose received from the attitude sensor in step 1004 as both A and B. Then, the flowchart 1000 branches to step 1101 of Figure 11 to check the position trigger 108. If at step 1003 it is determined that the values for A and B were previously stored, the flowchart 1000 Branching to step 1005, where the trigger 109 is between the current pose and the "last received" pose (B). Calculate the difference The trigger 109 then divides this posture difference by W to provide an angle / second value that represents the rate of change of the posture of the electronic device 110 (step 1006). ) Compares the calculated angle / second to the “angle / second” operating limit C, step 1006. If the calculated angle / second value is greater than C, the flowchart 1000 shows step 304 of FIG. , The system 100 fully operates the device 110. If the calculated angle / second value does not exceed C, the flowchart 1000 branches to step 1007.

In step 1007, the trigger 109 determines the difference between the current pose and the last received pose B. FIG. This difference is compared with the "recording of new steady state A" threshold (E). This threshold value E is a posture change threshold. For example, if the posture change is below the threshold, the steady state posture A and the current posture B will not be updated. If the pose change is greater than or equal to the threshold, these poses A and B will be updated. Accordingly, this limit E prevents small movements of the electronic device 110 from being recorded as a new steady state value A. FIG. That is, the threshold value E prevents the trigger 109 from resetting the steady state value A due to minor or insignificant movement of the system 100 or the electronic device 110.

Thus, if the posture change is greater than E, the flowchart 1000 branches to step 1008 where the current posture readings are the "normal state" posture A and the "last received" posture B ) Are stored as all. If the posture change does not exceed E, the flowchart branches to step 1009 where the trigger 109 calculates the difference between the current posture and the "normal state" posture A. The trigger 109 then compares this difference with the “angle from normal” operating threshold D in step 1010. If the difference exceeds D, flowchart 1000 branches to step 304 of FIG. 3, and system 100 operates device 110. If the difference does not exceed D, the flowchart branches to step 1011 to store the current attitude reading as B, then to step 1101 of FIG. 11 to check the position trigger 108. Thus, if device 110 is not actuated by posture trigger 109, system 100 continues to monitor position trigger 108.

11 is a flowchart 1100 illustrating the operation of the position trigger 108. The physical characteristics of the electronic device sensed by the position sensing device are called positional characteristics. The position trigger receives position information indicative of this position characteristic. This location information is obtained from the location signal coming from the location sensing device. In this embodiment, this operation is implemented using hardware executing software.

Referring to FIG. 14, hardware used to implement a position trigger will be described. Flowchart 1100 illustrates the operation of this software. The position trigger executes the position actuation routine. The position trigger 108 performs a check to determine whether the position outside the electronic device 110 has changed from that position when the position actuation routine is activated by a specified amount. The location trigger 108 also checks the access of the electronic device 110 to, for example, a region or point of interest specified by the user. In step 1101, the location monitoring mode is activated so that the location sensing device 104 sends location information to the trigger 108. Steps 1102-1109 process a location actuation routine to operate the electronic device 110 or a portion of the electronic device 110 at a user defined travel distance or user defined location. For example, a user sets the system 100 to operate the electronic device 110 every 50 feet. In step 1102, the trigger 108 determines whether this actuation routine is active. If this routine is not active, the flowchart 1100 branches to step 1110. If this routine is active, the flowchart 1100 branches to step 1103 to determine whether an active position actuation routine has just been initiated. If this routine has just begun, the trigger 108 stores the current position of the device 110 received in step 1101 as the "last stop" position G (step 1104) and the desired operating distance F for the user. ) Is entered (step 1105), and F is stored (step 1106). If it is determined in step 1103 that this operating routine is already active, the trigger 108 calculates the distance from G to the current position (step 1107), then the calculated distance and the user specified operating distance F Are compared (step 1108). If the calculated distance is greater than or equal to distance F, flow diagram 1100 branches to step 304 of FIG. 3, and system 100 fully operates device 110. If the calculated distance is less than F, flow diagram 1100 branches to step 1110. Alternative embodiments of the present invention may function using a position actuation routine that handles multiple user specified distances. Such user specified distances may be used, for example, to provide gradual power up or power down of device 110. In particular, designated portions of device 110 may be powered up or down at various distances to achieve gradual power up or power down of device 110.

Steps 1110-1112 process the access of the electronic device 110 to a region or point of interest specified by the user. For example, a user may indicate that he or she wants to activate device 110 or a portion of device 110 when the device enters a certain distance of a specified point or area. For example, a user may require that device 110 be active when the device is within half a mile of marker R2 outside the Auckland port. In step 1110, the system 100 checks to see if the user has specified a point / area of interest. If not specified, flow diagram 1100 branches to step 502 of FIG. 5 and returns to monitoring time trigger 106. If the user has designated this point of interest / area, flow chart 1100 branches to step 1111 where the trigger 108 determines the distance to or from each of these points / areas. In step 1112, the trigger 108 compares the determined distance with the user specified operating distance associated with each point / area. If any of the determined distances are less than the associated working distance, the flowchart 1100 branches to step 304 of FIG. 3, and the system 100 fully operates the device 110. If none of the determined distances is less than the associated working distance, the flowchart 1100 branches to step 502 of FIG. 5, and the system 100 returns to the monitor of the time trigger 106 as described above.

2 is a block diagram of a system 200 that is a second embodiment of the present invention. The system 200 includes components that operate in the same manner as those described with respect to the system 100. Similar components are similarly numbered (eg, time trigger 206 operates in the same manner as time trigger 106). In addition to having such similar components, system 200 includes an operational profile subsystem 210. This subsystem 210 is included as part of the expected / latency reduction subsystem 207 of the system 200.

Subsystem 210 is designed to allow system 200 to recognize a repetitive operation performed by a user or other recurring conditions that occur prior to the operation of device 110 over a period of use. Based on this recognition, subsystem 210 develops a particular operational profile associated with a particular repetitive operation or a particular repetitive condition. This operational profile allows the system 200 to recognize a particular repetitive operation or condition as an indication of imminent use. In response, system 200 may implement or initiate gradual operation of device 214. This operation profile subsystem 210 includes an operation interval trigger (AIT) 211, a repetition operation trigger (RAT) 212 and a repetition distance trigger (RDT) 213. Alternative embodiments of the present invention may be designed to respond to repetitive conditions other than the specific repetitive conditions described herein.

4 is a flow diagram 400 illustrating the general operation of the system 200. This behavior is almost the same as the behavior of system 100 with minor changes. Step 401 is almost the same as step 301. Step 402 is different from step 302. Specifically, the flowchart 500 of FIG. 5 describes the operation of step 402 of FIG. However, in step 512 of the flowchart 500, if Z is greater than or equal to W, the flowchart 500 of the system 200 executes step 514 and then branches to step 1001 of FIG. 10. Branch to step 601 of FIG. This change is shown to replace the flow chart connector 25 of FIG. 3 with the flow chart connector 3 of FIG. 4. Step 403 of FIG. 4 illustrates the operation of the operational profile subsystem 210 and the operation of the posture trigger 208 and the position trigger 209. The operation of subsystem 210 is described in more detail below. As can be determined at the end of the operation profile flow chart described below, the posture trigger 209 and the position trigger 208 are each operated, except that these triggers operate next to the operation profile subsystem 210. As described above, it operates in the same manner as the triggers 109 and 108. Thus, the operational flow diagram of the system 200 generally assumes that the electronic device 214 does not operate during this flowchart, generally from FIGS. 5 to 6, 7, 8, 9, 10, and then to FIG. Becomes 11. Once the operation of FIG. 11 is executed, assuming that electronic device 214 has not yet been operated by system 200, step 502 of FIG. 5 through connector 5 at operating temperature 11 of system 200. Loopback Thus, system 200 may make a multipath through this flow chart before device 214 operates.

After branching from step 514 of FIG. 5 to step 601 of FIG. 6, the system 200 checks the operational profile subsystem 210. This operational profile subsystem 210 may be implemented in the same manner as the triggers 106, 109 and 108, for example, using processor (s) executing software or other type of hardware. 6 is a flowchart 600 illustrating the basic operation of the software of the operational profile subsystem 210. In step 601, the subsystem 210 makes a check to see if the operational profile AP is active. That is, step 601 determines whether the subsystem 210 has been instructed by the user or some other device (eg, a computer) to retrieve a particular repetition condition. If received, the flowchart 600 branches to step 602. If at step 601 it is determined by subsystem 210 that the operational profile is not active, flow chart 600 branches to step 603.

In step 602, the subsystem 210 checks whether the system 200 has been instructed to use an AP different from the currently active AP. In other words, these instructions may come from a user of system 200 or any other device. If the system 200 determines in step 602 that it has been instructed to use another AP, the flowchart 600 branches to step 603. If at step 602 the system 200 determines that the system 200 is not instructed to use another AP, flow chart 600 branches to step 701 of flow chart 700. Flowchart 700 illustrates the operation of AIT 211.

In step 603, the system 200 confirms whether the user has selected the current AP, for example. If the AP is selected, the software of subsystem 210 branches to step 607. At step 607, system 200 recalls the selected current AP and provides settings to AP triggers 211, 212 and 213 defined by the current AP, respectively. As described in step 607, the operational profile may use some or all of these triggers to detect the condition. As described below, each of these triggers senses a different type of condition. Alternative embodiments may use alternative triggers that detect other types of conditions. After entering the AP definition setpoint in the appropriate one of triggers 211, 212 and 213, flow chart 600 branches to step 608 developed in Figures 7-9.

If in step 603 the system 200 determines that the current AP is not selected, the flowchart 600 branches to step 604. In step 604, the system 200 confirms whether to save the new AP upon deployment. As will be described below, this embodiment of storing values in a list each time system 200 passes through AP sub-systems 211, 212 and 213 provides an example of how an AP can be deployed. In other words, when a new AP is deployed, the instructions for the system 200 to store the AP may come from a user of the system 200 or any other device. If system 200 is instructed to save this AP when a new AP deploys, the system 200 causes the user to name the new AP at step 604. Upon receiving the name, the system 200 stores the default AP under that name in step 605, and then flow chart 600 branches to connector 7 through connector 26. The default AP may be defined in any manner appropriate for the particular application of system 200. In this embodiment, the default AP does not have any defined settings for the triggers 211, 212 and 213. Step 608 illustrates the operation of the operational profile triggers 211, 212 and 213. This operation starts from FIG. The operation of triggers 211, 212 and 213 are described in more detail below.

7 is a flowchart 700 illustrating the operation of an operation interval trigger 211. The operation interval trigger 211 is implemented using hardware and software. This hardware will be described with reference to FIG. 22 below. In this embodiment, flowchart 700 illustrates the operation of AIT software. In other words, this operation interval trigger 211 is used by the operation profile subsystem to detect repetitive conditions. This particular trigger 211 is for detecting the repetitive elapsed time from the time when the system 210 enters the monitor mode in step 401 to the "current time" at which the device 214 is activated. Thus, the system 200 may be configured to operate when the electronic device 214 has previously been repeatedly turned on at about the same time (within certain acceptable limits) as the time when the system 200 enters the monitor mode. ) Will “learn” to turn on the electronic device 214 at a particular time from the time it enters the monitor mode. Although this embodiment describes "operation" of an electronic device, alternative embodiments may differ in nonoperation. Thus, the AIT trigger and operating interval values herein refer to the interval as to whether the device 214 is being powered up or powered down.

In step 701, the AIT 211 checks whether the AIT interval value of this AIT 211 is stored. If the interval value is stored, flow chart 700 branches to step 702. If the interval value of the AIT is not stored, the flowchart 700 branches from step 701 to step 703. In step 702, the AIT 211 calculates the elapsed time from the time when the system 200 enters the monitor mode to the "current time", which is the most recently read time in step 502. This elapsed time is called the observed operating interval value. In other words, the monitor mode is activated in step 401. From step 702, the operation branches to step 704.

In step 704, the AIT 211 compares the elapsed time calculated in step 702 with the AIT interval value. If the elapsed time “matches” the AIT interval value, the flowchart 700 branches to step 404 of FIG. 4, and the system 200 fully operates the device 214. Elapsed time is " matched " with the AIT interval value refers to the case where such elapsed time is equal to or within a predetermined range of the interval value. If the elapsed time does not match the AIT interval value, flow chart 700 branches to step 703. As described below, this AIT interval value may be a "learned" value.

In step 703, the AIT 211 checks whether the device 214 has already been activated (by the system 200 itself, the user, or some other device). If the device 214 has not yet been activated, the operation represented by the flowchart 700 branches to step 801 of FIG. 8 to check the repetitive action trigger 212. In step 703, if the device 214 is operating, the flowchart 700 branches to step 705. In step 705, the AIT 211 calculates a mode change time interval (MCTI), which is triggered by the electronic device 214 by the trigger 212 from the time when the system 200 entered the monitor mode. Elapsed time until the current time to detect that the) has been activated. In the system 200, the electronic device 214 is initially powered off by the system 200 and then powered up. In an alternate embodiment, device 214 is initially powered on and system 200 can then power down the device. Thus, MCTI refers to the elapsed time from when the system 200 enters the monitor mode to when the electronic device 214 is deactivated. When system 200 is switching device 214 from off mode to on mode, MCTI may be referred to as down time interval (DTI). When system 200 is switching device 214 from on mode to off mode, MCTl may be referred to as an up time interval (UTI). System 200 and AIT 211 are described below in terms of down time intervals.

The AIT 211 keeps a list of DTIs. In other words, each DTI is generated by one pass of the AIT 211 through the flowchart 700. The AIT 211 uses the list to track the number of DTIs. Each newly calculated DTI is placed at the top of this DTl list. The number of entries in this list is typically defined according to the needs of a particular application. For example, if the application is for a highly mobile environment such as an airplane, the number of DTI entries can be quite large. Under these conditions, the user turns on the system 200 to operate the electronic device 214 a number of times. The number of DTI entries may be generated as follows. After the time when the system 200 is turned on and the system 200 turns on the electronic device 214, the electronic device 214 may be turned off by the user, the system 200 itself, or any other electronic device. In response to turning off the electronic device 214, the system 200 is turned off. After this point, the user can turn on the system 200 again and add another entry to the DTI list by taking another pass through the flowchart 700. If the list of DTIs is full, each newly calculated DTI is placed in the list (eg, at the top of the list), and for each new DTI added, the oldest DTI is from the list (eg, bottom of the list). From). Alternative ways of storing the associated DTI may be used.

In step 706, the system 200 makes a check to see if the DTI list is full. If the list is not full, the flowchart 700 branches to step 801 of the flowchart 800 shown in FIG. In step 801, the system 200 proceeds to update other AP triggers (ie, RAT 212 and RDT 213) as appropriate. In step 706, if the system 200 determines that the DTI list is full, the flowchart 700 branches to step 707. In step 707, the system 200 compares each of the entries in the DTI list to determine whether the majority of the DTIs are within a predetermined tolerance of each other in step 708. This comparison can be accomplished in any manner that identifies the majority group of DTIs that are relatively close to each other (ie, within the range of certain tolerances of each other). In other words, this predetermined tolerance may be appropriately selected for a particular application. One way to determine whether the majority of the DTIs are within a certain tolerance of each other is to determine the average of all entries in the DTI list. This allows each DTI to be compared to the mean. If the majority of the DTIs are within a predetermined tolerance for the mean, the flowchart 700 branches to step 709 where the majority of the DTIs are averaged. In other words, such identification may be performed for the appropriate majority using other schemes, including more complex ones. The average value of this specified majority of DTIs is stored as a new AIT interval value for the AIT 211. Flowchart 700 then branches from step 709 to step 801 of FIG. 8, where appropriate proceeds to update of another AP trigger. If it is determined in step 707 by the system 200 that the majority of the DTIs are not within a certain tolerance of each other, the flowchart 700 branches to step 801 of FIG. 8, where appropriate to trigger another AP. Proceed to the renewal of.

8 is a flowchart 800 illustrating the operation of a repetitive action trigger (RAT) 212. In this embodiment, this operation is implemented by executing software using hardware. Flowchart 800 illustrates the operation of the software. Hereinafter, hardware used by the RAT 212 will be described with reference to FIG. 23. This repetitive motion trigger retrieves a series of repetitive postures. Each attitude reading can be expressed as (x, y, z) coordinates, where x represents attitude rotation about the longitudinal axis, y represents attitude rotation about the horizontal axis, and z represents both the x and y axes Represents a rotation of the attitude about the axis perpendicular to the axis. Thus, for example, electronic device 214 may move through a series of postures before device 214 operates:

If the device moves regularly (within a certain tolerance) through this set of postures before the device 214 operates, the system 200 can learn this set of poses. The system 200 may then operate the device 214 as soon as it detects the learned series of poses.

In step 801, the RAT 212 writes a posture reading (eg, x, y, z coordinates) from the posture sensing device 205 and places the recorded posture on top of the list of posture readings. In other words, the number of attitude readings (x, y, z) in this attitude list is typically defined by the requirements of the particular application. The posture reading is added to this posture list until the posture list is full. In other words, each pass through flowchart 800 produces a single (x, y, z) attitude reading, which is added to the list. Once the attitude list is full, each newly recorded attitude reading is placed at the top of the list so that for each new reading added, the oldest attitude reading is removed from the bottom of the list. In step 802, the RAT 212 checks whether the device 214 has been activated. This device may have been operated by the user, the system 200 itself, or some other device. If device 214 has been activated, flow diagram 800 branches to step 806. If device 214 is inoperative, flow diagram 800 branches to step 803.

In step 803, the RAT 212 checks to see if the RAT posture setting for the Repetitive Action Trigger (RAT) 212 is stored. If the RAT attitude setpoint has been stored, the flowchart 800 branches to step 804. If this set point is not stored, the flowchart 800 branches to step 901 of FIG. 9 to check the repetition distance trigger 213. As described below, this RAT attitude setpoint may be a learned setpoint. The RAT attitude setting is actually a series of attitude readings (eg, indicated by (1) above) that the system 200 is searching.

In step 804 of the flowchart 800, the RAT 212 compares each of the entries in the list of posture readings (ie, the observed posture readings) with a corresponding posture in the RAT posture setpoint. For example, the RAT 212 compares the first observed posture with the first posture within the RAT set point, compares the second observed posture with the second posture within the RAT set point, and the like. The RAT posture set list may include one or more postures. In step 805, the SAT 212 checks whether each of the attitude readings in the attitude list matches the corresponding RAT attitude setting within a predetermined tolerance range. In other words, a match is made when the observed attitude reading is within a predetermined allowable range of the corresponding attitude in the RAT attitude setting list. In other words, this predetermined tolerance can be determined according to the requirements of the particular application. If each of the corresponding poses in these two lists match within a range of predetermined tolerances, the system 200 determines that the electronic device 214 has moved through the retrieved series of poses defined by the RAT pose setpoint. . As a result, the flowchart 800 branches to step 404 of FIG. 4, where the system 200 fully operates the device 214. If the two lists do not match within a range of predetermined tolerances, the flowchart 800 branches to step 901 of FIG. 9 and the system 200 checks the repetition distance trigger 213.

If the RAT 212 branches to step 806 at step 802, the RAT 212 at step 806 "learns" a series of poses that occurred before the device 214 was turned on. Specifically, a series of poses that occurred before the device 214 was turned on are added to the list of active motion routines (AMR). By moving through the flowchart 800 multiple times, a plurality of series of poses are added to the AMR list. Thus, the operational motion routine list is a list or lists of "serial poses". Specifically, each entry in the AMR list is itself or a list of poses. RAT 212 stores the pose list from step 801 as an operational motion routine. The RAT 212 then places this AMR on top of the list of AMRs. The number of entries in this AMR list is typically defined according to the requirements of the particular application. Each new AMR is added to the top of the AMR list. When the list is full, for each new AMR added, the oldest AMR is removed from the bottom of the list.

In step 807, the RAT 212 tests to see if the AMR list is actually full. If the AMR list is not full, the flowchart 800 branches to step 905 of the flowchart 900 of FIG. 9 to update the repetition distance trigger set point as appropriate. If the AMR list is full, the flowchart 800 branches to steps 808 and 809. In these steps 808 and 809, the RAT 212 compares the AMRs in the list to determine whether the majority of the AMRs are within a predetermined tolerance of each other. One way to do this is to determine the average of the corresponding attitude readings of all lists that make up the AMR. For example, the RAT 212 calculates an average of all the first posture readings in the lists constituting the AMR, and then calculates an average of all the second posture readings in the list constituting the AMR, in the same manner below. Calculate the mean. When calculating this “average pose list”, the RAT 212 compares each of the pose readings in each entry of the AMR list with the corresponding pose readings in the average pose list. If all of the attitude readings of a particular AMR entry are within a predetermined tolerance of the corresponding average pose from the average pose list, that particular AMR is included in the group. If the majority of AMRs are included in this group, flow diagram 800 branches from step 809 to step 810 where the corresponding attitude readings in each of the majority of AMR entries are averaged, and this average The list of poses is stored as a new RAT pose setpoint. Other techniques can be used to determine which AMRs are within certain tolerances of each other. From step 810, the flowchart branches to step 905 of FIG. 9 to update the repetition distance trigger set point if necessary. In step 809, if the majority of AMRs are not within a predetermined tolerance of each other, flow diagram 800 branches to step 905 of FIG. 9 to update the repetition distance trigger set point as appropriate.

9 is a flowchart 900 illustrating the operation of the repetition distance trigger 213. In this embodiment, this operation is implemented by executing software using hardware. Flowchart 900 illustrates the operation of this software. Hereinafter, hardware used by the RDT 213 will be described with reference to FIG. 24. The repetition distance trigger 213 monitors the repetition distance from the position of the electronic device 214 when the system 200 enters the monitor mode to the position of the electronic device 214 when the electronic device is turned on. The system 200 will “learn” turning on at the same distance from this position of the electronic device 214 when the electronic device 214 enters the monitor mode.

In step 901 of the flowchart 900, the RDT 213 checks whether the repetition distance value of the repetition distance trigger RDT is stored in the application profile AP. As will be explained below, this repetition distance value may be a value to be learned. If a repetitive distance value has been stored, the flowchart 900 branches to step 902. If no repetition distance value has been stored, flow chart 900 branches to step 903. In step 902, the RDT 213 calculates the distance from the current position of the electronic device 214 to the position of the electronic device 214 at the time when the monitor mode was activated. This distance is called the observed distance value. Flowchart 900 then branches from step 902 to step 904. In step 904, the RDT 213 compares the distance calculated in step 902 with the repetition distance value. If the calculated distance “matches” the repetitive distance value, flow chart 900 branches from step 904 to step 404 of FIG. 4, and system 200 fully operates device 214. Matching is made when the calculated distance is within a specified range of repeat distance values. If the calculated distance does not match the repeat distance value, flow diagram 900 branches to step 903. At step 903, the RDT 213 checks whether the device 214 has been activated. If device 214 does not operate, flow diagram 900 branches to step 1001 of FIG. 10 to continue checking of posture trigger 209 and position trigger 208. This branching is represented by the connector 27 from FIG. 9 to FIG. 6 and the connector 25 from FIG. 6 to FIG. 10. The operation of triggers 209 and 208 is the same as the operation of triggers 109 and 108 described with reference to system 100, respectively.

If the device 214 is actuated in step 903, the flowchart 900 branches from step 903 to step 905. In step 905, the RDT 213 calculates the distance from the current position of the electronic device 214 to the position of the electronic device 214 in which the monitor mode was activated. This distance is called the mode change distance interval (MCDI). This mode change distance interval (MCDI) is determined by the electronic device 214 from the time when the system 200 enters the monitor mode to the current time when the trigger 213 detects that the electronic device 214 has been activated. It's the distance you've moved. Similar to the MCTI of the AIT 211, the MCDI may be referred to as the change of the device 214 from the power down mode to the power up mode (ie, operation) as in this embodiment. This MCDl may also be called down distance interval (DDI). Similarly, MCDI may be referred to as the change of device 214 from a power up mode to a power down mode. Such MCDI may also be called Up Distance Interval (UDI). The system 200 is described below in terms of down distance intervals.

Each pass through flow diagram 900 calculates a single DDI. The trigger 213 puts the DDI calculated in step 905 at the top of the DDI list. The number of entries in this DDI list can be defined according to the requirements of each particular application. When the DDI list is full, the newly calculated DDI is put on top of the list, and the oldest DDI is removed from the bottom of the list. Other techniques may be used to store related DDI values. Trigger 213 branches from step 905 to step 906. In step 906, the system 200 checks whether the DDI list is full. If it is not full, flow chart 900 branches to step 404 of FIG. 4, and system 200 fully operates device 214. After device 214 is operated by system 200, device 214 may be turned off by the user, system 200 itself, or any other electronic device. If the system 200 is turned back on after this point, a second DDI is generated, which is added to the DDI list. If this DDI list is full, flow diagram 900 branches to step 907.

In step 907, the RDT 213 compares the entries in the DDI list with each other and then branches to step 908. In step 908, the RDT 213 checks whether the majority of the DDIs are within a predetermined tolerance of each other. This comparison can be accomplished in any way that specifies the majority of the DDI groups relatively close to each other (ie within a certain tolerance of each other). In other words, this predetermined tolerance may be appropriately selected for a particular application. One way of determining whether the majority of DDIs are within a predetermined tolerance of each other is to determine the average of all entries in the DDI list. This allows each observed DDI to be compared with this average. If the majority of the DDIs are within a predetermined tolerance of the average, the flowchart 900 branches to step 909 where the majority of the DDIs are averaged. In other words, other methods, including more complex ones, can be used to perform this specification on the appropriate majority.

If the majority of the DDI is within a predetermined tolerance of each other, the system 200 specifies the device 214 operating pattern, in which the device 214 will enter the monitor mode when the system 200 enters the monitor mode. It is operated repeatedly at about the same distance from the position of this device 214. If the majority of the DDI is within this predetermined tolerance, flow chart 900 branches to step 909 to average the majority of the DDI. This average value is stored as a new value for the repetition distance value. This step is for the system 200 to "learn" the repetition distance it is looking for. Flowchart 900 branches from step 909 to step 401 of FIG. 4, and system 200 fully operates device 214. If at step 908 the majority of the DDI is away from the repetitive distance value and is not within the predetermined tolerance range, the flow chart 900 branches to step 401 of FIG. 4, and the system 200 completes the device 214. It works.

15 illustrates a system 1500 coupled to a vision system 1514. This system 1500 illustrates one embodiment of the present invention used to control the vision system 1514. Vision system 1514 is a special example of an electronic device, such as device 214. The vision system 15l4 may be a conventional optical combiner type instrument such as a head up display, or preferably a type of vision system such as that disclosed in PCT Publication No. WO95 / 07526. Of Electro-optic Time System Using Position and Attitude (Publication No. WO95 / 07526, International Application Date 16 June 1994, Applicant Criticom Corp., Inventors John Ellenby and Thomas William Ellenby, International Application No. PCT / US94 / 06844). Published PCT applications are incorporated herein by reference. The systems 1500 and 1514 are also used to illustrate additional concepts related to the reduction in the level of complexity of the graphics when the movement of the controlled electrical device is detected. Such systems illustrate concepts related to the operation or non-operation of the system display based on the detected user's approach and concepts relating to the maintenance of the power of the medium in which the non-operation of the system is detected.

In FIG. L5, the components of system 1500 operate in the same manner as the components of system 200 of FIG. Vision system 1514 is a graphics limitation due to display such as unit motion subsystem 1516, display utilization subsystem 1517, sleep subsystem 1518, and video monitors or head-up displays (not shown). limitation). Vision system 1514 also includes a piezo electric gyro system 1515. This gyro system 1515 is coupled to an image stabilization system (not shown) of the vision system 1514. Examples of image stabilization, such as a changeable prism image stabilization system using piezo electronic gyros, are disclosed in International Publication No. WO95 / 07526, filed on March 16, 1995, filed by Criticom Corporation. The system of FIG. 15 can be used to implement a system such as that disclosed in this WO 95/07526. Specifically, this embodiment may be used in a system where, for example, information about the real world position and / or pose of the graphical object is previously stored in any manner. Such data may represent something in the real world, such as, for example, a real world object, location or region (s). However, graphical objects may or may not be associated with these real world items. The information thus stored is then provided to the system 1514. Based on the position and / or posture of the vision system 1514 and based on the field of view of the imaging device, the system l514 recalls the stored graphical objects and then places an accurate image on the real-time image of the particular field of view observed by the user. You can stack them in place. The imaging device may be a camera (eg, a digital camera) with a suitable lens.

The output of the clock 1501 and the user input 1502 are coupled to the time trigger 1506. The output of this time trigger 1506, the user input 1502, the position sensing device 1504 and the attitude sensing device 1505 are coupled to the output of the anticipation / latency reduction subsystem 1507, thereby positioning A trigger 1508, an attitude trigger 1509, an operation interval trigger 1511, a repetition operation trigger 1512, and a repetition distance trigger 1513. The prediction / latency reduction subsystem 1507, the clock 1501, the user input 1502, the position sensing device 1504, the attitude sensing device 1505, the time trigger 1506 and the piezo electric gyro 1515 are visioned. Coupled to system 1514, and thus to graphics limitations due to unit motion subsystem 1516, display utilization subsystem 1517, and sleep subsystem 1518.

16 is a flowchart 1600 illustrating general operation of the system 1500. At step 1601, the user activates the monitor mode to instruct the system 1500 to monitor the time trigger 1506 and the expected / latency reduction subsystem 1507. Flowchart 1600 then branches to step 1602 where the system 1500 monitors the time trigger 1506 for the time specified by the monitor threshold W and then branches to step 1603. do. In step 1603, the system 1500 monitors the expected / latency reduction subsystem 1507. Flowchart 1600 then branches to step 1604, where the vision system 1514 operates, and then branches to step 1605. In step 1605, the system 1500 monitors for graphics limitations due to the unit motion subsystem 1516 of the vision system 1514. Flowchart 1600 branches from step 1605 to step 1606, where the system 1500 monitors the display utilization subsystem 1517 of the vision system 1514. The flow chart then branches to step 1607, where the system 1500 monitors the sleep subsystem 1518 of the vision system 1514.

17 and 18 illustrate the operation of the graphics limiter due to the unit motion subsystem 1516. 21 is a block diagram of one embodiment of hardware used to implement graphics limitations due to unit motion subsystem 1516. 17 and 18 show how software used to implement graphics limitations due to unit motion subsystem 1516 operates in relation to the detected vibration of vision system 1514 recorded by piezo electric gyro 1515. Illustrate flow charts 1700 and 1800 indicating whether to do so. At step 1701, system 1516 defines an application specific vibration threshold H. The vision system 1514 begins to reduce the complexity of all graphics when the vibration level rises above the threshold H. A "vibration level" is typically measured by a change in a number of movements (eg, direction of movement) over a period of time. Thus, this "vibration level" is, for example, the "vibration rate" which becomes the rate of direction change. At step 1702, subsystem 1516 receives the motion signal from piezo electric gyro 1515 and the time signal from clock 1501 to calculate the vibration rate. Typically, the gyro may be independent of any other device 1514 subsystem, but such a gyro is associated with a deformable prism image stabilization system (not shown) of the vision system 1514. In step 1703, the system 1514 checks whether the calculated vibration rate exceeds the vibration threshold H. If the calculated vibration rate does not exceed H, flow diagram 1700 branches to step 1801 of FIG. 18 describing further operation of the graphics limiter by unit motion subsystem 1516. If the calculated vibration rate exceeds the vibration threshold H, the flowchart 1700 branches to step 1704. At step 1704, the system 1514 checks whether the calculated vibration rate exceeds the stabilization system's ability to stabilize the image displayed by the vision system. This image stabilization system is typically designated as capable of handling the maximum vibration rate. If the calculated vibration rate does not exceed the stabilization system's ability to stabilize the image, the flowchart 1700 branches to step 1706. If the calculated vibration rate exceeds the stabilization system's ability to stabilize the image, the flowchart 1700 branches to step 1705.

In step 1705, the system 1516 drops the "complexity level" of all imported graphic objects by an appropriate number of "complexity levels" based on the severity of the detected vibrations. In this embodiment, for example, in response to determining that vibration has exceeded the ability of the stabilization system to compensate for this vibration, the level of complexity may be reduced by two or more levels. In embodiments of the present invention, it may be appropriate to reduce the complexity level by a greater amount when the stabilization system can no longer compensate for the vibrations because of the possibility that the vibrations will become more severe under these conditions.

Even when the stabilization system can handle vibrations, the complexity level is reduced in this embodiment because of the possibility that the user will vibrate. Thus, at step 1706, the system 1514 reduces the "complexity level" of all graphical objects being displayed by one "level". In this embodiment, to reduce the complexity level, one or more complexity levels for representing each graphic object are defined. Thus, one graphical object can be represented by one complexity level. On the other hand, the second graphic object may be represented by a plurality of complexity levels. Different levels of complexity associated with any particular graphical object visually represent that particular graphical object at different levels of complexity. These levels can range from very complex (e.g., full blown raster images) to those of minimum complexity (e.g., simple vector images) required to convey the meaning of the graphical object to the user.

The complexity of the graphics used to represent a particular graphical object at any particular moment can be determined, for example, by assigning an importance number to the graphical object based on the importance of the real world object with which the graphical object is associated. This importance number IN may be defined by the application. For example, in maritime navigational applications, graphical objects associated with navigational markers may have a relatively high importance number. However, in tourist applications that cover the same geographic area, these navigation markers are likely to have lower importance. Thus, the graphical object associated with the nautical marker may have a high importance number in navigational applications, but may have a lower importance number in touristic applications. The importance number assigned by an application may change when the application switches from one mode of operation to another. Using the example above, the system 1514 may be designed to operate in two modes of operation, sailing and tourism, in any particular geographic area.

To change the level of complexity, system 1514 can control which graphical objects are displayed. For example, when vibrations occur, system 1514 may only display more important graphical objects. Alternatively, system 1514 can reduce complexity by gradually decreasing the resolution of some or all of the graphical objects being displayed based on importance. Thus, for example, if the system 1514 was using the conditions of tourism described above, the resolution of the marker would be degraded as a result of vibration, so that the marker would only be displayed as a rough geometric approximation. Alternatively, the marker may not be displayed at all in these conditions. To define this complexity level, each complexity level is assigned a "complexity number". In this embodiment, this complexity number is the number of calculations needed to generate the graphical object associated with that particular complexity level. When allocating resources of system 1514 for graphical generation, the system 1514 uses these various levels of complexity.

1800 is a flowchart 1800 illustrating operation of the second portion of the graphics limiter due to on unit motion subsystem 1516. This operation is similar to the operation described in FIG. 7 in the sense of lowering the complexity level of the graphical object in response to the detected condition. However, the operation of FIG. 18 handles the attitude change rate rather than vibration. Specifically, the subsystem 1516 of FIG. 18 operates in response to the detected attitude slew rate of the vision system 1514. In this embodiment, the slew rate of vision system 1514 is the attitude change rate of system 1514. In this embodiment, subsystem 1516 is implemented using hardware executing software. This hardware will be described with reference to FIG. 25. Flowchart 1800 illustrates the operation of this software. In step 1801 of flowchart 1800, subsystem 1516 defines a predetermined attitude slew rate threshold J. FIG. This threshold J can be application specific, i.e. determined according to the requirements of a particular application. This threshold J is the slew rate at which the system 1516 begins to drop the complexity level of the graphical object.

In step 1802, the system 1516 receives an attitude signal from the attitude sensing device 1505 and a click signal from the clock 1501. The system 1516 calculates the actual attitude slew rate K of the vision system 1514 from these signals. In step 1803, the system 1516 checks whether the calculated attitude slew rate K exceeds the attitude slew rate threshold J. If K does not exceed J, flow diagram 1800 branches to step 1901 of FIG. 19 to check display usage subsystem 1517. If K is greater than J, flow chart 1800 branches to step 1804. In step 1804, the system 1514 drops the complexity level of all graphics above level 1, but the amount is defined by the application specific complexity reduction slew rate threshold. For example, if the measured slew rate K is above the first threshold, the complexity level may be reduced to the level of complexity associated with exceeding this first threshold. If the slew rate K is above the second threshold, then the complexity level may be reduced to the complexity level associated with that second threshold. Flowchart 1800 then branches to step 1901 of FIG. 19 to check display usage subsystem 1517.

19 is a flow chart 1900 illustrating the operation of display utilization subsystem 1519 of system 1514. This subsystem 1519 detects whether the user is actually looking at the display (not shown) of the vision system 1514 and activates or deactivates the display (s) accordingly. Note that some of the activities related to the display, such as warming up the backlighting, may be inactive at all. Instead, these activities can remain active while the vision system 1514 is wholly inactive. At step 1901, subsystem 1519 checks whether the display (s) are active. If the display (s) are active, the flowchart branches to step 1902. If the display (s) is not active, the flowchart branches to step 1903.

At step 1902, subsystem 1519 checks whether the physical object is within the range of the display operating range threshold of the application / user definition of system 1514. In this embodiment, subsystem 1519 is designed to detect, for example, the approach of the user's eyes. This determination can be made using a low power sound wave or emission range finder or other similar device. The user may want to change this operational threshold so that the spectacles wearer can use the system. The glasses can affect the approach measurement by the range finder by providing a reflective surface closer to the display than the user's eyes. Preferred display operating range thresholds may be part of the user usage profile. Such a usage profile can inform the system 1500 and / or system 1514 of any constant posture associated with any particular user.

If the system 1519 detects an object within the display operating range threshold at step 1902, the flowchart 1900 branches to step 1905 where the display remains activated. Flowchart 1900 then branches to step 2001 of FIG. 20 to check subsystem 1518. If no object within the display operating range threshold is detected in step 1902, flow chart 1900 branches from step 1902 to step 1904. In step 1904, the display (s) is deactivated. Flowchart 1900 then branches to step 2001 of FIG. 20 to check sleep subsystem 1518. If the flowchart 1900 branches from step 1901 to step 1901, in step 1901 the system 1519 checks whether the object is within an application / user defined display operating range. If any object is detected within this display operating range threshold, flow chart 1900 branches from step 1903 to step 1906 where the displays are activated. The system 1519 then branches to step 2001 of FIG. 20 to check the sleep subsystem 1518. If no object is detected within the display operating range threshold at step 1903, flow chart 1900 branches to step 2001 of FIG. 20 to check sleep subsystem 1518.

20 is a flowchart 2000 illustrating the operation of the sleep subsystem 1518. This flowchart 2000 can be understood, for example, in connection with a flowchart illustrating the system 200. If the position or attitude of the vision system 1514 does not change over a user or application definition period, this subsystem 1518 returns the system 1500 to monitor mode via the connector 5. This subsystem 1518 illustrates an additional technique that can further reduce the power consumption of the device being controlled by one embodiment of the present invention.

Sleep subsystem 1518 is implemented by executing software using hardware. The operation of this software is illustrated by the flowchart 2000 of FIG. Hardware for implementing the sleep subsystem can be designed in a manner known in the art.

As shown in FIG. 20, in step 201 the sleep subsystem 1518 determines whether the user has activated the sleep routine. If the user did not run the sleep routine, the subsystem 1518 branches to step 2014. If the user has activated the sleep routine, subsystem 1518 branches to step 2002. At step 2002, subsystem 1518 defines a time limit M at steady state. This time limit M is the time the subsystem 1518 uses to determine whether the system 1514 should be put to sleep. For example, if no changes were made to the attitude and position of the system 1514 within the previous time M, the subsystem 1518 puts the system 1514 to sleep.

Subsystem 1518 branches from step 2002 to step 2003. In step 2003, subsystem 1518 tests to determine whether the sleep activation interval has been specified by the user or some other device or the like. This slip operating interval is used by the subsystem 1518 in the same way as the time limit M. For example, if no changes were made to the attitude and position of the system 1514 within the previous time L, the subsystem 1518 puts the system 1514 to sleep. The difference between M and L is that M is specified by the subsystem 1518 itself and L is specified by the user. If the slip operating interval L is specified, the subsystem 1518 branches to step 2006. If the slip operating interval is not specified, subsystem 1518 branches to step 2004.

In step 2006, the subsystem 1518 tests to determine whether it has started counting down from L to zero. This countdown begins whenever none of the position and attitude of the device 1514 changes. If subsystem 1518 has started this countdown, this subsystem 1518 branches to step 2007. If subsystem 1518 has not started counting down, this subsystem 1518 branches to step 2009.

In step 2009, the subsystem 1518 tests to determine whether the position or attitude of the vision system 1514 has changed during the last M seconds. If at least one of the position and attitude has changed, subsystem 1518 branches to step 2014. If one of the position and the posture has not changed, the subsystem 1518 branches to step 2010. At step 2010, subsystem 1518 counts down from L to 0 and then branches to step 2014.

If the subsystem 1518 branches to step 2004, the system 1500 allows the user to define a slip activation interval L. FIG. Subsystem 1518 then branches to step 2005. In step 2005, the user enters a time interval L into the system 1500. If system 1500 communicates this time interval to subsystem 1518, subsystem 1518 stores this time interval as L. Subsystem 1518 then branches to step 2014.

If the subsystem 1518 branches to step 2007, step 2007 tests to determine whether the position or attitude of the vision system 1514 has changed in the last M seconds. If one of the positions and postures has changed, subsystem 1518 branches to step 2008. In step 2008, the subsystem 1518 stops the countdown from L to 0 and resets the counter that performs the countdown to L. Subsystem 1518 branches from step 2008 to step 2014. If at step 2007 the subsystem 1518 determines that one of the position and attitude has not changed, the subsystem 1518 branches to step 2011. In step 2011, the subsystem 1518 tests to determine whether the countdown is zero. If the countdown is not zero, the subsystem 1518 branches to step 2014. If the countdown is zero, the subsystem 1518 branches from step 2011 to step 2012. At step 2012, subsystem 1518 tests to determine whether device 1514 has been deactivated (eg, by a user or some other device). If the device 1514 is deactivated, the subsystem 1518 branches to step 2015, where the system 1500 is switched off. If device 1514 is not deactivated, subsystem 1518 branches from step 2012 to step 2013.

If subsystem 1518 branches to step 2014, then at step 2014, subsystem 1518 may have put system 1514 to sleep by a user or some other device manually or by operation of another device. Test to determine whether or not If system 1514 has gone to sleep, subsystem 1518 branches to step 2013. In step 2013, the system 1500 deactivates the display (s) and returns to step 502 of FIG. If system 1514 has not entered a sleep state, subsystem 1518 branches to step 2016. In step 2016, the subsystem 1518 tests to determine whether the system 1514 has been deactivated. If system 1514 is inactive, switch off system 1500. If system 1514 is not deactivated, subsystem 1518 branches to step 1604 of FIG. 16.

12 illustrates hardware implementing time triggers 106 and 206. Time triggers 106 and 206 include four RISC processors 1202, 1204, 1206 and 1208. These processors are programmed to each perform some of the operations described in connection with FIG. RISC processor 1202 stores the monitor threshold W and compares the elapsed time reading Z with W. Processor 1204 tracks the elapsed time reading Z. The processor 1208 stores the "last check" time Y and calculates the elapsed time from this time Y to the current time. Processor 1206 stores an operating interval X, and compares this operating interval X with the elapsed time from time Y to the current time. There is no need to use multiple processors. Specifically, in alternative embodiments, other numbers of processors, a single RISC or CISC processor, or even other types of hardware and / or may be sufficient as long as they perform appropriate functions to implement one embodiment of the present invention. The combination can be used.

13 illustrates hardware implementing posture triggers 109 and 209. Posture triggers 109 and 209 include five RISC processors 1302, 1304, 1306, 1308, and 1310. These processors are programmed to each perform some of the operations described in connection with FIG. Processor 1308 stores the " last received " posture B and calculates the angle / second rate of posture change from the time when this posture B was stored to the time when the new posture is stored. Processor 1302 stores an "angle / second" operating limit C, and compares this limit C with the angle / second value calculated by processor 1308. Processor 1304 stores the steady state attitude reading A and calculates a difference from the last received attitude A. Processor 1306 stores the "record of new steady state A" threshold E, and compares the angle / second value calculated by processor 1308 with threshold E. The processor 1310 stores an “angle from normal” operating limit E, and compares this limit E with the difference calculated by the processor 1304. There is no need to use multiple processors. Specifically, in alternative embodiments, other numbers of processors, a single RISC or CISC processor, or even other types of hardware and / or combinations thereof may be employed, as long as they perform the appropriate functions to implement one embodiment of the present invention. It is available.

14 illustrates hard control implementing position triggers 108 and 208. Position triggers 108 and 208 include three RISC processors 1402 and 1404 and a graphics controller 1406. Each such processor is programmed to perform some of the operations described in connection with FIG. The graphics controller also performs some of the functions described in connection with FIG. Processor 1402 stores the "last stop" position G and calculates a range from the current position to the last stop position G. The processor 1404 stores the set distance F, and compares the distance F with the range calculated by the processor 1402. The graphics controller 1406 calculates ranges for all areas that the user has designated as interested and for all areas that have associated range operating thresholds. There is no need to use multiple processors. Specifically, in alternative embodiments, other numbers of processors, a single RISC or CISC processor, or even other types of hardware and / or the same may be used, as long as they perform the appropriate functions for implementing one embodiment of the present invention. Combinations can be used.

21 is a block diagram of a preferred embodiment of the hardware used to implement graphics limitations due to unit motion subsystem 1516. Subsystem 1516 includes three RISC processors 2102, 2104, and 2106. The RISC processor is programmed to perform some of the operations described in connection with FIGS. 17 and 18, respectively. For example, the RISC processor 2102 is programmed to store the vibration threshold H and compare H with the current measured vibration of the system 1514. RISC processor 2104 stores the vibration threshold of the stabilization system and is programmed to compare the current measurement vibration of subsystem 1514 with the vibration threshold of stabilization subsystem of system 1514. RISC processor 2106 stores the slew rate threshold J and compares J with the measured slew rate K of system 1514.

FIG. 22 illustrates the hardware of AIT 211 of FIG. 2. As shown, the AIT 211 utilizes seven RISC processors 2202, 2204, 2206, 2208, 2210, 2212, and 2214. The RISC processor 2202 stores the AIT interval value. Processor 2204 stores the time when the monitor mode of system 200 was activated. This time is the first time that was read in step 502 of FIG. Processor 2206 calculates the elapsed time from the time when stored by processor 2204 to the current time, where the current time is the time most recently read by system 200 in step 502. The processor 2208 compares the elapsed time DTI calculated by the processor 2206 with the AIT interval value stored by the processor 2202. Processor 2210 determines whether the user has activated device 214. When the user has operated the device 214, the elapsed time calculated by the processor 2206 becomes the down time interval DTI. Processor 2210 stores this DTI in a list of DTl. If this list is full, the oldest DTI is removed from the list. Processor 2212 compares each of the DTIs in the list generated by processor 2210 with each of the other DTIs in this list to determine whether the majority of the DTIs in the list are within a predetermined tolerance of each other. Processor 2214 averages them if there are DTIs within the tolerance of each other's complaints. This average is stored by the processor 2202 as a new value of the AIT interval value. There is no need to use multiple processors. In alternative embodiments, other numbers of processors, a single RISC or CISC processor, or even other types of hardware and / or combinations thereof may be utilized, as long as they perform appropriate functions to implement one embodiment of the present invention. Can be.

FIG. 23 illustrates the hardware of the RAT 212 of FIG. 2. As shown, the RAT 212 uses six RISC processors 2302, 2304, 2306, 2308, 2310, and 2312. RISC processor 2302 places the current attitude value of device 214 in the list of attitude readings. If the list is full, the oldest posture reading is removed from the list. Processor 2304 stores repetitive action trigger settings. Processor 2306 compares each value in the list generated by processor 2302 with the RAT setpoint stored by processor 2304. The processor 2308 determines whether the user has activated the electronic device 214. When the user has operated the electronic device 214, the list of attitude readings generated by the processor 2302 is stored at the top of the list of motion routines. If the list of motion routines is full, the oldest motion routine is removed from the list of motion routines. Processor 2310 compares each of the motion routines in this list to each other to determine whether the majority of the motion routines are within the predetermined tolerance of any other motion routine in the list. Processor 2312 averages motion routines that are within a predetermined tolerance of each other. Processor 2304 stores this average as a new value for the RAT set point. There is no need to use multiple processors. In alternative embodiments, other numbers of processors, a single RISC or CISC processor, or even other types of hardware and / or combinations thereof may be utilized, as long as they perform appropriate functions to implement one embodiment of the present invention. Can be.

FIG. 24 illustrates the hardware of the RDT 213 of FIG. 2. As shown, the RDT 213 utilizes seven RISC processors 2402, 2404, 2406, 2408, 2410, 2412, and 2414. The RISC processor 2402 stores the RDT repeat distance value. When the monitor mode of the system 200 is activated for the first time, the processor 2404 stores the location of the system 200. This position is the position that was initially read during the first pass through the position trigger action as illustrated in FIG. 11. The processor 2406 calculates the distance between the current location and the location stored by the processor 2404. The processor 2408 compares the distance calculated by the processor 2406 with the RDT repeat distance value stored by the processor 2402. Processor 2410 determines whether the user has activated device 214. When the user has operated the device 214, the distance calculated by the processor 2406 becomes the down distance interval DDI. Processor 2410 stores this DDI in a DDI list. If the list is full, the oldest DDI is removed from the list. Processor 2412 compares each of the DDIs in the list generated by processor 2410 with each of the other DDIs in this list to determine whether the majority of the DDIs in this list are within a predetermined tolerance of each other. Processor 2214 averages DDIs if they are within a predetermined tolerance of each other. This average is stored by processor 2402 as a new value for the RDT repeat distance value. There is no need to use multiple processors. In alternative embodiments, other numbers of processors, a single RISC or CISC processor, or even other types of hardware and / or combinations thereof may be utilized, as long as they perform appropriate functions to implement one embodiment of the present invention. Can be.

25 illustrates the hardware of the graphics constraints (GLDUM) subsystem 1516 due to unit motion. As shown, the GLDUM subsystem 1516 utilizes eight RISC processors 2502, 2504, 2506, 2508, 2510, 2512, 2514, and 2516. RISC processors 2502-2508 handle vibrations of electronic device 214. The RISC processor 2510-2516 handles posture change of the electronic device 214. The RISC processor 2502 stores the vibration threshold H. The processor 2504 calculates the vibration rate of the vision system 1514. The processor 2506 compares the vibration rate calculated by the processor 2504 with the vibration thresholds stored by the processor 2506. The processor 2508 instructs the system 1514 to drop the complexity level of the graphical objects displayed, according to the comparison result by the processor 2506. The processor 2510 stores the attitude slew rate threshold J of the system 1514. Processor 2512 calculates the actual attitude slew rate of system 1514. The processor 2514 compares the actual slew rate calculated by the processor 2514 with the slew rate threshold J stored by the processor 2510. There is no need to use multiple processors. In alternative embodiments, other numbers of processors, a single RISC or CISC processor, or even other types of hardware and / or combinations thereof may be utilized, as long as they perform appropriate functions to implement one embodiment of the present invention. Can be.

26 illustrates a display usage subsystem 1517. As shown, the display utilization subsystem 1517 utilizes a range finder 2602, three RISC processors 2604, 2606, and 2608, and a display plane 2610. The range finder 2602 can be an infrared range finder that detects a range for an object approaching the display plane 2610 of the device 1514. In this embodiment, this range is tested in a direction away from the display and in a direction perpendicular to the display. Display plane 2610 corresponds to a display, such as a video monitor or head-up display that presents an image to a user. RISC processor 2604 stores the display operating range threshold. Processor 2606 compares the range data from infrared range finder 2602 with the display operating thresholds stored by processor 2604. If the comparison performed by processor 2606 indicates that the object is within a display operating range threshold, processor 2608 activates the display. At this time, if the display is already in operation, the display is kept in operation. If the comparison performed by the processor 2606 indicates that the object is not within the display operating range threshold, the processor 2608 deactivates the display. At this time, if the display has already been deactivated, the display is kept in the deactivated state. There is no need to use multiple processors. In alternative embodiments, other numbers of processors, a single RISC or CISC processor, or even other types of hardware and / or combinations thereof may be utilized, as long as they perform appropriate functions to implement one embodiment of the present invention. Can be.

Applicants have described the invention in connection with specific embodiments, but the invention is not limited to these disclosed embodiments. Applicant's invention may be applied beyond the scope of the specific system described herein by way of example. Although various circuits have been described herein, embodiments of the present invention need not utilize all the specific circuits disclosed herein. In addition, alternative embodiments may use alternative circuits for some or all of these circuits. For example, the RISC processor of FIGS. 12-14 may be replaced by a CISC processor, a single RISC processor, or other circuitry that accomplishes the functionality described. In addition, while some of these embodiments have been described as software, alternative embodiments may implement some or all of these software functions in hardware. Alternative embodiments of the present invention may also achieve the object of the present disclosure using alternative sensing methods or devices. Alternate embodiments may also be embodied as a lower limit (or upper limit) and / or a threshold expressed herein as an upper limit (or lower limit). While these embodiments have described the operation of the electronic device, alternative embodiments may deal with the non-operation of the electronic device in the same manner. Similarly, although the flowchart of this embodiment has been described in terms of "operation of the device", alternative embodiments are designed to operate (or deactivate) a portion of the device, for example to provide gradual or gradual non-operation. Can be.

Claims (37)

An electronic device control system, A monitoring subsystem for sensing at least one physical characteristic of the electronic device; At least one prediction / latency reduction subsystem, coupled to the sensing subsystem, for periodically monitoring and storing physical characteristic signals based on the at least one physical characteristic sensed by the sensing subsystem; And In response to receiving the at least one physical characteristic signal from the at least one expected / latency reduction subsystem, providing the electronic device with a control signal for switching the electronic device from a first mode to a second mode. Includes a control subsystem, And said at least one physical characteristic signal is a signal indicative of at least one predetermined physical characteristic of said electronic device indicative of usage or expected usage of said electronic device. The method of claim 1, The sensing subsystem includes a posture sensing device, wherein the at least one predetermined physical characteristic signal has a posture signal, and the at least one predetermined physical characteristic has a predetermined posture characteristic of the electronic device. Electronic device control system. The method of claim 1, The sensing subsystem comprises a position sensing device, wherein the at least one physical characteristic signal has a position signal and the at least one predetermined physical characteristic has a predetermined position characteristic of the electronic device Device control system. The method of claim 1, And the control signal for switching the electronic device from the first mode to the second mode is for switching the electronic device from a power off mode to a power on mode. The method of claim 1, The control signal for switching the electronic device from the first mode to the second mode is for switching the electronic device from a power on mode to a power off mode. The method of claim 1, And said control signal for switching said electronic device from said first mode to said second mode is for switching a portion of said electronic device from a power off mode to a power on mode. The method of claim 1, And said control signal for switching said electronic device from said first mode to said second mode is for switching a portion of said electronic device from a power on mode to a power off mode. The method of claim 1, The control subsystem provides the electronic device with a second control signal for switching the electronic device from the second mode to a third mode; And The control subsystem provides the second control signal to the electronic device in response to receiving the second at least one physical characteristic signal from the at least one expected / latency reduction subsystem. At least one physical characteristic signal is indicative of a second at least one predetermined physical characteristic. The method of claim 8, The control signal for switching the electronic device from the first mode to the second mode is one of the first power off mode and the first power on mode from one of a first power off mode and a first power on mode. To convert a portion of the electronic device into another, The second control signal for switching the electronic device from the second mode to the third mode includes the second power off mode and the second power on mode from one of a second power off mode and a second power on mode. Electronic device control system for switching the second portion of the electronic device to another one. The method of claim 2, And wherein the predetermined posture characteristic comprises a range value of the posture. The method of claim 2, And the predetermined posture characteristic comprises a certain posture value and a predetermined allowable value around the specific posture value. The method of claim 2, The predetermined posture characteristic includes a posture change rate, and the posture change rate satisfies a predetermined posture change rate change threshold. The method of claim 4, wherein And said predetermined position characteristic comprises a position range. The method of claim 4, wherein And said predetermined position characteristic comprises any particular position and a predetermined tolerance value around said specific position. The method of claim 4, wherein The predetermined position characteristic comprises a rate of change of position, wherein the rate of change of position satisfies a predetermined position change rate change threshold. The method of claim 4, wherein The predetermined position characteristic includes an acceleration value, and the acceleration value satisfies a predetermined acceleration threshold value. The method of claim 10, Further comprising user input, wherein the control subsystem executes software to provide a user with an option to adjust the range of attitude values using the user input. The method of claim 13, Further comprising a user input, wherein the control subsystem executes software to provide a user with an option to adjust the range of the position using the user input. The method of claim 11, Further comprising user input, wherein the control subsystem executes software to provide the user with an option to adjust the particular posture value and the predetermined tolerance value around the particular posture value using the user input. Electronic device control system, characterized in that. The method of claim 14, Further comprising user input, wherein the control subsystem executes software to provide the user with an option to adjust the particular location and the predetermined tolerance value around the particular location using the user input. An electronic device control system. The method of claim 11, And further comprising user input, wherein said control subsystem executes software to provide a user with an option to adjust between said posture change rate and said predetermined posture change rate change threshold using said user input. Control system. The method of claim 15, Further comprising user input, said control subsystem executing software for providing a user with an option to adjust a rate of change of position and a predetermined change in posture change threshold. The method of claim 4, wherein And said control subsystem comprises a position trigger for receiving position information obtained from said position signal. The method of claim 2, And the control subsystem includes a posture trigger that receives posture information obtained from the posture signal. The method of claim 24, The posture trigger provides the control signal in response to the posture information. The method of claim 1, The control subsystem includes an operational profile subsystem for receiving physical characteristic information obtained from the physical characteristic signal, wherein the operational profile subsystem provides the control signal in response to the physical characteristic information. Control system. The method of claim 26, The operation profile subsystem includes an operation interval trigger, wherein the physical characteristic information includes an observed operation interval value. The method of claim 26, And said operational profile subsystem comprises a repetitive motion trigger, wherein said physical property information includes a series of observed attitude readings. The method of claim 26,  And said operational profile subsystem comprises a repetitive distance trigger, wherein said physical property information includes one observed distance value. The method of claim 26, The operational profile subsystem is adapted to access a plurality of operational profiles, wherein each operational profile relates to other users who can use the system. The method of claim 30, Each of the operation profiles having a setting value for at least one of an operation interval trigger, a repetitive operation trigger, and a repetition distance trigger. In the electronic device control method, Sensing one or more physical characteristics of the electronic device, wherein the one or more physical characteristics comprise one or more of a posture and a location of the electronic device; Providing a control signal to the electronic device triggered by at least one predetermined value of at least one of the one or more physical characteristics of the electronic device; And In response to the control signal, switching the electronic device from a first mode to a second mode, Wherein the first mode relates to a first power consumption level of at least a portion of the electronic device, the second mode relates to a second power consumption level of at least a portion of the electronic device, and wherein the first power consumption level is And consume more power when at least a portion of the electronic device is in an active state than with the second power consumption level when at least a portion of the electronic device is in an inactive state. In the electronic device control method, Sensing at least one physical characteristic of the electronic device; Periodically monitoring and storing, by the predicted / latency reduction subsystem, a physical characteristic signal based on the sensed at least one physical characteristic, wherein the at least one physical characteristic signal is at least one predetermined value of the electronic device. Physical properties; And In response to receiving the at least one physical characteristic signal, providing a control signal for transitioning the electronic device from a first mode to a second mode, wherein the at least one physical characteristic signal is selected from the electronic device. And a signal indicative of at least one predetermined physical characteristic of said electronic device indicating usage or anticipated usage. The method of claim 33, Wherein said at least one predetermined physical property comprises at least one of a posture and a location of said electronic device. The method of claim 33, And the first mode is a power on mode and the second mode is a power off mode. An electronic device operation mode switching system, A control subsystem having an attitude trigger for switching the operation mode of the electronic device between relative operating states; And A posture detection subsystem that detects a posture change transmitted to a posture trigger of the control subsystem as a posture signal, Wherein the posture trigger performs a check to determine whether the posture change is out of a preselected range that may initiate a change of the operating mode of the electronic device to a different operating state. Switching system. In the operation mode switching system of the vision system, A control subsystem having an attitude trigger for switching the operating mode of the vision system between the relative states of displayed graphics complexity; And A posture detection device for detecting a posture change transmitted to the control subsystem as a posture signal, Here, the vision system is monitored by a control subsystem having a graphics limiting subsystem due to unit motion in communication with the attitude sensing device, wherein the graphics limiting subsystem due to the unit motion is a range in which a change in the posture signal is preselected. Determining whether there is a deviation from the control system, so that the control system can initiate a change of the operation mode of the vision system to another state of the displayed graphic complexity.