KR20080069689A - Association of peripherals communicatively attached to a console device - Google Patents

Abstract

Systems and methods for associating a device to a peripheral that is communicating to a game console or computing device. The peripheral is initially bound to a port of the game console or computing device. The device binds to the game console or computing device via an automatic or user-initiated sequence and then correlated to the port assigned to the peripheral. Data that is associated with the peripheral is communicated to the device after being correlated. The device and peripheral may also be associated based on a user profile. When the user signs-in to the game console or computing device, the device is associated to the peripheral via a peripheral identifier and configuration information in the profile.

Description

CONNECTION OF PERIPHERAL DEVICES DESIGNED COMMUNICATELY TO CONSOLE DEVICES

Copyright Notice / Permission

Portions of this patent document disclosure contain copyrighted literature. A copyright owner may not refuse a facsimile copy of a patent document or patent disclosure made by anyone in a patent office file or record, but may otherwise exercise copyright. The following notice shall apply to software and data as described in the text and drawings below, copyrighted by Microsoft Corporation, All Rights Reserved, 2005 (Copyright © 2005, Microsoft Corporation, All Rights Reserved).

Technical field

The present invention generally relates to the field of computing and gaming devices. The present invention is directed to a technique for associating a peripheral device in communication with a console, controller, or other computing device.

Online games have become a significant part of the game experience. Initially, players could communicate via text, but had difficulty entering text during gameplay. After that, it became possible for players to connect with each other in the game and to cooperate by using a voice-only device such as a headset by a centralized server. Many gamers now use headsets designed specifically for this purpose. Traditional headsets are connected to game consoles using, for example, headsets or microphone jacks or USB connectors. Because it is wired to the controller or console, it is relatively easy to associate the sound with the play of a particular gamer.

Gamers can also play games using a wireless controller, which connects wirelessly to the game console, allowing players to move freely. Typically, wireless controllers provide functions such as vibration feedback, mini joysticks, D-pads, pressure sensitive buttons, etc. that players can see in a wired controller. In addition, systems that connect wireless controllers to game consoles often allow multiple players to play simultaneously on the console.

In general, the association of a headset voice with a game controller was accomplished by plugging the wired headset into the jack of a wired or wireless controller. However, if the headset is wireless, there is no physical mechanism to connect the headset to a particular gamer's play or controller because of the nature of the wireless device. In addition, due to the nature of the wireless device, there is no physical mechanism to connect the wireless headset to a particular gamer's play or controller.

Disclosed herein are systems and methods for connecting a device with a peripheral device in communication with a game console or computing device. Peripherals are initially bound to ports on game consoles or computing devices. The peripheral device is bound to the game console or computing device via an automatic or user initiated sequence and then associated with a port assigned to the peripheral device. Data associated with the peripheral device is transferred to the device after being associated. Devices and peripherals may also be connected based on user profiles.

Non-limiting examples of the above are wireless headsets used by gamers during game play. The headset is coupled to the gamer's controller so that game related voice associated with the gamer's play is transmitted from the game console to the headset. Gamers can also use headsets to communicate with other gamers.

Additional features and advantages will be clearly understood with reference to the following embodiments described with reference to the accompanying drawings.

The foregoing description and the detailed description of the preferred embodiment will be better understood when read in conjunction with the accompanying drawings. To illustrate the invention, an exemplary configuration of the invention is shown in the drawings, but the invention is not limited to the specific methods and instrumentalities disclosed.

1 is a block diagram illustrating a game console upon which features of the present invention may be implemented.

2 shows a controller and LED indicators.

3 illustrates one or more controllers / peripherals that are bound and found by a console.

4 is a block diagram of a wireless device.

5 illustrates an example method of performing a connection of a wireless device and a peripheral device.

6-9 illustrate exemplary wireless device designs.

10-11 illustrate alternative methods of performing a connection of a wireless device and a peripheral device.

