The application relates generally to mesh networks applied to fixed establishments with movable items therein.
A mesh network is a type of computer ecosystem characterized by its sustainability, self-organization, and scalability. Each mesh node relays network data flowing to the node, and the nodes cooperate to appropriately distribute the data in the network. Typically, mesh networks are relatively short range networks, i.e., with node-to-node link distances of 250 meters or less, although a mesh network may use a gateway to connect to a wide area network such as the Internet.
Because mesh networks typically are wireless, they are ad hoc, meaning that nodes easily join and leave the network. As but one example, mesh networks can be spontaneously organized by the wireless computing devices establishing the nodes using Zigbee. Other example non-limiting mesh network protocols/systems can be based on Wi-Fi IEEE 802.11p, IEEE 802.11s, WAVE IEEE 1609, WiMAX IEEE 802.16, Bluetooth, and IRA.
When the wireless nodes of a mesh network move as the network operates, the network is sometimes referred to as a mobile ad hoc network (MANET) which continuously self-configures as nodes move into network range and out of network range. For this reason, nodal links in MANETs change frequently. MANETs may operate independently but may also use one or more of the nodes as a gateway to other MANETs and other networks such as the Internet.
Of relevance to this application is the application of mesh/MANET principles to fixed establishments with movable items therein.
As understood herein, fixed establishments such as factory floors, grocery stores, etc. have the need to run as efficiently as possible. But often the information tracked is not done in real-time. Present principles apply mesh network principles with and having a database collecting sensor data from the establishment to track and respond to the data in near real-time.
Accordingly, a system includes a mesh network dynamically established among first computerized node modules operatively engaged with respective movable items in a building. At least some of the first computerized node modules communicate at least respective location information among each other. At least one monitoring computer receives location information from at least the first computerized node modules via at least one access point (AP) communicating with at least one of the first computerized node modules.
In some examples second computerized node modules are operatively engaged with immovable items in the building and at least one first computerized node module communicating with at least one second computerized node module.
In example implementations the first computerized node modules (FCNM) are located in a store, and the respective movable items communicate with a node module operatively engaged with a shopping cart in which the FCNM are located. The node module operatively engaged with a shopping cart in which the FCNM are located communicates item data from the movable items in the shopping cart to a checkout station node module. The item data can include item type. A computer adds prices for the movable items in the shopping cart and presents a sum representative thereof on an example display. The example display presents a “yes” selector selectable to agree to pay the sum and a “no” selector selectable to decline to pay the sum. The example display may be a display of a consumer electronics (CE) device of a shopper which downloads an application from a store computer and provides its network address to the store computer and updates the store computer with its location information. The store computer may correlate CE device location with a shopping cart based on the CE device location being closest to a particular shopping cart than it is to other shopping carts.
In other examples the first computerized node modules (FCNM) are located in a factory.
In another aspect, a device includes a display, a computer readable storage medium bearing instructions executable by a processor, and a processor configured for accessing the computer readable storage medium to execute the instructions to configure the processor to present on the display a user interface (UI) populated with information from a store computer including total price of items in a shopping container automatically uploaded to the store computer from mesh network nodes associated with the items. The UI includes a prompt selectable to agree to pay the total price.
In another aspect, a non-transitory computer readable storage medium (NTCRSM) bears instructions executable by a processor to configure the processor to present on a display a user interface (UI) populated with information from a store computer including total price of items in a shopping container automatically uploaded to the store computer from mesh network nodes associated with the items. The UI includes a prompt selectable to agree to pay the total price.
The details of the present invention, both as to its structure and operation, can be best understood in reference to the accompanying drawings, in which like reference numerals refer to like parts, and in which:
This disclosure relates generally to computer ecosystems and in particular to mesh networks and MANETs. A system herein may include server and client components that establish mesh network nodes, connected over a network such that data may be exchanged between the client and server components, although mesh networks may not include servers. The nodes may include one or more computing devices including portable televisions (e.g. smart TVs, Internet-enabled TVs), portable computers such as laptops and tablet computers, and other mobile devices including smart phones, mesh node modules that can be attached to moving objects, and additional examples discussed below. These devices may operate with a variety of operating environments. For example, some of the devices may employ, as examples, operating systems from Microsoft, or a Unix operating system, or operating systems produced by Apple Computer or Google.
Nodes, however implemented, may include one or more processors executing instructions that configure the node to receive and transmit data over a mesh network such as a MANET. A device such as a server may be instantiated by a game console such as a Sony Playstation (trademarked), a personal computer, etc.
Information may be exchanged over a network between network nodes. To this end and for security, nodes can include firewalls, load balancers, temporary storages, and proxies, and other network infrastructure for reliability and security. One or more nodes may form an apparatus that implement methods of providing a secure community such as an online social website to network members.
As used herein, instructions refer to computer-implemented steps for processing information in the system. Instructions can be implemented in software, firmware or hardware and include any type of programmed step undertaken by components of the system.
A processor may be any conventional general purpose single- or multi-chip processor that can execute logic by means of various lines such as address lines, data lines, and control lines and registers and shift registers.
Software modules described by way of the flow charts and user interfaces herein can include various sub-routines, procedures, etc. Without limiting the disclosure, logic stated to be executed by a particular module can be redistributed to other software modules and/or combined together in a single module and/or made available in a shareable library.
Present principles described herein can be implemented as hardware, software, firmware, or combinations thereof; hence, illustrative components, blocks, modules, circuits, and steps are set forth in terms of their functionality.
Further to what has been alluded to above, logical blocks, modules, and circuits described below can be implemented or performed with a general purpose processor, a digital signal processor (DSP), a field programmable gate array (FPGA) or other programmable logic device such as an application specific integrated circuit (ASIC), discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A processor can be implemented by a controller or state machine or a combination of computing devices.
The functions and methods described below, when implemented in software, can be written in an appropriate language such as but not limited to C# or C++, and can be stored on or transmitted through a computer-readable storage medium such as a random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), compact disk read-only memory (CD-ROM) or other optical disk storage such as digital versatile disc (DVD), magnetic disk storage or other magnetic storage devices including removable thumb drives, etc. A connection may establish a computer-readable medium. Such connections can include, as examples, hard-wired cables including fiber optics and coaxial wires and digital subscriber line (DSL) and twisted pair wires. Such connections may include wireless communication connections including infrared and radio.
Components included in one embodiment can be used in other embodiments in any appropriate combination. For example, any of the various components described herein and/or depicted in the Figures may be combined, interchanged or excluded from other embodiments.
“A system having at least one of A, B, and C” (likewise “a system having at least one of A, B, or C” and “a system having at least one of A, B, C”) includes systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and/or A, B, and C together, etc.
Now specifically referring to
The nodes 12 may all be mobile nodes and may communicate only within the network 10, and not outside the network 10. More typically, at least one of the nodes 12 is a router or other gateway device that interfaces the mesh network 10 with other networks, such as the Internet. In some embodiments, one or more of the nodes 12 may be a fixed node, e.g., a gateway router or a server whose location does not change after installation or changes only infrequently, with the remaining node(s) 12 being mobile, while in some embodiments all of the nodes 12 may be fixed nodes.
In any case, the node 12 dynamically establish a mesh network, typically through one or more of the short-range transmitters described below. Each node typically is associated with a unique identification such as a media access control (MAC) address, and the MAC address may be correlated within the node (e.g., at time of manufacture or by a user at time of association with a particular component) or within a network server receiving information from the node with an identification of the component with which the MAC address is associated. For example, a nodal module may be associated with a vehicle, a person, an animal, a bicycle, a piece of luggage or a pet kennel, a particular stadium seat, an item in a factory or store, a user's CE device, etc., and the MAC address of that node may be correlated with the component accordingly. Consequently, when a mesh network is established and at least one of the network nodes uploads information gathered from the other nodes, that information may include (or be correlated at a server to) a type of component, so that a network map or other network information user interface (UI) may be presented showing the mesh nodes along with an identification of the components, and not just the MAC addresses, with which the nodes are associated.
In addition to the foregoing, the node 12 may also include one or more input ports 26 such as, e.g., a high definition multimedia interface (HDMI) port or a USB port to physically connect (e.g. using a wired connection) to another CE device and/or a headphone port to connect headphones to the node 12 for presentation of audio from the node 12 to a user through the headphones. For example, the input port 26 may be connected via wire or wirelessly to a cable or satellite source of audio video content. Thus, the source may be, e.g., a set top box, or a satellite receiver, or a game console or disk player.
The node 12 may further include one or more tangible computer readable storage medium 28 such as disk-based or solid state storage. The data storage may contain the identification and price, for example, of an item on which it is to be applied or engaged. Also in some embodiments, the node 12 can include one or more position or location receivers such as but not limited to a cellphone receiver, GPS receiver and/or altimeter 30 that is configured to e.g. receive geographic position information from at least one satellite or cellphone tower and provide the information to the processor 24 and/or determine an altitude at which the node 12 is disposed in conjunction with the processor 24. However, it is to be understood that that another suitable position receiver other than a cellphone receiver, GPS receiver and/or altimeter may be used in accordance with present principles to e.g. determine the location of the node 12 in e.g. all three dimensions.
Continuing the description of the node 12, in some embodiments the NODE 12 may include one or more cameras 32 that may be, e.g., a thermal imaging camera, a digital camera such as a webcam, and/or a camera integrated into the node 12 and controllable by the processor 24 to gather pictures/images and/or video in accordance with present principles. Also included on the node 12 may be a Bluetooth transceiver 34 and other Near Field Communication (NFC) element 36 for communication with other devices using Bluetooth and/or NFC technology, respectively. An example NFC element can be a radio frequency identification (RFID) element.
Further still, the node 12 may include one or more auxiliary sensors 37 (e.g., a motion sensor such as an accelerometer, gyroscope, cyclometer, or a magnetic sensor, an infrared (IR) sensor, an optical sensor, a speed and/or cadence sensor, a gesture sensor (e.g. for sensing gesture command), other type of proximity sensor such as a camera executing image recognition to determine a particular object is close, etc.) providing input to the processor 24. The node 12 may include an over-the-air TV broadcast port 38 for receiving OTA TV broadcasts providing input to the processor 24. In addition to the foregoing, it is noted that the node 12 may also include an infrared (IR) transmitter and/or IR receiver and/or IR transceiver 40 such as an IR data association (IRDA) device. A battery (not shown) may be provided for powering the node 12.
The node 12 may include still other sensors such as e.g. one or more climate sensors 42 (e.g. barometers, humidity sensors, wind sensors, light sensors, temperature sensors, etc.) and/or one or more biometric sensors 44 providing input to the processor 24. For instance, the biometric sensor(s) may include heart rate sensors, temperature sensors, blood pressure sensors, blood sugar sensors, perspiration sensors, etc.
The above methods may be implemented as software instructions executed by a processor, suitably configured ASIC or FPGA modules, or any other convenient manner as would be appreciated by those skilled in those art. Where employed, the software instructions may be embodied in a non-transitory device such as a CD Rom or Flash drive. The software code instructions may alternatively be embodied via a download over the internet.
In the example shown, the nodes can include immovable items 58 with respective node modules 60, and movable items 62 with respective node modules 64. People 66 within the establishment housing the mesh network 50 may also wear respective node modules 68 on their persons, with the node modules 60, 64, 68 communicating with each other according to mesh network principles.
In some embodiments, the mesh network 50 is in a building such as a factory, the immovable items 58 are shelves or machines, and the movable items are work pieces or finished products. In other embodiments the mesh network is in a grocery store or other vending establishment, the immovable items are shelves or display cases, and the movable items 62 are items to be purchased, e.g., groceries or dry goods. These are but two example embodiments of establishments in which the mesh network 50 may be installed.
In such bounded environment, by means of the mesh network 50 it is possible to identify or predict optimal resource allocation for varying conditions and circumstances. For example, assume it is determined that there are four or five customers waiting in each line at the grocery store, based on their respective modules 68. Based on this information, more cashiers can automatically be dispatched to help decrease waiting time, thus providing better customer service.
Preferably, the mesh network 50 includes node modules engaged with all possible items in a particular environment. For example, in a factory, meshed sensor networks can be placed on every stationary and mobile items, including people (wearable technology). The mesh network can include audio and video feeds as well from video camera(s) 70 and microphone(s) 72 communicating with the monitoring computer 56, e.g., via APs 52. Just-in-time inventory is thus maintained of all items arriving using position signals from their respective node modules, as well as those items in process. Defective parts including why they failed and where they failed based on sensor data from their respective node modules also may be tracked, with this information being used to ensure there are replacement parts available or dispatch someone to repair the defect.
In the grocery store context, each stock item may include its own node module 64, and each cart may likewise include its own node module, in effect being a master node to the node of the items in the cart in a sub-mesh network. A fixed node module 62 at a checkout station can communicate with the node module of the cart, which receives items information from the node modules 64 of the items in the cart, and automatically produce an item list and pricing for payment. A customer may then swipe an electronic payment card at the checkout station to pay for the items without unloading the items from the cart, since all the items in a particular cart are network meshed together and report directly (through the cart node module) to the store's database network. Thus no cashier is required, just a checkout station to pay via credit card. This maintains checkout lines to an absolute minimum, making the store very efficient.
Proceeding to block 82, location signals may be received at, e.g., the monitoring computer 56 from the nodes in the network 50 as such information is relayed among the nodes and eventually through an AP 52. Also, audio and video feeds may be received at block 84 from the cameras 70 and microphone 72, and audio video information displayed at block 86.
Accordingly, a UI can be populated with information from a store computer including total price and presented on the CE device of the shopper. An amount to pay prompt (whether the shopper agrees to pay) may be presented on the CE device. Responsive to a “no” response from the CE device at decision diamond 92, an error is returned at state 94. Responsive to a “yes” response from the CE device at decision diamond 92, using the shopper ID from, e.g., the CE device or the shopper's electronic payment card or other shopper-associated device, an account of the shopper is debited for the total amount of the items at block 96.
A message 106 can be presented indicating a location within the store of an item on the list, and a sub-message 108 may indicate that the item which is the subject of the message 106 is on sale.
It will be appreciated that while the MESH NETWORK APPLIED TO FIXED ESTABLISHMENT WITH MOVABLE ITEMS THEREIN has been fully described in relation to one or more example embodiments, these are not intended to be limiting, and that various alternative arrangements may be used to implement the subject matter claimed herein.
Number | Name | Date | Kind |
---|---|---|---|
3985357 | Miller | Oct 1976 | A |
4123511 | Heintze | Oct 1978 | A |
4301207 | Schomerus | Nov 1981 | A |
4340053 | Sarui | Jul 1982 | A |
4463949 | McCoy, Sr. et al. | Aug 1984 | A |
4625336 | Derderian | Dec 1986 | A |
4962935 | Williams | Oct 1990 | A |
4992003 | Perach | Feb 1991 | A |
5154266 | Bieber et al. | Oct 1992 | A |
5201075 | Svetich | Apr 1993 | A |
5219316 | Huffman | Jun 1993 | A |
5413328 | Glancey et al. | May 1995 | A |
5639243 | Ryan et al. | Jun 1997 | A |
5742521 | Ellenby et al. | Apr 1998 | A |
5755405 | Socha et al. | May 1998 | A |
5927233 | Mainini et al. | Jul 1999 | A |
6401250 | McNabb | Jun 2002 | B1 |
6438755 | MacDonald et al. | Aug 2002 | B1 |
6588840 | Lombardo | Jul 2003 | B1 |
6742636 | Godshaw | Jun 2004 | B2 |
6810831 | Opfel | Nov 2004 | B1 |
6816460 | Ahmed et al. | Nov 2004 | B1 |
6910447 | Azarian | Jun 2005 | B1 |
6946817 | Fischer et al. | Sep 2005 | B2 |
7323981 | Peel et al. | Jan 2008 | B2 |
7328671 | Kates | Feb 2008 | B2 |
7416123 | Saperstein et al. | Aug 2008 | B2 |
7438356 | Howman et al. | Oct 2008 | B2 |
7451927 | Saperstein et al. | Nov 2008 | B2 |
7626966 | Ruiter et al. | Dec 2009 | B1 |
7714708 | Brackmann et al. | May 2010 | B2 |
7753826 | Oliver et al. | Jul 2010 | B1 |
7768150 | Platania et al. | Aug 2010 | B2 |
7770539 | Zimmerman et al. | Aug 2010 | B1 |
7818820 | Tsujimoto | Oct 2010 | B2 |
7916025 | Locker et al. | Mar 2011 | B2 |
7962186 | Cui et al. | Jun 2011 | B2 |
8126782 | Zhu et al. | Feb 2012 | B1 |
8149748 | Bata et al. | Apr 2012 | B2 |
8233846 | Rofougaran | Jul 2012 | B2 |
8253557 | Ani et al. | Aug 2012 | B2 |
8366570 | DeMarco et al. | Feb 2013 | B1 |
8526970 | Wala et al. | Sep 2013 | B2 |
8568191 | Rehkemper et al. | Oct 2013 | B2 |
8583182 | Piirainen et al. | Nov 2013 | B2 |
8609454 | Dai et al. | Dec 2013 | B2 |
8624743 | Langer et al. | Jan 2014 | B2 |
8719001 | Izdepski et al. | May 2014 | B1 |
8878671 | Buchheim et al. | Nov 2014 | B2 |
9167905 | Pajic | Oct 2015 | B2 |
9310205 | Xu et al. | Apr 2016 | B2 |
9577463 | McCoy et al. | Feb 2017 | B2 |
9654179 | Shultz et al. | May 2017 | B2 |
20040125493 | Shimotono et al. | Jul 2004 | A1 |
20040141635 | Liang et al. | Jul 2004 | A1 |
20040167367 | Beierle | Aug 2004 | A1 |
20050034083 | Jaeger | Feb 2005 | A1 |
20050127868 | Calhoon et al. | Jun 2005 | A1 |
20050259033 | Levine | Nov 2005 | A1 |
20050284405 | Pomakoy-Poole et al. | Dec 2005 | A1 |
20060063540 | Beuck | Mar 2006 | A1 |
20060080072 | Lachman et al. | Apr 2006 | A1 |
20060154642 | Scannell, Jr. | Jul 2006 | A1 |
20060224300 | Shioya et al. | Oct 2006 | A1 |
20060242901 | Casimaty et al. | Nov 2006 | A1 |
20070069687 | Suzuki | Mar 2007 | A1 |
20070130893 | Davies | Jun 2007 | A1 |
20070138272 | Saperstein et al. | Jun 2007 | A1 |
20070138273 | Saperstein et al. | Jun 2007 | A1 |
20070152479 | Howman et al. | Jul 2007 | A1 |
20070243296 | Bourassa et al. | Oct 2007 | A1 |
20080036610 | Hokuf et al. | Feb 2008 | A1 |
20080120768 | Tsujimoto | May 2008 | A1 |
20080173257 | Steiner et al. | Jul 2008 | A1 |
20080189170 | Ramachandra | Aug 2008 | A1 |
20080211641 | Murray et al. | Sep 2008 | A1 |
20080229704 | Augustyniak et al. | Sep 2008 | A1 |
20080237339 | Stawar | Oct 2008 | A1 |
20090040048 | Locker et al. | Feb 2009 | A1 |
20090118869 | Cauchy et al. | May 2009 | A1 |
20090203367 | Pamminger et al. | Aug 2009 | A1 |
20100020169 | Jang et al. | Jan 2010 | A1 |
20100119755 | Chung et al. | May 2010 | A1 |
20100123778 | Hada | May 2010 | A1 |
20100152545 | Ramsay et al. | Jun 2010 | A1 |
20100295687 | Kuzniar et al. | Nov 2010 | A1 |
20110005466 | Furth | Jan 2011 | A1 |
20110031928 | Soar | Feb 2011 | A1 |
20110068906 | Shafer | Mar 2011 | A1 |
20110068922 | Ross | Mar 2011 | A1 |
20110105099 | Roll | May 2011 | A1 |
20110156640 | Moshfeghi | Jun 2011 | A1 |
20110178863 | Daigle | Jul 2011 | A1 |
20110270712 | Wood | Nov 2011 | A1 |
20120069051 | Hagbi et al. | Mar 2012 | A1 |
20120099800 | Llano et al. | Apr 2012 | A1 |
20120158297 | Kim | Jun 2012 | A1 |
20120184200 | Chutorash et al. | Jul 2012 | A1 |
20120303939 | Cain et al. | Nov 2012 | A1 |
20120319487 | Shah | Dec 2012 | A1 |
20130015705 | Abe | Jan 2013 | A1 |
20130027561 | Lee | Jan 2013 | A1 |
20130056929 | Rehkemper et al. | Mar 2013 | A1 |
20130063304 | Almohsen | Mar 2013 | A1 |
20130068942 | Verenchikov | Mar 2013 | A1 |
20130093220 | Pajic | Apr 2013 | A1 |
20130132434 | Scofield et al. | May 2013 | A1 |
20130134923 | Smith et al. | May 2013 | A1 |
20130141251 | Sims et al. | Jun 2013 | A1 |
20130279409 | Dublin et al. | Oct 2013 | A1 |
20130292976 | Kane | Nov 2013 | A1 |
20130325940 | Foti | Dec 2013 | A1 |
20140023060 | Apte et al. | Jan 2014 | A1 |
20140025805 | Apte et al. | Jan 2014 | A1 |
20140046802 | Hosein et al. | Feb 2014 | A1 |
20140058866 | Okadome | Feb 2014 | A1 |
20140104046 | Howell | Apr 2014 | A1 |
20140117921 | Suomela | May 2014 | A1 |
20140118635 | Yang | May 2014 | A1 |
20140148095 | Smith et al. | May 2014 | A1 |
20140173439 | Gutierrez et al. | Jun 2014 | A1 |
20140179463 | Giles et al. | Jun 2014 | A1 |
20140236653 | Farrell | Aug 2014 | A1 |
20150039458 | Reid | Feb 2015 | A1 |
20150194814 | Taylor et al. | Jul 2015 | A1 |
20150348413 | Han et al. | Dec 2015 | A1 |
20150349537 | Milne et al. | Dec 2015 | A1 |
20150349572 | McCoy et al. | Dec 2015 | A1 |
20150382144 | Lopez | Dec 2015 | A1 |
20160019515 | Milne et al. | Jan 2016 | A1 |
20160019788 | Milne et al. | Jan 2016 | A1 |
20160021491 | Milne et al. | Jan 2016 | A1 |
20160021492 | Carlsson et al. | Jan 2016 | A1 |
20160021493 | Milne et al. | Jan 2016 | A1 |
20160021510 | Milne et al. | Jan 2016 | A1 |
20160048861 | Morgaine | Feb 2016 | A1 |
20160049993 | McCoy et al. | Feb 2016 | A1 |
20160233727 | Ollikainen et al. | Aug 2016 | A1 |
20170063431 | Milne et al. | Mar 2017 | A1 |
Number | Date | Country |
---|---|---|
101783931 | Jul 2010 | CN |
101978370 | Feb 2011 | CN |
101911668 | Nov 2014 | CN |
2004233269 | Aug 2004 | JP |
2005017465 | Jan 2005 | JP |
2006279859 | Oct 2006 | JP |
2013168883 | Aug 2013 | JP |
20140030707 | Mar 2014 | KR |
200845889 | Dec 2008 | TW |
201221051 | Jun 2012 | TW |
2009051449 | Jul 2009 | WO |
2009130199 | Oct 2009 | WO |
2010078616 | Jul 2010 | WO |
2013105920 | Jul 2013 | WO |
Entry |
---|
Arzoo Dahiya, Dr. R.K. Chauhan, “A Comparative Study of MANET and VANET Environment” Journal of Computing, vol. 2, Issue 7, Jul. 2010, ISSN 2151-9617. http://sites.google.com/site/JournalofComputing/. |
Yousaf Saeed, Suleman Aziz Lodhi, Khalil Ahmed, “Obstacle Management in VANET using Game Theory and Fuzzy Logic Control”, ACEEE Int. J. on Communications, vol. 4, No. 1, Jul. 2013. |
The Seventh ACM International Workshop on Vehicular Inter-NETworking (VANET 2010) in conjunction with ACM MobiCom 2010. Sep. 24, 2010. |
Tao Zhang, Xian Chen, Russell Hsing, K. Dnaiel Wong,“VNTA sub-TC” IEEE Communications Society, printed from web Jun. 3, 2014, http://www.danielwireless.com/vnta/. |
Reza Azimi, Gaurav Bhatia, Ragunathan (RAJ) Rajkumar, Priyantha Mudalige, “Vehicular Networks for Collision Avoidance at Intersections” Society for Automotive Engineers (SAE) World Congress, Apr. 2011, Detroit, MI, USA. |
Danda B. Rawat, Dimitrie C. Popescu, Gongjun Yan, Stephan Olariu, “Enhancing VANET Performance by joint Adaptation of Transmission Power and Contention Window Size”, IEEE Transaction on Parallel and Distributed Systems, vol. 22, No. 9, pp. 1528-1535, Sep. 2011. |
Stephan Eichler, Benedikt Ostermaier, Christopher Schroth, Timo Kosch, “Simulation of Car-to-Car Messaging: Analyzing the Impact on the Road Traffic”, IEEE Computer Society, 2005; 13th Annual Meeting of the IEEE International Symposium on Modeling, Analysis, and Simulation of Computer and Telecommunications Systems (MASCOTS). |
J. Gonzalvez, M. Sepulcre, R. Bauza, “IEEE 802.11p Vehicle to Infrastructure Communications in Urban Environments” IEEE Communications Magazine, vol. 50, No. 5, pp. 176-183, May 2012. |
James R. Milne, Gregory Peter Carlsson, Frederick J. Zustak, “Applying Mesh Network to Pet Carriers”, related U.S. Appl. No. 14/333,006, Final Office Action dated Oct. 28, 2015. |
James R. Milne, Gregory Peter Carlsson, Frederick J. Zustak, “Applying Mesh Network to Pet Carrier”, applicants response to final office action filed Oct. 28, 2015 in related pending U.S. Appl. No. 14/333,006. |
James R. Milne, Gregory Peter Carlsson, Frederick J. Zustak, “Applying Mesh Network to Pet Carrier”, non-final office action dated Dec. 4, 2015 in related pending U.S. Appl. No. 14/333,006. |
James R. Milne, Gregory Peter Carlsson, Frederick J. Zustak, “Applying Mesh Network to Pet Carrier”, applicants response to non-final office action filed Dec. 10, 2015 in related pending U.S. Appl. No. 14/333,006. |
Charles McCoy, James R. Milne, True Xiong, “Portable Device to Portable Device Wireless Power Transfer Methods and Systems” , related pending U.S. Appl. No. 14/290,409, non-final office action dated Apr. 19, 2016. |
James P. Milne, Gregory Peter Carlsson, Frederick J. Zustak, “Applying Mesh Network to Pet Carriers”, related U.S. Appl. No. 14/333,066, Applicant's response to Final Office Action filed Oct. 28, 2015. |
James R. Milne, Gregory Peter Carlsson, Frederick J. Zustak, “Applying Mesh Network to Pet Carriers”, related U.S. Appl. No. 14/333,006, Final Office Action dated Feb. 22, 2016. |
James R. Milne, Gregory Peter Carlsson, Frederick J. Zustak, “Applying Mesh Network to Pet Carriers”, related U.S. Appl. No. 14/333,006, Applicant's response to Final Office Action filed Mar. 16, 2016. |
James R. Milne, Gregory Peter Carlsson, Frederick J. Zustak, “Applying Mesh Network to Luggage”, related U.S. Appl. No. 14/332,919, Applicant's response to Final Office Action filed Jun. 14, 2016. |
Gregory Peter Carlsson, Frederick J. Zustak, James R. Milne, “Mesh Network Applied to Arena Events”, related U.S. Appl. No. 14/332,953, Non-Final Office Action dated Jun. 30, 2016. |
Gregory Peter Carlsson, Frederick J. Zustak, James R. Milne, “Mesh Network Applied to Arena Events”, related U.S. Appl. No. 14/332,953, Applicant's response to Non-Final Office Action filed Jun. 30, 2016. |
James R. Milne, Gregory Peter Calrsson, Frederick J. Zustak, “Vehicle Ad Hoc Network (VANET)”, related U.S. Appl. No. 14/332,900, Non-Final Office Action dated Jan. 14, 2016. |
James R. Milne, Gregory Peter Calrsson, Frederick J. Zustak, “Vehicle Ad Hoc Network (VANET)”, related U.S. Appl. No. 14/332,900, Applicant's response to Non-Final Office Action filed Jan. 15, 2016. |
James R. Milne, Gregory Peter Carlsson, Frederick J. Zustak, “Applying Mesh Network to Luggage”, related pending U.S. Appl. No. 14/332,919, non-final office action dated Jan. 20, 2016. |
James R. Milne, Gregory Peter Carlsson, Frederick J. Zustak, “Applying Mesh Network to Luggage”, related pending U.S. Appl. No. 14/332,919, filed Jul. 16, 2014. |
James R. Milne, Gregory Peter Carlsson, Frederick J. Zustak, “Applying Mesh Network to Pet Carrier”, related pending U.S. Appl. No. 14/333,006, filed Jul. 16, 2014. |
James R. Milne, Gregory Peter Carlsson, Frederick J. Zustak, “Applying Mesh Network to Stadium Services”, related pending U.S. Appl. No. 14/332,849, filed Jul. 16, 2014. |
James R. Milne, Gregory Peter Carlsson, Frederick J. Zustak, “Vehicle AD Hoc Network (VANET)”, related pending U.S. Appl. No. 14/332,900, filed Jul. 16, 2014. |
Gregory Peter Carlsson, Frederick J. Zustak, James R. Milne,“Mesh Network Applied to Arena Events”, related pending U.S. Appl. No. 14/332,953, filed Jul. 16, 2014. |
James R. Milne, Gregory Peter Carlsson, Frederick J. Zustak, “Applying Mesh Network to Luggage”, related U.S. Appl. No. 14/332,919, Applicant's response to Non-Final Office Action filed Feb. 11, 2016. |
James R. Milne, Gregory Peter Carlsson, Frederick J. Zustak, “Vehicle Ad Hoc Network (VANET)”, related pending U.S. Appl. No. 15/149,562, filed May 9, 2016. |
James R. Milne, Gregory Peter Carlsson, Frederick J. Zustak, “Applying Mesh Network to Luggage”, related U.S. Appl. No. 14/332,919, Final Office Action dated Jun. 3, 2016. |
James R. Milne, Gregory Peter Carlsson, Frederick J. Zustak, “Applying Mesh Network to Pet Carriers”, related U.S. Appl. No. 14/333,006. Non-Final Office Action dated Aug. 27, 2015. |
James R. Milne, Gregory Peter Carlsson, Frederick J. Zustak, “Applying Mesh Network to Pet Carriers”, related U.S. Appl. No. 14/333,006, Applicant's response to Non-Final Office Action filed Aug. 31, 2015. |
James R. Milne, Gregory Peter Carlsson, Frederick J. Zustak, “Applying Mesh Network to Pet Carriers”, related U.S. Appl. No. 14/333,006, Examiner's Answer dated Oct. 19, 2016. |
James R. Milne, Gregory Peter Carlsson, Frederick J. Zustak, “Applying Mesh Network to Pet Carriers”, related U.S. Appl. No. 14/333,006, Reply Brief filed Oct. 21, 2016. |
James R. Milne, Gergory Peter Carlsson, Frederick J. Zustak, “Applying Mesh Network to Pet Carriers”, related pending U.S. Appl. No. 14/333,006, Decision on Appeal reversed dated Dec. 6, 2017. |
James R. Milne, Charles McCoy, True Xiong, “Scalable Antenna System”, related U.S. Appl. No. 14/290,426, Non-Final Office Action dated Jul. 19, 2017. |
James R. Milne, Gregory Peter Carlson, Frederick J. Zustak, “Applying Mesh Network to Stadium Services”, related U.S. Appl. No. 14/332,849, Final Office Action dated Aug. 11, 2017. |
James R. Milne, Gregory Peter Carlson, Frederick J. Zustak, “Applying Mesh Network to Stadium Services”, related U.S. Appl. No. 14/332,849, Applicant's response to Final Office Action filed Aug. 17, 2017. |
James R. Milne, Gregory Peter Carlsson, Frederick J. Zustak, “Applying Mesh Network to Stadium Services”, related pending U.S. Appl. No. 14/332,849, applicant's response to final office action fled Jul. 17, 2017. |
James R. Milne, Charles McCoy, True Xiong, “Scalable Antenna System”, related U.S. Appl. No. 14/290,426, Non-Final Office Action dated Jun. 26, 2018. |
Charles McCoy, James R. Milne, Tru Xiong, “Method and System for Use in Configuring Multiple Near Field Antenna Systems”, related pending U.S. Appl. No. 14/460,224, non-final office action dated Apr. 19, 2017. |
James R. Milne, Gregory Peter Carlsson, Frederick J. Zustak, “Applying Mesh Network to Stadium Services”, related U.S. Appl. No. 14/332,849, Non-Final Office Action dated Jun. 19, 2017. |
“New app looks to give smartphone owners the ability to text without service or Internet”, Published Apr. 3, 2014, Associated Press. |
Number | Date | Country | |
---|---|---|---|
20160019515 A1 | Jan 2016 | US |