This application relates to systems and methods for stocking an automobile.
The present disclosure provides systems and methods for stocking an automobile. Stocking the automobile can include reading the location of the automobile in an electronic memory, comparing, via one or more processors, the location of the automobile with the location of the dealership to determine whether the automobile has arrived at the dealership, and notifying, via a network interface, the stocking system that the automobile has arrived at the dealership. Stocking the automobile can also include receiving a notification, via the network interface, from the dealership that the automobile is checked in.
In another example, stocking the automobile can include receiving, via a network interface, a location of the automobile, wherein the automobile provides the location, determining whether the automobile is within a perimeter based on the location of the automobile, and notifying, via a network interface, a dealership that the automobile is within the perimeter. Stocking the automobile can also include receiving a notification, via the network interface, from the dealership that the automobile is checked-in.
In yet another example, stocking the automobile can include receiving, via one or more access points of a wireless local area network (WLAN) operating on the premises of the dealership, a request to connect an automobile to the WLAN, identifying the automobile based on the request to connect the automobile to the WLAN, and determining whether the identified automobile is in stock at the dealership. Stocking the automobile can also include stocking-in the automobile based on a determination that the automobile is not in stock at the dealership.
In the following detailed description, reference is made to the accompanying drawings, which form a part hereof. In the drawings, similar symbols typically identify similar components, unless context dictates otherwise. The illustrative embodiments described in the detailed description, drawings, and claims are not meant to be limiting. Other embodiments may be utilized, and other changes may be made, without departing from the spirit or scope of the subject matter presented here.
Stocking an automobile can include receiving the automobile and adding the automobile to an inventory. Stocking an automobile can also include adding the automobile to a list of inventory (e.g., inventory list).
In a number of previous approaches, stocking an automobile can include providing a human user access to the automobile to verify that the automobile is in the premise of a dealership. Providing the user access to the automobile can incur the cost and the time of the user going to each automobile to verify that the automobile is on the premises.
Stocking an automobile can also include the user physically adding the automobile to an inventory by driving the received automobile to an inventory location where the inventory of automobiles is stored. Driving the automobile to an inventory location can also incur costs and time associated with paying a user to transfer the car from a receipt location to a storage location.
Stocking an automobile can also include the user physically adding the automobile to the inventory list. Physically adding the automobile to an inventory list can include a user writing and/or electronically including the automobile in a ledger and/or database. Physically adding the automobile to the inventory includes the cost of paying a user to perform the labor and the time used in physically adding the automobile to the inventory list. Additional costs can include the cost of transitioning between each of the above previous approaches to stocking an automobile.
As used herein, a dealership can include a legal entity and/or a physical structure. A physical structure can include a storage location, a place of business, office space, and/or a perimeter. A legal entity can be a new car dealership, a used car dealership, and/or any entity created to store automobiles for any interval of time. For example, a dealership can include a car rental entity and/or a bicycle rental entity. A dealership can include a central location and/or offsite locations. For example, a dealership can include a location of a business and/or a plurality of satellite locations of a business.
An automobile can include any vehicle used for transportation. For example, an automobile can be a car, a bus, a truck, and/or a motorcycle. The use of the term automobile is also intended to include bicycles, boats, and/or airplanes, among other types of transportation.
Embodiments may include various steps, which may be embodied in machine-executable instructions to be executed by a computer system. A computer system includes one or more general-purpose or special-purpose computers (or other electronic devices). The computer system may include hardware components that include specific logic for performing the steps or may include a combination of hardware, software, and/or firmware.
Embodiments may also be provided as a computer program product including a computer-readable medium having stored thereon instructions that may be used to program a computer system or other electronic device to perform the processes described herein. The computer-readable medium may include, but is not limited to: hard drives, floppy diskettes, optical disks, CD-ROMs, DVD-ROMs, ROMs, RAMs, EPROMs, EEPROMs, magnetic or optical cards, solid-state memory devices, or other types of media/computer-readable media suitable for storing electronic instructions.
Computer systems and the computers in a computer system may be connected via a network. Suitable networks for configuration and/or use as described herein include one or more local area networks, wide area networks, metropolitan area networks, and/or “Internet” or IP networks, such as the World Wide Web, a private Internet, a secure Internet, a value-added network, a virtual private network, an extranet, an intranet, or even standalone machines which communicate with other machines by physical transport of media (a so-called “sneakernet”). In particular, a suitable network may be formed from parts or entireties of two or more other networks, including networks using disparate hardware and network communication technologies. The network may include a wireless network.
One suitable network includes a server and several clients; other suitable networks may contain other combinations of servers, clients, and/or peer-to-peer nodes, and a given computer system may function both as a client and as a server. Each network includes at least two computers or computer systems, such as the server and/or clients. A computer system may include a workstation, laptop computer, disconnectable mobile computer, server, mainframe, cluster, so-called “network computer” or “thin client,” tablet, smart phone, personal digital assistant or other hand-held computing device, “smart” consumer electronics device or appliance, medical device, or a combination thereof.
The network may include communications or networking software, such as the software available from Novell, Microsoft, Artisoft, and other vendors, and may operate using TCP/IP, SPX, IPX, or other protocols over twisted pair, coaxial, or optical fiber cables, telephone lines, radio waves, satellites, microwave relays, modulated AC power lines, physical media transfer, and/or other data transmission “wires” and/or wireless protocols known to those of skill in the art. The network may encompass smaller networks and/or be connectable to other networks through a gateway or similar mechanism.
Each computer system includes at least a processor and a memory; computer systems may also include various input devices and/or output devices. The processor may include a general-purpose device, such as an Intel®, AMD®, or other “off-the-shelf” microprocessor. The processor may include a special-purpose processing device, such as an ASIC, a SoC, a SiP, an FPGA, a PAL, a PLA, an FPLA, a PLD, or other customized or programmable device. The memory may include static RAM, dynamic RAM, flash memory, one or more flip-flops, ROM, CD-ROM, disk, tape, magnetic, optical, or other computer storage medium. The input device(s) may include a keyboard, mouse, touch screen, light pen, tablet, microphone, sensor, or other hardware with accompanying firmware and/or software. The output device(s) may include a monitor or other display, printer, speech or text synthesizer, switch, signal line, or other hardware with accompanying firmware and/or software.
The computer systems may be capable of using a floppy drive, a tape drive, an optical drive, a magneto-optical drive, or other means to read a storage medium. A suitable storage medium includes a magnetic, optical, or other computer-readable storage device having a specific physical configuration. Suitable storage devices include floppy disks, hard disks, tape, CD-ROMs, DVDs, PROMs, random access memory, flash memory, and other computer system storage devices. The physical configuration represents data and instructions which cause the computer system to operate in a specific and predefined manner as described herein.
Suitable software to assist in implementing the invention is readily provided by those of skill in the pertinent art(s) using the teachings presented here and programming languages and tools, such as Java, Pascal, C++, C, database languages, APIs, SDKs, assembly, firmware, microcode, and/or other languages and tools. Suitable signal formats may be embodied in analog or digital form, with or without error detection and/or correction bits, packet headers, network addresses in a specific format, and/or other supporting data readily provided by those of skill in the pertinent art(s).
Several aspects of the embodiments described will be illustrated as software modules or components. As used herein, a software module or component may include any type of computer instruction or computer executable code located within a memory device. A software module may, for instance, include one or more physical or logical blocks of computer instructions, which may be organized as a routine, program, object, component, data structure, etc., that perform one or more tasks or implement particular abstract data types.
In certain embodiments, a particular software module may include disparate instructions stored in different locations of a memory device, different memory devices, or different computers, which together implement the described functionality of the module. Indeed, a module may include a single instruction or many instructions, and may be distributed over several different code segments, among different programs, and across several memory devices. Some embodiments may be practiced in a distributed computing environment where tasks are performed by a remote processing device linked through a communications network. In a distributed computing environment, software modules may be located in local and/or remote memory storage devices. In addition, data being tied or rendered together in a database record may be resident in the same memory device, or across several memory devices, and may be linked together in fields of a record in a database across a network.
Much of the infrastructure that can be used according to the present invention is already available, such as: general-purpose computers, computer programming tools and techniques, computer networks and networking technologies, digital storage media, authentication, access control, and other security tools and techniques provided by public keys, encryption, firewalls, and/or other means.
Although
The networks 104 and 108 can be a same network or different networks. For example, the scheduling system can employ an intranet as the network 104 or 108 to communicate with the dealerships 110 and/or an internet as the network 104 or 108 to communicate with the dealerships 110.
The dealerships 110 can receive automobiles including automobile 102. The dealerships 110 can be independently owned dealerships and/or dealerships that are part of a chain of dealerships, among other types of dealerships.
Each of the dealerships 110 can request, purchase, and/or acquire automobiles such as automobile 102. The dealerships 110 can schedule the receipt of an automobile. The dealerships 110 may automatically stock the automobile 102 once the automobile is delivered to the dealerships 110. Automatically stocking the automobile 102 can include adding the automobile 102 to an inventory after delivery without requiring that a user physically update the inventory list.
The stocking system 106 can include a plurality of computing devices configured to add the automobile 102 to an inventory list of at least one of the dealerships 110. For example, the stocking system 106 can include a computing device for receiving an indication that the automobile 102 is at the dealership. The stocking system 106 can also update an inventory list of at least one of the dealerships 110.
Each of the computing devices of a stocking system 106 can include one or more processors, electronic memory, and/or a network interface, among other components used by the computing device. The electronic memory is accessible by the one or more processors. The electronic memory can store the inventory lists of each of the dealerships 110, a plurality of attributes of the dealerships 110, and/or a plurality of attributes of automobiles such as automobile 102. A network interface may be enabled to provide communication with the automobile 102. At least one of the computing device may include a stocking application stored in the electronic memory and configured by the one or more processors, to stock an automobile 102.
In one example, the automobile 102 can be delivered to one of the dealerships 110. The automobile 102 can be delivered to one of the dealerships 110 based on a purchase agreement between the one of the dealerships 110 and a manufacturer of the automobile 102 and/or based upon a different agreement. For example, the automobile 102 can be returned by a client to one of the dealerships 110. In a number of examples, one of the dealerships 110 can expect delivery of the automobile 102.
The automobile 102 can communicate with the stocking system 106 via a network 104. The automobile 102 can communicate with the stocking system 106 to inform the stocking system 106 that the automobile 102 has arrived at one of the dealerships 110.
The automobile 102 can provide data to the stocking system 106 to verify that the automobile 102 is at one of the dealerships 110. For example, the automobile 102 can provide a global positioning system (GPS) coordinate that is within a predetermined distance from one of the dealerships 110. The automobile 102 can interact with one of the dealerships 110 in such a way that it can convey to the stocking system 106 that the automobile 102 is at one of the dealerships 110. For example, the automobile 102 can communicate with the stocking system 106 via the network 104 which includes a WLAN of a corresponding dealership.
In a number of embodiments, the dealerships 110 can determine that the automobile 102 is at their location and the dealerships 110 can inform the stocking system 106 that the automobile 102 has arrived.
The stocking system 106 can determine whether the automobile 102 is scheduled to arrive at a particular dealership from the dealerships 110. For example, the automobile 102 is scheduled to be delivered to the dealership 110-1. As such, the dealership 110-1 expects the automobile 102 to be delivered to its location. However, the automobile 102 may be delivered to the dealership 110-N. The stocking system 106 can determine whether the automobile 102 is delivered at a scheduled location or whether the automobile 102 is delivered at an incorrect dealership (e.g., location).
The stocking system 106 can maintain a record of the delivery schedules for each of the dealerships 110. For example, the stocking system 106 can query at least one of the dealerships 110 and/or receive from at least one of the dealerships 110 a delivery schedule at predefined intervals of time.
In some embodiments, the stocking system 106 can also access the delivery schedules stored at the dealerships 110. For example, the stocking system 106 may access the delivery schedules stored at the dealerships 110 to cross reference the delivery schedules stored at the stocking system 106. The stocking system 106 can access the delivery schedules stored at the dealerships 110 in response to receiving an indication from the automobile 102 and/or the dealerships 110 that the automobile 102 is at a particular dealership.
The stocking system 106 can determine whether the automobile 102 is at a dealership which was expecting the delivery of the automobile 102. The stocking system 106 can determine whether the automobile 102 is in fact at one of the dealerships 110.
Based on a determination that the automobile 102 is not at one of the dealerships 110 and/or that the automobile 102 is not at a dealership that is scheduled to receive the automobile 102, the stocking system 106 can inform a dealership that was scheduled to receive the automobile 102 of the automobile's location and/or of possible delays. The stocking system 106 can also reschedule the delivery of the automobile 102 from its current location to the correct dealership. The stocking system 106 can update a delivery schedule stored at the stocking system 106 and/or at the correct dealership (e.g., one of the dealerships 110).
Based on a determination that the automobile 102 is at a dealership that is scheduled to receive the automobile 102, the stocking system 106 can inform the dealership of the arrival of the automobile 102 at the dealership. The stocking system 106 can update a delivery schedule. Updating the delivery schedule can include removing the scheduled delivery of the automobile 102 from the delivery schedule. The stocking system can also add the automobile 102 to the inventory list.
In a number of embodiments, the dealerships 110 can receive a notice from the stocking system 106 that the automobile 102 has arrived at the dealerships 110. The dealerships 110 may desire to process the automobile 102. As such, the dealerships 110 may inform the stocking system 106 of the acceptance of the automobile 102. The stocking system 106 may add the automobile to the inventory list
As previously discussed, the automobile 202 can inform the stocking system of the automobile's 202 arrival at the dealership 210. The arrival of the automobile 202 at the dealership 210 can be determined based on the location of the automobile 202 and/or the dealership premises 212.
In a number of examples, the dealership premises 212 can be defined by the dealership 210 and provided to the stocking system. The dealership premises 212 can be defined based on a plurality of points, such as a plurality of GPS points. The dealership premises 212 can be defined based on a single point such as a single GPS point. For example, the dealership premises 212 can be defined as a circumference around a GPS point which defines the location of the dealership 210.
The plurality of points that define the dealership premises 212 can include a physical construct of the dealership 210. For example, the dealership premises 212 can be defined based on the boundaries surrounding the dealership 210. The boundary can be a physical boundary and/or a non-physical boundary. For example, the boundary can be a fence, a land feature, and/or lot dimensions.
In
Upon receiving the automobile's 202 location, the stocking system can compare the automobile's 202 location to the location of the dealership premises 212 which includes a plurality of GPS coordinates to define a boundary of the dealership 210. The stocking system can then determine whether the automobile 202 is within the dealership premises 212 and continue to stock the automobile 202 at the dealership 210.
The automobile 302 can be delivered at the dealership 310 within the dealership premises 312. The automobile 302 can connect to at least one of the access points 314 to communicate with the stocking system.
The automobile 302 can communicate with the stocking system periodically during the delivery, allowing the stocking system to determine the progress of the delivery of the automobile 302. The automobile 302 can communicate with the stocking system using a cellular connection, a WiFi connection, and/or a different type of connection.
In
The stocking system can receive the communications from the automobile 302 and determine that the communications were provided via the access points 314 and/or the WLAN of the dealership 310. As such, the stocking system can determine that the automobile 302 is at the dealership 310.
The network interface 424 can include hardware and/or computer readable instructions to communicate with the stocking system. The network interface 424 can also be used to communicate with a dealership, a dealership premises, and/or other components of the dealership such as an access point of the dealership WLAN.
The network interface 424 can include an antenna for wireless communications. The network interface 424 can receive data and send data via a network (e.g., networks 104, 108 in
The communications can be initiated by the communication device 426. The communication device 426 includes hardware and/or computer readable instructions to provide a location of the automobile 402 to the stocking system. The communication device 426 is further described in
The sensors 432 can include a plurality of sensors that provide data on the automobile's 402 location. The sensors 432 can monitor the actions taken by the automobile 402. For example, the sensors 432 can monitor the automobile's 402 speed and/or the revolutions per minute (RPM) of the automobile 402, among other actions taken by the automobile 402. The sensors 432 can include GPS sensors and/or a RFID sensors. The sensors 432 can also provide data other than a GPS coordinate and/or an RFID coordinate that can be used to determine a location of the automobile 402.
The one or more processors 542 can be independent of any other processors that are a part of the automobile (e.g., automobile 402 in
The automobile location 548 can be created by the sensors and stored in the electronic memory 544. The automobile stocking application 546 can be executed by the processors 542 to report a location of the automobile to the stocking system.
The automobile stocking application 546 can be configured to read the location of the automobile stored in the electronic memory. The automobile stocking application 546 can also be configured to provide, via the network interface 550, the automobile location 548.
In a number of examples, the automobile location 548 can be reported without a dealership's intervention. That is, the location of the automobile can be reported by the automobile, particularly by automobile stocking application 546 in the communication device 540. The dealership may be informed of the automobile's location after the automobile stocking application 546 has reported the automobile's location to the stocking system.
In some embodiments, the communication device 540 can be integrated into the automobile. That is, the communication device 540 can be permanently coupled to the automobile. For example, the communication device 540 may be an original equipment manufacturer (OEM) part of the automobile.
The communication device 540 can also be a mobile communication device that can be coupled to the automobile via a WiFi connection. That is, the communication device 540 can communicate with the automobile via the WiFi connection, among other types of connections. In some embodiments, the communication device 540 can be coupled to the automobile via an on-board diagnostics (OBD) port. As such, a user of the automobile may be able to plug the communication device 540 into the automobile and unplug the communication device 540 from the automobile.
The stocking application 651 can receive, via the network interface 653, the location of an automobile 649. The stocking application 651 can store the automobile's location 649 in the electronic memory 645. The stocking application 651 can interpret, via a computing device, whether the automobile has arrived at a dealership.
The stocking application 651 can update, via the computing device, the plurality of attributes of the dealerships which are stored in the dealership database 647. The dealership database 647 can store a location of the dealership, a plurality of GPS coordinates and/or RFID coordinates of the dealership, a delivery schedule of the dealership, an inventory list of the dealership, and/or identifying features of the WLAN of the dealership, among other data associated with the dealership.
The stocking application 651 can determine whether the automobile has arrived at the dealership by comparing the location of the automobile 649 to the location of the dealership stored in the dealership database 647. The stocking application 651 can inform the dealership of the arrival of the automobile at the dealership.
The method 760 also includes notifying 766, via the network interface, the stocking system that the automobile has arrived at the dealership. The dealership can check-in the automobile. Checking-in the automobile can include the dealership verifying that the automobile has arrived at the dealership and that the automobile is in a satisfactory condition. The vehicle can be in a satisfactory condition if the automobile meets a standard outlined in a purchase agreement of the automobile.
The method 760 also includes receiving 768 a notification, via the network interface, from the dealership that the automobile is checked-in. The method 760 can also include stocking the automobile at the dealership by adding the automobile to the inventory list.
In a number of embodiments the notice that the automobile has arrived at the dealership is automatic. That is, the notice can be provided to the dealership without a user's interaction. That is, the automatic notice is provided to the stocking system without a user's input. The user can include users of the stocking system and/or users of the dealership. For example, the automatic notice can be provided to the dealership without a representative of the dealership prompting and/or requesting the automobile's location and/or whether the automobile has arrived at the dealership.
In some embodiments, the communication device communicates with the automobile via a WiFi connection. The communication device can communicate with the automobile to retrieve a location of the automobile. In other embodiments, the communication device is integrated into the automobile. For example, the communication device can be an OEM part. The communication device can also be coupled to the automobile via an OBD port.
A network interface of the automobile and/or the communication device can connect the automobile and/or the communication device to the Internet via a cellular connection. The network interface can be used to communicate with the stocking system.
The stocking system can list the automobile as being in stock in response to receiving the notification. That is, the stocking system and/or the dealership can list the automobile as being in stock in response to the automobile being accepted by the dealership.
In a number of examples, the perimeter can be a geo-fence and/or a different type of fence that can interact with the dealership, the automobile, and/or the stocking system. The geo-fence can define a plurality of boundaries. The plurality of boundaries can surround a dealership. The plurality of boundaries can also and/or instead surround an intake location of the dealership.
The method 980 can also include receiving, via the one or more access points, automobile data for the automobile. The automobile data can include an identification of the automobile, a location from which the automobile is being transported, and/or a location to which the automobile is being transported. The automobile data can include a make and model of the automobile. The automobile data can include a vehicle identification number (VIN) number of the automobile, among other possible types of data that can describe the automobile such as a location of the automobile. In some embodiments the automobile can be identified based on the automobile data.
The automobile can include a communication device for communicating with the one or more access points of the WLAN. In a number of embodiments, the automobile can be stocked-in based on a notification that the automobile has arrived at the dealership.
While various aspects and embodiments have been disclosed herein, other aspects and embodiments will be apparent to those skilled in the art. The various aspects and embodiments disclosed herein are for purposes of illustration and are not intended to be limiting, with the true scope and spirit being indicated by the following claims.
Number | Name | Date | Kind |
---|---|---|---|
4992940 | Dworkin | Feb 1991 | A |
5421015 | Khoyi et al. | May 1995 | A |
5521815 | Rose, Jr. | May 1996 | A |
5649186 | Ferguson | Jul 1997 | A |
5694595 | Jacobs et al. | Dec 1997 | A |
5787177 | Leppek | Jul 1998 | A |
5790785 | Klug et al. | Aug 1998 | A |
5835712 | Dufresne | Nov 1998 | A |
5845299 | Arora et al. | Dec 1998 | A |
5862346 | Kley et al. | Jan 1999 | A |
5911145 | Arora et al. | Jun 1999 | A |
5956720 | Fernandez et al. | Sep 1999 | A |
5974149 | Leppek | Oct 1999 | A |
5974418 | Blinn et al. | Oct 1999 | A |
5974428 | Gerard et al. | Oct 1999 | A |
5978776 | Seretti et al. | Nov 1999 | A |
5987506 | Carter et al. | Nov 1999 | A |
6003635 | Bantz et al. | Dec 1999 | A |
6006201 | Berent et al. | Dec 1999 | A |
6009410 | Lemole et al. | Dec 1999 | A |
6018748 | Smith | Jan 2000 | A |
6021416 | Dauerer et al. | Feb 2000 | A |
6021426 | Douglis et al. | Feb 2000 | A |
6026433 | D'Arlach et al. | Feb 2000 | A |
6041310 | Green et al. | Mar 2000 | A |
6041344 | Bodamer et al. | Mar 2000 | A |
6055541 | Solecki et al. | Apr 2000 | A |
6061698 | Chadha et al. | May 2000 | A |
6067559 | Allard et al. | May 2000 | A |
6070164 | Vagnozzi | May 2000 | A |
6134532 | Lazarus et al. | Oct 2000 | A |
6151609 | Truong | Nov 2000 | A |
6178432 | Cook et al. | Jan 2001 | B1 |
6185614 | Cuomo et al. | Feb 2001 | B1 |
6189104 | Leppek | Feb 2001 | B1 |
6219667 | Lu et al. | Apr 2001 | B1 |
6236994 | Schwartz et al. | May 2001 | B1 |
6289382 | Bowman-Amuah | Sep 2001 | B1 |
6295061 | Park et al. | Sep 2001 | B1 |
6343302 | Graham | Jan 2002 | B1 |
6353824 | Boguraev et al. | Mar 2002 | B1 |
6374241 | Lamburt et al. | Apr 2002 | B1 |
6397226 | Sage | May 2002 | B1 |
6397336 | Leppek | May 2002 | B2 |
6401103 | Ho et al. | Jun 2002 | B1 |
6421733 | Tso et al. | Jul 2002 | B1 |
6473849 | Keller et al. | Oct 2002 | B1 |
6496855 | Hunt et al. | Dec 2002 | B1 |
6505205 | Kothuri et al. | Jan 2003 | B1 |
6519617 | Wanderski et al. | Feb 2003 | B1 |
6535879 | Behera | Mar 2003 | B1 |
6539370 | Chang et al. | Mar 2003 | B1 |
6546216 | Mizoguchi et al. | Apr 2003 | B2 |
6553373 | Boguraev et al. | Apr 2003 | B2 |
6556904 | Larson et al. | Apr 2003 | B1 |
6564216 | Waters | May 2003 | B2 |
6571253 | Thompson et al. | May 2003 | B1 |
6581061 | Graham | Jun 2003 | B2 |
6583794 | Wattenberg | Jun 2003 | B1 |
6594664 | Estrada et al. | Jul 2003 | B1 |
6606525 | Muthuswamy et al. | Aug 2003 | B1 |
6629148 | Ahmed et al. | Sep 2003 | B1 |
6643663 | Dabney et al. | Nov 2003 | B1 |
6654726 | Hanzek | Nov 2003 | B1 |
6678706 | Fishel | Jan 2004 | B1 |
6697825 | Underwood et al. | Feb 2004 | B1 |
6721747 | Lipkin | Apr 2004 | B2 |
6728685 | Ahluwalia | Apr 2004 | B1 |
6738750 | Stone et al. | May 2004 | B2 |
6785864 | Te et al. | Aug 2004 | B1 |
6795819 | Wheeler et al. | Sep 2004 | B2 |
6823359 | Heidingsfeld | Nov 2004 | B1 |
6826594 | Pettersen | Nov 2004 | B1 |
6847988 | Toyouchi et al. | Jan 2005 | B2 |
6871216 | Miller et al. | Mar 2005 | B2 |
6901430 | Smith | May 2005 | B1 |
6917941 | Wight et al. | Jul 2005 | B2 |
6922674 | Nelson | Jul 2005 | B1 |
6944677 | Zhao | Sep 2005 | B1 |
6963854 | Boyd et al. | Nov 2005 | B1 |
6965968 | Touboul | Nov 2005 | B1 |
6978273 | Bonneau et al. | Dec 2005 | B1 |
6981028 | Rawat et al. | Dec 2005 | B1 |
6990629 | Heaney et al. | Jan 2006 | B1 |
7000184 | Matveyenko et al. | Feb 2006 | B2 |
7028072 | Kliger et al. | Apr 2006 | B1 |
7031554 | Iwane | Apr 2006 | B2 |
7039704 | Davis et al. | May 2006 | B2 |
7047318 | Svedloff | May 2006 | B1 |
7062506 | Taylor et al. | Jun 2006 | B2 |
7072943 | Landesmann | Jul 2006 | B2 |
7107268 | Zawadzki et al. | Sep 2006 | B1 |
7124116 | Huyler | Oct 2006 | B2 |
7152207 | Underwood et al. | Dec 2006 | B1 |
7155491 | Schultz et al. | Dec 2006 | B1 |
7171418 | Blessin | Jan 2007 | B2 |
7197764 | Cichowlas | Mar 2007 | B2 |
7219234 | Ashland et al. | May 2007 | B1 |
7240125 | Fleming | Jul 2007 | B2 |
7246263 | Skingle | Jul 2007 | B2 |
7281029 | Rawat | Oct 2007 | B2 |
7322007 | Schowtka et al. | Jan 2008 | B2 |
7386786 | Davis et al. | Jun 2008 | B2 |
7401289 | Lachhwani et al. | Jul 2008 | B2 |
7433891 | Haber et al. | Oct 2008 | B2 |
7496543 | Bamford et al. | Feb 2009 | B1 |
7536641 | Rosenstein et al. | May 2009 | B2 |
7548985 | Guigui | Jun 2009 | B2 |
7587504 | Adams et al. | Sep 2009 | B2 |
7593925 | Cadiz et al. | Sep 2009 | B2 |
7624342 | Matveyenko et al. | Nov 2009 | B2 |
7657594 | Banga et al. | Feb 2010 | B2 |
7747680 | Ravikumar et al. | Jun 2010 | B2 |
7778841 | Bayer et al. | Aug 2010 | B1 |
7801945 | Geddes et al. | Sep 2010 | B1 |
7861309 | Spearman et al. | Dec 2010 | B2 |
7865409 | Monaghan | Jan 2011 | B1 |
7870253 | Muilenburg et al. | Jan 2011 | B2 |
7979506 | Cole | Jul 2011 | B2 |
8051159 | Muilenburg et al. | Nov 2011 | B2 |
8055544 | Ullman et al. | Nov 2011 | B2 |
8209259 | Graham, Jr. et al. | Jun 2012 | B2 |
8271473 | Berg | Sep 2012 | B2 |
8271547 | Taylor et al. | Sep 2012 | B2 |
8275717 | Ullman et al. | Sep 2012 | B2 |
8355950 | Colson et al. | Jan 2013 | B2 |
8438310 | Muilenburg et al. | May 2013 | B2 |
8538894 | Ullman et al. | Sep 2013 | B2 |
8645193 | Swinson et al. | Feb 2014 | B2 |
9754304 | Taira et al. | Sep 2017 | B2 |
9836714 | Lander | Dec 2017 | B2 |
20010037332 | Miller et al. | Nov 2001 | A1 |
20010039594 | Park et al. | Nov 2001 | A1 |
20010054049 | Maeda et al. | Dec 2001 | A1 |
20020023111 | Arora et al. | Feb 2002 | A1 |
20020026359 | Long et al. | Feb 2002 | A1 |
20020032626 | Dewolf et al. | Mar 2002 | A1 |
20020032701 | Gao et al. | Mar 2002 | A1 |
20020042738 | Srinivasan et al. | Apr 2002 | A1 |
20020046245 | Hillar et al. | Apr 2002 | A1 |
20020049831 | Platner et al. | Apr 2002 | A1 |
20020059260 | Jas | May 2002 | A1 |
20020065739 | Florance et al. | May 2002 | A1 |
20020069110 | Sonnenberg | Jun 2002 | A1 |
20020073080 | Lipkin | Jun 2002 | A1 |
20020082978 | Ghouri et al. | Jun 2002 | A1 |
20020091755 | Narin | Jul 2002 | A1 |
20020107739 | Schlee | Aug 2002 | A1 |
20020116418 | Lachhwani et al. | Aug 2002 | A1 |
20020123359 | Wei et al. | Sep 2002 | A1 |
20020124053 | Adams et al. | Sep 2002 | A1 |
20020129054 | Ferguson et al. | Sep 2002 | A1 |
20020138331 | Hosea et al. | Sep 2002 | A1 |
20020143646 | Boyden et al. | Oct 2002 | A1 |
20020154146 | Rodriquez et al. | Oct 2002 | A1 |
20020169851 | Weathersby et al. | Nov 2002 | A1 |
20020196273 | Krause | Dec 2002 | A1 |
20020198761 | Ryan et al. | Dec 2002 | A1 |
20020198878 | Baxter et al. | Dec 2002 | A1 |
20030014443 | Bernstein et al. | Jan 2003 | A1 |
20030023632 | Ries et al. | Jan 2003 | A1 |
20030033378 | Needham et al. | Feb 2003 | A1 |
20030036964 | Boyden et al. | Feb 2003 | A1 |
20030037263 | Kamat et al. | Feb 2003 | A1 |
20030046179 | Anabtawi et al. | Mar 2003 | A1 |
20030051022 | Sogabe et al. | Mar 2003 | A1 |
20030061263 | Riddle | Mar 2003 | A1 |
20030065532 | Takaoka | Apr 2003 | A1 |
20030069785 | Lohse | Apr 2003 | A1 |
20030069790 | Kane | Apr 2003 | A1 |
20030074392 | Campbell et al. | Apr 2003 | A1 |
20030115292 | Griffin et al. | Jun 2003 | A1 |
20030120502 | Robb et al. | Jun 2003 | A1 |
20030145310 | Thames et al. | Jul 2003 | A1 |
20030177050 | Crampton et al. | Sep 2003 | A1 |
20030177175 | Worley et al. | Sep 2003 | A1 |
20030225853 | Wang et al. | Dec 2003 | A1 |
20030229623 | Chang et al. | Dec 2003 | A1 |
20030233246 | Snapp et al. | Dec 2003 | A1 |
20040012631 | Skorski | Jan 2004 | A1 |
20040039646 | Hacker | Feb 2004 | A1 |
20040041818 | White et al. | Mar 2004 | A1 |
20040073546 | Forster et al. | Apr 2004 | A1 |
20040073564 | Haber et al. | Apr 2004 | A1 |
20040088228 | Mercer et al. | May 2004 | A1 |
20040128320 | Grove et al. | Jul 2004 | A1 |
20040139203 | Graham, Jr. et al. | Jul 2004 | A1 |
20040148342 | Cotte | Jul 2004 | A1 |
20040156020 | Edwards | Aug 2004 | A1 |
20040163047 | Nagahara et al. | Aug 2004 | A1 |
20040181464 | Vanker et al. | Sep 2004 | A1 |
20040220863 | Porter et al. | Nov 2004 | A1 |
20040225664 | Casement | Nov 2004 | A1 |
20040230897 | Latzel | Nov 2004 | A1 |
20040255233 | Croney et al. | Dec 2004 | A1 |
20040267263 | May | Dec 2004 | A1 |
20040268225 | Walsh et al. | Dec 2004 | A1 |
20040268232 | Tunning | Dec 2004 | A1 |
20050015491 | Koeppel | Jan 2005 | A1 |
20050065804 | Worsham et al. | Mar 2005 | A1 |
20050096963 | Myr et al. | May 2005 | A1 |
20050108112 | Ellenson et al. | May 2005 | A1 |
20050114270 | Hind et al. | May 2005 | A1 |
20050114764 | Gudenkauf et al. | May 2005 | A1 |
20050108637 | Sahota et al. | Jun 2005 | A1 |
20050171836 | Leacy | Aug 2005 | A1 |
20050228736 | Norman et al. | Oct 2005 | A1 |
20050267774 | Merritt et al. | Dec 2005 | A1 |
20050268282 | Laird | Dec 2005 | A1 |
20050289020 | Bruns et al. | Dec 2005 | A1 |
20050289599 | Matsuura et al. | Dec 2005 | A1 |
20060031811 | Ernst et al. | Feb 2006 | A1 |
20060059253 | Goodman et al. | Mar 2006 | A1 |
20060064637 | Rechterman et al. | Mar 2006 | A1 |
20060123330 | Horiuchi et al. | Jun 2006 | A1 |
20060129423 | Sheinson et al. | Jun 2006 | A1 |
20060129982 | Doyle | Jun 2006 | A1 |
20060161841 | Horiuchi et al. | Jul 2006 | A1 |
20060200751 | Underwood et al. | Sep 2006 | A1 |
20060248442 | Rosenstein et al. | Nov 2006 | A1 |
20060265355 | Taylor | Nov 2006 | A1 |
20060271844 | Suklikar | Nov 2006 | A1 |
20060277588 | Harrington et al. | Dec 2006 | A1 |
20070005446 | Fusz et al. | Jan 2007 | A1 |
20070016486 | Stone et al. | Jan 2007 | A1 |
20070033520 | Kimzey et al. | Feb 2007 | A1 |
20070053513 | Hoffberg | Mar 2007 | A1 |
20070150368 | Arora et al. | Jun 2007 | A1 |
20070209011 | Padmanabhuni et al. | Sep 2007 | A1 |
20070250327 | Hedy | Oct 2007 | A1 |
20070271154 | Broudy et al. | Nov 2007 | A1 |
20070271330 | Mattox et al. | Nov 2007 | A1 |
20070271389 | Joshi et al. | Nov 2007 | A1 |
20070282711 | Ullman et al. | Dec 2007 | A1 |
20070282712 | Ullman et al. | Dec 2007 | A1 |
20070282713 | Ullman et al. | Dec 2007 | A1 |
20070288413 | Mizuno et al. | Dec 2007 | A1 |
20070294192 | Tellefsen | Dec 2007 | A1 |
20080015929 | Koeppel et al. | Jan 2008 | A1 |
20080027827 | Eglen et al. | Jan 2008 | A1 |
20080172632 | Stambaugh | Jul 2008 | A1 |
20080195435 | Bentley et al. | Aug 2008 | A1 |
20080195932 | Oikawa et al. | Aug 2008 | A1 |
20080201163 | Barker et al. | Aug 2008 | A1 |
20090012887 | Taub et al. | Jan 2009 | A1 |
20090024918 | Silverbrook et al. | Jan 2009 | A1 |
20090043780 | Hentrich, Jr. et al. | Feb 2009 | A1 |
20090070435 | Abhyanker | Mar 2009 | A1 |
20090112687 | Blair | Apr 2009 | A1 |
20090182232 | Zhang et al. | Jul 2009 | A1 |
20090204454 | Lagudi | Aug 2009 | A1 |
20090222532 | Finlaw | Sep 2009 | A1 |
20090265607 | Raz et al. | Oct 2009 | A1 |
20090313035 | Esser et al. | Dec 2009 | A1 |
20100082778 | Muilenburg et al. | Apr 2010 | A1 |
20100082780 | Muilenburg et al. | Apr 2010 | A1 |
20100088158 | Pollack | Apr 2010 | A1 |
20100100506 | Marot | Apr 2010 | A1 |
20100312608 | Shan et al. | Dec 2010 | A1 |
20100318408 | Sankaran et al. | Dec 2010 | A1 |
20110022525 | Swinson et al. | Jan 2011 | A1 |
20110082804 | Swinson et al. | Apr 2011 | A1 |
20110145064 | Anderson et al. | Jun 2011 | A1 |
20110161167 | Jallapuram | Jun 2011 | A1 |
20110191264 | Inghelbrecht et al. | Aug 2011 | A1 |
20110196762 | Dupont | Aug 2011 | A1 |
20110307411 | Bolivar et al. | Dec 2011 | A1 |
20120209714 | Douglas et al. | Aug 2012 | A1 |
20120278886 | Luna | Nov 2012 | A1 |
20140026037 | Garb et al. | Jan 2014 | A1 |
20140094992 | Lambert | Apr 2014 | A1 |
20140278805 | Thompson | Sep 2014 | A1 |
20140337163 | Whisnant | Nov 2014 | A1 |
20150278886 | Fusz | Oct 2015 | A1 |
20160071054 | Kakarala et al. | Mar 2016 | A1 |
20160140622 | Wang et al. | May 2016 | A1 |
20170308864 | Kelley | Oct 2017 | A1 |
20170308865 | Kelley | Oct 2017 | A1 |
20180285901 | Zackrone | Oct 2018 | A1 |
20180285925 | Zackrone | Oct 2018 | A1 |
Entry |
---|
Java version history—Wikipedia, the free encyclopedia, printed Mar. 6, 2010, 9 pgs. |
Lee, Adam J. et al., “Searching for Open Windows and Unlocked Doors: Port Scanning in Large-Scale Commodity Custers,” Cluster Computing and the Grid, 2005. CCGrid 2005. IEEE International Symposium on vol. 1; Publication Year: 2005. |
Michener, J.R., et al., “Managing System and Active-Content Integrity,” Computer; vol. 33, Issue: 7; Publication Year 2000, pp. 108-110. |
Milic-Frayling, Natasa, et al., “SmartView: Enhanced Document Viewer for Mobile Devices,” Google Nov. 15, 2002, 11 pgs. |
Non-Final Office Action for U.S. Appl. No. 10/350,795, filed Jan. 24, 2003, and mailed from the USPTO dated Dec. 26, 2008, 13 pgs. |
Non-Final Office Action for U.S. Appl. No. 10/350,795, filed Jan. 24, 2003, and mailed from the USPTO dated Feb. 6, 2006, 11 pgs. |
Non-Final Office Action for U.S. Appl. No. 10/350,795, filed Jan. 24, 2003, and mailed from the USPTO dated Jul. 22, 2009, 22 pgs. |
Non-Final Office Action for U.S. Appl. No. 10/350,795, filed Jan. 24, 2003, and mailed from the USPTO dated Jun. 29, 2006, 11 pgs. |
Non-Final Office Action for U.S. Appl. No. 10/350,795, filed Jan. 24, 2003, and mailed from the USPTO dated Mar. 12, 2007, 10 pgs. |
Non-Final Office Action for U.S. Appl. No. 10/350,795, filed Jan. 24, 2003, and mailed from the USPTO dated May 29, 2008, 10 pgs. |
Non-Final Office Action for U.S. Appl. No. 10/350,795, filed Jan. 24, 2003, and mailed from the USPTO dated Nov. 1, 2010, 19 pgs. |
Non-Final Office Action for U.S. Appl. No. 10/350,796, filed Jan. 24, 2003 and mailed from the USPTO dated May 19, 2005, 7 pgs. |
Non-Final Office Action for U.S. Appl. No. 10/350,810, filed Jan. 24, 2003, and mailed from the USPTO dated Apr. 17, 2007, 12 pgs. |
Non-Final Office Action for U.S. Appl. No. 10/350,810, filed Jan. 24, 2003, and mailed from the USPTO dated Dec. 9, 2005, 14 pgs. |
Non-Final Office Action for U.S. Appl. No. 10/350,810, filed Jan. 24, 2003, and mailed from the USPTO dated Sep. 22, 2004, 10 pgs. |
Non-Final Office Action for U.S. Appl. No. 10/351,465, filed Jan. 24, 2003, and mailed from the USPTO dated Jul. 27, 2004, 9 pgs. |
Non-final Office Action for U.S. Appl. No. 10/351,606, filed Jan. 24, 2003 and mailed from the USPTO dated Dec. 19, 2005, 7 pgs. |
Non-final Office Action for U.S. Appl. No. 10/351,606, filed Jan. 24, 2003 and mailed from the USPTO dated May 17, 2004, 5 pgs. |
Non-Final Office Action for U.S. Appl. No. 10/665,899, filed Sep. 18, 2003, and mailed from the USPTO dated Aug. 30, 2010, 23 pgs. |
Non-Final Office Action for U.S. Appl. No. 10/665,899, filed Sep. 18, 2003, and mailed from the USPTO dated Nov. 13, 2008, 11 pgs. |
Non-Final Office Action for U.S. Appl. No. 10/665,899, filed Sep. 18, 2003, and mailed from the USPTO datedSep. 14, 2009, 14 pgs. |
Non-Final Office Action for U.S. Appl. No. 10/665,899, filed Sep. 18, 2003, and mailed from the USPTO dated Sep. 17, 2007, 11 pgs. |
Non-Final Office Action for U.S. Appl. No. 11/149,909, filed Jun. 10, 2005, and mailed from the USPTO dated May 13, 2008, 14 pgs. |
Non-Final Office Action for U.S. Appl. No. 11/149,909 filed Jun. 10, 2005, and mailed from the USPTO dated May 6, 2009, 6 pgs. |
Von-Final Office Action for U.S. Appl. No. 11/414,939, filed May 1, 2006, and mailed from the USPTO dated Jul. 19, 2010, 7 pgs. |
Non-Final Office Action for U.S. Appl. No. 11/414,939, filed May 1, 2006, and mailed from the USPTO dated Mar. 9, 2010, 11 pgs. |
Non-Final Office Action for U.S. Appl. No. 11/442,821, filed May 30, 2006, and mailed from the USPTO dated Jun. 1, 2011, 23 pgs. |
Non-Final Office Action for U.S. Appl. No. 11/442,821, filed May 30, 2006, and mailed from the USPTO dated Nov. 12, 2009, 19 pgs. |
Non-Final Office Action for U.S. Appl. No. 11/442,821, filed May 30, 2006, and mailed from the USPTO dated Sep. 3, 2008, 14 pgs. |
Non-Final Office Action for U.S. Appl. No. 11/446,011, filed Jun. 2, 2006, and mailed from the USPTO dated Mar. 1, 2011, 15 pgs. |
Non-Final Office Action for U.S. Appl. No. 11/446,011, filed Jun. 2, 2006, and mailed from the USPTO dated Nov. 27, 2009, 14 pgs. |
Non-Final Office Action for U.S. Appl. No. 11/524,602, filed Sep. 21, 2006, and mailed from the USPTO dated Dec. 11, 2009, 20 pgs. |
Non-Final Office Action for U.S. Appl. No. 11/524,602, filed Sep. 21, 2006, and mailed from the USPTO dated Nov. 4, 2011, 19 pgs. |
Non-Final Office Action for U.S. Appl. No. 11/525,009, filed Sep. 21, 2006, and mailed from the USPTO dated Aug. 10, 2011, 18 pgs. |
Non-Final Office Action for U.S. Appl. No. 11/525,009, filed Sep. 21, 2006, and mailed from the USPTO dated Dec. 16, 2009, 20 pgs. |
Non-Final Office Action for U.S. Appl. No. 12/243,852, filed Oct. 1, 2008, and mailed from the USPTO dated Jan. 16, 2013, 5 pgs. |
Non-Final Office Action for U.S. Appl. No. 12/243,852, filed Oct. 1, 2008, and mailed from the USPTO dated Mar. 17, 2011, 8 pgs. |
Non-Final Office Action for U.S. Appl. No. 12/243,855, filed Oct. 1, 2008, and mailed from the USPTO dated Oct. 14, 2010, 6 pgs. |
Non-Final Office Action for U.S. Appl. No. 12/243,861, filed Oct. 1, 2008, and mailed from the USPTO dated Nov. 8, 2010, 8 pgs. |
Non-Final Office Action for U.S. Appl. No. 13/025,019, filed Feb. 10, 2011, and mailed from the USPTO dated Apr. 22, 2016, 16 pgs. |
Non-Final Office Action for U.S. Appl. No. 13/025,019, filed Feb. 10, 2011, and mailed from the USPTO dated Apr. 5, 2013, 15 pgs. |
Mon-Final Office Action for U.S. Appl. No. 13/025,019, filed Feb. 10, 2011, and mailed from the USPTO dated Oct. 6, 2017, 17 pgs. |
Non-Final Office Action for U.S. Appl. No. 13/025,019, filed Feb. 10, 2011, and mailed from the USPTO dated Sep. 8, 2014, 15 pgs. |
Non-Final Office Action for U.S. Appl. No. 14/208,042, filed Mar. 13, 2014, and mailed from the USPTO dated Jun. 30, 2016, 23 pgs. |
Non-Final Office Action for U.S. Appl. No. 14/208,042, filed Mar. 13, 2014, and mailed from the USPTO dated Sep. 20, 2017. |
Non-Final Office Action for U.S. Appl. No. 15/602,999, filed May 23, 2017, and mailed from the USPTO dated May 3, 2018. |
Non-Final Office Action dated Oct. 6, 2017 in U.S. Appl. No. 13/025,019. |
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 10/350,795, filed Jan. 24, 2003, and mailed from the USPTO dated May 7, 2012, 15 pgs. |
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 10/350,796, filed Jan. 24, 2003 and mailed from the USPTO dated Feb. 1, 2006, 5 pgs. |
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 10/350,810, filed Jan. 24, 2003, and mailed from the USPTO dated Apr. 14, 2008, 6 pgs. |
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 10/351,465, filed Jan. 24, 2003, and mailed from the USPTO dated Sep. 21, 2005, 4 pgs. |
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 10/351,606, filed Jan. 24, 2003 and mailed from the USPTO dated Apr. 4, 2006, 8 pgs. |
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 11/149,909, filed Jun. 10, 2005, and mailed from the USPTO dated Sep. 16, 2009, 7 pgs. |
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 11/414,939, filed May 1, 2006, and mailed from the USPTO dated Nov. 2, 2010, pgs. |
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 11/442,821, filed May 30, 2006, and mailed from the USPTO dated Jul. 30, 2012, 6 pgs. |
Notice of Allowance arid Fee(s) Due for U.S. Appl. No. 11/446,011, filed Jun. 2, 2006, and mailed from the USPTO dated Aug. 9, 2011, 10 pgs. |
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 11/524,602, filed Sep. 21, 2006, and mailed from the USPTO dated Aug. 6, 2013, 22 pgs. |
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 11/525,009, filed Sep. 21, 2006, and mailed from the USPTO dated Jul. 23, 2012, 19 pgs. |
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 12/243,852, filed Oct. 1, 2008, and mailed from the USPTO dated Feb. 27, 2013, 6 pgs. |
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 12/243,855, filed Oct. 1, 2008, and mailed from the USPTO Nov. 22, 2010, 8 pgs. |
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 12/243,855, filed Oct. 1, 2008, and mailed from the USPTO Oct. 28, 2010, 5 pgs. |
Nlotice of Allowance and Fee(s) Due for U.S. Appl. No. 12/243,861, filed Oct. 1, 2008, and mailed from the USPTO Sep. 6, 2011, 10 pgs. |
Notice of Non-compliant Amendment dated Dec. 12, 2006 in U.S. Appl. No. 10/350,810. |
Permissions in the Java™ 2 SDK, printed Mar. 6, 2010, 45 pgs. |
Restriction Requirement for U.S. Appl. No. 12/243,852, filed Oct. 1, 2008, and mailed from the USPTO dated Dec. 7, 2010. |
Strebe, Matthew et al. MCSE: NT Server 4 Study Guide, Third Edition. 2000, SYBEX Inc. Front matter, pp. 284-293, and 308-347 are included. Entire book cited, 36 pgs. |
Supplemental Notice of Allowability for U.S. Appl. No. 12/243,852, filed Oct. 1, 2008, and mailed from the USPTO dated Mar. 19, 2013, 3 pgs. |
Trademark Electronic Search System record for Serial Number 7637505, Word Mark “NITRA”. |
Trademark Application, Serial number 76375405. 13 pages of advertising material and other application papers enclosed. Available from Trademark Document Retrieval system. |
“NetFormx Offers Advanced Network Discovery Software”. PR Newswire. Mar. 15, 1999. Retrieved from http://www.highbeam.com/doc/1G1-54102907.html>. |
Advisory Action for U.S. Appl. No. 14/208,042, filed Mar. 13, 2014, and mailed from the USPTO dated Jul. 12, 2018. |
Aloisio, Giovanni et al., “Web-based access to the Grid using the Grid Resource Broker portal,” Google 2002, pp. 1145-1160. |
Anonymous, “Software ready for prime time.” Automotive News. Detroit, Nov. 5, 2001. vol. 76, Issue 5996, p. 28. |
Chadwick, D. W., “Understanding X.500—The Directory.” Available at <http://sec.cs.kent.ac.uk/x500book/>. 1996. Entire work cited. |
Chen, Deren, “Business to Business Standard and Supply Chain System Framework in Virtual Enterprises,” Computer Supported Cooperative Work in Design, The Sixth International Conference on, 2001; Publication Year. 2001, pp. 472-476. |
CNY Business Journal, “Frank La Voila named Southern Tier Small-Business Person of 1999”. Jun. 11, 1999. 2 pgs. |
Davis, Peter T. et al., “Sams Teach Yourself Microsoft Windows NT Server 4 in 21 Days,” Sams® Publishing, ®1999. ISBN: 0-672-31555-6, 15 pgs., printed Dec. 21, 2008. |
Derfler, Frank J. et al., “How Networks Work: Millennium Edition,” Que, A Division of Macmillan Computer Publishing, ® 2000. ISBN: 0-7897-2445-6, 9 pgs. |
Final Office Action for U.S. Appl. No. 10/350,795, filed Jan. 24, 2003, and mailed from the USPTO dated Jul. 6, 2011, 26 pgs. |
Final Office Action for U.S. Appl. No. 10/350,795, filed Jan. 24, 2003, and mailed from the USPTO dated Mar. 3, 2010, 24 pgs. |
Final Office Action for U.S. Appl. No. 10/350,810, filed Jan. 24, 2003, and mailed from the USPTO dated Apr. 5, 2005, 12 pgs. |
Final Office Action for U.S. Appl. No. 10/350,810, filed Jan. 24, 2003, and mailed from the USPTO dated May 18, 2006, 15 pgs. |
Final Office Action for U.S. Appl. No. 10/350,810, filed Jan. 24, 2003, and mailed from the USPTO dated Nov. 14, 2007, 13 pgs. |
Final Office Action for U.S. Appl. No. 10/351,465, filed Jan. 24, 2003, and mailed from the USPTO dated May 5, 2005, 8 pgs. |
Final Office Action for U.S. Appl. No. 10/665,899, filed Sep. 18, 2003, and mailed from the USPTO dated Feb. 24, 2010, 22 pgs. |
Final Office Action for U.S. Appl. No. 10/665,899, filed Sep. 18, 2003, and mailed from the USPTO dated Jul. 7, 2008, 11 pgs. |
Final Office Action for U.S. Appl. No. 10/665,899, filed Sep. 18, 2003, and mailed from the USPTO dated Mar. 8, 2011, 21 pgs. |
Final Office Action for U.S. Appl. No. 10/665,899, filed Sep. 18, 2003, and mailed from the USPTO dated May 11, 2009, 14 pgs. |
Final Office Action for U.S. Appl. No. 11/149,909, filed Jun. 10, 2005, and mailed from the USPTO dated Feb. 4, 2009, 14 pgs. |
Final Office Action for U.S. Appl. No. 11/442,821, filed May 30, 2006, and mailed from the USPTO dated Apr. 7, 2009, 19 pgs. |
Final Office Action for U.S. Appl. No. 11/442,821, filed May 30, 2006, and mailed from the USPTO dated May 21, 2010, 28 pgs. |
Final Office Action for U.S. Appl. No. 11/442,821, filed May 30, 2006, and mailed from the USPTO dated Nov. 29, 2011, 26 pgs. |
Final Office Action for U.S. Appl. No. 11/446,011, filed Jun. 2, 2006, and mailed from the USPTO dated Jun. 8, 2010, 12 pgs. |
Final Office Action for U.S. Appl. No. 11/524,602, filed Sep. 21, 2006, and mailed from the USPTO dated Jul. 27, 2010, 13 pgs. |
Final Office Action for U.S. Appl. No. 11/524,602, filed Sep. 21, 2006, and mailed from the USPTO dated Jun. 26, 2012, 11 pgs. |
Final Office Action for U.S. Appl. No. 11/525,009, filed Sep. 21, 2006, and mailed from the USPTO dated Aug. 3, 2010,16 pgs. |
Final Office Action for U.S. Appl. No. 12/243,852, filed Oct. 1, 2008, and mailed from the USPTO dated Oct. 24, 2011, 13 pgs. |
Final Office Action for U.S. Appl. No. 12/243,861, filed Oct. 1, 2008, and mailed from the USPTO dated Jun. 22, 2011, 5 pgs. |
Final Office Action for U.S. Appl. No. 13/025,019, filed Feb. 10, 2011, and mailed from the USPTO dated Aug. 28, 2015, 25 pgs. |
Final Office Action for U.S. Appl. No. 13/025,019, filed Feb. 10, 2011, and mailed from the USPTO dated Jul. 13, 2018, 11 pgs. |
Internet Archive: Democracy Now, http://www.archive.org/audio/collection.php?collection=democracy_now, printed Mar. 12, 2004, 2 pgs. |
Final Office Action for U.S. Appl. No. 13/025,019, filed Feb. 10, 2011, and mailed from the USPTO dated Sep. 12, 2013, 13 pgs. |
Final Office Action for U.S. Appl. No. 13/025,019, filed Feb. 20, 2011, and mailed from the USPTO dated Dec. 20, 2016, 16 pgs. |
Final Office Action for U.S. Appl. No. 14/208,042, filed Mar. 13, 2014, and mailed from the USPTO dated Jan. 11, 2019 , 16 pgs. |
Final Office Action for U.S. Appl. No. 14/208,042, filed Mar. 13, 2014, and mailed from the USPTO dated Apr. 16, 2018. |
Final Office Action for U.S. Appl. No. 14/208,042, filed Mar. 13, 2014, and mailed from the USPTO dated Dec. 6, 2016, 26 pgs. |
Internet Archive Wayback Machine, archive of LDAP Browser.com—Product Info. Archived Dec. 11, 2000. Available at <http://web.archive.org/web/200012110541/http://www.ldapbrowser.com/prodinfo/prodinfo.php3?sID=fe4ae66f2fo23d86909f35e974f3a1ce>. |
Final Office Action for U.S. Appl. No. 15/602,999, filed May 23, 2017, and mailed from the USPTO dated Nov. 21, 2018. |
Hogue et al., “Thresher: Automating the Unwrapping of Semantic Content from the World Wide Web,” ACM 2005, pp. 86-95. |
Housel, Barron C. et al., “WebExpress: A client/intercept based system for optimizing Web browsing in a wireless environment,” Google 1998, pp. 419-431. |
http://web.archive.org/web/20010718130244/http://chromedata.com/maing2/about/index.asp, 1 pg. |
http://web.archive.org/web/20050305055408/http://www.dealerclick.com/, 1 pg. |
http://web.archive.org/web/20050528073821/http://www.kbb.com/, 1 pg. |
http://web.archive.org/web/20050531000823/http://www.carfax.com/, 1 pg. |
IBM Tivoli Access Manager Base Administration Guide, Version 5.1. 2003, International Business Machines Corporation. Entire book enclosed and cited. 402 pgs. |
Interconnection. (2003). In Roget's II the New Thesaurus. Boston, MA: Houghton Mifflin. Retrieved Jul. 16, 2009, from http://www.credoreference.com/entry/hmrogets/interconnection, 1 pg. |
Internet Archive: Audio Archive, http://www.archive.org/audio/audio-searchresults.php?search=@star=0&limit=100&sort=ad, printed May 12, 2004, 12 pgs. |
Internet Archive: Democracy Now, http://www.archive.org/audio/collection.php?collection=democracy_now, printed May 12, 2004, 2 pgs. |
Java 2 Platform, Enterprise Edition (J2EE) Overview, printed Mar. 6, 2010, 3 pgs. |
Number | Date | Country | |
---|---|---|---|
20170308844 A1 | Oct 2017 | US |