Charger for video game controllers

By integrating image capture and inertial measurement units into the computing device, the system automatically detects changes in controller status and identifies the user, solving the cumbersome issues of battery replacement and charging for wireless game controllers. This enables seamless charging and application recovery, enhancing user experience and convenience.

CN115768536BActive Publication Date: 2026-11-17SONY INTERACTIVE ENTERTAINMENT LLC
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
CN202180045096.1
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2020-06-25
Filing Date
2021-06-07
Publication Date
2026-11-17
Estimated Expiration
2041-06-07

AI Technical Summary

Technical Problem

The process of replacing and charging batteries for wireless game controllers is cumbersome, requiring users to replace or charge them frequently. Furthermore, existing technology cannot automatically identify user identity and application status, affecting the user experience.

Method used

By integrating an image capture unit and an inertial measurement unit into the computing device, the system automatically detects the pick-up and drop-down of the controller, combines machine learning algorithms to identify the user, achieves seamless charging and application recovery, and supports simultaneous use by multiple users.

Benefits of technology

It reduces user operation steps, improves the convenience and user experience of the game controller, supports multiple users to use at the same time, and improves charging efficiency and the automation of application recovery.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN115768536B_ABST
    Figure CN115768536B_ABST
Patent Text Reader

Abstract

A method, system, and apparatus for controller operation includes detecting a state change of the controller from a charging state to an operating state. In response to detecting the state change of the controller, the state of a computing device changes from a controller charging state to a controller operating state. The computing device receives input from the controller and sends a visual indication of the input to a display device. Alternatively, a method, system, and apparatus for enhanced controller charging may include detecting a change in controller state from an operating state to a charging state. After detecting the change in controller state, the computing device determines whether there is ignored input and, if there is no ignored input, automatically logs out of the user account or automatically enters a standby mode.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This disclosure relates to the field of controllers. Specifically, aspects of this disclosure relate to charging game controllers. Background Technology

[0002] Game controllers are used to control a variety of computing devices, from computers to game consoles. Typically, game controllers are connected to computing devices via a wired connection. More recently, game controllers have evolved to connect wirelessly to computing devices.

[0003] Wireless game controllers require power from sources other than the computing device itself. They are typically battery-powered. Battery-powered game controllers can use primary batteries such as alkaline, NiOx, and zinc-carbon batteries, or rechargeable batteries such as nickel-cadmium, lithium-ion, nickel-metal hydride, and rechargeable alkaline batteries.

[0004] Original batteries are discarded due to their wastefulness and inconvenience. They are wasteful because they become unusable after depletion and must be thrown away. They are inconvenient for users because once depleted, they must be replaced with another battery suitable for the game controller. Numerous battery model standards exist, and users must know which model is compatible with their controller. This creates numerous problems for users after purchasing a game controller, as they will ultimately have to buy or otherwise obtain batteries suitable for the controller, and they must remember the correct battery model. Therefore, rechargeable batteries represent a more advantageous option for wireless device manufacturers because they are more convenient for users.

[0005] Rechargeable batteries offer users greater convenience, but they also have their own problems. One advantage of rechargeable batteries is that they can be shipped with the game controller, allowing users to use the controller immediately after purchase. A second advantage is that users don't need to frequently buy new batteries for their game controllers and can easily recharge the rechargeable batteries that come with the controller. Recharging rechargeable batteries is also a major disadvantage, as charging can take a significant amount of time, and unless the game controller is specifically designed to be used, it cannot be used while charging. Additionally, recharging the game controller requires users to perform extra steps, such as pausing the game and plugging the controller into a power source or switching to a new, already charged controller.

[0006] It is against this backdrop that the implementation scheme of the present invention was proposed. Attached Figure Description

[0007] The teachings of this disclosure can be readily understood by considering the following detailed description in conjunction with the accompanying drawings, in which: Figure 1 This is a flowchart illustrating a method for performing controller operation when picked up by a user, according to aspects of this disclosure.

