Information processing device

Abstract

To provide a technology which can improve convenience when a user orders components for a vehicle.SOLUTION: An information processing device manages a first site for receiving an order of components for a vehicle. In the information processing device, a control unit acquires first identification information which uniquely identifies a first vehicle. The control unit identifies a first component which can be attached to the first vehicle, on the basis of the acquired first identification information. The control unit displays a component list which can identify the first component, on the first site.SELECTED DRAWING: Figure 6

Description

[Technical Field]

[0001] The present disclosure relates to an information processing device. [Background technology]

[0002] BACKGROUND ART A commodity trading system that allows a user to order commodities via a network is known (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2002-015178 Summary of the Invention [Problem to be solved by the invention]

[0004] An object of the present disclosure is to provide a technology that can improve convenience when a user orders vehicle parts. [Means for solving the problem]

[0005] The present disclosure relates to an information processing device that manages a first site for receiving orders for vehicle parts. In this case, the information processing device may, for example, Obtaining first identification information that uniquely identifies a first vehicle; Identifying a first part that can be installed on the first vehicle without conflicting with a part already installed on the first vehicle based on the first identification information; posting a parts list identifying the first part on the first site; The control unit may be configured to execute the above.

[0006] The present disclosure can also be regarded as an information processing method in which a computer executes the processing of an information processing device, a program for causing a computer to execute the information processing method, or a non-transitory storage medium for storing the program. [Effects of the Invention]

[0007] According to the present disclosure, it is possible to provide a technology that can improve convenience when a user orders parts for a vehicle. [Brief explanation of the drawings]

[0008] [Figure 1] 1 is a block diagram illustrating a schematic configuration example of a system to which an information processing device according to the present disclosure is applied. [Figure 2] FIG. 2 is a diagram illustrating an example of a first Web page in an embodiment. [Figure 3] FIG. 10 is a diagram illustrating an example of a second Web page in the embodiment. [Figure 4] FIG. 3 is a diagram illustrating an example of information stored in a vehicle management DB according to the embodiment. [Figure 5] FIG. 4 is a diagram illustrating an example of information stored in a parts management DB according to the embodiment. [Figure 6] 10 is a flowchart illustrating an example of a processing routine executed by a server in the embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0009] The information processing device according to the present disclosure is a computer that manages a first site for receiving orders for vehicle parts. The "vehicle parts" referred to here include exterior and interior vehicle parts. This is not limited to hardware such as parts, but also includes software for upgrading the vehicle's driving functions and safety functions. In the information processing device, the control unit acquires first identification information of the first vehicle. The first vehicle is a vehicle for which the user has ownership or usage rights. The first identification information is information for uniquely identifying the first vehicle, such as a VIN (Vehicle Identification Number) or a vehicle identification number. The first identification information may include the VIN and the vehicle ID number. The information is not limited to the vehicle identification number, and may be any information that can identify a part (first part) that can be installed on the first vehicle without conflicting with parts already installed on the first vehicle. The first identification information may be acquired by having a user browsing the first site input the information. Alternatively, the first identification information may be linked in advance to authentication information (e.g., a user ID) used when the user logs in to the first site, and the control unit may acquire the first identification information using the user ID as an argument.

[0010] Based on the acquired first identification information, the control unit identifies a first part that can be installed on the first vehicle without conflicting with parts already installed on the first vehicle. The "first part" here refers to, for example, a part that is compatible with the model of the first vehicle and does not conflict with parts already installed on the first vehicle in terms of function and / or installation location. In other words, the "first part" refers to a part that can be installed on the first vehicle without taking measures such as changing the function of and / or removing parts already installed on the first vehicle. The above-described first part may be identified based on the first identification information and information stored in a database. The "database" here may, for example, store installability information for each part in association with the first identification information. The "installability information" is, for example, information indicating whether a part can be installed on the first vehicle without conflicting with parts already installed on the first vehicle. The parts for which the installation feasibility information is obtained may be all parts handled at the first site, or may be only parts handled at the first site that are compatible with the model of the first vehicle.

