WO2018188503A1 - 车辆定损配件匹配方法和系统 - Google Patents

车辆定损配件匹配方法和系统 Download PDF

Info

Publication number
WO2018188503A1
WO2018188503A1 PCT/CN2018/081795 CN2018081795W WO2018188503A1 WO 2018188503 A1 WO2018188503 A1 WO 2018188503A1 CN 2018081795 W CN2018081795 W CN 2018081795W WO 2018188503 A1 WO2018188503 A1 WO 2018188503A1
Authority
WO
WIPO (PCT)
Prior art keywords
accessory
vehicle
damaged
fixed
name
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.)
Ceased
Application number
PCT/CN2018/081795
Other languages
English (en)
French (fr)
Inventor
洪旭栓
林佩珊
范永安
饶怡骏
马显芳
刘泽圆
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Ping An Technology Shenzhen Co Ltd
Original Assignee
Ping An Technology Shenzhen Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Ping An Technology Shenzhen Co Ltd filed Critical Ping An Technology Shenzhen Co Ltd
Publication of WO2018188503A1 publication Critical patent/WO2018188503A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/50—Information retrieval; Database structures therefor; File system structures therefor of still image data
    • G06F16/58—Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
    • G06F16/583—Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually using metadata automatically derived from the content
    • G06F16/5838—Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually using metadata automatically derived from the content using colour
    • 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
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/08—Insurance
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06V—IMAGE OR VIDEO RECOGNITION OR UNDERSTANDING
    • G06V10/00—Arrangements for image or video recognition or understanding
    • G06V10/40—Extraction of image or video features
    • G06V10/44—Local feature extraction by analysis of parts of the pattern, e.g. by detecting edges, contours, loops, corners, strokes or intersections; Connectivity analysis, e.g. of connected components
    • G06V10/443—Local feature extraction by analysis of parts of the pattern, e.g. by detecting edges, contours, loops, corners, strokes or intersections; Connectivity analysis, e.g. of connected components by matching or filtering
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06V—IMAGE OR VIDEO RECOGNITION OR UNDERSTANDING
    • G06V20/00—Scenes; Scene-specific elements
    • G06V20/50—Context or environment of the image
    • G06V20/56—Context or environment of the image exterior to a vehicle by using sensors mounted on the vehicle
    • G06V20/58—Recognition of moving objects or obstacles, e.g. vehicles or pedestrians; Recognition of traffic objects, e.g. traffic signs, traffic lights or roads
    • G06V20/584—Recognition of moving objects or obstacles, e.g. vehicles or pedestrians; Recognition of traffic objects, e.g. traffic signs, traffic lights or roads of vehicle lights or traffic lights