[0008] Figure 2 This is a flowchart illustrating a method for operating a controller using context information according to aspects of this disclosure.

[0009] Figure 3 This is a schematic diagram illustrating the context determination of controller operation when picked up by a user, according to aspects of this disclosure.

[0010] Figure 4 This is a schematic diagram illustrating a computing device having an image capture unit according to aspects of the present disclosure, the image capture unit being used in conjunction with a method for controller operation when picked up by a user.

[0011] Figure 5 This is a flowchart illustrating a method for controller operation when placed in a charging state according to aspects of this disclosure.

[0012] Figure 6 This is a schematic diagram illustrating a controller with ignored input on a charger according to aspects of this disclosure.

[0013] Figure 7 This is a schematic diagram illustrating a controller according to an aspect of this disclosure, the controller having an ignore input.

[0014] Figure 8 This is a schematic diagram illustrating a computing device having an image capture unit according to aspects of this disclosure, the image capture unit being used in conjunction with a method for controller operation when placed on a charger.

[0015] Figure 9 This is a block diagram illustrating a system for controller operation and charging according to aspects of this disclosure. Detailed Implementation

[0016] While the following detailed description contains numerous specific details for illustrative purposes, those skilled in the art will understand that many variations and modifications to these details are within the scope of the invention. Therefore, the examples of embodiments of the invention described below are illustrated without losing the generality of the claimed invention and without limiting the claimed invention.

[0017] While numerous specific details have been set forth to provide a thorough understanding of embodiments of the invention, those skilled in the art will appreciate that other embodiments may be practiced without these specific details. In other instances, well-known methods, procedures, components, and circuits have not been described in detail so as not to obscure aspects of this disclosure. Certain portions of the description herein are presented based on algorithms and symbolic representations of operations on data bits or binary digital signals within computer memory. These algorithmic descriptions and representations may be techniques used by those skilled in the art of data processing to communicate the essence of their work to others skilled in the art.

[0018] As used in this paper, an algorithm is a self-consistent sequence of actions or operations that lead to a desired result. These actions or operations involve the physical manipulation of physical quantities. Typically, though not always, these quantities take the form of electrical or magnetic signals that can be stored, transmitted, combined, compared, and otherwise manipulated. Sometimes, primarily due to frequent use, it has proven convenient to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, etc.

[0019] Unless specifically stated or otherwise apparent from the following discussion, it should be understood that throughout the description, discussions using terms such as “processing,” “computing,” “converting,” “coordinating,” “determining,” or “identifying” refer to the actions and processes of a computer platform, which is an electronic computing device including a processor that manipulates and transforms data represented as physical (e.g., electronic) quantities within the processor’s registers and accessible platform memory into other data represented similarly as physical quantities within the computer platform memory, processor registers, or display screen.

[0020] Computer programs may be stored in computer-readable storage media, such as, but not limited to, any type of disk, including floppy disks, optical disks (e.g., compressed optical disc read-only memory (CD-ROM), digital multifunction optical disc (DVD), Blu-ray Discs™, etc.), and magneto-optical disks, read-only memory (ROM), random access memory (RAM), EPROM, EEPROM, magnetic cards or optical cards, flash memory, or any other type of non-transitory media suitable for storing electronic instructions.

[0021] The terms “connected” and “linked” together with their derivatives are used herein to describe structural relationships between components of a device used to perform the operations described herein. It should be understood that these terms are not intended to be synonyms. Rather, in some specific cases, “connected” may indicate that two or more elements are in direct physical or electrical contact with each other. In other cases, “connected,” “linked,” and their derivatives are used to indicate logical relationships, such as the logical relationships between node layers in a neural network. “Connected” can be used to indicate that two or more elements are in direct or indirect physical or electrical contact (with other intermediary elements between them), and / or that two or more elements cooperate with or communicate with each other (e.g., as in causal relationships).

