Classifications

• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
  • G06Q99/00—Subject matter not provided for in other groups of this subclass

Definitions

• the present invention relates to online communication between a user and a server system. More particularly, the present invention pertains to interactive online vehicle registration, for example, registration that may result in an order for a document or article (e.g., a license plate or validation sticker) to be manufactured and distributed.
• a document or article e.g., a license plate or validation sticker
• the Web An information system known as the World Wide Web (“the Web”) is part of the Internet and is a wide area hypermedia information system aimed to give wide access to a large universe of documents and carry out a variety of different types of transactions.
• the architecture of the Web follows a conventional client-server model.
• client and server are used to refer to a computer's general role as a requester of data (the client computer) or provider of data (the server computer).
• web browsers reside at a client computer site and other information, such as documents, reside at a server computer site.
• Web clients and servers communicate using a common protocol.
• HTTP Hypertext Transfer Protocol
• client computer e.g., client computer or server computer
• HTTP Hypertext Transfer Protocol
• server computer may request data in one transaction and provide data in another transaction, thus changing the computer's role from a client to server, or vice versa.
• client- server relationship can be used to provide interaction for carrying out various transactions.
• transactions include auction transactions, payment transactions, product ordering transactions, document search transactions, information forwarding transactions, etc.
• conventional vehicle registration has involved various parties to process the transaction.
• a registrant e.g., a truck driver
• DMV Department of Motor Vehicles
• the transaction by the DMV regional office is processed and information is provided to a larger state-run DMV organization along with a license plate order.
• the state-run DMV organization has a large computer system, including a mainframe computer and large memory capacity for storing information with regard to all state vehicle registrations. License plate, validation sticker or other vehicle registration device orders received from the local DMV offices are processed and orders associated with a large number of vehicles are placed with a suitable organization for production.
• such orders may be provided to a production management organization where the orders are again processed for production, e.g., printed in large quantities in the case of general issue plates, or in the case of special plates, printed in much smaller quantities.
• general issue license plates may all be printed in long production runs which print the same general design on retro- reflective sheeting that is ultimately applied to a suitable substrate.
• general issue license plates may be further stamped with license plate numbers at, for example, a correctional facility.
• the overall process of vehicle registration and processing of document or article orders tends to be a lengthy and inefficient process.
• the time between the placement of an order (e.g., at the time of registration) and receipt of the license plate, or validation sticker in case of some registration renewals may be quite long.
• plates are available for distribution, for example, general issue plates available at a local DMV office, managing such inventory at the local DMV may be difficult.
• the time for processing a replacement for such a distributed plate may still require processing of a plate order in a manner similar to that described above.
• registrants are requesting special plates, e.g., vanity identification (ID) plates and/or special design plates (e.g., wildlife plates).
• ID vanity identification
• special design plates e.g., wildlife plates.
• the registrant may select a plate ID that the state DMV will not allow (e.g., the ID may be previously used or unacceptable for other reasons). In such a case, several iterations for ordering a vanity ID plate may need to be performed.
• This web site is designed to provide limited information to a user. Such information includes the amount of fees for license renewal, directions for filling out forms sent to users, and information regarding the ability to renew plate registrations by a process over the telephone by calling an interactive voice response system, etc. Further, other types of licenses, such as hunting, fishing, and boating licenses, can be ordered over the Internet such as shown in a web site for the State of Georgia (http://www.permit.com). At this web site, for example, a resident of Georgia can fill out a form ordering a hunting or fishing license.
• Such systems are problematic for various reasons. For example, they do not deal effectively with either general issue and special issue license plate ordering processes.
• Such systems typically provide a form that may be filled out for ordering a license plate, and then the form sent to the DMV over the Internet.
• transactions such as the ordering of signs (e.g., traffic signs printed on retro-reflective materials, decals printed on retro-reflective materials, etc.) similar to license plates, are also not effectively handled.
• signs e.g., traffic signs printed on retro-reflective materials, decals printed on retro-reflective materials, etc.
• sign orders may involve several iterations between the producer and the customer to achieve a correctly designed and produced sign.
• the present invention provides systems and methods for online registration (e.g., vehicle registration) wherein interactive communication between the user and server is used to register the article, and if required upon a successful registration, result in a unique document/article (e.g., license plate or validation sticker) order for production/distribution.
• a method according to the present invention for use in online registration of a vehicle includes the establishment of a communication link between a user (e.g., through a user computer) and a registration server.
• a user interface is presented to the user (e.g., via a user computer or other device).
• the user interface provides the user with at least one or more options associated with the registration of a vehicle.
• interactive communication of information associated with the registration of a vehicle between the user computer or device and the registration server is carried out.
• user input related to one or more of the options presented to the user by the user interface regarding the registration of a vehicle is communicated by the user to the registration server.
• Information to the user is provided in response to the user information from the registration server via the user interface.
• a possible result of the interactive communication between the user and the registration server is the registration of a vehicle (a "positive registration decision").
• Another possible result of the interactive communication is a rejection of the registration (a "negative registration decision", e.g., if the user failed to meet a qualification requirement, etc.).
• Another possible result of the interactive communication between the user and the registration server is a plate/document/article order associated with the registration of the vehicle.
• the order is provided to a production facility.
• the production facility is operable to print a plate/document/article in response to the provision of the order such that the order can be distributed.
• Still another possible result of the interactive communication is a direction that the user must follow (e.g., in person or at a later date) in order to complete the registration process.
• the establishment of a communication link between the user computer or device and the registration server is accomplished by requesting a personal identification number from the user.
• the personal identification number may be provided to the user with a registration renewal reminder document previously provided to the user (e.g., reminder document from the Department of Motor Vehicles or some other source), and/or the personal identification number may be associated with a number such as a social security number, a number associated with a vehicle to be registered (e.g., a vehicle identification number, plate number, etc.), or a combination of various identifiers.
• a registration renewal reminder document previously provided to the user
• the personal identification number may be associated with a number such as a social security number, a number associated with a vehicle to be registered (e.g., a vehicle identification number, plate number, etc.), or a combination of various identifiers.
• the user interface may present various types of information and/or links to the user.
• a customized user interface may present information based on the analysis of information received from the user.
• directed advertising on the customized user interface may be presented based on the type of vehicle being registered.
• Links to commercial entities, such as insurance companies, may be based on information associated with the fact that a user needs insurance.
• Information such as maintenance information associated with the type of vehicle (e.g., safety recalls, maintenance reminders, etc.) may also be presented in the customized user interface.
• the present invention when information from the user is received with regard to one or more options related to the registration of a vehicle, the present invention may interrogate a remote computer site to verify such information received from the user. For example, such interrogation may be performed with regard to vehicle identification numbers, insurance information, credit card information, etc. Further, the remote computer may be updated with such new information. As a result of the verification process, acceptance or rejection of the registration may be determined.
• a remote computer site may be interrogated to obtain data related to information received from the user. For example, a remote computer site may be checked for whether a user has paid alimony or spousal maintenance obligations, paid child support obligations, etc. Such information may be provided back to the user and/or to a third party.
• the user interface may provide options for ordering items such as a general purpose plate/document/article and/or a special purpose plate/document/article.
• general purpose may alternatively be called “general issue”.
• special purpose may be called “special issue.”
• An option for ordering either the general issue or special issue plate/document/article is selected by the user and is communicated to the registration server.
• the order is received by the registration server and provided to a production facility where the general issue item may be produced using fixed field preprinted retro-reflective sheeting or free form blank retro-reflective sheeting.
• a special issue item order is provided to such a production facility for production of a special issue item using fixed field pre-printed retro- reflective shield sheeting or free form blank retro-reflective sheeting.
• the registration server may provide to the user, via the user interface, one or more preset fixed form special issue item designs (e.g., plate designs) for selection by the user. Further, the registration server may provide an option of customizing a design for the special issue item. In such a case, the user interface may provide a predetermined set of graphics or graphic tools for use in customizing the design. Further, the user may create and view the customized design prior to the special issue order being generated and sent to the registration server. Yet further, with regard to the selection of a special issue option, the registration server may request that the user provide, if desired, any special identification (e.g., vanity ID) for use in printing the special issue item.
• any special identification e.g., vanity ID
• the special identification selected by the user is determined to be acceptable or unacceptable.
• a vanity identification requested by the user may be compared to previously used vanity identifications or to a database of unacceptable vanity identifications for making such a determination.
• the interactive communication between the user and the registration server may result in a retro-reflective sticker (e.g., validation sticker) order.
• a retro-reflective sticker e.g., validation sticker
• the interactive communication between the user and the registration server may result in a license plate order.
• such an order may result when a user selects an option for registering a new vehicle or when a user selects an option to purchase a vanity or special issue plate.
• techniques for rejection or acceptance of an item received by a user may be performed online.
• a computer site for use in online registration of a vehicle, including at least one registration server operable for allowing the various embodiments as described above to be implemented, is also described.
• the registration server includes software for use in communicating with the user regarding such registration.
• a user interface allowing online registration of a vehicle.
• the user interface is operable and designed for allowing the method as described above in its various embodiments to be carried out.
• the interface may present options for a user to select a general issue or special issue item to be ordered, create a customized design using a predetermined set of graphics presented to the user via the interface, etc.
• the user interface may present target advertising and/or service information (e.g., vehicle recall notices) to the user via the interface.
• a system for allowing the method as described above in its various embodiments to be carried out is also described.
• a system generally includes the user computer and the registration server operable over a network for carrying out one or more of the various embodiments of the method.
• the online design and ordering of signs may also be accomplished according to the present invention.
• sheeting designs may include those for traffic signs, vehicle decals, vehicle stickers, or any other signs.
• the method may include establishing a communication link between a user device and a server.
• a user interface may be presented on the user device (e.g., a computer) to the user.
• the user interface may provide a predetermined set of graphics or graphic tools for use in customizing the sign design for the sign order.
• a sign order is communicated to the server and the sign order is sent to a sign production facility.
• the sign production facility is operable to print the sign in response to the provision of the sign order for distribution to the user.
• the designed sign may be graphically displayed with an object upon which the sign design is to be used, e.g., a vehicle, a truck, a larger sign alongside a road, etc.
• Figure 1 is an illustrative general block diagram of an online vehicle registration system according to the present invention.
• Figure 2 is an illustrative general block diagram of an online vehicle registration method capable of being carried out by the online vehicle registration system of Figure 1.
• FIG. 3 is a more detailed illustrative block diagram of the vehicle registration via direct interactive communication interface block of the online vehicle registration method of Figure 2.
• Figure 4A is a more detailed illustrative block diagram of the interrogation loops of the block diagram of Figure 3.
• Figure 4B is a more detailed illustrative block diagram of the customized user interface portion of the block diagram of Figure 3.
• Figure 4C is a more detailed illustrative block diagram of the order/fee calculation and payment portion of the block diagram of Figure 3 related to registration and license plate orders.
• Figure 4D is a more detailed illustrative block diagram of the order/fee calculation and payment portion of the block diagram of Figure 3 related to registration renewal and sticker orders.
• Figure 5 is a general illustrative block diagram of a sign design and order system according to the present invention.
• Figure 6 is a more detailed illustrative block diagram of the production/distribution of vehicle registration plate/document/article block of the online vehicle registration method of Figure 2.
• FIGS 7 A and 7B are a more detailed illustrative block diagram of the vehicle registration plate/document production/distribution diagram of Figure 6.
• Figure 7C is another alternate detailed illustrative block diagram of the vehicle registration plate/document production/distribution diagram of Figure 6.
• Figures 8 A and 8B are illustrative block diagrams of embodiments of plate production and sticker production methods according to the present invention.
• Figure 9 is an illustrative block diagram of one embodiment of a distribution method according to the present invention. Detailed Description of the Embodiments
• FIG. 1 is an illustrative block diagram overview of an online registration system 10 according to the present invention.
• the online registration system 10 may be used, for example, to register a new vehicle, order new license plates, renew a registration of a vehicle, or perform other registration tasks associated with vehicles, such as ordering replacement license plates, ordering license stickers, paying license or registration fees, etc. Therefore, as used herein, vehicle registration includes not only an initial registration of a vehicle, but also registration renewal, in addition to any other registration tasks associated with a vehicle.
• a vehicle may refer to any object requiring registration by a user with or without payment of fees.
• the vehicle is one which requires that an item (e.g., a plate/document/article) be provided in response to an order placed online using the system 10.
• a vehicle may be a car, a truck, a bicycle, a boat, a motorcycle, an airplane, etc.
• the registration process may not require that an item be provided. Instead, the registration process may simply result in a database entry that may be reviewed from time-to-time to verify compliance.
• a plate/document/article refers to any item or object distributed upon placement of an order online using the system 10.
• the plate/document/article may be a license plate (e.g., special license plate, general issue license plate, customized design license plate, etc.), a registration renewal sticker, a temporary license, a window sticker, an inspection sticker, or an access sticker (e.g., a park access sticker, a toll road sticker, etc.).
• the plate/document is produced using retro-reflective sheeting (e.g., fixed form retro-reflective sheeting, free form blank retro- reflective sheeting, etc.).
• fixed form retro-reflective sheeting refers to retro- reflective sheeting having pre-printed information on at least portions thereof.
• Free form blank retro-reflective sheeting generally refers to retro-reflective sheeting that is not preprinted with information thereon.
• the online registration system as shown in Figure 1 generally includes one or more devices such as user computer sites 14 and one or more registration servers 30 (for simplicity purposes, hereafter referred to as a single "registration server 30").
• the one or more user devices e.g., user computer sites 14
• the one or more user devices preferably communicate interactively with the registration server 30 over a publicly accessible network 12, preferably online over the publicly accessible network referred to commonly as the WEB, or more generally as the Internet.
• the devices may communicate over a private network or connection.
• the interactive communication between the one or more user computer sites 14 and the registration server 30 optimally results in a plate/document order, preferably associated with the registration of a vehicle.
• the registration server may be in communication with one or more other local or remote computer sites (e.g., database sites 38, DMV mainframe 32 and database 36).
• database sites 38 e.g., database sites 38, DMV mainframe 32 and database 36.
• the registration server 30 may be in communication with a DMV mainframe computer 32 allowing access of information from DMV vehicle registration databases 36. Further, for example, the registration server 30 may be in communication with other databases 38 such as for interrogating insurance company databases, criminal record databases, etc.
• An optional plate/document/article order resulting from the interactive communication between the registration server 30 and the one or more user devices (e.g., user computer sites 14) over the publicly accessible network 12 is preferably provided to a production management system 50 which is associated with the control of the print production system 52 and the packaging/distribution block 54.
• the print production system 52 produces plates/documents/articles for packaging and distribution as generally shown by packaging/distribution block 54.
• the publicly accessible network 12 (e.g., including the WEB of the Internet) is accessed through the user computer sites 14 which are generally, for example, small computers such as personal computers or workstations.
• Such computer sites 14 are configured so that a human user operates a computer to make requests from other computers or servers using the Internet.
• the requested data resides in large computers commonly referred to herein as servers (e.g., registration server).
• the term "user's computer” refers to a computer's general role as a computer used by a user for online registration of a vehicle, either for requesting information or for receiving information over the Internet.
• “Registration server” is used to refer to a provider of information to the user or a requestor of information from a user requesting to perform a task online with respect to a vehicle registration.
• the size of a computer, or the resources associated with it do not preclude the computer's ability to act as a user computer or a server.
• each computer may request data in one transaction and provide data in another transaction.
• the registration server 30 is the computer site accessible for interactive communication by one or more user computer sites 14.
• the one or more user computer sites 14 may include any number of conventional components such as a processor, a memory, a bus coupled to the processor and memory, a mass storage device (e.g., a magnetic card disk or an optical storage disk) coupled to the processor and memory through an I/O controller, and a network interface (e.g., a modem).
• a processor e.g., a central processing unit (CPU)
• a memory e.g., a central processing unit
• a bus e.g., a central processing unit
• a mass storage device e.g., a magnetic card disk or an optical storage disk
• a network interface e.g., a modem
• modems may be part of computer sites 14 including those shown in Figure 1.
• the one or more computer sites 14 as shown in Figure 1 include personal computer systems 16, computer systems at kiosks 18 accessible by the general public at various public or private locations, computer systems available at DMV local registration offices 20, or may be any other computer system accessible by a user operable for interactive communication used in online vehicle registration according to the present invention.
• Other devices 15 may also be used to facilitate communication between a user and the registration server 30.
• a telephone with or without memory or display features
• the practical interactive communication may be more limited. However, for very routine transactions, the use of this device may suffice.
• the registration server 30 may include conventional components such as a processor, a memory, a bus which couples the processor and memory, a mass storage device (e.g., magnetic or optical disk) coupled to the processor and memory through an I/O controller, and a network interface (e.g., a modem).
• a processor e.g., a central processing unit (CPU)
• a memory e.g., a central processing unit (CPU)
• a mass storage device e.g., magnetic or optical disk
• I/O controller e.g., a graphics processing unit
• a network interface e.g., a modem
• the Internet consists of a worldwide computer network that communicates using well-defined protocols.
• Computer systems that are directly connected to the Internet each have a unique Internet address.
• a domain name system was created with the domain name system allowing users to access Internet resources with a simple naming system.
• a uniform resource locator system was created.
• a Uniform Resource Locator (URL) is a descriptor that specifically defines a type of Internet resource and its location.
• the registration server 30 responds to the HTTP request by sending an object to the user computer 14.
• the HTTP object is a plain text (ASCII) document containing text that is written in hypertext mark-up language (HTML).
• ASCII plain text
• HTML hypertext mark-up language
• the HTML document may contain hyperlinks to other web documents.
• the web browser displays the HTML document on the screen for the user, and the hyperlinks to the other web documents may be emphasized in some fashion such that the user can select the hyperlinks.
• software e.g., instructions executable at the user computer site 14 may be sent to a user's computer site, such as in the sending of a user interface for online registration according to the present invention.
• the information transferred is generally not limited and various types of information may be sent from the registration server 30 to the user computer sites 14, and vice versa.
• a user at one of the user computer sites 14 uses web browser software to access registration server 30.
• a registration application can be reviewed and acted upon and a plate/document article order can be processed and optimally completed.
• the browser software may send an HTTP request for the home page of the registration server.
• the registration server 30 may send a response to the request.
• the response may be an HTML object, such as an interface document that is displayed by the browser, or may send software for presenting a user communication interface to the user.
• a user communication interface is presented to the user which contains one or more options available with respect to the registration of vehicles.
• the options may include a request for information from the user such as whether the user is a resident of a particular state, whether the user wishes to renew a registration, register a new vehicle, pay a registration fee, or any other option associated with vehicle registration.
• the user can then browse the options and any pages, links, etc. presented to the user and select various options and/or provide any requested information to the registration server to perform various registration functions that result in a plate/document order.
• the registration server 30 includes software for use in communicating with a user regarding registration of a vehicle and, as applicable, for carrying out the processes as described herein with reference to at least portions of Figures 2-4 and 6-9.
• the registration server 30 may, as previously described herein, provide executable code to the user's computer 14 for presenting the user communication interface thereto.
• Such code may be deleted from the user's computer site 14 (e.g., automatically deleted, upon completion of the resulting plate/document order) or saved (e.g., for use in a subsequent registration).
• the user interface may also be provided in some other manner such that interactive communication between the user computer site 14 and the registration server 30 can be effectively performed.
• the registration server 30 need not be located at any particular location and may be part of any one of various systems. For example, registration server 30 may be part of a system located locally with the DMV mainframe computer 32.
• the registration server 30 may provide a plate/document/article order resulting from the interactive communication with the one or more user computers 14 via an intranet (e.g., a non-publicly accessible network) to a production management system 50 as shown generally by block 34.
• an intranet e.g., a non-publicly accessible network
• a production management system 50 as shown generally by block 34.
• intranet e.g., a non-publicly accessible network
• the registration server 30 may be located locally with the production management system 50 for the direct communication therebetween as indicated by the double-ended arrows.
• a registration server 30 may be located remotely from the production management system 50 and the publicly accessible network 12 may be used to transfer data, e.g., plate/document orders, from the registration server 30 to the production management system 50.
• the production management system 50 after receiving plate/document orders may present them in some organized fashion such that a print production system 52 can be efficiently and effectively controlled to prepare plates/documents corresponding thereto.
• the registration server 30 may be controlled by a Department of Transportation or a Department of Motor Vehicle organization of a State government organization, or may be controlled by a private organization on behalf of such governmental organizations.
• the controlling organization will have the registration server 30 located within its computer system or network.
• the registration server 30 may be located locally with the production management system 50 system as described herein or with any other computer sites.
• the registration server 30 is located locally with the production management system 50 such that integration of the plate/document orders into the print management system is easily and effectively accomplished.
• registration server 30 may be used to send information to various other computer sites on a real-time basis or in any other manner, such as by batches.
• plate/document/article orders may be batch processed or may be sent on a realtime basis to the production management system 50 via Internet, remote intranet, direct connection, etc.
• the online registration system 10 as shown in Figure 1 is one illustrative system embodiment which may be used for carrying out the online registration method 100 as shown in Figure 2.
• the online registration method 100 includes the provision of user input 120 for use in vehicle registration through an interactive communication interface (block 122).
• the user input 120 is preferably user input from one or more user computer sites 14.
• Block 122 represents the software operating upon user input with interactive communication therebetween as represented by the double-ended arrow between blocks 120 and 122.
• Resulting from the interactive communication is a registration decision and/or notification.
• the notification of a decision (and entry of the notification in a database) completes the process.
• the interactive communication results in a plate/document/article order which is provided for production/distribution as represented generally by block 124.
• the plate/document/article is provided to a recipient as shown in block 128, e.g., a local DMV office, the user, a third party, etc.
• the distribution may be tracked to ensure the proper receipt of the order and such tracking information may be stored in an appropriate database.
• FIG 3 is an illustrative general block diagram of the interactive communication interface block 122 of the online vehicle registration method 100 shown in Figure 2.
• the registration server 30 is accessed and a link between the registration server 30 and user's computer 14 is established.
• the initial user input results in presentation of a user communication interface 200 for facilitating interactive communication between the registration server 30 and the user's computer 14.
• software operable on the user's computer may be provided from the registration server 30 to present the user communication interface 200 to the user, e.g., via a display associated with the computer site 14. It will be recognized that the interface may be entirely different depending upon the identity of the user.
• the user may be a clerk at a local DMV office that desires to order 100 plates.
• the user could be an owner of a single car.
• Any peripherals known to the one skilled in the art may be used in combination with the user interface 200 presented to the user, e.g., touch screen, keyboard, mouse, etc.
• a vehicle registration decision can be obtained and optionally a plate/document/article order 206 (e.g., license plates, renewal tabs, inspection stickers, etc.) can be efficiently and/or effectively processed.
• interactive communication process 122 may take place via communication between the user communication interface 200 and central routines 204.
• the user communication interface 200 is used to allow the user to provide input such as registration/renewal information 202 upon which central routines 204 operate to produce a vehicle registration plate/document order 206.
• the central routines 204 provide initiation of, control of, and information back to the user communication interface 200 via various process loops.
• process loops may include interrogation loops 210, customized user interface 212, order/fee calculation and payment loop 216, security procedures 218, and temporary plate/document loop 220.
• Various loops may perform processes simultaneously as communication is occurring between the user computer 14 and the registration server 30.
• loops 210, 212, 216, 218, and 220 shall be described further below with reference to Figures 4A-4D. It is recognized that for a particular system some of these loops will be optional. Also, the loops are not described in any particular relevant order.
• the customized user interface loop 212 may be operable throughout a substantial portion, or a much smaller portion, of the period of communication between the user computer 14 and the registration server 30. Interrogation loops 210 may also be processing information during this time as further described below. However, security procedures 218 are generally performed at certain times as required during the interactive communication between the user computer 14 and the registration server 30.
• a security procedure 218 may be performed with regard to a credit card used for payment of a registration or license fee during the order/fee calculation and payment loop 216.
• other loops such as temporary plate/document loop 220 may occur only at the end of a registration process, as further described below.
• the order in which such loops are described in no manner describes the general timing of such loops within the overall online registration method 100.
• loop processes may be occurring serially or in a simultaneous manner with other occurring loop processes.
• Security procedure loop 218 preferably includes routines carried out for security purposes of the overall online registration process.
• the security procedure routines may include routines for encryption of information between the user computer 14 and the registration server 30, the security routines may require the registration server 30 to direct that an interrogation loop 210 be performed (e.g., checking of a credit card limit or authenticity as further described below with regard to interrogation loops 210), and preferably, the security procedure routines are used to determine that the user has the authority to perform online vehicle registration.
• various requests for information known only by the user may be made.
• the user is presented with requests from the registration server 30 via the user communication interface 200. For example, the user is asked whether the user is a resident of a particular state and whether the user is going to be initially registering a vehicle or whether a renewal of a registration is going to be attempted.
• the registration server may request that the user enter a personal identification number (PIN), or any other identifier suitable to assure that the person attempting to register or renew a registration is authorized.
• PIN personal identification number
• such a PIN may be provided to the user with a renewal notice prior to expiration of a user's registration of a vehicle.
• the registration server may request an identifier that is associated with the vehicle being registered.
• the registration server 30 may request that the plate number of the currently issued plate associated with the vehicle having its registration renewed be entered, that the social security number of the owner of the vehicle be entered, that some other governmental issued number such as a driver's license number be entered, that a combination of such numbers be entered, etc.
• the central routines 204 perform interrogation loops 210 to check that such identifiers are correct and that the user is authorized to proceed with a registration process.
• various other security procedures may be carried out through the online registration process 100 and that the present invention is not limited to only those illustrative security procedures described herein.
• Optional temporary plate/document loop 220 generally includes routines performed at the end of a registration process.
• the temporary plate/document loop 220 provides for a temporary plate/document useable by the user to verify that an online registration process, e.g., a renewal registration process, has indeed been performed by the user and that appropriate license fees, registration fees, etc. have been paid.
• the registration server 30 upon completion of the registration process, provides a document file to the user computer 14. The user may then print out the document on an appropriate printer, e.g., a home ink jet printer. Further, for example, the document may include an authenticity marking, such as a type of printed water color background or any other anti- forgery data, to prevent illegal creation of such temporary documents.
• the registration server 30 may be automatically notified that such a temporary plate/document is being printed so that information can be recorded with proper authorities.
• the temporary plate/document may be printed with various types of information associated with the vehicle being registered.
• information may include the vehicle identification number upon which the temporary plate/document is to be placed, may include information relating to the time period for which the temporary plate/document may be used, may include various types of data with regard to the vehicle itself such as color, make, and year, or may include any other data such as that which would be beneficial in allowing an enforcement official to determine whether the vehicle is properly licensed.
• Interrogation loops 210 include routines to perform various information queries 214 as shown in Figure 3 and as shown in further detail in the illustrative block diagram of
• the interrogation loops 210 are loops which often require interface with other computer sites, such as the DMV mainframe computer site 32 which allows access to vehicle registration databases 36, and/or other databases 38, as shown in Figure 1.
• registration server 30 may include extraction routines, interface routines, knowledge regarding various database formats, and any other information necessary to query other computer sites for information, update such sites (e.g., provide information to such databases for updating them), and/or report information to a particular site.
• queries may take place via an intranet, the Internet, or any other network between the registration server 30 and the computer sites controlling access to such databases.
• the user communication interface 200 receives user input
• a query to verify data and/or update data is performed as generally represented by block 234.
• a query of appropriate databases is made and/or a report is provided to an appropriate or proper third party.
• verification loops 230 may be performed which accesses a vehicle registration database 36.
• the DMV database 36 may be used to verify such information and, if such information has changed, to update such information.
• any new information with regard to vehicle registration numbers, vehicle identification numbers, insurance carriers, or any other information associated with the vehicle registration may be provided to DMV mainframe computers for updating of the vehicle registration databases 36.
• the user communication interface 200 may request the user to input insurance information regarding the vehicle being registered.
• the central routines 204 may determine that a verification loop 230 needs to be performed to verify the insurance information. As such, a query and/or update 234 is optionally performed.
• the registration server accesses an insurance database 238 to verify that the information provided by the user is correct. Further, such insurance information may be used to update either the insurance company's records and/or may be used to update a vehicle registration database 236 at the DMV mainframe computer site 232.
• verification loops 230 with respect to credit card information, driver's license information, driving record information (e.g., arrests made that may affect the registration of a vehicle), or any other information which may require verification, can be performed.
• the user's request for registration and/or order for a plate/document/article may be reviewed based on the information from the verification loops.
• the request and/or order may be accepted or rejected accordingly as shown by decision block 232 in Figure 4A.
• the user communication interface 200 may request the user to enter a social security number or some other identification number. Based on such user input, the central routines 204 may determine that a report loop 240 is required. For example, based on the social security number, the query may be made to a proper agency with respect to whether the user identified by the social security number has outstanding alimony payments that need to be made, whether that user has outstanding child support payments that need to be made, etc. Information with regard to the address of the user belonging to the social security number may be provided to the proper agency or the user may be notified via the user communication interface 200 that such alimony or child support is due.
• central routines 204 may determine that a report loop 240 is required upon entry by the user of vehicle information (e.g., year, model, type, etc.). For example, a query to a safety database at a particular auto manufacturer or a scheduled maintenance database at the auto manufacturer may be made. Information, e.g., recall information, scheduled maintenance information, air bag information, etc., may then be obtained and reported to the user via the user communication interface 200. Further, such various types of information may be provided to the user in conjunction with the distributed plate/document at the time it is provided to the user. Alternatively, the name of the user may be provided to a local dealer who can provide such information.
• vehicle information e.g., year, model, type, etc.
• vehicle information e.g., year, model, type, etc.
• Information e.g., recall information, scheduled maintenance information, air bag information, etc.
• the name of the user may be provided to a local dealer who can provide such information.
• central routines 204 may determine that report loops 240 may be necessary to query enforcement agencies with respect to outstanding warrants, traffic violations, etc. For example, upon query and attainment of such information, if fees are warranted such as for traffic violations, they may be added to the fee necessary for a license renewal, e.g., a fee determined in the order/fee calculation and payment loop 216.
• Customized user interface loop 212 as shown in Figure 3 is further illustrated in an illustrative detail block diagram of Figure 4B.
• central routines 204 initiate customized interface loop 212.
• customized interface loop 212 may include various routines for customizing user communication interface 200.
• routines may include processes to determine directed advertising based on registration/renewal information as shown in block 240, may provide links to related commercial entities as shown generally in block 242, and may provide various announcements as shown in block 244.
• direct advertising based on registration/renewal information block
• the customized user interface loop routines may make determinations for types of directed advertising based on the user's income level. For example, certain travel ads (e.g., exotic locations) may be advertised on the user communication interface 200 based on user input that the user owns an expensive car. Further, for example, camping ads may be presented on the user communication interface 200 for users owning sport utility vehicles. Other examples include used car ads, military recruitment or college recruitment ads for 18 year old registrants. Various types of directed advertising may be presented based on numerous characteristics of the user input, such as car type, age, geographical location, etc. Further, based on information provided regarding the user, links to related commercial entities (block 242) may be provided.
• types of directed advertising may be presented based on numerous characteristics of the user input, such as car type, age, geographical location, etc.
• central routines 204 may determine that a loop 242 may be required to link the user to insurance carriers. Further, for example, based on the type of vehicle the user is attempting to register, or renew a registration for, a link to a car dealership for such model of vehicle may be presented on the user communication interface 200 so as to present the user with a possible trade-in opportunity.
• central routines 204 may determine that certain announcements (block 244) should be presented in the customized user interface 200 for the user.
• announcements may include recalls and safety concerns regarding a vehicle owned by the user.
• other announcements related to transportation may also be provided, such as transportation update information and emissions update information.
• Figure 4C shows an illustrative block diagram of a process with respect to order/fee calculation and payment for a license plate order.
• Figure 4D includes an illustrative block diagram related to the order/fee calculation and payment for a validation sticker order related to a renewal of a vehicle registration.
• user communication interface 200 presents options to the user related to whether the user desires or is required to place a plate order, such as in the initial registration of a vehicle, or whether the user desires or is required to renew a registration resulting in a validation sticker order, e.g., a retro-reflective sticker. If the user selects or is directed to select a plate order, the illustrative plate order process 260 as shown in Figure 4C may be performed. If, however, a renewal of a registration is to take place, illustrative sticker order process 280 as shown in Figure 4D may be performed.
• the illustrative license plate order method 260 includes presenting to the user via the communication interface 200 the option of selecting a general issue plate (sometimes called a "general purpose” plate) or a special issue license plate (sometimes called a "special purpose” plate) as shown by decision block 261.
• a general issue license plate is characterized as including only fixed form preprinted retro- reflective sheeting wherein the fields are filled with standard information and are not manipulatable by the user. Further, the license number (or characters) are standard unselectable characters as opposed to special characters obtainable for vanity identification (ID) plates. If a user selects the option of a general issue license plate, a vehicle registration plate order optimally results as shown in block 272.
• a fee calculation 276 is performed with regard to the plate order and is presented to the user via the communication user interface 200.
• a payment transaction 278 is then completed in a manner as is readily known with respect to other payment transactions performed over the Internet.
• such payment transaction may include an interrogation loop 210 to verify credit card information, credit card limits, etc.
• the user is preferably presented with a plurality of preset plate designs as shown by decision block 262.
• preset plate designs may include, as is generally known, wildlife supporter plate designs, plate designs indicating support of a university, or other preset plate designs where such plate designs are typically purchased by a large group of users. If the user selects one of the preset plate designs, then the user is given the opportunity to request a vanity ID per decision block 264. If a vanity ID is not desired, then the vehicle registration plate order is completed (block 262). In other words, the plate order includes a preset plate design with a standard license plate number.
• an interrogation loop 266 is performed to validate the vanity ID selection. In other words, an interrogation loop 266 is performed to compare the vanity ID to other vanity IDs already in use and/or compared to a listing of unacceptable vanity IDs. If the vanity ID is validated as per decision block 268, then a plate order 272 results. If the vanity ID is not validated per decision block 268, then the user communication interface 200 requires that the user provide a new vanity ID selection and the interrogation loop 266 to validate the new vanity ID selection is repeated. Such a closed-loop is performed until a valid vanity ID is attained or the user decides that a vanity ID is not desired.
• the customized plate design interface presented to the user includes a set of predetermined graphical elements for use in customizing the design for the special plate order.
• the user is then able to create a customized design using the predetermined set of graphical elements and view a special plate having such a customized design on the communication user interface 200.
• the predetermined set of graphics may include any graphical elements which may be used to create designs.
• Various limitations may apply to the graphical elements, positioning of such elements, colors, etc. For example, such elements may need to be placed and colors chosen so as to provide an unobstructed view of the vehicle license number.
• the user Upon completion of the customized plate design and acceptance thereof by the user, the user is given the option of requesting a vanity ED per decision block 264. If no vanity ED is requested, then the customized design plate order is issued with a standard license number and fee calculation 276 and payment transaction 278 are carried out. If a vanity ID is requested per decision block 264, then the validation process as described previously is performed until a vanity ID is validated. Thereafter, a customized design plate order with a vanity ID is issued and a fee calculation 276 and payment transaction
• the sticker order method 280 as shown in Figure 4D is simplified relative to the plate order process 260 of Figure 4C.
• the user inputs information (block 120) to the user communication interface 200 selecting an option that a renewal of a registration is to be completed.
• a sticker order results from the interactive communication between the user and the registration server, e.g., loops 218, 220, 210 etc., as shown generally in block 284.
• the communication user interface 200 receives user information regarding the vehicle whose registration is being renewed. Thereafter, various types of information on the sticker may be matched to such information. For example, characters on the sticker may be matched to the vehicle identification number or the license plate number as shown generally by block 282.
• the sticker will include a number that is matched to the plate and/or to the vehicle.
• Preferred vehicle registration sticker forms and sheeting are described in Patent Application No. PCT/US99/06918 filed March 30, 1999 and in U.S. Pat. Application No. 09/379,534, which are herein incorporated by reference.
• Figure 5 is a general diagram presenting a similar process as described with regard to customized plate design block 263 of Figure 4C only in the context of providing a mechanism for ordering signs or other articles printed on retro-reflective sheeting.
• a sign includes various types of signs using retro-reflective sheeting such as traffic signs, safety signs, decals on the side of vehicles or other objects, etc.
• sign order process 300 in Figure 5 a user provides input 302 to access a web server.
• the web server allows the user to create a custom designed sign as shown generally in block 304.
• the user is allowed to use a set of predetermined graphics as shown provided by block 308.
• a sign order 310 is provided to the web server.
• the web server then, like a license plate order, may provide the sign order to a production facility for production.
• the designed sign may be viewed relative to an object upon which the sign is to be placed or positioned.
• the sign is a decal such as a retro-reflective decal including an emergency number
• the decal may be positioned relative to a car on the display such that the user may view the decal in the context of the object upon which it is to be positioned.
• the central routines 204 upon successful completion of the interactive communication between the user computer 14 and the registration server 30, optionally provide an order for production of a plate/document/article and distribution thereof as generally shown by block 124 of Figure 2, and as further shown in the illustrative block diagram of Figure 6.
• production and distribution process 124 for a vehicle registration plate/document article 124 includes the provision of one or more vehicle registration plate/document orders under control of the central routines 204 of registration server 30.
• production orders may be provided to a production management system 50.
• the production management system 50 generally performs various functions such as the preparatory production processes 400 as shown in Figure 6.
• Such preparatory production processes 400 may include license plate/document data acquisition 402, license plate/document verification and preparation for production process 404, and license plate/document production scheduling and management 406.
• production of the plate/document/article is performed (block 408). Thereafter, the plate/document article is distributed (block 410).
• FIG. 7A One illustrative embodiment of the production/distribution process 124 for vehicle registration plates/documents is shown in the illustrative block diagram of Figure 7A. It will be recognized by one skilled in the art that the details shown in Figure 7A are for illustration only and that various additional processes may be performed or many of the processes described therein may be removed without affecting the ultimate outcome of a produced and distributed plate/document/article.
• Figures 7A and 7B provide for a production process for general issue and special issue orders.
• general issue orders include orders for a plate/document/article that is produced using preprinted retro-reflective sheeting wherein fields of the sheeting are preprinted with general issue information.
• preprinted retro- reflective sheeting is also referred to herein as fixed form retro-reflective sheeting.
• a special order includes orders for plates/documents/articles produced using free form blank retro-reflective sheeting, and in some cases preprinted retro-reflective sheeting (e.g., special orders for a predetermined preset design as described previously herein).
• preprinted retro-reflective sheeting e.g., special orders for a predetermined preset design as described previously herein.
• the production and distribution process 124 generally includes acquiring order data (block 402). For example, as shown in Figures 7A and 7B, general issue orders and/or special orders for plates/documents/articles are provided. Upon acquisition of such order data, which may occur on a serial basis, in real-time, on a batch basis, or by any other time sequence manner, the production management system 50 provides for the acknowledgment and validation of such plate/document/article orders. For example, an acknowledgment may be sent to the registration server 30 indicating that an order was received. Upon acknowledgment and validation of such orders, generally, the process proceeds to check general issue and special orders for various duplicate and/or illegal matters and/or invalid names, characters, character sets, etc. For example, general issue orders may be checked such that duplicate plates are not produced.
• special orders wherein a vanity ED has been requested may be checked to assure that the vanity ED is not a duplicate of a previously issued ED and/or that the character sets used on the special order are not illegal, e.g., use profanity.
• the orders are provided for production scheduling and management (block 406).
• Various processes may be performed to organize and arrange such orders for efficiency in production.
• the orders may be sorted by plate type (e.g., how the plate type is to be made such as whether the plate type is to be produced from free form blank retro-reflective sheeting or fixed form retro-reflective sheeting). Further, for example, such orders may be sorted by destination.
• a production schedule for the plate/document orders is generated dependent upon what process is to be used to produce such plates/documents.
• the production processes are illustrated as including a free form blank retro-reflective sheeting production process and a fixed form retro-reflective sheeting production process.
• various other types of production processes may be used according to the present invention.
• a free form blank retro-reflective sheeting production schedule is generated for the plate/document orders that require free form blank retro-reflective sheeting production.
• general issue plates may be printed using free form blank retro-reflective sheeting, and special plates/documents more likely will require free form blank retro-reflective sheeting production.
• a fixed form retro-reflective sheeting production schedule for those plates/documents to be produced by a fixed form retro-reflective sheeting production process.
• general issue plates/documents which are produced using preprinted retro-reflective sheeting having the fields already completed with general information other than the plate number, are generally produced by the fixed form production process.
• fixed form production processing has been used for production of license plates as is generally known in the art.
• thermal transfer printing as described in the following references has been used: U.S. Patent No. 5,508,105 to Orensteen et al., issued April 16, 1996, entitled "Thermal Print Receptive and Frangible Retroreflective Polymeric Sheetings;" U.S. Patent No.
• the production scheduling and management process 406 upon generation of production schedules as described above, generates run lists for production and packaging of the plate/document orders for both the free form blank retro-reflective sheeting production processes and the fixed form retro-reflective sheeting production processes. Thereafter, as shown in Figures 7 A and 7B, the license plates/documents/articles are produced. General information regarding such production is provided below with reference to Figure 8 A and 8B.
• the production process (block 408) also provides for inspection of the plates produced. For example, such plates/documents produced may be visually inspected, the information on the plates may be inspected such as by reading of bar codes, and/or any other inspection processes for quality purposes or for any other purposes may be performed.
• the plate/document is distributed (block 410), e.g., optionally packaged with a shipping label including a bar code identifier. If the inspection results in a rejected plate, the defects are logged and a new plate/document is reordered as generally shown in blocks 41 1 and 413.
• One particular production/distribution process 469 for use with thermal transfer printing is shown in the attached Figure 7C.
• Figure 7C is an alternate illustrative embodiment to the process shown in Figures 7A and 7B.
• electronic order files 471 are received from a registration server 30 at a production management system 470, e.g., via a network 475.
• the production management system 470 sorts the orders into special and general issue orders (block 473) and a schedule is developed with associated materials (e.g., printed schedules, packing slips, production travelers, movement orders, box labels, shipping labels) for control of the production process (block 476).
• the production is then carried out under control of the production management system 470 via a production server 472 (which typically includes a database and associated printer files) and a printer (e.g., a thermal transfer printer) 474.
• a production server 472 which typically includes a database and associated printer files
• a printer e.g., a thermal transfer printer
• the articles may optionally be further processed (e.g., by laminating the printed component to a substrate and/or blanking the printed component into pieces). This is shown schematically in block 477.
• the finished articles may also be optionally and preferably inspected (manually and/or automatically) as indicated by block
• Accepted articles may then be shipped to the recipient.
• a notice is provided to the production management system 470 (e.g., to the production server 472) so that a remake can be made.
• Figures 8A and 8B generally describe print production processes, however, specific details with regard to such processes are described in the patents as referenced hereinabove. Generally, Figures 8A and 8B are provided to describe the types of information that may be printed on the plates/documents produced.
• Figure 8A shows a block diagram of a plate production process 600. The plate production process is initiated under control of a production management system (block 602). Generally, a film is printed with one or more of a plate ED/number (e.g., vanity or general issue), a bar code, a plate design (e.g., special or general issue), a vehicle identification number, advertising information, etc. For example, a bar code may be used for tracking and inventory, etc.
• a plate ED/number e.g., vanity or general issue
• a bar code e.g., a bar code
• a plate design e.g., special or general issue
• a vehicle identification number e.g., advertising information, etc.
• the film may be either a free form blank retro-reflective sheeting, or may be a fixed form retro-reflective sheeting, as described in the references above.
• the film is generally laminated to a substrate (block 606), such as a metal substrate.
• the plate is then complete for packaging and shipping (block 608).
• a sticker production process 620 such as for production of a retro-reflective sticker issued in a renewal of a registration, e.g., a sticker to be applied to a previously issued plate, is shown in Figure 8B. Again, the production process is initiated (block 622) such as under the control of a production management system per a schedule as described above.
• the sticker may be printed with one or more of: date (e.g., year, month); a bar code; vehicle identification number; or any other information as desired (block 624). Thereafter, the sticker is completed for packaging and shipping (block 626).
• date e.g., year, month
• bar code e.g., bar code
• vehicle identification number e.g., vehicle identification number
• any other information e.g., shipping, shipping, or any other information as desired.
• the sticker is completed for packaging and shipping (block 626).
• Preferred vehicle registration sticker forms and sheeting are described in Patent Application No. PCT/US99/06918 filed March 30, 1999 and in U.S. Pat. Application No. 09/379,534, which are herein incorporated by reference.
• Figures 8A and 8B are provided to show the various types of information which may be printed on plates and stickers using the processes as described above.
• a user may order a plate.
• the plate order may be immediately sent in real-time to production management system 50 for production control.
• the plate is then produced and thereafter shipped to the user for use. This reduces the need for various processes of managing and administrating a larger non-online registration system, provides for an efficient production center and distribution center, and achieves significant economies of scale for such production.
• Figure 9 is an illustrative block diagram of a distribution process 410.
• the plate/document may be shipped (block 712) directly to the user which placed the order via the user computer 14.
• the recipient receives the plate/document and inspects the order (714).
• the user can then reject (block 716) the order via the user communication interface 200 or can affirm acceptance (block 718) of the plate/document.
• a message from the registration server may be used to follow up on whether the plate/document was received and accepted. For example, if the user does not reply to the message it may be automatically assumed that the transaction was completed successfully.
• the plate/document may not be sent to the end user, particularly in the case of a general issue license plate.
• the online orders may be used to control the inventories at particular local DMV offices who distribute the plate to the user.
• the local DMV office is requested to provide a plate to a particular user based on a user order of a general issue plate.
• the production and distribution process is notified that they need to produce a plate to replace the one at the local DMV office that distributed a general issue plate to the user.
• the production and distribution systems may be notified that materials and supplies for additional plates are needed.

Landscapes

• Business, Economics & Management (AREA)
• Physics & Mathematics (AREA)
• General Business, Economics & Management (AREA)
• General Physics & Mathematics (AREA)
• Engineering & Computer Science (AREA)
• Theoretical Computer Science (AREA)
• Management, Administration, Business Operations System, And Electronic Commerce (AREA)
• Information Transfer Between Computers (AREA)

Applications Claiming Priority (5)

Publications (1)

Family

ID=26852554

Family Applications (1)

Country Status (4)

Families Citing this family (7)

• 2000
  • 2000-09-20 WO PCT/US2000/025734 patent/WO2001022317A2/en active Application Filing
  • 2000-09-20 AU AU75942/00A patent/AU7594200A/en not_active Abandoned
  • 2000-09-20 EP EP00965180A patent/EP1222590A2/en not_active Withdrawn
  • 2000-09-20 JP JP2001525609A patent/JP2003523553A/ja active Pending

Non-Patent Citations (1)

Also Published As

Similar Documents

Legal Events