Information processing device

The information processing device addresses the challenge of meeting user-specific vehicle needs by facilitating user feedback and manufacturing communication, enabling cost-effective customization of vehicles.

JP7620263B2Active Publication Date: 2025-01-23TOYOTA JIDOSHA KK
View PDF 7 Cites 0 Cited by

Patent Information

Application Number
JP2021142578
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2021-09-01
Publication Date
2025-01-23
Estimated Expiration
2041-09-01

AI Technical Summary

Technical Problem

Existing vehicle manufacturing systems struggle to meet user-specific needs without significantly increasing costs or complicating product management.

Method used

An information processing device that collects user preferences, identifies suitable vehicle models, generates manufacturing plans, and facilitates communication between users and manufacturers to propose and evaluate customized vehicles.

Benefits of technology

Enables the production of user-specific vehicles at a realistic cost by aggregating user feedback and manufacturing proposals, ensuring only high-value ideas are commercialized.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007620263000001
    Figure 0007620263000001
  • Figure 0007620263000002
    Figure 0007620263000002
  • Figure 0007620263000003
    Figure 0007620263000003
Patent Text Reader

Abstract

To provide an information processor that proposes a vehicle that meets a user request at a realistic cost.SOLUTION: A vehicle proposal server 100 includes: a collection unit 110 for collecting custom information of a vehicle requested by a user; a vehicle type database 121 in which vehicle type information for each selectable vehicle is registered; an identification unit 130 for identifying, on the basis of the custom information, vehicle model information necessary to realize the user request; a generation unit 140 for generating, on the basis of the identified vehicle type information, and the custom information, request information; a transmission unit 150 for transmitting the generated request information to a manufacturing candidate; a reception unit 160 for receiving proposal information of a customized vehicle reflecting the request information from the manufacturing candidate; and an output unit 170 for outputting the received proposal information.SELECTED DRAWING: Figure 4
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to an information processing device suitable for use in manufacturing a vehicle that reflects user requests. [Background technology]

[0002] In the sale of four-wheeled vehicles, the customer selects and purchases products with designs and specifications provided by the manufacturer. Therefore, it is difficult to meet the detailed needs of the user, such as detailed options, designs, and functions related to the vehicle.

[0003] On the other hand, for products other than vehicles, there are known systems that process and manage products based on the standards and specifications required by users (see, for example, Patent Document 1). Such systems enable users to obtain products that reflect detailed options, etc. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2002-328972 A Summary of the Invention [Problem to be solved by the invention]

[0005] However, if an attempt is made to accommodate detailed options for all users, as in the system disclosed in Patent Document 1, there are problems in that the manufacturing costs increase significantly and the methods of processing and managing the products become extremely complicated.

[0006] The present invention has been made in consideration of the above-described circumstances, and has as its object to provide a vehicle that meets the needs of users at a realistic cost. [Means for solving the problem]

[0007] An information processing device according to one embodiment of the present disclosure comprises a collection unit that collects custom information of a vehicle desired by a user, a database in which vehicle model information of each selectable vehicle is registered, an identification unit that identifies vehicle model information of a vehicle required to realize the user's wishes from multiple vehicle model information registered in the database based on the custom information, a generation unit that generates request information based on the identified vehicle model information and custom information, a transmission unit that transmits the generated request information to a manufacturing candidate, a receiving unit that receives proposal information of a customized vehicle that reflects the request information from the manufacturing candidate, and an output unit that outputs the received proposal information. Effect of the Invention

[0008] According to certain aspects of the present invention, it is possible to provide a vehicle that meets the needs of a user at a realistic cost. [Brief description of the drawings]

[0009] [Figure 1] FIG. 1 is an explanatory diagram showing an overview of a system according to an embodiment of the present invention. [Diagram 2] FIG. 1 illustrates an example of a system configuration. [Diagram 3] FIG. 2 is a diagram illustrating an example of a hardware configuration of a vehicle proposal server and a terminal. [Figure 4] FIG. 2 is a block diagram showing a functional configuration of a vehicle proposal server 100. [Diagram 5] FIG. 13 is a diagram illustrating an example of a web page screen. [Figure 6] 13 is a flowchart showing a flow of a vehicle suggestion process. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS The present invention will now be described with reference to the accompanying drawings, in which like reference numerals denote like or similar structures.