[0022] According to aspects of this disclosure, features of the controller and / or associated computing device may enhance the charging of the controller or its use after charging. Figure 1 A method 100 for controller operation according to aspects of this disclosure is illustrated. Figure 1 The flowchart shown illustrates the controller operations performed when a user picks up the controller. As shown, the computing device can detect that the controller has been picked up, as indicated at 101. The computing device can detect that the controller has been picked up when the controller changes its state from a charging state to an operating state. Alternatively, the computing device can detect when the user picks up the controller using inertial data from the controller or by analyzing an image obtained by an image capture unit using an image analysis algorithm. Once the computing device detects that the controller has been picked up, the computing device can connect to the controller, as indicated at 102. In some implementations, the computing device may include an internal state from a charging state to an operating state. In some implementations, connecting the computing device to the controller may include other operations, such as operations associated with establishing a wireless connection with the controller. After the connection has been established, the controller can begin normal operation to control the computing device. Specifically, the computing device can receive input 105 from the controller and use these inputs and send visual feedback corresponding to the inputs to a display device 106 to perform calculations.

[0023] Alternatively, during or after establishing a connection with the controller, the computing device may log in to a user account or profile associated with the controller 103. During or after establishing a connection, the controller may transmit a unique code or other identifier information associated with the controller to the computing device. The computing device may access account or profile information associated with the unique code or other identifier information. When receiving the unique code or other identifier information from the controller, the computing device may log in to the account or profile using the associated account information. Non-limiting examples of other identifier information include the assigned controller name, the assigned controller number, the controller color, or other information that can be used to distinguish the first controller from the second controller. After logging in to the account or profile associated with the controller, the computing device may resume normal operation, as indicated at 105. According to an additional aspect of this disclosure, the computing device may resume the application associated with the controller after connecting to the controller at 102. Application resumption may occur after logging in to the account associated with the controller, as indicated at 103, or it may occur at 102 when the computing device connects to the controller. Whenever a user pauses an application, the computing device may automatically resume the application associated with the controller by automatically creating a log of the unique code or other identifier information and application status information. When the computing device receives a unique code or other identifier, it can use the unique code or other identifier and logs to determine the application's status information, launch the application, and load the application's status information into memory so that the application can be resumed if the user pauses it. If the application is still running on the computing device, it can be easily resumed. After the application is resumed, the computing device can return to normal operation at point 105.

[0024] This enhances the user experience of controller operation by eliminating the need for users to pair their controllers with the console every time they want to use them. Previously, users had to manually log into their accounts and restore the application. Additionally, it would be advantageous for the computing device to automatically recognize the user when the controller is picked up.

[0025] Figure 2This is a flowchart illustrating a method 200 for operating a controller using context information according to aspects of this disclosure. Method 200 begins when the computing device detects that the controller has been picked up, as indicated at 201. As discussed above, the computing device can determine that the controller has been picked up when the controller changes its state from a charging state to an operating state. Upon detecting this state change or upon detecting that the controller has been picked up, the computing device can change the controller state on the computing device from charging to operating. In other words, the computing device can be connected to the controller. Before, during, or after the controller state on the computing device changes from the charging state to the operating state, the computing device can analyze the context regarding the controller picking up or the transition from the charging state to the operating state, as indicated at 202. The analysis of the context regarding the controller picking up or the transition from the charging state to the operating state at 202 may use historical data, controller motion data, and / or image data from the image capture unit.

[0026] Analysis of historical data at point 202 may include using a table or other log file containing past user login times and / or application access times. After the computing device has determined that the controller state has changed from a charging state to an operating state, the computing device may use this table to determine at point 203 which user account was logged in or at point 204 which application to restore or launch. Alternatively, after logging the computing device into a user account or profile, the computing device may use historical data to determine the application to restore or launch at point 205.