1 illustrates the functional components of a multimedia / game console 100 in which certain features of the invention may be implemented. Multimedia console 100 includes a central processing unit (CPU) 101 having a primary cache 102, a secondary cache 104, and a flash ROM (read only memory) 106. Primary cache 102 and secondary cache 104 temporarily store data to reduce the number of memory access cycles, thereby improving throughput and throughput. CPU 101 may be provided having one or more cores, and thus additional level 1 and secondary caches 102 and 104. The flash ROM 106 may store executable code that is loaded during the initial stages of the boot process when the multimedia console 100 is powered on.

Graphics processing unit (GPU) 108 and video encoder / video codec (coder / decoder) 114 form an image processing pipeline for high speed and high resolution graphics processing. Data is transferred from the graphics processing unit 108 to the video encoder / video codec 114 via the bus. The image processing pipeline outputs data to the A / V (audio / video) port 140 for television or other displays. The memory controller 110 is coupled to the GPU 108 to allow the processor to access various types of memory 112, such as, but not limited to, random access memory (RAM).

The multimedia console 100 preferably includes an I / O controller 120, a system management controller 122, an audio processing unit 123, a network interface controller 124, a first USB host controller implemented in the module 118. 126, a second USB controller 128 and a front panel I / O subassembly 130. USB controllers 126 and 128 support peripheral controllers 142 (1) -142 (2), wireless adapters 148, and external memory devices 146 (e.g., flash memory, external CD / DVD ROM drives, removable media). Etc.). Note that additional USB controllers may be provided. Network interface 124 and / or wireless adapter 148 provide access to a network (eg, the Internet, home network, etc.) and a wide variety of wireless or wired adapter components, including Ethernet cards, modems, Bluetooth modules, cable modems, and the like. Can be any of

System memory 143 is provided to store application data that is loaded during the boot process. A media drive 144 is provided that may include a DVD / CD drive, hard drive, or other removable media drive. The media drive 144 may be internal or external to the multimedia console 100. Application data may be accessed by multimedia console 100 via media drive 144 for execution, playback, and the like. The media drive 144 is connected to the I / O controller 120 via a bus such as a serial ATA bus or other high speed connection (eg, IEEE 1394).

The system management controller 122 provides various service functions related to ensuring the availability of the multimedia console 100. The speech processing unit 123 and the audio codec 132 form a corresponding speech processing pipeline with high performance and stereo processing. Voice data is transferred between the voice processing device 123 and the audio codec 132 via a communication link. The voice processing pipeline outputs data to the A / V port 140 for duplication by a voice player or device with voice capability.

The front I / O unit 130 supports the power button 150 and the eject button 152, as well as any light emitting diodes (LEDs) that are exposed on the exterior surface of the multimedia console 100, or Other indicators are supported. The system power supply module 106 supplies power to the components of the multimedia console 100. The fan 138 cools the circuitry inside the multimedia console 100.

Various components within CPU 101, GPU 108, memory controller 110, and multimedia console 100 may utilize a serial or parallel bus, a memory bus, a peripheral bus, and a local bus using any of the processor or various bus architectures. It may be interconnected via one or more buses comprising. By way of example, such an architecture may include a Peripheral Component Interconnects (PCI) bus, a PCI-Express bus, and the like.

When the multimedia console 100 is powered on, application data may be loaded from the system memory 143 into the memory 112 and / or caches 102 and 104 and executed on the CPU 101. The application may provide a graphical user interface that is available on the multimedia console 100 to provide a consistent user experience when navigating to different media types. In operation, applications and / or other media mounted within media drive 144 may be started and played back from media drive 144 to provide additional functionality to multimedia console 100.

Multimedia console 100 may operate as a standalone system by simply connecting the system to a television or other display. In this stand-alone mode, the multimedia console 100 allows one or more users to interact with the system, watch movies or listen to music. However, due to the integrated broadband connection made available through the network interface 124 or the wireless adapter 148, the multimedia console 100 can operate as a participant in a larger network community.