Definitions

  • the present application relates to the field of computer technology, and in particular, to a method and system for matching a vehicle damage component.
  • a method and system for matching a vehicle's lossy accessory is provided.
  • a method for matching a vehicle damage component includes:
  • the car insurance report information includes a license plate number of the accident vehicle
  • a vehicle fixed damage accessory matching system includes:
  • a client terminal for uploading auto insurance report information, where the auto insurance report information includes a license plate number of the accident vehicle;
  • a server configured to receive the vehicle insurance report information, generate a vehicle risk determination task according to the vehicle insurance report information, and send the vehicle insurance damage loss task to the fixed loss terminal;
  • a fixed loss terminal configured to receive the fixed loss task, input a frame number and a fixed damage item according to the license plate number when performing the fixed loss task, and generate an accessory matching request by using the frame number and the fixed damage item Uploading the accessory matching request to the server;
  • the server is further configured to receive the accessory matching request, and match the accessory identifier of the accident vehicle according to the frame number and the fixed damage item to obtain the damaged accessory identifier of the accident vehicle;
  • the fixed loss terminal is further configured to input the damaged accessory identifier corresponding to the fixed loss item.
  • a vehicle fixed damage accessory matching system includes:
  • a client terminal for uploading auto insurance report information, where the auto insurance report information includes at least a license plate number of the accident vehicle, a frame number, and an accident vehicle picture;
  • a server configured to receive the vehicle insurance report information, compare the vehicle insurance report information with a preset rule, and if the vehicle accident is determined to be a simple accident after the comparison, the image of the accident vehicle is identified according to the The name of the damaged component is matched according to the frame number and the damaged accessory name, and the accessory identification of the accident vehicle is obtained, and the damaged vehicle accessory identification is obtained according to the vehicle insurance report information, the damaged accessory name and the damaged accessory identification.
  • the vehicle is subjected to a fixed loss.
  • a server comprising a memory and one or more processors, the memory storing computer readable instructions, the computer readable instructions being executed by the processor, causing the one or more processors to perform the following step:
  • the auto insurance report information includes the license plate number of the accident vehicle
  • One or more non-transitory computer readable storage mediums storing computer readable instructions, when executed by one or more processors, cause one or more processors to perform the steps of:
  • the car insurance report information includes a license plate number of the accident vehicle
  • FIG. 1 is an application environment diagram of a method for matching a vehicle damage component according to one or more embodiments
  • FIG. 2 is a flow chart of a method for matching a vehicle's fixed damage accessory in accordance with one or more embodiments
  • FIG. 3 is a block diagram of a vehicle fixed-loss accessory matching system in accordance with one or more embodiments
  • FIG. 4 is a block diagram of a vehicle fixed damage accessory matching system in still another embodiment
  • FIG. 5 is a block diagram of a server in accordance with one or more embodiments.
  • the method for matching the vehicle damage component provided in the embodiment of the present application can be applied to the application environment as shown in FIG. 1 .
  • the client terminal 102 is connected to the server 104 via a network
  • the fixed-loss terminal 106 is connected to the server 104 via a network.
  • the customer can use the client terminal 102 to report the vehicle insurance to the server 104.
  • the auto insurance report information includes the auto insurance report information including the license plate number of the accident vehicle and the place of the accident.
  • the server 104 generates a vehicle risk determination task using the report information, and transmits the vehicle risk determination task to the fixed loss terminal 106.
  • the fixed-loss personnel inspect the damage to the accident vehicle at the place of the accident, and input the damage item and the frame number through the fixed-loss terminal 106.
  • the damage item includes the name of the damaged part.
  • the fixed loss terminal 106 generates an accessory matching request corresponding to the item loss item using the frame number and the damaged accessory name, and transmits the accessory matching request to the server 104.
  • the server 104 acquires a plurality of accessory names and accessory models corresponding to the accident vehicle according to the frame number, and then searches for a plurality of accessory names and accessory models corresponding to the accident vehicle according to the damaged accessory name, thereby obtaining an accident vehicle. Damage to the accessory identification.
  • Server 104 returns the damaged accessory identification to fixed loss terminal 106.
  • the fixed loss terminal 106 inputs the damaged accessory name and the damaged accessory identification. This avoids the problem of incorrect selection of the components when the vehicle is damaged due to the different configuration of the vehicle.
  • a method for matching a vehicle damage component is provided.
  • the method is applied to the server in FIG. 1 as an example, and specifically includes the following steps:
  • Step 202 Receive car insurance report information uploaded by the client terminal; the car insurance report information includes a license plate number of the accident vehicle.
  • Step 204 Generate a vehicle risk determination task according to the vehicle insurance report information, and send the vehicle risk determination loss task to the fixed loss terminal.
  • the customer can use the client terminal to report the vehicle to the server.
  • the auto insurance report information includes the basic information of the vehicle and the place of the insurance.
  • the basic vehicle information includes the license plate number of the accident vehicle.
  • the server receives the auto insurance report information, generates the auto insurance fixed loss task by using the auto insurance report information, and sends the auto insurance fixed loss task to the fixed loss terminal.
  • the license damage number carries the license plate number and the place of the accident.
  • Step 206 Receive an accessory matching request uploaded by the fixed loss terminal when performing the loss determining task, where the accessory matching request includes a frame number and a fixed loss item.
  • Step 208 Matching the accessory identification of the accident vehicle according to the frame number and the fixed damage item, and obtaining the damaged accessory identification of the accident vehicle.
  • Step 210 Return the damaged accessory identification to the fixed loss terminal, so that the fixed loss terminal inputs the damaged accessory identifier corresponding to the fixed loss item.
  • the fixed loss terminal After receiving the loss loss task, the fixed loss terminal can capture the current location information through GPS positioning and upload the location information to the server. The fixed-loss terminal can upload its location information to the server in real time on the way to the place of the insurance.
  • the fixed loss terminal refuses the operation of inputting the loss information by the fixed loss person before the fixed damage person arrives at the place of the risk.
  • the location information of the fixed loss terminal includes longitude and latitude.
  • the fixed loss terminal obtains the longitude and latitude corresponding to the place of the accident.
  • the fixed loss terminal can determine that the location information of the terminal is consistent with the location of the insurance, indicating that the determined damage person arrives at the place of the risk.
  • the fixed-loss personnel inspect the accident vehicle at the place of the accident, and input the loss information through the fixed-loss terminal.
  • the loss information includes: basic information and fixed loss items.
  • the basic information includes: frame number, insurance and accident liability.
  • the damage items include: damaged parts name and working hours. Among them, the damaged accessory name has a corresponding damaged accessory identification.
  • the damaged accessory identification can be a damaged accessory model or the like.
  • the accessory identification corresponding to the accessory name of the vehicle with the different configuration of the same model may be different.
  • the fixed loss terminal when the damaged accessory name is input in the fixed loss terminal, the fixed loss terminal generates the accessory matching request by using the frame number and the damaged accessory name, and matches the accessory with the accessory. Upload to the server.
  • the frame number also known as the vehicle identification code, is a set of codes that the car manufacturer assigns to each car. Each car has a unique frame number. The frame number includes the model of the vehicle.
  • the server receives the accessory matching request, and matches the accessory identifier of the accident vehicle according to the frame number and the fixed damage accessory name carried in the accessory matching request. This makes it possible to accurately match the damaged accessory identification corresponding to the name of the damaged component.
  • the step of matching the accessory identification of the accident vehicle according to the frame number and the damage item comprises: obtaining a plurality of accessory names and accessory models corresponding to the accident vehicle according to the frame number; according to the damaged accessory name The plurality of accessory names and accessory models corresponding to the accident vehicle are searched to obtain the damaged component identification of the accident vehicle.
  • a database is deployed on the server, and the model, the frame number, the accessory identification, and the accessory picture are stored in the database.
  • the server can retrieve all the accessory names and accessory models corresponding to the accident vehicle in the database according to the frame number. To further improve the matching accuracy, the server can also retrieve the damaged accessory identification from all the accessory names corresponding to the accident vehicle according to the damaged accessory name. .
  • the server receives the accessory matching request sent by multiple fixed loss terminals, multiple threads can be called to perform concurrent operations, thereby effectively improving the matching efficiency of the components.
  • the fixed loss terminal may generate the accessory matching request corresponding to the fixed damage item by using the frame number and the damaged accessory name each time the damaged accessory name is input.
  • the server returns the corresponding damaged accessory identification one by one according to the accessory matching request.
  • the fixed loss terminal can also input the name of a plurality of damaged accessories, and then generate an accessory matching request by using the frame number and the plurality of damaged accessory names.
  • the server can batch process according to the accessory matching request and return multiple damaged accessory identifiers.
  • the server returns the damaged accessory identification to the fixed loss terminal.
  • the fixed loss terminal receives the damaged accessory identification, the fixed damage personnel selects the damaged accessory identification corresponding to the damaged accessory name, and inputs the fixed damage accessory identifier corresponding to the fixed damage item to the fixed loss terminal.
  • the client terminal may report the vehicle insurance to the server.
  • the server generates a vehicle risk determination task according to the vehicle insurance report information, and the fixed loss personnel can upload the accessory matching request to the server when performing the vehicle insurance fixed loss task.
  • the server matches the accessory identification of the accident vehicle according to the frame number and the damage item carried in the accessory matching request, and obtains the corresponding damaged accessory identification. Since the frame number of each car is unique, the frame number includes the model, etc., so the server can accurately match the damaged component identification of the accident vehicle according to the frame number and the damage item. Therefore, it is possible to effectively avoid the problem that the component selection is incorrect when the vehicle is damaged due to the different configuration of the vehicle.
  • the fixed damage item includes a picture of the accident vehicle; the name of the damaged accessory can be obtained by: identifying the image of the accident vehicle, identifying the damaged part of the vehicle; analyzing the damaged part of the vehicle, and obtaining damage The name of the accessory.
  • the loss-receiving person can also take a picture of the accident vehicle through the fixed-loss terminal.
  • the fixed loss terminal uploads the accident vehicle image to the server.
  • the server receives the picture of the accident vehicle, identifies the image of the accident vehicle, identifies the damaged part of the vehicle, and locates the damaged part of the vehicle.
  • a large number of fixed loss pictures are stored in the database deployed on the server, and the damaged parts of the vehicle are located in the fixed loss picture, and the corresponding classification and accessory names are configured.
  • the server compares the damaged part of the located vehicle in the accident vehicle picture with the fixed loss picture in the database to identify the damaged accessory name.
  • the server returns the identified damaged accessory name to the fixed loss terminal, thereby eliminating the operation of manually inputting the damaged accessory name by the fixed loss personnel, which provides convenience for the fixed damage personnel.
  • the accessory matching request may be generated by using the frame number and the damaged accessory name according to the manner provided in the above embodiment, and the accessory matching request is uploaded to the server.
  • the server matches the accessory identification of the accident vehicle according to the frame number and the damaged accessory name, and obtains the damaged accessory identification of the accident vehicle.
  • the method further includes: acquiring a plurality of accessory identifiers of the accident vehicle according to the frame number; using the accessory identifier to establish an index, and querying the fixed damage price corresponding to the damaged accessory identifier according to the index; The accessory ID is returned to the fixed loss terminal.
  • the database in addition to storing the model, the frame number, the accessory identification, and the accessory picture, the database is deployed on the server, and the accessory price is also stored.
  • the server can use the multiple accessory identifiers corresponding to the model to establish an index. After the server matches the damaged accessory identification according to the frame number and the damaged accessory name, the index can also be used to query the fixed damage price corresponding to the damaged accessory identification.
  • the server returns the fixed loss price corresponding to the damaged accessory identification to the fixed loss terminal, so that the fixed loss terminal can further improve the loss information. Therefore, it is possible to prevent the fixed loss personnel from manually inquiring the fixed damage price corresponding to each damaged accessory, which provides convenience for the fixed loss personnel.
  • the server needs to query the fixed loss price corresponding to the plurality of damaged accessory identifiers at the same time, multiple threads may be called to perform concurrent query, thereby effectively improving the query efficiency of the fixed loss price corresponding to the plurality of damaged accessory identifiers.
  • steps in the flowchart of FIG. 2 are sequentially displayed as indicated by the arrows, these steps are not necessarily performed in the order indicated by the arrows. Except as explicitly stated herein, the execution of these steps is not strictly limited, and the steps may be performed in other orders. Moreover, at least some of the steps in FIG. 2 may include a plurality of sub-steps or stages, which are not necessarily performed at the same time, but may be executed at different times, the execution of these sub-steps or stages The order is also not necessarily sequential, but may be performed alternately or alternately with other steps or at least a portion of the sub-steps or stages of the other steps.
  • a vehicle loss component matching system including: a client terminal 302, a server 304, and a loss-making terminal 306, wherein:
  • the client terminal 302 is configured to upload auto insurance report information, and the auto insurance report information includes a license plate number of the accident vehicle.
  • the server 304 is configured to receive the vehicle insurance report information, generate a vehicle risk determination task according to the vehicle insurance report information, and send the vehicle risk determination loss task to the fixed loss terminal.
  • the fixed loss terminal 306 is configured to receive the fixed loss task, input the frame number and the fixed damage item according to the license plate number when performing the fixed loss task, generate the accessory matching request by using the frame number and the fixed damage item, and upload the accessory matching request to the server. .
  • the server 304 is further configured to receive an accessory matching request, and match the accessory identifier of the accident vehicle according to the frame number and the fixed damage item to obtain the damaged accessory identifier of the accident vehicle;
  • the fixed loss terminal 306 is also used to input the damaged accessory identification corresponding to the fixed loss item.
  • the customer can use the client terminal 302 to report the vehicle insurance to the server 304.
  • the auto insurance report information includes the basic information of the vehicle and the place of the insurance.
  • the basic vehicle information includes the license plate number of the accident vehicle.
  • the server 304 receives the vehicle insurance report information, generates the vehicle risk determination task by using the vehicle insurance report information, and sends the vehicle risk determination task to the fixed loss terminal 306.
  • the license damage number carries the license plate number and the place of the accident.
  • the fixed-loss personnel inspect the accident vehicle at the place of the accident, and input the loss-reduction information through the fixed-loss terminal 306.
  • the loss information includes: basic information and fixed loss items.
  • the basic information includes: frame number, insurance and accident liability.
  • the damage items include: damaged parts name and working hours. Among them, the damaged accessory name has a corresponding accessory identification.
  • the accessory identification corresponding to the accessory name of the vehicle with the different configuration of the same model may be different.
  • the fixed loss terminal when the damaged accessory name is input in the fixed loss terminal, the fixed loss terminal generates the accessory matching request by using the frame number and the damaged accessory name, and matches the accessory with the accessory. Upload to the server.
  • the frame number includes the model of the vehicle.
  • the server receives the accessory matching request, and matches the accessory identifier of the accident vehicle according to the frame number and the fixed damage accessory name carried in the accessory matching request. This makes it possible to accurately match the damaged accessory identification corresponding to the name of the damaged component.
  • the loss item may be manually entered by the loss user to the fixed loss terminal 306.
  • the server 304 is further configured to acquire the accessory name and the accessory model corresponding to the accident vehicle according to the frame number; perform the search according to the damaged accessory name in the accessory name and the accessory model corresponding to the accident vehicle, and obtain the damaged accessory identifier of the accident vehicle.
  • the damage item may include an accident vehicle picture and a damaged accessory name; the loss terminal 306 uploads the accident vehicle picture to the server 304.
  • the server 304 is further configured to identify the image of the accident vehicle, identify the damaged part of the vehicle, and analyze the damaged part of the vehicle to obtain the name of the damaged accessory.
  • the server returns the identified damaged accessory name to the fixed loss terminal, thereby eliminating the operation of manually inputting the damaged accessory name by the fixed loss personnel, which provides convenience for the fixed damage personnel.
  • the accessory matching request may be generated by using the frame number and the damaged accessory name according to the manner provided in the above embodiment, and the accessory matching request is uploaded to the server.
  • the server matches the accessory identification of the accident vehicle according to the frame number and the damaged accessory name, and obtains the damaged accessory identification of the accident vehicle.
  • the client terminal can report the vehicle to the server.
  • the server generates a vehicle risk determination task according to the vehicle insurance report information, and the fixed loss personnel can upload the accessory matching request to the server when performing the vehicle insurance fixed loss task.
  • the server matches the accessory identification of the accident vehicle according to the frame number and the damage item carried in the accessory matching request, and obtains the corresponding damaged accessory identification. Since the frame number of each car is unique, the frame number includes the model, etc., so the server can accurately match the damaged component identification of the accident vehicle according to the frame number and the damage item. Therefore, it is possible to effectively avoid the problem that the component selection is incorrect when the vehicle is damaged due to the different configuration of the vehicle.
  • the damage item includes a damaged accessory name
  • the damage terminal 306 is further configured to perform matching verification on the input damaged accessory name, and if the verification fails, generate a prompt message and refuse to accept the next message. Item operation.
  • the loss-receiving personnel can input the damaged accessory name one by one in the fixed-loss item.
  • the damage terminal 306 will perform a match check on the damaged accessory name. Specifically, if the current damage item is an assembly accessory or an inclusive accessory, the next damaged component name entered is an accessory accessory of the assembly accessory or an accessory accessory containing the accessory, or the next item entered is damaged. If the accessory name is the total accessory of the assembly accessory or the total accessory containing the accessory, the verification fails.
  • the verification fails; if input If the name of the next damaged accessory is the same as the name of the previous damaged accessory, the verification fails.
  • a vehicle loss component matching system comprising: a client terminal 402 and a server 404, wherein:
  • the client terminal 402 is configured to upload car insurance report information, and the car insurance report information includes at least the license plate number of the accident vehicle, the frame number, and the accident vehicle picture.
  • the server 404 is configured to receive the vehicle insurance report information, compare the vehicle insurance report information with a preset rule, and if the vehicle accident is determined to be a simple accident after the comparison, the damaged vehicle image is identified according to the image of the damaged vehicle, according to the name of the damaged component.
  • the frame number and the damaged component name are matched to the accessory identification of the accident vehicle, and the damaged vehicle accessory identification is obtained, and the accident vehicle is determined according to the vehicle insurance report information, the damaged accessory name and the damaged accessory identification.
  • the customer can use the client terminal 402 to report the vehicle insurance to the server 404.
  • the information on the auto insurance report includes the basic information of the vehicle, the picture of the accident vehicle, the cause of the accident, the place of the accident, whether it is reported on the spot, and whether it is out of danger.
  • the basic information of the vehicle includes the license plate number and the frame number of the accident vehicle.
  • the server 404 compares the vehicle insurance report information with the preset rule to determine whether the vehicle accident is a simple accident.
  • the preset rules include: on-site reporting, non-off-site insurance, and the location of the insurance does not include preset keywords.
  • the default rules are as shown in Table 1:
  • the server 404 After the comparison, it is determined that the vehicle accident is a simple accident, and the server 404 records the vehicle insurance report as a simple accident. For a simple accident, the server 404 can no longer generate a car insurance damage task, and no longer assigns a loss to the person to determine the loss.
  • the server 404 can identify the damaged vehicle picture according to the image of the accident vehicle in the manner provided in the above embodiment. Then, the accessory identification of the accident vehicle is matched according to the frame number and the damaged accessory name, and the damaged vehicle accessory identification of the accident vehicle is obtained.
  • the server 404 uses the vehicle insurance report information, the damaged accessory name, and the damaged accessory identification to damage the accident vehicle.
  • the server 404 is further configured to acquire a plurality of accessory identifiers of the accident vehicle according to the frame number; use the accessory identifier to establish an index, and query the fixed damage price corresponding to the damaged accessory identifier according to the index.
  • the client terminal reports the vehicle insurance to the server.
  • the server compares the vehicle insurance report information with the preset rule. If it is determined to be a simple accident, it identifies the accident vehicle image carried in the vehicle insurance report information, and obtains the name of the damaged accessory. Then, according to the frame number and the damaged accessory name carried in the vehicle type report information, the accessory identification of the accident vehicle is matched, and the damaged vehicle accessory identification is obtained. Since the frame number of each automobile is unique, the frame number is included. The model and other content, so the server can accurately match the damaged parts identification of the accident vehicle according to the frame number and the damage item. Therefore, it is possible to effectively avoid the problem that the component selection is incorrect when the vehicle is damaged due to the different configuration of the vehicle.
  • the server damages the accident vehicle based on the vehicle insurance report information, the damaged accessory name, and the damaged accessory identification. In this process, it is not necessary to send a fixed loss person to make a loss, which effectively improves the loss efficiency.
  • a server is provided, as shown in FIG. 5, which includes a processor coupled via a system bus, internal memory, a non-volatile storage medium, and a network interface.
  • the processor is used to provide calculation and control capabilities.
  • the internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage medium.
  • An operating system and computer readable instructions are stored in the non-volatile storage medium.
  • the non-volatile storage medium can be a non-transitory computer readable storage medium.
  • the processor can be caused to perform a vehicle damage accessory matching method.
  • the network interface is used to communicate with external client terminals or fixed loss terminals via a network connection.
  • the server can be implemented as a standalone server or a server cluster consisting of multiple servers. It will be understood by those skilled in the art that the structure shown in FIG. 5 is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the server to which the solution of the present application is applied.
  • the specific server may include More or fewer components are shown in the figures, or some components are combined, or have different component arrangements.
  • a server comprising a memory and one or more processors having stored therein computer readable instructions that, when executed by a processor, cause one or more processors to perform the steps of the various method implementations described above.
  • One or more non-volatile storage media storing computer readable instructions, when executed by one or more processors, cause one or more processors to perform the steps in the various method implementations described above.
  • Non-volatile memory can include read only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory.
  • Volatile memory can include random access memory (RAM) or external cache memory.
  • RAM is available in a variety of formats, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronization chain.
  • SRAM static RAM
  • DRAM dynamic RAM
  • SDRAM synchronous DRAM
  • DDRSDRAM double data rate SDRAM
  • ESDRAM enhanced SDRAM
  • Synchlink DRAM SLDRAM
  • Memory Bus Radbus
  • RDRAM Direct RAM
  • DRAM Direct Memory Bus Dynamic RAM
  • RDRAM Memory Bus Dynamic RAM

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • Business, Economics & Management (AREA)
  • Library & Information Science (AREA)
  • Multimedia (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Vision & Pattern Recognition (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Strategic Management (AREA)
  • Technology Law (AREA)
  • General Business, Economics & Management (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

本申请涉及一种车辆定损配件匹配方法，包括：接收客户终端上传的车险报案信息；所述车险报案信息包括事故车辆的车牌号；根据所述车险报案信息生成车险定损任务，将所述车险定损任务发送至定损终端；接收定损终端在执行所述定损任务时上传的配件匹配请求，所述配件匹配请求中包括车架号和定损项目；根据所述车架号和定损项目对事故车辆的配件标识进行匹配，得到事故车辆的受损配件标识；将所述受损配件标识返回至定损终端，以使得所述定损终端对应定损项目输入所述受损配件标识。

Description

车辆定损配件匹配方法和系统
本申请要求于2017年4月11日提交中国专利局，申请号为2017102340618，申请名称为“车辆定损配件匹配方法和系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及计算机技术领域，特别是涉及一种车辆定损配件匹配方法和系统。
背景技术
随着汽车的普及，车险也逐渐融入到人们的生活中。当被保险的车辆发生交通事故时，保险公司会派出定损员对车辆的损失部位和程度进行定损。在进行定损时，定损员通常是根据车系来选择需要维修或更换的配件。同一车型一般都包括多种不同的配置，例如，低配、标配和高配等，而且不同配置的车辆配件是不同的。在传统的方式中，车辆定损时只能根据车型来选择配件型号，因此很难避免配件选择错误。
发明内容
根据本申请公开的各种实施例，提供一种车辆定损配件匹配方法和系统。
一种车辆定损配件匹配方法，包括：
接收客户终端上传的车险报案信息；所述车险报案信息包括事故车辆的车牌号；
根据所述车险报案信息生成车险定损任务，将所述车险定损任务发送至定损终端；
接收定损终端在执行所述定损任务时上传的配件匹配请求，所述配件匹配请求中包括车架号和定损项目；
根据所述车架号和定损项目对事故车辆的配件标识进行匹配，得到事故车辆的受损配件标识；及
将所述受损配件标识返回至定损终端，以使得所述定损终端对应定损项目输入所述受损配件标识。
一种车辆定损配件匹配系统，包括：
客户终端，用于上传车险报案信息，所述车险报案信息包括事故车辆的车牌号；
服务器，用于接收所述车险报案信息，根据所述车险报案信息生成车险定损任务，将所述车险定损任务发送至定损终端；
定损终端，用于接收所述定损任务，在执行所述定损任务时根据所述车牌号输入车架号和定损项目，利用所述车架号和定损项目生成配件匹配请求并将所述配件匹配请求上传至服务器；
所述服务器还用于接收所述配件匹配请求，根据所述车架号和定损项目对事故车辆的配件标识进行匹配，得到事故车辆的受损配件标识；及
所述定损终端还用于对应定损项目输入所述受损配件标识。
一种车辆定损配件匹配系统，包括：
客户终端，用于上传车险报案信息，所述车险报案信息至少包括事故车辆的车牌号、车架号和事故车辆图片；及
服务器，用于接收所述车险报案信息，将所述车险报案信息与预设规则进行比对，若经过比对后确定车辆事故为简单事故，则根据对所述事故车辆图片进行识别，得到受损配件名称，根据所述车架号和受损配件名称对事故车辆的配件标识进行匹配，得到事故车辆受损配件标识，根据所述车险报案信息、受损配件名称和受损配件标识对事故车辆进行定损。
一种服务器，包括存储器和一个或多个处理器，所述存储器中储存有计算机可读指令，所述计算机可读指令被所述处理器执行时，使得所述一个或多个处理器执行以下步骤：
接收客户终端上传的车险报案信息；所述车险报案信息包括事故车辆的 车牌号；
根据所述车险报案信息生成车险定损任务，将所述车险定损任务发送至定损终端；
接收定损终端在执行所述定损任务时上传的配件匹配请求，所述配件匹配请求中包括车架号和定损项目；
根据所述车架号和定损项目对事故车辆的配件标识进行匹配，得到事故车辆的受损配件标识；及
将所述受损配件标识返回至定损终端，以使得所述定损终端对应定损项目输入所述受损配件标识。
一个或多个存储有计算机可读指令的非易失性计算机可读存储介质，计算机可读指令被一个或多个处理器执行时，使得一个或多个处理器执行以下步骤：
接收客户终端上传的车险报案信息；所述车险报案信息包括事故车辆的车牌号；
根据所述车险报案信息生成车险定损任务，将所述车险定损任务发送至定损终端；
接收定损终端在执行所述定损任务时上传的配件匹配请求，所述配件匹配请求中包括车架号和定损项目；
根据所述车架号和定损项目对事故车辆的配件标识进行匹配，得到事故车辆的受损配件标识；及
将所述受损配件标识返回至定损终端，以使得所述定损终端对应定损项目输入所述受损配件标识。
本申请的一个或多个实施例的细节在下面的附图和描述中提出。本申请的其它特征和优点将从说明书、附图以及权利要求书变得明显。
附图说明
为了更清楚地说明本申请实施例中的技术方案，下面将对实施例中所需 要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其它的附图。
图1为根据一个或多个实施例中的车辆定损配件匹配方法应用环境图；
图2为根据一个或多个实施例中车辆定损配件匹配方法的流程图；
图3为根据一个或多个实施例中车辆定损配件匹配系统的框图；
图4为又一个实施例中车辆定损配件匹配系统的框图；
图5为根据一个或多个实施例中服务器的框图。
具体实施方式
为了使本申请的目的、技术方案及优点更加清楚明白，以下结合附图及实施例，对本申请进行进一步详细说明。应当理解，此处描述的具体实施例仅仅用以解释本申请，并不用于限定本申请。
本申请实施例中所提供的车辆定损配件匹配方法，可以应用于如图1所示的应用环境中。客户终端102通过网络与服务器104连接，定损终端106通过网络与服务器104连接。当参保车辆发生事故时，客户可以利用客户终端102向服务器104进行车险报案。车险报案信息包括车险报案信息包括事故车辆的车牌号和出险地点等。服务器104利用报案信息生成车险定损任务，并且将车险定损任务发送至定损终端106。定损人员在出险地点对事故车辆进行查勘定损，通过定损终端106输入定损项目和车架号。其中，定损项目包括受损配件名称。定损终端106利用车架号和受损配件名称生成项定损项目对应的配件匹配请求，并且将配件匹配请求发送至服务器104。服务器104根据车架号获取事故车辆对应的多个配件名称和配件型号，继而根据所述受损配件名称在所述事故车辆对应的多个配件名称和配件型号中进行检索，得到事故车辆的受损配件标识。服务器104将受损配件标识返回至定损终端106。定损终端106将受损配件名称与受损配件标识进行对应输入。由此避免 了因车型对应的配置不同而导致车辆定损时配件选择错误的问题。
在一个实施例中，如图2所示，提供了一种车辆定损配件匹配方法，以该方法应用于图1中的服务器为例进行说明，具体包括以下步骤：
步骤202，接收客户终端上传的车险报案信息；车险报案信息包括事故车辆的车牌号。
步骤204，根据车险报案信息生成车险定损任务，将车险定损任务发送至定损终端。
当车辆发生事故时，客户可以利用客户终端向服务器进行车险报案。车险报案信息包括车辆基本信息和出险地点等。车辆基本信息包括事故车辆的车牌号。服务器接收车险报案信息，利用车险报案信息生成车险定损任务，并且将车险定损任务发送至定损终端。定损任务中携带了事故车辆的车牌号和出险地点等。
步骤206，接收定损终端在执行定损任务时上传的配件匹配请求，配件匹配请求中包括车架号和定损项目。
步骤208，根据车架号和定损项目对事故车辆的配件标识进行匹配，得到事故车辆的受损配件标识。
步骤210，将受损配件标识返回至定损终端，以使得定损终端对应定损项目输入受损配件标识。
定损终端在接收到定损任务后，定损终端可以通过GPS定位来捕捉当前所在的位置信息，并且将位置信息上传至服务器。定损人员在前往出险地点的途中，定损终端可以将其位置信息实时上传至服务器。
为了确保定损人员录入的定损信息的准确性，在定损人员到达出险地点之前，定损终端拒绝定损人员输入定损信息的操作。定损终端的位置信息包括经度和纬度。定损终端获取出险地点对应的经度和纬度。当定损终端的经度和纬度与出险地点的经度和纬度的误差在预设范围内时，定损终端可以确定其所在的位置信息与出险地点一致，表示定损人员到达出险地点。
定损人员在出险地点对事故车辆进行查勘，通过定损终端输入定损信息。 定损信息包括：基本信息和定损项目。基本信息包括：车架号、承保险别和事故责任等。定损项目包括：受损配件名称和工时等。其中，受损配件名称具有对应的受损配件标识。受损配件标识可以是受损配件型号等。
同一车型不同配置的车辆的配件名称对应的配件标识可能会不同。为了能够有效避免由于车辆配置不同而造成的配件标识选择错误，当定损终端中输入受损配件名称时，定损终端利用车架号和受损配件名称生成配件匹配请求，并将配件匹配请求上传至服务器。车架号也可称为车辆识别代码，是汽车制造商为每一辆车指定的一组代码。每辆汽车都具有唯一的车架号。车架号中包括了车辆的车型等内容。服务器接收该配件匹配请求，根据该配件匹配请求中携带的车架号和定损配件名称对事故车辆的配件标识进行匹配。由此能够准确匹配出受损配件名称对应的受损配件标识。
在其中一个实施例中，根据车架号和定损项目对事故车辆的配件标识进行匹配的步骤，包括：根据车架号获取事故车辆对应的多个配件名称和配件型号；根据受损配件名称在事故车辆对应的多个配件名称和配件型号中进行检索，得到事故车辆的受损配件标识。
服务器上部署了数据库，数据库中存储了车型、车架号、配件标识和配件图片等。服务器可以根据车架号在数据库中检索事故车辆对应的所有配件名称和配件型号，为了进一步提高匹配准确度，服务器还可以根据受损配件名称在事故车辆对应的所有配件名称中检索受损配件标识。当服务器接收到多个定损终端发送的配件匹配请求时，可以调用多个线程进行并发操作，从而能够有效提高配件匹配效率。
定损终端可以在每次输入受损配件名称时，利用车架号和该受损配件名称生成该项定损项目对应的配件匹配请求。服务器根据配件匹配请求逐一返回对应的受损配件标识。定损终端也可以输入多个受损配件的名称后，利用车架号和多个受损配件名称生成配件匹配请求。服务器可以根据配件匹配请求进行批量处理，返回多个受损配件标识。
服务器将受损配件标识返回至定损终端。定损终端接收受损配件标识， 定损人员对应受损配件名称选择受损配件标识，将定损配件标识对应定损项目进行输入至定损终端。
本实施例中，当车辆发生事故时，客户终端可以向服务器进行车险报案。服务器根据车险报案信息生成车险定损任务，定损人员在执行车险定损任务时，可以向服务器上传配件匹配请求。服务器根据配件匹配请求中携带的车架号和定损项目对事故车辆的配件标识进行匹配，得到相应的受损配件标识。由于每辆汽车的车架号是唯一的，车架号中包括了车型等内容，因此服务器根据车架号和定损项目能够准确匹配出事故车辆的受损配件标识。从而能够有效避免因车型对应的配置不同而导致车辆定损时配件选择错误的问题。
在一个实施例中，定损项目包括事故车辆图片；上述受损配件名称可通过如下步骤获得：对事故车辆图片进行识别，识别出车辆受损部位；对车辆受损部位进行解析，得到受损配件名称。
本实施例中，在对事故车辆进行定损时，定损人员还可以通过定损终端拍摄事故车辆图片。定损终端将事故车辆图片上传至服务器。服务器接收事故车辆图片，对事故车辆图片进行识别，识别出车辆受损部位，对车辆受损部位进行定位。服务器上部署的数据库中存储了海量的定损图片，定损图片中对车辆受损部位已定位，并配置了相应的分类和配件名称。服务器将事故车辆图片中的已定位的车辆受损部位与数据库中的定损图片进行比对，识别出受损配件名称。服务器将识别出的受损配件名称返回至定损终端，由此省去了定损人员手动输入受损配件名称的操作，为定损人员提供了方便。
当定损终端接收到服务器返回的受损配件名称后，可以根据上述实施例中提供的方式，利用车架号和受损配件名称生成配件匹配请求，并将配件匹配请求上传至服务器。服务器根据车架号和受损配件名称对事故车辆的配件标识进行匹配，得到事故车辆的受损配件标识。
在一个实施例中，该方法还包括：根据车架号获取事故车辆的多个配件标识；利用配件标识建立索引，根据索引查询受损配件标识对应的定损价格；将定损价格对应受损配件标识返回至定损终端。
本实施例中，服务器上部署的数据库中，除了储存了车型、车架号、配件标识和配件图片之外，还存储了配件价格。服务器可以利用车型对应的多个配件标识建立索引。当服务器根据车架号和受损配件名称匹配出受损配件标识之后，还可以利用该索引查询受损配件标识对应的定损价格。服务器将受损配件标识对应的定损价格返回至定损终端，使得定损终端能够进一步完善定损信息。由此可以避免定损人员手动查询每个受损配件对应的定损价格，为定损人员提供了方便。
进一步的，如果服务器要同时查询多个受损配件标识对应的定损价格，可以调用多个线程，进行并发查询，从而能够有效提高多个受损配件标识对应的定损价格的查询效率。
应该理解的是，虽然图2的流程图中的各个步骤按照箭头的指示依次显示，但是这些步骤并不是必然按照箭头指示的顺序依次执行。除非本文中有明确的说明，这些步骤的执行并没有严格的顺序限制，这些步骤可以以其它的顺序执行。而且，图2中的至少一部分步骤可以包括多个子步骤或者多个阶段，这些子步骤或者阶段并不必然是在同一时刻执行完成，而是可以在不同的时刻执行，这些子步骤或者阶段的执行顺序也不必然是依次进行，而是可以与其它步骤或者其它步骤的子步骤或者阶段的至少一部分轮流或者交替地执行。
在一个实施例中，如图3所示，提供了一种车辆定损配件匹配系统，包括：客户终端302、服务器304和定损终端306，其中：
客户终端302，用于上传车险报案信息，车险报案信息包括事故车辆的车牌号。
服务器304，用于接收车险报案信息，根据车险报案信息生成车险定损任务，将车险定损任务发送至定损终端。
定损终端306，用于接收定损任务，在执行定损任务时根据车牌号输入车架号和定损项目，利用车架号和定损项目生成配件匹配请求并将配件匹配请求上传至服务器。
服务器304还用于接收配件匹配请求，根据车架号和定损项目对事故车辆的配件标识进行匹配，得到事故车辆的受损配件标识；
定损终端306还用于对应定损项目输入受损配件标识。
当车辆发生事故时，客户可以利用客户终端302向服务器304进行车险报案。车险报案信息包括车辆基本信息和出险地点等。车辆基本信息包括事故车辆的车牌号。服务器304接收车险报案信息，利用车险报案信息生成车险定损任务，并且将车险定损任务发送至定损终端306。定损任务中携带了事故车辆的车牌号和出险地点等。定损人员在出险地点对事故车辆进行查勘，通过定损终端306输入定损信息。定损信息包括：基本信息和定损项目。基本信息包括：车架号、承保险别和事故责任等。定损项目包括：受损配件名称和工时等。其中，受损配件名称具有对应的配件标识。
同一车型不同配置的车辆的配件名称对应的配件标识可能会不同。为了能够有效避免由于车辆配置不同而造成的配件标识选择错误，当定损终端中输入受损配件名称时，定损终端利用车架号和受损配件名称生成配件匹配请求，并将配件匹配请求上传至服务器。车架号中包括了车辆的车型等内容。服务器接收该配件匹配请求，根据该配件匹配请求中携带的车架号和定损配件名称对事故车辆的配件标识进行匹配。由此能够准确匹配出受损配件名称对应的受损配件标识。
在其中一个实施例中，定损项目可以是定损人员手动输入至定损终端306的。服务器304还用于根据车架号获取事故车辆对应的配件名称和配件型号；根据受损配件名称在事故车辆对应的配件名称和配件型号中进行检索，得到事故车辆的受损配件标识。
在其中一个实施例中，定损项目可以包括事故车辆图片和受损配件名称；定损终端306将事故车辆图片上传至服务器304。服务器304还用于对事故车辆图片进行识别，识别出车辆受损部位；对车辆受损部位进行解析，得到受损配件名称。服务器将识别出的受损配件名称返回至定损终端，由此省去了定损人员手动输入受损配件名称的操作，为定损人员提供了方便。当定损 终端接收到服务器返回的受损配件名称后，可以根据上述实施例中提供的方式，利用车架号和受损配件名称生成配件匹配请求，并将配件匹配请求上传至服务器。服务器根据车架号和受损配件名称对事故车辆的配件标识进行匹配，得到事故车辆的受损配件标识。
当车辆发生事故时，客户终端可以向服务器进行车险报案。服务器根据车险报案信息生成车险定损任务，定损人员在执行车险定损任务时，可以向服务器上传配件匹配请求。服务器根据配件匹配请求中携带的车架号和定损项目对事故车辆的配件标识进行匹配，得到相应的受损配件标识。由于每辆汽车的车架号是唯一的，车架号中包括了车型等内容，因此服务器根据车架号和定损项目能够准确匹配出事故车辆的受损配件标识。从而能够有效避免因车型对应的配置不同而导致车辆定损时配件选择错误的问题。
在一个实施例中，定损项目包括受损配件名称，定损终端306还用于对输入的受损配件名称进行匹配校验，若校验未通过，则生成提示信息，并且拒绝接受下一项操作。
本实施例中，定损人员可以在定损项目中逐一输入受损配件名称。对于输入的受损配件名称，定损终端306会对受损配件名称进行匹配校验。具体的，当前定损项目为总成配件或包含性配件时，若输入的下一项受损配件名称为总成配件的附属配件或包含性配件的附属配件，或输入的下一项受损配件名称为总成配件的总配件或包含性配件的总配件，则校验未通过。当前定损项目为即修且换配件时，若当前输入的受损配件名称为待维修配件，下一项操作中对受损配件名称输入为待更换配件，则校验未通过；若输入的下一项受损配件名称与上一项受损配件名称相同，则校验未通过。
通过对输入的定损项目进行多种匹配校验，以便有效防止重复输入以及错误输入等。对于未能通过匹配校验的定损项目进行及时提示，以确保定损人员输入的配件项目准确无误。
在一个实施例中，如图4所示，提供了一种车辆定损配件匹配系统，包括：客户终端402和服务器404，其中：
客户终端402，用于上传车险报案信息，车险报案信息至少包括事故车辆的车牌号、车架号和事故车辆图片。
服务器404，用于接收车险报案信息，将车险报案信息与预设规则进行比对，若经过比对后确定车辆事故为简单事故，则根据对事故车辆图片进行识别，得到受损配件名称，根据车架号和受损配件名称对事故车辆的配件标识进行匹配，得到事故车辆受损配件标识，根据车险报案信息、受损配件名称和受损配件标识对事故车辆进行定损。
当车辆发生事故时，客户可以利用客户终端402向服务器404进行车险报案。车险报案信息包括车辆基本信息、事故车辆图片、出险原因、出险地点、是否现场报案和是否异地出险等。其中，车辆基本信息包括事故车辆的车牌号和车架号。
服务器404根据车险报案信息与预设规则进行比对，判断本次车辆事故是否为简单事故。预设规则包括：现场报案、非异地出险、出险地点不包含预设关键字。举例说明，预设规则如下表一所示：
表一：
现场报案 是
高速公路 否
出险原因 行驶受损
出险地点不包含关键字 高架桥、立交桥、隧道、隧洞
承保险别 车损险
报案损失类型 标的车损、三者车损
出险地点 南山区、龙华区
车辆能否正常行驶 是
经过比对后确定本次车辆事故为简单事故时，服务器404将本次车险报案记录为简单事故。对于简单事故，服务器404可以不再生成车险定损任务，也不再外派定损人员前去定损。服务器404可以按照上述实施例中提供的方式，根据事故车辆图片进行识别，得到受损配件名称。继而根据车架号和受 损配件名称对事故车辆的配件标识进行匹配，得到事故车辆受损配件标识。服务器404利用车险报案信息、受损配件名称和受损配件标识对事故车辆进行定损。
在其中一个实施例中，服务器404还用于根据车架号获取事故车辆的多个配件标识；利用配件标识建立索引，根据索引查询受损配件标识对应的定损价格。
当车辆发生事故时，客户终端向服务器进行车险报案。服务器根据车险报案信息与预设规则进行比对，若确定为简单事故，则根据车险报案信息中携带的事故车辆图片进行识别，得到受损配件名称。继而根据车型报案信息中携带的车架号和受损配件名称对事故车辆的配件标识进行匹配，得到事故车辆受损配件标识，由于每辆汽车的车架号是唯一的，车架号中包括了车型等内容，因此服务器根据车架号和定损项目能够准确匹配出事故车辆的受损配件标识。从而能够有效避免因车型对应的配置不同而导致车辆定损时配件选择错误的问题。服务器根据车险报案信息、受损配件名称和受损配件标识对事故车辆进行定损。在这个过程中，不需要派出定损人员进行定损，有效提高了定损效率。
在一个实施例中，提供了一种服务器，如图5所示，该服务器包括通过系统总线连接的处理器、内存储器、、非易失性存储介质和网络接口。其中，处理器用于提供计算和控制能力。内存储器为非易失性存储介质中的操作系统和计算机程序的运行提供环境。非易失性存储介质中存储有操作系统和计算机可读指令。非易失性存储介质可以是非易失性计算机可读存储介质。计算机可读指令被处理器执行时，可使得处理器执行一种车辆定损配件匹配方法。网络接口用于据以与外部的客户终端或定损终端通过网络连接通信。
该服务器可以用独立的服务器或者是多个服务器组成的服务器集群来实现。本领域技术人员可以理解，图5中示出的结构，仅仅是与本申请方案相关的部分结构的框图，并不构成对本申请方案所应用于其上的服务器的限定，具体的服务器可以包括比图中所示更多或更少的部件，或者组合某些部件， 或者具有不同的部件布置。
一种服务器，包括存储器和一个或多个处理器，存储器中储存有计算机可读指令，计算机可读指令被处理器执行时，使得一个或多个处理器执行上述各个方法实施中的步骤。
一个或多个存储有计算机可读指令的非易失性存储介质，计算机可读指令被一个或多个处理器执行时，使得一个或多个处理器执行上述各个方法实施中的步骤。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程，是可以通过计算机可读指令来指令相关的硬件来完成，所述的计算机可读指令可存储于一非易失性计算机可读取存储介质中，该计算机可读指令在执行时，可包括如上述各方法的实施例的流程。其中，本申请所提供的各实施例中所使用的对存储器、存储、数据库或其它介质的任何引用，均可包括非易失性和/或易失性存储器。非易失性存储器可包括只读存储器(ROM)、可编程ROM(PROM)、电可编程ROM(EPROM)、电可擦除可编程ROM(EEPROM)或闪存。易失性存储器可包括随机存取存储器(RAM)或者外部高速缓冲存储器。作为说明而非局限，RAM以多种形式可得，诸如静态RAM(SRAM)、动态RAM(DRAM)、同步DRAM(SDRAM)、双数据率SDRAM(DDRSDRAM)、增强型SDRAM(ESDRAM)、同步链路(Synchlink)DRAM(SLDRAM)、存储器总线(Rambus)直接RAM(RDRAM)、直接存储器总线动态RAM(DRDRAM)、以及存储器总线动态RAM(RDRAM)等。
以上实施例的各技术特征可以进行任意的组合，为使描述简洁，未对上述实施例中的各个技术特征所有可能的组合都进行描述，然而，只要这些技术特征的组合不存在矛盾，都应当认为是本说明书记载的范围。
以上所述实施例仅表达了本申请的几种实施方式，其描述较为具体和详细，但并不能因此而理解为对发明专利范围的限制。应当指出的是，对于本领域的普通技术人员来说，在不脱离本申请构思的前提下，还可以做出若干 变形和改进，这些都属于本申请的保护范围。因此，本申请专利的保护范围应以所附权利要求为准。

Claims (18)

  1. 一种车辆定损配件匹配方法，包括：
    接收客户终端上传的车险报案信息；所述车险报案信息包括事故车辆的车牌号；
    根据所述车险报案信息生成车险定损任务，将所述车险定损任务发送至定损终端；
    接收定损终端在执行所述定损任务时上传的配件匹配请求，所述配件匹配请求中包括车架号和定损项目；
    根据所述车架号和定损项目对事故车辆的配件标识进行匹配，得到事故车辆的受损配件标识；及
    将所述受损配件标识返回至定损终端，以使得所述定损终端对应定损项目输入所述受损配件标识。
  2. 根据权利要求1所述的方法，其特征在于，所述定损项目包括受损配件名称，所述根据所述车架号和定损项目对事故车辆的配件标识进行匹配包括：
    根据车架号获取事故车辆对应的多个配件名称和配件型号；及
    根据所述受损配件名称在所述事故车辆对应的多个配件名称和配件型号中进行检索，得到事故车辆的受损配件标识。
  3. 根据权利要求1所述的方法，其特征在于，所述定损项目包括事故车辆图片和受损配件名称；所述方法还包括：
    对所述事故车辆图片进行识别，识别出车辆受损部位；及
    对车辆受损部位进行解析，得到所述受损配件名称。
  4. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    根据所述车架号获取事故车辆的多个配件标识；
    利用所述配件标识建立索引，根据所述索引查询所述受损配件标识对应的定损价格；及
    将所述定损价格对应所述受损配件标识返回至定损终端。
  5. 一种车辆定损配件匹配系统，其特征在于，所述系统包括：
    客户终端，用于上传车险报案信息，所述车险报案信息包括事故车辆的车牌号；
    服务器，用于接收所述车险报案信息，根据所述车险报案信息生成车险定损任务，将所述车险定损任务发送至定损终端；
    定损终端，用于接收所述定损任务，在执行所述定损任务时根据所述车牌号输入车架号和定损项目，利用所述车架号和定损项目生成配件匹配请求并将所述配件匹配请求上传至服务器；
    所述服务器还用于接收所述配件匹配请求，根据所述车架号和定损项目对事故车辆的配件标识进行匹配，得到事故车辆的受损配件标识；及
    所述定损终端还用于对应定损项目输入所述受损配件标识。
  6. 根据权利要求5所述的系统，其特征在于，所述定损项目包括受损配件名称，所述服务器还用于根据车架号获取事故车辆对应的配件名称和配件型号；及根据所述受损配件名称在所述事故车辆对应的配件名称和配件型号中进行检索，得到事故车辆的受损配件标识。
  7. 根据权利要求5所述的系统，其特征在于，所述定损项目包括事故车辆图片和受损配件名称；所述定损终端还用于将事故车辆图片上传至服务器；所述服务器还用于对事故车辆图片进行识别，识别出车辆受损部位；对车辆受损部位进行解析，得到受损配件名称；及将识别出的受损配件名称返回至所述定损终端。
  8. 根据权利要求5所述的系统，其特征在于，所述定损项目包括受损配件名称，所述定损终端还用于对输入的受损配件名称进行匹配校验，若校验未通过，则生成提示信息，并且拒绝接受下一项操作。
  9. 一种车辆定损配件匹配系统，其特征在于，所述系统包括：
    客户终端，用于上传车险报案信息，所述车险报案信息至少包括事故车辆的车牌号、车架号和事故车辆图片；及
    服务器，用于接收所述车险报案信息，将所述车险报案信息与预设规则 进行比对，若经过比对后确定车辆事故为简单事故，则根据对所述事故车辆图片进行识别，得到受损配件名称，根据所述车架号和受损配件名称对事故车辆的配件标识进行匹配，得到事故车辆受损配件标识，根据所述车险报案信息、受损配件名称和受损配件标识对事故车辆进行定损。
  10. 根据权利要求9所述的系统，其特征在于，所述服务器还用于根据所述车架号获取事故车辆的多个配件标识；及利用所述配件标识建立索引，根据所述索引查询所述受损配件标识对应的定损价格。
  11. 一种服务器，包括存储器和一个或多个处理器，存储器中储存有计算机可读指令，计算机可读指令被处理器执行时，使得一个或多个处理器执行以下步骤：
    接收客户终端上传的车险报案信息；所述车险报案信息包括事故车辆的车牌号；
    根据所述车险报案信息生成车险定损任务，将所述车险定损任务发送至定损终端；
    接收定损终端在执行所述定损任务时上传的配件匹配请求，所述配件匹配请求中包括车架号和定损项目；
    根据所述车架号和定损项目对事故车辆的配件标识进行匹配，得到事故车辆的受损配件标识；及
    将所述受损配件标识返回至定损终端，以使得所述定损终端对应定损项目输入所述受损配件标识。
  12. 根据权利要求11所述的服务器，其特征在于，所述定损项目包括受损配件名称，计算机可读指令被处理器执行时，使得一个或多个处理器还执行以下步骤：
    根据车架号获取事故车辆对应的多个配件名称和配件型号；及
    根据所述受损配件名称在所述事故车辆对应的多个配件名称和配件型号中进行检索，得到事故车辆的受损配件标识。
  13. 根据权利要求11所述的服务器，其特征在于，所述定损项目包括事 故车辆图片和受损配件名称；计算机可读指令被处理器执行时，使得一个或多个处理器还执行以下步骤：
    对所述事故车辆图片进行识别，识别出车辆受损部位；及
    对车辆受损部位进行解析，得到所述受损配件名称。
  14. 根据权利要求11所述的服务器，其特征在于，计算机可读指令被处理器执行时，使得一个或多个处理器还执行以下步骤：
    根据所述车架号获取事故车辆的多个配件标识；
    利用所述配件标识建立索引，根据所述索引查询所述受损配件标识对应的定损价格；及
    将所述定损价格对应所述受损配件标识返回至定损终端。
  15. 一个或多个存储有计算机可读指令的非易失性存储介质，计算机可读指令被一个或多个处理器执行时，使得一个或多个处理器执行以下步骤：
    接收客户终端上传的车险报案信息；所述车险报案信息包括事故车辆的车牌号；
    根据所述车险报案信息生成车险定损任务，将所述车险定损任务发送至定损终端；
    接收定损终端在执行所述定损任务时上传的配件匹配请求，所述配件匹配请求中包括车架号和定损项目；
    根据所述车架号和定损项目对事故车辆的配件标识进行匹配，得到事故车辆的受损配件标识；及
    将所述受损配件标识返回至定损终端，以使得所述定损终端对应定损项目输入所述受损配件标识。
  16. 根据权利要求15所述的存储介质，其特征在于，所述定损项目包括受损配件名称，计算机可读指令被一个或多个处理器执行时，使得一个或多个处理器还执行以下步骤：
    根据车架号获取事故车辆对应的多个配件名称和配件型号；及
    根据所述受损配件名称在所述事故车辆对应的多个配件名称和配件型号 中进行检索，得到事故车辆的受损配件标识。
  17. 根据权利要求15所述的存储介质，其特征在于，所述定损项目包括事故车辆图片和受损配件名称；计算机可读指令被一个或多个处理器执行时，使得一个或多个处理器还执行以下步骤：
    对所述事故车辆图片进行识别，识别出车辆受损部位；及
    对车辆受损部位进行解析，得到所述受损配件名称。
  18. 根据权利要求15所述的存储介质，其特征在于，计算机可读指令被一个或多个处理器执行时，使得一个或多个处理器还执行以下步骤：
    根据所述车架号获取事故车辆的多个配件标识；
    利用所述配件标识建立索引，根据所述索引查询所述受损配件标识对应的定损价格；及
    将所述定损价格对应所述受损配件标识返回至定损终端。
PCT/CN2018/081795 2017-04-11 2018-04-04 车辆定损配件匹配方法和系统 Ceased WO2018188503A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710234061.8 2017-04-11
CN201710234061.8A CN107798284A (zh) 2017-04-11 2017-04-11 车辆定损配件匹配方法和系统

Publications (1)

Publication Number Publication Date
WO2018188503A1 true WO2018188503A1 (zh) 2018-10-18

Family

ID=61531040

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/081795 Ceased WO2018188503A1 (zh) 2017-04-11 2018-04-04 车辆定损配件匹配方法和系统

Country Status (2)

Country Link
CN (1) CN107798284A (zh)
WO (1) WO2018188503A1 (zh)

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109635651A (zh) * 2018-11-07 2019-04-16 中国平安财产保险股份有限公司 一种基于图像识别的车辆定损方法、存储介质及服务器
CN110084470A (zh) * 2019-03-15 2019-08-02 深圳壹账通智能科技有限公司 基于人脸识别的防查勘员造假方法、装置、终端及介质
CN110210699A (zh) * 2019-04-18 2019-09-06 深圳壹账通智能科技有限公司 智能调度方法、装置、电子设备及存储介质
CN110533449A (zh) * 2019-07-08 2019-12-03 中国平安财产保险股份有限公司 数据推荐方法、装置、设备及存储介质
CN110889593A (zh) * 2019-11-01 2020-03-17 浙江大搜车软件技术有限公司 车辆评估方法、装置、计算机可读存储介质和计算机设备
CN110909731A (zh) * 2019-10-12 2020-03-24 深圳壹账通智能科技有限公司 车辆救援场景质检方法、装置、设备及存储介质
CN111754211A (zh) * 2020-07-27 2020-10-09 杭州钧钥信息科技有限公司 一种基于大数据的智能分析报告自动生成系统
CN113222331A (zh) * 2021-03-29 2021-08-06 北京中交兴路信息科技有限公司 识别车辆事故真实性的方法、装置、设备及存储介质
CN116304148A (zh) * 2022-09-07 2023-06-23 厦门创联享信息科技有限公司 用于车辆配件交易的数据匹配方法
CN116664112A (zh) * 2023-07-25 2023-08-29 凯泰铭科技（北京）有限公司 用于车损案件的检修扩损决策方法及系统

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107798284A (zh) * 2017-04-11 2018-03-13 平安科技（深圳）有限公司 车辆定损配件匹配方法和系统
CN109242006A (zh) * 2018-08-23 2019-01-18 阿里巴巴集团控股有限公司 基于车型分类的识别车辆损伤的方法及装置
CN112364187B (zh) * 2020-10-27 2022-11-08 南阳理工学院 基于大数据的汽车配件数据库建库方法、装置及设备
CN113344712A (zh) * 2021-05-07 2021-09-03 北京精友时代信息技术发展有限公司 基于图像识别的智能分拣及保险赔付系统

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101242379A (zh) * 2008-03-18 2008-08-13 北京中车检信息技术有限公司 基于移动通讯终端或网络终端的车辆定损方法
CN102831502A (zh) * 2012-08-13 2012-12-19 福州华昆电子科技有限公司 汽车车险管理系统及方法
CN106231263A (zh) * 2016-08-03 2016-12-14 深圳市永兴元科技有限公司 基于移动网络通信的车辆定损理赔方法及装置
CN106296118A (zh) * 2016-08-03 2017-01-04 深圳市永兴元科技有限公司 基于图像识别的车辆定损方法及装置
CN107798284A (zh) * 2017-04-11 2018-03-13 平安科技（深圳）有限公司 车辆定损配件匹配方法和系统

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103473923B (zh) * 2013-09-18 2016-04-20 林诗昊 一种机动车交通违法实时告知、确认的方法
CN105931007A (zh) * 2016-01-13 2016-09-07 平安科技（深圳）有限公司 定损审核方法、服务器及终端
CN106131206A (zh) * 2016-08-01 2016-11-16 深圳市永兴元科技有限公司 车辆事故现场勘查方法和装置
CN106296409A (zh) * 2016-08-01 2017-01-04 深圳市永兴元科技有限公司 车辆事故现场勘察方法和系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101242379A (zh) * 2008-03-18 2008-08-13 北京中车检信息技术有限公司 基于移动通讯终端或网络终端的车辆定损方法
CN102831502A (zh) * 2012-08-13 2012-12-19 福州华昆电子科技有限公司 汽车车险管理系统及方法
CN106231263A (zh) * 2016-08-03 2016-12-14 深圳市永兴元科技有限公司 基于移动网络通信的车辆定损理赔方法及装置
CN106296118A (zh) * 2016-08-03 2017-01-04 深圳市永兴元科技有限公司 基于图像识别的车辆定损方法及装置
CN107798284A (zh) * 2017-04-11 2018-03-13 平安科技（深圳）有限公司 车辆定损配件匹配方法和系统

Cited By (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109635651B (zh) * 2018-11-07 2024-05-24 中国平安财产保险股份有限公司 一种基于图像识别的车辆定损方法、存储介质及服务器
CN109635651A (zh) * 2018-11-07 2019-04-16 中国平安财产保险股份有限公司 一种基于图像识别的车辆定损方法、存储介质及服务器
CN110084470A (zh) * 2019-03-15 2019-08-02 深圳壹账通智能科技有限公司 基于人脸识别的防查勘员造假方法、装置、终端及介质
CN110210699A (zh) * 2019-04-18 2019-09-06 深圳壹账通智能科技有限公司 智能调度方法、装置、电子设备及存储介质
CN110533449A (zh) * 2019-07-08 2019-12-03 中国平安财产保险股份有限公司 数据推荐方法、装置、设备及存储介质
CN110909731A (zh) * 2019-10-12 2020-03-24 深圳壹账通智能科技有限公司 车辆救援场景质检方法、装置、设备及存储介质
CN110889593A (zh) * 2019-11-01 2020-03-17 浙江大搜车软件技术有限公司 车辆评估方法、装置、计算机可读存储介质和计算机设备
CN111754211A (zh) * 2020-07-27 2020-10-09 杭州钧钥信息科技有限公司 一种基于大数据的智能分析报告自动生成系统
CN113222331B (zh) * 2021-03-29 2024-03-05 北京中交兴路信息科技有限公司 识别车辆事故真实性的方法、装置、设备及存储介质
CN113222331A (zh) * 2021-03-29 2021-08-06 北京中交兴路信息科技有限公司 识别车辆事故真实性的方法、装置、设备及存储介质
CN116304148A (zh) * 2022-09-07 2023-06-23 厦门创联享信息科技有限公司 用于车辆配件交易的数据匹配方法
CN116664112A (zh) * 2023-07-25 2023-08-29 凯泰铭科技（北京）有限公司 用于车损案件的检修扩损决策方法及系统
CN116664112B (zh) * 2023-07-25 2023-11-14 凯泰铭科技（北京）有限公司 用于车损案件的检修扩损决策方法及系统

Also Published As

Publication number Publication date
CN107798284A (zh) 2018-03-13

Similar Documents

Publication Publication Date Title
WO2018188503A1 (zh) 车辆定损配件匹配方法和系统
KR101721339B1 (ko) 새로운 공급처의 주소를 확정하는 방법 및 장치
CN109992601B (zh) 待办事项信息的推送方法、装置和计算机设备
WO2020186786A1 (zh) 文件处理方法、装置、计算机设备和存储介质
CN108427613B (zh) 异常接口定位方法、装置、计算机设备和存储介质
CN111767350B (zh) 数据仓库测试方法、装置、终端设备及存储介质
JP7701112B2 (ja) バッテリー仕様の検索及び集約方法
WO2018201977A1 (zh) 查勘任务分配方法、系统、服务器和存储介质
WO2018184533A1 (zh) 车险理赔方法和装置
CN111190901B (zh) 业务数据存储方法、装置、计算机设备和存储介质
WO2020006878A1 (zh) 语音识别测试方法、装置、计算机设备及存储介质
CN110276458A (zh) 车辆故障的处理方法、装置、存储介质及电子装置
WO2020253122A1 (zh) 数据核对方法、装置、计算机设备和存储介质
WO2017190483A1 (zh) 一种车辆维修策略推送方法及装置
CN111324375A (zh) 代码管理方法、装置、计算机设备和存储介质
CN108399125B (zh) 自动化测试方法、装置、计算机设备和存储介质
US11281564B2 (en) Method and system for generating key performance indicators (KPIs) for software based on debugging information
CN110310127B (zh) 录音获取方法、装置、计算机设备及存储介质
CN115114503B (zh) 医疗搜索模型性能评价方法、装置、设备及介质
WO2020215693A1 (zh) 软件测试方法、装置、计算机设备和可读存储介质
CN105843890B (zh) 基于知识库面向大数据及普通数据的数据采集方法和系统
CN110533129B (zh) 电子图书馆的管理方法、电子设备及计算机存储介质
CN116719750B (zh) 软件测试方法及装置、服务器设备和存储介质
CN109359279B (zh) 报表生成方法、装置、计算机设备和存储介质
CN110321379A (zh) 调频辅助服务市场出清文件的解析方法、装置、计算机设备和存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18784947

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 20.01.2020)

122 Ep: pct application non-entry in european phase

Ref document number: 18784947

Country of ref document: EP

Kind code of ref document: A1