In today's world mobile subscribers or users have user devices such as smart phones that can not only make telephone calls, but can also function as general purpose computing devices that run software applications and network with other computing devices, for example by enabling users to communicate and share different kinds of information with each other.
The detailed description is described with reference to the accompanying figures. In the figures, the left-most digit(s) of a reference number identifies the figure in which the reference number first appears. The same reference numbers indicate similar or identical items.
In simple form, example embodiments variously encompass a process where a first mobile device (e.g., a child's personal mobile device such as a smart watch) displays or otherwise presents (e.g., via aural guidance and/or haptic feedback) directions or vectors to a user of the first mobile device, to direct the user to move (with the first mobile device) to a geographic location of a second mobile device (e.g., a parent's smartphone). The location of the second mobile device can be dynamic or changeable and the directions or instructions presented by the first mobile device can adapt accordingly as a location of the second mobile device changes. In example embodiments the second mobile device (e.g., the parent's smart phone) can display or convey progress updates and/or a current location of the first mobile device (the child's smart watch). In example embodiments, the second mobile device also presents directions to direct the user of the second mobile device to move toward and meet the user of the first mobile device.
One or more additional mobile devices can also become involved, and present directions that enable their users to navigate towards either the first mobile device or the second mobile device, and can present locations of, and communications from, the first and second mobile devices.
In example embodiments, each of the mobile devices receives information regarding its own geographic location, for example via Global Positioning System signals received by the mobile device and/or location data determined from interaction of the mobile device with local WiFi™ hotspots and/or wireless service provider network cell towers or base stations having known locations. In example embodiments the mobile devices share their respective geographic locations with each other via wireless communications, and one or more of the mobile devices generates or receives geographic directions or vectors toward another of the mobile devices, based on the shared geographic locations. These directions enable or direct users of the mobile devices to navigate toward and meet each other.
Also shown in
The wireless telecommunications service provider network 101 contains appropriate infrastructure to support communications between the user devices 120, 130, 140 and also, in accordance with example embodiments, to support determining geographic locations of the user devices 120, 130, 140 (e.g., via cell tower or base station triangulation) and geographic directions or vector instructions for one or more of the user devices 120, 130, 140 to move toward another of the user devices 120, 130, 140. In particular, the wireless telecommunications service provider network 101 includes resources such as servers 104, 114, data stores 106, 116 and servers 108, 118 to variously support telecommunications services and functions.
In a first example embodiment, the user device 130 is a smart phone or smart watch that belongs to a child, and the user device 120 is a smart phone that belongs to a parent, and the child and parent are separated in a park such as a city park or a commercial theme park, and the parent decides that she would like the child to rejoin her. She sends a request, for example, via a navigation application on her smart phone, to or via a corresponding navigation application on the child's smart phone 130 for the child to make her way back to the parent. The applications share respective locations of the user devices 120, 130 (in this and other example embodiments each user device either knows its own geographic location based on received GPS signals and/or receives location information periodically from a wireless telecommunications service provider), and the application on the child's user device provides instructions or directions to the child via the interface 132 on how to navigate to the parent (i.e., the geographic location of the parent's user device 120). In example embodiments, the directions are requested by the application on the child's user device 130 or by the application on the parent's user device 120 from the wireless telecommunications service provider network 101 or third-party navigation service accessible through the Internet 105, which generates and sends the directions to the child's user device 130 for presentation to the child (and optionally to the parent's user device 120, to show a projected path of the child to the parent and/or provide progress updates to the parent on how the child is progressing in her journey back to the parent, optionally along with an estimated time of arrival, an elapsed duration of the journey, and so forth). The directions can be visual, for example, textual directions and/or images or arrows, vectors, or pathway(s) shown on a map, and/or aural (e.g., verbal instructions or simple tones to indicate proper direction and false directions), and/or haptic feedback (vibration patterns, frequencies, or intensities to indicate proper direction and false directions). The parent and child can also communicate with each other, for example, via text messages in the communications 132B of the interface 132 and/or the communications 122B of the interface 122, as part of the navigation applications and/or via regular text or voice smart phone communications between the user devices 120, 130. The user devices 120, 130 continue to periodically share location information, so that progress of the child in her journey is updated and continues to be reported to the parent, and so that, if the parent's location changes, then updated directions can be requested and sent to the child's user device 130 and optionally the parent's user device 120.
In a second embodiment similar to the first, the navigation process is triggered by the child requesting navigation to the parent, and an alert is optionally sent to the parent's user device 120 indicating that the child has made the request.
In a third embodiment similar to the first, the parent also requests navigation to the child, and consequently navigation instructions are requested and sent to the parent's smart phone (user device 120) to navigate the parent to the child (i.e., the child's smart phone or user device 130), and optionally also to the child's user device 130. In this embodiment both sets of navigation instructions are periodically updated or are updated as needed to reflect new locations of the user devices 120, 130 as the parent and child move along their respective journeys, and progress reports can be provided to both the parent and the child.
In a fourth embodiment similar to the third embodiment, navigation initially proceeds as outlined with respect to the first embodiment (the child is provided with navigation instructions to the parent). The parent also specifies or includes a time limit, so that if the child hasn't reached the parent by an expiration of the time limit, then the parent's user device 120 requests navigation to the child's user device 130 so that the parent can go find the child, as outlined with respect to the third embodiment. The time limit can be set in various ways. For example, the parent can explicitly set the time limit, can select a default time limit, or can select a function in the parent's navigation application (e.g., as a default selection or an active selection when the timeout function is selected or enabled) that determines the time limit based on an initial distance between the child's user device 130 and the parent's user device 120.
In a fifth embodiment similar to the fourth embodiment, upon expiration of the time limit, in addition to the (first) parent receiving navigation instructions to the child, a third person such as another parent of the child also receives navigation instructions to the child (via, for example, the user device 140), or navigation instructions to the first parent, in the same fashion as described above with respect to the third or fourth embodiments.
In a sixth embodiment that combines functions from the second embodiment with functions or operations from the fifth embodiment, the child requests navigation (via her user device 130) to the first parent (or the user device 120), and in response not only is she provided with directions to the first parent, but also both parents are alerted and provided with directions (via the user devices 120, 140) to the child (or the user device 130). This can be set up as a default when the child requests navigation to a parent or can be set to occur when the child requests navigation to a parent and also selects or sends a message to one or both parents that indicates urgency.
In a seventh embodiment that is a varied combination of the fourth and fifth embodiments, the child receives navigation instructions to a first parent (at the child's request, or at the first parent's request, or at the second parent's request) and then upon expiration of the time limit, the second parent also receives navigation instructions to the first parent, and the child and both parents are each apprised of the others' progress and locations.
In an eighth embodiment that builds on the first or second embodiments, after the child has begun navigation back to the first parent (user device 120), either the first parent or the second parent requests that the child be redirected to the second parent, so that updated navigation directions are sent to the child (i.e., the child's user device 130) to direct the child to the second parent (the user device 140). Thereafter, operation can optionally shift to any of the fifth, sixth, or seventh embodiments, with the roles of the first and second parents exchanged (e.g., with respect to adapting the seventh embodiment, upon expiration of the time limit, the first parent receives navigation instructions via the user device 120 to the second parent (i.e., the second parent's user device 140)).
In a ninth embodiment that builds on the fourth and eighth embodiments, after the child begins navigation back to the first parent, upon expiration of a time period, the child is redirected to the second parent, so that updated navigation directions are sent to the child (i.e., the child's user device 130) to direct the child to the second parent (the user device 140). Thereafter, operation can optionally shift to any of the fifth, sixth, or seventh embodiments, with the roles of the first and second parents exchanged (e.g., with respect to adapting the seventh embodiment, upon expiration of the time limit, the first parent receives navigation instructions via the user device 120 to the second parent (i.e., the second parent's user device 140)). As in the fourth embodiment, the time limit can be set in various ways. For example, either the first or second parent can explicitly set the time limit, can select a default time limit, or can select a function in the first or second parent's navigation application (e.g., as a default selection or an active selection when the timeout function is selected or enabled) that determines the time limit based on an initial distance between the child's user device 130 and the first parent's user device 120, or between the child's user device 130 and the second parent's user device 140.
Additional features can be variously provided in the example embodiments described herein. For example, if one of the user devices strays beyond a threshold distance from navigation path, then alerts or warnings and optionally additional navigation instructions can be provided to the straying user device or other user devices to redirect the straying user and/or vector other users to the straying user. The threshold distance can, for example, be predetermined, set by one or more of the users, or dynamically determined based on geographic features of terrain to be navigated or safety issues such as proximity to a busy street or crowded area. In example embodiments, security protocols can be employed, for example, to provide or limit a child's navigation options to a select or approved list of other user devices or mobile devices, and to allow emergency overrides (either to expand service/navigation options or contract them) based on inclement weather conditions, urgency of successfully brings mobile device users together, and so forth. In example embodiments, navigation can be automatically invoked not just upon expiration of time limits as variously described herein, but also on other conditions, including for example, when a parent's query to a child is not answered with a predetermined time interval, or is answered in a particular way that indicates a need or likelihood for navigation to be provided. Different navigation paths or navigation criteria can also be specified, for example, by a parent requesting that a child receive geographic directions to navigate to the parent, based on time to travel the navigation path, safety of the navigation path, or other factors that might affect success or efficiency of the navigation endeavor—for example, to route the child past a particular landmark or location, or to make it easier for the parent or another parent or trusted party to intercept and meet or join the child along the navigation path.
Further variations and implementation details are available in example embodiments. For example, any appropriate location services or location techniques or combinations thereof can be used, including but not limited to GPS positioning, cell tower/base station triangulation, WiFi™ network proximity or triangulation, self-reporting of a user via their user device 120, 130, 140 of proximity to a known landmark or street address, and so forth. Geographic directions or vectors or other journey instructions can be generated by a wireless telecommunications service provider (e.g., by resources on the network 101 or by cloud computing resources available to the wireless telecommunications service provider), by computation or navigation functions resident on one or more of the user devices 120, 130, 140, or can be generated by one or more third parties accessible, for example, via the Internet 105 as requested directly by one or more of the user devices 120, 130, 140 or indirectly by a wireless telecommunications service provider (e.g., via the network 101) with which the user device(s) has an account or service contract. In addition, although a child and two parents are variously described herein with respect to example embodiments, other example embodiments consistent with the principles and operations and functions described herein can be implemented with respect to different entities and different numbers of entities. For example, various embodiments can include multiple children, embodiments can be adapted to be used by multiple people in commercial, government or military relationships and activities, and so forth.
One or more instances of the computing device 201 can, for example, form a basis for the user devices 120, 130, 140 as well as for other equipment and functions of the wireless telecommunications service provider network 101, including for example, the servers 108, 118 as well as various functions described with respect to the process of
One or more instances of the router 203 can be variously located within and support routing functions within the wireless telecommunications service provider network 101. The router 203 includes processors 224, a communication interface 228, hardware 230, and a memory 226 that contains various software modules including a routing management module 234 that supports various routing functions of the router 203. A communication monitor module 236 can support monitoring of communications between the router 203 and other entities, for example, the Wi-Fi network 103, the Internet 105 and the user devices 120, 130, 140, to support analysis and management functions performed by the servers 108, 118 or other elements of the wireless telecommunications service provider or wireless telecommunications service provider network 101 with respect to the services and communications described herein. Also included are a user interface module 238 to facilitate direct communications with a human operator if needed, and a general operations module 232 that can enable the router 203 to accept and accomplish various tasks for the system or subsystem to which it more particularly belongs.
The memories 206, 226 optionally include computer-readable storage media. Computer-readable storage media can include or encompass volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules, or other data. Computer-readable storage media includes, but is not limited to, random access memory (RAM), read only memory (ROM), electrically erasable programmable read only memory (EEPROM), flash memory or other memory technology, compact disk—read only memory (CD-ROM), digital versatile disks (DVD), high-definition multimedia/data storage disks, or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store information for access by a computing device. As defined herein, computer-readable storage media do not consist of, and are not formed exclusively by, modulated data signals, such as a carrier wave.
In block 304, geographic locations of the mobile devices are received, for example, by a central authority, along with any context information (such as requests and request origins, applicable rules such as time limits described herein with respect to various embodiments). In this block, location information can also be shared, so that involved mobile devices receive or report their own locations and also receive location information pertaining to other mobile devices to which they will be directed and/or which will be directed to them. From block 304 the process moves to block 306.
In block 306, geographic navigation directions are provided to the mobile devices in accordance with various embodiments described herein, for example, to a first mobile device for navigating to a second mobile device as in the first embodiment, and to second and optionally third mobile devices for navigating to the first mobile device (or the other of the second or third mobile device) consistent with embodiments variously described herein. Status information is also conveyed, for example, progress of the first mobile device along its journey or path to the second mobile device is reported to the second mobile device for presentation or display to the second user (or user of the second mobile device). As noted elsewhere herein, the geographic navigation directions are variously generated by a wireless telecommunications service provider network, by one or more of the user devices or mobile devices, and/or by third-party or computational cloud resources accessible to the wireless telecommunications service provider or third party. From block 306, the process moves to block 308.
In block 308, updated mobile device location(s) and updated context information are received. For example, new locations reflecting movement of one or more of the mobile devices is shared and geographic navigation directions are updated accordingly and sent out to appropriate ones of the mobile devices, along with updated context information, which can include, for example, status information such as journey progress, proximity or degree of adherence of mobile devices to (or deviation from) directed navigation paths, or in other words, paths that the navigation directions direct mobile device(s) (or in other words their users) to follow along. Context information can also include information based on which rules are invoked and geographic navigation directions are updated or changed, for example, expirations of time as described for example with respect to various embodiments such as the fourth, sixth and seventh embodiments described herein. From block 308 the process moves to block 310.
In block 310, updated geographic navigation directions and status information are provided to the mobile devices in accordance with various embodiments described herein, so that the directions and information can be presented or displayed on the mobile devices for their respective users to act upon. The geographic navigation directions and status information are updated, for example, based on the location and context information received in block 308. The subprocess of blocks 308 and 310 can for example be repeated until involved mobile devices are co-located, one or more users of the mobile devices opt out of the process, or one or more other end conditions occur such as timing, failure of service, mobile device battery reserves below predetermined or critical levels, and so forth. The process shown in
Various embodiments provide technical advantages that enable greater service and functionality to be provided to users with greater efficiency and lower resource cost. For example, instead of requiring users to acquire and deploy specialized equipment to implement and use geographic wayfinding to navigate to each other, existing equipment and capabilities can be advantageously applied to provide greater functionality to users via their wireless mobile device without requiring additional devices or infrastructure, thus conserving material resources and energy.
Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.
This application is a continuation of U.S. application Ser. No. 16/920,285, filed Jul. 2, 2020, which claims the benefit of U.S. Application 62/905,289, filed Sep. 24, 2019, both of which are incorporated by reference.
Number | Name | Date | Kind |
---|---|---|---|
D578961 | Fisher et al. | Oct 2008 | S |
D647107 | Akana et al. | Oct 2011 | S |
8256612 | Wang | Sep 2012 | B1 |
D678298 | Burridge | Mar 2013 | S |
8554243 | Klassen | Oct 2013 | B2 |
D705160 | Ormesher et al. | May 2014 | S |
D714295 | Fujioka | Sep 2014 | S |
D716312 | Fujioka | Oct 2014 | S |
D725497 | Henne et al. | Mar 2015 | S |
D727259 | Hwang | Apr 2015 | S |
D729163 | Meyer | May 2015 | S |
9053588 | Briggs | Jun 2015 | B1 |
D735199 | Song | Jul 2015 | S |
D749570 | Lee | Feb 2016 | S |
D762203 | Chin et al. | Jul 2016 | S |
D763107 | Nielsen et al. | Aug 2016 | S |
D766905 | Lee | Sep 2016 | S |
D766906 | Kim | Sep 2016 | S |
D769879 | Kim | Oct 2016 | S |
D775126 | Odasso | Dec 2016 | S |
D780740 | Kim | Mar 2017 | S |
D784346 | Tao | Apr 2017 | S |
D786879 | Kim | May 2017 | S |
D792886 | Schwibner et al. | Jul 2017 | S |
9723439 | Segev et al. | Aug 2017 | B2 |
D797099 | Wieser et al. | Sep 2017 | S |
D800721 | Kim et al. | Oct 2017 | S |
D802151 | Bagatar et al. | Nov 2017 | S |
D807877 | Iwamatsu et al. | Jan 2018 | S |
D808961 | Lee et al. | Jan 2018 | S |
10039074 | Sargent | Jul 2018 | B1 |
D834029 | Wengreen | Nov 2018 | S |
10136251 | Parab et al. | Nov 2018 | B2 |
D838716 | Teng et al. | Jan 2019 | S |
D839753 | Domke et al. | Feb 2019 | S |
D841005 | Lin | Feb 2019 | S |
D841636 | Turk | Feb 2019 | S |
D843864 | Vandenbussche et al. | Mar 2019 | S |
10288444 | Andrew | May 2019 | B2 |
10299073 | Cornwall et al. | May 2019 | B2 |
D850968 | Zhang | Jun 2019 | S |
D851913 | Yu | Jun 2019 | S |
D853878 | Wright et al. | Jul 2019 | S |
D854433 | Vandenbussche et al. | Jul 2019 | S |
D855813 | Hu | Aug 2019 | S |
D856341 | Tur | Aug 2019 | S |
10423688 | Patton et al. | Sep 2019 | B1 |
D861766 | Lim et al. | Oct 2019 | S |
D862462 | Zhang | Oct 2019 | S |
D864767 | Vandenbussche et al. | Oct 2019 | S |
D869461 | Ke | Dec 2019 | S |
D869462 | Ke | Dec 2019 | S |
10511939 | Wihardja | Dec 2019 | B1 |
10511971 | Akpinar | Dec 2019 | B1 |
D872690 | Williams et al. | Jan 2020 | S |
D877145 | Shin | Mar 2020 | S |
D877153 | Peng | Mar 2020 | S |
D884061 | Arens et al. | May 2020 | S |
D884615 | Ito et al. | May 2020 | S |
D885229 | Kim | May 2020 | S |
D885230 | Kim | May 2020 | S |
10694331 | Brooks Powell | Jun 2020 | B1 |
D891366 | Xie et al. | Jul 2020 | S |
D891425 | Lin | Jul 2020 | S |
D893323 | Xiao | Aug 2020 | S |
D893420 | Xiao | Aug 2020 | S |
D893422 | Xiao | Aug 2020 | S |
D897350 | Wang | Sep 2020 | S |
D898745 | Ye | Oct 2020 | S |
D902933 | Zhang | Nov 2020 | S |
D903508 | Zhang | Dec 2020 | S |
D904498 | Lim et al. | Dec 2020 | S |
D909903 | Lin | Feb 2021 | S |
D911946 | Turksu et al. | Mar 2021 | S |
D912562 | Zhou | Mar 2021 | S |
D913138 | Maile et al. | Mar 2021 | S |
D913291 | Zhang | Mar 2021 | S |
D918137 | Painter et al. | May 2021 | S |
D918696 | Painter et al. | May 2021 | S |
D920143 | Painter et al. | May 2021 | S |
D920147 | Liu | May 2021 | S |
D920662 | Youn | Jun 2021 | S |
D922947 | Wang et al. | Jun 2021 | S |
D923003 | Lin | Jun 2021 | S |
D924715 | Wright et al. | Jul 2021 | S |
D924716 | Wright et al. | Jul 2021 | S |
D925385 | Lin | Jul 2021 | S |
D925543 | Ma | Jul 2021 | S |
D931209 | Hahn et al. | Sep 2021 | S |
D931286 | Tur | Sep 2021 | S |
D931287 | Tur | Sep 2021 | S |
D932321 | Jung | Oct 2021 | S |
D934869 | Wright et al. | Nov 2021 | S |
D935397 | Brisebras et al. | Nov 2021 | S |
D935398 | Wang et al. | Nov 2021 | S |
D941763 | Pena et al. | Jan 2022 | S |
D942458 | Tur | Feb 2022 | S |
D945965 | Wang et al. | Mar 2022 | S |
D947122 | Dastmalchi et al. | Mar 2022 | S |
D947179 | Yin | Mar 2022 | S |
D949038 | Hu | Apr 2022 | S |
20020169539 | Menard | Nov 2002 | A1 |
20100243516 | Martin et al. | Sep 2010 | A1 |
20100295656 | Herickhoff | Nov 2010 | A1 |
20110046878 | Sung | Feb 2011 | A1 |
20110297578 | Stiehl et al. | Dec 2011 | A1 |
20120043236 | Szucs et al. | Feb 2012 | A1 |
20120257340 | Kim | Oct 2012 | A1 |
20130144523 | Haney | Jun 2013 | A1 |
20130148955 | Overall | Jun 2013 | A1 |
20130222139 | Gouge et al. | Aug 2013 | A1 |
20130279142 | Wang | Oct 2013 | A1 |
20140114564 | Callaghan | Apr 2014 | A1 |
20140171059 | Parker | Jun 2014 | A1 |
20140216953 | Su et al. | Aug 2014 | A1 |
20150219458 | Shah | Aug 2015 | A1 |
20150296341 | Cecchini | Oct 2015 | A1 |
20160140302 | Saulnier | May 2016 | A1 |
20160191637 | Memon | Jun 2016 | A1 |
20160196525 | Kantor | Jul 2016 | A1 |
20160300185 | Zamer | Oct 2016 | A1 |
20170045627 | Larsson | Feb 2017 | A1 |
20170064490 | Jin | Mar 2017 | A1 |
20170115125 | Outwater | Apr 2017 | A1 |
20170188199 | Ashley, Jr. | Jun 2017 | A1 |
20170248922 | Hynecek | Aug 2017 | A1 |
20170272916 | Stewart | Sep 2017 | A1 |
20170295468 | Snyder | Oct 2017 | A1 |
20180146011 | Nagao | May 2018 | A1 |
20180176271 | Laurent | Jun 2018 | A1 |
20190035171 | Jayanthi | Jan 2019 | A1 |
20190297049 | Serad | Sep 2019 | A1 |
20190369563 | Chen et al. | Dec 2019 | A1 |
20200042080 | Lyren | Feb 2020 | A1 |
20200053510 | Snyder | Feb 2020 | A1 |
20200363773 | Wang et al. | Nov 2020 | A1 |
20210092554 | Painter | Mar 2021 | A1 |
20210368293 | Painter | Nov 2021 | A1 |
20220007164 | Sutherland | Jan 2022 | A1 |
Number | Date | Country |
---|---|---|
2022038897 | Mar 2022 | JP |
WO-2013188717 | Dec 2013 | WO |
2013188717 | Jul 2014 | WO |
WO-2015157487 | Oct 2015 | WO |
2016117926 | Jul 2016 | WO |
WO-2016117926 | Jul 2016 | WO |
Entry |
---|
Hands On with the T-Mobile SyncUp Kids Watch phonescoop.com; Nov. 2021 [online]. © 2001-2021 Phone Factor, LLC. [retrieved Dec. 15, 2021] from Internet: (Year: 2021). |
U.S. Appl. No. 29/761,517, Office Action dated Dec. 20, 2021, 18 pages. |
U.S. Appl. No. 29/761,523, Notice of Allowance dated Dec. 8, 2021, 36 pages. |
Automatic dependent surveillance—broadcast. Wikipedia, Apr. 16, 2020 [retrieved on Jul. 2, 2020] Retrieved from the Internet URL: https://en.wikipedia.org/wiki/Automatic_dependent_surveillance_-_broadcast. |
Find your way. And find your way around. Apple.com [retrieved on Jul. 2, 2020] Retrieved from the Internet URL: https://www.apple.com/ios/maps. |
Locate a friend in Find My on iPhone. Apple.com [retrieved on Jul. 2, 2020] Retrieved from the Internet URL: https://support.apple.com/guide/iphone/locate-a-friend-ipha24eb4a37/ios. |
U.S. Appl. No. 16/920,285, Non-Final Office Action dated Dec. 24, 2020, 23 pages. |
U.S. Appl. No. 16/920,285, Notice of Allowance dated Apr. 29, 2021, 16 pages. |
Wolfhound-PRO Cell Phone Detector. Berkeley Varitronics Systems, [retrieved on Jul. 2, 2020] Retrieved from the Internet URL: https://www.bvsystems.com/product/wolfhound-pro-cell-phone-detector/. |
Amazon.com: Conido Charging Stand for Apple Watch. Date first available of Mar. 17, 2020. Retrieved from the internet at [https://www.amazon.com/conido-charging-magnetic-wireless-compatible/dp/B085ZHH7LW], Mar. 22, 2022. 1 page. (Year: 2020). |
U.S. Appl. No. 29/761,517, Corrected Notice of Allowability dated Jun. 8, 2022, 11 pages. |
U.S. Appl. No. 29/761,517, Notice of Allowance dated May 4, 2022, 21 pages. |
U.S. Appl. No. 29/761,519, Office Action dated Mar. 25, 2022, 22 pages. |
U.S. Appl. No. 29/761,522, Office Action dated Apr. 25, 2022, 23 pages. |
U.S. Appl. No. 29/761,523, Notice of Allowance dated May 3, 2022, 23 pages. |
U.S. Appl. No. 29/761,523, Notice of Allowance dated Mar. 24, 2022, 27 pages. |
U.S. Appl. No. 29/761,519, Notice of Allowance dated Aug. 31, 2022, 19 pages. |
U.S. Appl. No. 29/761,522, Notice of Allowance dated Aug. 24, 2022, 22 pages. |
Number | Date | Country | |
---|---|---|---|
20210368293 A1 | Nov 2021 | US |
Number | Date | Country | |
---|---|---|---|
62905289 | Sep 2019 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 16920285 | Jul 2020 | US |
Child | 17393826 | US |