When the multimedia console 100 is powered on, a fixed amount of hardware resources are reserved by the multimedia console operating system for use of the system. These resources include securing memory (eg 16 MB), CPU and GPU cycles (eg 5%), and network bandwidth (eg 8 kbps). Since these resources are reserved at system boot time, the resources reserved do not appear to exist from the point of view of the application.

In particular, there is preferably sufficient memory to store the starting kernel, parallel system applications and drivers. If the reserved CPU usage is not used by the system application, the CPU is preferably reserved by a certain amount so that idle threads consume unused cycles.

With respect to GPU acquisition, low volume messages (e.g. popups) generated by the system application are displayed using GPU interrupts that schedule code to render the popups as overlays. The amount of memory required for the overlay depends on the overlay area size and the overlay is preferably sized to fit the screen resolution. If the entire user interface is used by a parallel system application, it is desirable to use a unique resolution independent of the application resolution. A scaler can be used to set this resolution so that the requirement to change the frequency and cause the TV to resynchronize is ignored.

When the multimedia console 100 is booted and system resources are secured, the parallel system application is executed to provide system functions. System functions are encapsulated within a set of system applications running within the secured system resources described above. The operating system kernel identifies the system application thread against the game application thread. The system application is preferably scheduled to run at a predefined time and interval on the CPU 101 to provide a consistent view of system resources to the application. Scheduling can minimize cache disruption for game applications running on the console.

When a parallel system application requires voice, voice processing is scheduled asynchronously to the game application due to time sensitivity. The multimedia console application manager (described below) adjusts the game application voice level (e.g. mute, attenuate) when the system application is running.

Input devices (e.g., controllers 142 (1) and 142 (2)) are shared by the game application and the system application. The input device is not a reserved resource, but between the system application and the game application each focuses the device's focus. The application manager preferably controls switching of the input stream without game application information, and the driver manages state information related to focus switching.

Referring to FIG. 2, an exemplary wireless controller 154 (and an enlarged view thereof) with four quadrant LED indicators 156 and a console 100 with four quadrant indicators 158 are shown. The controller 154 also includes vibration feedback, mini joysticks, pressure sensing buttons, and the like. The game is displayed on screen 160. The console indicator 158 appears in the form of surrounding the power button, although other configurations may be implemented. Each quadrant of the ring can be illuminated by an LED, which can be single or dual colored and can emit multiple colors. As described below, the quadrant can emit light in patterns that indicate notification, system status, binding, and discovery.

In order to support an environment where multiple consoles 100 and wireless controllers 154 coexist, each controller is logically bound to a single console 100 such that only a link with that console 100 is established. Controller 154 may not be bound to more than one console 100 at a time. Binding is a process that allows the console 100 to send information to the controller 154 and allows the controller to establish a link with the console 100. Once bound to the console 100, the controller 154 attempts to establish a link with the bound console 100 each time the power is turned on.

It is desirable that binding information be maintained only within the controller. The binding is one-to-one for the controller 154, but one-to-many for the console 100. Thus, even after a battery discharge / charge cycle, the binding is maintained in the controller 154 until a new binding relationship is established. The establishment of the binding relationship is attempted when the BIND button on the console and the BIND button on the wireless controller 154 are pressed within a predefined time interval. The establishment of a successful binding relationship depends on the establishment of a successful wireless communication link and the execution of a mutual verification algorithm.

The console should be powered on preferably before pressing its binding button. When the user initiates the binding on the controller 154 currently connected to the console 100, the controller 154 disconnects from the console 100 prior to attempting the binding process. As the binding process operates, the status notification screen may display the display binding and discovery process (eg, binding, bound, found). The binding is a one-to-one event. In other words, one controller 154 will be bound at a time by pressing the binding button on console 100. To bind the second controller 154, the binding button on the console is pressed at the second time. If not successfully bound within a predefined time, the console 100 or controller 154 automatically times out and returns to its previous state so that the previous binding relationship is not lost.