[0027] Figure 3 A graphical illustration shows an example of context determination for an application recovery operation performed by the controller when picked up by a user, according to aspects of this disclosure. As indicated by arrow 301, when user 306 picks up controller 307 from charging pad 302, the controller device changes from a charging state to an operating state. Charging pad 302 can monitor the charging state of controller 307, and can send a signal to computing device 303 indicating that controller 307 is no longer charging and has therefore changed from a charging state to an operating state. Computing device 303 can use internal clock 308 to determine the time when user 306 picks up controller 307 from charging pad 302 and use historical data 304 to determine the applications that the user has historically recovered or launched and launch the determined applications, as indicated at 305. As shown, for example, but not limited to, Figure 3 The computing device can receive the time when the controller changes from the charging state to the operating state from the charging pad. The computing device can use a table or other log file containing historical data 304 to query the applications launched by the user at 9:00 PM. Based on the historical data, the computing device determines, for example, that the user typically launches a movie streaming application on the computing device at 9:00 PM, and then the computing device can launch the movie application at 305.

[0028] Alternatively, images from the image capture unit targeting the user or controller can be used to determine the context of the user picking up the controller and the controller transitioning from a charging state to an operating state, such as... Figure 4 As shown. Figure 4 This is a diagram illustrating a computing device with an image capture unit according to aspects of this disclosure, used in conjunction with a method for controller operation when picked up by a user. When a user picks up the controller 407 from the charger 402 as indicated by arrow 401, the image capture unit 404 can acquire an image, such as a photograph or video of the user 406. The image capture unit can be a camera, video camera, laser scanning device, or other means that converts visible or invisible radiation (e.g., infrared or ultraviolet) into electrical signals that can be interpreted as an image. The charger 402 can send a signal to the computing device 403 that the controller is no longer charging and therefore the controller has changed its state from charging to operating. This signal can trigger the image capture unit 404 to turn on and acquire an image of the user 406. Alternatively, the image capture unit can always be on and analyze the image to determine when the user picked up the controller. The computing device 403 or a server communicating with the computing device can apply a facial recognition algorithm to the image to identify whether someone is holding the controller 407 and the identity of the person holding the controller. The computing device 403 may include a database DB having associations between user accounts and identifier information. The identifier information may be any information used to associate an image acquired from the image capture unit with a user. Identifier information may be generated for a user during the registration process to log in to their account using the computing device 403. During the registration process, an image may be captured and identified by the user 406. The identifier information generated from the identified image may be stored on the computing device and associated with the corresponding user account, for example, in the database DB. Any subsequently identified images from the user 406 may also be stored to improve the identifier information. Once the user's identity is determined, the computing device 403 may, for example, log in to the account associated with the detected user 406. Additionally, in some embodiments, the computing device may restore or launch an application associated with the controller after logging into the user account.

[0029] In another alternative implementation, motion data from the controller can be used to identify the user. For example, but not limited to, the controller may include an inertial measurement unit (IMU) comprising an accelerometer, gyroscope, tilt sensor, or other sensors for controller movement. These may include a user-identifiable signature movement when the user picks up the controller. During user registration with a user account or profile, the computing device may record the signature movement sensed by the IMU as the user's signature movement information, which can then be associated with the user account. The signature movement information may be stored on the computing device and associated with the user account; it may include inertial data from the controller when the user picks up the controller. Therefore, when the user picks up the controller and the inertial data from the controller matches the signature movement information, the user has been identified and the computing device can log into the user account associated with the signature movement and the user holding the controller. For example, but not limited to, a person with tremor can register a user account on the computing device, and during registration, their signature movement information can be recorded when they pick up and put down the controller several times. The signature information is then associated with a user account or profile in memory or an external database. Due to a user's physical condition, the signature information of a user with tremors may include a combination of many unique acceleration spikes. Therefore, the controller detects the unique spike combination that the computing device can log into the associated user account.

[0030] Figure 5 This is a flowchart illustrating a method for operating a controller when placed in a charging state, according to aspects of this disclosure. The computing device may detect that a user has placed the controller down, as indicated in 501. For example, and not limitingly, the computing device may detect that the controller has changed its state from an operating state to a charging state or that the user or another person is no longer holding the controller. Detecting the state change from the operating state to the charging state may use, for example, but not limited to, signals from a charging pad connected to the computing device, signals from the controller, or signals from an image capture unit.