[0011] A. This embodiment <System Overview> FIG. 1 is an explanatory diagram showing an overview of a system 1000 according to this embodiment. A user who has a vague idea of ​​the vehicle they want sends an idea about the vehicle to the vehicle proposal server 100 (step S1). When the vehicle proposal server 100 receives the idea about the vehicle, it refers to a database (described later) and identifies a vehicle model (e.g., SUV-type yes or no) that embodies the received idea. When the vehicle proposal server 100 identifies the vehicle model, it generates request information that includes the idea received from the proposing user and the vehicle model to be embodied. The vehicle proposal server 100 transmits the generated request information to a candidate for vehicle manufacturing.

[0012] Based on the request information, the vehicle manufacturing candidate generates proposal information representing a vehicle manufacturing plan required to materialize the idea (e.g., required parts, delivery date, estimated cost, etc.) and transmits it to the vehicle proposal server 100 (step S2). The vehicle proposal server 100 posts the received proposal information on a specified web page (step S3).

[0013] Each potential customer understands the contents of the proposal information by accessing a specific web page. Each potential customer evaluates the customized vehicle shown in the proposal information and sends it as evaluation information to the vehicle proposal server 100 (step S4). When the vehicle proposal server 100 receives the evaluation information of the customized vehicle from each potential customer, it compiles it and outputs it to an outside party (for example, a vehicle manufacturer) (step S5).

[0014] With this system, only those vehicle ideas proposed by users that receive high praise from potential customers can be commercialized, making it possible to provide vehicles that meet customer demands at a realistic cost.

[0015] <System configuration> FIG. 2 is a diagram illustrating an example of the configuration of the system 1000. The system 1000 includes a vehicle proposal server (information processing device) 100 and a terminal 200. The vehicle proposal server 100 and the terminal 200 are capable of communicating with each other via a network N.

[0016] One or more portions of network N may be a wired network or a wireless network, which may include, by way of example and without limitation, an ad hoc network, an intranet, an extranet, a virtual private network (VPN), a local area network (LAN), a wireless LAN (WLAN), a wide area network (WAN), a wireless WAN (WWAN), a metropolitan area network (MAN), a portion of the Internet, a portion of the Public Switched Telephone Network (PSTN), a cellular network, Integrated Service Digital Networks (ISDNs), wireless LANs, Long Term Evolution (LTE), Code Division Multiple Access (CDMA), Bluetooth, satellite communications, or the like, or a combination of two or more thereof.

[0017] The vehicle proposal server 100 is configured, for example, by a server computer, and has functions such as using vehicle model information for each vehicle stored in an on-premise or cloud-based database (described later) to identify the vehicle model that embodies the vehicle-related idea proposed by the user, generating request information for vehicle manufacturer candidates, and posting proposal information received from vehicle manufacturer candidates on a web page (described in more detail later).

[0018] The terminal 200 is a terminal operated by a user, a vehicle manufacturing candidate, a potential customer, etc., and is configured by a personal computer, a handheld computing device, a smartphone, a mobile phone, a wearable terminal, or the like.

[0019] A user generates an idea for a vehicle by operating the terminal 200 and transmits it to the vehicle proposal server 100. A candidate vehicle manufacturer generates proposal information representing a vehicle manufacturing plan (e.g., required parts, delivery date, predicted cost, etc.) required to realize the proposed idea by operating the terminal 200 and transmits it to the vehicle proposal server 100. A potential customer generates evaluation information for the customized vehicle indicated in the proposal information by operating the terminal 200 and transmits it to the vehicle proposal server 100.

[0020] The vehicle proposal server 100 and the terminal 200 described above do not necessarily have to be configured as a single computer, but may be configured as a plurality of computers and storages distributed over the network N.