There are four (or other numbers) virtual controller ports on the console 100, which are referred to herein as "V ports." The V-port represents a game controller that is connected to the console by wire or wirelessly. The numbered V ports are automatically assigned to the controller in the order in which the controller is connected to the console 100. Each V port is represented by a quadrant of the LED indicator 156 and the console indicator 158. "Discovery" is the process by which a wireless or wired game device is recognized by console 100, assigned a V port, and made available for game play.

Thus, the "binding" and "discovery" operations are preferably two separate operations. The binding operation is initiated by pressing the binding buttons on the controller and the console. Once bound, the controller will begin the discovery process, and if the discovery is successful, the controller will be assigned the first available V port, which in this case is the V port 1. If one to three controllers were previously bound and found, then V ports (2, 3, 4, etc.) will be assigned to the next found controller, respectively. If a total number of controllers equal to the total number of V ports has already been found, the binding process can still be performed, but since there are no more V ports that can be allocated, no V ports will be assigned to the controller. However, if one of the other controllers is powered off or bound to a new console, the controller will also be bound to the console and will be discoverable.

Referring to FIG. 3, a visualization of the binding and discovery process is shown and how the LED indicator 156 and console indicator 158 visually convey this process to the player. As shown in FIG. 3, the controller is powered on and the binding button on the console 100 and the controller is pressed. After the binding process is complete, the discovery process is performed. Since this controller is the first controller found by console 100, it will signal that V port 1 and the upper left quadrants of indicators 156 and 158 are illuminated and connected. If more than one controller has been found by the console 100, the other quadrant of the indicator 158 will subsequently light up. Thus, when two controllers are connected, two quadrants of the indicator 158 will emit light, and for four controllers, four quadrants will emit light. Note that when the quadrants are additionally lit on the console continuously, only a single quadrant is lit for any single controller, except when displaying error conditions or other states to the user.

4, a block diagram of an example wireless device 200 (eg, a headset) is shown. Headset 200 is a wireless device 203, microcontroller (MCU) / digital signal processor (DSP), audio codec 204, input / output device 205, digital to analog converter (DAC) 208, analog to digital converter (ADC) 210, a power supply 212, an input device 214, and an electronic module 202 mounted with a visual indicator 216. Components in the electronic module 203 are connected to the speaker 216 and the microphone 218.

The wireless device 203 may be a frequency hopping spread spectrum (FHHS) wireless device operating in a 2.4 GHz frequency band that transmits data (eg, voice, environment setting, etc.) to the console 100. MCU / DSP / CODEC 204 handles voice communication to or from headset 200. The output voice is delivered to the speaker 216 via the DAC 208. The input voice is received by the microphone 218 and converted into digital information by the ADC 210 and delivered to the MCU / DSP / CODEC 204 for the wireless device 203 for delivery to the console 100.

The input device 214, which will be described in more detail below with reference to FIGS. 6-9, is used to connect the headset 200 with a particular V port. The visual indicator 206 provides an indication or confirmation for the V port connected to the user. As will be described below, voice associated with the user's game play is delivered to / from the headset 200 based on the connection of the headset 200 to the V port assigned to the user's controller 154 or discovered peripherals. do.

As described above, the wireless headset 200 communicates directly with the console 100 without passing through the controller 154. As such, the headset performs binding / discovery similar to controller 154. To accomplish this, the wireless headset 200 is connected to the console and assigned a V port. There are separate V ports for the controller and voice device ports.

5 illustrates the binding and discovery process of the wireless headset 200. In step 220, the user connects (binds) to the console, for example, by pressing a button on the console 100, the wireless controller 154, or the headset 200 (via the input device 214). Preferably, the headset 200 and / or console 100 is powered on after the binding button is pressed, which can advantageously reduce RF emissions. However, in the case of the headset 200, the user may first turn on the headset 200 or the headset 200 may be turned on by pressing a button. Optionally, performing step 220 may be accomplished by placing the headset 200 in the communication range of the console 100. At step 222, console 100 initiates and completes the binding process with headset 200. In step 224, it is determined whether there is one active controller 154. In one case, the same V port as the controller 154 operating in step 226 is assigned to the headset 222.