[0031] When the user is detected to have placed the controller down at 501, the computing device may (optionally) automatically pause the application running on the computing device, as indicated at 502. The pause operation may save the state of the application running on the computing device, so that if the device stops, the application closes, or the device is picked up again, the state can be loaded to resume the application. Alternatively, the computing device may simply pause further processing of the application.

[0032] The charger, controller, or computing device may include an ignored input that, when triggered, causes the computing device to ignore that the controller has been put down by the user or that the state has been changed from an operational state to a charging state. After detecting that the user has put down the controller at 501 or (alternatively) that the computing device has paused the application at 502, the computing device may check whether an ignored input signal has been received, as indicated at 503. The ignored input may be a button, touchscreen press, switch, a series of buttons, controller movement, voice command, visual gesture that can be captured by an image capture device, or any other type of interface element interpreted as ignored input by the computing interface. When no ignored input signal is received after a timeout period, the console may log out the user account or profile and / or enter sleep mode or shut down, as indicated at 504. The sleep mode may be a power-saving mode in which most features of the computing device are turned off or in power-saving mode, but the state of the device is saved in memory so that the computing device can be quickly 'woke up' and the device state before sleep is quickly restored. The timeout period can be a set time for the computing device to wait to receive an ignored input signal. The timeout period can be of any length, such as, but not limited to, less than 30 seconds, less than one minute, less than two minutes, or no timeout. When an ignored input signal is received before or during the timeout period, the computing device can ignore that the controller has been put down or that the controller has changed its state from the operating state to the charging state and maintain connection with the controller, as indicated at 505. Alternatively, if the controller is put down or its state changes from the operating state to the charging state after receiving an ignored input and within the input reception period, the computing device can ignore the change in the controller's state from operating to charging and maintain connection with the controller at 505. The input reception period can be the same length as the timeout period or can be a different length, such as, but not limited to, less than 30 seconds, less than one minute, or less than two minutes. If an ignored input is received and the controller is not put down or does not change its state from operating to charging within the input reception period, subsequent changes in the controller's state from "operating" to "charging" after the input reception period expires will not cause the device to behave as if the ignored input has been pressed. If the controller has been placed down or is charging and has received an ignored input, the computing device can maintain its connection to the controller at point 505 and wait for further action from the user. This provides the benefit that players can temporarily place their controllers on the charging pad without putting the computing device to sleep or logging out of its configuration file.

[0033] A common scenario with controllers equipped with rechargeable batteries occurs when the battery of the first controller is depleted. In these situations, the user can turn off the first controller, put it into a charging state, pick up the fully charged second controller, and use the second controller in place of the first controller. According to some aspects of this disclosure, an "ignore" button can facilitate this controller switching. As indicated at 506, the computing device can continuously monitor the state change of the second controller from a charging state to an operational state, or monitor whether the second controller will be picked up when the first controller is in a charging state or placed down. In some cases, if the second controller is not picked up after the pickup period, the computing device can simply maintain the connection with the first controller at 505. If the first controller is not picked up or does not change from a charging state to an operational state during the shutdown period, the computing device can disconnect from the controller and log out of the user account and / or enter sleep mode or shut down. If the second controller is picked up or changes from a charging state to an operational state, the computing device can wait to detect whether the first controller has also been picked up or changed from a charging state to an operational state, as indicated at 507.

[0034] When the computing device detects that the first controller has been picked up during a controller switching period, it determines that two players want to play the game. Therefore, the computing device connects to the second controller under a second user account or profile 509, or changes the internal controller state of the second controller from charging to operational. Thus, the first controller logs in under the first account or profile, and the second controller logs in under the second account or profile, allowing two or more players to play the game simultaneously on the computing device. Settings and profile customizations can be saved separately for each account associated with each controller. While the described methods relate to the first and second controllers, these methods can be extended to any number of controllers, including third, fourth, or more controllers.

