Patent Application
20230172306
The subject matter disclosed herein generally relates to an article of footwear having an autolacing motor and a tubular spool member.
Some embodiments are illustrated by way of example and not limitation in the figures of the accompanying drawings.
Example methods and systems are directed to an article of footwear having an autolacing motor and a tubular spool member. Examples merely typify possible variations. Unless explicitly stated otherwise, components and functions are optional and may be combined or subdivided, and operations may vary in sequence or be combined or subdivided. In the following description, for purposes of explanation, numerous specific details are set forth to provide a thorough understanding of example embodiments. It will be evident to one skilled in the art, however, that the present subject matter may be practiced without these specific details.
Articles of footwear, such as shoes, may include a variety of components, both conventional and unconventional. Conventional components may include an upper, a sole, and laces or other securing mechanisms to enclose and secure the foot of a wearer within the article of footwear. Unconventionally, a motorized lacing system may engage with the lace to tighten and/or loosen the lace. Additional or alternative electronics may provide a variety of functionality for the article of footwear, including operating and driving the motor, sensing information about the nature of the article of footwear, providing lighted displays and/or other sensory stimuli, and so forth.
In general, and particularly for articles of footwear oriented toward the performance of athletic activities, characteristics such as the size, form, robustness, and weight of the article of footwear may be of particular importance. The capacity to firmly secure the article of footwear to the foot by way of tightening a lace, laces, or other tension members may further enhance wearability, comfort, and performance. Providing adequate tightness across a desired range of the upper of a footwear may be a particular challenge of autolacing footwear and footwear in general.
Autolacing footwear has been developed that seeks to distribute the tension on laces through the use of an elongate spool. The elongate spool may be tubular, conical, have stepped portions, or be any other suitable shape. The elongate spool may be positioned outside of a lacing engine but be connected between the lacing engine and laces that engage with an upper to tighten the upper and secure the article of footwear to a foot of a wearer. The result may be an even, desired tension placed on one or more laces and an even distribution of tension across the upper.
In the example of
In an example, the receive coil 208 is positioned on or inside of the housing 103 of the lacing engine 102. In various examples, the receive coil 208 is positioned on an outside major surface, e.g., a top or bottom surface, of the housing 103 and, in a specific example, the bottom surface. In various examples, the receive coil 208 is a qi charging coil, though any suitable coil, such as an A4WP charging coil, may be utilized instead.
In an example, the processor circuit 204 controls one or more aspects of the drive mechanism 214. For example, the processor circuit 204 can be configured to receive information from the buttons 200 and/or from the foot presence sensor 202 and/or from the motion sensor 212 and, in response, control the drive mechanism 214, such as to tighten or loosen footwear about a foot. In an example, the processor circuit 204 is additionally or alternatively configured to issue commands to obtain or record sensor information, from the foot presence sensor 202 or other sensor, among other functions. In an example, the processor circuit 204 conditions operation of the drive mechanism 214 on (1) detecting a foot presence using the foot presence sensor 202 and (2) detecting a specified gesture using the motion sensor 212.
Information from the environment sensor 224 can be used to update or adjust a baseline or reference value for the foot presence sensor 202. As further explained below, capacitance values measured by a capacitive foot presence sensor can vary over time, such as in response to ambient conditions near the sensor. Using information from the environment sensor 224, the processor circuit 204 and/or the foot presence sensor 202 can update or adjust a measured or sensed capacitance value.
A plurality of laces 306 are spaced along each of the elongate spools 302. Each one of the plurality of laces 306 has a first end 308 secured to one of the elongate spools 302 and a second end 310 secured to the other one of the elongate spools 302, causing each of the plurality of laces to extend across a throat section 312 of an upper 314 of the article of footwear 300. In various examples, the first and second ends 308, 310 of each of the plurality of laces 306 are secured in part by being wound about the respective elongate spool 302 and in part by being fastened, glued, inserted into, or otherwise affixed to or within the elongate spool 302.
To tighten the plurality of laces 306, the motor 216 (
To loosen the plurality of laces 306, the motor 216 operates and causes the lace spool 220 to turn in an opposite direction from the direction the lace spool 216 turned to tighten the plurality of laces 306. The primary lace 304 then becomes slack, allowing the elongate spools 302 to rotate in the opposite direction along their respective major axis 303 as from the tightening the plurality of laces 306, thereby allowing the plurality of laces 306 to go slack. As a wearer removes their foot from the article of footwear 300 or a force is otherwise imposed on the plurality of laces 306, e.g., by applying a force to a tongue of the article of footwear 300 or by directly manipulating the plurality of laces 306, the plurality of laces 306 may become more slack, creating a larger opening to remove the foot of the wearer.
Because the elongate spool 602 turns at a constant rate about the major axis 603, each one of the plurality of laces 610 has a different amount of travel owning to the corresponding different in diameter in the corresponding one of the plurality of segments 604, 606, 608. Thus, the lace 610′, which is wound about the segment 604 having the largest diameter, will have a larger amount of travel than the lace 610″ which is wound about the segment 606 having a smaller diameter. In other words, one rotation of the elongate spool 602 winds or unwinds more of the lace 610′ than the lace 610″. As a result, the cinching characteristics of each of the plurality of laces 610 may be customized by selecting the diameter of each of the plurality of segments 604, 606, 608.
Because each of the plurality of laces 710 winds around a length 712 of the elongate spool 702, the torque on each of the plurality of laces 710 varies as the individual lace winds about the elongate spool 702. Thus, for instance, the lace 710′ starts at a first, greater-diameter location 714 on the spool 702 but as the spool 702 turns gradually moves down the length 712 to a second, lesser-diameter location 716. Because the diameter of the elongate spool 702 on which the lace 710′ is engaged is constantly decreasing as the elongate spool 702 turns, the torque imparted on the lace 710′ by the spool constantly decreases. As illustrated, each of the plurality of laces 710 experiences the same decrease in torque, potentially creating a relatively softer cinching sensation on a wearer than may be the case if the torque does not decrease as the plurality of laces 710 tighten.
The principles of the elongate spools 602, 702 may be combined in a single spool. Thus, a single elongate spool may incorporate both conical sections with gradual changes in diameter and discrete sections separated by abrupt changes in diameter. The discrete sections may themselves be conical, with an abrupt change between conical sections.
As seen in the side view of
Throughout this specification, plural instances may implement components, operations, or structures described as a single instance. Although individual operations of one or more methods are illustrated and described as separate operations, one or more of the individual operations may be performed concurrently, and nothing requires that the operations be performed in the order illustrated. Structures and functionality presented as separate components in example configurations may be implemented as a combined structure or component. Similarly, structures and functionality presented as a single component may be implemented as separate components. These and other variations, modifications, additions, and improvements fall within the scope of the subject matter herein.
Certain embodiments are described herein as including logic or a number of components, modules, or mechanisms. Modules may constitute either software modules (e.g., code embodied on a machine-readable medium or in a transmission signal) or hardware modules. A “hardware module” is a tangible unit capable of performing certain operations and may be configured or arranged in a certain physical manner. In various example embodiments, one or more computer systems (e.g., a standalone computer system, a client computer system, or a server computer system) or one or more hardware modules of a computer system (e.g., a processor or a group of processors) may be configured by software (e.g., an application or application portion) as a hardware module that operates to perform certain operations as described herein.
In some embodiments, a hardware module may be implemented mechanically, electronically, or any suitable combination thereof. For example, a hardware module may include dedicated circuitry or logic that is permanently configured to perform certain operations. For example, a hardware module may be a special-purpose processor, such as a field programmable gate array (FPGA) or an ASIC. A hardware module may also include programmable logic or circuitry that is temporarily configured by software to perform certain operations. For example, a hardware module may include software encompassed within a general-purpose processor or other programmable processor. It will be appreciated that the decision to implement a hardware module mechanically, in dedicated and permanently configured circuitry, or in temporarily configured circuitry (e.g., configured by software) may be driven by cost and time considerations.
Accordingly, the phrase “hardware module” should be understood to encompass a tangible entity, be that an entity that is physically constructed, permanently configured (e.g., hardwired), or temporarily configured (e.g., programmed) to operate in a certain manner or to perform certain operations described herein. As used herein, “hardware-implemented module” refers to a hardware module. Considering embodiments in which hardware modules are temporarily configured (e.g., programmed), each of the hardware modules need not be configured or instantiated at any one instance in time. For example, where a hardware module comprises a general-purpose processor configured by software to become a special-purpose processor, the general-purpose processor may be configured as respectively different special-purpose processors (e.g., comprising different hardware modules) at different times. Software may accordingly configure a processor, for example, to constitute a particular hardware module at one instance of time and to constitute a different hardware module at a different instance of time.
Hardware modules can provide information to, and receive information from, other hardware modules. Accordingly, the described hardware modules may be regarded as being communicatively coupled. Where multiple hardware modules exist contemporaneously, communications may be achieved through signal transmission (e.g., over appropriate circuits and buses) between or among two or more of the hardware modules. In embodiments in which multiple hardware modules are configured or instantiated at different times, communications between such hardware modules may be achieved, for example, through the storage and retrieval of information in memory structures to which the multiple hardware modules have access. For example, one hardware module may perform an operation and store the output of that operation in a memory device to which it is communicatively coupled. A further hardware module may then, at a later time, access the memory device to retrieve and process the stored output. Hardware modules may also initiate communications with input or output devices, and can operate on a resource (e.g., a collection of information).
The various operations of example methods described herein may be performed, at least partially, by one or more processors that are temporarily configured (e.g., by software) or permanently configured to perform the relevant operations. Whether temporarily or permanently configured, such processors may constitute processor-implemented modules that operate to perform one or more operations or functions described herein. As used herein, “processor-implemented module” refers to a hardware module implemented using one or more processors.
Similarly, the methods described herein may be at least partially processor-implemented, a processor being an example of hardware. For example, at least some of the operations of a method may be performed by one or more processors or processor-implemented modules. Moreover, the one or more processors may also operate to support performance of the relevant operations in a “cloud computing” environment or as a “software as a service” (SaaS). For example, at least some of the operations may be performed by a group of computers (as examples of machines including processors), with these operations being accessible via a network (e.g., the Internet) and via one or more appropriate interfaces (e.g., an application program interface (API)).
The performance of certain of the operations may be distributed among the one or more processors, not only residing within a single machine, but deployed across a number of machines. In some example embodiments, the one or more processors or processor-implemented modules may be located in a single geographic location (e.g., within a home environment, an office environment, or a server farm). In other example embodiments, the one or more processors or processor-implemented modules may be distributed across a number of geographic locations.
Some portions of this specification are presented in terms of algorithms or symbolic representations of operations on data stored as bits or binary digital signals within a machine memory (e.g., a computer memory). These algorithms or symbolic representations are examples of techniques used by those of ordinary skill in the data processing arts to convey the substance of their work to others skilled in the art. As used herein, an “algorithm” is a self-consistent sequence of operations or similar processing leading to a desired result. In this context, algorithms and operations involve physical manipulation of physical quantities. Typically, but not necessarily, such quantities may take the form of electrical, magnetic, or optical signals capable of being stored, accessed, transferred, combined, compared, or otherwise manipulated by a machine. It is convenient at times, principally for reasons of common usage, to refer to such signals using words such as “data,” “content,” “bits,” “values,” “elements,” “symbols,” “characters,” “terms,” “numbers,” “numerals,” or the like. These words, however, are merely convenient labels and are to be associated with appropriate physical quantities.
Unless specifically stated otherwise, discussions herein using words such as “processing,” “computing,” “calculating,” “determining,” “presenting,” “displaying,” or the like may refer to actions or processes of a machine (e.g., a computer) that manipulates or transforms data represented as physical (e.g., electronic, magnetic, or optical) quantities within one or more memories (e.g., volatile memory, non-volatile memory, or any suitable combination thereof), registers, or other machine components that receive, store, transmit, or display information. Furthermore, unless specifically stated otherwise, the terms “a” or “an” are herein used, as is common in patent documents, to include one or more than one instance. Finally, as used herein, the conjunction “or” refers to a non-exclusive “or,” unless specifically stated otherwise.
This application is a continuation of U.S. patent application Ser. No. 16/557,176, filed Aug. 30, 2019, which application claims the benefit of priority to U.S. Provisional Application Ser. No. 62/725,672, filed Aug. 31, 2018, the contents of both which are incorporated herein by reference in their entireties.
| Number | Date | Country | |
|---|---|---|---|
| 62725672 | Aug 2018 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16557176 | Aug 2019 | US |
| Child | 18076077 | US |