[0011] The control unit posts a parts list on the first site that allows the user to identify the identified first part. The "parts list" here refers to, for example, a list that allows the user to identify the first part from other parts (parts that cannot be installed on the first vehicle). The parts list may also be a list that includes only the first part. The parts list may also be posted by displaying a web page on which the parts list is posted through a browser on the user's terminal.

[0012] According to the present disclosure, a user of a first vehicle can identify parts that can be installed without conflicting with parts already installed on the first vehicle. This saves the user the trouble of searching for parts that can be installed without conflicting with parts already installed on the first vehicle, and prevents the user from ordering parts that cannot be installed on the first vehicle. This improves convenience for users when ordering parts for their vehicles.

[0013] Another aspect of the present disclosure can be specified as an information processing method in which a computer executes the processing of the information processing device. Such an information processing method can achieve the same functions and effects as the information processing device. Another aspect of the present disclosure can also be specified as a program for causing a computer to execute the processing of the information processing device, or a non-transitory storage medium for storing the program.

[0014] Specific embodiments of the present disclosure will be described below with reference to the accompanying drawings. The configurations of the following embodiments are examples, and the present disclosure is not limited to the configurations of the embodiments.

[0015] <Embodiment> An embodiment of the present disclosure will be described with reference to Fig. 1 to Fig. 6. In this embodiment, an example will be described in which an information processing device according to the present disclosure is applied to a system for online ordering of vehicle parts.

[0016] (Overall system configuration) Fig. 1 is a block diagram showing a schematic configuration example of a system according to this embodiment. The system according to this embodiment includes a user terminal 200 and a server 300. Although only one user terminal 200 is shown in the example shown in Fig. 1, multiple user terminals 200 may be included.

[0017] The user terminal 200 is a terminal used by a user who has ownership or use rights of the first vehicle 1. In this embodiment, the user terminal 200 is a computer on which a browser application program is installed, such as a smartphone, a mobile phone, a tablet terminal, a wearable device, or a personal computer.

[0018] Server 300 is an information processing device that manages a first site for receiving orders for vehicle parts. Server 300 can be configured as a computer having a processor such as a CPU or GPU, a main storage device such as RAM and ROM, and an auxiliary storage device such as an EPROM, a hard disk drive, or removable media. The auxiliary storage device of server 300 stores an operating system (OS), various programs, various tables, etc. The processor of server 300 loads programs stored in the auxiliary storage device into a working area of ​​the main storage device and executes them to realize various functions consistent with predetermined purposes, as described below. However, some or all of the functions of server 300 may be realized by hardware circuits such as an ASIC (Application Specific Integrated Circuit) or an FPGA (Field Programmable Gate Array).

[0019] In this embodiment, the server 300 is configured to be able to execute a web server for interacting with the user terminal 200. When a user logs in to a site (first site) provided by the web server through the browser of the user terminal 200, the server 300 displays the web page of the first site (a web page listing information about vehicle parts) through the browser of the user terminal 200. The server 300 receives an order request for a part listed on the web page from the user terminal 200 and processes the order for the corresponding product. Note that the server 300 may provide the above-described services by means other than a web server. For example, the server 300 may execute a service that interacts with a dedicated application program installed on the user terminal 200 using a predetermined protocol. Note that the parts handled on the first site are not limited to hardware such as exterior and interior vehicle parts, but also include software for upgrading the vehicle's driving and safety functions.

[0020] As shown in FIG. 1, the server 300 in this embodiment includes a communication unit 301, a control unit 302, a user management DB 303, a vehicle management DB 304, a parts management DB 305, and the like.

[0021] The communication unit 301 is a communication interface for connecting the server 300 to the network N1. The communication unit 301 connects to the network N1 via, for example, a LAN or Wi-Fi (registered trademark), and communicates with the user terminal 200 via the network N1. The network N1 is, for example, a WAN, which is a global public communication network such as the Internet, or another communication network.

[0022] The control unit 302 is realized by the processor of the server 300 executing a program stored in the auxiliary storage unit. The control unit 302 acquires the vehicle ID of the first vehicle 1 when the user logs in to the first site through the browser of the user terminal 200. The vehicle ID is information for uniquely identifying the individual first vehicle 1, and corresponds to the "first identification information" according to the present disclosure. The vehicle ID uses the VIN or the vehicle identification number. The vehicle ID is acquired based on the user ID of the user and information stored in the user management DB 303, which will be described later. The user ID is information for individually identifying multiple users who use the first site, and is information used as a login ID when each user logs in to the web server (first site). The user ID is set, for example, when each user registers as a member of the first site.