[0035] When the first controller is not picked up during the controller switching period, it can be disconnected from the computing device, as indicated at 508. Disconnection can be achieved by the computing device changing the controller's internal state from an operating state to a charging or non-operating state and subsequently ignoring inputs from the first controller (except for some applicable basic charging or signals). Then, at 510, the computing device can connect to the second controller under the first user account or configuration file, thereby enabling controller switching, as the user can use the second controller exactly as if it were the first controller.

[0036] Figures 6 to 8 Different embodiments of this disclosure are illustrated, having different locations for “ignoring” inputs and / or different charging methods. Figure 6 This is a diagram illustrating a controller on a charger that ignores inputs, according to aspects of this disclosure. Figure 6 As shown, controller 602 can be placed on charger 601 (e.g., a wireless charger or a charging pad connected to the controller via conductive contacts). Charger 601 is connected to computing device 603 and includes an "ignore" input 604. In this case, the ignore input is an ignore button mounted on the housing of charger 601. When the "ignore" input 604 is triggered, for example by pressing the ignore button, charger 601 sends an ignore signal to computing device via the connection between computing device and charging pad. Here, the ignore button has not been pressed, but controller 602 has been placed on charger 601 and controller 602 has changed its state from operating state to charging state. Computing device 603 can receive a signal from charging pad 601 indicating to computing device 603 that controller 602 is charging. In the example shown, the user enables the option to pause the application on the placed controller, thus pausing application 605 running on computing device 603.

[0037] Figure 7 This is a diagram illustrating a controller according to aspects of this disclosure, the controller having an ignore input. In the illustrated example, the charger 701 does not communicate with the computing device 703, but is simply plugged into a wall socket 706. The charger 701 may be a charging pad, charging cable, charging dock, or other similar charging device. The controller 702 communicates with the computing device 703 via a wireless connection 707. With the controller 702 connected to the charger 701, the controller sends a wireless signal to the computing device 703, notifying the computing device 703 that the controller 702 has changed its state from an operating state to a charging state. When an “ignore” input 704 is triggered, the controller may send a wireless signal to the computing device 703 notifying it that the “ignore” input 704 has been triggered. Here, the “ignore” input 704 has not yet been triggered, but the controller 702 is connected to the charger 701. The controller 702 wirelessly communicates with the computing device 703, informing it that its state has changed from an operating state to a charging state. After a timeout period has elapsed, the computing device logs out of the user account, as indicated in 705. The advantage of this implementation is that it eliminates the need to develop a dedicated charging pad for communication with the computing device. The wireless signal can be wireless internet, Bluetooth, near-field communication, infrared, etc.

[0038] Figure 8 This is a diagram illustrating a computing device having an image capture unit according to aspects of this disclosure, the image capture unit being used in conjunction with a method for controller operation when placed on a charger. Using an image capture unit 806 communicatively connected to a computing device 803 allows for greater flexibility and choice in controller operation. Figure 8In the example illustrated, the user has placed the controller 802 on the charger 801. The image capture unit 806 may be configured to acquire an image of an area 807 in front of the display device 808, including the charger 801. The image capture unit 806 may acquire an image that the computing device identifies as an indication that the user is not holding the controller or that the controller has changed its state from an operating state to a charging state. For example, and not limitingly, the captured image may show the user putting the controller down, the controller not being in the user's hand, or the controller being on the charger. The computing device may use machine learning algorithms in conjunction with the image to help identify whether the controller is being held by the user or whether its state has changed from an operating state. Machine learning algorithms may include object detection algorithms, object recognition algorithms, facial recognition algorithms, etc. According to some aspects of this disclosure, the image capture unit 806 may be used to determine whether the computing device 803 should log out of a user account or profile. For example, but not limited to, computing device 803 can analyze an image from image capture unit 806, the image including a user and a controller, but the controller is not in the user's hand or is on a charger. In these cases, computing device 803 can interpret this as an ignored input and maintain connection with the controller. Alternatively, the ignored input can be a series of button presses on controller 802. In some embodiments of this disclosure, there may not be a dedicated ignored input button. Instead, a reprogrammable button, a series of button presses, or multiple simultaneous button presses can be used as an ignored input, wherein the button has other functions when pressed individually or programmed in a different way. In the illustrated example, controller 802 is on charger 801, and computing device 803 analyzes the image captured by image capture unit 806 and determines that there is no user nearby. Therefore, no ignored input has been received and computing device determines that the controller state has changed from an operating state to a charging state. Therefore, computing device 803, according to Figure 5 The method described herein logs out the user account, as indicated at 805. When using an image capture unit, the method currently described for controller operation can be used without dedicated hardware for the controller or charger.