[0021] <Hardware configuration> 3 is a diagram showing an example of the hardware configuration of the vehicle proposal server 100 and the terminal 200. The vehicle proposal server 100 and the terminal 200 each have a CPU (Central Processing Unit) 1, a storage device 2 such as a ROM (Read Only Memory) or a RAM (Random Access Memory), a communication IF (Interface) 3 for wired or wireless communication, an input device 4 for accepting input operations, and an output device 5 for outputting information. The input device 4 is, for example, a keyboard, a mouse, a touch panel, a microphone, etc. The output device 5 is, for example, a display (screen) and / or a speaker, etc.

[0022] Hereinafter, the functional configuration and functional overview of the vehicle proposal server 100 will be described with reference to the drawings.

[0023] <Functional configuration and function overview> FIG. 4 is a block diagram showing the functional configuration of the vehicle proposal server 100. As shown in FIG.

[0024] The vehicle proposal server 100 includes a collection unit 110, a storage unit 120, an identification unit 130, a generation unit 140, a transmission unit 150, a reception unit 160, an output unit 170, and an evaluation unit 180. The collection unit 110, the identification unit 130, the generation unit 140, the transmission unit 150, the reception unit 160, the output unit 170, and the evaluation unit 180 are realized by the CPU 1 of the vehicle proposal server 100 executing various programs stored in the storage device 2. The programs can be stored in a storage medium such as a USB memory or a CD-ROM.

[0025] The collection unit 110 receives vehicle-related ideas (image information, text information, audio information, etc.) proposed by the user. Ideas related to the vehicle include, for example, the installation of a roof tent or bed board, or the installation of parts that enable amphibious use. When the collection unit 110 receives such ideas, it grasps the user's ideas by, for example, using AI (Artificial Intelligence) to perform image recognition, audio recognition, natural language processing, etc., and collects them as custom information for the vehicle desired by the user.

[0026] The storage unit 120 is realized by the storage device 2, and stores various data and the like, and programs that realize each function of the vehicle proposal server 100. The storage unit 120 also includes a vehicle model database (DB) 121 that registers vehicle model information of each vehicle selectable by the vehicle proposal server 100, a customer database (DB) 122 that registers a potential customer list related to potential customers, a manufacturer database (DB) 123 that registers a manufacturing candidate list related to manufacturing candidates, and the like.

[0027] Vehicle type information is information that indicates the type of vehicle that a vehicle manufacturer can provide, for example, and may include not only information indicating the body type, such as a sedan or a minivan, but also information such as the year, grade, and the like.

[0028] A potential customer list is, for example, a list of customers held by a vehicle manufacturer. In the potential customer list, basic information of each customer (ID, name, age, sex, address, contact information, email address, SNS account, annual income, family composition, hobbies, etc.) and vehicle-related information on the vehicles owned by each customer (purchase history, repair history, vehicle name, model number, etc.) are registered for each customer.

[0029] The candidate manufacturer list is a list of manufacturers held by, for example, a vehicle manufacturer. The candidate manufacturer list includes basic information about each manufacturer (ID, company name, number of employees, address, contact information, email address, etc.) and performance information about the vehicle manufacturing performance (manufacturing history, delivery date, cost, etc.).

[0030] Based on an idea related to a vehicle proposed by a user (i.e., vehicle customization information), the identification unit 130 identifies vehicle model information representing a vehicle manufacturing plan required to realize the idea from among a plurality of vehicle model information registered in the vehicle model DB 121. To explain by way of an example, when the identification unit 130 determines, based on the vehicle customization information provided by the collection unit 110, that a roof tent is desired to be installed, it identifies vehicle model information (e.g., ◯ or ◯ for an SUV) of a vehicle on which a roof tent can be installed as an option from among a plurality of vehicle model information registered in the vehicle model DB 121.

[0031] The generating unit 140 generates request information for requesting a potential manufacturer to create and propose a manufacturing plan according to the vehicle model information and vehicle customization information of the vehicle identified by the identifying unit 130. For example, if the vehicle customization information is "installation of roof tent" and the vehicle model information is "SUV-type yes / no," the generation unit 140 generates request information that includes this information as well as other information necessary to realize the user's idea (such as parts, delivery date, and estimated cost) and proposes it as a manufacturing proposal.