The user is then notified at step 228 that the connection was successfully completed. The notification can be audio or visual. Acoustic verification of the V-port can be accomplished by sending a chime or tone to the headset. Personalized settings can be ignored / disabled to ensure that chimes or tones are played in the headset. Visual notification may be made by a light emitting LED on the headset (or by other visual indicator 206). If a single LED is provided on the headset, it can emit light at a predefined rate. If several LEDs are provided on the headset, the LED pattern can be emitted. It is preferable to use the same pattern as the connected controller 154 in later scenarios. Further, on-screen display notification can be used. Further, on-screen display notification can be used. If the connection is not successful, a different set of notifications may be used for the successful connection.

However, at step 224, if there is more than one active controller 154, the user is informed by the console 100 to select the V port to which the headset 200 is to be connected. This notification may be performed acoustically or visually via the indicator 206 on the headset 200, through a visual on screen display. Referring now to FIGS. 6-9, the user's V port through an input device 214 such as a dial or jog shuttle (FIG. 6), a slider (FIG. 7), a button (FIG. 8) or a toggle switch (FIG. 9). Selection may be made for. One skilled in the art will recognize that other mechanical input devices may be provided to select the V port.

The visual indicator 206 includes an LED, a seven segment display, etc., to convey to the user which V port was selected on the headset 200. The use of input devices helps to resolve / avoid conflicts between multiple headsets and specific controllers 154. Furthermore, when a plurality of headsets are set to the same V port, it is preferable that the first found headset is assigned a V port. In step 232 the headset 200 is found by the console 100 and connected to the selected V port. In step 234, a notification is provided that the connection is successful. This notification may be similar to that described above.

Alternatively, the method may be performed using an on screen display. The use of an on-screen display is desirable because the on-screen display can be used to set various options for game play, so that the user can feel more familiar and convenient to use the on-screen display. Referring now to FIG. 10, when the user powers on the wireless headset (step 240), an on screen process may begin. Next, the button is pressed on the controller and the user proceeds to the options screen (step 242 and step 244). An “Find Wireless Headset” option may be provided, where the console initiates the binding process with the headset (step 246). The on-screen display can indicate the user to press the bind button on the headset (step 248). The user presses the binding button on the headset and the console completes the binding process to connect the headset to the controller. The headset then notifies the user that binding and connection has completed successfully (step 250).

As another alternative, the user turns on the wireless headset and presses the headset's binding button (steps 240 and 242). These two steps can be performed by pressing the power button once. The user may press a button on the controller to proceed to the options screen (step 244). The user then selects the "Assign Wireless Headset" button from the Options screen (step 252). The console initiates the binding process with the headset and connects the headset to the V port of the controller that initiated the process. The headset and / or on-screen display notifies the user that the binding and connection has been completed successfully (step 250).

The above process can be repeated for all users who want to connect the wireless headset and the controller.

Thus, as described above, the console 100 can manage the connection of the headset to the controller. The headset is bound to the console, thereby allowing management of the headset and other peripherals to be improved over time as the console 100 can be upgraded relatively easily to have new functionality. It is also desirable to have a one-to-one connection between the headset and the controller.

In addition to the binding / discovery notification, the user may be notified that the V port assignment has been lost and / or reconnected. For example, the controller 100 connection should preferably be maintained between power / sleep cycles of the console 100. However, the wireless controller discovery process may reassign V ports after a power cycle. This means that the controller 154 connected to the V port 3 before the power cycle can then be connected to the V port 1. The headset 200 is connected to the V port 1 along the controller 154.

The headset 200 originally connected to the controller 154 is connected to the newly assigned V port along the controller 154. This may be done via a predetermined headset identifier or preferably in the gamer profile used to connect the headset 200 to the controller 154. Thereafter, when the gamer logs in, the profile determines which headset 200 should be connected to the controller 154 via a unique headset identifier 200 associated with the gamer profile. The controller 154 is automatically assigned a V port upon discovery, and the headset 200 is then connected to that V port as described above.