[0039] system

[0040] Figure 9 A system 900 for controller operation and charging according to aspects of this disclosure is illustrated. System 900 may include one or more processors 903, which may be configured according to well-known processor architectures, such as, for example, single-core, dual-core, quad-core, multi-core, processor-coprocessor, unit processor, etc. The market server may also include one or more memories 904 (e.g., random access memory (RAM), dynamic random access memory (DRAM), read-only memory (ROM), etc.).

[0041] Processor 903 can execute one or more programs 917, portions of which can be stored in memory 904, and processor 903 can be operatively linked to memory, for example, via data bus 905. Program 917 can be configured according to the above description. Figure 1 and / or Figure 2 and / or Figure 5 The described method determines the system's operating state 909 in response to a change in controller state 910 detected from controller 902. Operating state 909 may determine whether the system is logged into a user account or profile, or whether the system is in sleep mode or shut down. Operating state may also include status information of the system and applications running on the system. Status information may be loaded along with application 924 to restore the application and / or system. Memory 904 may store the association between user accounts and user-identifiable information or controller identification information 908. Additionally, memory 904 may store historical information 921, which can be analyzed to determine the system's behavior regarding application 924 or the operating state 909 of system 900. Historical information 921 may include application usage information, user account information, usage time information, image information, etc. Memory 904 may store images 926 captured by image capture unit 923 and algorithm 926 to analyze the images and determine whether the user is holding controller 902 or whether controller 902 has changed its state from operating state to charging state. Algorithm 925 can be a machine learning algorithm, such as an object recognition algorithm or a facial recognition algorithm. Applications, historical information, algorithms, associations, operation status, and controller status can also be stored as data 918 in a large-capacity storage area 918.

[0042] System 900 may also include well-known support circuitry such as input / output (I / O) 907, circuitry, power supply (P / S) 911, clock (CLK) 912, and cache memory 913, which may communicate with other components of the system, for example, via data bus 905. The computing device may include a network interface 914. Processor 903 and network interface 914 may be configured to implement a local area network (LAN) or PAN via a suitable network protocol for a personal area network (PAN), such as Bluetooth. The computing device may optionally include a mass storage device 915, such as a disk drive, CD-ROM drive, magnetic tape drive, flash memory, etc., and the mass storage device may store programs and / or data. The system may also include a user interface 916 to facilitate interaction between the system and a user. The user interface may include a display device, such as a monitor, television screen, speaker, headset, or other means of conveying information to the user. The display device may include a visual, audio, or haptic display, or some combination thereof. Controller 902, such as a mouse, keyboard, game controller, joystick, etc., can communicate with the I / O interface and provide the user with control over the system. Additionally, charger 922 can optionally communicate with the system using I / O interface 906. The charger can be a charging pad, charging cable, charging dock, or other device that supplies power to controller 902 to charge the battery within controller 902. Image capture unit, such as a camera, camcorder, or other optical transducer, can optionally communicate with the system using I / O interface 906.

[0043] The controller operation according to aspects of this disclosure can reduce or even eliminate the additional time and effort associated with connecting or disconnecting the controller each time a player wants to use it. While many of the implementations discussed above are applicable to video games, there are potential uses in other applications. For example, a television may run certain task lists depending on input from the charger of a remote controller. Similarly, a multimedia player or set-top box may run certain task lists depending on input from the charger used for a remote controller. Those skilled in the art will be able to design other implementations within the scope of this disclosure.

