EP3207723A1 - Plate-forme de mise en réseau de données d'incident d'automobile - Google Patents
Plate-forme de mise en réseau de données d'incident d'automobileInfo
- Publication number
- EP3207723A1 EP3207723A1 EP14904054.5A EP14904054A EP3207723A1 EP 3207723 A1 EP3207723 A1 EP 3207723A1 EP 14904054 A EP14904054 A EP 14904054A EP 3207723 A1 EP3207723 A1 EP 3207723A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- incident
- data
- user
- service providers
- platform
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Withdrawn
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; 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
- G06Q30/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
- G06Q30/0241—Advertisements
- G06Q30/0251—Targeted advertisements
- G06Q30/0257—User requested
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; 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
- G06Q30/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
- G06Q30/0241—Advertisements
- G06Q30/0251—Targeted advertisements
- G06Q30/0261—Targeted advertisements based on user location
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; 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
- G06Q30/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
- G06Q30/0241—Advertisements
- G06Q30/0251—Targeted advertisements
- G06Q30/0267—Wireless devices
Definitions
- the present disclosure generally relates to automobile incidents and networking individuals with service providers.
- an individual may have an automobile incident such as an accident, a citation for a traffic violation, or arrest for driving under the influence.
- the individual may need the assistance of a service provider, such as an attorney or insurance company.
- the conventional method would require the individual to manually gather all necessary information such as, but not limited to, pictures and video of the incident aftermath, witness testimony and police officer information. This often causes problems, as the individual may not know what information to gather and have difficulty consolidating the information without losing any essential elements therein. Then, under the conventional method, the individual would need to find a service provider to assist the individual in taking the proper course of action to resolve the automobile incident. Finding a well-qualified and reasonably priced service provider presents yet another hurdle that the individual must overcome in resolving the automobile incident.
- An automobile incident data networking platform may be provided to help consumers navigate the intersection between everyday driving and the laws of the road.
- the platform may capture data and information related to traffic incidents. Whether it's a severe auto accident, fender bender, speeding ticket, routine traffic ticket, or a DUI, the platform may help consumers preserve data/evidence and instructs them how to utilize that data to protect themselves and preserve their rights. Additionally, the platform may help individuals contact emergency services, as well as friends and loved ones in emergencies on the road. Furthermore, the platform may allow drivers to immediately call an emergency provider as well as send texts and emails to friends and family that alerts them that they are in an emergency situation and it gives them the GPS generated location of the emergency.
- the platform may comprise a network for consumers to find service providers connected to issues involving traffic incidents. This includes, but is not limited to, for example, personal injury attorneys, DUI attorneys, car repair shops, auto glass repair shops, car
- These service providers may be enabled to interface with the consumer through the platform, viewing the incident data and providing quotes in response thereto. The consumer may then select, through the platform, at least one desired service provider to handle the incident or portions thereof.
- drawings may contain text or captions that may explain certain embodiments of the present disclosure. This text is included for illustrative, non- limiting, explanatory purposes of certain embodiments detailed in the present disclosure.
- drawings may contain text or captions that may explain certain embodiments of the present disclosure. This text is included for illustrative, non- limiting, explanatory purposes of certain embodiments detailed in the present disclosure.
- FIG. 1 illustrates a platform consistent with embodiments of the present disclosure
- FIG. 2A is a flow chart of a method for providing an automobile incident data networking platform
- FIG. 2B is a flow chart of a method for providing platform for directing interaction between a user and service provider;
- FIG. 3 is an illustration of an embodiment for selecting the submission type consistent with the present disclosure
- FIG. 4 illustrates an emergency menu consistent with embodiments of the present disclosure
- FIG. 5 illustrates an embodiment of a prompt for enabling the user to add or edit more contact information
- FIG. 6 illustrates a menu for the user to add data pertaining to an accident consistent with embodiments of the present disclosure
- FIG. 7 illustrates an embodiment for the location display consistent with the present disclosure
- FIG. 8 illustrates a menu for adding photos consistent with embodiments of the disclosure
- FIG. 9 illustrates a menu for inputting information for another party involved in the incident consistent with embodiments of the disclosure.
- FIG. 10 illustrates a menu for inputting information for another vehicle involved in the incident consistent with embodiments of the disclosure
- FIG. 11 illustrates a menu for inputting information for one or more responders involved in the incident consistent with embodiments of the disclosure
- FIG. 12 illustrates a menu for adding photos consistent with embodiments of the disclosure
- FIG. 13 illustrates a menu for witness data collection consistent with
- FIG. 14 illustrates an example of a ticket menu consistent with embodiments of the present disclosure.
- FIG. 15 is a block diagram of a system including a computing device for performing the method of FIG. 2.
- An automobile incident data networking platform may be provided.
- This platform may facilitate a network of service providers and provide consumers access to that network of service providers.
- Service providers may include, for example, but not be limited to, attorneys, insurance companies and body shops.
- the platform may enable consumers to communicate with those service providers with case specific information. This may be accomplished by, for example, enabling the consumers to provide case specific information to the service providers through the platform of the present disclosure.
- the platform may enable the service providers to informatively bid on the consumer's matter. Further, the platform may empower the consumer to select the service provider he or she wishes to work with.
- FIG. 1 illustrates one possible operating environment through which a platform consistent with embodiments of the present disclosure may be provided.
- an automobile incident data networking platform 100 may be hosted on a centralized server 110, such as, for example, a cloud computing service.
- a user 105 may access platform 100 through a software application.
- the software application may be embodied as, for example, but not be limited to, a website, a web application, a desktop application, and a mobile application compatible with a computing device 1500.
- One possible embodiment of the software application may be provided by the Auto Law ProTM suite of products and services.
- the computing device through which the platform may be accessed may comprise, but not be limited to, for example, a desktop computer, laptop, a tablet, or mobile telecommunications device.
- the computing device through which the platform may be accessed may comprise, but not be limited to, for example, a desktop computer, laptop, a tablet, or mobile telecommunications device.
- the present disclosure is written with reference to a mobile telecommunications device, it should be understood that any computing device may be employed to provide the various embodiments disclosed herein.
- the platform may further be comprised of a plurality of registered service providers related to issues involving traffic incidents, such as, for example, personal injury attorneys, DUI attorneys, car repair shops, auto glass repair shops, car
- the platform components may be accessed and/ or configured by a user via an admin portal provided by, for example, the software application.
- the admin portal may provide a dashboard including search capability and diagnostics.
- the admin portal may enable the user to set various configuration, security, and operational parameters.
- the platform may capture data and evidence related to traffic incidents such as, for example, a severe auto accident, fender bender, speeding ticket, routine traffic ticket, or a DUI. Further, the platform may enable users store data and evidence. The platform may determine the location of the user by utilizing methods, such as, for example, GPS, Wi-Fi, or triangulation of cell phone service towers. Moreover, the platform may enable users to utilize that data in communication with service providers. Additionally, the platform may also enable users to contact emergency services, as well as friends and family in emergencies on the road. The platform may enable users to send texts and emails to friends and family that alerts them that they are in an emergency situation.
- traffic incidents such as, for example, a severe auto accident, fender bender, speeding ticket, routine traffic ticket, or a DUI. Further, the platform may enable users store data and evidence. The platform may determine the location of the user by utilizing methods, such as, for example, GPS, Wi-Fi, or triangulation of cell phone service towers. Moreover, the platform may enable users to utilize
- FIG. 2A is a flow chart setting forth the general stages involved in a method 200A consistent with an embodiment of the disclosure for providing an automobile incident networking platform 100.
- Method 200A may be implemented using a computing device
- computing device 1500 may be used to perform the various stages of method 200A.
- different operations may be performed by different networked elements in operative communication with computing device 1500.
- server 110 may be employed in the performance of some or all of the stages in method 200A.
- server 110 may be configured much like computing device 1500.
- stages illustrated by the flow charts are disclosed in a particular order, it should be understood that the order is disclosed for illustrative purposes only. Stages may be combined, separated, reordered, and various intermediary stages may exist. Accordingly, it should be understood that the various stages illustrated within the flow chart may be, in various embodiments, performed in arrangements that differ from the ones illustrated. Moreover, various stages may be added or removed from the flow charts without altering or deterring from the fundamental scope of the depicted methods and systems disclosed herein. Ways to implement the stages of method 200 will be described in greater detail below.
- Method 200A may begin at starting block 205 and proceed to stage 210 where computing device 1500 may receive a submission type.
- submission types may include an emergency, an accident or a ticket.
- FIG. 3 shows an illustration of an embodiment of a home interface 300 for selecting the submission type consistent with the present disclosure.
- a placeholder image or text 301 may be provided.
- Emergency button 302 may be a user selectable button corresponding to an emergency submission type; accident button 303 may be a user selectable button corresponding to an accident submission type; and ticket button 304 may be a button corresponding to a traffic ticket type-
- a capture media button 305 may enable the user to capture multimedia content for storage and/or communication.
- a user may select button 305 and, in response thereto, platform 100 may enable a recording interface to be provided. The recording interface may enable the user to capture images, videos, and/or audio files. Upon capture, platform 100 may communicate the captured media to a plurality of specified contacts (as will be better understood below] and return to home interface 300.
- a find services button 310 may be provided.
- platform 100 may provide, to the user, a listing of service providers registered with platform 100.
- service providers may be registered and vetted through platform 100. In this way, the user may quickly access, for example, a sortable and searchable service provider list, thereby enabling the user to select a fitting service provider for an incident.
- stage 220 computing device 1500 may optionally determine the user location.
- the user location may be determined, for example, by GPS, Wi-Fi, or triangulation of cell phone service towers.
- the user may be able to select the location of the incident. This may be accomplished, for example, by entering an address in text or by selecting a location on a map.
- FIG. 4 illustrates an emergency interface 400 consistent with embodiments of the present disclosure.
- Emergency interface 400 may be comprised of, for example, a navigation button 410; a title menu 412; a settings button 414; a series of buttons for contacting specific groups 416, such as, for example, 911, emergency contacts and DUI contacts; a button 418 for viewing contacts; a button 420 for reporting accident information; and a button for reporting information for a ticket 422.
- Selecting "CALL 911" may take the user to the communication module (i.e., phone section] of their device with the number 911 pre-dialed. Once the call is complete, the device may return to emergency interface 400. Selecting "SEND
- EMERGENCY MESSANGES may automatically notify any pre-selected contacts via SMS or MMS messages.
- the messages may include the location information detected for the user and a pre-determined message provided by the user or an administrator of the platform. Selecting the "SEND DUI Messages" may automatically notify any people via text that have been marked as DUI contacts in the contacts interface described below. Messages may be sent at regular intervals until recipient acknowledges receipt of the message.
- computing device 1500 may prompt the user adding or editing contact information.
- FIG. 5 illustrates an embodiment of a prompt 500 for enabling the user to add or edit more contact information.
- the add and edit contact menu may be comprised of, for example, a series of prompts 524 for adding contact information; a series of buttons for determining when the described contact should be contacted (e.g., during a DUI, Emergency, and/or Video capture], 526; a save button 530 enabling the user to add contacts from the address book, 528; and a button for saving information.
- computing device 1500 may show a menu for the user to add data pertaining to an accident.
- FIG. 6 illustrates a menu 600 for the user to add data pertaining to an accident consistent with embodiments of the present disclosure.
- This menu may be comprised of a series of prompts 632 for adding information and a next button 634.
- computing device 1500 may enable the user to navigate a series of interfaces for inputting the accident data.
- a check may appear next to the corresponding prompt in menu 600.
- FIG. 7 illustrates an embodiment for the location display 700 consistent with the present disclosure.
- Subtitle 735 may also be shown.
- a user may drop a pin 736 within a map associated with their location.
- the location may be automatically detected using the location detection components described above.
- the user may confirm the location information by selecting save button 530.
- FIG. 8 illustrates a My Vehicle interface 800 for adding photos consistent with embodiments of the disclosure.
- computing device 1500 may enable a camera on a smartphone for taking and saving photos. Further, computing device 1500 may display photos in thumbnail form.
- Subtitle 735 may also be shown. The user may confirm the photo data by selecting save button 530.
- computing device 1500 may enable the user to add information for one or more parties involved in the incident.
- FIG. 9 illustrates an other party input interface 900 for inputting information for another party involved in the incident consistent with embodiments of the disclosure.
- the menu for adding information for one or more parties in the incident may be comprised of photo button 838 and prompts 940.
- the user may confirm the other party data by selecting save button 530.
- computing device 1500 may enable the user to add information for one or more vehicles involved in the incident.
- FIG. 10 illustrates an other vehicle interface 1000 for inputting information for another vehicle involved in the incident consistent with embodiments of the disclosure.
- the menu for adding information for one or more parties in the incident may be comprised of prompts 1042 (e.g., make, model, year, license plate number and VIN number] and photo buttons 838.
- the user may confirm the other vehicle data by selecting save button 530.
- computing device 1500 may enable the user to add information for one or more vehicles involved in the incident, such as, for example, a police officer or firefighter.
- FIG. 11 illustrates a first responder interface 1100 for inputting information for one or more responders involved in the incident consistent with embodiments of the disclosure.
- the menu for adding information for one or more responders in the incident may be comprised of prompts 1144 (e.g., name, badge number, accident report/case number, phone number and police department name ⁇ .
- the user may confirm the other vehicle data by selecting save button 530.
- computing device 1500 may enable the user to add one or more photos pertaining to non-vehicle property damage.
- FIG. 12 illustrates a non-vehicle property damage interface 1200 for adding photos, via photo buttons 838, consistent with embodiments of the disclosure. The user may confirm the non- vehicle damage data by selecting save button 530.
- computing device 1500 may enable the user to add witness data.
- FIG. 13 illustrates a menu for witness data collection consistent with embodiments of the disclosure.
- the menu for witness data may be comprised of prompts 1346.
- Prompts 1346 may, for example, enable the user to add a video, add audio, playback audio, and add textual information received from the witness.
- the user may confirm the witness data by selecting save button 530.
- FIG. 14 illustrates an example of a ticket menu consistent with embodiments of the present disclosure.
- the menu may be comprised of one or more photo buttons 838, prompts for selecting the ticket type (e.g., DUI, traffic/parking, speeding], and a prompt for comments.
- a next button may not be activated until at least a photo of the ticket has been received.
- method 200A may proceed to stage 240 where computing device 1500 may receive submission data.
- the data may be sent to server 110 which may comprise a database for storage.
- server 110 may comprise a database for storage.
- method 200A may then end at stage 250.
- FIG. 2B is a flow chart setting forth the general stages involved in a method 200B consistent with an embodiment of the disclosure for providing an automobile incident networking platform 100.
- Method 200B may be implemented using a computing device 1500 as described in more detail below with respect to FIG. 15.
- computing device 1500 may be used to perform the various stages of method 200B.
- different operations may be performed by different networked elements in operative communication with computing device 1500.
- server 110 may be employed in the performance of some or all of the stages in method 200B.
- server 110 may be configured much like computing device 1500.
- Stages may be combined, separated, reordered, and various intermediary stages may exist. Accordingly, it should be understood that the various stages illustrated within the flow chart may be, in various embodiments, performed in arrangements that differ from the ones illustrated. Moreover, various stages may be added or removed from the flow charts without altering or deterring from the fundamental scope of the depicted methods and systems disclosed herein. Ways to implement the stages of method 200 will be described in greater detail below.
- Method 200B may begin at starting block 255 and proceed to stage 260 where computing device 1500 may compile a list of qualified service providers.
- relevant service providers may be determined, such as, for example, body shops, insurance companies and personal injury lawyers.
- These entities may be pre-registered as service providers associated with the platform.
- the pre-registration may include a vetting process to ensure quality control.
- These service providers may then be provided to the user, via platform 100.
- the service providers may include their information, any recommendations associated with the incident, and a quote for which the service provider is willing to resolve the incident or a portion thereof.
- computing device 1500 may receive a selection of at least one service provider. For example, if the user has indicated, through the platform, that he or she received a ticket for a DUI, computing device 200 may display available DUI attorneys. In addition, and as mentioned above, the user may receive further information pertaining to the relevant service providers, including description, ratings, potential fees, etc. Similarly, other service providers associated with the incident type may be listed to the user. The user may then select one or more of the listed service providers to engage in dialog with the service provider regarding the matter.
- stage 280 computing device 1500 may communicate submission data to one or more service providers.
- the user who received a ticket for a DUI may select from a list one or more DUI lawyers to whom the user would like to send the collected information.
- the platform may choose to redact certain data that may not be relevant to the service provider. For instance, in the event of an auto-accident, a body shop may not need to receive witness data or first responder data. Accordingly, platform 100 may be configured to send the data that is pertinent to the particular service provider, while redacting other unrelated data. In this way, a degree of user privacy may be provided.
- method 200B may proceed to stage 290, where computing device 1500 may facilitate interaction between the user and one or more service providers.
- the selected service providers may receive all of the relevant data captured by the user, such as, for example, the location, time and date, pictures, audio, video, witness information and the information of the police officer who was on the scene.
- the service providers may then follow up with the user, by, for example, sending price quotes or other relevant information.
- method 200B may end at 295.
- the automobile incident data networking platform 100 may be embodied as, for example, but not be limited to, a website, a web application, a desktop application, and a mobile application compatible with a computing device.
- the computing device may comprise, but not be limited to, a desktop computer, laptop, a tablet, or mobile telecommunications device.
- the automobile incident data networking platform 100 may be hosted on a centralized server, such as, for example, a cloud computing service.
- method 200 has been described to be performed by a computing device 1500, it should be understood that, in some embodiments, different operations may be performed by different networked elements in operative
- Embodiments of the present disclosure may comprise a system having a memory storage and a processing unit.
- the processing unit coupled to the memory storage, wherein the processing unit is configured to: receive a selection on an incident type; receive incident data; determine a plurality of service providers associated with handling the incident type; display the plurality of service providers for selection;
- FIG. 15 is a block diagram of a system including computing device 1500.
- the aforementioned memory storage and processing unit may be implemented in a computing device, such as computing device 1500 of FIG. 15. Any suitable combination of hardware, software, or firmware may be used to implement the memory storage and processing unit.
- the memory storage and processing unit may be implemented with computing device 1500 or any of other computing devices 1518, in combination with computing device 1500.
- the aforementioned system, device, and processors are examples and other systems, devices, and processors may comprise the aforementioned memory storage and processing unit, consistent with embodiments of the disclosure.
- a system consistent with an embodiment of the disclosure may include a computing device, such as computing device 1500.
- computing device 1500 may include at least one processing unit 1502 and a system memory 1504.
- system memory 1504 may comprise, but is not limited to, volatile (e.g., random access memory (RAM ⁇ , non-volatile (e.g., read-only memory (ROM ⁇ , flash memory, or any combination.
- System memory 1504 may include operating system 1505, one or more programming modules 1506, and may include a program data 1507. Operating system 1505, for example, may be suitable for controlling computing device 1500's operation.
- programming modules 1506 may include data capture, data storing and data transmission.
- embodiments of the disclosure may be practiced in conjunction with a graphics library, other operating systems, or any other application program and is not limited to any particular application or system. This basic configuration is illustrated in FIG. 15 by those components within a dashed line 1508.
- Computing device 1500 may have additional features or functionality.
- computing device 1500 may also include additional data storage devices (removable and/or non-removable ⁇ such as, for example, magnetic disks, optical disks, or tape.
- additional storage is illustrated in FIG. 15 by a removable storage 1509 and a non-removable storage 1510.
- Computer storage media may include volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information, such as computer readable instructions, data structures, program modules, or other data.
- System memory 1504, removable storage 1509, and non-removable storage 1510 are all computer storage media examples (i.e., memory storage. ⁇
- Computer storage media may include, but is not limited to, RAM, ROM, electrically erasable read-only memory (EEPROM], flash memory or other memory technology, CD-ROM, digital versatile disks (DVD] or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store information and which can be accessed by computing device 1500. Any such computer storage media may be part of device 1500.
- Computing device 1500 may also have input devicefs] 1512 such as a keyboard, a mouse, a pen, a sound input device, a touch input device, etc.
- Output devicefs] 1514 such as a display, speakers, a printer, etc. may also be included. The aforementioned devices are examples and others may be used.
- Computing device 1500 may also contain a communication connection 1516 that may allow device 1500 to communicate with other computing devices 1518, such as over a network in a distributed computing environment, for example, an intranet or the Internet.
- Communication connection 1516 is one example of communication media.
- Communication media may typically be embodied by computer readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave or other transport mechanism, and includes any information delivery media.
- modulated data signal may describe a signal that has one or more characteristics set or changed in such a manner as to encode information in the signal.
- communication media may include wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, radio frequency (RF], infrared, and other wireless media.
- RF radio frequency
- computer readable media may include both storage media and communication media.
- program modules 1506 may perform processes including, for example, one or more of methods 200A and 200B's stages as described above.
- processing unit 1502 may perform other processes.
- Other programming modules that may be used in accordance with embodiments of the present disclosure may include electronic mail and contacts applications, word processing applications, spreadsheet applications, database applications, slide presentation applications, drawing or computer-aided application programs, etc.
- program modules may include routines, programs, components, data structures, and other types of structures that may perform particular tasks or that may implement particular abstract data types.
- embodiments of the disclosure may be practiced with other computer system configurations, including hand-held devices, multiprocessor systems, microprocessor- based or programmable consumer electronics, minicomputers, mainframe computers, and the like.
- Embodiments of the disclosure may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing
- program modules may be located in both local and remote memory storage devices.
- embodiments of the disclosure may be practiced in an electrical circuit comprising discrete electronic elements, packaged or integrated electronic chips containing logic gates, a circuit utilizing a microprocessor, or on a single chip containing electronic elements or microprocessors.
- Embodiments of the disclosure may also be practiced using other technologies capable of performing logical operations such as, for example, AND, OR, and NOT, including but not limited to mechanical, optical, fluidic, and quantum technologies.
- embodiments of the disclosure may be practiced within a general purpose computer or in any other circuits or systems.
- Embodiments of the disclosure may be implemented as a computer process (method], a computing system, or as an article of manufacture, such as a computer program product or computer readable media.
- the computer program product may be a computer storage media readable by a computer system and encoding a computer program of instructions for executing a computer process.
- the computer program product may also be a propagated signal on a carrier readable by a computing system and encoding a computer program of instructions for executing a computer process.
- the present disclosure may be embodied in hardware and/or in software (including firmware, resident software, micro-code, etc. ⁇ .
- embodiments of the present disclosure may take the form of a computer program product on a computer-usable or computer-readable storage medium having computer- usable or computer-readable program code embodied in the medium for use by or in connection with an instruction execution system.
- a computer-usable or computer-readable medium may be any medium that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device.
- the computer-usable or computer-readable medium may be, for example but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, device, or propagation medium.
- the computer-readable medium may include the following: an electrical connection having one or more wires, a portable computer diskette, a random access memory (RAM], a read-only memory (ROM], an erasable programmable read-only memory (EPROM or Flash memory], an optical fiber, and a portable compact disc read-only memory (CD-ROM ⁇ .
- the computer-usable or computer-readable medium could even be paper or another suitable medium upon which the program is printed, as the program can be electronically captured, via, for instance, optical scanning of the paper or other medium, then compiled, interpreted, or otherwise processed in a suitable manner, if necessary, and then stored in a computer memory.
- Embodiments of the present disclosure are described above with reference to block diagrams and/or operational illustrations of methods, systems, and computer program products according to embodiments of the disclosure.
- the functions/acts noted in the blocks may occur out of the order as shown in any flowchart.
- two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality/acts involved.
Landscapes
- Business, Economics & Management (AREA)
- Engineering & Computer Science (AREA)
- Strategic Management (AREA)
- Accounting & Taxation (AREA)
- Development Economics (AREA)
- Finance (AREA)
- Economics (AREA)
- Game Theory and Decision Science (AREA)
- Entrepreneurship & Innovation (AREA)
- Marketing (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- User Interface Of Digital Computer (AREA)
Abstract
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US14/514,012 US20160104198A1 (en) | 2014-10-14 | 2014-10-14 | Automobile incident data networking platform |
| PCT/US2014/063497 WO2016060697A1 (fr) | 2014-10-14 | 2014-10-31 | Plate-forme de mise en réseau de données d'incident d'automobile |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| EP3207723A1 true EP3207723A1 (fr) | 2017-08-23 |
| EP3207723A4 EP3207723A4 (fr) | 2018-06-13 |
Family
ID=55655747
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| EP14904054.5A Withdrawn EP3207723A4 (fr) | 2014-10-14 | 2014-10-31 | Plate-forme de mise en réseau de données d'incident d'automobile |
Country Status (5)
| Country | Link |
|---|---|
| US (1) | US20160104198A1 (fr) |
| EP (1) | EP3207723A4 (fr) |
| AU (1) | AU2014409125A1 (fr) |
| CA (1) | CA2964335A1 (fr) |
| WO (1) | WO2016060697A1 (fr) |
Families Citing this family (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10643458B2 (en) | 2014-11-18 | 2020-05-05 | William Michael Smith | Emergency service provision with destination-specific information |
| US11216824B1 (en) * | 2015-02-26 | 2022-01-04 | Allstate Insurance Company | Role assignment for enhanced roadside assistance |
| US11836821B2 (en) * | 2017-05-17 | 2023-12-05 | Malik Azim | Communication system for motorists |
| US11699308B2 (en) | 2019-07-29 | 2023-07-11 | Toyota Motor North America, Inc. | Tracking of transport data |
| US11217041B2 (en) | 2019-07-29 | 2022-01-04 | Toyota Motor North America, Inc. | Tracking of transport data |
| US11500571B2 (en) | 2019-07-29 | 2022-11-15 | Toyota Motor North America, Inc. | Tracking of transport data |
| US20230377081A1 (en) * | 2020-07-20 | 2023-11-23 | Malik Azim | Novel communications system for motorists |
| CN114708542B (zh) * | 2022-06-06 | 2022-09-02 | 阿里巴巴达摩院(杭州)科技有限公司 | 图像处理方法、装置及计算机可读存储介质 |
Family Cites Families (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20020019741A1 (en) * | 2000-07-07 | 2002-02-14 | Heston Robert L. | Method and system for performing legal services over the internet |
| JP2007094935A (ja) * | 2005-09-30 | 2007-04-12 | Omron Corp | 情報処理装置および情報処理方法、情報処理システム、プログラム、並びに、記録媒体 |
| US8549028B1 (en) * | 2008-01-24 | 2013-10-01 | Case Global, Inc. | Incident tracking systems and methods |
| US9070243B1 (en) * | 2009-08-19 | 2015-06-30 | Allstate Insurance Company | Assistance on the go |
| US8493234B2 (en) * | 2009-12-07 | 2013-07-23 | At&T Mobility Ii Llc | Devices, systems and methods for detecting a traffic infraction |
| US20110239113A1 (en) * | 2010-03-25 | 2011-09-29 | Colin Hung | Systems and methods for redacting sensitive data entries |
| US20110320492A1 (en) * | 2010-06-24 | 2011-12-29 | DriveMeCrazy, Inc. | System and method for tracking vehicle operation through user-generated driving incident reports |
| US9147336B2 (en) * | 2012-02-29 | 2015-09-29 | Verizon Patent And Licensing Inc. | Method and system for generating emergency notifications based on aggregate event data |
| CA2812486A1 (fr) * | 2012-04-13 | 2013-10-13 | Trapeze Software Ulc | Systeme et procede permettant le deploiement configurable du contenu d'une agence de transit |
| US20140114691A1 (en) * | 2012-10-23 | 2014-04-24 | InnovaPad, LP | Methods and Systems for the Integrated Collection of Data for Use in Incident Reports and Insurance Claims and to Related Methods of Performing Emergency Responder Cost Recovery |
| US20150087279A1 (en) * | 2013-09-20 | 2015-03-26 | Better Mousetrap, LLC | Mobile accident processing system and method |
| US9877176B2 (en) * | 2013-12-18 | 2018-01-23 | Medlegal Network, Inc. | Methods and systems of managing accident communications over a network |
-
2014
- 2014-10-14 US US14/514,012 patent/US20160104198A1/en not_active Abandoned
- 2014-10-31 AU AU2014409125A patent/AU2014409125A1/en not_active Abandoned
- 2014-10-31 WO PCT/US2014/063497 patent/WO2016060697A1/fr not_active Ceased
- 2014-10-31 CA CA2964335A patent/CA2964335A1/fr not_active Abandoned
- 2014-10-31 EP EP14904054.5A patent/EP3207723A4/fr not_active Withdrawn
Also Published As
| Publication number | Publication date |
|---|---|
| CA2964335A1 (fr) | 2016-04-21 |
| AU2014409125A1 (en) | 2017-05-18 |
| WO2016060697A1 (fr) | 2016-04-21 |
| EP3207723A4 (fr) | 2018-06-13 |
| US20160104198A1 (en) | 2016-04-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20160104198A1 (en) | Automobile incident data networking platform | |
| US20230394585A1 (en) | Automatic Claim Generation | |
| US11763388B1 (en) | Visual reconstruction of traffic incident based on sensor device data | |
| US9747655B2 (en) | Emergency service provision with destination-specific information | |
| US9866673B2 (en) | Methods and systems of managing accident communications over a network | |
| US8948732B1 (en) | System and method for responding to service requests and facilitating communication between relevant parties | |
| Bloom et al. | Self-driving cars and data collection: Privacy perceptions of networked autonomous vehicles | |
| US10922776B2 (en) | Platform for real-time views on consolidated data | |
| US12033217B2 (en) | Electronic exchange of insurance information | |
| US20120143630A1 (en) | Third party verification of insurable incident claim submission | |
| US20100039254A1 (en) | Transportation activity information tools and techniques for mobile devices | |
| US10643458B2 (en) | Emergency service provision with destination-specific information | |
| US20240346614A1 (en) | Systems, apparatus, and methods for integrating and streamlining the process of issuing citations while simultaneously enhancing security of law enforcement officers (leos) | |
| CN114047854B (zh) | 用于文档处理的信息交互方法、装置、电子设备和存储介质 | |
| WO2017139229A1 (fr) | Procédés et systèmes de gestion de communications d'accidents sur un réseau | |
| KR102013150B1 (ko) | 재난 현장 정보 공유 장치 및 방법 | |
| JP2020064451A (ja) | 情報処理装置、情報処理システム、及び、情報処理方法 | |
| US10602338B2 (en) | Emergency authorization to access data on proximate computing devices | |
| US20210073860A1 (en) | Methods, systems, apparatuses, and devices for facilitating presentation of promotional content to a user of a ride-sharing service | |
| US20160277892A1 (en) | Proximity based messaging platform | |
| US20170301051A1 (en) | Media sharing application with geospatial tagging for crowdsourcing of an event across a community of users | |
| US20170024684A1 (en) | Systems and Methods for Worksite Safety Management and Tracking | |
| Carlton | Data privacy in connected vehicle infotainment systems: A comprehensive framework for rental vehicles | |
| US12211054B2 (en) | System and method to support human-machine interactions for public safety annotations | |
| US10636096B1 (en) | Dynamic generation of an electronic identification card for display by an electronic device based on real-time policy information |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
| 17P | Request for examination filed |
Effective date: 20170426 |
|
| AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
| AX | Request for extension of the european patent |
Extension state: BA ME |
|
| RIN1 | Information on inventor provided before grant (corrected) |
Inventor name: LUBY, ZEUS CORY Inventor name: SMITH, WILLIAM MICHAEL |
|
| RIN1 | Information on inventor provided before grant (corrected) |
Inventor name: SMITH, WILLIAM MICHAEL Inventor name: LUBY, ZEUS CORY |
|
| RIN1 | Information on inventor provided before grant (corrected) |
Inventor name: LUBY, ZEUS CORY Inventor name: SMITH, WILLIAM MICHAEL |
|
| DAX | Request for extension of the european patent (deleted) | ||
| A4 | Supplementary search report drawn up and despatched |
Effective date: 20180514 |
|
| RIC1 | Information provided on ipc code assigned before grant |
Ipc: G06Q 30/02 20120101AFI20180508BHEP |
|
| STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN |
|
| 18D | Application deemed to be withdrawn |
Effective date: 20181212 |