During gameplay, the user may want to use a wired headset. The wireless connection will be interrupted for the wired headset. This is because a wired headset is used according to a user's preference, and it is assumed that accidental insertion of the wired headset does not occur.

In addition to selecting the V port, the headset also includes controls for power on / off, microphone mute, volume up / down, connection to the console, and more. Indicators (eg, LEDs or voice alerts) may be provided for battery level, headset on, and the like. A buzzer or other audible mechanism may be provided to locate the lost headset 200.

Although the process has been described with reference to a wireless controller, the same may apply to the case where a wireless headset is connected to a wired controller.

Although the present invention has been described in connection with the preferred embodiments of the various features, other similar embodiments may be used and modifications and additions may be made to the described embodiments to carry out the same functions without departing from the scope of the invention. You will understand.

Claims (20)

A wireless communication device, A radio in communication with the console; A selector for selecting a port setting used by the wireless communication device associated with a port assigned to a peripheral device by the console; And Indicator to display the port setting Wherein the communication associated with the peripheral device is communicated to the wireless communication device. The method of claim 1, If the peripheral device is the only peripheral device assigned a port by the console, the port setting is automatically assigned to the wireless communication device. The method of claim 1, The selector includes a bind input device, when the binding input device is activated, the wireless communication device is bound to the console, and the console is turned on to discover the wireless communication device. A wireless communication device providing screen display options. The method of claim 1, And the wireless communication device is set to the port setting based on a user profile and an identifier associated with the peripheral device. The method of claim 1, And the notification comprises an audible component. The method of claim 1, And the indicator emits light in a predefined sequence to convey a notification that the wireless communication device has been successfully associated with the peripheral device. The method of claim 1, Communication associated with the peripheral device is communicated between the wireless communication device and the console. A method of establishing a connection between a wireless device and a peripheral device that communicates with a computing device, Initiating a binding sequence; Recognizing and binding the wireless device to the computing device; Setting the wireless device to a port setting associated with a port assigned to a peripheral device; And Transferring data between the wireless device and the computing device, wherein the data is coupled with the peripheral device. The method of claim 8, And automatically assigning the port setting if the peripheral device is the only assigned peripheral device in communication with the computing device. The method of claim 8, Initiating the binding sequence, Receiving input via a binding input device; And Providing an on screen display option to discover the wireless device. The method of claim 10, Setting the wireless communication device to the port setting based on the selected on-screen display option. The method of claim 8, Providing a notification that the wireless device is associated with the peripheral device. The method of claim 12, Illuminating the visual indicator in a predefined order to deliver the notification. The method of claim 8, The setting step further comprises receiving user input via a mechanical input device to set the wireless device to the port setting. The method of claim 8, Establishing communication between a wired device and the computing device; Removing the connection of the wireless device and the peripheral device; And And establishing the connection between the wired device and the peripheral device. The method of claim 7, wherein The setting step, Accessing a user profile; Determining peripheral device settings within the user profile; And Setting the port setting based on the peripheral device setting and the identifier of the peripheral device. A method of establishing a connection between a game controller and a wireless headset that communicates with a game console, Initiating a binding sequence to bind the wireless headset to the game console; Setting the wireless headset to a port setting associated with a port assigned to the game controller; And Delivering voice between the wireless headset and the game console, the voice being coupled to the game controller and a port. The method of claim 17, Initiating the binding sequence, Providing an on screen display option to discover the wireless headset; And Setting the wireless headset to the port setting based on the selected on screen display option. The method of claim 17, Maintaining the wireless device in the game console in an OFF state until the binding sequence is initiated. The method of claim 17, The setting step, Accessing a gamer profile; Determining peripheral device settings within the gamer profile; And Setting the port setting based on the game controller setting and an identifier of the game controller.

Images