[0044] While the foregoing is a complete description of preferred embodiments of the invention, various alternatives, modifications, and equivalents may be used. It should be understood that the above description is intended to be illustrative and not restrictive. For example, although the flowcharts accompanying the drawings illustrate a particular sequence of operations performed by certain embodiments of the invention, it should be understood that this sequence is not necessary (e.g., alternative embodiments may perform operations in a different order, combine certain operations, overlap certain operations, etc.). Furthermore, many other embodiments will be apparent to those skilled in the art upon reading and understanding the foregoing description. Although the invention has been described with reference to specific exemplary embodiments, it should be recognized that the invention is not limited to the described embodiments but can be practiced with modifications and variations within the spirit and scope of the appended claims. Therefore, the scope of the invention should be determined by reference to the entire scope of the appended claims together with the equivalents conferred by those claims. Any feature described herein (whether preferred or not) may be combined with any other feature described herein (whether preferred or not). In the following claims, unless expressly stated otherwise, The indefinite articles "A" or "An" This refers to the number of one or more items following the article. The appended claims should not be interpreted as including means plus functional limitations unless such limitation is expressly stated in a given claim using the phrase "means for...".

Claims

1. A method for operating a controller, in a computing device configured to operate together with a controller, the method comprising: The computing device is used to detect the state change of the controller from the charging state to the operating state; In response to detecting the state change of the controller, the state of the computing device is changed from the controller charging state to the controller operating state; The computing device receives input from the controller; The visual instruction for the input is sent to the display device; The computing device is made to automatically log in to the user account associated with the controller; or The application is automatically launched or restored after the state change of the controller is detected.

2. The method of claim 1, further comprising using the computing device to analyze historical or contextual data to determine a user account or application associated with the controller.

3. The method of claim 2, further comprising automatically logging the computing device into a user account or launching an application associated with the controller after detecting the state change of the controller.

4. The method of claim 2, wherein analyzing context data includes using images captured from the image capture unit to determine a user account or application associated with the controller.

5. The method of claim 2, wherein analyzing the context data includes using the timing of the detected controller state changes to determine the user account or application associated with the controller.

6. The method of claim 2, wherein analyzing historical data includes analyzing past application startup information or past account login information.

7. The method of claim 2, wherein analyzing context information includes using controller motion information.

8. The method of claim 1, wherein detecting the state change of the controller includes using charging state information to determine that the state change of the controller is an operation.

9. The method of claim 1, wherein detecting the change in the state of the controller includes using controller motion information.

10. The method of claim 1, wherein detecting the state change of the controller includes using image information from the image capture unit.

11. A system for controller operation, the system comprising: processor; A controller, which is connected to the processor; The memory is coupled to the processor; Non-transitory instructions, which are embedded in memory for enhanced controller operation, include: The processor is used to detect the state change of the controller from the charging state to the operating state. In response to detecting the state change of the controller, the state of the processor is changed from the controller charging state to the controller operating state; The processor receives input from the controller; The visual instruction for the input is sent to the display device; The computing device may automatically log in to the user account associated with the controller; or automatically launch or restore the application after detecting the change in the controller's state.

12. A computer-readable medium having non-transitory instructions embedded thereon, wherein the non-transitory instructions, when executed by a computer, cause the computer to perform a method for controller operation, the method comprising: The computer is used to detect the state change of the controller from the charging state to the operating state. In response to detecting the state change of the controller, the state of the computer is changed from the controller charging state to the controller operating state; The computer receives input from the controller; The visual instruction for the input is sent to the display device; The computing device is enabled to automatically log in to the user account associated with the controller; or The application is automatically launched or restored after the state change of the controller is detected.

Citation Information

Patent Citations

  • Redirecting notifications to a wearable computing device

    US20150130623A1