[0032] The transmission unit 150 transmits the request information generated by the generation unit 140 to the terminal 200 of the manufacturing candidate. The manufacturing candidate to which the request information is to be transmitted (i.e., the transmission destination of the request information) may be set appropriately depending on the request content, etc. For example, the transmission unit 150 selects the most suitable manufacturing candidate by comparing the request content indicated in the request information with the performance information of each manufacturing candidate registered in the manufacturing candidate list, and transmits the request information to the selected manufacturing candidate. However, the selected manufacturing candidate is not limited to one company, and may be two or more companies (multiple companies).

[0033] The receiving unit 160 receives proposal information representing a manufacturing plan for a vehicle (i.e., a customized vehicle) that reflects the request information from the manufacturing candidate's terminal 200. The manufacturing plan generated by the manufacturing candidate includes information representing details of the customized vehicle (e.g., vehicle customization information, vehicle model information, necessary parts, delivery date, estimated cost, etc.).

[0034] The output unit 170 posts the proposal information received by the receiving unit 160 on a predetermined Web page (for example, the site of the vehicle proposal server 100, etc.).

[0035] FIG. 5 is a diagram illustrating an example of a screen P1 of a Web page on which proposal information is posted. On the web page screen P1, for example, in addition to a projected image F1 of the customized vehicle, vehicle customization information IF1, vehicle model information IF2, parts information IF3 regarding required parts, delivery date information IF4 regarding delivery dates, cost information IF5 regarding estimated costs, etc. are displayed.

[0036] Returning to FIG. 4, the evaluation unit 180 compiles evaluations of the customized vehicle by potential customers and outputs them to the outside (for example, the manufacturer). In more detail, the evaluation unit 180 refers to the proposal information and the potential customer list, and identifies potential customers who are likely to be interested in the customized vehicle shown in the proposal information. For example, in the case of a customized vehicle equipped with a "roof tent" or the like, the evaluation unit 180 extracts potential customers who are likely to be interested in outdoor sports, camping, and the like from the customer DB 122, and requests the terminal 200 of the extracted potential customer to evaluate the customized vehicle.

[0037] The number of potential customers requesting an evaluation is not limited, but in the following, two or more potential customers are assumed (see FIG. 1). When the potential customer receives such a request, the potential customer appropriately operates the terminal 200 to access a Web page and understand the contents of the proposed information (i.e., details of the customized vehicle, etc.). The potential customer then inputs evaluation information of the customized vehicle to the terminal 200. To explain this with an example, the potential customer inputs information such as whether or not he or she intends to purchase the customized vehicle, and requests regarding the customized vehicle, as evaluation information of the customized vehicle. The terminal 200 of the potential customer transmits the input evaluation information of the customized vehicle to the vehicle proposal server 100. When the evaluation unit 180 receives the evaluation information of the customized vehicle from the terminal 200 of each potential customer, it compiles the information and outputs it to the vehicle manufacturer, etc. The vehicle manufacturer manufactures the customized vehicle based on the evaluation information obtained from the evaluation unit 180 when a predetermined condition is satisfied (for example, when a certain number of purchases or more are expected).

[0038] The evaluation unit 180 may provide the customized vehicle evaluation information to the vehicle manufacturer using a graph, a table, etc. The operation of the vehicle proposal server 100 will be described below with reference to the drawings.

[0039] <Operation> FIG. 6 is a flowchart showing the flow of the vehicle proposal process executed by the vehicle proposal server 100. When the collection unit 110 receives an idea for a vehicle proposed by a user, it uses AI to grasp the user's idea and collects it as customization information for the vehicle desired by the user (step Sa1). The identifying unit 130 identifies vehicle model information of a vehicle required to realize the idea from among a plurality of vehicle model information registered in the vehicle model DB 121 based on the custom information of the vehicle (step Sa2).

