The following specification describes various aspects of a footwear assembly involving a lacing system including a motorized or non-motorized lacing engine, footwear components related to the lacing engines, automated lacing footwear platforms, and lacing architectures for use in an automated footwear platform. More specifically, much of the following specification describes various aspects of lacing architectures (configurations) for use in footwear including motorized or non-motorized lacing engines for centralized lace tightening.
In the drawings, which are not necessarily drawn to scale, like numerals may describe similar components in different views. Like numerals having different letter suffixes may represent different instances of similar components. The drawings illustrate generally, by way of example, but not by way of limitation, various embodiments discussed in the present document.
Any headings provided herein are merely for convenience and do not necessarily affect the scope or meaning of the terms used or discussion under the heading.
The concept of self-tightening shoe laces was first widely popularized by the fictitious power-laced Nike® sneakers worn by Marty McFly in the movie Back to the Future II, which was released back in 1989. While Nike® has since released at least one version of power-laced sneakers similar in appearance to the movie prop version from Back to the Future II, the internal mechanical systems and surrounding footwear platform employed do not necessarily lend themselves to mass production or daily use. Additionally, other previous designs for motorized lacing systems comparatively suffered from problems such as high cost of manufacture, complexity, assembly challenges, and poor serviceability. The present inventors have developed a lacing architecture for use on a modular footwear platform to accommodate motorized and non-motorized lacing engines that assists in solving some or all of the problems discussed above, among others. The lacing architectures and lace guides discussed herein also focus on improving fit and comfort when used in conjunction with an automated lacing engine. In order to fully leverage the modular lacing engine discussed briefly below and in greater detail in co-pending application Ser. No. 15/452,636, titled “LACING ENGINE FOR AUTOMATED FOORWEAR PLATFORM,” which is hereby incorporated by reference in its entirety, the present inventors developed lacing architectures discussed herein. The lacing architectures and lace guides discussed herein can solve various problems experienced with centralized lace tightening mechanisms, such as uneven tightening, fit, comfort, and performance. One aspect of enhanced comfort involves a lacing architecture that reduces pressure across the top of the foot. Example lacing architectures can also enhance fit and performance by manipulating lace tension in both a medial-lateral direction as well as in an anterior-posterior (front to back) direction. Another example lacing architecture discussed below splits the lacing system into two zones to provide better fit, performance and comfort by separating the toe (forefoot) area from the mid-foot area. Various other benefits of the components described below will be evident to persons of skill in the relevant arts.
The lacing architectures discussed were developed specifically to interface with a modular lacing engine positioned within a mid-sole portion of a footwear assembly. However, the concepts could also be applied to motorized and manual lacing mechanisms disposed in various locations around the footwear, such as in the heel or even the toe portion of the footwear platform. The lacing architectures discussed include use of lace guides that can be formed from tubular plastic, metal clip, fabric loops or channels, plastic clips, and open u-shaped channels, among other shapes and materials. In some examples, various different types of lacing guides can be mixed to perform specific lace routing functions within the lacing architecture. Certain examples of specific lace guide configurations are discussed in detail below.
The motorized lacing engine discussed below was developed from the ground up to provide a robust, serviceable, and inter-changeable component of an automated lacing footwear platform. The lacing engine includes unique design elements that enable retail-level final assembly into a modular footwear platform. The lacing engine design allows for the majority of the footwear assembly process to leverage known assembly technologies, with unique adaptions to standard assembly processes still being able to leverage current assembly resources.
In an example, the modular automated lacing footwear platform includes a mid-sole plate secured to the mid-sole for receiving a lacing engine. The design of the mid-sole plate allows a lacing engine to be dropped into the footwear platform as late as at a point of purchase. The mid-sole plate, and other aspects of the modular automated footwear platform, allow for different types of lacing engines to be used interchangeably. For example, the motorized lacing engine discussed below could be changed out for a human-powered lacing engine. Alternatively, a fully automatic motorized lacing engine with foot presence sensing or other optional features could be accommodated within the standard mid-sole plate. The lacing architectures are specifically designed to assist in interfacing a lace cable (or similar lacing element) with a lacing engine.
Utilizing motorized or non-motorized centralized lacing engines to tighten athletic footwear presents some challenges in providing sufficient performance without sacrificing some amount of comfort. Lacing architectures discussed herein have been designed specifically for use with centralized lacing engines, and are designed to enable various footwear designs from casual to high-performance.
Footwear terminology used in this disclosure includes terms such as floating textile layer, outer layer, shoe upper, bonding material, and eyestay, which are all further defined in a co-pending application Ser. No. 15/459,932, titled “SHOE UPPER WITH FLOATING LAYER”, that is hereby incorporated by reference in its entirety. The floating textile layer is a term used, in an example, to describe an inner sock-like structure that essentially floats within an outer layer of an upper portion of a footwear assembly. The floating textile layer can be attached to the mid-sole of the footwear assembly and may be minimally attached at select places to portions of an upper portion as well. In certain examples, the floating textile layer can be made from material with no-stretch or limited stretch properties. In some examples, the material of the floating textile layer is a quad-axial, tri-axial, or non-woven material.
The outer layer is a second layer of a footwear upper (or shoe upper) that covers the floating textile layer and substantially accounts for the outside shell of the shoe upper. In some examples, the outer layer is an outer knit shell. The outer layer can also be made in whole or in part from polyurethane, leather, cast urethane, or digitally printed urethane as well as knit, woven, braided, or non-woven materials.
A bonding material is typically used to reinforce portions of a footwear assembly, such as edges of the outer layer or floating textile layer, among others. The eyestay is a term used, in some examples, to describe an area on the footwear upper adapted to receive eyelets or lace guides. In some examples, the eyestay area can be reinforced with bonding or similar materials.
This initial overview is intended to introduce the subject matter of the present patent application. It is not intended to provide an exclusive or exhaustive explanation of the various inventions disclosed in the following more detailed description.
Automated Footwear Platform
The following discusses various components of the automated footwear platform including a motorized lacing engine, a mid-sole plate, and various other components of the platform. While much of this disclosure focuses on lacing architectures for use with a motorized lacing engine, the discussed designs are applicable to a human-powered lacing engine or other motorized lacing engines with additional or fewer capabilities. Accordingly, the term “automated” as used in “automated footwear platform” is not intended to only cover a system that operates without user input. Rather, the term “automated footwear platform” includes various electrically powered and human-powered, automatically activated and human activated mechanisms for tightening a lacing or retention system of the footwear.
In an example, the footwear article or the motorized lacing system 1 includes or is configured to interface with one or more sensors that can monitor or determine a foot presence characteristic. Based on information from one or more foot presence sensors, the footwear including the motorized lacing system 1 can be configured to perform various functions. For example, a foot presence sensor can be configured to provide binary information about whether a foot is present or not present in the footwear. If a binary signal from the foot presence sensor indicates that a foot is present, then the motorized lacing system 1 can be activated, such as to automatically tighten or relax (i.e., loosen) a footwear lacing cable. In an example, the footwear article includes a processor circuit that can receive or interpret signals from a foot presence sensor. The processor circuit can optionally be embedded in or with the lacing engine 10, such as in a sole of the footwear article.
Footwear Assembly
In this example, a small outer portion of the mid-sole plate 213 is exposed through a cut-out in the mid-sole 211. In other examples, only the actuator buttons 214 may be exposed through the side of the mid-sole 211. The mid-sole plate 213 is adapted to retain and protect a lacing engine within the mid-sole 211 of the footwear assembly 200.
Lacing Architectures
In this example, the lacing architecture comprises a series of lace guides 310 that route a lace cable 319 in a crisscross pattern over the throat portion 311. A crisscross lacing pattern is one that alternates between medial and lateral side lace guides across a centerline of the footwear assembly. The lace cable 319 can be fixed at a medial lace termination 316 and a lateral lace termination 317, which creates a lace loop that is routed by the lacing architecture to engage a lacing engine housed within a mid-sole of the footwear assembly. The lacing engine can be located in various locations throughout the footwear assembly, but is discussed for exemplary purposes only as being more or less centered under the arch within the mid-sole.
In this example, the lacing architecture includes a tongue lace guide assembly 315 (or simply a tongue lace guide 315). The tongue lace guide 315 can include a medial facing lace guide and a lateral facing lace guide. The medial facing lace guide and the lateral facing lace guide can be molded or formed from a single piece of material or be separate structures coupled together in some manner. In certain examples, the medial facing lace guide and the lateral facing lace guide can be coupled together with an elastic member that allows for some separation between the lace guides upon application of tension on the lace cable 319. In certain examples, the medial facing lace guide and the lateral facing lace guide can be adhered to a tongue lace guide reinforcement 306. In yet other examples, the medial facing lace guide and the lateral facing lace guide are disposed on, wrapped in, or otherwise connected via a webbing material. The tongue lace guide reinforcement can be a no-stretch or limited-stretch material, a rigid material, or an elastic material. The tongue lace guide reinforcement 306 can be adhered, stitched, or similarly affixed to the floating tongue 305. In some examples, the tongue lace guide reinforcement 306 be padded or similarly constructed to distribute forces applied to the tongue lace guide across a wider area to avoid hot-spots for a user.
The lacing architecture can include multiple lace guides 310 distributed around a periphery of the throat portion 311 and affixed to an eyestay 308. The eyestay 308 can be a reinforced portion of the outer layer 302 or a separate structure affixed to the outer layer 302. The eyestay 308 can be a bonding material, as noted above. The lace guides 310 can be stitched, adhered, or otherwise affixed to the eyestay 308. The eyestay 308 can include enlarged areas to receive a lace guide 310, as illustrated in
In the illustrated lacing architecture example, the lace guides 310 route the lace cable 319 proximally along a periphery of the throat portion 311 in a crisscross fashion. From the lace guides 310, the lace cable 319 is routed into the tongue lace guide 315, which in turn routes the lace cable 319 medially and laterally into heel lace guides 312. The heel lace guides 312 can be adhered or affixed to a heel counter as well as connected to a heel counter with an elastic connection or inelastic connection to distribute lace cable forces around a heel portion of the footwear assembly. From the heel lace guides 312 the lace cable 319 is routed into either a medial lace exit 318 or a lateral lace exit 321. The medial lace exit 318 and the lateral lace exit 321 route the lace cable 319 into a position to engage a lacing engine disposed in the mid-sole of the footwear assembly. The medial lace exit 318 and lateral lace exit 321 can be a molded lace guide, a fabric lace guide, a tubular lace guide, a channel molded into the mid-sole, or some similar structure capable of guiding the lace cable 319.
In this example, the lacing architecture is split into two different zones. The first zone interacts with the toe or forefoot area of the footwear upper 400. The second zone interacts with the mid-foot area of the footwear upper 400. The first lacing zone lace cable is illustrated as a solid dark grey line, and the second lacing zone lace cable illustrated as a dotted black line. These differences are merely for illustrative purposes to assist in distinguishing the different lace cable paths, the lace cable in these details is a single cable running from termination 420 to termination 421 (terminations also referred to as anchor locations or anchor points). Alternatively, even in designs were the first lacing zone and the second lacing zone utilize different lace cables, the material used will typically be common between the different zones. The first lacing zone can include lace guides guiding the lace cable 410 from a first lace termination 420. In this example, the first lace termination 420 is located on a distal-lateral portion of eyestay 408. The lace cable 410 is routed from the first lace termination 420 across a distal end of throat portion 411 and through a first medial lace guide 440. From the first medial lace guide 440 the lace cable 410 is routed back over the throat portion 411 and through a first lateral lace guide 430. From the first lateral lace guide 430, the lace cable 410 is routed pass a second lateral lace guide 431 and though a third lateral lace guide 432. The lace guides are label first, second, third, etc. . . . to signify an order running proximally from the distal end of the throat portion 411 towards the foot opening 409. Optionally, the lace cable 410 can route through a material guide 422 enroute from the first lateral lace guide 430 to the third lateral lace guide 432. From the third lateral lace guide 432, the lace cable 410 is routed through a lateral facing tongue lace guide 417 and down to a lateral heel lace guide 451 through an optional material guide 422. The lateral heel lace guide 451 routes the lace cable 410 into a mid-sole plate via lateral lace exit 419.
The second lacing zone includes a set of lace guides routing the lace cable 410 from the second termination 421 to the medial lace exit 418. In this example, the lace cable 410 is routed from the second termination 421 on the lateral side of eyestay 408 over the throat portion 411 to the second medial lace guide 441. From the second medial lace guide 441 the lace cable 410 is routed back over the throat portion 411 to the second lateral lace guide 431. The lace cable 410 then routes through the second lateral lace guide 431 back over the throat portion 411 for a third time and through the third medial lace guide 442. The third medial lace guide 442 routes the lace cable 410 on to the medial facing tongue lace guide 416, which routes the lace cable on towards the medial heel lace guide 450. Enroute to the medial heel lace guide 450 the lace cable can optionally be routed through a material lace guide 424. From the medial heel lace guide 450 the lace cable 410 is routed into the mid-sole plate via the medial lace exit 418.
The two-zone lacing architecture enables an uneven distribution of the lace cable tension between the distal end of the throat portion 411 and the proximal end. The first lacing zone applies the same lace cable tension across fewer lace guides, resulting the tension being distributed across a smaller area. The second lacing zone distributes the lace cable tension over a larger area with more lace guides The user experiences a tighter, higher performance fit in the toe (forefoot) area of the footwear with the two-zone lacing architecture. Other multi-zone lacing architectures can be utilized to vary the distribution of lace cable tension as desired for a particular footwear application.
Example Lace Guides
In this example, the lacing guide 800 can be initially attached to a footwear upper through stitching or adhesives. The illustrated design includes a stitch opening 810 that is configured to enable easy manual or automated stitching of lacing guide 800 onto a footwear upper (or similar material). Once lacing guide 800 is attached to the footwear upper, lace cable can be routed by simply pulling a loop of lace cable into the lace channel 825. The lace access opening 840 extends through the inferior surface 845 to provide a relief recess for the lace cable to get around the lace retainer 820. In some examples, the lace retainer 820 can be different dimensions or even be split into multiple smaller protrusions. In an example, the lace retainer 820 can be narrower in width, but extend further towards or even into access opening 840. In some examples, the access opening 840 can also be different dimensions, and will usually somewhat mirror the shape of lace retainer 820 (as illustrated in
In this example, lacing guides 800 are at least initially adhered to upper 805 through stitching 860. The stitching 860 is shown over or engaging stitch opening 810. One of the lacing guide 800 is also depicted with a reinforcement 870 covering the lacing guide. Such reinforcements can be positioned individually over each of the lacing guides 800. Alternatively, larger reinforcements could be used to cover multiple lacing guides. Similar to the reinforcements discussed above, reinforcement 870 can be adhered through adhesives, heat-activated adhesives, and/or stitching. In some examples, reinforcement 870 can be adhered using adhesives (heat-activated or not) and a vacuum bagging process that uniformly compresses the reinforcement over the lacing guide. A similar vacuum bagging process can also be used with reinforcements and lacing guides discussed above. In other examples, mechanical presses or similar machines can be used to assist with adhering reinforcements over lacing guides.
Once all of the lacing guides 800 are initially positioned and attached to footwear upper 805, the lace cable can be routed through the lacing guides. Lace cable routing can begin with anchoring a first end of the lace cable at lateral anchor point 870. The lace cable can then be pulled into each lace channel 825 starting with the anterior most lacing guide and working posteriorly towards the heel of upper 805. Once the lace cable is routed through all lacing guides 800, reinforcements 870 can be optionally adhered over each of the lacing guides 800 to secure both the lacing guides and the lace cable.
The present inventors have recognized, among other things, a need for an improved lacing architecture for automated and semi-automated tightening of shoe laces. This document describes, among other things, example lacing architectures and example lace guides used in the lacing architectures. The following examples provide some non-limiting examples of the actuator and footwear assembly discussed herein.
Example 1 describes subject matter including a footwear assembly with a lacing architecture to facilitate automated tightening. In this example, the footwear assembly can include a footwear upper assembly, a lace cable, a plurality of lace guides, a tongue lace guide, a medial heel lace guide, a lateral heel lace guide, as well as a medial and lateral lace exit. The footwear upper assembly can include an outer layer, a floating textile layer, and a floating tongue, the footwear upper assembly including a toe box section, a medial side, a lateral side, a heel section, and a central throat section. The footwear assembly can also include a lace cable running through a plurality of lace guides. The lace cable can include a first end anchored to the upper assembly adjacent a distal medial portion of the central throat and a second end anchored to the upper assembly adjacent a distal lateral portion of the central throat. The plurality of lace guides can be distributed on the upper assembly along the medial side and the lateral side of the central throat, each lace guide of the plurality of lace guides adapted to receive a length of the lace cable. In this example, the lace cable can extend through each of the plurality of lace guides and into the tongue lace guide assembly. The tongue lace guide assembly can be secured to a proximal portion of the floating tongue, the tongue lace guide assembly adapted to receive lace cable from both the medial side and the lateral side. The medial heel guides can be positioned to receive the lace cable from the tongue lace guide along the medial side of the upper assembly. The lateral heel lace guide can be positioned to receive the lace cable from the tongue lace guide along the lateral side of the upper assembly. The medial lace exit can route the lace cable from the medial heel lace guide into a position allowing the lace cable to engage a lacing engine disposed within a mid-sole portion of the footwear assembly. The lateral lace exit can route the lace cable from the lateral heel lace guide into a position to engage the lacing engine.
In example 2, the subject matter of example 1 can optionally include the tongue lace guide assembly having a medial facing lace guide opposite a lateral facing lace guide.
In example 3, the subject matter of example 2 can optionally include the tongue lace guide assembly having an elastic member coupling the medial facing lace guide to the lateral facing lace guide.
In example 4, the subject matter of example 2 can optionally include the tongue lace guide assembly being a single structure with a rigid connection between the medial facing lace guide and the lateral facing lace guide.
In example 5, the subject matter of any one of examples 1 to 4 can optionally include the tongue lace guide assembly being fused to a reinforcement material that is stitched to the floating tongue.
In example 6, the subject matter of any one of examples 1 to 5 can optionally include the floating tongue being secured to the upper assembly adjacent to a distal end of the central throat.
In example 7, the subject matter of example 6 can optionally include the floating tongue being additionally secured to the upper assembly adjacent a proximal end of the central throat.
In example 8, the subject matter of example 7 can optionally include the floating tongue having an elastic coupling to the upper assembly.
In example 9, the subject matter of any one of examples 1 to 8 can optionally include the lace cable forming a crisscross pattern across at least a length of the central throat connecting the medial side the lateral side of the upper assembly.
In example 10, the subject matter of example 9 can optionally include the crisscross pattern being created by routing the lace cable in an alternating pattern between lace guides on the medial side and lace guides on the lateral side of the upper assembly.
In example 11, the subject matter of any one of examples 1 to 10 can optionally include the medial heel lace guide and the lateral heel lace guide being coupled, via a heel coupling, to a heel counter within the heel section of the upper assembly.
In example 12, the subject matter of example 11 can optionally include at least one of the heel counter or the heel coupling being an elastic member.
In example 13, the subject matter of any one of examples 1 to 12 can optionally include each lace guide of the plurality of lace guides forming a u-shaped channel to retain the lace cable.
In example 14, the subject matter of example 13 can optionally include the u-shaped channel in each lace guide being an open channel allowing a lace loop to be pulled into the lace guide.
In example 15, the subject matter of any one of examples 1 to 14 can optionally include each lace guide of the plurality of lace guides being at least secured to the upper assembly by stitching.
In example 16, the subject matter of example 15 can optionally include each lace guide of the plurality of lace guides being further secured to the upper assembly with an overlay including heat-activated adhesive compressed over each lace guide.
Example 17 describes subject matter including a lacing architecture for an automated footwear platform. In this example, the lacing architecture for an automated footwear platform can include a lace cable routed through a plurality of medial lace guides and a plurality of lateral guides into a tongue lace guide. For the tongue lace guide the lace cable can be routed into a medial heel lace guide and/or a lateral heel lace guide, which then leads to either a medial lace exit or a lateral lace exit. The lace cable can include a first end anchored to an upper assembly adjacent a distal medial portion of a central throat and a second end anchored to the upper assembly adjacent a distal lateral portion of the central throat. The plurality of medial lace guides can be distributed on the upper assembly adjacent to a medial side of the central throat. The tongue lace guide can be secured to a proximal portion of a floating tongue, with the tongue lace guide assembly adapted to receive lace cable from a medial lace guide of the plurality of medial lace guides and a lateral lace guide of the plurality of lateral lace guides. The medial heel lace guide can be positioned to receive the lace cable from the tongue lace guide along a medial side of the upper assembly. While, the lateral heel lace guide can be positioned to receive the lace cable from the tongue lace guide along a lateral side of the upper assembly. The medial lace exit can route the lace cable from the medial heel lace guide into a position allowing the lace cable to engage a lacing engine disposed within a mid-sole portion of the footwear platform. While the lateral lace exit routes the lace cable from the lateral heel lace guide into a position to engage the lacing engine.
In example 18, the subject matter of example 17 can optionally include the tongue lace guide having a medial facing lace guide opposite a lateral facing lace guide.
In example 19, the subject matter of example 18 can optionally include the tongue lace guide including an elastic member coupling the medial facing lace guide to the lateral facing lace guide.
In example 20, the subject matter of example 18 can optionally include the tongue lace guide assembly being a single structure with a rigid connection between the medial facing lace guide and the lateral facing lace guide.
In example 21, the subject matter of example 17 can optionally include the tongue lace guide being fused to a reinforcement material that is stitched to a floating tongue.
Example 22 describes subject matter including a footwear assembly with a lacing architecture to facilitate automated tightening. In this example, the footwear assembly can include a footwear upper assembly, a lace cable, a plurality of lace guides, a tongue lace guide, a medial heel lace guide, a lateral heel lace guide, as well as a medial and lateral lace exit. The lace cable can include a first end anchored to the upper assembly in a first anchor location and a second end anchored to the upper assembly in a second anchor location. A first plurality of lace guides can form a first lacing zone routing a first portion of the lace cable to tension a forefoot region of the footwear assembly. A second plurality of lace guides can form a second lacing zone routing a second portion of the lace cable to tension a mid-foot region of the footwear assembly. A tongue lace guide assembly can be secured to a proximal portion of the floating tongue, the tongue lace guide assembly adapted to receive lace cable from both the medial side and the lateral side. The medial heel lace guide can be positioned to receive the lace cable from the tongue lace guide along the medial side of the upper assembly. The lateral heel lace guide can be positioned to receive the lace cable from the tongue lace guide along the lateral side of the upper assembly. The medial lace exit can route the lace cable from the medial heel lace guide into a position allowing the lace cable to engage a lacing engine disposed within a mid-sole portion of the footwear assembly. The lateral lace exit can route the lace cable from the lateral heel lace guide into a position to engage the lacing engine.
In Example 23, the subject matter of Example 22 can optionally include the second plurality of lace guides having a greater number of lace guides than the first plurality of lace guides.
In Example 24, the subject matter of any one of Examples 22 and 23 can optionally include the second plurality of lace guides distributing lace cable tension across a larger area of the footwear assembly than the first plurality of lace guides.
In Example 25, the subject matter of any one of Examples 1 to 3 can optionally include the first plurality of lace guides including a medial lace guide on the medial side of the central throat section and two lateral lace guides on the lateral side of the central throat section.
In Example 26, the subject matter of Example 25 can optionally include the first lateral lace guide of the two lateral lace guides being located towards a distal end of the central throat section and the second lateral lace guide of the two lateral lace guides being located towards a proximal end of the central throat section.
In Example 27, the subject matter of Example 26 can optionally include the lace cable path for the first lacing zone including the path segments such as: the first anchor location to the medial lace guide; the medial lace guide to the first lateral lace guide; and the first lateral lace guide to the second lateral lace guide.
In Example 28, the subject matter of Example 27 can optionally include the lace cable path for the first lacing zone continuing from the first second lateral lace guide to a lateral facing lace guide in the tongue lace guide assembly.
In Example 29, the subject matter of Example 28 can optionally include the lace cable path for the first lacing zone continuing from the lateral facing lace guide to the lateral heel lace guide.
In Example 30, the subject matter of any one of Examples 22 to 29 can optionally include the second plurality of lace guides forming the second lacing zone including a first lateral lace guide disposed along a central portion of a lateral side of the central throat section and a plurality of medial lace guides distributed along a length of a medial side of the central throat section.
In Example 31, the subject matter of Example 30 can optionally include the lace cable path for the second lacing zone including the path segments such as: the second anchor location to a first medial lace guide of the plurality of medial lace guides; the first medial lace guide to the first lateral lace guide; the first lateral lace guide to a second medial lace guide of the plurality of medial lace guides.
In Example 32, the subject matter of Example 31 can optionally include the second anchor location is located on a lateral side of the central throat section proximal at least one lace guide from the first lacing zone.
In Example 33, the subject matter of any one of Example 30 and 31 can optionally include the lace cable path for the second lacing zone further including a path segment running from the second medial lace guide to a medial facing lace guide within the tongue lace guide assembly.
In Example 34, the subject matter of Example 33 can optionally include the lace cable path for the second lacing zone continuing from the lateral facing lace guide to the lateral heel lace guide.
In Example 35, the subject matter of any one of Examples 22 to 34 can optionally include the first anchor location being on the lateral side distal of the central throat section, and the second anchor location being on the lateral side adjacent to a first lateral lace guide.
In Example 36, the subject matter of any one of Examples 22 to 35 can optionally include the tongue lace guide assembly having a medial facing lace guide opposite a lateral facing lace guide.
In Example 37, the subject matter of Example 36 can optionally include the tongue lace guide assembly having an elastic member coupling the medial facing lace guide to the lateral facing lace guide.
In Example 38, the subject matter of Example 36 can optionally include the tongue lace guide assembly is a single structure with a rigid connection between the medial facing lace guide and the lateral facing lace guide.
In Example 39, the subject matter of Example 38 can optionally include the tongue lace guide assembly being fused to a reinforcement material that is stitched to the floating tongue.
In Example 40, the subject matter of any one of Examples 22 to 39 can optionally include the medial heel lace guide and the lateral heel lace guide being coupled, via a heel coupling, to a heel counter within the heel section of the upper assembly.
In Example 41, the subject matter of Example 40 can optionally include at least one of the heel counter or the heel coupling being an elastic member.
Example 42 describes subject matter including a lacing architecture for an automated footwear platform. In this example, the lacing architecture can include a lace cable, a first lacing zone and a second lacing zone. The lace cable can include a first end anchored to an upper footwear assembly adjacent a distal lateral portion of a central throat and a second end anchored to the upper assembly adjacent a first lateral lace guide on a lateral portion of the central throat. The first lacing zone can include a first portion of the lace cable running from the first end over the central throat to a first medial lace guide back over the central throat to a first lateral lace guide proximal along a lateral side of the central throat to a third lateral lace guide proximal to a lateral facing lace guide within a tongue lace guide assembly laterally to a lateral heel lace guide and on to a lateral lace exit along a lateral edge of the footwear upper. The second lacing zone can include a second portion of the lace cable running from the second end over the central throat to a second medial lace guide back over the central throat to a second lateral lace guide back over the central throat to a third medial lace guide proximally to a medial facing lace guide within the tongue lace guide assembly medially to a medial heel lace guide and on to a medial lace exit along a medial edge of the footwear upper.
Additional, Notes
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.
Although an overview of the inventive subject matter has been described with reference to specific example embodiments, various modifications and changes may be made to these embodiments without departing from the broader scope of embodiments of the present disclosure. Such embodiments of the inventive subject matter may be referred to herein, individually or collectively, by the term “invention” merely for convenience and without intending to voluntarily limit the scope of this application to any single disclosure or inventive concept if more than one is, in fact, disclosed.
The embodiments illustrated herein are described in sufficient detail to enable those skilled in the art to practice the teachings disclosed. Other embodiments may be used and derived therefrom, such that structural and logical substitutions and changes may be made without departing from the scope of this disclosure. The disclosure, therefore, is not to be taken in a limiting sense, and the scope of various embodiments includes the full range of equivalents to which the disclosed subject matter is entitled.
As used herein, the term “or” may be construed in either an inclusive or exclusive sense. Moreover, plural instances may be provided for resources, operations, or structures described herein as a single instance. Additionally, boundaries between various resources, operations, modules, engines, and data stores are somewhat arbitrary, and particular operations are illustrated in a context of specific illustrative configurations. Other allocations of functionality are envisioned and may fall within a scope of various embodiments of the present disclosure. In general, structures and functionality presented as separate resources in the example configurations may be implemented as a combined structure or resource. Similarly, structures and functionality presented as a single resource may be implemented as separate resources. These and other variations, modifications, additions, and improvements fall within a scope of embodiments of the present disclosure as represented by the appended claims. The specification and drawings are, accordingly, to be regarded in an illustrative rather than a restrictive sense.
Each of these non-limiting examples can stand on its own, or can be combined in various permutations or combinations with one or more of the other examples.
The above detailed description includes references to the accompanying drawings, which form a part of the detailed description. The drawings show, by way of illustration, specific embodiments in which the invention can be practiced. These embodiments are also referred to herein as “examples.” Such examples can include elements in addition to those shown or described. However, the present inventors also contemplate examples in which only those elements shown or described are provided. Moreover, the present inventors also contemplate examples using any combination or permutation of those elements shown or described (or one or more aspects thereof), either with respect to a particular example (or one or more aspects thereof), or with respect to other examples (or one or more aspects thereof) shown or described herein.
In the event of inconsistent usages between this document and any documents so incorporated by reference, the usage in this document controls.
In this document, the terms “a” or “an” are used, as is common in patent documents, to include one or more than one, independent of any other instances or usages of “at least one” or “one or more.” In this document, the term “or” is used to refer to a nonexclusive or, such that “A or B” includes “A but not B,” “B but not A,” and “A and B,” unless otherwise indicated. In this document, the terms “including” and “in which” are used as the plain-English equivalents of the respective terms “comprising” and “wherein.” Also, in the following claims, the terms “including” and “comprising” are open-ended, that is, a system, device, article, composition, formulation, or process that includes elements in addition to those listed after such a term in a claim are still deemed to fall within the scope of that claim. Moreover, in the following claims, the terms “first,” “second,” and “third,” etc. are used merely as labels, and are not intended to impose numerical requirements on their objects.
The above description is intended to be illustrative, and not restrictive. For example, the above-described examples (or one or more aspects thereof) may be used in combination with each other. Other embodiments can be used, such as by one of ordinary skill in the art upon reviewing the above description. An Abstract, if provided, is included to comply with 37 C.F.R. § 1.72(b), to allow the reader to quickly ascertain the nature of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. Also, in the above Description, various features may be grouped together to streamline the disclosure. This should not be interpreted as intending that an unclaimed disclosed feature is essential to any claim. Rather, inventive subject matter may lie in less than all features of a particular disclosed embodiment. Thus, the following claims are hereby incorporated into the Detailed Description as examples or embodiments, with each claim standing on its own as a separate embodiment, and it is contemplated that such embodiments can be combined with each other in various combinations or permutations. The scope of the invention should be determined with reference to the appended claims, along with the full scope of equivalents to which such claims are entitled.
This application is a divisional application of U.S. patent application Ser. No. 16/165,023, filed Oct. 19, 2018, which application claims the benefit of priority to U.S. Provisional Patent Application Ser. No. 62/634,358, filed Feb. 23, 2018 and U.S. Provisional Patent Application Ser. No. 62/574,940, filed Oct. 20, 2017, the contents of all which are hereby incorporated by reference in their entireties.
Number | Name | Date | Kind |
---|---|---|---|
64155 | Sickels et al. | Apr 1867 | A |
3808644 | Schoch | May 1974 | A |
5566474 | Leick | Oct 1996 | A |
5791021 | James | Aug 1998 | A |
5791068 | Bernier et al. | Aug 1998 | A |
5934599 | Hammerslag | Aug 1999 | A |
5983530 | Chou | Nov 1999 | A |
6032387 | Johnson | Mar 2000 | A |
6691433 | Liu | Feb 2004 | B2 |
6896128 | Johnson | May 2005 | B1 |
7721468 | Johnson et al. | May 2010 | B1 |
7752774 | Ussher | Jul 2010 | B2 |
8418381 | Reagan et al. | Apr 2013 | B2 |
8904672 | Johnson | Dec 2014 | B1 |
9693605 | Beers | Jul 2017 | B2 |
9861165 | Schneider et al. | Jan 2018 | B2 |
9961963 | Schneider et al. | May 2018 | B2 |
10856618 | Avar et al. | Dec 2020 | B2 |
20020083621 | Durocher | Jul 2002 | A1 |
20020095750 | Hammerslag | Jul 2002 | A1 |
20030204938 | Hammerslag | Nov 2003 | A1 |
20050210706 | Johnson | Sep 2005 | A1 |
20070068040 | Farys | Mar 2007 | A1 |
20070240334 | Johnson | Oct 2007 | A1 |
20080172848 | Chen | Jul 2008 | A1 |
20080301919 | Ussher | Dec 2008 | A1 |
20080307673 | Johnson | Dec 2008 | A1 |
20090272007 | Beers et al. | Nov 2009 | A1 |
20110296712 | Settele | Dec 2011 | A1 |
20130086816 | Johnson et al. | Apr 2013 | A1 |
20140068838 | Beers et al. | Mar 2014 | A1 |
20140082963 | Beers | Mar 2014 | A1 |
20150047230 | Beers | Feb 2015 | A1 |
20170265579 | Schneider et al. | Sep 2017 | A1 |
20170265580 | Schneider et al. | Sep 2017 | A1 |
20170265593 | Schneider et al. | Sep 2017 | A1 |
20180110294 | Schneider et al. | Apr 2018 | A1 |
20180110298 | Schneider et al. | Apr 2018 | A1 |
20180199671 | Schneider et al. | Jul 2018 | A1 |
20180199673 | Schneider et al. | Jul 2018 | A1 |
20180263338 | Amis et al. | Sep 2018 | A1 |
20180289110 | Bock et al. | Oct 2018 | A1 |
20180368526 | Bock et al. | Dec 2018 | A1 |
20190116935 | Avar et al. | Apr 2019 | A1 |
20200170352 | Avar et al. | Jun 2020 | A1 |
Number | Date | Country |
---|---|---|
1939179 | Apr 2007 | CN |
102014682 | Apr 2011 | CN |
102821635 | Dec 2012 | CN |
103156331 | Jun 2013 | CN |
203505737 | Apr 2014 | CN |
104582519 | Apr 2015 | CN |
110099584 | Aug 2019 | CN |
111278319 | Jun 2020 | CN |
111278319 | Dec 2021 | CN |
114652053 | Jun 2022 | CN |
3900777 | Jul 1990 | DE |
102005036013 | Feb 2007 | DE |
H0751103 | Feb 1995 | JP |
2006502797 | Jan 2006 | JP |
2021500120 | Jan 2021 | JP |
20200058591 | May 2020 | KR |
20210071092 | Jun 2021 | KR |
521593 | Feb 2003 | TW |
201739371 | Nov 2017 | TW |
2004034831 | Apr 2004 | WO |
2009071652 | Jun 2009 | WO |
2017160558 | Sep 2017 | WO |
2019079673 | Apr 2019 | WO |
Entry |
---|
“Chinese Application Serial No. 201880068332.X, Office Action dated Dec. 31, 2020”, w English translation, 13 pgs. |
“Japanese Application Serial No. 2020-521956, Response filed Jan. 29, 2021 to Notification of Reasons for Refusal dated Nov. 17, 2020”, w English Claims, 17 pgs. |
“Japanese Application Serial No. 2020-521956, Examiners Decision of Final Refusal dated Mar. 30, 2021”, w English Translation, 7 pgs. |
U.S. Appl. No. 16/165,023, U.S. Pat. No. 10/856,618, filed Oct. 19, 2018, Lacing Architecture for Automated Footwear Platform. |
“Japanese Application Serial No. 2020-521956, Response filed Jul. 27, 1021 to Examiners Decision of Final Refusal dated Mar. 30, 2021”, With English claims, 7 pgs. |
“International Application Serial No. PCT US2017 021393, International Search Report dated Jun. 16, 2017”, 4 pgs. |
“International Application Serial No. PCT US2017 021393, Written Opinion dated Jun. 16, 2017”, 6 pgs. |
“U.S. Appl. No. 15/452,636, Restriction Requirement dated Jul. 6, 2017”, 6 pgs. |
“U.S. Appl. No. 15/610,151, Non Final Office Action dated Jul. 12, 2017”, 15 pgs. |
“U.S. Appl. No. 15/452,636, Response filed 09-06=17 to Restriction Requirement dated Jul. 6, 2017”, 7 pgs. |
“U.S. Appl. No. 15/452,636, Non Final Office Action dated Sep. 15, 2017”, 17 pgs. |
“U.S. Appl. No. 15/610,151, Response filed Sep. 27, 2017 to Non Final Office Action dated Jul. 12, 2017”, 14 pgs. |
“U.S. Appl. No. 15/610,151, Preliminary Amendment filed Jun. 28, 2017”, 6 pgs. |
“U.S. Appl. No. 15/610,151, Notice of Allowance dated Oct. 24, 2017”, 8 pgs. |
“U.S. Appl. No. 15/452,636, Response filed Dec. 15, 2017 to Non Final Office Action dated Sep. 15, 2017”, 17 pgs. |
“Taiwanese Application Serial No. 106108511, Office Action dated Dec. 5, 2017”, w English translation, 16 pgs. |
“U.S. Appl. No. 15/452,636, Notice of Allowance dated Feb. 12, 2018”, 10 pgs. |
“Taiwanese Application Serial No. 106108511, Response filed Mar. 5, 2018 to Office Action dated Dec. 5, 2017”, w claims in English, 110 pgs. |
“International Application Serial No. PCT US2018 056631, International Search Report dated Feb. 8, 2019”, 3 pgs. |
“International Application Serial No. PCT US2018 056631, Written Opinion dated Feb. 8, 2019”, 5 pgs. |
“U.S. Appl. No. 16/165,023, Restriction Requirement dated Mar. 20, 2020”, 5 pgs. |
“International Application Serial No. PCT US2018 056631, International Preliminary Report on Patentability dated Apr. 30, 2020”, 7 pgs. |
“U.S. Appl. No. 16/165,023, Response filed Jun. 19, 2020 to Restriction Requirement dated Mar. 20, 2020”, 8 pgs. |
“U.S. Appl. No. 16/165,023, Notice of Allowance dated Aug. 3, 2020”, 12 pgs. |
“Korean Application Serial No. 10-2020-7014339, Notice of Preliminary Rejection dated Jul. 31, 2020”, w English translation, 8 pgs. |
“U.S. Appl. No. 16/165,023, Corrected Notice of Allowability dated Nov. 12, 2020”, 2 pgs. |
“Japanese Application Serial No. 2020-521956, Notification of Reasons for Refusal dated Nov. 17, 2020”, w English translation, 10 pgs. |
“European Application Serial No. 18867964.1, Response to Communication Pursuant to Rules 161 and 162 filed Nov. 9, 2020”, 10 pgs. |
“Korean Application Serial No. 10-2020-7014339, Response filed Jan. 11, 2021 to Notice of Preliminary Rejection dated Jul. 31, 2020”, w English claims, 14 pgs. |
“Chinese Application Serial No. 202111346221.0, Response filed Mar. 4, 2022 to Notification to Make Rectification dated Jan. 4, 2022”, w/ English claims, 64 pgs. |
“Chinese Application Serial No. 202111346221.0, Notification to Make Rectification dated Jan. 4, 2022”, w/o English translation, 1 pgs. |
“European Application Serial No. 18867964.1, Response filed Dec. 17, 2021 to Extended European Search Report dated May 19, 2021”, 23 pgs. |
“European Application Serial No. 18867964.1, Extended European Search Report dated May 19, 2021”, 10 pgs. |
“Chinese Application Serial No. 201880068332.X, Response filed Jul. 14, 2021 to Office Action dated Dec. 31, 2020”, w English claims, 76 pgs. |
“Chinese Application Serial No. 202111346221.0, Response filed May 23, 2022 to Notification to Make Rectification dated Mar. 21, 2022”, w/ English claims, 63 pgs. |
“Japanese Application Serial No. 2020-521956, Notification of Reasons for Refusal dated May 17, 2022”, w/ English translation, 4 pgs. |
Number | Date | Country | |
---|---|---|---|
20210120917 A1 | Apr 2021 | US |
Number | Date | Country | |
---|---|---|---|
62634358 | Feb 2018 | US | |
62574940 | Oct 2017 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 16165023 | Oct 2018 | US |
Child | 17092555 | US |