[0023] The control unit 302 identifies the first part based on the vehicle ID and information stored in the vehicle management DB 304 (described later). The first part is a part that can be installed on the first vehicle 1 among the parts handled at the first site. A "part that can be installed on the first vehicle 1" is a part that is compatible with the model of the first vehicle 1 and does not conflict with parts already installed on the first vehicle 1 in terms of function and / or installation location. In other words, a "part that can be installed on the first vehicle 1" is a part that is compatible with the model of the first vehicle 1 and can be installed without taking measures such as changing the function and / or removing the parts already installed on the first vehicle 1. Therefore, parts that are the same as parts already installed on the first vehicle 1 and parts that conflict with parts already installed on the first vehicle 1 are excluded from the first parts. Such first parts may include multiple types of parts. In addition, "parts already installed on the first vehicle 1" includes, for example, parts that were installed when the first vehicle 1 was manufactured, when the first vehicle 1 was sold, and / or when the lease of the first vehicle 1 began, as well as parts that were previously ordered at the first site (corresponding to the "fourth part" in this disclosure).

[0024] The control unit 302 generates a parts list based on the identified first parts. The control unit 302 displays a web page (hereinafter sometimes referred to as the "first web page") listing the generated parts list via the browser of the user terminal 200. The parts list in this embodiment is a list of parts available on the first site, and is a list that allows the first parts to be identified. Specifically, the parts list is a list that displays the first parts in an orderable form, and displays parts that cannot be installed on the first vehicle 1 (corresponding to the "second parts" according to the present disclosure) in an orderable form. The second parts include parts that are not compatible with the model of the first vehicle 1, and parts that are compatible with the model of the first vehicle 1 but conflict with parts already installed on the first vehicle 1.

[0025] FIG. 2 is a diagram showing an example of a first Web page. In the example shown in FIG. 2, the first Web page displays a parts list D1 and a "View Shopping Cart" button D2. The parts list D1 includes display areas D11-D12 for each part. The display areas D11-D12 for each part include a photo of the part, the name of the part (part name), a description of the part, an "Add to Cart" button, and the like. In this embodiment, for parts included in the parts list that correspond to first parts, the "Add to Cart" button is displayed in a selectable form (D11 in FIG. 2). Furthermore, for parts included in the parts list that correspond to second parts, the "Add to Cart" button is displayed in an unselectable form (grayed out) (D12 in FIG. 2).

[0026] When a user viewing a first web page inputs an operation to user terminal 200 to select the "Add to Cart" button in the display area of ​​a part corresponding to the first part (e.g., D11 in FIG. 2), a request signal (hereinafter sometimes referred to as a "first request signal") to add the corresponding part to the shopping cart is transmitted from user terminal 200 to server 300. When communication unit 301 of server 300 receives the first request signal, control unit 302 saves identification information (part ID) of the corresponding part in the shopping cart. The shopping cart is a function that stores the part IDs of parts that the user plans to order, and is an example of a "planned order list" according to the present disclosure.

[0027] A user viewing the first web page selects the "View Cart" button D2 When the user inputs the above operation into user terminal 200, a request signal to view the shopping cart (hereinafter, sometimes referred to as a "second request signal") is sent from user terminal 200 to server 300. When communication unit 301 of server 300 receives the second request signal, control unit 302 displays a web page of the shopping cart (hereinafter, sometimes referred to as a "second web page") through the browser of user terminal 200.

[0028] FIG. 3 is a diagram showing an example of a second web page. In the example shown in FIG. 3, the second web page includes the total price of the parts held in the shopping cart, an "Order" button, and a list of the parts held in the shopping cart. The list of parts held in the shopping cart includes a "Delete" button for deleting each part from the shopping cart. When a user viewing the second web page inputs an operation to select the "Order" button into user terminal 200, a request signal (hereinafter sometimes referred to as a "third request signal") requesting an order for the parts held in the shopping cart is transmitted from user terminal 200 to server 300. When communication unit 301 of server 300 receives the third request signal, control unit 302 executes payment processing, ordering processing, and the like for the parts held in the shopping cart. Known technologies can be used for the payment processing and ordering processing, and therefore, a description thereof will be omitted.