[0040] The generating unit 140 generates request information for requesting the manufacturing candidate to create and propose a manufacturing plan according to the vehicle model information and vehicle customization information of the vehicle identified by the identifying unit 130 (step Sa3).

[0041] The transmitting unit 150 transmits the request information generated by the generating unit 140 to the terminal 200 of the manufacturing candidate (step Sa4).

[0042] The receiving unit 160 receives proposal information that represents a manufacturing plan for a customized vehicle that reflects the request information, transmitted from the terminal 200 of the manufacturing candidate (step Sa5).

[0043] The output unit 170 posts the proposal information received by the receiving unit 160 on a predetermined Web page (step Sa6).

[0044] The evaluation unit 180 refers to the proposal information and the potential customer list, and identifies potential customers who are likely to be interested in the customized vehicle shown in the proposal information (step Sa7).

[0045] The evaluation unit 180 requests the terminal 200 of the identified potential customer to evaluate the customized vehicle (step Sa8). When the evaluation unit 180 receives the evaluation information of the customized vehicle from the terminal 200 of the potential customer, it compiles the information and outputs it to an external party such as the manufacturer (step Sa9), and the process ends.

[0046] C. Modifications The present invention is not limited to the above-described embodiment, and can be implemented in various other forms without departing from the scope of the present invention. Therefore, the above-described embodiment is merely an example in all respects and should not be interpreted as being restrictive. For example, the order of each of the above-described processing steps can be arbitrarily changed or executed in parallel as long as no contradiction occurs in the processing content.

[0047] In the above embodiment, customers who are likely to be interested in the customized vehicle are determined as potential customers by referring to the proposal information and the potential customer list, but the present invention is not limited to this. For example, customers randomly selected from the potential customer list may be determined as potential customers.

[0048] In the above embodiment, a four-wheeled automobile is used as an example of a vehicle, but the present invention is not limited to this and can be applied to various vehicles with wheels. In addition, the present invention can be applied to any moving body such as a ship, an airplane, a rocket, etc.

[0049] In this specification, a "unit" does not simply mean a physical configuration, but also includes cases where the processing performed by the "unit" is realized by software. Furthermore, the processing performed by one "unit" or device may be realized by two or more physical configurations or devices, and the processing performed by two or more "units" or devices may be realized by one physical means or device. [Explanation of symbols]

[0050] 1000...system, 100...vehicle proposal server, 110...collection unit, 120...memory unit, 121...vehicle model database, 122...customer database, 123...manufacturer database, 130...identification unit, 140...generation unit, 150...transmission unit, 160...reception unit, 170...output unit, 180...evaluation unit, 200...terminal, F1...image of completed product, IF1...vehicle customization information, IF2...vehicle model information, IF3...parts information, IF4...delivery date information, IF5...cost information.

Claims

[Claim 1] A collection unit that collects custom information of a vehicle desired by a user; A database that contains information on the vehicle models that can be selected, A potential customer list that includes vehicle-related information about the vehicles owned by each customer; an identification unit that identifies vehicle model information required to realize the user's desire from among a plurality of vehicle model information registered in the database based on the custom information; A generation unit that generates request information based on the specified vehicle type information and the specified custom information; a transmission unit that transmits the generated request information to a manufacturing candidate; a receiving unit that receives, from the manufacturing candidate, proposal information of a customized vehicle that reflects the request information; an output unit that outputs the received proposal information; an evaluation unit that identifies a potential customer of the customized vehicle that reflects the request information based on the proposal information and the potential customer list, and requests a terminal of the identified potential customer of the customized vehicle to evaluate the customized vehicle; The evaluation unit is an information processing device that receives evaluation information indicating an evaluation of the customized vehicle from a terminal of the potential customer and outputs the evaluation information to a vehicle manufacturer.

Citation Information

Patent Citations

  • System and method for managing manufacturing of custom-built product

    JP2002328972A

  • System, method and program for selling article and recording medium for recording program

    JP2002352091A

  • Information processing method, information processing device, and information processing program

    JP2003108825A

  • Simulator for mounting car parts

    JP2003296725A

  • Vehicle component customization proposal system

    JP2019197477A