The present invention relates to a user input device for an electronic system. In some implementations, the user input device is configured as a video game controller.
A user input device according to some implementations of the present invention may be configured as a video game controller. The user input device may include a plurality of user-actuated controls configured to generate signals which are communicated with an electronic system, such as a computer, cloud-based server, or video game console in order to operate and control the electronic system. The input device may be configured to communicate the signals via a wired connection and/or wirelessly.
In some implementations, an input device according to the present invention may include at least one control pad assembly, for example, a directional control pad (D-pad). In some implementations, the control pad assembly includes a bracket including a support having a bearing surface, a button cap configured to pivot relative to the bracket, the button cap having a peripheral lip and a pivot member configured to abut against the bearing surface of the support, and a return mechanism configured to bias the button cap towards the bracket. In some implementations, the control pad assembly further includes a snap dome film, and the bracket is positioned between the snap dome film and the return mechanism. The snap dome film may be positioned on or against a printed circuit board and be configured to complete an electrical circuit when the button cap is pressed by the user during actuation of the control pad assembly. In some implementations, the button cap further includes one or more contacts which extend toward the snap dome film. The one or more contacts may be configured to push against the snap dome film when the button cap is pivoted with respect to the bracket. In some such implementations, the one or more contacts are sized and positioned to extend below a bottom surface of the bracket.
In some implementations, the return mechanism includes a hub portion positioned at least partially between the button cap and the bracket, and at least a first spring having a fixed end connected to the hub portion and a free end that is configured to deflect relative to the fixed end, the free end being coupled to a first portion of the peripheral lip of the button cap. In some implementations, the hub portion includes a major aperture, and the support of the bracket is received through the major aperture of the hub portion. In some implementations, the fixed end of the first spring is connected to the hub portion by a first arm extending outwardly from the hub portion.
In some implementations, the first spring includes a first spring body between the fixed end and the free end that extends along a first spring axis, and the first arm extends along a first arm axis, and an angle between the first spring axis and the first arm axis is less than 90 degrees (e.g., from 30 degrees to 60 degrees). In some implementations, the bracket includes a first arm support, and wherein at least a portion of the first arm is disposed between the first arm support and the button cap. In some implementations, the first arm includes a minor aperture, and the first arm support includes a post received through the minor aperture of the first arm. In further implementations, the hub portion includes a top surface, and an angle between the first spring axis and a plane of the top surface is greater than 0 degrees when the free end of the first spring is coupled to the peripheral lip of the button cap.
In further implementations, the return mechanism may include a plurality of springs. In some such implementations, the return mechanism may include at least a second spring having a fixed end connected to the hub portion and a free end that is configured to deflect relative to the fixed end of the second spring, the free end of the second spring being coupled to a second portion of the peripheral lip of the button cap. In some implementations, the return mechanism includes at least a third spring having a fixed end connected to the hub portion and a free end that is configured to deflect relative to the fixed end of the third spring, the free end of the third spring being coupled to a third portion of the peripheral lip of the button cap. In yet further implementations, the return mechanism includes at least a fourth spring having a fixed end connected to the hub portion and a free end that is configured to deflect relative to the fixed end of the fourth spring, the free end of the fourth spring being coupled to a fourth portion of the peripheral lip of the button cap. The button cap, in some implementations, includes four or more lobes and each of the first portion, second portion, third portion, and fourth portion of the peripheral lip are located on a different lobe of the button cap.
A battery assembly which may be used with an input device according to various implementations of the present invention includes a battery pack containing one or more cells, the battery pack having a top surface and a bottom surface, a first foam layer coupled to the bottom surface of the battery pack, a battery bracket positioned over the top surface of the battery pack, and a first adhesive layer disposed between the top surface of the battery pack and the battery bracket. In some implementations, the first adhesive layer is or includes a pressure sensitive adhesive (PSA). In some implementations, the first adhesive layer has an area that is less than an area of the top surface of the battery pack. In some implementations, the first adhesive layer includes one or more windows. In some implementations, the first adhesive layer does not cover a central portion of the top surface of the battery pack. In some implementations, the battery pack includes at least two cells. In some such implementations, the battery assembly includes a second adhesive layer disposed between the at least two cells of the battery pack. In some implementations, the battery pack includes a housing surrounding the at least two cells and at least one internal foam member disposed within the housing. The at least one internal foam member may be positioned on or around at least one of the at least two cells.
In still further implementations, the first foam layer has an area that is less than an area of the bottom surface of the battery pack. In some implementations, the first foam layer comprises one or more foam strips. In some implementations, the battery assembly includes a second foam layer positioned on an external surface of the bracket. In some implementations, the second foam layer includes one or more foam strips. In some implementations, the battery assembly further includes an insulator disposed at least partially around the bracket. In some such implementations, the insulator includes one or more cutouts that are sized and shaped to receive the foam strips of the second foam layer.
For a better understanding of the various described implementations, reference should be made to the Description of Implementations below, in conjunction with the following drawings in which like reference numerals refer to corresponding parts throughout the figures.
Reference will now be made in detail to implementations, examples of which are illustrated in the accompanying drawings. In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the various described implementations. However, it will be apparent to one of ordinary skill in the art that the various described implementations may be practiced without these specific details. In other instances, well-known methods, procedures, components, circuits, and networks have not been described in detail so as not to unnecessarily obscure aspects of the implementations.
In some implementations, input device 100 is shaped and sized to be held by one or both hands of a user. Input device includes a housing 102 which, in some implementations, may be made from two or more pieces which are joined together. For example, housing 102 may include a top housing 102a and a bottom housing 102b which are secured together to form housing 102 which surrounds and encloses internal components of input device 100. In some implementations, housing 102 is shaped to include one or more grips that are sized and configured to be held by a user's palm and/or fingers. As shown in the illustrated example, input device 100 includes a left grip 104 intended to be held in a user's left hand, and a right grip 106 intended to be held by the user's right hand.
Input device 100 includes one or more controls configured to receive the user input. In some implementations, input device includes a plurality of controls that are configured to be physically actuated or toggled by the user, for example, one or more buttons, control sticks, and/or triggers, etc. In some implementations, input device 100 includes at least one directional control pad assembly 108, which may also be referred to as a “D-pad,” that extends through top housing 102a. In some implementations, directional control pad assembly 108 may be a multi-way directional control configured to be operated by a user's thumb, e.g., the user's left thumb while left grip 104 is positioned in the user's left hand. In some such implementations, direction control pad assembly 108 includes a separate button for each directional control. In some implementations, directional control pad assembly 108 is a four-way directional control. In other implementations, directional control pad assembly 108 is an eight-way directional control. In some implementations, input device 100 may include at least one control stick, for example, left and right control sticks 110a, 110b, which extend through top housing 102a. Left and right control sticks 110a, 110b may each be a thumb-operated analog stick which can be pivoted by the user, and wherein input is based on the direction and/or magnitude that the control stick is pivoted in relation to a default center position. In some implementations, for example, each of left and right control sticks may be pivoted in any direction up to 18 degrees to 22 degrees away from the center position. In some implementations, each of left and right control sticks 110a, 110b may be biased toward their respective default center positions by a biasing force such that the user must apply a force greater than the biasing force in order to pivot the control stick.
In further implementations, input device 100 may include a plurality of buttons, for example, action buttons 112 (e.g., “A,” “B,” “X,” and “Y” buttons) which may be positioned to be pressed by a user's right thumb or fingers. Input device 100 may also include one or more function buttons 114 which may include, for example, a selection button, an option button, an assistant button, and/or a share button. Each of such function buttons 114, when pressed, may activate a different function or feature in the electronic system. Input device 100, in some implementations, may also include a separate home button 116. In some implementations, function buttons 114 may be positioned between directional control pad 108 and action buttons 112 and home button 116 may be positioned between left and right control sticks 110a, 110b. Action buttons 112, function buttons 114, and/or home button 116 may each extend through top housing 102a. In some implementations, each of action buttons 112, function buttons 114, and/or home button 116 may include a button cap having a top surface with a different symbol, character, color, design, texture, and/or logo that may be representative of the button's purpose. In some implementations, the symbol, character, color design, texture, and/or logo may be painted/coated, molded, or etched onto the button, for example. In some implementations, the symbol, character, color design, texture, and/or logo is formed from a different material than the rest of the button cap. In further implementations, one or more of action buttons 112, function buttons 114, and/or home button 116 may be illuminated, for example, by a light-emitting diode (LED) positioned beneath or within the button.
In yet further implementations, input device 100 may include one or more triggers and/or one or more bumper buttons positioned at a front of input device 100. In some such implementations, input device includes a left trigger 118a and/or a right trigger 118b, which are configured to be pivoted from a default position to actuate, and may include a biasing device (e.g., spring) configured to bias the triggers to the default position. Input device 100 may also include left and right bumper buttons 120a, 120b which are positioned above left and right triggers 118a, 118b, respectively. In some implementations, input device 100 includes a data port 122, for example, a USB port configured to receive a USB cable. Data port 122 may be positioned on a front portion of input device 100 and, in some implementations, may be located centrally between left and right bumper buttons 120a, 120b. In some implementations, input device 100 further includes a microphone port 124 for receiving audio signals, and an audio jack 126 for connecting to an audio output device (e.g., headphones), each of which may be positioned or a rear portion of input device 100.
With reference to
In some such implementations, button assembly 128 is mounted onto a mid-frame 132 which is positioned between button assembly 128 and main printed circuit board 134. Mid-frame 132, in some implementations, may be rigidly constructed to provide support for the internal components of input device 100 and/or housing 102. Main PCB 134 includes, in some implementations, one or more processors, communication modules, wireless transmitters/receivers, memory devices, and/or other circuitry for operating input device 100. In some implementations, a ribbon connector 136 electronically connects PCB 130 to main PCB 134 such that signals received from operation of the buttons of button assembly 128 can be conveyed to main PCB 134. In some implementations, left and right control sticks 110a, 110b may be mounted onto and electrically connected to main PCB 134. PCB 130 and mid-frame 132, in some implementations, may be shaped or contoured to provide clearance for the left and right control sticks 110a, 110b. In some implementations, input device 100 further includes one or more rumble motors 138a, 138b which are configured to vibrate in response to certain signals to create a tactile sensation for the user. Rumble motors 138a, 138b may be positioned within left and right grips 104, 106, respectively and be at least partially surrounded by mid-frame 132. In some implementations, rumble moters 138a, 138b may be sandwiched between mid-frame 132 and bottom housing 102b. As shown in
Directional Control Pad Assembly
In further implementations, directional control pad assembly 108 further includes a button cap 152 which is configured to pivot relative to bracket 142. Button cap 152 may have a multi-lobe shape, for example, a plus-shape or a quatrefoil shape with four lobes. In some implementations, button cap 152 may have fewer or more than four lobes. Each lobe of button cap 152 may act as a separate button representing a different direction (e.g., up, down, left, right). In some implementations, button cap 152 includes a pivot member 154 (
In some implementations, directional control pad assembly 108 further includes a return mechanism 162 configured to bias button cap 152 towards bracket 142. In some implementations, return mechanism 162 is configured to bias button cap 152 to a default position when directional control pad assembly 108 is not being actuated by the user. In some implementations, return mechanism 162 includes a hub portion 164 positioned at least partially between button cap 152 and bracket 142. Return mechanism 162 includes one or more springs 166, each spring 166 having a fixed end 168 connected to hub portion 164 and a free end 170 that is configured to deflect relative to the fixed end 168. In some implementations, each spring 166 is configured as a cantilever spring. In some implementations, free end 170 of each spring 166 is coupled to a portion of the peripheral lip 156 of button cap 152. In some implementations, return mechanism 162 includes at least one spring 166 for each lobe of button cap 152. In some implementations, each free end 170 of springs 166 is coupled to a different tab 158 of button cap 152. In some implementations, coupling of free end 170 to a tab 158 of button cap 152 causes the free end 170 to deflect relative to the fixed end 168 of the spring 166. In some implementations, hub portion 164 includes a generally planar top surface, and an angle between the spring 166 and a plane of the top surface is greater than 0 degrees when the free end 170 of the spring 166 is coupled to the peripheral lip 156 of button cap 152. In some implementations, each fixed end 168 is connected to the hub portion 164 by an arm 172 extending outwardly from the hub portion 164. In some implementations, as shown in
In some implementations, hub portion 164 of return mechanism 162 includes a main aperture 174. In some such implementations, support 144 of bracket 142 is received through main aperture 174. In some implementations, pivot member 154 of button cap 152 is received through main aperture 174. In some implementations, main aperture 174 is centrally positioned on hub portion 164. In some implementations, one or more of arms 172 includes a further minor aperture 176 which is shaped and sized to receive a post 150 of bracket 142. In some implementations, posts 150 received through further apertures 176 help prevent return mechanism 162 from rotating with respect to bracket 142. Minor aperture 176 may be smaller in dimension (e.g., diameter) than main aperture 174 according to some implementations. In some implementations, as shown in
Battery Assembly
In some implementations, battery assembly 140 further includes a bracket 190 which surrounds at least a portion of battery pack 180. In some implementations, bracket 190 is configured to help physically protect battery pack 180. In some implementations, bracket 190 acts a heat spreader for dissipating heat from battery pack 180. In some implementations, bracket 190 may be used to secure battery assembly 140 to bottom housing 102b via, for example, one or more screws 192. In some implementations, bracket 190 is positioned between battery pack 180 and main PCB 134. Disposed between bracket 190 and battery pack 180 may be an adhesive layer 194. Adhesive layer 194 may be positioned on a top surface of battery pack 180 and may include a PSA. In some such implementations, adhesive layer 194 has an area that is less than an area of the top surface of the battery pack 180. In some implementations, adhesive layer 194 is shaped and sized so as not to cover a central portion of the top surface of battery pack 180. In some implementations, adhesive layer 194 may be shaped to have a window or opening 196 as illustrated. Window or opening 196, according to some implementations, provides further clearance to allow for expansion of battery pack 180 during use. In some implementations, window or opening 196 is positioned to overlay a central portion of the top surface of battery pack 180. In other implementations, adhesive layer 194 may include two or more separate strips of PSA that are spaced apart by one or more gaps.
In some implementations, battery assembly 140 may include a bottom foam layer 198 coupled to the bottom surface of the battery pack 180. In some implementations, bottom foam layer 198 is positioned between battery pack 180 and bottom housing 102b. In some implementations, the bottom foam layer 198 has an area that is less than an area of the bottom surface of battery pack 180. In some implementations, bottom foam layer 198 includes one or more foam strips or blocks. In some such implementations, bottom foam layer 198 includes at least two foam strips or blocks that are separated by a gap.
In yet further implementations, battery assembly 140 may include a top foam layer 200 coupled to a top surface of bracket 190. In some implementations, top foam layer 200 is positioned between bracket 190 and a bottom surface of main PCB 134. In some implementations, top foam layer 200 is configured to provide spacing between main PCB 134 and bracket 190 to ensure that main PCB 134 does not make direct contact with bracket 190. Furthermore, in some implementations, spacing bracket 190 away from main PCB 134 can help in dissipating heat from battery assembly 140. In some implementations, top foam layer 200 has an area that is less than an area of the top surface of bracket 190. In some implementations, top foam layer 200 includes one or more foam strips or blocks. In some such implementations, top foam layer 200 includes at least two foam strips or blocks that are separated by a gap.
Battery assembly, in some implementations, may also include a bracket insulator 202. In some embodiments, bracket insulator 202 is disposed between bracket 190 and main PCB 134. Bracket insulator 202, in some embodiments, prevents main PCB 134 from contacting bracket 190. In some implementations, bracket insulator 202 is positioned on and around at least a top portion of bracket 190. In some such implementations, bracket insulator 202 includes cutouts or openings 204 which are sized and shaped to allow the foam strips or blocks of top foam layer 200 to extend through bracket insulator 202 when bracket insulator 202 is positioned around bracket 190, as depicted in
Trigger and Bumper Button Assembly
Input device 100, in some implementations, includes left and right triggers 118a, 118b and may further include left and right bumper buttons 120a, 120b. As shown in the
In some implementations, left and right triggers 118a, 118b are each configured to be rotated from an unactuated default position toward bottom housing 102b during actuation (e.g., as shown by the arrow in
In some implementations, left and right triggers 118a, 118b may be pivotally mounted onto a front portion of mid-frame 132.
In some implementations, each trigger 118a, 118b may include a magnet 212 which is configured to interact with a sensor that is configured to sense a position of magnet 212. Magnet 212 may be, for example, a rare earth magnet (e.g., neodymium magnet). Magnet 212 may be positioned within a housing 210 which rigidly extends from a rear of each trigger 118a, 118b. Housing 210 may define a chamber which is sized to receive magnet 212. Magnet 212 may be secured within the chamber, for example, using an adhesive or mechanical fastener. With particular reference to
Referring now to
In some implementations, left and right bumper button 120a, 120b are connected by a beam 220 which is positioned to extend along a front portion of main PCB 134 and/or mid-frame 132. In some implementations, beam 220 is bendable and includes one or more flexion points to provide a hinge motion for bumper buttons 120a, 120b. In some implementations, left and right bumper buttons 120a, 120b and beam 220 are formed as a single component which may reduce complexity of manufacture and help maintain the position of the component with input device 100.
Microphone Assembly
As discussed with regards to
Button Construction
In some implementations, home button 116 includes a light pipe 242 housed within button cap 240, and which may be constructed from a different material and/or have a different color than button cap 240. In some implementations, light pipe 242 may be shaped to line an internal surface of button cap 240. In some implementations, light pipe 242 may be made from a material configured to transmit visible light, whereas button cap 240 may be made from an opaquer material. In some implementations, light pipe 242 is configured to transmit at least a portion of light from a light source 248 (e.g., LED) positioned below or within home button 116 to opening 240b of button cap 240. In some implementations, light pipe 242 may be made from a transparent or translucent plastic material, for example, acrylonitrile butadiene styrene (ABS). In some implementations, light pipe 242 may include a light scattering material or light scattering texture in at least a portion of light pipe 242. In some implementations, light pipe 242 includes a top portion 242a which is shaped and sized to fit within opening 240b of button cap 240. In some implementations, top portion 242a may be shaped and sized to match and completely fill opening 240b and be flush with top surface 240a. Top portion 242a may include a light scattering material or have a light scattering texture such that top portion 242a appears illuminated or glowing when light source 248 is emitting light. As shown in the illustrated example, top portion 242a is in the shape of a “home” symbol which is configured to match and fit within the “home” symbol opening 240b of button cap 240. In some implementations, for example, light pipe 242 and button cap 240 may be formed together by double injection or double-shot molding such that the two layers of plastic are molded into each other. In other implementations, light pipe 242 and button cap 240 may be separate formed and fitted together.
In some implementations, home button 116 may further include a deformable web 244 upon which button cap 240 and/or light pipe 242 may be mounted. Web 244, in some implementations, is made from an elastic and/or resilient material, for example, silicone, and is disposed between light pipe 242 and PCB 130. In some implementations, web 244 is configured to bias light pipe 242 and button cap 240 away from PCB 130. When a user presses upon home button 116 according to some implementations, the user's force against button cap 240 may overcome the biasing force of web 244 such that web 244 deforms to allow button contact 246 of home button 116 to contact PCB 130 and complete a circuit to generate a signal. Button contact 246 may be, for example, a carbon pill which acts as a switch contact and be secured to a bottom of web 244 and/or light pipe 242. In some implementations, button contact 246 and web 244 may be annular or ring shaped to allow light from light source 248 to pass through. While the discussion of
Further Components and Modules
In some implementations, input device 100 may include one or more output device(s) 318 that facilitate audio output and/or visual output, including speaker(s) 320, LED(s) 322, and/or optionally, a display 324. The input device 100, in some implementations, includes a location detection unit 334, for example, a GPS (global positioning satellite) or other geo-location receiver, for determining the location of the input device 100. The input device 100 may further include a proximity detection unit 332, e.g., an IR sensor, for determining a proximity of an interface device and/or of other input devices 100 and/or electronic devices. The input device 100 may also include one or more sensor(s) 328 (e.g., accelerometer, gyroscope, etc.) for sensing motion, orientation, and other parameters of the input device 100, which may be used as input. In some implementations, input device 100 includes an optional headset 326 which plays back audio messages and/or gaming audio streams.
In some implementations, the input device 100 includes radios 330 that enable one or more communication networks and allow the input device 100 to communicate with other devices (e.g., with an interface device). In some implementations, the radios 330 are capable of data communications using any of a variety of custom or standard wireless protocols (e.g., IEEE 802.15.4, Wifi, ZigBee, 6LoWPAN, Thread, Z-Wave, Bluetooth Smart, ISA100.5A, WirelessHART, MiWi Whispernet, Bluetooth low energy etc.), custom or standard wired protocols (e.g., Ethernet, HomePlug etc.), and/or other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document.
The memory 306, in some implementations, includes high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid state memory devices; and, optionally, includes non-volatile memory, such as one or more magnetic disk storage devices, one or more optical disk storage devices, one or more flash memory devices, or one or more other non-volatile solid state storage devices. The memory 306, optionally, includes one or more storage devices remotely located from one or more processing units 302. The memory 306, or alternatively the non-volatile memory within the memory 306, includes a non-transitory computer readable storage medium. In some implementations, the memory 306, or the non-transitory computer readable storage medium of the memory 306, stores the following programs, modules, and data structures, or a subset or superset thereof:
In some implementations, the communication module 351 can be one or more of a radio transmission module, a communication bus, such as the one or more communication buses 308, and a wired connection.
In some implementations, the controller module 350 is a part (e.g., a sub-module) of the interface device application 334 or another application in the memory 306. In some other implementations, the controller module 350 is a part of the operating system 336. In some further implementations, the controller module 350 is a distinct module or application.
Each of the above identified elements may be stored in one or more of the previously mentioned memory devices, and corresponds to a set of instructions for performing a function described above. The above identified modules or programs (i.e., sets of instructions) need not be implemented as separate software programs, procedures, modules or data structures, and thus various subsets of these modules may be combined or otherwise re-arranged in various implementations. In some implementations, memory 306, optionally, stores a subset of the modules and data structures identified above. Furthermore, memory 306, optionally, stores additional modules and data structures not described above.
While certain implementations of the present invention discussed herein are illustrative of input devices that may be useful for video game controllers, the input devices and the components thereof described herein are not necessarily limited to this particular use. Input devices according to implementations of the present invention may also include, for example, remote controls for televisions, audio systems, robots, remotely operated vehicles, unmanned aerial vehicles, or other electronic systems. Furthermore, elements described herein, such as the battery assembly, directional control pad assembly, microphone assembly, triggers, buttons, etc. are not restricted to use in input devices, and such elements may be used in other devices, for example, switches, mobile phones, computers, cameras, audio equipment, or other electronic devices.
The terminology used in the description of the various described implementations herein is for the purpose of describing particular implementations only and is not intended to be limiting. As used in the description of the various described implementations and the appended claims, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term “and/or” as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms “includes,” “including,” “comprises,” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
The foregoing description, for purpose of explanation, has been described with reference to specific implementations. However, the illustrative discussions above are not intended to be exhaustive or to limit the scope of the claims to the precise forms disclosed. Many modifications and variations are possible in view of the above teachings. The implementations were chosen in order to best explain the principles underlying the claims and their practical applications, to thereby enable others skilled in the art to best use the implementations with various modifications as are suited to the particular uses contemplated.
Number | Date | Country | Kind |
---|---|---|---|
PCT/US2019/002472 | Mar 2019 | WO | international |
This application is a U.S. National Stage application under 35 U.S.C. § 371 of International Patent Application Serial No. PCT/US 2019/025400, entitled “Input Device for an Electronic System,” and filed on Apr. 2, 2019, which claims priority to U.S. Provisional Patent Application No. 62/779,794, filed on Dec. 14, 2018 and entitled, “Input Device for an Electronic System,” to U.S. Provisional Patent Application No. 62/651,542, filed on Apr. 2, 2018 and entitled, “Methods, Devices, and Systems for Interactive Cloud Gaming,” and to International Application No. PCT/US2019/022472, filed on Mar. 15, 2019 and entitled, “Methods, Devices, and Systems for Interactive Cloud Gaming,” each of which is incorporated herein by reference in its entirety.
Filing Document | Filing Date | Country | Kind |
---|---|---|---|
PCT/US2019/025400 | 4/2/2019 | WO |
Publishing Document | Publishing Date | Country | Kind |
---|---|---|---|
WO2019/195300 | 10/10/2019 | WO | A |
Number | Name | Date | Kind |
---|---|---|---|
5948559 | Snyder | Sep 1999 | A |
6855058 | Kubota et al. | Feb 2005 | B2 |
7401150 | Shea et al. | Jul 2008 | B2 |
7774440 | Bagrodia | Aug 2010 | B1 |
8171145 | Allen et al. | May 2012 | B2 |
8215483 | Wakitani et al. | Jul 2012 | B2 |
8619588 | Karacali-Akyamac | Dec 2013 | B2 |
8621585 | Danieli et al. | Dec 2013 | B2 |
8641531 | Patil | Feb 2014 | B2 |
8979647 | Ostergren et al. | Mar 2015 | B2 |
9339733 | Boudville | May 2016 | B2 |
9393486 | George | Jul 2016 | B2 |
9396702 | Colenbrander | Jul 2016 | B2 |
9498711 | Assa | Nov 2016 | B2 |
9526989 | Oh | Dec 2016 | B2 |
9592446 | Bono et al. | Mar 2017 | B2 |
9675874 | Park | Jun 2017 | B1 |
9912562 | Callahan et al. | Mar 2018 | B2 |
10166471 | Vincent et al. | Jan 2019 | B2 |
10244765 | Pierce et al. | Apr 2019 | B2 |
10255765 | Washington et al. | Apr 2019 | B2 |
10456672 | Champy | Oct 2019 | B2 |
11128636 | Jorasch et al. | Sep 2021 | B1 |
20010023816 | Kuriyama | Sep 2001 | A1 |
20040198403 | Pedersen et al. | Oct 2004 | A1 |
20050074063 | Nair et al. | Apr 2005 | A1 |
20060154710 | Serafat | Jul 2006 | A1 |
20060287096 | O'Kelley et al. | Dec 2006 | A1 |
20060287099 | Shaw et al. | Dec 2006 | A1 |
20070018980 | Berteig et al. | Jan 2007 | A1 |
20080220878 | Michaelis | Sep 2008 | A1 |
20090008404 | Kim et al. | Jan 2009 | A1 |
20090125961 | Perlman et al. | May 2009 | A1 |
20090271656 | Yokota et al. | Oct 2009 | A1 |
20100167809 | Perlman et al. | Jul 2010 | A1 |
20100203952 | Zalewski | Aug 2010 | A1 |
20100306813 | Perry | Dec 2010 | A1 |
20100317443 | Cook et al. | Dec 2010 | A1 |
20110124417 | Baynes et al. | May 2011 | A1 |
20110145635 | Buckler et al. | Jun 2011 | A1 |
20120004042 | Perry et al. | Jan 2012 | A1 |
20120079080 | Pishevar | Mar 2012 | A1 |
20120209571 | Peterson et al. | Aug 2012 | A1 |
20120270644 | Buhr | Oct 2012 | A1 |
20120306877 | Rosasco | Dec 2012 | A1 |
20130034160 | Schmit | Feb 2013 | A1 |
20130198642 | Carney et al. | Aug 2013 | A1 |
20130221923 | Robertson | Aug 2013 | A1 |
20130274000 | Novotny et al. | Oct 2013 | A1 |
20140006517 | Hsiao et al. | Jan 2014 | A1 |
20140019582 | Kim | Jan 2014 | A1 |
20140032670 | Ellingson et al. | Jan 2014 | A1 |
20140179426 | Perry et al. | Jan 2014 | A1 |
20140043333 | Narayanan et al. | Feb 2014 | A1 |
20140179434 | Xu | Jun 2014 | A1 |
20140221087 | Huang et al. | Aug 2014 | A1 |
20140274384 | Boswell et al. | Sep 2014 | A1 |
20140342819 | Bruno, Jr. et al. | Nov 2014 | A1 |
20150009222 | Diard et al. | Jan 2015 | A1 |
20150087414 | Chen et al. | Mar 2015 | A1 |
20150297998 | Karamfilov et al. | Oct 2015 | A1 |
20160001184 | Sepulveda et al. | Jan 2016 | A1 |
20160028854 | Leeb et al. | Jan 2016 | A1 |
20160171757 | Panneer et al. | Jun 2016 | A1 |
20160279523 | Altagar et al. | Sep 2016 | A1 |
20160293134 | Fortin | Oct 2016 | A1 |
20160317921 | Schmitz | Nov 2016 | A1 |
20170034234 | Zimring et al. | Feb 2017 | A1 |
20170083396 | Bishop et al. | Mar 2017 | A1 |
20170097816 | Joshi | Apr 2017 | A1 |
20170124812 | Washington et al. | May 2017 | A1 |
20170142201 | Holmes | May 2017 | A1 |
20170185464 | Lipinski et al. | Jun 2017 | A1 |
20170246544 | Agarwal et al. | Aug 2017 | A1 |
20170354878 | Posin | Dec 2017 | A1 |
20170354893 | Benedetto et al. | Dec 2017 | A1 |
20180176282 | Benguerah | Jun 2018 | A1 |
20180229128 | Chandrasekaran et al. | Aug 2018 | A1 |
20180250591 | Prado Rojas et al. | Sep 2018 | A1 |
20180253880 | Yeh et al. | Sep 2018 | A1 |
20180256981 | Enomoto | Sep 2018 | A1 |
20190199722 | Pennarun et al. | Jun 2019 | A1 |
20190259130 | Yeh et al. | Aug 2019 | A1 |
20190272707 | Washington et al. | Sep 2019 | A1 |
20190308099 | Lalonde et al. | Oct 2019 | A1 |
20190321725 | Zimring et al. | Oct 2019 | A1 |
20190321727 | Rodgers | Oct 2019 | A1 |
20190321732 | Zimring et al. | Oct 2019 | A1 |
20190344163 | Imada | Nov 2019 | A1 |
20200001177 | Champy | Jan 2020 | A1 |
20200111317 | Oberberger et al. | Apr 2020 | A1 |
20210146240 | Colenbrander | May 2021 | A1 |
Number | Date | Country |
---|---|---|
101068258 | Nov 2007 | CN |
103904263 | Jul 2014 | CN |
106328855 | Jan 2017 | CN |
107050858 | Aug 2017 | CN |
107269307 | Oct 2017 | CN |
107666943 | Feb 2018 | CN |
0632475 | Jan 1995 | EP |
1374959 | Jan 2004 | EP |
2546811 | Jan 2013 | EP |
3610933 | Feb 2020 | EP |
2331850 | Feb 1999 | GB |
2525437 | Oct 2015 | GB |
2003236251 | Aug 2003 | JP |
2014130589 | Jul 2014 | JP |
2015139565 | Aug 2015 | JP |
20070082395 | Aug 2007 | KR |
20070082395 | Aug 2007 | KR |
0003407 | Jan 2000 | WO |
2005010680 | Feb 2005 | WO |
2008104221 | Apr 2008 | WO |
2012161102 | Nov 2012 | WO |
2012170437 | Dec 2012 | WO |
2014085717 | Jun 2014 | WO |
2014120369 | Aug 2014 | WO |
2014186858 | Nov 2014 | WO |
2015039583 | Mar 2015 | WO |
2015191965 | Dec 2015 | WO |
2016183253 | Nov 2016 | WO |
2017007659 | Jan 2017 | WO |
2017201472 | Nov 2017 | WO |
2019074952 | Apr 2019 | WO |
2019182752 | Sep 2019 | WO |
2019195300 | Oct 2019 | WO |
2020102493 | May 2020 | WO |
Entry |
---|
Notice of Allowance dated Jul. 29, 2022 for U.S. Appl. No. 17/123,523, 6 pages. |
Notice of Allowance dated Oct. 27, 2022 for Korean Patent Application No. 10-2020-7030955, 4 pages. |
Notice of Allowance dated Jun. 29, 2022 for U.S. Appl. No. 17/123,523, 6 pages. |
Translation of Korean Office Action dated Apr. 14, 2022 for Korean Application No. 10-2020-7030955, 19 pages. |
European Communication pursuant to Article 94(3) EPC dated Mar. 20, 2023 for EP Application No. 19717207.5, 4 pages. |
English Translation of Chinese Office Action dated May 21, 2021 for CN Application No. 20198029685.3, 15 pages. |
Yoneda, Satoshi, “Completed Understanding of Windows 8 as a Game Environment (6) Windows Store App Version Game and Xbox Smart Glass,” Oct. 30, 2012; 22 pages; accessed on Aug. 5, 2020 from https://www.4gamer.net/games/126/G012689/20121029010/. |
Extended European Search Report dated Jan. 3, 2020 for EP Application No. EP 19199853.3, 10 pages. |
Notice of Grant dated Nov. 5, 2019 for JP Application No. JP 2019220516, 7 pages. English machine translation included. |
English Translation of Korean Notice of Allowance dated Jan. 28, 2020 for KR Application No. KR 10-2018-7023961, 3 pages. |
English Translation of Korean Office Action dated Apr. 15, 2019 for KR Application No. KR 10-2018-7023961, 2 pages. |
English Translation of Korean Office Action dated Aug. 18, 2018 for KR Application No. KR 10-2020-7002403, 5 pages. |
International Preliminary Report on Patentability dated Apr. 24, 2018 for International Application No. PCT/US2017/033642, 13 pages. |
International Search Report and Written Opinion dated Sep. 18, 2017 for International Application No. PCT/US2017/033642, 28 pages. |
First Action Interview Office Action Summary dated Feb. 26, 2019 for U.S. Appl. No. 15/599,408, 3 pages. |
First Action Interview Pilot Program Pre-Interview Communication dated Jan. 8, 2019 for U.S. Appl. No. 15/599,408, 4 pages. |
Notice of Allowance dated Jun. 19, 2019 for U.S. Appl. No. 15/599,408, 6 pages. |
Non-Final Office Action dated Jun. 12, 2020 for U.S. Appl. No. 16/566,607, 23 pages. |
Final Office Action dated Oct. 16, 2020 for U.S. Appl. No. 16/566,607, 18 pages. |
International Search Report and Written Opinion dated Feb. 26, 2019 for International Application No. PCT/US2018/066844, 13 pages. |
Non-Final Office Action dated May 15, 2020 for U.S. Appl. No. 15/851,610, 15 pages. |
Final Office Action dated Nov. 30, 2020 for U.S. Appl. No. 15/851,610, 33 pages. |
International Search Report and Written Opinion dated Feb. 24, 2020 for International Application No. PCT/US2019/061407, 13 pages. |
International Preliminary Report on Patentability dated Apr. 14, 2020 for International Application No. PCT/US2018/055055, 13 pages. |
International Search Report and Written Opinion dated Apr. 26, 2019 for International Application No. PCT/US2018/055055, 21 pages. |
International Search Report and Written Opinion dated Oct. 4, 2019 for International Application No. PCT/US2019/025182, 23 pages. |
International Preliminary Report on Patentability dated Oct. 15, 2020 for International Application No. PCT/US2019/025182, 18 pages. |
First Action Interview Pilot Program Pre-Interview Communication dated Apr. 9, 2020 for U.S. Appl. No. 16/368,801, 4 pages. |
Notice of Allowance dated Jun. 10, 2020 for U.S. Appl. No. 16/368,801, 12 pages. |
International Search Report and Written Opinion dated Jun. 18, 2019 for International Application No. PCT/US2019/025185, 11 pages. |
International Preliminary Report on Patentability dated Oct. 15, 2020 for International Application No. PCT/US2019/025185, 7 pages. |
Notice of Allowance dated May 5, 2020 for U.S. Appl. No. 16/368,806, 8 pages. |
International Search Report and Written Opinion dated Jun. 18, 2019 for International Application No. PCT/US2019/022472, 13 pages. |
International Preliminary Report on Patentability dated Oct. 15, 2020 for International Application No. PCT/US2019/022472, 8 pages. |
Non-Final Office Action dated Jun. 22, 2020 for U.S. Appl. No. 16/373,558, 6 pages. |
Notice of Allowance dated Sep. 17, 2020 for U.S. Appl. No. 16/373,558, 9 pages. |
International Search Report and Written Opinion dated Sep. 20, 2019 for International Application No. PCT/US2019/026611, 26 pages. |
First Action Interview Pilot Program Pre-Interview Communication dated May 21, 2020 for U.S. Appl. No. 16/380,831, 4 pages. |
First Action Interview Office Action dated Sep. 2, 2020 for U.S. Appl. No. 16/380,831, 4 pages. |
International Search Report and Written Opinion dated Aug. 1, 2019 for International Application No. PCT/US2019/020935, 23 pages. |
Slivar, Ivan et al., “Empirical QoE Study of In-Home Streaming of Online Games”, 2014 13th Annual Workshop on Network and Systems Support for Games, IEEE, Dec. 4, 2014, 6 pages. |
Bernier, Yahn W., “Latency Compensating Methods in Client/Server In-game Protocol Design and Optimization”, Game Developers Conference Proceedings, Mar. 20, 2001, 13 pages. |
Herrscher et al., “A Dynamic Network Scenario Emulation Tool”, Proceedings of the IEEE Eleventh International Conference on Computer Communications and Networks, Oct. 16, 2002; pp. 262-267. |
Noble et al., “Trace-Based Mobile Network Emulation”, Proceedings of the ACM SIGCOMM'97 Conference on Applications, Technologies, Architectures, and Protocols for Computer Communication; Oct. 1, 1997; pp. 51-61. |
International Search Report and Written Opinion dated Oct. 7, 2019 for corresponding International Application No. PCT/US2019/025400, 13 pages. |
Ra-Qin, “Ra-Qin Review of the Activision Decathlon—Gamespot,” Sep. 2, 2006; XP055625157; retrieved from www.gamespot.com/the-activision-decathlon/user-reviews/2200-128501/ on Sep. 23, 2019; 3 pages. |
Non-Final Office Action dated Nov. 29, 2021 for U.S. Appl. No. 17/123,523, 7 pages. |
Notice of Allowance dated Mar. 22, 2022 for U.S. Appl. No. 17/123,523, 9 pages. |
Number | Date | Country | |
---|---|---|---|
20210093950 A1 | Apr 2021 | US |
Number | Date | Country | |
---|---|---|---|
62651542 | Apr 2018 | US | |
62779794 | Dec 2018 | US |