[0029] Returning to the description of FIG. 1 , upon receiving a first request signal (when a part is placed in the shopping cart), the control unit 302 updates the parts list displayed on the first web page. Specifically, the control unit 302 removes from the first parts the first parts included in the parts list before receiving the first request signal the part that was placed in the shopping cart (corresponding to the “third part” in this disclosure) and any parts that conflict with the third part. That is, the control unit 302 generates a new parts list in which the attributes of the third part and any parts that conflict with the third part are changed from first parts to second parts. The control unit 302 displays the new parts list on the first web page. Note that a part that conflicts with the third part is a part that conflicts with the third part in terms of function and / or installation location, etc., and cannot be installed in the first vehicle 1 unless measures such as changing the function and / or removing the third part are taken. The control unit 302 identifies the part that competes with the third part based on information stored in a part management DB 305 (described later).

[0030] User management DB 303, vehicle management DB 304, and parts management DB 305 are relational databases constructed in an auxiliary storage device of server 300. User management DB 303, vehicle management DB 304, and parts management DB 305 are realized, for example, by the processor of server 300 executing a DBMS program.

[0031] The user management DB 303 stores information linking users with the first vehicle 1. Specifically, it stores information linking the user ID of each user with the vehicle ID of the first vehicle 1 that each user owns or has the right to use.

[0032] The vehicle management DB 304 stores information linking the first vehicle 1 with the installation feasibility information for each part handled at the first site. FIG. 4 is a diagram showing an example of information stored in the vehicle management DB 304. As shown in FIG. 4, the vehicle management DB 304 in this embodiment has a record for each first vehicle 1 (hereinafter, sometimes referred to as a "vehicle information record"). As shown in FIG. 4, each vehicle information record has fields such as a vehicle ID, a part ID, installation feasibility, and history. Note that the configuration of the vehicle information record is not limited to the example shown in FIG. 4, and fields can be added, changed, or deleted as appropriate.

[0033] The vehicle ID of the first vehicle 1 is registered in the vehicle ID field of the vehicle information record. The part ID field registers the part ID of each of multiple parts handled at the first site. The installation feasibility field registers information indicating whether each part registered in the part ID field can be installed on the first vehicle 1. For example, a part that can be installed on the first vehicle 1 is registered as "Yes." Furthermore, a part that cannot be installed on the first vehicle 1 is registered as "No." The information registered in the installation feasibility field is set based on the parts already installed on the first vehicle 1. Information regarding the parts already installed on the first vehicle 1 may be provided to the operator of the first site by, for example, the manufacturer of the first vehicle 1, the dealer of the first vehicle 1, and / or the leasing company of the first vehicle 1. The history field registers the part ID of a part that the user of the first vehicle 1 has previously ordered on the first site. Note that if the user of the first vehicle 1 has not previously ordered any parts on the first site, "No" is registered in the history field.

[0034] Returning to the explanation of FIG. 1, the parts management DB 305 stores information linking each part handled at the first site with a part that competes with that part. FIG. 5 is a diagram showing an example of information stored in the parts management DB 305. As shown in FIG. 5, the parts management DB 305 in this embodiment has records (hereinafter sometimes referred to as "part information records") corresponding to each of the multiple parts handled at the first site. As shown in FIG. 5, each part information record has fields such as a part ID and a competing part. Note that the configuration of the part information record is not limited to the example shown in FIG. 5, and fields can be added, changed, or deleted as appropriate.

[0035] The part ID field of the part information record is registered with the part ID of a part handled at the first site. The competing part field is registered with the part ID of a part handled at the first site that competes with the part registered in the part ID field.

[0036] Any of the components of server 300 or part of its processing may be executed by another computer connected to network N1. The configuration of server 300 is not limited to the example shown in Fig. 1, and components may be omitted, changed, or added as appropriate.

[0037] (Processing flow) Next, the flow of processing performed by server 300 in this embodiment will be described with reference to Fig. 6. Fig. 6 is a flowchart showing a processing routine executed by server 300 when triggered by a user logging in to the first site.

[0038] 6, when a user logs in to a first site through a browser on user terminal 200, control unit 302 of server 300 accesses user management DB 303 using the user's login ID (user ID) as an argument and acquires the vehicle ID of first vehicle 1 (step S101). After completing the process of step S101, control unit 302 executes the process of step S102.

[0039] In step S102, the control unit 302 accesses the vehicle management DB 304 using the vehicle ID acquired in step S101 as an argument, and identifies a vehicle information record in which information matching the vehicle ID is registered in the vehicle ID field. The control unit 302 extracts, as candidates for the first part, parts in which "Yes" is registered in the installation feasibility field in the identified record. The control unit 302 determines whether a part ID (part ID of the fourth part) is registered in the history field of the identified vehicle information record. If "No" is registered in the history field, the control unit 302 identifies all of the candidates for the first part as the first part. Furthermore, if a part ID (part ID of the fourth part) is registered in the history field, the control unit 302 accesses the part management DB 305 using the part ID (part ID of the fourth part) registered in the history field as an argument, and extracts the part ID and The control unit 302 identifies a part information record in which matching information is registered in the part ID field. The control unit 302 extracts the part ID (part ID of the part that competes with the fourth part) registered in the competing part field of the identified part information record. The control unit 302 identifies, as the first part, candidates for the first part, excluding the fourth part and parts that compete with the fourth part. After completing the processing of step S102, the control unit 302 executes the processing of step S103.

[0040] In step S103, control unit 302 generates a parts list based on the first part identified in step S102. As described above, the parts list is a list in which, of the parts handled at the first site, the first part is displayed in an orderable form and the second part is displayed in an unorderable form. After completing the processing of step S103, control unit 302 executes the processing of step S104.

[0041] In step S104, control unit 302 displays a first Web page including the parts list generated in step S103 via the browser of user terminal 200. On the first Web page, as illustrated in FIG. 2 above, for parts included in the parts list that correspond to the first parts, the "Add to Cart" button is displayed in a selectable form (D11 in FIG. 2), and for parts that correspond to the second parts, the "Add to Cart" button is displayed in an unselectable form (D12 in FIG. 2). After completing the processing of step S104, control unit 302 executes the processing of step S105.

[0042] In step S105, control unit 302 determines whether communication unit 301 of server 300 has received a first request signal. As described above, the first request signal is a signal transmitted from user terminal 200 to server 300 when an operation to select the "Add to Cart" button for the first part is input to user terminal 200. If communication unit 301 of server 300 has received the first request signal (positive determination in step S105), control unit 302 executes the process of step S106.

[0043] In step S106, the control unit 302 identifies a third part (a part that the user plans to order) based on the part ID held in the shopping cart. After completing the process of step S106, the control unit 302 executes the process of step S107.

[0044] In step S107, the control unit 302 accesses the parts management DB 305 using the part ID of the third part identified in step S106 as an argument, and identifies a part information record in which information matching the part ID of the third part is registered in the part ID field. The control unit 302 identifies parts (parts that compete with the third part) registered in the competing part field of the identified part information record. The control unit 302 updates the parts list generated in step S103 by changing the attributes of the third part and parts that compete with the third part from first parts to second parts. After completing the processing of step S107, the control unit 302 executes the processing of step S108.

[0045] In step S108, control unit 302 updates the first Web page by changing the parts list displayed on the first Web page to the parts list updated in step S107. On the updated first Web page, the "Add to Cart" buttons for the third part and parts that compete with the third part, among the first parts identified in step S102, are displayed in an unselectable form. After completing the processing of step S108, control unit 302 executes the processing of step S109.

[0046] If the communication unit 301 of the server 300 does not receive the first request signal in step S105 (negative determination in step S105), the control unit 302 The process of step S108 is skipped and the process of step S109 is executed.

[0047] In step S109, the control unit 302 determines whether the communication unit 301 of the server 300 has received a first trigger signal. The first trigger signal is a signal that triggers the termination of the display of the first Web page. Such first trigger signals include, for example, a second request signal and a signal requesting the user to log out. If the communication unit 301 of the server 300 has not received the first trigger signal (negative determination in step S109), the control unit 302 executes the processing from step S105 onwards again. On the other hand, if the communication unit 301 of the server 300 has received the first trigger signal (positive determination in step S109), the control unit 302 terminates the execution of this processing routine.

[0048] According to the embodiment described above, among the parts handled at the first site, in addition to parts that have already been installed on the first vehicle 1 (parts that were installed when the first vehicle 1 was manufactured, parts that were installed when the first vehicle 1 was sold, parts that were installed when the lease of the first vehicle 1 began, and parts that have previously been ordered at the first site (fourth parts)), and parts that conflict with the parts that have already been installed on the first vehicle 1, parts (third parts) that are held in the shopping cart (list of parts to be ordered) and parts that conflict with the third parts are excluded from the first parts. Furthermore, on the first web page, among the parts handled at the first site, only the parts that correspond to the first parts are displayed in a form that can be ordered.

[0049] Therefore, by viewing the parts list on the first web page, the user of the first vehicle 1 can identify parts that can be installed without conflicting with parts already installed on the first vehicle 1. This saves the user the trouble of searching for parts that can be installed without conflicting with parts already installed on the first vehicle 1. Furthermore, it is possible to prevent the user from ordering parts that cannot be installed on the first vehicle 1, third parts, parts that conflict with the third parts, fourth parts, and parts that conflict with the fourth parts. This improves convenience for the user when ordering parts for the vehicle.

[0050] <Other> The above-described embodiment is merely an example, and the present disclosure may be modified and implemented as appropriate within the scope of the gist thereof. Furthermore, the processes and configurations described in the present disclosure may be freely combined and implemented as long as no technical contradictions arise. Furthermore, processes described as being performed by one device may be shared and executed by multiple devices. Furthermore, processes described as being performed by different devices may be executed by a single device. In a computer system, the hardware configuration for implementing each function can be flexibly changed.

[0051] The present disclosure can also be realized by supplying a computer program implementing the functions described in the above embodiments to a computer, and having one or more processors of the computer read and execute the program. Such a computer program may be provided to the computer via a non-transitory computer-readable storage medium connectable to the computer's system bus, or via a network. A non-transitory computer-readable storage medium is a recording medium that stores information such as data and programs through electrical, magnetic, optical, mechanical, or chemical action and can be read by a computer or the like. Such a non-transitory computer-readable storage medium may be, for example, any type of disk, such as a magnetic disk (such as a floppy disk or HDD) or an optical disk (such as a CD-ROM, DVD disk, or Blu-ray disk). The non-transitory computer-readable storage medium may also be a medium such as a read-only memory (ROM), a random access memory (RAM), an EPROM, an EEPROM, a magnetic card, a flash memory, an optical card, or a solid-state drive (SSD). good. [Explanation of symbols]

[0052] 1. First vehicle 200 user terminals 300 servers 301 Communications Department 302 Control Unit 303 User Management DB 304 Vehicle Management DB 305 Parts management DB

Claims

1. An information processing device that manages a first site for receiving orders for vehicle parts, the information processing device includes a database that stores mountability information for each component in association with first identification information that uniquely identifies a first vehicle, and a control unit connected to the database; The control unit obtaining the first identification information; Identifying a first part that can be installed on the first vehicle without conflicting with a part already installed on the first vehicle based on the first identification information and information stored in the database; posting a parts list identifying the first part on the first site; determining whether a first request signal is received from a user terminal used by a user of the first vehicle; In response to receiving the first request signal from the user terminal, identifying a third part included in a to-be-ordered list for the first vehicle; excluding the third part and parts competing with the third part from the first parts; To execute Information processing device.

2. the parts list includes, in addition to the first part, a second part that cannot be installed on the first vehicle; the control unit outputs the parts list in a format in which the first part is orderable and in which the second part is not orderable. The information processing device according to claim 1 .

3. The control unit Identifying a fourth part previously ordered for the first vehicle; excluding the fourth part and a part competing with the fourth part from the first parts; Further execute The information processing device according to claim 1 .

Images